Methods, architectures, apparatuses, and systems for wireless sensing

Abstract

Procedures, methods, architectures, apparatus, systems, devices, and computer program products for sensing services in a network are described. A wireless transmit receive unit can be a candidate to participate in a sensing service in a network as a sensing entity. The WTRU can send capability information to the network for participating in the sensing service using its resources. The network can select a sensing entity to participate in the sensing service based on the capability information received from the candidate sensing entities, and can send an estimate of a reward / compensation to the candidate sensing entities for using the sensing entity's resources in the sensing service. The candidate sensing entities can send an acceptance or rejection to participate in the sensing service as a reply.

Description

Cross-references to related applications

[0001] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 627,927, filed February 1, 2024, which is incorporated herein by reference in its entirety. Technical Field

[0002] This disclosure generally relates to the fields of communications, software, and coding, including, for example, methods, architectures, apparatuses, and systems related to wireless sensing. Background Technology

[0003] Wireless sensing is a technology enabling the acquisition of information about the characteristics of an environment and / or objects within that environment. Wireless sensing uses radio waves to determine the distance (range), angle, or instantaneous linear velocity of an object. Wireless sensing services rely on the analysis of the emission, reflection, and scattering of wireless sensing signals. Example applications of wireless sensing include: object and intruder detection in predefined security zones around smart homes, highways, railways, factories, and critical infrastructure; collision avoidance and trajectory tracking for UAVs, vehicles, and AGVs; vehicle control and navigation; public safety search and rescue; rainfall monitoring and flood control; and health and motion monitoring. Summary of the Invention

[0004] Embodiments of the method are disclosed, as described below and claimed in the appended claims.

[0005] Embodiments of WTRUs are disclosed as described below and as claimed in the appended claims. Attached Figure Description

[0006] A more detailed understanding can be obtained from the following detailed description given by way of example in conjunction with the accompanying drawings. As described in detail, the figures in such drawings are exemplary. Therefore, the figures and the detailed description should not be considered limiting, and other equally valid examples are possible. Furthermore, the same reference numerals (“reference numerals”) in the figures indicate the same elements, and wherein: Figure 1A This is a system diagram illustrating an exemplary communication system; Figure 1B It shows that it can be shown Figure 1A A system diagram of an exemplary wireless transmit / receive unit (WTRU) used within the communication system shown; Figure 1C It shows that it can be shown Figure 1A A system diagram showing an exemplary radio access network (RAN) and an exemplary core network (CN) used within the communication system; Figure 1D It shows that it can be shown Figure 1AThe system diagram shown illustrates yet another exemplary RAN and yet another exemplary CN used within the communication system. Figure 2 It is a reference model for 5G / next-generation networks; Figure 3 It is a pedestrian / animal intrusion detection system; Figure 4 Demonstrates intruder detection in the surrounding environment of a smart home; Figure 5 It involves WTRU sensing of both the base station and the object; Figure 6 This is a sequence diagram of an embodiment of a WTRU compensation method for providing sensing services; Figure 7 This is a sequence diagram of an embodiment of a WTRU compensation method for providing sensing services; Figure 8 This is a sequence diagram of a WTRU compensation method for providing sensing services according to an embodiment; and Figure 9 This is a flowchart of a method according to an embodiment. Detailed Implementation

[0007] In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments and / or examples disclosed herein. However, it will be understood that such embodiments and examples may be practiced without some or all of the specific details set forth herein. In other instances, well-known methods, procedures, components, and circuits have not been described in detail so as not to obscure the following description. Furthermore, embodiments and examples not specifically described herein may be practiced in place of or in combination with the embodiments and other examples expressly, implicitly, and / or inherently described, disclosed, or otherwise provided herein (collectively, the “Provided”). Although various embodiments are described and / or claimed herein in which devices, systems, apparatuses, etc., and / or any elements thereof perform operations, processes, algorithms, functions, etc., and / or any part thereof, it should be understood that any embodiment described and / or claimed herein assumes that any device, system, apparatus, etc., and / or any element thereof is configured to perform any operation, process, algorithm, function, etc., and / or any part thereof.

[0008] Abbreviations and acronyms ABMF Account and Balance Management Functions AMF access and mobility management functions AS Application Server CCS Converged Billing System CDR call details D2D device to device DDNMF Direct Discovery Name Management Function ISANF Integrated Sensing Assist NF NEF Network Exposure Function NF Network Functions N3IWF Non-3GPP Interoperability Function PCF strategy control function RF rating function SNF sensing NF SOMF sensing operation management function UDM Unified Data Management UDR Unified Data Repository 5GC 5G core 5GS 5G system.

[0009] Exemplary communication system The methods, apparatus, and systems provided herein are well-suited for communications involving wired and wireless networks. About Figures 1A to 1D An overview of various types of wireless devices and infrastructures is provided, wherein various elements of a network may utilize, perform, be arranged according to, and / or be adapted to and / or configured for use with the methods, apparatuses and systems provided herein.

[0010] Figure 1A This is a system diagram illustrating an exemplary communication system 100 that may implement one or more of the disclosed embodiments. The communication system 100 may be a multiple access system providing content such as voice, data, video, messaging, and broadcasting to multiple wireless users. The communication system 100 enables multiple wireless users to access such content through shared system resources including wireless broadband. 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-Tailed (ZT) Unique Word (UW) Discrete Fourier Transform (DFT) Extended OFDM (ZTUWDTS-sOFDM), Unique Word OFDM (UW-OFDM), Resource Block Filtered OFDM, Filter Bank Multicarrier (FBMC), etc.

[0011] like Figure 1AAs shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104 / 113, a core network (CN) 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112. However, it will be understood 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. For example, WTRUs 102a, 102b, 102c, and 102d (any of which may be referred to as a “station” and / or “STA”) may be configured to transmit and / or receive wireless signals and may include / or be user equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. Any of WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

[0012] The communication system 100 may also include base station 114a and / or base station 114b. Each of base stations 114a and 114b may be any type of device configured to wirelessly interface with at least one of WTRUs 102a, 102b, 102c, and 102d, for example, to facilitate access to one or more communication networks such as CN 106 / 115, Internet 110, and / or Network 112. For example, base stations 114a and 114b may be base transceiver stations (BTS), Node-B (NB), eNode-B (eNB), home Node-B (HNB), home eNode-B (HeNB), gNode-B (gNB), NRNode-B (NRNB), site controllers, access points (APs), wireless routers, etc. Although base stations 114a and 114b are each depicted as a single element, it will be understood that base stations 114a and 114b may include any number of interconnected base stations and / or network elements.

[0013] Base station 114a may be part of RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as base station controllers (BSCs), radio network controllers (RNCs), relay nodes, etc. Base station 114a and / or base station 114b may be configured to transmit and / or receive radio 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 coverage for a specific geographic area that may be relatively fixed or may change over time. A cell may also be divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Therefore, in an embodiment, base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In an embodiment, base station 114a may employ multiple-input multiple-output (MIMO) technology and may utilize multiple transceivers for each or any sector of the cell. For example, beamforming may be used to transmit and / or receive signals in a desired spatial direction.

[0014] Base stations 114a and 114b can communicate with one or more of WTRUs 102a, 102b, 102c, and 102d via air interface 116, which can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). Any suitable radio access technology (RAT) can be used to establish air interface 116.

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

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

[0017] In the embodiments, base station 114a and WTRUs 102a, 102b, 102c may implement radio technologies, such as using New Radio (NR) to establish NR radio access for air interface 116.

[0018] In the embodiments, base station 114a and WTRUs 102a, 102b, and 102c can implement various radio access technologies. For example, base station 114a and WTRUs 102a, 102b, and 102c can, for instance, use the dual connectivity (DC) principle to jointly implement LTE radio access and NR radio access. Therefore, the air interface used by WTRUs 102a, 102b, and 102c can be characterized by various types of radio access technologies and / or by transmissions sent to / from various types of base stations (e.g., eNBs and gNBs).

