hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
701465bc5227ddf47bbba259b7283444
|
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 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.
7.5.2.25a Reference point CSC-25 (between the group management server and the configuration management server)
The CSC-25 reference point, which exists between the group management server and the configuration management server, to allow the group management server to obtain non-group configuration related information (e.g. recording admin user profiles). The CSC-25 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-25 reference point shall use SIP-2 reference point for transport and routing of subscription/notification related signalling.
|
701465bc5227ddf47bbba259b7283444
|
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 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.
|
701465bc5227ddf47bbba259b7283444
|
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 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.
|
701465bc5227ddf47bbba259b7283444
|
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 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.
|
701465bc5227ddf47bbba259b7283444
|
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, which is specified in TS 33.180 [25]. All other details of the REC-1 reference point are outside the scope of the present document.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
7.5.2.30 Void
| |
701465bc5227ddf47bbba259b7283444
|
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 and routing of security related information to the recording server.
Editor's note: REC-2 shall be specified in 3GPP TS 33.180 [25]. Whether existing CSC-8 or CSC-9 can be used as REC-2 is FFS and in SA3's scope.
|
701465bc5227ddf47bbba259b7283444
|
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 non-subscription/notification related signalling. The REC-3 reference point shall use SIP-2 and SIP-3 reference point for transport and routing of subscription/notification related signalling. The SIP-3 reference point is used when the recording server and the configuration management server are served by different SIP cores.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
7.5.2.33 Void
| |
701465bc5227ddf47bbba259b7283444
|
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 and private calls.
The REC-4 reference point shall use the SIP-2 reference point for transport and routing of signalling and communication sessions related metadata. If an MC service server and a recording server are served by different SIP cores, then the REC-4 reference point shall also use the SIP-3 reference point for transport and routing of signalling and communication sessions related metadata.
MC service server and recording server shall use Session Recording Protocol as specified in IETF RFC-7866 [40] for establishing and controlling recording sessions between MC service servers and recording server for MCPTT and MCVideo private and group communications. IETF RFC-7866 [40] specifies the use of SIP, Session Description Protocol (SDP), and RTP to establish a recording session.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
7.5.2.35 Void
| |
701465bc5227ddf47bbba259b7283444
|
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].
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
7.5.3 Signalling control plane
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
7.5.3.1 General
|
The reference points for the SIP and HTTP signalling are described in the following subclauses.
|
701465bc5227ddf47bbba259b7283444
|
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 for support of MC service). The SIP-1 reference point fulfils the requirements of the GC1 reference point specified in 3GPP TS 23.468 [18]. 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.
|
701465bc5227ddf47bbba259b7283444
|
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 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.
|
701465bc5227ddf47bbba259b7283444
|
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; and
- media negotiation.
|
701465bc5227ddf47bbba259b7283444
|
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 is based on HTTP (which may be secured using e.g. SSL, TLS).
|
701465bc5227ddf47bbba259b7283444
|
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).
|
701465bc5227ddf47bbba259b7283444
|
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).
|
701465bc5227ddf47bbba259b7283444
|
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 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.
|
701465bc5227ddf47bbba259b7283444
|
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;
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
8 Identities
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
8.1 Application plane
| |
701465bc5227ddf47bbba259b7283444
|
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 an identity which is linked to a set of credentials (e.g. biometrics, secureID, username/password) that may not necessarily be tied to a single mission critical service. The MC ID and the MC service ID or MCRec ID may be the same. The MC ID uniquely identifies the MC service user or recording admin and/or replay service user to the identity management server. The MC ID is used by the identity management server to provide the identity management client a means for mission critical service authentication.
NOTE: The specific security and authentication mechanisms required in order to use the MC user identity is specified in 3GPP TS 33.180 [25].
|
701465bc5227ddf47bbba259b7283444
|
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 application layer.
There are attributes associated with the MC service ID configured in the MC service that relate to the human user of the MC service. Typically, this information identifies the MC service user, by name or role, may also identify a user's organization or agency, and may also identify MC service user's service subscription to one or more MC services. Such attributes associated with an MC service ID can be used by the MC service server to make authorization decisions about the MC service granted to the user. For example, if the MC service user is subscribed to MCPTT service, an attribute that identifies a user's role as an incident commander could automatically be used by the MCPTT service to grant the user additional administrative rights over the creation of groups, or access to privileged talk groups.
The MC service ID shall be a URI. The MC service ID uniquely identifies an MC service user in an MC system. The MC service ID indicates the MC system where the MC service ID is defined.
When required by the MC service provider, the MC service ID is hidden from the signalling control plane.
A default or temporary MC service ID may be used where a user is not yet associated with a device. When a user would like to use one or more MC services but has not been authenticated by the identity management server, a default or temporary MC service ID and a corresponding MC service user profile may be used.
For the purposes of this document, an MC service administrator, MC service dispatcher, or MC service authorized user is an MC service user that has been granted special privileges within the context of the client function being performed (e.g. MC service client, group management client, configuration management client, key management client). For example, the MC service ID of a group management client of an MC service administrator can be authorized within the group management server to create new groups and add members to groups (i.e. administrative function), but is not authorized to dynamically create group or user regroups (i.e. operational function). Alternatively, for example, the MC service ID of a dispatcher will typically be authorized to dynamically create group and user regroups, but is not authorized to create new groups or add/delete members to groups. The MC service authorization framework is defined in TS 33.180 [25].
8.1.2a Recording admin and replay service user identity (MCRec ID)
The recording admin and replay service user identity (MCRec ID) is a globally unique identifier that identifies the recording administrator and/or replay service user in an MC system.
The MCRec ID shall be a URI. The MCRec ID indicates the MC system where that ID is defined.
The authorizations to modify other users’ or groups’ configuration tables (recording admin users) as well as the authorizations to replay recordings (replay users) are set in the Recording admin and/or replay user profile configuration data (on-network) (see clause A.11).
For the access to related servers (CMS, GMS, Recording server), the recording admin and replay services utilize the same service authorization framework as MC services. The service authorization framework is defined in TS 33.180 [25].
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
8.1.3 MC service group identity (MC service group ID)
| |
701465bc5227ddf47bbba259b7283444
|
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 identified by each user's respective MC service ID.
The MC service group ID identifies an MC service group in an MC system. It indicates the MC system where the MC service group is defined. It indicates the MC service server within the MC system where the group is defined as described in subclause 8.3.2.
The MC service group ID is used as follows:
a) For identifying a set of identities of its group members; and
b) By the MC service client to address the MC service group.
The MC service group ID shall be a URI.
When required by the MC service provider, the MC service group ID is hidden from the signalling control plane.
In 3GPP TS 23.379 [16], the MCPTT group ID is an MC service group ID.
In 3GPP TS 23.281 [12], the MCVideo group ID is an MC service group ID.
In 3GPP TS 23.282 [13], the MCData group ID is an MC service group ID.
|
701465bc5227ddf47bbba259b7283444
|
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 communications (as per the group configuration) with other member UEs whose users are of the same MC service group ID over ProSe direct communications based on ProSe Layer-2 Group ID and ProSe Group IP multicast address, and utilising IPv4 or IPv6 as indicated by policy, as described in 3GPP TS 23.303 [14].
Figure 8.1.3.2-1 illustrates how the MC service group ID, ProSe Group IP multicast address and the ProSe Layer-2 Group ID are mapped to each other. ProSe Group IP multicast address and ProSe Layer-2 Group ID are pre-configured in accordance with the MC service group ID. Thus, they are pre-defined and associated. This mapping information should be provisioned through UICC in the UE or through ProSe function as specified in 3GPP TS 23.303 [14], or be delivered from an application server. Mapping information is provisioned from group management server for online configuration, and provisioned from configuration management server for offline configuration.
NOTE: To define the retrieval mechanism of the off-network information (ProSe Group IP multicast address and ProSe Layer-2 Group ID) from ProSe function to group management server is out of scope of the present document.
Figure 8.1.3.2-1: MC service group ID management in off-network operation
|
701465bc5227ddf47bbba259b7283444
|
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.
|
701465bc5227ddf47bbba259b7283444
|
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 alias takes a form of a URI where the host part of the URI shall identify the home MC system MC service functional alias controlling server. The application addressing remains in its form and forms the foundation for the association with the corresponding functional alias. An MC service user can simultaneously activate several functional aliases but only one can be associated to a certain communication.
Each functional alias is subject to the uniqueness principle within an organization and can be shared simultaneously by several MC service users, depending on the assignment. In this case, all assigned MC service users sharing a functional alias can be included in a communication.
An MC service user uses a different set of functional aliases when migrating towards another service organization to allow the MC service user to be reachable by functional aliases within that organization.
The use of a functional alias always requires an association with the MC service ID. The MC service ID needs to be used to provide the security context for a communication.
|
701465bc5227ddf47bbba259b7283444
|
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 ID, manufacturer name, brand, model, serial number, etc.
NOTE: The MC service UE label may be provided during initial MC service UE configuration, see clause A.6.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
8.1.7 Void
| |
701465bc5227ddf47bbba259b7283444
|
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 authentication of the signalling user agent by the registrar / application service selection. This private user identity fulfils the same functions as the IMPI defined in 3GPP TS 23.228 [9].
All SIP signalling messages sent by a signalling user agent to an MC service server via a SIP core use a public user identity as the identifier to enable signalling messages to be routed through the SIP system. The public user identity fulfils the same functions as IMPU defined in 3GPP TS 23.228 [9].
NOTE 1: The relationship between the private user identity and public user identity is defined in 3GPP TS 23.228 [9].
The public user identities do not necessarily contain any application-level attributes of MC services (e.g., MCPTT ID). Any association of the public user identities with such attributes occurs at the application layer only.
When the SIP core and the MC service are part of the same trust domain, public user identities may be provided by the MC service provider or the PLMN operator. When the SIP core and the MC service are part of the different trust domains, public user identities may be provided by the PLMN operator.
NOTE 2: The MC service provider can have an agreement with the PLMN operator to manage a pool of public user identities.
The SIP core may generate public GRUUs and temporary GRUUs in order to uniquely identify MC service UEs when a user logging on from multiple devices or multiple users sharing the same device is supported per 3GPP TS 23.228 [9].
Public service identity is used as the identifier to route SIP signalling for the MC system. The public service identity fulfils the same functions as PSI defined in 3GPP TS 23.228 [9].
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
8.3 Relationship between identities in different planes
| |
701465bc5227ddf47bbba259b7283444
|
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); and
- An MC service ID may be mapped to one or more public GRUUs (e.g. a user logging on from multiple UEs, multiple users sharing the same UE).
The MC service server manages the mapping between MC service IDs and public user identities.
The MC service server manages the mapping between MC service IDs and public GRUUs.
Temporary GRUUs are mapped to public GRUUs by the SIP core.
The public user identity does not necessarily identify the MC service user at the SIP signalling control plane. When the MC service provider and the home PLMN operator are part of the same trust domain, the public user identity in the SIP signalling control plane may also identify the MC service user at the application plane.
|
701465bc5227ddf47bbba259b7283444
|
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, the public service identity in the SIP signalling control plane may also identify the MC service group ID at the application plane.
Figure 8.3.2-1: The relationship of MC service group IDs, PSIs and MC service servers
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
9 Application of functional model to deployments
| |
701465bc5227ddf47bbba259b7283444
|
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.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
9.2 Architecture model and deployment scenarios for on-network operations
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
9.2.1 On-network architectural model
| |
701465bc5227ddf47bbba259b7283444
|
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
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
9.2.1.2 Application services layer
| |
701465bc5227ddf47bbba259b7283444
|
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.
|
701465bc5227ddf47bbba259b7283444
|
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 server as described in subclause 7.4.2.2.8; and
- for signalling control, an HTTP proxy as described in subclause 7.4.3.3.2 and an HTTP server as described in subclause 7.4.3.3.3.
|
701465bc5227ddf47bbba259b7283444
|
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.
|
701465bc5227ddf47bbba259b7283444
|
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 described in subclause 7.4.3.1.3.3 and a registrar / application service selection entity as described in subclause 7.4.3.1.3.4.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
9.2.1.4 EPS
|
The EPS provides point-to-point and point-to-multipoint bearer services with QoS.
|
701465bc5227ddf47bbba259b7283444
|
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 to one or more MC services, UE 1 is composed of the same functional entities as for UE 2, as described in subclause 9.2.1.6, without the support of ProSe capabilities.
|
701465bc5227ddf47bbba259b7283444
|
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.2.2.1, an identity management client as described in subclause 7.4.2.2.5 and a key management client as described in subclause 7.4.2.2.7;
- for MC services, MC service clients as described in subclause 7.4.2.3.1 with relevant application functions of the corresponding MC service defined in the corresponding MC service TS; and
- for signalling control, a signalling user agent as described in subclause 7.4.3.1.1 and an HTTP client as described in subclause 7.4.3.3.1.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
9.2.2 Deployment scenarios
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
9.2.2.1 Administration of MC service, SIP core and EPS
| |
701465bc5227ddf47bbba259b7283444
|
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 different from the organisation that administers these devices. For example, the MC service provider may own some RAN components within the EPS even when the EPS is administered by the PLMN operator, and the MC service UE may be owned by an organisation that is independent from PLMN and MC service providers.
|
701465bc5227ddf47bbba259b7283444
|
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 is no particular sensitivity of identities and other information at the application plane, and these may be exposed to the SIP core and the EPS.
All authorisation and authentication mechanisms at each plane, i.e. the application services layer, SIP core and EPS, shall be separate, but there may be no need for any restrictions in how these are stored and managed; for example the same entity could provide services to each of the application services layer, SIP core and EPS.
|
701465bc5227ddf47bbba259b7283444
|
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 service separately from SIP core and EPS
The MC service provider may require that all application services layer identities and other sensitive information are hidden both from the SIP core and the EPS.
When required by the MC service provider, all authentication and authorisation mechanisms, including security roots, at the application services layer are hidden from and not available to the PLMN operator.
|
701465bc5227ddf47bbba259b7283444
|
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 identities and other sensitive information at the application services layer are hidden from the EPS. The MC service provider need not hide the identities and signalling at the application services layer from the SIP core. However the MC service provider may require that identities and other sensitive information between SIP core and SIP client in the MC service UE are also hidden from the EPS.
All authentication and authorisation mechanisms, including security roots, at both application services layer and at SIP signalling plane may need to be hidden from, and not available to, the PLMN operator.
The HSS-IMS and HSS-EPS in this deployment scenario is across two different administrative domains, then IMS features such as, e.g., T-ADS (3GPP TS 23.237 [10]) related to service continuity between on-network and UE-to-network relay as in annex B, NPLI (3GPP TS 23.228 [38]) related to lawful interception, and P-CSCF restoration (3GPP TS 23.380 [39]) are not supported.
|
701465bc5227ddf47bbba259b7283444
|
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 partial provision of SIP core, separate domain from EPS
The MC service provider may require that all identities and signalling at the application services layer are hidden from the EPS, and may require identities and other sensitive information to be hidden from the PLMN operator administered part of the SIP core.
All authentication and authorisation mechanisms, including security roots, at the application services layer may need to be hidden from, and not available to, the PLMN operator.
|
701465bc5227ddf47bbba259b7283444
|
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 SIP core
The MC service provider may require that all identities and signalling at the application services layer are hidden from the SIP core and EPS.
When required by the MC service provider, all authentication and authorisation mechanisms, including security roots, at the application services layer may need to be hidden from, and not available to, the PLMN operator.
The security roots (authentication keys) required for access to the signalling control plane are not available to the PLMN operator as these are held in the MC service provider's SIP database. However, derived parameters e.g. authentication vectors are provided to the SIP core to allow signalling control plane authentication to take place.
The HSS-IMS and HSS-EPS in this deployment scenario is across two different administrative domains, then IMS features such as, e.g., T-ADS (3GPP TS 23.237 [10]) related to service continuity between on-network and UE-to-network relay as in annex B, NPLI (3GPP TS 23.228 [38]) related to lawful interception, and P-CSCF restoration (3GPP TS 23.380 [39]) are not supported.
|
701465bc5227ddf47bbba259b7283444
|
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 trust domain).
The MC service user database may be a user data repository (UDR) in deployment scenarios when the UDC architecture is applied (see 3GPP TS 23.335 [15]), in that case the MC service server and the configuration management server are assumed to be application front-ends and the Ud interface is used to access data from the repository.
NOTE 1: As an implementation option, the SIP database can be located within the SIP core, in which case the AAA‑1 interface is not exposed.
NOTE 2: The MC service user database and the MC service server are always deployed in the same network i.e. both in the PLMN operator's network or both in the MC service provider's network.
Figure 9.2.2.2-1: Collocation of MC service user database and SIP database with HSS
The HSS depicted in figure 9.2.2.2-1 can be deployed either in the PLMN operator's network or the MC service provider's network.
Figure 9.2.2.2-2: Shared PLMN operator and MC service provider based deployment of MC service - SIP database collocated with HSS with separate MC service user database
The MC service user database depicted in figure 9.2.2.2-2 can be deployed in the PLMN operator's network or the MC service provider's network, and the HSS depicted in figure 9.2.2.2-2 can be deployed in the same or different network to the MC service user database i.e. PLMN operator's network or the MC service provider's network.
Figure 9.2.2.2-3: Shared PLMN operator and MC service provider based deployment of MC service - MC service user database and SIP database deployed together, with separate HSS
The MC service user database and SIP database depicted in figure 9.2.2.2-3 can be deployed in the PLMN operator's network or the MC service provider's network, and the HSS depicted in figure 9.2.2.2-3 can be deployed in the same or different network to the MC service user database i.e. PLMN operator's network or the MC service provider's network.
Figure 9.2.2.2-4: Shared PLMN operator and MC service provider based deployment of MC service - separate HSS, MC service user database and SIP database
Each of the MC service user database, SIP database and HSS depicted in figure 9.2.2.2-4 can be deployed in the same or different networks i.e. PLMN operator's network or the MC service provider's network.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
9.2.2.3 Control of bearers by SIP core and MC service server
| |
701465bc5227ddf47bbba259b7283444
|
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 subclause to each of the scenarios described in subclause 9.2.2.1.
|
701465bc5227ddf47bbba259b7283444
|
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
|
701465bc5227ddf47bbba259b7283444
|
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
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
9.3 Architecture model for off-network operations
| |
701465bc5227ddf47bbba259b7283444
|
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 MC system solution for configuration management and group management.
Figure 9.3.1-2: Off-network architectural model for configuration management and group management
NOTE 1: The offline common services server denoted in figure 9.3.1-2 could be provided by a portable device e.g. laptop.
NOTE 2: Non-EPS access can be any IP-CAN that is mutually supported by the offline common services server and the UE 3, and which provides necessary connectivity for the CSC-11 and CSC-12 reference points. It is out of scope of this specification what type of IP-CANs are supported, but could be e.g. USB, Bluetooth or WLAN.
The offline common services server could be the same entity (or set of entities) as the common services core. In this case the configuration management server shall not configure to the same user on the same UE, with parameters provisioned by offline and online configuration simultaneously. The configuration management server shall not configure to the same user on the same UE for the same parameters by using CSC-11 and CSC-4 reference points simultaneously.
The entities within this model are described in the following subclauses and a full functional model is given in subclause 7.3.2.
|
701465bc5227ddf47bbba259b7283444
|
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 service TS;
- for signalling control, a signalling user agent as described in subclause 7.4.3.1.1;
- for configuration management, a configuration management client as described in subclause 7.4.2.2.1; and
- for group management, a group management client as described in subclause 7.4.2.2.3.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
9.3.3 UE 4
|
The UE 4 represents one or more UEs with the same functionality as UE 3.
|
701465bc5227ddf47bbba259b7283444
|
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 in subclause 7.4.2.2.4.
|
701465bc5227ddf47bbba259b7283444
|
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].
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10 Procedures and information flows
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.1 MC service configuration
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.1.1 General
| |
701465bc5227ddf47bbba259b7283444
|
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 with initial UE configuration via a bootstrap procedure that provides the MC service UE's clients (e.g. MC service client, group management client, configuration management client, identity management client, key management client, functional alias management client) with critical information needed to connect to the MC system. This includes PDN connection information corresponding to the configured MC services on the MC service UE (see "EPS bearer considerations" in the 3GPP TS 23.379 [16]) and on-network server identity information for all application plane servers with which the MC service UE needs to interact. See annex A.6 for more information.
The MC service UE is provided with UE configuration, MC service user profile configuration and group configuration via online configuration. While the MC service UE is using the MC service it may receive online configuration updates. When this happens, the MC service UE shall apply these updates and use them for further operations. If the MC service user profile configuration contains multiple MC service user profiles for an authenticated MC service user, then the MC service client and MC service server set the active MC service user profile to the configured pre-selected MC service user profile after MC service authorization (which can be updated by the MC service user using the procedure specified in subclause 10.1.4.6). The active MC service user profile can be changed by the MC service user to a different MC service user profile during MC service service (see MC service TSs).
The MC service is configured with the service configuration (not shown in the figure 10.1.1.1-1) which the MC service enforces during the entire phase of MC service UE using the MC service.
Editor's note: The extent of MC services available to an MC service UE with an unauthenticated MC user or unauthorized MC service user is described as 'limited services' in 3GPP TS 33.180 and is FFS.
|
701465bc5227ddf47bbba259b7283444
|
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.2-1 MC service UE configuration sequence for migration
The MC service user and MC service UE first follow the MC service UE configuration and MC service user authorization steps described in subclause 10.1.1.1 to obtain one or more MC service user profiles from the primary MC system. Each user profile received from the primary MC system contains a list of partner MC systems to which migration is permitted using that user profile, together with the access information needed to communicate with the application plane servers of the partner MC system. See Annex A.3 for more information. The MC service user also obtains the necessary security parameters needed to authenticate and become service authorized on the partner MC system; the process for this is specified in 3GPP TS 33.180 [25]. At this point, the MC UE is configured sufficiently for the partner system so that the MC service user is capable of utilizing "limited services" as described in 3GPP TS 33.180 [25].
NOTE 1: The above steps which enable migration to take place may be carried out some time in advance of migration. The MC service user could repeatedly obtain migrated MC service, e.g. on successive days while located in the area of the partner MC system, without needing to obtain the initial configuration afresh in advance of each period of migrated MC service. The user profile from the primary MC system must be retained to provide the access information to permit this.
To initiate migration, the desired partner system from those listed in the chosen user profile is selected, and the access information provided in the user profile is used to initiate communication with the partner MC system.
NOTE 2: Selection of the relevant partner MC system could be performed as a result of a manual action by the user or automatically by an application in the MC service UE, e.g. according to the current location of the MC service UE or according to the serving PLMN of the MC service UE.
The MC service user performs MC user migration service authentication and authorization to the partner MC system as specified in 3GPP TS 33.180 [25].
The user profile or profiles for that MC service user which are to be used for service when migrated to the partner MC system are then downloaded to the configuration management client in the MC service UE by the partner MC system, and these downloaded profile or profiles are used by the MC service user during the ensuing period of MC service on the partner MC system.
NOTE 3: The user profile obtained from the primary MC system is simply used to provide access information for the partner MC system and is not otherwise used by the MC service client during migrated MC service.
Group configuration for the MC service groups listed in the user profile are then obtained by the group management client in the MC service UE. After these configuration steps, the MC service user obtains service authorization on the partner MC system.
Once service authorized, further configuration changes may be provided by the partner MC system during the period of operational MC service, in accordance with subclause 10.1.1.1. The partner MC system enforces the use of the user profiles and group configuration that have been provided by the configuration process described in this subclause.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.1.2 Information flows for MC service configuration
| |
701465bc5227ddf47bbba259b7283444
|
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 configuration data
M
MC service group configuration data
10.1.2.1a Store target group configuration request
Table 10.1.2.1a-1 describes the information flow store target group configuration request from the group management client to the group management server.
Table 10.1.2.1a-1: Store target group configuration request
Information element
Status
Description
MCRec ID
M
The MCRec ID of the requestor.
MC service group ID (see NOTE 1)
M
MC service group ID of the target group.
MC service group configuration data (see NOTE 2)
M
The contents of the MC service group configuration data to be updated.
NOTE 1: In this version of this specification, only MCPTT group ID and MCVideo group ID is supported.
NOTE 2: A Recording admin user (MCRec ID) has the authority to update only two parameters in the group configuration data - “Group is a target for recording” and “Recording server address”.
|
701465bc5227ddf47bbba259b7283444
|
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
Indicates the success or failure for the result
|
701465bc5227ddf47bbba259b7283444
|
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 information reference
M
Reference to configuration data for the MC service group
MC services requested
(see NOTE)
O
Service(s) for which group configuration is requested; one or more of MCPTT, MCVideo, MCData
NOTE: If 'MC services requested' is not present, group configuration is requested for all services defined for the MC service group
|
701465bc5227ddf47bbba259b7283444
|
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 configuration data
M
MC service group configuration data
|
701465bc5227ddf47bbba259b7283444
|
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 requested
(see NOTE)
O
Service(s) for which group configuration is requested; one or more of MCPTT, MCVideo, MCData
NOTE: If 'MC services requested' is not present, group configuration is requested for all services defined for the MC service group
10.1.2.5a Subscribe group policy request
Table 10.1.2.5a-1 describes the information flow subscribe group policy request from the MC service server to the group management server.
Table 10.1.2.5a-1: Subscribe group policy request
Information element
Status
Description
MC service group ID
M
MC service group ID of the group
MC services requested
(see NOTE)
O
Service(s) for which group configuration is requested; one or more of MCPTT, MCVideo, MCData
NOTE: The 'MC services requested' is the same service that requesting MC service server supports.
|
701465bc5227ddf47bbba259b7283444
|
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
Indicates the success or failure for the result
10.1.2.6a Subscribe group policy response
Table 10.1.2.6a-1 describes the information flow subscribe group configuration response from the group management server to the MC service server.
Table 10.1.2.6a-1: Subscribe group policy response
Information element
Status
Description
MC service group ID
M
MC service group ID of the group
Result
M
Indicates the success or failure for the result
|
701465bc5227ddf47bbba259b7283444
|
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 information reference (see NOTE)
O
Reference to information stored relating to the MC service group
Group related key material (see NOTE)
O
Key material for use with the MC service group
NOTE: At least one of these information elements shall be present.
10.1.2.7a Notify group policy request
Table 10.1.2.7a-1 describes the information flow notify group policy request from the group management server to the MC service server.
Table 10.1.2.7a-1: Notify group policy request
Information element
Status
Description
MC service group ID
M
MC service group ID of the group
MC service group configuration data
M
MC service group configuration data
|
701465bc5227ddf47bbba259b7283444
|
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
Indicates the success or failure for the result
10.1.2.8a Notify group policy response
Table 10.1.2.8a-1 describes the information flow notify group configuration response from the MC service server to the group management server.
Table 10.1.2.8a-1: Notify group policy response
Information element
Status
Description
MC service group ID
M
MC service group ID of the group
Result
M
Indicates the success or failure for the result
|
701465bc5227ddf47bbba259b7283444
|
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 alias
M
URI of the functional alias
Functional alias information reference
M
Reference to configuration data for the functional alias
MC services requested
(see NOTE)
O
Service(s) for which functional alias configuration is requested; one or more of MCPTT, MCVideo, MCData
NOTE: If 'MC services requested' is not present, functional alias configuration is requested for all services defined for the functional alias.
|
701465bc5227ddf47bbba259b7283444
|
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 of the functional alias
Functional alias configuration data
M
Functional alias configuration data
|
701465bc5227ddf47bbba259b7283444
|
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
Functional alias
M
URI of the functional alias
MC services requested
(see NOTE)
O
Service(s) for which functional alias configuration is requested; one or more of MCPTT, MCVideo, MCData
NOTE: If 'MC services requested' is not present, functional alias configuration is requested for all services defined for the functional alias.
|
701465bc5227ddf47bbba259b7283444
|
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
Functional alias
M
URI of the functional alias
Result
M
Indicates the success or failure for the result
|
701465bc5227ddf47bbba259b7283444
|
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
Functional alias
M
URI of the functional alias
Functional alias information reference
M
Reference to information stored relating to the functional alias
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.1.2.14 Notify functional alias configuration response
|
Table 10.1.2.14-1 describes the information flow notify functional alias configuration response from the functional alias management client or the MC service server to the functional alias management server.
Table 10.1.2.14-1: Notify functional alias configuration response
Information element
Status
Description
Functional alias
M
URI of the functional alias
Result
M
Indicates the success or failure for the result
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.1.2.15 Void
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.1.2.16 Void
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.1.2.17 Void
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.1.2.18 Void
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.1.2.19 Void
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.1.2.20 Void
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.1.2.21 Void
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.1.2.22 Void
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.1.2.23 Void
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.1.2.24 Void
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.1.2.25 Void
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.