Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.280  Word version:  19.4.0

Top   Top   Up   Prev   Next
1…   5…   6   7…   8…   9…   10…   10.1.5…   10.2…   10.2.6…   10.3…   10.6…   10.7…   10.7.3.8…   10.8…   10.9…   10.9.3.9…   10.10…   10.10.3   10.11…   10.12…   10.13…   10.14…   10.15…   10.16…   10.17…   11…   11.5…   A…   B…   C…   E… 
7 Functional model  7.1 General  7.2 Description of the planes  7.3 Functional model description  7.4 Functional entities description  7.5 Reference points 
...

 

7  Functional model  p. 34

7.1  General  p. 34

The functional model for the MC services architecture is defined as a series of planes to allow for the breakdown of the architectural description.
Further, each plane is expected to operate in an independent manner, providing services to the connected planes as and when requested by the connected plane, and requesting services from other planes as required.
As a consequence of this each plane should manage on its own behalf:
  1. use of identities. Each plane is therefore responsible for the privacy of that plane's own identities; and
  2. security for that plane. This does not preclude a plane requesting security services from another plane, but that is a decision made within the plane, as to whether to use offered security services or mechanisms within the plane itself.
Up

7.2  Description of the planes  p. 34

The following planes are identified:
  1. application plane: The application plane provides all of the services (e.g. call control, floor control, video control, data control) required by the user together with the necessary functions to support MC service. It uses the services of the signalling control plane to support those requirements. For example, within the MCPTT service, the application plane also provides for the conferencing of media, and provision of tones and announcements; and
  2. signalling control plane: The signalling control plane provides the necessary signalling support to establish the association of users involved in an MC service, such as an MCPTT call or other type of MC services. The signalling control plane also offers access to and control of services across MC services. The signalling control plane uses the services of the bearer plane.
Bearers supporting these planes are defined for LTE within TS 23.401. The resource control that is needed to support these planes is defined within TS 23.203. The application plane also relies on the use of multicast bearers established via procedures defined in TS 23.468 and TS 23.246.
Up

7.3  Functional model description  p. 34

7.3.1  On-network functional model  p. 34

Each MC service can be represented by an application plane functional model. The functional model across MC services may be similar but is described by the individual functional entities and reference points that belong to that MC service. Within the application plane for an MC service there is a common set of functions and reference points. The common set is shared across services. This common set of functions and reference points is known as the common services core.
Figure 7.3.1-1 shows the functional model for the application plane for an MC system.
Reproduction of 3GPP TS 23.280, Fig. 7.3.1-1: Functional model for application plane for an MC system
Figure 7.3.1-1: Functional model for application plane for an MC system
Up
The common services core functions and reference points shown in Figure 7.3.1-1 are shared across each MC service. The description of the functions and reference points specific to an MC service is contained in the corresponding MC service TS.
In the model shown in Figure 7.3.1-1, the following apply:
  • A specific MC service server is an instantiation of a GCS AS in accordance with TS 23.468.
  • The functional alias management client is an integrated functional entity of the configuration management client. The functional alias management client is described in subclause 7.4.2.2.12.
  • The functional alias management server is an integrated functional entity of the configuration management server. The functional alias management server is described in subclause 7.4.2.2.13.
Figure 7.3.1-2 shows the functional model for the signalling control plane.
Reproduction of 3GPP TS 23.280, Fig. 7.3.1-2: Functional model for signalling control plane
Figure 7.3.1-2: Functional model for signalling control plane
Up
Figure 7.3.1-3 shows the relationships between the reference points of the application plane of an MC service server and the signalling plane.
Reproduction of 3GPP TS 23.280, Fig. 7.3.1-3: Relationships between reference points of MC service application plane and signalling control planes
Figure 7.3.1-3: Relationships between reference points of MC service application plane and signalling control planes
Up
Up

7.3.2  Off-network functional model  p. 38

Figure 7.3.2-1 shows the functional model for off-network operation.
Reproduction of 3GPP TS 23.280, Fig. 7.3.2-1: Functional model for MC service off-network operation
Figure 7.3.2-1: Functional model for MC service off-network operation
Up
For a specific MC service, the description of off-network operation is contained in the corresponding MC service TS.

7.4  Functional entities description  p. 38

7.4.1  General  p. 38

Each subclause is a description of a functional entity and does not imply a physical entity.

7.4.2  Application plane  p. 38

7.4.2.1  General  p. 38

Entities within the application plane of an MC system provide application control and media specific functions to support one or more MC services.
For each MC service, the functional entities description is contained in the corresponding MC service TS.

