Content for TS 24.548 Word version: 17.3.0

1 Scope p. 9

The present document specifies the protocol aspects for the network resource management capability of SEAL to support vertical applications (e.g. V2X) over the 3GPP system.

The present document is applicable to the user equipment (UE) supporting the network resource management client functionality as described in TS 23.434, to the application server supporting the network resource management server functionality as described in TS 23.434 and to the application server supporting the vertical application server (VAL server) functionality as defined in the specific vertical application service (VAL service) specifications.

2 References p. 9

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 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows".

[3]

TS 23.003: "Numbering, addressing and identification".

[4]

TS 23.203: "Policy and charging control architecture".

[5]

TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols; Stage 3".

[6]

TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".

[7]

TS 24.486: "Vehicle-to-Everything (V2X) Application Enabler (VAE) layer; Protocol aspects; Stage 3".

[8]

TS 24.545: "Location Management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification".

[9]

TS 24.547: "Identity management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification".

[10]

TS 26.346: "Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs".

[11]

TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)".

[12]

TS 29.214: "Policy and Charging Control over Rx reference point".

[13]

TS 29.468: "Group Communication System Enablers for LTE (GCSE_LTE); MB2 reference point; Stage 3".

[14]

TS 29.514: "5G System; Policy Authorization Service; Stage 3".

[15] Void.

[16]

RFC 3095: "RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed".

[17]

RFC 3428: "Session Initiation Protocol (SIP) Extension for Instant Messaging".

[18]

RFC 3841: "Caller Preferences for the Session Initiation Protocol (SIP)".

[19]

RFC 4825: "The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)".

[20]

RFC 5795: "The Robust Header Compression (ROHC) Framework".

[21]

OMA OMA-TS-XDM_Group-V1_1_1-20170124-A: "Group XDM Specification".

[22]

RFC 7231: "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content".

[23]

RFC 7252: "The Constrained Application Protocol (CoAP)".

[24]

RFC 7959: "Block-Wise Transfers in the Constrained Application Protocol (CoAP) ".

[25]

RFC 7641: "Observing Resources in the Constrained Application Protocol (CoAP)".

[26]

RFC 8323: "CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets".

[27]

RFC 8949: "Concise Binary Object Representation (CBOR)".

[28]

Constrained RESTful Environments (CoRE) Parameters at IANA, https://www.iana.org/assignments/core-parameters/core-parameters.xhtml

[29]

draft-ietf-core-new-block-14 "Constrained Application Protocol (CoAP) Block- Wise Transfer Options Supporting Robust Transmission".

[30]

RFC 8610: "Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures".

[31]

TS 24.546: "Configuration management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification".

3 Definitions of terms and abbreviations p. 10

3.1 Terms p. 10

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.

SEAL network resource management client:

An entity that provides the client side functionalities corresponding to the SEAL network resource management service.

SEAL network resource management server:

An entity that provides the server side functionalities corresponding to the SEAL network resource management service.

For the purposes of the present document, the following terms and definitions given in TS 23.434 apply:

SEAL client

SEAL server

SEAL service

VAL server

VAL service

VAL user

Vertical

Vertical application

3.2 Abbreviations p. 11

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.

BM-SC

Broadcast-Multicast Service Centre

SNRM-C

SEAL Network Resource Management Client

SNRM-S

SEAL Network Resource Management Server

PCF

Policy Control Function

SEAL

Service Enabler Architecture Layer for verticals

VAL

Vertical Application Layer

4 General description p. 11

Network resource management is a SEAL service that provides the network resource management related capabilities (e.g. unicast and multicast network resources) to one or more vertical applications. The present document enables a SEAL network resource management client (SNRM-C) and a VAL server that communicate with a SEAL network resource management server (SNRM-S).

The SNRM-S obtains and controls multicast resources from the underlying 3GPP network system via the BM-SC and controls unicast resources from the underlying 3GPP network system via the PCRF/PCF.