tech-invite   World Map
3GPP     Specs     Glossaries     Architecture     IMS     UICC       IETF     RFCs     Groups     SIP     ABNFs       Search     Home

Features       Entities       Reference Points       UICC Files       Identifiers

3GPP Glossaries:  Interfaces / Reference Points

   #      A      B      C      D      E      F      G      H      I      J      K      L      M      N      O      P      Q      R      S      T      U      V      W      X      Y      Z  
Here        Top        Up        Prev        Next

 

|  C  |  CAP  |  Cr  |  CSC‑1  |  CSC‑2  |  CSC‑3  |  CSC‑4  |  CSC‑5  |  CSC‑7  |  CSC‑8  |  CSC‑9  |  CSC‑10  |  CSC‑11  |  CSC‑12  |  CSC‑13  |  CSC‑14  |  CSC‑15  |  Cx  |

 

C-interface   (MAP)

Up       Top

between  HLR
and  MSC

specified from  GSM Phase 2  in
TS 09.02, clause 4.4.5 

When the fixed network is not able to perform the interrogation procedure needed to set up a call to a mobile subscriber, the Gateway MSC has to interrogate the HLR of the called subscriber to obtain the roaming number of the called MS. To forward a short message to a mobile subscriber, the SMS Gateway MSC has to interrogate the HLR to obtain the MSC number where the MS is located.


CAP   (CAMEL Application Part)

Up       Top

between  CTF
and  OCF



Cr   (SIP)

Up       Top

between  AS
and  MRFC

specified from  Rel-8
in TS 23.218, clauses 8.2 and 9.2 

This reference point enables the MRFC to fetch and cache documents and resources from an Application Server and to return data to an Application Server. It enables media control protocol requests, responses and notifications to be sent between the MRFC and an Application Server.


Up       Top

between  UE MC identity management client
and  MC Common Services Core: identity management server

see it   here

specified from  Rel-14  in
TS 23.280, clause 7.5.2.2
TS 33.180, clause 5.1.2.1 

The CSC-1 reference point provides for the authentication of the common services core to the MC service client and subsequent authentication of the user to the common services core on behalf of applications within the application plane


Up       Top

between  "on-network" UE MC group management client
and  MC Common Services Core: group management server

see it   here

specified from  Rel-14  in
TS 23.280, clause 7.5.2.3 

The CSC-2 reference point is used for MC service signalling for MC service data management of the MC service. The CSC‑2 reference point supports:
  • Configuration of group related data at the group management client by the group management server; and
  • Configuration of group related data at the group management server by the group management client.
The CSC-2 reference point shall use the HTTP‑1 and HTTP‑2 reference points for transport and routing of non-subscription/ notification related signalling. The CSC‑2 reference point shall use SIP‑1 and SIP‑2 reference points for transport and routing of subscription/notification related signalling.


Up       Top

between  MC service server
and  MC Common Services Core: group management server

see it   here

specified from  Rel-14  in
TS 23.280, clause 7.5.2.4 

The CSC-3 reference point provides for the MC service server to obtain group information corresponding to the MC service. The CSC‑3 reference point shall use HTTP‑1 and HTTP‑2 reference points for transport and routing of non-subscription/notification related signalling. The CSC‑3 reference point shall use SIP‑2 reference point for transport and routing of subscription/notification related signalling.


Up       Top

between  "on-network" UE MC configuration management client
and  MC Common Services Core: configuration management server

see it   here

specified from  Rel-14  in
TS 23.280, clause 7.5.2.5 

The CSC-4 reference point, which exists between the configuration management client and the configuration management server, provides the configuration information required for MC services while the MC service client is onnetwork. The CSC‑4 reference point supports:
  • configuration of the MC service UE by the MC service; and
  • configuration of the MC service application with the MC service related information that is not part of group management (e.g. policy information) by the MC service UE.
The CSC‑4 reference point shall use the HTTP‑1 and HTTP‑2 reference points for transport and routing of nonsubscription/ notification related signalling. The CSC‑4 reference point shall use SIP‑1 and SIP‑2 reference points for transport and routing of subscription/notification related signalling.


Up       Top

between  MC service server
and  MC Common Services Core: configuration management server

see it   here

specified from  Rel-14  in
TS 23.280, clause 7.5.2.6 

The CSC-5 reference point provides for the MC service server to obtain non-group MC service related information (e.g. policy information). The CSC‑5 reference point shall use HTTP‑1 reference point and HTTP‑2 reference point for transport and routing of nonsubscription/ notification related signalling. The CSC‑5 reference point shall use SIP‑2 reference point for transport and routing of subscription/notification related signalling.


Up       Top

between  MC Common Services Core: group management server
and  MC Common Services Core: group management server

see it   here

specified from  Rel-14  in
TS 23.280, clause 7.5.2.7 

