Content for TR 22.821 Word version: 16.1.0

6.1 Considerations on security 6.2 Considerations on charging 7.1 General 7.2 5G PVN 7.3 Creation and management 7.4 Authorization 7.5 Privacy 7.6 Traffic types 7.7 Indirect communication mode 7.8 Service exposure 7.9 Ethernet A.1 Performance Requirements A.2 Networking Model A.3 Network Topology

6 Considerations p. 44

6.1 Considerations on security p. 44

[PR 5.1.4-1]

A 5G LAN-type service shall support regulatory requirements.

[PR 5.2.3-3]

The 5G LAN-type service shall support a 3GPP supported mechanism to authenticate legacy non-3GPP devices for 5G PVN access.

[PR 5.9.6-3]

The 5G network shall be able to verify the identity of a UE requesting to join a specific private group communications.

[PR 5.19.6-1]

The 5G network shall enable the MNO to authenticate and authorize a remote UE in indirect mode under a relay UE to use 5G LAN-type service.

[PR 5.22.6-1]

The 5G system shall support a secure mechanism for an operator to provision 3GPP credentials to industrial IoT devices for 5G LAN-type services.

[PR 5.24.3.2]

A 5G PVN shall provide integrity protection for communications between authorized UEs.

6.2 Considerations on charging p. 45

[PR 5.1.4-1]

A 5G LAN-type service shall provide a mechanism to collect charging information based on resource usage (e.g., licensed or unlicensed spectrum, QoS, applications).

[PR 5.2.4-2]

The 5G LAN-type service shall support a mechanism to collect charging information based on a UE's MNO.

[PR 5.9.6-4]

The 5G LAN-type service shall be able to collect charging information when a UE joins a specific private communication.

[PR 5.24.4.1]

The 5G LAN-type service shall support a mechanism to collect charging information for both home and roaming UEs.

7 Potential Requirements p. 45

7.1 General p. 45

[PR 5.1.3-1]

A 5G network shall be able to support a 5G LAN-type service with scalable capacity that is able to support a range of UEs from single digits to tens of thousands.

[PR 5.2.3-2]

The 5G LAN-type service shall support authorized UEs, independent of the 3GPP subscription a UE may have.

[PR 5.2.4-1]

The 5G LAN-type service shall provide a mechanism to provide local area coverage while minimizing interference from multi-channel UE.

[PR 5.5.6-1]

The 3GPP 5G LAN-type service shall work with shared Radio Access Network configurations.

[PR 5.6.6-1]

The 3GPP 5G LAN-type service shall work over a wide area mobile network.

[PR 5.7.6-1]

The 3GPP System shall support the on-demand establishment of UE to UE private data communication connections.

[PR 5.7.6-2]

The 3GPP System shall support on-demand UE to UE private data communication connections with multiple types of data communication. At least IP and Ethernet should be supported.

[PR 5.13.6-1]

The 5G network shall support 3GPP service continuity for 5G LAN-type service, i.e., the private communication between UEs shall not be interrupted when one or more UEs of the private communication move within the same PLMN that provides the 5G LAN-type service.

[PR 5.23.6-1]

Based on operator policy and user permission the 5G system shall enable a UE to be aware whether or not a specific UE in the same 5G LAN-type service is available for communication, regardless of whether none, either or both UEs are roaming.

[PR 5.27.6-1]

The 3GPP 5GLAN-type service shall be able to support LAN discovery mechanism.

[PR 5.28.6-1]

The 5G network shall support the routing of non-IP packet (e.g. Ethernet packet) efficiently for private communication between UEs and Control Center (UE) .

[PR 5.28.6-2]

The 5G network shall enable the network operator to scale up/down the 5G PVN, e.g., the coverage, capacity for efficient consumption of network resources.

[PR 5.28.6-3]

The 5G network shall allow the operator to add/remove UEs to/from a 5G LAN-type service.

[PR 5.28.6-4]

The 5G network shall enable the UEs to use the multicast/broadcast addresses to communicate with other UEs with required latency (e.g. 180ms).

[PR 5.29.6-1]

The 5G system shall support to disable a UE from a 5G-LAN type service based on the UE's location (e.g. when UE moves out the area where a particular 5G-LAN type service is allowed).

[PR 5.29.6-2]

The 5G system shall ensure that disablement of a UE from a 5G-LAN type service has no impact on other 5G-LAN type services provided to the same UE.

[PR 5.29.6-3]