7.4.2.2  Common services core  p. 39

7.4.2.2.1  Configuration management client  p. 39
The configuration management client functional entity acts as the application user agent for configuration related transactions. The configuration management client interacts with the configuration management server and provides and receives configuration data.
The configuration management client functional entity is supported by the signalling user agent and HTTP client functional entities of the signalling control plane.
The configuration management client provides the functional alias management client functionality as described in subclause 7.4.2.2.12.
Up
7.4.2.2.2  Configuration management server (CMS)  p. 39
The configuration management server is a functional entity used to configure one or more MC service applications with non-group management MC service related information and configure data on the configuration management client. The configuration management server manages MC service configuration supported within the MC service provider.
The configuration management server functional entity is supported by the SIP AS and HTTP server functional entities of the signalling control plane.
The configuration management server provides the functional alias management server functionality as described in subclause 7.4.2.2.13.
Up
7.4.2.2.3  Group management client  p. 39
The group management client functional entity acts as the application user agent for management of groups. A MC system maintains groups corresponding to one or more mission critical organizations. The group management client interacts with the group management server.
The group management client functional entity is supported by the signalling user agent and HTTP client functional entities of the signalling control plane.
7.4.2.2.4  Group management server (GMS)  p. 39
The group management server functional entity provides for management of groups supported within the MC service provider.
The group management server functional entity is supported by the SIP AS and HTTP server functional entities of the signalling control plane.
All the group management clients supporting users belonging to a single group are required to use the same group management server for that group. A group management client supporting a user involved in multiple groups can have relationships with multiple group management servers.
The group management server manages media policy information for use by the UE for media processing.
The group management server manages group call policy information for use by the UE for both on-network and off-network group call control.
Up
7.4.2.2.5  Identity management client  p. 39
This functional entity acts as the application user agent for MC ID transactions. It interacts with the identity management server.
7.4.2.2.6  Identity management server (IdMS)  p. 39
The identity management server is a functional entity that is capable of authenticating the MC ID. It contains the knowledge and means to do authentication by verifying the credentials supplied by the user.
The identity management server functional entity may reside in the same domain as the user's MC system.
7.4.2.2.7  Key management client  p. 40
This functional entity acts as the application user agent for key management functions. It interacts with the key management server.
The functionality of the key management client is specified in TS 33.180.
7.4.2.2.8  Key management server (KMS)  p. 40
The key management server is a functional entity that stores and provides security related information (e.g. encryption keys) to the key management client, group management server and MC service server(s) to achieve the security goals of confidentiality and integrity of media and signalling.
The functionality of the key management server is specified in TS 33.180.
7.4.2.2.9  Location management client  p. 40
This functional entity acts as the application user agent for location management functions. It interacts with the location management server.
7.4.2.2.10  Location management server (LMS)  p. 40
The location management server is a functional entity that receives and stores user location information, and provides user location information to the MC service server. The location management server may also acquire location information provided by PLMN operator (e.g. LCS network).
7.4.2.2.11  Void
7.4.2.2.12  Functional alias management client |R15|  p. 40
The functional alias management client functional entity acts as the application user agent for management of functional aliases. The functional alias management client interacts with the functional alias management server.
The functional management client functional entity is supported by the signalling user agent and by the HTTP client functional entities of the signalling control plane.
7.4.2.2.13  Functional alias management server |R15|  p. 40
The functional alias management server functional entity provides the configuration management of functional alias(es).
The functional alias management server functional entity is supported by the SIP AS and by the HTTP server functional entities of the signalling control plane.
7.4.2.2.14  Void
7.4.2.2.15  Void

7.4.2.3  MC service  p. 40