[0019] In the embodiments, base station 114a and WTRUs 102a, 102b, and 102c can implement radio technologies such as IEEE 802.11 (i.e., Wi-Fi), IEEE 802.16 (i.e., Global System for Multi-Use Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rate GSM Evolution (EDGE), and GSM EDGE (GERAN).

[0020] Figure 1ABase station 114b can be, for example, a wireless router, a home Node-B, a home eNode-B, or an access point, and can utilize any suitable RAT to facilitate wireless connectivity in localized areas such as commercial locations, homes, vehicles, campuses, industrial facilities, air corridors (e.g., for use by drones), roads, etc. In embodiments, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). In embodiments, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In embodiments, base station 114b and WTRUs 102c, 102d can utilize cellular-based RATs (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish any of small cells, picocells, or femtocells. Figure 1A As shown, base station 114b can be directly connected to Internet 110. Therefore, base station 114b does not need to access Internet 110 via CN106 / 115.

[0021] RAN 104 / 113 can communicate with CN 106 / 115, which can be any type of network configured to provide voice, data, application, and / or Voice over Internet Protocol (VoIP) services to one or more of WTRU 102a, 102b, 102c, and 102d. Data can 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. CN 106 / 115 can provide call control, billing services, location-based services, prepaid calling, internet connectivity, video distribution, etc., and / or perform advanced security functions such as user authentication. Although Figure 1A As not shown, but will be understood, RAN 104 / 113 and / or CN 106 / 115 can communicate directly or indirectly with other RANs employing the same RAT as or a different RAT than RAN 104 / 113. For example, in addition to being connected to RAN 104 / 113, which may be utilizing NR radio technology, CN 106 / 115 can also communicate with another RAN (not shown) employing any of the following radio technologies: GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or Wi-Fi.

[0022] CN 106 / 115 can also serve as a gateway for WTRU 102a, 102b, 102c, 102d to access PSTN 108, the Internet 110, and / or other networks 112. PSTN 108 may include a circuit-switched telephone network providing Common Old-Style Telephone Service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices using common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and / or Internet Protocol (IP) from the TCP / IP Internet Protocol suite. Network 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, network 112 may include another CN connected to one or more RANs, which may use the same RAT as RAN 104 / 114 or a different RAT.

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

[0024] Figure 1B This is a system diagram illustrating example WTRU 102. (See diagram below.) Figure 1B As shown, WTRU 102 may include a processor 118, a transceiver 120, a transmitting / receiving 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 components / peripherals 138, etc. It will be understood that, while remaining consistent with the embodiments, WTRU 102 may include any sub-combination of the foregoing components.

[0025] Processor 118 can be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple 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) circuit, any other type of integrated circuit (IC), a state machine, etc. Processor 118 can perform signal encoding, data processing, power control, input / output processing, and / or any other functionality that enables WTRU 102 to operate in a wireless environment. Processor 118 can be coupled to transceiver 120, which can be coupled to transmitting / receiving element 122. Although Figure 1B The processor 118 and transceiver 120 are depicted as separate components, but it will be understood that the processor 118 and transceiver 120 can be integrated together, for example, in an electronic package or chip.

[0026] Transmitting / receiving element 122 can be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) via air interface 116. For example, in one embodiment, transmitting / receiving element 122 can be an antenna configured to transmit and / or receive RF signals. In another embodiment, transmitting / receiving element 122 can be a transmitter / detector configured to transmit and / or receive, for example, IR, UV, or visible light signals. In yet another embodiment, transmitting / receiving element 122 can be configured to transmit and / or receive both RF signals and optical signals. It will be understood that transmitting / receiving element 122 can be configured to transmit and / or receive any combination of wireless signals.

[0027] Although the transmitting / receiving element 122 is in Figure 1B While depicted as a single element, WTRU 102 may include any number of transmitting / receiving elements 122. For example, WTRU 102 may employ MIMO technology. Therefore, in an embodiment, WTRU 102 may include two or more transmitting / receiving elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals via air interface 116.

[0028] Transceiver 120 can be configured to modulate signals transmitted by transmitting / receiving element 122 and demodulate signals received by transmitting / receiving element 122. As described above, WTRU 102 can have multi-mode capability. Therefore, transceiver 120 can include multiple transceivers for enabling WTRU 102 to communicate via various RATs (e.g., such as NR and IEEE 802.11).

[0029] The processor 118 of WTRU 102 can be coupled to and 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) unit or an organic light-emitting diode (OLED) display unit). The processor 118 can also output user data to the speaker / microphone 124, keypad 126, and / or display / touchpad 128. Additionally, the processor 118 can access information and store data from any suitable type of memory, such as non-removable memory 130 and / or removable memory 132. 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. Removable memory 132 may include a subscriber identity module (SIM) card, memory stick, secure digital storage (SD) card, etc. In other embodiments, the processor 118 can access information and store data from memory not actually located on WTRU 102, such as on a server or home computer (not shown).

[0030] The processor 118 may receive power from the power supply 134 and may be configured to distribute power to other components in the WTRU 102 and / or control power to those other components. The power supply 134 may be any suitable device for powering the WTRU 102. For example, the power supply 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.

[0031] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) about the current location of the WTRU 102. In addition to or instead of information from the GPS chipset 136, the WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114b) via 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 understood that, while remaining consistent with the embodiments, the WTRU 102 may acquire location information using any suitable location determination method.

[0032] The processor 118 can also be coupled to other components / peripherals 138, which may include one or more software and / or hardware modules / units providing additional features, functionality, and / or wired or wireless connectivity. For example, components / peripherals 138 may include accelerometers, electronic compasses, satellite transceivers, digital cameras (e.g., for photos and / or video), Universal Serial Bus (USB) ports, vibration devices, television transceivers, hands-free headsets, Bluetooth® modules, FM radio units, digital music players, media players, video game player modules, internet browsers, virtual reality and / or augmented reality (VR / AR) devices, activity trackers, etc. Components / peripherals 138 may include one or more sensors, which may be one or more of the following: gyroscopes, accelerometers, Hall effect sensors, magnetometers, orientation sensors, proximity sensors, temperature sensors, time sensors; geolocation sensors; altimeters, light sensors, touch sensors, magnetometers, barometers, gesture sensors, biometric sensors, and / or humidity sensors.

[0033] WTRU 102 may include a full-duplex radio, wherein the transmission and reception of some or all of the signals (e.g., associated with a specific subframe of both the uplink (e.g., for transmission) and the downlink (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 (e.g., a separate processor (not shown) or via processor 118). In embodiments, WTRU 102 may include a half-duplex radio, wherein the transmission and reception of some or all of the signals (e.g., associated with a specific subframe of both the uplink (e.g., for transmission) and the downlink (e.g., for reception)) may be concurrent and / or simultaneous.

[0034] Figure 1C This is a system diagram illustrating RAN 104 and CN 106 according to an embodiment. As described above, RAN 104 can employ E-UTRA radio technology to communicate with WTRUs 102a, 102b, and 102c via air interface 116. RAN 104 can also communicate with CN 106.

[0035] RAN 104 may include eNode-Bs 160a, 160b, and 160c, but it will be understood that RAN 104 may include any number of eNode-Bs while remaining consistent with the embodiments. eNode-Bs 160a, 160b, and 160c may each include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 116. In embodiments, eNode-Bs 160a, 160b, and 160c may implement MIMO technology. Therefore, for example, eNode-B 160a may use multiple antennas to transmit radio signals to and receive radio signals from WTRU 102a.

[0036] Each of the eNode-B 160a, 160b, and 160c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in the uplink (UL) and / or downlink (DL), etc. Figure 1C As shown, eNode-B 160a, 160b, and 160c can communicate with each other via the X2 interface.

[0037] Figure 1C The CN 106 shown may include a Mobility Management Entity (MME) 162, a Serving Gateway (SGW) 164, and a Packet Data Network (PDN) Gateway (PGW) 166. While each of the foregoing elements is depicted as part of the CN 106, it will be understood that any of these elements may be owned and / or operated by an entity other than a CN operator.

[0038] The MME 162 can connect to each of the eNode-Bs 160a, 160b, and 160c in RAN 104 via the S1 interface and can act as a control node. For example, the MME 162 can be responsible for authenticating users of WTRUs 102a, 102b, and 102c, bearer activation / deactivation, selecting a specific serving gateway during the initial attachment of WTRUs 102a, 102b, and 102c, etc. The MME 162 can provide control plane functions for handover between RAN 104 and other RANs (not shown) employing other radio technologies such as GSM and / or WCDMA.

[0039] The SGW 164 can connect to each of the eNodeBs 160a, 160b, and 160c in RAN 104 via the S1 interface. The SGW 164 can typically route and forward user data packets to or from WTRUs 102a, 102b, and 102c. The SGW 164 can perform other functions, such as anchoring the user plane during inter-eNode-B handover, triggering paging when DL data is available to WTRUs 102a, 102b, and 102c, and managing and storing the context of WTRUs 102a, 102b, and 102c.

[0040] SGW 164 can be connected to PGW 166, which can provide WTRU 102a, 102b, 102c with access to packet-switched networks (such as Internet 110) to facilitate communication between WTRU 102a, 102b, 102c and IP-enabled devices.

[0041] CN 106 can facilitate communication with other networks. For example, CN 106 can provide WTRUs 102a, 102b, and 102c with access to circuit-switched networks (such as PSTN 108) to facilitate communication between WTRUs 102a, 102b, and 102c and traditional terrestrial line communication equipment. For example, CN 106 may include an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between CN 106 and PSTN 108, or may communicate with such an IP gateway. Additionally, CN 115 can provide WTRUs 102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0042] Despite WTRU in Figures 1A to 1D While described as a wireless terminal, it is envisioned that, in some representative embodiments, such a terminal may (e.g., temporarily or permanently) use a wired communication interface with a communication network.

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

[0044] A WLAN in Infrastructure Basic Services Set (BSS) mode can have an Access Point (AP) for the BSS and one or more Stations (STAs) associated with the AP. The AP can have an interface to a Distribution System (DS) or another type of wired / wireless network that loads and / or loads traffic into and / or out of the BSS. Traffic originating outside the BSS destined for a STA can be delivered to the AP via the AP. Traffic from a STA to a destination outside the BSS can be transmitted to the AP for delivery to the appropriate destination. Traffic between STAs within the BSS can be transmitted via the AP, for example, where a source STA can transmit traffic to the AP, and the AP can deliver the traffic to the destination STA. Traffic between STAs within the BSS can be considered and / or referred to as point-to-point traffic. Point-to-point traffic can be transmitted between a source STA and a destination STA using a Direct Link Setup (DLS) (e.g., transmitted directly between them). In some representative embodiments, the DLS can use 802.11e DLS or 802.11z Tunneled DLS (TDLS). WLANs using the Independent BSS (IBSS) mode can function without access points (APs), and STAs within the IBSS or using the IBSS (e.g., all STAs) can communicate directly with each other. The IBSS communication mode may sometimes be referred to as a "self-organizing" communication mode in this document.

[0045] When operating in 802.11ac infrastructure mode or a similar mode, the AP can transmit beacons on a fixed channel, such as the primary channel. The primary channel can be of fixed width (e.g., a 20 MHz bandwidth) or dynamically set via signaling. The primary channel can be the operating channel of the BSS and can be used by the STA to establish a connection with the AP. In some representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) can be implemented, for example, in an 802.11 system. For CSMA / CA, each STA (e.g., every STA), including the AP, can sense the primary channel. If a particular STA senses / detects that the primary signal is busy and / or determines that the primary signal is busy, that particular STA can back off. In a given BSS, at any given time, only one STA (e.g., only one station) can transmit.

