Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.434  Word version:  19.4.2

Top   Top   Up   Prev   Next
0…   6…   8…   9…   9.3…   9.3.3…   9.3.8…   9.3.13…   9.3.20…   9.3.23…   9.4…   10…   10.3…   10.3.3…   10.3.7…   10.4…   11…   12…   13…   14…   14.3…   14.3.3   14.3.4   14.3.4A…   14.3.4A.5…   14.3.4A.8…   14.3.5…   14.3.9…   14.4…   15…   17…   18…   A…

 

14.3  Procedures and information flows for network resource managementp. 202

14.3.1  Generalp. 202

The procedures related to the network resource management are described in the following subclauses.

14.3.2  Information flowsp. 202

14.3.2.1  Network resource adaptation requestp. 202

Table 14.3.2.1-1 describes the information flow network resource adaptation request from the VAL/SEALDD server to the NRM server.
Information Element Status Description
Requester IdentityMThe identity of the VAL server performing the request
List of VAL UE IDsO
(see NOTE)
List consisting of one or more VAL UE IDs for whom the network resource adaptation occurs
VAL group IDO
(see NOTE)
The VAL group ID for whom the network resource adaptation occurs
Resource adaptation requirementMThe resource adaptation requirement corresponds to the VAL service QoS requirements as applied for a UE or group of UEs (E.g. bandwidth, resource)
BDT Reference IDOIndicates the Background data transfer Reference ID provided by the 3GPP network
NOTE:
Either of the information elements should be present.
Up

14.3.2.2  Network resource adaptation responsep. 203

Table 14.3.2.2-1 describes the information flow network resource adaptation response from the NRM server to the VAL server.
Information Element Status Description
ResultMResult includes success or failure of the network resource adaptation with the underlying network. The response can also include an updated value for some of the parameters included in the network resource adaptation request (e.g. negotiation of resource offering)
Up

14.3.2.3  MBMS bearer announcementp. 203

Table 14.3.2.3-1 describes the information flow MBMS bearer announcement from the NRM server to the NRM client.
Information Element Status Description
TMGIMTMGI information
Alternative TMGIOA list of additional alternative TMGI may be included and used in roaming scenarios
QCIOQCI information used by the ProSe UE-Network Relay to determine the ProSe Per-Packet Priority value to be applied for the multicast packets relayed to Remote UE over PC5
List of service area identifierMA list of service area identifier for the applicable MBMS broadcast area
FrequencyOIdentification of frequency if multi carrier support is provided
SDP informationMSDP with media and application control information applicable to groups that can use this bearer (e.g. codec, protocol id, FEC information)
Monitoring stateOThe monitoring state is used to control if the client is actively monitoring the MBMS bearer quality or not
Announcement acknowledgmentOIndicate if the NRM server requires an acknowledgement of the MBMS bearer announcement
Unicast statusOAn indication that the listening status of the unicast bearer is requested
ROHC informationOIndicate the usage of ROHC and provide the parameters of the ROHC channel to signal to the ROHC decoder
NOTE:
When MBMS bearer announcement is done on a MBMS bearer all attributes above are optional except the TMGI.
Up

14.3.2.4  MBMS listening status reportp. 204

Table 14.3.2.4-1 describes the information flow for the MBMS listening status report from NRM client to NRM server.
Information Element Status Description
VAL user ID or VAL UE IDMThe identity of the VAL user or VAL UE who wants to report the MBMS listening status
TMGI(s)MTMGI(s) information
MBMS listening status(s)MThe MBMS listening status per TMGI
MBMS reception quality levelOThe reception quality level per TMGI (see NOTE)
Unicast listening statusOThe unicast listening status
NOTE:
The set of quality levels helps service continuity in MBMS scenarios. A reception quality level may help to make an efficient switching decision to another bearer. How these levels are used is implementation specific.
Up

14.3.2.5  MBMS suspension reporting instructionp. 204