The 5G system shall support to enable a UE for a 5G-LAN type service based on the UE's location (e.g. when UE moves back to the area where the 5G-LAN type service is allowed).

7.2 5G PVN p. 46

[PR 5.1.3-4]

A UE shall be able to select a 5G PVN for service.

[PR 5.1.3-6]

A 5G PVN shall support use of unlicensed as well as licensed spectrum.

[PR 5.2.3-1]

The 5G PVN shall support a mechanism to provide consistent QoE to UEs independent of the UEs' MNO.

[PR 5.20.3-1]

The 5G PVN shall support a suitable mechanism for a 5G PVN application to assign a private address to a UE for use within the 5G PVN, and to subsequently modify or remove that assignment.

[PR 5.20.3-2]

A 5G PVN shall support routing based on a private addressing scheme within the 5G PVN.

[PR 5.24.3.1]

A 5G PVN may have member UEs that are subscribed to different PLMNs, e.g., a 5G PVN may span multiple countries and have member UEs that have a subscription to a PLMN in their home country.

[PR 5.30.6-1]

The 5G system shall support on-demand establishment of a multicast session over a 5G PVN.

[PR 5.30.6-2]

The 5G system shall allow UEs to join the multicast within a 5G PVN.

7.3 Creation and management p. 46

[PR 5.8.5-1]

The 5G network shall enable the MNO to create a 5G PVN for one or more UEs.

[PR 5.8.5-2]

The 5G network shall enable the MNO to add one or more UEs to an existing 5G PVN.

[PR 5.8.5-2a]

The 5G network shall enable the MNO to remove one or more UEs from an existing 5G PVN.

[PR 5.9.6-1]

The 5G network shall enable the MNO to authorize the dynamic addition of a UE into a 5G LAN-type service.

[PR 5.9.6-2]

The 5G network shall enable the new UE to communicate with other UEs within the same 5G LAN-type service.

[PR 5.10.6-1]

The 5G network shall enable the MNO to remove a UE from a 5G LAN-type service.

[PR 5.10.6-2]

The 5G network shall ensure that the removed UE has no interference with the 5G LAN-type service that the UE has been removed from.

[PR 5.10.6-3]

The 5G network shall ensure that removal of UE from a particular 5G LAN-type service has no impact on other 5G LAN-type services including the same UE.

[PR 5.11.6-1]

The 5G system shall enable the MNO to assign a UE to multiple independent 5G LAN-type services.

[PR 5.14.6-5]

The 3GPP network shall enable the network operator to support point-to-point addressing as well as multicast addressing between the different UEs in a 5G LAN-type service. It is assumed that all UEs in a 5G LAN-type service use the same type of addresses (e.g. IP, Ethernet or other).

[PR 5.14.6-6]

The 3GPP network shall enable the network operator to create, manage, and remove 5G LAN-type services including their related functionality (subscription data, routing and addressing functionality).

[PR 5.16.6-1]

The 5G network shall enable the 3GPP network operator to define set of UEs allowed to communicate together in a secured way.

[PR 5.24.3-4]

A 5G PVN shall support a mechanism to restrict service for a UE that is a member of a 5G PVN to only communicate with other UEs that are members of the same PVN.

7.4 Authorization p. 47

[PR 5.1.3-2]

A 5G system shall provide a mechanism for an authorized 5G PVN administrator to enable or disable a UE from accessing the 5G PVN.

[PR 5.7.6-3]

The 3GPP 5G network shall enable the MNO to pre-authorize on-demand UE to UE private communication connections through definition of a 5G LAN-type service. Only on-demand private communication requests from other members of the 5G LAN-type service are authorized.

[PR 5.7.6-4]

The 3GPP 5G network shall enable the MNO to authorize on-demand UE to UE private communication connection within a 5G LAN-type service subject to third party authorization. The on-demand private communication connection will be established only in case of positive authorization by the third party (e.g. the owner of a UE).

7.5 Privacy p. 47

[PR 5.3.6-1]

The 5G network shall support a restricted set of UEs to communicate privately amongst each other within a 5G LAN-type service even if these UEs are subscribers to different MNOs.

[PR 5.4.6-1]

For residential scenarios, the 3GPP System shall enable the MNO to provide the same 3GPP 5G LAN-type service to any 5G UE, regardless of whether it is connected via public base stations, indoor small base stations connected via fixed access, or via relay UEs connected to either of these two types of base stations.

[PR 5.7.6-5]

