Method and apparatus for exposing aware services in wireless network

Abstract

An integrated awareness assistance function (ISANF) may receive a request from an application function (AF) to establish an awareness service. The request may include a configuration of a trigger event for initiating the requested aware service. The trigger event may be associated with a wireless transmit-receive unit (WTRU) mobility event or a data session state. The ISANF may subscribe to an event exposure service from a first network function (NF) based on a configured trigger event. The ISANF may receive an event notification from the first NF, which may trigger the awareness service. The ISANF may select the awareness mechanism to use. The awareness mechanism may be network-based, WTRU-based, or collaboration-based awareness. The ISANF may send a perception request to a second NF in the 5GC. The ISANF may receive the perception result from the second NF and forward the received perception result to the requesting AF.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 444,515, filed February 9, 2023, the disclosure of which is incorporated herein by reference. Background Art

[0003] In the 5G Core (5GC), events can be exposed externally and internally to network functions (NFs). NF producers can provide event exposure services to NF consumers by exposing information associated with one or more events. To receive the event exposure services of NF producers, NF consumers can subscribe to the event exposure services, and NF producers can provide notifications of events to NF consumers. Summary of the Invention

[0004] An event exposure service for a perception event may be provided by a 5G core (5GC) network function (NF) to an application function (AF). The AF may request a specific perception service associated with a trigger condition of a wireless transmit-receive unit (WTRU). The NF may subscribe to a perception event exposure service associated with the WTRU to monitor the trigger condition. When the trigger condition is met, the associated perception service is initiated. In an example use case, the NF may subscribe to a mobility event associated with a WTRU entering a given perception service area, and upon entry, the NF may trigger a new perception service to collect perception data in the given perception service area. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] A more detailed understanding may be derived from the following description, given by way of example in conjunction with the accompanying drawings, in which like reference numerals indicate like elements, and in which:

[0006] Figure 1A is a system diagram illustrating an example communication system in which one or more disclosed embodiments may be implemented;

[0007] Figure 1B is a diagram illustrating that according to one embodiment, Figure 1A A system diagram of an example wireless transmit / receive unit (WTRU) used in the illustrated communication system;

[0008] Figure 1C is a diagram illustrating that according to one embodiment, Figure 1A a system diagram of an example radio access network (RAN) and an example core network (CN) used in the illustrated communication system;

[0009] Figure 1D is a diagram illustrating that according to one embodiment, Figure 1Aa system diagram of yet another example RAN and yet another example CN used in the illustrated communication system;

[0010] Figure 2 An example reference model illustrating a potential architecture for a 5G or next generation network;

[0011] Figure 3 An example system for pedestrian or animal intrusion detection is illustrated;

[0012] Figure 4 An example system for intruder detection in a smart home perimeter is illustrated;

[0013] Figure 5 An example of the call flow for an event-based perception program is shown;

[0014] Figure 6 An example of the calling process of the perception program initiated by the NF is shown;

[0015] Figure 7 An example of the call flow of an NF-initiated awareness procedure using the service operation of the AMF is shown;

[0016] Figure 8 An example of a call flow for a service request procedure having a trigger associated with an awareness service is shown;

[0017] Figure 9 An example flow diagram illustrating a process for performing perception measurements by a WTRU or BS is shown;

[0018] Figure 10 An example flow chart illustrating a process for exposing services that sense events triggered by requests for network operations; and

[0019] Figure 11 An example flow diagram of a process for providing an exposure service for awareness events to an Integrated Awareness Assisted Network Function (ISANF) is shown. DETAILED DESCRIPTION

[0020] The following acronyms may be mentioned in the following descriptions:

[0021] 5GC 5G core network

[0022] 5GS 5G system

[0023] NEF network exposure function

[0024] AMF Access and Mobility Management Function

[0025] AUSF authentication server function

[0026] CP Control Plane

[0027] DL Downlink

[0028] DN Data Network

[0029] DNN data network name

[0030] MBS Multicast / Broadcast Service

[0031] NEF network exposure function

[0032] NF Network Function

[0033] PCF Policy Control Function

[0034] (R)AN (Radio) Access Network

[0035] RAT Radio Access Technology

[0036] S-NSSAI Single Network Slice Selection Auxiliary Information

[0037] SMF session management functions

[0038] TA Tracking Area

[0039] UDM Unified Data Management

[0040] UL Uplink

[0041] UP User Plane

[0042] UPF User Plane Function

[0043] ISANF Integrated Sensing Assisted NF

[0044] SOMF-aware operations management capabilities

[0045] Figure 1A 1 is a schematic diagram illustrating an example communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multi-access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content by sharing system resources, including wireless bandwidth. For example, the communication system 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tailing unique word discrete Fourier transform spread OFDM (ZT-UW-DFT-S-OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multi-carrier (FBMC), etc.

[0046] like Figure 1A As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network (CN) 106, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112. However, it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d (any of which may be referred to as a station (STA)) may be configured to transmit and / or receive wireless signals and may include user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical equipment and applications (e.g., remote surgery), industrial equipment and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated process chain environments), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

[0047] The communication system 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106, the Internet 110, and / or other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node B, an eNode B (eNB), a Home Node B, a Home eNode B, a next generation Node B (such as a gNode B (gNB)), a New Radio (NR) Node B, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0048] Base station 114a may be part of RAN 104, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. Base station 114a and / or base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies, which may be referred to as cells (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide wireless service coverage to a specific geographic area, which may be relatively fixed or may change over time. The cell may be further divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Thus, in one embodiment, base station 114a may include three transceivers, one for each sector of the cell. In one embodiment, base station 114a may employ multiple-input multiple-output (MIMO) technology and may use multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and / or receive signals in a desired spatial direction.

[0049] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

[0050] More specifically, as described above, the communication system 100 may be a multiple access system and may employ one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, the base station 114a in the RAN 104 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interface 116. WCDMA may include communication protocols such as High Speed ​​Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed ​​Downlink (DL) Packet Access (HSDPA) and / or High Speed ​​Uplink (UL) Packet Access (HSUPA).

[0051] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) and / or LTE-Advanced Pro (LTE-A Pro).

[0052] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR wireless access and may establish the air interface 116 using NR.

[0053] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may jointly implement LTE radio access and NR radio access, e.g., using dual connectivity (DC) principles. Thus, the air interface used by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions to / from multiple types of base stations (e.g., eNBs and gNBs).

[0054] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi)), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.

[0055] For example, Figure 1AThe base station 114b in the WLAN may be a wireless router, a Home NodeB, a Home eNodeB, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a local area, such as a business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish a microcell or a femtocell. Figure 1A As shown, base station 114b may be directly connected to the Internet 110. Therefore, base station 114b may not need to access the Internet 110 via CN 106.

[0056] The RAN 104 may be in communication with the CN 106, which may be any type of network configured to provide voice, data, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. Data may have different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 may provide call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform advanced security functions, such as user authentication. Although in Figure 1A Although not shown, it will be appreciated that the RAN 104 and / or the CN 106 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 or a different RAT as the RAN 104. For example, in addition to being connected to the RAN 104, which may utilize an NR radio technology, the CN 106 may also be in communication with another RAN (not shown) that employs GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0057] The CN 106 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and / or the Internet Protocol (IP) from the TCP / IP Internet protocol suite. The networks 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 or a different RAT.

[0058] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks via different wireless links). Figure 1A The WTRU 102c shown in FIG. 1 may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0059] Figure 1B is a system diagram illustrating an example WTRU 102. Figure 1B As shown, the WTRU 102 may include, among other things, a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power supply 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138. It will be appreciated that the WTRU 102 may include any subcombination of the foregoing elements while remaining consistent with an embodiment.

[0060] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, but it is understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0061] The transmit / receive element 122 may be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) over the air interface 116. For example, in one embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In one embodiment, the transmit / receive element 122 may be, for example, an emitter / detector configured to transmit and / or receive IR, UV, or visible light signals. In yet another embodiment, the transmit / receive element 122 may be configured to transmit and / or receive both RF and light signals. It should be understood that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals.

[0062] Although the transmit / receive element 122 is Figure 1B Although depicted as a single element in FIG1 , the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

[0063] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and demodulate signals received by the transmit / receive element 122. As described above, the WTRU 102 may have multi-mode capabilities. Thus, for example, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.

[0064] The processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. Furthermore, the processor 118 may access information from and store data in any type of suitable memory, such as non-removable memory 130 and / or removable memory 132. The non-removable memory 130 may include random access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from and store data in memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0065] The processor 118 may receive power from the power source 134 and may be configured to distribute and / or control power to the other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel-metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, etc.

