hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5.2.7 Bearer management
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5.2.7.0 General
| The MC service UE shall use the following APNs:
- an MC services APN for the SIP-1 reference point;
- an MC common core services APN for the HTTP-1 reference point; and
- an MC identity management service APN for the CSC-1 reference point.
The value of each of these APNs:
- may be the same or may differ;
- may b... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5.2.7.1 MBMS bearer management
| When operating in systems that support MBMS functionality, the MC service can provide downlink MBMS delivery of MC service media.
When operating in systems that support MBMS functionality, the MC service can provide downlink MBMS delivery of application level control messages targeted towards multiple MC clients at th... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5.2.7.2 EPS bearer considerations
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5.2.7.2.1 Considerations for the EPS bearer to the MC services PDN
| If the PDN connection established during the initial attach by the MC service UE is to an APN other than the MC services APN, then prior to user authentication, the MC service UE shall establish another PDN connection to the MC services APN. PDN connection establishment can also be caused by a SIP registration request ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5.2.7.2.2 Considerations for the EPS bearer to the MC common core services PDN and MC identity management service PDN
| The QCI value 8 (as specified in 3GPP TS 23.203 [8]) or better shall be used for the EPS bearer that transports HTTP-1 reference point messaging. If QCI value 8 is not used for HTTP-1 transport, then caution should be used that a higher priority bearer (that is used for signalling or media) is not compromised by combin... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5.2.8 External applications access to services in a MC system
| The support for external applications to access MC services is out of scope of this document.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5.2.9 Migration
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5.2.9.1 General
| Migration provides means for the MC service user to obtain MC services from a partner MC system. As the MC service client receives one or multiple user profiles for the MC service user from its primary MC system (as described in clause 10.1.4.3). Each user profile contains a list of partner MC systems that the user is ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5.2.9.2 PLMN utilisation
| Migrated MC service users should utilize the PLMN used by the partner MC system to access MC services in the partner MC system, however, utilizing the PLMN used by the primary MC system is not precluded.
NOTE 1: The above recommendation ensures the security policy of the partner MC system is not compromised, the expec... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5.2.9.3 SIP core / IMS utilisation
| Migrated MC service users should utilise the SIP core / IMS of the partner MC system.
NOTE 1: The above recommendation ensures the security policy of the partner MC system is not compromised and ensures service‑level delay requirements are consistently met (which are especially at risk when the SIP core / IMS of the p... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5.2.10 Interconnection
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5.2.10.1 General
| MC service interconnection allows a first set of MC service users who are receiving MC service from a first MC system to take part in communications with a second set of MC service users, where this second set of MC service users are receiving MC service from a second MC system, and where the second MC system is in a d... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5.2.10.2 Connectivity
| The MC service clients of the MC service users receiving MC service(s) from a first MC system and using MC service interconnection to take part in communication with MC service users in a second MC system require connectivity to only the identity management server in the second MC system.
IP connectivity is required b... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5.2.10.3 Migration
| Interconnection may be used by a migrated MC service user who is receiving service from a partner MC system to take part in communication with MC service users in the primary MC system of that migrated MC service user.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5.2.10.4 Private calls
| Where private calls take place using interconnection between MC service users who are receiving MC service in different MC systems, the MC system providing MC service to the calling MC service user will provide the controlling function for the private call.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5.2.10.5 Group calls
| Where MC service users in a partner MC system of the group home MC system of an MC service group take part in group calls in that group, the group home MC system of the MC service group will provide the controlling function for the group call.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5.2.10.6 Group configuration
| A partner MC system may apply local configuration to an MC service group configuration received from the primary MC system (i.e. the group home MC system).
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5.2.10.7 MC system topology hiding
| If an MC system requires internal network topology hiding, then this shall be achieved in the MC system by use of the following:
- proxies for signalling plane functions; and
- gateway MC service servers for application plane functions.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5.2.11 Use of priorities
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5.2.11.1 Requested priority
| The MC system may allow the MC service client to request the priority of a communication by selecting the corresponding priority level. The MC service server can enforce the selected priority level in determining the application priority for resource allocation during communication establishment.
The use of the reques... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5.2.12 Recording and replay requirements
| The MC system may support recording and replay of group and private communications (media and the metadata) and metadata of non-communication activities (e.g., affiliation/de-affiliation, group management operations).
NOTE: The recording and replay of non-session based communications and non-communication activities ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5.2.13 MC gateway UE requirements
| The MC gateway UE shall provide the capabilities to allow an MC service user utilizing a non-3GPP device, which may or may not host the MC clients, to access one or more MC services.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5.2.14 Sharing administrative configuration between interconnected MC systems requirements
| The MC system may support the sharing of administrative configurations between the primary MC system and the partner MC system.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 6 Involved business relationships
| Based on the information in subclause 5.2.1 and subclause 5.2.2, figure 6-1 shows the business relationships that exist and that are needed to support a single MC service user.
Figure 6-1: Business relationships for MC services
The MC service user belongs to a single mission critical organization based on a MC ser... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7 Functional model
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.1 General
| 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 requestin... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.2 Description of the planes
| The following planes are identified:
a) 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... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.3 Functional model description
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.3.1 On-network functional model
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.3.1.1 General
| 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 function... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.3.1.2 Functional model for an MC system
| Figure 7.3.1.2-1 shows the functional model for the application plane for an MC system.
Figure 7.3.1.2-1: Functional model for application plane for an MC system
The common services core functions and reference points shown in figure 7.3.1.2-1 are shared across each MC service. The description of the functions and ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.3.1.3 Functional model for Recording admin UE and Replay UE
| The recording admin and replay functions can be implemented also in UEs that are not MC service UE’s i.e. do not have the MCPTT / MCData / MCVideo clients.
A minimum set of MC common functions are required in such UEs. Two examples are presented in this clause, a “Recording admin UE” and a “Replay UE”.
Figure 7.... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.3.2 Off-network functional model
| Figure 7.3.2-1 shows the functional model for off-network operation.
Figure 7.3.2-1: Functional model for MC service off-network operation
For a specific MC service, the description of off-network operation is contained in the corresponding MC service TS.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4 Functional entities description
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.1 General
| Each subclause is a description of a functional entity and does not imply a physical entity.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.2 Application plane
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.2.1 General
| 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.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.2.2 Common services core
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.2.2.1 Configuration management client
| 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 ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.2.2.2 Configuration management server (CMS)
| 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 M... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.2.2.3 Group management client
| 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 s... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.2.2.4 Group management server (GMS)
| 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 belo... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.2.2.5 Identity management client
| This functional entity acts as the application user agent for MC ID transactions. It interacts with the identity management server.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.2.2.6 Identity management server (IdMS)
| 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.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.2.2.7 Key management client
| 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 3GPP TS 33.180 [25].
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.2.2.8 Key management server (KMS)
| 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 k... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.2.2.9 Location management client
| This functional entity acts as the application user agent for location management functions. It interacts with the location management server.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.2.2.10 Location management server (LMS)
| 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).
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.2.2.11 Void
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.2.2.12 Functional alias management client
| 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 an... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.2.2.13 Functional alias management server
| 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.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.2.2.14 Void
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.2.2.15 Void
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.2.3 MC service
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.2.3.1 MC service client
| 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.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.2.3.2 MC service server
| 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 3GPP TS 23.468 [18] to control multicast and unicast operations for group communications. For a specific MC service, the detailed ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.2.3.3 MC service user database
| 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.
Ea... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.2.3.4 MC gateway server
| 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 s... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.2.4 Recording and replay
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.2.4.1 Replay client
| The replay client is a functional entity that acts as the application user agent for replay services i.e. retrieving of recorded metadata and media from recording server(s) and replaying it. The replay client interacts with the recording server.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.2.4.2 Recording server
| The 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 recording server securely stores the recorded information into mass storage(s) and allows controlled access for replay/retrieve functions.
... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.2.4.3 Mass storage
| The recorded media and metadata are stored on mass storage(s). The storage solution is outside the scope of the present document.
NOTE: MC recording server and mass storage(s) can be co-located.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.2.4.4 Recording admin client
| The recording admin client is a functional entity that acts as the application user agent for recording admin services i.e. setting or modifying target users and target groups for recording. The recording admin client interacts with the configuration management server via configuration management client and with the gr... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.2.5 Administrative Configuration Management
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.2.5.1 ACM client
| 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... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.2.5.2 ACM server
| 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 r... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.3 Signalling control plane
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.3.1 SIP entities
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.3.1.1 Signalling user agent
| This functional entity acts as the SIP user agent (both client and server) for all SIP transactions.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.3.1.2 SIP AS
| 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.
NOTE: In the IM CN subsystem, this is provided by the Application Server as defined in 3GPP TS 23.002 [6].
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.3.1.3 SIP core
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.3.1.3.1 General
| 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 3GPP TS 23.228 [9], i.e. the SIP core is a 3GPP IP multimedia core network subsystem; or
2. a SIP core, which internally need not... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.3.1.3.2 Local inbound / outbound proxy
| 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; an... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.3.1.3.3 Registrar finder
| The registrar finder functional entity is responsible for:
a) 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 s... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.3.1.3.4 Registrar / application service selection
| 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 se... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.3.1.4 Diameter proxy
| This functional entity acts as a proxy agent for Diameter messaging as specified in IETF RFC 6733 [26].
The Diameter proxy, when used on the AAA-2 interface may also be present in the SIP core / IMS.
NOTE: The number of instances of the Diameter proxy is deployment specific.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.3.2 SIP database
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.3.2.1 General
| 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.... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.3.2.2 SIP database logical functions
| The SIP database provides the following logical functions:
a) mobility management;
- provides the UE mobility through the SIP core.
b) 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. wheth... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.3.3 HTTP entities
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.3.3.1 HTTP client
| This functional entity acts as the client for all hypertext transactions.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.3.3.2 HTTP proxy
| 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 ser... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.4.3.3.3 HTTP server
| This functional entity acts as the HTTP server for all hypertext transactions.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5 Reference points
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.1 General reference point principle
| 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 3GPP TS 23.002 [6].
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.2 Application plane
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.2.1 General
| The reference points for the application plane of an MC service are described in the following subclauses.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.2.2 Reference point CSC-1 (between the identity management client and the identity management server)
| 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, recording admin client and replay client and subsequent authentication of the user to the common services core on behal... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 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)
| 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 managem... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.2.4 Reference point CSC-3 (between the MC service server and the group management server)
| 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/noti... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 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)
| 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 se... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.2.6 Reference point CSC-5 (between the MC service server and the configuration management server)
| The CSC-5 reference point, which exists between the MC service server and the configuration management server, provides a means 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 fo... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.2.7 Reference point CSC-7 (between the group management servers)
| 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/notificati... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.2.8 Reference point CSC-8 (between the key management server and the key management client)
| 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... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.2.9 Reference point CSC-9 (between the key management server and the MC service server)
| 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 tra... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.2.10 Reference point CSC-10 (between the key management server and the group management server)
| 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 ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 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)
| 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 do... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 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)
| 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/notificatio... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.2.13 Reference point CSC-13 (between the configuration management server and the MC service user database)
| 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 t... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.