Content for TR 22.867 Word version: 18.2.0

1… 5… 5.2… 5.3… 5.4… 5.5… 5.7… 5.8… 5.10… 5.12… 5.13… 5.15… 5.16… 5.17… 5.18… 5.20… 5.22… 5.23… 6… 8…

6.1 Potential security considerations 6.2 Potential charging considerations 7.1 Consolidated potential requirements 7.2 Consolidated potential KPIs

6 Considerations p. 86

6.1 Potential security considerations p. 86

(void)

In order to guarantee high level of secured communication for energy applications, as described in clause 5.10, it is important to support secured communication between the 5G core network and energy applications.

A new potential security requirement i.e. [CPR 009] is identified in clause 7.1.

6.2 Potential charging considerations p. 87

None.

7 Consolidated potential requirements and KPIs p. 88

7.1 Consolidated potential requirements p. 88

Table 7.1-1: Consolidated Potential Requirements

CPR #	Consolidated Potential Requirement	Original PR #
CPR-7.1-1	The 5G system shall support an end-to-end latency of less than 5ms or 10ms, as requested by the UE initiating the communication.	PR[5.4]-001
CPR-7.1-2	The 5G system shall support communication channel symmetry in terms of latency (latency from UE1 to UE2, and latency from UE2 to UE1) between the two UEs, with the max asymmetry < 2ms.	PR[5.4]-002.option1
CPR-7.1-3	Based on MNO policy, the 5G network shall provide suitable means to allow a trusted third party to monitor LAN-VN performance parameters, to configure and receive information for conditions relevant to a specific UE, network and specific configuration aspects of the UE in the VN.	PR[5.7]-001
CPR-7.1-4	The 5G system shall provide a means by which an MNO informs 3rd parties of network events (failure of network infrastructure affecting UEs in a particular area, etc.).	PR[5.7]-002
CPR-7.1-5	Based on operator policy, the 5G system shall provide means by which an MNO informs 3rd parties of changes in UE subscription information. The 5G system shall also provide a means for 3rd parties to request this information at any time from the MNO. (note 1)	PR[5.7]-005
CPR-7.1-6	Based on operator policy, the 5G system shall provide means for the 3rd parties to request changes to UE subscription parameters for access to data networks, e.g. static IP address and APN.	PR[5.7]-005a
CPR-7.1-7	The 5G system shall provide a means by which an MNO can inform 3rd parties of changes in the RAT type serving UE, cell ID, quality of signal information, change in frequency band assigned with a suitable frequency via OAM and/or 5G core network to aid the 3rd party user in taking proactive actions to achieve their own service availability.	PR[5.7]-006
CPR-7.1-8	The 5G system shall enable support of a mechanism to support authentication and secured communication between the 5G system Core Network and a 3rd party's application function, in order to provide secure end to end communication service.	PR[5.10]-001
CPR-7.1-9	The 5G system shall provide a mechanism for a 3rd party to report to an MNO service degradations, communications loss and sustained connection loss. These reports use a standard form. The specific values, thresholds and conditions upon which alarms occur could include e.g. the measured values for latency, data rate, availability, jitter, etc. for a UE, its location, and the time(s) in which the degradation occurred. (notes 2, 3)	PR[5.11]-001
CPR-7.1-10	The 5G System should support the IEC 61850-9-3 [29] profile and IEEE Std C37.238-2017 [24].	PR[5.13]-001
CPR-7.1-11	5G system should support at least one of the two profiles for synchrophasor communications: IEC 61850-90-5:2012 [26], or IEEE Std C37.118.2-2011 [28].	PR[5.13]-002
CPR-7.1-12	The 5G system should support the IEEE 802.1Q QoS profile as defined IEC 61850-90-5 [26].	PR[5.13]-003
CPR-7.1-13	The 5G system shall support delivery of the same UE originated data to a group of recipient UEs distributed over a large geographical area in a resource-efficient manner in terms of bandwidth.	PR[5.13]-004
CPR-7.1-14	The 5G system shall allow an originating UE to request a communication service to send data to different groups of UEs at the same time.	PR[5.13]-005
CPR-7.1-15	The 5G system shall allow a UE to request different QoS for the communication in each of those groups.	PR[5.13]-006
CPR-7.1-16	The 5G system shall provide a mechanism for an MNO, based on MNO policy, to automatically report to 3rd party' service degradations, communications loss and sustained connection loss in a specific geographic area (e.g. a cell sector, a cell or a group of cells.) These reports use a standard form. The specific values, thresholds and conditions upon which alarms occur could include e.g. the measured values for latency, data rate, availability, jitter, etc. for a UE, its location, and the time(s) in which the degradation occurred.	PR[5.17]-002
CPR-7.1-17	Subject to regulatory requirements and operator policy, the 5G system shall support a mechanism by which an MNO can identify the uninterruptable power supply status of the MNO's infrastructure, specifying which physical regions would be affected in terms of physical topology, as this information will facilitate energy system recovery operations	PR[5.18]-001
CPR-7.1-18	Subject to regulatory requirements, the 5G system shall support a mechanism by which a third party can communicate the energy system recovery status in terms of location and time table to the MNO, as this information will facilitate MNO operations to facilitate energy system recovery. (note 4)	PR[5.18]-002
CPR-7.1-19	The 5G system shall enable recipient UEs to indicate their interest in receiving data from a specific originating UE.	PR[5.16]-003
NOTE 1: Examples of UE subscription information include IP, 5G LAN-VN membership address and APN/DNN. These changes can have strong impacts in the stability of the 3rd party service. NOTE 2: What the MNO does with such reports is out of scope of 3GPP specifications. NOTE 3: The above potential requirement expresses the need for reporting by a third party to the 5GS and leaves it to downstream groups (in this case SA5) to work out the implications. NOTE 4: It is assumed that once aware of the proximity and duration of the energy outage, the MNO may manage the 5G nodes affected by the outage to make use of the power autonomy remaining in the 5G nodes, e.g. prioritizing the delivery of resources to support the energy system operations communications. Power consumption for energy system operations must be optimized so that the service recovery can be remotely orchestrated by the energy utility.