[0066] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to or in lieu of information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) over the air interface 116 and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by any suitable location-determination method while remaining consistent with an embodiment.

[0067] The processor 118 may be further coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, Modules, frequency modulation (FM) radio units, digital music players, media players, electronic game player modules, Internet browsers, virtual reality and / or augmented reality (VR / AR) devices, activity trackers, etc. Peripheral devices 138 may include one or more sensors. The sensor may be one or more of a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor, a geographic location sensor, an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a posture sensor, a biometric sensor, a humidity sensor, etc.

[0068] The WTRU 102 may include a full-duplex radio for which transmission and reception of some or all signals (e.g., signals associated with particular subframes used for UL (e.g., for transmission) and DL (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via hardware (e.g., a choke) or via signal processing by a processor (e.g., a separate processor (not shown) or via the processor 118). In one embodiment, the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all signals (e.g., signals associated with particular subframes used for UL (e.g., for transmission) or DL ​​(e.g., for reception)) may be concurrent and / or simultaneous.

[0069] Figure 1C 1 is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As described above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0070] The RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, for example, the eNode-B 160a may use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a.

[0071] Each of the eNode-Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, etc. Figure 1C As shown, eNode-Bs 160a, 160b, 160c may communicate with each other over an X2 interface.

[0072] Figure 1C The CN 106 shown in FIG may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. Although the foregoing elements are described as being part of the CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0073] The MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like. The MME 162 may also provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

[0074] The SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to and from the WTRUs 102a, 102b, 102c. The SGW 164 may also perform other functions, such as anchoring the user plane during inter-eNode B handovers, triggering paging when downlink data is available for the WTRUs 102a, 102b, 102c, managing and storing the context of the WTRUs 102a, 102b, 102c, and the like.

[0075] The SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0076] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0077] Even though the WTRU Figures 1A-1D Although described as a wireless terminal, it is contemplated that in certain representative embodiments such a terminal may employ (eg, temporarily or permanently) a wired communication interface with a communication network.

[0078] In a representative embodiment, the other network 112 may be a WLAN.

[0079] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may access or be connected to a distributed system (DS) or another type of wired / wireless network that transmits traffic to and / or out of the BSS. Traffic originating from outside the BSS and destined for a STA may arrive through the AP and be delivered to the STA. Traffic originating from a STA to a destination outside the BSS may be sent to the AP for delivery to the corresponding destination. For example, traffic between STAs within a BSS may be sent through the AP, where the source STA may send traffic to the AP, and the AP may deliver the traffic to the destination STA. Traffic between STAs within a BSS may be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic may be transmitted between the source and destination STAs (e.g., directly between them) using direct link setup (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunneled DLS (TDLS). A WLAN using an independent BSS (IBSS) mode may not have an AP, and STAs (eg, all STAs) within or using the IBSS may communicate directly with each other. The IBSS communication mode is sometimes referred to herein as an "ad hoc" communication mode.

[0080] When using 802.11ac infrastructure operation mode or a similar operation mode, the AP can transmit beacons on a fixed channel (such as a primary channel). The primary channel can be a fixed width (e.g., a wide bandwidth of 20 MHz) or a dynamically set width. The primary channel can be the operating channel of the BSS and can be used by STAs to establish a connection with the AP. In certain representative embodiments, such as in an 802.11 system, carrier sense multiple access with collision avoidance (CSMA / CA) can be implemented. For CSMA / CA, STAs (e.g., each STA), including the AP, can sense the primary channel. If a particular STA senses / detects and / or determines that the primary channel is busy, the particular STA can back off. One STA (e.g., only one station) can transmit at any given time in a given BSS.

[0081] High throughput (HT) STAs may communicate using a 40 MHz wide channel, for example, via a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.

[0082] Very high throughput (VHT) STAs can support 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels. 40 MHz and / or 80 MHz channels can be formed by combining consecutive 20 MHz channels. A 160 MHz channel can be formed by combining eight consecutive 20 MHz channels, or by combining two discontinuous 80 MHz channels, which can be referred to as an 80+80 configuration. For the 80+80 configuration, after channel coding, the data can pass through a segment parser that can separate the data into two streams. Each stream can be subjected to inverse fast Fourier transform (IFFT) processing and time domain processing separately. These streams can be mapped onto two 80 MHz channels, and the data can be transmitted by the transmitting STA. At the receiver of the receiving STA, the operations of the above-mentioned 80+80 configuration can be reversed, and the combined data can be sent to the media access control (MAC).

[0083] 802.11af and 802.11ah support operating modes below 1 GHz. The channel operating bandwidth and carrier in 802.11af and 802.11ah are reduced relative to the channel operating bandwidth and carrier used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support metered type control / machine type communication (MTC), such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, for example, limited capabilities, including support for (e.g., only support for) certain and / or limited bandwidths. MTC devices may include batteries with battery life above a threshold (e.g., in order to maintain very long battery life).

[0084] WLAN systems that can support multiple channels and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include a channel that can be designated as a primary channel. The bandwidth of the primary channel can be equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and / or limited by one STA among all STAs operating in the BSS that supports the minimum bandwidth operating mode. In the example of 802.11ah, for a STA that supports (e.g., only supports) 1 MHz mode (e.g., an MTC-type device), the primary channel can be 1 MHz wide, even if the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or network allocation vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which only supports 1 MHz operating mode) transmitting to the AP, all available frequency bands can be considered busy, even if most of the available frequency bands remain idle.

[0085] In the United States, 802.11ah can be used in the available frequency band from 902MHz to 928MHz. In South Korea, the available frequency band is from 917.5MHz to 923.5MHz. In Japan, the available frequency band is from 916.5MHz to 927.5MHz. The total available bandwidth for 802.11ah ranges from 6MHz to 26MHz, depending on the country code.

[0086] Figure 1D1 is a system diagram illustrating the RAN 104 and the CN 106 according to one embodiment. As described above, the RAN 104 may employ NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0087] The RAN 104 may include gNBs 180a, 180b, and 180c, though it will be appreciated that the RAN 104 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, and 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, and 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, and 180c may implement MIMO technology. For example, the gNBs 180a and 180b may utilize beamforming to transmit signals to and / or receive signals from the gNBs 180a, 180b, and 180c. Thus, for example, the gNB 180a may use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a. In one embodiment, the gNBs 180a, 180b, and 180c may implement carrier aggregation technology. For example, the gNB 180a may transmit multiple component carriers (not shown) to the WTRU 102a. A subset of these component carriers may be on unlicensed spectrum, while the remaining component carriers may be on licensed spectrum. In one embodiment, the gNBs 180a, 180b, and 180c may implement coordinated multi-point (CoMP) technology. For example, the WTRU 102a may receive coordinated transmissions from the gNB 180a and gNB 180b (and / or gNB 180c).

[0088] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with scalable numerology. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing may be different for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of varying or scalable lengths (e.g., containing a variable number of OFDM symbols and / or lasting a variable length of absolute time).

[0089] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c without accessing other RANs (e.g., such as the eNode-Bs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may utilize one or more of the gNBs 180a, 180b, 180c as mobility anchors. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in an unlicensed frequency band. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate / connect with the gNBs 180a, 180b, 180c while also communicating / connecting with another RAN, such as the eNode-Bs 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the eNode-Bs 160a, 160b, 160c may serve as mobility anchors for the WTRUs 102a, 102b, 102c, and the gNBs 180a, 180b, 180c may provide additional coverage and / or throughput for the serving WTRUs 102a, 102b, 102c.

[0090] Each of the gNBs 180a, 180b, 180c may be associated with a specific cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, network slicing support, interworking between DC, NR, and E-UTRA, routing user plane data to a user plane function (UPF) 184a, 184b, routing control plane information to an access and mobility management function (AMF) 182a, 182b, etc. Figure 1D As shown, gNBs 180a, 180b, and 180c can communicate with each other on the Xn interface.

[0091] Figure 1DThe illustrated CN 106 may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and possibly a data network (DN) 185a, 185b. While the aforementioned elements are depicted as part of the CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0092] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via the N2 interface and may act as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRU 102a, 102b, 102c, supporting network slicing (e.g., handling different protocol data unit (PDU) sessions with different requirements), selecting a specific SMF 183a, 183b, managing registration areas, terminating non-access stratum (NAS) signaling, mobility management, and the like. The AMF 182a, 182b may use network slicing to customize CN support for the WTRU 102a, 102b, 102c based on the type of service being used by the WTRU 102a, 102b, 102c. For example, different network slices may be established for different use cases, such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for MTC access, and the like. The AMFs 182a, 182b may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi.