[0046] High-throughput (HT) STAs can communicate using a 40MHz wide channel, for example, by combining a primary 20MHz channel with adjacent or non-adjacent 20MHz channels.

[0047] Very High Throughput (VHT) STAs can support channels with widths of 20MHz, 40MHz, 80MHz, and / or 160MHz. 40MHz and / or 80MHz channels can be formed by combining consecutive 20MHz channels. A 160MHz channel can be formed by combining eight consecutive 20MHz channels, or by combining two non-consecutive 80MHz channels, which can be referred to as an 80+80 configuration. In the 80+80 configuration, data, after channel coding, can be passed through a fragment parser that divides the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time-domain processing can be performed on each stream separately. The streams can be mapped onto the two 80MHz channels, and the data can be transmitted by the transmitting STA. At the receiver of the receiving STA, the above operations of the 80+80 configuration can be reversed, and the combined data can be sent to the Media Access Control (MAC) layer, entities, etc.

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

[0049] 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 the primary channel. The primary channel can have a bandwidth 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 the STAs operating in the BSS that support the minimum bandwidth operating mode. In the 802.11ah example, for STAs that support (e.g., only support) the 1MHz mode (e.g., MTC type devices), the primary channel can be 1MHz wide, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or other channel bandwidth operating modes. Carrier Sense and / or Network Allocation Vector (NAV) settings can depend on the status of the primary channel. If the primary channel is busy, for example, due to STAs (which only support the 1MHz operating mode) transmitting to the AP, the entire available band may be considered busy even if most of the band remains idle and potentially available.

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

[0051] Figure 1D This is a system diagram illustrating RAN 113 and CN 115 according to one embodiment. As described above, RAN 113 may employ NR radio technology to communicate with WTRUs 102a, 102b, and 102c via air interface 116. RAN 113 may also communicate with CN 115.

[0052] RAN 113 may include gNBs 180a, 180b, and 180c, but it will be understood that RAN 113 may include any number of gNBs while remaining consistent with the embodiments. gNBs 180a, 180b, and 180c may each include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 116. In embodiments, gNBs 180a, 180b, and 180c may implement MIMO technology. For example, gNBs 180a and 180b may utilize beamforming to transmit signals to and / or receive signals from WTRUs 102a, 102b, and 102c. Thus, for example, gNB 180a may use multiple antennas to transmit radio signals to and / or receive radio signals from WTRU 102a. In embodiments, gNBs 180a, 180b, and 180c may implement carrier aggregation technology. For example, gNB 180a can transmit multiple component carriers to WTRU 102a (not shown). A subset of these component carriers may be located on unlicensed spectrum, while the remaining component carriers may be located on licensed spectrum. In embodiments, gNBs 180a, 180b, and 180c may implement Coordinated Multipoint (CoMP) technology. For example, WTRU 102a can receive coordinated transmissions from gNBs 180a and 180b (and / or gNB 180c).

[0053] WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using transmissions associated with a scalable digital architecture. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing can vary for different transmissions, different cells, and / or different portions of the radio transmission spectrum. WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using subframes of various lengths or scalable lengths or transmission time intervals (TTIs) (e.g., including different numbers of OFDM symbols and / or absolute times of varying durations).

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

[0055] Each of gNBs 180a, 180b, and 180c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, support for network slicing, dual connectivity, interoperability between NR and E-UTRA, routing of user plane data to User Plane Functions (UPF) 184a and 184b, routing of control plane information to Access and Mobility Management Functions (AMF) 182a and 182b, etc. Figure 1D As shown, gNB 180a, 180b, and 180c can communicate with each other via the Xn interface.

[0056] Figure 1DThe CN 115 shown may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least two Session Management Functions (SMFs) 183a, 183b, and at least one Data Network (DN) 185a, 185b. While each of the foregoing elements is described as part of the CN 115, it will be understood that any of these elements may be owned and / or operated by an entity other than a CN operator.

[0057] AMF 182a and 182b can connect to one or more of the gNBs 180a, 180b, and 180c in RAN 113 via the N2 interface and can act as control nodes. For example, AMF 182a and 182b can be responsible for authenticating users of WTRU 102a, 102b, and 102c, supporting network slicing (e.g., handling different Protocol Data Unit (PDU) sessions with different requirements), selecting specific SMF 183a and 183b, managing registration areas, terminating NAS signaling, mobility management, etc. AMF 182a and 182b can use network slicing, for example, to customize CN support for WTRU 102a, 102b, and 102c based on the service types being used by WTRU 102a, 102b, and 102c. For example, different network slices can be created for different use cases, such as services dependent on Ultra Reliable Low Latency (URLLC) access, services dependent on Enhanced Massive Mobile Broadband (eMBB) access, and services for MTC access. AMF 162 can provide control plane functions for handover between RAN 113 and other RANs (not shown) employing other radio technologies (such as LTE, LTE-A, LTE-APro) and / or non-3GPP access technologies (such as Wi-Fi).

[0058] SMFs 183a and 183b can connect to AMFs 182a and 182b in CN 115 via the N11 interface. SMFs 183a and 183b can also connect to UPFs 184a and 184b in CN 115 via the N4 interface. SMFs 183a and 183b can select and control UPFs 184a and 184b, and configure service routing through UPFs 184a and 184b. 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 downlink data notifications. PDU session types can be IP-based, non-IP-based, or Ethernet-based.

[0059] UPFs 184a and 184b can be connected via the N3 interface to one or more of the gNBs 180a, 180b, and 180c in RAN 113. These gNBs can provide WTRUs 102a, 102b, and 102c with access to packet-switched networks (such as the Internet 110), for example, to facilitate communication between WTRUs 102a, 102b, and 102c and IP-enabled devices. UPFs 184 and 184b can perform other functions such as routing and forwarding packets, enforcing user plane policies, supporting multihomed PDU sessions, handling user plane QoS, buffering downlink packets, and providing mobility anchoring.

