Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.434  Word version:  18.1.0

Top   Top   Up   Prev   Next
0…   4…   6…   6.4…   6.5…   7…   8…   8.2.2…   9…   9.3…   9.3.6…   9.4…   10…   10.3…   10.3.2.22…   10.3.3…   10.3.7…   10.4…   11…   11.3…   12…   13…   14…   14.3…   14.3.3…   14.3.3.3…   14.3.4…   14.3.4.6…   14.4…   15…   A…

 

14.3.3.3  Unicast resource management without SIP corep. 142

14.3.3.3.1  Network resource adaptationp. 142
14.3.3.3.1.1  Generalp. 142
This subclause describes the procedure for network resource adaptation using PCC procedures. This procedure satisfies the requirements for requesting unicast resources and modification to already allocated unicast resources to VAL communications.
14.3.3.3.1.2  Procedurep. 142
Figure 14.3.3.3.1.2-1 illustrates the procedure for the network resource adaptation.
Reproduction of 3GPP TS 23.434, Fig. 14.3.3.3.1.2-1: Network resource adaptation
Up
Step 1.
The VAL server sends a network resource adaptation request to the NRM server for one or more users belonging to one or more VAL services, and may comprise one or more VAL UEs that will have updated resource requirement. This requirement may be in the form of exact resources /resource pools to be used or indication of bandwidth increase/decrease for the corresponding VAL UEs or set of VAL UEs.
Step 2.
The NRM server processes the request and applies / enforces the resource adaptation per VAL UE.
Step 3.
The NRM server retrieves UE IP address by using event monitoring capability for PDU session status (or PDN connectivity status) and initiates the PCC procedures for each VAL UE.
Step 4.
The NRM server provides a network resource adaptation response to the VAL server, providing information on the fulfilment of the network resource adaptation request. This will include information either per VAL UE or per set of VAL UEs, as indicated by the request of the VAL server in step 1.
Up
14.3.3.3.2  Request for unicast resources at VAL service communication establishmentp. 143
14.3.3.3.2.1  Generalp. 143
The procedure defined in this subclause specifies how network resources are requested at VAL service communication establishment. If concurrent sessions are used the NRM server may utilize the capability of resource sharing specified for underlying network policy and charging functions. The request for resources includes application type, bandwidth, priority, application identifier and resource sharing information.
14.3.3.3.2.2  Procedurep. 143
The procedure is generic to any type of session establishment that requires requests for network resources.
Procedures in Figure 14.3.3.3.2.2-1 are the signalling procedures for the requesting resource at session establishment.
Pre-condition:
  • The VAL client has requested VAL service communication with the VAL server.
  • Reproduction of 3GPP TS 23.434, Fig. 14.3.3.3.2.2-1: Resource request at VAL service communication establishment
    Up
    Step 1.
    The VAL server sends request for resources to the NRM server.
    Step 2.
    The NRM server evaluates the need for network resources and use of resource sharing.
    Step 3.
    PThe NRM server retrieves UE IP address by using event monitoring capability for PDU session status (or PDN connectivity status), and then PCC procedures are initiated from NRM server.
    Step 4.
    The NRM server sends a resource response to the VAL server.
    Step 5.
    The VAL service communication is established, and resources have been allocated.
    14.3.3.3.3  Request for modification of unicast resourcesp. 143
    14.3.3.3.3.1  Generalp. 143
    To modify unicast resources, the NRM server shall send a resource modification request containing the parameters to be modified for the UE.
    Possible scenarios when this procedure may be used are:
    • Modify the allocation and retention priority for unicast resources;
    • Release and resume resources in-between VAL service communications; or
    • Release and resume resources when a UE is able to receive the VAL service communications over multicast transmission
    14.3.3.3.3.2  Procedurep. 144
    Procedures in Figure 14.3.3.3.3.2-1 are the signalling procedures for the modification of a unicast:
    Pre-condition:
  • A VAL service communication is already in progress;
  • Reproduction of 3GPP TS 23.434, Fig. 14.3.3.3.3.2-1: Bearer modification request
    Up
    Step 1.
    The VAL server sends a resource modification request to the NRM server.
    Step 2a.
    The NRM server decides to modify the parameters of a unicast bearer.
    Step 2b.
    If the media bearer modification is not required, the NRM server sends a resource modification response to the VAL server.
    Step 3.
    PCC procedures are initiated from NRM server.
    Step 4.
    The NRM server sends a resource modification response to the VAL server.
    Step 5.
    The VAL service communication continues with the modified unicast resources.
    Up

    14.3.3.4  Unicast QoS monitoring |R17|p. 145

    14.3.3.4.1  Unicast QoS monitoring subscription procedurep. 145
    14.3.3.4.1.1  Generalp. 145
    This subclause describes the high level procedure for unicast QoS monitoring subscription. This procedure satisfies the requirements for monitoring of unicast QoS for already allocated unicast resources to VAL communications.
    14.3.3.4.1.2  Procedurep. 145
    Figure 14.3.3.4.1.2-1 illustrates the high level procedure for unicast QoS monitoring subscription.
    Pre-conditions:
    • The VAL UE has an established connection in the 5GS
    Reproduction of 3GPP TS 23.434, Fig. 14.3.3.4.1.2-1: Unicast QoS monitoring subscription
    Up
    Step 1.
    The VAL server sends a unicast QoS monitoring subscription request to the NRM server either in conjunction with a request for unicast network resources requiring QoS or when the unicast QoS connection is already established. The NRM server checks if the VAL server is authorized to initiate the unicast QoS monitoring request for the requested target VAL UEs, VAL group ID, or VAL stream IDs.
    Step 2.
    The NRM server interacts with the NEF to establish relevant QoS monitoring subscriptions. The NRM server uses the NEF procedures for the AFsessionWithQoS described in clause 5.2.6.9 of TS 23.502 and the NEF procedures for the AnalyticsExposure described in clause 5.2.6.16 of TS 23.502 and in particular the UE Communication Analytics described in clause 6.7.3 of TS 23.288 and DN Performance Analytics described in clause 6.14 of TS 23.288. Based on the input received from the VAL server in step 1, the NRM server determines the relevant NEF subscription procedures and the parameters for these subscriptions, such as the QoS parameters to be measured (e.g. packet delay, data rate, traffic volume), the frequency of reporting etc. For the frequency of reporting which can be event triggered, periodic, or when the PDU Session is released, the NRM server determines the following:
    1. if the reporting frequency is event triggered:
      1. the corresponding reporting threshold to each QoS parameter;
      2. minimum waiting time between subsequent reports;
    2. if the reporting frequency is periodic, the reporting period.
    Step 3.
    The NRM server responds with a unicast QoS monitoring subscription response indicating the subscription status.
    Up
    14.3.3.4.2  Unicast QoS monitoring notification procedurep. 146
    14.3.3.4.2.1  Generalp. 146
    This subclause describes the high level procedure for unicast QoS monitoring notification.
    14.3.3.4.2.2  Procedurep. 146
    Figure 14.3.3.4.2.2-1 illustrates the high level procedure of unicast QoS monitoring notification event.
    Pre-conditions:
    • The VAL server has an active unicast QoS monitoring subscription with the NRM server
    Reproduction of 3GPP TS 23.434, Fig. 14.3.3.4.2.2-1: Unicast QoS monitoring notification procedure
    Up
    Step 1.
    The NRM server receives QoS monitoring data by means of notifications provided by the NEF. The NRM server coordinates and combines the information from the NEF notifications and determines whether to send a notification to the VAL server based on the VAL server subscription's frequency of reporting. For a VAL group or a list of VAL UEs, the NRM server aggregates QoS monitoring data for each UE belonging to the group or the list; for a VAL stream, the NRM server aggregates the QoS monitoring data for the stream. The NRM server stores the QoS monitoring data as needed for later retrieval.
    Step 2.
    The NRM server sends a unicast QoS monitoring notification including the measured QoS data to the VAL server. If the reporting termination criteria is met (e.g. number of reports reached, threshold reached), NRM server shall also terminate the subscription.
    Up
    14.3.3.4.3  Unicast QoS monitoring subscription termination procedurep. 146
    14.3.3.4.3.1  Generalp. 146
    This subclause describes the high level procedure for unicast QoS monitoring subscription termination.
    14.3.3.4.3.2  Procedurep. 146
    Figure 14.3.3.4.3.2-1 illustrates the high level procedure of unicast QoS monitoring subscription termination.
    Pre-conditions:
    • The VAL server has an active unicast QoS monitoring subscription with the NRM server
    Reproduction of 3GPP TS 23.434, Fig. 14.3.3.4.3.2-1: Unicast QoS monitoring subscription termination procedure
    Up
    Step 1.
    When the VAL server decides to terminate a unicast QoS monitoring subscription, it sends a QoS monitoring unsubscribe request to the NRM server.
    Step 2.
    The NRM server interacts with the NEF to terminate the related QoS monitoring subscriptions.
    Step 3.
    The NRM server sends a QoS monitoring unsubscribe response to the VAL server.
    14.3.3.4.4  Unicast QoS monitoring data retrieval procedurep. 147
    14.3.3.4.4.1  Generalp. 147
    This subclause describes the high level procedure for unicast QoS monitoring data retrieval.
    14.3.3.4.4.2  Procedurep. 147
    Figure 14.3.3.4.4.2-1 illustrates the high level procedure of unicast QoS monitoring data retrieval.
    Reproduction of 3GPP TS 23.434, Fig. 14.3.3.4.4.2-1: Retrieval of unicast QoS monitoring data
    Up
    Step 1.
    The VAL server sends a unicast QoS monitoring data request to the NRM server specifying the details of the requested data and the time period of interest. The NRM server checks if the VAL server is authorized to initiate the unicast QoS monitoring data request for the requested target VAL UEs, VAL group ID, or VAL stream IDs.
    Step 2.
    The NRM server determines if it has the requested data stored internally or whether it needs to interact with the NEF to fetch the data using the AnalyticsExposure described in clause 5.2.6.16 of TS 23.502 and in particular the UE Communication Analytics described in clause 6.7.3 of TS 23.288 and DN Performance Analytics described in clause 6.14 of TS 23.288. The NRM server collects and processes the collected data to match the measurement data requirement provided in the VAL server request.
    Step 3.
    The NRM server responds with a unicast QoS monitoring data response with the requested data or with a failure indication, and optionally the cause of the failure, in case the requested data is not available.
    Up

    Up   Top   ToC