[0093] The SMFs 183a and 183b can connect to the AMFs 182a and 182b in the CN 106 via the N11 interface. The SMFs 183a and 183b can also connect to the UPFs 184a and 184b in the CN 106 via the N4 interface. The SMFs 183a and 183b can select and control the UPFs 184a and 184b and configure the routing of traffic through the UPFs 184a and 184b. The SMFs 183a and 183b can perform other functions, such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, and providing DL data notifications. The PDU session type can be IP-based, non-IP-based, Ethernet-based, and so on.

[0094] The UPF 184a, 184b may be connected to one or more gNBs 180a, 180b, 180c in the RAN 104 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering DL packets, providing mobility anchoring, etc.

[0095] The CN 106 may facilitate communications with other networks. For example, the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 106 and the PSTN 108. Furthermore, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may connect to the local DN 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and the N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0096] Given that Figures 1A-1D as well as Figures 1A-1D

[0015] As described herein, one or more or all of the functionality described herein with respect to one or more of the following may be performed by one or more emulated devices (not shown): the WTRUs 102a-d, base stations 114a-b, eNode-Bs 160a-c, MMEs 162, SGWs 164, PGWs 166, gNBs 180a-c, AMFs 182a-b, UPFs 184a-b, SMFs 183a-b, DNs 185a-b, and / or any other device(s) described herein. An emulated device may be one or more devices configured to emulate one or more or all of the functionality described herein. For example, an emulated device may be used to test other devices and / or simulate network and / or WTRU functionality.

[0097] Emulated devices can be designed to implement one or more tests of other devices in a laboratory environment and / or in a carrier network environment. For example, one or more emulated devices can perform one or more or all functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network in order to test other devices within the communication network. One or more emulated devices can perform one or more or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. Emulated devices can be directly coupled to another device for testing purposes and / or perform tests using over-the-air wireless communications.

[0098] One or more emulated devices can perform one or more functions, including all functions, without being implemented / deployed as part of a wired and / or wireless communication network. For example, the emulated device can be used in a test lab and / or a test scenario in a non-deployed (e.g., testing) wired and / or wireless communication network to enable testing of one or more components. The one or more emulated devices can be test devices. The emulated device can transmit and / or receive data using direct RF coupling and / or wireless communication via RF circuitry (e.g., which can include one or more antennas).

[0099] Figure 2 An example reference model of a potential architecture for a 5G or next-generation network is shown. The RAN may refer to a radio access network based on 5G radio access technology (RAT) or evolved E-UTRA, connected to the next-generation core network. The access control and mobility management function (AMF) includes, for example, the following functions: registration management, connection management, reachability management, and mobility management. The session management function (SMF) includes, for example, the following functions: session management (including session establishment, modification, and release), UE IP address allocation, and selection and control of user plane (UP) functions. The user plane function (UPF) includes, for example, the following functions: packet routing and forwarding, packet inspection, and traffic usage reporting.

[0100] In the 5G Core (5GC), events can be exposed both externally and internally to network functions (NFs). An "NF producer" is an NF that generates events; an "NF consumer" is an NF interested in information associated with one or more events generated by the NF producer. NF producers can provide "event exposure services" to NF consumers by exposing information associated with one or more events.

[0101] To receive the event exposure service of the NF producer, the NF consumer can subscribe to the event exposure service, and the NF producer can provide the NF consumer with notification results of the event. When subscribing to an event, the NF consumer can provide parameters such as the event ID, event filter information (including parameter type and value as conditions for notifying the subscribed event ID), event report information, (one or more) target UE information for the event report, and expiration time. The content of the event report information may include, for example, the event reporting mode, the maximum number of reports, the maximum duration of the report, the report type, and the reporting threshold.

[0102] A monitoring event feature may be available and may be intended for monitoring specific events in the 3GPP system and then reporting the occurrence of the event to the NF consumer, for example, via the NEF. Examples of monitoring events may include loss of connectivity, WTRU reachability, location reporting, roaming status, communication failure, etc.

[0103] In case of internal exposure, mobility events from AMF exposure, communication trends from SMF exposure, subscription changes from UDM exposure, etc. can be provided to NF consumers.

[0104] Integrated perception can include use cases and potential requirements for enhancing wireless systems to provide perception services that address different target verticals and applications, such as autonomous / assisted driving, V2X, UAVs, 3D map reconstruction, smart cities, smart homes, factories, healthcare, and maritime sector solutions.

[0105] For integrated sensing, there may be a process of collecting sensing measurement data, which may be data collected for sensing purposes about radio / wireless signals affected by objects of interest or the environment (e.g., reflection, refraction, diffraction), and deriving sensing results from processing the sensing measurement data. There may be areas defined for sensing, so-called sensing service area locations, which may be locations with or without obstacles, where the 5G system is able to provide sensing services with a certain quality or accuracy.

[0106] Non-3GPP entities can also be considered as sources for sensing data. Sensing measurement data from these entities and networks can be considered transparent to 5GS. Data can be communicated to interfaces defined by 5GS using standard protocols.

[0107] One use case for integrated perception is object detection, for example, pedestrian / animal intrusion detection on highways or intruder detection around the perimeter of a smart home.

[0108] Figure 3 An example system for pedestrian or animal intrusion detection is illustrated.

[0109] Figure 4 An example system for intruder detection within a smart home perimeter is illustrated.

[0110] exist Figure 3 and Figure 4 In this scenario, the base station or WTRU can detect intrusions in the base station's sensing area by itself or through collaboration between the WTRU and the base station. The sensing measurements can be passed to the network and further processed into sensing results.

[0111] Some use cases for awareness services can leverage 5GC event exposure; other use cases can leverage awareness services as event exposure services. For example, when a UE is using awareness services in an environment where the UE is a moving vehicle, as the UE moves to a new location (e.g., out of the awareness service area), mobility can be detected and mobility events can be provided by the AMF. Based on the provided information, the awareness control NF can trigger a new awareness service to collect awareness data for the new UE's awareness service area.

[0112] As another example, one perception service can trigger another perception service. For example, when a perception service for intrusion detection detects an unidentified vehicle, a new perception service (e.g., trajectory tracking of the unidentified vehicle) can be activated until the unidentified vehicle moves out of the area of ​​interest. In this case, the trajectory tracking service will not be triggered unless the perception service detects an intrusion.

[0113] As another example, an existing NF can be a consumer of the event exposure of integrated perception. For example, when an intrusion is detected at a smart home, several surveillance cameras may begin to stream live video to a control center. To support the real-time monitoring service, the SMF can subscribe to perception events regarding intrusion detection, and based on the results, the SMF can activate a PDU session related to the live streaming video service.

[0114] In order to provide better communication services and perception services, 5GS may be able to provide mechanisms to solve the following problems: (1) How can 5GC provide integrated perception operations based on event notifications from NFs; (2) How can 5GC provide efficient perception services to AF when AF requests are for multiple perception services; and (3) How can 5GC provide efficient communication services to AF when AF's request is for communication services related to perception events.

[0115] In one embodiment for handling awareness services, several new network functions are defined, such as the Integrated Awareness Assistance NF (ISANF) and the Awareness Operations Management Function (SOMF). The ISANF and SOMF are logical entities and can be collocated with other entities. In one example, all NEFs, ISANFs, and SOMFs can be implemented at the same entity. In another example, the SOMF can be implemented at the AMF, RAN, or another NF.

[0116] The ISANF can oversee interactions with application functions to perform awareness services. The ISANF understands awareness service requests from application functions and can derive the awareness mechanism corresponding to the request. After determining the requested awareness mechanism, it can forward the request to the AMF serving the requested area or requested entity. Later, the ISANF can receive a report on the awareness directly from the AMF or from other network entities (e.g., the Awareness Operations Management Function (SOMF)), and can report the results to the application function.

[0117] When the application function is a third-party application (the third-party application is not a trusted entity of 5GS), the application function and ISANF can communicate through NEF (Network Exposure Function).

