Valosin-containing protein

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

Lua error in Module:Infobox_gene at line 33: attempt to index field 'wikibase' (a nil value). Transitional endoplasmic reticulum ATPase (TER ATPase) also known as valosin-containing protein (VCP) or CDC48 in S. Cerevisiae is an enzyme that in humans is encoded by the VCP gene.[1][2][3] The TER ATPase is an ATPase enzyme present in all eukaryotes and archaebacteria. Its main function is to segregate protein molecules from large cellular structures such as protein assemblies, organelle membranes and chromatin, and thus facilitate the degradation of released polypeptides by the multi-subunit protease proteasome.

p97/CDC48 is a member of the AAA+ (extended family of ATPases associated with various cellular activities) ATPase family. Enzymes of this family are found in all species from bacteria to humans. Many of them are important chaperones that regulate folding or unfolding of substrate proteins. p97/CDC48 is a type II AAA+ ATPase, which means that it contains two tandem ATPase domains (named D1 and D2, respectively) (Figure 1).

File:VCP Wiki Figure 1.jpg
Figure 1- A schematic diagram of the p97 domain structure.

The two ATPase domains are connected by a short polypeptide linker. A domain preceding the D1 domain (N-terminal domain]]) and a short carboxyl-terminal tail are involved in interaction with cofactors.[4] The N-domain is connected to the D1 domain by a short N-D1 linker.

Most known substrates of p97/CDC48 are modified with ubiquitin chains and degraded by the 26S proteasome. Accordingly, many p97/CDC48 coenzymes and adaptors have domains that can recognize ubiquitin.[5] It has become evident that the interplays between ubiquitin and p97/CDC48 cofactors are critical for many of the proposed functions, although the precise role of these interactions remains to be elucidated.

Discovery

CDC48 was discovered in a genetic screen for genes involved in cell cycle regulation in budding yeast.[6] The screen identified several alleles of Cdc48 that affects cell growth at non-permissive temperatures. The mammalian homolog of CDC48 was initially characterized as a 97 kDa protein precursor for the small peptide valosin. It was therefore named as valosin-containing protein (VCP) or p97,[7] but subsequent studies showed that valosin is an artifact of purification unrelated to p97. Nevertheless, the VCP nomenclature is still being used in the literature.

Tissue and subcelluar distribution

p97/CDC48 is one of the most abundant cytoplasmic proteins in eukaryotic cells. It is ubiquitously expressed in all tissues in multicellular organisms. In humans, the mRNA expression of p97 was found to be moderately elevated in certain types of cancer.[5]

In mammalian cells, p97 is predominantly localized to the cytoplasm, and a significant fraction is associated to membranes of cellular organelles such as the endoplasmic reticulum (ER), Golgi, mitochondria, and endosomes.[2][8][9][10][11] The subcellular localization of CDC48 has not been fully characterized, but is likely to be similar to the mammalian counterpart. A fraction of p97/CDC48 was also found in the nucleus.[12]

Structure

According to the crystal structures of full-length wild-type p97,[13][14] six p97 subunits assemble into a barrel-like structure, in which the N-D1 and D2 domains form two concentric, stacked rings (Figure 2).

File:VCP Wiki Figure 2.jpg
Figure 2- The structure of p97. The six subunits are shown as molecular surface in different colors. Domains of each subunit are also shaded differently. Two views are presented. This structure represents p97 in an ADP bound state.

The N-D1 ring is larger (162 Å in diameter) than the D2 ring (113 Å) due to the laterally attached N-domains. The D1 and D2 domains are highly homologous in both sequence and structure, but they serve distinct functions. For example, the hexameric assembly of p97 only requires the D1 but not the D2 domain.[15] Unlike many bacterial AAA+ proteins, assembly of p97 hexamer does not depend on the presence of nucleotide. The p97 hexameric assembly can undergo dramatic conformational changes during nucleotide hydrolysis cycle,[16][17][18][19][20] and it is generally believed that these conformational changes generate mechanical force, which is applied to substrate molecules to influence their stability and function. However, how precisely p97 generates force is unclear.

The ATP hydrolysis cycle

The ATP hydrolyzing activity is indispensable for the p97/CDC48 functions.[21] The two ATPase domains of p97 (D1 and D2) are not equivalent because the D2 domain displays higher ATPase activity than the D1 domain in wild-type protein. Nevertheless, their activities are dependent of each other.[22][23][24][25] For example, nucleotide binding to the D1 domain is required for ATP binding to the D2 domain and nucleotide binding and hydrolysis in D2 is required for the D1 domain to hydrolyze ATP.

