Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.433  Word version:  19.4.0

Top   Top   Up   Prev   Next
0…   4…   7…   8…   9.2…   9.2.2.3…   9.2.3…   9.2.4…   9.3…   9.3.2.2…   9.3.3…   9.3.4…   9.4…   9.5…   9.5.3…   9.5.4…   9.6…   9.7…   9.7.3…   9.7.4…   9.8…   9.9…   9.9.3…   9.10…   9.10.3…   9.11…   9.11.3…   9.12…   9.12.3…   9.13   10…   A…   C   D…

 

9.2.3  Information flowsp. 38

9.2.3.1  SEALDD enabled regular transmission requestp. 38

Table 9.2.3.1-1 describes the information flow from the VAL server to the SEALDD server for requesting the regular application transmission service.
Information element Status Description
VAL server IDMIdentity of the VAL server.
VAL service IDOIdentity of the VAL service.
IdentityOIdentifier of specific UE or VAL user.
SEALDD-S connection informationMAddress information (e.g., IP address and/or port, URL) of the VAL server to receive the traffic from the SEALDD server.
QoS informationOQoS information provided by VAL server.
VAL server's total bandwidth limitO
(See NOTE)
The total bandwidth limit of VAL server, including UL/DL.
VAL users' bandwidth limitO
(See NOTE)
The bandwidth limits (i.e. minimum bandwidth requirement and maximum bandwidth limit) for VAL users, including UL/DL.
NOTE:
These IEs are used for the SEALDD enabled bandwidth control for different VAL users.
Up

9.2.3.2  SEALDD enabled regular transmission responsep. 38

Table 9.2.3.2-1 describes the information flow from the SEALDD server to the VAL server for responding to the regular application transmission.
Information element Status Description
ResultMSuccess or failure.
SEALDD-S information connection informationOAddress information (e.g., IP address and/or port, URL) of the SEALDD server to receive the packets from the VAL server for traffic transfer.
CauseO
(See NOTE)
Indicates the reason for the failure, e.g. SEALDD policy mismatch.
NOTE:
The IE is only present if the Result is failure.
Up

9.2.3.3  SEALDD regular transmission connection establishment requestp. 38

Table 9.2.3.3-1 describes the information flow from the SEALDD client to the SEALDD server or from the SEALDD server to the SEALDD client for requesting the regular SEALDD connection establishment.
Information element Status Description
Requestor IDMIdentity of the requestor (SEALDD client or SEALDD server).
SEALDD-UU flow IDM
(See NOTE 1)
Identity of the SEALDD-UU flow.
VAL server IDOIdentity of the VAL server, applicable for SEALDD client side initiated request.
VAL service IDOIdentity of the VAL service
Selected VAL server endpointMEndpoint of the selected VAL server
SEALDD traffic descriptorOSEALDD traffic descriptor (e.g. address, port, URL, transport layer protocol) of the SEALDD client side (for client side initiated request) or the SEALDD server side (for server side initiated request) used to establish SEALDD connection.
IdentityOThe VAL user ID of the VAL user or VAL UE ID.
SEALDD communication lifetimeOIdentifies the DD communication lifetime, applicable for SEALDD server side initiated request.
Capability for BAT and periodicity adaptationO
(See NOTE 2)
Indicates BAT and periodicity adaptation capability of the SEALDD client side (for client side initiated request) per SEALDD traffic descriptor.
Transmission assistance infoO
(See NOTE 2, NOTE 4)
Indicates transmission assistance information for uplink SEALDD traffic of the SEALDD client side (for client side initiated request).
It includes BAT, BAT window, periodicity, and periodicity range per SEALDD traffic descriptor.
L4S feedback capabilityO
(See NOTE 3)
Identifies the L4S feedback capability (i.e. ECN identification, L4S feedback) for client side initiated request.
VAL UE client access capabilityOIndicates the access technologies supported by VAL UE client. E.g.,3GPP, Non-3GPP(WLAN).
XR Application device capability informationO
(See NOTE 5)
Indicates XR Application device capability information (e.g., encoding capabilities).
NOTE 1:
The SEALDD-UU flow ID is used by the SEALDD client and SEALDD server to identify different application traffic, and it is mapped to the identifiers of the application traffic and data transmission session.
NOTE 2:
If provided, BAT window and periodicity range are mutually exclusive with capability for BAT and periodicity adaptation.
NOTE 3:
This IE is used for the SEALDD enabled congestion control for VAL applications, as specified in clause 9.8.2.2.
NOTE 4:
The periodicity range may only be present together with the periodicity when BAT and BAT window are present. The BAT window may only be present together with the BAT.
NOTE 5:
This IE is used for the SEALDD enabled XR traffic data delivery.
Up

