hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.6.3.2 Procedure
|
The procedure for NRM server notifying the VAL server with VAL UE(s) related events is described in figure 14.3.6.3.2-1.
Pre-conditions:
- The VAL server has subscribed with NRM server using Monitoring Events Subscription Procedure as specified in clause 14.3.6.2;
Figure 14.3.6.3.2-1: Monitoring Events Notification Procedure
1. If applicable, the NRM server receives the VAL UE related monitoring event notifications from the 3GPP core network as specified in 3GPP TS 23.502 [11].
2. If applicable, the NRM server receives the VAL UE related Analytics event notifications from the 3GPP core network as specified in 3GPP TS 23.288 [34].
3. The NRM server notifies the VAL server about the events related to the VAL UE in Notify Monitorng Events message. If multiple events are to be notified, then the NRM server may aggregate the notifications and send to the VAL server.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.7 5G TSC resource management procedures
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.7.1 General
|
The procedures related to the 5G TSC network resource management are described in the following subclauses.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.7.2 TSC stream availability discovery procedure
|
The TSC stream availability discovery procedure is used by the VAL server to discover the availability of resources for TSC communication for the given stream specification (i.e., between the target UEs) prior to creating the stream.
Pre-conditions:
1. Each UE has an established Ethernet PDU session and DS-TTs are connected to the 5GS TSC bridge. The traffic classes are configured on each DS-TT.
2. The NRM server has collected the 5GS TSC bridge management and port management information. The latter is related to the Ethernet ports located in the DS-TTs including bridge delay per DS-TT Ethernet port pair per traffic class.
3. NRM server has calculated the bridge delay for each port pair, i.e. composed of (ingress DS-TT Ethernet port, egress DS-TT Ethernet port) including the UE-DS-TT residence time, packet delay budget (PDB) and propagation delay for both UL from sender UE and DL to receiver UE.
Figure 14.3.7.2-1: TSC stream availability discovery procedure
1. The NRM server receives a request from a VAL server on NRM-S reference point to discover the connectivity and available QoS characteristics between DS-TTs identified by the stream specification.
2. The NRM server validates the connectivity between the DS-TTs connected in the same 5GS TSC bridge based on the collected 5GS TSC bridge management and port management information, identifies the traffic classes supported by the DS-TTs and determines the end-to-end latency (including the UE-DS-TT residence times, PDBs and propagation delay).
3. NRM server responds to the VAL server with the stream specification and a list of traffic specifications with the available end-to-end latency and the traffic classes supported by the DS-TTs.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.7.3 TSC stream creation procedure
|
This procedure allows the VAL server to create a TSC stream. The TSC stream creation procedure enables the VAL server to establish TSC connectivity with the required QoS between the UEs connected to the 5GS after the stream discovery procedure.
Pre-conditions:
1. Each UE has an established Ethernet PDU session for its DS-TT port MAC address.
2. Connectivity between the DS-TTs has been validated by the TSC stream availability discovery procedure specified in clause 14.3.7.2.
3. The NRM server maintains mapping from the traffic class to TSC QoS.
Figure 14.3.7.3-1: TSC stream creation procedure
1. The NRM server receives a TSC stream creation request from a VAL server to create a TSC stream identified by a VAL Stream ID, between DS-TT ports in the stream specification and for the traffic class in the traffic specification.
2. The NRM server calculates the schedule for the VAL Stream ID based on the information collected earlier from the 5GS via N5. It provides per-stream filtering and policing parameters (e.g. as defined in IEEE 802.1Q [36]) used to derive the TSC QoS information and related flow information. NRM server also provides the forwarding rule (e.g. as defined in IEEE 802.1Q [36]) used to identify the DS-TT MAC address of the corresponding PDU session. Based on the 5GS bridge delay information it determines the TSC QoS information and TSC Assistance information for the stream.
3. Based on the Traffic specification (from the TSC stream creation request in step 1), the SEAL NRM server determines whether time synchronization needs to be activated for the TSC stream on the DS-TTs. If the DS-TTs are time synchronized, then the NRM does not activate the time synchronization for the corresponding DS-TT.
4. As a TSCTSF, the NRM server triggers via N84 the Npcf_PolicyAuthorization_Create service operation as described in 3GPP TS 23.502 [11] for the TSC stream for both UL QoS flow (sender UE to UPF/bridge) and DL QoS flow (UPF/bridge to receiver UE). The Policy Authorization request includes the DS-TT port MAC address, TSC QoS information, TSC Assistance Information (3GPP TS 23.501 [1], cl.5.27.2.3), flow bit rate, priority, Service Data Flow Filter containing flow description including Ethernet Packet Filters. The QoS flow will be assigned for the PDU session for the source MAC address for the UL direction and for the PDU session for the destination MAC address for the DL direction. This information is delivered to the DS-TT by the 5GS.
If time synchronization is determined to be needed for the TSC stream on the DS-TTs in step 3, the NRM server uses the procedures in clause K.2.2 of 3GPP TS 23.501 [10] to activate the time synchronization via the Npcf_PolicyAuthorization_Update service operation. The procedure includes the configuration and initialization of the PTP instance in the DS-TTs, the construction of PMICs to each DS-TT/UE to activate the time synchronization service in the DS-TT and to subscribe for the port management information changes in the DS-TTs.
NOTE: Using gate control parameters for hold and forward buffering is out of scope of the present document.
5. The NRM server sends TSC stream creation response to the VAL server with the result of TSC stream creation for the VAL Stream ID.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.7.4 TSC stream deletion procedure
|
This procedure allows the VAL server to delete a TSC stream.
Pre-conditions:
1. The TSC stream is configured in the 5GS and the DS-TTs.
Figure 14.3.7.4-1: TSC stream deletion procedure
1. The NRM server receives a request from VAL server to delete a TSC stream for with a VAL Stream ID.
2. The NRM server identifies the MAC addresses of the DS-TTs involved in the stream based on the stored information for the VAL Stream ID. If none of the streams require to keep the time synchronization activated, the NRM server deactivates the time synchronization for the corresponding DS-TTs, otherwise keeps the time synchronization activated if the time synchronization for the DS-TTs was activated by the NRM server.
3. As a TSCTSF, the NRM server triggers via N84 the Npcf_PolicyAuthorization_Delete service operation defined in 3GPP TS 23.502 [11] for MAC addresses referred to by the VAL Stream ID. The NRM server uses the procedure to delete both UL QoS flow (sender UE to UPF/bridge) and DL QoS flows (UPF/bridge to receiver UE) from the PDU sessions of the UEs referred to by the VAL Stream ID. Before invoking the Npcf_PolicyAuthorization_Delete procedure, if the time synchronization service for the DS-TTs needs deactivation, the NRM server deactivates the time synchronization for the DS-TTs as described in clause K.2.2 3GPP TS 23.501 [10] via the Npcf_PolicyAuthorization_Update service operation.
4. The NRM server sends TSC stream deletion response to the VAL server with the result of TSC stream deletion for the VAL Stream ID.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.8 TSN resource management procedures
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.8.1 General
|
The procedures related to the TSN network resource management are described in the following subclauses.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.8.2 5GS TSN Bridge information reporting
|
Pre-conditions:
1. There is already an established session between the TSN CNC and the NRM server acting as TSN-AF.
Figure 14.3.8.2-1: TSN Bridge information reporting procedure
1. 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. The NRM server stores the binding relationship between 5GS Bridge ID, MAC address of the DS-TT Ethernet port and also updates 5GS bridge delay as defined in clause 5.27.5 of TS 23.501 [10]. The NRM server retrieves txPropagationDelay and Traffic Class table from DS-TT and it also retrieves txPropagationDelay and Traffic Class table from NW-TT.
2. Whenever there is a new or updated bridge information the NRM server interacts with the TSN CNC and reports the TSN Bridge information to register a new TSN Bridge or update an existing TSN Bridge. The TSN CNC stores the TSN Bridge information and confirms to the NRM server.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.8.3 5GS TSN Bridge configuration procedure
|
Pre-conditions:
1. The TSN CNC has stored the 5GS TSN Bridge information received from the NRM server acting as TSN AF.
2. The NRM server acting as TSN AF has stored the 5GS TSN Bridge information collected from the 5GS, as described in clause 14.3.8.2.
Figure 14.3.8.3-1: TSN Bridge configuration procedure
1. The NRM server receives from the TSN CNC per-stream filtering, policing parameters and related flow information according to IEEE 802.1Q [36] and it uses them to derive TSN QoS information and related flow information. The TSN AF uses this information to identify the DS-TT MAC address of the corresponding PDU session.
2. NRM server triggers via N5 the AF request procedure as described in 3GPP TS 23.502 [11] Annex F.2. The AF request includes the DS-TT port MAC address, TSC QoS information, TSC Assistance Information, flow bit rate, priority, Service Data Flow Filter containing flow description including Ethernet Packet Filters.
3. NRM server responds with a TSN Bridge configuration.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.9 Establishing communication with application service requirements
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.9.1 General
|
The NRM client and the NRM server (acting as an AS) are involved in the exchange and analysis of the desired service requirements (e.g. packet size, packet transmission interval, reliability, packet error rate) for the E2E communication amongst the Vertical UEs. The NRM server triggers the establishment of application-level direct service connectivity between two UEs via Uu, based on the information provided by the UEs and static configuration information available to the NRM server prior to the UE interaction. Note that service connectivity among VAL clients is established over the Uu, without device-to-device direct radio connectivity (e.g. PC5) requirement.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.9.2 Procedures
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.9.2.1 Procedure triggered by correlated source and destination requests
|
The procedure for establishing Uu-based application-level direct communications between two UEs, with application service requirements is as illustrated in figure 14.3.9.2.1‑1. In this procedure the source and destination VAL clients correlate their triggering of the procedure establishment before the NRM Server provides the service.
Pre-conditions:
- NRM client 1 and NRM client 2 are provided configuration information for the VAL clients served e.g. connectivity requirements, which destination UEs to connect to over Uu, etc.
- The NRM client 1 and NRM client 2 are configured with the information of the NRM server and have connectivity enabled to communicate with the NRM server. The information is provided via pre-configuration.
- The NRM server is configured with policies and information of the UEs to determine authorization of the UEs requesting connectivity via Uu.
- The VAL clients associated with NRM client 1 and NRM client 2 have triggered the establishment of connectivity.
Figure 14.3.9.2.1-1: Establishing communication with application service requirements
1a. The NRM client 1 sends the application connectivity request (source identity and IP address, destination identities, service requirements) to the NRM Server. The service requirement from the source includes packet size, packet transmission interval, packet E2E latency, allowed packet loss rate/packet loss amount/packet error rate, etc. The destination may be multiple UEs (devices). The identity of source and destination may be the application user identity or the MAC address.
1b. The NRM server determines whether the UE of NRM client 1 is authorized to connect to the destination UEs for direct service communications via Uu. If UE of NRM client 1 is authorized to connect to the destination UEs, then a response is provided to the NRM client 1 indicating acceptance of the request.
2a. The NRM client 2 sends the application connectivity request (destination identity and IP address, source identity, service requirements) to the NRM server. The service requirements from the destination includes the service requirements as described in step 1a.
2b. The NRM server determines whether the UE of NRM client 2 is authorized to connect to the destination UEs for direct service communications via Uu. If UE of NRM client 2 is authorized to connect to the destination UEs, then a response is provided to the NRM client 2 indicating acceptance of the request.
3. Based on the service requirements received in step 1 and step 2, the NRM server determines the parameters and patterns for direct service connectivity between the source UE and the destination UE via Uu and also the transport requirements (i.e., QoS requirements for the 3GPP system (e.g. 5GS)). Further, the NRM server derives the individual QoS requirements for the source UE and the destination UE from the transport requirement accordingly, i.e., the QoS requirements required between the source UE of NRM client 1 and the 3GPP network and the QoS requirements required between the destination UE of NRM client 2 and the 3GPP network. This step may also include retrieving the direct link status of the UEs (e.g. PDU Session Status, UE reachability). If the NRM server determines that direct service connectivity via Uu is not authorized or not possible with the given connectivity requirements, it skips step 4 and proceeds to steps 5 and 6, informing each NRM client accordingly.
NRM server will process E2E connectivity establishment between NRM client 1 and NRM client 2 only after it receives the request from NRM client 2. There can be several NRM clients (destinations) which will perform step 2 and NRM server will process their E2E connectivity with NRM client 1 (source) as and when the requests are received by the NRM server.
4. The NRM server triggers 3GPP system to establish QoS flow between the UE of NRM client 1 and the 3GPP network and the QoS flow between the UE of NRM client 2 and the network with individual QoS requirements derived from step 3 followed the procedure as specified in 3GPP TS 23.502 [12], 3GPP TS 23.501 [10].
5. The NRM server sends the application connectivity notification (connectivity/session information) to NRM client 1 indicating successful establishment of the connectivity. The connectivity/session information may contain the accepted destination identities.
6. The NRM server sends the application connectivity notification (connectivity/session information) to NRM client 2 indicating successful establishment of the connectivity.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.9.2.2 Procedure triggered by source request and coordinated with destination
|
This procedure is used for establishing Uu-based application-level direct communications between two UEs, based on a single client initiating and providing application requirements. The procedure is as illustrated in figure 14.3.9.2.2‑1. The NRM Server provides the service by coordinating with the destination client.
Pre-conditions:
- NRM client 1 and NRM client 2 are provided configuration information for the VAL clients served e.g. connectivity requirements, etc.
- Pre-processing determines that network assisted UE-to-UE communications is required. VAL application policies and destination information for NRM clients are available at the NRM server.
- The VAL client associated with NRM client 1 triggers the establishment of connectivity and provides information about (one or more) destination VAL client(s).
Figure 14.3.9.2.2-1: Coordination UE-to-UE communications with VAL application requirements
1. The NRM client 1 sends the application connectivity request (source identity and IP address, destination identities, application requirements) to the NRM server to establish connectivity for VAL client 1 on UE 1. The destination VAL client(s) may be hosted on one or multiple UEs (devices).
2. The NRM server determines whether VAL client 1 is authorized to connect to VAL client 2 for application-level direct UE-to-UE communications. If VAL client 1 is authorized to connect to VAL client 2, the NRM server performs the get application connectivity context request to retrieve VAL UE-to-UE connection coordination context procedure as described in clause 14.3.2.56. This step can be skipped if the NRM server is already aware of VAL client 2's context information.
NOTE: The signaling and functionality for handling the cases when NRM client 2 will be temporarily unavailable for establishing the direct service connection are implementation dependent.
3. The NRM client 2 sends the get application connectivity context response to the NRM server, 2. Using the request information and local policies, the NRM client 2 determines whether context information is to be provided for establishing application-level direct connectivity to the counterpart UE for the VAL application indicated. If the NRM client determines that context information is to be provided, it responds to the NRM server and provides the VAL connection coordination context data for the VAL client served.
4. The NRM server sends the application connectivity response to NRM client 1.
5. The NRM server uses VAL client 1's and VAL client 2's context information, their application-level direct UE-to-UE connectivity requirements, location information, and network context as input, checks connectivity service policies, and determines the parameters and patterns for application-level direct UE-to-UE connectivity between the VAL clients. The NRM server may also determine transport requirements (e.g. QoS requirements, for the 3GPP system (e.g. 5GS)). Further, the NRM server derives the individual QoS requirements for the source UE and the destination UE from the transport requirement accordingly, i.e., the QoS requirements required between the source UE of NRM client 1 and the 3GPP network and the QoS requirements required between the destination UE of NRM client 2 and the 3GPP network.
If network provided location information is used, location information may be obtained from the SEAL location management server. Alternatively, Location Reporting monitoring as described in 23.502[12] may be used. This step may also include a request for direct link status (e.g. PDU Session Status, UE reachability, etc. as described in 23.502 [12]). This action may be skipped if the clients provide location information or if there are no location requirements for establishing the application-level direct UE-to-UE connectivity.
If the NRM server determines that UE-to-UE application-level direct connectivity is not authorized or not possible with the given connectivity requirements, it skips step 5 and proceeds to steps 6 and 7, informing each NRM client accordingly.
6. The NRM server may request the 3GPP system to establish or modify the QoS flow between the source UE and the network, and the QoS flow between the destination UE and the network that enables the application-level direct UE-to-UE connection for VAL client 1 and VAL client 2 services, e.g. via modification of existing radio bearers. NRM server provides the necessary information (e.g. identifiers of VAL client 1 and VAL client 2, transport requirements) in this request message as per the procedure as specified in 3GPP TS 23.502 [12], 3GPP TS 23.501 [10].
7. a. The NRM server notifies NRM client 1 of the established UE-to-UE connection b. The NRM server notifies the NRM client 2 of the established UE-to-UE connection.
Each NRM client notifies the corresponding VAL client of the established application-level direct UE-to-UE connection.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.10 AF influence URSP procedure for reliable transmission
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.10.1 General
|
The procedures related to the AF influence URSP for reliable transmission are described in the following subclauses.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.10.2 AF influence URSP procedure for reliable transmission
|
Pre-conditions:
1. The SEALDD server (or VAL server) has decided to use reliable transmission for a specific SEALDD client (or VAL client) and has got the UE address or UE ID.
Figure 14.3.10.2-1: AF influence URSP procedure for reliable transmission
1. The NRM server receives from the SEALDD server (or VAL server) about the request for reliable transmission service with the application descriptors for the two redundant transmission paths. The SEALDD client's current UE address or UE ID is also provided to identify the affected UE.
2. After receiving the request from SEALDD server (or VAL server), the NRM server associates the available DNN and S-NSSAI information for the two application descriptors. NRM server triggers via N5/N33 with the AF guidance for URSP procedure as described in 3GPP TS 23.502 [11] clause 4.15.6.10. The AF request includes the application traffic descriptors and the associated DNN, S-NSSAI, and also includes UE address or UE ID received in step 1.
3. NRM server sends response about reliable transmission service.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.11 VAL services over 5GS supporting EPS interworking
|
The VAL server consumes the network resource management services from the NRM server. As specified in 3GPP TS 23.501 [10], a dedicated user plane anchor point, i.e. UPF + PGW-U function, is defined for interworking between 5GS and EPS. This enables that the network can directly handle PDU sessions (in 5GS) and PDN connections (in EPS) associated to VAL service sessions of a VAL UE during inter-system mobility.
The inter-system mobility of a VAL UE will be transparent to the NRM server and VAL server. The NRM server will continue interacting with the same control plane functions, e.g. PCF, and the VAL server will continue interacting with the same user plane function, e.g. UPF + PGW-U.
NOTE: For the case that seamless session continuity is required for VAL services, EPS interworking with N26 (interface between AMF in 5GC and MME in EPC) is required for inter-system change, as described in 3GPP TS 23.501 [10].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.12 UE unified traffic pattern and monitoring management
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.12.1 General
|
UE unified traffic pattern and monitoring management procedures allow NRM to offer services leveraging CN exposure APIs for network parameter values configuration and UE monitoring event management.
14.3.12.2 UE unified traffic pattern and monitoring management subscription procedure
VAL servers can indicate to the NRM server interest in receiving UE unified traffic patterns and monitoring management services by sending the UE unified traffic pattern and monitoring management subscription requests.
The subscription requests from each VAL server also include the traffic pattern configuration of the requester, which refers to application-level patterns of data traffic. The NRM server aggregates the traffic patterns obtained from the requestors (and described in Table 14.3.2.53-2) to determine the UE unified traffic patterns per UE. The UE unified traffic patterns are described via Table 14.3.2.55-1 for the UE unified traffic pattern update notification. These aggregated traffic patterns per UE (termed UE unified traffic pattern) are updated/adjusted by the NRM Server based on information obtained from UE monitoring.
Figure 14.3.12.2-1: UE unified traffic pattern and monitoring management subscription procedure
1. In order to subscribe to the NRM Server services, the VAL server sends the UE unified traffic pattern and monitoring management subscription request, as detailed in clause 14.3.2.53. The subscription request may include traffic pattern configuration, which provides the traffic patterns of the specific VAL Server. The request may also include Management subscription indications which indicate to the NRM Server which management and 5GC exposure procedures the VAL server allows the NRM Server to perform on its behalf.
2. Upon receipt of the request, the NRM server sends a UE unified traffic pattern and monitoring management subscription response as detailed in clause 14.3.2.54.
3. The NRM Server aggregates UE unified traffic pattern and monitoring management subscription requests from different VAL servers and determines the UE unified traffic pattern per UE (using the traffic patterns of all the communicating with the UE).
4. Depending on the subscription requests received and local policies, the NRM Server executes one or more management and 5GC exposure procedure (per UE). Management and 5GC exposure procedures are detailed in clause 14.3.12.4.
The NRM Server determines the management procedures required to be executed on behalf of the VAL Servers based on the received management subscription indications as follows:
- If the UE unified traffic pattern monitoring management indication is provided, the NRM Server executes steps 1-3 of the UE unified traffic pattern monitoring procedure detailed in clause 14.3.12.4.2.
- If the UE unified traffic pattern monitoring update notification indication is provided, the NRM Server executes the steps 1-4 of the UE unified traffic pattern monitoring procedure detailed in clause 14.3.12.4.2.
- If the Network parameter coordination indication is provided, the NRM executes the network parameter coordination procedure detailed in clause 14.3.12.4.3.
NOTE: The NRM Server translates the management subscription indications received from different VAL Servers into per-UE management indications based on local policies and configurations. For example, an NRM Server may be configured to execute a management procedure for a UE if at least one VAL Server indicates it. Another NRM Server may be configured to provide all the management procedures for the UEs using the platform independent of VAL Server subscription indications.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.12.3 UE unified traffic pattern update notification procedure
|
An NRM Server can provide updated UE unified traffic pattern information to VAL servers by sending UE unified traffic pattern update notifications as shown in figure 14.3.12.3-1. The UE unified traffic pattern management procedure detailed in clause 14.3.12.4.2. is an example of procedure which may result in UE unified traffic pattern updates at the NRM server, based on which UE unified traffic pattern update notifications are provided.
Pre-conditions:
1. The VAL server has subscribed for UE unified traffic pattern and monitoring management services, requesting to receive UE unified traffic pattern update notifications
Figure 14.3.12.3-1: UE unified traffic pattern update notification procedure
1. The NRM server sends the UE unified traffic pattern update notification when either of the following occurs:
- Monitoring events lead to updates in the UE unified traffic pattern (e.g., to schedule elements in Table 14.3.2.55-1) the NRM server sends a corresponding notification to the VAL server. Other notifications may be provided, e.g., if the stationary indication changes.
- An NP Configuration Notification is received with a new set of applied network parameters and if the NRM Server determines that the new configuration is incompatible with the current UE unified traffic pattern (see also clause 14.3.12.4.2 step 3).
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.12.4 Management and 5GC exposure procedures
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.12.4.1 General
|
The management and 5GC exposure procedures in this clause show NRM processing and its interactions with 5GC in support of the functionality described in clause 14.3.12.2
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.12.4.2 UE unified traffic pattern management procedure
|
The UE unified traffic pattern management procedure is used to determine and manage a unified traffic pattern applicable to a specified UE. The NRM Server then uses the 5GC exposure of UE monitoring events to update the UE unified traffic pattern.
Pre-conditions:
1. The NRM Server determines to provide the service for a specific UE if either of the following conditions is true:
a) It receives UE unified traffic pattern monitoring management indications in UE unified traffic pattern and monitoring management subscription requests; or
b) It determines to provide Network parameter coordination services for the UE.
Figure 14.3.12.4.2-1: UE unified traffic pattern and monitoring management subscription procedure
1. The NRM Server determines an initial UE unified traffic pattern, e.g. by using all Traffic pattern configurations received for the UE .
2. The NRM Server determines, based on local policy that UE monitoring events are to be configured and executes the corresponding Monitoring procedure as described in 3GPP TS 29.122 [54] clause 4.4.2.
3. The NRM Server updates the UE unified traffic pattern based on the received monitoring events as follows:
- If a Monitoring Notification report for UE_REACHABILITY is received, and idleStatusInfo information is provided in the report, the NRM Server changes the schedule element of the UE unified traffic pattern such that the duration of activity is set to the value of the activeTime parameter configured in the idleStatusInfo.
- If a Monitoring Notification report for AVAILABILITY_AFTER_DDN_FAILURE is received after UEs transition to idle mode, the NRM Server updates the schedule element of the UE unified traffic pattern such that: the start of an activity window is based on the Idle Timestamp, with a periodicity equal to the TAU/RAU Timer; the duration of the activity window indicates the Active Time value.
- If a Monitoring Notification report for COMMUNICATION_FAILURE is received The NRM updates the schedule element of the UE unified traffic pattern to indicate that no communications are currently available (e.g. by using a keyword such as "NULL"). Local policies may specify events/ thresholds further defining when the NRM may provide a UE unified traffic pattern update based on monitoring events. For example, the update may be provided only after repeated communication failures are received within a timespan, or only if high reliability communications are expected. It is recommended that UE Reachability monitoring is also enabled in conjunction with the Communication Failure monitoring. This enables the NRM to provide updated timing information once the UE becomes reachable again.
- If a Monitoring Notification report for LOSS_OF_CONNECTIVITY is received, the NRM Server changes the schedule element of the UE unified traffic pattern to indicate that no communications are currently available
4. Conditional: The NRM Server notifies subscribers of the UE unified traffic pattern updates, as described in clause 14.3.2.55
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.12.4.3 Network parameter coordination procedure
|
The network parameter coordination procedure uses UE unified traffic pattern information to influence aspects of UE/network behaviour such as the UE's PSM and extended idle mode DR14. For this purpose, parameter values may be suggested for Maximum Latency and Maximum Response Time for a UE. 5GC may choose to accept, reject or modify the suggested configuration parameter value.
Pre-conditions:
1. The NRM Server determines to provide the service for a specific UE after receiving Network parameter coordination indications in UE unified traffic pattern and monitoring management subscription requests, subject to policy.
2. The NRM Server determines and manages UE unified traffic patterns as described in clause 14.3.12.4.2.
Figure 14.3.12.4.3-1: Network parameter coordination procedure
1. The NRM Server determines to provide Network parameter configuration to 5GC. This determination can be based on updates to the UE unified traffic patterns resulting from interactions with VAL Servers (e.g. Traffic pattern configuration updates), on local policies, etc.
The NRM Server determines parameters the needed for NpConfiguration data structure as specified in 3GPP TS 29.122 [54] from the UE unified traffic patterns as follows:
- maximumLatency – This value tells the network how long the UE is allowed to sleep. Setting it to 0 will disable PSM, extended idle mode DRX, and extended buffering. The NRM Server can extract the periodicity derived from the UE unified traffic pattern, which includes the schedule elements for the UEs communications with all VAL servers. The NRM Server sets Maximum Latency to be approximately the periodicity of the active periods derived from the schedule element of the UE unified traffic pattern.
- maximumResponseTime – When the UE uses PSM, Maximum Response Time tells the network how long the UE should stay reachable after a transition to idle. When the UE uses eDRX, Maximum Response Time is used by the network to determine when to send a reachability notification before a UE's paging occasion. The NRM Server extracts a duration of activity from the schedule element of the UE unified traffic pattern and sets Maximum Response Time to reflect the duration of activity, indicating how long the UE should stay reachable for downlink communications.
2. The NRM Server performs the Network Parameter Configuration procedure as described in 3GPP TS 29.122 [54] clause 4.4.12.
NOTE: The values provided by NRM Server to 5GC in the Network parameter configuration procedure may or may not be accepted by the network. If they are not accepted, 5GC responds accordingly and the previous values apply, or new values are provided. The new values are used by NRM Server as described in this clause when they were provided via monitoring event notifications.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.13 Background Data Transfer configuration
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.13.1 General
|
The Background Data Transfer (BDT) feature requires an initial step in which BDT policies are requested and negotiated. BDT Policy requests to the 3GPP network are based on an expected time window, expected data volume per UE and UE set, with additional optional information e.g., network area information. The UE set is indicated as an expected number of UEs, and optionally a VAL group ID or a list of VAL UE IDs.
The feature allows for the NRM server involved to negotiate the BDT policies proposed by the network. It also allows the NRM server to enable notifications to be sent, should network conditions affect future BDT policies.
Based on the BDT policies obtained using the procedures detailed in this clause, a VAL server can initiate a data transfer to the client and/or the VAL client can initiate a data transfer to the VAL server at the negotiated time and with the negotiated charging rates. The data transfer between the VAL Server and the VAL Client is performed without NRM Server enablement. Service layer functionality for the purpose of facilitating the data transfer with the negotiated BDT policy is not in scope of this specification.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.13.2 Request and Select Background Data Transfer Policy
|
Figure 14.3.13.2-1 depicts a general procedure for the request and configuration of traffic policies for BDT initiated by a request from a VAL Server.
Figure 14.3.13.2-1: General Procedure for configuration of Background Data Transfer
1. A VAL Server requests the NRM Server to negotiate with the 3GPP network a background data transfer policy using the BDT_Configuration_request (see clause 14.4.2.15).
The request includes expected data volume per UE, expected number of UEs, expected time window for the background data transfer. The request may also include group ID, geographic information for the UEs, application traffic descriptors, a request expiration time, guidance for policy selection. If guidance for policy selection is not included, the NRM Server may choose independently from among multiple transfer policies, depending on local and ASP-provided policies.
2. Based on the request expiration time and Service Provider policies, NRM Server may determine to delay interactions with the 3GPP network in order to negotiate on behalf of multiple VAL Servers.
The NRM Server performs the procedure for negotiation of background data transfer policy as described in 3GPP TS 23.502 [11] clause 4.16.7.2. The procedure requires that expected data volume per UE, expected number of UEs, and expected time window are provided by the NRM Server. If the NRM Server determines to negotiate on behalf of multiple VAL Servers, the parameters included reflects a superset of the individual VAL Server requests.
NOTE 1: The NRM Server determines to negotiate on behalf of multiple VAL Servers based on implementation options and local policies. For example, if the request expiration time and expected time window are sufficiently large and, respectively, far away in time, the NRM Server may be allowed to delay the negotiations with the 3GPP network in case another request is received, targeting the same group of UEs. If another request is received with expected time windows sufficiently close and if the guidance for policy selection allows, a single policy/time window may be negotiated instead. This allows the UE group to wake up only once for multiple background data transfers.
The 3GPP network determines one or more applicable BDT policies based on the requesting Background Data Transfer parameters. A list of BDT policies and a mandatory BDT Reference ID is provided to the NRM Server. Each BDT policy includes charging rating group reference and allocated time window and optional maximum UL and DL aggregated bandwidth as specified by 3GPP TS 23.503 [12]. The NRM Server uses ASP policies and the transfer selection guidance (if available) to select a BDT policy. The NRM Server informs the 3GPP Network of the selected BDT policy.
NOTE 2: Based on 3GPP TS 23.503 [12] clause 6.1.2.4. it is assumed that the NRM server is configured to understand the charging rating group reference based on agreements with the operator.
NOTE 3: The NRM server utilizes the BDT warning notification from 3GPP network based on local policies.
3. The NRM Server stores the BDT configuration information with the information received from VAL server in step 1 along with the BDT Reference ID and selected BDT policy. The NRM server responds to the VAL Server, providing the BDT Reference ID and allocated time window of the selected background data transfer policy.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.13.3 Reselect Background Data Transfer Policy
|
Figure 14.3.13.3-1 depicts a procedure for reselecting BDT policies after BDT warning.
Figure 14.3.13.3-1: Reselecting BDT policies after BDT warning
1. The 3GPP Network, via NEF, sends the BDT warning (BDT Policy negotiate) notification to the NRM server as specified in step 10, clause 4.16.7.3 of 3GPP TS 23.502 [11]. The notification includes the affected BDT Reference ID and list of candidate BDT policies.
Each of the BDT policies in the candidate BDT list includes charging rating group reference and time window, as well as optional maximum UL and DL aggregated bandwidth.
The NRM Server checks the new BDT policies included in the candidate list of the BDT warning notification. The NRM Server determines whether the notification affects multiple VAL Servers or not. The NRM Server uses ASP policies and the transfer selection guidance (if available) provided with the initial VAL Server request to select a policy.
The NRM Server informs the 3GPP Network of the selected transfer policy or that no new policy has been selected by using steps 11-16 of the procedure for BDT warning notification in 3GPP TS 23.502 [11] clause 4.16.7.3.
2 The NRM server updates the BDT configuration information with the newly selected BDT policy or no BDT policy is selected for the BDT Reference ID. The NRM Server sends a BDT_Negotiation_notification (see clause 14.4.2.16), to the VAL server, providing information about the newly selected BDT policy, , if the granted time window changes or that no BDT policy is selected for the BDT Reference ID. If a new BDT policy affecting the granted time window is selected by the NRM server, the information provided to the VAL Server includes the BDT Reference ID and the granted time window.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.13.4 BDT configuration get
|
Figure 14.3.13.4-1 illustrates a procedure for retrieving the BDT configuration on the NRM server by the VAL server.
Pre-conditions:
1. The VAL server has performed the BDT configuration request as specified in clause 14.3.13.2.
Figure 14.3.13.4-1: BDT configuration get
1. A VAL Server requests the NRM Server to retrieve its background data transfer policy configuration using the BDT_Configuration_Get_request (see clause 14.4.2.19).
The request includes identifier for the BDT policy configuration stored at the NRM server.
2. The NRM Server provides a response to the VAL server indicating success or failure of the operation and the BDT configuration data available at the NRM server.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.13.5 BDT configuration update
|
Figure 14.3.13.5-1 illustrates a procedure for updating the BDT configuration on the NRM server by the VAL server.
Pre-conditions:
1. The VAL server has performed the BDT configuration request as specified in clause 14.3.13.2.
Figure 14.3.13.5-1: BDT configuration update
1. A VAL Server requests the NRM Server to update its background data transfer policy configuration using the BDT_Configuration_Update_request (see clause 14.4.2.20).
The request includes identifier for the BDT policy configuration stored at the NRM server and one or more updated information like expected data volume per UE, expected number of UEs, expected time window for the background data transfer, geographic information for the UEs, a request expiration time, guidance for policy selection.
2. The NRM Server may perform the BDT policy negotiation as specified in 3GPP TS 23.502 [11] clause 4.16.7.2. The request for update of the BDT policy configuration by the VAL server may impact the selected BDT policy.
3. The NRM Server provides a response to the VAL server indicating success or failure of the operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.13.6 BDT configuration delete
|
Figure 14.3.13.6-1 illustrates a procedure for deleting the BDT configuration on the NRM server by the VAL server.
Pre-conditions:
1. The VAL server has performed the BDT configuration request as specified in clause 14.3.13.2.
Figure 14.3.13.6-1: BDT configuration delete
1. A VAL Server requests the NRM Server to delete its background data transfer policy configuration using the BDT_Configuration_delete_request (see clause 14.4.2.21).
The request includes identifier for the BDT policy configuration stored at the NRM server.
2. The NRM Server may perform the BDT policy negotiation update as specified in 3GPP TS 23.502 [11] clause 4.16.7.2. If NRM server is currently serving only one VAL server, then BDT policy update is performed as specified in 3GPP TS 23.502 [11] clause 4.16.7.3. The request for deletion of the BDT policy configuration by the VAL server removes the requirement of the VAL server and/or the VAL UE or group of VAL UEs to perform BDT.
3. The NRM Server provides a response to the VAL server indicating success or failure of the operation.
14.3.14 Device triggering
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.14.1 General
|
A service may initiate a device trigger to a UE to cause it, for example, to connect to a VAL server, to provide updated information, etc.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.14.2 Device Triggering via NRM procedure
|
Figure 14.3.14.2-1: Device Triggering via NRM Procedure
1. The device triggering procedure is initiated by an API request from a VAL Server.
2. The NRM Server determines the valid conditions to initiate the device triggering procedure with the CN. The determination is based on request parameters as follows:
a) If “Time Window” IE is present, the NRM Server includes its value to limit the conditions considered as valid based on step a) and/or to determine the trigger validity time value for the CN API request .
b) If “Area information” IE is present, the NRM Server includes its value to limit the conditions considered as valid based on step b)
3. The NRM Server performs the device triggering procedure described in 3GPP TS 23.682 [7] clause 5.2. The procedure requires that the UE Identifier, port number(s) and protocol information are available at the NRM Server. The trigger may be sent to ensure that a target UE in PSM mode is reachable when application communications resume.
As part of the procedure, the NRM Server receives a Device Triggering delivery status report from SCEF/NEF indicating the success of the delivery.
4. The NRM Server responds to the step 1 request.
Based on the trigger purpose derived from the payload, the targeted NRM Client or VAL Client performs the corresponding actions (e.g., connect to the VAL Server).
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4 SEAL APIs for network resource management
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.1 General
|
Table 14.4.1-1 illustrates the SEAL APIs for network resource management.
Table 14.4.1-1: List of SEAL APIs for network resource management
API Name
API Operations
Known Consumer(s)
Communication Type
SS_NetworkResourceAdaptation
Reserve_Network_Resource
VAL server
Request /Response
Request_Unicast_Resource
VAL server
Request /Response
Update_Unicast_Resource
VAL server
Request /Response
Request_Multicast_Resource
VAL server
Request /Response
Notify_UP_Delivery_Mode
VAL server
Subscribe/Notify
Reliable_Transmission
VAL server, SEALDD server
Request /Response
BDT_Configuration_Request
VAL server, SEALDD server
Subscribe/Notify
BDT_Negotiation_Notification
VAL server, SEALDD server
Subscribe/Notify
BDT_Configuration_Get
VAL server, SEALDD server
Request /Response
BDT_Configuration_Update
VAL server, SEALDD server
Request /Response
BDT_Configuration_Delete
VAL server, SEALDD server
Request /Response
TSC_Stream_Availability_Discovery
VAL server
Request /Response
TSC_Stream_Creation
VAL server
Request /Response
TSC_Stream_Deletion
VAL server
Request /Response
SS_EventsMonitoring
Subscribe_Monitoring_Events
VAL server
Subscribe/Notify
Notify_Monitoring_Events
VAL server
SS_NetworkResourceMonitoring
Subscribe_Unicast_QoS_Monitoring
VAL server
Subscribe/Notify
Notify_Unicast_QoS_Monitoring
VAL server
Unsubscribe_Unicast_QoS_Monitoring
VAL server
Obtain_Unicast_QoS_Monitoring_Data
VAL server
Request /Response
Update_Unicast_QoS_Monitoring_Subscription
VAL server
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.2 SS_NetworkResourceAdaptation API
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.2.1 General
|
API description: This API enables the VAL server to communicate with the network resource management server for network resource adaptation and VAL UE monitoring over NRM-S.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.2.2 Reserve_Network_Resource operation
|
API operation name: Reserve_Network_Resource
Description: Requesting for network resource adaptation.
Known Consumers: VAL server.
Inputs: See subclause 14.3.2.1
Outputs: See subclause 14.3.2.2
See subclause 14.3.3 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.2.3 Request_Unicast_Resource
|
API operation name: Request_Unicast_Resource
Description: Requesting unicast resource.
Known Consumers: VAL server.
Inputs: See subclause 14.3.2.6
Outputs: See subclause 14.3.2.7
See subclause 14.3.3 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.2.4 Update_Unicast_Resource
|
API operation name: Update_Unicast_Resource
Description: Updating unicast resource.
Known Consumers: VAL server.
Inputs: See subclause 14.3.2.8
Outputs: See subclause 14.3.2.9
See subclause 14.3.3 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.2.5 Request_Multicast_Resource
|
API operation name: Request_Multicast_Resource
Description: Requesting multicast resource.
Known Consumers: VAL server.
Inputs: See subclause 14.3.2.10
Outputs: See subclause 14.3.2.11
See subclause 14.3.4 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.2.6 Notify_UP_Delivery_Mode
|
API operation name: Notify_UP_Delivery_Mode
Description: Notifying the user plane delivery mode.
Known Consumers: VAL server.
Inputs: See subclause 14.3.2.12
Outputs: None.
See subclause 14.3.4 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.2.7 TSC_Stream_ Availability_Discovery
|
API operation name: TSC_Stream_ Availability_Discovery
Description: Requesting to discover the connectivity and available QoS characteristics between DS-TTs.
Known Consumers: VAL server.
Inputs: See subclause 14.3.2.23
Outputs: See subclause 14.3.2.24
See subclause 14.3.7.2 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.2.8 TSC_Stream_Creation
|
API operation name: TSC_Stream_Creation
Description: Requesting the NRM to create a TSC stream.
Known Consumers: VAL server.
Inputs: See subclause 14.3.2.25
Outputs: See subclause 14.3.2.26
See subclause 14.3.7.3 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.2.9 TSC_Stream_Deletion
|
API operation name: TSC_Stream_Deletion
Description: Requesting the NRM to delete the TSC stream.
Known Consumers: VAL server.
Inputs: See subclause 14.3.2.27
Outputs: See subclause 14.3.2.28
See subclause 14.3.7.4 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.2.10 Request_Multicast/Broadcast_Resource
|
API operation name: Request_Multicast/Broadcast_Resource
Description: Requesting multicast/broadcast resource.
Known Consumers: VAL server.
Inputs: See subclause 14.3.2.40.
Outputs: See subclause 14.3.2.41.
See subclause 14.3.4A for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.2.11 Update_Multicast/Broadcast_Resource
|
API operation name: Update_Multicast/Broadcast_Resource
Description: Updating multicast/broadcast resource.
Known Consumers: VAL server.
Inputs: See subclause 14.3.2.42.
Outputs: See subclause 14.3.2.43.
See subclause 14.3.4A for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.2.12 Delete_Multicast/Broadcast_Resource
|
API operation name: Delete_Multicast/Broadcast_Resource
Description: Deleting multicast/broadcast resource.
Known Consumers: VAL server.
Inputs: See subclause 14.3.2.44.
Outputs: See subclause 14.3.2.45.
See subclause 14.3.4A for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.2.13 Activate_Multicast_Resource
|
API operation name: Activate_multicast_Resource
Description: Activating multicast/broadcast resource.
Known Consumers: VAL server.
Inputs: See subclause 14.3.2.46.
Outputs: See subclause 14.3.2.47.
See subclause 14.3.4A for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.2.14 Deactivate_Multicast_Resource
|
API operation name: Deactivate_multicast_Resource
Description: Deactivating multicast/broadcast resource.
Known Consumers: VAL server.
Inputs: See subclause 14.3.2.48.
Outputs: See subclause 14.3.2.49.
See subclause 14.3.4A for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.2.15 BDT_Configuration_request
|
API operation name: BDT_Configuration_request
Description: Requesting Background data transfer configuration.
Known Consumers: VAL server.
Inputs: See subclause 14.3.2.58
Outputs: See subclause 14.3.2.59
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.2.16 BDT_Negotiation_notification
|
API operation name: BDT_Negotiation_notification
Description: Forwards BDT negotiation notification.
Known Consumers: VAL server.
Inputs: None
Outputs: See subclause 14.3.2.59
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.2.17 Subscribe_Unified_Traffic_Pattern_and_Monitoring_Management operation
|
API operation name: Subscribe_Unified_Traffic_Pattern_and_Monitoring_Management
Description: Requesting UE unified traffic pattern and monitoring management subscription
Known Consumers: VAL server.
Inputs: See subclause 14.3.2.53
Outputs: See subclause 14.3.2.54.
See subclause 14.3.12.2 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.2.18 Notify_Unified_Traffic_Pattern_Update operation
|
API operation name: Notify_Unified_Traffic_Pattern_Update
Description: Notifies of update to UE unified traffic patterns
Known Consumers: VAL server.
Inputs: None
Outputs: See subclause 14.3.2.55.
See subclause 14.3.12.3 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.2.19 BDT_Configuration_Get_request
|
API operation name: BDT_Configuration_Get_request
Description: Retrieving Background data transfer configuration.
Known Consumers: VAL server.
Inputs: See subclause 14.3.2.61
Outputs: See subclause 14.3.2.62
See subclause 14.3.13.4 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.2.20 BDT_Configuration_Update_request
|
API operation name: BDT_Configuration_Update_request
Description: Updating Background data transfer configuration.
Known Consumers: VAL server.
Inputs: See subclause 14.3.2.63
Outputs: See subclause 14.3.2.64
See subclause 14.3.13.5 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.2.21 BDT_Configuration_Delete_request
|
API operation name: BDT_Configuration_Delete_request
Description: Deleting Background data transfer configuration.
Known Consumers: VAL server.
Inputs: See subclause 14.3.2.65
Outputs: See subclause 14.3.2.66
See subclause 14.3.13.6 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.2.22 Reliable_Transmission_request
|
API operation name: Reliable_Transmission_request
Description: Requesting Reliable Transmission service
Known Consumers: SEALDD server or VAL server
Inputs: See subclause 14.3.2.67.
Outputs: See subclause 14.3.2.68.
See subclause 14.3.10.2 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.2.23 Request_Device_Triggering
|
API operation name: Request_Device_Triggering
Description: Requesting device triggering.
Known Consumers: VAL server.
Inputs: See subclause 14.3.2.69
Outputs: See subclause 14.3.2.70
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.3 SS_EventsMonitoring API
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.3.1 Subscribe_Monitoring_Events
|
API operation name: Subscribe_Monitoring_Events
Description: Subscription to monitoring events.
Known Consumers: VAL server.
Inputs: See subclause 14.3.2.17
Outputs: 14.3.2.18.
See subclause 14.3.6.2 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.3.2 Notify_Monitoring_Events
|
API operation name: Notify_Monitoring_Events
Description: Notifying the VAL server with monitoring events related to VAL UE(s).
Known Consumers: VAL server.
Inputs: See subclause 14.3.2.19
Outputs: None.
See subclause 14.3.6.3 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.4 SS_NetworkResourceMonitoring API
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.4.1 General
|
API description: This API enables the VAL server to monitor a network resource and to retrieve monitoring data.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.4.2 Subscribe_Unicast_QoS_Monitoring operation
|
API operation name: Subscribe_Unicast_QoS_Monitoring
Description: Subscribing to QoS monitoring of a unicast resource.
Known Consumers: VAL server.
Inputs: See subclause 14.3.2.20
Outputs: See subclause 14.3.2.21
See subclause 14.3.3.4.1 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.4.3 Notify_Unicast_QoS_Monitoring operation
|
API operation name: Notify_Unicast_QoS_Monitoring
Description: Notification of latest QoS data of a monitored unicast resource.
Known Consumers: VAL server.
Inputs: See subclause 14.3.2.22
Outputs: See subclause 14.3.2.22
See subclause 14.3.3.4.2 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.4.4 Unsubscribe_Unicast_QoS_Monitoring operation
|
API operation name: Unsubscribe_Unicast_QoS_Monitoring
Description: Unsubscribing from QoS monitoring of a unicast resource.
Known Consumers: VAL server.
Inputs: See subclause 14.3.2.20
Outputs: See subclause 14.3.2.21
See subclause 14.3.3.4.3 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.4.5 Obtain_Unicast_QoS_Monitoring_Data operation
|
API operation name: Obtain_Unicast_QoS_Monitoring_Data
Description: Request QoS monitoring data of a unicast resource.
Known Consumers: VAL server.
Inputs: See subclause 14.3.2.33
Outputs: See subclause 14.3.2.34
See subclause 14.3.3.4.4 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.4.4.6 Update_Unicast_QoS_Monitoring_Subscription operation
|
API operation name: Update_Unicast_QoS_Monitoring_Subscription
Description: Updates the QoS monitoring subscription of a unicast resource.
Known Consumers: VAL server.
Inputs: See subclause 14.3.2.38
Outputs: See subclause 14.3.2.39
See subclause 14.3.3.4.5 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
15 Service-based interface representation of the functional model for SEAL services
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
15.1 General
|
The functional models for SEAL services is represented using functional entities and reference points between the functional entities as specified in subclause 6. The vertical applications consume the SEAL services in the form of APIs. Each SEAL service offers these APIs on a service-based interface to all its consumer entities.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
15.2 Functional model representation
|
Figure 15.2-1 illustrates the service-based interface representation of the functional model for SEAL services.
Figure 15.2-1: SEAL generic functional model representation using service-based interfaces
The SEAL function(s) exhibit the service-based interfaces which are used for providing and consuming SEAL services. The service APIs are specified for each SEAL function enabled over the service-based interface. The service-based interfaces of specific SEAL services are specified in this document. All the interactions with SEAL are governed based on the reference point interactions of the functional models specified in subclause 6. VAL function represents the functionalities of the VAL server.
NOTE: The service-based interface Sval for the VAL function is out of scope of the present document.
The service APIs offered by the SEAL function(s) are published and discovered on the CAPIF core function as specified in 3GPP TS 23.222 [8].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
15.3 Service-based interfaces
|
Table 15.3-1 specifies the service-based interfaces supported by SEAL.
Table 15.3-1: Service-based interfaces supported by SEAL
Service-based interface
Application functionEntity
Mapping server entity
APIs offered
Slm
Location management function
Location management server
Specified in subclause 9.4
Sgm
Group management function
Group management server
Specified in subclause 10.4
Scm
Configuration management function
Configuration management server
Specified in subclause 11.4
Sim
Identity management function
Identity management server
Specified in subclause 12.4
Skm
Key management function
Key management server
Specified in subclause 13.4
Snrm
Network resource management function
Network resource management server
Specified in subclause 14.4
Snsce
Network slice capability enablement function
Network slice capability enablement server
Specified in 3GPP TS 23.435 [40]
Sdd
Data delivery function
Data delivery server
Specified in 3GPP TS 23.433 [48]
Cccf
CAPIF core function
Not applicable
Specified in subclause 10 of 3GPP TS 23.222 [8]
Snm
Notification management function
Notification management server
Specified in subclause 17.4
Sadae
Application data analytics enablement function
Application data analytics enablement server
Specified in 3GPP TS 23.436 [49]
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
16 Network slice capability enablement
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
16.1 General
|
The network slice capability enablement is a SEAL service that offers network slice capability enablement capabilities, such as support for vertical application to slice re-mapping (which can be defined as the mapping of the UEs running a vertical application to different slice), to one or more vertical applications. The NSCE service provides additional functionality and exposes slice capabilities based on 5GS management system services (e.g. MnS services) and 5GS network services (e.g. NEF APIs, NWDAF APIs, NSACF APIs). The detailed specification of NSCE is provided in 3GPP TS 23.435 [40].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
16.2 Functional model
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
16.2.1 General
|
The functional model for the network slice capability enablement is specified in 3GPP TS 23.435 [40].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
16.2.2 Void
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
16.2.3 Void
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
16.2.4 Void
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
16.3 Procedures and information flows for network slice capability enablement
|
The Procedures and information flows for the network slice capability enablement are specified in 3GPP TS 23.435 [40].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
16.4 SEAL APIs for network slice capability enablement
|
The SEAL APIs for the network slice capability enablement are specified in 3GPP TS 23.435 [40].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
17 Notification Management
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
17.1 General
|
The notification management is a SEAL service that offers the notification functionality to one or more verticals. This service enables VAL clients to subscribe and receive notifications from the VAL servers and thereby offloading the complexity of delivery and reception of notifications to the enabler layer. It provides common notification delivery service to vertical applications.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
17.2 Functional model
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
17.2.1 General
|
The functional model for the notification management is based on the generic functional model specified in clause 6.2. It is organized into functional entities to describe a functional architecture which addresses the notification management aspects required for vertical applications. Since the notification management is a feature which considers the Uu interfaces, only the on-network functional model is specified in this clause.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
17.2.2 Functional model description
|
Figure 17.2.2-1 illustrates the generic functional model for notification management.
Figure 17.2.2-1: Functional model for notification management
The notification management client communicates with the notification management server over the NM-UU reference point. The notification management client provides the support for notification management functions to the VAL client(s) over NM‑C reference point. The VAL server(s) communicates with the notification management server over the NM-S reference point for delivering the notification messages which is targeted for the VAL client(s). Notification management server sends these notification messages to the notification management client either through NM-UU interface for direct delivery (e.g. Long-polling, WebSocket) or through the OEM PUSH server for indirect delivery (e.g. FCM, APNS, OMA PUSH) which is implementation specific and outside the scope of this specification.
NOTE: Notification messages from PUSH notification server to the PUSH notification client are delivered either through 3GPP network system or through any non-3GPP system, which is implementation specific.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
17.2.3 Functional entities description
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
17.2.3.1 General
|
The functional entities for notification management service are described in the following subclauses.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
17.2.3.2 Notification Management client
|
The notification management client functional entity acts as the application client for notification management aspects. It interacts with the notification management server. It handles the notification messages received from the notification management server and deliver it to the corresponding VAL clients residing on the VAL UE.
The notification management client functional entity is supported by the HTTP client functional entities of the signalling control plane.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
17.2.3.3 Notification Management server
|
The notification management server is a functional entity that handles the notification management aspects by interacting with the notification management client and the VAL servers. The notification management server receives the notification messages from the vertical application layer and delivers it to the notification management client. The notification management server acts as CAPIF's API exposing function as specified in 3GPP TS 23.222 [8].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
17.2.4 Reference points description
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
17.2.4.1 General
|
The reference points for the functional model for notification management are described in the following subclauses.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
17.2.4.2 NM-UU
|
The interactions related to notification management functions between the notification management client and the notification management server are supported by NM-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
|
17.2.4.3 NM-C
|
The interactions related to notification management functions between the VAL client(s) and the notification management client within a VAL UE are supported by NM-C reference point.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
17.2.4.4 NM-S
|
The interactions related to notification management functions between the VAL server(s) and the notification management server are supported by NM-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
|
17.3 Procedures and information flows for notification management
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
17.3.1 General
|
This sub-clause describes the procedure and information flows for notification management service. The notification management procedures apply to on-network VAL service only.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.