Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TR 22.859  Word version:  18.2.0

Top   Top   Up   Prev   Next
1…   5…   5.5…   5.10…   6…   A…

 

6  ConsiderationsWord‑p. 44

A lot of the use cases in this document are based on existing systems (e.g. ZigBee® Specification [9], Z-Wave ® [10]]) that can be deployed today, in fact the overview identifies two main Personal IoT Networks, wearables and home automation. These existing Personal IoT Networks use a number of different technologies that provide a set of capabilities.
Up

7  Potential Consolidated RequirementsWord‑p. 44

This section provides Consolidated Potential Requirements for consideration to include in the normative specifications. The CPR's have been grouped into different functional categories, each category contains a table that lists the original PR and any relationship to TR 22.858.

7.0  PIN Element RequirementsWord‑p. 44

CPR # Consolidated Potential Requirement Original PR # Comment
CPR 7.0-1The 5G System shall support mechanisms to identify a PIN and a PIN Element.PR.5.1.5-11
CPR 7.0-2The 5G system shall allow PIN Elements to communicate when there is no connectivity between a PIN Element with Gateway Capability and a 5G network. For a Public Safety PIN licensed spectrum may be used for PIN direct communications otherwise unlicensed spectrum shall be used. Editors note: This requirement is FFS. PR.5.1.5-7
CPR 7.0-3The 5G system shall support a mechanism for a PIN Element to be member of more than one PIN.PR 5.2.6-1
PR 5.7.6-1
PR 5.10.6-1
CPR 7.0-4The 5G system shall support a PIN Element that can:
  • simultaneously unicast to multiple PIN Elements within a PIN; and
  • multicast to multiple PIN elements within a PIN.
PR 5.3.6-1
Up

7.1  GatewayWord‑p. 45

CPR # Consolidated Potential Requirement Original PR # Comment
CPR 7.1-1A PIN shall include at least one PIN Element with Gateway Capability.PR 5.3.6-3
CPR 7.1-2The 5G system shall support access to the 5G network and its services for an authorized PIN Element (linked to a 3GPP subscription and provisioned with credentials) via one or more PIN Elements with gateway capability or directly via non-3GPP access.PR 5.9.6-1
PR 5.10.6-4
CPR 7.1-3The 5G system shall allow only authorized PIN elements to connect to the 5G network via a PIN element with gateway capability. PR 5.13.6-3
Up

7.2  Device and Service DiscoveryWord‑p. 45

CPR # Consolidated Potential Requirement Original PR # Comment
CPR 7.2-1The 5G system shall enable a PIN Element in a PIN to discover other PIN Elements within the same PIN subject to access rights.
CPR 7.2-2The 5G system shall efficiently support service discovery mechanisms where PIN Elements can discover, subject to access rights:
  • availability and reachability of other PIN Elements (e.g. whether a PEGC has external data network connectivity);
  • capabilities of other PIN Elements (e.g. PEMC, PEGC, connection types) and/or;
  • services provided by other PIN Elements (e.g. the PIN Element is an AR/VR headset).
PR.5.1.5-10
PR 5.6.6-1
PR 5.8.6-1,
PR 5.8.6-2
PR 5.10.6-2,
PR 5.10.6-6,
PR 5.11.6-2
CPR 7.2-3The 5G system shall support a mechanism for a PIN Element to select a relay for PIN direct connection that enables access to the target PIN Element.PR 5.10.6-5
CPR 7.2-4The 5G system shall support a mechanism for the PIN user to indicate whether a PIN element is discoverable by other PIN elements of the same PIN.PR 5.13.6-4
CPR 7.2-5The 5G system shall support a mechanism for the PIN user to indicate whether a PIN element is discoverable by UEs that are not members of the PIN.PR 5.13.6-5
Up

7.3  Application ServersWord‑p. 45

CPR # Consolidated Potential Requirement Original PR # Comment
None None
Up

7.4  Privacy and SecurityWord‑p. 46

CPR # Consolidated Potential Requirement Original PR # Comment
CPR 7.4-1The 5G system shall be able to provide secure communications between two or more PIN Elements in a PIN.PR 5.6.6-4
PR 5.7.6-7
PR 5.11.6-4
PR 5.5.6-1
CPR 7.4-2The 5G system shall support a mechanism to mitigate repeated and unauthorized attempts to access PIN Elements (e.g. mitigate a malicious flood of messages).PR 5.8.6-3
PR 5.8.6-4
CPR 7.4-3The 5G system shall support a PIN Element using non-operator managed credentials (e.g. provided by a third party) for performing communications within the PIN when those communications use PIN direct connections.PR 5.1.5.-6
None PR 5.10.6-3
PR 5.5.6-2
CPR 7.4-4The 5G system shall be able to support PINs with PIN Elements subscribed to more than 1 network operator.PR 5.11.6-3
Up