Table 14.3.2.5-1 describes the information flow for the MBMS suspension reporting instruction from NRM server to NRM client in a unicast bearer for MBMS suspension reporting.
Information Element Status Description
VAL user ID or VAL UE IDMThe identity of the VAL user or VAL UE
Suspension reportingMEnables or disable the suspension reporting for a specific NRM client
Table 14.3.2.5-2 describes the information flow for the MBMS suspension reporting instruction from NRM server to NRM client in a multicast bearer for MBMS suspension reporting.
Information Element Status Description
Suspension reporting client subsetMContains a uniquely defined subset of NRM clients that shall report MBMS suspension
Up

14.3.2.6  Resource requestp. 205

Table 14.3.2.6-1 describes the information flow for the resource request from VAL server to NRM server for unicast resources.
Information Element Status Description
Requester IdentityMThe identity of the VAL server performing the request
VAL user ID or VAL UE IDMThe identity of the VAL user or VAL UE
VAL service requirement information (see NOTE)OVAL service requirements for unicast resource (e.g. VAL service ID, Bitrate)
NOTE:
When this information element is not included, the NRM server considers default VAL service requirement for the unicast resources.
Up

14.3.2.7  Resource responsep. 205

Table 14.3.2.7-1 describes the information flow for the resource response from NRM server to VAL server for unicast resources.
Information Element Status Description
ResultMThe result indicates success or failure of the resource request operation
Up

14.3.2.8  Resource modification requestp. 205

Table 14.3.2.8-1 describes the information flow for the resource modification request from VAL server to NRM server for unicast resources.
Information Element Status Description
Requester IdentityMThe identity of the VAL server performing the request
VAL user ID or VAL UE IDMThe identity of the VAL user or VAL UE
VAL service requirement informationMVAL service requirements for unicast resource (e.g. VAL sevice ID, Bitrate)
Up

14.3.2.9  Resource modification responsep. 205

Table 14.3.2.9-1 describes the information flow for the resource modification response from NRM server to VAL server for unicast resources.
Information Element Status Description
ResultMThe result indicates success or failure of the resource modification operation
Up

14.3.2.10  MBMS bearers requestp. 206

Table 14.3.2.10-1 describes the information flow for the MBMS bearers request from VAL server to NRM server.
Information Element Status Description
Requester IdentityMThe identity of the VAL server performing the request
VAL group IDMThe identity of the group that the MBMS bearer is requested for
Service announcement modeMIndicates whether the request is sent by NRM server or by the VAL server
QoSMIndicates the requested QoS for the bearer
Broadcast areaOIndicate the area where the MBMS bearer is requested for
Endpoint informationMInformation of the endpoint of the VAL server to which the user plane notifications have to be sent
Local MBMS information
(see NOTE)
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
(see NOTE)
OIndicates whether to request the NRM server to use Local MBMS information
NOTE:
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.
Up

14.3.2.11  MBMS bearers responsep. 206

Table 14.3.2.11-1 describes the information flow for the MBMS bearers response from NRM server to VAL server.
Information Element Status Description
ResultMThe result indicates success or failure of the MBMS bearers request operation
TMGIO
(see NOTE 1)
TMGI information
User plane addressM
(see NOTE 2)
BM-SC user plane IP address and port
Service descriptionO
(see NOTE 2)
Indicates MBMS bearer related configuration information as defined in TS 26.346 (e.g. radio frequency and MBMS Service Area Identities)
NOTE 1:
TMGI may not be required if the service 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 have no meaning.
Up

14.3.2.12  User plane delivery modep. 206

Table 14.3.2.12-1 describes the information flow for the user plane delivery mode from NRM server to VAL server.
Information Element Status Description
Delivery modeMIndicates whether to deliver the user data to the UE(s) via unicast mode or multicast mode
MBMS media stream identifierMIndicates the MBMS media stream to be used to deliver the media currently over unicast, or the MBMS media stream currently being used
Unicast media stream identifier(s)MIndicates the unicast media stream to be used to deliver the media currently over multicast, or the unicast to be stopped and switched to multicast
MBS service areaOIndicates the MBS service area where the delivery mode is applied.
List of VAL UE IDsO
(NOTE)
The list of UEs where the unicast mode is applied.
NOTE:
This information element is only applicable when the delivery mode is unicast mode.
Up

14.3.2.13  end-to-end QoS management request |R17|p. 207

