Abstract

Membrane fusion by the parainfluenza viruses is induced by virus-specific functional interaction between the attachment protein (HN) and the fusion (F) protein. This interaction is thought to be mediated by transient contacts between particular amino acids in the HN stalk domain and those in the F head domain. However, we recently reported that replacement of specified amino acids at or around the dimer interface of the HN head domain remarkably affected the F protein specificity. We then intended to further investigate this issue in the present study and revealed that the HPIV2 HN protein can be converted to an SV41 HN-like protein by substituting at least nine amino acids in the HPIV2 HN head domain with the SV41 HN counterparts in addition to the replacement of the stalk domain, indicating that specified amino acids in the HN head domain play very important roles in determining the specificity of the HN-F interaction. On the other hand, we previously reported that the PIV5 F protein can be converted to an SV41 F-like protein by replacing 21 amino acids in the head domain of the PIV5 F protein with those of the SV41 F protein. We then intended to further investigate this issue in the present study and found that replacement of 15 amino acids in the stalk domain in addition to the replacement of the 21 amino acids in the head domain of the PIV5 F protein resulted in creation of a more SV41 F-like protein, indicating that specified amino acids in the F stalk domain play important roles in determining the specificity of the HN-F interaction. These results suggest that the conformations of the HN stalk domain and the F head domain are dependent on the structures of the HN head domain and the F stalk domain, respectively. Presumably, the conformations of the former domains, which are considered directly involved in the HN-F interaction, can be modified by subtle changes in the structure of the latter domains, resulting in an altered specificity for the interacting partners.

Highlights

  • The parainfluenza viruses are classified into three genera in the subfamily Paramyxovirinae, that is, Rubulavirus, Avulavirus, and Respirovirus (Karron and Collins, 2013; Lamb and Parks, 2013)

  • In order to ascertain in the current study whether this simian virus 41 (SV41) F-like chimeric protein really has an HN protein specificity that is identical to that of the SV41 F protein, we employed a chimeric HN protein, CH541, whose ectodomain is composed of parainfluenza virus 5 (PIV5) HN-derived stalk domain and SV41 HN-derived head domain (Figures 1A,B), because it activated the PIV5 F protein seven-times more efficiently compared to the PIV5 HN protein at 12 h after co-transfection while it could not activate the SV41 F protein at all (Tsurudome et al, 2011)

  • We reported previously that a chimeric PIV5 F protein, no. 36, which harbored SV41 F-derived 21 amino acids in the head domain, was activated by the SV41 HN protein but not by the PIV5 HN protein as judged by cell–cell fusion assay in BHK cells at 12 h post transfection (Tsurudome et al, 2013) (Figure 1C)

Read more

Summary

Introduction

The parainfluenza viruses are classified into three genera in the subfamily Paramyxovirinae, that is, Rubulavirus, Avulavirus, and Respirovirus (Karron and Collins, 2013; Lamb and Parks, 2013). The HN protein is required for the F protein in order to mediate membrane fusion, it is not precisely known how the HN protein activates the F protein. It is appreciated, at least, that membrane fusion is induced through a series of conformational changes of the F protein that has been triggered by specific interaction with the cognate HN protein (Lamb and Jardetzky, 2007; Iorio et al, 2009)

Methods
Results
Conclusion
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.