7.4.2.3.1  MC service client  p. 40
The MC service client functional entity acts as the user agent for all MC service transactions. For a specific MC service, the detailed description of functions of the MC service client is contained in the corresponding MC service TS.
7.4.2.3.2  MC service server  p. 41
The MC service server functional entity provides centralised support for MC services.
The MC service server functional entity represents a specific instantiation of the GCS AS described in TS 23.468 to control multicast and unicast operations for group communications. For a specific MC service, the detailed description of the GCS AS role assumed by the MC service server is contained in the corresponding MC service TS.
The MC service server performs the functional alias controlling role for functional alias management including functional alias activation, deactivation, take over and interrogation. For a single functional alias, only one MC service server is specified as the functional alias controlling role. The detailed description of the functional alias controlling role assumed by the different MC service servers are contained in TS 23.379, TS 23.281 and TS 23.282.
The MC service server functional entity is supported by the SIP AS, HTTP client and HTTP server functional entities of the signalling control plane.
Up
7.4.2.3.3  MC service user database  p. 41
This functional entity contains information of the MC service user profile associated with an MC service ID that is held by the MC service provider at the application plane. The MC service user profile is determined by the mission critical organization, the MC service provider, and potentially the MC service user.
Each MC service shall have a corresponding MC service user database i.e. MCPTT user database as defined in TS 23.379, MCVideo user database as defined in TS 23.281 and MCData user database as defined in TS 23.282. These MC service user databases can be co-located.
Up
7.4.2.3.4  MC gateway server |R15|  p. 41
The MC gateway server provides support for interconnection between a primary MC system and a partner MC system in a different trust domain whilst providing topology hiding. It acts as a proxy for one or more MC service servers in the partner MC system without needing to expose the MC service servers in the primary MC system outside the trusted domain of the primary MC system. It may be a role of an MC service server described in subclause 7.4.2.3.2 of the present document.
The MC gateway server is responsible for relaying signalling control messages and media between MC service servers in the interconnected MC systems.
Up

7.4.2.4  Recording and replay |R19|  p. 41

7.4.2.4.1  MC replay client  p. 41
The MC replay client is a functional entity that can be used by an authorized user to retrieve recorded metadata and media from an MC recording server and replay it.
An MC replay client may be used in an MC replay UE. It may also be included in an MC service UE.
7.4.2.4.2  MC recording server  p. 41
The MC recording server is a functional entity that can receive and record communications metadata and media relating to target users and target groups from MC service servers. The MC recording server securely stores the recorded information into mass storage(s) and allows controlled access for replay/retrieve functions.
The security aspects of storing metadata and media into mass storage is specified in TS 33.180.
The MC recording server functional entity is supported by the SIP AS and HTTP server functional entities of the signalling control plane.
The target users and/or groups for recording are set in the MC service user profile configuration data (A.3) and in the group configuration data (A.4). This can be done by an authorized user utilizing the CSC-4 reference point.
Up
7.4.2.4.3  Mass storage  p. 42
The recorded media and metadata are stored on mass storage(s). The storage solution is outside the scope of the present document.

7.4.2.5  Administrative Configuration Management |R19|  p. 42

7.4.2.5.1  ACM client  p. 42
The ACM client is a functional entity that acts as the application user agent for an authorized user that is responsible for requesting, approving, and applying configurations between a primary MC system and partner MC system. These configurations include MC service user profile, group management, and associated system parameters. The administrative configuration management client interacts with the administrative configuration management server.
The ACM client functional entity is supported by the signalling user agent and by the HTTP client functional entities of the signalling control plane.
Up
7.4.2.5.2  ACM server  p. 42
The ACM server is a functional entity that provides the necessary capabilities to control and perform required transactions to exchange administrative configurations and/or information between partner MC system(s). ACM server has the following functions:
  • Provides the temporary storage of configuration changes when requests are received from a partner MC system. The configuration changes include MC service user profile, group management configuration, and associated system parameters.
  • Supports requests from the ACM client that result in exchanges with the partner MC system to share administrative configurations and information.
  • Controls, processes, validates, accepts, forwards or rejects administrative configuration exchange based on a set of pre-defined rules and policies.
The administrative configuration management server functional entity is supported by the SIP AS and by the HTTP server functional entities of the signalling control plane.
Up

7.4.3  Signalling control plane  p. 42

7.4.3.1  SIP entities  p. 42

7.4.3.1.1  Signalling user agent  p. 42
This functional entity acts as the SIP user agent (both client and server) for all SIP transactions.
7.4.3.1.2  SIP AS  p. 42
The SIP AS functional entity supports the following functions on behalf of the MC service:
  • influencing and impacting the SIP session; and
  • supporting event subscription and event notification.
7.4.3.1.3  SIP core  p. 43
7.4.3.1.3.1  General  p. 43
The SIP core contains a number of sub-entities responsible for registration, service selection and routing in the signalling control plane.
The SIP core shall be either:
  1. compliant with TS 23.228, i.e. the SIP core is a 3GPP IP multimedia core network subsystem; or
  2. a SIP core, which internally need not comply with the architecture of TS 23.228, but with the reference points that are defined in subclause 7.5.3 (if exposed), compliant to the reference points defined in TS 23.002.