The CSC-7 reference point allows group management servers to handle group management related signalling in multiple MC service systems environment. The CSC‑7 reference point shall use the HTTP‑1, HTTP‑2 and HTTP‑3 reference points for transport and routing of non-subscription/notification related signalling. The CSC‑7 reference point shall use SIP‑2 and SIP‑3 reference points for transport and routing of subscription/notification related signalling.


Up       Top

between  UE MC key management client
and  MC Common Services Core: key management server

see it   here

specified from  Rel-14  in
TS 23.280, clause 7.5.2.8
TS 33.180, clause 5.3.2 

The CSC-8 reference point provides a means for the key management server to provide security related information (e.g. encryption keys) to the key management client. The CSC‑8 reference point shall use the HTTP‑1 and HTTP‑2 reference points for transport and routing of security related information to the key management client.


Up       Top

between  MC service server
and  MC Common Services Core: key management server

see it   here

specified from  Rel-14  in
TS 23.280, clause 7.5.2.9
TS 33.180, clause 5.3.2 

The CSC-9 reference point provides a means for the key management server to provide security related information (e.g. encryption keys) to the MC service server. The CSC‑9 reference point shall use the HTTP‑1 and HTTP‑2 reference points for transport and routing of security related information to the MC service server.


Up       Top

between  MC Common Services Core: key management server
and  MC Common Services Core: group management server

see it   here

specified from  Rel-14  in
TS 23.280, clause 7.5.2.10
TS 33.180, clause 5.3.2 

The CSC-10 reference point provides a means for the key management server to provide security related information (e.g. encryption keys) to the group management server. The CSC‑10 reference point shall use the HTTP‑1 and HTTP‑2 reference points and may use the HTTP‑3 reference point for transport and routing of security related information to the group management server.


Up       Top

between  "off-network" UE MC configuration management client
and  MC Common Services Core: configuration management server

see it   here

specified from  Rel-14  in
TS 23.280, clause 7.5.2.11 

The CSC-11 reference point provides the configuration information required for MC services while the MC service client is offnet-work. The CSC‑11 reference point is the same as CSC‑4 reference point except that CSC‑11 does not support subscription/notification and therefore does not require the use of SIP‑1 and SIP‑2 reference points.


Up       Top

between  "off-network" UE MC group management client
and  MC Common Services Core: group management server

see it   here

specified from  Rel-14  in
TS 23.280, clause 7.5.2.12 

The CSC-12 reference point is used for MC service application signalling for data management of the MC service. The CSC‑12 reference point is the same as CSC‑2 reference point except that CSC‑12 does not support subscription/notification and therefore does not require the use of SIP‑1 and SIP‑2 reference points.


Up       Top

between  MC service user database
and  MC Common Services Core: configuration management server

see it   here

specified from  Rel-14  in
TS 23.280, clause 7.5.2.13 

The CSC-13 reference point is used for:
  • the configuration management server to store the user profile data in the specific MC service user database; and
  • the configuration management server to obtain the user profile from the specific MC service user database for further configuration in the MC service UE.


Up       Top

between  UE MC location management client
and  MC Common Services Core: location management server

see it   here

specified from  Rel-14  in
TS 23.280, clause 7.5.2.14 

The CSC-14 reference point is used by the location management server to receive location information report from location management client. The CSC‑14 reference point uses SIP‑1 and SIP‑2 reference points for transport and routing of subscription/notification related signalling. The CSC‑14 reference point uses the HTTP‑1 and HTTP‑2 reference points for transport and routing of non-subscription/notification related signalling.


Up       Top

between  MC service server
and  MC Common Services Core: location management server

see it   here

specified from  Rel-14  in
TS 23.280, clause 7.5.2.15 

The CSC-15 reference point is used by the MC service server to request and receive location information from location management server. The CSC‑15 reference point uses SIP‑1 and SIP‑2 reference points for transport and routing of subscription/notification related signalling. The CSC‑15 reference point uses the HTTP‑1 and HTTP‑2 reference points for transport and routing of non-subscription/notification related signalling.


Cx   (Diameter)

Up       Top

between  HSS
and  S-CSCF / I-CSCF

specified from  Rel-5
in  TS 23.228  and  TS 29.229 

Main procedures:
  • Serving CSCF assignment
  • Routing information retrieval from HSS to CSCF
  • Authorisation (e.g., checking of roaming agreement)
  • Authentication: transfer of security parameters of the subscriber between HSS and CSCF
  • Filter control: transfer of filter parameters of the subscriber from HSS to CSCF.
Commands:
  • UAR/UAA:  User-Authorization-Request/Answer
  • SAR/SAA:  Server-Assignment-Request/Answer
  • LIR/LIA:  Location-Info-Request/Answer
  • MAR/MAA:  Multimedia-Auth-Request/Answer
  • RTR/RTA:  Registration-Termination-Request/Answer
  • PPR/PPA:  Push-Profile-Request/Answer
See also  RFC 6733  for Diameter Base Protocol, and  TS 29.230  for 3GPP-specific Diameter codes and identifiers.



Up       Top