7.2 Consolidated potential KPIs p. 91

Table 7.2-1: KPI Table of Periodic Communication Services

Use case	Experienced data rate	availability	Transfer interval: target value	Message size	Service area	Max Allowed End-to-End latency	density
5.1 Distributed Energy Storage -monitoring	UL: > 16 Mbit/s (urban), 640 Mbit/s (rural) DL: > 100 kbit/s (note 1)	DL: >99.90%	UL: 10 ms	UL: 50 x 16 kbyte	-	DL:<10 ms UL:<10 ms	>10 /km² (urban), >100 /km² (rural) (storage node density, note 2)
5.1 Distributed Energy -Storage Data collection	UL: > 128 kbit/s (urban), 10.4 Mbit/s (rural) DL: > 100 kbit/s (note 1)	DL: >99.90%	UL: 1000 ms	UL: 50 x 26 kbyte DL: >100 kbyte	-	DL:<10 ms UL:<1000 ms	>10 /km² (urban), >[100 /km² (rural) (storage node density, note 2)
5.2 advanced metering	UL:<2 Mbit/s DL:<1 Mbit/s	>99.99%	-	-	-	General information data collection: <3000 ms (note 3)	<10000/km² (connection density, note 4)
5.3 Distributed Feeder Automation	2 Mbit/s to 10 Mbit/s	99.999%	Normal:-1s; Fault:2ms -	-	-	<10 ms (see note 6)- Latency jitter <50 μs (note 5)	54/km² (see note 7) 78/km² (connection density, note 8)
5.5 Distribution Automation (DA), centralized architecture	9.6-100 kbit/s	99.999%	-	-	-	100 ms - 2 s	100/km² concentrated rural, 10/km² semi-urban
5.8 Smart Distribution Transformer Terminal	>2 Mbit/s (note9)				100 m ~ 500 m, outdoor, indoor / deep indoor	10 ms, 100 ms, 3 s (note10)	500 /distribution area (note 11)
5.12 Distribution Intelligence - FLISR High speed current differential protection (see NOTE 13 )	1,2Mbit/s~2,5 Mbit/s	> 99,999 %	≤ 1 ms~2ms	<245 byte	- several km²	5 ms~15ms	≤ 100/km²
5.15 Distributed Energy Resources and Microgrids (note 9 )	5.4 Mbit/s	99.9999 %	≤ 1 ms	140 byte	-	3 ms	-
5.22 ensuring uninterrupted MTC service availability during emergencies	< 1 kbit/s per DER	99.9999 %	100 ms (notes 10, 11 )	-	-	-	-
NOTE 1: This KPI is to require data rate in one Energy storage station which may provide via one or more 5G connections and via one or more 3GPP UE(s) at the same time. NOTE 2: It is used to deduce data volume in an area which has multiple energy storage stations. The data volume can be deduced through follow formula: ( Current + other data) data rate per storage station * (Storage node density /km²) * (Active factor/km²) + video data rate per storage station * (Storage node density /km²). In general, the Active factor is 10% NOTE 3: It is one way latency from 5G IoT device to backend system while the distance between them is no more than 40 km i.e. city range. The command implementation need 100 ms. NOTE 4: It is the typical connection density in today city environment. With the evolution from meter centralization collection to sockets in home directly collection, the connection density is expected to increase 5-10 times. NOTE 5: The latency jitter is required for the switch off between the active and standby communication links NOTE 6: It is the one way delay from a distributed terminal to 5G network. NOTE 7: When the distributed terminals are deployed along overhead line, about 54 terminals will be distributed along overhead lines in one square kilometre with the power load density is 20MW/km². NOTE 8: When the distributed terminals are deployed in power distribution cabinets, and considering the power load density is 20 MW/km², there are about 78 terminals in one square kilometre. NOTE 9: It is the smart metering application data rate between the Smart Distribution Transformer Terminal and energy end equipment. Once there are multiple smart grid applications, it is required more data rate. NOTE 10: It depends on different applications supported by the Smart Distribution Transformer Terminal. The less the latency is, the more applications can be supported. NOTE 11: The distribution area is circular with range between 100 m and 500 m (0.031 km² to 0.785 km²). NOTE 12: UE to UE communication is assumed. NOTE 13: Unless otherwise specified, all communication includes 1 wireless link (UE to network node or network node to UE) rather than two wireless links (UE to UE). NOTE 14: It applies to both UL and DL unless stated otherwise.

Table 7.2-2: KPI Table of Aperiodic Communication Services

Use case	Max allowed end-to-end latency	Experienced data rate	Communication service availability	Message size	Service area	Reliability	Storage node density # /km² (note 2)
5.1 Distributed Energy Storage Energy storage station: video	DL:<10 ms UL:<1000 ms (rural)	UL: >5 Gbit/s DL: >100 kbit/s (see note 1)	-	-	-	DL: >99.90%	>[x]*100
5.2 Advanced metering	Accuracy fee control: < 100 ms (note2);	DL:<1 Mbit/s				>99,99%
5.12 Distribution Intelligence - FLISR Feeder automation (note 2)	20 ms	-	> 99.999 %	< 100 byte	several km²	-	-
5.15 Distributed Energy Resources and Microgrids (note 2)	<3 ms	-	> 99.9999 %	160 byte	-	-	-
NOTE 1: The required data rate in one Energy storage station which may provide via one or more 5G connections and one or more 3GPP UE(s) at the same time. It can be calculated with following formula: 12.5 Mbytes/s * 50(containers) * 8 = 5 Gbit/s NOTE 2: The accuracy fee control latency here is for communication one way latency from backend system to 5G IoT device while the distance between them is no more than 40 km i.e. city range. NOTE 3: UE to UE communication is assumed.

Table 7.2-3: Clock Synchronization Service Performance Requirements

Use case	User-specific clock synchronicity accuracy level [65]	Number of devices in one Communication group for clock synchronisation	Clock synchronicity requirement	Service area	5GS synchronicity budget requirement
5.3 Distributed Feeder Automation	-	54/km² (note 1) 78/km² (note 2)	-	several km²	<10 μs
5.12 Distribution Intelligence - FLISR feeder automation aperiodic deterministic communication and High speed current differential protection periodic deterministic communication	-	≤ 100/km²	-	several km²	≤ 10 μs
5.19 Applications Using IEC 61850-9-2 Sampled Values Smart Grid: Synchronicity between sync master and PMUs This range covers the extreme cases where the PTP clock in the end device uses 5G sync modem as direct time-source (1 μs) The 5G sync modem acts as PTP GM or 5G sync modem provides PPS output to PTP GM at the top of the Ethernet based synchronization chain with up to 15 transparent clocks or 3 boundary clocks (250 ns).	4	Up to 100 UEs	<250 ns-1 μs [7] (note 3)	< 20 km²	-
5.19 Applications Using IEC 61850-9-2 Sampled Values Smart Grid: Power system protection in digital substation with merging units, line differential protection and synchronization	4a	Up to 100 UEs	<10-20 μs [64] (note 3)	< 20 km²
5.19 Applications Using IEC 61850-9-2 Sampled Values Smart Grid: Event reporting and Disturbance recording use-cases	4b	Up to 100 UEs	<1 ms [64] (note 3)	< 20 km²
NOTE 1: When the distributed terminals are deployed along overhead line, about 54 terminals will be distributed along overhead lines in one square kilometre with the power load density is 20MW/km². NOTE 2: When the distributed terminals are deployed in power distribution cabinets, and considering the power load density is 20MW/km², there are about 78 terminals in one square kilometer. NOTE 3: The clock synchronicity requirement refers to the clock synchronicity budget for the 5G system, as described in Clause 5.19.6.1.