[0060] CN 115 can facilitate communication with other networks. For example, CN 115 may include or be able to communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between CN 115 and PSTN 108. Additionally, CN 106 can provide WTRUs 102a, 102b, and 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 an embodiment, WTRUs 102a, 102b, and 102c can be connected to DN185a and 185b via UPF 184a and 184b through the N3 interface to UPF 184a and 184b and the N6 interface between UPF 184a and 184b and local data networks (DNs) 185a and 185b.

[0061] Given Figures 1A to 1D and Figures 1A to 1D The corresponding description can be performed by one or more emulation components / devices (not shown) that perform one or more or all of the functions described herein with respect to any of the following: WTRU 102a to 102d, base stations 114a to 114b, eNode-B 160a to 160c, MME 162, SGW 164, PGW 166, gNB 180a to 180c, AMF 182a to 182b, UPF 184a to 184b, SMF 183a to 183b, DN 185a to 185b, and / or any other components / devices described herein. An emulation device can be one or more devices configured to emulate one or more or all of the functions described herein. For example, an emulation device can be used to test other devices and / or simulate network and / or WTRU functions.

[0062] Simulation devices can be designed to perform one or more tests on other devices in laboratory and / or carrier network environments. For example, one or more simulation devices may perform one or more functions when fully or partially implemented and / or deployed as part of a wired and / or wireless communication network to test other devices within the communication network. One or more simulation devices may perform one or more functions when temporarily implemented / deployed as part of a wired and / or wireless communication network. Simulation devices may be directly coupled to another device for testing purposes and / or may use over-the-air wireless communication to perform tests.

[0063] One or more simulation devices may perform one or more functions when implemented / deployed without being part of a wired and / or wireless communication network. For example, simulation devices may be used to test scenarios in a laboratory and / or undeployed (e.g., testing) wired and / or wireless communication networks to perform tests on one or more components. One or more simulation devices may be test rigs. Simulation devices may transmit and / or receive data using direct RF connections and / or wireless communication via RF circuitry (e.g., which may include one or more antennas).

[0064] Figure 2 This is a reference model for 5G / next-generation networks. RAN here refers to the radio access network based on 5GRAT and / or evolved E-UTRA connected to the next-generation core network.

[0065] Access control and mobility management functions (AMF) include the following functionalities: registration management, connection management, reachability management, mobility management, etc.

[0066] The Session Management Function (SMF) includes the following functionalities: session management (including session establishment, modification, and release), UE / WTRU IP address allocation, selection, and UP function control.

[0067] User plane functions (UPF) include the following functionalities: packet routing and forwarding, packet inspection, service usage reporting, etc.

[0068] Integrated sensing A feasibility study in 3GPP SA1 explores the topic of integrated sensing and focuses on use cases and potential needs for enhancing 5G systems to provide sensing services / operations for different target vertical industries / applications (e.g., autonomous driving / assisted driving, V2X, UAV, 3D mapping, smart cities, smart homes, factories, healthcare, and maritime sectors).

[0069] Wireless sensing technology aims to acquire information about remote objects or environments and their characteristics without physical contact. Sensing data about the object and its surroundings can be used for analysis, enabling the acquisition of meaningful information about the object or environment and its characteristics.

[0070] For integrated sensing, sensing measurement data is collected. Sensing measurement data is the collected data on radio / wireless signals affected by the object of interest or the environment used for sensing purposes (e.g., reflection, refraction, diffraction), and sensing results are derived from processing this sensing measurement data. The area defined for sensing is called the sensing service area location, which is the area where the 5G system can provide sensing services with a specific quality, regardless of the presence of obstacles.

[0071] One use case for integrated sensing involves object detection, such as pedestrian / animal intrusion detection on highways or intruder detection in the surrounding environment of a smart home.

[0072] exist Figure 3 and Figure 4 In the example scenario shown, a base station or WTRU can detect intrusions in the base station's sensing area either on its own or through cooperation between the WTRU and the base station. The sensing measurements are transmitted to the network and further processed into sensing results.

[0073] like Figure 5 As shown in the example, another use case for integrated sensing is transparent sensing, where sensing data is captured and communicated by the WTRU so that the 5GS knows the sensing information.

[0074] In this scenario, the user terminal unit (WTRU) can acquire sensing signals from numerous 3GPP and non-3GPP devices. The 5GC can then process the collected sensing data to determine the various available sensing services.

[0075] Assistance in the selection of WTRU members 3GPP has defined procedures that allow 5GC to provide assistance to AF in selecting member WTRUs.

[0076] The AF provides the NEF, which collects information from other NFs, with an initial list of target WTRUs and one or more filtering criteria to derive a list of candidate WTRUs from the target list and based on the filtering criteria.

[0077] Some examples of filtering criteria include WTRU location, for example, to indicate that a candidate WTRU should be located in a specific location that qualifies it to be selected as a member WTRU.

[0078] Sensing service incentives One motivation for WTRUs to voluntarily participate in sensing operations is economic compensation, which utilizes the WTRU's own resources (such as bandwidth, battery power, and airtime) to assist an initiating entity that is unable to act on its own. The actual amount of compensation can be one factor influencing WTRUs' decisions to use their resources to participate in sensing services, and the amount of compensation can influence user consent decisions.

[0079] While a UDM can contain subscription information for sensing services, the actual compensation depends on many dynamic attributes, such as the time of day, location, available and used resources, and the complexity of the sensing services involved.

[0080] The WTRU that initiates sensing needs to know the rating of the expected sensing service (estimated credits / compensation amount, compensation information) for using network and sensing entity resources before it actually begins a sensing request.

[0081] Currently, considering sensing mode / accuracy and the resources consumed within a specific target sensing service area to meet the requirements of the sensing task, 3GPP systems do not enable rating and compensation calculations for sensing entities. Sensing mode indicates which mode (such as transmitter and / or receiver) the sensor can operate in during sensing operations. Several modes exist, such as single-site UE / BS-based sensing (where the UE or BS acts as both transmitter and receiver), bi-site sensing where different sensing entities act as transmitter and receiver, etc. Rating and compensation calculations need to consider the sensing entities involved, sensing complexity, the sensing mechanism used, the network and sensor resources utilized, and the location and time when the sensing operation is performed. Accuracy can refer to, for example, the size of the identifiable object.

[0082] Therefore, it makes sense to conceive of the following: delivering compensation information to the end user for each engagement in sensing services, for example, to obtain the user's (WTRU's) consent; evaluating compensation using inputs such as resources to be used, complexity, sensing capabilities, sensing accuracy, the WTRU's current context, location, and remaining battery power; and / or delivering dynamic ratings to the WTRU that is expected to initiate sensing services / operations so that it can utilize network sensing resources and services from other entities before deciding to actually begin the service.

[0083] Sensing service network exposure Currently, the 3GPP system does not provide a means for third parties (e.g., AFs) to discover 5G radio sensing services enabled by one or more WTRUs. Different AFs may wish to invoke different types of sensing services based on their desired use cases (e.g., intrusion detection, environmental monitoring, drone tracking). Different WTRUs may be equipped with different sensing capabilities, which may be adapted for some use cases (e.g., with appropriate key performance indicators (KPIs)) but not for others. Therefore, it makes sense to devise a way to enable trusted third parties to discover 5G radio sensing services provided by one or more UEs to support application-specific sensing services.

[0084] Sensor network function To achieve integrated sensing, new network functions are defined here according to embodiments. These new network functions are collectively referred to as "sensing NFs", such as integrated sensing assist NFs (so-called ISANFs) and sensing operation management functions (so-called SOMFs). ISANFs and SOMFs are logical entities and can be co-located; for example, ISANFs can be co-located with NEFs, both ISANFs and SOMFs can be co-located with NEFs, SOMFs can be co-located with NEFs, or SOMFs can be co-located with RANs.

[0085] ISANF—can monitor interactions with Application Functions (AFs) used for sensing services. ISANF can understand service requests from application functions and deduce the corresponding sensing mechanism. Based on the sensing mechanism, it can forward requests to relevant Network Functions (NFs) within the 5GC, which serve the Region of Interest (ROI) or the requesting entity (such as WTRU). When the application function is a third-party application that is not a trusted entity in the 5GS, the application function and the ISANF can communicate through the Network Exposure Function (NEF).

[0086] SOMF is a coordination function for handling sensing operations between the BS and WTRU. Based on information received from the AMF, such as the requested sensing area, the list of BS and WTRU, and the sensing mechanism with QoS requirements, SOMF can derive coordination information for sensing operations. For example, SOMF can determine the roles of the sensing operation, such as the transmitter of the sensing signal, the receiver of the sensing signal, the entity for collecting sensing measurement data, and the entity for calculating the sensing results. For example, SOMF can determine the sensing period, the waveform of the sensing signal, and request resource allocation from the BS or transmitter for transmitting the sensing signal at the sensing period.