[0118] The SOMF may handle the coordination of sensing operations between base stations (BSs) and WTRUs. Based on information received from the AMF, such as the requested sensing area, a list of BSs and WTRUs, or a requested sensing mechanism with QoS requirements, the SOMF may derive coordination information for sensing operations. For example, the SOMF may determine the roles of the sensing operation, such as the sender(s) of the sensing signal(s), the receiver(s) of the sensing signal(s), the entity(ies) that collect the sensing measurement data, and the entity(ies) that calculate the sensing results. For example, the SOMF may determine the sensing period, the waveform of the sensing signal, and / or the resource allocation that requires the BS(s) or sender(s) to send the sensing signal(s) during the sensing period. The sensing signal may be, for example, a specific type of radio waveform. The sensing signal may be transmitted via the radio resources allocated for sensing. The sensing signal may be different for each sender, each sensing opportunity, and / or each sensing mechanism.

[0119] Figure 5 An example of a call flow for an event-based awareness program is shown.

[0120] At (1), a sensing service request message comes from the application function (AF). The message may include a specific type of sensing request (e.g., intrusion detection, rainfall detection, drone detection, etc.), as well as information about the area in which the sensing needs to be performed.

[0121] The awareness service request message may include a condition parameter that indicates the event that triggers the requested awareness service. The condition parameter may include an event associated with the target WTRU (such as a mobility event or session event to be monitored), and a condition for detecting the event. For example, a traffic monitoring awareness event may be requested whenever the target WTRU enters a new awareness service area during a certain requested time period. In this case, the event is the target WTRU entering or leaving the service area, and the condition occurs when the event is detected during a certain requested time period. In another example, a rainfall monitoring awareness event may be requested at the WTRU's service area when the WTRU (here, UAV) is in connected mode. In this case, the event is the target WTRU entering the service area and the WTRU entering connected mode, and the condition occurs during a certain requested time period.

[0122] The sensing service request message may include the WTRU information required to perform sensing (i.e., collect sensing measurement data). The sensing service request message may include specific QoS requirements for the sensing service, such as sensing accuracy, latency, sensing frequency, resolution, etc.

[0123] The Aware Service Request message may include network slice information, such as Single Network Slice Selection Assistance Information (S-NSSAI), at which the Aware Service needs to be provided. When network slice information is provided, entities such as the NF belonging to the network slice and the WTRUs allowed at the network slice may be involved in the operation for the Aware Service. When the network slice information includes a target WTRU, only the WTRUs allowed to operate at the network slice may be considered. When multiple target WTRUs are included, the ISANF may consider the Aware Service Area to be large enough to cover the area of ​​the target WTRU.

[0124] At (2), the ISANF may convert the sensing service request into the requested sensing mechanism that may need to be executed in the 5GS (e.g., BS-based sensing only, BS and UE collaboration-based sensing, or WTRU-based sensing only), and derive the requested event service for the conditional parameters of the requested sensing service.

[0125] At (3), based on the requested event service derived for the condition, the ISANF may subscribe to events of the relevant NF. For example, if a traffic monitoring awareness event is requested with an associated condition when the target WTRU enters a new awareness service, the ISANF may subscribe to the mobility event exposure service of the target WTRU's serving AMF to detect when the target WTRU moves out of the awareness service area.

[0126] When network slice information is received at (1), the network slice information may be included in a subscription to event exposure.

[0127] At (4), when the requested event (3) occurs, the event may be notified from the relevant NF to the ISANF. When the result of the event is notified to the ISANF, location information of the target WTRU may be provided, such as information of the serving AMF, the location of the target WTRU, or the registration area of ​​the target WTRU.

[0128] At (5), when the event is notified to ISANF, which may satisfy the conditions for the requested awareness service, ISANF may derive the requested awareness mechanism, the requested awareness service area, and a list of BSs and WTRUs for awareness operation in the requested awareness service area.

[0129] When network slice information is included at (1), only network entities (such as AMF, RAN, SOMF) belonging to the network slice and WTRUs allowed by the network slice can be selected.

[0130] If the location information of the target WTRU is provided at (4), it can be considered as an input for determining or calculating the sensing service area, and / or a list of BSs and WTRUs for performing sensing operations.

[0131] In addition, the ISANF may refer to the PCF to check the SLA of the awareness service requested by the application function (AF) and decide whether the requested awareness service is supported, and if so, the QoS requirements for the requested awareness service should be supported.

[0132] If the request is for sensing data in a fixed sensing service area location, the ISANF may derive a candidate list of BSs and WTRUs that perform the sensing mechanism over the requested area.

[0133] Alternatively, the ISANF may request the AMF to derive the awareness service area based on the location of the target WTRU and provide a complete list of Tracking Area Identifiers (TAIs) or a list of BSs (gNB IDs) for all associated awareness-capable WTRUs. Based on the reported location of the target WTRU, the ISANF may determine the awareness service area and the ISANF may select or derive a candidate list of BSs and WTRUs that perform the awareness mechanism on the determined awareness service area. Alternatively, the ISANF may request the AMF to provide a candidate list of BSs and WTRUs that are capable of awareness based on the requested awareness service area or based on the identity and location of the target WTRU. In this case, there may be additional signaling between the ISANF and the AMF (6) to query the awareness service area information or a list of BSs and WTRUs for each awareness service area or location of the target WTRU.

[0134] Based on the capabilities of each base station and WTRU, the ISANF may determine the sensing mechanism and the list of base stations and WTRU(s) to perform the sensing mechanism. If there are any WTRUs that support non-3GPP (N3GPP) sensing methods, those N3GPP sensing capabilities may also be considered when selecting the sensing mechanism, which may utilize N3GPP sensing data.

[0135] At (6), the ISANF may send a sensing request (e.g., a Nisanf_Sensing Request message) to the AMF serving the target WTRU or serving the requested area, and connect with or control the BS and (one or more) WTRUs in the list of BSs and WTRUs to perform sensing. When the AMF cannot serve the target WTRU or the requested area, multiple AMFs may be selected to serve the target WTRU or the requested area, and the ISANF may send a Nisanf_Sensing Request message to each selected AMF.

[0136] The awareness request may include requested awareness area information (e.g., a list of TAIs, a list of cell IDs), a list of BSs (gNB IDs) and a list of WTRUs, application IDs, requested awareness mechanisms with QoS requirements, and / or network slice information.

[0137] Alternatively, when the ISANF knows the service area of ​​the SOMF, the ISANF may include the target SOMF in the message.

[0138] When network slice information is included, only network entities (such as RAN, SOMF, etc.) belonging to the network slice can be selected for operation, and the WTRUs in the WTRU list can be selected among the WTRUs allowed at the network slice.

[0139] At (7), after receiving the Nisanf_Sensing request from ISANF, AMF may send a sensing request (e.g., Namf_Sensing request message) to SOMF. The Namf_Sensing request message may include the requested sensing mechanism with QoS requirements, a list of involved BSs and UEs, application ID, target area, and network slice information.

[0140] Alternatively, the list of BSs and WTRUs and / or the sensing mechanism may be determined by the SOMF or the AMF. For example, when the AMF / SOMF decides the sensing mechanism and / or the list of BSs and WTRUs, the AMF / SOMF may determine the candidate list of BSs and WTRUs based on the requested sensing area information. Furthermore, the AMF / SOMF may determine the sensing mechanism and the target list of BSs and WTRUs based on the requested sensing mechanism with QoS requirements, and the list of allowed or restricted applications and the capabilities of the entities for sensing each entity in the candidate list. In this case, the ISANF / AMF may include the requested sensing area information in the Nisanf_Sensing request and the Namf_Sensing request, and may not include the list of BSs and WTRUs and / or the sensing mechanism in the Nisanf_Sensing request and the Namf_Sensing request.

[0141] When network slice information is included, a WTRU from a list of WTRUs may be selected among the WTRUs allowed at the network slice.

[0142] The list of BSs and WTRUs involved in the Namf_Sensing request may be different from the list of BSs and WTRUs in the Nisanf_Sensing request message, because the AMF may narrow the range selection based on the status and circumstances of the WTRU and BS (for example, resource load, WTRU's sensing operation capability, WTRU's mobility state (such as idle mode, connected mode, or connected but RRC inactive mode)).

[0143] The AMF may coordinate with the PCF or UDM to check the policy configuration regarding the capabilities of the candidate WTRUs. For example, the WTRU's capabilities may include a list of application IDs that are allowed or not allowed to be used for sensing operations by the WTRU. Based on coordination with the PCF and UDM, the AMF may narrow down the list of WTRUs to be selected for sensing operations.

[0144] At (8), the SOMF may develop coordination information for controlling the sensing operations of the BSs and WTRUs in the list based on the requested sensing mechanism and QoS requirements. For example, the SOMF may determine the roles of the sensing operations (such as sender of (one or more) sensing signals, receiver of (one or more) sensing signals, etc.), and may determine the sensing period and / or the waveform of the sensing signal.

