z-logo
Premium
Regulated Oligomerization Induces Uptake of a Membrane Protein into COPII Vesicles Independent of Its Cytosolic Tail
Author(s) -
Springer Sebastian,
Malkus Per,
Borchert Britta,
Wellbrock Ursula,
Duden Rainer,
Schekman Randy
Publication year - 2014
Publication title -
traffic
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 2.677
H-Index - 130
eISSN - 1600-0854
pISSN - 1398-9219
DOI - 10.1111/tra.12157
Subject(s) - copii , microbiology and biotechnology , copi , endoplasmic reticulum , protein targeting , biology , transmembrane protein , vesicle , cytosol , fusion protein , transport protein , membrane protein , biochemistry , membrane , secretory pathway , golgi apparatus , recombinant dna , enzyme , receptor , gene
Export of transmembrane proteins from the endoplasmic reticulum ( ER ) is driven by directed incorporation into coat protein complex II ( COPII )‐coated vesicles. The sorting of some cargo proteins into COPII vesicles was shown to be mediated by specific interactions between transmembrane and COPII ‐coat‐forming proteins. But even though some signals for ER exit have been identified on the cytosolic domains of membrane proteins, the general signaling and sorting mechanisms of ER export are still poorly understood. To investigate the role of cargo protein oligomer formation in the export process, we have created a transmembrane fusion protein that – owing to its FK506 ‐binding protein domains – can be oligomerized in isolated membranes by addition of a small‐molecule dimerizer. Packaging of the fusion protein into COPII vesicles is strongly enhanced in the presence of the dimerizer, demonstrating that the oligomeric state is an ER export signal for this membrane protein. Surprisingly, the cytosolic tail is not required for this oligomerization‐dependent effect on protein sorting. Thus, an alternative mechanism, such as membrane bending, must account for ER export of the fusion protein.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here