[0087] WTRU compensation for providing sensing services Sensing entities that voluntarily participate in sensing services initiated by other entities using their own resources are incentivized through sensing service points and compensation. According to an embodiment, when a sensing entity is discovered and listed as a candidate sensing entity in the sensing service, points and compensation are estimated using the requested sensing capabilities, modes, and resources used. According to an embodiment, the estimated points and compensation are transmitted to the WTRU to determine its willingness to participate in the sensing service. According to an embodiment, if the WTRU agrees, points and compensation are awarded to the WTRU after the sensing service is executed.

[0088] Figure 6 This is an embodiment of a method for providing information and compensation to a WTRU for providing sensing services, and illustrates the interaction between network entities and the parameters / messages used to complete the task.

[0089] Step 601: A candidate sensing entity (WTRU) registers its sensing capabilities for the sensing service, for example, by sending information about resources used to register the WTRU in the sensing service. When a WTRU registers for the sensing service, it can receive credits / compensation for the registered service from the sensing NF or a third-party AF (see further in this document).

[0090] WTRUs can leverage capability registration to provide price indicators. Alternatively, the network can adjust the price range, while the WTRU / sensing entity can determine the price at a given time based on various parameters, such as demand.

[0091] Step 602: Trigger the sensing service at AF / NF / AS.

[0092] Steps 603-604: The AF / NF / AS requests sensing services or available sensing entities from the sensing NF. This request may include discovery criteria / sensing requirements (e.g., location, preferred distance to the sensing target, sensing area, sensing mode, start time and duration, and authorization token). When the sensing NF receives the request, it can verify the authorization token.

[0093] Alternatively, according to an embodiment, the sensing NF can insert the integration / compensation into the discovery criteria. This can be an option if the sensing NF knows all the parameters to estimate the integration / compensation for each candidate WTRU in a set of candidate WTRUs.

[0094] Step 605: The sensing NF detects sensing entities that meet the requested sensing requirements (such as pattern, presence / location, capability, etc.).

[0095] Steps 606-609: The sensing NF sends a sensing request to the PCF to check the policy rules for the WTRU and other sensing entities. The PCF then retrieves the subscriber profile from the UDM / UDR.

[0096] Steps 610-612: The sensing NF transmits the request, along with the retrieved policy and subscriber profile, to the CCS / RF / ABMF to obtain ratings and service compensation for candidate WTRUs whose resources or services may be required for the sensing service requested in step 603. The CCS examines the policy and compensation rules, deriving points / monetary compensation for the requested sensing service for WTRUs with the requested resources / capabilities. Once the compensation / monetary reward is calculated for the sensing service, this information is transmitted to the sensing NF in step 612. Depending on the configuration, if the compensation is pre-configured in the UDR (e.g., a fixed amount of compensation is pre-configured), steps 610-612 can optionally be performed by retrieving the subscription from the UDM / UDR without going through the CCS.

[0097] Step 613: The sensing NF transmits the sensing request along with compensation / monetary reward information to be considered by the WTRU. Additionally, the sensing request and pattern are included for WTRU authorization. This request can be combined with a user consent / authorization request.

[0098] Steps 614-615: If the WTRU accepts compensation / monetary rewards, and the WTRU authorizes the requested sensing mode / requirements and the limited sensing granularity (accuracy) level, then the WTRU responds to the sensing NF using the authorized sensing granularity level and sensing mode. If the WTRU has already received credits at registration or the credit value is higher than the threshold configured in the UDM in step 601, then steps 613-615 may be optional according to the embodiment.

[0099] Step 616: Before executing the sensing service, the selected sensing entities perform the configuration for the sensing process and establish the connections required to execute the sensing activities. After the sensing service is completed, compensation and billing data is collected from all entities involved in providing the sensing service (e.g., WTRU, sensing NF, AF, RAN, AMF / SMF / UPF / PCF / UDM). The compensation and billing data includes resources used, sensing modes, operations performed, start / end times, transmitted / received messages / results, etc. A call detail record (CDR) is generated, and service compensation / credits are calculated for the sensing entities that agreed to use their resources and sensing capabilities to participate in the sensing service.

[0100] Step 617: Issue service points and compensation to participating sensing entities.

[0101] According to an embodiment, the WTRU receives information about the sensing service before sending information for registration, such as the type and quantity of resources of the WTRU to be used for the sensing service, the level of sensing accuracy and sensing mode required for the sensing service, the expected level of complexity (or expected CPU load) of the WTRU performing the sensing service, the QoS level required for the wireless link with the network used to perform the sensing service, and the duration and planned time for performing the sensing service.

[0102] In this way, the WTRU has information to determine whether it has sufficient resources to participate in the sensing service, and the WTRU can decide / determine whether to send a request to participate in the sensing service based on the received information (step 1 above). If the WTRU wants to participate, it wants to make certain resources available for the sensing service (e.g., if the sensing service will require resources from 8 PM to 2 AM on a given date, the WTRU will only register resources from 10 PM to 11 PM; if the sensing service will request 100% availability of a given resource, the WTRU will only register 80%; if the sensing service will request 2 gigabytes of memory resources, the WTRU will only register 1 gigabyte). The types and quantities of resources proposed by the WTRU for participating in the sensing service can then be sent to the network, and the network can use this information to select the sensing entity (WTRU) from the candidate sensing entities to participate in the sensing service.

[0103] WTRU registers for sensing services and receives credits and compensation estimates. According to an embodiment, a candidate sensing entity (e.g., a WTRU herein; the term "sensing entity" as used herein is a generic term that may refer to, for example, WTRU, ISANF, SOMF) may receive an integration and compensation estimate when it registers its sensing capabilities, sensing modes, and sensing resources with the sensing management entity. The integration and compensation parameters may be received in an authorization token. The sensing service authorization token may be presented during the sensing entity discovery process.

[0104] Figure 7 A flowchart is shown illustrating a method for providing WTRU compensation (and related information) to a sensing entity for providing sensing services.

[0105] Step 701: The candidate sensing entity (WTRU) registers its sensing capabilities, modes, time spans and locations in the sensing capability registration to indicate that the candidate sensing entity is a candidate to use its resources and capabilities to participate in the sensing service.

[0106] The sensing NF can interact with CCS / RF / ABMF, PCF and AF to obtain integration / compensation information during WTRU registration, and in step 702, information is provided to the candidate sensing entity (WTRU) in response to the registration of the WTRU's sensing capability.

[0107] Step 702: In response to the registration of the sensing capability of the WTRU, the candidate sensing entity (WTRU) receives an authorization token from the sensing NF and an estimate of the integral / compensation for the candidate sensing entity’s demonstrated ability to provide sensing services.

[0108] Step 703: Trigger the sensing service at AF / NF / AS.

[0109] Step 704: The AF / NF / AS requests sensing services or available candidate sensing entities from the sensing NF. This request may include discovery criteria / sensing requirements (e.g., location, preferred distance to the sensing target, sensing area, sensing mode, start time and duration, and authorization token). When the sensing NF receives such a request, it first authorizes the request by verifying the authorization token.

[0110] Step 705: The sensing NF authorizes the request via the authorization token in the service request.

[0111] Step 706: The sensing NF discovers sensing entities that meet the requested sensing requirements (such as mode, presence / location, capability, etc.). Sensing integrals / compensation are associated with specific sensing requirements and modes. Sensing integrals / compensation may be included in the authorization token. A WTRU may have multiple tokens / integrations associated with different sensing modes. Therefore, the WTRU presents the token along with the integrals / compensation to participate in the intended sensing operation. The candidate sensing entity (i.e., the WTRU) presents the authorization token received in step 2 along with the sensing integrals / compensation. The WTRU is selected based on a match of sensing capabilities and sensing parameters (such as location and time span) along with an estimate of the integrals / compensation for the candidate sensing entity.

[0112] Sensing-based functional programming (NF) selects the WTRU (WTR) to participate in sensing operations based on the match between sensing capabilities and sensing parameters. If all else is the same, sensing-based NF can select candidate WTRUs with lower integrals / compensation to save costs. Therefore, the selection decision can depend on many factors.

[0113] The authorization token contains a list of sensing capabilities and a list of associated integral / compensation estimates. The token's validity period is controlled by its lifecycle. If the token expires, the sensing entity needs to register with the sensing NF again and receive a new token, or refresh the token.

[0114] Step 707: The sensing NF transmits the sensing request along with compensation / monetary reward information to be considered by the WTRU. Additionally, the sensing request and pattern are included for WTRU authorization. This request can be combined with a user consent / authorization request.

