Content for TS 23.433 Word version: 19.3.0

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…

3.1 Terms 3.2 Symbols 3.3 Abbreviations
...

0 Introduction p. 10

With increasing demand of applications consumption over mobile networks, more and more application content is transmitted over the mobile networks. Vertical applications have diverse requirements for the application content distribution and delivery. To ease the various data delivery demands for vertical applications, a data delivery enabler is specified in this document.

The data delivery service is part of the SEAL services specified in TS 23.434.

1 Scope p. 11

The present document specifies the application enabling layer platform architecture, capabilities and services to efficiently support storage and delivery for the application content/data for vertical applications as part of SEAL services specified in TS 23.434.

This work takes into consideration the existing stage 1 and stage 2 work within 3GPP related to data delivery and 3GPP system user plane aspects specified in TS 22.261 and TS 23.501.

2 References p. 11

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.

References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
For a specific reference, subsequent revisions do not apply.
For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.

[1]

TR 21.905: "Vocabulary for 3GPP Specifications".

[2]

TS 22.261: "Service requirements for the 5G system; Stage 1".

[3]

TS 23.222: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs; Stage 2".

[4]

TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows".

[5]

TS 23.501: "System architecture for the 5G System (5GS); Stage 2".

[6]

TS 23.502: "Procedures for the 5G System (5GS); Stage 2".

[7]

TS 23.503: "Policy and charging control framework for the 5G System (5GS); Stage 2".

[8]

TS 23.548: "5G System Enhancements for Edge Computing ".

[9]

TS 23.554: "Application architecture for MSGin5G Service; Stage 2".

[10]

TS 23.558: "Architecture for enabling Edge Applications".

[11]

TS 28.104: "Management and orchestration; Management Data Analytics (MDA)".

[12]

TS 28.541: "Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3".

[13]

TS 23.436: "Functional architecture and information flows for Application Data Analytics Enablement Service".

[14]

TS 26.501: "5G Media Streaming (5GMS); General description and architecture".

[15]

TS 26.506: "5G Real-time Media Communication Architecture (Stage 2)".

3 Definitions of terms, symbols and abbreviations p. 12

3.1 Terms p. 12

For the purposes of the present document, the terms given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.

Application connection:

Association between the VAL client and the VAL service to provide the VAL service.

Application traffic:

a set of signaling messages or a set of media packet constituting a application service flow. E.g., one or more picture(s) may be an application traffic, the audio stream and the video stream are two different application traffic.

Crossflow QoS measurement:

E2E measurement between SEALDD client and SEALDD server that considers multi-modal traffic routes in combination of uplink direction and downlink direction for same application.

SEALDD-S connection:

Association between the SEALDD server and the VAL server to achieve data delivery of the application traffic. One application connection may have one SEALDD-S connection, e.g., for all the application traffic flows, or have more SEALDD-S connections, e.g., one for application signaling flow, and the other or application media traffic flow(s). A SEALDD-S connection shall be uniquely identified between the VAL server and the SEALDD server.

SEALDD-S flows:

a set of packets have the same attributes, e.g., the same 5-tuple, media type. The application traffic flow may be mapped to one ore more SEALDD-S flow(s). A SEALDD-S flow should be uniquely identified with the SEALDD-S connection.

SEALDD-UU connection:

Association between the SEALDD server and the SEALDD client to achieve the data delivery of the application traffic from the VAL server or the VAL client. One SEALDD-S connection may be associated with one SEALDD-UU connection or multiple SEALDD-UU connections. A SEALDD-UU connection shall be uniquely identified between the SEALDD client and the SEALDD server.

SEALDD-UU flows:

a set of packets have the same attributes, e.g., the same 5-tuple, media type, QoS requirements. One SEALDD-S flow(s) may be mapped to one or multiple SEALDD-UU flows. A SEALDD-UU flow should be uniquely identified with the SEALDD-Uu connection.

3.2 Symbols p. 12

None

3.3 Abbreviations p. 12

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.

Application Function

CAPIF

Common API Framework for northbound APIs

Data Delivery

EAS

Edge Application Server

EDN

Edge Data Network

NRM

Network Resource Management

SBA

Service Based Architecture

SCEF

Service Capability Exposure Function

SEAL

Service Enabler Architecture Layer for verticals

SEALDD

SEAL Data Delivery

URSP

UE Route Selection Policy

VAL

Vertical Application Layer