Table 14.3.2.13-1 describes the information flow end-to-end QoS management request from the NRM client to the NRM server.
Information Element Status Description
List of VAL UEs or VAL Group IDMList of VAL UEs or the group of VAL UEs for whom the end-to-end QoS management occurs.
> VAL UE/user IDMIdentity of the VAL UE.
> IP addressOIP address of the VAL UE.
VAL service IDOThe VAL service identity for whom the end-to-end QoS management occurs.
End-to-end QoS requirementsOThe application QoS requirements / KPIs (latency, error rate, ..) for the end-to-end session.
This may optionally include information which will support the NRM server to identify the per session QoS requirements (e.g. a flag indicating the use of HD video for assisting the end-to-end session, a video resolution/encoding required for the HD video).
Service areaOThe area where the QoS management request applies. This can be geographical area, or topological area.
Time validityOThe time of validity of the requirement.
Up

14.3.2.14  end-to-end QoS management response |R17|p. 207

Table 14.3.2.14-1 describes the information flow end-to-end QoS management response from the NRM server to the NRM client.
Information Element Status Description
ResultMThe positive or negative result of the end-to-end QoS management request.
QoS report configurationOThe 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)
Up

14.3.2.15  QoS downgrade indication |R17|p. 208

Table 14.3.2.15-1 describes the information flow QoS downgrade indication from the NRM client to the NRM server.
Information Element Status Description
VAL UE IDMThe identifier of the VAL UE which indicates the QoS downgrade.
QoS downgrade reportMThe report including the expected or actual QoS / QoE parameters which were downgraded (i.e. latency, throughput, reliability, jitter). This report may be configured by the end-to-end QoS management response message.
Up

14.3.2.16  Application QoS change notification |R17|p. 208

Table 14.3.2.16-1 describes the information flow Application QoS change notification from the NRM server to the NRM clients (which are involved at the end-to-end session).
Information Element Status Description
NRM server IDMThe identifier of the NRM server which provides the notification.
Requested QoS parametersMThe updated requested QoS parameters for the end-to-end session (NRM server to source VAL UE or NRM server to target VAL UE), based on the QoS change on one or both links involved in the network-assisted end-to-end communication.
Up

14.3.2.17  Monitoring Events Subscription Request |R17|p. 208

Table 14.3.2.17-1 describes the information flow from the VAL server to the NRM server for monitoring events subscription request.
Information Element Status Description
Identities listO
(see NOTE 1)
List of VAL users or VAL UEs whose events monitoring is requested.
VAL group IDO
(see NOTE 1)
VAL group ID of the VAL UE group of target UEs.
VAL service IDOVAL service ID.
Monitoring profile IDO
(see NOTE 2)
The monitoring profile ID, which identifies a list of monitoring and/or analytics events.
Validity conditionsOThe temporal and/or spatial conditions applied for the events to be considered as valid.
Event DetailsO
(see NOTE 2)
List of monitoring and/or analytics events that the VAL server is interested in.
NOTE 1:
For identifying the target UE(s), either a list of VAL users/UEs or a group of VAL UEs shall be provided.
NOTE 2:
Either Event Details or Monitoring profile ID is present.
Up

14.3.2.18  Monitoring Events Subscription Response |R17|p. 209

Table 14.3.2.18-1 describes the information flow from the NRM server to the VAL server for Monitoring Events Subscription response.
Information Element Status Description
Subscription statusMIt indicates the subscription result
Monitoring profile IDOIt indicates the monitoring profile identifier. It is present when Subscription status is success and Event Details are provided in the Monitoring Events Subscription request.
Up

14.3.2.19  Monitoring Events Notification message |R17|p. 209

Table 14.3.2.19-1 describes the information flow from the NRM server to the VAL server on notification of monitoring events.
Information Element Status Description
EventDetailsList of events related to VAL UE(s).
> identityMVAL UE for which the events are related to.
> eventsMList of Monitoring and Analytics events related to the VAL UE.
TimestampOThe timestamp for the monitoring and analytics events
Up

14.3.2.20  Unicast QoS monitoring subscription request |R17|p. 209

