hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
6.2 Data transmission requirements
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
6.2.1 Description
|
This clause specifies the data transmission requirements for SEALDD service.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
6.2.2 Requirements
|
[AR-6.2.2-a] The SEALDD service shall provide a mechanism for application signalling data transmission and application media data transmission between VAL client(s) and VAL server(s).
[AR-6.2.2-b] The SEALDD service shall provide a mechanism to support the data transmission quality requirement configurations and measurements for the application data transmission between VAL client(s) and VAL server(s).
[AR-6.2.2-c] The SEALDD service shall provide a mechanism for application data transmission between VAL client(s) and VAL server(s) with guaranteed quality.
[AR-6.2.2-d] The SEALDD service shall provide a mechanism for application data packaging and un-packaging to support the data transmission between VAL client(s) and VAL server(s).
[AR-6.2.2-e] The SEALDD service shall provide a mechanism for E2E redundant data transmission between VAL client and VAL server.
[AR-6.2.2-f] The SEALDD service shall provide a mechanism to support the packet/data duplication, elimination and error recovery between VAL client and VAL server.
[AR-6.2.2-g] The SEALDD service shall provide a mechanism to support favouring time windows for data transfer between VAL client(s) and VAL server(s) that are less costly and/or able to handle larger bitrates.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
6.3 Data storage requirements
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
6.3.1 Description
|
This clause specifies the data storage requirements for SEALDD service.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
6.3.2 Requirements
|
[AR-6.3.2-a] The SEALDD service shall provide a mechanism for data storage supporting the CRUD operations.
[AR-6.3.2-b] The SEALDD service shall provide a mechanism to support the data storage status management.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
6.4 SEALDD server discovery and selection requirements
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
6.4.1 Description
|
This clause specifies the SEALDD server discovery and selection requirements for SEALDD service.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
6.4.2 Requirements
|
[AR-6.4.2-a] The SEALDD service shall provide a mechanism for supporting the SEALDD server discovery and selection for VAL server.
[AR-6.4.2-b] The SEALDD service shall provide a mechanism to provide the information of SEALDD server to VAL/SEALDD client.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
6.5 MSGin5G message transfer requirements
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
6.5.1 Description
|
This clause specifies the MSGin5G message transfer requirements for SEALDD service.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
6.5.2 Requirements
|
[AR-6.5.2-a] The SEALDD service shall provide a mechanism to support the SEALDD traffic transmission using MSGin5G message.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
6.6 Data transmission bandwidth control requirements
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
6.6.1 Description
|
This clause specifies the data transmission bandwidth control requirements for SEALDD service.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
6.6.2 Requirements
|
[AR-6.6.2-a] The SEALDD service shall provide a mechanism to support the transmission bandwidth control for VAL application.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
7 Architecture
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
7.1 General
|
The architecture for the SEAL data delivery enabler is based on the generic functional model specified in clause 6.2 of 3GPP TS 23.434 [4].
This clause provides the overall architecture description:
- Clause 7.2 describes the functional architecture;
- Clause 7.3 describes the functional entities;
- Clause 7.4 describes the reference points; and
- Clause 7.5 describes the cardinality of functional entities and reference points.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
7.2 Architecture
|
This clause describes the architecture for enabling SEAL Data Delivery applications in the following representations:
- A service-based representation as specified in 3GPP TS 23.434 [4], where the SEAL Data Delivery Enabler Layer functions (e.g. SEALDD server) enable other authorized Vertical Application Layer functions (e.g. VAL server) to access their services.
- A service-based representation as specified in 3GPP TS 23.501 [5], where the Network Functions (e.g. NEF) enable authorized SEAL Data Delivery Layer functions (e.g. SEALDD server) i.e. Application Functions, to access their services;
- A service-based representation, where the Core Network Northbound APIs as specified in 3GPP TS 23.501 [5] and 3GPP TS 23.502 [6], are utilized by authorized SEAL Data Delivery Enabler Layer functions via CAPIF core function specified in 3GPP TS 23.222 [3]; and
- A reference point representation, where existing interactions between any two functions (e.g. SEALDD client and SEALDD server) is shown by an appropriate point-to-point reference point (e.g. SEALDD-UU).
SEAL Data Delivery Enabler Layer functions shown in the service-based representation of the SEAL Data Delivery architecture shall only use service-based interfaces for their interactions.
The service based representation of SEAL Data Delivery function in the overall SEAL service-based representation is specified in clause 15 of 3GPP TS 23.434 [4]. The SEALDD function exhibits service-based interfaces which are used for providing and consuming SEALDD services. The service-based interface for SEALDD function is representation as Sdd.
Figure 7.2-1 illustrates the service-based representation for utilization of the 5GS network services based on the 5GS SBA specified in 3GPP TS 23.501 [5].
Figure 7.2-1: Utilization of 5GS network services based on the 5GS SBA – service based representation
The SEALDD server acts as AF for consuming network services from the 3GPP 5G Core Network entities over the Service Based Architecture specified in 3GPP TS 23.501 [5].
Figure 7.2-2 illustrates the service-based representation for utilization of the Core Network (5GC, EPC) northbound APIs via CAPIF.
Figure 7.2-2: Utilization of Core Network Northbound APIs via CAPIF – service based representation
The SEALDD server acts as authorized API invoker to consume services from the Core Network (5GC, EPC) northbound API entities like SCEF, NEF, SCEF+NEF which act as API Exposing Function as specified in 3GPP TS 23.222 [3].
The mechanism for northbound APIs discovery using the service-based interfaces depicted in figure 7.2-3 is as specified in 3GPP TS 23.222 [3].
Figure 7.2-3 illustrates the architecture for SEAL Data Delivery enabler service.
Figure 7.2-3: Architecture for SEAL Data Delivery Service
The SEALDD server communicates with the control plane of 3GPP core network via N33/N5 interface with the SEALDD control plane functionality. The SEALDD server may consume other SEAL (e.g. NRM) services.
For uplink traffic, VAL client sends application data traffic to SEALDD client for SEALDD service over SEALDD-C. After data plane packet processing by SEALDD client, the application data traffic is converted to SEALDD data traffic and transferred to SEALDD server over SEALDD-UU. The SEALDD server restores the application data traffic and sends it to VAL server over SEALDD-S. For downlink traffic, VAL server sends application data traffic to SEALDD server for SEALDD service over SEALDD-S. After data plane packet processing by SEALDD server, the application data traffic is converted to SEALDD data traffic and transferred to SEALDD client over SEALDD-UU. The SEALDD client restores the application data traffic and sends it to VAL client over SEALDD-C. Optionally, VAL deployments may choose to route application signalling traffic and application data traffic for some or all functions it offers using SEALDD service and figure 7.2-4 illustrates the architecture for achieving this. In this case the VAL client and VAL server may choose not to maintain application connection by themselves and transfer all the application traffic over SEALDD connections for those functions. The data storage functionality may be provided by SEALDD server or provided by other storage functions in VAL server, or other cloud platform.
To facilitate the specific optimization for XR application provided by 5G network, the application enablement architecture for the XRApp service is based on the generic functional model specified in 3GPP TS 23.434 [4].
NOTE 1: It is up to the implementation of VAL server about which storage entity (e.g. VAL server, SEALDD server, or other cloud platform) is selected and used.
NOTE 2: SEALDD capabilities are provided as APIs to the VAL Layer, it is up to VAL layer to decide which traffic to be transferred (e.g. application signalling, application data).
Figure 7.2-4: Architecture for application traffic transfer
The SEAL Data Delivery client interacts with the SEAL data delivery server to establish application layer data transport path.
Through this path, the SEALDD server and client provides data transport service capabilities such as data plane packet processing (e.g. packet duplication, elimination or transport coordination), data forwarding, data caching, background data transfer, etc. to support the VAL server and VAL client. Annex C describes a typical lifecycle of SEALDD to establish the SEALDD connection for the VAL client and VAL server.
Figure 7.2-5 illustrates the architecture for SEAL Data Delivery enabler service used to support UE-to-UE communication.
Figure 7.2-5: SEALDD architecture with on-network and off-network
VAL UE 1 and VAL UE 2 have on-network connectivity, and both VAL UEs directly communicate with each other via off-network connectivity (i.e. SEALDD-PC5 reference point) or via on-nework connectivity (i.e. SEALDD-UU reference point).
Multi-modal services are based on several data flows related to each other and subject to application coordination. The data flows transfers different types of data (for example audio, video, positioning, haptic data) and may come from different sources(e.g. a single UE, a single device or multiple devices connected to the single UE, or multiple UEs).
Figure 7.2-6 illustrates XR multi-modal services using two different XR Servers. To support E2E multi-modal communication flows between multiple VAL clients and servers, a SEALDD server and clients may support multi-modal service capabilities. The SEALDD server and clients perform multi-modal traffic transfer and management processing (e.g., E2E synchronization of application traffic having multi-modal dependencies with one another).
Figure 7.2-6: Architecture for multi-modal application traffic transfer with tethered devices.
To support the Tethered device, there are two types of Application enablement architectures based on SEALDD and PINAPP, corresponding to two types of tethered devices. One is the tethered XR device, where XR application client is deployed on the tethered XR device, i.e., Tethered Standalone AR Glasses, and Tethered AR Glasses with 5G Relay. The other is the Tethered Display XR device, who deploys the XR application on the 5G client, with only the XR runtime residing on the tethered UE.
For the tethered XR device, the application enablement layer architecture is shown in the figure 7.2-7. The SEALDD client on the 3GPP UE, acting as PIN client, could get tethered device information from the PEMC using the PIN-3 interface. Then the SEALDD client could interact with XR client on the tethered device to do the tethered link measurement. The interaction between the SEALDD client and XR client on different device is conducted over SEALDD-C.
Figure 7.2-7: Application enablement architecture based on SEALDD and PINAPP without SEALDD client in the tethering device
For the Tethered Display XR device, the application enablement layer architecture is shown in the figure 7.2-8. The SEALDD client on the 3GPP UE, acting as PIN client, could get tethered device information from the PEMC using the PIN-3 interface. The SEALDD-UUc interface supports the interaction between the SEALDD client on the tethered UE and SEALDD client on the 3GPP UE.
Figure 7.2-8: Application enablement architecture based on SEALDD and PINAPP with SEALDD client in the tethering device
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
7.3 Functional entities
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
7.3.1 General
|
The functional entities for SEALDD service are described in the following clauses.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
7.3.2 SEAL Data Delivery server
|
The SEAL data delivery server functional entity acts as the application server for the data delivery enablement. The SEALDD server supports the following capabilities:
a) Support the signalling interaction with VAL server to negotiate the data delivery aspects including QoS requirement, protocols information, bandwidth settings, delivery policy provisioning, transmission quality measurement, background data transfer.
b) Support the signalling interaction with the SEALDD client to management the data delivery between the SEALDD server and the SEALDD client, including the establish/update/release of signalling plane and user plane of SEALDD-UU, bandwidth control, transmission quality measurement.
c) Providing the application data/media storage.
d) Interacting with 5GC via N33/N5 (i.e. send control plane requirements or receive control plane notification) with usage of capability exposed by 3GPP network.
e) Support user plane handlings including obtaining the application data/media and/or application signalling data from VAL server via SEALDD-S, delivering it to the SEALDD client via the SEALDD-UU, and receiving the application data/media and/or application signalling data from SEALDD client and providing it to the VAL server via SEALDD-S, enforce the rate control.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
7.3.3 SEAL Data Delivery client
|
The SEAL data delivery client functional entity acts as the application client for the data delivery enablement. The SEALDD client supports the following capabilities:
a) Interact with the SEALDD server to management the data delivery between the SEALDD server and the SEALDD client, including the establish/update/release of signalling and user plane of SEALDD-UU, bandwidth control, transmission quality measurement.
b) Support user plane handlings including obtaining the application data/media and/or application signalling data from VAL client, delivering it to the SEALDD server via the SEALDD -UU, and receiving the application data/media and/or application signalling data from SEALDD client, providing it to the VAL server via the SEALDD-S.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
7.4 Reference points
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
7.4.1 General
|
The reference points for the functional model for SEALDD are described in the following clauses.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
7.4.2 SEALDD-UU
|
SEALDD-UU reference point is between the SEALDD client and the SEALDD server. It supports the user plane functionality of transferring data content and the signalling plane functionality of exchanging information for SEALDD service provisioning, control, reporting etc.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
7.4.3 SEALDD-C
|
Reference point between SEALDD client and VAL client to enable northbound client side API exposed by SEALDD client to VAL client for data delivery and SEALDD service provisioning, control, reporting etc. This reference point should also enables the interaction between the VAL client on the tethered device and SEALDD client on the 3GPP device to support the tethering link management(e.e., measurement etc.).
NOTE: Detailed specification of this reference point is out of scope of this release of this specification.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
7.4.4 SEALDD-S
|
SEALDD-S reference point is between the SEALDD server and the VAL server. It supports the user plane functionality of data content delivery and the signalling plane functionality SEALDD service provisioning, control, reporting etc.
NOTE: The data/content delivery between SEALDD server and VAL server can use the pull mode or push mode over SEALDD-S interface, as specified in clause 9.1.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
7.4.5 SEALDD-E
|
Reference point enables interactions between two SEALDD servers to transfer data content and exchange information for SEALDD service provisioning, control, reporting etc.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
7.4.6 N6
|
Reference point enables interactions between SEALDD server and 5GC to transfer SEALDD traffic packets.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
7.4.7 N33/N5
|
Reference point enables interactions between SEALDD server and 5GC to send control plane requirements or receive control plane notification for optimized data transmission.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
7.4.8 SEALDD-UUc
|
Reference point enables the interactions between the SEALDD client on the tethered device and SEALDD client on the 3GPP device.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
7.4.9 SEALDD-PC5
|
SEALDD-PC5 reference point is between the SEAL clients of two VAL UEs. This reference point utilizes PC5 reference point as described in 3GPP TS 23.303 [16] or 3GPP TS 23.304 [17]. It supports the user plane functionality of transferring data content and the signalling plane functionality of exchanging information for SEALDD service provisioning, control, reporting etc.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
7.4.10 SEALDD-X
|
Reference point enables interactions between the SEALDD server and other SEAL enablers to exchange information for SEALDD service provisioning, control, reporting etc.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
7.5 Cardinality rules
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
7.5.1 General
|
The cardinality rules for the SEALDD entities and SEALDD reference points are described in the following clauses.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
7.5.2 Functional Entity Cardinality
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
7.5.2.1 VAL client
|
The following cardinality rules apply for VAL clients:
a) One or more VAL client(s) may be located in a VAL UE.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
7.5.2.2 SEALDD client
|
The following cardinality rules apply for SEALDD clients:
a) One or more SEALDD client(s) may be located in a VAL UE.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
7.5.2.3 SEALDD server
|
The following cardinality rules apply for SEALDD server:
a) One or more SEALDD server(s) may be located in network.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
7.5.2.4 VAL server
|
The following cardinality rules apply for VAL server:
a) One or more VAL server(s) may be located in network.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
7.5.3 Reference Point Cardinality
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
7.5.3.1 SEALDD-C (Between VAL client and SEALDD client)
|
The following cardinality rules apply for the reference of SEALDD-C:
a) One VAL client may communicate with only one SEALDD client; and
b) One SEALDD client may communicate with one or more VAL client(s) concurrently.
NOTE: Detailed specification of this reference point is out of scope of this release of this specification.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
7.5.3.2 SEALDD-S (Between VAL layer and SEALDD server)
|
The following cardinality rules apply for the reference of SEALDD-S:
a) One VAL server may communicate with one or more SEALDD server; and
b) One SEALDD server may communicate with one or more VAL server(s) concurrently.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
7.5.3.3 SEALDD-UU (Between SEALDD client and SEALDD server)
|
The following cardinality rules apply for the reference of SEALDD-UU:
a) One SEALDD client may communicate with one or more SEALDD servers.
b) One SEALDD server may communicate with one or more SEALDD client(s) concurrently.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
7.5.3.4 SEALDD-E (Between SEALDD server and SEALDD server)
|
The following cardinality rules apply for the reference of SEALDD-E:
a) One SEALDD server may communicate with one or more SEALDD server(s) concurrently.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
7.5.3.5 SEALDD-PC5 (Between SEAL clients of two VAL UEs)
|
The following cardinality rules apply for the reference of SEALDD-PC5:
a) One SEALDD client may communicate with one or more SEALDD client(s) concurrently.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
7.5.3.6 SEALDD-X (Between SEALDD server and other SEAL server)
|
The following cardinality rules apply for the reference of SEALDD-X:
a) One SEALDD server may communicate with one or more SEAL server(s) concurrently.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
7.5.3.7 SEALDD-UUc (Between the SEALDD client on the tethered device and SEALDD client on the 3GPP UE)
|
The following cardinality rules apply for the reference of SEALDD-UUc:
a) One SEALDD client may communicate with one or more SEALDD client (s) concurrently.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
8 Identities and commonly used values
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
8.1 General
|
The common identities for SEAL refer to 3GPP TS 23.434 [4]. The following clauses list the additional identities and commonly used values for SEALDD.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
8.2 SEALDD server ID
|
The SEALDD server ID uniquely identifies the SEAL data delivery server.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
8.3 SEALDD client ID
|
The SEALDD client ID is a globally unique value that identifies the SEAL data delivery client.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
8.4 SEALDD-UU flow ID
|
The SEALDD-UU flow ID is used by the SEALDD client and SEALDD server to identify different VAL application traffic, which has the same attributes, e.g. the same 5-tuple, media type, QoS requirements. The SEALDD-UU flow ID should be uniquely identified with the SEALDD-UU connection.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
8.5 Multi-modal SEALDD-UU flow ID
|
The multi-modal SEALDD-UU flow ID is used by the SEALDD client and SEALDD server to uniquely identify associated multi-modal VAL application traffic flows per VAL service.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
8.6 Multi-modal service ID
|
The Multi-modal Service ID is an identifier of the multi-modal service as defined in clause 6.1.3.27.3 of 3GPP TS 23.503 [7]. Data flows belonging to the same multi-modal service share the same Multi-modal Service ID.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9 Procedures and information flows
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.1 General
|
The VAL application data/content is stored in the VAL server, or the SEALDD server, or other cloud platform. For the downlink traffic transmission, the SEALDD server retrieves the data/content of VAL application, by using one of the following modes:
- Downlink pull mode: the SEALDD server pulls the data/content of VAL application from the address provided by the VAL server (i.e. pull from the data/content address in VAL server over SEALDD-S interface, or in other cloud platform).
- Downlink push mode: the VAL server pushes the data/content of VAL application to the SEALDD server over SEALDD-S interface.
For the uplink traffic transmission, the SEALDD server sends the data/content of VAL application to the address provided by the VAL server, by using one of the following modes:
- Uplink pull mode: the VAL server pulls the data/content of VAL application from the SEALDD server over SEALDD-S interface.
- Uplink push mode: the SEALDD server pushes the data/content of VAL application to the address provided by the VAL server (i.e. push to the data/content address in VAL server over SEALDD-S interface, or in other cloud platform).
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2 SEALDD regular connection management
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.1 General
|
The following clauses specify procedures, information flow and APIs for establishing an SEALDD enabled end-to-end connection between VAL client and VAL server. The end-to-end connection (also termed SEALDD-UU flow) is uniquely identified in the SEALDD layer by the SEALDD-UU flow ID. The specific procedures detailed in the subsequent clauses are for cases in which the SEALDD regular connection is used respectively for application signalling, application data delivery initiated by VAL server, and application data delivery initiated based on DD policy.
NOTE: SEALDD server and VAL server may have different behaviour when establishing the connection for signalling transmission and regular data transmission. For signalling transmission, the VAL server may allocate the same address and port to send/receive the signalling traffic of all the users. For data transmission, the VAL server may allocate different addresses and ports to send/receive the data traffic of different users. And SEALDD server may need to identify the data traffic by checking the SEALDD connection establishment request since different SEALDD clients’ application data traffic should be mapped to their specific SEALDD-S connection.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.2 Procedure
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.2.1 SEALDD enabled signalling transmission connection establishment procedure
|
Figure 9.2.2.1-1 illustrate the procedure for signalling transmission connection establishment.
Pre-condition:
- The VAL server has discovered and selected the SEALDD server by CAPIF functions.
Figure 9.2.2.1-1: SEALDD signalling transmission connection establishment procedure
1. The VAL server decides to use SEALDD service for application signalling transfer and allocates as SEALDD-S connection information for receiving the application signalling traffic from SEALDD server. The VAL server sends Sdd_RegularTransmission request to the SEALDD server. The service request includes the VAL server ID, VAL service ID to identify the VAL application signalling traffic, the SEALDD-S connection information of the VAL server side.
2. Upon receiving the request, the SEALDD server performs an authorization check. If authorization is successful, the SEALDD server allocates a specific address used for SEALDD signalling traffic transfer with the incoming SEALDD client(s) for the VAL server and responds with a SEALDD service response.
NOTE 1: If the SEALDD server does not allocate SEALDD-S connection information in this step, then VAL server uses wildcard endpoint as SEALDD-S connection information for SEALDD-S reference point to receive all the application signalling traffic.
3. The VAL client sends a SEALDD service request to SEALDD client. The service request also indicates to establish application signalling transmission connection. The VAL client receives a SEALDD service response to the SEALDD client. The response indicates that whether the SEALDD service request is successful or not.
4. The VAL/SEALDD client discovers and selects the proper SEALDD server for the VAL application, as described in clause 9.4.3. After this step, the VAL server is discovered and selected along with the associated SEALDD server, and the SEALDD client obtains the SEALDD server's address.
5. The SEALDD client allocates SEALDD-UU flow ID(s) mapping to application signalling traffic for application signalling transmission. The SEALDD client sends Sdd_RegularTransmissionConnection_Establish request to SEALDD server with the SEALDD client ID, the SEALDD-UU flow ID(s), VAL server ID, VAL service ID and the SEALDD traffic descriptor of the SEALDD client side (the SEALDD-S connection information of the SEALDD client for receiving the downlink SEALDD-UU signalling traffic). The request message also contains the selected VAL server endpoint information. The SEALDD server retrieves the location information of the VAL UE or SEALDD client from SEAL LM services defined in 3GPP TS 23.434 [4] clause 9.3.12 and verifies with the Geofence policy configured by the VAL server to allow or restrict the signalling connection establishment. If the location information is allowed as per the configured geofence policy then the SEALDD server allows the signalling connection establishment, otherwise SEALDD server returns failed result e.g. performs connection reject.
NOTE 2: The SEALDD-UU flow ID is used by the SEALDD client and SEALDD server to identify different application signalling traffic, and it is mapped to the VAL service ID.
6. The SEALDD server responds to the SEALDD client with the SEALDD traffic descriptor of SEALDD server side (e.g. SEALDD-S connection information, transport layer protocol) mapping to the application traffic.
7. The SEALDD server stores the SEALDD client ID, SEALDD-UU flow ID(s) to identify the SEALDD-UU signalling traffic and establishes SEALDD-S connection with VAL server for the VAL client to transmit application signalling traffic mapping to the SEALDD traffic. SEALDD server may use different SEALDD connection information to establish the SEALDD-S signalling transmission connection for application signalling transfer towards the VAL server for different SEALDD client and SEALDD-UU flow. Then each VAL client will have different SEALDD-S signalling transmission connection at the SEALDD server side.
8. The SEALDD client uses the SEALDD traffic descriptor of SEALDD server side for SEALDD signalling connection establishment.
NOTE 3: If the UE's address for SEALDD traffic transfer is different from the address used in the control plane interaction (step 5 and 6), another SEALDD interaction procedure may be triggered to notify the SEALDD server about the SEALDD-S connection information used by the SEALDD client for SEALDD traffic transfer. Or the SEALDD server reuses the SEALDD client's address used in step 5 for SEALDD traffic transfer.
After this step, the SEALDD client and SEALDD server both get the whole SEALDD traffic descriptor (including the SEALDD client's address and SEALDD server's address for the SEALDD traffic transmission). The SEALDD client gets the mapping information (i.e. SEALDD-UU flow ID for the application signalling transfer). The SEALDD server gets the mapping information between the SEALDD-UU flow ID, the signalling transmission Session ID and the SEALDD-S connection. The SEALDD client and SEALDD server store the mapping between the application traffic and SEALDD traffic.
Upon receiving application signalling traffic from VAL client, the SEALDD client maps it into SEALDD traffic with SEALDD traffic descriptor as negotiated with SEALDD server. The SEALDD server maps the SEALDD traffic to the application traffic according to the stored SEALDD traffic descriptor, SEALDD client ID, SEALDD-UU flow ID. The SEALDD server sends the received application traffic to VAL server via the connection established in step 7 according to the mapping relationship between the SEALDD-S connection and the SEALDD traffic.
For the downlink application signalling traffic in response to the uplink application signalling, the VAL server responds to the source address (SEALDD-S address of the SEALDD server side) of the uplink signalling traffic. Upon receiving the downlink application signalling traffic from the SEALDD-S connection, the SEALDD server maps the downlink application signalling traffic to the related SEALDD client ID and SEALDD-UU flow ID and send the mapped SEALDD traffic to the SEALDD client. The rest of the downlink application traffic transfer is processed similarly with the uplink traffic.
After the connection establishment, the VAL server communicates with VAL client for application layer signalling traffic transfer via the established SEALDD connection.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.2.2 SEALDD enabled regular data transmission connection establishment procedure
|
Figure 9.2.2.2-1 illustrate the procedure for establishing regular SEALDD data transmission connection.
Pre-condition:
- The VAL server has discovered and selected the SEALDD server by CAPIF functions.
Figure 9.2.2.2-1: SEALDD enabled regular data transmission connection establishment procedure
1. The VAL server decides to use SEALDD service for application data traffic transfer and allocates address as SEALDD-S connection information for receiving the traffic packets from SEALDD server. The VAL server sends Sdd_RegularTransmission request to the SEALDD server discovered by CAPIF. The request includes UE ID/address, VAL server ID, VAL service ID, SEALDD-S connection information of the VAL server side, and optionally, the QoS information for the application traffic, e.g. QoS requirements.
2. Upon receiving the request, the SEALDD server performs an authorization check. If authorization is successful, SEALDD server allocates SEALDD-S connection information of the SEALDD server to receive the application data traffic from the VAL server for application data transfer as SEALDD-S connection information of the SEALDD server side. The SEALDD server allocates a specific SEALDD-S connection information used for SEALDD traffic transfer with the specific UE for the VAL server and responds with a SEALDD service response (including SEALDD-S connection information of the SEALDD server side). The VAL server and SEALDD server use SEALDD-S connection information to establish the data transmission connection between VAL server and SEALDD server for application data transfer.
The SEALDD server may send the AF request to provide the required QoS information to 5GC via N33/N5, as defined in clause 5.2.6.9 and in clause 5.2.5.3 of 3GPP TS 23.502 [6]. The AF request includes the application traffic descriptor containing the SEALDD-S connection information allocated by SEALDD server, and the QoS information for application traffic. The QoS information may be determined by SEALDD server according to VAL service ID for different service type of application traffic if the QoS information is not provided by VAL server. The SEALDD server relies on the northbound Policy Authorization Service API exposed by the PCF as specified in 3GPP TS 23.502 [6] and 3GPP TS 23.503 [7], if the SEALDD server is connected to the PCF via the N5 reference point, or the northbound AF Session with QoS Service APIs and/or the PFD Management northbound APIs exposed by the NEF as specified in 3GPP TS 23.502 [6] and 3GPP TS 23.503 [7], if the SEALDD server is connected to the PCF via NEF. SEALDD may also rely upon the EES Session with QoS API as specified in 3GPP TS 23.558 [10] and/or the NRM QoS functionality as described in 3GPP TS 23.434 [4].
NOTE 1: The SEALDD-S connection information of the SEALDD server side is optional to respond to the VAL server, if the SEALDD server uses the downlink pull mode to obtain the data/content from the address provided by the VAL server in step 1, and uses the uplink push mode to send the data/content to the address provided by VAL server.
3. Data transmission session information is provisioned to the VAL client by the VAL server via application signalling. The data transmission session information may contain the SEALDD address information which is discovered and selected by VAL server.
NOTE 2: The SEALDD address information for VAL server and SEALDD client is the same.
NOTE 3: The application signalling may be transmitted via direct application layer connection or via the SEALDD layer.
4. The VAL client sends a SEALDD service request to SEALDD client. The VAL client receives a SEALDD service response to the SEALDD client. If the data transmission session information contains the SEALDD address information, then the VAL client sends the selected SEALDD address information to SEALDD client in service request message. The response indicates that whether the SEALDD service request is successful or not.
5. If the data transmission session information does not contain the SEALDD address information, then the VAL/SEALDD client discover and select the proper SEALDD server for the VAL application, as described in clause 9.4.3. After this step, the VAL server is discovered and selected along with the associated SEALDD server, the SEALDD client obtains the SEALDD server's address.
6. The SEALDD client allocates SEALDD-UU flow ID(s) mapping to the identifiers of the application traffic. The SEALDD client sends Sdd_RegularTransmissionConnection_Establish request to SEALDD server with the SEALDD client ID, the SEALDD-UU flow ID(s), the SEALDD traffic descriptor of the SEALDD client side (SEALDD-S connection information of the SEALDD client for receiving the downlink SEALDD traffic), VAL server ID, VAL service ID. The request message also contains the selected VAL server endpoint information and UE ID. The SEALDD server retrieves the location information of the VAL UE or SEALDD client from SEAL LM services defined in 3GPP TS 23.434[4] clause 9.3.12 and verifies with the Geofence policy configured by the VAL server to allow or restrict the data connection establishment. If the location information is allowed as per the configured geofence policy then the SEALDD server allows the data connection establishment, otherwise SEALDD server returns a failed result e.g. performs connection reject.
NOTE 4: The SEALDD server can use or update the association between SEALDD-UU connection and SEALDD-S connection that associated with UE ID, VAL service ID, VAL server endpoint, which is used to correlate the SEALDD traffic and the VAL application traffic.
NOTE 5: The SEALDD-UU flow ID is used by the SEALDD client and SEALDD server to identify different VAL application traffic of the same SEALDD client. The SEALDD-UU flow ID may be same with the identifiers of the application traffic or new simplified IDs allocated by SEALDD.
7. The SEALDD server responds to the SEALDD client with the SEALDD traffic descriptor of SEALDD server side (e.g. address allocated in step 2, transport layer protocol) mapping to the application data traffic.
8. If the connection between VAL server and SEALDD server is not established in step 2, the SEALDD server establishes connection with VAL server for the VAL client to transmit application data traffic mapping to the SEALDD traffic according to the SEALDD-S information negotiated in step 1-2.
9. The SEALDD client uses the SEALDD traffic descriptor of SEALDD server side for SEALDD connection establishment.
After this step, the SEALDD client and SEALDD server both get the whole SEALDD traffic descriptor (including the UE's address and SEALDD server's address for the SEALDD traffic transmission).
After the negotiation and establishment of the connections, the SEALDD client gets the mapping information between application data traffic and SEALDD-UU flow ID. The SEALDD server gets the mapping information between the SEALDD-UU flow ID and the SEALDD-S connection. Upon receiving application data traffic from VAL client, the SEALDD maps it to SEALDD traffic with SEALDD traffic descriptors as negotiated with SEALDD server in step 6 and step 7. The SEALDD traffic is sent to the SEALDD server. The SEALDD server maps the SEALDD traffic to the application traffic according to the stored SEALDD traffic descriptor, SEALDD client ID and SEALDD-UU flow ID. The SEALDD server sends the recovered application traffic to the address provided by VAL server in step 1, via the connection established in step 2 or 8 according to the mapping information. The downlink application traffic sent from VAL server to VAL client is processed similarly.
The SEALDD server receives any UE location change notification using SEAL LM services defined in 3GPP TS 23.434 [4] clause 9.3.12, then the SEALDD server performs the data delivery in alignment with the geofence policy. If the UE is in the forbidden location or not allowed for the given VAL service to send/receive data as per the Geofence policy, then the SEALDD server performs action like releases the connection and informs the VAL server that UE is not reachable because in a forbidden location using connection event status procedure. If UE enters the allowed location area then the SEALDD server initiates the connection establishment using the procedure defined in clause 9.2.2.3.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.2.3 SEALDD enabled regular data transmission connection establishment based on policy
|
The SEALDD servers has Data Delivery (DD) policy being provisioned. Before the application communication between VAL client and VAL server starts, the DD policy is enforced by the SEALDD server to establish the SEALDD connection.
Pre-conditions:
1. The SEALDD server has DD policies available.
Figure 9.2.2.3-1: Policy enforced by SEALDD server for connectivity
1. The VAL server subscribes to SEALDD event exposure for connection status using the procedure defined in clause 9.2.2.6.
NOTE 1: The VAL server can update/delete an existing subscription at the SEALDD Server when required.
2. When the time for data transmission is about to start, the SEALDD server enforces the policy to trigger regular data transmission connection establishment. If spatial condition for UE is provided, the SEALDD server also ensures the UE’s location requirement is satisfied when establishing regular data transmission connection (e.g. by using NEF service for monitoring UE location or SEAL location service for UE entering area of interest).
3. If there is a special routing requirement for SEALDD user plane traffic (e.g. running on a specific slice and DNN), the SEALDD server interacts with 3GPP CN to provision service specific parameters with NEF as described in 3GPP TS 23.502 [6], clause 4.15.6.10 and clause 4.15.6.7.
If there are QoS requirements in the DD policy, the SEALDD server also applies QoS to ensure the quality for SEALDD traffic by utilizing NEF/PCF/NRM/EES service for QoS adjustment. Specifically, the SEALDD server relies on the northbound Policy Authorization Service API exposed by the PCF as specified in 3GPP TS 23.502 [6] and 3GPP TS 23.503 [7], if the SEALDD server is connected to the PCF via the N5 reference point, or the northbound AF Session with QoS Service API and/or the PFD Management northbound APIs exposed by the NEF as specified in 3GPP TS 23.502 [6] and 3GPP TS 23.503 [7], if the SEALDD server is connected to the PCF via NEF. SEALDD may also rely upon the EES Session with QoS API as specified in 3GPP TS 23.558 [10] and/or the NRM QoS functionality as described in 3GPP TS 23.434 [4].
If the DD policy specifies failure detection report, the SEALDD server may subscribe to CN analytics (e.g. DN performance analytics) from NEF/NWDAF and further notify data delivery status of application traffic to VAL client (via SEALDD client) and VAL server based on analytics result.
4. The SEALDD server allocates an IP address and port for sending and receiving packet over SEALDD-S reference point, then SEALDD server sends SEALDD connection establishment notification (i.e. SEALDD connection status notification with establishment event, as described in Table 9.2.3.9-1) to the VAL server with VAL service ID, the address.
5-6. The SEALDD server allocates a SEALDD-S connection information for sending and receiving packet over SEALDD-UU reference point, then SEALDD server sends data transmission connection establishment initiated by SEALDD server request to the SEALDD client with SEALDD-UU flow ID, VAL service ID, the address. The request is responded by the SEALDD client. UE IP address may be included by the SEALDD client in the response or sent in a separate update message by SEALDD client if a different UE IP address is to be used in SEALDD connection user plane.
NOTE 2: Step 4 and step 5 can be done in parallel.
NOTE 3: SEALDD server can know the UE address (e.g. via SEALDD connection establishment request initiated by SEALDD client, but rejected by SEALDD server due to policy condition not met) before step 5, if not, step 5 can be sent via application triggering.
7. The SEALDD client further notifies the VAL client about the SEALDD connection being established.
Upon receiving application traffic from VAL client (not shown in the figure), the SEALDD client sends it to SEALDD server in SEALDD traffic. The SEALDD server identifies application traffic based on the VAL service ID and further sends the application traffic to VAL server. The downlink application traffic sent from VAL server to VAL client is processed similarly.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.2.4 SEALDD enabled regular data transmission connection deletion based on policy
|
Figure 9.2.2.4-1: SEALDD enabled regular data transmission connection deletion
1. SEALDD server decides to remove the connection. Such a decision may be based on decision in SEALDD server in the following cases:
a. DD policy removal or validity time expiration;
b. DD policy specified end time reached for SEALDD communication;
c. UE is leaving the area of interest (if spatial condition for UE is provided in the policy).
2-3. The SEALDD server notifies SEALDD connection deletion (i.e. SEALDD connection status notification with release event, as described in Table 9.2.3.9-1) to the VAL server. The VAL server removes the connection information. The application traffic is stopped on both sides.
4-5. The SEALDD server requests regular data transmission connection deletion to the SEALDD client. The request is responded by the SEALDD client. The application traffic is stopped on both sides.
NOTE 1: Step 2 and step 4 can be done in parallel.
NOTE 2: Step 5 can be sent via PDU session (if exist) or via application triggering (if no PDU session exists).
6. The SEALDD client further notifies the VAL client about the SEALDD connection being removed. The application traffic is stopped on both sides.
7. If a special routing requirement for SEALDD user plane traffic was provided to 3GPP CN, the SEALDD server interacts with 3GPP CN to remove service specific parameters with NEF as described in 3GPP TS 23.502 [6], clause 4.15.6.7.
8. The SEALDD server removes the SEALDD connection (i.e. deletes the SEALDD connection context).
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.2.5 SEALDD client initiated connection release
|
Figure 9.2.2.5-1 illustrates the procedure for SEALDD client initiated connection release procedure from the SEALDD client to the SEALDD server.
Figure 9.2.2.5-1: SEALDD client initiated connection release
1. The SEALDD client sends the SEALDD connection release request to the SEALDD server to release the established connection.
2. The SEALDD server releases the SEALDD-UU data transmission connection (which was established by SEALDD client or SEALDD server) and sends the response in the SEALDD connection release response message. Upon receiving the acknowledgement, the SEALDD client releases the connection resources.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.2.6 SEALDD connection status procedure
|
Figure 9.2.2.6-1 illustrates the procedure for SEALDD connection status from the VAL server to the SEALDD server.
Figure 9.2.2.6-1: SEALDD connection status procedure
1. The VAL server sends the SEALDD connection status subscribe request to the SEALDD server. The request includes the identifiers of the application traffic (e.g. VAL service ID, VAL server ID), VAL UE identity, and the SEALDD client connection status check periodicity under "SEALDD client connection status" event as described in Table 9.2.3.7-1. The VAL server also includes the Non-3GPP access measurement information(like list of WLAN SSIDs, location-based measurement) in the request message.
2. The SEALDD server subscribes to the NEF UE reachability, Application Detection and Loss of connectivity events using the procedure defined in clause 4.15.3.2.3b 3GPP TS 23.502 [6]. It also uses the NRM Event monitoring procedure defined in clause 14.3.6.2.2 3GPP TS 23.434 [4].
3. The SEALDD server also sends a SEALDD client connection status reporting configuration request to the SEALDD client. The request message consists of SEALDD-UU flow ID and method of reporting, which includes the reporting interval when the mode of reporting is periodic, and optionally the SEALDD client connection status reporting priority. The SEALDD-UU flow ID identifies the application traffic flow for which the reporting notification is configured. The SEALDD client monitors the application using SEALDD-UU flow ID. The method of reporting is defined as periodic or event triggered. The periodic reporting method uses the reporting interval to send the notification. The event triggered reporting method sends the notification if the current connection status is different from the previous connection status or if the application state changes (like crash, close, stop).
The SEALDD server includes the Non-3GPP access measurement in the SEALDD client connection status reporting configuration request. The SEALDD server uses the Non-3GPP access measurement information received in step 1 or Non-3GPP access measurement information configured in the SEALDD server as policy by VAL server or configured as internal policy.
4. The SEALDD client configures the reporting configuration and provides the response to the SEALDD server. If the Non-3GPP access measurement includes list of WLAN SSIDs, then the SEALDD client performs the signal strength measurement for the requested WLAN SSID. If the request contains location-based measurement, then the SEALDD client measures the signal strength of nearby WLAN SSIDs based on its location. The response also includes the list of WLAN SSIDs and their signal strength measurements.
5. The SEALDD server sends the connection status subscription response to the VAL server.
6a-6b. The SEALDD server receives the notification for the UE connection status from the subscribed NEF, NRM. It may also receive a notification from the SEALDD client regarding the connection status. If the UE is in power saving mode, then the SEALDD client sends the connection status reporting notification with the status as sleeping to the SEALDD server and suspends the connection status periodic reporting.
7. Based on the NRM, NEF event subscription response and SEALDD client connection status reporting notification message with "SEALDD client connection status" event as described in Table 9.2.3.9-1, the SEALDD server processes the responses and sends the SEALDD client connection status of unreachable or sleeping status notification to the VAL server.
NOTE: If the VAL server is not aware of the connection status like VAL UE reachability and may continue sending the application traffic, results in packet losses and degradation of the QoS of the VAL UEs.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.2.7 Client initiated regular data transmission path establishment procedure
|
Figure 9.2.2.7-1 illustrates the procedure for client initiated regular data transmission establishment for data transfer per application layer transaction.
Pre-conditions:
1. The SEALDD client is authorized to request regular data transmission services on behalf of the VAL client when the VAL client initiates transmission service.
2. The VAL client has discovered the VAL server.
Figure 9.2.2.7-1: Client initiated regular data transmission path establishment
1a. A VAL client may discover and select a proper SEALDD server for the VAL application and VAL server as specified in clause 9.4.3.2.3.
1b. A VAL client determines to use SEALDD service to ensure that the data transmission quality for the application traffic is met and makes a service request to the SEALDD client.
2. Upon receiving the request, the SEALDD client decides to establish regular data transmission path according to the QoS requirements. The SEALDD client discovers and selects the proper SEALDD server for the VAL application and VAL server as specified in clause 9.4.3.2.3, if the SEALDD server and VAL server information are not received.
3-4. Same as step 6-7 of clause 9.2.2.2.
5. The SEALDD client responds with a SEALDD service response.
NOTE: Details of the VAL client service request in step 1 and the corresponding response in step 5 are out of scope of the current specification.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.3 Information flows
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.3.1 SEALDD enabled regular transmission request
|
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.
Table 9.2.3.1-1: SEALDD enabled Regular transmission request
Information element
Status
Description
VAL server ID
M
Identity of the VAL server
VAL service ID
O
Identity of the VAL service
Identity
O
Identifier of specific UE or VAL user
SEALDD-S connection information
M
Address information (e.g., IP address and/or port, URL) of the VAL server to receive the traffic from the SEALDD server
QoS information
O
QoS information provided by VAL server
VAL server’s total bandwidth limit
O
(See NOTE)
The total bandwidth limit of VAL server, including UL/DL
VAL users’ bandwidth limit
O
(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.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.3.2 SEALDD enabled regular transmission response
|
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.
Table 9.2.3.2-1: SEALDD enabled regular transmission response
Information element
Status
Description
Result
M
Success or failure.
SEALDD-S information connection information
O
Address information (e.g., IP address and/or port, URL) of the SEALDD server to receive the packets from the VAL server for traffic transfer
Cause
O
See NOTE
Indicates the reason for the failure, e.g. SEALDD policy mismatch.
NOTE: The IE is only present if the Result is failure.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.3.3 SEALDD regular transmission connection establishment request
|
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.
Table 9.2.3.3-1: SEALDD regular transmission connection establishment request
Information element
Status
Description
Requestor ID
M
Identity of the requestor (SEALDD client or SEALDD server).
SEALDD-UU flow ID
M
(See NOTE 1)
Identity of the SEALDD-UU flow.
VAL server ID
O
Identity of the VAL server, applicable for SEALDD client side initiated request.
VAL service ID
O
Identity of the VAL service
Selected VAL server endpoint
M
Endpoint of the selected VAL server
SEALDD traffic descriptor
O
SEALDD 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.
Identity
O
The VAL user ID of the VAL user or VAL UE ID.
SEALDD communication lifetime
O
Identifies the DD communication lifetime, applicable for SEALDD server side initiated request.
Capability for BAT and periodicity adaptation
O
(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 info
O
(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 capability
O
(See NOTE 3)
Identifies the L4S feedback capability (i.e. ECN identification, L4S feedback) for client side initiated request
VAL UE client access capability
O
Indicates the access technologies supported by VAL UE client. E.g.,3GPP, Non-3GPP(WLAN)
XR Application device capability information
O
(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.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.3.4 SEALDD regular transmission connection establishment response
|
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.
Table 9.2.3.4-1: SEALDD regular transmission connection establishment response
Information element
Status
Description
Result
M
Indicates the success or failure of establishing the SEALDD connection.
SEALDD traffic descriptor
O
SEALDD 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 timer
O
(See NOTE 1)
The pending timer to trigger the re-connection from SEALDD client when bandwidth limit check is failed.
Suggested traffic transmission bandwidth
O
(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.
Cause
O
(See NOTE 2)
Indicates the reason for the failure, e.g. SEALDD policy mismatch.
Capability for BAT and periodicity adaptation
O
(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 info
O
(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.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.3.5 SEALDD regular data transmission connection release request
|
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.
Table 9.2.3.5-1: SEALDD regular data transmission connection release request
Information element
Status
Description
Requestor ID
M
Identity of the requestor (SEALDD client or SEALDD server).
SEALDD-UU flow ID
M
Identifies the SEALDD-UU flow.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.3.6 SEALDD regular data transmission connection release response
|
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.
Table 9.2.3.6-1: SEALDD regular data transmission connection release response
Information element
Status
Description
Result
M
Result of the operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.3.7 SEALDD connection status subscription request
|
Table 9.2.3.7-1 describes the information flow from the VAL server to SEALDD server to subscribe to SEALDD connection status information.
Table 9.2.3.7-1: SEALDD connection status subscription request
Information element
Status
Description
VAL server ID
M
Identity of the VAL server
Event ID list
M
Identifies a list of events such as establishment, release, congestion report, SEALDD client connection status.
VAL service ID
O
Identity of the VAL service
Identity
O
Identifier of VAL UE or VAL user.
SEALDD-S connection information
M
Address information (e.g., IP address and/or port, URL) to send/receive the traffic to/from the SEALDD server.
Immediate reporting flag
O
Indicates the immediate reporting of connection status notification
SEALDD client connection status check periodicity
O
Indicates the frequency to perform SEALDD client connection status check
Non-3GPP access measurement information
O
Indicates the Non-3GPP access measurement information like list of WLAN SSIDs, location-based measurement
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.3.8 SEALDD connection status subscription response
|
Table 9.2.3.8-1 describes the information flow from the SEALDD server to VAL server for responding SEALDD connection status subscription request.
Table 9.2.3.8-1: SEALDD connection status subscription response
Information element
Status
Description
Result
M
Success or failure.
Subscription ID
O
(NOTE)
Subscription identifier corresponding to the subscription.
Expiration time
O
(NOTE)
Indicates the expiration time of the subscription.
NOTE: These IEs shall be present when the result is success.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.3.9 SEALDD connection status notification
|
Table 9.2.3.9-1 describes the information flow from the SEALDD server to the VAL server to notify SEALDD connection status.
Table 9.2.3.9-1: SEALDD connection status notification
Information element
Status
Description
Event ID
M
Identifies event such as establishment, release, congestion report, SEALDD client connection status.
Identity
M
Identifier of VAL UE or VAL user.
VAL service ID
M
Identity of the VAL service.
SEALDD connection establishment data
O
(see NOTE 1)
Data related to SEALDD connection establishment.
> SEALDD-S connection information
M
Address 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 lifetime
O
Identifies the DD communication lifetime.
Congestion level
O
(See NOTE 2)
The congestion level of the VAL service
SEALDD client connection status
O
(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.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.3.10 SEALDD client connection status reporting configuration request
|
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.
Table 9.2.3.10-1: SEALDD client connection status reporting configuration request
Information element
Status
Description
SEALDD-UU Flow ID
M
Indicates the SEALDD-UU flow ID of the application for which the reporting is required.
Mode of reporting
O
Indicates the mode of reporting: periodic and/or event triggered. If omitted, the default value is event triggered.
> Reporting interval
O
(See NOTE)
Indicates the reporting interval to report the notification.
SEALDD client connection status reporting priority
O
Indicates the priority of the requested SEALDD-UU flow ID for the reporting of the SEALDD client connection status.
Non-3GPP access measurement information
O
Indicates 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., RSSI) values for measurement.
NOTE: This IE shall be present if the mode of reporting is periodic
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.3.11 SEALDD client connection status reporting configuration response
|
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.
Table 9.2.3.11-1: SEALDD client connection status reporting configuration response
Information element
Status
Description
Result
M
Success or failure.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.3.12 SEALDD client connection status reporting notification
|
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.
Table 9.2.3.12-1: SEALDD client connection status reporting notification
Information element
Status
Description
SEALDD client connection status
M
Indicates the status of VAL UEs/users like reachable, unreachable, or sleeping
Non-3GPP access measurement information reporting
O
Indicates the Non-3GPP access measurement information report.
> Measured non-3GPP access
O
List of measured non-3GPP access (e.g., WLAN SSID(s)/BSSID(s) or location information).
>> Signal strength value(s)
M
List of signal strength values (e.g., RSSI) for the measured non-3GPP access.
SEALDD data transmission connection access usage
M
Indicates which access (3GPP or Non-3GPP) is used for the SEALDD-UU data transmission
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.3.13 SEALDD connection status subscription update request
|
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.
Table 9.2.3.13-1: SEALDD connection status subscription update request
Information element
Status
Description
Subscription ID
M
Subscription identifier corresponding to the subscription to be updated
Event ID list
O
Identifies a list of events such as establishment, release, congestion report, SEALDD client connection status.
Immediate reporting flag
O
Indicates the immediate reporting of connection status notification
SEALDD client connection status check periodicity
O
Indicates the frequency to perform SEALDD client connection status check
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.3.14 SEALDD connection status subscription update response
|
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.
Table 9.2.3.14-1: SEALDD connection status subscription update response
Information element
Status
Description
Result
M
Success or failure.
Expiration time
O
(NOTE)
Indicates the expiration time of the subscription.
NOTE: This IE shall be present when the result is success.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.3.15 SEALDD connection status unsubscribe request
|
Table 9.2.3.15-1 describes the information flow from the VAL server to SEALDD server to unsubscribe the SEALDD connection status information.
Table 9.2.3.15-1: SEALDD connection status unsubscribe request
Information element
Status
Description
Subscription ID
M
Subscription identifier corresponding to the subscription to be updated
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.3.16 SEALDD connection status unsubscribe response
|
Table 9.2.3.16-1 describes the information flow from the SEALDD server to VAL server for responding SEALDD connection status unsubscribe request.
Table 9.2.3.16-1: SEALDD connection status unsubscribe response
Information element
Status
Description
Result
M
Success or failure.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.3.17 SEALDD data transmission connection establishment initiated by SEALDD server request
|
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.
Table 9.2.3.17-1: SEALDD data transmission connection establishment initiated by SEALDD server request
Information element
Status
Description
Requestor ID
M
Identity of the requestor (SEALDD client or SEALDD server).
SEALDD-UU flow ID
M
(See NOTE 1)
Identity of the SEALDD-UU flow.
VAL service ID
O
Identity of the VAL service
Selected VAL server endpoint
M
Endpoint of the selected VAL server
SEALDD traffic descriptor
O
SEALDD traffic descriptor (e.g. address, port, URL, transport layer protocol) of the SEALDD server used to establish SEALDD connection.
Identity
O
The VAL user ID of the VAL user or VAL UE ID.
SEALDD communication lifetime
O
Identifies 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.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.3.18 SEALDD data transmission connection establishment initiated by SEALDD server response
|
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.
Table 9.2.3.18-1: SEALDD data transmission connection establishment initiated by SEALDD server response
Information element
Status
Description
Result
M
Indicates the success or failure of establishing the SEALDD connection.
SEALDD traffic descriptor
O
SEALDD 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 bandwidth
O
(See NOTE 1)
The suggested traffic transmission bandwidth used by SEALDD client to perform bandwidth control for VAL users, including UL/DL.
Cause
O
(See NOTE 2)
Indicates the reason for the failure, e.g. SEALDD policy mismatch.
Capability for BAT and periodicity adaptation
O
(See NOTE 3)
Indicates BAT and periodicity adaptation capability for SEALDD client.
Capability for BAT and periodicity adaptation
O
(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.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.4 APIs
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.4.1 General
|
Table 9.2.4.1-1 illustrates the APIs exposed by SEALDD server for regular connection establishment.
Table 9.2.4.1-1: List of SEALDD server APIs for data distribution
API Name
API Operations
Operation Semantics
Consumer(s)
Sdd_RegularTransmission
Request
Request/Response
VAL server
Sdd_RegularTransmissionConnection
Establish
Request/Response
SEALDD client, SEALDD server
Release
Request/Response
SEALDD client, SEALDD server
Sdd_ConnectionStatusEvent
Subscribe
Subscribe/Notify
VAL server
Notify
Subscribe/Notify
VAL server
Update
Subscribe/Notify
VAL server
Unsubscribe
Subscribe/Notify
VAL server
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.4.2 Sdd_RegularTransmission operation
|
API operation name: Sdd_RegularDataTransmission_Request
Description: The consumer requests for one time for SEALDD enabled regular data transmission.
Inputs: See clause 9.2.3.1.
Outputs: See clause 9.2.3.2.
See clause 9.2.2.1 and 9.2.2.2 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.4.3 Sdd_RegularTransmissionConnection_Establish operation
|
API operation name: Sdd_RegularTransmissionConnection_Establish
Description: The consumer requests for one time for SEALDD enabled regular data connection establishment.
Inputs: See clause 9.2.3.3.
Outputs: See clause 9.2.3.4.
See clause 9.2.2.1 and 9.2.2.2 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.4.4 Sdd_ConnectionStatusEvent_Subscribe operation
|
API operation name: Subscribe
Description: The consumer requests to subscribe to SEALDD connection status event.
Inputs: See clause 9.2.3.7.
Outputs: See clause 9.2.3.8.
See clause 9.2.2.6 and clause 9.3.2.3 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.4.5 Sdd_ConnectionStatusEvent_Notify operation
|
API operation name: Notify
Description: The consumer is notified with SEALDD connection status.
Inputs: See clause 9.2.3.9.
Outputs: None.
See clause 9.2.2.3, clause 9.2.2.4, clause 9.2.2.6, clause 9.3.2.3 and clause 9.3.2.4 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.4.6 Sdd_RegularTransmissionConnection_Release operation
|
API operation name: Sdd_RegularTransmissionConnection_Release
Description: The consumer requests to release the SEALDD connection resources.
Inputs: See clause 9.2.3.5.
Outputs: See clause 9.2.3.6.
See clause 9.2.2.5 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.4.7 Sdd_ConnectionStatusEvent_Subscribe_Update operation
|
API operation name: Subscribe update
Description: The consumer requests to update the subscription of SEALDD connection status event.
Inputs: See clause 9.2.3.13.
Outputs: See clause 9.2.3.14.
See clause 9.2.2.3 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.2.4.8 Sdd_ConnectionStatusEvent_Unsubscribe operation
|
API operation name: Unsubscribe
Description: The consumer requests to unsubscribe the subscription of SEALDD connection status event.
Inputs: See clause 9.2.3.15.
Outputs: See clause 9.2.3.16.
See clause 9.2.2.3 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.3 SEALDD enabled E2E redundant transmission
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.3.1 General
|
The following clauses specify procedures, information flow and APIs for SEALDD enabled E2E redundant transmission.
SEALDD client and SEALDD server transfer SEALDD traffic via two redundant PDU sessions as specified in clause 5.33.2.1 of 3GPP TS 23.501 [5].
Figure 9.3.1-1 shows the data traffic flow of E2E redundant transmission. For uplink data delivery, VAL client sends application traffic to SEALDD client, the SEALDD client duplicates the application packets and maps them into two SEALDD traffic. Then the two SEALDD traffic are transferred to SEALDD server via the two redundant PDU sessions shown in figure 9.3.1-1. The SEALDD server eliminates the redundant packets and recovers the application traffic. The recovered application traffic is transferred to VAL server by the SEALDD server. For downlink data delivery, VAL server sends application traffic to SEALDD server, the SEALDD server duplicates the application packets and maps them into two SEALDD traffic. The two SEALDD traffic are transferred to UE via the two redundant PDU sessions. The SEALDD client eliminates the redundant SEALDD packets and recovers the application traffic, then sends the application traffic to the VAL client.
Figure 9.3.1-1: E2E redundant transmission traffic flow
Figure 9.3.1-2 shows the data traffic flow of E2E redundant transmission for multiple VAL servers. In this scenario, SEALDD server and SEALDD client use different SEALDD-UU flow IDs and SEALDD traffic descriptors to identify SEALDD traffic for different VAL servers.
Figure 9.3.1-2: E2E redundant transmission traffic flow for multiple VAL servers
For outbound data delivery, VAL application traffic is sent to SEALDD enabler layer, the SEALDD enabler duplicates the application packets and maps them into two SEALDD traffic (with the different -SEALDD-UU Flow ID with the same SEALDD connection). Then according to the SEALDD traffic descriptors of the SEALDD-UU flow, the SEALDD traffic is sent out with different destination addresses or ports and different source addresses or ports. For inbound data delivery, two SEALDD traffic (with different source addresses or ports and different destination addresses or ports) are received. According to the SEALDD traffic descriptors, SEALDD enabler decides they belong to the same SEALDD-S Flow for the same service. Then after packet elimination and reordering, the two SEALDD traffic is aggregated to one VAL application traffic.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.3.2 Procedure
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.3.2.1 E2E redundant transmission path establishment procedure
|
Figure 9.3.2.1-1 illustrates the procedure for redundant transmission establishment. This procedure may be triggered by a VAL server for data transfer per application layer transaction.
Pre-conditions:
1. The VAL server has discovered and selected the SEALDD server by CAPIF functions as specified in clause 9.4.2.
Figure 9.3.2.1-1: E2E redundant transmission path establishment
1. The VAL server decides to use SEALDD service to help ensuring data transmission quality for application traffic transfer and send a Sdd_URLLCTransmission request to the SEALDD server discovered by CAPIF. The request includes UE ID, VAL server ID, VAL service ID, SEALDD-S Data transmission connection information of the VAL server side, and optionally, the QoS information for the application traffic, e.g. QoS requirements. The VAL server ID and VAL service ID are used to identify the VAL application traffic.
2. Upon receiving the request, the SEALDD server decides to establish redundant transmission path. The SEALDD server allocates two different SEALDD-S connection information for the two redundant transmission paths and sends an AF request to 5GS to create or update URSP rules as described in clause 4.15.6.10 of 3GPP TS 23.502 [6] for the UE(s) going to use the redundant transmission service. The AF request includes Identifiers of the UE(s) and application traffic descriptor containing the SEALDD-S connection information allocated by SEALDD server. The SEALDD server may send the AF request to provide the required QoS information to 5GC via N33/N5, as defined in clause 5.2.6.9 and in clause 5.2.5.3 of 3GPP TS 23.502 [6].
3. If the processing of the request was successful, SEALDD server allocates SEALDD-S connection information of the SEALDD server to receive the packets from the VAL server for application data transfer as SEALDD-S data transmission connection information of the SEALDD server side. The SEALDD server responds with a SEALDD service response (including SEALDD-S data transmission connection information of the SEALDD server side) and indicates to the VAL server that redundant transmission service should be activated. The VAL server and SEALDD server uses SEALDD-S data transmission connection information to establish the data transmission connection between VAL server and SEALDD server for application data transfer.
4. If the redundant transmission requirement is not preconfigured or notified to the VAL client, the VAL server may notify the VAL client(s) which is going to use the redundant transmission service through application layer message.
NOTE 1: The application signalling may be transmitted via direct application layer connection or via the SEALDD layer.
NOTE 2: The VAL client can be preconfigured that the VAL service should always be transmitted via redundant transmission. Or this application layer notification may be notified to the UE in another period before the VAL application traffic is really transmitted.
5. The VAL client sends a SEALDD service request to use E2E redundant transmission for the application traffic.
6. The SEALDD client discovers and selects the proper SEALDD server for the VAL application as specified in clause 9.4.3. After this step, the SEALDD client obtains the SEALDD server's address.
7. The SEALDD client allocates two different SEALDD-UU flow IDs mapping to the application traffic. The SEALDD client sends Sdd_URLLCTransmissionConnection_Establish request to SEALDD server. The request includes the SEALDD client ID, SEALDD-UU flow IDs, VAL server ID, VAL service ID for SEALDD server to identify the specific application traffic.
8. Upon receiving the request, the SEALDD server sends SEALDD traffic descriptor for redundant transmission of the SEALDD server side (i.e. SEALDD-S connection information for the redundant transmission paths allocated in step 2 and the transport protocol used for the SEALDD traffic) to SEALDD client.
9. The UE uses the SEALDD traffic descriptor of the SEALDD server and the created or updated URSP rules to trigger two redundant PDU Sessions establishment procedure via 5GS as specified in clause 5.33.2.1 of 3GPP TS 23.501 [5].
10. [Optional] The SEALDD client sends Sdd_URLLCTransmissionConnection_Update request to SEALDD server. The request includes the SEALDD client ID, the SEALDD-UU flow IDs, the SEALDD traffic descriptors for redundant transmission of the SEALDD client side (i.e. UE addresses of the two redundant PDU Sessions). The two redundant SEALDD traffic use the different SEALDD-UU flow IDs with different SEALDD-S connection information for identification.
11. [Optional] The SEALDD server sends a response to SEALDD client. After this step, the SEALDD client and SEALDD server both get the whole SEALDD traffic descriptors (including the UE's addresses and SEALDD server's addresses for the SEALDD traffic transmission). The SEALDD client and SEALDD server store the mapping between the application traffic and SEALDD traffic.
12. [Optional] If the connection between VAL server and SEALDD server is not established in step 3, the SEALDD server establishes connection with VAL server for the VAL client to transmit application traffic mapping to the redundant SEALDD traffic according to the SEALDD-S information negotiated in step 1-3
NOTE 3: Step 10 and Step 11 are optional. If the redundant PDU sessions are already established before step 7, the IP addresses of the UE may be notified to the SEALDD server in step 7. In other cases, after the establishment of the two redundant PDU sessions, the SEALDD client may communicate with SEALDD server through the redundant PDU sessions to let the SEALDD server know the UE's address(es) of the redundant PDU session to fulfil the traffic mapping or the SEALDD client and SEALDD server may use other mapping mechanisms, it is up to the transport protocol used by SEALDD client and SEALDD server for the SEALDD traffic.
13. The SEALDD client responds with a SEALDD service response.
After the negotiation and establishment of the connections, the SEALDD client gets the mapping information between the application traffic and SEALDD-UU flow IDs. The SEALDD server gets the mapping information between the SEALDD-UU flow IDs and the SEALDD-S connection. Upon receiving application traffic from VAL client, the SEALDD client duplicates the application packets and maps them into two SEALDD traffic flows with SEALDD traffic descriptors as negotiated with SEALDD server in step 8 and step 11. The two SEALDD traffic is sent through two redundant PDU sessions to the SEALDD server. The SEALDD server maps the two SEALDD traffic to the same application traffic according to the stored SEALDD traffic descriptors, SEALDD client ID and SEALDD-UU flow IDs. After packet elimination and reordering the SEALDD server sends the aggregated application traffic to VAL server via the connection established in step 3 and step 12 according to the mapping information. The downlink application traffic sent from VAL server to VAL client is processed similarly.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.3.2.2 Client initiated E2E redundant transmission path establishment procedure
|
Figure 9.3.2.2-1 illustrates the procedure for client initiated redundant transmission establishment for data transfer per application layer transaction.
Pre-conditions:
1. The SEALDD client is authorized to request redundant transmission services on behalf of the VAL client when the VAL client initiates redundant transmission service.
Figure 9.3.2.2-1: Client initiated E2E redundant transmission path establishment
1. A VAL client determines to use SEALDD service to ensure that the data transmission quality for the application traffic is met and makes a service request to the SEALDD client.
2. Upon receiving the request, the SEALDD client decides to establish redundant transmission path according to the QoS requirements. The SEALDD client discovers and selects the proper SEALDD server for the VAL application as specified in clause 9.4.3.
3. The SEALDD client sends a request to the SEALDD server to configure redundant transport for the application traffic. The SEALDD client allocates two different SEALDD-UU flow IDs mapping to the application traffic. The SEALDD client sends Sdd_URLLCTransmissionConnection_Establish request to SEALDD server. The request includes the SEALDD client ID, the SEALDD-UU flow IDs, the application ID, the UE ID/address, the VAL server ID/address, the QoS requirements, the UE location, and a request for redundant transport.
4. The SEALDD server allocates SEALDD-S connection information for the redundant transport paths and initiates the application guidance for URSP determination procedure with the 5G network to create or update URSP rules for the UE, as described in clause 4.15.6.10 of 3GPP TS 23.502 [6]. The request includes the UE ID and application traffic descriptor containing the addresses allocated by SEALDD server. The UE receives the new or updated URSP rules from the 5G core network.
5. The SEALDD server responds to the SEALDD client providing the configuration status. The response includes the SEALDD-S connection information for the redundant transmission paths allocated in step 4. The SEALDD client and SEALDD server store the mapping between the application traffic and SEALDD traffic.
6. The UE establishes redundant PDU sessions with the 5G network using the new or updated URSP rules as specified in clause 5.33.2.1 of 3GPP TS 23.501 [5].
7. [Optional] The SEALDD client sends Sdd_URLLCTransmissionConnection_Update request to SEALDD server. The request includes the SEALDD client ID, the SEALDD-UU flow IDs, the application traffic descriptors for redundant transmission of the SEALDD client side (i.e. UE addresses and ports of the two redundant PDU Sessions). The two redundant SEALDD traffic use the same SEALDD-UU flow IDs for identification.
8. [Optional] The SEALDD server establishes connection with VAL server for the VAL client to transmit application traffic mapping to the redundant SEALDD traffic. The SEALDD server sends a response to the SEALDD client. After this step, the SEALDD client and SEALDD server both get the application traffic descriptors (including the UE's addresses/ports and SEALDD server's addresses/ports for the SEALDD traffic transmission). The SEALDD client and SEALDD server store the mapping between the application traffic and SEALDD traffic.
9. The SEALDD client responds with a SEALDD service response.
NOTE: Details of the VAL client service request in step 1 and the corresponding response in step 9 are out of scope of the current specification.
The VAL client sends application traffic to the SEALDD client, which duplicates the application data on the redundant PDU sessions. The SEALDD server receives the redundant traffic and reassembles the data to send to the VAL server. Similarly, the SEALDD server duplicates downlink traffic from the VAL server and sends the data to the SEALDD client on the redundant PDU sessions. The SEALDD client eliminates the redundant data and reassembles data to send to the VAL client.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.