hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.2.14 Reference point CSC-14 (between the location management client and the location management server)
| 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 routin... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.2.15 Reference point CSC-15 (between the location management server and the MC service server)
| 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. This reference point is also utilized by the location management server to retrieve the group dynamic d... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.2.16 Reference point CSC-16 (between group management servers in different MC systems)
| 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 ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.2.17 Reference point CSC-17 (between configuration management servers in different MC systems)
| 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 referenc... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.2.18 Void
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.2.19 Reference point MCX-1 (between MC service servers)
| 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 d... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.2.20 Reference point CSC-19 (between group management server and MC gateway server)
| 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 C... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.2.21 Reference point CSC-20 (between configuration management server and MC gateway server)
| 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-... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.2.22 Reference point CSC-21 (between MC gateway servers in different MC systems)
| 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 i... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.2.23 Reference point CSC-22 (between location management servers in different MC systems)
| The CSC-22 reference point, which exists between location management servers in different MC systems, is used to share location information 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 ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.2.24 Reference point CSC-23 (between location management server and MC gateway server)
| 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 and request/response related signalling.
... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.2.25 Reference point CSC-24 (between the Location management server and the configuration management server)
| 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 poi... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.2.26 Reference point ACM-1 (between administrative configuration management client and administrative configuration management server)
| 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... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.2.27 Reference point ACM-2 (between ACM server of primary MC system and ACM server of partner MC system)
| 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 HT... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.2.28 Reference point ACM-3 (between ACM server and MC gateway server)
| 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 SI... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.2.29 Reference point REC-1 (between the replay client and the recording server)
| 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, whic... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.2.30 Void
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.2.31 Reference point REC-2 (between recording server and key management server)
| The REC-2 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-2 reference point shall use the HTTP-1 and HTTP-2 reference points for transport ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.2.32 Reference point REC-3 (between recording server and configuration management server)
| The REC-3 reference point, which exists between recording server and configuration management server, is used by the recording server to obtain user profiles (and updated user profile data) of the replay service users.
The REC-3 reference point shall use HTTP-1 and HTTP-2 reference points for transport and routing of ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.2.33 Void
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.2.34 Reference point REC-4 (between recording server and MC service servers)
| The REC-4 reference point, which exists between recording server and MC service servers, is used for transmitting metadata and media of the communication sessions of target users and target groups.
NOTE: In this version of this specification the communication sessions that may be recorded are MCPTT and MCVideo group a... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.2.35 Void
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.2.36 Reference point Le
| The Le reference point, which exists between the location management server and the 3GPP core network, is used to obtain location information of MC service UEs using the LCS. The Le reference point is defined in 3GPP TS 23.271 [29] and 3GPP TS 23.273 [41].
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.2.37 Reference point REC-5 (between recording server and group management server)
| The REC-5 reference point, which exists between recording server and group management server, is used by the recording server to obtain information related to target groups for the recordings, including the group related key material.
Editor's note: REC-5 shall be specified by SA3 in 3GPP TS 33.180 [25].
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.3 Signalling control plane
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.3.1 General
| The reference points for the SIP and HTTP signalling are described in the following subclauses.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.3.2 Reference point SIP-1(between the signalling user agent and the SIP core)
| 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 3GPP TS 23.002 [6] (with necessary enhancements to support MC service requirements and profiled to meet the minimum requirements ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.3.3 Reference point SIP-2 (between the SIP core and the SIP AS)
| 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 3GPP TS 23.002 [6]. The SIP-2 reference point is used for:
- notification to the MC service server(s) of SIP registration by the MC se... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.3.4 Reference point SIP-3 (between the SIP core and SIP core)
| 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 3GPP TS 23.002 [6]. The SIP-3 reference point is used for:
- event subscription and event notification;
- session management; a... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.3.5 Reference point HTTP-1 (between the HTTP client and the HTTP proxy)
| 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 3GPP TS 23.002 [6] (with necessary enhancements to support specific MC service requirements). The HTTP-1 reference point i... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.3.6 Reference point HTTP-2 (between the HTTP proxy and the HTTP server)
| 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).
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.3.7 Reference point HTTP-3 (between the HTTP proxy and HTTP proxy)
| 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).
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.3.8 Reference point AAA-1 (between the SIP database and the SIP core)
| 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 3GPP TS 23.002 [6].
In some deployment scenarios the registrar and SIP database are... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 7.5.3.9 Reference point AAA-2 (between the SIP core and Diameter proxy)
| 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 3GPP TS 23.002 [6]. The AAA-2 reference point is used for:
- authentication and security to the service layer for migration;
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 8 Identities
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 8.1 Application plane
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 8.1.1 Mission Critical user identity (MC ID)
| The mission critical user identity is also known as the MC ID. The MC ID is the identity that an MC service user or recording admin service user or replay service user presents to the identity management server during a user authentication transaction. In general, since identity management is a common service, it uses ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 8.1.2 MC service user identity (MC service ID)
| The MC service user identity is also known as the MC service ID. The MC service ID is a globally unique identifier within the MC service that represents the MC service user. The MC service ID identifies an MC service user. The MC service ID may also identify one or more MC service user profiles for the user at the appl... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 8.1.3 MC service group identity (MC service group ID)
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 8.1.3.1 General
| The MC service group identity is also known as the MC service group ID. The MC service group ID is a globally unique identifier within the MC service that represents a set of MC service users. The set of MC service users may belong to the same or different MC systems. The MC system for each user (within the group) is i... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 8.1.3.2 MC service group ID management (off-network operation)
| In off-network operation, an MC service group ID is used for identifying the MC service group while off-network. The MC service group ID should be resolved to the ProSe Group IP multicast address and ProSe Layer-2 Group ID for the group communication. The MC service UE is able to make one or more MC service communicati... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 8.1.4 MC system identity (MC system ID)
| The MC system ID is a globally unique identifier representing an MC system. The MC system ID shall be a URI.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 8.1.5 Functional Alias
| Functional alias provides a complementary, role-based user identification scheme which can be used by MC service users for operational purposes in the form of meaningful elements such as the function, the order number or vehicle identifications that can be used within any form of MC service communication. Functional al... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 8.1.6 MC service UE label
| The optional MC service UE label allows to distinguish between different MC service UEs in use by the same MC service ID. The MC service UE label may be added to location information reports.
The non-routable MC service UE label may include human readable information, such as an incident or MC service user specific I... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 8.1.7 Void
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 8.2 SIP signalling control plane
| The SIP signalling control plane depends upon the use of both a private user identity and one or more public user identities.
When the signalling user agent sends registration requests to the registrar / application service selection, the private user identity is used to find corresponding credentials for authenticati... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 8.3 Relationship between identities in different planes
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 8.3.1 Relationship between MC service ID and public user identity
| The following relationships exist between the MC service ID(s) and the public user identity(ies):
- An MC service ID may be mapped to one or more public user identities (e.g. multiple UEs, shared UE, multiple MC services);
- A public user identity may be mapped to one or more MC service IDs (e.g. UE-to-network relay)... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 8.3.2 Relationship between MC service group ID and public service identity
| Each MC service group ID shall be mapped to a public service identity for the MC service server where the group is defined. The MC service server manages the mapping between MC service group IDs and public service identities.
When the MC service provider and the home PLMN operator are part of the same trust domain, th... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 9 Application of functional model to deployments
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 9.1 General
| This clause describes the application of the functional model, described in clause 7, to on-network and off-network deployments. It also describes deployment scenarios that highlight some of the possible variations in the way that the functional model can be applied in different situations.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 9.2 Architecture model and deployment scenarios for on-network operations
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 9.2.1 On-network architectural model
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 9.2.1.1 On-network architectural model diagram
| Figure 9.2.1.1-1 below is the on-network architectural model for the MC system solution, where the MC system provides one or more MC services via a single PLMN.
Figure 9.2.1.1-1: On-network architectural model
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 9.2.1.2 Application services layer
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 9.2.1.2.1 Overview
| The application services layer includes application functions of one or more MC services and any required supporting functions grouped into common services core.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 9.2.1.2.2 Common services core
| Common services core is composed of the following functional entities:
- for common services, a configuration management server as described in subclause 7.4.2.2.2, a group management server as described in subclause 7.4.2.2.4, an identity management server as described in subclause 7.4.2.2.6 and a key management serv... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 9.2.1.2.3 MC services
| MC services are composed of the following functional entities:
- an MC service server as described in subclause 7.4.2.3.2 with relevant application functions of the corresponding MC service defined in the corresponding MC service TS.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 9.2.1.3 SIP core
| The SIP core provides rendezvous (contact address binding and URI resolution) and service control (application service selection) functions. It is composed of the following functional entities:
- for signalling control, a local inbound / outbound proxy as described in subclause 7.4.3.1.3.2, a registrar finder as descr... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 9.2.1.4 EPS
| The EPS provides point-to-point and point-to-multipoint bearer services with QoS.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 9.2.1.5 UE 1
| UE 1 is:
- an MC service UE in on-network mode supporting bearer services and application(s) related to one or more MC service;
- an MC service UE that acts as ProSe UE-to-network relay; or
- both of the above.
When acting as an MC service UE in on-network mode supporting bearer services and application(s) related ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 9.2.1.6 UE 2
| UE 2 is a device using ProSe UE-to-network relay, and supporting application(s) related to one or more MC services. It is composed of the following functional entities:
- for common services, a group management client as described in subclause 7.4.2.2.3, a configuration management client as described in subclause 7.4.... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 9.2.2 Deployment scenarios
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 9.2.2.1 Administration of MC service, SIP core and EPS
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 9.2.2.1.1 General
| This subclause describes five different deployment scenarios in which different administration of MC service, SIP core and EPS are described, together with the sensitivities of identities and other forms of signalling in those scenarios.
In each of these scenarios, the owner of the devices at each plane may be differe... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 9.2.2.1.2 Common administration of all planes
| In this scenario, all planes (application services layer, SIP core and EPS) are administered by the same party. This is illustrated in figure 9.2.2.1.2-1 below.
Figure 9.2.2.1.2-1: Common administration of all services by one operator
Although the identities in each plane are separate according to clause 8, there i... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 9.2.2.1.3 MC service provider separate from SIP core and EPS
| In this scenario, as illustrated in figure 9.2.2.1.3-1, the MC service provider is separate and independent from the PLMN operator, and the MC service is administered independently of the EPS and SIP core. The PLMN operator administers the EPS and the SIP core.
Figure 9.2.2.1.3-1: MC service provider administers MC ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 9.2.2.1.4 MC service provider administers SIP core, separate from EPS
| In this scenario, as illustrated in figure 9.2.2.1.4-1, the MC service provider administers the SIP core, and the MC services and SIP core are independent of the PLMN operator.
Figure 9.2.2.1.4-1: MC service provider provision of SIP core, separate domain from EPS
The MC service provider may require that all identi... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 9.2.2.1.5 SIP core partially administered by both PLMN operator and MC service provider
| In this scenario, as illustrated in figure 9.2.2.1.5-1, the SIP core is partially administered by both parties, for example when the SIP core registrar is administered by the MC service provider, but the SIP core registrar finder and proxy is administered by the PLMN operator.
Figure 9.2.2.1.5-1: MC service provider... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 9.2.2.1.6 PLMN operator administers SIP core with SIP identities administered by MC service provider
| In this scenario, the PLMN operator administers the SIP core. However, the identities used by the SIP core (IMPI and IMPU) for MC service UEs served by the MC service provider are provided from the SIP database of the MC service provider.
Figure 9.2.2.1.6-1: MC service provider provides identities to PLMN operator S... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 9.2.2.2 MC service user database, SIP database and HSS
| Figures 9.2.2.2-1 to 9.2.2.2-4 show the possible deployment scenarios of the MC service user database and SIP database, including collocation with the HSS.
The MC service user database may be combined with an HSS in some deployment scenarios (e.g. when the MC service provider and the PLMN operator are part of the same... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 9.2.2.3 Control of bearers by SIP core and MC service server
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 9.2.2.3.1 General
| This subclause describes two different scenarios in which bearers are controlled by access to Rx by either the SIP core or the MC service server.
These may provide suitable models for each of the scenarios listed in subclause 9.2.2.1. However, there is no direct correlation of any of the scenarios described in this su... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 9.2.2.3.2 Control of bearers by SIP core
| In this scenario, bearer control is performed by the SIP core alone, as shown in figure 9.2.2.3.2-1 below.
Figure 9.2.2.3.2-1: Bearer control by SIP core
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 9.2.2.3.3 Control of bearers by MC service server
| In this scenario, bearer control is performed by the MC service server alone, as shown in figure 9.2.2.3.3-1 below.
Figure 9.2.2.3.3-1: Bearer control by MC service server
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 9.3 Architecture model for off-network operations
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 9.3.1 Off-network architectural model diagram
| Figure 9.3.1-1 shows the off-network architectural model for the MC system solution for inter-UE communication, where no relay function is used.
Figure 9.3.1-1: Off-network architectural model for inter-UE communication where no relay function is used
Figure 9.3.1-2 shows the off-network architectural model for the... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 9.3.2 UE 3
| The UE 3 is a UE using ProSe and supporting application(s) related to off-network MC service, and is composed of the following functional entities:
- for MC services, MC service clients as described in subclause 7.4.2.3.1 with relevant application functions of the specific MC service defined in the corresponding MC se... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 9.3.3 UE 4
| The UE 4 represents one or more UEs with the same functionality as UE 3.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 9.3.4 Offline common services server
| The offline common services server supports configuration applications related to MC service, and is composed of the following functional entities:
- for configuration management, a configuration management server as described in subclause 7.4.2.2.2; and
- for group management, a group management server as described ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 9.4 Architecture model for roaming
| Roaming is achieved using either:
- EPC-level roaming as defined in 3GPP TS 23.401 [17]; or
- IMS-level roaming as defined in 3GPP TS 23.228 [9].
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10 Procedures and information flows
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.1 MC service configuration
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.1.1 General
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.1.1.1 MC service configuration on primary MC system
| Depicted in figure 10.1.1.1-1 is a MC service configuration time sequence of the data related to specific MC service, representing the general lifecycle of MC service UE using an MC service.
Figure 10.1.1.1-1 MC service UE configuration time sequence and associated configuration data
The MC service UE is provided ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.1.1.2 MC service configuration for migration to partner MC system
| Figure 10.1.1.2‑1 depicts a general MC service configuration time sequence of the data related to MC service, representing the general lifecycle of MC service UE which obtains MC service when migrated to a partner MC system. The MC service user can only receive MC service from one MC system at a time.
Figure 10.1.1.... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.1.2 Information flows for MC service configuration
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.1.2.1 Store group configuration request
| Table 10.1.2.1-1 describes the information flow store group configuration request from the group management client to the group management server.
Table 10.1.2.1-1: Store group configuration request
Information element
Status
Description
MC service group ID
M
MC service group ID of the group
MC service group co... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.1.2.2 Store group configuration response
| Table 10.1.2.2-1 describes the information flow store group configuration response from the group management server to the group management client.
Table 10.1.2.2-1: Store group configuration response
Information element
Status
Description
MC service group ID
M
MC service group ID of the group
Result
M
Indica... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.1.2.3 Get group configuration request
| Table 10.1.2.3-1 describes the information flow get group configuration request from the group management client to the group management server.
Table 10.1.2.3-1: Get group configuration request
Information element
Status
Description
MC service group ID
M
MC service group ID of the group
MC service group inform... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.1.2.4 Get group configuration response
| Table 10.1.2.4-1 describes the information flow get configuration response from the group management server to the group management client.
Table 10.1.2.4-1: Get group configuration response
Information element
Status
Description
MC service group ID
M
MC service group ID of the group
MC service group configurat... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.1.2.5 Subscribe group configuration request
| Table 10.1.2.5-1 describes the information flow subscribe group configuration request from the group management client to the group management server.
Table 10.1.2.5-1: Subscribe group configuration request
Information element
Status
Description
MC service group ID
M
MC service group ID of the group
MC services... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.1.2.6 Subscribe group configuration response
| Table 10.1.2.6-1 describes the information flow subscribe group configuration response from the group management server to the group management client.
Table 10.1.2.6-1: Subscribe group configuration response
Information element
Status
Description
MC service group ID
M
MC service group ID of the group
Result
M... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.1.2.7 Notify group configuration request
| Table 10.1.2.7-1 describes the information flow notify group configuration request from the group management server to the group management client.
Table 10.1.2.7-1: Notify group configuration request
Information element
Status
Description
MC service group ID
M
MC service group ID of the group
MC service group ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.1.2.8 Notify group configuration response
| Table 10.1.2.8-1 describes the information flow notify group configuration response from the group management client to the group management server.
Table 10.1.2.8-1: Notify group configuration response
Information element
Status
Description
MC service group ID
M
MC service group ID of the group
Result
M
Indi... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.1.2.9 Get functional alias configuration request
| Table 10.1.2.9-1 describes the information flow get functional alias configuration request from the functional alias management client or the MC service server to the functional alias management server.
Table 10.1.2.9-1: Get functional alias configuration request
Information element
Status
Description
Functional a... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.1.2.10 Get functional alias configuration response
| Table 10.1.2.10-1 describes the information flow get configuration response from the functional alias management server to the functional alias management client or the MC service server.
Table 10.1.2.10-1: Get functional alias configuration response
Information element
Status
Description
Functional alias
M
URI ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.1.2.11 Subscribe functional alias configuration request
| Table 10.1.2.11-1 describes the information flow subscribe functional alias configuration request from the functional alias management client or the MC service server to the functional alias management server.
Table 10.1.2.11-1: Subscribe functional alias configuration request
Information element
Status
Description... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.1.2.12 Subscribe functional alias configuration response
| Table 10.1.2.12-1 describes the information flow subscribe functional alias configuration response from the functional alias management server to the functional management client or the MC service server.
Table 10.1.2.12-1: Subscribe functional alias configuration response
Information element
Status
Description
Fu... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.1.2.13 Notify functional alias configuration request
| Table 10.1.2.13-1 describes the information flow notify functional alias configuration request from the functional alias management server to the functional alias management client or the MC service server.
Table 10.1.2.13-1: Notify functional alias configuration request
Information element
Status
Description
Func... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.