9.2.3.4  SEALDD regular transmission connection establishment responsep. 39

Table 9.2.3.4-1 describes the information flow from the SEALDD server to the SEALDD client or from the SEALDD client to the SEALDD server for responding to the regular SEALDD connection establishment.
Information element Status Description
ResultMIndicates the success or failure of establishing the SEALDD connection.
SEALDD traffic descriptorOSEALDD traffic descriptor (e.g. address, port, URL, transport layer protocol) of the SEALDD server side (for client side initiated request) or the SEALDD client side (for server side initiated request) used to establish SEALDD connection.
Pending timerO
(See NOTE 1)
The pending timer to trigger the re-connection from SEALDD client when bandwidth limit check is failed.
Suggested traffic transmission bandwidthO
(See NOTE 1)
The suggested traffic transmission bandwidth used by SEALDD client or SEALDD server to perform bandwidth control for VAL users, including UL/DL.
CauseO
(See NOTE 2)
Indicates the reason for the failure, e.g. SEALDD policy mismatch.
Capability for BAT and periodicity adaptationO
(See NOTE 3)
Indicates BAT and periodicity adaptation capability of the SEALDD client side (for server side initiated request) per SEALDD traffic descriptor.
Transmission assistance infoO
(See NOTE 3, NOTE 4)
Indicates transmission assistance information for uplink SEALDD traffic of the SEALDD client side (for server side initiated request).
It includes BAT, BAT window, periodicity, and periodicity range per SEALDD traffic descriptor.
NOTE 1:
These IEs are used for the SEALDD enabled bandwidth control for different VAL users, applicable for client side initiated request.
NOTE 2:
This IE is only present if the Result is failure.
NOTE 3:
If provided, BAT window and periodicity range are mutually exclusive with capability for BAT and periodicity adaptation.
NOTE 4:
The periodicity range may only be present together with the periodicity when BAT and BAT window are present. The BAT window may only be present together with the BAT.
Up

9.2.3.5  SEALDD regular data transmission connection release requestp. 40

Table 9.2.3.5-1 describes the information flow from the SEALDD client to the SEALDD server or from the SEALDD server to the SEALDD client for requesting the SEALDD connection release.
Information element Status Description
Requestor IDMIdentity of the requestor (SEALDD client or SEALDD server).
SEALDD-UU flow IDMIdentifies the SEALDD-UU flow.
Up

9.2.3.6  SEALDD regular data transmission connection release responsep. 40

Table 9.2.3.6-1 describes the information flow from the SEALDD server to the SEALDD client or from the SEALDD client to the SEALDD server for responding the SEALDD connection release request.
Information element Status Description
ResultMResult of the operation.
Up

9.2.3.7  SEALDD connection status subscription requestp. 40

Table 9.2.3.7-1 describes the information flow from the VAL server to SEALDD server to subscribe to SEALDD connection status information.
Information element Status Description
VAL server IDMIdentity of the VAL server.
Event ID listMIdentifies a list of events such as establishment, release, congestion report, SEALDD client connection status.
VAL service IDOIdentity of the VAL service.
IdentityOIdentifier of VAL UE or VAL user.
SEALDD-S connection informationMAddress information (e.g., IP address and/or port, URL) to send/receive the traffic to/from the SEALDD server.
Immediate reporting flagOIndicates the immediate reporting of connection status notification.
SEALDD client connection status check periodicityOIndicates the frequency to perform SEALDD client connection status check.
Non-3GPP access measurement informationOIndicates the Non-3GPP access measurement information like list of WLAN SSIDs, location-based measurement.
Up

