Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TR 22.861  Word version:  14.1.0

Top   Top   Up   Prev   None
1…   5…   5.2…   5.3…   6…

 

6  ConsiderationsWord‑p. 23

6.1  Considerations on securityWord‑p. 23

6.1.1  GeneralWord‑p. 23

[PR.6.1-001]
The 3GPP network shall support end-to-end integrity protection and confidentiality for data transmitted between the core network and a device when the device is in indirect 3GPP connection mode.
[PR.6.1-001a]
The 3GPP network shall support end-to-end integrity protection and confidentiality for signalling transmitted between the core network and a device when the device is in indirect 3GPP connection mode.
[PR.6.1-002]
The 3GPP network shall support a resource efficient mechanism to authenticate a device when the device is in indirect 3GPP connection mode.
[PR.6.1-002a]
The 3GPP network shall support a resource efficient mechanism to authorize a device to use an indirect 3GPP connection.
[PR.5.2.3-004]
A device shall determine the relay UE is authorized to serve as a relay before the device uses the indirect connection to the 3GPP network via the relay UE.
[PR.5.2.3-005]
Devices shall determine they are authorized to engage in direct device communication with each other upon establishing a direct device communication using a 3GPP RAT.
[PR.5.2.3-006]
Before establishing a direct device communication using a non-3GPP RAT, devices may use 3GPP credentials to determine if they are authorized to engage in direct device communication.
[PR.5.1.3.2-001]
The 3GPP system shall support a secure mechanism to remotely provision a device that has not been pre-provisioned, with its 3GPP subscription credentials.
[PR.5.1.3.3-001]
The 3GPP system shall minimize the signalling for security that is required prior to user data transmission.
[PR.5.1.3.5-002]
The 3GPP system shall be able to support enhanced authentication and authorization mechanisms to support various types of connectivity (e.g., subscribed, connectivity), with or without the presence of operator credentials in the device.
[PR.5.1.3.5-003]
Enhanced authentication mechanism shall enable an operator to provide efficient means to authenticate a user and a device (e.g., using biometric information).
[PR.5.1.3.5-004]
Enhanced authorization mechanism shall be able to provide a user and a device with on-demand connectivity based on operator policy.
[PR.5.1.3.6-001]
The 3GPP system shall provide a capability for users, applications and devices to register, identify, address and reach other devices, regardless of how each device is connected to 3GPP network.
Up

6.1.2  Group based securityWord‑p. 24

[PR.5.3.3.1-005]
The 3GPP shall support a mechanism which provides an appropriate and efficient authentication mechanism for groups of devices.
[PR.5.2.3-020]
The 3GPP system shall support a secure mechanism to transmit the same information to multiple devices.

6.2  Considerations on chargingWord‑p. 24

This section describes the requirements for collecting charging data for a device. The requirements also apply in the roaming case.
[PR.6.2-001]
The 3GPP core network shall support online and offline charging for a device whether the device is in direct 3GPP connection mode or indirect 3GPP connection mode.
[PR.6.2-002]
The 3GPP core network shall be able to separately identify the charging data of a device from the charging data of a relay UE when the device is in indirect 3GPP connection mode via the relay UE.
[PR.5.1.3.5-002a]
The 3GPP system shall be able to support enhanced charging mechanisms to support various types of connectivity (e.g., subscribed, connectivity), with or without the presence of operator credentials in the device.
[PR.5.1.3.5-005]
Enhanced charging mechanism shall enable an operator to collect charging-related information for enhanced authentication mechanism and enhanced authorization mechanism.
Up

6.3  Considerations on cross TR dependenciesWord‑p. 24

