Content for TR 23.700-88 Word version: 18.0.0

3.1 Terms 3.2 Abbreviations 4.1 Architectural Requirements 4.2 Architectural Assumptions
...

1 Scope p. 11

The scope of this Technical Report is to study the enhancement of 5G System to support Personal IoT Network (PIN). The study addresses the service requirements documented in TS 22.261 for the Personal IoT Networks. The following aspects needs to be studied:

Architecture enhancement:
- To study the potential architectural enhancements for supporting management of PIN, access of PIN via PIN Element with Gateway Capability (PEGC), and communication of PIN (e.g. PIN Element communicates with other PIN Elements directly or via PEGC or via PEGC and 5GS).
- To study the potential architecture enhancements for supporting identifying PIN and the PIN Elements.
Security related:

NOTE:
The study may need cooperation with SA3. If solutions are related to security impact, they will be studied in SA WG3.
To study how to identify PIN and the PIN Elements in the PIN at 5GC level to serve for authentication/authorization.
- Management as well as policy and routing control enforcement:
- To study the management of a PIN.
To study the procedures for PIN discovery, PIN Element discovery.

2 References p. 11

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.501: "System Architecture for the 5G System; Stage 2".

[3]

TS 23.502: "Procedures for the 5G system, Stage 2".

[4]

TS 23.503: "Policy and Charging Control Framework for the 5G System".

[5]

TS 22.261: "Service requirements for the 5G system; Stage 1".

[6]

TS 23.304: "Proximity based Services (ProSe) in the 5G System (5GS)".

[7]

TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".

[8]

TS 23.316: "Wireless and wireline convergence access support for the 5G System (5GS)".

[9]

TS 24.502: "Access to the 3GPP 5G Core Network (5GCN) via Non-3GPP Access Networks (N3AN); Stage 3".

3 Definitions of terms and abbreviations p. 12

3.1 Terms p. 12

For the purposes of the present document, the terms given in TR 21.905, in TS 23.501 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 or in TS 23.501.

Personal IoT Network:

A configured and managed group of PIN Element that are able to communicate each other directly or via PIN Elements with Gateway Capability (PEGC), communicate with 5G network via at least one PEGC, and managed by at least one PIN Element with Management Capability (PEMC).

PIN Element:

A UE or non-3GPP device that can communicate within a PIN (via PIN direct connection, via PEGC, or via PEGC and 5GC), or outside the PIN via a PEGC and 5GC.

PIN Element with Gateway Capability:

A PIN Element with the ability to provide connectivity to and from the 5G network for other PIN Elements, or to provide relay for the communication between PIN Elements.

PIN Element with Management Capability:

A PIN Element with capability to manage the PIN.

PINE-to-PINE communication:

communication between two PINEs which may use PINE-to-PINE direct communication or PINE-to-PINE indirect connection.

PINE-to-PINE direct connection:

the connection between two PIN Elements without PEGC, any 3GPP RAN or core network entity in the middle.

PINE-to-PINE indirect connection:

the connection between two PIN Elements via PEGC or via UPF.

PINE-to-PINE routing:

the traffic is routed by a PEGC between two PINEs, the two PINEs direct connect with the PEGC via non-3GPP access.

PINE-to-Network routing:

the traffic is routed by a PEGC between PINE and 5GS, the PINE direct connects with the PEGC via non-3GPP access separately.

Network local switch for PIN:

the traffic is routed by UPF(s) between two PINEs, the two PINEs direct connect with two PEGCs via non-3GPP access separately.

3.2 Abbreviations p. 12

For the purposes of the present document, the abbreviations given in TR 21.905, in TS 23.501 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 or in TS 23.501.

Personal IoT Networks

PINE

PIN Element

PEGC

PIN Elements with Gateway Capability

PEMC

PIN Elements with Management Capability

P2P

PINE-to-PINE

P2N

PINE-to-Network

NLSP

Network local switch for PIN

4 Architectural requirements and assumptions p. 12

4.1 Architectural Requirements p. 12

This study has following architectural requirements:

If sidelink is used for the direct communication between PEMC and PEGC, reuse procedures defined for 5G ProSe Direct Communication without introducing new features to sidelink.
There shall be no change to underlying non-3GPP access (e.g. WIFI, Bluetooth) standards.

4.2 Architectural Assumptions p. 13

This study has following architectural assumptions:

Only a 3GPP UE can act as PEGC and/or PEMC.
There are one or more PEGCs in a PIN.
There are one or more PEMCs in a PIN, at any point of time one of which is able to control the PIN.
The PIN Elements assumes to use non-3GPP access (e.g. WIFI, Bluetooth) for direct communication, the PEMC can use 5G ProSe Direct Communication for direct communication with PEGC.
In this release, the PEGC and PEMC belongs to same PLMN or (S)NPN.
The scenario when a PEGC or PEMC or both are in roaming is out of the scope of this release.
A single PEGC may support more than one PIN at a time.
Multi-hop P2P (i.e. communication between a chain of PINEs) and P2N relay (i.e. communication from a PINE to another PINE or to the network via an intermediate PINE) are not studied in this release.