The data related to the functions of the SIP core, e.g. for data for application service selection, the identity of the serving registrar or authentication related information may be provided by the PLMN operator responsible for the bearer plane. In this case, the SIP database that is the source of the data may be part of the HSS. Alternatively, this data may be provided by the MC service provider. In this case, the source of the data may be the MC service provider's SIP database.
Up
7.4.3.1.3.2  Local inbound / outbound proxy  p. 43
The local inbound / outbound proxy functional entity acts as both an inbound proxy and an outbound proxy for all SIP transactions. This functional entity can provide the following functions:
  • NAT traversal;
  • Resource control;
  • Route/forward requests and responses to the user agents;
  • SIP signalling security; and
  • Depending on the PLMN operator policy, discovery and address resolution, including E.164 numbers.
7.4.3.1.3.3  Registrar finder  p. 43
The registrar finder functional entity is responsible for:
  1. Identifying the serving registrar / application service selection functional entity. The serving registrar / application service selection functional entity is identified using information provided either by the PLMN operator's own SIP database or the MC service provider's SIP database, and optionally using the PLMN operator's internal information e.g. network topology, registrar availability.
    1. Registrar finder and registrar in the MC service provider domain: registrar finder in the MC service provider's domain uses the information from the MC service provider's SIP database to identify the serving registrar in the MC service provider domain.
    2. Registrar finder and registrar in the PLMN operator domain: registrar finder uses information from PLMN operator's SIP database to identify the serving registrar in the PLMN operator domain.
    3. Registrar finder in PLMN operator domain and registrar in MC service provider domain: registrar finder uses information from the MC service provider's SIP database to identify the serving registrar in the MC service provider domain.
  2. Providing discovery and address resolution, including E.164 numbers.
Up
7.4.3.1.3.4  Registrar / application service selection  p. 44
The registrar / application service selection functional entity provides the following functions:
  • Registrar function (with integral provision of a location server) and also acts as an inbound proxy (with access to the integral location server), and outbound proxy for all SIP transactions where application service selection is required. It registers the user and maintains the association of the location and identity of the user in a location service. It provides notifications of the registration states.
  • Supports authentication for identities provided within SIP signalling. Both the registrar (with integral location server) and authentication functions are supported by access either to the public network's own SIP database or the MC service provider's SIP database.
  • Can provide the application service selection for all SIP transactions, possibly based on application service selection information stored by either the public network's own SIP database or the MC service provider's SIP database.
  • Performs SIP signalling security.
Up
7.4.3.1.4  Diameter proxy |R15|  p. 44
This functional entity acts as a proxy agent for Diameter messaging as specified in RFC 6733.
The Diameter proxy, when used on the AAA-2 interface may also be present in the SIP core / IMS.

7.4.3.2  SIP database  p. 44

7.4.3.2.1  General  p. 44
The SIP database contains information concerning the SIP subscriptions and corresponding identity and authentication information required by the SIP core, and such information as application service selection.
In deployment scenarios where the PLMN operator provides the SIP core, this database is provided by the HSS.
In deployment scenarios where the MC service provider provides the SIP core, the SIP database may be provided by the MC service provider.
Access to the data residing in the SIP database is restricted to the SIP core entities that are specifically serving the subscriber/user whose data are stored, i.e. registrars and registrar finders can access SIP databases only when they are part of the same trust domain for the data being provided.
The SIP database is responsible for storing the following user related information:
  • signalling plane user identities: Numbering and addressing information;
  • signalling plane security information: SIP core access control information for authentication and authorization;
  • MC service UE Location information at inter-system level: the SIP database supports the user registration, and stores inter-system location information, etc.; and
  • signalling plane subscription profile (including initial filter criteria).
The SIP database also generates signalling plane security information for mutual authentication, communication integrity check and ciphering.
Based on this information, the SIP database is also responsible to support the call control and session management entities of the SIP core.
The SIP database consists of the following functionalities:
  • support for control functions of the SIP core such as the Registrar and Registrar finder. This is needed to enable subscriber usage of the SIP core services. This functionality is independent of the access network used to access the SIP core; and
  • authentication functionality required by the SIP core to authenticate the MC service UE.