Table 14.3.2.20-1 describes the information flow from the VAL server to the network resource management server for unicast QoS monitoring subscription request.
Information Element Status Description
Requester IdentityMThe identity of the VAL server performing the request.
List of VAL UE IDsO
(see NOTE 1 NOTE 4)
List of VAL UEs whose QoS monitoring data is requested.
VAL group IDO
(see NOTE 1 NOTE 4)
The group ID used for the VAL group for which QoS monitoring data is requested.
List of VAL stream IDsO
(see NOTE 1 NOTE 4)
List of VAL streams for which QoS monitoring data is requested.
VAL service IDORepresents the VAL service ID.
Monitoring profile IDO
(see NOTE 5)
Represents the monitoring profile ID.
Monitoring profileO
(see NOTE 5)
Represents the monitoring profile.
> Measurement requirementsOIt describes the requirements on the QoS measurements.
>> type of dataMAt least one of the following measurement index shall be provided.
>>> packet delayOUL/DL/RT packet delay.
For VAL stream, the packet delay means measurement from a source UE to a target UE.
>>> packet loss rateOAverage packet loss rate.
>>> data rateOAverage data rate and/or maximum data rate.
>>> traffic volumeOAverage traffic volume for UL and/or DL.
>> measurement time periodOThe measurement time period indicates a current time period. If absent, current time and 5 minutes duration are used as default setting.
>> aggregation granularity windowO
OIndicates how long the QoS monitoring is performed to compute the average value and gather the maximum value. If absent, 1 minute is used as default setting.
> Reporting requirementsOIt describes the requirements for QoS monitoring reporting.
>> Frequency of reportingOIt indicates the requested frequency of reporting. The reporting frequency may be periodic or event triggered (i.e. threshold reached). If absent in the request, default event triggered reporting is used.
>> Reporting thresholdOIf the Frequency of reporting is event triggered (threshold reached), the reporting threshold corresponding to the measurement index shall be provided.
>> Threshold reaching directionOIt indicates the reaching direction (i.e. ascending, descending or crossed) for the reporting threshold. It shall be provided if reporting threshold is present.
>> Reporting periodicityOIf the Frequency of reporting is periodic, the reporting periodicity shall be provided.
> Termination of reportingO
(see NOTE 6)
It indicates when the reporting of QoS monitoring shall stop. It can be event triggered (i.e. either number of reports reached or threshold reached) or when reporting duration expires or when explicit termination is requested. If absent in the request, it defaults to explicit termination. Once the termination condition is met, the monitoring subscription ceases to exist.
> Max number of reportsO
(NOTE 3, NOTE 6)
It indicates the maximum number of reports, it shall be provided when Termination of reporting is set to event triggered (number of reports reached).
> Termination thresholdO
(see NOTE 2, NOTE 3, NOTE 6)
It indicates the reporting termination threshold corresponding to the measurement index. Each measurement index has only one termination threshold.
> Termination condition for termination thresholdO
(see NOTE 2, NOTE 6)
It indicates threshold-based termination condition (e.g. all reached or any of them reached) if multiple measurement indexes are provided.
> Reporting durationO
(NOTE 3, NOTE 6)
It indicates the reporting duration, it shall be provided when Termination of reporting is set to duration expiration.
NOTE 1:
Only one of these information elements shall be present.
NOTE 2:
It shall be provided when Termination of reporting is set to event triggered (threshold reached).
NOTE 3:
If provided, only one of these information elements shall be present.
NOTE 4:
When used by the Update_Unicast_QoS_Monitoring_Subscription operation, the same information element with identical content shall be present as in the associated Subscribe_Unicast_QoS_Monitoring operation.
NOTE 5:
Only one of these information elements shall be present.
NOTE 6:
When used by the Update_Unicast_QoS_Monitoring_Subscription operation, this IE may be used by the VAL server to modify the proposed by NRM server subscription termination conditions.
Up

14.3.2.21  Unicast QoS monitoring subscription response |R17|p. 212

Table 14.3.2.21-1 describes the information flow from the network resource management server to the VAL server for unicast QoS montoring subscription response.
Information Element Status Description
Subscription statusMIt indicates the subscription result
Monitoring profile IDORepresents the identifier of the stored monitoring profile. This IE may be present if the subscription status is success.
Termination of reportingOIt indicates when the reporting of QoS monitoring will stop. This IE may be present if the subscription status is success.
Up