[0145] Alternatively, if a list of BSs and WTRUs is not provided, the SOMF may derive a list of BSs and WTRUs for sensing operation based on the requested sensing service area, and may develop coordination information for controlling sensing operation of the BSs and UEs in the list based on the requested sensing mechanism and QoS requirements.

[0146] The SOMF may coordinate with the PCF or UDM to check the policy configuration regarding the capabilities of the candidate UEs, such as the list of application IDs that are allowed or not allowed to be used for sensing operations by the UE. Based on the coordination with the PCF and UDM, the SOMF may narrow down the list of WTRUs to be selected for sensing operations.

[0147] Alternatively, the resource allocation for sending the sensing signal may be determined by the BS sensing signal(s) and may be notified to other entities in the list, ie, the BS and the UE.

[0148] At (9), the SOMF may send a sense request to the entities involved in the sense operation. When sending a sense request to the involved WTRU, the SOMF may send it through the AMF using a NAS container. When sending a sense request to the involved BS, the SOMF may send it using direct communication between the SOMF and the BS or through the AMF using an N2 connection.

[0149] The WTRU-directed awareness request message and the BS-directed awareness request message may include different information. For example, the WTRU-directed awareness request message may include information about the awareness area that the WTRU needs to sense, the BS that the WTRU needs to monitor, etc. For example, the BS-directed awareness request message may include some configuration information (e.g., frame structure, resource allocation information, etc.) and / or a list of BS information to coordinate the sending of awareness signals.

[0150] At (10), based on the coordination from the SOMF, the BS and WTRU perform collecting perception measurement data.

[0151] At (11), the collected perception measurement data may be sent to the SOMF.

[0152] When the collected perception measurement data is sent, it may first be collated at the WTRU or BS and then may be sent to the SOMF. Which entity will collect the perception data may be indicated in the coordination information.

[0153] At (12), the SOMF may calculate a perception result using the collected perception measurement data received at (11).

[0154] At (13), SOMF may send the sensing result to AMF via Namf_Sensing response.

[0155] Alternatively, another entity (e.g., a BS or one of the WTRUs in the list) or another dedicated network function may calculate the sensing result. For example, if the BS calculates the sensing result, the collected sensing measurement data may be sent to the BS before (11). The calculation result may be sent by the BS to the SOMF at (11). In some cases, (12) may not be performed.

[0156] At (14)-(15), after receiving the sensing result, the AMF may report the sensing result to the ISANF via the NisaNF_Sensing response. And, the ISANF may report the sensing result to the AF via the Service Response message. When multiple AMFs are involved in the sensing service, at (15), the sensing results collected from the involved AMFs may be included in the sensing response to the AF.

[0157] Figure 6 An example of a call flow for an NF-initiated awareness procedure is shown.

[0158] At (1), based on some configuration or a request from another NF or AF, the NF may be triggered to request a sensing service, and the NF may send a sensing service request message. The sensing service request message may include a specific type of sensing service, such as intrusion detection, traffic monitoring, rain detection, drone detection, etc. The sensing service request message may include specific QoS requirements for the sensing service, such as sensing accuracy, latency, sensing frequency, and resolution. The sensing service request message may request a certain sensing mechanism that needs to be implemented in the 5GS, such as BS-based sensing only, BS and WTRU-cooperative sensing, or WTRU-based sensing only.

[0159] When the awareness service is requested for a fixed awareness service area, the awareness service area may be included. When the awareness service is for a specific target WTRU(s), target WTRU(s) information may be included. When the target WTRU(s) information is included but the awareness service area is not included, the awareness service area may be determined based on the location of the target WTRU(s) when the awareness operation is required.

[0160] The perception service request message may request an event-triggered perception service report, or a periodic perception service report. When an event-triggered perception service report is requested, it may include a perception report triggering condition. When a triggering condition is included, other parameters may also be included, such as a perception report start time and a perception report end time. The triggering condition may include logical data (for example, whether a certain event is detected) and / or a value used to trigger an event report (such as reporting the event when the time the event is detected is longer than a certain value, or reporting the event when the number of detected events is greater than a certain value).

[0161] The sensing service request message may request a periodic sensing result report. If a periodic result report is requested, the sensing report start time, the sensing report end time, and the periodicity of the sensing report may be included.

[0162] At (2), if the requested sensing mechanism is included in the message at (1), it may be included in the sensing request message at (3). Otherwise, the assisting NF (ISANF) may convert the specific type of sensing service requested in the sensing request message into the requested sensing mechanism that needs to be performed in the 5GS, such as BS-based sensing only, BS and UE-cooperative sensing, or WTRU-based sensing only.

[0163] Based on the awareness mechanism and the included service area information or based on the location of the target WTRU, the ISANF may derive a candidate list of BSs and WTRUs that perform the awareness mechanism over the requested area. Alternatively, at (3), the AMF may derive a candidate list of BSs and WTRUs after receiving the awareness request from the ISANF.

[0164] At (3), the ISANF may send a NisaNF_Sensing request message to the AMF serving the target WTRU(s). The sensing request message may include the requested sensing report type, requested sensing area information, target WTRU(s) ID(s), application ID(s), and the requested sensing mechanism with QoS requirements. It may include a candidate list of BSs and WTRUs for sensing operations.

[0165] When the awareness request is for a periodic awareness service report or an event-triggered awareness service report, the awareness request may include parameters related to the requested awareness report type. For example, for a periodic awareness service report, the relevant parameters may include the awareness report start time, the awareness report end time, and the periodicity of the awareness report. For an event-triggered awareness service report, the relevant parameters may include the awareness report start time, the awareness report end time, and the awareness report triggering condition. All or some of these parameters may be included.

[0166] ISANF may manage the service request ID so that ISANF may map the requested sensing service, and the recipient of the sensing service and the service request ID may be included in the Nisanf_Sensing request message.

[0167] When the awareness service request message at (1) includes multiple target WTRUs and the target WTRUs are served by different serving AMFs, an awareness request may be sent to each AMF. The awareness request may include the target WTRUs served by the AMF.

[0168] At (4), after receiving the Nisanf_Sensing request from the ISANF, the AMF may send a Namf_Sensing request message to the SOMF. The Namf_Sensing request message may include the requested sensing report type and related parameters, the service request ID, the requested sensing mechanism with QoS requirements, the list of BSs and WTRUs, the application ID and / or the target WTRU ID.

[0169] If there is a candidate list of BSs and WTRUs received at (3), then the candidate list may be used to derive a list of BSs and WTRUs that participate in the sensing procedure. When available, the AMF may derive the list of BSs and WTRUs based on the sensing mechanism, the requested service area, and the candidate list of BSs and WTRUs.

[0170] At (5), the SOMF may develop coordination information for controlling the sensing operations of the BSs and WTRUs in the list based on the requested sensing mechanism and QoS requirements. For example, the SOMF may determine the roles of the sensing operations (such as sender(s) of sensing signals(s), receiver(s) of sensing signals(s), etc.) and may determine the sensing period and the waveform of the sensing signal.

[0171] Alternatively, if no candidate BS and WTRU list is provided, the SOMF may derive a list of BS and WTRUs for sensing operation based on the requested sensing service area, and may develop coordination information for controlling sensing operation of the BS and WTRUs in the list based on the requested sensing mechanism and QoS requirements.

[0172] The SOMF may coordinate with the PCF or UDM to verify the policy configuration regarding the capabilities of the candidate WTRUs, such as the list of application IDs that are allowed or not allowed to be used by the WTRU for sensing operations. Based on the coordination with the PCF and UDM, the SOMF may narrow down the list of WTRUs to be selected for sensing operations.

[0173] The SOMF may request BS(s) resource allocation for sending sensing signals in a sensing period.When requesting resource allocation for periodic sensing operation, relevant parameters such as time period and periodicity may be included in the request.

[0174] Alternatively, the resource allocation for sending the awareness signal may be decided by the BS(s) and may be informed to the other entities in the list, ie, the BS and the WTRU.

[0175] At (6), the SOMF may send an Awareness Request message to the entities involved in the Awareness operation. When sending the Awareness Request message to the involved WTRU(s), the SOMF may send the message through the AMF using a NAS container. When sending the Awareness Request message to the involved BS(s), the SOMF may send the message using direct communication between the SOMF and the BS or through the AMF using an N2 connection.

