Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.434  Word version:  19.3.0

Top   Top   Up   Prev   Next
0…   4…   5   6…   6.4…   6.5…   6.5.3…   7…   8…   8.2.2…   9…   9.3…   9.3.2.21…   9.3.3…   9.3.6…   9.3.11…   9.3.13…   9.3.14…   9.4…   9.4.6…   9.5…   10…   10.3…   10.3.2.22…   10.3.3…   10.3.7…   10.3.10…   10.4…   11…   11.3…   11.3.3…   11.4…   12…   12.3…   13…   14…   14.2.2.2…   14.3…   14.3.2.20…   14.3.2.40…   14.3.3…   14.3.3.3…   14.3.4…   14.3.4.6   14.3.4.7…   14.3.4A…   14.3.4A.3…   14.3.4A.4…   14.3.4A.6…   14.3.4A.8…   14.3.4A.9…   14.3.4A.10…   14.3.5…   14.3.6…   14.3.9…   14.3.12…   14.4…   15…   16…   17…   18…   A   B…
14.3.2.40 Multicast/broadcast resource request14.3.2.41 Multicast/broadcast resource response14.3.2.42 Multicast/broadcast resource update request14.3.2.43 Multicast/broadcast resource update response14.3.2.44 Multicast/broadcast resource delete request14.3.2.45 Multicast/broadcast resource delete response14.3.2.46 Multicast resource activate request14.3.2.47 Multicast resource activate response14.3.2.48 Multicast resource deactivate request14.3.2.49 Multicast resource deactivate response14.3.2.50 MapVALGroupToSessionStream14.3.2.51 UE session join notification14.3.2.52 MBS listening status report14.3.2.53 UE unified traffic pattern and monitoring management subscription request14.3.2.54 UE unified traffic pattern and monitoring management subscription response14.3.2.55 UE unified traffic pattern update notification14.3.2.56 Get application connectivity context request.14.3.2.57 Get application connectivity context response.14.3.2.58 BDT configuration request14.3.2.59 BDT configuration response14.3.2.60 BDT negotiation notification14.3.2.61 BDT configuration get request14.3.2.62 BDT configuration get response14.3.2.63 BDT configuration update request14.3.2.64 BDT configuration update response14.3.2.65 BDT configuration delete request14.3.2.66 BDT configuration response14.3.2.67 Reliable transmission request14.3.2.68 Reliable transmission response14.3.2.69 Device triggering request14.3.2.70 Device triggering response
...

 

14.3.2.40  Multicast/broadcast resource request |R18|p. 195

Table 14.3.2.40-1 describes the information flow for the multicast/broadcast resource request from VAL server to NRM server.
Information element Status Description
Requester IdentityMThe identity of the VAL server performing the request.
VAL group IDO (NOTE 3)The identity of the group that the multicast/broadcast resource is requested for.
VAL UE ID ListO (NOTE 3)The list of VAL UE ID that the multicast/broadcast resource is requested for.
Session announcement modeMIndicates whether the session announcement is sent by NRM server or by the VAL server
Service requirement descriptionMIndicates 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 informationOIndicate the area where the multicast/broadcast resource is requested for
Endpoint informationMInformation of the endpoint of the VAL server to which the user plane notifications have to be sent.
Network system indicatorOIndicate if the multicast/broadcast resrouce is required from 5GS, EPS, or both
Local MBMS information (NOTE 1, NOTE 2)O
> MB2-U informationOIP address, UDP port number of the MB2-U interface
> xMB-U informationOIP address, UDP port number of the xMB-U interface
> M1 interface informationOM1 interface information for local MBMS
Local MBMS activation indication (NOTE 1, NOTE 2)OIndicates 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.
Up

14.3.2.41  Multicast/broadcast resource response |R18|p. 196