14.3.2.22  Unicast QoS monitoring notification |R17|p. 212

Table 14.3.2.22-1 describes the information flow for unicast QoS monitoring notification from the network resource management server to the VAL server.
Information Element Status Description
List of VAL UE IDsO
(see NOTE 1)
List of VAL UEs whose QoS monitoring data is provided. This list is either the list provided in the subscription request or a subset of that list. It can contain a single UE.
VAL group IDO
(see NOTE 1)
The group ID used for the VAL group for which QoS monitoring data is provided. This group ID shall be the same VAL group ID as the VAL group ID provided in the subscription request.
List of VAL stream IDsO
(see NOTE 1)
List of VAL stream IDs whose QoS monitoring data is provided. This list is either the list provided in the subscription request or a subset of that list. It can contain a single stream ID.
QoS monitoring dataO
(see NOTE 2)
QoS monitoring data is an aggregate of QoS measurements data obtained from the 5GS.
Termination causeO
(see NOTE 2)
Indicates that the subscription is terminated with the termination cause.
Monitoring profile IDORepresents the monitoring profile identifier whose reporting requirements triggered notification.
NOTE 1:
Only one of these information elements shall be present.
NOTE 2:
At least one of these information elements shall be present.
Up

14.3.2.23  TSC stream availability discovery request |R17|p. 213

Table 14.3.2.23-1 describes the information flow TSC stream availability discovery request from the VAL server to the NRM server.
Information Element Status Description
Requester IdentityMThe identity of the VAL server performing the request.
Stream specificationM Stream specification includes MAC addresses of the source and destination DS-TT ports (e.g. as defined in IEEE 802.1CB [37]).
Up

14.3.2.24  TSC stream availability discovery response |R17|p. 213

Table 14.3.2.24-1 describes the information flow TSC stream availability discovery response from the NRM server to the VAL server.
Information Element Status Description
ResultMResult includes success or failure of the TSC stream availability discovery with the underlying network.
Stream specificationM Stream specification includes MAC addresses of the source and destination DS-TT ports (e.g. as defined in IEEE 802.1CB [37]).
List of traffic specificationsMThe traffic classes supported by the DS-TTs and available end-to-end MaxLatency value per traffic class. The VAL server should not request lower latency than the available end-to-end latency.
Up

14.3.2.25  TSC stream creation request |R17|p. 213

Table 14.3.2.25-1 describes the information flow TSC stream creation request from the VAL server to the NRM server.
Information Element Status Description
Requester Identity MThe identity of the VAL server performing the request.
VAL Stream IDMIt identifies the VAL stream.
Stream specificationMy Stream specification includes MAC addresses of the source and destination DS-TT ports (e.g. as defined in IEEE 802.1CB [37]).
Traffic specificationM It includes MaxLatency, MaxFrameInterval, MaxFrameSize, MaxIntervalFrames as described in IEEE 802.1Qcc [35] in clause 46.2.
Up

14.3.2.26  TSC stream creation response |R17|p. 213

Table 14.3.2.26-1 describes the information flow TSC stream creation response from the NRM server to the VAL server.
Information Element Status Description
ResultMResult includes success or failure of the TSC stream creation.
VAL Stream IDMIt identifies the VAL stream.
Up

14.3.2.27  TSC stream deletion request |R17|p. 214

Table 14.3.2.27-1 describes the information flow TSC stream deletion request from the VAL server to the NRM server.
Information Element Status Description
Requester Identity MThe identity of the VAL server performing the request.
VAL Stream IDMIt identifies the VAL stream.
Up

14.3.2.28  TSC stream deletion response |R17|p. 214

Table 14.3.2.28-1 describes the information flow TSC stream deletion response from the NRM server to the VAL server.
Information Element Status Description
ResultMResult includes success or failure of the network TSC stream deletion. Even in case of failure, the stream is deemed unusable.
VAL Stream IDMIt identifies the VAL stream.
Up

14.3.2.29  TSN bridge information report |R17|p. 214