[0176] The WTRU-directed awareness request message and the BS-directed awareness request message may include different information. For example, the WTRU-directed awareness request message may include information about the awareness area that the WTRU needs to sense, the BS that the WTRU needs to monitor, etc. For example, the BS-directed awareness request message may include some configuration information (such as frame structure and resource allocation information) and a list of BS information to coordinate the sending of awareness signals.

[0177] When the requested perception report type is for periodic perception service reporting or event-triggered perception service reporting, the perception service request may include parameters for periodic perception (such as start time, end time, and periodicity of perception) so that the BS and WTRU involved can perform periodic perception operations based on coordination information.

[0178] When a service request ID is received at (4), the service request ID may be included in the awareness request.

[0179] The awareness request message may include the ID or address of the SOMF as service SOMF information.

[0180] At (7), based on the coordination from the SOMF, the BS and WTRU may perform the collection of perception measurement data.

[0181] At (8), the collected perception measurement data may be sent to the SOMF.

[0182] When the service request ID is received at (6), the service request ID may be included in the report to the SOMF.

[0183] If the service SOMF information is received at (6), the report may be sent to the SOMF indicated by the service SOMF information.

[0184] When the collected perception measurement data is sent, it may first be collated at the WTRU or at the BS and then may be sent to the SOMF. Which entity will collate the perception data may be indicated in the coordination information.

[0185] At (9), the SOMF may calculate a perception result using the collected perception measurement data received at (8).

[0186] At (10), the SOMF may send the sensing result to the AMF via a Namf_Sensing response message. If a service request ID is received at (8), the service request ID may be included.

[0187] When a periodic sensing operation is requested by the SOMF, the BS and WTRU may perform (7) and (8) according to the requested time interval and periodicity. Whenever a sensing response is received from the WTRU and BS, the SOMF may perform (9) and (10).

[0188] exist Figure 6 In alternative C, when the perception report type is a periodic perception report, the SOMF may repeat (5) based on the periodicity, and (6), (7), (8) and (9) will be repeated during the requested time interval. The SOMF may repeat sending the perception response to the AMF at (10) during the requested time interval. When the perception report type is an event-triggered perception report, the SOMF may repeat (5) and (6), and (7), (8) and (9) will be repeated until the perception result calculated at (9) meets the condition of the event-triggered perception service report. When the calculated perception result meets the condition of the event-triggered perception service report, the SOMF may send a perception response including the perception result to the AMF.

[0189] After receiving the sensing result, AMF reports the sensing result to ISANF via Nisanf_Sensing response at (11). And ISANF reports the sensing result to NF via Sensing Service Response at (12).

[0190] exist Figure 6In alternative B, when the perception report type is a periodic perception report, the AMF may repeat (4) based on the periodicity, and steps (5), (6), (7), (8), (9) and (10) will be repeated during the requested time interval. The AMF may repeat sending the perception response to the ISANF at (11) during the requested time interval. When the perception report type is an event-triggered perception report, the AMF may repeat steps (4) and (5), and steps (6), (7), (8), (9) and (10) will be repeated until the result received at (10) meets the conditions for the event-triggered perception service report. When the calculated perception result meets the conditions for the event-triggered perception service report, the AMF may send a perception response including the perception result to the ISANF. For a perception request whose perception report type is periodic perception report or event-triggered perception report, when the AMF periodically repeats (4) based on the included parameters, or the AMF repeats (4) until the conditions for event-triggered perception report are met, the perception service type and related parameters may be maintained within the AMF, and those parameters may not be included in the perception request at (4).

[0191] exist Figure 6 In alternative A, when the perception report type is a periodic perception report, the ISANF may repeat (3) based on the periodicity, and (4), (5), (6), (7), (8), (9), (10), and (11) will be repeated within the requested time interval. The ISANF may repeat sending the perception response to the NF at (12) during the requested time interval. When the perception report type is an event-triggered perception report, the ISANF may repeat step (3), and steps (5), (6), (7), (8), (9), and (10) will be repeated until the result received at (11) meets the condition of the event-triggered perception service report. When the received perception result meets the condition of the event-triggered perception service report, the ISANF may send a perception response including the perception result to the NF at (12). For a perception request whose perception report type is a periodic perception report or an event-triggered perception report, when the ISANF periodically repeats (3) based on the included parameters, or when the ISANF repeats (3) until the conditions for the event-triggered perception report are met, the perception service report type and related parameters may be maintained in the ISANF, and those parameters may not be included in the perception request at (3).

[0192] Figure 7 An example of a call flow for an NF-initiated awareness procedure operating using the services of the AMF is shown.

[0193] At (1), based on a certain configuration or a request from another NF or AF, the NF may be triggered to request a sensing service and may send a sensing service request message to the serving AMF of the target WTRU or the AMF serving the requested sensing service area. The sensing service request message may include a specific type of sensing service, such as intrusion detection, traffic monitoring, rainfall detection, drone detection, etc. The sensing service request message may include specific QoS requirements for the sensing service, such as sensing accuracy, latency, sensing frequency, resolution. The sensing service request message may request a sensing mechanism that needs to be performed in the 5GS, such as BS-based sensing only, BS and WTRU collaboration-based sensing, or UE-based sensing only. When the sensing service is requested for a fixed sensing service area, the sensing service area may be included.

[0194] When the sensing service is targeted at (one or more) WTRUs, (one or more) target WTRU information may be included.

[0195] When target WTRU(s) information is included but the sensing service area is not included, the sensing service area may be determined based on the location of the target WTRU(s) when the sensing operation needs to be performed.

[0196] The perception service request message may request an event-triggered perception service report or a periodic perception service report. When an event-triggered perception service report is requested, it may include a perception report triggering condition. When there is an included triggering condition, other parameters may also be included, such as a perception report start time and a perception report end time. The triggering condition may include logical data (e.g., whether a certain event is detected) and / or a value used to trigger the reporting of the event (e.g., reporting the event when the time for which the event is detected is longer than a certain value, or reporting the event when the number of detected events is greater than a certain value).

[0197] The sensing service request message may request a periodic sensing result report. If a periodic result report is requested, the sensing report start time, the sensing report end time, and the periodicity of the sensing report may be included.

[0198] At (2), upon receiving the awareness service request from the NF, the AMF may communicate with the ISANF to determine the awareness mechanism from the requested awareness service. The ISANF may also provide a candidate list of BSs and WTRUs that perform the derived awareness mechanism over the requested area based on the derived awareness mechanism and the included service area information.

[0199] At (3), for the requested awareness service, the AMF may send a Namf_Sensing request message to the SOMF. The Namf_Sensing request message may include the requested awareness report type and related parameters, service request ID, requested awareness mechanism with QoS requirements, list of BSs and WTRUs, application ID, and target WTRU ID.

[0200] If there is a candidate list of BSs and WTRUs received at (2), then the candidate list may be used to derive a list of BSs and WTRUs that participate in the sensing procedure. When available, the AMF may derive the list of BSs and WTRUs based on the sensing mechanism, the requested service area, and the candidate list of BSs and WTRUs.

[0201] At (4), the SOMF may develop coordination information for controlling the sensing operations of the BSs and WTRUs in the list based on the requested sensing mechanism and QoS requirements, for example, the SOMF may decide the roles of the sensing operations (such as the sender(s) of the sensing signals and the receiver(s) of the sensing signals), and may determine the sensing period and / or the waveform of the sensing signal.

[0202] Alternatively, if a list of BSs and WTRUs is not provided, the SOMF may derive a list of BSs and WTRUs for sensing operations based on the requested sensing service area, and may develop coordination information for controlling sensing operations of the BSs and WTRUs in the list based on the requested sensing mechanism and QoS requirements.

[0203] The SOMF may coordinate with the PCF or UDM to verify the policy configuration regarding the capabilities of the candidate WTRUs. This may include a list of application IDs that are allowed or not allowed to be used by the WTRU for sensing operations. Based on coordination with the PCF and UDM, the SOMF may narrow down the list of WTRUs selected for sensing operations.

[0204] The SOMF may request BS(s) resource allocation for sending sensing signals in a sensing period, and when requesting resource allocation for periodic sensing operation, the time period and periodicity may be included in the request.

[0205] Alternatively, the resource allocation for sending the sensing signal may be determined by the BS sensing signal(s) and may be notified to other entities in the list, ie, the BS and the UE.

[0206] At (5), the SOMF may send an Awareness Request message to the entities involved in the Awareness operation. When sending the Awareness Request message to the involved WTRU, the SOMF may send the message through the AMF using a NAS container. When sending the Awareness Request to the involved BS, the SOMF may send the Awareness Request using direct communication between the SOMF and the BS or through the AMF using an N2 connection.

