Content for  TR 22.837  Word version:  19.3.0

In general, a UE senses using either or combination of the non-3GPP sensors such as camera, Lidar, 3GPP-based sensing. In 3GPP 5G wireless sensing, the Sensing transmitters and Sensing receivers sense for stationary and moving Objects around them - using time-difference-of-arrival (TDoA), angle-of-arrival (AoA), angle-of-departure (AoD) measurements, RSSI etc. as shown in Figure 5.4.1-1 [14]. Transparent sensing is a use case in which 3GPP sensing data is captured by Sensing transmitter and/or Sensing receiver and communicated so that the 5GS is aware of the 3GPP sensing data, while the non-3GPP sensing data is the result of non-3GPP sensors and is transparent to 5GS. From this information, service enablers can be defined. One example of such information is location data, whose corresponding service enabler is Location Based Services.

In this use case, non-3GPP sensing data is made available to the 5GS, and the requirements for this exposure are considered. The data so obtained can be used for diverse purposes. One such purpose is Localization (identifying both a three- dimensional position and orientation.) Transparent Sensing data used for Localization is described in TR 22.856.

The distinguishing characteristic of this use case is that the non-3GPP sensing data is provided to the 5GS itself. The application server receiving 'transparent non-3GPP sensing data' as shown in Figure 5.4.1-2 can be operated by the MNO. This enables the MNO to provide specific processing to produce 'combined sensing results as a service,' where the sensing data is supplied by non-3GPP sensors owned and operated by third parties, subscribers, etc. In this use case it is the 5GS that receives 3GPP and non-3GPP sensing data, not a third party.

A UE has access to one or more sensors. In this use case. the UE has access to four sensors: NR-based sensing, 3D LiDAR, an RGB Camera and a Smart Phone Camera. The sensors' physical configuration is known (e.g. the cameras are 10 cm apart). The NR-based sensing capabilities of the UE and its connected BS are used to capture information about the nearby environment by the UE. A mobile network MN supports the acquisition of non-3GPP sensing data. We term this support by the network a 'non-3GPP sensing data consuming service'.

The user U activates a mechanism to enable Non-3GPP sensing data acquisition that can be collected at U's UE. The user U provides this non-3GPP sensing data via the 5GS. This process is analogous to activating or enabling a location tracking service. MN acquires sensing data provided by U's UE, for a period of time. MN can also acquire 3GPP sensing data. 3GPP-RF sensing data can be processed only in 5GS to derive sensing results. The sensing results and the Non-3GPP sensing data can be combined to produce a combined sensing result. The user U deactivates the mechanism to provide non-3GPP sensing data to the 5GS.

The non-3GPP sensing data acquired by the 5GS is processed in order to enable other services. The processed information can for example provide 'Spatial Localization' information that can be exposed to authorized third parties, as discussed in TS 22.856. "Spatial Localization Use Case".

Positioning in 5G Networks been proposed in 3GPP release-16, it specifies positioning signals and measurements for the 5G NR. In release-16, 5G Positioning architecture extends 4G positioning architecture by adding Location Management Function (LMF) and Transmission reception points (TRP). 5GS provides new positioning methods based on multi-cell round-trip time measurements, multiple antenna beam measurements, to enable downlink angle of departure (DL-AoD) and uplink angle of arrival (UL-AoA) [15] [16]. The Rel-17 5G system supports positioning of the device-based but not device-free - objects that do not radiate EM signals [14] [15] [16]. The 5GS already supports transport of non-3GPP sensor data. The Table below provides indicative performance requirements for media used for sensor information communication.

[PR 5.4.6-1] [PR 5.4.6-2] [PR 5.4.6-3] [PR 5.4.6-4]