[0115] Steps 708-709: If the WTRU accepts the estimated compensation / monetary reward, and the WTRU authorizes the requested sensing mode / requirement and the limited sensing granularity level, then the WTRU responds to the sensing NF using the authorized granularity level and sensing mode.

[0116] Step 710: Before executing the sensing service, the selected sensing entities perform the configuration for the sensing process and establish the connections required to execute the sensing activities. After the sensing service / operation is completed, billing compensation data is collected from all entities that contributed to providing the sensing service (e.g., WTRU, sensing NF, AF, RAN, AMF / SMF / UPF / PCF / UDM). The billing compensation data includes resources used, sensing mode, operations performed, start / end time, messages / results transmitted / received, etc. Service data is generated, and service compensation / points are calculated for the sensing entities that agreed to use their resources and sensing capabilities to participate in the sensing service.

[0117] Step 711: Distribute service points and compensation to participating entities.

[0118] WTRU compensation for 5G / 6G services The WTRU compensation mechanism according to the described embodiment can be applied to other 5G / 6G services: the 5G / 6G CCS system calculates points and compensation based on resources used by the participating WTRUs (such as battery power, processing power, bandwidth, complexity, time, location, etc.); users can subscribe to sensing services / operations by accepting a fixed amount of points / compensation and configure it in the user profile data in the UDM; compensation can also be calculated dynamically based on parameters and policies. If the amount of points / compensation is higher than a threshold, points / compensation will be automatically accepted; if the points / compensation calculated for the sensing service / operation is lower than the threshold, the user will be asked whether to accept; and after the sensing service / operation is completed, the points / compensation for the WTRU will be calculated based on the actual resources used and will be distributed to the WTRU.

[0119] Sensor WTRU selection based on third-party AF / AS sensor selection criteria According to an embodiment, a sensing entity (e.g., a WTRU) may coordinate with an application function (third party) to obtain ratings / points from the application function based on its participation as a sensing WTRU, and these points may be accumulated per sensing service.

[0120] According to another embodiment, the application functionality understands the cooperation / billing schemes shared between different service providers, so that devices belonging to those service providers can be used by each other. According to this embodiment, this is distinguished by the issuance of certain tokens at the application layer and shared when other devices (sensing WTRUs) are discovered. In this way, they (WTRUs that have obtained authorization tokens and credits from the AF) will already know whether they can voluntarily act as sensing WTRUs.

[0121] In this scenario, the 5GS assists in identifying and selecting qualified WTRUs for specific sensing operations required by the AF.

[0122] Possible preconditions may include: a) the WTRU wishes to participate in sensing operations, such as based on application layer logic or pre-configured; b) the WTRU has registered its specific sensing capabilities, such as standard sensing service types / sensing levels. Sensing capabilities may include any of the following sensing-related information, such as: sensing range / power, sensitivity, accuracy, resolution, and sensing category (e.g., object tracking / detection, motion detection, environmental monitoring).

[0123] According to an embodiment, the assistance at the NEF in selecting member WTRUs is enhanced to enable the AF (e.g., an intrusion detection service provider) to select suitable / qualified WTRUs specifically for sensing operations: a) The NEF receives a member WTRU selection auxiliary subscription request from the AF. The request includes sensing filtering criteria such as: the sensing capabilities desired by the WTRU, such as sensing category, sensitivity, resolution, accuracy, minimum / maximum relative distance required to the sensing target (e.g., the location of a physical object), sensing area, and whether the WTRU is in motion or stationary.

[0124] b) The NEF queries different NFs (e.g., AMF, sensing control functions) to determine a list of candidate sensing UEs based on the criteria above. The NEF provides the AF with a list of candidate WTRUs, each WTRU accompanied by sensing capability information and applicable context / environment information (e.g., relative distance to the sensing target).

[0125] c) Using the obtained list of WTRUs, the AF can then trigger sensing operations on the selected WTRUs to receive and process sensing-related information from these WTRUs.

[0126] Figure 8 A sequence diagram illustrating a method for WTRU compensation using a third-party AF / AS according to an embodiment is shown.

[0127] Step 801: The sensing entity (WTRU) registers its sensing capabilities, modes, time span for which the WTRU can provide sensing services, locations where the WTRU can use its resources and capabilities to participate in the sensing services, and negotiates with the AF / AS for incentive points / economic compensation for the registered sensing capabilities.

[0128] Step 802: Trigger the sensing service at AF / NF / AS.

[0129] Step 803: The AF subscribes to the member selection assistance functionality by transmitting an Nnef_UEMemberSelectionAssistance_subscribe request that includes a list of target WTRUs, one or more UE member filtering criteria, and an optional time window. The filtering criteria also include sensing capabilities, sensing requirements, sensing mode, preferred distance to the sensing target, sensing area, time window, and stimulus.

[0130] Step 804: NEF verifies the authorization of the AF request, identifies what information needs to be collected, and performs corresponding service operations, such as events, analytics, and / or notifications, based on the WTRU member filtering criteria provided by the AF.

[0131] Step 805: The NEF interacts with different 5GC network functions to gather the necessary information. The set of interactions between NEFs and between 5GC NFs depends on the WTRU member filtering criteria provided by the AF. For example, the NEF may interact with the Network Sensing Control Function and / or the AMF to retrieve a list of registered / active WTRUs based on a list of target WTRUs. User consent will be performed based on user configuration and subscription to confirm that the received service incentives meet the required sensing capabilities and sensing patterns.

[0132] Step 806: Based on information collected from other 5GC NFs, the NEF integrates all information collected from other 5GC NFs to derive a list of candidate WTRUs that meet the WTRU member filtering criteria in the AF request. For example, the NEF checks for each WTRU in the collected data: the WTRU provides the desired sensing capabilities (e.g., appropriate sensing level, sensitivity / power), availability (e.g., based on time span), and location (e.g., appropriate relevant location to the sensing target). The NEF selects WTRUs that meet the AF request to construct the list of candidate WTRUs.

[0133] Step 807: The NEF sends an Nnef_UEMemberSelectionAssistance_Notify request to the AF, which includes a list of candidate WTRUs and possible additional contextual information (e.g., relative distance to the sensed target).

[0134] Step 808: AF / AS determines the final list of WTRUs and uses the requested resources / capabilities to begin the sensing service.

[0135] Step 809: The selected sensing entity performs configuration and establishes a connection for performing sensing services, and then performs the sensing services.

[0136] Figure 9 This is an embodiment of a method 900 for performing sensing services, implemented, for example, by a WTRU. The method may include: a) Send (901) information for registering one or more of the WTRU’s resources (“WTRU’s resources”) in the sensing service; b) In response to the transmission, receive (902) a request to participate in the sensing service, the request including: information related to an estimate of compensation for resources used in the sensing service for the WTRU; c) Send a response to the request (903) based at least on an estimate of the compensation; and d) If the request is accepted, use the resources of the WTRU to perform the (904) sensing service.

[0137] According to an embodiment, a request to participate in the sensing service is received based on selecting a WTRU from among those WTRUs that have sent requests to participate in the sensing service, wherein the selection is based on selection criteria applied to information used for registering WTRU resources in the sensing service.

[0138] According to an embodiment, the information for registering WTRU resources in the sensing service includes one or more of the following: a) One or more sensing capabilities of the WTRU for sensing services; b) One or more sensing modes supported by WTRU for sensing services; c) One or more parameters of the WTRU; and d) One or more resources of the WTRU that can be used for sensing services.

[0139] According to an embodiment, the resources include one or more of the following: a) Available wireless network bandwidth for the WTRU (can be specified separately for UL and DL); and b) WTRU battery charge level.

[0140] According to an embodiment, the parameters of the WTRU include one or more of the following: a) Remaining WTRU battery charge; b) Current network bandwidth (e.g., what WTRU has experienced); and c) Geographical location (e.g., WTRU).

[0141] According to embodiments, the sensing capability includes one or more of the following: a) Sensing range (e.g., 20cm, 50cm, 1m, 10m); b) Sensing power (e.g., measured in Watt or Watt / m2); c) Sensing accuracy (e.g., 1 micrometer, 1 cm, 1 m); and d) Sensing category.

[0142] According to an embodiment, the sensing category is one or more of the following: a) Object tracking; b) Object detection; c) Motion tracking; d) Motion detection; and e) Environmental monitoring.

[0143] An embodiment of a WTRU is also described and disclosed, the WTRU including at least one processor configured to: a) Send information for registering the WTRU resources in the sensing service; b) In response to the transmission, receive a request to participate in the sensing service, the request including: information related to an estimate of compensation for resources used in the sensing service for the WTRU; c) Send a response to the request based at least on an estimate of the compensation; and d) If the request is accepted, use the resources of the WTRU to perform the sensing service.