The 5GS bridge management information is defined in clause 5.28.1 of TS 23.501 (5GS bridge management).

14.3.2.30  TSN bridge information confirmation |R17|p. 214

The 5GS bridge management information is defined in clause 5.28.1 of TS 23.501 (5GS bridge management).

14.3.2.31  TSN bridge configuration request |R17|p. 214

The configuration information of 5GS Bridge is defined in clause 5.28.2 of TS 23.501 (The configuration information of 5GS Bridge).

14.3.2.32  TSN bridge configuration response |R17|p. 214

The configuration information of 5GS Bridge is defined in clause 5.28.2 of TS 23.501 (The configuration information of 5GS Bridge).

14.3.2.33  Unicast QoS monitoring data request |R17|p. 214

Table 14.3.2.33-1 describes the information flow from the VAL server to the network resource management server for unicast QoS monitoring data request.
Information Element Status Description
Requester Identity MThe identity of the VAL server performing the request.
List of VAL UE IDs O (see NOTE)List of VAL UEs whose QoS monitoring data is requested.
VAL group ID O (see NOTE)The group ID used for the VAL group for which QoS monitoring data is requested.
List of VAL stream IDs O (see NOTE)List of VAL streams for which QoS monitoring data is requested.
Measurement requirementsMIt describes the requirements on the QoS measurement data to be provided.
> type of dataMAt least one of the following measurement index shall be provided.
>> packet delayOUL/DL/RT packet delay.
For VAL stream, the packet delay means measurement from a source UE to a target UE.
>> packet loss rateOAverage packet loss rate.
>> data rateOAverage data rate and/or maximum data rate.
>> traffic volumeOAverage traffic volume for UL and/or DL
> measurement time periodOThe measurement time period indicates either a current or past time period. If absent, current time and 5 minutes duration are used as default setting.
> aggregation granularity windowOIndicates how long the QoS monitoring is performed to compute the average value and gather the maximum value. If absent, 1 minute is used as default setting.
NOTE:
Only one of these information elements shall be present.
Up

14.3.2.34  Unicast QoS monitoring data response |R17|p. 215

Table 14.3.2.34-1 describes the information flow from the VAL server to the network resource management server for unicast QoS monitoring data response.
Information Element Status Description
List of VAL UE IDsO
(see NOTE 1)
List of VAL UEs whose QoS monitoring data is provided. This list is either the list provided in the request or a subset of that list. It can contain a single UE.
VAL group ID O (see NOTE 1)The group ID used for the VAL group for which QoS monitoring data is provided. This group ID shall be the same VAL group ID as the VAL group ID provided in the request.
List of VAL stream IDs O (see NOTE 1)List of VAL stream IDs whose QoS monitoring data is provided. This list is either the list provided in the request or a subset of that list. It can contain a single stream ID.
ResultMIndicates the success or failure for the operation
QoS monitoring dataM (see NOTE 2)QoS monitoring data is an aggregate of QoS measurements data obtained from the 5GS.
CauseOProvides reason for the failure (e.g. when data for the requested time period is not available).
NOTE 1:
Only one of these information elements shall be present.
NOTE 2:
If the Result information element indicates failure then the value of the QoS monitoring data information element has no meaning.
Up

14.3.2.35  Application connectivity request |R18|p. 216

Table 14.3.2.35-1 describes the information flow for application connectivity request from a NRM client to the NRM server.
Information element Status Description
Source VAL UE IDMIdentifier of the requestor VAL UE.
Source IP addressMIP address of the requestor VAL UE.
VAL service IDMIdentifier of the VAL service
List of destination VAL UE IDsMIdentifiers of the destination VAL UEs.
Application service requirementsMDetails of service requirements
>Packet size (see NOTE)OSize of the packet to be transmitted.
>Packet transmission interval (see NOTE)OIntervals at which the packet is to be transmitted
>Packet E2E latency (see NOTE)OE2E Latency for packet transmission
>Packet error KPI (see NOTE)OThe KPIs related to packet error (e.g. allowed packet loss rate, packet loss amount, packet error rate)
>Bitrate (see NOTE)OThe bitrate required
Application connectivity contextOApplication 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.
Information element Status Description
LocationOLocation information of the client. The element may also indicate whether network-determined location is to be used instead.
SpeedOSpeed information for the client.
DirectionODirection information for the client.
Up

