Abstract

The entry of the SARS coronavirus (SCV) into cells is initiated by binding of its spike envelope glycoprotein (S) to a receptor, ACE2. We and others identified the receptor-binding domain (RBD) by using S fragments of various lengths but all including the amino acid residue 318 and two other potential glycosylation sites. To further characterize the role of glycosylation and identify residues important for its function as an interacting partner of ACE2, we have cloned, expressed and characterized various soluble fragments of S containing RBD, and mutated all potential glycosylation sites and 32 other residues. The shortest of these fragments still able to bind the receptor ACE2 did not include residue 318 (which is a potential glycosylation site), but started at residue 319, and has only two potential glycosylation sites (residues 330 and 357). Mutation of each of these sites to either alanine or glutamine, as well as mutation of residue 318 to alanine in longer fragments resulted in the same decrease of molecular weight (by approximately 3 kDa) suggesting that all glycosylation sites are functional. Simultaneous mutation of all glycosylation sites resulted in lack of expression suggesting that at least one glycosylation site (any of the three) is required for expression. Glycosylation did not affect binding to ACE2. Alanine scanning mutagenesis of the fragment S319–518 resulted in the identification of ten residues (K390, R426, D429, T431, I455, N473, F483, Q492, Y494, R495) that significantly reduced binding to ACE2, and one residue (D393) that appears to increase binding. Mutation of residue T431 reduced binding by about 2-fold, and mutation of the other eight residues – by more than 10-fold. Analysis of these data and the mapping of these mutations on the recently determined crystal structure of a fragment containing the RBD complexed to ACE2 (Li, F, Li, W, Farzan, M, and Harrison, S. C., submitted) suggested the existence of two hot spots on the S RBD surface, R426 and N473, which are likely to contribute significant portion of the binding energy. The finding that most of the mutations (23 out of 34 including glycosylation sites) do not affect the RBD binding function indicates possible mechanisms for evasion of immune responses.

Highlights

  • Viral envelope glycoproteins initiate entry of viruses into cells by binding to cell surface receptors followed by conformational changes leading to membrane fusion and http://www.virologyj.com/content/2/1/73 delivery of the genome to the cytoplasm [1]

  • Together with data for inhibition of binding by antibodies, developed against peptides from S, these findings suggested that the receptor-binding domain (RBD) is located between amino acid residues 303 and 537 [6]

  • We and others have previously identified the RBD by using fragments containing three potential glycosylation sites – at residues 318, 330 and 357 [6,8,10]

Read more

Summary

Background

Viral envelope glycoproteins initiate entry of viruses into cells by binding to cell surface receptors followed by conformational changes leading to membrane fusion and (page number not for citation purposes) http://www.virologyj.com/content/2/1/73 delivery of the genome to the cytoplasm [1]. Glycoproteins of coronaviruses are no exception and mediate binding to host cells followed by membrane fusion; they are major targets for neutralizing antibodies and form the characteristic corona of large, distinctive spikes in the viral envelopes [2,3]. Such 20 nm complex surface projections surround the periphery of the SCV particles [4]. Fragments containing the N-terminal amino acid residues 17 to 537 and 272 to 537 but not 17 to 276 bound to Vero E6 cells and purified soluble receptor (ACE2) molecules [6]. RBD does not affect to any measurable degree their binding to the receptor (ACE2), and analyze the S RBD-ACE2 interaction

Results
Discussion
Methods
Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.