hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 6.4 SEALDD server discovery and selection requirements
| |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 6.4.1 Description
| This clause specifies the SEALDD server discovery and selection requirements for SEALDD service.
|
7c353f7900c6911ed12bf8daab944b90 | 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.
|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 6.5 MSGin5G message transfer requirements
| |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 6.5.1 Description
| This clause specifies the MSGin5G message transfer requirements for SEALDD service.
|
7c353f7900c6911ed12bf8daab944b90 | 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.
|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 6.6 Data transmission bandwidth control requirements
| |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 6.6.1 Description
| This clause specifies the data transmission bandwidth control requirements for SEALDD service.
|
7c353f7900c6911ed12bf8daab944b90 | 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.
|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 7 Architecture
| |
7c353f7900c6911ed12bf8daab944b90 | 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 desc... |
7c353f7900c6911ed12bf8daab944b90 | 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 functio... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 7.3 Functional entities
| |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 7.3.1 General
| The functional entities for SEALDD service are described in the following clauses.
|
7c353f7900c6911ed12bf8daab944b90 | 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, bandwidt... |
7c353f7900c6911ed12bf8daab944b90 | 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/rele... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 7.4 Reference points
| |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 7.4.1 General
| The reference points for the functional model for SEALDD are described in the following clauses.
|
7c353f7900c6911ed12bf8daab944b90 | 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.
|
7c353f7900c6911ed12bf8daab944b90 | 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 cl... |
7c353f7900c6911ed12bf8daab944b90 | 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 1: The data/content delivery between SEALDD server and VAL server can use the pull... |
7c353f7900c6911ed12bf8daab944b90 | 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.
|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 7.4.6 N6
| Reference point enables interactions between SEALDD server and 5GC to transfer SEALDD traffic packets.
|
7c353f7900c6911ed12bf8daab944b90 | 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.
|
7c353f7900c6911ed12bf8daab944b90 | 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.
|
7c353f7900c6911ed12bf8daab944b90 | 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 ... |
7c353f7900c6911ed12bf8daab944b90 | 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.
|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 7.5 Cardinality rules
| |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 7.5.1 General
| The cardinality rules for the SEALDD entities and SEALDD reference points are described in the following clauses.
|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 7.5.2 Functional Entity Cardinality
| |
7c353f7900c6911ed12bf8daab944b90 | 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.
|
7c353f7900c6911ed12bf8daab944b90 | 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.
|
7c353f7900c6911ed12bf8daab944b90 | 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.
|
7c353f7900c6911ed12bf8daab944b90 | 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.
|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 7.5.3 Reference Point Cardinality
| |
7c353f7900c6911ed12bf8daab944b90 | 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 specif... |
7c353f7900c6911ed12bf8daab944b90 | 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.
|
7c353f7900c6911ed12bf8daab944b90 | 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.
|
7c353f7900c6911ed12bf8daab944b90 | 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.
|
7c353f7900c6911ed12bf8daab944b90 | 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.
|
7c353f7900c6911ed12bf8daab944b90 | 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.
|
7c353f7900c6911ed12bf8daab944b90 | 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.
|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 8 Identities and commonly used values
| |
7c353f7900c6911ed12bf8daab944b90 | 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.
|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 8.2 SEALDD server ID
| The SEALDD server ID uniquely identifies the SEAL data delivery server.
|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 8.3 SEALDD client ID
| The SEALDD client ID is a globally unique value that identifies the SEAL data delivery client.
|
7c353f7900c6911ed12bf8daab944b90 | 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.
|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 8.5 Multi-modal SEALDD flow ID
| The multi-modal SEALDD flow ID is used by the SEALDD client and SEALDD server to uniquely identify associated multi-modal VAL application traffic flows per VAL service.
|
7c353f7900c6911ed12bf8daab944b90 | 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.
|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9 Procedures and information flows
| |
7c353f7900c6911ed12bf8daab944b90 | 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... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9.2 SEALDD regular connection management
| |
7c353f7900c6911ed12bf8daab944b90 | 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 ... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9.2.2 Procedure
| |
7c353f7900c6911ed12bf8daab944b90 | 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 SEA... |
7c353f7900c6911ed12bf8daab944b90 | 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 ... |
7c353f7900c6911ed12bf8daab944b90 | 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: P... |
7c353f7900c6911ed12bf8daab944b90 | 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 co... |
7c353f7900c6911ed12bf8daab944b90 | 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 establish... |
7c353f7900c6911ed12bf8daab944b90 | 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... |
7c353f7900c6911ed12bf8daab944b90 | 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 transm... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9.2.3 Information flows
| |
7c353f7900c6911ed12bf8daab944b90 | 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
... |
7c353f7900c6911ed12bf8daab944b90 | 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 inform... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9.2.3.3 SEALDD regular transmission connection establishment request (Client to Server)
| Table 9.2.3.3-1 describes the information flow from the SEALDD client to the SEALDD server 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 (SEA... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9.2.3.4 SEALDD regular transmission connection establishment response (Server to Client)
| Table 9.2.3.4-1 describes the information flow from the SEALDD server to the SEALDD client 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 ... |
7c353f7900c6911ed12bf8daab944b90 | 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... |
7c353f7900c6911ed12bf8daab944b90 | 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... |
7c353f7900c6911ed12bf8daab944b90 | 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 ... |
7c353f7900c6911ed12bf8daab944b90 | 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)
Subscr... |
7c353f7900c6911ed12bf8daab944b90 | 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 co... |
7c353f7900c6911ed12bf8daab944b90 | 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... |
7c353f7900c6911ed12bf8daab944b90 | 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 o... |
7c353f7900c6911ed12bf8daab944b90 | 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 statu... |
7c353f7900c6911ed12bf8daab944b90 | 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 correspondi... |
7c353f7900c6911ed12bf8daab944b90 | 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... |
7c353f7900c6911ed12bf8daab944b90 | 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 subscr... |
7c353f7900c6911ed12bf8daab944b90 | 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.
|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9.2.3.17 SEALDD data transmission connection establishment request (Server to Client)
| 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 request
Information element
Status
Description
Requestor ID
M
Identity of the reque... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9.2.3.18 SEALDD data transmission connection establishment response (Client to Server)
| 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 response
Information element
Status
Description
Result
M
Indicates the success o... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9.2.3.19 SEALDD bandwidth control notify
| Table 9.2.3.19-1 describes the information flow from the SEALDD server to the VAL server to notify the bandwidth control message.
Table 9.2.3.19-1: SEALDD bandwidth control notify
Information element
Status
Description
Result
M
Success or failure.
Notification ID
M
Identifies the bandwidth control notificatio... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9.2.4 APIs
| |
7c353f7900c6911ed12bf8daab944b90 | 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_RegularTransmissionConne... |
7c353f7900c6911ed12bf8daab944b90 | 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.
|
7c353f7900c6911ed12bf8daab944b90 | 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. for SEALDD client side initiated operation and clause 9.2.3.17 for server side initiated operation.
Outputs: See clause... |
7c353f7900c6911ed12bf8daab944b90 | 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.
|
7c353f7900c6911ed12bf8daab944b90 | 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.
|
7c353f7900c6911ed12bf8daab944b90 | 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.
|
7c353f7900c6911ed12bf8daab944b90 | 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.
|
7c353f7900c6911ed12bf8daab944b90 | 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.
|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9.3 SEALDD enabled E2E redundant transmission
| |
7c353f7900c6911ed12bf8daab944b90 | 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 ... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9.3.2 Procedure
| |
7c353f7900c6911ed12bf8daab944b90 | 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.
... |
7c353f7900c6911ed12bf8daab944b90 | 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 tr... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9.3.2.3 SEALDD enabled URLLC transmission connection establishment based on policy
| The SEALDD servers has Data Delivery (DD) policy being provisioned. The DD policy includes reliable transmission service for the associated VAL traffic. 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... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9.3.2.4 SEALDD enabled URLLC transmission connection deletion based on policy
|
Figure 9.3.2.4-1: SEALDD enabled URLLC transmission connection deletion
The procedure is same as step 1 to 8 in clause 9.2.2.4 with differences that in step 4 to 5, the SEALDD server requests URLLC transmission connection deletion to the SEALDD client and the SEALDD client responds with URLLC transmission connection... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9.3.2.5 SEALDD client initiated connection release
| Figure 9.3.2.5-1 illustrates the procedure for SEALDD client initiated connection release procedure from the SEALDD client to the SEALDD server.
Figure 9.3.2.5-1: SEALDD client initiated connection release
1. The SEALDD client sends the SEALDD URLLC connection release request to the SEALDD server to release the est... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9.3.3 Information flows
| |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9.3.3.1 SEALDD URLLC transmission request
| See clause 9.2.3.1 for the details of information flow with the following clarification:
- The bandwidth related IEs are not applicable.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.