hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.4.7.2 Procedure
| Figure 14.3.4.7.2.-1 illustrates a procedure in which the NRM client notifies the NRM server about an MBMS suspension decision in RAN.
The NRM server can decide on a subset of all VAL UEs in the MBMS broadcast area that shall report on MBMS bearer suspension. When the NRM server makes the decision of the VAL UE subset... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.4.8 MBMS bearer event notification
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.4.8.1 General
| The NRM server is an instantiation of a GCS AS. For the NRM server to know the status of the MBMS bearer, and thus know the network's ability to deliver the VAL service, it is required that the network provides MBMS bearer event notifications to the NRM server. The different events notified to the NRM server include th... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.4.8.2 Procedure
| The procedure in figure 14.3.4.8.2-1 shows notification information flows from NRM server to BM-SC.
Figure 14.3.4.8.2-1: MBMS bearer event notification
1. The NRM server activates an MBMS bearer. The activation of the MBMS bearer is done on the MB2-C reference point and according to 3GPP TS 23.468 [16].
2. The BM... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.4.9 Switching between MBMS bearer and unicast bearer
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.4.9.1 General
| The NRM server monitors the bearers used for VAL service communications and decides to switch between MBMS and unicast bearers.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.4.9.2 Procedure
| Figure 14.3.4.9.2-1 shows the procedure for service continuity when a UE is about to move out of MBMS coverage or getting into good MBMS coverage by switching between MBMS bearer and unicast bearer.
Pre-condition:
- It is assumed that a bearer (unicast or MBMS) has been activated by the VAL server for downlink deliv... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.5 QoS/resource management for network-assisted UE-to-UE/VN group communications
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.5.1 General
| This feature provides the SEAL NRM support for coordinated QoS/resource management for network assisted UE-to-UE communications. Such capability may be required for guaranteeing end-to-end QoS fulfilment (primarily for meeting end-to-end latency requirements) in network assisted UE to UE communications and may accommod... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.5.2 QoS/resource management capability initiation in network assisted UE-to-UE communications
| This procedure provides a mechanism for initiating the capability at the NRM server for managing the end-to-end application QoS requirement fulfilment for a network-assisted VAL UE to VAL UE session (comprising a PDU session for each of the constituent links, e.g. VAL UE 1 to PLMN, and PLMN to VAL UE 2). The request ma... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.5.2.1 Procedure for a single pair of UEs
| Figure 14.3.5.2.1-1 illustrates the procedure where the NRM server is initiating the end-to-end QoS/resource management capability for network-assisted UE-to-UE communications for a single pair of UEs.
Pre-conditions:
1. The NRM client is connected to the NRM server.
2. The VAL UEs involved in the end-to-end sessio... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.5.2.2 Procedure for a group of UEs
| Figure 14.3.5.2.2 illustrates the procedure where the NRM server is initiating the end-to-end QoS/resource management capability for network-assisted UE-to-UE communications for a group of UEs.
Pre-conditions:
1. The NRM client is connected to the NRM server.
2. The VAL UEs involved in the end-to-end session (VAL U... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.5.3 Procedure for coordinated QoS provisioning operation in network assisted UE-to-UE communications
| This procedure provides a mechanism for ensuring the end-to-end application QoS requirement fulfilment for the application service (which is between two or more VAL UEs), considering that the QoS of one of the links may downgrade. It is assumed that the application session is ongoing, and both the source and target VAL... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.5.3.1 Procedure for a single pair of UEs
| Figure 14.3.5.3.1-1 illustrates the procedure where the NRM server supports the coordinated QoS provisioning for network-assisted UE-to-UE communications for a single pair of UEs.
Pre-conditions:
1. NRM server has activated the end-to-end QoS/resource management capability, as described in 14.3.5.2.1
2. NRM serve... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.5.3.2 Procedure for a group of UEs
| Figure 14.3.5.3.2 illustrates the procedure where the NRM server supports the coordinated QoS provisioning for network-assisted UE-to-UE communications.
Pre-conditions:
1. NRM server has activated the end-to-end QoS/resource management capability, as described in 14.3.5.2.1
2. NRM server, acting as AF, has register... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.5.4 Application QoS coordination for Mobile Metaverse Services in distributed VAL servers
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.5.4.1 General
| This clause provides a mechanism for application session QoS coordination for mobile metaverse (MM) services where these services are offered by more than one VAL server.
It is assumed that the MM service consists of the following VAL sessions which can be present for multi-user interactions. The sessions may include ... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.5.4.2 Procedure on application QoS coordination for Mobile Metaverse Services
| Figure 14.3.5.4.1-1 illustrates the procedure where the NRM server is supporting application QoS coordination for the VAL sessions within a MM Service.
Pre-conditions:
1. The NRM clients are connected to the NRM server.
2. The VAL servers are connected to the NRM server.
3. The VAL sessions which are coupled to s... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.6 Event Monitoring
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.6.1 General
| The VAL server utilizes the NRM server for monitoring the events related to its VAL UEs and receive the event reports. The NRM server shall subscribe to multiple core network services to fetch all the required events related to the multiple VAL UEs served by the VAL server and report the same to the VAL server with the... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.6.2 Monitoring Events Subscription Procedure
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.6.2.1 General
| The VAL server subscribes to the NRM server to monitor the events related to VAL UE(s). Based on the VAL server request, the NRM server consumes the relevant core network services to receive the events related to the VAL UE(s). The related procedure is illustrated in the next clause.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.6.2.2 Procedure
| The procedure for VAL server subscribing to the NRM server, to monitor the VAL UE(s) related events is described in figure 14.3.6.2.2-1.
Pre-conditions:
- The NRM server is authorized to consume the core network services (Monitoring events as specified in 3GPP TS 23.502 [11] and Analytics services as specified in 3GP... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.6.3 Monitoring Events Notification Procedure
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.6.3.1 General
| The NRM server receives the events related to VAL UE(s) from the 3GPP core network. The NRM server reports the monitoring events information to the VAL server.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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 Notificatio... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.7 5G TSC resource management procedures
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.7.1 General
| The procedures related to the 5G TSC network resource management are described in the following subclauses.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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 ... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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 it... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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 identi... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.8 TSN resource management procedures
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.8.1 General
| The procedures related to the TSN network resource management are described in the following subclauses.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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 de... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.9 Establishing communication with application service requirements
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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-... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.9.2 Procedures
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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 provid... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.9.2.3 Procedure for establishing communication in Situational Awareness use case
| As described in Annex F, in Mobile Metaverse (MMeta) for 5G-enabled Traffic Flow Simulation and Situational Awareness use case and requirements as specified in 3GPP TS 22.156 [61], real-time information and data about the real objects can be delivered to the virtual objects of the road infrastructure and traffic partic... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.10 AF influence URSP procedure for reliable transmission
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.10.1 General
| The procedures related to the AF influence URSP for reliable transmission are described in the following subclauses.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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)... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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 conn... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.12 UE unified traffic pattern and monitoring management
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 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 th... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.12.4 Management and 5GC exposure procedures
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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 fo... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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, ... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.13 Background Data Transfer configuration
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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 ba... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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 [... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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 t... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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 t... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.14 Device triggering
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.15 Power saving configuration
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.15.1 General
| This clause discusses the possibility for the VAL server or VAL client (via the NRM server or NRM client, respectively) to influence the power saving configurations of a VAL UE(s), e.g., by configuring their DRX and eDRX parameters, through e.g., CpProvisioning, NpConfiguration and/ or MonitorEvent APIs to meet the app... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.15.2 VAL server triggers power saving configuration
| Figure 14.3.15.2-1 describes the procedure when the VAL server triggers power saving assist service for power saving in IoT devices.
Figure 14.3.15.2-1: Procedure for VAL server triggers power saving assist service
1. VAL server requests the NRM Server to assist power saving of the VAL user(s) that are part of VAL... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.15.3 VAL client triggers power saving configuration
| Figure 14.3.15.3-1 describes the procedure when the VAL client triggers power saving assist service for power saving in IoT devices.
Figure 14.3.15.3-1: Procedure for VAL client triggers power saving assist service
0. VAL Server may interact with VAL UE(s) that are part of VAL Service for power saving request.
1... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.4 SEAL APIs for network resource management
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.4.2 SS_NetworkResourceAdaptation API
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
14.4.2.2a Reserve_Network_Resource_Modify operation... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.4.2.3 Void
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.4.2.4 Void
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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 ope... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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 o... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.4.3 SS_EventsMonitoring API
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.4.4 SS_NetworkResourceMonitoring API
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.