[0144] According to an embodiment, a request to participate in the sensing service is received based on selecting a WTRU from among those WTRUs that have sent requests to participate in the sensing service, wherein the selection is based on selection criteria applied to resources used to register the WTRU in the sensing service.

[0145] According to an embodiment, the information for registering WTRU resources in the sensing service includes one or more of the following: a) One or more sensing capabilities of the WTRU for sensing services; b) One or more sensing modes supported by WTRU for sensing services; c) One or more parameters of the WTRU; and d) One or more of the resources available to the WTRU for sensing services.

[0146] According to an embodiment, the resources include one or more of the following: a) Wireless network bandwidth; and b) (e.g., WTRU) Battery charge.

[0147] According to an embodiment, the parameters of the WTRU include one or more of the following: a) Remaining battery charge of the WTRU; b) The current network bandwidth experienced by the WTRU (which can be specified separately according to UL and DL); and c) Geographical location (e.g., WTRU).

[0148] According to embodiments, the sensing capability includes one or more of the following: a) Sensing range; b) Sensing power; c) Sensing accuracy; and d) Sensing category.

[0149] According to an embodiment, the sensing category is one or more of the following: a) Object tracking; b) Object detection; c) Motion tracking; d) Motion detection; and e) Environmental monitoring.

[0150] Although features and elements have been provided above in specific combinations, those skilled in the art will understand that each feature or element may be used alone or in any combination with other features and elements. This disclosure is not limited in its description of the specific embodiments described herein, which are intended as illustrative of various aspects. Many modifications and variations are possible without departing from its spirit and scope, as will be apparent to those skilled in the art. No element, action, or instruction used in the description of this application should be construed as critical or essential to the invention unless expressly provided so. In addition to those listed herein, functionally equivalent methods and apparatus within the scope of this disclosure will be apparent to those skilled in the art based on the foregoing description. Such modifications and variations are intended to fall within the scope of the appended claims. This disclosure is limited only by the terms of the appended claims and the full scope of equivalents conferred by such claims. It should be understood that this disclosure is not limited to the specific methods or systems described herein.

[0151] For simplicity, the foregoing embodiments have been discussed in terms of terminology and structure relating to communication-capable devices (i.e., radio wave transmitters and receivers). However, the embodiments discussed are not limited to these systems, but can be applied to other systems that use other forms of electromagnetic waves or non-electromagnetic waves (such as sound waves).

[0152] It will also be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used herein, the term "video" or the term "image" may mean any of a snapshot, a single image, and / or multiple images displayed on a time basis. As another example, when referred to herein, the term "user equipment" and its abbreviation "UE," the term "remote," and / or the term "head-mounted display" or its abbreviation "HMD" may mean or include: (i) a wireless transmit and / or receive unit (WTRU); (ii) any of many embodiments of a WTRU; (iii) a device, particularly configured with some or all of the structural and functional aspects of a WTRU, having wireless and / or wired capabilities (e.g., tetherable); (iv) a device configured with fewer than all of the structural and functional aspects of a WTRU having wireless and / or wired capabilities; or (iv) similar devices. References herein Figures 1A to 1D Details of an exemplary WTRU are provided, which may represent any WTRU described herein. As another example, various disclosed embodiments herein... The above text and The following text It is described as utilizing a head-mounted display. Those skilled in the art will recognize that devices other than head-mounted displays can be used, and some or all of the embodiments disclosed herein and in various other disclosures can be modified accordingly without excessive experimentation. Examples of such other devices may include drones or other devices configured to stream information to provide an adaptive, realistic experience.

[0153] Furthermore, the methods described herein can be implemented in computer programs, software, or firmware incorporated into computer-readable media 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 memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM discs and digital multifunction disks (DVDs). The processor associated with the software can be used to implement a radio frequency transceiver for a WTRU, UE, terminal, base station, RNC, or any host computer.

[0154] Variations of the methods, apparatus, and systems provided above are possible without departing from the scope of the invention. Given the wide variety of embodiments that can be applied, it should be understood that the illustrated embodiments are merely examples and should not be construed as limiting the scope of the appended claims. For example, embodiments provided herein include handheld devices that may include or be used with any suitable voltage source (such as a battery) that provides any suitable voltage.

[0155] Furthermore, in the embodiments provided above, a processing platform, computing system, controller, and other devices including a processor are mentioned. These devices may include at least one central processing unit (“CPU”) and memory. According to the practice of those skilled in the art of computer programming, references to actions and symbolic representations of operations or instructions can be performed by various CPUs and memories. Such actions and operations or instructions may be referred to as “execution,” “computer execution,” or “CPU execution.”

[0156] Those skilled in the art will understand that the actions and symbols representing operations or instructions include the CPU's manipulation of electrical signals. An electrical system represents a data bit, which can cause a final conversion or reduction of the electrical signal and is maintained in a memory location in the storage system, thereby reconfiguring or otherwise altering the CPU's operation and other signal processing. The memory location maintaining the data bit is a physical location having specific electrical, magnetic, optical, or organic properties corresponding to or representing the data bit. It should be understood that the embodiments are not limited to the platforms or CPUs described above, and other platforms and CPUs may support the provided methods.

[0157] Data bits can also be maintained on a computer-readable medium, including disks, optical disks, and any other CPU-readable volatile (e.g., random access memory (RAM)) or non-volatile (e.g., read-only memory (ROM)) mass storage system. The computer-readable medium can include cooperative or interconnected computer-readable media that exist only on the processing system or are distributed across multiple interconnected processing systems that may be located locally or remotely on the processing system. It should be understood that the embodiments are not limited to the above-described memories, and other platforms and memories may support the provided methods.

[0158] In the illustrative embodiments, any operations, processes, etc., described herein can be implemented as computer-readable instructions stored on a computer-readable medium. These computer-readable instructions can be executed by a processor of a mobile unit, network element, and / or any other computing device.

[0159] The differences between the hardware and software implementations of various aspects of the system are minor. The use of hardware or software is typically (but not always, as the choice between hardware and software can become important in certain situations) a design choice representing a cost-efficiency trade-off. Various vehicles (e.g., hardware, software, and / or firmware) may exist to implement the processes and / or systems and / or other technologies described herein, and the preferred vehicle may vary depending on the context in which the processes and / or systems and / or other technologies are deployed. For example, if the implementer determines that speed and accuracy are most important, then the implementer may choose the primary hardware and / or firmware vehicle. If flexibility is most important, then the implementer may choose the primary software implementation. Alternatively, the implementer may choose some combination of hardware, software, and / or firmware.

[0160] The foregoing detailed description has illustrated various embodiments of the devices and / or processes using block diagrams, flowcharts, and / or examples. Those skilled in the art will understand that each function and / or operation within such block diagrams, flowcharts, and / or examples can be implemented individually and / or collectively by a wide range of hardware, software, firmware, or virtually any combination thereof, with respect to the inclusion of one or more functions and / or operations in such block diagrams, flowcharts, or examples. In embodiments, several portions of the subject matter described herein can be implemented via application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), and / or other integration formats. However, those skilled in the art will recognize that all or part of some aspects of the embodiments disclosed herein can be equivalently implemented in integrated circuits as one or more computer processes running on one or more computers (e.g., as one or more processes running on one or more computer systems), as one or more processes running on one or more processors (e.g., as one or more processes running on one or more microprocessors), as firmware, or virtually as any combination thereof, and that designing circuit systems and / or writing code for software and / or firmware according to this disclosure will be entirely within the skill of those skilled in the art. Furthermore, those skilled in the art will understand that the mechanisms of the subject matter described herein can be distributed as process products in various forms, and the illustrative examples of the subject matter described herein apply regardless of the specific type of signal-bearing medium used for actual distribution. Examples of signal-bearing media include, but are not limited to, the following: recordable media, such as floppy disks, hard disk drives, CDs, DVDs, digital magnetic tapes, computer memory, etc.; and transmitting media, such as digital and / or analog communication media (e.g., fiber optic cables, waveguides, wired communication links, wireless communication links, etc.).

