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, consideration shall be taken to the location of the VAL UEs, since VAL UEs' location is dynamically changed. This means that the MBMS suspension reporting instruction may need to be updated regularly based on the VAL UEs mobility.
Pre-condition:
- It is assumed that there is at least one active MBMS bearer
Figure 14.3.4.7.2-1: MBMS suspension notification
1. The NRM server sends an MBMS suspension reporting instruction to the NRM client.
NOTE: This message may be included in the MBMS bearer announcement message and may be sent both on a unicast bearer and a multicast bearer.
2. RAN decides to suspend the MBMS bearer, according to existing procedures in 3GPP TS 36.300 [23].
3. An MBMS suspension indication is sent in the MSI (MCH Scheduling Information), according to existing procedures in 3GPP TS 36.300 [23].
4. The NRM client detect the MBMS suspension and sends an MBMS suspension report.
5. Based on the MBMS suspsension report received, the NRM server determines whether to switch to a new bearer (unicast or MBMS). If NRM server determines to switch to unicast bearer, then the NRM server sends the user plane delivery mode message to VAL server , and the VAL server sends the downlink data over the new bearer.
The NRM client that is not instructed to send an MBMS suspension report shall still detect the MBMS suspension indication from RAN (step 3). A NRM client shall in this case not send other types of report (e.g. MBMS listening reports).
The same procedure can be applied at MBMS resumption or other MBMS events that may be detected by the NRM client.
|
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 the MBMS bearer start result (e.g. when the first cell successfully allocated MBMS resources), including information if any cells fail to allocate MBMS resources to a specific MBMS bearer.
|
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 BMSC will respond to the activation with an Activate MBMS bearer response message, according to 3GPP TS 23.468 [16].
3. The EPC and RAN will initiate the MBMS session start procedure according to 3GPP TS 23.246 [17]. This procedure is outside the scope of this specification.
4a. At the first indication of a successful MBMS session start procedure, the BM-SC sends a MBMS bearer event notification, indicating that the MBMS bearer is ready to use.
4b. The NRM server notifies user plane delivery mode to the VAL server.
5. The VAL server starts to use the MBMS bearer according to the MBMS procedures in this specification.
6. The NRM server may decide, based on the received events (e.g., any cells fail to allocate MBMS resources to a specific MBMS bearer), to switch to unicast transmission for relevant VAL UEs.
|
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 delivery.
Figure 14.3.4.9.2-1: Switching between MBMS delivery and unicast delivery
1. The VAL UE detects changing MBMS bearer condition (good or bad MBMS coverage) for the corresponding MBMS service. The method to detect is implementation specific.
2. The NRM client notifies the NRM server about the MBMS bearer condition for the corresponding MBMS service by sending the MBMS listening status report.
NOTE 1: To efficiently notify the NRM server, e.g., when the NRM client detects that the reception quality of the MBMS bearer is decreasing or reaching an insufficient quality level for the reception of VAL services, the NRM client proactively may send to the NRM server a MBMS listening status report including the MBMS reception quality level.
3. The NRM server makes the decision to switch between MBMS delivery and unicast delivery based on available information at the NRM server including the MBMS listening status report as described in clause 14.3.4.5. The NRM server notifies a user plane delivery mode to the VAL server.
4. The VAL server sends the downlink data over the new bearer (unicast or MBMS) to the VAL client as per step 3.
NOTE 2: The new bearer (unicast or MBMS) may be set up on demand after step 3 or before.
5. During the switching, the VAL client simultaneously receives downlink data through both bearers (unicast bearer and MBMS bearer). If there is no downlink data to the VAL client, this step can be skipped.
6. The VAL client ceases to receive the downlink data through previous bearer but continues receiving data through new bearer.
14.3.4A Multicast resource management for 5GS
14.3.4A.1 General
This subclause defines information flows and procedures for 5G MBS usage that applies to VAL services. 5G MBS session can be used by any VAL service for any VAL service group.
The main purpose of using 5G Multicast-Broadcast Service (MBS) by verticals is to provide efficient downlink delivery of user traffic in VAL service group communications or in a certain area.
Multicast and broadcast communication services in 5G for vertical applicationsrely on the creation and establishment of MBS sessions to deliver user data in downlink. Shared and individual delivery from the VAL server to multiple VAL users is supported either as point-to-point or point-to-multipoint over the radio. The MBS session which consist of one or multiple QoS flows for different service requirements are either broadcast or multicast type. For the broadcast MBS session or local MBS session, the MBS service area is configured with the MBS session.
NOTE 1: Support of MBS and specific session types is an implementation choice.
Within this arrangement, the VAL server decides whether to create broadcast or multicast MBS sessions to be associated with certain VAL service groups or area. The 5GC adaptively decides whether to deliver the MBS traffic from the MB-UPF in the form of shared delivery or individual delivery, where the latter is applicable to multicast MBS sessions. The NG-RAN decides to utilize point-to-point or point-to-multipoint delivery methods applicable for shared delivery only. MBS provides reliability enhancements and minimizes loss of information, e.g., due to mobility and handover.
MBS group scheduling mechanism enables simultaneous reception of MBS and unicast user traffic by the VAL UEs. The UEs can receive broadcast MBS sessions irrespective of their RRC state (i.e., connected, inactive or idle) and multicast sessions in RRC‑CONNECTED state and RRC_INACTIVE state.
The following capabilities (non-exhaustive list) provided by MBS could be used by NRM server:
- MBS session creation;
- MBS session update;
- MBS session release;
- MBS session ID allocation;
- Dynamic PCC control for MBS session.
The first phase to utilize MBS sessions for VAL media transmission is to reserve the network resource by creating a MBS sessions. The MBS session creation is initiated by the VAL server towards the NRM server, and the NRM server further interacts with the 5GS to complete the whole process. The UE's capabilities and service related information e.g., UE's MBS capabilities, location, MBS listening status report, UE session join notification sent by group members are considered when deciding to create or use MBS sessions. During the interaction with NRM server, the necessary information related to the requested session is determined, e.g., MBS session mode (either a broadcast or a multicast session) and the required service profile. This interaction between the NRM server and the 5GS depends on the configuration option under consideration, i.e., whether the NRM server is in trusted domain (limited operations), and whether the session creation is done with or without a dynamic PCC rule.
NOTE 1: It is implementation specific whether the VAL server decides to use multicast or broadcast MBS sessions.
NOTE 2: It is implementation specific whether the VAL decides to create (one or multiple) MBS sessions for VAL media for VAL group communications associated to a certain VAL group or create (one or multiple) dynamic MBS sessions once the need has emerged, e.g., dynamic MBS sessions to be associated for an ad hoc group.
NOTE 3: It is implementation specific whether an MBS session is associated to one or multiple VAL service groups, and whether it is re-assigned to other VAL service groups.
NOTE 4: How the NRM server uses the UE's capabilities and service related information in order to create and use the MBS session is implementation specific.
The information elements describing the MBS session under consideration is then sent to the NRM clients via MBS session announcement, where the latter need to react according to the announced session mode.
If eMBMS and 5G MBS co-exist for VAL services, the NRM service server may decide to trigger the establishment of an eMBMS bearer to deliver the VAL media associated to the VAL service group communications, if the target VAL service group(s) consists of members with MBMS capable RAT. As a result, the NRM server subsequently needs to send an eMBMS bearer announcement towards the clients camping on LTE.
NOTE 5: It is implementation specific whether the NRM server triggers an eMBMS bearer or a unicast bearer to serve VAL clients camping on LTE.
14.3.4A.2 MBS session creation and MBS session announcement
14.3.4A.2.1 General
The procedures in this clause describe how MBS session creation and MBS session announcement can be used for the transmission of VAL service group communication data over either broadcast or multicast MBS sessions. The MBS session can either be created with or without dynamic PCC rule, where the latter requires less interaction done by the NRM server towards the 5GC (either directly or via NEF).
14.3.4A.2.2 Procedure for pre-created MBS session and MBS session announcement
Pre-conditions:
- The NRM server has decided to use an MBS session for VAL service group communications associated to a certain VAL servive group based on transport only mode.
- The NRM server has performed MB-SMF discovery and selection either directly or indirectly via NEF/MBSF, unless the corresponding information is locally configured.
- NRM clients 1 to n are attached to the 5GS, registered and belong to the same VAL service group X.
- The NRM server is aware whether to request the creation of the MBS service server with or without dynamic PCC rule.
Figure 14.3.4A.1.2-1: Use of pre-created MBS session.
1. The VAL server sends a multicast/broadcast resource request towards the NRM server including the VAL server identity, service description(s), multicast resource type (e.g,. multicast type or broadcast type), service announcement mode (i.e., service announcement is sent by NRM or the VAL itself), Endpoint of the VAL server.
2. The NRM server initiates an MBS session creation procedure towards the 5GC as described in 3GPP TS 23.247 [39]. The procedure starts once the NRM server initiates a TMGI allocation request (either directly to MB-SMF or indirectly via NEF). Upon the reception of the TMGI allocation response, the NRM server sends an MBS session creation request, including further information related to the MBS session, e.g., MBS session ID, MBS session mode and the QoS requirements if dynamic PCC rule is not considered. However, if dynamic PCC rule is considered, the NRM server defines these requirements at a later step, namely it sends an MBS authorization/policy create request towards PCF (either directly or to the NEF) indicating the QoS requirements.
In the case of an untrusted NRM server, when the requested MBS service area crosses several MB-SMF service areas, the NEF/MBSF rejects the TMGI allocation request, and it guides the NRM server by dividing the requested MBS service area into groups and returns the groups as described in 3GPP TS 23.247 [39]. Hence, the NRM server initiates a new TMGI allocation request for each grouped MBS service area. If during MBS session creation request the 5GS discovers that the MBS service area crosses several MB-SMF service areas, the request is rejected and the NEF/MBSF guides the NRM server by dividing the requested MBS service area into groups and returns the groups as described in 3GPP TS 23.247 [39]. The NRM initiates a new MBS session creation procedure for each grouped MBS service area.
The NRM server may utilize a unicast session if any MBS service area is not supported by any MB-SMF.
NOTE 1: In case of LTE eMBMS and 5G MBS co-existence, the NRM server may trigger the establishment of eMBMS bearers as described in clause 14.3.4 (or it may establish a unicast bearer) based on the RAT capabilities supported by the VAL service group members in the VAL service group X. If MBSF and BM-SC are co-located, TMGI used by 4G eMBMS can be the same as the MBS session ID.
NOTE 2: For the case of multi carrier support for broadcast MBS sessions, the NRM server may indicate the frequencies within a broadcast MBS service area by providing the MBS frequency selection area ID(s) (MBS FSA ID(s)) to the MB-SMF or indirectly via NEF.
3. The NRM server provides the NRM clients of the VAL service group X with the information related to the created MBS session via the MBS session announcement. The MBS session announcement includes information such as the MBS session ID, MBS session mode (broadcast or multicast service type) and SDP information related to the MBS session under consideration.
NOTE 3: The NRM server may send an MBS session announcement at an earlier step during the MBS session creation procedure towards the NRM clients once the VAL service group associated to the MBS session is known.
Optionally, the NRM server includes the information elements related to the established eMBMS bearer, as indicated in table 7.3.2.2-1. The NRM clients which camp on LTE will subsequently react to the information elements related to the eMBMS bearer as described in 3GPP TS 23.280 [3].
4. NRM clients store and process the received MBS session information.
5. NRM clients may provide an MBS session announcement acknowledgment to the NRM server to indicate the reception of the corresponding MBS session announcement.
6. Based on the MBS session mode (either multicast or broadcast), the following actions take place;
6a. For multicast MBS sessions, NRM clients initiate a UE session join request towards the 5GC using the information provided via the MBS session announcement. Hence, upon the first successful UE session join request, the multicast is then established, and the radio resources are reserved, if the session is in an active state. The established session can either be in active or inactive state as indicated in 3GPP TS 23.247 [39]. The NRM clients sends a UE session join notification towards the server as indicated in the MBS session announcement. If indicated in the MBS session announcement information, NRM clients report the monitoring state (i.e. the reception quality of the MBS session) back to the NRM server; or
6b. For broadcast MBS sessions, if the NRM client is accessing over 5G, the session is established as part of the session creation procedures as described in 3GPP TS 23.247 [39], and the network resources are reserved both in 5GC and NG-RAN. The NRM clients start monitoring the reception quality of the broadcast MBS session. If indicated in the MBS session announcement information, NRM clients report the monitoring state (i.e. the reception quality of the MBS session) back to the NRM server.
NOTE 4: It is implementation specific whether the MBS session reception quality level is determined per MBS session, per media stream or per MBS QoS flow level via e.g., measurements of radio level signals, such as the reference signals from the NG-RAN node(s), or packet loss.
7. The NRM clients provide a listening status notification related to the announced session (multicast or broadcast session) in the form of an MBS listening status report.
8. The NRM server provides a multicast/broadcast resource response to the VAL server.
9. An VAL service group communication setup takes place and uses the pre-created MBS session for this group communication packet DL delivery.
14.3.4A.2.3 Procedure for dynamic MBS sessions
In this scenario, the VAL service group communication is already taken place and a unicast PDU session is utilized for DL transmission. When the NRM server decides to use an MBS session for the transmission under consideration, the NRM server interacts with 5GC to reserve the necessary network resources.
NOTE 1: The NRM server logic for determining when to create a dynamic MBS session is implementation specific.
The procedure in figure 14.3.4A.2.3-1 shows one NRM client receiving the DL media. There might also be NRM clients in the same VAL service group communication session that receive the communication on a PDU session.
Pre-conditions:
- NRM client is attached to the 5GS, registered and affiliated to a certain VAL service group X.
- The NRM server is aware whether to request the creation of the MBS session with or without dynamic PCC rule.
- The NRM server has performed MB-SMF discovery and selection either directly or indirectly via NEF/MBSF, unless the corresponding information is locally configured.
- No MBS session exists, or the existing multicast MBS session fails to satisfy the QoS requirements.
Figure 14.3.4A.2.3-1: Use of dynamic MBS session.
1. An VAL service group communication session is established and the DL media packet is delivered to the VAL client via unicast.
2. The VAL server sends a multicast/broadcast resource request towards the NRM server including the VAL server identity, service description(s), multicast resource type (e.g,. multicast type or broadcast type), service announcement mode (i.e., service announcement is sent by NRM or the VAL itself), Endpoint of the VAL server.
3. The NRM server decides to create an MBS session. The MBS session creation procedure takes place as described in clause 14.3.4A.2.2.
NOTE 2: In case of LTE eMBMS and 5G MBS co-existence, the NRM server may trigger the establishment of eMBMS bearers as described in 3GPP TS 23.280 [3] (or it may establish a unicast bearer) based on the RAT capabilities supported by the affiliated members in the VAL service group X. If MBSF and BM-SC are co-located, TMGI used by 4G eMBMS can be the same as the MBS session ID.
NOTE 3: For the case of multi carrier support for broadcast MBS sessions, the NRM server may indicate the frequencies within a broadcast MBS service area by providing the MBS frequency selection area ID(s) (MBS FSA ID(s)) to the MB-SMF or indirectly via NEF.
4. The NRM server provides the NRM client with the information related to the created MBS session via an MBS session announcement. As described in table 7.3.2.2-1, the session announcement includes information such as the MBS session ID, MBS session mode (broadcast or multicast service type), and SDP information related to the MBS session.
Optionally, the NRM server includes the information elements related to the established eMBMS bearer once the NRM server has determined the need, as indicated in table 7.3.2.2-1. The NRM clients which camp on LTE will subsequently react to the information elements related to the eMBMS bearer as described in 3GPP TS 23.280 [3].
5. The NRM client stores the MBS session ID and other associated information.
6. The NRM client may send an MBS session announcement ack back to the NRM server.
7. Based on the MBS session mode (either multicast or broadcast), the following actions take place:
7a. For multicast MBS sessions, NRM client initiates a UE session join request towards the 5GC using the information provided via the MBS session announcement. Hence, upon the first successful UE session join request, the multicast is then established, and the radio resources are reserved, if the session is in active state. The established session can either be in active or inactive state as indicated in 3GPP TS 23.247 [39]. The NRM client sends a UE session join notification towards the server as indicated in the MBS session announcement. If indicated in the MBS session announcement information, NRM clients report the monitoring state (i.e. the reception quality of the MBS session) back to the NRM server; or
7b. For broadcast MBS sessions, if the NRM client is accessing over 5G, the session is established as part of the session creation procedures as described in 3GPP TS 23.247 [39], and the network resources are reserved both in 5GC and NG-RAN. The NRM clients start monitoring the reception quality of the broadcast MBS session. If indicated in the MBS session announcement information, NRM clients report the monitoring state (i.e. the reception quality of the MBS session) back to the NRM server.
NOTE 4: It is implementation specific whether the MBS session reception quality level is determined per MBS session, per media stream or per MBS QoS flow level via e.g., measurements of radio level signaling such as the reference signals from the NG-RAN node(s), packet loss.
8. The NRM clients provide a listening status notification related to the announced session (multicast or broadcast session) in the form of an MBS listening status report.
9. The NRM server provides a multicast/broadcast resource response to the VAL server.
10. An VAL service group communication via dynamic MBS session is established. The VAL server sends the downlink packet for the VAL service group communication session over the MBS session.
14.3.4A.3 MBS resources update
14.3.4A.3.1 General
The VAL server can create one or several MBS sessions via the NRM server, based on certain service requirements, a certain service area, or the activity status of multicast MBS sessions. However, during the life cycle of the MBS sessions, the VAL server may need to trigger the update of the sessions via the NRM server to meet emerging needs, including the service requirements, service area related parameters.
14.3.4A.3.2 Procedure for updating MBS resources without dynamic PCC rule
The procedure shown in figure 14.3.4A.3.2-1 presents an MBS session update procedure triggered by the VAL server via the NRM server (either directly interacting with the MB-SMF, or indirectly with NEF/MBSF). Within the update request, either the service requirements, MBS service area, activity status of multicast MBS session, or all three are done, as indicated in 3GPP TS 23.247 [39].
Pre-conditions:
- The NRM clients 1 to n are attached to the 5GS, registered and belong to the same active VAL service group.
- The NRM server has obtained the required information related to the MB-SMF, either locally configured or during initial session configuration.
- The MBS session is created with certain service requirements and optionally with a certain broadcast/multicast service area. The MBS session is announced to be associated with the VAL service group for group communication purposes.
Figure 14.3.4A.3.2-1: MBS session update without dynamic PCC
1. An MBS session is established as described in in 3GPP TS 23.247 [39] (either a multicast or a broadcast session), and associated with a certain active VAL service group for group communication purposes. In the case of a multicast MBS session, the NRM clients have already joined the session.
2. The VAL server invokes the multicast resource update request to the NRM server once the need has emerged to modify some aspects for the given MBS session under consideration. The updated parameters are included, e.g., service requirements, MBS service area or both. In case of multicast MBS sessions, the VAL server may as well include the status (active or inactive) of the multicast MBS session to be set.
3. The NRM server sends an MBS session update request towards the 5GC, either directly or via NEF, as described in 3GPP TS 23.247 [39], either directly or indirectly via NEF.
4. Based on the needed requirements, the corresponding MBS session is accordingly modified at the 5GS as described in 3GPP TS 23.247 [39]. The update may lead to QoS Flow(s) addition, modification, or removal.
5. The NRM server receives an MBS session update response from the 5GS either directly or via NEF once the requested modifications are performed, and the indicated MBS session is updated accordingly.
6. In case of untrusted NRM server, if the requested MBS service area crosses several MB-SMF service areas, the requested MBS service area to be updated is partially accepted by the 5GC as described in 3GPP TS 23.247 [39]. The reduced MBS service area is grouped and provided by the NEF/MBSF in the response. Hence, the NRM server sends a new MBS session creation request as described in clause 14.3.4A.1.2. for each grouped MBS service area.
7. The NRM server may initiate a session announcement towards the NRM clients associated with the ongoing session in order to announce the updated information, if required, e.g., the updated service area or SDP information.
8. The NRM server sends an MapGroupToSessionStream over the configured MBS session providing the required information to receive the media related to the established VAL service group communication.
9. The NRM clients process the received information over the MapGroupToSessionStream in order to receive the associated VAL media over the specific MBS session stream.
10. The NRM server returns the multicast resource update response to the VAL server.
11. If the MBS session creation is failed towards the grouped MBS service areas in step 6, then the NRM server indicates to the VAL server to use unicast delivery for that grouped MBS service areas via by sending the user plane delivery mode message.
12. VAL client 1 sends media to the VAL server over unicast to be distributed for the established group communication.
13. The VAL server distributes the VAL media to the VAL clients 2 to n over the indicated streams.
14.3.4A.3.3 Procedure for updating MBS resources with dynamic PCC rule
The procedure shown in figure 14.3.4A.3.3-1 presents an MBS session update procedure triggered by the NRM server to the 5GC, either directly or via NEF/MBSF. Based on the required updates to be done, the NRM server needs to interact with the MB-SMF to update the MBS service area and multicast activity status, with the PCF to update the required QoS requirements, or sequentially both to update all the above, as indicated in 3GPP TS 23.247 [39].
Pre-conditions:
- The NRM clients 1 to n are attached to the 5GS, registered and belong to the same active VAL service group.
- The NRM server has obtained the required information related to the MB-SMF, either locally configured or during initial session configuration.
- The MBS session is created with certain service requirements and optionally with a certain broadcast/multicast service area. The MBS session is announced to be associated with the VAL service group for group communication purposes.
Figure 14.3.4A.3.3-1: MBS session update with dynamic PCC
1. An MBS session is established as described in 3GPP TS 23.247 [39] (either a multicast or a broadcast session), and associated with a certain active VAL service group for group communication purposes. In the case of a multicast MBS session, the NRM clients have already joined the session.
2. The VAL server invoke the multicast resource update request to the NRM server once the need has emerged to modify some aspects for the given MBS session under consideration. The updated parameters are included, e.g., service requirements, service area or both.
3. The NRM server sends an MBS session update request towards the 5GC as described in 3GPP TS 23.247 [39], either directly or indirectly via NEF.
NOTE 1: The updated service area information is required for local MBS and for broadcast MBS services.
4. Based on the update requirements perform the MBS session is updated with PCC procedure as described in 3GPP TS 23.247 [39].
5. The NRM server receives an MBS session update response from the 5GC either directly or via NEF once the requested modifications are performed, and the indicated MBS session is updated accordingly.
6. In case of untrusted NRM server, if the requested MBS service area crosses several MB-SMF service areas, the requested MBS service area to be updated is partially accepted by the 5GC, as described in 3GPP TS 23.247 [39]. The reduced MBS service area is grouped and provided by the NEF/MBSF in the response. Hence, the NRM server sends a new MBS session creation request as described in clause 14.3.4A.1.2. for each grouped MBS service area.
7. The NRM server may initiate a session announcement towards the NRM clients associated with the ongoing session in order to announce the updated information if required, e.g., the updated service area or SDP information.
NOTE 2: The updated service area information is required for local MBS and for broadcast MBS services.
8. The NRM server sends an MapGroupToSessionStream over the MBS session providing the required information to receive the media related to the established VAL service group communication.
9. The NRM server returns the multicast resource update response to the VAL server.
10. The NRM clients process the received information over the MapGroupToSessionStream in order to receive the associated VAL media over the specific MBS session stream.
11. If the MBS session creation is failed towards the grouped MBS service areas in step 6, then the NRM server indicates to the VAL server to use unicast delivery for that grouped MBS service areas via by sending the user plane delivery mode message.
12. VAL client 1 sends media to the VAL server over unicast to be distributed for the established group communication.
13. The VAL server distributes the VAL media to the VAL clients 2 to n over the indicated streams.
14.3.4A.4 MBS resource deletion
14.3.4A.4.1 General
The VAL server can decide to release a certain MBS session once it is no longer further utilized for the associated VAL service group communication, e.g., the VAL service group is no longer active, the VAL media transmission is over and no further VAL media to be delivered, group communication is terminated. The MBS session deletion procedure leads to releasing the network resources associated to that MBS session.
NOTE: It is up to implementation of VALserver to decide whether to release the MBS session or re-use it for subsequent group operations.
To delete the MBS session, the VAL server invokes the multicast/broadcast resource release service of NRM server which further triggers the NRM server to send an MBS session deletion request to the 5GS providing the corresponding MBS session ID. The MBS session deletion request is sent to the MB-SMF (directly or via NEF/MBSF) when PCC is not used. However, if dynamic PCC rule is utilized, a policy authorization deletion request is initially sent to the PCF. Further details of the MBS session deletion are provided in 3GPP TS 23.247 [39].
NRM server further informs the NRM client with the MBS session de-announcement, so that the VAL UE stops monitoring the broadcast MBS session or leaves the multicast MBS session. This procedure is applied for both broadcast MBS session and multicast MBS session.
14.3.4A.4.2 Procedure
The procedure in figure 14.3.4A.4.2-1 describes the MBS session deletion aspects for group communication.
Pre-conditions:
- NRM clients 1 to n are attached to the 5GS, registered and affiliated to the same active VAL service group.
- An MBS session is configured to address the corresponding VAL service group with certain service requirements and optionally with a certain broadcast/multicast service area. The session is announced and established for group communication purposes for the VAL service group.
Figure 14.3.4A.4.2-1: MBS session deletion procedure.
1. The VAL server decides to delete the MBS session for the associated VAL group communication, either multicast or broadcast session.
2. The VAL server invokes the multicast/broadcast resource release service of the NRM server by sending the multicast/broadcast resource release request.
3. Upon receiving the multicast/broadcast resource release request, the NRM server sends an MBS session de-announcement message with the MBS session ID towards the NRM client(s). Upon receiving the MBS session de-announcement message, either 4a or 4b is performed.
4a. If the MBS session identified by MBS session ID is a broadcast MBS session, the UE(s) stops monitoring the broadcast MBS session and removes the broadcast MBS session related information.
4b. If the MBS session identified by MBS session ID is a multicast MBS session, the joined UE(s) initiate an MBS session leave procedure to leave the indicated MBS session in order to release the respective network resources, as defined in 3GPP TS 23.247 [39].
5. Subsequently, the NRM clients may send an MBS session de-announcement acknowledgement message to the NRM server indicating the status of MBS session.
6. The NRM server initiates the MBS session deletion procedure with the 5GC (either directly or through NEF/MBSF) in order to stop using the configured MBS session and release the corresponding network resources. The NRM server indicates within the MBS session release request the corresponding MBS session ID. The MBS session deletion procedure can either be with or without a dynamic PCC rule, as indicated in 3GPP TS 23.247 [39].
7. The NRM server returns the multicast/broadcast resource release response to the VAL server indicating the result.
14.3.4A.5 Request to activate / de-activate multicast MBS sessions
14.3.4A.5.1 General
In case of multicast MBS sessions, the members affiliated to a certain VAL service group need to initiate a UE session join request towards the 5GC in order to receive the VAL media sent via the associated MBS session. The UE session join request enables the reservation of NG-RAN resources for the members of the VAL group. However, it is not necessary that the VAL media is delivered over the whole time the multicast MBS session is associated to the group under consideration. Therefore, the VAL server is able to efficiently utilize and control the reservation of radio resources based on the availability of VAL data to be delivered via the activation and de-activation procedure with NRM server. This presents more flexibility and efficient use of resources different from LTE.
The most suitable scenario to activate/de-activate a certain multicast MBS session is based on whether there is a VAL group communication, taking place over that associated session to the VAL service group. In this manner, the VAL server can activate the associated multicast session once a VAL group communication takes place, then deactivate it once the VAL group communication is over. Whether the multicast session is activated (i.e., in an active state), or de-activated (in an inactive state), the VAL group is associated to the multicast session and its members are within a UE session join.
The activation or de-activation request is initiated by the VAL server towards the NRM server which further interacts either directly with the MB-SMF or indirectly with NEF/MBSF.
NOTE: The activation of de-activation procedure may also be triggered by MB-SMF based on receiving notification from MB-UPF based on the availability of VAL data to be transmitted.
14.3.4A.5.2 Multicast MBS session activation procedure
The procedure shown in figure 14.3.4A.5.2-1 presents the multicast MBS session activation procedure initiated by the VAL server.
Pre-conditions:
- NRM clients are attached to the 5GS, registered and affiliated to the same VAL service group X.
- The NRM server has directly performed (or via NEF/MBSF) an MB-SMF discovery and selection, unless the corresponding information is locally configured.
- The multicast MBS session for NRM group communications associated to VAL service group X.
- The MBS session is created and announced to address VAL group communication related to the associated VAL service group X with certain service requirements and optionally with a certain service area.
Figure 14.3.4A.5.2-1: Multicast MBS session activation procedure.
1. The multicast MBS session is established as the first UE session join request, which is initiated by the first VAL UE towards 5GC, is granted. At this stage, the multicast MBS session is established with an inactive state.
2. The VAL server decides to activate the multicast MBS session as VAL data is needed to be transmitted over the session to the VAL service group X, as a VAL group communication is to take place over the associated MBS session.
3. The VAL server invokes the multicast resource activation request provided by NRM server, the MBS session ID is included.
4. Upon receiving the request in step 3, the NRM server sends an MBS session activation request towards the 5GC, either directly to the MB-SMF or via NEF/MBSF, indicating the TMGI to be activated.
5. The 5GC changes the session status to "active" and finds the list of joined VAL UEs associated with the session and activates the NG- RAN resources for VAL data delivery.
6. The 5GC may send an MBS session activation response to the NRM server indicating that the requested multicast MBS session has been activated.
7. The NRM server returns the multicast resource activation response to the VAL server.
14.3.4A.5.3 Multicast MBS session de-activation procedure
The procedure shown in figure 14.3.4A.5.3-1 presents the multicast MBS session activation procedure initiated by the VAL server.
Pre-conditions:
- NRM clients are attached to the 5GS, registered and affiliated to the same VAL service group X.
- The NRM server has directly performed (or via NEF/MBSF) an MB-SMF discovery and selection, unless the corresponding information is locally configured.
- A multicast MBS session is created and announced to address the corresponding VAL service group with certain service requirements and optionally with a certain multicast service area.
- The VAL UE have already joined the multicast MBS session and are able to receive the VAL data over the associated MBS session.
Figure 14.3.4A.5.3-1: Multicast MBS session deactivation procedure.
1. The group communication associated with VAL service group X takes place, and the corresponding VAL data is delivered over the associated multicast MBS session, hence the MBS session has an active state.
2. The VAL server decides to deactivate the multicast MBS session, as no further VAL data to be delivered to the associated group, or the VAL group communication is over, and no further VAL media is to be delivered.
3. The VAL server invokes the multicast resource deactivation request provided by NRM server, the MBS session ID is included.
4. Upon receiving the request in step 3, the NRM server sends an MBS session deactivation request towards the 5GC, either directly to the MB-SMF or via NEF/MBSF, indicating the TMGI to be deactivated.
4. The 5GC changes the session state to "inactive" and deactivates the radio resources associated with the joined VAL UEs.
5. The 5GC may send an MBS deactivation response to the server indicating that the requested multicast MBS session has been inactivated.
7. The NRM server may return the multicast resource deactivation response to the VAL server.
14.3.4A.6 VAL service group media transmissions over 5G MBS sessions
14.3.4A.6.1 General
The VAL server can decide to configure an MBS session per VAL service group to transmit the media related to the corresponding VAL group communications. Such group communications can comprise different service requirements. For that, multicast and broadcast MBS sessions need to be configured with multiple MBS QoS flows to address different service requirements, e.g., different required QoS, provided by the NRM server. For instance, application-level control messages or media associated to a group communication can comprise different QoS requirements. Also, different type of group communications can comprise different QoS requirements, e.g., emergency group communication should be handled with a higher priority than normal group communication.
The configuration of multiple MBS QoS flows to address different service requirements is associated to the assignment of different streams (e.g., different ports) within an MBS session.
The established multicast MBS session can either be in active or inactive state, where the former indicates the activation of radio resources hence transmitting the VAL media to the associated VAL service group, and the latter indicates their deactivation as no VAL media is being transmitted. The VAL server may initiate the activation of multicast MBS sessions once the VAL service group is established and active, as well as once the VAL media is available for transmission. For this purpose, the VAL server sends a multicast MBS session activation request towards the NRM indicating the MBS session ID to be activated, and the NRM server further interacts with the 5GS to complete the MBS session activation.
Similar to the use of eMBMS, the NRM server shall provide the associated information between a specific group communication and the stream to be used within an MBS session to the UE. This information could be sent in advance in an MBS session announcement or could be provided on demand in an additional signalling message for the MBS session, e.g., MapGroupToSessionStream (similar to the MapGroupToBearer in eMBMS).
14.3.4A.6.2 Procedure
The procedure in figure 14.3.4A.6.2-1 describes how media related to a specific group communication can be distributed over a configured MBS session which consist of multiple QoS flows, i.e. addressing different service requirements. The procedure is applicable for both the pre-created MBS session case as described in 14.3.4A.2.2 and the dynamic MBS session case as described in 14.3.4A.2.3. For simplicity, the figure 14.3.4A.6.2-1 shows that the MBS session is pre-created prior to the group communication establishment.
Pre-conditions:
- VAL UE 1 to n are attached to the 5GS, registered and belong to the same VAL service group X.
- The VAL server has decided to use an MBS session for VAL service group communications associated to VAL service group X.
Figure 14.3.4A.6.2-1: VAL service group media transmission over MBS sessions
1. The VAL server creates a multicast or a broadcast MBS session targeting group communications associated to VAL service group X via the NRM server, as being specified in clause 14.3.4A.2. Therefore, the VAL server can provide default service requirements to be addressed by the MBS session.
The MBS session is announced by NRM server and received by NRM client 2 to n. The NRM server has identified that VAL UE 2 to n can receive media over the MBS sessions, e.g. based on a notification from NRM clients indicating the successful join of the multicast MBS session or a monitoring report of the broadcast MBS session (similar to the listening status report used for MBMS).
2. A new VAL group communication is established for the VAL service group X consisting of a specific required service requirements, e.g. a VAL service emergency group communication. The group communication setup can be done over unicast.
2a. For broadcast MBS sessions, the session is established as described in 3GPP TS 23.247 [39].
2b. For multicast MBS session, the session is established upon the acceptance of the first UE session join request initiated from the VAL UE towards the 5GS, as described in 3GPP TS 23.247 [39]. The multicast session can then have either an active or an inactive state.
3. The VAL server may initiate the multicast MBS activation towards the NRM as described in clause 14.3.4A.5 in order to activate the multicast MBS session in case the session has an inactive state.
4. Considering that the established group communication requires a specific QoS, e.g. an VALemergency group communication which requires higher priority (i.e. better ARP), the VAL server initiates an MBS session update to the NRM to provide the new required service requirements, if not done during the MBS session creation in step 1, as described in clause 14.3.4A.2. The MBS session should then be updated and an additional QoS flow may be configured.
5. The NRM server sends a MapGroupToSessionStream to NRM clients 2 to n over the configured MBS session providing the required stream information to receive the media related to the specific established VAL group communication within the MBS session.
6. NRM clients process the MapGroupToSessionStream information to receive the related media over the specific MBS session stream.
7. The NRM server sends the user plane delivery mode message to the VAL server to instruct the VAL server to switch to MBS delivery.
8. VAL client 1 sends media to the VAL server over unicast to be distributed for the established group communication.
9. The VAL server distributes the media to VAL clients 2 to n over the indicated stream within the established MBS session.
NOTE: The VAL server can stop the unicast delivery (if ongoing) towards the VAL clients considering the UE session join notification or the MBS listening status report.
10. The VAL server may initiate the multicast MBS session deactivation towards the NRM as described in clause 14.3.4A.5, in order to deactivate the multicast MBS session.
11. The NRM server may further trigger the UE to leave multicast MBS session.
14.3.4A.7 Aplication level control signalling over 5G MBS sessions
14.3.4A.7.1 Description
The VAL server may use an 5G MBS session for application level control signalling. An 5G MBS session for application level control signalling is typically used for the purposes beyond the benefit for using 5G for resource efficiency, e.g. for improved MC service performance (KPIs), handling of high load scenarios.
Similar to the usage of eMBMS, both broadcast and multicast 5MBS session for application level control signalling may be used to transmit the following messages, for example:
- MBS session announcement for media sessions
- Group application paging
- Group dynamic data (e.g. status of the group)
5G MBS session for application level control signalling is created in a service area that is larger than the estimated service for media MBS session. The service area for the media sessions is mainly based on counting of group members in each defined service area. The MBS session for application level control signalling is also created with a QoS that is better than MBS media session since the packet loss requirements are much stricter.
The NRM client shall not send responses to group-addressed application level control signalling unless instructed or configured to respond.
14.3.4A.7.2 Procedure
The procedure in figure 14.3.4A.7.2-1 shows only one of the receiving VAL UE using a 5G MBS session.
Figure 14.3.4A.7.2-1: Use of 5G MBS for application-level control signalling
1. The VAL server determines to create MBS session for application-level control signalling, the VAL server initiated the 5G MBS session establishment via the NRM is done according to clause 14.3.4A.2.
2. The NRM server passes the 5G MBS session info for the service description associated with the 5G MBS session to the NRM client. The NRM client obtains the MBS session ID, from the service description.
NOTE: For 5G MBS and 4G MBMS co-existence, the MBMS bearers activation and MBS session announcement are performed as specified in the procedure for pre-created MBS session and session announcement.
3. The NRM client stores the information associated with the MBS session ID. The NRM client uses the MBS session ID and other 5G MBS session related information to enable monitoring of the 5G MBS session by the VAL UE.
4. Steps 4 to 6 defined in clause 14.3.4A.2 are performed.
5. The VAL server transmits MC application control messages over the MBS session.
14.3.4A.8 Service continuity between 5G MBS delivery and unicast delivery
14.3.4A.8.1 General
This clause addresses the issue of VAL data delivery over MBS session, specifically, to maintain the service continuity when switching between 5G MBS delivery and unicast delivery.
14.3.4A.8.2 Service continuity for broadcast MBS session
14.3.4A.8.2.1 General
This solution provides the procedure which allows the NRM client to report the broadcast reception quality to the NRM server which is used to make the decision whether to use the unicast delivery to the VAL UE(s) which are suffering bad broadcast reception quality due to e.g., move out of the broadcast service area.
An NRM client monitors the broadcast MBS session to receive VAL data. Based on the received quality (e.g., radio level quality, RTP packet loss), the NRM client needs to inform the NRM server that the NRM client is able to receive the VAL data on the broadcast MBS session with sufficient quality or not.
This estimation of the broadcast reception quality may be dependent on, for example, the modulation and coding scheme (MCS) and measurements from the reference signals from the NG-RAN node(s), RTP packet loss, BLER of the received VAL data.
14.3.4A.8.2.2 Procedures
14.3.4A.8.2.2.1 Service continuity from broadcast to unicast
The procedure in figure 14.3.4A.8.2.2.1-1 illustrates the VAL UE which is receiving VAL data via broadcast MBS session is switched to unicast delivery because the VAL UE suffers from bad broadcast reception quality due to e.g., moving out of the broadcast service area. It shows only one of the receiving VAL UEs receiving the broadcast MBS session.
Pre-conditions:
1. The VAL group communication is ongoing and the VAL data (e.g., DL media, application layer control signalling) is transmitted via broadcast MBS session.
2. The NRM client is receiving the VAL data (e.g., DL media, application layer control signalling) via the broadcast MBS session.
3. The NRM client(s) already have the associated information (e.g., SDP) to receive the unicast delivery during the group communication establishment phase.
4. An VAL group communication session is ongoing and the DL VAL data is transmitted over broadcast MBS session.
Figure 14.3.4A.8.2.2.1-1: Service continuity from broadcast to unicast
1. The NRM client detects that it suffers bad broadcast reception due to e.g., moving out of the broadcast service area of the announced MBS session ID. The NRM client may determine the broadcast reception quality by using the BLER of the received media. When no media is received, the quality estimation can consider the reference signals and the modulation and coding scheme (MCS).
2. The NRM client sends MBS listening status report which indicates the broadcast reception quality associated with the MBS session ID is not sufficient to receive media. The NRM client may also map the determined broadcast reception quality to a broadcast reception quality level. The broadcast reception quality level indicates at which specific broadcast reception quality level the VAL data has been received.
NOTE 1: It is implementation that the broadcast reception quality level can be determined per MBS session, per media stream or per MBS QoS flow level via e.g., measurements of radio level signalling such as the reference signals from the NG-RAN node(s), packet loss.
NOTE 2: The set of MBS reception quality levels and the mapping of the determined broadcast reception quality to those levels are implementation.
NOTE 3: The frequency of VAL UE sending listening reports can be limited to prevent signalling congestion. E.g., the VAL UE can stop monitoring the broadcast reception quality and send the MBS listening status report only once when it moves outside of the broadcast service area.
3. The NRM server based on the report from the participant, determines that the UE is not able to receive the media or the QoS requirements is not satisfied. The NRM server determines the VAL media (e.g., DL media, application layer control signalling) needs to be delivered via the unicast delivery to the reported NRM client.
4. If the unicast QoS flow is not satisfied, the NRM server interacts with the 5GC to update the QoS requirements.
5. The NRM server informs the VAL server to send the VAL data via the unicast delivery towards the reported NRM client by sending a user plane delivery mode message.
6. The NRM server sends the VAL media via the unicast delivery towards the NRM client which suffers bad broadcast reception quality.
7. The NRM client then receives the DL VAL data via both broadcast MBS session and unicast delivery.
14.3.4A.8.2.2.2 Service continuity from unicast to broadcast
The procedure in figure 14.3.4A.8.2.2.2-1 illustrates the VAL UE receiving VAL data via unicast delivery being switched to broadcast MBS session as the UE enters the broadcast service area where the NG-RAN is broadcasting the VAL media of the ongoing group communication. The VAL UE now is able to receive the VAL data via the broadcast MBS session. Only one of the receiving VAL UEs receiving the broadcast MBS session is shown.
Pre-conditions:
1. The VAL group communication is ongoing and the VAL data (e.g., DL media, application layer control signalling) is transmitted via broadcast MBS session in the broadcast service areas.
2. The VAL UE is receiving the VAL data (e.g., DL media, application layer control signalling) via the unicast delivery.
3. The NRM client has already received the broadcast MBS session announcement, MapVALGroupToSessionStream information and enters the broadcast service area.
4. A VAL group communication session is ongoing and the broadcast MBS session is used by the VAL server to deliver the VAL data of the group communication. The VAL UE is receiving the VAL data via the unicast delivery.
Figure 14.3.4A.8.2.2.2-1: Service continuity from unicast to broadcast
1. The NRM client detects that it is able to receive the broadcast media due to e.g., moving into the broadcast service area of the announced MBS session ID. The NRM client may determine the broadcast reception quality by using the BLER of the received media. When no media is received, the quality estimation can consider the reference signals and the modulation and coding scheme (MCS).
2. The NRM client sends MBS listening status report which indicates the broadcast reception quality associated with the MBS session ID is sufficient to receive VAL data. The NRM client may also map the determined broadcast reception quality to a broadcast reception quality level. The broadcast reception quality level indicates at which specific broadcast reception quality level the VAL data has been received.
NOTE 1: The set of MBS reception quality levels and the mapping of the determined broadcast reception quality to those levels are up to implementation.
NOTE 2: It is up to implementation that the broadcast reception quality level can be determined per MBS session, per media stream or per MBS QoS flow level via e.g., measurements of radio level signals, such as the reference signals from the NG-RAN node(s), or packet loss.
3. The NRM server determines the VAL UE is able to receive the VAL data via the the broadcast MBS session, and the NRM server sends a user plane delivery mode to the VAL server indicating to stop the unicast delivery.
4. Based on the MapVALGroupToSessionStream received before, the NRM client receives the DL VAL data via both the broadcast MBS session and the unicast delivery.
NOTE 3: If any information about the broadcast MBS session stream has changed, the NRM server provides the MapVALGroupToSessionStream again.
5. The VAL server, based on the user plane delivery mode message, determines to stop sending the VAL data (e.g., DL media, application layer control signalling) via the unicast delivery to the reporting NRM client. After then, the NRM client receives the VAL data only via the broadcast MBS session.
14.3.4A.8.3 Service continuity for multicast MBS session
14.3.4A.8.3.1 General
The NRM server may also switch between multicast and unicast by utilizing application layer mechanisms similar to switching between broadcast and unicast as specified in clause 14.3.4A.8.2. If indicated in the MBS session announcement information, the NRM client reports the monitoring state (i.e., the reception quality of the MBS session) back to the NRM server.
NOTE: Once the VAL UE has successfully joined the multicast MBS session and started to receive the VAL data via the multicast MBS session, then the network mechanism specified in 3GPP TS 23.247 [39] will deliver the media from the NRM server via the 5GC Individual MBS traffic delivery method or the 5GC Shared MBS traffic delivery method towards the VAL UE(s). The usage of 5GC Individual MBS traffic delivery method or the 5GC Shared MBS traffic delivery method is transparent to the NRM server and VAL server.
14.3.4A.9 Service continuity between 5G MBS delivery and unicast delivery
14.3.4A.9.1 General
This clause addresses the issue of VAL data delivery over MBS session, specifically, to maintain the service continuity when switching between 5G MBS delivery and unicast delivery.
14.3.4A.9.2 Service continuity for broadcast MBS session
14.3.4A.9.2.1 General
This solution provides the procedure which allows the NRM client to report the broadcast reception quality to the NRM server which is used to make the decision whether to use the unicast delivery to the VAL UE(s) which are suffering bad broadcast reception quality due to e.g., move out of the broadcast service area.
An NRM client monitors the broadcast MBS session to receive VAL data. Based on the received quality (e.g., radio level quality, RTP packet loss), the NRM client needs to inform the NRM server that the NRM client is able to receive the VAL data on the broadcast MBS session with sufficient quality or not.
This estimation of the broadcast reception quality may be dependent on, for example, the modulation and coding scheme (MCS) and measurements from the reference signals from the NG-RAN node(s), RTP packet loss, BLER of the received VAL data.
14.3.4A.9.2.2 Procedures
14.3.4A.9.2.2.1 Service continuity from broadcast to unicast
The procedure in figure 14.3.4A.9.2.2.1-1 illustrates the VAL UE which is receiving VAL data via broadcast MBS session is switched to unicast delivery because the VAL UE suffers from bad broadcast reception quality due to e.g., moving out of the broadcast service area. It shows only one of the receiving VAL UEs receiving the broadcast MBS session.
Pre-conditions:
1. The VAL group communication is ongoing and the VAL data (e.g., DL media, application layer control signalling) is transmitted via broadcast MBS session.
2. The NRM client is receiving the VAL data (e.g., DL media, application layer control signalling) via the broadcast MBS session.
3. The NRM client(s) already have the associated information (e.g., SDP) to receive the unicast delivery during the group communication establishment phase.
4. An VAL group communication session is ongoing and the DL VAL data is transmitted over broadcast MBS session.
Figure 14.3.4A.9.2.2.1-1: Service continuity from broadcast to unicast
1. The NRM client detects that it suffers bad broadcast reception due to e.g., moving out of the broadcast service area of the announced MBS session ID. The NRM client may determine the broadcast reception quality by using the BLER of the received media. When no media is received, the quality estimation can consider the reference signals and the modulation and coding scheme (MCS).
2. The NRM client sends MBS listening status report which indicates the broadcast reception quality associated with the MBS session ID is not sufficient to receive media. The NRM client may also map the determined broadcast reception quality to a broadcast reception quality level. The broadcast reception quality level indicates at which specific broadcast reception quality level the VAL data has been received.
NOTE 1: It is implementation that the broadcast reception quality level can be determined per MBS session, per media stream or per MBS QoS flow level via e.g., measurements of radio level signalling such as the reference signals from the NG-RAN node(s), packet loss.
NOTE 2: The set of MBS reception quality levels and the mapping of the determined broadcast reception quality to those levels are implementation.
NOTE 3: The frequency of VAL UE sending listening reports can be limited to prevent signalling congestion. E.g., the VAL UE can stop monitoring the broadcast reception quality and send the MBS listening status report only once when it moves outside of the broadcast service area.
3. The NRM server based on the report from the participant, determines that the UE is not able to receive the media or the QoS requirements is not satisfied. The NRM server determines the VAL media (e.g., DL media, application layer control signalling) needs to be delivered via the unicast delivery to the reported NRM client.
4. If the unicast QoS flow is not satisfied, the NRM server interacts with the 5GC to update the QoS requirements.
5. The NRM server informs the VAL server to send the VAL data via the unicast delivery towards the reported NRM client by sending a user plane delivery mode message.
6. The NRM server sends the VAL media via the unicast delivery towards the NRM client which suffers bad broadcast reception quality.
7. The NRM client then receives the DL VAL data via both broadcast MBS session and unicast delivery.
14.3.4A.9.2.2.2 Service continuity from unicast to broadcast
The procedure in figure 14.3.4A.8.2.2.2-1 illustrates the VAL UE receiving VAL data via unicast delivery being switched to broadcast MBS session as the UE enters the broadcast service area where the NG-RAN is broadcasting the VAL media of the ongoing group communication. The VAL UE now is able to receive the VAL data via the broadcast MBS session. Only one of the receiving VAL UEs receiving the broadcast MBS session is shown.
Pre-conditions:
1. The VAL group communication is ongoing and the VAL data (e.g., DL media, application layer control signalling) is transmitted via broadcast MBS session in the broadcast service areas.
2. The VAL UE is receiving the VAL data (e.g., DL media, application layer control signalling) via the unicast delivery.
3. The NRM client has already received the broadcast MBS session announcement, MapVALGroupToSessionStream information and enters the broadcast service area.
4. A VAL group communication session is ongoing and the broadcast MBS session is used by the VAL server to deliver the VAL data of the group communication. The VAL UE is receiving the VAL data via the unicast delivery.
Figure 14.3.4A.9.2.2.2-1: Service continuity from unicast to broadcast
1. The NRM client detects that it is able to receive the broadcast media due to e.g., moving into the broadcast service area of the announced MBS session ID. The NRM client may determine the broadcast reception quality by using the BLER of the received media. When no media is received, the quality estimation can consider the reference signals and the modulation and coding scheme (MCS).
2. The NRM client sends MBS listening status report which indicates the broadcast reception quality associated with the MBS session ID is sufficient to receive VAL data. The NRM client may also map the determined broadcast reception quality to a broadcast reception quality level. The broadcast reception quality level indicates at which specific broadcast reception quality level the VAL data has been received.
NOTE 1: The set of MBS reception quality levels and the mapping of the determined broadcast reception quality to those levels are up to implementation.
NOTE 2: It is up to implementation that the broadcast reception quality level can be determined per MBS session, per media stream or per MBS QoS flow level via e.g., measurements of radio level signals, such as the reference signals from the NG-RAN node(s), or packet loss.
3. The NRM server determines the VAL UE is able to receive the VAL data via the the broadcast MBS session, and the NRM server sends a user plane delivery mode to the VAL server indicating to stop the unicast delivery.
4. Based on the MapVALGroupToSessionStream received before, the NRM client receives the DL VAL data via both the broadcast MBS session and the unicast delivery.
NOTE 3: If any information about the broadcast MBS session stream has changed, the NRM server provides the MapVALGroupToSessionStream again.
5. The VAL server, based on the user plane delivery mode message, determines to stop sending the VAL data (e.g., DL media, application layer control signalling) via the unicast delivery to the reporting NRM client. After then, the NRM client receives the VAL data only via the broadcast MBS session.
14.3.4A.9.3 Service continuity for multicast MBS session
14.3.4A.9.3.1 General
The NRM server may also switch between multicast and unicast by utilizing application layer mechanisms similar to switching between broadcast and unicast as specified in clause 14.3.4A.9.2. If indicated in the MBS session announcement information, the NRM client reports the monitoring state (i.e., the reception quality of the MBS session) back to the NRM server.
NOTE: Once the VAL UE has successfully joined the multicast MBS session and started to receive the VAL data via the multicast MBS session, then the network mechanism specified in 3GPP TS 23.247 [39] will deliver the media from the NRM server via the 5GC Individual MBS traffic delivery method or the 5GC Shared MBS traffic delivery method towards the VAL UE(s). The usage of 5GC Individual MBS traffic delivery method or the 5GC Shared MBS traffic delivery method is transparent to the NRM server and VAL server.
14.3.4A.10 VAL service inter-system switching between 5G and LTE
14.3.4A.10.1 General
The VAL server delivers the VAL data to the VAL UE(s) without being aware of the mobility of the VAL UE with the assistance and guidance of the NRM server. When working in transport only mode, the NRM server guides the NRM clients throughout the VAL data transmission for switching between the LTE and 5G systems. For this purpose, the location management client may send location related information to the location management server, similar to the one defined in clause 9, which is triggered due to its location change – in this case due to Radio Access Technology (RAT) change, to inform the NRM server hence the latter provides guidance related to how to receive the VAL data after the location update.
The procedures cover both the deployment scenarios with/without MBSF/MBSTF. The procedures specify four inter-system switching related scenarios as follows:
1. Inter-system switching from 5G MBS session to LTE eMBMS bearer, as in 14.3.4A.10.2
2. Inter-system switching from 5G MBS session to LTE unicast bearer, as in 14.3.4A.10.3
3. Inter-system switching from LTE eMBMS to 5G MBS session, as in 14.3.4A.10.4
4. Inter-system switching from LTE eMBMS to 5G unicast PDU session, as in 14.3.4A.10.5
In all the inter-system switching related scenario described in 14.3.4A.10.2, 14.3.4A.10.3, 14.3.4A.10.4 and 14.3.4A.10.5, the functional entity that resides in 5GS may be NEF, or MBSF, or MB-SMF for session creation and together with PCF or PCC related interaction.
NOTE: There will be a service interruption when the VAL server performs path switch between 5G and LTE bearers or sessions.
14.3.4A.10.2 Inter-system switching from 5G MBS session to LTE eMBMS bearer
The procedure provided in figure 14.3.4A.10.2-1 describes how the NRM server handles inter-system switching when the VAL UE switches from 5G to LTE network, where the NRM server is able to provide the VAL data to the clients over eMBMS bearer(s).
Pre-conditions:
- NRM clients are attached to the 5GS, registered.
- The VAL service can be provided via both 5GS and EPS.
- The NRM client(s) is within the eMBMS service area.
- It is assumed that the NRM client(s) has not received the eMBMS bearer announcement while camping in 5GS.
Figure 14.3.4A.10.2-1: Inter-system switching from 5G MBS session to LTE eMBMS bearer.
1. An VAL group communication takes place, and the VAL data is delivered over 5G MBS session (either broadcast or multicast session mode), which is associated to the VAL group X.
2. The VAL UE performs handover to EPS.
3. Location information indicating the RAT change from the VAL UE is provided to the NRM server. VAL UE`s location information is provided via the location management client, triggered by RAT change, to the location management server, where the latter provides the location information to the NRM server. Also, location information handling can be based on notifications provided from the network to the NRM server related to 5GS supporting EPS interworking, as specified in 3GPP TS 23.501 [10], 3GPP TS 23.502 [11], and 3GPP TS 23.503 [12]. For that, the NRM server can subscribe to receive notifications of specific events from the network. For instance, the NRM server can subscribe to PCF related notifications (via N5 or Rx) for specific events, e.g., access network information notification and change of access type. Also, when SCEF+NEF is deployed, the NRM server can subscribe to SCEF+NEF related notifications for specific events, e.g., core network (CN) type change.
4. The NRM server analyses the RAT change and decides how to deliver the DL VAL data. If the NRM server decides to serve the client via eMBMS bearer, it may send an eMBMS bearer announcement. This step is optional as the bearer announcement related information could be sent in advance (implementation specific).
5. If not already available, the NRM client stores the announced TMGI(s), service area, and any relevant information to the eMBMS, which is delivered via the bearer announcement. As a result, the NRM client starts monitoring the bearer.
6. The NRM server may inform the VAL server to stop sending DL VAL data via the MBS by sending the user plane delivery mode message, e.g., when the last UE leaves the MBS session or move out of the MBS service area.
7. The NRM client sends an eMBMS listening status report to inform the server of its ability of receiving DL VAK data over the specified bearer.
8. The NRM server sends the necessary information related to receiving the DL VAL data in the form of the MapGroupToBearer.
9. The NRM server may inform the VAL server to start sending DL VAL data via the eMBMS by sending the user plane delivery mode message, e.g., the first UE(s) enters the eMBMS service area.
10. The VAL group communication takes place over EPS, and the VAL data is transmitted over an eMBMS bearer.
14.3.4A.10.3 Inter-system switching from 5G MBS session to LTE unicast bearer
The procedure provided in figure 14.3.4A.10.3-1 describes how the NRM server handles inter-system switching when the VAL UE switches from 5G to LTE network, where the VAL server is unable to provide the VAL services to the VAL UE over eMBMS bearer.
Pre-conditions:
- NRM clients are attached to the 5GS, registered and affiliated to the same VAL group X.
- The VAL services can be provided via both 5GS and EPS.
Figure 14.3.4A.10.3-1: Inter-system switching from 5G MBS session to LTE unicast bearer.
1. An VAL group communication takes place, and the VAL data is delivered over 5G MBS session (either broadcast or multicast session mode), which is associated to the VAL group X.
2. The VAL UE performs handover to EPS.
3. Location information indicating the RAT change from the VAL UE is provided to the NRM server. VAL UE`s location information is provided via the location management client, triggered by RAT change, to the location management server, where the latter provides the location information to the NRM server.
Also, location information handling can be based on notifications provided from the network to the NRM server related to 5GS supporting EPS interworking, as specified in 3GPP TS 23.501 [10], 3GPP TS 23.502 [11], and 3GPP TS 23.503 [12]. For that, the NRM server can subscribe to receive notifications of specific events from the network. For instance, the NRM server can subscribe to PCF related notifications (via N5 or Rx) for specific events, e.g. access network information notification and change of access type. Also, when SCEF+NEF is deployed, the NRM server can subscribe to SCEF+NEF related notifications for specific events, e.g. core network (CN) type change.
4. The NRM server may inform the VAL server to stop sending DL VAL data via the MBS by sending the user plane delivery mode message, e.g., when the last UE leaves the MBS session or move out of the MBS service area.
5. The NRM server may interact with the EPC for providing the required media resources over the unicast bearer, if not already allocated.
6. The NRM server informs the VAL server to send DL VAL data to the VAL UE via the LTE unicast bearer by sending the user plane delivery mode message.
7. The VAL group communication takes place over EPS, and the DL VAL data is transmitted over a LTE unicast bearer.
14.3.4A.10.4 Inter-system switching from LTE eMBMS to 5G MBS session
The procedure provided in figure 14.3.4A.10.4-1 describes how the NRM server handles inter-system switching when the VAL UE switches from LTE network to 5G, where the NRM server is able to provide the VAL services to the client over 5G MBS sessions (either broadcast or multicast).
Pre-conditions:
- NRM clients are attached to the EPC.
- The VAL services can be provided via both 5GS and EPS.
- The NRM client(s) is within the service area (if the session is limited to an area), where the MBS session is configured.
- It is assumed that the NRM client(s) has not received the 5G MBS session announcement while camping in EPS.
Figure 14.3.4A.10.4-1: Inter-system switching from LTE eMBMS bearer to 5G MBS sessions (either broadcast or multicast).
1. An VAL group communication takes place, and the DL VAL data is delivered over eMBMS bearer, which is associated to the VAL group X.
2. The VAL UE performs handover to 5GS.
3. Location information indicating the RAT change from the VAL UE is provided to the NRM server. VAL UE`s location information is provided via the location management client, triggered by RAT change, to the location management server, where the latter provides the location information to the NRM server.
Also, location information handling can be based on notifications provided from the network to the NRM server related to 5GS supporting EPS interworking, as specified in 3GPP TS 23.501 [10], 3GPP TS 23.502 [11], and 3GPP TS 23.503 [12]. For that, the NRM server can subscribe to receive notifications of specific events from the network. For instance, the NRM server can subscribe to PCF related notifications (via N5 or Rx) for specific events, e.g., access network information notification and change of access type. Also, when SCEF+NEF is deployed, the NRM server can subscribe to SCEF+NEF related notifications for specific events, e.g., core network (CN) type change.
4. The NRM server analyses the RAT change and decides how to deliver the DL VAL data. If the NRM server decides to serve the client via 5G MBS session, it may send an MBS session announcement indicating information among others the session mode to serve the NRM client and the corresponding MBS session ID. This step is optional as the session announcement related information could be sent in advance (implementation specific).
5. The VAL UE acts according to the MBS session mode provided to receive the DL media.
5a. In case of multicast MBS sessions, the VAL UE performs a UE session join towards the 5GC indicating the MBS session ID to join. It may as well send a UE session join acknowledgement to the NRM server.
5b. In case of broadcast MBS sessions, the VAL UE starts monitoring the broadcast MBS session. 6. The NRM server may inform the VAL server to stop sending DL VAL data via the eMBMS bearer by sending the user plane delivery mode message, e.g., when the last UE moves out of the MBMS service area.
7. The NRM client sends an MBS listening status report to the server indicating its ability to receive media over the indicated MBS session.
8. The NRM server sends a MapVALGroupToSessionStream over the MBS session providing the required stream information to receive the media related to the group communication.
9. The NRM client processes the received information related to the DL VAL data over the MBS session.
10. The NRM server may inform the VAL server to start sending DL VAL data via the 5G MBS session by sending the user plane delivery mode message, e.g., the first UE(s) enters the MBS service area or joins the multicast MBS session.
11. The VAL group communication takes place over 5GS, and the DL VAL data is delivered over the broadcast or multicast MBS session.
14.3.4A.10.5 Inter-system switching from LTE eMBMS to 5G unicast PDU session
The procedure provided in figure 14.3.4A.10.5-1 describes how the NRM server handles inter-system switching when the VAL UE switches from LTE network to 5G, where the NRM server is able to provide the VAL services to the client over 5G MBS sessions (either broadcast or multicast).
Pre-conditions:
- NRM clients are attached to the EPC and affiliated to the same VAL group X.
- The VAL services can be provided via both 5GS and EPS.
Figure 14.3.4A.10.5-1: Inter-system switching from LTE eMBMS bearer to 5G unicast PDU session.
1. An VAL group communication takes place, and the VAL data is delivered over eMBMS bearer, which is associated to the VAL group X.
2. The VAL UE performs handover to 5GS.
3. Location information indicating the RAT change from the VAL UE is provided to the NRM server. VAL UE`s location information is provided via the location management client, triggered by RAT change, to the location management server, where the latter provides the location information to the NRM server.
Also, location information handling can be based on notifications provided from the network to the NRM server related to 5GS supporting EPS interworking, as specified in 3GPP TS 23.501 [10], 3GPP TS 23.502 [11], and 3GPP TS 23.503 [12]. For that, the NRM server can subscribe to receive notifications of specific events from the network. For instance, the NRM server can subscribe to PCF related notifications (via N5 or Rx) for specific events, e.g. access network information notification and change of access type. Also, when SCEF+NEF is deployed, the NRM server can subscribe to SCEF+NEF related notifications for specific events, e.g. core network (CN) type change.
4. The NRM server may inform the VAL server to stop sending DL VAL data via the eMBMS bearer by sending the user plane delivery mode message, e.g., when the last UE moves out of the LTE MBMS service area.
5. The NRM server may interact with the 5GC to request media resources (if not already allocated) with specific requirements over unicast PDU session, as it is able to serve the NRM client via unicast PDU session.
6. The NRM server informs the VAL server to send DL VAL data to the VAL UE via the PDU session by sending the user plane delivery mode message.
7. The VAL group communication takes place over 5GS, and the VAL data is delivered over unicast PDU session.
|
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 accommodate various vertical-specific application services, e.g.:
- Network-assisted Command and Control (C2) communications in UASAPP, 3GPP TS 23.255 [62], where the UAV controller navigates its UAV over the 5GS;
- Teleoperated Driving (ToD) in eV2XAPP, 3GPP TS 23.286 [7], where the a V2X UE acting as server may remotely control a further V2X UE over the 5GS;
- Network-assisted Device-to-Device communications in Factory of the Future (FF) use cases, such as control-to-control communications.
- 5G LAN-Type communication within a 5G VN group as specified in 3GPP TS 23.501 [10].
- Application QoS coordination for Mobile Metaverse Services in distributed VAL servers.
|
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 may come from NRM client of either of the VAL UEs within the service and will trigger the end-to-end QoS/resource management by the NRM server. The triggering the end-to-end QoS management request can be initiated by the VAL application at the VAL UE, and the conditions may depend on the requirements of the VAL service, e.g. for UAS such triggering may be needed when a UAV is in-flight, or for V2X such trigger may be initiated when a controlled VAL UE enters an urban area, or for 5G LAN-type service such trigger may be initiated by the AF (e.g. on VAL UE1) that manages the corresponding 5G VN group.
The clause 14.3.5.2.1 describes the end-to-end QoS/resource management capability for network-assisted UE-to-UE communications for a single pair of UEs.
The clause 14.3.5.2.2 describes the end-to-end QoS/resource management capability for network-assisted UE-to-UE communications for a group of UEs.
|
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 session (VAL UE 1 and VAL UE 2) are connected to one or more PLMNs and have ongoing PDU sessions.
3. NRM server has used the "Setting up an AF session with required QoS procedure" (clause 4.15.6.6 of 3GPP TS 23.502 [11]).
Figure 14.3.5.2.1-1 end-to-end QoS management request / response
1. The NRM client 1 (of VAL UE 1) sends to the NRM server an end-to-end QoS management request for managing the QoS for the end-to-end application session.
2. The NRM server configures the application QoS parameters by decomposing the end-to-end QoS requirements (VAL UE 1 to VAL UE 2) to application QoS parameters for each individual session (e.g. network session for VAL UE 1 -and network session for VAL UE 2) which are part of the end-to-end application session.
3. The NRM server sends to the NRM client 1 an end-to-end QoS management response with a positive or negative acknowledgement of the request.
4. The NRM server may also send a notification to NRM client 2 (of VAL UE 2) to inform about the end-to-end QoS management initiation by the NRM server.
|
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 UE 1 and a group of VAL UEs) are connected to one or more PLMNs and have ongoing PDU sessions.
Note : The NRM client2 (of VAL UE 2) can be any VAL UEs in the group of VAL UEs.
Figure 14.3.5.2.2 end-to-end QoS management request / response for a group of UEs
1. The NRM server receives from the AF on NRM client 1 (of VAL UE 1) the end-to-end QoS management request for managing the QoS on UE-to-UE traffic for a group of UEs.
2. The NRM server retrieves from 5GC or subscribe to 5GC to obtain additional VAL-UE associated information for each member in the group identified by the VAL group ID, which is account for decomposition. The VAL-UE associated information could be from the 5GC (NEF Monitoring Events as in 3GPP TS 23.502 [11], QoS sustainability analytics as in 3GPP TS 23.288 [34]) or SEAL LMS (on demand location reporting).
3. The NRM server configures the application QoS parameters by decomposing the end-to-end QoS requirements (UE-to-UE traffic for any two UEs in a group) to application QoS parameters for each individual session (uplink network session for ingress group member and downlink network session for egress group member). The NRM server needs to take the additional VAL-UE associated information into account for evaluation during such decomposition.
4. The NRM/SEAL server, acting as AF, sends to the 5GC a "Procedures for AF requested QoS for a UE or group of UEs not identified by a UE address" to set the application QoS parameters respectively for uplink network session for each ingress group member in the group and for downlink network session for egress group member.
Additionally, the NRM/SEAL server may activate monitoring of the performance to receive QoS monitoring event notifications from 5GC by setting the (optionally with Alternative QoS Profiles) in the request, in this case the AF may receive the QoS downgrade notification for e.g. latency thus to initiate the NRM-assisted coordinated QoS provisioning for 5G LAN-Type communication in clause 14.3.5.3.x
5. The NRM server sends to the NRM client 1an end-to-end QoS management response with a positive or negative acknowledgement of the request.
6. If the NRF server receives the end-to-end QoS management request including VAL UE2 as any of the List of VAL UEs, then the NRM server may also send a notification to NRM client 2 (of VAL UE 2) to inform about the end-to-end QoS management initiation by the NRM server.
|
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 UEs are connected to 3GPP network (the same or different). The communication between the VAL UEs is assumed to be in-direct / network-assisted; hence two PDU sessions are established respectively (one per VAL UE).
The clause 14.3.5.2.1 describes the end-to-end QoS/resource management capability for network-assisted UE-to-UE communications for a single pair of UEs.
The clause 14.3.5.2.2 describes the end-to-end QoS/resource management capability for network-assisted UE-to-UE communications for a group of UEs.
|
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 server, acting as AF, has registered to receive QoS monitoring event notifications from 5GC and notifications from VAL UEs (from both UEs), as specified in 3GPP TS 23.501 [10].
Figure 14.3.5.3.1-1: NRM-assisted coordinated QoS provisioning for C2 communication
1a. A QoS downgrade trigger event is sent from the NRM client of the VAL UE 1 to the NRM server, denoting an application QoS degradation (experienced or expected) e.g. based on the experienced packet delay or packet loss for the Uu link (e.g. packet loss great than threshold value). The conditions for triggering the QoS downgrade indication from the NRM client is based on the threshold that may be provided in advance by the NRM server (at the end-to-end QoS management response by the NRM server in 14.3.5.2.1).
1b. Alternatively, the NRM server receives a trigger event from the 5GC (SMF/NEF), denoting a QoS downgrade notification for the VAL UE 1 session. (described in clause 5.7.2.4.1b of 3GPP TS 23.501 [10]).
2. The NRM server evaluates the fulfilment/non-fulfilment of the end-to-end QoS based on the trigger event. NRM server may retrieve additional information based on subscription to support its evaluation. This could be from the 5GC (NEF Monitoring Events as in 3GPP TS 23.502 [11], QoS sustainability analytics as in 3GPP TS 23.288 [34]) or SEAL LMS (on demand location reporting for one or both VAL UEs 1 and 2).
Then, the NRM server, determines an action, which is the QoS parameter adaptation of one or both links (QoS profile downgrade for the link receive QoS notification control, and QoS upgrade for the link which can be upgraded).
3. The NRM/SEAL server, acting as AF, sends to the 5GC (to SMF via NEF or to PCF via N5) a request for a change of the QoS profile mapped to the one or both network sessions (for VAL UE 1 and UE 2) or the update of the PCC rules to apply the new traffic policy (as specified in 3GPP TS 23.502 [11] in clause 4.15.6.6a: AF session with required QoS update procedure).
4. The NRM server sends an application QoS change notification to the affected NRM clients, to inform on the adaptation of the QoS requirements for the individual session.
|
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 registered to receive QoS monitoring event notifications from 5GC and notifications from VAL UEs (from any UEs in a group), as specified in 3GPP TS 23.501 [10].
Figure 14.3.5.3.2-1: NRM-assisted coordinated QoS provisioning for 5G LAN-Type communication
1. The NRM server receives a trigger event from the 5GC (SMF/NEF), denoting a QoS downgrade notification for the network session of any group member in a group. (described in clause 5.7.2.4.1b of 3GPP TS 23.501 [10]).
2. The NRM server evaluates the fulfilment/non-fulfilment of the end-to-end QoS based on the trigger event. NRM server may retrieve additional information based on subscription to support its evaluation. This could be from the 5GC (NEF Monitoring Events as in 3GPP TS 23.502 [11], QoS sustainability analytics as in 3GPP TS 23.288 [34]) or SEAL LMS (on demand location reporting for one or both VAL UEs 1 and 2).
Then, the NRM server, determines an action, which is the QoS parameter adaptation of only uplink/downlink network session or both uplink and downlink network sessions for each ingress group member in the group.
3. The NRM/SEAL server, acting as AF, sends to the 5GC (to SMF via NEF or to PCF via N5) a request for a change of the QoS profile mapped to the impacted network sessions or the update of the PCC rules to apply the new traffic policy (as specified in 3GPP TS 23.502 [11] in clause 4.15.6.14: AF requested QoS for a UE or group of UEs not identified by a UE address procedure).
4. The NRM server sends an application QoS change notification to the affected NRM clients, to inform on the adaptation of the QoS requirements for the individual session.
|
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 VAL UE1 and VAL UE2 and digital counterparts of UE1 and UE2 instantiated in one or more DNs (called as virtual or avatar VAL UEs).
- VAL session #1: VAL client 1 sends to VAL server 1 (including virtual VAL UE 1 at DN side) sensor data / measurements on the physical environment related to VAL UE1 over VAL-UU interface. VAL server (virtual VAL UE1) sends back haptic feedback to VAL UE1 (for UE1 and/or UE2 and the environment).
- VAL session #2: VAL client 2 sends to VAL server 2 (including virtual VAL UE 2 at DN side) sensor data / measurements on the physical environment related to VAL UE2 over VAL-UU interface. VAL server (virtual VAL UE2) sends back haptic feedback to UE2 (for UE1 and/or UE2 and the environment).
- VAL session #3: Exchange of service related / feedback data between VAL server 1 and 2 for interactions between virtual UE 1 and 2 (for example micro-transactions such as avatar updates/modifications or environment changes).
- VAL session #4: Sensor data / measurements are exchanged between VAL UEs over VAL-PC5 (communication can be over side link) for traffic related to the MM service.
There is a coupling in the performance requirements for all the above VAL sessions which is corresponding to the end-to-end MM service. The end-to-end MM service may be related e.g., to 5G-enabled Traffic Flow Simulation and Situational Awareness, where the physical objects including UEs (e.g. V2X UEs) in cars and trucks in each lanes, will have a corresponding digital twin in the virtual world in distributed VAL servers, and the virtual and physical UEs form the mobile metaverse.
One possible coupling of such requirements is about the expected sequence of certain messages to be transferred via the 5GS. For example, the delay of the collection of sensor information from the physical environment may have impact on the expected delay of haptic feedback from the server to the VAL UE which will result in degrading the QoE for the MM service.
In the procedure as defined in 14.3.5.4.2, the NRM server takes the performance of VAL Session # 1, VAL Session # 2, VAL Session # 3, VAL Session # 4 into consideration to ensure the E2E performance (UE#1 - VAL server#1 - VAL server#2 - UE#2). For example, if the delay of VAL session # 1 is long, the delay of other sessions needs to be reduced.
NOTE: This capability is only applicable to multiple VAL server deployments (e.g., virtual UEs in different edge or cloud deployed VAL servers). In case of single VAL server offering the MM service, the application QoS coordination is performed based on procedure in clause 14.3.5.3.1 for single pair and 14.3.5.3.2 for group of UEs..
|
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 support the Mobile Metaverse (MM) Service (e.g., VAL client 1 to VAL server 1, VAL client 2 to VAL server 2) are established.
4. The NRM client 1 has acquired information on the dependencies among different sessions (e.g. sequence of data to be exchanged among VAL servers and clients) from the VAL client.
Figure 14.3.5.4.1-1 application QoS coordination for VAL MM services
1. The NRM client 1 (acting on behalf of VAL client 1) sends to the NRM server an MM-specific QoS management request to trigger the application QoS coordination between the physical and virtual VAL UEs within MM service. This request may also include the end-to-end QoS/service provisioning requirement for the MM service, and the expected dependencies among different sessions (e.g. sequence of data to be exchanged among VAL servers and clients).
2. The NRM server decomposes the MM service performance requirement (end to end application QoS target) to per VAL session requirement taking into account the dependencies among sessions, where in this step the NRM server identifies the VAL sessions for which the application QoS parameters need to be configured or updated.
3. The NRM server configures the application QoS parameters per VAL session, for the identified VAL sessions to ensure meeting the end-to-end QoS requirements for the MM service.
4. he NRM server sends the MM-specific QoS management response to the NRM client 1 to provide the configuration information for the QoS attributes for the VAL sessions related to VAL UE 1.
5. The NRM server sends a QoS configuration notification to the VAL servers 1 and 2 as well as to the NRM client 2 to provide the configuration information for the QoS attributes for the corresponding VAL sessions. The QoS configuration notification may include per session QoS requirements for each metaverse session received/sent at/by the UE, where each metaverse session may be composed of multi-modal type of communication conveying audio, video or haptic/sensor information from/between the UE.
|
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 event details.
To monitor and report the events related to the VAL UE from the 3GPP core network, the NRM server shall use the Monitoring Events procedures as specified in 3GPP TS 23.502 [11].
To monitor and report the analytics events related to the VAL UE, the NRM server shall use the procedures specified in 3GPP TS 23.288 [34].
|
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 3GPP TS 23.288 [34]);
Figure 14.3.6.2.2-1: Monitoring Events Subscription Procedure
1. The VAL server sends Monitoring Events Subscription request to the NRM server, requesting the NRM server to monitor the events related to the VAL UE(s) as per the subscription request, and shall include the information related to the events that the VAL server is interested in.
2. The NRM server shall check if the VAL server is authorized to initiate the Monitoring Events Subscription request and if authorized, shall respond with Monitoring Events Subscription Response message, indicating the successful subscription status along with subscription information to the VAL server. The VAL service ID may be used by the NRM server to derive event specific information in 3GPP core network services (e.g. QoS requirement in analytics event subscription), based on e.g. local configuration. The NRM server maps the VAL group ID (if received) to the External Group ID known to the 3GPP core network.
NOTE: The mapping between Monitoring profile ID and event details in the NRM server can be pre-configured and/or dynamically built based on VAL server request with explicitly sent event details, which is implementation specific.
3. Based on the events of interest information in the subscription request message, if applicable, the NRM server shall subscribe to the UE monitoring events (LOSS_OF_CONNECTIVITY, COMMUNICATION_FAILURE, etc.) for the set of UEs (VAL UEs) in the subscription request, as specified in 3GPP TS 23.502 [11].
4. Based on the events of interest information in the subscription request message, if applicable, the NRM server shall subscribe to the UE analytics events (like ABNORMAL_BEHAVIOUR etc.) for the set of UEs (VAL UEs) in the subscription request, as specified in 3GPP TS 23.288 [34].
|
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 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.
|
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 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.
|
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 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.
|
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 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.
|
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 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.
|
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 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.
|
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-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.
|
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 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.
|
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.
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.
|
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 participants including vulnerable road users can form a smart transport metaverse. To support such use case, it is essential to discover the identities of the virtual UEs (as counterparts of the physical UEs at the VAL server side) and identify the sessions required as well as the per session requirement in both physical and virtual world.
This clause describes the procedure for the translation of MMeta service requirements to network and connectivity requirements and the MMeta service connectivity support of all VAL UEs within the MMeta service area of interest.
Pre-conditions:
- VAL server has deployed the MMeta service for the target VAL service area.
Figure 14.3.9.2.3-1: Establishing communication with MMeta service requirements
1. The VAL server (MMeta service provider who deploys the virtual UEs) sends an MMeta service requirement subscription request message to the NRM server for configuring the connectivity and network requirements for the MM service.
2. The NRM server authorizes the request and sends an MMeta service requirements subscription response to the VAL server.
3. The NRM server translates the MMeta service requirement to a network communication requirement (which is equivalent network resources/QoS requirements) for the mobile metaverse service.
4. The NRM server based on the translated network requirements, obtains location info for all the connected VAL UEs within the network coverage area where the MMeta service is deployed. For location information, such retrieval is based on SEAL LMS service for receiving the list of UEs and their locations in each area/zone (see clause 9.3.12), or by querying this information from the UEs (via NRM clients) for the area of interest (see clause 9.3.4 and clause 9.3.5).
5. The NRM server identifies the application sessions among the VAL UEs (VAL UE -to network -to- VAL UE) and between the VAL UEs and the VAL servers (where the virtual UEs are deployed) required for the end-to-end MMeta service. Then, NRM server translates the network requirements to different per session performance requirements for expected communications among the discovered virtual - physical UEs.
NOTE: It is assumed that all VAL UEs with the MMeta capability (based on the VAL UE capability requirement) which are discovered in the area of interest, are selected to establish VAL sessions among them as well as towards their virtual UEs at the VAL server side.
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].
6. The NRM server sends an MM service connectivity request to NRM client 1 and NRM client 2.
7. The NRM client 1 and 2 send an MM service connectivity response to NRM server.
8. The NRM server sends the MM service connectivity notification (connectivity/session information) to VAL server indicating successful establishment of the connectivity.
|
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) 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.
|
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 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].
|
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 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.
|
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 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).
|
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 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
|
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, 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.
|
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 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.
|
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 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.
|
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 [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.
|
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 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.
|
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 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.
|
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 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.
|
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) 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).
|
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 application requirement, e.g., IoT application requirements.
For this purpose, the NRM server may be configured with DRX and eDRX parameters that influences different power saving modes, which for example extend the battery lifetime.
NOTE 1: It is up to the PLMN operator to determine which parameters the NRM server may request to reconfigure the VAL UEs.
NOTE 2: It is up to the PLMN operator to accepted, modify, or reject the requested configurations by the NRM server.
The power saving configurations may either be triggered by the VAL server as described in clause 14.3.15.2, or by the VAL UE as described in clause 14.3.15.3.
|
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 Service. The request contains the list of VAL UEs and VAL Users that are targets for the power saving, VAL service ID, power saving requirements, e.g., mode (economy, balanced, performance).
2. NRM server determines, based on the VAL service ID, UE(s) access type and power saving mode, the power saving configuration, network parameters and communication pattern parameters for each requested VAL UE(s). Furthermore, the SEAL Server may determine the VAL UE ID(s) associated with the VAL user(s) included in step 1.
3. NRM Server interacts with 3GPP CN (e.g., CpProvisioning, NpConfiguration and/or MonitorEvent APIs) to provision the VAL UE(s) network parameters and communication pattern parameters determined in step 2.
4. NRM Server interacts with NRM Client with recommended power saving configuration for the UE (e.g., the determined power saving configuration in step 2).
5. The target UE interacts with 3GPP network as per clause 4.2.2.2.2 of 3GPP TS 23.502 [11], to indicate the desired power saving configuration, e.g., DRX or eDRX configuration. The UE receives from 3GPP RAN the accepted power saving configuration.
NOTE: It is up to the 3GPP system to determine the final DRX configurations to be reconfigured in the VAL UE.
6. NRM Client responds to the NRM Server with power saving configuration response and indicates the accepted power saving configuration.
7. NRM Server responds to the VAL Server with power saving assist response.
|
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. NRM Client requests the NRM Server to assist power saving of the VAL UE(s). The NRM client indicates the desired power saving configuration to the NRM Server.
2. Steps 2-6 as in Figure 14.3.15.2-1.
3. The NRM Server responds to the NRM Client with power saving assist response.
4. The VAL UE may interact with VAL Server for power saving response.
|
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
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
SS_MMetaServiceRequirements
Subscribe_MMeta_Service Requirements
VAL server
Subscribe/Notify
Notify_ MMeta_Service Requirements
VAL server
|
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
API operation name: Reserve_Network_Resource Modify
Description: Requesting for the modification of network resource adaptation.
Known Consumers: VAL server.
Inputs: See subclause 14.3.2.2a
Outputs: See subclause 14.3.2.2b
See subclause 14.3.3 for the details of usage of this API 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 operation.
|
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 of this API operation.
|
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.