The 3GPP System shall ensure that no other UEs, even in the same 5G LAN-type service, can interfere with the UE to UE private communication.

[PR 5.14.6-3]

The 3GPP network shall enable the network operator to ensure confidentiality and isolation of communications for the private group.

[PR 5.14.6-2]

Only UEs that are members of the 5G LAN-type service shall be able to establish or maintain communication within a 5G LAN-type service.

[PR 5.14.6-3]

The 3GPP network shall enable the network operator to ensure confidentiality and isolation of communications for the 5G LAN-type service.

[PR 5.16.6-2]

The 5G system shall ensure the 3GPP communication between UEs of a 5G LAN-type service with no impact with communications of other UEs not belonging to this 5G LAN-type service.

[PR 5.23.6-3]

The 3GPP 5G system shall enable the MNO to protect personally identifying information of the 5G LAN-type service users including from members of the same 5G LAN-type service while allowing members to address each other to enable communications.

[PR 5.24.3-3]

A 5G PVN shall provide privacy on communications between authorized UEs.

7.6 Traffic types p. 47

[PR 5.1.3-2]

A 5G LAN-type service shall support all media types (e.g., voice, data, multimedia).

[PR 5.4.6-2]

For residential scenarios, the 3GPP 5G LAN-type service shall support traffic scenarios typically found in a home setting (from sensors to video streaming, relatively low amount of UEs per group, many devices are used only occasionally).

[PR 5.5.6-2]

The 3GPP 5G LAN-type service shall support traffic scenarios typically found in an office setting (from sensors to very high data rates e.g. for conferencing, medium amount of UEs per group).

[PR 5.6.6-2]

The 3GPP 5G LAN-type service shall support traffic scenarios typically found in an industrial setting (from sensors to remote control, large amount of UEs per group).

7.7 Indirect communication mode p. 48

[PR 5.19.6-2]

The 5G network shall allow the MNO to add/remove a remote UE in indirect mode to/from a 5G LAN-type service.

[PR 5.19.6-3]

The 5G network shall be able to provide a remote UE using 5G LAN-type service via a relay UE with same level of service as if the remote UE would be in direct mode (i.e. provide required QoS for the Ethernet packets transferred between remote UE and relay UE if they using 3GPP access).

[PR 5.19.6-4]

The 5G network shall be able to support service continuity for the communication between a remote UE with other UEs belonging to the same private communication of a 5G LAN-type service, when the remote UE changes from one relay UE to another or when the UE changes between direct and indirect mode.

7.8 Service exposure p. 48

[PR 5.23.6-2]

Based on operator policy and user permission the system shall enable an authorized 5G LAN-type service to know whether a UE is reachable for communication whether or not the UE is roaming.

[PR 5.23.6-4]

The 3GPP 5G system shall be capable of exchanging with an application sufficient information to identify UEs for the purpose of granting permission to communicate via a 5G LAN-type service.

[PR 5.25.6-1]

Based on MNO policy, the 5G network shall provide suitable APIs to allow a trusted 3rd party application to add/remove a UE to/from a specific 5G LAN type-service.

[PR 5.25.6-2]

Based on MNO policy, the 5G network shall provide suitable APIs to allow a trusted 3rd party application to create a new 5G LAN-type service.

[PR 5.26.6-1]

The 3GPP network operator shall provide an efficient mechanism to allow the application layer of a UE to get the identifiers of other UEs in the same set for 5G LAN-type service that may be used for application communication needs.

7.9 Ethernet p. 48

[PR.5.12.6-1]

The 5G network shall support the routing of non-IP packet (e.g., Ethernet frame) efficiently for private communication between UEs within a 5G LAN-type service.

[PR.5.12.6-2]

The 5G network shall be able to provide the required QoS (e.g., reliability, latency, and bandwidth) for non-IP packet (e.g. Ethernet frame) for private communication between UEs within a 5G LAN-type service.

[PR.5.17.6-001]

The 3GPP system shall be able to support an Ethernet transport service.

[PR.5.17.6-003]

The Ethernet transport service shall support routing based on information extracted from Virtual LAN (VLAN) ID by the 3GPP system.

[PR.5.17.6-004]

The Ethernet transport service shall support routing based on information extracted by the 3GPP system from the Bridge Protocol Data Units created in the Ethernet network based on a Spanning Tree Protocol (e.g. RSTP).

[PR.5.17.6-005]