[0161] Those skilled in the art will recognize that devices and / or processes are typically described in the manner set forth herein, and that engineering practice is subsequently used to integrate such described devices and / or processes into data processing systems. That is, at least a portion of the devices and / or processes described herein can be integrated into a data processing system through a reasonable number of experiments. Those skilled in the art will recognize that a typical data processing system typically includes a system unit housing, a video display device, memory such as volatile and non-volatile memory, a processor such as a microprocessor and a digital signal processor, a computing entity such as an operating system, drivers, a graphical user interface and application processes, one or more interactive devices such as a touchpad or screen, and / or a control system including feedback loops and control motors (e.g., feedback for sensing position and / or speed; control motors for moving and / or adjusting the number and / or quantity of components). A typical data processing system can be implemented using any suitable commercially available components, such as those commonly found in data computing / communication and / or network computing / communication systems.

[0162] The topics described herein sometimes illustrate different components that are included within or connected to different other components. It should be understood that such depicted architectures are merely examples, and many other architectures that achieve the same functionality can actually be implemented. Conceptually, any arrangement of components used to achieve the same functionality is effectively “associated” such that the desired functionality can be achieved. Therefore, any two components combined herein to achieve a particular functionality can be considered “associated” with each other such that the desired functionality is achieved regardless of the architecture or intermediate components. Similarly, any two such associated components can also be considered “operably connected” or “operably linked” to each other to achieve the desired functionality, and any two components that can be suchly associated can also be considered “operably linked” to each other to achieve the desired functionality. Specific examples of operablely linked components include (but are not limited to) physically matable and / or physically interactive components, and / or wirelessly interactive and / or logically interactive components.

[0163] Regarding the use of virtually any plural and / or singular terms in this document, those skilled in the art can convert plural to singular and / or singular to plural as appropriate to the context and / or application. For clarity, various singular / plural permutations may be explicitly described herein.

[0164] Those skilled in the art will understand that, generally, the terms used herein and especially in the appended claims (e.g., the body of the appended claims) are intended to be largely "open-ended" terms (e.g., the term "comprising" should be interpreted as "including but not limited to," the term "having" should be interpreted as "having at least," the term "including" should be interpreted as "including but not limited to," etc.). Those skilled in the art will further understand that if an intention is to express a specific number of the introduced claims, then this intention will be explicitly stated in the claims, and without such a statement, this intention does not exist. For example, the term "single" or similar language may be used where only one item is intended. To aid understanding, the appended claims and / or the description herein may include the use of the introductory phrases "at least one" and "one or more" to introduce multiple claims. However, the use of such phrases should not be construed as implying that a claim recitation introduced by the indefinite article "a" will include any particular claim recitation limited to an embodiment comprising only one such recitation, even if the same claim includes the introductory phrase "one or more" or "at least one" and indefinite articles such as "a" (e.g., "a" should be interpreted as meaning "at least one" or "one or more"). The same applies to the use of definite articles used to introduce a claim recitation. Furthermore, even if a specific number of introduced claim recitations are explicitly stated, those skilled in the art will recognize that this statement should be interpreted as meaning at least the number recitations (e.g., in the absence of other modifiers, simply stating "two recitations" means at least two recitations or two or more recitations). Moreover, in cases where conventions such as "at least one of A, B, and C" are used, generally, this structure is intended to represent conventions that those skilled in the art will understand (e.g., "a system having at least one of A, B, and C" will include, but is not limited to, systems having only A, only B, only C, both A and B, both A and C, both B and C, and / or both A, B, and C). In cases where conventions such as "at least one of A, B, or C" are used, those skilled in the art will generally understand that the meaning of such conventions is expected to be such that (e.g., "a system having at least one of A, B, or C" will include, but is not limited to, systems having only A, only B, only C, both A and B, both A and C, both B and C, and / or both A, B, and C). Those skilled in the art will further understand that any transitional words and / or phrases (whether in the specification, claims, or drawings) that actually give two or more alternatives should be understood to be intended to include the possibility of including one, any, or both of the items. For example, the phrase "A or B" will be understood to include the possibility of including "A" or "B" or "A and B".Furthermore, the term "any" as used herein, followed by a list of multiple items and / or multiple categories, is intended to include "any," "any combination," "any multiple," and / or "any combination of multiple" individually or in combination with other items and / or other categories. Additionally, as used herein, the term "set" is intended to include any number of items, including zero. Furthermore, as used herein, the term "number" is intended to include any number, including zero. And the term "multiple" as used herein is intended to be synonymous with "multiple."

[0165] Furthermore, when features or aspects of this disclosure are described in accordance with the Markush Group, those skilled in the art will recognize that this disclosure is also described in accordance with any individual member or subgroup member of the Markush Group.

[0166] As those skilled in the art will understand, for any and all purposes, such as providing a written description, all scopes disclosed herein also encompass any and all possible subscopes and combinations thereof. Any listed scope can be readily identified as sufficiently descriptive and such that the same scope can be decomposed into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each scope discussed herein can be readily decomposed into a lower third, a middle third, and an upper third, etc. Those skilled in the art will also understand that all language, such as “up to,” “at least,” “greater than,” “less than,” etc., includes the listed numbers and refers to a scope that can subsequently be decomposed into subscopes as described above. Finally, as those skilled in the art will understand, a scope includes each individual member. Thus, for example, a group having 1 to 3 units refers to a group having 1, 2, or 3 units. Similarly, a group having 1 to 5 units refers to a group having 1, 2, 3, 4, or 5 units, and so on.

[0167] Furthermore, unless otherwise stated, the claims should not be construed as being limited to the order or elements provided. Additionally, the use of the term "means for..." in any claim is intended to invoke 35 USC §112, ¶ 6 or the means plus function claim format, and any claim without the term "means for..." is not intended to do so.

Claims

1. A method implemented by a wireless transmit-receive unit (WTRU), the method comprising: Send information for registering the WTRU with one or more resources in the sensing service; In response to the sending, a request to participate in the sensing service is received, the request including: information related to an estimate of compensation for the one or more resources used in the sensing service with the WTRU; A response to the request shall be sent at least based on the estimated compensation; and If the request is accepted, the sensing service is performed using one or more resources of the WTRU.

2. The method of claim 1, wherein the request to participate in the sensing service is received based on selecting the WTRU from among those WTRUs that have sent requests to participate in the sensing service, wherein the selection is based on selection criteria applied to the one or more resources used to register the WTRU in the sensing service.

3. The method of claim 1, wherein the information for registering the one or more resources of the WTRU in the sensing service includes one or more of the following: The WTRU has one or more sensing capabilities for the sensing service; One or more sensing modes supported by the WTRU for the sensing service; One or more parameters of the WTRU; as well as One or more of the resources of the WTRU that can be used for the sensing service.

4. The method of claim 3, wherein one or more of the resources of the WTRU include one or more of the following: Wireless network bandwidth; and WTRU battery charge level.

5. The method of claim 3, wherein the one or more parameters of the WTRU include one or more of the following: Remaining battery power; Current network bandwidth; and Geographical location.

6. The method of claim 3, wherein the one or more sensing capabilities include one or more of the following: Sensing range; Sensing power; Sensing accuracy; and Sensing category.

7. The method of claim 6, wherein the sensing category includes one or more of the following: Object tracking; Object detection; Motion tracking; Motion detection; and Environmental monitoring.

8. A wireless transmit / receive unit (WTRU) comprising at least one processor, said at least one processor being configured to: Send information for registering the WTRU with one or more resources in the sensing service; In response to the sending, a request to participate in the sensing service is received, the request including: information related to an estimate of compensation for the one or more resources used in the sensing service with the WTRU; A response to the request shall be sent at least based on the estimated compensation; and If the request is accepted, the sensing service is performed using one or more resources of the WTRU.

9. The WTRU of claim 8, wherein the request to participate in the sensing service is received based on selecting the WTRU from among those WTRUs that have sent requests to participate in the sensing service, wherein the selection is based on selection criteria applied to the one or more resources used to register the WTRU in the sensing service.

10. The WTRU of claim 8, wherein the information for registering the one or more resources of the WTRU in the sensing service includes one or more of the following: The WTRU has one or more sensing capabilities for the sensing service; One or more sensing modes supported by the WTRU for the sensing service; One or more parameters of the WTRU; as well as One or more of the resources of the WTRU that can be used for the sensing service.

11. The WTRU of claim 10, wherein one or more of the resources of the WTRU include one or more of the following: Wireless network bandwidth; and WTRU battery charge level.

12. The WTRU of claim 10, wherein the one or more parameters of the WTRU include one or more of the following: Remaining battery power; Current network bandwidth; and Geographical location.

13. The WTRU of claim 10, wherein the one or more sensing capabilities include one or more of the following: Sensing range; Sensing power; Sensing accuracy; and Sensing category.

14. The WTRU of claim 13, wherein the sensing category includes one or more of the following: Object tracking; Object detection; Motion tracking; Motion detection; and Environmental monitoring.

Images