Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.433  Word version:  19.3.0

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

 

7  Architecturep. 17

7.1  Generalp. 17

The architecture for the SEAL data delivery enabler is based on the generic functional model specified in clause 6.2 of TS 23.434.
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.
Up

7.2  Architecturep. 17

This clause describes the architecture for enabling SEAL Data Delivery applications in the following representations:
  • A service-based representation as specified in TS 23.434, 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 TS 23.501, 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 TS 23.501 and TS 23.502, are utilized by authorized SEAL Data Delivery Enabler Layer functions via CAPIF core function specified in TS 23.222; 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 TS 23.434. 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 TS 23.501.
Reproduction of 3GPP TS 23.433, Fig. 7.2-1: Utilization of 5GS network services based on the 5GS SBA - service based representation
Up
The SEALDD server acts as AF for consuming network services from the 3GPP 5G Core Network entities over the Service Based Architecture specified in TS 23.501.
Figure 7.2-2 illustrates the service-based representation for utilization of the Core Network (5GC, EPC) northbound APIs via CAPIF.
Reproduction of 3GPP TS 23.433, Fig. 7.2-2: Utilization of Core Network Northbound APIs via CAPIF - service based representation
Up
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 TS 23.222.
The mechanism for northbound APIs discovery using the service-based interfaces depicted in Figure 7.2-3 is as specified in TS 23.222.
Figure 7.2-3 illustrates the architecture for SEAL Data Delivery enabler service.
Reproduction of 3GPP TS 23.433, Fig. 7.2-3: Architecture for SEAL Data Delivery Service
Up
The SEALDD server can communicate 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.
Reproduction of 3GPP TS 23.433, Fig. 7.2-4: Architecture for application traffic transfer
Up
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.
Up

7.3  Functional entitiesp. 20

7.3.1  Generalp. 20

The functional entities for SEALDD service are described in the following clauses.

7.3.2  SEAL Data Delivery serverp. 20

The SEAL data delivery server functional entity acts as the application server for the data delivery enablement. The SEALDD server supports the following capabilities:
  1. Suppport the signalling interaction with VAL server to negotiation the data delivery aspects including QoS requirement, protocols information, bandwidth settings, delivery policy provisioning, transmission quality measurement.
  2. 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.
  3. Providing the application data/media storage.
  4. 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.
  5. 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.
Up

7.3.3  SEAL Data Delivery clientp. 20

The SEAL data delivery client functional entity acts as the application client for the data delivery enablement. The SEALDD client supports the following capabilities:
  1. 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.
  2. 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.
Up

7.4  Reference pointsp. 20

7.4.1  Generalp. 20

The reference points for the functional model for SEALDD are described in the following clauses.

7.4.2  SEALDD-UUp. 21

SEALDD-UU reference point is between the SEALDD client and the SEALDD server. It supports the user plane functionality of transfering data content and the signalling plane functionality of exchanging information for SEALDD service provisioning, control, reporting etc.

7.4.3  SEALDD-Cp. 21

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.

7.4.4  SEALDD-Sp. 21

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.

7.4.5  SEALDD-Ep. 21

Reference point enables interactions between two SEALDD servers to transfer data content and exchange information for SEALDD service provisioning, control, reporting etc.

7.4.6  N6p. 21

Reference point enables interactions between SEALDD server and 5GC to transfer SEALDD traffic packets.

7.4.7  N33/N5p. 21

Reference point enables interactions between SEALDD server and 5GC to send control plane requirements or receive control plane notification for optimized data transmission.

7.5  Cardinality rulesp. 21

7.5.1  Generalp. 21

The cardinality rules for the SEALDD entities and SEALDD reference points are described in the following clauses.

7.5.2  Functional Entity Cardinalityp. 21

7.5.2.1  VAL clientp. 21

The following cardinality rules apply for VAL clients:
  1. One or more VAL client(s) may be located in a VAL UE.

7.5.2.2  SEALDD clientp. 21

The following cardinality rules apply for SEALDD clients:
  1. One or more SEALDD client(s) may be located in a VAL UE.

7.5.2.3  SEALDD serverp. 22

The following cardinality rules apply for SEALDD server:
  1. One or more SEALDD server(s) may be located in network.

7.5.2.4  VAL serverp. 22

The following cardinality rules apply for VAL server:
  1. One or more VAL server(s) may be located in network.

7.5.3  Reference Point Cardinalityp. 22

7.5.3.1  SEALDD-C (Between VAL client and SEALDD client)p. 22

The following cardinality rules apply for the reference of SEALDD-C:
  1. One VAL client may communicate with only one SEALDD client; and
  2. One SEALDD client may communicate with one or more VAL client(s) concurrently.

7.5.3.2  SEALDD-S (Between VAL layer and SEALDD server)p. 22

The following cardinality rules apply for the reference of SEALDD-S:
  1. One VAL server may communicate with one or more SEALDD server; and
  2. One SEALDD server may communicate with one or more VAL server(s) concurrently.

7.5.3.3  SEALDD-UU (Between SEALDD client and SEALDD server)p. 22

The following cardinality rules apply for the reference of SEALDD-UU:
  1. One SEALDD client may communicate with one or more SEALDD servers.
  2. One SEALDD server may communicate with one or more SEALDD client(s) concurrently.

7.5.3.4  SEALDD-E (Between SEALDD server and SEALDD server)p. 22

The following cardinality rules apply for the reference of SEALDD-E:
  1. One SEALDD server may communicate with one or more SEALDD server(s) concurrently.

Up   Top   ToC