The Ethernet transport service shall support the transport of Ethernet frames between UEs that an Ethernet device is connected to.

[PR.5.17.6-006]

The Ethernet transport service shall support the transport of Ethernet broadcast frames.

[PR.5.17.6-007]

The Ethernet transport service shall support traffic filtering and prioritization based on source and destination MAC addresses

[PR.5.17.6-008]

The Ethernet transport service shall support traffic filtering and prioritization based on Ethertype (including multiple Ethertypes in double-tagging)

[PR.5.17.6-009]

The Ethernet transport service shall support traffic filtering and prioritization based on 802.1Q VLAN tags (including double tagging).

[PR.5.18.6-1]

The 5G system shall provide a mechanism to ensure the jitter for transporting Ethernet packets is limited by a certain time boundaries.

[PR.5.18.6-3]

The Ethernet transport service shall support routing based on information extracted from the Ethernet header information created based on 802.1Qbv.

[PR.5.21.6-1]

For infrastructure dedicated to high performance Ethernet applications, the 3GPP system shall support clock synchronization defined by IEEE 802.1AS across 5G-based Ethernet links with PDU-session type Ethernet.

[PR.5.21.6-2]

[PR.5.21.6-3]

For infrastructure dedicated to high performance Ethernet applications, the accuracy of clock synchronization should be below 1μs.

[PR.5.21.6-4]

For infrastructure dedicated to high performance Ethernet applications, the 3GPP system shall support time-aware scheduling with absolute cyclic time boundaries defined by IEEE 802.1Qbv [14] for 5G-based Ethernet links with PDU sessions type Ethernet.

[PR.5.21.6-5]

For infrastructure dedicated to high performance Ethernet applications, absolute cyclic time boundaries shall be configurable for flows in DL direction and UL direction.

[PR.5.21.6-6]

For infrastructure dedicated to high performance Ethernet applications, the 3GPP system shall support coexistence of hard-RT traffic following a time-aware schedule and lower priority traffic. The lower priority traffic cannot have a performance degrading impact on the hard-RT traffic.

8 Conclusion and Recommendations p. 49

The present study identified use cases and potential requirements for the application of 5G technology in Local Area Networks. A normative phase should follow. Note that there is some overlap with the FS_CAV study in the industrial LAN use cases. Therefore, the common parts of these two studies should be merged in the normative work.

A Industrial Networking Model p. 50

A.1 Performance Requirements p. 50

Some closed-loop applications typically rely on deterministic and periodic communication, where the controller sends commands to sensors and actuators periodically and the devices respond within a short cycle time. Performance requirements for critical-communication use cases have been specified in [8]. For example, for motion control, a cycle time of up to 2 ms is specified, which imposes a constraint of 1 ms on the delivery time. Further, a tight constraint of 1 μs is specified for jitter.

To achieve these requirements, LAN design requires careful design for medium access, scheduling, etc. To achieve stringent latency and jitter requirements, packet routing is done at OSI layer 2 (Ethernet) instead of the OSI layer 3 (IP). Other important requirements, e.g., communication service availability and communication service reliability, require additional design considerations. For example, redundancy schemes are designed to achieve extremely high communication service availability.

A.2 Networking Model p. 50

Most fieldbuses operate according to a reduced three-layer networking model. Figure A-1 shows a comparison between the OSI reference model and a fieldbus reference model [9], [10]. The fieldbus reference model has three layers - Physical Layer, Data Link Layer and Application Layer. All of the fieldbuses defined in IEC 61784 operate according to this model [9]. In a reduced model, there are fewer interfaces between different networking layers, and therefore, delays due to passing information between the layers can be reduced. This model tends to make the implementation robust. Further, delays due to per- layer processing can be reduced [10]. In a reduced model, network layer functionality can be implemented in either the Data Link Layer, or the Application Layer. For example, the Ethernet Data Link Layer can perform routing in a LAN.

Copy of original 3GPP image for 3GPP TS 22.821, Fig. A-1: OSI and fieldbus reference model [9, 10].

Figure A-1: OSI and fieldbus reference model [9, 10].
(⇒ copy of original 3GPP image)

A.3 Network Topology p. 50

A typical factory network contains controllers, I/O devices, Ethernet switches, and network management and configuration servers. Figure A-2 shows two examples of network topologies.

Copy of original 3GPP image for 3GPP TS 22.821, Fig. A-2: Network topology examples.

Figure A-2: Network topology examples.
(⇒ copy of original 3GPP image)