hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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)
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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)
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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)
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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)
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.2.74 MMeta service requirements request
| Table 14.3.2.74-1 describes the information flow MMeta service requirements request from the VAL server to the NRM server.
Table 14.3.2.74-1: MMeta service requirements request
Information element
Status
Description
Requestor ID
M
Identity of the requestor (VAL server).
VAL service ID
M
The VAL service identity for whom the service requirement occurs.
MMeta performance requirements
M
The mobile metaverse QoS/QoE requirements and KPIs (latency, error rate, ..) for the MMeta end to end service.
VAL UE capability requirement
M
Information about the needed capability for the VAL UEs (e.g. device type, resource usage level) to support the MMeta service requirements. This requirement is used to filter only VAL UEs with required capability (e.g. of certain device type).
Service area
M
The area where the MMeta service is deployed. This can be geographical area, or topological area.
Time validity
O
The time of validity of the requirement.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.2.75 MMeta service requirements response
| Table 14.3.2.75-1 describes the information flow MMeta service requirements response from the NRM server to the VAL server.
Table 14.3.2.75-1: MMeta service requirements response
Information element
Status
Description
Result
M
The positive or negative result of the MMeta service requirements request.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.2.76 MMeta service connectivity request
| Table 14.3.2.76-1 describes the information flow MMeta service connectivity request from the NRM server to the NRM client 1 and 2.
Table 14.3.2.76-1: MMeta service connectivity request
Information element
Status
Description
VAL service ID
M
The VAL service identity for whom the connectivity occurs
Session information
M
Session information for the established connectivity for MMeta service communication.
>MMeta session ID
M
The identity of the session.
> MMeta session type
M
The type of session (UE to network or UE-to-UE)
>MMeta QoS configuration
M
The configuration of the QoS attributes (latency, jitter) for the VAL session within the MMeta service
>List of destination VAL UE IDs
O
The list of destination VAL UEs which are selected for the connectivity to be established for the MMeta service communication.
Service area
M
The area where the MMeta service is deployed. This can be geographical area, or topological area.
Time validity
O
The time of validity of the connectivity request.
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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.2.77 MMeta service connectivity response
| Table 14.3.2.77-1 describes the information flow for MMeta service connectivity response from the NRM client to the NRM server.
Table 14.3.2.77-1: MMeta service connectivity response
Information element
Status
Description
Result
M
Result from the NRM client in response to request indicating success or failure for accepting the request.
Cause
O
The cause of failure, if the result indicates failure.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.2.78 MMeta service connectivity notification
| Table 14.3.2.78-1 describes the information flow for MMeta service connectivity notification from the NRM server to the VAL server.
Table 14.3.2.78-1: MMeta service 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
List of VAL UEs
O
The list of VAL UEs which are accepted for the connectivity established for the application service communication.
>VAL UE/user ID
O
Identity of the VAL UE.
> Connection information
O
Connection information including address / port and / or URL of the VAL UE.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.2.79 Power saving assist request
| Table 14.3.2.79-1 describes the information flow for power saving assist request from the VAL server to the NRM server, or from the NRM client to the NRM server.
Table 14.3.2.79-1: Power saving assist request
Information element
Status
Description
VAL User or VAL UE(s) ID(s) (NOTE)
M
The identity of the VAL user whose UE(s) are target for power savings configuration. Alternatively, is the UE ID on which the NRM client resided
VAL Service ID
M
The identity of the VAL service
Power saving requirements
M
The desired power saving requirements for the VAL UE(s), e.g., power saving mode (e.g., power-saving, balanced, performance) to be enforced for the target user(s)
NOTE: If the consumer is the NRM client, this IE shall be the UE ID. If the consumer is VAL server, the IE may be a list of UE IDs or identity of VAL user.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.2.80 Power saving configuration request
| Table 14.3.2.80-1 describes the information flow for power saving configuration request sent from the NRM server to the NRM client
Table 14.3.2.80-1: Power saving configuration request
Information element
Status
Description
VAL UE ID
M
Identity of the VAL UE which is a target for power savings configuration
Requested power saving configuration
M
The desired power saving configuration to be updated for the target user, e.g., DRX and eDRX configurations in 3GPP TS 38.331 [63] clause 6.3, clause 6.2, respectively.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.2.81 Power saving configuration response
| Table 14.3.2.81-1 describes the information flow for power saving configuration response sent from the NRM client to NRM server.
Table 14.3.2.81-1: Power saving configuration response
Information element
Status
Description
VAL UE ID
M
Identity of the VAL UE which is a target for power savings configuration
Result
M
Indicates whether the result of the power saving configuration request is successful or not
Accepted power saving configuration
O (NOTE)
Indicates the accepted power saving configuration
NOTE: This information element is present if the accepted power saving configurations are different from the desired one.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.2.82 Power saving assist response
| Table 14.3.2.82-1 describes power saving assist response sent from the NRM server to the VAL server and from NRM sever to the NRM client.
Table 14.3.2.82-1: Power saving assist response
Information element
Status
Description
VAL User or VAL UE(s) ID(s) (NOTE)
M
The identity of the VAL user whose UE(s) are target for power savings configuration. Alternatively, is the UE ID on which the NRM client resided.
>Result
M
Indicates whether the result of the power saving configuration request is successful or not
>Accepted power saving configuration
O
Indicates the accepted power saving configuration
NOTE: If the consumer is the NRM client, this IE shall be the UE ID. If the consumer is VAL server, the IE may be a list of UE IDs or identity of VAL user.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.3 Unicast resource management
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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 NRM server interactions with SIP core and NRM server interactions with PCC. 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].
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.3.2 Unicast resource management with SIP core
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.3.2.1 Request for unicast resources at VAL service communication establishment
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 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 network resource adaptation to the NRM server. The request includes a VAL UE ID or a VAL user ID.
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 network resource adaptation response to the VAL server.
7. The VAL service communication is established, and resources have been allocated.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.3.2.2 Request for modification of unicast resources
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.3.2.2.1 General
| To modify unicast bearers, the NRM server shall send a network resource adaptation 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
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 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;
- The VAL server requested network resources for the VAL UE ID, VAL User ID.
Figure 14.3.3.2.2.2-1: Bearer modification request
1. The VAL server sends a network resource adaptation modification request to the NRM server. The request includes a VAL UE ID or a VAL user ID whose resources need to be modified.
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 adaptation resource adaptation 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 network resource adaptation 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 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.3.3 Unicast resource management without SIP core
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.3.3.1 Network resource adaptation
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 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 group 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) if not provided in step 1 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.3.3.2 Request for unicast resources at VAL service communication establishment
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 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 a network resource adaptation request to the NRM server for a VAL UE or a VAL user ID.
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) if not provided in step 1, and then PCC procedures are initiated from NRM server.
4. The NRM server sends a network resource adaptation response to the VAL server.
5. The VAL service communication is established, and resources have been allocated.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.3.3.3 Request for modification of unicast resources
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.3.3.3.1 General
| To modify unicast resources, the NRM server shall send a network resource adaptation 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
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 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;
- The VAL server requested network resources for the VAL UE ID, VAL User ID.
Figure 14.3.3.3.3.2-1: Bearer modification request
1. The VAL server sends a network resource adaptation modification request for a VAL UE ID or VAL user ID 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 network resource adaptation modification response to the VAL server.
3. PCC procedures are initiated from NRM server.
4. The NRM server sends a network resource adaptation 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.3.4 Unicast QoS monitoring
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.3.4.1 Unicast QoS monitoring subscription procedure
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.3.4.2 Unicast QoS monitoring notification procedure
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.3.4.2.1 General
| This subclause describes the high level procedure for unicast QoS monitoring notification.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.3.4.3 Unicast QoS monitoring subscription termination procedure
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.3.4.3.1 General
| This subclause describes the high level procedure for unicast QoS monitoring subscription termination.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.3.4.4 Unicast QoS monitoring data retrieval procedure
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.3.4.4.1 General
| This subclause describes the high level procedure for unicast QoS monitoring data retrieval.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.3.4.5 Unicast QoS monitoring subscription update procedure
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.4 Multicast resource management for EPS
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.4.2 Use of pre-established MBMS bearers
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.4.3 Use of dynamic MBMS bearer establishment
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.4.4 MBMS bearer announcement over MBMS bearer
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.4.5 MBMS bearer quality detection
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.4.6 Service continuity in MBMS scenarios
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.3.4.7 MBMS suspension notification
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 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.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.