Up
7.4.3.2.2  SIP database logical functions  p. 45
The SIP database provides the following logical functions:
  1. mobility management;
    • provides the UE mobility through the SIP core.
  2. registrar assignment support;
    • provides to the registrar finder the required capabilities for MC services based on MC service provider requirements on a per-user basis, (e.g. whether a particular registrar within the PLMN operator's network (e.g. a registrar reserved for MC service use or a registrar in a secure location) or a registrar within the MC service provider network is assigned.
  3. call and/or session establishment support;
    • provides the call and/or session establishment procedures in the SIP core. For terminating traffic, it provides information on which registrar currently hosts the user.
  4. user security information generation;
    • provides generation of user authentication, integrity and ciphering data for the SIP core.
  5. signalling plane security support;
    • provides authentication procedures to access MC services by storing the generated data for authentication, integrity and ciphering at the signalling plane and by providing these data to the appropriate registrar.
  6. user identification handling;
    • provides the appropriate relations among all the identifiers uniquely determining the signalling plane identities in the SIP core e.g. IMS public identities.
  7. access authorisation; and
    • provides authorisation of the user for mobile access when requested by the registrar e.g. by checking that the user is allowed to roam to that visited network.
  8. service authorisation support.
    • provides basic authorisation for terminating call/session establishment and service invocation. The SIP database may update the registrar with filter criteria to trigger the MC service server(s).
Up

7.4.3.3  HTTP entities  p. 45

7.4.3.3.1  HTTP client  p. 45
This functional entity acts as the client for all hypertext transactions.
7.4.3.3.2  HTTP proxy  p. 45
This functional entity acts as a proxy for hypertext transactions between the HTTP client and one or more HTTP servers. The HTTP proxy terminates a TLS session on HTTP-1 with the HTTP client of the MC service UE allowing the HTTP client to establish a single TLS session for hypertext transactions with multiple HTTP servers that are reachable by the HTTP proxy.
The HTTP proxy terminates the HTTP-3 reference point that lies between different HTTP proxies. It may provide a topology hiding function from HTTP entities outside the trust domain of the MC system.
The HTTP proxy is not used as part of CSC-1 interface. CSC-1 is a direct HTTP interface between the IdM client in the UE and the IdM server as specified in TS 33.180.
According to TS 33.180, either an HTTP proxy or a direct HTTP interface is used between the key management server and the key management client in the UE for CSC-8.
The HTTP proxy shall be in the same trust domain as the HTTP clients and HTTP servers that are located within a MC service provider's network. There can be multiple instances of an HTTP proxy e.g. one per trust domain.
Up
7.4.3.3.3  HTTP server  p. 46
This functional entity acts as the HTTP server for all hypertext transactions.

7.5  Reference points  p. 46

7.5.1  General reference point principle  p. 46

The protocols on any reference point that is exposed for MC service interoperability with other SIP core or other IMS entities in other systems shall be compatible with the protocols defined for the corresponding reference point defined in TS 23.002.

7.5.2  Application plane  p. 46

7.5.2.1  General  p. 46

The reference points for the application plane of an MC service are described in the following subclauses.

7.5.2.2  Reference point CSC-1 (between the identity management client and the identity management server)  p. 46

The CSC-1 reference point, which exists between the identity management client and the identity management server, provides for the authentication of the common services core to the MC service client and MC replay client and subsequent authentication of the user to the common services core on behalf of applications within the application plane.
CSC-1 is specified in TS 33.180.

7.5.2.3  Reference point CSC-2 (between the group management client and the group management server for configuration while UE is on-network)  p. 46

The CSC-2 reference point, which exists between the group management client and the group management server, 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

7.5.2.4  Reference point CSC-3 (between the MC service server and the group management server)  p. 47

The CSC-3 reference point, which exists between the MC service server and the group management server, 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 and SIP-3 reference points for transport and routing of subscription/notification related signalling. The SIP-3 reference point is used when a MC service server and the group management server, are served by different SIP cores.
Up

7.5.2.5  Reference point CSC-4 (between the configuration management client and the configuration management server for configuration while UE is on-network)  p. 47

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 on-network.
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 non-subscription/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

7.5.2.6  Reference point CSC-5 (between the MC service server and the configuration management server)  p. 47

The CSC-5 reference point, which exists between the MC service server and the configuration management server, 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 non-subscription/notification related signalling. The CSC-5 reference point shall use SIP-2 and SIP-3 reference points for transport and routing of subscription/notification related signalling. The SIP-3 reference point is used when a MC service server and the configuration management server, are served by different SIP cores.
Up

7.5.2.7  Reference point CSC-7 (between the group management servers)  p. 47

The CSC-7 reference point, which exists between group management servers, allows group management servers to handle group management related signalling in the same security domain. 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. The SIP-3 reference point is used when a pair of group management servers, are served by different SIP cores.
Up

7.5.2.8  Reference point CSC-8 (between the key management server and the key management client)  p. 47

The CSC-8 reference point, which exists between the key management server and the key management client, 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.
CSC-8 is specified in TS 33.180.
Up

7.5.2.9  Reference point CSC-9 (between the key management server and the MC service server)  p. 48

The CSC-9 reference point, which exists between the key management server and the MC service server, 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.
CSC-9 is specified in TS 33.180.

7.5.2.10  Reference point CSC-10 (between the key management server and the group management server)  p. 48

The CSC-10 reference point, which exists between the key management server and the group management server, 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.
CSC-10 is specified in TS 33.180.
Up

7.5.2.11  Reference point CSC-11 (between the configuration management client and the configuration management server for configuration while UE is off-network)  p. 48

The CSC-11 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 off-network.
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.

7.5.2.12  Reference point CSC-12 (between the group management client and the group management server for configuration while UE is off-network)  p. 48

The CSC-12 reference point, which exists between the group management client and the group management server, 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.

7.5.2.13  Reference point CSC-13 (between the configuration management server and the MC service user database)  p. 48

The CSC-13 reference point, which exists between the MC service user database and the configuration management server, 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.

7.5.2.14  Reference point CSC-14 (between the location management client and the location management server)  p. 48

The CSC-14 reference point, which exists between the location management client and the location management server, 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

7.5.2.15  Reference point CSC-15 (between the location management server and the MC service server)  p. 49

The CSC-15 reference point, which exists between the location management server and the MC service server, 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.
Up

7.5.2.16  Reference point CSC-16 (between group management servers in different MC systems) |R15|  p. 49

The CSC-16 reference point, which exists between two group management servers in different MC systems in different security domains, is used by the group management servers to share group configuration information for MC service groups that can take part in interconnected MC service group calls.
The CSC-16 reference point uses the HTTP-1, HTTP-2 and HTTP-3 reference points for transport and routing of non-subscription/notification related signalling. The CSC-16 reference point uses SIP-2 and SIP-3 reference points for transport and routing of subscription/notification related signalling.
Up

7.5.2.17  Reference point CSC-17 (between configuration management servers in different MC systems) |R15|  p. 49

The CSC-17 reference point, which exists between configuration management servers in different MC systems in different security domains, is used by the configuration management servers to share user configuration information for MC service users who are permitted to migrate between the MC systems.
The CSC-17 reference point uses the HTTP-1, HTTP-2 and HTTP-3 reference points for transport and routing of non-subscription/notification related signalling.

7.5.2.18  Void

7.5.2.19  Reference point MCX-1 (between MC service servers) |R15|  p. 49

The MCX-1 reference point is defined between MC service servers, between MC service servers and MC gateway servers and between MC gateway servers. The MC service servers and MC gateway servers may be located within one MC system or in separate MC systems. Furthermore, the MC service servers may be of the same type or different types.
This MCX-1 reference point is used by MC service servers' coordination procedures (e.g. priority coordination). This reference point is not part of the common service core functionality.
Up

7.5.2.20  Reference point CSC-19 (between group management server and MC gateway server) |R16|  p. 50

The CSC-19 reference point, which exists between the group management server and MC gateway server is used by the group management server for subscription and notification signalling related to group configuration information that is shared between MC systems to permit interconnection of MC service group calls.
The CSC-19 reference point uses the SIP-2 and SIP-3 reference points for transport and routing of subscription/notification related signalling. The SIP-3 reference point is used when a group management server and an MC gateway server, are served by different SIP cores.
Up

7.5.2.21  Reference point CSC-20 (between configuration management server and MC gateway server) |R16|  p. 50

The CSC-20 reference point, which exists between configuration management server and MC gateway server is used by the configuration management server for subscription and notification signalling related to user configuration information that is shared between MC systems to permit migration between MC systems.
The CSC-20 reference point uses the SIP-2 and SIP-3 reference points for transport and routing of subscription/notification related signalling. The SIP-3 reference point is used when a configuration management server and an MC gateway server, are served by different SIP cores.
Up

7.5.2.22  Reference point CSC-21 (between MC gateway servers in different MC systems) |R16|  p. 50

The CSC-21 reference point, which exists between MC gateway servers in different MC systems in different security domains, is used to share subscription and notification related signalling for group configuration, user configuration management, administrative configuration management and location management to permit interconnection and migration between MC systems.
The CSC-21 reference point uses the SIP-3 reference point for transport and routing of subscription/notification related signalling.

7.5.2.23  Reference point CSC-22 (between location management servers in different MC systems) |R18|  p. 50

The CSC-22 reference point, which exists between location management servers in different MC systems, is used to share location information and non-subscription/notification related signalling for location management for interconnected MC systems.
The CSC-22 reference point uses the HTTP-1, HTTP-2 and HTTP-3 reference points for transport and routing of non-subscription/notification related signalling.

7.5.2.24  Reference point CSC-23 (between location management server and MC gateway server) |R18|  p. 50

The CSC-23 reference point, which exists between location management server and MC gateway server, is used to handle location management related signalling.
The CSC-23 reference point uses SIP-2 and SIP-3 reference points for transport and routing of subscription/notification related signalling.

7.5.2.25  Reference point CSC-24 (between the Location management server and the configuration management server) |R18|  p. 51

The CSC-24 reference point, which exists between the location management server and the configuration management server, to allow the location management server to obtain non-group configuration related information for location service (e.g. policy information). The CSC-24 reference point shall use HTTP-1 reference point and HTTP-2 reference point for transport and routing of non-subscription/notification related signalling. The CSC-24 reference point shall use SIP-2 reference point for transport and routing of subscription/notification related signalling.
Up

7.5.2.26  Reference point ACM-1 (between administrative configuration management client and administrative configuration management server) |R19|  p. 51

The ACM-1 reference point, which exists between the administrative configuration management client and the administrative configuration management server, provides exchange of administrative configuration data between interconnected MC systems while the administrative configuration management client is on-network.
The ACM-1 reference point supports:
  • retrieving the administrative management configuration client user configuration data for authorization
  • sending requests for exchanging administrative configuration data with an partner MC system
  • receiving responses from partner MC system upon requests sent
  • receiving requests of administrative configuration management client of partner MC system for exchanging administrative configuration data
  • decision taking on how to handle received requests and to reply with status response to the requestor of the partner MC system
The ACM-1 reference point shall use the HTTP-1 and HTTP-2 reference points for transport and routing of non-subscription/notification related signalling. The ACM-1 reference point shall use SIP-1 and SIP-2 reference points for transport and routing of subscription/notification related signalling.
Up

7.5.2.27  Reference point ACM-2 (between ACM server of primary MC system and ACM server of partner MC system) |R19|  p. 51

The ACM-2 reference point, which exists between the administrative configuration management servers in different security domains, is used by administrative configuration management servers to exchange administrative configuration data between interconnected MC systems.
The ACM-2 reference point uses the HTTP-2 and HTTP-3 reference points for transport and routing of non-subscription/notification related signalling. The ACM-2 reference point uses SIP-2 and SIP-3 reference points for transport and routing of subscription/notification related signalling.
Up

7.5.2.28  Reference point ACM-3 (between ACM server and MC gateway server) |R19|  p. 51

The ACM-3 reference point, which exists between administrative configuration management server and MC gateway server is used for signalling related to administrative configuration management that is shared to provide preconditions for the cooperation between interconnected MC systems.
The ACM-3 reference point uses SIP-2 and SIP-3 reference points for transport and routing of signalling. The SIP-3 reference point is used when an administrative configuration management server and a MC gateway server are served by different SIP cores.
Up

7.5.2.29  Reference point REC-1 (between the replay client and the recording server) |R19|  p. 51

The REC-1 reference point, which exists between replay client and recording server, is used by the replay client to request and receive logs/recordings of metadata and media from the replay server.
The requests from the replay clients to the recording server shall be validated with the MC access token mechanism, which is specified in TS 33.180. All other details of the REC-1 reference point are outside the scope of the present document.
Up

7.5.2.30  Reference point REC-2 (between recording server and location management server) |R19|  p. 52

The REC-2 reference point, which exists between recording server and location management server, is used by the recording server to request and receive location information from the location management server.
The REC-2 reference point uses the HTTP-1 and HTTP-2 reference points for transport and routing of non-subscription/notification related signalling. The REC-2 reference point uses SIP-2 reference point for transport and routing of subscription/notification related signalling.

7.5.2.31  Reference point REC-3 (between recording server and key management server) |R19|  p. 52

The REC-3 reference point, which exists between recording server and key management server, provides a means for the key management server to provide security related information (e.g. encryption keys) to the MC recording server.
The REC-3 reference point shall use the HTTP-1 and HTTP-2 reference points for transport and routing of security related information to the recording server.
Up

7.5.2.32  Reference point REC-4 (between recording server and configuration management server) |R19|  p. 52

The REC-4 reference point, which exists between recording server and configuration management server, is used by the recording server to request and receive information related to target users for the recordings.
The REC-4 reference point shall use HTTP-1 and HTTP-2 reference points for transport and routing of non-subscription/notification related signalling. The REC-4 reference point shall use SIP-2 reference point for transport and routing of subscription/notification related signalling.

7.5.2.33  Reference point REC-5 (between recording server and group management server) |R19|  p. 52

The REC-5 reference point, which exists between recording server and group management server, is used by the recording server to request and receive information related to target groups for the recordings.
The REC-5 reference point shall use HTTP-1 and HTTP-2 reference points for transport and routing of non-subscription/notification related signalling. The REC-5 reference point shall use SIP-2 reference point for transport and routing of subscription/notification related signalling.

7.5.2.34  Reference point REC-6 (between recording server and MC service servers) |R19|  p. 52

The REC-6 reference point, which exists between recording server and MC service servers, is used for transmitting metadata and media of the target users and target groups.
The REC-6 reference point shall use the HTTP-1 and HTTP-2 reference points for transport and routing of non-subscription/notification related signalling. The REC-6 reference point shall use SIP-2 reference point for transport and routing of subscription/notification related signalling.

7.5.2.35  Reference point REC-7 (between recording server and mass storage(s)) |R19|  p. 52

The REC-7 reference point, which exists between recording server and mass storage(s), is used for storing the logged MC service metadata as well as the recorded media of MC group communications and MC private communications. REC-7 is used also to retrieve the recorded data and media when requested by an authorized user.
The details of REC-7 are outside the scope of the present document.

7.5.3  Signalling control plane  p. 53

7.5.3.1  General  p. 53

The reference points for the SIP and HTTP signalling are described in the following subclauses.

7.5.3.2  Reference point SIP-1(between the signalling user agent and the SIP core)  p. 53

The SIP-1 reference point, which exists between the signalling user agent and the SIP core for establishing a session in support of MC service, shall use the Gm reference point as defined in TS 23.002 (with necessary enhancements to support MC service requirements and profiled to meet the minimum requirements for support of MC service). The SIP-1 reference point fulfils the requirements of the GC1 reference point specified in TS 23.468. The SIP-1 reference point is used for:
  • SIP registration;
  • authentication and security to the service layer;
  • event subscription and event notification;
  • communication of the TMGI for multicast operation;
  • overload control;
  • session management; and
  • media negotiation.
Up

7.5.3.3  Reference point SIP-2 (between the SIP core and the SIP AS)  p. 53

The SIP-2 reference point, which exists between the SIP core and the SIP AS for establishing a session in support of MC service, shall use the ISC and Ma reference points as defined in TS 23.002. The SIP-2 reference point is used for:
  • notification to the MC service server(s) of SIP registration by the MC service UE;
  • authentication and security to the service layer;
  • event subscription and event notification;
  • communication of the TMGI for multicast operation;
  • session management; and
  • media negotiation.
Up

7.5.3.4  Reference point SIP-3 (between the SIP core and SIP core)  p. 53

The SIP-3 reference point, which exists between one SIP core and another SIP core for establishing a session in support of MC service, shall use the Mm and ICi reference points as defined in TS 23.002. The SIP-3 reference point is used for:
  • event subscription and event notification;
  • session management; and
  • media negotiation.

7.5.3.5  Reference point HTTP-1 (between the HTTP client and the HTTP proxy)  p. 54

The HTTP-1 reference point exists between the HTTP client and the HTTP proxy. Between the MC service UE and the HTTP proxy, the HTTP-1 reference point shall use the Ut reference point as defined in TS 23.002 (with necessary enhancements to support specific MC service requirements). The HTTP-1 reference point is based on HTTP (which may be secured using e.g. SSL, TLS).

7.5.3.6  Reference point HTTP-2 (between the HTTP proxy and the HTTP server)  p. 54

The HTTP-2 reference point, which exists between the HTTP proxy and the HTTP server, is based on HTTP (which may be secured using e.g. SSL, TLS).

7.5.3.7  Reference point HTTP-3 (between the HTTP proxy and HTTP proxy)  p. 54

The HTTP-3 reference point, which exists between the HTTP proxy and another HTTP proxy in a different network, is based on HTTP (which may be secured using e.g. SSL, TLS).

7.5.3.8  Reference point AAA-1 (between the SIP database and the SIP core)  p. 54

The AAA-1 reference point, which exists between the SIP database and the SIP core, is used by the SIP core to retrieve signalling plane data from the SIP database. The AAA-1 reference point utilises the Cx reference point as defined in TS 23.002.
In some deployment scenarios the registrar and SIP database are located in the MC service provider's network while the registrar finder is in the PLMN operator's network and the AAA-1 reference point is an inter-network interface.
Up

7.5.3.9  Reference point AAA-2 (between the SIP core and Diameter proxy) |R15|  p. 54

The AAA-2 reference point, which exists between the SIP core / IMS and Diameter proxy for SIP registration during migration, shall use the Cx reference point as defined in TS 23.002. The AAA-2 reference point is used for:
  • authentication and security to the service layer for migration;

Up   Top   ToC