14.3.2.36  Application connectivity response |R18|p. 216

Table 14.3.2.36-1 describes the information flow for application connectivity response from the NRM server to the NRM client.
Information element Status Description
ResultMResult from the NRM server in response to request indicating success or failure for accepting the request.
CauseOThe cause of failure, if the result indicates failure.
Up

14.3.2.37  Application connectivity notification |R18|p. 216

Table 14.3.2.37-1 describes the information flow for application connectivity notification from the NRM server to the NRM client.
Information element Status Description
Session informationMSession information for the established connectivity for application communication
VAL service IDMIdentifier of the VAL service
Requestor VAL UE IDMThe identity of the source VAL UE requesting the connectivity.
List of accepted destination VAL UE IDs (see NOTE)OThe 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.
Up

14.3.2.38  Unicast QoS monitoring subscription update request |R18|p. 217

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.

14.3.2.39  Unicast QoS monitoring subscription update response |R18|p. 217

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.
Information element Status Description
Update statusMIt indicates the subscription update result
Up

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

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. 218

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. 219

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 to be updated.
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. 219

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 to be updated.
New Identity of the multicast/broadcast resourceOThe identity of the new multicast/broadcast MBS session created during update.
User plane addressOAdditional 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, 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. 220

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. 220

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. 220

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. 220

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. 220

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. 221

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. 221

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. 221

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. 221

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. 222

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. 223

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. 223

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. 224

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.
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. 224

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.
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. 224

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.
Number of UEsMExpected number of UEs.
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.
Application traffic descriptorsOApplication traffic descriptors (e.g. addresses, port, transport layer protocol) of the VAL server.
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. 225

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. 225

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. 226

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. 226

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. 226

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.
Number of UEsOExpected number of UEs.
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.
Application traffic descriptors (see NOTE)OApplication traffic descriptors (e.g. addresses, port, transport layer protocol) of the VAL server.
Request expiration time (see NOTE)OExpiration 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.
Up

14.3.2.64  BDT configuration update response |R18|p. 227

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.
Granted time window (see NOTE)OGranted 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.
Up

14.3.2.65  BDT configuration delete request |R18|p. 227

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 delete response |R18|p. 228

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. 228

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. 228

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. 228

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. 229

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

14.3.2.71  MM-specific QoS management request |R19|p. 229

Table 14.3.2.71-1 describes the information flow MM-specific QoS management request from the NRM client to the NRM server.
Information element Status Description
List of VAL UEs or VAL Group IDMList of VAL UEs or the group of VAL UEs for whom the MM QoS management occurs.
> VAL UE/user IDMIdentity of the VAL UE.
> Connection informationOConnection information including address / port and / or URL of the VAL UE.
List of VAL serversMThe list of VAL servers involved in the mobile metaverse service.
> VAL server IDMIdentity of the VAL server.
> Connection informationOConnection information including address / port and / or URL of the VAL server.
MM service or session(s) IDOThe VAL service or session(s) identity for whom the QoS management occurs.
MM QoS requirementsOThe 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 informationOInformation and dependencies (e.g. sequence or priority) among VAL sessions within MM service.
Service areaOThe area where the QoS management request applies. This can be geographical area, or topological area.
Time validityOThe time of validity of the requirement.
Up

14.3.2.72  MM-specific QoS management response |R19|p. 229

Table 14.3.2.72-1 describes the information flow MM-specific QoS management response from the NRM server to the NRM client.
Information element Status Description
ResultMThe positive or negative result of the MM-specific QoS management request.
QoS report configurationOThe 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).
Up

14.3.2.73  MM service QoS configuration notification |R19|p. 230

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.
Information element Status Description
MM service IDMThe VAL service identity for whom the QoS management occurs.
VAL session IDMThe VAL session for which the QoS is configured.
> MM QoS configurationMThe configuration of the QoS attributes (latency, jitter) for the VAL sessions within the MM service.
QoS report configurationOThe 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).
Up

Up   Top   ToC