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.583  Word version:  18.0.0

Top   Top   None   None   Next
1…   5…   6… 
1 Scope  2 References  3 Definitions of terms, symbols and abbreviations  3.1 Terms  3.2 Abbreviations  4 Overview  4.1 General 
...

 

1  Scope  p. 16

The present document specifies the protocols and the associated procedures for application layer support for Personal IoT Network (PINAPP) as specified in TS 23.542 for:
  1. PIN application communication among PIN peers (over the PIN-2, PIN-3, and PIN-4 interfaces); and
  2. PIN application communication between the PIN peer and the PIN server (over the PIN-6, PIN-7, and PIN-10 interfaces).
The present specification also defines the message format, message contents, error handling and system parameters applied by the protocols for PINAPP.
Up

2  References  p. 16

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.542: "Application layer support for Personal IoT Network".
[3]
TS 22.261: "Service requirements for the 5G system".
[4]
RFC 9110  :"HTTP Semantics".
[5]
TS 29.571: "5G System; Common Data Types for Service Based Interfaces Stage 3".
[6]
ITU-T Recommendation E.212: "The international identification plan for public networks and subscriptions", 2016-09-23.
[7]
TS 23.003: "Numbering, addressing and identification".
[8]
RFC 791:  "Internet Protocol".
[9]
RFC 4291:  "IP Version 6 Addressing Architecture".
[10]
RFC 3986:  "Uniform Resource Identifier (URI): Generic Syntax".
[11]
TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
[12]
W3C REC-xmlschema-2-20041028: "XML Schema Part 2: Datatypes".
[13]
IEEE 802.11-2012, Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications, IEEE Std.
[14]
RFC 5905:  "Network Time Protocol Version 4: Protocol and Algorithms Specification".
[15]
TS 24.526: "UE policies for 5G System (5GS); Stage 3".
Up

3  Definitions of terms, symbols and abbreviations  p. 17

3.1  Terms  p. 17

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.
PIN application enabler server:
An entity that provides the server side functionalities corresponding to the PIN application enabler layer.
PIN communication:
A communication in a PIN between two PIN peers or between a PIN peer and an application server, which is supported by PGAE-C within the same PIN via a PDU session.
PIN element application enabler client:
An entity that provides the client side functionalities corresponding to the PIN application enabler layer.
PIN gateway application enabler client:
An entity that provides the client side functionalities corresponding to the PIN application enabler layer.
PIN management application enabler client:
An entity that provides the client side functionalities corresponding to the PIN application enabler layer.
PIN peer:
The appellative of the element in the PIN, which can be a PEAE-C, a PGAE-C, or a PMAE-C.
For the purposes of the present document, the following terms given in TS 22.261 apply:
Personal IoT Network
PIN Element
PIN Element with Gateway Capability
PIN Element with Management Capability
Up

3.2  Abbreviations  p. 17

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.
FQDN
Fully Qualified Domain Name
GPSI
Generic Public Subscription Identifier
MIME
Multipurpose Internet Mail Extensions
PAE-S
PIN Application Enabler Server
PEMC
PIN Element with Management Capability
PEAE-C
PIN Element Application Enabler Client
PEGC
PIN Element with Gateway Capability
PGAE-C
PIN Gateway Application Enabler Client
PIN
Personal IoT Network
PINAPP
Application layer support for Personal IoT Network
PINE
PIN Element
PMAE-C
PIN Management Application Enabler Client
URI
Uniform Resource Identifier
Up

4  Overview  p. 17

4.1  General  p. 17

To support the application layer support for Personal IoT Network (PINAPP), the PINE contains a PIN element application enabler client (PEAE-C), the PEGC contains a PIN gateway application enabler client (PGAE-C), the PEMC contains a PIN management application enabler client (PMAE-C), and the PIN server contains a PIN application enabler server (PAE-S). The communication in PINAPP includes:
  1. PIN application communication among PIN peers (over the PIN-2, PIN-3, and PIN-4 interfaces); and
  2. PIN application communication between the PIN peers and the PIN server (over the PIN-6, PIN-7, and PIN-10 interfaces),
wherein:
  1. the PEAE-C communicates with PGAE-C over the PIN-2 interface;
  2. the PEAE-C communicates with PMAE-C over the PIN-3 interface;
  3. the PGAE-C communicates with PMAE-C over the PIN-4 interface;
  4. the PMAE-C communicates with PAE-S over the PIN-6 interface;
  5. the PGAE-C communicates with PAE-S over the PIN-7 interface; and
  6. the PEAE-C communicates with PAE-S over the PIN-10 interface.
The HTTP protocol interactions for the above interfaces are specified in clause 5.
The coding of all the messages is specified in clause 6.
The message format and the message contents are specified in clause 7.
Up

Up   Top   ToC