Table 14.3.2.41-1 describes the information flow for the multicast/broadcast resource response from NRM server to VAL server.
Information element Status Description
ResultMThe result indicates success or failure of the multicast/broadcast resource request operation.
Identity of the multicast/broadcast resourceO (NOTE 1)The identity of the multicast/broadcast MBS session, or/and the identity of the MBMS bearer.
User plane addressM (NOTE 2)User plane IP address(es) and port for VAL to deliver the DL packet
Session description informationO (NOTE 2)Indicates Multicast/broadcast related configuration information as defined in TS 26.346 (e.g. radio frequency and MBMS Service Area Identities) or/and TS 23.247 (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.
Up

14.3.2.42  Multicast/broadcast resource update request |R18|p. 197

Table 14.3.2.42-1 describes the information flow for the multicast/broadcast resource update request from VAL server to NRM server.
Information element Status Description
Requester IdentityMThe identity of the VAL server performing the request.
Identity of the multicast/broadcast resourceMIdentity of the multicast/broadcast resource
Service requirement descriptionO (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 informationO (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 informationOIP address, UDP port number of the MB2-U interface
> xMB-U informationOIP address, UDP port number of the xMB-U interface
> M1 interface informationOM1 interface information for local MBMS
Local MBMS activation indication (NOTE 1, NOTE 2)OIndicates 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.
Up

14.3.2.43  Multicast/broadcast resource update response |R18|p. 197

Table 14.3.2.43-1 describes the information flow for the Multicast/broadcast resource update response from NRM server to VAL server.
Information element Status Description
ResultMThe result indicates success or failure of the multicast/broadcast resource update request operation.
Identity of the multicast/broadcast resourceM (NOTE 1)The identity of the multicast/broadcast MBS session, or/and the identity of the MBMS bearer.
Session description informationO (NOTE 2)Indicates Multicast/broadcast related configuration information as defined in TS 26.346 (e.g. radio frequency and MBMS Service Area Identities) or/and TS 23.247 (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.
Up

14.3.2.44  Multicast/broadcast resource delete request |R18|p. 197

Table 14.3.2.44-1 describes the information flow for the multicast/broadcast resource delete request from VAL server to NRM server.
Information element Status Description
Requester Identity MThe identity of the VAL server performing the request.
Identity of the multicast/broadcast resourceMIdentity of the multicast/broadcast resource, i.e., the MBS session ID for 5G MBS, TMGI for 4G MBMS, or both
Up

14.3.2.45  Multicast/broadcast resource delete response |R18|p. 198

Table 14.3.2.45-1 describes the information flow for the Multicast/broadcast resource delete response from NRM server to VAL server.
Information element Status Description
ResultMThe result indicates success or failure of the multicast/broadcast resource delete request operation.
Identity of the multicast/broadcast resourceMThe identity of the multicast/broadcast MBS session, or/and the identity of the MBMS bearer.
Up

14.3.2.46  Multicast resource activate request |R18|p. 198

Table 14.3.2.46-1 describes the information flow for the multicast resource activate request from VAL server to NRM server.
Information element Status Description
Requester IdentityMThe identity of the VAL server performing the request.
MBS session IDMIdentity of multicast MBS session
Up

14.3.2.47  Multicast resource activate response |R18|p. 198

Table 14.3.2.47-1 describes the information flow for the multicast resource activate response from NRM server to VAL server.
Information element Status Description
ResultMThe result indicates success or failure of the multicast resource activate operation.
MBS session IDMIdentity of multicast MBS session
Up

14.3.2.48  Multicast resource deactivate request |R18|p. 198

Table 14.3.2.48-1 describes the information flow for the multicast resource deactivate request from VAL server to NRM server.
Information element Status Description
Requester IdentityMThe identity of the VAL server performing the request.
MBS session IDMIdentity of multicast MBS session
Up

14.3.2.49  Multicast resource deactivate response |R18|p. 199

Table 14.3.2.49-1 describes the information flow for the multicast resource deactivate response from NRM server to VAL server.
Information element Status Description
ResultMThe result indicates success or failure of the multicast resource deactivate operation.
MBS session IDMIdentity of multicast MBS session
Up

14.3.2.50  MapVALGroupToSessionStream |R18|p. 199

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.
Information element Status Description
VAL group IDMThis element identifies the VAL group related to a group related VAL data communication to be delivered over the MBS session.
VAL data stream identifierMThis element identifies the VAL data stream of the SDP used for the group related VAL data communication within the MBS session.
MBS session IDOThe MBS session identifier if the MapVALGroupToSessionStream message is not sent on the same session as the VAL data
Up

14.3.2.51  UE session join notification |R18|p. 199

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 TS 23.247.
Information element Status Description
MBS session ID(s)MThe 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 IDMThe identity of the VAL user or VAL UE who sends this notification.
MBS multicast joining statusMUE's multicast MBS session status per MBS session ID, e.g., successfully joined.
Up

14.3.2.52  MBS listening status report |R18|p. 199

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.
Information element Status Description
VAL user ID or VAL UE IDMThe identity of the VAL user or VAL UE who wants to report the MBS listening status.
MBS session ID(s)MThe identity of the MBS session(s) being monitored.
MBS listening statusMThe listening status per MBS session ID.
MBS reception quality level (NOTE)OThe reception quality level
Unicast listening statusOThe 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.
Up

14.3.2.53  UE unified traffic pattern and monitoring management subscription request |R18|p. 200

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.
Information element Status Description
VAL UE IDMUEs hosting clients for which the subscription is requested.
VAL service IDMIdentity of the VAL service for which the subscription is requested.
Management subscription indicationsMAt least one of the following indications is to be provided.
> UE unified traffic pattern monitoring management indicationOIndicates that management of the UE unified traffic pattern is requested.
> UE unified traffic pattern update notification indicationOIndicates that notifications for updates of the UE unified traffic pattern monitoring is requested.
> Network parameter coordination indicationOIndicates whether network parameter coordination by the NRM with 5GC is requested (see NOTE 1).
traffic pattern configurationOTraffic 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.
Information element Status Description
Schedule elementsOList 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 timeOIdentifies when the VAL traffic pattern parameter configuration expires. If absent, it indicates that there is no expiration time.
Stationary indicationOIdentifies whether the UE is expected to be stationary or mobile while communicating using this traffic pattern configuration.
Up

14.3.2.54  UE unified traffic pattern and monitoring management subscription response |R18|p. 201

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.
Information element Status Description
ResultMIndicates success or failure of the subscription request.
Up

14.3.2.55  UE unified traffic pattern update notification |R18|p. 201

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.
Information element Status Description
UE IDMUE for which the UE unified traffic pattern update notification is provided for.
Schedule elementsOSchedule 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 indicationOIdentifies whether the UE is expected to be stationary or mobile while communicating using this UE unified traffic pattern, as determined by the NRM Server.
CauseOThis 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).
Up

14.3.2.56  Get application connectivity context request. |R18|p. 202

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 (e.g. over FFA-2 reference point see TS 23.545 [55]).
Information element Status Description
Requester VALUE IDMThe identity of the source VAL client for which the NRM client performs the request.
VAL service IDMIdentify of the VAL service for which the information is requested.
VAL-specific connection coordination context informationOAdditional information required to identify the context data (e.g. device type, device vendor, etc).
Up

14.3.2.57  Get application connectivity context response. |R18|p. 202

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 (e.g. over FFA-2 reference point see TS 23.545 [55]).
Information element Status Description
ResultMThe 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.
Up

14.3.2.58  BDT configuration request |R18|p. 202

Table 14.3.2.58-1 describes the information flow for the BDT configuration request from the VAL server to the NRM Server.
Information element Status Description
VAL service IDMIdentity of the VAL service for which the configuration is requested.
List of VAL UE IDsMList of VAL UE IDs for which the transfer policy applies or a VAL group ID.
Volume per UEMExpected data volume for the background data transfer.
Desired time windowMDesired time window for the background data transfer.
Desired area informationMDesired geographical area for the background data transfer.
Request expiration timeOExpiration 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 GuidanceO 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.
Up

14.3.2.59  BDT configuration response |R18|p. 203

Table 14.3.2.59-1 describes the information flow for BDT configuration response from the NRM server to the VAL server.
Information element Status Description
ResultMThe result indicates success or failure of the BDT configuration operation.
BDT configuration identifier (NOTE)OIdentifier of the BDT configuration information stored at the NRM server.
BDT Reference ID (see NOTE)OIndicates the Background data transfer Reference ID provided by the 3GPP network.
Granted time window (see NOTE)OGranted time window for the background data transfer.
NOTE:
These IEs shall be included when Result is success.
Up

14.3.2.60  BDT negotiation notification |R18|p. 203

Table 14.3.2.60-1 describes the information flow for BDT negotiation notification from the NRM server to the VAL server.
Information element Status Description
BDT configuration identifierMIdentifier of the BDT configuration information stored at the NRM server.
Granted time window (see NOTE)OGranted time window for the background data transfer.
BDT Reference IDMIndicates the Background data transfer Reference ID provided by the 3GPP network.
BDT policy removal indicator (see NOTE)OThe indicator about the BDT policy removal.
NOTE:
Either of these IEs are included.
Up

14.3.2.61  BDT configuration get request |R18|p. 204

Table 14.3.2.61-1 describes the information flow for the BDT configuration get request from the VAL server to the NRM Server.
Information element Status Description
VAL service IDMIdentity of the VAL service for which the BDT configuration is requested to be updated.
BDT configuration identifierMIdentifier of the BDT configuration stored in the NRM server.
Up

14.3.2.62  BDT configuration get response |R18|p. 204

Table 14.3.2.62-1 describes the information flow for BDT configuration get response from the NRM server to the VAL server.
Information element Status Description
ResultMThe result indicates success or failure of BDT configuration get operation.
BDT configuration identifierMIdentifier of the BDT configuration stored in the NRM server.
BDT configuration data (see NOTE)OThe 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.
Up

14.3.2.63  BDT configuration update request |R18|p. 204

Table 14.3.2.63-1 describes the information flow for the BDT configuration update request from the VAL server to the NRM Server.
Information element Status Description
VAL service IDMIdentity of the VAL service for which the BDT configuration is requested to be updated.
BDT Configuration identifierMIdentifier of the BDT configuration stored in the NRM server.
Volume per UE (see NOTE)OUpdated expected data volume for the background data transfer.
Desired time window (see NOTE)OUpdated desired time window for the background data transfer.
Desired area information (see NOTE)OUpdated desired geographical area for the background data transfer.
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.
Up

14.3.2.64  BDT configuration update response |R18|p. 205

Table 14.3.2.64-1 describes the information flow for BDT configuration update response from the NRM server to the VAL server.
Information element Status Description
ResultMThe result indicates success or failure of BDT configuration update operation.
BDT Configuration identifierMIdentifier of the BDT configuration stored in the NRM server.
Up

14.3.2.65  BDT configuration delete request |R18|p. 205

Table 14.3.2.65-1 describes the information flow for the BDT configuration delete request from the VAL server to the NRM Server.
Information element Status Description
VAL service IDMIdentity of the VAL service for which the BDT configuration is requested to be deleted.
BDT configuration identifierMIdentifier of the BDT configuration stored in the NRM server.
Up

14.3.2.66  BDT configuration response |R18|p. 205

Table 14.3.2.66-1 describes the information flow for BDT configuration delete response from the NRM server to the VAL server.
Information element Status Description
ResultMThe result indicates success or failure of BDT configuration delete operation.
Up

14.3.2.67  Reliable transmission request |R18|p. 205

Table 14.3.2.67-1 describes the information flow for reliable transmission request from SEALDD server (or VAL server) to the NRM server.
Information element Status Description
Requester IdentityMThe identity of the SEALDD server (or VAL server) performing the request.
Application descriptorsOA 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 IDOThe identity of VAL UE.
UE addressOThe address of VAL UE.
Up

14.3.2.68  Reliable transmission response |R18|p. 205

Table 14.3.2.68-1 describes the information flow for the reliable transmission response from NRM server to SEALDD server (or VAL server).
Information element Status Description
ResultThe result indicates success or failure of the reliable transmission request operation.
Up

14.3.2.69  Device triggering request |R19|p. 206

Table 14.3.2.69-1 describes the information flow for the Device triggering request from the VAL server to the NRM Server.
Information element Status Description
IdentifierMVAL UE ID or VAL group ID to be triggered.
Port numberODevice triggering port number. If not provided, NRM determines the port number to be used based on local policies.
Triggering purposeMIndicates the device triggering purpose which is included in the payload. The default is a reserved value e.g. NULL.
Time windowODesired 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 informationODesired geographical area for trigger.
Up

14.3.2.70  Device triggering response |R19|p. 206

Table 14.3.2.70-1 describes the information flow for Device triggering response from the NRM server to the VAL server.
Information element Status Description
ResultMThe result indicates success or failure of the operation.
Up

Up   Top   ToC