The ATPase activity of p97 can be influenced by many factors. For example, it can be stimulated by heat[25] or by a putative substrate protein.[26] Association with cofactors can have either positive or negative impact on the p97 ATPase activity.[27][28]

Mutations in p97 can also influence its activity. For example, p97 mutant proteins carrying single point mutations found in patients with IBMPFD (inclusion body myopathy associated with Paget disease of the bone and frontotemporal dementia) (see below) have 2-3fold increase in ATPase activity.[23][29][30]

p97/CDC48-interacting proteins

Recent proteomic studies have identified a large number of p97-interacting proteins. Many of these proteins serve as adaptors that link p97/CDC48 to a particular subcellular compartment to function in a specific cellular pathway. Others function as adaptors that recruit substrates to p97/CDC48 for processing. Some p97-interacting proteins are also enzymes such as N-glycanase, ubiquitin ligase, and deubiquitinase, which assist p97 in processing substrates.

Most cofactors bind p97/CDC48 through its N-domain, but a few interact with the short carboxy-terminal tail in p97/CDC48. Representative proteins interacting with the N-domain are Ufd1, Npl4, p47 and FAF1.[31][32][33] Examples of cofactors that interact with the carboxy-terminal tail of p97 are PLAA, PNGase, and Ufd2.[34][35][36]

The molecular basis for cofactor binding has been studied for some cofactors that interact with the p97 N-domain. The N-domain consists of two sub-domains of roughly equal size: the N-terminal double Y-barrel and a C-terminal b-barrel (Figure 3).

File:VCP Wiki Figure 3.jpg
Figure 3- Structure of the N-domain of p97. The N-domain is depicted as a molecular surface superimposed to a ribbon representation.

Structural studies show that many cofactor proteins bind to the N-domain at a cleft formed between the two sub-domains.

Among those that bind to the N-domain of p97, two most frequently occurring sequence motifs are found: one is called UBX motif (ubiquitin regulatory X)[37] and the other is termed VIM (VCP-interacting motif).[38] The UBX domain is a 80-residue module with a fold highly resembling the structure of ubiquitin. The VCP-interacting motif (VIM) is a linear sequence motif (RX5AAX2R) found in a number of p97 cofactors including gp78,[39] SVIP (small VCP-inhibiting protein)[40] and VIMP (VCP interacting membrane protein).[41] Although the UBX domain uses a surface loop whereas the VIM forms a-helix to bind p97, both UBX and VIM bind at the same location between the two sub-domains of the N-domain (Figure 3).[42] It was proposed that hierarchical binding to distinct cofactors may be essential for the broad functions of p97/CDC48.[43][44]

Function

p97/CDC48 performs diverse functions through modulating the stability and thus the activity of its substrates. The general function of p97/CDC48 is to segregate proteins from large protein assembly or immobile cellular structures such as membranes or chromatin, allowing the released protein molecules to be degraded by the proteasome. The functions of p97/CDC48 can be grouped into the following three major categories.

Protein quality control

The best characterized function of p97 is to mediate a network of protein quality control processes in order to maintain protein homeostasis.[45] These include endoplasmic reticulum-associated protein degradation (ERAD) and mitochondria-associated degradation.[10][46] In these processes, ATP hydrolysis by p97/CDC48 is required to extract aberrant proteins from the membranes of the ER or mitochondria. p97/CDC48 is also required to release defective translation products stalled on ribosome in a process termed ribosome-associated degradation.[47][48][49] It appears that only after extraction from the membranes or large protein assembly like ribosome, can polypeptides be degraded by the proteasome. In addition to this ‘segregase’ function, p97/CDC48 might have an additional role in shuttling the released polypeptides to the proteasome. This chaperoning function seems to be particularly important for degradation of certain aggregation-prone misfolded proteins in nucleus.[50] Several lines of evidence also implicate p97 in autophagy, a process that turns over cellular proteins (including misfolded ones) by engulfing them into double-membrane-surrounded vesicles named autophagosome, but the precise role of p97 in this process is unclear.[51]

Chromatin-associated functions

p97 also functions broadly in eukaryotic nucleus by releasing protein molecules from chromatins in a manner analogous to that in ERAD.[52] The identified p97 substrates include transcriptional repressor α2 and RNA polymerase (Pol) II complex and CMG DNA helicase in budding yeast, and the DNA replicating licensing factor CDT1, DNA repairing proteins DDB2 and XPC, mitosis regulator Aurora B, and certain DNA polymerases in mammalian cells. These substrates link p97 function to gene transcription, DNA replication and repair, and cell cycle progression.

