Content for TS 29.583 Word version: 18.1.1
1 Scope
2 References
3 Definitions and abbreviations
3.1 Definitions
3.2 Abbreviations
4 Overview
...
...
1 Scope p. 8
The present document specifies the stage 3 protocol and data model for PIN-9 interface between the PIN application server and PIN server. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the PIN server over PIN-9 interface. The stage 2 functional requirements are defined in TS 23.542.
2 References p. 8
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 29.122: "T8 reference point for Northbound Application Programming Interfaces (APIs)".
[3]
TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
[4]
OpenAPI: "OpenAPI Specification Version 3.0.0", https://spec.openapis.org/oas/v3.0.0 .
[5]
TR 21.900: "Technical Specification Group working methods".
[6]
TS 23.222: "Common API Framework for 3GPP Northbound APIs; Stage 2".
[7]
TS 29.222: "Common API Framework for 3GPP Northbound APIs; Stage 3".
[8]
TS 33.122: "Security aspects of Common API Framework (CAPIF) for 3GPP northbound APIs".
[9]
RFC 6749: "The OAuth 2.0 Authorization Framework".
[10]
TS 23.542: "Application layer support for Personal IoT Network".
[11]
TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
[12]
TS 24.526: "User Equipment (UE) policies for 5G System (5GS); Stage 3".
3 Definitions and abbreviations p. 8
3.1 Definitions p. 8
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.
Personal IoT Network (PIN): A configured and managed group of PIN Element(s) that are able to communicate with each other directly, communicate with each other via PIN Element(s) with Gateway Capability (i.e. PEGC(s)), or use a PEGC to communicate with devices or servers that are outside of the PIN via the 5G network. A PIN includes at least one PEGC and is managed by PIN Element(s) with Management Capability (i.e. PEMC(s)) with the support by an AF if AF is deployed.
PIN Element with Gateway Capability (PEGC): A PIN Element with the ability to provide DN connectivity via the 5G network for other PIN Elements and/or is able to provide relay functionality for communication between PIN Elements. Only a UE is able to act as a PEGC.
3.2 Abbreviations p. 9
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.
PAS
PIN Application Server
PEGC
PIN Element with Gateway Capability
PIN
Personal IoT Network
PINAPP
Personal IoT Network Application
4 Overview p. 9
The Personal IoT Network (PIN) Server forms part of the Application layer support for Personal IoT Networks defined in TS 23.542. It is aimed to support the server-side functionalities required for managing the PIN. The PIN Server provides the following functionalities:
- support PAS registration management procedure (see clause 5.2);
- support PAS service switch subscription procedure (see clause 5.3); and
- support PAS service continuity subscription procedure (see clause 5.4).
PIN-9 reference point exists between the application server and PIN server for the interactions related to enabling PINAPP.
