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 24.542  Word version:  18.1.0

Top   Top   None   None   Next
1…   6…   A… 
1 Scope  2 References  3 Definitions of terms, symbols and abbreviations  3.1 Terms  3.2 Abbreviations  4 General description  5 Functional Entities  5.1 SEAL notification management client (SNM-C)  5.2 SEAL notification management server (SNM-S) 
...

 

1  Scope  p. 7

The present document specifies the protocol aspects for the notification management capability of SEAL to support vertical applications (e.g. V2X) over the 3GPP system for NM-UU reference point.
The present document is applicable to the User Equipment (UE) supporting the notification management client functionality as described in TS 23.434, to the application server supporting the notification 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 specific vertical application service (VAL service) specification.
Up

2  References  p. 7

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 24.547: "Identity management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification".
[4]
RFC 6750:  "The OAuth 2.0 Authorization Framework: Bearer Token Usage".
[5]
RFC 8259:  "The JavaScript Object Notation (JSON) Data Interchange Format".
Up

3  Definitions of terms, symbols and abbreviations  p. 7

3.1  Terms  p. 7

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 notification management client:
An entity that provides the client side functionalities corresponding to the SEAL notification management service.
SEAL notification management server:
An entity that provides the server side functionalities corresponding to the SEAL notification 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 notification
VAL server
VAL service
VAL user
Vertical
Vertical application
Up

3.2  Abbreviations  p. 8

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.
NEF
Network Exposure Function
SCEF
Service Capability Exposure Function
SEAL
Service Enabler Architecture Layer for verticals
SNM-C
SEAL Notification Management Client
SNM-S
SEAL Notification Management Server
URI
Uniform Resource Identifier
URL
Uniform Resource Locator
VAL
Vertical Application Layer
Up

4  General description  p. 8

Notification management is a SEAL service that provides the notification management related capabilities to one or more vertical applications. The present document enables a SEAL notification management Client (SNM-C) and VAL server to manage notifications through the SEAL notification management Server (SNM-S).

5  Functional Entities  p. 8

5.1  SEAL notification management client (SNM-C)  p. 8

The SNM-C is a functional entity that acts as the application client for notification management.
To be compliant with the HTTP procedures in the present document, the SNM-C:
  1. shall support the procedure of creating and opening notification channel as per clause 6.2.2.1;
  2. shall support the procedure to receive PUSH notification message from the SNM-S as per clause 6.2.3.1.1;
  3. shall support the procedure to PULL notification message from the SNM-S as per clause 6.2.3.2.1;
  4. shall support the procedure to update notification channel as per clause 6.2.5.1; and
  5. shall support the procedure to delete notification channel as per clause 6.2.4.1.
Up

5.2  SEAL notification management server (SNM-S)  p. 8

The SNM-S functional entity provides notification management support within the vertical application layer.
To be compliant with the HTTP procedures in the present document, the SNM-S:
  1. shall support the procedure of creating and opening notification channel as per clause 6.2.2.2;
  2. shall support the procedure to send PUSH notification message to the SNM-C as per clause 6.2.3.1.2;
  3. shall support the procedure to PULL notification message as per clause 6.2.3.2.2;
  4. shall support the procedure to update notification channel as per clause 6.2.5.2; and
  5. shall support the procedure to delete notification channel as per clause 6.2.4.2.
Up

Up   Top   ToC