Membrane fusion and trafficking

Biochemical and genetic studies have also implicated p97 in fusion of vesicles that lead to the formation of Golgi apparatus at the end of mitosis.[53] This process requires the ubiquitin binding adaptor p47 and a p97-associated deubiquitinase VCIP135, and thus connecting membrane fusion to the ubiquitin pathways. However, the precise role of p97 in Golgi formation is unclear due to lack of information on relevant substrate(s). Recent studies also suggest that p97 may regulate vesicle trafficking from plasma membrane to the lysosome, a process termed endocytosis.[51]

Clinical significance

Links to human diseases

Mutations in VCP cause multisystem proteinopathy (MSP), a dominantly inherited, pleiotropic, degenerative disorder of humans that can affect muscle, bone and/or the central nervous system.[1][2] MSP can manifest clinically as classical amyotrophic lateral sclerosis (ALS), frontotemporal dementia (FTD), inclusion body myopathy (IBM), Paget's disease of bone (PDB), or as a combination of these disorders.[3] A useful operational definition of MSP is dominantly inherited degeneration that includes neurological involvement (either motor neuron disease or dementia) in combination with either distal myopathy or Pagetic bone degeneration.[1] Most MSP patients present with weakness and of these ~65% present with motor neuron involvement.[3] Up to 30% of MSP patients may have exclusively motor neuron involvement.[3] Although MSP is rare, growing interest in this syndrome derives from the molecular insights the condition provides into the etiological relationship between common age-related degenerative diseases of muscle, bone and brain. It has been estimated that ~50% of MSP may be caused by missense mutations affecting the valosin-containing protein (VCP) gene.[4]

Cancer therapy

The first p97 inhibitor Eeyarestatin (EerI) was discovered by screening and characterizing compounds that inhibit the degradation of a fluorescence-labeled ERAD substrate.[54][55] The mechanism of p97 inhibition by EerI is unclear, but when applied to cells, it induces biological phenotypes associated with p97 inhibition such as ERAD inhibition, ER stress elevation, and apoptosis induction. Importantly, EerI displays significant cancer-killing activity in vitro preferentially against cancer cells isolated from patients, and it can synergize with the proteasome inhibitor Bortezomib to kill cancer cells.[56] These observations prompt the idea of targeting p97 as a potential cancer therapy. This idea was further confirmed by studying several ATP competitive and allosteric inhibitors.[57][58][59] More recently, a potent and specific p97 inhibitor CB-5083 has been developed, which demonstrates promising anti-cancer activities in mouse xenograft tumor models.[60] The compound is now being evaluated in a phase 1 clinical trial.

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. 2.0 2.1 Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. 4.0 4.1 Lua error in package.lua at line 80: module 'strict' not found.
  5. 5.0 5.1 Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. 10.0 10.1 Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. 23.0 23.1 Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. 25.0 25.1 Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. Lua error in package.lua at line 80: module 'strict' not found.
  36. Lua error in package.lua at line 80: module 'strict' not found.
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. Lua error in package.lua at line 80: module 'strict' not found.
  40. Lua error in package.lua at line 80: module 'strict' not found.
  41. Lua error in package.lua at line 80: module 'strict' not found.
  42. Lua error in package.lua at line 80: module 'strict' not found.
  43. Lua error in package.lua at line 80: module 'strict' not found.
  44. Lua error in package.lua at line 80: module 'strict' not found.
  45. Lua error in package.lua at line 80: module 'strict' not found.
  46. Lua error in package.lua at line 80: module 'strict' not found.
  47. Lua error in package.lua at line 80: module 'strict' not found.
  48. Lua error in package.lua at line 80: module 'strict' not found.
  49. Lua error in package.lua at line 80: module 'strict' not found.
  50. Lua error in package.lua at line 80: module 'strict' not found.
  51. 51.0 51.1 Lua error in package.lua at line 80: module 'strict' not found.
  52. Lua error in package.lua at line 80: module 'strict' not found.
  53. Lua error in package.lua at line 80: module 'strict' not found.
  54. Lua error in package.lua at line 80: module 'strict' not found.
  55. Lua error in package.lua at line 80: module 'strict' not found.
  56. Lua error in package.lua at line 80: module 'strict' not found.
  57. Lua error in package.lua at line 80: module 'strict' not found.
  58. Lua error in package.lua at line 80: module 'strict' not found.
  59. Lua error in package.lua at line 80: module 'strict' not found.
  60. Lua error in package.lua at line 80: module 'strict' not found.

Further reading

  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.

External links

Lua error in package.lua at line 80: module 'strict' not found.