9.2.3.8  SEALDD connection status subscription responsep. 41

Table 9.2.3.8-1 describes the information flow from the SEALDD server to VAL server for responding SEALDD connection status subscription request.
Information element Status Description
ResultMSuccess or failure.
Subscription IDO
(NOTE)
Subscription identifier corresponding to the subscription.
Expiration timeO
(NOTE)
Indicates the expiration time of the subscription.
NOTE:
These IEs shall be present when the result is success.
Up

9.2.3.9  SEALDD connection status notificationp. 41

Table 9.2.3.9-1 describes the information flow from the SEALDD server to the VAL server to notify SEALDD connection status.
Information element Status Description
Event IDMIdentifies event such as establishment, release, congestion report, SEALDD client connection status.
IdentityMIdentifier of VAL UE or VAL user.
VAL service IDMIdentity of the VAL service.
SEALDD connection establishment dataO
(see NOTE 1)
Data related to SEALDD connection establishment.
> SEALDD-S connection informationMAddress information (e.g., IP address and/or port, URL of the SEALDD server to send/receive the traffic to/from the VAL server.
> SEALDD communication lifetimeOIdentifies the DD communication lifetime.
Congestion levelO
(See NOTE 2)
The congestion level of the VAL service.
SEALDD client connection statusO
(See NOTE 3)
Indicates the connection status of VAL UE/user e.g. reachable, unreachable, sleeping.
NOTE 1:
This IE is used for the establishment event.
NOTE 2:
This IE is used for the congestion report event.
NOTE 3:
This IE is used for the SEALDD client connection status event.
Up

9.2.3.10  SEALDD client connection status reporting configuration requestp. 42

Table 9.2.3.10-1 describes the information flow from the SEALDD server to SEALDD client to configure the SEALDD client for connection status reporting.
Information element Status Description
SEALDD-UU Flow IDMIndicates the SEALDD-UU flow ID of the application for which the reporting is required.
Mode of reportingOIndicates the mode of reporting: periodic and/or event triggered.
> Reporting intervalO
(See NOTE)
Indicates the reporting interval to report the notification.
SEALDD client connection status reporting priorityOIndicates the priority of the requested SEALDD-UU flow ID for the reporting of the SEALDD client connection status.
Non-3GPP access measurement informationOIndicates the Non-3GPP access measurement information for the SEALDD client to perform measurement. It contains list of WLAN SSIDs or location-based reporting and signal strengths (e.g., RSRP, RSSI, RSRQ, SINR) values for measurement.
NOTE:
This IE shall be present if the mode of reporting is periodic.
Up

9.2.3.11  SEALDD client connection status reporting configuration responsep. 42

Table 9.2.3.11-1 describes the information flow from the SEALDD client to the SEALD server for sending the SEALDD client connection status reporting configuration response.
Information element Status Description
ResultMSuccess or failure.
Up

9.2.3.12  SEALDD client connection status reporting notificationp. 42

Table 9.2.3.12-1 describes the information flow from the SEALDD client to the SEALD server for sending the SEALDD client connection status reporting configuration response.
Information element Status Description
SEALDD client connection statusMIndicates the status of VAL UEs/users like reachable, unreachable, or sleeping.
Non-3GPP access measurement information reportingOIndicates the Non-3GPP access measurement information report. It contains measured list of WLAN SSIDs and signal strengths(e.g., RSRP, RSRQ, RSSI, SINR) values.
SEALDD data transmission connection access usageMIndicates which access(3GPP or Non-3GPP) is used for the SEALDD-UU data transmission.
Up

9.2.3.13  SEALDD connection status subscription update requestp. 42

Table 9.2.3.13-1 describes the information flow from the VAL server to SEALDD server to update subscription for SEALDD connection status information.
Information element Status Description
Subscription IDMSubscription identifier corresponding to the subscription to be updated.
Event ID listOIdentifies a list of events such as establishment, release, congestion report, SEALDD client connection status.
Immediate reporting flagOIndicates the immediate reporting of connection status notification.
SEALDD client connection status check periodicityOIndicates the frequency to perform SEALDD client connection status check.
Up

9.2.3.14  SEALDD connection status subscription update response |R19|p. 43

Table 9.2.3.14-1 describes the information flow from the SEALDD server to VAL server for responding SEALDD connection status subscription update request.
Information element Status Description
ResultMSuccess or failure.
Expiration timeO
(NOTE)
Indicates the expiration time of the subscription.
NOTE:
This IE shall be present when the result is success.
Up

9.2.3.15  SEALDD connection status unsubscribe request |R19|p. 43

Table 9.2.3.15-1 describes the information flow from the VAL server to SEALDD server to unsubscribe the SEALDD connection status information.
Information element Status Description
Subscription IDMSubscription identifier corresponding to the subscription to be updated.
Up

9.2.3.16  SEALDD connection status unsubscribe response |R19|p. 43

Table 9.2.3.16-1 describes the information flow from the SEALDD server to VAL server for responding SEALDD connection status unsubscribe request.
Information element Status Description
ResultMSuccess or failure.
Up

9.2.3.17  SEALDD data transmission connection establishment initiated by SEALDD server request |R19|p. 43

Table 9.2.3.17-1 describes the information flow from the SEALDD server to the SEALDD client for requesting the SEALDD data transmission connection establishment.
Information element Status Description
Requestor IDMIdentity of the requestor (SEALDD client or SEALDD server).
SEALDD-UU flow IDM
(See NOTE 1)
Identity of the SEALDD-UU flow.
VAL service IDOIdentity of the VAL service.
Selected VAL server endpointMEndpoint of the selected VAL server.
SEALDD traffic descriptorOSEALDD traffic descriptor (e.g. address, port, URL, transport layer protocol) of the SEALDD server used to establish SEALDD connection.
IdentityOThe VAL user ID of the VAL user or VAL UE ID.
SEALDD communication lifetimeOIdentifies the DD communication lifetime.
NOTE 1:
The SEALDD-UU flow ID is used by the SEALDD client and SEALDD server to identify different application traffic, and it is mapped to the identifiers of the application traffic and data transmission session.
Up

9.2.3.18  SEALDD data transmission connection establishment initiated by SEALDD server response |R19|p. 44

Table 9.2.3.18-1 describes the information flow from the SEALDD client to the SEALDD server for responding to the SEALDD data transmission connection establishment.
Information element Status Description
ResultMIndicates the success or failure of establishing the SEALDD connection.
SEALDD traffic descriptorOSEALDD traffic descriptor (e.g. address, port, URL, transport layer protocol) of the SEALDD client side used to establish SEALDD-UU data connection.
Suggested traffic transmission bandwidthO
(See NOTE 1)
The suggested traffic transmission bandwidth used by SEALDD client to perform bandwidth control for VAL users, including UL/DL.
CauseO
(See NOTE 2)
Indicates the reason for the failure, e.g. SEALDD policy mismatch.
Capability for BAT and periodicity adaptationO
(See NOTE 3)
Indicates BAT and periodicity adaptation capability for SEALDD client.
Capability for BAT and periodicity adaptationO
(See NOTE 3)
Indicates BAT and periodicity adaptation capability for SEALDD client.
NOTE 1:
These IEs are used for the SEALDD enabled bandwidth control for different VAL users.
NOTE 2:
This IE is only present if the Result is failure.
NOTE 3:
If provided, only one of these IEs shall be present in the message.
Up

Up   Top   ToC