hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.31 TSN bridge configuration request
|
The configuration information of 5GS Bridge is defined in TS 23.501 [10], clause 5.28.2 (The configuration information of 5GS Bridge).
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.32 TSN bridge configuration response
|
The configuration information of 5GS Bridge is defined in TS 23.501 [10], clause 5.28.2 (The configuration information of 5GS Bridge).
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.33 Unicast QoS monitoring data request
|
Table 14.3.2.33-1 describes the information flow from the VAL server to the network resource management server for unicast QoS monitoring data request.
Table 14.3.2.33-1: Unicast QoS monitoring data request
Information element
Status
Description
Requester Identity
M
The identity of the VAL server performing the request.
List of VAL UE IDs
O
(see NOTE)
List of VAL UEs whose QoS monitoring data is requested.
VAL group ID
O
(see NOTE)
The group ID used for the VAL group for which QoS monitoring data is requested.
List of VAL stream IDs
O
(see NOTE)
List of VAL streams for which QoS monitoring data is requested.
Measurement requirements
M
It describes the requirements on the QoS measurement data to be provided.
> type of data
M
At least one of the following measurement index shall be provided.
>> packet delay
O
UL/DL/RT packet delay.
For VAL stream, the packet delay means measurement from a source UE to a target UE.
>> packet loss rate
O
Average packet loss rate.
>> data rate
O
Average data rate and/or maximum data rate.
>> traffic volume
O
Average traffic volume for UL and/or DL
> measurement time period
O
The measurement time period indicates either a current or past time period. If absent, current time and 5 minutes duration are used as default setting.
> aggregation granularity window
O
Indicates how long the QoS monitoring is performed to compute the average value and gather the maximum value. If absent, 1 minute is used as default setting.
NOTE: Only one of these information elements shall be present.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.34 Unicast QoS monitoring data response
|
Table 14.3.2.34-1 describes the information flow from the VAL server to the network resource management server for unicast QoS monitoring data response.
Table 14.3.2.34-1: Unicast QoS monitoring data response
Information element
Status
Description
List of VAL UE IDs
O
(see NOTE 1)
List of VAL UEs whose QoS monitoring data is provided. This list is either the list provided in the request or a subset of that list. It can contain a single UE.
VAL group ID
O
(see NOTE 1)
The group ID used for the VAL group for which QoS monitoring data is provided. This group ID shall be the same VAL group ID as the VAL group ID provided in the request.
List of VAL stream IDs
O
(see NOTE 1)
List of VAL stream IDs whose QoS monitoring data is provided. This list is either the list provided in the request or a subset of that list. It can contain a single stream ID.
Result
M
Indicates the success or failure for the operation
QoS monitoring data
M
(see NOTE 2)
QoS monitoring data is an aggregate of QoS measurements data obtained from the 5GS.
Cause
O
Provides reason for the failure (e.g. when data for the requested time period is not available).
NOTE 1: Only one of these information elements shall be present.
NOTE 2: If the Result information element indicates failure then the value of the QoS monitoring data information element has no meaning.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.35 Application connectivity request
|
Table 14.3.2.35-1 describes the information flow for application connectivity request from a NRM client to the NRM server.
Table 14.3.2.35-1: Application connectivity request
Information element
Status
Description
Source VAL UE ID
M
Identifier of the requestor VAL UE
Source IP address
M
IP address of the requestor VAL UE
VAL service ID
M
Identifier of the VAL service
List of destination VAL UE IDs
M
Identifiers of the destination VAL UEs
Application service requirements
M
Details of service requirements
>Packet size (see NOTE)
O
Size of the packet to be transmitted.
>Packet transmission interval (see NOTE)
O
Intervals at which the packet is to be transmitted
>Packet E2E latency (see NOTE)
O
E2E Latency for packet transmission
>Packet error KPI (see NOTE)
O
The KPIs related to packet error (e.g. allowed packet loss rate, packet loss amount, packet error rate)
>Bitrate (see NOTE)
O
The bitrate required
Application connectivity context
O
Application connectivity context of the requester, used for determining the destination and/or resource parameters. If this IE is included, at least one of the information elements in Table 14.3.2.35-2 shall be provided.
NOTE: At least one of information elements of the application service requirements shall be included.
Table 14.3.2.35-2: Application connectivity context
Information element
Status
Description
Location
O
Location information of the client. The element may also indicate whether network-determined location is to be used instead.
Speed
O
Speed information for the client.
Direction
O
Direction information for the client.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.36 Application connectivity response
|
Table 14.3.2.36-1 describes the information flow for application connectivity response from the NRM server to the NRM client.
Table 14.3.2.36-1: Application connectivity response
Information element
Status
Description
Result
M
Result from the NRM server in response to request indicating success or failure for accepting the request.
Cause
O
The cause of failure, if the result indicates failure.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.37 Application connectivity notification
|
Table 14.3.2.37-1 describes the information flow for application connectivity notification from the NRM server to the NRM client.
Table 14.3.2.37-1: Application connectivity notification
Information element
Status
Description
Session information
M
Session information for the established connectivity for application communication
VAL service ID
M
Identifier of the VAL service
Requestor VAL UE ID
M
The identity of the source VAL UE requesting the connectivity
List of accepted destination VAL UE IDs (see NOTE)
O
The list of destination VAL UEs which are accepted for the connectivity established for the application service communication
NOTE: The List of accepted destination VAL UE IDs IE shall be included when the application connectivity notification is sent to the initiator of the application connectivity request.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.38 Unicast QoS monitoring subscription update request
|
The information flow from the VAL server to the network resource management server for unicast QoS monitoring subscription update request has the same content as unicast QoS monitoring subscription request specified in clause 14.3.2.20.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.39 Unicast QoS monitoring subscription update response
|
Table 14.3.2.39-1 describes the information flow from the network resource management server to the VAL server for unicast QoS montoring subscription update response.
Table 14.3.2.39-1: Unicast QoS monitoring subscription update response
Information element
Status
Description
Update status
M
It indicates the subscription update result
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.40 Multicast/broadcast resource request
|
Table 14.3.2.40-1 describes the information flow for the multicast/broadcast resource request from VAL server to NRM server.
Table 14.3.2.40-1: Multicast/broadcast resource request
Information element
Status
Description
Requester Identity
M
The identity of the VAL server performing the request.
VAL group ID
O (NOTE 3)
The identity of the group that the multicast/broadcast resource is requested for.
VAL UE ID List
O (NOTE 3)
The list of VAL UE ID that the multicast/broadcast resource is requested for.
Session announcement mode
M
Indicates whether the session announcement is sent by NRM server or by the VAL server
Service requirement description
M
Indicates the service characteristics, e.g., Media type, Media format, bandwidth requirements, flow description, Application Identifier, Priority indicator, emergency indicator Application service provider.
Multicast/Broadcast area information
O
Indicate the area where the multicast/broadcast resource is requested for
Endpoint information
M
Information of the endpoint of the VAL server to which the user plane notifications have to be sent.
Network system indicator
O
Indicate if the multicast/broadcast resrouce is required from 5GS, EPS, or both
Local MBMS information (NOTE 1, NOTE 2)
O
> MB2-U information
O
IP address, UDP port number of the MB2-U interface
> xMB-U information
O
IP address, UDP port number of the xMB-U interface
> M1 interface information
O
M1 interface information for local MBMS
Local MBMS activation indication (NOTE 1, NOTE 2)
O
Indicates whether to request the NRM server to use Local MBMS information.
NOTE 1: The VAL server may provide either the Local MBMS information or the Local MBMS activation indication. This IE is present when the local MBMS is required for VAL services like V2X service.
NOTE 2: This information element is only applicable when EPS is specified in the network system indicator IE.
NOTE 3: Either of the IEs shall be present.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.41 Multicast/broadcast resource response
|
Table 14.3.2.41-1 describes the information flow for the multicast/broadcast resource response from NRM server to VAL server.
Table 14.3.2.41-1: Multicast/broadcast resource response
Information element
Status
Description
Result
M
The result indicates success or failure of the multicast/broadcast resource request operation.
Identity of the multicast/broadcast resource
O
(NOTE 1)
The identity of the multicast/broadcast MBS session, or/and the identity of the MBMS bearer.
User plane address
M
(NOTE 2)
User plane IP address(es) and port for VAL to deliver the DL packet
Session description information
O
(NOTE 2)
Indicates Multicast/broadcast related configuration information as defined in 3GPP TS 26.346 [28] (e.g. radio frequency and MBMS Service Area Identities) or/and 3GPP TS 23.247 [39] (e.g. MBS FSA ID(s), Area Session ID)
NOTE 1: This IE may not be required if the session announcement mode indicates that the request is sent by the NRM server.
NOTE 2: If the Result Information element indicates failure then the values of the other information elements shall not present.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.42 Multicast/broadcast resource update request
|
Table 14.3.2.42-1 describes the information flow for the multicast/broadcast resource update request from VAL server to NRM server.
Table 14.3.2.42-1: Multicast/broadcast resource update request
Information element
Status
Description
Requester Identity
M
The identity of the VAL server performing the request.
Identity of the multicast/broadcast resource
M
Identity of the multicast/broadcast resource to be updated.
Service requirement description
O (NOTE 3)
Indicates the service characteristics, e.g., Media type, Media format, bandwidth requirements, flow description, Application Identifier, Priority indicator, emergency indicator Application service provider.
Multicast/Broadcast area information
O(NOTE 3)
Indicate the area where the multicast/broadcast resource is requested for.
Local MBMS information
(NOTE 1, NOTE 2)
O(NOTE 3)
> MB2-U information
O
IP address, UDP port number of the MB2-U interface.
> xMB-U information
O
IP address, UDP port number of the xMB-U interface.
> M1 interface information
O
M1 interface information for local MBMS.
Local MBMS activation indication (NOTE 1, NOTE 2)
O
Indicates whether to request the NRM server to use Local MBMS information.
NOTE 1: The VAL server may provide either the Local MBMS information or the Local MBMS activation indication. This IE is present when the local MBMS is required for VAL services like V2X service.
NOTE 2: This information element is only applicable when EPS is specified in the network system indicator IE.
NOTE 3: At least one of those IEs shall be present.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.43 Multicast/broadcast resource update response
|
Table 14.3.2.43-1 describes the information flow for the Multicast/broadcast resource update response from NRM server to VAL server.
Table 14.3.2.43-1: Multicast/broadcast resource update response
Information element
Status
Description
Result
M
The result indicates success or failure of the multicast/broadcast resource update request operation.
Identity of the multicast/broadcast resource
M
(NOTE 1)
The identity of the multicast/broadcast MBS session, or/and the identity of the MBMS bearer to be updated.
New Identity of the multicast/broadcast resource
O
The identity of the new multicast/broadcast MBS session created during update.
User plane address
O
Additional user plane IP address(es) and port for VAL to deliver the DL packet.
Session description information
O
(NOTE 2)
Indicates Multicast/broadcast related configuration information as defined in 3GPP TS 26.346 [28] (e.g. radio frequency and MBMS Service Area Identities) or/and 3GPP TS 23.247 [39] (e.g. MBS FSA ID(s), Area Session ID, service requirements)
NOTE 1: This IE may not be required if the session announcement mode indicates that the request is sent by the NRM server.
NOTE 2: If the Result Information element indicates failure then the values of the other information elements shall not present.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.44 Multicast/broadcast resource delete request
|
Table 14.3.2.44-1 describes the information flow for the multicast/broadcast resource delete request from VAL server to NRM server.
Table 14.3.2.44-1: Multicast/broadcast resource delete request
Information element
Status
Description
Requester Identity
M
The identity of the VAL server performing the request.
Identity of the multicast/broadcast resource
M
Identity of the multicast/broadcast resource, i.e., the MBS session ID for 5G MBS, TMGI for 4G MBMS, or both
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.45 Multicast/broadcast resource delete response
|
Table 14.3.2.45-1 describes the information flow for the Multicast/broadcast resource delete response from NRM server to VAL server.
Table 14.3.2.45-1: Multicast/broadcast resource delete response
Information element
Status
Description
Result
M
The result indicates success or failure of the multicast/broadcast resource delete request operation.
Identity of the multicast/broadcast resource
M
The identity of the multicast/broadcast MBS session, or/and the identity of the MBMS bearer.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.46 Multicast resource activate request
|
Table 14.3.2.46-1 describes the information flow for the multicast resource activate request from VAL server to NRM server.
Table 14.3.2.46-1: Multicast resource activate request
Information element
Status
Description
Requester Identity
M
The identity of the VAL server performing the request.
MBS session ID
M
Identity of multicast MBS session
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.47 Multicast resource activate response
|
Table 14.3.2.47-1 describes the information flow for the multicast resource activate response from NRM server to VAL server.
Table 14.3.2.47-1: Multicast resource activate response
Information element
Status
Description
Result
M
The result indicates success or failure of the multicast resource activate operation.
MBS session ID
M
Identity of multicast MBS session
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.48 Multicast resource deactivate request
|
Table 14.3.2.48-1 describes the information flow for the multicast resource deactivate request from VAL server to NRM server.
Table 14.3.2.48-1: Multicast resource deactivate request
Information element
Status
Description
Requester Identity
M
The identity of the VAL server performing the request.
MBS session ID
M
Identity of multicast MBS session
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.49 Multicast resource deactivate response
|
Table 14.3.2.49-1 describes the information flow for the multicast resource deactivate response from NRM server to VAL server.
Table 14.3.2.49-1: Multicast resource deactivate response
Information element
Status
Description
Result
M
The result indicates success or failure of the multicast resource deactivate operation.
MBS session ID
M
Identity of multicast MBS session
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.50 MapVALGroupToSessionStream
|
Table 14.3.2.50-1 defines the MapVALGroupToSessionStream to be sent from the NRM server to NRM clients to provide specific required information to receive the media related to a group related VAL data communication within an MBS session.
Table 14.3.2.50-1: MapVALGroupToSessionStream
Information element
Status
Description
VAL group ID
M
This element identifies the VAL group related to a group related VAL data communication to be delivered over the MBS session.
VAL data stream identifier
M
This element identifies the VAL data stream of the SDP used for the group related VAL data communication within the MBS session.
MBS session ID
O
The MBS session identifier if the MapVALGroupToSessionStream message is not sent on the same session as the VAL data
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.51 UE session join notification
|
Table 14.3.2.51-1 defines the UE session join notification to be sent from the NRM client to NRM server after successfully joining a certain multicast MBS session procedure as defined in 3GPP TS 23.247 [39].
Table 14.3.2.51-1: UE session join notification
Information element
Status
Description
MBS session ID(s)
M
The identity of the multicast MBS session(s) being joined. It is either TMGI or source specific IP multicast address.
VAL user ID or VAL UE ID
M
The identity of the VAL user or VAL UE who sends this notification.
MBS multicast joining status
M
UE’s multicast MBS session status per MBS session ID, e.g., successfully joined.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.52 MBS listening status report
|
Table 14.3.2.52-1 describes the information flow of MBS listening status report from the NRM client to the NRM server. The MBS listening status report is applicable to both broadcast and multicast MBS sessions.
Table 14.3.2.52-1: MBS listening status report
Information element
Status
Description
VAL user ID or VAL UE ID
M
The identity of the VAL user or VAL UE who wants to report the MBS listening status.
MBS session ID(s)
M
The identity of the MBS session(s) being monitored.
MBS listening status
M
The listening status per MBS session ID.
MBS reception quality level (NOTE)
O
The reception quality level
Unicast listening status
O
The unicast listening status associated with the unicast delivery.
NOTE: The set of quality levels helps service continuity in broadcast and multicast scenarios. A reception quality level may help to make an efficient switching decision to unicast delivery. How these levels are used is implementation specific.
14.3.2.53 UE unified traffic pattern and monitoring management subscription request
Table 14.3.2.53-1 describes the information flow for the UE unified traffic pattern and monitoring management subscription request from the VAL server to the NRM Server.
Table 14.3.2.53-1: UE unified traffic pattern and monitoring management subscription request
Information element
Monitoring
Description
VAL UE ID
M
UEs hosting clients for which the subscription is requested
VAL service ID
M
Identity of the VAL service for which the subscription is requested.
Management subscription indications
M
At least one of the following indications is to be provided
> UE unified traffic pattern monitoring management indication
O
Indicates that management of the UE unified traffic pattern is requested
> UE unified traffic pattern update notification indication
O
Indicates that notifications for updates of the UE unified traffic pattern monitoring is requested
> Network parameter coordination indication
O
Indicates whether network parameter coordination by the NRM with 5GC is requested (see NOTE 1)
traffic pattern configuration
O
Traffic pattern configuration of the VAL service for this UE, as described in table 14.3.2.53-2.
NOTE 1: The network parameter coordination functionality is also subject to policies available at the NRM Server.
Table 14.3.2.53-2: VAL traffic pattern configuration
Information element
Monitoring
Description
Schedule elements
O
List of schedule elements applicable to the traffic patterns of the VAL service for this UE. Each schedule element is composed from seven fields: second, minute, hour, day of month, month, day of week and year. Each element indicates times or durations when the service traffic occurs. Multiple schedule elements can be used to create complex scheduling. (see NOTE 2)
Expiration time
O
Identifies when the VAL traffic pattern parameter configuration expires. If absent, it indicates that there is no expiration time.
Stationary indication
O
Identifies whether the UE is expected to be stationary or mobile while communicating using this traffic pattern configuration
NOTE 2: The following is an example of a schedule element with the fields: second, minute, hour, day of month, month, day of week and year:
*; 0-30 ; 2; *; Jan-Sept; Tues; *.
The following mapping is provided for information, if this schedule element is derived from communication patterns as described in 3GPP TS 29.122 [54] clause 5.10
- periodicCommunicationIndicator: TRUE
- communicationDurationTime: 30 min
- periodicTime: 1 week
- scheduledCommunicationTime: Tues, 2:00-2:30
- validityTime: calculated using the Jan-Sept range and the provided expiration time.
NOTE 3: The format of this IE is to be provided in stage 3. The purpose of this description is to clarify how the same element can contain multiple periodicities, specify start/stop times, etc.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.54 UE unified traffic pattern and monitoring management subscription response
|
Table 14.3.2.54-1 describes the information flow for the UE unified traffic pattern and monitoring management subscription response from the NRM server to the VAL server.
Table 14.3.2.54-1: UE unified traffic pattern and monitoring management subscription response
Information element
Monitoring
Description
Result
M
Indicates success or failure of the subscription request
14.3.2.55 UE unified traffic pattern update notification
Table 14.3.2.55-1 describes the information flow for the UE unified traffic pattern update notification from the NRM server to the VAL server.
Table 14.3.2.55-1: UE unified traffic pattern update notification
Information element
Monitoring
Description
UE ID
M
UE for which the UE unified traffic pattern update notification is provided for.
Schedule elements
O
Schedule element applicable to the unified traffic patterns of the UE. A schedule element is composed from seven fields: second, minute, hour, day of month, month, day of week and year. Each element indicates times or durations of UE availability.
Stationary indication
O
Identifies whether the UE is expected to be stationary or mobile while communicating using this UE unified traffic pattern, as determined by the NRM Server
Cause
O
This element is mandatory when the notification is provided to inform of a parameter configuration applied by the network which is incompatible with the existing Traffic Patterns. (see NOTE)
The element is optional when the notification informs of UE unified traffic pattern updates, providing additional information on the reason for the UE unified traffic pattern update (e.g. monitoring events received)
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.56 Get application connectivity context request.
|
Table 14.3.2.56-1 describes the information flow for application connectivity context request from the NRM server to the NRM client, the context applying to UE-to-UE application-level direct communications.
Table 14.3.2.56-1: Get Application connectivity context request.
Information element
Status
Description
Requester VALUE ID
M
The identity of the source VAL client for which the NRM client performs the request.
VAL service ID
M
Identify of the VAL service for which the information is requested.
VAL-specific connection coordination context information
O
Additional information required to identify the context data (e.g. device type, device vendor, etc)
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.57 Get application connectivity context response.
|
Table 14.3.2.57-1 describes the information flow for application connectivity context response from the NRM client to the NRM server, the context applying to UE-to-UE application-level direct communications.
Table 14.3.2.57-1: UE-to-UE connection coordination context response
Information element
Status
Description
Result
M
The result indicates success or failure of the UE-to-UE resource coordination response operation.
Application connectivity context (see NOTE)
O
Application connectivity context used for determining connectivity parameters. If this IE is included, at least one of the information elements in Table 14.3.2.35-2 shall be provided.
NOTE: When this information element is not included, the NRM server considers default or pre-provisioned values.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.58 BDT configuration request
|
Table 14.3.58-1 describes the information flow for the BDT configuration request from the VAL server to the NRM Server.
Table 14.3.2.58-1: BDT configuration request
Information element
Status
Description
VAL service ID
M
Identity of the VAL service for which the configuration is requested.
List of VAL UE IDs
M
List of VAL UE IDs for which the transfer policy applies or a VAL group ID.
Number of UEs
M
Expected number of UEs.
Volume per UE
M
Expected data volume for the background data transfer.
Desired time window
M
Desired time window for the background data transfer.
Desired area information
M
Desired geographical area for the background data transfer
Application traffic descriptors
O
Application traffic descriptors (e.g. addresses, port, transport layer protocol) of the VAL server.
Request expiration time
O
Expiration time for the background data transfer request to enable NRM server to delay BDT negotiation with 3GPP core network considering BDT configuration requests from other VAL servers.
Policy Selection Guidance
O
List that includes guidance to the NRM in selecting from multiple transfer policies provided by underlying network. Possible values include: ”lowest cost”, “highest throughput given maximum cost of X”, etc.
If not included, the NRM may choose from among multiple transfer policies, depending on local and ASP-provided policies.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.59 BDT configuration response
|
Table 14.3.2.59-1 describes the information flow for BDT configuration response from the NRM server to the VAL server.
Table 14.3.2.59-1: BDT configuration response
Information element
Status
Description
Result
M
The result indicates success or failure of the BDT configuration operation.
BDT configuration identifier (NOTE)
O
Identifier of the BDT configuration information stored at the NRM server
BDT Reference ID (see NOTE)
O
Indicates the Background data transfer Reference ID provided by the 3GPP network
Granted time window (see NOTE)
O
Granted time window for the background data transfer.
NOTE: These IEs shall be included when Result is success.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.60 BDT negotiation notification
|
Table 14.3.2.60-1 describes the information flow for BDT negotiation notification from the NRM server to the VAL server.
Table 14.3.2.60-1: BDT negotiation notification
Information element
Status
Description
BDT configuration identifier
M
Identifier of the BDT configuration information stored at the NRM server
Granted time window (see NOTE)
O
Granted time window for the background data transfer.
BDT Reference ID
M
Indicates the Background data transfer Reference ID provided by the 3GPP network
BDT policy removal indicator (see NOTE)
O
The indicator about the BDT policy removal.
NOTE: Either of these IEs are included.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.61 BDT configuration get request
|
Table 14.3.2.61-1 describes the information flow for the BDT configuration get request from the VAL server to the NRM Server.
Table 14.3.2.61-1: BDT configuration get request
Information element
Status
Description
VAL service ID
M
Identity of the VAL service for which the BDT configuration is requested to be updated.
BDT configuration identifier
M
Identifier of the BDT configuration stored in the NRM server.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.62 BDT configuration get response
|
Table 14.3.2.62-1 describes the information flow for BDT configuration get response from the NRM server to the VAL server.
Table 14.3.2.62-1: BDT configuration get response
Information element
Status
Description
Result
M
The result indicates success or failure of BDT configuration get operation.
BDT configuration identifier
M
Identifier of the BDT configuration stored in the NRM server.
BDT configuration data (see NOTE)
O
The BDT configuration data stored at the NRM server which includes information like VAL service ID, List of VAL UE IDs/VAL group ID, Volume per UE, Desired Time Window, Granted Time Window, Desired Area Information, Policy Selection Guidance, BDT Reference ID
NOTE: The BDT configuration data IE is included if the Result indicates success.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.63 BDT configuration update request
|
Table 14.3.2.63-1 describes the information flow for the BDT configuration update request from the VAL server to the NRM Server.
Table 14.3.2.63-1: BDT configuration update request
Information element
Status
Description
VAL service ID
M
Identity of the VAL service for which the BDT configuration is requested to be updated.
BDT Configuration identifier
M
Identifier of the BDT configuration stored in the NRM server.
Number of UEs
O
Expected number of UEs.
Volume per UE (see NOTE)
O
Updated expected data volume for the background data transfer.
Desired time window (see NOTE)
O
Updated desired time window for the background data transfer.
Desired area information (see NOTE)
O
Updated desired geographical area for the background data transfer
Application traffic descriptors (see NOTE)
O
Application traffic descriptors (e.g. addresses, port, transport layer protocol) of the VAL server.
Request expiration time (see NOTE)
O
Expiration time for the background data transfer request to enable NRM server to delay BDT negotiation with 3GPP core network considering BDT configuration requests from other VAL servers.
Policy Selection Guidance (see NOTE)
O
Updated list that includes guidance to the NRM in selecting from multiple transfer policies provided by underlying network. Possible values include: ”lowest cost”, “highest throughput given maximum cost of X”, etc.
If value is empty, the NRM may choose from among multiple transfer policies, depending on local and ASP-provided policies.
NOTE: At least one of the IEs shall be present
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.64 BDT configuration update response
|
Table 14.3.2.64-1 describes the information flow for BDT configuration update response from the NRM server to the VAL server.
Table 14.3.2.64-1: BDT configuration update response
Information element
Status
Description
Result
M
The result indicates success or failure of BDT configuration update operation.
BDT Configuration identifier
M
Identifier of the BDT configuration stored in the NRM server.
Granted time window
(see NOTE)
O
Granted time window for the background data transfer.
NOTE: This IE shall be included when Result is success and changed as consequence of the configuration update request.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.65 BDT configuration delete request
|
Table 14.3.2.65-1 describes the information flow for the BDT configuration delete request from the VAL server to the NRM Server.
Table 14.3.2.65-1: BDT configuration delete request
Information element
Status
Description
VAL service ID
M
Identity of the VAL service for which the BDT configuration is requested to be deleted.
BDT configuration identifier
M
Identifier of the BDT configuration stored in the NRM server.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.66 BDT configuration delete response
|
Table 14.3.2.66-1 describes the information flow for BDT configuration delete response from the NRM server to the VAL server.
Table 14.3.2.66-1: BDT configuration delete response
Information element
Status
Description
Result
M
The result indicates success or failure of BDT configuration delete operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.67 Reliable transmission request
|
Table 14.3.2.67-1 describes the information flow for reliable transmission request from SEALDD server (or VAL server) to the NRM server.
Table 14.3.2.67-1: Reliable transmission request
Information element
Status
Description
Requester Identity
M
The identity of the SEALDD server (or VAL server) performing the request.
Application descriptors
O
A pair of applic traffic descriptors (e.g. address, port, transport layer protocol) of the SEALDD server (or VAL server), used to establish redundant transmission paths.
UE ID
O
The identity of VAL UE.
UE address
O
The address of VAL UE
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.68 Reliable transmission response
|
Table 14.3.2.68-1 describes the information flow for the reliable transmission response from NRM server to SEALDD server (or VAL server).
Table 14.3.2.68-1: Reliable transmission response
Information element
Status
Description
Result
M
The result indicates success or failure of the reliable transmission request operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.69 Device triggering request
|
Table 14.3.69-1 describes the information flow for the Device triggering request from the VAL server to the NRM Server.
Table 14.3.2.69-1: Device triggering request
Information element
Status
Description
Identifier
M
VAL UE ID or VAL group ID to be triggered.
Port number
O
Device triggering port number. If not provided, NRM determines the port number to be used based on local policies.
Triggering purpose
M
Indicates the device triggering purpose which is included in the payload. The default is a reserved value e.g. NULL.
Time window
O
Desired time window for the trigger. This value may be used by NRM to determine when to initiate the TS 23.682 device triggering procedure, and/or to determine the trigger validity time value used.
Area information
O
Desired geographical area for trigger.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.70 Device triggering response
|
Table 14.3.2.70-1 describes the information flow for Device triggering response from the NRM server to the VAL server.
Table 14.3.2.70-1: Device triggering response
Information element
Status
Description
Result
M
The result indicates success or failure of the operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.71 MM-specific QoS management request
|
Table 14.3.2.71-1 describes the information flow MM-specific QoS management request from the NRM client to the NRM server.
Table 14.3.2.71-1: MM-specific QoS management request
Information element
Status
Description
List of VAL UEs or VAL Group ID
M
List of VAL UEs or the group of VAL UEs for whom the MM QoS management occurs.
>VAL UE/user ID
M
Identity of the VAL UE.
> Connection information
O
Connection information including address / port and / or URL of the VAL UE.
List of VAL servers
M
The list of VAL servers involved in the mobile metaverse service.
> VAL server ID
M
Identity of the VAL server.
> Connection information
O
Connection information including address / port and / or URL of the VAL server.
MM service or session(s) ID
O
The VAL service or session(s) identity for whom the QoS management occurs.
MM QoS requirements
O
The mobile metaverse QoS requirements / KPIs (latency, error rate, ..) for the MM end to end service.
This may optionally include information which will support the NRM server to identify the per session QoS requirements.
VAL session information
O
Information and dependencies (e.g. sequence or priority) among VAL sessions within MM service.
Service area
O
The area where the QoS management request applies. This can be geographical area, or topological area.
Time validity
O
The time of validity of the requirement.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.72 MM-specific QoS management response
|
Table 14.3.2.72-1 describes the information flow MM-specific QoS management response from the NRM server to the NRM client.
Table 14.3.2.72-1: MM-specific QoS management response
Information element
Status
Description
Result
M
The positive or negative result of the MM-specific QoS management request.
QoS report configuration
O
The configuration of the NRM client's report triggering by NRM server (e.g. setting thresholds for reporting a QoS downgrade / notifications based on channel loss great than threshold value)
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.2.73 MM service QoS configuration notification
|
Table 14.3.2.73-1 describes the information flow MM service QoS configuration notification from the NRM server to the NRM client or to the VAL server.
Table 14.3.2.73-1: MM service QoS configuration notification
Information element
Status
Description
MM service ID
M
The VAL service identity for whom the QoS management occurs.
VAL session ID
M
The VAL session for which the QoS is configured.
>MM QoS configuration
M
The configuration of the QoS attributes (latency, jitter) for the VAL sessions within the MM service
QoS report configuration
O
The configuration of the NRM client's or VAL server report triggering by NRM server (e.g. setting thresholds for reporting a QoS downgrade / notifications based on channel loss great than threshold value)
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.3 Unicast resource management
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.3.1 General
|
The following subclauses specify the procedures for unicast resource management for vertical application layer. The NRM server sets up bearers and may need to modify the bearers for an already established VAL service communication.
Characteristics that may need to be modified include:
- activation and deactivation of the bearer;
- modification of the QoS characteristics of the bearer (e.g. bearer priority adjustment); and
- modification of GBR due to application requirement
NOTE: A VAL service communication can consist of both unicast and multicast bearers which can all need modification due to the same event.
Vertical application layer specific pre-requisites and resultant behaviour by functional entities in performing these procedures are specified in the respective vertical application layer TS (e.g. for V2X application layer, see 3GPP TS 23.286 [7]).
Unicast resource management is supported with PCC interactions with SIP core and PCC interactions with NRM server. The PCC procedures for EPS are specified in 3GPP TS 23.203 [18] and the PCC procedures for 5GS are specified in 3GPP TS 23.503 [19].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.3.2 Unicast resource management with SIP core
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.3.2.1 Request for unicast resources at VAL service communication establishment
|
14.3.3.2.1.1 General
The procedure defined in this subclause specifies how network resources are requested at VAL service communication establishment. If concurrent sessions are used the NRM server may utilize the capability of resource sharing specified for underlying network policy and charging functions. The request for resources includes application type, bandwidth, priority, application identifier and resource sharing information.
14.3.3.2.1.2 Procedure
The procedure is generic to any type of session establishment that requires requests for network resources.
Procedures in figure 14.3.3.2.1.2-1 are the signalling procedures for the requesting resource at session establishment.
Pre-condition:
- The VAL client has requested VAL service communication with the VAL server.
Figure 14.3.3.2.1.2-1: Resource request at VAL service communication establishment
1. The VAL server sends request for resources to the NRM server.
2. The NRM server evaluates the need for network resources and use of resource sharing.
3. The NRM server sends a session progress request containing request for resources.
4. PCC procedures are initiated from SIP core local inbound/outbound proxy.
5. The SIP core local inbound / outbound proxy sends a OK message to the NRM server.
6. The NRM server sends a resource response to the VAL server.
7. The VAL service communication is established, and resources have been allocated.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.3.2.2 Request for modification of unicast resources
|
14.3.3.2.2.1 General
To modify unicast bearers, the NRM server shall send a resource modification request containing the parameters to be modified for the UE.
Possible scenarios when this procedure may be used are:
- Modify the allocation and retention priority for unicast resources;
- Release and resume resources in-between VAL service communications; or
- Release and resume resources when a UE is able to receive the VAL service communications over multicast transmission
14.3.3.2.2.2 Procedure
Procedures in figure 14.3.3.2.2.2-1 are the signalling procedures for the modification of a unicast:
Pre-condition:
- A VAL service communication is already in progress;
Figure 14.3.3.2.2.2-1: Bearer modification request
1. The VAL server sends a resource modification request to the NRM server.
2a. The NRM server decides to modify the parameters of a unicast bearer.
2b. If the media bearer modification is not required, the NRM server sends a resource modification response to the VAL server.
3. The NRM server sends a session update which includes a resource modification request containing the modified parameters of the unicast bearer.
4. PCC procedures are initiated from SIP core local inbound/outbound proxy.
5. The SIP core local inbound / outbound proxy sends a OK message to the NRM server.
6. The NRM server sends a resource modification response to the VAL server.
7. The VAL service communication continues with the modified unicast resources.
NOTE 1: If the VAL service communication is transferred to multicast transmission, the unicast resources could be temporarily be released.
NOTE 2: If multiple VAL service communication streams are sent to the UE, additional bearer resources could be required during an established VAL service communication. Pre-allocation of additional bearer resources already at VAL service communication establishment could be useful.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.3.3 Unicast resource management without SIP core
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.3.3.1 Network resource adaptation
|
14.3.3.3.1.1 General
This subclause describes the procedure for network resource adaptation using PCC procedures. This procedure satisfies the requirements for requesting unicast resources and modification to already allocated unicast resources to VAL communications.
14.3.3.3.1.2 Procedure
Figure 14.3.3.3.1.2-1 illustrates the procedure for the network resource adaptation.
Figure 14.3.3.3.1.2-1: Network resource adaptation
1. The VAL server (or SEALDD server) sends a network resource adaptation request to the NRM server for one or more users belonging to one or more VAL services, and may comprise one or more VAL UEs that will have updated resource requirement. This requirement may be in the form of exact resources /resource pools to be used or indication of bandwidth increase/decrease for the corresponding VAL UEs or set of VAL UEs. The BDT Reference ID may also be included for setting BDT policies.
NOTE: The SEALDD server can use the NRM netwok resource adaption service as per the procedure defined in 3GPP TS 23.433 clause 9.11 SEALDD Background data transfer.
2. The NRM server processes the request and applies / enforces the resource adaptation per VAL UE.
3. The NRM server retrieves UE IP address by using event monitoring capability for PDU session status (or PDN connectivity status) and initiates the PCC procedures for each VAL UE.
4. The NRM server provides a network resource adaptation response to the VAL server, providing information on the fulfilment of the network resource adaptation request. This will include information either per VAL UE or per set of VAL UEs, as indicated by the request of the VAL server in step 1.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.3.3.2 Request for unicast resources at VAL service communication establishment
|
14.3.3.3.2.1 General
The procedure defined in this subclause specifies how network resources are requested at VAL service communication establishment. If concurrent sessions are used the NRM server may utilize the capability of resource sharing specified for underlying network policy and charging functions. The request for resources includes application type, bandwidth, priority, application identifier and resource sharing information.
14.3.3.3.2.2 Procedure
The procedure is generic to any type of session establishment that requires requests for network resources.
Procedures in figure 14.3.3.3.2.2-1 are the signalling procedures for the requesting resource at session establishment.
Pre-condition:
- The VAL client has requested VAL service communication with the VAL server.
Figure 14.3.3.3.2.2-1: Resource request at VAL service communication establishment
1. The VAL server sends request for resources to the NRM server.
2. The NRM server evaluates the need for network resources and use of resource sharing.
3. The NRM server retrieves UE IP address by using event monitoring capability for PDU session status (or PDN connectivity status), and then PCC procedures are initiated from NRM server.
4. The NRM server sends a resource response to the VAL server.
5. The VAL service communication is established, and resources have been allocated.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.3.3.3 Request for modification of unicast resources
|
14.3.3.3.3.1 General
To modify unicast resources, the NRM server shall send a resource modification request containing the parameters to be modified for the UE.
Possible scenarios when this procedure may be used are:
- Modify the allocation and retention priority for unicast resources;
- Release and resume resources in-between VAL service communications; or
- Release and resume resources when a UE is able to receive the VAL service communications over multicast transmission
14.3.3.3.3.2 Procedure
Procedures in figure 14.3.3.3.3.2-1 are the signalling procedures for the modification of a unicast:
Pre-condition:
- A VAL service communication is already in progress;
Figure 14.3.3.3.3.2-1: Bearer modification request
1. The VAL server sends a resource modification request to the NRM server.
2a. The NRM server decides to modify the parameters of a unicast bearer.
2b. If the media bearer modification is not required, the NRM server sends a resource modification response to the VAL server.
3. PCC procedures are initiated from NRM server.
4. The NRM server sends a resource modification response to the VAL server.
5. The VAL service communication continues with the modified unicast resources.
NOTE 1: If the VAL service communication is transferred to multicast transmission, the unicast resources could be temporarily be released.
NOTE 2: If multiple VAL service communication streams are sent to the UE, additional bearer resources could be required during an established VAL service communication. Pre-allocation of additional bearer resources already at VAL service communication establishment could be useful.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.3.4 Unicast QoS monitoring
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.3.4.1 Unicast QoS monitoring subscription procedure
|
14.3.3.4.1.1 General
This subclause describes the high level procedure for unicast QoS monitoring subscription. This procedure satisfies the requirements for monitoring of unicast QoS for already allocated unicast resources to VAL communications.
14.3.3.4.1.2 Procedure
Figure 14.3.3.4.1.2-1 illustrates the high level procedure for unicast QoS monitoring subscription.
Pre-conditions:
- The VAL UE has an established connection in the 5GS
- The VAL server may have Monitoring profile ID pre-configured in the NRM server local configuration.
Figure 14.3.3.4.1.2-1: Unicast QoS monitoring subscription
1. The VAL server sends a unicast QoS monitoring subscription request to the NRM server either in conjunction with a request for unicast network resources requiring QoS or when the unicast QoS connection is already established. The NRM server checks if the VAL server is authorized to initiate the unicast QoS monitoring request for the requested target VAL UEs, VAL group ID, or VAL stream IDs. The request may include monitoring profile (represents the monitoring and reporting requirements) or list of monitoring profile identifiers.
NOTE: It is left for stage 3 to decide whether to combine the QoS monitoring subscription request with the request for unicast resources.
2. If the the monitoring profile ID and monitoring profile information elements are not provided, the NRM server shall determine the monitoring profile including the QoS measurement requirements and reporting requirements with subscription termination criteria based on the VAL service identifier and/or requester identity received in step 1. If monitoring profile ID is provided in step 1, the NRM server shall obtain the corresponding monitoring profile internally and apply for the subscription. The NRM server interacts with the NEF to establish relevant QoS monitoring subscriptions. The NRM server uses the NEF procedures for the AFsessionWithQoS described in clause 5.2.6.9 of 3GPP TS 23.502 [11] and the NEF procedures for the AnalyticsExposure described in clause 5.2.6.16 of 3GPP TS 23.502 [11] and in particular the UE Communication Analytics described in clause 6.7.3 of 3GPP TS 23.288 [34] and DN Performance Analytics described in clause 6.14 of 3GPP TS 23.288 [34]. Based on the input received from the VAL server in step 1, the NRM server determines the relevant NEF subscription procedures and the parameters for these subscriptions, such as the QoS parameters to be measured (e.g. packet delay, data rate, traffic volume), the frequency of reporting etc. For the frequency of reporting which can be event triggered, periodic, or when the PDU Session is released, the NRM server determines the following:
a) if the reporting frequency is event triggered:
i) the corresponding reporting threshold to each QoS parameter;
ii) minimum waiting time between subsequent reports;
b) if the reporting frequency is periodic, the reporting period.
3. The NRM server responds with a unicast QoS monitoring subscription response indicating the subscription status. If the monitoring profile is not provided in step 1, the NRM server shall provide the proposed termination of reporting condition.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.3.4.2 Unicast QoS monitoring notification procedure
|
14.3.3.4.2.1 General
This subclause describes the high level procedure for unicast QoS monitoring notification.
14.3.3.4.2.2 Procedure
Figure 14.3.3.4.2.2-1 illustrates the high level procedure of unicast QoS monitoring notification event.
Pre-conditions:
- The VAL server has an active unicast QoS monitoring subscription with the NRM server
Figure 14.3.3.4.2.2-1: Unicast QoS monitoring notification procedure
1. The NRM server receives QoS monitoring data by means of notifications provided by the NEF. The NRM server coordinates and combines the information from the NEF notifications and determines whether to send a notification to the VAL server based on the VAL server subscription's frequency of reporting. For a VAL group or a list of VAL UEs, the NRM server aggregates QoS monitoring data for each UE belonging to the group or the list; for a VAL stream, the NRM server aggregates the QoS monitoring data for the stream. The NRM server stores the QoS monitoring data as needed for later retrieval.
2. The NRM server sends a unicast QoS monitoring notification including the measured QoS data and monitoring profile identifier whose reporting requirements triggered notification to the VAL server. If the reporting termination criteria is met (e.g. number of reports reached, threshold reached), NRM server shall also terminate the subscription and notify the VAL server about the subscription termination.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.3.4.3 Unicast QoS monitoring subscription termination procedure
|
14.3.3.4.3.1 General
This subclause describes the high level procedure for unicast QoS monitoring subscription termination.
14.3.3.4.3.2 Procedure
Figure 14.3.3.4.3.2-1 illustrates the high level procedure of unicast QoS monitoring subscription termination.
Pre-conditions:
- The VAL server has an active unicast QoS monitoring subscription with the NRM server
Figure 14.3.3.4.3.2-1: Unicast QoS monitoring subscription termination procedure
1. When the VAL server decides to terminate a unicast QoS monitoring subscription, it sends a QoS monitoring unsubscribe request to the NRM server.
2. The NRM server interacts with the NEF to terminate the related QoS monitoring subscriptions.
3. The NRM server sends a QoS monitoring unsubscribe response to the VAL server.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.3.4.4 Unicast QoS monitoring data retrieval procedure
|
14.3.3.4.4.1 General
This subclause describes the high level procedure for unicast QoS monitoring data retrieval.
14.3.3.4.4.2 Procedure
Figure 14.3.3.4.4.2-1 illustrates the high level procedure of unicast QoS monitoring data retrieval.
Figure 14.3.3.4.4.2-1: Retrieval of unicast QoS monitoring data
1. The VAL server sends a unicast QoS monitoring data request to the NRM server specifying the details of the requested data and the time period of interest. The NRM server checks if the VAL server is authorized to initiate the unicast QoS monitoring data request for the requested target VAL UEs, VAL group ID, or VAL stream IDs.
2. The NRM server determines if it has the requested data stored internally or whether it needs to interact with the NEF to fetch the data using the AnalyticsExposure described in clause 5.2.6.16 of 3GPP TS 23.502 [11] and in particular the UE Communication Analytics described in clause 6.7.3 of 3GPP TS 23.288 [34] and DN Performance Analytics described in clause 6.14 of 3GPP TS 23.288 [34]. The NRM server collects and processes the collected data to match the measurement data requirement provided in the VAL server request.
3. The NRM server responds with a unicast QoS monitoring data response with the requested data or with a failure indication, and optionally the cause of the failure, in case the requested data is not available.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.3.4.5 Unicast QoS monitoring subscription update procedure
|
14.3.3.4.5.1 General
This subclause describes the high-level procedure to update unicast QoS monitoring subscription. This procedure updates the parameters to be monitored of an already existing unicast QoS monitoring subscription.
14.3.3.4.5.2 Procedure
Figure 14.3.3.4.5.2-1 illustrates the high level procedure for unicast QoS monitoring subscription update.
Pre-conditions:
- The VAL UE has an established connection in the 5GS
- Unicast QoS monitoring subscription has successfully been invoked established for the VAL UE
Figure 14.3.3.4.5.2-1: Unicast QoS monitoring subscription update
1. The VAL server sends a unicast QoS monitoring subscription update request to the NRM server. It shall refer to an existing subscription, identified by the list of VAL UEs, VAL UE group or VAL stream IDs included into the message.
2. The NRM server interacts with the NEF to update the relevant QoS monitoring subscription parameters and reporting frequency as specified in step 2 of clause 14.3.3.4.1.2 of this document.
3. The NRM server responds with a unicast QoS monitoring subscription update response indicating the subscription status.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.4 Multicast resource management for EPS
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.4.1 General
|
The VAL server utilizes the NRM server for multicast resource management.
To activate the multicast bearers in the EPS, the NRM server shall use the Activate MBMS Bearer procedure specified in 3GPP TS 23.468 [16] with the NRM server performing the GCS AS function.
To deactivate the multicast bearers in the EPS, the NRM server shall use the Deactivate MBMS Bearer procedure specified in 3GPP TS 23.468 [16] with the NRM server performing the GCS AS function.
To modify multicast bearers in the EPS, the NRM server shall use the Modify MBMS Bearer procedure specified in 3GPP TS 23.468 [16] with the NRM server performing the GCS AS function.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.4.2 Use of pre-established MBMS bearers
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.4.2.1 General
|
In this scenario, upon triggered by VAL server, the NRM server pre-establishes MBMS bearer(s) in certain pre-configured areas before the initiation of the VAL service group communication session. When a user originates a request for a VAL service group communication session for one of these areas, the pre-established MBMS bearer(s) is used for the DL VAL service communication.
The following steps need to be performed prior to the start of the VAL service group communication session over pre-established MBMS bearer:
- Pre-establish MBMS bearer(s)
- Announce the pre-established MBMS bearer to the NRM clients
When these preparation steps have been done the VAL service group communication session using MBMS bearer can start.
The vertical application level communications are sent on the MBMS bearer. Optionally a separate MBMS bearer could be used for the application level control messages, due to different bearer characteristic requirements.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.4.2.2 Procedure
|
The procedure figure 14.3.4.2.2-1 shows only one of the receiving VAL clients using an MBMS bearer. There might also be VAL clients in the same VAL service group communication session that receive the communication on unicast bearers.
Figure 14.3.4.2.2-1: Use of pre-established MBMS bearers
1. The VAL server sends a MBMS bearers request to the NRM server including service description(s) for which the MBMS bearers are requested.
2a. The NRM server determines to activate MBMS bearer. The activation of the MBMS bearer in EPS is done on the MB2-C reference point and according to 3GPP TS 23.468 [16]. This bearer will be used for the VAL service communication. If local MBMS is requested in step 1, the NRM server uses the local MBMS information provided by VAL server in step 1 or the local MBMS information configured locally in the NRM server to activate the MBMS bearers. The NRM server performs local MBMS procedures in line with the procedure of L.MBMS based MBMS data delivery defined in 3GPP TS 23.285 [31].
2b. Optionally, the NRM server may also activate an MBMS bearer dedicated for application level control signalling. The activation of the MBMS bearer is done on MB2-C reference point and according to 3GPP TS 23.468 [16]. If local MBMS is requested in step 1, the NRM server uses the local MBMS information provided by VAL server in step 1 or the local MBMS information configured locally in the NRM server to activate the MBMS bearers. The NRM server performs local MBMS procedures in line with the procedure of L.MBMS based MBMS data delivery defined in 3GPP TS 23.285 [31].
NOTE 1: The procedure to determine the activation of MBMS bearers is implementation specific.
3a. The NRM server passes the MBMS bearer info for the service description associated with the pre-established MBMS bearer to the NRM client. The NRM client obtains the TMGI, identifying the MBMS bearer, from the service description.
3b. The NRM server may pass the MBMS bearer info for the service description associated with the application control MBMS bearer to the NRM client. The NRM client obtains the TMGI, identifying the MBMS bearer, from the service description.
NOTE 2: Step 3a and step 3b can be done in one MBMS bearer announcement message.
4. The NRM client stores the information associated with the TMGI(s). The NRM service client uses the TMGI and other MBMS bearer related information to activate the monitoring of the MBMS bearer by the VAL UE. The NRM client shares the MBMS bearer related information with the VAL client.
5. The NRM client that enters or is in the service area of at least one announced TMGI indicates to the NRM server that the VAL UE is able to receive VAL service communication over MBMS, whereby the NRM server may decide to use the MBMS bearer instead of unicast bearer for VAL service communication sessions based on available information at the NRM server including the MBMS listening status report as described in clause 14.3.4.5.
NOTE 3: Step 5 is optional for the VAL UE on subsequent MBMS bearer announcements.
6. The NRM server provides a MBMS bearers response to the VAL server.
7. A VAL service group communication session is established.
8. As the VAL server transmits the VAL service communication over the MBMS bearer, the VAL service communication packets are detected and delivered to the VAL client.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.4.3 Use of dynamic MBMS bearer establishment
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.4.3.1 General
|
In this scenario, the VAL server uses a unicast bearer for communication with the UE on the DL at the start of the group communication session. When the VAL server triggers to use an MBMS bearer in EPS for the DL VAL service communication, the NRM server decides to establish an MBMS bearer in EPS using the procedures defined in 3GPP TS 23.468 [16]. The NRM server provides MBMS service description information associated with MBMS bearer(s), obtained from the BM-SC, to the UE. The UE starts using the MBMS bearer(s) to receive DL VAL service and stops using the unicast bearer for the DL VAL service communication.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.4.3.2 Procedure
|
Figure 14.3.4.3.2-1 illustrates the use of dynamic MBMS bearer establishment.
Figure 14.3.4.3.2-1: Use of dynamic MBMS bearer establishment
1. A VAL service group communication session is established.
2. The downlink data is sent by unicast delivery.
3. The VAL server sends MBMS bearers request to the NRM server.
4. The NRM server establishes the MBMS bearer(s) for the VAL service group communication session according to the procedures defined in 3GPP TS 23.468 [16]. Service description associated with the MBMS bearer(s) is returned from the BM-SC. If local MBMS is requested in step 3, the NRM server uses the local MBMS information provided by VAL server in step 3 or the local MBMS information configured locally in the NRM server to activate the MBMS bearers. The NRM server performs local MBMS procedures in line with the procedure of L.MBMS based MBMS data delivery defined in 3GPP TS 23.285 [31].
5. The NRM server provides service description information associated with the MBMS bearer to the UE. The VAL UE obtains the TMGI from the announcement message. This message may be sent on an application level control signalling bearer.
6. The VAL UE starts monitoring data over MBMS associated with the TMGI, while in the service area associated with the TMGI.
7. The VAL UE detects that it is able to receive data over MBMS associated with the TMGI.
8. The NRM client notifies the NRM server the MBMS listening status associated to the monitored TMGI, (e.g. that it is successfully receiving the TMGI). The NRM client may also notify the MBMS reception quality level of the TMGI. The NRM server may decide to use the MBMS bearer instead of unicast bearer for VAL service communication sessions based on available information at the NRM server including the MBMS listening status report as described in clause 14.3.4.5.
9. The NRM server provides an MBMS bearer response to the VAL server with the dynamic MBMS bearer(s) information. The VAL server stops sending VAL service communication data over unicast way to the VAL client.
NOTE: The MBMS reception quality level may be used by the NRM server to make an efficient decision to switch again to a unicast transmission or to take measures to prepare such a switch (e.g. when the quality level indicates that the reception quality of the MBMS bearer is decreasing or reaching an insufficient quality level for the reception of VAL services).
10. A VAL service group communication session via dynamic MBMS bearer(s) is established.
11. The VAL server sends the downlink VAL service communication for the VAL service group communication session over the MBMS.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.4.4 MBMS bearer announcement over MBMS bearer
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.4.4.1 General
|
The MBMS announcement may be done on either a unicast bearer or a MBMS bearer. Using a unicast bearer for MBMS bearer announcement provides an interactive way of doing announcement. The NRM server will send the MBMS bearer announcement message to the NRM client regardless if there is an MBMS bearer active or the VAL client can receive the data on the MBMS bearer with sufficient quality. The benefit of the existing procedure is that it gives a secure way to inform the NRM client about the MBMS bearer and how to retrieve the data on the MBMS bearer.
When there is more than one MBMS bearer active in the same service area for VAL service, there are not the same reasons to use unicast bearer for additional MBMS bearer announcement. Instead a MBMS bearer for application level control signalling can be used to announce additional MBMS bearers.
The MBMS bearer announcement messages are sent on an MBMS bearer used for application control messages. This bearer will have a different QoS setting compared to an MBMS bearer used for VAL service communication, since application signalling messages are more sensitive to packet loss.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.4.4.2 Procedure
|
Figure 14.3.4.4.2-1 illustrates a procedure that enables the NRM server to announce a new MBMS bearer.
Pre-conditions:
1. An MBMS bearer used for VAL service application control messages must have been pre-established and announced to the NRM client.
2. Additional MBMS bearer information may have already been announced to the NRM client.
Figure 14.3.4.4.2-1: MBMS bearer announcement over an MBMS bearer used for application control messages
1. The NRM client monitors an MBMS bearer that is used for VAL service application signalling messages, such as bearer announcement messages.
2. The NRM server activates a new MBMS bearer.
3. The NRM server announces the MBMS bearer to the NRM client. The bearer may have just been activated or may have already been running for some time. The step may be repeated as needed.
4. The NRM server sends a MBMS bearer announcement on the MBMS bearer used for VAL application control messages. The MBMS bearer announcement contains the identity of the MBMS bearer (i.e. the TMGI) and may optionally include additional information about the newly announced bearer. Required and optional MBMS bearer announcement details may have already been provided. In this case the MBMS bearer identity could be used as a key for such MBMS bearer details.
5. The NRM client start to monitor the newly announced MBMS bearer.
6. If requested by the NRM server, the NRM client sends an acknowledgement of the MBMS bearer to the NRM server.
7. The NRM server de-announce the MBMS bearer.
8. The NRM server sends a MBMS bearer de-announcement message that contains the identity of the MBMS bearer.
9. The NRM client stops monitoring the de-announced MBMS bearer.
The same procedure can also be used to modify existing MBMS bearer announcement information. Example of such modification could be addition of UDP ports or modification of codec in the SDP.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.4.5 MBMS bearer quality detection
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.4.5.1 General
|
The NRM client and NRM server use this procedure to report and take action on the MBMS bearer quality towards VAL service communications. A NRM client monitors an MBMS bearer to enable receiving VAL service communication. Based on the received quality (e.g. radio level quality, transport level quality), the NRM client needs to inform the NRM server that the VAL UE is able to receive the VAL service communication on the MBMS bearer with sufficient quality or not able to receive the VAL service communication on the MBMS bearer with sufficient quality. Furthermore, based on the received quality, the NRM client may notify the NRM server at which MBMS reception quality level it has received the VAL service communication on the MBMS bearer.
The issue can be more complex since the NRM client needs to estimate the quality of the bearer even in the scenario when there are no data currently transmitted on the MBMS bearer. The reason for this is that an NRM client that has entered an area with significantly degraded MBMS quality, might not even notice that a VAL service communication is ongoing, meanwhile the NRM server still assumes that the VAL UE can receive the VAL service communication being broadcasted.
To estimate the MBMS bearer quality, for example as an equivalent BLER (Block Error Rate), when no data is sent is implementation specific. This estimation can be dependent on for example the modulation and coding scheme (MCS) and measurements from the reference signals from the eNB(s). Other metrics (e.g. RTP packet loss) may be used to estimate the MBMS bearer quality.
Based on the MBMS bearer quality reported from the NRM clients, the NRM server may decide to use the MBMS bearer for a group communication if a certain number of NRM clients located in the MBMS service area are able to receive the VAL service communication. And if a NRM client is not able to receive the VAL service communication on the MBMS bearer, the NRM server may decide to switch the user plane deliver mode for the NRM client from MBMS bearer to unicast bearer.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.4.5.2 Procedure
|
The NRM client shall indicate the ability of the NRM client to receive the MBMS bearer.
Pre-conditions:
1. There is an MBMS bearer activated and the MBMS bearer information is announced to the NRM client
2. The NRM client is located in the MBMS broadcasting area
3. The VAL UE monitors SIB-13 (or SIB-20) and (SC-)MCCH to receive the modulation and coding scheme
4. The VAL UE monitors the cell specific reference signal and when MBSFN transmission is used, the MBSFN specific reference signals
Figure 14.3.4.5.2-1: MBMS bearer quality detection
1. The NRM client determines that the MBMS bearer quality shall be reported to the NRM server. The NRM client may determine the MBMS bearer quality by using the BLER of the received data. When no data is received, the quality estimation can consider the reference signals and the modulation and coding scheme (MCS). The UE may also use predictive methods to estimate the expected MBMS bearer quality (e.g. speed and direction) to proactively inform the NRM server of an expected loss of the MBMS bearer quality. The NRM client may also map the determined MBMS bearer quality to a MBMS reception quality level. The MBMS reception quality level indicates at which specific MBMS bearer quality level the VAL service communication has been received.
NOTE 1: The set of MBMS reception quality levels and the mapping of the determined MBMS bearer quality to those levels are upto implementation.
NOTE 2: When MBSFN transmission is used, the MBSFN reference signal needs to be used and when SC-PTM is used the cell specific reference signal needs to be used. With the measured reference signal, the reference signal received quality (RSRQ) can be calculated.
2. If the MBMS bearer quality reaches a certain threshold, the NRM client sends an MBMS listening status report. The threshold is used to define the MBMS listening status, which indicates if the MBMS bearer quality has been acceptable or not to receive a specific VAL service communication. If the MBMS bearer quality is mapped to a different MBMS reception quality level, the NRM client may send an MBMS listening status report including the MBMS reception quality level. Based on the MBMS listening status, if MBMS reception quality level is received, then the NRM server may efficiently decide to switch to another bearer (e.g., MBMS bearer or unicast bearer) or to take measures to prepare such a switch and further notify the VAL server.
NOTE 3: Prior sending the MBMS listening status report, it could be beneficial to also include information for different alternatives e.g. another MBMS bearer might have better quality and could be a better option than a transfer of the communication to unicast.
NOTE 4: The threshold used to indicate MBMS bearer quality depends on VAL service type (i.e. V2X, MCPTT, MCVideo or MCData) and the metrics used. The metrics used and the associated thresholds are out of scope of this specification.
3. The NRM server may send additional proposal for measurements e.g. information about neighbouring MBMS bearers. This message may be an MBMS bearer announcement message.
4. The NRM server may send user plane delivery mode to VAL server based on the MBMS listening status to preserve the service continuity as described in clause 14.3.4.6 and clause 14.3.4.9.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.4.6 Service continuity in MBMS scenarios
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.4.6.1 General
|
This subclause specifies service continuity scenarios when MBMS bearers are used. There are different solutions for different scenarios.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.4.6.2 Service continuity when moving from one MBSFN to another
|
The service continuity solution described in this subclause is suitable in the scenario when multiple MBMS bearers are used with the purpose to cover a larger area. In VAL communications several VAL service communication streams may be multiplexed in one MBMS bearer. Furthermore, one VAL service communication stream may be sent on more than one MBMS bearer if the receiving users are distributed over more than one MBMS service area. A VAL UE that is interested in receiving a VAL service communication stream that is broadcasted in both MBMS bearers is a candidate for this service continuity procedure.
Figure 14.3.4.6.2-1 illustrates a deployment scenario that provides service continuity between two MBSFN areas. Two different MBMS bearers are activated (TMGI 1 and TMGI 2), the activation of the bearers is done in the two MBSFN areas (MBSFN 1 and MBSFN 2). The MBSFN areas 1 and 2 are partially overlapping, meaning that some transmitting cells belong to both MBSFN area 1 and MBSFN area 2.
Figure 14.3.4.6.2-1: Two MBMS bearer using overlapping MBSFN areas
Figure 14.3.4.6.2-2 illustrates the procedure:
Figure 14.3.4.6.2-2: Service continuity when moving from one MBSFN to another
1. The VAL UE is located in MBSFN 1 and can listen to TMGI 1. No additional MBMS bearers that the NRM client is interested in are active in the current cell.
2a. The NRM client notifies the NRM server that the VAL UE is successfully receiving the VAL service communication over TMGI 1. The NRM client may also notify the MBMS reception quality level of TMGI 1.
2b. The NRM server notifies a user plane delivery mode to the VAL server.
NOTE: The MBMS reception quality level may be used by the NRM server to make an efficient decision to switch to another MBMS bearer or to a unicast bearer, or to take measures to prepare such a switch (e.g. when the quality level indicates that the reception quality of the MBMS bearer is decreasing or reaching an insufficient quality level for the reception of VAL services).
3. The VAL UE moves into a new cell in which both TMGI 1 and TMGI 2 are active. This cell is part of both MBSFN area 1 and MBSFN area 2, and broadcast the same service on both TMGIs.
4. The NRM client sends a location information report to the NRM server. For that, the UE uses the SAI information found in the system information block (SIB) transmitted by the radio cells.
5. The NRM server sends to the NRM client a MBMS bearer announcement with information related to TMGI 2 (if the NRM server had not done it before). Hence, the NRM client knows that TMGI 2 transmits the same VAL service communication.
6a. The NRM client notifies the NRM server that it is successfully receiving TMGI 1 and TMGI 2. The NRM client may also notify the MBMS reception quality level per TMGI.
6b. The NRM server notifies a user plane delivery mode to the VAL server.
7. The VAL UE may receive the VAL service communication over both MBMS bearers, i.e. TMGI 1 and TMGI 2. The VAL UE may also verify that it is the same content sent on both bearers. The duplicated packets may also be used to perform error corrections.
8. The VAL UE moves into a new cell in MBSFN area 2, where only TMGI 2 is active.
9a. The NRM client notifies the NRM server that the VAL UE is successfully receiving the VAL service communication over TMGI 2. The NRM client may also notify the MBMS reception quality level of TMGI 2.
9b. The NRM server notifies a user plane delivery mode to the VAL server.
10. The VAL UE receives the VAL service communication only over TMGI 2.
This service continuity procedure mitigates the risk of packet loss that may occur if the VAL UE would request to transfer the VAL service communication stream to a unicast bearer when moving into the new area and then back to a multicast bearer when the UE can listen to TMGI 2. However, it is still required that the NRM client sends a location report (and MBMS listening report), as described in steps 4-6 above. To send the location report and the MBMS listening report by the NRM client to the NRM server a unicast bearer is needed. The location report from the NRM client is required, since the NRM server must know that the VAL UE has entered a new area and can only listen to MBMS bearer active in that area. If this is not done the VAL server might send a VAL service communication stream that the VAL UE is required to listen to on the MBMS bearer 1, since the NRM server still assumes that the VAL:UE is located in the MBSFN area 1.
The solution can be improved as illustrated in figure 14.3.4.6.2-3. In this case two different MBMS bearers are activated (TMGI 1 and TMGI 2), these MBMS bearers are used only for VAL service communication. An application level signalling bearer is activated (TMGI 9), in both MBSFN areas. This bearer is used for application level signalling messages that are sent on the MBMS bearer TMGI 9. By using an application level signalling bearer (e.g. TMGI 9) the VAL UEs can receive application control messages for all VAL service communication going on in the areas of both TMGI 1 and TMGI 2. A VAL UE that is located in the area of TMGI 2 and is interested in a VAL service group transmission (e.g. V2X) only going on in TMGI 1, can with the information received in TMGI 9 initiate a unicast bearer and request to receive that specific VAL service communication over a unicast instead. Without the information received over TMGI 9 the NRM client must immediately report that the VAL UE has left the broadcast area that the NRM server assumes that the VAL UE is located in. With the use of TMGI 9 there is no immediate need for the NRM client to inform the NRM server of a location change.
Figure 14.3.4.6.2-3: Two MBMS bearer using overlapping MBSFN areas with a separate application signalling bearer
The procedural steps in this scenario will be the same as described above in this subclause. However, in this scenario the NRM client is not required to initiate a unicast bearer to send location report (or MBMS listening report). The VAL UE may move between the two MBMS bearers (TMGI 1 and TMGI 2) without the need to report an area change. A condition for this to work is that there is an application level signalling bearer (TMGI 9) activated in the full area (i.e. the area of both TMGI 1 and TMGI 2). The TMGI 9 will broadcast all application control messages for all VAL service communications ongoing in both areas. If the VAL UE is in coverage of one of the two MBMS bearers that does not transmit the VAL service communication of interest the VAL UE can report to the NRM server that it is not able to listen to the VAL service communication over the MBMS bearer, which triggers the NRM server to switch to a unicast bearer instead.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.4.7 MBMS suspension notification
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.4.7.1 General
|
In this procedure the NRM client is requested by the NRM server to send a MBMS suspension report. This request for MBMS suspension report can be included in the MBMS bearer announcement and the NRM server may choose to only send this request for MBMS suspension report to a subset of all NRM clients.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.4.8 MBMS bearer event notification
| |
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.4.9 Switching between MBMS bearer and unicast bearer
| |
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.5 QoS/resource management for network-assisted UE-to-UE/VN group communications
| |
d23d1b9504aafd6c2e98868ecaffb278
|
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 [TS 23.255], where the UAV controller navigates its UAV over the 5GS;
- Teleoperated Driving (ToD) in eV2XAPP [TS 23.286], 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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.5.4 Application QoS coordination for Mobile Metaverse Services in distributed VAL servers
| |
d23d1b9504aafd6c2e98868ecaffb278
|
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..
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.6 Event Monitoring
| |
d23d1b9504aafd6c2e98868ecaffb278
|
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].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.6.2 Monitoring Events Subscription Procedure
| |
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
14.3.6.3 Monitoring Events Notification Procedure
| |
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.