hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
12.4.3 SS_IdmParameterProvisioning API
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
12.4.3.1 General
|
API description: This API enables the VAL server to provision configuration for the VAL service to the SEAL IM-S.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
12.4.3.2 Provide_Configuration operation
|
API operation name: Provide_Configuration
Description: Provisioning of VAL service configuration to IM-S.
Known Consumers: VAL server.
Inputs: See subclause 12.3.2.1
Outputs: See subclause 12.3.2.2
See subclause 12.3.4.2 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
12.4.3.3 Update_Configuration operation
|
API operation name: Update_Configuration
Description: Updating the provisioning of VAL service configuration to IM-S.
Known Consumers: VAL server.
Inputs: See subclause 12.3.2.3
Outputs: See subclause 12.3.2.4
See subclause 12.3.4.3 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
12.4.3.4 Get_Configuration operation
|
API operation name: Get_Configuration
Description: Get provisioning of VAL service configuration from IM-S.
Known Consumers: VAL server.
Inputs: See subclause 12.3.2.5
Outputs: See subclause 12.3.2.6
See subclause 12.3.4.4 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
12.4.3.5 Delete_Configuration operation
|
API operation name: Delete_Configuration
Description: Deleting the provisioning of VAL service configuration on IM-S.
Known Consumers: VAL server.
Inputs: See subclause 12.3.2.7
Outputs: See subclause 12.3.2.8
See subclause 12.3.4.5 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
13 Key management
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
13.1 General
|
The key management is a SEAL service that offers the key management related capabilities to one or more vertical applications.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
13.2 Functional model for key management
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
13.2.1 General
|
The functional model for the key management is based on the generic functional model specified in clause 6. It is organized into functional entities to describe a functional architecture which addresses the support for key management aspects for vertical applications. The on-network and off-network functional model is specified in this clause.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
13.2.2 On-network functional model description
|
Figure 13.2.2-1 illustrates the generic on-network functional model for key management.
Figure 13.2.2-1: On-network functional model for key management
The key management client communicates with the key management server over the KM-UU reference point. The key management client provides the support for key management functions to the VAL client(s) over KM‑C reference point. The VAL server(s) communicate with the key management server over the KM-S reference point.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
13.2.3 Off-network functional model description
|
Figure 13.2.3-1 illustrates the off-network functional model for key management.
Figure 13.2.3-1: Off-network functional model for key management
The key management client of the UE1 communicates with the key management client of the UE2 over the KM-PC5 reference point.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
13.2.4 Functional entities description
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
13.2.4.1 General
|
The functional entities for key management SEAL service are described in the following subclauses.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
13.2.4.2 Key management client
|
The key management functional entity acts as the application client for key management functions. It interacts with the key management server. The key management client also supports interactions with the corresponding key management client between the two UEs.
NOTE: The functionality of the key management client is specified in subclause 5.3 of 3GPP TS 33. 434 [29].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
13.2.4.3 Key management server
|
The key management server is a functional entity that stores and provides security related information (e.g. encryption keys) to the key management client, group management server and vertical application server to achieve the security goals of confidentiality and integrity of media and signalling. The key management server acts as CAPIF's API exposing function as specified in 3GPP TS 23.222 [8]. The key management server also supports interactions with the corresponding key management server in distributed SEAL deployments.
NOTE: The functionality of the key management server is specified in subclause 5.3 of 3GPP TS 33.434 [29].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
13.2.5 Reference points description
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
13.2.5.1 General
|
The reference points for the functional model for key management are described in the following subclauses.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
13.2.5.2 KM-UU
|
The interactions related to key management functions between the key management client and the key management server are supported by KM-UU reference point. This reference point utilizes Uu reference point as described in 3GPP TS 23.401 [9] and 3GPP TS 23.501 [10].
KM-UU reference point provides a means for the key management server to provide security related information (e.g. encryption keys) to the key management client. The KM-UU reference point shall use the HTTP-1 and HTTP-2 signalling control plane reference points for transport and routing of security related information to the key management client.
NOTE: KM-UU reference point is specified in subclause 5.1.1.4 of 3GPP TS 33.434 [29].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
13.2.5.3 KM-PC5
|
The interactions related to key management functions between the key management clients located in different VAL UEs are supported by KM-PC5 reference point. This reference point utilizes PC5 reference point as described in 3GPP TS 23.303 [12].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
13.2.5.4 KM-C
|
The interactions related to key management functions between the VAL client(s) and the key management client within a VAL UE are supported by KM-C reference point.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
13.2.5.5 KM-S
|
The interactions related to key management functions between the VAL server(s) and the key management server are supported by KM-S reference point. This reference point is an instance of CAPIF-2 reference point as specified in 3GPP TS 23.222 [8].
KM-S reference point provides a means for the key management server to provide security related information (e.g. encryption keys) to the VAL server. The KM-S reference point shall use the HTTP-1 and HTTP-2 signalling control plane reference points for transport and routing of security related information to the VAL server.
NOTE: KM-S is specified in subclause 5.1.1.4 of 3GPP TS 33.434 [29].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
13.2.5.6 KM-E
|
The interactions related to key management functions between the key management servers in a distributed deployment are supported by KM-E reference point.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
13.2.5.7 SEAL-X1
|
NOTE: SEAL-X1 reference point between the key management server and the group management server is described in subclause 6.5.9.2.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
13.3 Procedures and information flows for key management
|
NOTE: The procedure for key management is specified in subclause 5.3 of 3GPP TS 33.434 [29].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
13.3.1 Information flows
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
13.3.1.1 void
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
13.3.1.2 void
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
13.3.2 VAL server provisioning for key management service
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
13.3.2.1 General
|
The high level procedure for VAL server to provision required information to SEAL key management server in order to provide the format and content of a key management record is described in clause 5.8 of 3GPP TS 33.434 [29].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
13.3.2.2 void
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
13.4 SEAL APIs for key management
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
13.4.1 General
|
Table 13.4.1-1 illustrates the SEAL APIs for key management.
Table 13.4.1-1: List of SEAL APIs for key management
API Name
API Operations
Known Consumer(s)
Communication Type
SS_KmParameterProvisioning
Provide_Configuration
VAL server
Request /Response
The other SEAL APIs for Key Management are specified in subclauses 5.7.1 and 7.6.1 of 3GPP TS 29.549 [30].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
13.4.2 Void
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
13.4.2.1 Void
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
13.4.2.2 Void
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
13.4.3 void
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14 Network resource management
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.1 General
|
The network resource management is a SEAL service that offers the network resource management (e.g. unicast and multicast network resources) and monitoring related capabilities to one or more vertical applications.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.2 Functional model for network resource management
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.2.1 General
|
The functional model for the network resource management is based on the generic functional model specified in clause 6. It is organized into functional entities to describe a functional architecture which addresses the support for network resource management aspects for vertical applications. The on-network and off-network functional model is specified in this clause.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.2.2 On-network functional model description
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.2.2.1 Generic on-network functional model for network resource management
|
Figure 14.2.2-1 illustrates the generic on-network functional model for network resource management.
Figure 14.2.2.1-1: On-network functional model for network resource management
The network resource management client communicates with the network resource management server over the NRM-UU reference point. The network resource management client provides the support for network resource management functions to the VAL client(s) over NRM‑C reference point. The VAL server(s) communicate with the network resource management server over the NRM-S reference point.
The network resource management server obtains and controls the multicast/broadcast resource from the underlaying 3GPP network system by communicating with the BM-SC via MB2-C and xMB-C reference points towards LTE eMBMS and with the 5G MBS control plane functions via Nmb13, Nmb10 or N33 towards the 5GS. The network resource management server communicates with the PCRF via Rx reference point or communicates with the PCF via N5 reference point to control the unicast resources from the underlying 3GPP network system. The network resource management server communicates with the SCEF via T8 reference point or communicates with the NEF via N33 reference point to perform event monitoring procedures from the underlying 3GPP network system. The network resource management server interacts with NEF via N33 to obtain QoS monitoring information from the 5GS.
Figure 14.2.2.1-2 exhibits the service-based interfaces for providing and consuming group management services. The network resource management server could provide service to VAL server and network resource management client through interface Snrm.
Figure 14.2.2.1-2: Architecture for network resource management – Service based representation
Figure 14.2.2.1-3 illustrates the service-based representation for utilization of the 5GS network services based on the 5GS SBA specified in 3GPP TS 23.501 [10].
Figure 14.2.2.1-3: Architecture for network resource management utilizing the 5GS network services based on the 5GS SBA – Service based representation
Figure 14.2.2.1-4 illustrates the service-based representation for utilization of the Core Network northbound APIs via CAPIF.
Figure 14.2.2.1-4: Utilization of Core Network Northbound APIs via CAPIF – service based representation
The Network resource management server and VAL server act as authorized API invoker to consume services from the Core Network northbound API entities like NEF which act as API Exposing Function as specified in 3GPP TS 23.222 [6].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.2.2.2 On-network functional model for network resource management for TSN
|
The architecture for integration of the 5G with TSN [36] is depicted in Figure 14.2.2.2-1. The SEAL Network Resource Management (NRM) server acts as a TSN AF (defined in [10] in clause 5.28.1). TSN CNC (defined in [35]) via the NRM-S reference point configures the TSN flows in the 5GS. In this case the NRM-S supports the IEEE 802.1Qcc management protocol. As a TSN AF the SEAL NRM server interacts with the 5GS PCF over the N5 reference point to configure the 5G QoS and TSCAI parameters in the 5GS.
Figure 14.2.2.2-1: On-network functional model for network resource management for TSN
NOTE: Whether DS-TT and UE are combined or are separate is up to implementation.
Acting as the TSN AF the NRM server collects 5GS TSN Bridge information by interaction with the 5GS via the N5 reference point, as described in in TS 23.502 [11] Annex F.1.
NRM server triggers via N5 the AF request procedure as described in 3GPP TS 23.502 [11] Annex F.2.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.2.2.3 On-network functional model for network resource management for 5G TSC
|
5G TSC refers to time sensitive communication service offered within the 5G system (i.e. without integration with a TSN system) by the 5GS for the UEs connected to the 5GS. The architecture for the 5G TSC is depicted in Figure 14.2.2.3-1. The SEAL NRM server acts as an AF towards the 5G Core Network and performs coordination of QoS flows to fulfill the end-to-end QoS requirements for the UEs involved in the TSC communication. It combines the roles of TSCTSF and TSC CNC (similar to the TSN CNC in the TSN integration case), which means that it controls the allocation of resources of TSC communication within the boundaries of the 5G domain.
Upon request from a VAL server via the NRM-S reference point it configures the TSC end-to-end QoS flows in the 5GS. In line with other SEAL service enablers the SEAL NRM server provides a RESTful interface on the NRM-S reference point. As a TSCTSF the SEAL NRM server interacts with the 5GS PCF over the N84 reference point to configure the 5G QoS and TSCAI parameters in the 5GS.
Figure 14.2.2.3-1: On-network functional model for network resource management for 5G TSC
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.2.3 Off-network functional model description
|
Figure 14.2.3-1 illustrates the off-network functional model for network resource management.
Figure 14.2.3-1: Off-network functional model for network resource management
The network resource management client of the UE1 communicates with the network resource management client of the UE2 over the NRM‑PC5 reference point.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.2.4 Functional entities description
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.2.4.1 General
|
The functional entities for network resource management SEAL service are described in the following subclauses.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.2.4.2 Network resource management client
|
The network resource management client functional entity acts as the application client for the management of network resources. The network resource management client interacts with the network resource management server.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.2.4.3 Network resource management server
|
The network resource management server functional entity provides for management of 3GPP system network resources (e.g. unicast, multicast) and monitoring events to support the VAL applications. The network resource management server acts as CAPIF's API exposing function as specified in 3GPP TS 23.222 [8]. The network resource management server also supports interactions with the corresponding network resource management server in distributed SEAL deployments. The NRM server's role may be assumed by the VAL server in some deployments, in which case, the VAL server performs the procedures for network resource management of the NRM server.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.2.5 Reference points description
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.2.5.1 General
|
The reference points for the functional model for network resource management are described in the following subclauses.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.2.5.2 NRM-UU
|
The interactions related to network resource management functions between the network resource management client and the network resource management server are supported by NRM-UU reference point. This reference point utilizes Uu reference point as described in 3GPP TS 23.401 [9] and 3GPP TS 23.501 [10].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.2.5.3 NRM-PC5
|
The interactions related to network resource management functions between the network resource management clients located in different VAL UEs are supported by the NRM-PC5 reference point. This reference point utilizes PC5 reference point as described in 3GPP TS 23.303 [12].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.2.5.4 NRM-C
|
The interactions related to network resource management functions between the VAL client(s) and the network resource management client within a VAL UE are supported by the NRM-C reference point.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.2.5.5 NRM-S
|
The interactions related to network resource management functions between the VAL server(s) and the network resource management server are supported by the NRM-S reference point. This reference point is an instance of CAPIF-2 reference point as specified in 3GPP TS 23.222 [8].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.2.5.6 NRM-E
|
The interactions related to network resource management functions between the network resource management servers in a distributed deployment are supported by NRM-E reference point.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.2.5.7 MB2-C
|
The reference point MB2-C supports the control plane interactions between the network resource management server and the BM-SC and is specified in 3GPP TS 29.468 [22].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.2.5.8 xMB-C
|
The reference point xMB-C supports the control plane interactions between the network resource management server and the BM-SC and is specified in 3GPP TS 26.348 [20].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.2.5.9 Rx
|
The reference point Rx supports the interactions between the network resource management server and the PCRF and is specified in 3GPP TS 29.214 [21].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.2.5.10 N5
|
The reference point N5 supports the interactions between the network resource management server and the PCF and is specified in 3GPP TS 23.501 [10].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.2.5.11 N33
|
The reference point N33 supports the interactions between the network resource management server and the NEF and is specified in 3GPP TS 23.501 [10].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.2.5.12 Nmb13
|
The reference point Nmb13 supports the interactions between the network resource management server and the MB-SMF is specified in 3GPP TS 23.247 [39].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.2.5.13 Nmb10
|
The reference point Nmb10 supports the interactions between the network resource management server and the MBSF is specified in 3GPP TS 23.247 [39].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.2.5.14 N6mb
|
The reference point N6mb supports the interactions between the VAL server and the MB-UPF is specified in 3GPP TS 23.247 [39].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.2.5.15 Nmb8
|
The reference point Nmb8 supports the interactions between the VAL server and the MBSTF is specified in 3GPP TS 23.247 [39].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.2.5.16 N6
|
The reference point N6 supports the interactions between the VAL server and the UPF is specified in 3GPP TS 23.501 [10].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3 Procedures and information flows for network resource management
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.1 General
|
The procedures related to the network resource management are described in the following subclauses.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2 Information flows
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.1 Network resource adaptation request
|
Table 14.3.2.1-1 describes the information flow network resource adaptation request from the VAL/SEALDD server to the NRM server.
Table 14.3.2.1-1: Network resource adaptation request
Information element
Status
Description
Requester Identity
M
The identity of the VAL server performing the request.
List of VAL UE IDs
O
(see NOTE)
List consisting of one or more VAL UE IDs for whom the network resource adaptation occurs.
VAL group ID
O
(see NOTE)
The VAL group ID for whom the network resource adaptation occurs.
Resource adaptation requirement
M
The resource adaptation requirement corresponds to the VAL service QoS requirements as applied for a UE or group of UEs (E.g. bandwidth, resource).
BDT Reference ID
O
Indicates the Background data transfer Reference ID provided by the 3GPP network
NOTE: Either of the information elements should be present.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.2 Network resource adaptation response
|
Table 14.3.2.2-1 describes the information flow network resource adaptation response from the NRM server to the VAL server.
Table 14.3.2.2-1: Network resource adaptation response
Information element
Status
Description
Result
M
Result includes success or failure of the network resource adaptation with the underlying network. The response can also include an updated value for some of the parameters included in the network resource adaptation request (e.g. negotiation of resource offering)
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.3 MBMS bearer announcement
|
Table 14.3.2.3-1 describes the information flow MBMS bearer announcement from the NRM server to the NRM client.
Table 14.3.2.3-1: MBMS bearer announcement
Information element
Status
Description
TMGI
M
TMGI information
Alternative TMGI
O
A list of additional alternative TMGI may be included and used in roaming scenarios.
QCI
O
QCI information used by the ProSe UE-Network Relay to determine the ProSe Per-Packet Priority value to be applied for the multicast packets relayed to Remote UE over PC5
List of service area identifier
M
A list of service area identifier for the applicable MBMS broadcast area.
Frequency
O
Identification of frequency if multi carrier support is provided
SDP information
M
SDP with media and application control information applicable to groups that can use this bearer (e.g. codec, protocol id, FEC information)
Monitoring state
O
The monitoring state is used to control if the client is actively monitoring the MBMS bearer quality or not.
Announcement acknowledgment
O
Indicate if the NRM server requires an acknowledgement of the MBMS bearer announcement.
Unicast status
O
An indication that the listening status of the unicast bearer is requested.
ROHC information
O
Indicate the usage of ROHC and provide the parameters of the ROHC channel to signal to the ROHC decoder.
NOTE: When MBMS bearer announcement is done on a MBMS bearer all attributes above are optional except the TMGI.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.4 MBMS listening status report
|
Table 14.3.2.4-1 describes the information flow for the MBMS listening status report from NRM client to NRM server.
Table 14.3.2.4-1: MBMS listening status report
Information element
Status
Description
VAL user ID or VAL UE ID
M
The identity of the VAL user or VAL UE who wants to report the MBMS listening status.
TMGI(s)
M
TMGI(s) information.
MBMS listening status(s)
M
The MBMS listening status per TMGI.
MBMS reception quality level
O
The reception quality level per TMGI (see NOTE)
Unicast listening status
O
The unicast listening status.
NOTE: The set of quality levels helps service continuity in MBMS scenarios. A reception quality level may help to make an efficient switching decision to another bearer. How these levels are used is implementation specific.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.5 MBMS suspension reporting instruction
|
Table 14.3.2.5-1 describes the information flow for the MBMS suspension reporting instruction from NRM server to NRM client in a unicast bearer for MBMS suspension reporting.
Table 14.3.2.5-1: MBMS suspension reporting instruction (unicast)
Information element
Status
Description
VAL user ID or VAL UE ID
M
The identity of the VAL user or VAL UE.
Suspension reporting
M
Enables or disable the suspension reporting for a specific NRM client
Table 14.3.2.5-2 describes the information flow for the MBMS suspension reporting instruction from NRM server to NRM client in a multicast bearer for MBMS suspension reporting.
Table 14.3.2.5-2: MBMS suspension reporting instruction (multicast)
Information element
Status
Description
Suspension reporting client subset
M
Contains a uniquely defined subset of NRM clients that shall report MBMS suspension
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.6 Resource request
|
Table 14.3.2.6-1 describes the information flow for the resource request from VAL server to NRM server for unicast resources.
Table 14.3.2.6-1: Resource request
Information element
Status
Description
Requester Identity
M
The identity of the VAL server performing the request.
VAL user ID or VAL UE ID
M
The identity of the VAL user or VAL UE.
VAL service requirement information (see NOTE)
O
VAL service requirements for unicast resource (e.g. VAL service ID, Bitrate)
NOTE: When this information element is not included, the NRM server considers default VAL service requirement for the unicast resources.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.7 Resource response
|
Table 14.3.2.7-1 describes the information flow for the resource response from NRM server to VAL server for unicast resources.
Table 14.3.2.6-1: Resource response
Information element
Status
Description
Result
M
The result indicates success or failure of the resource request operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.8 Resource modification request
|
Table 14.3.2.8-1 describes the information flow for the resource modification request from VAL server to NRM server for unicast resources.
Table 14.3.2.8-1: Resource modification request
Information element
Status
Description
Requester Identity
M
The identity of the VAL server performing the request.
VAL user ID or VAL UE ID
M
The identity of the VAL user or VAL UE.
VAL service requirement information
M
VAL service requirements for unicast resource (e.g. VAL sevice ID, Bitrate)
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.9 Resource modification response
|
Table 14.3.2.9-1 describes the information flow for the resource modification response from NRM server to VAL server for unicast resources.
Table 14.3.2.9-1: Resource modification response
Information element
Status
Description
Result
M
The result indicates success or failure of the resource modification operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.10 MBMS bearers request
|
Table 14.3.2.10-1 describes the information flow for the MBMS bearers request from VAL server to NRM server.
Table 14.3.2.10-1: MBMS bearers request
Information element
Status
Description
Requester Identity
M
The identity of the VAL server performing the request.
VAL group ID
M
The identity of the group that the MBMS bearer is requested for.
Service announcement mode
M
Indicates whether the request is sent by NRM server or by the VAL server
QoS
M
Indicates the requested QoS for the bearer
Broadcast area
O
Indicate the area where the MBMS bearer is requested for
Endpoint information
M
Information of the endpoint of the VAL server to which the user plane notifications have to be sent.
Local MBMS information (see NOTE)
O
> MB2-U information
O
IP address, UDP port number of the MB2-U interface
> xMB-U information
O
IP address, UDP port number of the xMB-U interface
> M1 interface information
O
M1 interface information for local MBMS
Local MBMS activation indication (see NOTE)
O
Indicates whether to request the NRM server to use Local MBMS information.
NOTE: The VAL server may provide either the Local MBMS information or the Local MBMS activation indication. This IE is present when the local MBMS is required for VAL services like V2X service.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.11 MBMS bearers response
|
Table 14.3.2.11-1 describes the information flow for the MBMS bearers response from NRM server to VAL server.
Table 14.3.2.11-1: MBMS bearers response
Information element
Status
Description
Result
M
The result indicates success or failure of the MBMS bearers request operation.
TMGI
O
(see NOTE 1)
TMGI information.
User plane address
M
(see NOTE 2)
BM-SC user plane IP address and port
Service description
O
(see NOTE 2)
Indicates MBMS bearer related configuration information as defined in 3GPP TS 26.346 [28] (e.g. radio frequency and MBMS Service Area Identities)
NOTE 1: TMGI may not be required if the service announcement mode indicates that the request is sent by the NRM server.
NOTE 2: If the Result Information element indicates failure then the values of the other information elements have no meaning.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.12 User plane delivery mode
|
Table 14.3.2.12-1 describes the information flow for the user plane delivery mode from NRM server to VAL server.
Table 14.3.2.12-1: User plane delivery mode
Information element
Status
Description
Delivery mode
M
Indicates whether to deliver the user data to the UE(s) via unicast mode or multicast mode
MBMS media stream identifier
M
Indicates the MBMS media stream to be used to deliver the media currently over unicast, or the MBMS media stream currently being used.
Unicast media stream identifier(s)
M
Indicates the unicast media stream to be used to deliver the media currently over multicast, or the unicast to be stopped and switched to multicast.
MBS service area
O
Indicates the MBS service area where the delivery mode is applied.
List of VAL UE IDs
O
(NOTE)
The list of UEs where the unicast mode is applied.
NOTE: This information element is only applicable when the delivery mode is unicast mode.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.13 end-to-end QoS management request
|
Table 14.3.2.13-1 describes the information flow end-to-end QoS management request from the NRM client to the NRM server.
Table 14.3.2.13-1: end-to-end QoS management request
Information element
Status
Description
List of VAL UEs or VAL Group ID
M
List of VAL UEs or the group of VAL UEs for whom the end-to-end QoS management occurs
>VAL UE/user ID
M
Identity of the VAL UE
> IP address
O
IP address of the VAL UE
VAL service ID
O
The VAL service identity for whom the end-to-end QoS management occurs.
End-to-end QoS requirements
O
The application QoS requirements / KPIs (latency, error rate, ..) for the end-to-end session.
This may optionally include information which will support the NRM server to identify the per session QoS requirements (e.g. a flag indicating the use of HD video for assisting the end-to-end session, a video resolution/encoding required for the HD video).
Service area
O
The area where the QoS management request applies. This can be geographical area, or topological area.
Time validity
O
The time of validity of the requirement.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.14 end-to-end QoS management response
|
Table 14.3.2.14-1 describes the information flow end-to-end QoS management response from the NRM server to the NRM client.
Table 14.3.2.14-1: end-to-end QoS management response
Information element
Status
Description
Result
M
The positive or negative result of the end-to-end QoS management request.
QoS report configuration
O
The configuration of the NRM client's report triggering by NRM server (e.g. setting thresholds for reporting a QoS downgrade / notifications based on channel loss great than threshold value)
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.15 QoS downgrade indication
|
Table 14.3.2.15-1 describes the information flow QoS downgrade indication from the NRM client to the NRM server.
Table 14.3.2.15-1: QoS downgrade indication
Information element
Status
Description
VAL UE ID
M
The identifier of the VAL UE which indicates the QoS downgrade.
QoS downgrade report
M
The report including the expected or actual QoS / QoE parameters which were downgraded (i.e. latency, throughput, reliability, jitter). This report may be configured by the end-to-end QoS management response message.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.16 Application QoS change notification
|
Table 14.3.2.16-1 describes the information flow Application QoS change notification from the NRM server to the NRM clients (which are involved at the end-to-end session).
Table 14.3.2.16 -1: Application QoS change notification
Information element
Status
Description
NRM server ID
M
The identifier of the NRM server which provides the notification.
Requested QoS parameters
M
The updated requested QoS parameters for the end-to-end session (NRM server to source VAL UE or NRM server to target VAL UE), based on the QoS change on one or both links involved in the network-assisted end-to-end communication.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.17 Monitoring Events Subscription Request
|
Table 14.3.2.17-1 describes the information flow from the VAL server to the NRM server for monitoring events subscription request.
Table 14.3.2.17-1: Monitoring Events Subscription request
Information element
Status
Description
Identities list
O
(see NOTE 1)
List of VAL users or VAL UEs whose events monitoring is requested.
VAL group ID
O
(see NOTE 1)
VAL group ID of the VAL UE group of target UEs.
VAL service ID
O
VAL service ID.
Monitoring profile ID
O
(see NOTE 2)
The monitoring profile ID, which identifies a list of monitoring and/or analytics events.
Validity conditions
O
The temporal and/or spatial conditions applied for the events to be considered as valid.
Event Details
O
(see NOTE 2)
List of monitoring and/or analytics events that the VAL server is interested in.
NOTE 1: For identifying the target UE(s), either a list of VAL users/UEs or a group of VAL UEs shall be provided.
NOTE 2: Either Event Details or Monitoring profile ID is present.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.18 Monitoring Events Subscription Response
|
Table 14.3.2.18-1 describes the information flow from the NRM server to the VAL server for Monitoring Events Subscription response.
Table 14.3.2.18-1: Monitoring Events Subscription response
Information element
Status
Description
Subscription status
M
It indicates the subscription result
Monitoring profile ID
O
It indicates the monitoring profile identifier. It is present when Subscription status is success and Event Details are provided in the Monitoring Events Subscription request.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.19 Monitoring Events Notification message
|
Table 14.3.2.19-1 describes the information flow from the NRM server to the VAL server on notification of monitoring events.
Table 14.3.2.19-1: Monitoring Events Notification
Information element
Status
Description
EventDetails
List of events related to VAL UE(s).
> identity
M
VAL UE for which the events are related to.
> events
M
List of Monitoring and Analytics events related to the VAL UE.
Timestamp
O
The timestamp for the monitoring and analytics events
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.20 Unicast QoS monitoring subscription request
|
Table 14.3.2.20-1 describes the information flow from the VAL server to the network resource management server for unicast QoS monitoring subscription request.
Table 14.3.2.20-1: Unicast QoS monitoring subscription request
Information element
Status
Description
Requester Identity
M
The identity of the VAL server performing the request.
List of VAL UE IDs
O
(see NOTE 1 NOTE 4)
List of VAL UEs whose QoS monitoring data is requested.
VAL group ID
O
(see NOTE 1, NOTE 4)
The group ID used for the VAL group for which QoS monitoring data is requested.
List of VAL stream IDs
O
(see NOTE 1, NOTE 4)
List of VAL streams for which QoS monitoring data is requested.
VAL service ID
O
Represents the VAL service ID.
Monitoring profile ID
O
(see NOTE 5)
Represents the monitoring profile ID.
Monitoring profile
O
(see NOTE 5)
Represents the monitoring profile.
> Measurement requirements
O
It describes the requirements on the QoS measurements.
>> type of data
M
At least one of the following measurement index shall be provided.
>>> packet delay
O
UL/DL/RT packet delay.
For VAL stream, the packet delay means measurement from a source UE to a target UE.
>>> packet loss rate
O
Average packet loss rate.
>>> data rate
O
Average data rate and/or maximum data rate.
>>> traffic volume
O
Average traffic volume for UL and/or DL
>> measurement time period
O
The measurement time period indicates a current time period. If absent, current time and 5 minutes duration are used as default setting.
>> aggregation granularity window
O
Indicates how long the QoS monitoring is performed to compute the average value and gather the maximum value. If absent, 1 minute is used as default setting.
> Reporting requirements
O
It describes the requirements for QoS monitoring reporting.
>> Frequency of reporting
O
It indicates the requested frequency of reporting. The reporting frequency may be periodic or event triggered (i.e. threshold reached). If absent in the request, default event triggered reporting is used.
>> Reporting threshold
O
If the Frequency of reporting is event triggered (threshold reached), the reporting threshold corresponding to the measurement index shall be provided.
>> Threshold reaching direction
O
It indicates the reaching direction (i.e. ascending, descending or crossed) for the reporting threshold. It shall be provided if reporting threshold is present.
>> Reporting periodicity
O
If the Frequency of reporting is periodic, the reporting periodicity shall be provided.
> Termination of reporting
O
(see NOTE 6)
It indicates when the reporting of QoS monitoring shall stop. It can be event triggered (i.e. either number of reports reached or threshold reached) or when reporting duration expires or when explicit termination is requested. If absent in the request, it defaults to explicit termination. Once the termination condition is met, the monitoring subscription ceases to exist.
> Max number of reports
O
(NOTE 3, NOTE 6)
It indicates the maximum number of reports, it shall be provided when Termination of reporting is set to event triggered (number of reports reached).
> Termination threshold
O
(see NOTE 2, NOTE 3, NOTE 6)
It indicates the reporting termination threshold corresponding to the measurement index. Each measurement index has only one termination threshold.
> Termination condition for termination threshold
O
(see NOTE 2, NOTE 6)
It indicates threshold-based termination condition (e.g. all reached or any of them reached) if multiple measurement indexes are provided.
> Reporting duration
O
(NOTE 3, NOTE 6)
It indicates the reporting duration, it shall be provided when Termination of reporting is set to duration expiration.
NOTE 1: Only one of these information elements shall be present.
NOTE 2: It shall be provided when Termination of reporting is set to event triggered (threshold reached).
NOTE 3: If provided, only one of these information elements shall be present.
NOTE 4: When used by the Update_Unicast_QoS_Monitoring_Subscription operation, the same information element with identical content shall be present as in the associated Subscribe_Unicast_QoS_Monitoring operation.
NOTE 5: Only one of these information elements shall be present.
NOTE 6: When used by the Update_Unicast_QoS_Monitoring_Subscription operation, this IE may be used by the VAL server to modify the proposed by NRM server subscription termination conditions.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.21 Unicast QoS monitoring subscription response
|
Table 14.3.2.21-1 describes the information flow from the network resource management server to the VAL server for unicast QoS montoring subscription response.
Table 14.3.2.21-1: Unicast QoS monitoring subscription response
Information element
Status
Description
Subscription status
M
It indicates the subscription result
Monitoring profile ID
O
Represents the identifier of the stored monitoring profile. This IE may be present if the subscription status is success.
Termination of reporting
O
It indicates when the reporting of QoS monitoring will stop. This IE may be present if the subscription status is success.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.22 Unicast QoS monitoring notification
|
Table 14.3.2.22-1 describes the information flow for unicast QoS monitoring notification from the network resource management server to the VAL server.
Table 14.3.2.22-1: Notify unicast QoS monitoring event
Information element
Status
Description
List of VAL UE IDs
O
(see NOTE 1)
List of VAL UEs whose QoS monitoring data is provided. This list is either the list provided in the subscription request or a subset of that list. It can contain a single UE.
VAL group ID
O
(see NOTE 1)
The group ID used for the VAL group for which QoS monitoring data is provided. This group ID shall be the same VAL group ID as the VAL group ID provided in the subscription request.
List of VAL stream IDs
O
(see NOTE 1)
List of VAL stream IDs whose QoS monitoring data is provided. This list is either the list provided in the subscription request or a subset of that list. It can contain a single stream ID.
QoS monitoring data
O
(see NOTE 2)
QoS monitoring data is an aggregate of QoS measurements data obtained from the 5GS.
Termination cause
O
(see NOTE 2)
Indicates that the subscription is terminated with the termination cause.
Monitoring profile ID
O
Represents the monitoring profile identifier whose reporting requirements triggered notification.
NOTE 1: Only one of these information elements shall be present.
NOTE 2: At least one of these information elements shall be present.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.23 TSC stream availability discovery request
|
Table 14.3.2.23-1 describes the information flow TSC stream availability discovery request from the VAL server to the NRM server.
Table 14.3.2.23-1: TSC stream availability discovery request
Information element
Status
Description
Requester Identity
M
The identity of the VAL server performing the request.
Stream specification
M
Stream specification includes MAC addresses of the source and destination DS-TT ports (e.g. as defined in IEEE 802.1CB [37]).
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.24 TSC stream availability discovery response
|
Table 14.3.2.24-1 describes the information flow TSC stream availability discovery response from the NRM server to the VAL server.
Table 14.3.2.24-1: TSC stream availability discovery response
Information element
Status
Description
Result
M
Result includes success or failure of the TSC stream availability discovery with the underlying network.
Stream specification
M
Stream specification includes MAC addresses of the source and destination DS-TT ports (e.g. as defined in IEEE 802.1CB [37]).
List of traffic specifications
M
The traffic classes supported by the DS-TTs and available end-to-end MaxLatency value per traffic class. The VAL server should not request lower latency than the available end-to-end latency.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.25 TSC stream creation request
|
Table 14.3.2.25-1 describes the information flow TSC stream creation request from the VAL server to the NRM server.
Table 14.3.2.25-1: TSC stream creation request
Information element
Status
Description
Requester Identity
M
The identity of the VAL server performing the request.
VAL Stream ID
M
It identifies the VAL stream.
Stream specification
M
Stream specification includes MAC addresses of the source and destination DS-TT ports (e.g. as defined in IEEE 802.1CB [37]).
Traffic specification
M
It includes MaxLatency, MaxFrameInterval, MaxFrameSize, MaxIntervalFrames as described in IEEE 802.1Qcc [35] in clause 46.2.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.26 TSC stream creation response
|
Table 14.3.2.26-1 describes the information flow TSC stream creation response from the NRM server to the VAL server.
Table 14.3.2.26-1: TSC stream creation response
Information element
Status
Description
Result
M
Result includes success or failure of the TSC stream creation.
VAL Stream ID
M
It identifies the VAL stream.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.27 TSC stream deletion request
|
Table 14.3.2.27-1 describes the information flow TSC stream deletion request from the VAL server to the NRM server.
Table 14.3.2.27-1: TSC stream deletion request
Information element
Status
Description
Requester Identity
M
The identity of the VAL server performing the request.
VAL Stream ID
M
It identifies the VAL stream.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.28 TSC stream deletion response
|
Table 14.3.2.28-1 describes the information flow TSC stream deletion response from the NRM server to the VAL server.
Table 14.3.2.28-1: TSC stream deletion response
Information element
Status
Description
Result
M
Result includes success or failure of the network TSC stream deletion. Even in case of failure, the stream is deemed unusable.
VAL Stream ID
M
It identifies the VAL stream.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.29 TSN bridge information report
|
The 5GS bridge management information is defined in TS 23.501 [10], clause 5.28.1 (5GS bridge management).
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.30 TSN bridge information confirmation
|
The 5GS bridge management information is defined in TS 23.501 [10], clause 5.28.1 (5GS bridge management).
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.