Terminal sensing integrated with communication via WLAN operation
By enhancing N3IWF and AMF functionalities and introducing SF-C/SF-U entities, wireless communication systems integrate sensing and communication over WLAN, addressing the limitations of existing systems and enabling efficient data acquisition and transmission for enhanced situational awareness and use cases.
Patent Information
- Application Number
- PCT/CN2025/093444
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-08
- Publication Date
- 2026-11-12
AI Technical Summary
Existing wireless communication systems lack efficient integration of sensing and communication functionalities, particularly in non-3GPP access networks like WLAN, which limits the ability to provide integrated sensing and communication services across various use cases such as smart homes, health monitoring, and intelligent transportation.
Enhancements to the N3IWF and AMF functionalities to support sensing control signaling and data transmission over untrusted WLAN access, along with the introduction of SF-C and SF-U entities to manage and process sensing data in the control and user planes, respectively, enabling seamless integration of sensing and communication services.
Facilitates wide-area multi-dimensional sensing and communication services, enhancing situational awareness and supporting various use cases by enabling efficient data acquisition and transmission via non-3GPP access networks like WLAN.
Smart Images

Figure CN2025093444_12112026_PF_FP_ABST
Abstract
Description
TERMINAL SENSING INTEGRATED WITH COMMUNICATION VIA WLAN OPERATIONTECHNICAL FIELD
[0001] This application relates generally to wireless communication systems, including wireless communication systems using integrated sensing and communication (ISAC) functionalities.BACKGROUND
[0002] Wireless mobile communication technology uses various standards and protocols to transmit data between a base station and a wireless communication device. Wireless communication system standards and protocols can include, for example, 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) (e.g., 4G) , 3GPP New Radio (NR) (e.g., 5G) , and Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard for Wireless Local Area Networks (WLANs) (commonly known to industry groups as ) .
[0003] As contemplated by the 3GPP, different wireless communication systems' standards and protocols can use various radio access networks (RANs) for communicating between a base station of the RAN (which may also sometimes be referred to generally as a RAN node, a network node, or simply a node) and a wireless communication device known as a user equipment (UE) . 3GPP RANs can include, for example, Global System for Mobile communications (GSM) , Enhanced Data Rates for GSM Evolution (EDGE) RAN (GERAN) , Universal Terrestrial Radio Access Network (UTRAN) , Evolved Universal Terrestrial Radio Access Network (E-UTRAN) , and / or Next-Generation Radio Access Network (NG-RAN) .
[0004] Each RAN may use one or more radio access technologies (RATs) to perform communication between the base station and the UE. For example, the GERAN implements GSM and / or EDGE RAT, the UTRAN implements Universal Mobile Telecommunication System (UMTS) RAT or other 3GPP RAT, the E-UTRAN implements LTE RAT (sometimes simply referred to as LTE) , and NG-RAN implements NR RAT (sometimes referred to herein as 5G RAT, 5G NR RAT, or simply NR) . In certain deployments, the E-UTRAN may also implement NR RAT. In certain deployments, NG-RAN may also implement LTE RAT.
[0005] A base station used by a RAN may correspond to that RAN. One example of an E-UTRAN base station is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB) . One example of an NG-RAN base station is a next generation Node B (also sometimes referred to as a g Node B or gNB) .
[0006] A RAN provides its communication services with external entities through its connection to a core network (CN) . For example, E-UTRAN may utilize an Evolved Packet Core (EPC) while NG-RAN may utilize a 5G Core Network (5GC) .
[0007] Frequency bands for 5G NR may be separated into two or more different frequency ranges. For example, Frequency Range 1 (FR1) may include frequency bands operating in sub-6 gigahertz (GHz) frequencies, some of which are bands that may be used by previous standards, and may potentially be extended to cover new spectrum offerings from 410 megahertz (MHz) to 7125 MHz. Frequency Range 2 (FR2) may include frequency bands from 24.25 GHz to 52.6 GHz. Note that in some systems, FR2 may also include frequency bands from 52.6 GHz to 71 GHz (or beyond) . Bands in the millimeter wave (mmWave) range of FR2 may have smaller coverage but potentially higher available bandwidth than bands in FR1. Skilled persons will recognize these frequency ranges, which are provided by way of example, may change from time to time or from region to region.BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS
[0008] To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which that element is first introduced.
[0009] FIG. 1 illustrates an architecture for a 5G CN that operates with an untrusted non-3GPP access.
[0010] FIG. 2 illustrates an architecture for a 5G CN that operates with a TNAN.
[0011] FIG. 3 illustrates an architecture for sensing integration that operates with an untrusted non-3GPP access in a reference point representation.
[0012] FIG. 4 illustrates a procedure for performing sensor registration via an untrusted non-3GPP access.
[0013] FIG. 5 illustrates a procedure for performing UE triggered sensing session establishment over non-3GPP access.
[0014] FIG. 6 illustrates a procedure for performing AF triggered sensing session establishment over non-3GPP access.
[0015] FIG. 7 illustrates a method of a sensing apparatus, according to embodiments discussed herein.
[0016] FIG. 8 illustrates a method of an N3IWF of a 3GPP wireless communication system, according to embodiments discussed herein.
[0017] FIG. 9 illustrates a method of a sensing apparatus, according to embodiments discussed herein.
[0018] FIG. 10 illustrates a method of an N3IWF of a 3GPP wireless communication system, according to embodiments discussed herein.
[0019] FIG. 11 illustrates a method of an SF-C of a 3GPP wireless communication system, according to embodiments discussed herein.
[0020] FIG. 12 illustrates a method of an AF of a 3GPP wireless communication system, according to embodiments discussed herein.
[0021] FIG. 13 illustrates a method of an NEF of a 3GPP wireless communication system, according to embodiments discussed herein.
[0022] FIG. 14 illustrates an example architecture of a wireless communication system, according to embodiments disclosed herein.
[0023] FIG. 15 illustrates a system for performing signaling between a wireless device and a RAN device connected to a core network of a CN device, according to embodiments disclosed herein.DETAILED DESCRIPTION
[0024] Various embodiments are described with regard to a UE. However, reference to a UE is merely provided for illustrative purposes. The example embodiments may be utilized with any electronic component that may establish a connection to a network and is configured with the hardware, software, and / or firmware to exchange information and data with the network. Therefore, the UE as described herein is used to represent any appropriate electronic component.
[0025] Aspects for various wireless communication systems (e.g., 5G, 5G-Advanced, etc. ) and the use of integrated sensing and communication (ISAC) are discussed herein.
[0026] Beneficial use cases and potential aspects for the enhancement of a wireless communication system in order to provide integrated communication and sensing services addressing different target verticals / applications (e.g. autonomous / assisted driving, vehicle to everything (V2X) , aviation / unmanned aerial vehicles (UAVs) , 3D map reconstruction, smart cities / factories, public sectors, healthcare, smart homes, maritime sector cases, etc. ) are identified. Various use cases focus on NR-based sensing, and could include non-3GPP type sensors (e.g., radar, camera, etc. ) . Further, certain use cases (e.g., a use case of a detection of a significant location change at a UE) might alternatively be satisfied using information already available in and EPC and Evolved Universal Terrestrial Radio Access (E-UTRA) . In such cases, the available information may be used.
[0027] Potential service requirements may be identified, for example in the areas of collection and reporting of the sensing information and / or exposure of the sensing capabilities and information to a third party.
[0028] Key performance indicators (KPIs) related to NR-based sensing (e.g., range, motion, velocity, etc. ) and performance requirements for transferring sensing related data may be identified.
[0029] Further, aspects related to security, privacy, regulatory requirements, and / or charging may be considered. Gap analysis between the identified potential functional targets and existing 5G system requirements or functionalities may be informative in such contexts.
[0030] In some cases for ISAC, it may be beneficial to introduce KPIs and 5G system functional requirements for wireless sensing services.
[0031] In some cases for ISAC, it may be beneficial to identify high level principles and use cases in order to define potential functional targets to enable a 3GPP system to support the needs of new and enhanced services and scenarios, based on, but not limited to, various international mobile telecommunications (IMT) -2030 usage scenarios.
[0032] It is contemplated that ISAC use facilitates new applications and services that use sensing capabilities. ISAC embodiments offer wide area multi-dimensional sensing that provides spatial information about unconnected objects as well as connected devices and their movements and surroundings.
[0033] System architecture enhancements for the support of ISAC may be considered. It may be beneficial to provide function enhancement, end to end service operations, and / or procedures to support ISAC with the considerations of a sub-set of use cases (e.g. commercial, automotive, public safety and emergency services) based on given requirements.
[0034] In this context, various aspects may be considered, including: architecture and function enhancements to support sensing; service authorization and revocation, including the investigation of mechanisms for authorization and revocation of sensing service requests from a service consumer; discovery and selection of sensing entities based on service requirements triggered by the service request and / or capability (s) of the sensing entities; sensing data and associated information collection and transport mechanisms for result calculations; mechanisms for providing sensing-associated information and result (including sensing result and contextual information) exposure, for one time, periodic and / or event based reporting; and / or configuration parameters / policy provisioning for the support of ISAC services.
[0035] It may be beneficial to define channel modelling aspects to support object detection and / or tracking (e.g., as discussed in 3GPP Technical Specification (TS) 22.137 v. 19.1.0 (March 2024) ) .
[0036] Further, the development of a common modelling framework capable of detecting and / or tracking various example objects and enabling them to be distinguished from unintended objects may be beneficial. Such example object may include: UAVs; humans (indoors and outdoors) ; automotive vehicles (e.g., outdoors) ; automated guided vehicles (e.g., in indoor factories) ; and / or objects creating hazards on roads / railways, with a minimum size dependent on frequency.
[0037] Various ISAC sensing modes should be considered for use, including, but not limited to, transmission reception point (TRP) -TRP bistatic sensing, TRP monostatic sensing, TRP-UE bistatic sensing, UE-TRP bistatic sensing, UE-UE bistatic sensing, and / or UE monostatic sensing.
[0038] With respect to sensing modes and / or frequencies for the above use cases, it may be beneficial to identify details of corresponding deployment scenarios.
[0039] It may be beneficial to define channel modeling details for sensing (e.g., by using 3GPP TS 38.901 v. 18.0.0 (March 2024) as a starting point) . This procedure can take into account relevant measurements, including: modeling of sensing targets and background environments, including, for example (if needed by the above us e cases) , radar cross-section (RCS) , mobility and clutter / scattering patterns, etc.; and spatial consistency aspects.
[0040] Under IMT-2030, the integration of sensing and communication (e.g., ISAC) is expected to enable a wide range of use cases. Moreover, sensing the physical surroundings together with an application of such data to appropriate artificial intelligence (AI) model could further enhance situational awareness aspects.
[0041] Various aspects related to performing sensing via wireless local area network (WLAN) signals are discussed in embodiments herein. For ISAC use cases, sensing via WLAN is applicable for multiple use cases. For example, multiple market segments and verticals where 5G-based sensing services can be beneficial for intelligent transportation, intruder detection in and surrounding smart home, weather monitoring, intelligent factories, health monitoring, etc., may be considered. For example, in use case of intruder detection in a smart home, it is introduced that sensing in smart home is one kind of the typical scenarios of indoor / local-area sensing.
[0042] Various network architectures for non-3GPP access are discussed herein. In some wireless communication systems, various types of non-3GPP access networks may be defined. These include, for example, untrusted non-3GPP access networks, trusted non-3GPP access networks, and wireline access networks.
[0043] FIG. 1 illustrates an architecture 100 for a 5G CN that operates with an untrusted non-3GPP access. The architecture 100 may be a non-roaming architecture.
[0044] The architecture 100 illustrates various entities of a home public land mobile network (HPLMN) 102 of a wireless communication system, including an access and mobility management function (AMF) 104, a non-3GPP-internetworking function (N3IWF) 106, a user plane function (UPF) 108, and a session management function (SMF) 110.
[0045] One function of the architecture 100 is to provide a UE 112 with access to a data network 114. The UE 112 can connect to the HPLMN 102 (and ultimately to the data network 114) through a 3GPP access 116.
[0046] The UE 112 may additionally and / or alternatively be able to connect to the HPLMN 102 (and ultimately to the data network 114) through an untrusted non-3GPP access 118 of a non-3GPP network 120 that is available at the UE 112 (e.g., an available WLAN) . The untrusted non-3GPP access 118 may be connected with the HPLMN 102 via a N3IWF 106.
[0047] As shown, the UE 112 communicates with the AMF 104 through the 3GPP access 116 via an N1 interface. Further, the UE 112 communicates with the N3IWF 106 on a NWu interface. The UE 112 communicates with the AMF 104 through the N3IWF 106 on an N1 interface.
[0048] As illustrated, the architecture 100 uses further interfaces between its various elements, including: a Y1 interface between the UE 112 and the untrusted non-3GPP access 118, a Y2 interface between the untrusted non-3GPP access 118 and the N3IWF 106, an N2 interface between the 3GPP access 116 and the AMF 104, an N2 interface between the N3IWF 106 and the AMF 104, an N3 interface between the 3GPP access 116 and the UPF 110, an N3 interface between the N3IWF 106 and the UPF 110, an N11 interface between the AMF 104 and the SMF 108, an N4 interface between the SMF 108 and the UPF 110, and an N6 interface between the UPF 110 and the data network 114.
[0049] FIG. 2 illustrates an architecture 200 for a 5G CN that operates with a trusted non-3GPP access network (TNAN) 216. The architecture 200 may be a non-roaming architecture.
[0050] The architecture 200 illustrates various entities of an HPLMN 202 of a wireless communication system, including an AMF 204, an SMF 206, and a UPF 208.
[0051] One function of the architecture 200 is to provide a UE 210 with access to a data network 212. The UE 210 can connect to the HPLMN 202 (and ultimately to the data network 212) through a 3GPP access 214. The UE 210 can additionally and / or alternatively connect to the HPLMN 202 (and ultimately to the data network 212) via the TNAN 216. The TNAN 216 may be, for example, a WLAN that is operated by, known to, and / or otherwise trusted by the wireless communication system.
[0052] As illustrated, the TNAN 216 includes a trusted non-3GPP access point (TNAP) 218 and a trusted non-3GPP gateway function (TNGF) 220.
[0053] As shown, the UE 210 communicates with the AMF 204 through the 3GPP access 214 via an N1 interface. The UE 210 communicates with the TNAP 218 on a Yt interface. The UE 210 communicates with the TNGF 220 via the TNAP 218 on an NWt interface. Further, the UE 210 communicates with the AMF 204 via the TNAP 218 and the TNGF 220 on an N2 interface.
[0054] As illustrated, the architecture 200 uses further interfaces between its various elements, including: a Ta interface between the TNAP 218 and the TNGF 220, a Tn interface from and to the TNGF 220, an N2 interface between the 3GPP access 214 and the AMF 204, an N2 interface between the TNGF 220 and the AMF 204, an N11 interface between the AMF 204 and the SMF 206, an N4 interface between the SMF 206 and the UPF 208, an N3 interface between the TNGF 220 and the UPF 208, and an N6 interface between the UPF 208 and the data network 212.
[0055] Note that according to ISAC operation, there may be various types of sensors, including: 3GPP terminals with 3GPP access, 3GPP terminals with non-3GPP (e.g., WLAN) access, and / or non-3GPP sensors (for example, some use cases may focus on NR-based sensing and could include non-3GPP-type sensors, such as radar sensors, camera sensors, etc. ) .
[0056] It is common / practical that acquisition and / or transmission of sensing data from 3GPP terminals (e.g., UEs) occurs via WLAN in various use cases. Typical such use cases may include, for example, indoor use cases (such as smart home use cases, health monitoring use cases, etc. when, for example, the use case occurs indoors where cellular signals may be relatively weaker than WLAN signals. In some such use cases sensors can be 3GPP terminals with a non-3GPP access (e.g., WLAN access points (APs) ) that is used to ultimately access the 3GPP wireless communication system (e.g., 5G, 6G) network. Discussion herein thus relates to enhancements to current systems to support sensing data acquisition and transmission via non-3GPP access (e.g., WLAN) .
[0057] A terminal (e.g., a UE) having / acting as a sensor and that has 3GPP access via untrusted WLAN may exchange sensing control signaling with the 3GPP system and transmit sensing data to / through a CN of the 3GPP system via an N3IWF (e.g., in the manner that was described in relation to FIG. 1) .
[0058] A sensing function-control plane (SF-C) (also referred to herein as a “control plane sensing function” ) may operate in the control plane for purposes of WLAN sensing control. An N3IWF may interacts with an SF-C via an AMF, and sensing control signaling may be transmitted by the untrusted WLAN between sensors and the SF-C via the N3IWF and the AMF (e.g., transparently) .
[0059] A sensing function-user plane (SF-U) (also referred to herein as a “user plane sensing function” ) may operate in the user plane for purposes of WLAN sensing data transmission and processing. An N3IWF may interact with the SF-U directly when sensing data is transmitted by an untrusted WLAN from sensors to an SF-U via an N3IWF (e.g., transparently) .
[0060] Functionalities of N3IWF and AMF may be enhanced to support sensing control signaling and / or sensing data transmission.
[0061] Note that while architectures discussed / illustrated herein may explicitly show various network function (s) (e.g., including those directly connected to non-3GPP access and / or an SF-C and / or an SF-U) , it is contemplated that other network functions / elements may exist within the system.
[0062] Further, while various examples in this disclosure relate to cases for the use of N3IWF for untrusted WLAN connections, persons of ordinary skill will understand that aspects of these solutions may also apply to cases for trusted non-3GPP access networks that are connected to a CN (e.g., via a TNGF, as described in relation to FIG. 2) .
[0063] It is recognized that sensing data and signaling can be transmitted by both a 3GPP access and a non-3GPP access. For example, it is recognized that the sensing data transmission via the use of both access mechanisms / either access mechanism can be independent or coordinated as between the two access mechanisms
[0064] An example architecture for the use of integrated sensing (e.g., ISAC) via a WLAN network is now provided. FIG. 3 illustrates an architecture 300 for sensing integration that operates with an untrusted non-3GPP access in a reference point representation. The architecture 300 may be a non-roaming architecture.
[0065] The architecture 300 illustrates various entities of an HPLMN 302 of a wireless communication system. The architecture 300 may include an AMF 304, an N3IWF 306, an SMF 308, and a UPF 310 (e.g., as these were discussed in relation to FIG. 1) . The architecture 300 further includes, as illustrated, an SF-U 322, an SF-C 324, a unified data management (UDM) network function (NF) 326 (sometimes referred to more simply herein as a “UDM” ) , a network exposure function (NEF) / application function (AF) 328, a network data analytics function (NWDAF) , and a policy control function (PCF) 332.
[0066] One function of the architecture 300 is to provide a UE 312 with access to a data network 314. Another function of the architecture 300 is to provide a UE 312 with a mechanism for the communication of sensing data (e.g., ISAC sending data) with / into the HPLMN 302 (an in some cases, on to the data network 314) through the untrusted non-3GPP access 318.
[0067] The UE 312 can connect to the HPLMN 302 (and ultimately to the data network 314) through a 3GPP access 316.
[0068] The UE 312 may additionally and / or alternatively be able to connect to the HPLMN 302 (and ultimately to the data network 314) through an untrusted non-3GPP access 318 of a non-3GPP network 320 that is available at the UE 312 (e.g., an available WLAN) . The untrusted non-3GPP access 318 may be connected with the HPLMN 302 via a N3IWF 306.
[0069] A terminal (e.g., the UE 312) may act as a sensor operating in untrusted WLAN, and may accordingly transmit sensing control signaling and / or sensing data to the CN (the HPLMN 302) via the N3IWF 306.
[0070] The SF-C 324 is introduced in the control plane, and includes functionalities supporting WLAN sensing control. The N3IWF 306 interacts with the SF-C 324 via the AMF 304. Sensing control signaling is transmitted via untrusted WLAN between the sensors (e.g., the UE 312) and the SF-C 324 via the N3IWF 306 and the AMF 304 transparently.
[0071] The SF-C 324 interacts with the AMF 304, the PCF 332, the UDM 326, the NWDAF 330, and the NEF / AF 328 directly, as shown.
[0072] The SF-U 322 is introduced in the user plane, and includes functionalities that support WLAN sensing data transmission. The N3IWF 306 interacts with the SF-U 322 directly, when sensing data is transmitted via the untrusted WLAN from sensors (e.g., the UE 312) to the SF-U 322 via the N3IWF 306 (e.g., transparently) .
[0073] Sensing data (e.g., from the UE 312) is processed in the SF-U 322 as managed by the SF-C 324. The SF-U 322 feeds back sensing processing results (intermediate results or final results) to the N3IWF 306 and / or to the SF-C 324 (and from the SF-C 324 to other CN NFs) .
[0074] Accordingly, it is understood that functionalities of the N3IWF 306 and the AMF 304 are enhanced (e.g., as compared to the case discussed in relation to FIG. 1) in order for these entities to support sensing control signaling and sensing data transmission as discussed.
[0075] As shown, the UE 312 communicates with the AMF 304 through the 3GPP access 316 via an N1 interface. Further, the UE 312 communicates with the N3IWF 306 on a NWu interface. The UE 312 communicates with the AMF 304 through the N3IWF 306 on an N1 interface.
[0076] As illustrated, the architecture 300 uses further interfaces between its various elements, including: a Y1 interface between the UE 312 and the untrusted non-3GPP access 318, a Y2 interface between the untrusted non-3GPP access 318 and the N3IWF 306, an N2 interface between the 3GPP access 316 and the AMF 304, an N2 interface between the N3IWF 306 and the AMF 304, an N3 interface between the 3GPP access 316 and the UPF 310, an N3 interface between the N3IWF 306 and the UPF 310, an N11 interface between the AMF 304 and the SMF 308, an N4 interface between the SMF 308 and the UPF 310, an N6 interface between the UPF 310 and the data network 314, an Nx interface between the SF-U 322 and the SF-C 324, an Ny interface between the AMF 304 and the SF-C 324, and an Nz interface between the N3IWF 306 and the SF-U 322.
[0077] Embodiments for functionalities of an SF-C are now discussed. An SF-C may have various functionalities for sensing access and mobility management, including: functionalities for sensor registration management; functionalities for sensor connection management; functionalities for sensor mobility management; functionalities for sensor access authentication; functionalities for sensor access authorization; and / or functionalities for provisioning for external parameters for sensing;
[0078] An SF-C may have various functionalities for sensing session management (SSM) , including: functionalities for sensing session establishment, modification, and / or release; functionalities for a selection of and / or control of an SF-U; functionalities for the configuration of traffic steering at an SF-U to route sensing data to proper destination; functionalities for the termination of interfaces towards policy control functions for sensing; functionalities for provisioning external parameters for sensing; functionalities for initiating access network (AN) -specific sensing session management information (e.g., as sent via an AMF over an N2 interface to an AN) ; and / or functionalities for supporting interaction with an external data network for transport of signaling for sensing session authentication / authorization by the external data network.
[0079] An SF-C may have various functionalities for supporting sensing integration (e.g., ISAC integration) over WLAN, including: functionalities supporting the authentication of sensors connected over a N3IWF / a TNGF and / or functionalities for management of mobility, authentication, and separate security context state (s) of a sensor connected via a non-3GPP access or connected via a 3GPP access and a non-3GPP access simultaneously.
[0080] Some or all of these SF-C functionalities may be supported in a single instance of an SF-C.
[0081] Embodiments for functionalities of an SF-U are now discussed. An SF-U may include: functionalities for retrieving sensing data from a RAN and / or from sensors via a RAN; functionalities for sensing data processing (e.g., as depending on scenario) ; functionalities for transmitting a sensing data processing result to a CN and / or to a RAN; functionalities for a user plane part of sensing policy rule enforcement; and / or functionalities for sensing traffic usage reporting.
[0082] An SF-U may have various functionalities for supporting WLAN sensing. An SF-U may include: functionalities for retrieving sensing data from a WLAN via an N3IWF and / or from sensors (e.g., UEs) via a WLAN and a N3IWF; and functionalities for quality of service (QoS) handling for sensing.
[0083] Some or all of these SF-U functionalities may be supported in a single instance of a SF-U.
[0084] An AMF may have various functionalities for supporting sensing integration over WLAN. An AMF may include: functionalities for the support of NAS signaling with a sensor over a RAN / a N3IWF / a TNGF; functionalities for a transparent proxy for routing SSM messages; functionalities for providing transport for SSM messages between sensors and an SF-C; functionalities for sensor mobility event notification; and / or functionalities for the support of sensors connected over an N3IWF / a TNGF.
[0085] Note that these AMF functionalities imply corresponding behaviors for sensing not only at a N3IWF but also for sensing at a RAN and / or a TNGF.
[0086] An N3IWF may have various functionalities for supporting sensing integration over WLAN. An N3IWF may include: functionalities for the support of an internet protocol security (IPsec) tunnel establishment with a sensor; functionalities for relaying uplink (UL) and downlink (DL) control-plane non-access stratum (NAS) signaling between a sensor and an AMF / an SF-C; functionalities for handling N2 signaling from an SF-C (as relayed by an AMF) related to sensing data transmission; functionalities for relaying UL and DL sensing data between a sensor and SF-U; functionalities for enforcing QoS for sensing; functionalities for sensing data marking (considering optional functionality (s) depending on specific use cases) ; and / or functionalities for supporting AMF selection for sensing.
[0087] Embodiments for sensor registration for sensing over untrusted non-3GPP access are now discussed. FIG. 4 illustrates a procedure 400 for performing sensor registration 402 via an untrusted non-3GPP access (e.g., WLAN) . Embodiments of the procedure 400 use a UE / sensor 404, a RAN 406, a N3IWF 408, an AUSF 410, a UDM 412, an AMF 414, and / or an SF-C 416, as illustrated. The UE / sensor 404 may be an example of a “sensing apparatus” as discussed herein.
[0088] Preliminarily, the UE / sensor 404 connects to the untrusted non-3GPP access network (e.g., a WLAN) with any appropriate authentication procedure and is assigned an internet protocol (IP) address. The UE / sensor 404 proceeds with the establishment of an IPsec security association (SA) for sensing signaling with a selected N3IWF 408. Corresponding to such cases, an AN message from the UE / sensor 404 to the N3IWF 408 for registration may include indications for the UE / sensor 404, such as a capability of the UE / sensor 404 and / or a type of the UE / sensor 404. For example, this AN message may include: AN parameters; a registration request; one or more security parameters; and / or one or more sensor indications, including a sensor capability identifier (ID) , a sensor type ID, and / or other (optional) parameters.
[0089] Then, the N3IWF 408 may perform AMF selection 418, as illustrated. The N3IWF 408 may select an AMF 414 based on any received AN parameters and / or a local policy. The AMF selection functionality in the N3IWF 408 for sensing use cases may consider sensing indications as factors for selecting an AMF set, which means the N3IWF 408 should select an enhanced AMF supporting sensing (note that the AMF 414 of the procedure 400 may be understood to be such an enhanced AMF) .
[0090] Various options for using one or more of the AMF 414, the AUSF 410, the UDM 412, the SF-C 416 for performing sensor authentication 420 are now discussed. In a first option, the AMF 414 decides to authenticate the UE / sensor 404 by invoking the AUSF 410. The AUSF 410 executes the authentication of the UE / sensor 404, selects the UDM 412 and subsequently receives authentication data from UDM 412.
[0091] In a second option, the SF-C 416 decides to authenticate the UE / sensor 404 by invoking the AUSF 410. The AUSF 410 executes the authentication of the UE / sensor 404, selects the UDM 412, and subsequently receives authentication data from UDM 412.
[0092] In a third option, the SF-C 416 decides to authenticate the UE / sensor 404, executes the authentication of the UE / sensor 404, selects the UDM 412, and receives authentication data from the UDM 412.
[0093] In a fourth option, the SF-C 416 decides to authenticate the UE / sensor 404 and then executes the authentication of the UE / sensor 404 according to the authentication data storage in SF-C 416.
[0094] The SF-C 416 may register its capability (s) in a networking repository function (NRF) by sending an SF-C register request message to the NRF. This message informs the NRF of the profile of the SF-C when the SF-C becomes operative for the first time. The NRF may acknowledge the NF registration as accepted (e.g., via an Nnrf_NFManagement_NFRegister response) .
[0095] The SF-C 416 may update its capability (s) in an NRF by sending an SF-C update request message to the NRF to inform the NRF of its updated NF profile (e.g., when triggered by a scaling operation) .
[0096] Embodiments for UE triggered sensing session establishment over a non-3GPP access (e.g., WLAN) are now discussed. FIG. 5 illustrates a procedure 500 for performing UE triggered sensing session establishment over non-3GPP access (e.g., WLAN) . Embodiments of the procedure 500 use a UE / sensor 502, a N3IWF 504, an AMF 506, an SF-C 508, an SF-U 510, and a PCF 512, as illustrated. The UE / sensor 502 may be an example of a “sensing apparatus” as discussed herein.
[0097] As illustrated, the UE / sensor 502 sends a sensing session establishment request message 514 to the N3IWF 504 via an IPsec SA for NAS signaling. The N3IWF 504 transparently forwards this information to the AMF 506 in the 5GC in a N2 sensing session establishment request message 516.
[0098] It may accordingly be understood that the UE / sensor 502 initiates the UE / sensor-requested sensing session establishment procedure by the transmission of a NAS message containing a sensing session establishment request within an N1 sensing session management container. The NAS message includes one or more of: a sensing session ID, a requested sensing session type, a requested destination of uploading sensing data (e.g., a requested data network name (DNN) ) , and an N1 sensing session management container. The N1 sensing session management container may include a sensing session establishment request.
[0099] The sensing session establishment request carries one or more of: sensing QoS requirements (e.g., sensing resolution, sensing accuracy, data rate, etc. ) and may carry other sensing parameters depending on a specific use case (e.g., a duration, target area information, sensing target information, sensing node information, etc. ) .
[0100] Upon receiving the N2 sensing session establishment request message 516, the AMF 506 selects 518 an SF-C (the procedure 500 assumes that the SF-C 508 is selected) according to the requirements of the UE / sensor 502. The AMF 506 then initiates the creation of a sensing session management context with the SF-C 508 by sending the SF-C 508 a sensing session management context creation request message 520. The SF-C 508 responds with a sensing session management context creation response message 522, confirming the acceptance of the creation of the sensing session management context.
[0101] Optionally, the SF-C 508 performs a policy interaction 524 with the PCF 512 to retrieve applicable policy information for the sensing. Note that this policy interaction 524 is labeled as optional because in at least some embodiments, the SF-C 508 may instead apply a local policy that is known / stored at the SF-C 508, without performing the policy interaction 524 with the PCF 512.
[0102] After the sensing session management context is created, the SF-C 508 selects 526 an SF-U (the procedure 500 assumes that the SF-U 510 is selected) . The SF-C 508 then initiates the establishment of Nx sensing session with the selected SF-U 510 by sending the SF-U 510 an Nx sensing session establishment request message 528. The SF-U 510 confirms its acceptance of the establishment of the Nx sensing session with a responsive Nx sensing session establishment response message 530.
[0103] Once the Nx sensing session is established, the SF-C 508 sends the AMF 506 a sensing message transfer configuration message 532 (e.g., an Namf_Sensing_N1N2MessageTransfer message) over an Ny interface between the SF-C 508 and the AMF 506. The sensing message transfer configuration message 532 may carry a sensing session ID.
[0104] The sensing message transfer configuration message 532 may carry N2 sensing session management information, which may include one or more of: a sensing session ID; sensing QoS flow indicator (s) (QFI (s) ) , sensing QoS profile (s) , and / or CN tunnel information for sensing, etc. The CN tunnel information for sensing may correspond to the core network address (es) of an Nz tunnel corresponding to the sensing session.
[0105] The sensing message transfer configuration message 532 may carry an N1 sensing session management container. The N1 sensing session management container may include a sensing session establishment accept indication that includes one or more of: a requested destination for uploading sensing data (e.g., a requested DNN) , an allocated address, etc.
[0106] Then, the AMF 506 sends a N2 sensing session request message 534 to the N3IWF 504 N3IWF to establish access resources for the sensing session.
[0107] The N3IWF 504 then performs child IPsec SA establishment 536 with the UE / sensor 502. The N3IWF 504 establishes at least one child IPsec SA for the sensing session with the UE / sensor 502. Note that if, based on contents of the N2 sensing session request message 534, the N3IWF 504 determines to establish multiple child IPsec SAs for the sensing session, then multiple (more than one) child IPsec SAs are established as part of the child IPsec SA establishment 536.
[0108] The N3IWF 504 sends a sensing session establishment accept message 538 to the UE / sensor 502, indicating that the sensing session is accepted. The N3IWF 504 also sends a sensing session response message 540 to the AMF 506, indicating the acceptance by the N3IWF 504 of the N2 sensing session request message 534.
[0109] The sensing session is now established. The UE / sensor 502 then proceeds to transmit sensing data 542 to the SF-U 510 via the N3IWF 504 (which forwards the sensing data 542 as the sensing data 544, as shown) . Note that a user plane between the UE / sensor 502 and the N3IWF 504 may be established using internet key exchange version 2 (IKEv2) signaling (e.g., instead of radio resource control (RRC) signaling) in at least some cases..
[0110] Then, sensing data processing 546 is carried out at the SF-U 510 and / or the SF-C 508, according to sensing policies. If the sensing data processing 546 is executed in the SF-U 510 (or at least partially in SF-U 510) , the SF-U 510 reports its processing results to the SF-C 508.
[0111] The SF-C 508 executes 548 the sensing processing results. For example, the SF-C 508 may transmit the sensing processing results to sensing service consumers (e.g., an NWDAF, a PCF, an AF, a RAN, a UE, etc. ) .
[0112] Embodiments for AF triggered sensing session establishment over a non-3GPP access (e.g., WLAN) are now discussed. FIG. 6 illustrates a procedure 600 for performing AF 618 triggered sensing session establishment over non-3GPP access (e.g., WLAN) . Embodiments of the procedure 600 use a UE / sensor 602, a N3IWF 604, an AMF 606, an SF-C 608, an SF-U 610, a PCF 612, a UDM 614, a NEF 616, and an AF 618, as illustrated. The UE / sensor 602 may be an example of a “sensing apparatus” as discussed herein.
[0113] First, the AF 618 determines 620 the need to trigger a sensing session. Then, the AF 618 sends a sensing trigger request message 622 to the NEF 616. For example, the sensing trigger request message 622 may be processed by an Nnef_Trigger_Delivery service of the NEF 616 (e.g., in cases where the Nnef_Trigger_Delivery service may be particularly configured to support this sensing trigger) .
[0114] The sensing trigger request message 622 may carry an AF identifier, a trigger type (e.g., for sensing session establishment) , a requested sensing session type, a requested destination of uploading sensing data (e.g., a requested DNN) , sensing QoS requirements (e.g., a sensing resolution, a sensing accuracy, a data rate, etc. ) , and / or other sensing parameters, depending on specific use case (e.g., duration, target area information, sensing target information, sensing node information, etc. ) .
[0115] The NEF 616 may perform a sensing service authorization procedure 624 to check that the AF 618 is authorized to send trigger requests The NEF 616 may check that the AF 618 has not exceeded a sensing trigger request limit (e.g., a maximum number of trigger submissions / requests allowed and / or a maximum allowed rate for such trigger submissions / requests) over Nnef. If one or more of these checks fails, the NEF 616 may send the AF 618 a response message having a cause value indicating the reason for failure / the failure condition and the flow of the procedure 600 stops. Otherwise, the flow continues (this is the case illustrated in the procedure 600) .
[0116] In some options, authorization information used by the NEF 616 to check the authorization of the service awareness request by the AF 618 as part of the sensing service authorization procedure 624 is stored locally in the NEF 616.
[0117] In some options, the authorization information used by the NEF 616 to check the authorization of the service awareness request by the AF 618 is stored in the UDM 614. In such cases, the NEF 616 communicates, as part of the sensing service authorization procedure 624, with the UDM 614. In the sensing service authorization procedure 624, authorization data for the AF 618 is received from the UDM 614. The NEF 616 then checks the authorization of service awareness of the AF 618 using the data received from the UDM 614.
[0118] The NEF 616 then sends a sensing trigger request message 626 to the SF-C 608. In response, the SF-C 608 sends a submit trigger confirmation message 628 to the NEF 616.
[0119] One purpose of the submit trigger confirmation message 628 to trigger a confirmation to the AF 618 that the submission of sensing trigger has been accepted by the SF-C 608. Accordingly, upon receiving the submit trigger confirmation message 628, the NEF 616 sends the AF 618 a trigger delivery response message 630 (e.g., an Nnef_Trigger_Delivery response message) to the AF 618 that indicates that the sensing trigger request message 622 has been accepted for delivery to the UE / sensor 602.
[0120] In response to the sensing trigger request message 626, the SF-C 608 selects 632 an AMF according to the payload of the sensing trigger request message 626 (the procedure 600 assumes that the AMF 606 is selected) . The SF-C 608 then sends a sensing trigger request message 634 to the AMF 606 via Ny. As illustrated, the AMF 606 forwards this information to the N3IWF 604 in another sensing trigger request message 636 on N2. The N3IWF 604 then passes this information to the UE / sensor 602 as part of a sensing trigger request and response procedure 638.
[0121] As shown, the sensing trigger request and response procedure 638 may occur over one or more signaling IPsce SA (s) . As part of the sensing trigger request and response procedure 638, the N3IWF 604 receives a response from the UE / sensor 602 and sends a corresponding message delivery report 640 indicating this response to the AMF 606. This information is sent to the NEF 616 in the message delivery report 642, as shown.
[0122] In response to the message delivery report 642, the NEF 616 provides a trigger delivery notification message 644 (e.g., an Nnef_Trigger_DeliveryNotify message) to the AF 618. The trigger delivery notification message 644 includes a delivery report indicating a trigger delivery outcome corresponding to the sensing trigger request message 622. For example, the trigger delivery notification message 644 may indicate that the sensing session corresponding to the sensing trigger request message 622 was successfully triggered, that the result is unknown, and / or that or triggering of the sensing session failed (and in some such cases, a reason for the failure is indicated) . The procedure 600 assumes the successful case.
[0123] In response to the trigger received as part of the sensing trigger request and response procedure 638, the UE / sensor 602 triggers sensing session establishment via WLAN. This procedure takes into consideration the content of the trigger payload within the sensing trigger request and response procedure 638.
[0124] FIG. 7 illustrates a method 700 of a sensing apparatus, according to embodiments discussed herein. The method 700 includes connecting 702 to a WLAN access point. The method 700 further includes performing 704 a registration of the sensing apparatus with a 3GPP wireless communication system via the WLAN access point, wherein the registration comprises sending an AN message to an N3IWF of the 3GPP wireless communication system that indicates sensing functionality information for the sensing apparatus, and wherein the registration results in an IPsec SA between the sensing apparatus and the N3IWF. The method 700 further includes sending 706, after the registration of the sensing apparatus with the 3GPP wireless communication system is complete, sensing data generated by the sensing apparatus that is for SF-U of the 3GPP wireless communication system to the N3IWF.
[0125] In some embodiments of the method 700, the sensing functionality information for the sensing apparatus comprises a sensor capability ID.
[0126] In some embodiments of the method 700, the sensing functionality information for the sensing apparatus comprises a sensor type ID.
[0127] In some embodiments of the method 700, the sensing apparatus comprises a UE.
[0128] FIG. 8 illustrates a method 800 of an N3IWF of a 3GPP wireless communication system, according to embodiments discussed herein. The method 800 includes performing 802 a registration of a sensing apparatus that communicates with the N3IWF via a WLAN access point with the 3GPP wireless communication system, wherein the registration results in an IPsec SA between the sensing apparatus and the N3IWF, and wherein the registration comprises receiving, from the sensing apparatus, an AN message that indicates sensing functionality information for the sensing apparatus and selecting an AMF of the 3GPP wireless communication system to use with the sensing apparatus based on the sensing functionality information. The method 800 further includes receiving 804, after the registration of the sensing apparatus with the 3GPP wireless communication system is complete, sensing data generated from the sensing apparatus.
[0129] In some embodiments of the method 800, the sensing functionality information for the sensing apparatus comprises a sensor capability ID.
[0130] In some embodiments of the method 800, the sensing functionality information for the sensing apparatus comprises a sensor type ID.
[0131] In some embodiments of the method 800, the sensing apparatus comprises a UE.
[0132] FIG. 9 illustrates a method 900 of a sensing apparatus, according to embodiments discussed herein. The method 900 includes sending 902, via a WLAN access point, to a n N3IWF of a 3GPP wireless communication system, using an IPsec SA between the sensing apparatus and the N3IWF, a NAS message comprising a sensing session establishment request message. The method 900 further includes receiving 904, from the N3IWF, in response to the NAS message, a first identification of a first child IPsec SA for a sensing session. The method 900 further includes sending 906 first sensing data of the sensing session that is for an SF-U to the N3IWF using the first child IPsec SA.
[0133] In some embodiments, the method 900 further includes receiving, from the N3IWF, in response to the NAS message, a second identification of a second child IPsec SA for the sensing session; and sending second sensing data of the sensing session that is for the SF-U to the N3IWF using the second child IPsec SA.
[0134] In some embodiments of the method 900, the NAS message further comprises one or more of: a sensing session ID for the sensing session; a requested sensing session type; and a requested destination for the first sensing data.
[0135] In some embodiments of the method 900, the sensing session establishment request message comprises one or more of: QoS requirements for the sensing session; a duration for the sensing session; target area information for the sensing session; and sensing node information for the sensing apparatus.
[0136] In some embodiments of the method 900, the sensing apparatus comprises a UE.
[0137] FIG. 10 illustrates a method 1000 of an N3IWF of a 3GPP wireless communication system, according to embodiments discussed herein. The method 1000 includes receiving 1002, from a sensing apparatus that communicates with the N3IWF via a WLAN access point, using an IPsec SA between the sensing apparatus and the N3IWF, a NAS message comprising a sensing session establishment request message. The method 1000 further includes sending 1004, to an AMF of the 3GPP wireless communication system, the sensing session establishment request message. The method 1000 further includes receiving 1006, from the AMF, a sensing session request message. The method 1000 further includes sending 1008, to the sensing apparatus, in response to receiving the sensing session request message, a first identification of a first child IPsec SA for a sensing session. The method 1000 further includes receiving 1010 first sensing data of the sensing session that is for a SF-U from the sensing apparatus using the first child IPsec SA. The method 1000 further includes sending 1012 the first sensing data to the SF-U.
[0138] In some embodiments, the method 1000 further includes sending, to the sensing apparatus, in response to the NAS message, a second identification of a second child IPsec SA for the sensing session; receiving second sensing data of the sensing session that is for the SF-U from the sensing apparatus using the second child IPsec SA; and sending the second sensing data to the SF-U.
[0139] In some embodiments of the method 1000, the NAS message further comprises one or more of: a sensing session ID for the sensing session; a requested sensing session type; and a requested destination for the first sensing data.
[0140] In some embodiments of the method 1000, the sensing session establishment request message comprises one or more of: QoS requirements for the sensing session; a duration for the sensing session; target area information for the sensing session; and sensing node information for the sensing apparatus.
[0141] In some embodiments of the method 1000, the sensing apparatus comprises a UE.
[0142] FIG. 11 illustrates a method 1100 of an SF-C of a 3GPP wireless communication system, according to embodiments discussed herein. The method 1100 includes receiving 1102, from an access an AMF of the 3GPP wireless communication system, a sensing session management context creation request message. The method 1100 further includes sending 1104, to the AMF, a sensing session management context creation response message indicating that the SF-C accepts a creation of a sensing session management context between the SF-C and the AMF. The method 1100 further includes selecting 1106 an SF-U of the 3GPP wireless communication system for use with a sensing session between the SF-C and the SF-U. The method 1100 further includes sending 1108, to the SF-U, a sensing session establishment request message for the sensing session. The method 1100 further includes receiving 1110, from the SF-U, a sensing session establishment response message indicating that the SF-U accepts an establishment of the sensing session. The method 1100 further includes sending 1112, to the AMF, in response to the establishment of the sensing session between the SF-C and the SF-U, a sensing message transfer configuration message.
[0143] In some embodiments of the method 1100, the sensing message transfer configuration message comprises a sensing session ID for the sensing session.
[0144] In some embodiments of the method 1100, the sensing message transfer configuration message comprises N2 sensing session management information for an N2 interface between the AMF and an N3IWF of the 3GPP wireless communication system, the N2 sensing session management information comprising one or more of: a sensing session ID for the sensing session; a sensing QFI for the sensing session; a sensing QoS profile for the sensing session; and CN tunnel information for the sensing session.
[0145] In some embodiments of the method 1100, the sensing message transfer configuration message comprises N1 sensing session management information for an N1 interface between the AMF and a sensing apparatus that communicates with the 3GPP wireless communication system via a WLAN access point, the N1 sensing session management information comprising one or more of: an indication that the establishment of the sensing session is accepted; a requested destination for uploading sensing data of the sensing session; and an allocated address for the sensing apparatus. In some such embodiments, the sensing apparatus comprises a UE.
[0146] FIG. 12 illustrates a method 1200 of an AF of a 3GPP wireless communication system, according to embodiments discussed herein. The method 1200 includes determining 1202 to trigger a sensing session for collecting sensing data from a sensing apparatus that communicates with 3GPP wireless communication system via a WLAN access point. The method 1200 further includes sending 1204, to an NEF of the 3GPP wireless communication system, a sensing trigger request message configured to trigger the sensing session. The method 1200 further includes receiving 1206, from the NEF, a trigger delivery response message indicating that the sensing trigger request message was accepted for delivery to the sensing apparatus. The method 1200 further includes receiving 1208, from the NEF, a trigger delivery notification message indicating that the sensing trigger request message was successfully delivered to the sensing apparatus.
[0147] In some embodiments of the method 1200, the sensing trigger request message comprises one or more of: an ID for the AF; a trigger type; a requested sensing type; a requested destination for uploading the sensing data; QoS requirements for the sensing session; a duration for the sensing session; target area information for the sensing session; sensing target information for the sensing session; and sensing node information for the sensing apparatus.
[0148] In some embodiments of the method 1200, the sensing apparatus comprises a UE.
[0149] FIG. 13 illustrates a method 1300 of an NEF of a 3GPP wireless communication system, according to embodiments discussed herein. The method 1300 includes receiving 1302, from an AF of the 3GPP wireless communication system, a sensing trigger request message configured to trigger a sensing session for collecting sensing data from a sensing apparatus that communicates with 3GPP wireless communication system via a WLAN access point. The method 1300 further includes determining 1304 that the AF is authorized to send the sensing trigger request message and that the AF has not exceeded a sensing trigger request limit. The method 1300 further includes sending 1306 the sensing trigger request message to an SF-C of the 3GPP wireless communication system. The method 1300 further includes receiving 1308, from the SF-C, a trigger submission confirmation indicating that the sensing trigger request message is accepted by the SF-C. The method 1300 further includes sending 1310, to the AF, a trigger delivery response message indicating that the sensing trigger request message was accepted for delivery to the sensing apparatus. The method 1300 further includes receiving 1312, from an AMF of the 3GPP wireless communication system, a message delivery report indicating the sensing trigger request message was successfully delivered to the sensing apparatus. The method 1300 further includes sending 1314, to the AF, a trigger delivery notification message indicating that the sensing trigger request message was successfully delivered to the sensing apparatus.
[0150] In some embodiments of the method 1300, the sensing trigger request limit comprises a maximum sensing trigger request number.
[0151] In some embodiments of the method 1300, the sensing trigger request limit comprises a maximum sensing trigger request rate.
[0152] In some embodiments of the method 1300, the determining that the AF is authorized to send the sensing trigger request message comprises checking authorization information for the AF that is stored at the NEF.
[0153] In some embodiments of the method 1300, the determining that the AF is authorized to send the sensing trigger request message comprises: receiving, from a UDM NF of the 3GPP wireless communication system, authorization information for the AF; and checking the authorization information for the AF received from the UDM NF.
[0154] FIG. 14 illustrates an example architecture of a wireless communication system 1400, according to embodiments disclosed herein. The following description is provided for an example wireless communication system 1400 that operates in conjunction with the LTE system standards and / or 5G or NR system standards as provided by 3GPP technical specifications.
[0155] As shown by FIG. 14, the wireless communication system 1400 includes UE 1402 and UE 1404 (although any number of UEs may be used) . In this example, the UE 1402 and the UE 1404 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) , but may also comprise any mobile or non-mobile computing device configured for wireless communication.
[0156] The UE 1402 and UE 1404 may be configured to communicatively couple with a RAN 1406. In embodiments, the RAN 1406 may be NG-RAN, E-UTRAN, etc. The UE 1402 and UE 1404 utilize connections (or channels) (shown as connection 1408 and connection 1410, respectively) with the RAN 1406, each of which comprises a physical communications interface. The RAN 1406 can include one or more base stations (such as base station 1412 and base station 1414) that enable the connection 1408 and connection 1410.
[0157] In this example, the connection 1408 and connection 1410 are air interfaces to enable such communicative coupling, and may be consistent with RAT (s) used by the RAN 1406, such as, for example, an LTE and / or NR.
[0158] In some embodiments, the UE 1402 and UE 1404 may also directly exchange communication data via a sidelink interface 1416. The UE 1404 is shown to be configured to access an access point (shown as AP 1418) via connection 1420. By way of example, the connection 1420 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 1418 may comprise a router. In this example, the AP 1418 may be connected to another network (for example, the Internet) without going through a CN 1424.
[0159] In embodiments, the UE 1402 and UE 1404 can be configured to communicate using orthogonal frequency division multiplexing (OFDM) communication signals with each other or with the base station 1412 and / or the base station 1414 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an orthogonal frequency division multiple access (OFDMA) communication technique (e.g., for downlink communications) or a single carrier frequency division multiple access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications) , although the scope of the embodiments i s not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.
[0160] In some embodiments, all or parts of the base station 1412 or base station 1414 may be implemented as one or more software entities running on server computers as part of a virtual network. In addition, or in other embodiments, the base station 1412 or base station 1414 may be configured to communicate with one another via interface 1422. In embodiments where the wireless communication system 1400 is an LTE system (e.g., when the CN 1424 is an EPC) , the interface 1422 may be an X2 interface. The X2 interface may be defined between two or more base stations (e.g., two or more eNBs and the like) that connect to an EPC, and / or between two eNBs connecting to the EPC. In embodiments where the wireless communication system 1400 is an NR system (e.g., when CN 1424 is a 5GC) , the interface 1422 may be an Xn interface. The Xn interface is defined between two or more base stations (e.g., two or more gNBs and the like) that connect to 5GC, between a base station 1412 (e.g., a gNB) connecting to 5GC and an eNB, and / or between two eNBs connecting to 5GC (e.g., CN 1424) .
[0161] The RAN 1406 is shown to be communicatively coupled to the CN 1424. The CN 1424 may comprise one or more network elements 1426, which are configured to offer various data and telecommunications services to customers / subscribers (e.g., users of UE 1402 and UE 1404) who are connected to the CN 1424 via the RAN 1406. The components of the CN 1424 may be implemented in one physical device or separate physical devices including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) .
[0162] In embodiments, the CN 1424 may be an EPC, and the RAN 1406 may be connected with the CN 1424 via an S1 interface 1428. In embodiments, the S1 interface 1428 may be split into two parts, an S1 user plane (S1-U) interface, which carries traffic data between the base station 1412 or base station 1414 and a serving gateway (S-GW) , and the S1-MME interface, which is a signaling interface between the base station 1412 or base station 1414 and mobility management entities (MMEs) .
[0163] In embodiments, the CN 1424 may be a 5GC, and the RAN 1406 may be connected with the CN 1424 via an NG interface 1428. In embodiments, the NG interface 1428 may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the base station 1412 or base station 1414 and a user plane function (UPF) , and the S1 control plane (NG-C) interface, which is a signaling interface between the base station 1412 or base station 1414 and access and mobility management functions (AMFs) .
[0164] Generally, an application server 1430 may be an element offering applications that use internet protocol (IP) bearer resources with the CN 1424 (e.g., packet switched data services) . The application server 1430 can also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc. ) for the UE 1402 and UE 1404 via the CN 1424. The application server 1430 may communicate with the CN 1424 through an IP communications interface 1432.
[0165] FIG. 15 illustrates a system 1500 for performing signaling 1534 between a wireless device 1502 and a RAN device 1518 connected to a core network of a CN device 1536, according to embodiments disclosed herein. The system 1500 may be a portion of a wireless communications system as herein described. The wireless device 1502 may be, for example, a UE of a wireless communication system. The RAN device 1518 may be, for example, a base station (e.g., an eNB or a gNB) of a wireless communication system. The CN device 1536 may be one or more devices making up a CN, as described herein.
[0166] The wireless device 1502 may include one or more processor (s) 1504. The processor (s) 1504 may execute instructions such that various operations of the wireless device 1502 are performed, as described herein. The processor (s) 1504 may include one or more baseband processors implemented using, for example, a central processing unit (CPU) , a digital signal processor (DSP) , an application specific integrated circuit (ASIC) , a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.
[0167] The wireless device 1502 may include a memory 1506. The memory 1506 may be a non-transitory computer-readable storage medium that stores instructions 1508 (which may include, for example, the instructions being executed by the processor (s) 1504) . The instructions 1508 may also be referred to as program code or a computer program. The memory 1506 may also store data used by, and results computed by, the processor (s) 1504.
[0168] The wireless device 1502 may include one or more transceiver (s) 1510 that may include radio frequency (RF) transmitter circuitry and / or receiver circuitry that use the antenna (s) 1512 of the wireless device 1502 to facilitate signaling (e.g., the signaling 1534) to and / or from the wireless device 1502 with other devices (e.g., the network CN device 1536) according to corresponding RATs.
[0169] The wireless device 1502 may include one or more antenna (s) 1512 (e.g., one, two, four, or more) . For embodiments with multiple antenna (s) 1512, the wireless device 1502 may leverage the spatial diversity of such multiple antenna (s) 1512 to send and / or receive multiple different data streams on the same time and frequency resources. This behavior may be referred to as, for example, multiple input multiple output (MIMO) behavior (referring to the multiple antennas used at each of a transmitting device and a receiving device that enable this aspect) . MIMO transmissions by the wireless device 1502 may be accomplished according to precoding (or digital beamforming) that is applied at the wireless device 1502 that multiplexes the data streams across the antenna (s) 1512 according to known or assumed channel characteristics such that each data stream is received with an appropriate signal strength relative to other streams and at a desired location in the spatial domain (e.g., the location of a receiver associated with that data stream) . Certain embodiments may use single user MIMO (SU-MIMO) methods (where the data streams are all directed to a single receiver) and / or multi user MIMO (MU-MIMO) methods (where individual data streams may be directed to individual (different) receivers in different locations in the spatial domain) .
[0170] In certain embodiments having multiple antennas, the wireless device 1502 may implement analog beamforming techniques, whereby phases of the signals sent by the antenna (s) 1512 are relatively adjusted such that the (joint) transmission of the antenna (s) 1512 can be directed (this is sometimes referred to as beam steering) .
[0171] The wireless device 1502 may include one or more interface (s) 1514. The interface (s) 1514 may be used to provide input to or output from the wireless device 1502. For example, a wireless device 1502 that is a UE may include interface (s) 1514 such as microphones, speakers, a touchscreen, buttons, and the like in order to allow for input and / or output to the UE by a user of the UE. Other interfaces of such a UE may be made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver (s) 1510 / antenna (s) 1512 already described) that allow for communication between the UE and other devices and may operate according to known protocols (e.g., and the like) .
[0172] The wireless device 1502 may include a sensing module 1516. The sensing module 1516 may be implemented via hardware, software, or combinations thereof. For example, the sensing module 1516 may be implemented as a processor, circuit, and / or instructions 1508 stored in the memory 1506 and executed by the processor (s) 1504. In some examples, the sensing module 1516 may be integrated within the processor (s) 1504 and / or the transceiver (s) 1510. For example, the sensing module 1516 may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor (s) 1504 or the transceiver (s) 1510.
[0173] The sensing module 1516 may be used for various aspects of the present disclosure, for example, aspects of FIG. 7 and / or FIG. 9. For example, the sensing module 1516 may configure the wireless device 1502 to connect to a WLAN access point; perform a registration of the sensing apparatus with a 3GPP wireless communication system via the WLAN access point, wherein the registration comprises sending an AN message to an N3IWF of the 3GPP wireless communication system that indicates sensing functionality information for the sensing apparatus, and wherein the registration results in an IPsec SA between the sensing apparatus and the N3IWF; send, after the registration of the sensing apparatus with the 3GPP wireless communication system is complete, sensing data generated by the sensing apparatus that is for SF-U of the 3GPP wireless communication system to the N3IWF.
[0174] In another example, the sensing module 1516 may configure the wireless device 1502 to send, via a WLAN access point, to a n N3IWF of a 3GPP wireless communication system, using an IPsec SA between the sensing apparatus and the N3IWF, a NAS message comprising a sensing session establishment request message; receive, from the N3IWF, in response to the NAS message, a first identification of a first child IPsec SA for a sensing session; and send first sensing data of the sensing session that is for an SF-U to the N3IWF using the first child IPsec SA.
[0175] The RAN device 1518 may include one or more processor (s) 1520. The processor (s) 1520 may execute instructions such that various operations of the RAN device 1518 are performed, as described herein. The processor (s) 1520 may include one or more baseband processors implemented using, for example, a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.
[0176] The RAN device 1518 may include a memory 1522. The memory 1522 may be a non-transitory computer-readable storage medium that stores instructions 1524 (which may include, for example, the instructions being executed by the processor (s) 1520) . The instructions 1524 may also be referred to as program code or a computer program. The memory 1522 may also store data used by, and results computed by, the processor (s) 1520.
[0177] The RAN device 1518 may include one or more transceiver (s) 1526 that may include RF transmitter circuitry and / or receiver circuitry that use the antenna (s) 1528 of the RAN device 1518 to facilitate signaling (e.g., the signaling 1534) to and / or from the RAN device 1518 with other devices (e.g., the wireless device 1502) according to corresponding RATs.
[0178] The RAN device 1518 may include one or more antenna (s) 1528 (e.g., one, two, four, or more) . In embodiments having multiple antenna (s) 1528, the RAN device 1518 may perform MIMO, digital beamforming, analog beamforming, beam steering, etc., as has been described.
[0179] The RAN device 1518 may include one or more interface (s) 1530. The interface (s) 1530 may be used to provide input to or output from the RAN device 1518. For example, a RAN device 1518 that is a base station may include interface (s) 1530 made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver (s) 1526 / antenna (s) 1528 already described) that enables the base station to communicate with other equipment in a core network, and / or that enables the base station to communicate with external networks, computers, databases, and the like for purposes of operations, administration, and maintenance of the base station or other equipment operably connected thereto.
[0180] The RAN device 1518 may include a sensing module 1532. The sensing module 1532 may be implemented via hardware, software, or combinations thereof. For example, the sensing module 1532 may be implemented as a processor, circuit, and / or instructions 1524 stored in the memory 1522 and executed by the processor (s) 1520. In some examples, the sensing module 1532 may be integrated within the processor (s) 1520 and / or the transceiver (s) 1526. For example, the sensing module 1532 may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor (s) 1520 or the transceiver (s) 1526.
[0181] The sensing module 1532 may be used for various aspects of the present disclosure.
[0182] The RAN device 1518 may communicate with the CN device 1536 via the interface 1548.
[0183] The CN device 1536 may include one or more processor (s) 1538. The processor (s) 1538 may execute instructions such that various operations of the CN device 1536 are performed, as described herein. The processor (s) 1538 may include one or more baseband processors implemented using, for example, a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.
[0184] The CN device 1536 may include a memory 1540. The memory 1540 may be a non-transitory computer-readable storage medium that stores instructions 1542 (which may include, for example, the instructions being executed by the processor (s) 1538) . The instructions 1542 may also be referred to as program code or a computer program. The memory 1540 may also store data used by, and results computed by, the processor (s) 1538.
[0185] The CN device 1536 may include one or more interface (s) 1544. The interface (s) 1544 may be used to provide input to or output from the CN device 1536. For example, a CN device 1536 may include interface (s) 1530 made up of transmitters, receivers, and other circuitry that enables the CN device 1536 to communicate with other equipment in the CN, and / or that enables the CN device 1536 to communicate with external networks, computers, databases, and the like for purposes of operations, administration, and maintenance of the CN device 1536 or other equipment operably connected thereto.
[0186] The CN device 1536 may include a sensing module 1546. The sensing module 1546 may be implemented via hardware, software, or combinations thereof. For example, the sensing module 1546 may be implemented as a processor, circuit, and / or instructions 1542 stored in the memory 1540 and executed by the processor (s) 1538. In some examples, the sensing module 1546 may be integrated within the processor (s) 1538. For example, the sensing module 1546 may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor (s) 1538.
[0187] The sensing module 1546 may be used for various aspects of the present disclosure, for example, aspects of FIG. 8, FIG. 10, FIG. 11 FIG. 12, and / or FIG. 13. For example, the sensing module 1546 may configure a CN device 1536 that implements an N3IWF to perform a registration of a sensing apparatus that communicates with the N3IWF via a WLAN access point with the 3GPP wireless communication system, wherein the registration results in an IPsec SA between the sensing apparatus and the N3IWF, and wherein the registration comprises receiving, from the sensing apparatus, an AN message that indicates sensing functionality information for the sensing apparatus and selecting an AMF of the 3GPP wireless communication system to use with the sensing apparatus based on the sensing functionality information; and receive, after the registration of the sensing apparatus with the 3GPP wireless communication system is complete, sensing data generated from the sensing apparatus.
[0188] In another example, the sensing module 1546 may configure a CN device 1536 that implements an N3IWF to receive, from a sensing apparatus that communicates with the N3IWF via a WLAN access point, using an IPsec SA between the sensing apparatus and the N3IWF, a NAS message comprising a sensing session establishment request message; send, to an AMF of the 3GPP wireless communication system, the sensing session establishment request message; receive, from the AMF, a sensing session request message; send, to the sensing apparatus, in response to receiving the sensing session request message, a first identification of a first child IPsec SA for a sensing session; receive first sensing data of the sensing session that is for a SF-U from the sensing apparatus using the first child IPsec SA; and send the first sensing data to the SF-U.
[0189] In another example, the sensing module 1546 may configure a CN device 1536 that implements an SF-C to receive, from an access an AMF of the 3GPP wireless communication system, a sensing session management context creation request message; send, to the AMF, a sensing session management context creation response message indicating that the SF-C accepts a creation of a sensing session management context between the SF-C and the AMF; select an SF-U of the 3GPP wireless communication system for use with a sensing session between the SF-C and the SF-U; send, to the SF-U, a sensing session establishment request message for the sensing session; receive, from the SF-U, a sensing session establishment response message indicating that the SF-U accepts an establishment of the sensing session; and send, to the AMF, in response to the establishment of the sensing session between the SF-C and the SF-U, a sensing message transfer configuration message.
[0190] In another example, the sensing module 1546 may configure a CN device 1536 that implements an AF to determine to trigger a sensing session for collecting sensing data from a sensing apparatus that communicates with 3GPP wireless communication system via a WLAN access point; send, to an NEF of the 3GPP wireless communication system, a sensing trigger request message configured to trigger the sensing session; receive, from the NEF, a trigger delivery response message indicating that the sensing trigger request message was accepted for delivery to the sensing apparatus; and receive, from the NEF, a trigger delivery notification message indicating that the sensing trigger request message was successfully delivered to the sensing apparatus.
[0191] In another example, the sensing module 1546 may configure a CN device 1536 that implements an NEF to receive, from an AF of the 3GPP wireless communication system, a sensing trigger request message configured to trigger a sensing session for collecting sensing data from a sensing apparatus that communicates with 3GPP wireless communication system via a WLAN access point; determine that the AF is authorized to send the sensing trigger request message and that the AF has not exceeded a sensing trigger request limit; send the sensing trigger request message to an SF-C of the 3GPP wireless communication system; receive, from the SF-C, a trigger submission confirmation indicating that the sensing trigger request message is accepted by the SF-C; send, to the AF, a trigger delivery response message indicating that the sensing trigger request message was accepted for delivery to the sensing apparatus; receive, from an AMF of the 3GPP wireless communication system, a message delivery report indicating the sensing trigger request message was successfully delivered to the sensing apparatus; and send, to the AF, a trigger delivery notification message indicating that the sensing trigger request message was successfully delivered to the sensing apparatus.
[0192] Embodiments contemplated herein include an apparatus comprising means to perform one or more elements of either of the method 700 and / or the method 900. This apparatus may be, for example, an apparatus of a UE (such as a wireless device 1502 that is a UE, as described herein) .
[0193] Embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of either of the method 700 and / or the method 900. This non-transitory computer-readable media may be, for example, a memory of a UE (such as a memory 1506 of a wireless device 1502 that is a UE, as described herein) .
[0194] Embodiments contemplated herein include an apparatus comprising logic, modules, or circuitry to perform one or more elements of either of the method 700 and / or the method 900. This apparatus may be, for example, an apparatus of a UE (such as a wireless device 1502 that is a UE, as described herein) .
[0195] Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of either of the method 700 and / or the method 900. This apparatus may be, for example, an apparatus of a UE (such as a wireless device 1502 that is a UE, as described herein) .
[0196] Embodiments contemplated herein include a signal as described in or related to one or more elements of either of the method 700 and / or the method 900.
[0197] Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processor is to cause the processor to carry out one or more elements of either of the method 700 and / or the method 900. The processor may be a processor of a UE (such as a processor (s) 1504 of a wireless device 1502 that is a UE, as described herein) . These instructions may be, for example, located in the processor and / or on a memory of the UE (such as a memory 1506 of a wireless device 1502 that is a UE, as described herein) .
[0198] Embodiments contemplated herein include an apparatus comprising means to perform one or more elements of any of the method 800, the method 1000, the method 1100, the method 1200, and / or the method 1300. This apparatus may be, for example, a CN device (such as a CN device 1536 that is a base station, as described herein) .
[0199] Embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of any of the method 800, the method 1000, the method 1100, the method 1200, and / or the method 1300. This non-transitory computer-readable media may be, for example, a memory of a CN device (such as a memory 1540 of a CN device 1536, as described herein) .
[0200] Embodiments contemplated herein include an apparatus comprising logic, modules, or circuitry to perform one or more elements of any of the method 800, the method 1000, the method 1100, the method 1200, and / or the method 1300. This apparatus may be, for example, an apparatus of a CN device (such as a CN device 1536, as described herein) .
[0201] Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of any of the method 800, the method 1000, the method 1100, the method 1200, and / or the method 1300. This apparatus may be, for example, an apparatus of a CN device (such as a CN device 1536, as described herein) .
[0202] Embodiments contemplated herein include a signal as described in or related to one or more elements of any of the method 800, the method 1000, the method 1100, the method 1200, and / or the method 1300.
[0203] Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out one or more elements of any of the method 800, the method 1000, the method 1100, the method 1200, and / or the method 1300. The processor may be a processor of a CN device (such as a processor (s) 1538 of a CN device 1536, as described herein) . These instructions may be, for example, located in the processor and / or on a memory of the CN device (such as a memory 1540 of a CN device 1536, as described herein) .
[0204] For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and / or methods as set forth herein. For example, a baseband processor as described herein in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein.
[0205] Any of the above described embodiments may be combined with any other embodiment (or combination of embodiments) , unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.
[0206] Embodiments and implementations of the systems and methods described herein may include various operations, which may be embodied in machine-executable instructions to be executed by a computer system. A computer system may include one or more general-purpose or special-purpose computers (or other electronic devices) . The computer system may include hardware components that include specific logic for performing the operations or may include a combination of hardware, software, and / or firmware.
[0207] It should be recognized that the systems described herein include descriptions of specific embodiments. These embodiments can be combined into single systems, partially combined into other systems, split into multiple systems or divided or combined in other ways. In addition, it is contemplated that parameters, attributes, aspects, etc. of one embodiment can be used in another embodiment. The parameters, attributes, aspects, etc. are merely described in one or more embodiments for clarity, and it is recognized that the parameters, attributes, aspects, etc. can be combined with or substituted for parameters, attributes, aspects, etc. of another embodiment unless specifically disclaimed herein.
[0208] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.
[0209] Although the foregoing has been described in some detail for purposes of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles thereof. It should be noted that there are many alternative ways of implementing both the processes and apparatuses described herein. Accordingly, the present embodiments are to be considered illustrative and not restrictive, and the description is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.
Claims
1.A method of a sensing apparatus, comprising:connecting to a wireless local area network (WLAN) access point;performing a registration of the sensing apparatus with a 3rd-generation-partnership-project (3GPP) wireless communication system via the WLAN access point, wherein the registration comprises sending an access network (AN) message to a non-3GPP internetworking function (N3IWF) of the 3GPP wireless communication system that indicates sensing functionality information for the sensing apparatus, and wherein the registration results in an internet protocol security (IPsec) security association (SA) between the sensing apparatus and the N3IWF; andsending, after the registration of the sensing apparatus with the 3GPP wireless communication system is complete, sensing data generated by the sensing apparatus that is for user plane sensing function (SF-U) of the 3GPP wireless communication system to the N3IWF.2.The method of claim 1, wherein the sensing functionality information for the sensing apparatus comprises a sensor capability identifier (ID) .3.The method of claim 1, wherein the sensing functionality information for the sensing apparatus comprises a sensor type identification (ID) .4.The method of claim 1, wherein the sensing apparatus comprises a user equipment (UE) .5.A method of a non-3rd-generation-partnership-project (3GPP) internetworking function (N3IWF) of a 3GPP wireless communication system, comprising:performing a registration of a sensing apparatus that communicates with the N3IWF via a wireless local area network (WLAN) access point with the 3GPP wireless communication system, wherein the registration results in an internet protocol security (IPsec) security association (SA) between the sensing apparatus and the N3IWF, and wherein the registration comprises:receiving, from the sensing apparatus, an access network (AN) message that indicates sensing functionality information for the sensing apparatus, andselecting an access and mobility management function (AMF) of the 3GPP wireless communication system to use with the sensing apparatus based on the sensing functionality information; andreceiving, after the registration of the sensing apparatus with the 3GPP wireless communication system is complete, sensing data generated from the sensing apparatus.6.The method of claim 5, wherein the sensing functionality information for the sensing apparatus comprises a sensor capability identifier (ID) .7.The method of claim 5, wherein the sensing functionality information for the sensing apparatus comprises a sensor type identification (ID) .8.The method of claim 5, wherein the sensing apparatus comprises a user equipment (UE) .9.A method of a sensing apparatus, comprising:sending, via a wireless local area network (WLAN) access point, to a non-3rd-generation partnership-project (3GPP) internetworking function (N3IWF) of a 3GPP wireless communication system, using an internet protocol security (IPsec) security association (SA) between the sensing apparatus and the N3IWF, a non-access stratum (NAS) message comprising a sensing session establishment request message;receiving, from the N3IWF, in response to the NAS message, a first identification of a first child IPsec SA for a sensing session; andsending first sensing data of the sensing session that is for a user plane sensing function (SF-U) to the N3IWF using the first child IPsec SA.10.The method of claim 9, further comprising:receiving, from the N3IWF, in response to the NAS message, a second identification of a second child IPsec SA for the sensing session; andsending second sensing data of the sensing session that is for the SF-U to the N3IWF using the second child IPsec SA.11.The method of claim 9, wherein the NAS message further comprises one or more of:a sensing session identifier (ID) for the sensing session;a requested sensing session type; anda requested destination for the first sensing data.12.The method of claim 9, wherein the sensing session establishment request message comprises one or more of:quality of service (QoS) requirements for the sensing session;a duration for the sensing session;target area information for the sensing session; andsensing node information for the sensing apparatus.13.The method of claim 9, wherein the sensing apparatus comprises a user equipment (UE) .14.A method of a non-3rd-generation-partnership-project (3GPP) internetworking function (N3IWF) of a 3GPP wireless communication system, comprising:receiving, from a sensing apparatus that communicates with the N3IWF via a wireless local area network (WLAN) access point, using an internet protocol security (IPsec) security association (SA) between the sensing apparatus and the N3IWF, a non-access stratum (NAS) message comprising a sensing session establishment request message;sending, to an access and mobility management function (AMF) of the 3GPP wireless communication system, the sensing session establishment request message;receiving, from the AMF, a sensing session request message;sending, to the sensing apparatus, in response to receiving the sensing session request message, a first identification of a first child IPsec SA for a sensing session;receiving first sensing data of the sensing session that is for a user plane sensing function (SF-U) from the sensing apparatus using the first child IPsec SA; andsending the first sensing data to the SF-U.15.The method of claim 14, further comprising:sending, to the sensing apparatus, in response to the NAS message, a second identification of a second child IPsec SA for the sensing session;receiving second sensing data of the sensing session that is for the SF-U from the sensing apparatus using the second child IPsec SA; andsending the second sensing data to the SF-U.16.The method of claim 14, wherein the NAS message further comprises one or more of:a sensing session identifier (ID) for the sensing session;a requested sensing session type; anda requested destination for the first sensing data.17.The method of claim 14, wherein the sensing session establishment request message comprises one or more of:quality of service (QoS) requirements for the sensing session;a duration for the sensing session;target area information for the sensing session; andsensing node information for the sensing apparatus.18.The method of claim 14, wherein the sensing apparatus comprises a user equipment (UE) .19.A method of a control plane sensing function (SF-C) of a third generation partnership project (3GPP) wireless communication system, comprising:receiving, from an access and mobility management function (AMF) of the 3GPP wireless communication system, a sensing session management context creation request message;sending, to the AMF, a sensing session management context creation response message indicating that the SF-C accepts a creation of a sensing session management context between the SF-C and the AMF;selecting a user plane sensing function (SF-U) of the 3GPP wireless communication system for use with a sensing session between the SF-C and the SF-U;sending, to the SF-U, a sensing session establishment request message for the sensing session;receiving, from the SF-U, a sensing session establishment response message indicating that the SF-U accepts an establishment of the sensing session; andsending, to the AMF, in response to the establishment of the sensing session between the SF-C and the SF-U, a sensing message transfer configuration message.20.The method of claim 19, wherein the sensing message transfer configuration message comprises a sensing session identifier (ID) for the sensing session.21.The method of claim 19, wherein the sensing message transfer configuration message comprises N2 sensing session management information for an N2 interface between the AMF and a non-3GPP internetworking function (N3IWF) of the 3GPP wireless communication system, the N2 sensing session management information comprising one or more of:a sensing session identifier (ID) for the sensing session;a sensing quality of service (QoS) flow indicator (QFI) for the sensing session;a sensing QoS profile for the sensing session; andcore network (CN) tunnel information for the sensing session.22.The method of claim 19, wherein the sensing message transfer configuration message comprises N1 sensing session management information for an N1 interface between the AMF and a sensing apparatus that communicates with the 3GPP wireless communication system via a wireless local area network (WLAN) access point, the N1 sensing session management information comprising one or more of:an indication that the establishment of the sensing session is accepted;a requested destination for uploading sensing data of the sensing session; andan allocated address for the sensing apparatus.23.The method of claim 22, wherein the sensing apparatus comprises a user equipment (UE) .24.A method of an application function (AF) of a third generation partnership project (3GPP) wireless communication system, comprising:determining to trigger a sensing session for collecting sensing data from a sensing apparatus that communicates with 3GPP wireless communication system via a wireless local area network (WLAN) access point;sending, to a network exposure function (NEF) of the 3GPP wireless communication system, a sensing trigger request message configured to trigger the sensing session;receiving, from the NEF, a trigger delivery response message indicating that the sensing trigger request message was accepted for delivery to the sensing apparatus; andreceiving, from the NEF, a trigger delivery notification message indicating that the sensing trigger request message was successfully delivered to the sensing apparatus.25.The method of claim 24, wherein the sensing trigger request message comprises one or more of:an identifier (ID) for the AF;a trigger type;a requested sensing type;a requested destination for uploading the sensing data;quality of service (QoS) requirements for the sensing session;a duration for the sensing session;target area information for the sensing session;sensing target information for the sensing session; andsensing node information for the sensing apparatus.26.The method of claim 24, wherein the sensing apparatus comprises a user equipment (UE) .27.A method of a network exposure function (NEF) of a third generation partnership project (3GPP) wireless communication system, comprising:receiving, from an application function (AF) of the 3GPP wireless communication system, a sensing trigger request message configured to trigger a sensing session for collecting sensing data from a sensing apparatus that communicates with 3GPP wireless communication system via a wireless local area network (WLAN) access point;determining that the AF is authorized to send the sensing trigger request message and that the AF has not exceeded a sensing trigger request limit;sending the sensing trigger request message to a control plane sensing function (SF-C) of the 3GPP wireless communication system;receiving, from the SF-C, a trigger submission confirmation indicating that the sensing trigger request message is accepted by the SF-C;sending, to the AF, a trigger delivery response message indicating that the sensing trigger request message was accepted for delivery to the sensing apparatus;receiving, from an access and mobility management function (AMF) of the 3GPP wireless communication system, a message delivery report indicating the sensing trigger request message was successfully delivered to the sensing apparatus; andsending, to the AF, a trigger delivery notification message indicating that the sensing trigger request message was successfully delivered to the sensing apparatus.28.The method of claim 27, wherein the sensing trigger request limit comprises a maximum sensing trigger request number.29.The method of claim 27, wherein the sensing trigger request limit comprises a maximum sensing trigger request rate.30.The method of claim 27, wherein the determining that the AF is authorized to send the sensing trigger request message comprises checking authorization information for the AF that is stored at the NEF.31.The method of claim 27, wherein the determining that the AF is authorized to send the sensing trigger request message comprises:receiving, from a unified data management (UDM) network function (NF) of the 3GPP wireless communication system, authorization information for the AF; andchecking the authorization information for the AF received from the UDM NF.32.The method of claim 27, wherein the sensing apparatus comprises a user equipment (UE) .33.An apparatus comprising means to perform the method of any of claim 1 to claim 32.34.A computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform the method of any of claim 1 to claim 32.35.An apparatus comprising logic, modules, or circuitry to perform the method of any of claim 1 to claim 32.36.A baseband processor for a user equipment (UE) that is configured to cause the UE to perform one or more elements of any one of claim 1 to claim 3 and claim 9 to claim 12.