[0207] The WTRU-directed awareness request message and the BS-directed awareness request message may include different information. For example, the WTRU-directed awareness request message may include information about the awareness area that the WTRU needs to sense, the BS that the WTRU needs to monitor, etc. For example, the BS-directed awareness request message may include some configuration information (such as frame structure and resource allocation information) and a list of BS information to coordinate the sending of awareness signals.

[0208] When the requested perception report type is for periodic perception service reporting, the perception service request may include parameters for periodic perception (such as start time, end time, and perception periodicity) so that the BS and UE involved can perform periodic perception operations based on the coordination information.

[0209] When a service request ID is received at (4), the service request ID may be included in the awareness request.

[0210] The awareness request message may include the ID or address of the SOMF as service SOMF information.

[0211] At (6), based on the coordination from the SOMF, the BS and WTRU collect perception measurement data.

[0212] At (7), the collected perception measurement data may be sent to the SOMF.

[0213] When the service request ID is received at (5), the service request ID may be included in the report to the SOMF.

[0214] If the service SOMF information is received at (5), the report may be sent to the SOMF indicated by the service SOMF information.

[0215] When the collected perception measurement data are sent, they may first be collated at the WTRU or at the BS and then may be sent to the SOMF. Which entity shall collect the perception data may be indicated in the coordination information.

[0216] At (8), the SOMF may calculate a perception result using the collected perception measurement data received at (7).

[0217] At (9), the SOMF may send the sensing result to the AMF via a Namf_Sensing response. If a service request ID is received at (7), the service request ID may be included.

[0218] When a periodic sensing operation is requested by the SOMF, the BS and WTRU perform (6) and (7) based on the requested time interval and periodicity. And whenever a sensing response is received from the WTRU and BS, the SOMF may perform (8) and (9).

[0219] exist Figure 7 In alternative E, when the perception report type is a periodic perception report, the SOMF may repeat (4) based on the periodicity, and (5), (6), (7) and (8) will be repeated during the requested time interval. The SOMF may repeat sending the perception response to the AMF at (9) during the requested time interval. When the perception report type is an event-triggered perception report, the SOMF may repeat (4) and (5), and (6), (7) and (8) will be repeated until the perception result calculated at (8) meets the condition of the event-triggered perception service report. When the calculated perception result meets the condition of the event-triggered perception service report, the SOMF may send a perception response including the perception result to the AMF at (9).

[0220] After receiving the sensing result, the AMF may report the sensing result to the NF via a sensing service response at (10).

[0221] exist Figure 7In alternative D, when the perception report type is a periodic perception report, the AMF may repeat (3) based on the periodicity, and (4), (5), (6), (7), (8) and (9) will be repeated during the requested time interval. The AMF may repeat sending the perception response to the NF at (10) during the requested time interval. When the perception report type is an event-triggered perception report, the AMF may repeat (3) and (4), and (5), (6), (7), (8) and (9) will be repeated until the result received at (9) meets the condition of the event-triggered perception service report. When the received perception result meets the condition of the event-triggered perception service report, the AMF may send a perception response including the perception result to the NF. For a perception request whose perception report type is a periodic perception report or an event-triggered perception report, when the AMF periodically repeats (3) based on the included parameters, or the AMF repeats (3) until the conditions for the event-triggered perception report are met, the perception service type and related parameters may be maintained within the AMF, and those parameters may not be included in the perception request at (3). The exposure service of the perception event is described in this document. With respect to the perception service, the NF involved in the integrated perception service (such as ISANF, AMF and SOMF) can provide the perception service to other NFs.

[0222] ISANF can provide other NFs with a perception method conversion service. The perception method conversion service can be a service that determines the perception method that can be executed in the 5GC for the requested perception service.

[0223] NF consumers (e.g., NEF and AMF) may send a perception method conversion service request to ISANF. The perception method conversion service request may include the requested perception service, and may include the requested perception service area and target WTRU information.

[0224] The ISANF may respond to the NF consumer with a Sensing Method Conversion Service Response. This response message includes the Sensing Method that can be executed in the 5GC for the requested Sensing Service and may additionally include a list of BSs and WTRUs to execute the Sensing Method in the requested Sensing Service Area or to provision the Sensing Service based on the location of the target WTRU.

[0225] ISANF can provide event exposure services when it perceives other NFs.

[0226] When an NF consumer subscribes to an ISANF's perception events, the event subscription message may include the requested perception event information. Furthermore, the request may include the requested target WTRU information, the requested perception service area, and the threshold for reporting results. For example, the NF consumer may request a report when rain is detected in the area surrounding the target WTRU's location. As another example, the NF consumer may request a report of an intrusion detection event in a certain area if the detected intrusion lasts for several seconds.

[0227] After receiving a perception event subscription, the ISANF can trigger a perception operation based on the requested perception event information and other parameters (such as the perception service area and threshold) until the perception result based on the perception data measured at the requested perception service area or at the location or surrounding area of ​​the requested target UE exceeds the requested threshold. When the perception result exceeds the requested threshold, the ISANF notifies the subscribed NF consumer or other NFs indicated when subscribing to the perception event of the perception result and any other relevant information. The AMF and / or SOMF can provide event exposure services when sensing other NFs.

[0228] When an NF consumer subscribes to a perception event of an AMF or SOMF, the event subscription message may include the requested perception event information and / or the requested perception method. In addition, the request may include the requested target WTRU information, the requested perception service area, a list of BS and WTRU information that perform the requested perception event, and a threshold for reporting results. When a perception event subscription is received from an NF consumer, the NF provider (i.e., AMF or SOMF) may derive the perception method from the requested perception event information, and may derive a list of BS and WTRU information based on the determined perception method to perform the perception operation. The AMF or SOMF may use the perception method conversion service of the ISANF to determine the perception method and derive a list of WTRU and BS.

[0229] After receiving the perception event subscription, based on the requested perception event information and other parameters (such as perception service area and threshold), the NF producer (i.e., AMF or SOMF) can trigger the perception operation until the perception result based on the perception data measured at the requested perception service area or at the location or surrounding area of ​​the requested target UE exceeds the requested threshold. When the perception result exceeds the requested threshold, the NF producer notifies the subscribed NF consumer or other NFs indicated when subscribing to the perception event of the perception result and any other relevant information.

[0230] Figure 8An example of a call flow for a service request procedure with a trigger associated with an awareness service is shown. In this example, a service request message may be received from an AF, the requested service may have an associated trigger condition, and the trigger condition may be related to the awareness service.

[0231] At (1), the NF may receive a service request message directly from the AF or via the NEF or PCF, which may include the requested network operation and the triggering conditions for the network operation. Alternatively, the NF may be configured with a policy including verification conditions related to the sensing event.

[0232] In one example, the SMF may receive policy rules regarding session management for certain WTRUs, with the condition that the session be activated only when intrusion detection is monitored in certain service areas.

[0233] In another example, the SMF may be configured to contact the PCF for updating the PDU session, provided that the PCF is contacted when the mobility trajectory of the target WTRU has changed.

[0234] At (2), based on the received request or configured policy, the NF can identify the requested sensing events to monitor as conditions for network operation. For example, the NF can identify an intrusion detection service for a certain area with a threshold, such as when the number of intrusion detections exceeds a threshold, it should be reported.

[0235] At (3), based on the identified sensing event, the requested sensing service area, and the target WTRU information, the NF may discover and select a NF (e.g., AMF) to handle the sensing event, and may send an event subscription request message to the selected NF. The event subscription request message may include the requested sensing event information, the target WTRU information, the sensing service area information, and the threshold for reporting sensing results. The sensing event subscription may include the sensing mechanism requested for the sensing service.

[0236] At (4), if necessary, to determine the awareness mechanism, the NF (e.g., AMF) may utilize the information in the awareness method conversion service message. The awareness method conversion service request message may include the requested awareness service, service area information, and target WTRU information.

[0237] At (5), the NF (e.g., AMF) may receive a Perception Method Conversion Service Response message from the ISANF. The Perception Method Conversion Service Response message may include the perception methods executable in the 5GC for the requested perception service, and a list of BSs and WTRUs that execute the perception methods in the requested perception service area or provision the perception service based on the location of the target WTRU.