While the four TRs, 22.861, 22.862, 22.863, and 22.864 separately address certain characteristics of a 5G system, they cannot be viewed as providing entirely standalone sets of potential requirements. In addition to the charging and security considerations, there are a number of other cross TR dependencies that must be accounted for. These include specifically requirements related to 5G devices, identities, and access types which may appear in one or more TR, but apply equally across others.
For example, use of the different access modes defined in TR 22.861 may apply as well for the automation and drone scenarios found in TR 22.862. Similarly, the KPIs defined in TR 22.862 are applicable for other IoT scenarios such as those described in TR 22.861. The broadband metrics defined in TR 22.863 are relevant to many scenarios in the other three TRs. And of course, the functionality such as network slicing, scalability, in-network caching defined in TR 22 864 [], can be useful in meeting the KPIs for latency reduction and user density defined in TRs 22.862 [] and TR 22.863.
The cross TR dependencies need to be taken into account in developing normative requirements based on the studies.
Up

7  Consolidation of Potential RequirementsWord‑p. 25

7.1  Resource efficiencyWord‑p. 25

7.1.1  GeneralWord‑p. 25

[PR.5.1.3.1-002]
The 3GPP system shall minimize signalling for device configuration (i.e., service parameters).
[PR.5.1.3.3-001]
The 3GPP system shall minimize the signaling that is required prior to user data transmission.
[PR.5.1.3.4-001]
The 3GPP system shall be able to provide mechanisms to change the association between a subscription and address/number of a device within the same operator and in between different operators in an automated way.
[PR.5.2.3-013]
The 3GPP system shall support mechanisms to optimize the battery consumption of a device.
[PR.5.2.3-014]
The 3GPP system shall optimize the battery consumption of a relay UE via which a device is in indirect 3GPP connection mode.
[PR.5.3.3.2-001]
The 3GPP system shall minimize resources usage for infrequent data transfer from send only devices which send information without requiring a response (e.g., send status information to an application but do not need to receive information from the application).
[PR.5.3.3.2-001a]
The 3GPP system shall minimize resources usage for transfer of infrequent small data units.
[PR.5.3.3.2-004]
The 3GPP system shall support significantly increased device power efficiency over what is supported by EPS.
[PR.5.3.3.4-001]
The 3GPP system shall be able to efficiently and flexibly support any size of data transmissions (e.g., from a few bits to streaming video) to or from the same device.
[PR.5.3.3.1-002a]
The 3GPP network shall support high density massive connections (e.g.,1 million connections per square kilometre) of devices in an efficient manner.
[PR.5.3.3.5-001]
The 3GPP system shall efficiently support service discovery mechanisms where devices can discover, subject to access rights:
  • status of other devices (e.g., sound on/off);
  • capabilities of other devices (e.g., the device is a relay device) and/or;
  • services provided by other devices (e.g., the device is a colour printer).
[PR.5.1.3.6-002]
The 3GPP system shall be able to provide a means for efficient light-weight communication to/from devices (e.g., appliances, wearables, vehicles).
Up

7.1.2  Bulk operationsWord‑p. 25

[PR.5.3.3.1-002]
The 3GPP network shall support high density massive connections (e.g., 1 million connections per square kilometre) of grouped devices in an efficient manner.
[PR.5.3.3.1-003]
The 3GPP network shall be able to support devices, including groups of devices, (e.g., smart meter) with limited communication requirements and capabilities (e.g., devices without an IMS client).
[PR.5.3.3.2-002]
The 3GPP network shall support a resource efficient mechanism to manage (e.g., provide service parameters, activate, deactivate) devices, including groups of devices.
Up

7.1.3  Diverse mobility managementWord‑p. 26

[PR.5.3.3.2-007]
The 3GPP system shall support a resource efficient mechanism to communicate with a stationary device (e.g., simplified mobility management, lower signalling to user data resource usage ratio).
[PR.5.3.3.3-001]
The 3GPP system shall provide efficient support for devices with restricted range of mobility (e.g., within a warehouse).
[PR.5.3.3.3-002]
The 3GPP system shall provide resource efficient support for stationary devices with reduced mobility management (e.g., handover support, idle mode mobility management).

7.2  Connection modelsWord‑p. 26

