Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.433  Word version:  19.0.0

Top   Top   Up   Prev   None
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.10…   A…   C… 
C Overall lifecycle of SEALDD service  D Media data delivery in SEALDD  D.1 General  D.2 SEALDD deployment for media delivery  $ Change history 

 

C  Overall lifecycle of SEALDD service  p. 89

Reproduction of 3GPP TS 23.433, Fig. C-1: Overall lifecycle of SEALDD
Figure C-1: Overall lifecycle of SEALDD
Up
As shown in Figure C-1, the whole lifecycle of SEALDD to establish the SEALDD connection for the VAL client and VAL server includes two phases:
1.
SEALDD server Service Preparation Phase (This Phase is used by the VAL server to get SEALDD server prepared for SEALDD client access):
  1. When the VAL server decides to use the SEALDD service for data transmission enhancement, it discovers the SEALDD server (e.g. by CAPIF).
  2. Then the VAL server triggers SEALDD service subscription procedure to the discovered SEALDD server, in that procedure, SEALDD server is associated with the VAL server, and specific SEALDD server resource (e.g. address/port of the SEALDD server for redundant transmission) is allocated for the VAL server's service to transfer SEALDD traffic.
  3. For EDN scenario, the SEALDD server or VAL server will register the association information to the EES.
2.
SEALDD client Service Consuming Phase (When SEALDD server is prepared in SEALDD server Service Preparation Phase, the VAL client(s) can trigger SEALDD client to connect to specific prepared SEALDD server for SEALDD service):
  1. When VAL client request to use SEALDD service to transmit the VAL traffic to VAL server, the VAL client or SEALDD client can discover the proper SEALDD server associated with the VAL server (e.g. via EAS discovery, DNS query, pre-configuration or Application layer signalling).
  2. Then SEALDD client can interact with SEALDD server to negotiate for SEALDD data transfer. If Address/Port is allocated in SEALDD service subscription phase, it will be notified to SEALDD client in this step.
  3. Data transmission connection is established between the SEALDD client and SEALDD server for SEALDD traffic transfer.
  4. The whole configuration is accomplished and the VAL traffic is transferred via the SEALDD connection.
Up

D  Media data delivery in SEALDD |R19|  p. 90

D.1  General  p. 90

The SEALDD layer provides a general functionality to support data storage and data delivery by introducing 5G interaction (N5/N33 in control plane, N6 in user plane), including application data storage and management, application signalling and data transmission, E2E URLCC transmission, IoT message transmission (i.e. MSGin5G), etc.

D.2  SEALDD deployment for media delivery  p. 90

For media delivery functionality in SEALDD, as shown in Figure D.2-1, the functionality/protocol defined in SA4 can be reused and further enhanced by SEALDD for supporting media type traffic, 5GMS/RTC AF and 5GMS RTC AS in TS 26.501 and TS 26.506 is utilized in SEALDD server to support the general media type delivery. The 5G transmission adaptation component is added in SEALDD, to facilitate the specific optimization for XR application provided by 5G network.
NOTE: The functionality about 5G transmission adaptation component for media type will be further detailed based on the other progresses (e.g. application enabler for XR Services).
Reproduction of 3GPP TS 23.433, Fig. D.2-1: SEALDD deployment for media delivery
Figure D.2-1: SEALDD deployment for media delivery
Up

$  Change history  p. 92

Up   Top