[0238] At (6), the NF (e.g., AMF) may initiate a sensing operation based on the information received at (3) and derive a sensing mechanism based on the information from (2) and (5). The sensing operation may be similar to that described above regarding Figure 7 The sending operation described in alternative D of FIG. When there is a threshold for reporting the sensing event at (3), the sensing operation can be repeated until a sensing result that meets the threshold is obtained. When there is a sensing event whose sensing result meets the threshold, the result is reported to the NF in a sensing result notification message.

[0239] At (7), based on the notification result, the NF can initiate relevant network operations according to the AF's request or according to the policy configuration.

[0240] Figure 9 An example flow chart of a process for performing awareness measurements by a WTRU or BS is shown. The process begins with receiving an awareness request message 901 from the awareness operation management function (SOMF). The process then continues with collecting awareness measurement data 902. Finally, the results of the data collection are sent to the SOMF in a awareness result message 903.

[0241] Figure 10 A flowchart illustrating an example process for exposing services for an awareness event triggered by a request for a network operation is shown. The AF may trigger a service request 1001 toward the first NF by sending a service request message to the first NF. The service request message may be received from the AF via at least one of a network exposure function (NEF) or a policy control function (PCF). The service request message may include a request for a network operation and associated triggering conditions. The request may indicate that the requested network operation is to be performed when the triggering conditions are met.

[0242] Based on the trigger condition, the first NF may identify a perception event 1002 associated with the trigger condition. The trigger condition may be associated with one or more perception events. The perception event may be characterized by one or more perception parameters and thresholds. The perception event may be associated with one or more WTRUs. The perception event may be associated with the location of one or more WTRUs. The perception event may be associated with a specific area, which may be identified by a cell identity, a tracking area identity, or a geo-fence configuration. The perception event may be associated with the network slice for which perception is to be performed, which may be identified by its single network slice selection assistance information (S-NSSAI). The perception event may be associated with a configured time value, thereby indicating that the event has occurred when a certain condition is met within a time period equal to or greater than the configured time value.

[0243] The first NF may determine a sensing mechanism to be performed 1003. The sensing mechanism may be one of network-based sensing, WTRU-based sensing, or collaborative-based sensing (eg, network and WTRU collaboration).

[0244] The first NF may subscribe to the awareness event 1004 with the second NF. The second NF may be an AMF. The first NF may send an event subscription request message to the AMF. The subscription request may indicate event-triggered awareness service reporting, periodic awareness service reporting, or both.

[0245] The first NF may receive a sensing result from the second NF, for example, a sensing result notification message 1005 from the AMF. Based on the received sensing result notification message, the NF may initiate relevant network operations 1006 as requested by the AF. The result may include, for example, intrusion detection in the service area. The network operation may include, for example, PDU session activation or PDU session modification for WTRUs deployed in the service area. The network operation may be associated with a configured policy.

[0246] Figure 11 An example flow chart illustrates a process for providing an exposure service for an integrated awareness assisted network function (ISANF) for an awareness event. The ISANF may receive an awareness service request message 1101 from an AF. The awareness service request message may include a configuration of one or more triggering events that may trigger the initiation of the requested awareness service. Based on the configured triggering events, the ISANF may subscribe to event exposure services 1102 from the NF associated with the triggering event in the 5GC. The ISANF may receive an event notification 1103 from the NF. The ISANF may select an awareness mechanism to be used 1104. The awareness mechanism may be one of network-based awareness, WTRU-based awareness, or collaborative awareness (e.g., network and WTRU collaboration). The ISANF may determine the BS, WTRU, and 5GC NF associated with the requested awareness and the selected awareness mechanism 1105 and may send an awareness request 1106 to the determined 5GC NF. The AISNF may receive an awareness result 1107 and may forward the result to the requesting AF 1108.

[0247] Although features and elements are described above in specific combinations, it will be understood by those skilled in the art that each feature or element can be used alone or in combination with other features and elements. In addition, the methods described herein can be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted via a wired or wireless connection) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor storage devices, magnetic media (such as internal hard disks and removable disks), magneto-optical media, and optical media (such as CD-ROM disks and digital versatile disks (DVDs)). A processor associated with the software can be used to implement a radio frequency transceiver used in a WTRU, UE, terminal, base station, RNC, or any host computer.

Claims

1. A method for integrating a perceptual assistance function, the method comprising: receiving a request from an application function (AF) to establish an awareness service, the request including configuration information associated with one or more triggering events that trigger initiation of the requested awareness service; subscribing to an event exposure service from a first network function (NF) in a core network (CN) based on the configuration information; receiving an event notification from a first NF in the CN; Determining a second NF in the CN based on the event notification; Select the perception mechanism to use; Sending a sensing request associated with the selected sensing mechanism to a second NF in the CN; receiving a sensing result from a second NF in the CN; as well as The received sensing result is sent to the AF.

2. The method according to claim 1, wherein The received request to establish a sensing service further includes quality of service (QoS) requirements, including one or more of sensing accuracy, sensing latency, sensing frequency, or sensing resolution.

3. The method according to claim 1 or 2, wherein: The received request to establish an awareness service further includes configuration information identifying one or more geographic regions for which awareness is to be performed.

4. The method according to any one of claims 1 to 3, wherein: The received request to establish the awareness service further includes information associated with the network slice on which awareness is to be performed, such as single network slice selection assistance information (S-NSSAI).

5. The method according to any one of claims 1 to 4, wherein: The one or more triggering events are associated with wireless transmit-receive unit (WTRU) mobility events.

6. The method according to any one of claims 1 to 5, wherein: The one or more triggering events are associated with a WTRU data session state.

7. The method according to any one of claims 1 to 6, wherein: The event notification includes the identity of the WTRU and the Access and Mobility Management Function (AMF) serving the WTRU.

8. The method according to any one of claims 1 to 7, wherein: The second NF is AMF.

9. The method according to any one of claims 1 to 8, wherein: The selected sensing mechanism to be used includes one of: network-based sensing, WTRU-based sensing, or network and WTRU-cooperative sensing.

10. The method according to any one of claims 1 to 9, wherein The sensing request sent to the second NF includes at least one of the following: the identity of one or more base stations (e.g., eNB, gNB) performing the sensing operation, the identity of one or more WTRUs performing the sensing operation, the requested sensing mechanism, the sensing QoS requirements, information about the network slice on which sensing is to be performed (e.g., S-NSSAI), or the sensing area.

11. A device for implementing an integrated perception assistance function, the device comprising a processor and a communication interface, wherein the processor and the communication interface are configured to: receiving a request from an application function (AF) to establish an awareness service, the request including configuration information associated with one or more triggering events that trigger initiation of the requested awareness service; subscribing to an event exposure service from a first network function (NF) in a core network (CN) based on the configuration information; receiving an event notification from a first NF in the CN; Determining a second NF in the CN based on the event notification; Select the perception mechanism to use; Sending a sensing request associated with the selected sensing mechanism to a second NF in the CN; receiving a sensing result from a second NF in the CN; as well as The received sensing result is sent to the AF.

12. The apparatus according to claim 11, wherein The received request to establish a sensing service further includes quality of service (QoS) requirements, including one or more of sensing accuracy, sensing latency, sensing frequency, or sensing resolution.

13. The apparatus according to claim 11 or 12, wherein: The received request to establish an awareness service further includes configuration information identifying one or more geographic regions for which awareness is to be performed.

14. The apparatus according to any one of claims 11 to 13, wherein The received request to establish the awareness service further includes information associated with the network slice on which awareness is to be performed, such as single network slice selection assistance information (S-NSSAI).

15. The apparatus according to any one of claims 11 to 14, wherein The one or more triggering events are associated with wireless transmit-receive unit (WTRU) mobility events.

16. The apparatus according to any one of claims 11 to 15, wherein The one or more triggering events are associated with a WTRU data session state.

17. The apparatus according to any one of claims 11 to 16, wherein The event notification includes the identity of the WTRU and the Access and Mobility Management Function (AMF) serving the WTRU.

18. The apparatus according to any one of claims 11 to 17, wherein The second NF is AMF.

19. The apparatus according to any one of claims 11 to 18, wherein The selected sensing mechanism to be used includes one of: network-based sensing, WTRU-based sensing, or network and WTRU-cooperative sensing.

20. The apparatus according to any one of claims 11 to 19, wherein The sensing request sent to the second NF includes at least one of the following: the identity of one or more base stations (e.g., eNB, gNB) performing sensing operations, the identity of one or more WTRUs performing sensing operations, the requested sensing mechanism, sensing QoS requirements, information about the network slice on which sensing is to be performed (e.g., S-NSSAI), or sensing area information.

Images