7.2.1  General requirementsWord‑p. 26

Requirements below are for all kinds of connectivity aspects, including devices which support both direct and indirect 3GPP connection mode and devices which support only indirect 3GPP connection mode. 3GPP RAT or non-3GPP RAT can be used between the devices and relay UEs, in a licensed band or an unlicensed band. 3GPP RAT or non-3GPP access networks (e.g., WLAN, fixed broadband access) can be used between the relay UEs and the 3GPP network:
[PR.5.2.3-002]
The 3GPP system shall support a device to access to the 3GPP network indirectly via a relay UE when the device and the relay UE can communicate in direct device connection mode.
[PR.5.2.3-007]
The 3GPP system shall support an indirect 3GPP connection where a device and a relay UE subscribe to different PLMNs, when both PLMNs have a roaming agreement with the VPLNM.
[PR.5.2.3-009]
The 3GPP system shall support real time and non-real time services (e.g., real time voice and/or real time video) for a device, whether the device is in indirect 3GPP connection mode or in direct 3GPP connection mode.
[PR.5.2.3-011]
The 3GPP system shall support service continuity for a device, when the device changes from one relay UE to another and both relay UEs are connected via 3GPP access to the 3GPP core network in indirect 3GPP connection.
[PR.5.2.3-012]
The 3GPP system shall support service continuity for a device, when the device changes from a direct 3GPP connection to an indirect 3GPP connection via a Relay UE that is connected via 3GPP access to the 3GPP core network, and vice versa.
[PR.5.2.3-015]
The 3GPP network shall identify, address and reach a device with a 3GPP subscription when the device establishes an indirect 3GPP connection mode.
[PR.5.2.3-017]
The 3GPP system shall support a relay UE providing an indirect 3GPP connection with the network for multiple devices.
[PR.5.2.3-018]
The 3GPP system shall support selection of different connectivity aspects by the device (e.g., direct device connection, direct/indirect 3GPP connection) to be used for the device.
[PR.5.2.3-019]
The 3GPP system shall support flexible selection of different RATs (e.g., 3GPP RATs, non-3GPP RATs) to be used for a device.
[PR.5.2.3-020]
The 3GPP system shall support a timely, efficient, and reliable mechanism to transmit the same information to multiple devices.
Up

7.2.2  Requirements specific to use of a 3GPP RATWord‑p. 26

[PR.5.2.3-016]
The 3GPP network shall support end to end QoS for a device when the device is in indirect 3GPP connection mode or direct 3GPP connection mode.
[PR.5.2.3-008a]
A device which is able to access the 3GPP network in direct 3GPP connection mode using a 3GPP RAT shall have a 3GPP subscription.
[PR.5.2.3-017a]
The 3GPP network shall be able to control 3GPP resources used in the communication path between a device and network when the device is in indirect 3GPP connection mode.
Up

7.2.3  Requirements specific to use of a non-3GPP RATWord‑p. 27

[PR.5.2.3-008b]
A device which is able to connect to a UE in direct device connection mode shall have a 3GPP subscription, if the device needs to be identifiable by the core network (e.g., for device management purposes or to use indirect 3GPP connection mode).

8  Conclusion and RecommendationsWord‑p. 27

The Feasibility Study for Massive Internet of Things Technical Report analyses a number of MIoT use cases from TR 22.891, exploring the traffic scenarios in greater details and proposing potential requirements based on those traffic scenarios. The traffic scenarios cover three aspects of MIoT:
  • Operational aspects,
  • Connectivity aspects, and
  • Resource efficiency aspects.
Taking into consideration the use cases from TR 22.891 and the traffic scenarios described in clause 5, new potential requirements related to system operations, connectivity models, and resource efficiencies for Massive Internet of Things have been identified in clause 7 with additional potential requirements for charging and security in clauses 6.
It is recommended to proceed with normative work.
The text of the present document will not be updated to align with normative specifications.
Up

$  Change historyWord‑p. 28


Up   Top