7.5  Direct CommunicationsWord‑p. 46

CPR # Consolidated Potential Requirement Original PR # Comment
CPR 7.5-1The 5G system shall support mechanisms to provision a PIN Element to use either licensed (under control of a MNO) or unlicensed spectrum (may be under the control of the MNO, or not) (e.g., when it has no connectivity to the 5G system).PR 5.2.6-3
PR 5.7.6-3
PR 5.1.5-4
CPR 7.5-2The 5G system shall support mechanisms to aggregate, switch or split the service between non-3GPP RAT and PIN direct connections using licensed spectrum.PR 5.4.6-1
CPR 7.5-3The 5G system shall be able to support concurrent use of both licenced spectrum and non-licensed spectrum PIN direct connectivity between PIN Elements.PR 5.7.6-5
CPR 7.5-4The 5G system shall be able to minimize service disruptionwhen a PIN Element changes the communication path from one PIN Element to another PIN Element. The communication path between PIN devices may include both licensed and unlicensed spectrum 3GPP and non-3GPP access.PR 5.3.6-2
Up

7.6  Connectivity - QoS - chargingWord‑p. 46

CPR # Consolidated Potential Requirement Original PR # Comment
CPR 7.6-1The 5G system shall support a mechanism to manage QoS for communications between PIN Elements when supported by the radio access technology.PR 5.6.6-2
PR 5.6.6-3
Up

7.7  PIN ManagementWord‑p. 47

CPR # Consolidated Potential Requirement Original PR # Comment
CPR 7.7-1A PIN shall include at least one PIN Element with Management CapabilityPR.5.1.5-8
PR.5.1.5-9
CPR 7.7-2 The 5G system shall support mechanisms for a PIN User, network operator or authorized 3rd party to create and manage a PIN, including:
  • Authorizing/deauthorizing PIN Elements;
  • Authorizing/deauthorizing PIN Elements with Management Capability;
  • Authorizing/deauthorizing PIN Elements with Gateway Capability;
  • Establishing duration of the PIN;
  • Configure PIN Elements to enable service discovery of other PIN Elements;
  • Authorize/deauthorise if a PIN Element can use a PEGC to communicate with the 5GS;
  • Authorize/deauthorise for a PIN Element(s):
    • which other PIN Element it can communicate with,
    • which applications/service or service in that PIN it can access'
    • which PIN Element it can use as a relay.
  • Authorize/deauthorise a UE to perform service discovery of PIN Elements over the 5G network;
  • Configure a PIN Element for external connectivity e.g. via 5G system;
PR 5.1.5-1
PR 5.2.6-2
PR 5.7.6-2
PR 5.13.6-2
PR 5.8.6-1a
PR 5.11.6-1
PR 5.11.6-6
PR 5.11.6-7
PR 5.12.6-1
CPR 7.7-3The 5G system shall support mechanisms for a network operator to configure the following policies in a PIN:
  • Configure the connectivity type (e.g. licensed or unlicensed PIN direct connection) a PIN Element can use.
CPR 7.7-45G system shall be able to support mechanism to provide life span information of the PIN to the authorized 3rd party or the PIN elements when the PIN is created for limited time spanPR-5.11.6-5
CPR 7.7-5The 5G system shall support a mechanism to enable a UE or a non-3GPP device that is not a PIN element of the PIN to request to join the PIN.PR 5.13.6-7
Up

7.8Void

7.9  KPIsWord‑p. 47

7.10  ChargingWord‑p. 47

CPR # Consolidated Potential Requirement Original PR # Comment
CPR 7.10-1The 5G system shall support mechanisms to collect charging information on PIN Element communications (e.g., start and stop of communications, amount of data transmitted, radio resources used, PIN identification) when 3GPP access is used.PR.5.1.5-5
PR 5.4.6-2
Up

8  Conclusions and RecommendationsWord‑p. 48

This document analyses a number of use cases related to Personal IoT Networks, the resulting potential requirements have been consolidated in clause 7. In addition, when the use cases where being written for this TR some overlap was seen with use cases TR 22.858.
It is recommended that the consolidated potential requirements identified in this TR and TR 22.858 are considered together as the basis of normative requirements.
Up

Up   Top   ToC