Registration and discovery via a network function

Abstract

A wireless transmit / receive unit (WTRU) may send a sensing request message, for example to a network. The sensing request message may include an indication of sensing criteria, for example associated with device to device (D2D) sensing services. The WTRU may receive a sensing response message, for example from the network. The sensing response message may include an indication associated with another WTRU. The WTRU may send a discovery request, for example to the network. The discovery request may include an indication of one or more one D2D sensing capabilities of the other WTRU. The WTRU may receive a proximity service (ProSe) code, for example in response to the discovery request. The ProSe code may be associated with the other WTRU. The ProSe code may include the indication of the at least one D2D sensing capabilities of the other WTRU.

Description

REGISTRATION AND DISCOVERY VIA A NETWORK FUNCTIONCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of United States Provisional Application No. 63 / 578,784 filed on August 25, 2023, the entire contents of which are incorporated herein by reference.BACKGROUND

[0002] A radio access network (RAN) may be based on the 5thgeneration (5G) radio access technology (RAT) and / or Evolved E-universal terrestrial radio access (UTRA) that connects to the NextGen core network. An access control and mobility management function (AMF) may include one or more of registration management, connection management, reachability management, and / or mobility management. A session management function (SMF) may include one or more of session management (e.g., including session establishment, modify and release), wireless transmit / receive unit (WTRU) internet protocol (IP) address allocation, selection, and / or control of user plane (UP) function. A user plane function (UPF) may include one or more of packet routing and forwarding, packet inspection, and / or traffic usage reporting.

[0003] Integrated sensing may be used for and / or utilize enhancement of 5G system to provide sensing services addressing different target verticals / applications (e.g., autonomous / assisted driving, vehicle to everything (V2X), unmanned aerial vehicle (UAV), 3D map, smart city, smart home, factories, healthcare, and / or maritime sector).SUMMARY

[0004] A wireless transmit / receive unit (WTRU) may send a registration message, for example to a network function (NF). The registration message may include one or more WTRU sensing capabilities. The WTRU may receive a response message, for example from the NF. The response message may include an indication of authorization, for example for one or more sensing and provisioning parameters. The WTRU may send a registration complete message. The WTRU may receive configuration information, for example associated with the one or more sensing and provisioning parameters.

[0005] The one or more sensing and provisioning parameters may include one or more of a proximity service (ProSe) parameter and / or a discovery code. The one or more sensing capabilities may include an indication of one or more of a sensing type, a sensing service, and / or a sensing role.

[0006] A WTRU may send a sensing request message, for example to a network. The sensing request message may include an indication of sensing criteria, for example associated with device to device (D2D) sensing services. The WTRU may receive a sensing response message, for example from the network. The sensing response message may include an indication associated with another WTRU.

[0007] The WTRU may send a discovery request, for example to the network. The discovery request may include an indication of one or more one D2D sensing capabilities of the other WTRU. The WTRU may receive a proximity service (ProSe) code, for example in response to the discovery request. The ProSe code may be associated with the other WTRU. The ProSe code may include the indication of the at least one D2D sensing capabilities of the other WTRU. The D2D sensing capability may include a sensing capability associated with one or more of a sensing type, a sensing service, and / or a sensing role.

[0008] The indication of sensing criteria associated with D2D sensing services may include one or more of a data time validity, a delay requirement, a proximity, a location, a location of interest, a sensing data communication preference, a data storage destination, a periodicity, a frequency, or a sampling size associated with D2D sensing services.

[0009] The WTRU may determine to request the D2D sensing services from one or more other WTRUs, for example based on a trigger. The trigger may include one or more of a real-time map, an indication of blockage associated with a sensor, and / or an indication of data associated with a sensor. The sensor may be comprised in the WTRU.

[0010] The WTRU may receive authorization and provisioning information, for example for the D2D sensing services. The sensing response message may include an indication of whether a sensing request is accepted. The sensing response message may include an indication of information associated with a plurality of (e.g., other) WTRUs. The WTRU may select another WTRU from the plurality of (e.g., other) WTRUs. The indication of information associated with the plurality of (e.g., other) WTRUs may include an indication of a sensing service for each of the plurality of (e.g., other) WTRUs. The WTRU may select another WTRU from the plurality of (e.g., other) WTRUs based on the indication of the sensing service for one or more of the plurality of (e.g., other) WTRUs. The plurality of (e.g., other) WTRUs may be included in a list of WTRUs. For example, the WTRU may choose a (e.g., another) WTRU based on an indication of a list of (e.g., other) WTRUs.

[0011] A base station may receive a sensing request message, for example from a WTRU. The sensing request message may include an indication of sensing criteria associated with D2D sensing services. The base station may send a sensing response message, for example to theWTRU. The sensing response message may include an indication associated with another WTRU.

[0012] The base station may receive a discovery request, for example from the WTRU. The discovery request may include an indication of at least one D2D sensing capabilities of the other WTRU. The base station may send a ProSe code associated with the other WTRU, for example in response to the discovery request.BRIEF DESCRIPTION OF THE DRAWINGS

[0013] FIG. 1A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented.

[0014] FIG. 1 B is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A according to an embodiment.

[0015] FIG. 1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1A according to an embodiment.

[0016] FIG. 1 D is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1A according to an embodiment.

[0017] FIG. 2 is a diagram illustrating an example 5G network.

[0018] FIG. 3 is a diagram illustrating an example pedestrian / animal intrusion detection.

[0019] FIG. 4 is a diagram illustrating an example intruder detection in surroundings of a smart home.

[0020] FIG. 5 is a diagram illustrating an example base station and WTRU with object detection.

[0021] FIG. 6 illustrates an example flowchart of policy provisioning and authorization procedures.

[0022] FIGs. 7A and 7B illustrate an example flowchart of procedures for network based WTRU discovery for sensing.

[0023] FIGs. 8A and 8B illustrate an example flowchart of procedures for server based device to device (D2D) sensing.DETAILED DESCRIPTION

[0024] FIG. 1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented. The communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communications systems 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-tail unique-word DFT-Spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.

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

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

[0027] The base station 114a may be part of the RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 114a and / or the base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (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 wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, i.e., one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and / or receive signals in desired spatial directions.

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

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

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

[0031] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access, which may establish the air interface 116 using New Radio (NR).

[0032] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles. Thus, the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., an eNB and a gNB).

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

[0034] The base station 114b in FIG. 1 A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellularbased RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell. As shown in FIG. 1A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not be required to access the Internet 110 via the CN 106 / 115.

[0035] The RAN 104 / 113 may be in communication with the CN 106 / 115, which may be any type of network configured to provide voice, data, applications, and / or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have varying quality of service (QoS) requirements, such as differing throughput requirements,latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like. The CN 106 / 115 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Although not shown in FIG. 1 A, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113, which may be utilizing a NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or Wi-Fi radio technology.

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

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

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

[0039] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. While FIG. 1 B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

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

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

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

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

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

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

[0046] The processor 118 may further be coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functionality and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and / or Augmented Reality (VR / AR) device, an activity tracker, and the like. The peripherals 138 may include one or more sensors, the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.

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

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

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

[0050] Each of the eNode-Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, and the like. As shown in FIG. 1 C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.

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

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

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

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

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

[0056] Although the WTRU is described in FIGS. 1A-1 D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.

[0057] In representative embodiments, the other network 112 may be a WLAN.

[0058] A WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have an access or an interface to a Distribution System (DS) or another type of wired / wireless network that carries traffic in to and / or out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. The traffic between STAs within a BSS may be considered and / or referred to as peer-to-peer traffic. The peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS). In certain representativeembodiments, the DLS may use an 802.11e DLS or an 802.11z tunneled DLS (TDLS). A WL N using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an “ad-hoc” mode of communication.

[0059] When using the 802.11ac infrastructure mode of operation or a similar mode of operations, the AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling. The primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP. In certain representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) may be implemented, for example in in 802.11 systems. For CSMA / CA, the STAs (e.g., every STA), including the AP, may sense the primary channel. If the primary channel is sensed / detected and / or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0060] High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.

[0061] Very High Throughput (VHT) STAs may support 20MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels. The 40 MHz, and / or 80 MHz, channels may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, may be passed through a segment parser that may divide the data into two streams. Inverse Fast Fourier Transform (IFFT) processing, and time domain processing, may be done on each stream separately. The streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA. At the receiver of the receiving STA, the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).

[0062] Sub 1 GHz modes of operation are supported by 802.11 af and 802.11 ah. The channel operating bandwidths, and carriers, are reduced in 802.11 af and 802.11ah relative to those used in 802.11 n, and 802.11ac. 802.11af supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support Meter Type Control / Machine-Type Communications, suchas MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and / or limited bandwidths. The MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).

[0063] WLAN systems, which may support multiple channels, and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include a channel which may be designated as the primary channel. The primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode. In the example of 802.11 ah, the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available.

[0064] In the United States, the available frequency bands, which may be used by 802.11ah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11 ah is 6 MHz to 26 MHz depending on the country code.

[0065] FIG. 1 D is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment. As noted above, the RAN 113 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also be in communication with the CN 115.

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

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

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

[0069] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG. 1 D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.

[0070] The CN 115 shown in FIG. 1 D may include at least one AM F 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While each of the foregoing elements are depicted as part of the CN 115, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0071] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like. Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for machine type communication (MTC) access, and / or the like. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non- 3GPP access technologies such as Wi-Fi.

[0072] The SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 115 via an N11 interface. The SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 115 via an N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating WTRU IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like. A PDU session type may be IP-based, non-IP based, Ethernet-based, and the like.

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

[0074] The CN 115 may facilitate communications with other networks. For example, the CN 115 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and / or wireless networks that are owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to a local Data Network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0075] In view of Figures 1A-1 D, and the corresponding description of Figures 1A-1 D, one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-ab, UPF 184a-b, SMF 183a-b, DN 185a-b, and / or any other device(s) described herein, may be performed by one or more emulation devices (not shown). The emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein. For example, the emulation devices may be used to test other devices and / or to simulate network and / or WTRU functions.

[0076] The emulation devices may be designed to implement one or more tests of other devices in a lab environment and / or in an operator network environment. For example, the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network in order to test other devices within the communication network. The one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The emulation device may be directly coupled to another device for purposes of testing and / or may perform testing using over-the-air wireless communications.

[0077] The one or more emulation devices may perform the one or more, including all, functions while not being implemented / deployed as part of a wired and / or wireless communication network. For example, the emulation devices may be utilized in a testing scenario in a testing laboratory and / or a non-deployed (e.g., testing) wired and / or wireless communication network in order to implement testing of one or more components. The one or more emulation devices may be test equipment. Direct RF coupling and / or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and / or receive data.

[0078] Systems and methods are provided for integrated sensing, communication, and / or proximity services (ProSe). Features and / or functions may include one or more of registration, authentication and authorization, direct discovery, and / or direct integrated discovery and communication. There may be registration and / or discovery via a network function (NF). There may be policy provisioning and authorization via a NF for device to device (D2D) sensing and / or WTRU discovery, for example via a NF for D2D sensing. There may be discovery of WTRU(s) and / or parameter provisioning for D2D sensing via sensing server.

[0079] Registration and / or discovery may be provided via a network function (NF). Policy provisioning and / or authorization may be provided, for example via a NF, for D2D sensing. A WTRU may send a non-access stratum (NAS) message, for example to a NF. The NAS message may include a registration request, for example to an AMF. The NAS message may include D2D sensing capability (e.g., Uu and / or PC5 based sensing capability together and / or independently) of the WTRU.

[0080] For a localized D2D sensing service for example, the NAS message may include the WTRU’s location and / or a location of interest. Additionally, or alternatively, the NAS message may include a requested sensing service type and / or a list of requested sensing data types (e.g., third generation partnership project (3GPP) / non-third generation partnership project (N3GPP) and any other quality of service (QoS) parameters). The WTRU may share one or more supported sensing service types and / or a list of supported sensing data types, for example if acting as a sensing data sharing WTRU. The WTRU may share the one or more supported sensing service types and / or the list of supported sensing data types, for example as part of registration in addition or alternatively to D2D sensing capabilities. For example, the WTRU may send the one or more supported sensing service types (e.g., to the NF) via the NAS message.

[0081] The WTRU may receive a NAS message, for example, from a NF. The NAS message may include a registration response from the AMF. The registration response may indicate authorization for D2D sensing and / or provisioning parameters. The indication of authorization for D2D sensing and / or provisioning parameters may include one or more of proximity based services (ProSe) parameters to discover a WTRU for sensing operation, and / or any discovery codes or other relevant parameters.

[0082] The WTRU may receive a UE (e.g., WTRU) configuration update (UCU) for policy parameters provisioning for D2D sensing. The UCU may include one or more ProSe parameters to discover a WTRU for D2D sensing operation and / or any discovery codes or other relevant parameters. The WTRU may be (e.g., already) provisioned for a sensing service via Uu. One ormore additional or alternative parameters may be sent to the WTRU, for example for D2D sensing over Uu or PC5.

[0083] A network function, for example AMF / policy control function (PCF), may be provided. An AMF may check WTRU subscription data, for example, for authorization of D2D sensing with NF (e.g., UDM / UDR, which refers to sensing capabilities stored in NF). Additionally, or alternatively, the AMF may check with the sensing server for authorization of D2D sensing, for example, by providing one or more sensing capabilities of the WTRU and / or a WTRU ID to the sensing server.

[0084] The AMF may send an AM (access management) policy request, for example to PCF. The AM policy request may include a D2D sensing service indication and / or one or more requested data types. The PCF may (e.g., then) coordinate with UDM / UDR, for example to extract standardized 3GPP / N3GPP sensing capabilities for parameters provisioning. The PCF may derive QoS policy and / or parameters, for example, for D2D sensing data collection. The PCF may send an AM policy response to the AMF. The AM policy response may include authorization for D2D sensing and / or policy parameters.

[0085] A NF (e.g., AMF) may send a NAS message to the WTRU. The NAS message may include a registration response that indicates authorization for D2D sensing. The PCF may send one or more provisioning parameters to the WTRU. The AMF may send a UCU for policy parameters provisioning for D2D sensing. For example, the UCU policy parameters may include one or more of ProSe parameters to discover a WTRU for sensing operation, any discovery codes, and / or other relevant parameters. The WTRU may (e.g., already) be provisioned for a sensing service, for example via Uu. Additional, or alternative parameters may be sent to the WTRU, for example for D2D sensing over PC5.

[0086] A WTRU may perform discovery, for example, via a NF for D2D sensing. The WTRU may send a request to a NF (e.g., a sensing NF), for example, for network assistance to discover available WTRUs in the proximity. The request may include a requested sensing service type, a requested sensing data type, standardized N3GPP data, a QoS, a location of the WTRU, and / or a location of interest associated with the WTRU.

[0087] The WTRU may receive a list of discovered WTRUs, for example from a NF. The WTRU may (e.g., then) select one or more WTRUs, for example, based on the requirements (e.g., such as requested sensing services). The WTRU may request connection establishment with the select WTRU(s) (e.g., over CP or UP via AMF / SMF respectively). The WTRU may send a discovery request, for example, to a direct discovery name management function (DDNMF).The WTRU may send the discovery request after selection (e.g., by the DDNMF) of one or moreWTRUs from the list provided by the sensing NF. The discovery request may include one or more D2D sensing capabilities of the WTRU, for example, to obtain one or more ProSe Codes. The DDNMF may interact with the application server for the authorization of the discovery request.

[0088] Additionally, or alternatively, the WTRU may discover one or more WTRUs in proximity, for example, via PC5 discovery. The WTRU may discover one or more WTRUs in proximity that are offering sensing data sharing. The WTRU may report the NW for requested sensing service and / or a list of discovered WTRU(s) to sensing NF, which, for example, may coordinate with a sensing server to select one or more WTRUs among the discovered WTRU(s) for D2D sensing based on the requested sensing service.

[0089] A NF (e.g., AMF / SMF / Sensing NF) may receive a request from the WTRU, for example, to assist with the discovery of sensing capable WTRUs for the requested sensing service. The request may include one or more of a requested sensing service type, a requested sensing data type, standardized N3GPP data, a QoS, a location of the WTRU, and / or a WTRU’s location of interest.

[0090] A sensing NF may determine the target area, for example, based on the location of the WTRU to discover available WTRUs supporting requested sensing service and / or data types. The available WTRUs may be D2D sensing services capable and / or authorized to exchange sensing data. The sensing NF may coordinate with the network exposure function (NEF) and / or an AMF, for example to discover available WTRUs in a given area. The sensing NF may coordinate with the network exposure function (NEF) and / or an AMF to discover available WTRUs in a given area based on the sensing requirements and / or the capability.

[0091] The NF (e.g., sensing NF) may select one or more WTRUs for D2D sensing among the discovered WTRUs. The NF may select the one or more WTRUs for D2D sending per requested sensing service from a WTRU and / or discovered WTRU's registered sensing capabilities. The NF may (e.g., then) generate a list of WTRUs discovered and / or select one or more of the WTRUs that meets the requirements. The NF may (e.g., then) send those WTRU IDs (e.g., in the list of WTRUs) to the WTRU.

[0092] The DDNMF may receive one or more D2D sensing capabilities from the WTRU. The DDNMF may coordinate with another DDNMF in another PLMN. The DDNMF may request authorization from the sensing NF or application server. The DDNMF may assign one or more ProSe codes to the WTRU, for example, based on the D2D sensing capabilities of the WTRU (e.g., as received in the discovery request).

[0093] A WTRU may send a sensing service request message. The WTRU may receive a sensing service response message. The sensing service response message may include a list of one or more second WTRUs. The WTRU may send a sensing authorization request message. The authorization request message may include a list of one or more selected second WTRUs, for example based on the list of one or more second WTRUs. The WTRU may receive a sensing authorization response message. The WTRU may (e.g., then) establish connection with a selected second WTRU.

[0094] The WTRU may perform a direct discovery and connection establishment procedure with the selected second WTRU. The WTRU may trigger the sensing service request message, for example based on one or more of an application that generates a real-time map of an environment, sensor blockage information, and / or sensing data from a second WTRU. The sensing service request message may include a list of target WTRUs or target service area. Sensor blockage may, for example, occur when an object such as a building or vehicle and / or an environmental condition blocks / interferes with sensor(s). A real-time map may include processing and / or communication delay(s).

[0095] Server-based D2D sensing may be provided. A WTRU may register the WTRU’s D2D sensing capability (e.g., Uu and / or PC5 based sensing capability together or independently), for example, with a sensing server. The WTRU may establish a connection with the sensing server and / or send a sensing service request to the sensing server. The sensing service request may be a general request. The sensing service request may include localized D2D sensing services, for example based on the WTRU’s location and / or location of interest. The sensing service request message may include one or more of a requested sensing service type, a list of requested sensing data types, a WTRU’s location, a WTRU’s location of interest, and / or any other QoS parameters.

[0096] The WTRU may receive a list of WTRUs that are D2D capable and / or are located in the area of interest. The WTRU may receive a list of supported sensing services and / or a list of supported sensing data sharing for each of the located WTRUs. The WTRU may select one or more WTRUs from the list, for example that match the requirements. The WTRU may send an authorization and / or authentication request to the server to access those WTRUs from the list that match the requirements. The authorization and / or authentication request may include one or more of WTRU IDs, requested sensing service, and / or requested sensing data type (e.g., 3GPP / N3GPP data type).

[0097] The sensing server may send a sensing service request, for example to a sensing NF (e.g., integrated sensing assistance network function (ISANF) / SOFM / sensing network function(SNF)). The sensing service request may be used to check the availability of the other WTRU in the proximity (e.g., discovery of WTRUs) of the requesting WTRU and / or in the location of interest. The sensing server may collect from the sensing NF the WTRU IDs of the WTRUs supporting requested sensing service and / or data types. The WTRUs may be D2D sensing services capable and / or authorized to exchange sensing data, for example for the respective area as requested by a first WTRU (e.g., WTRU1).

[0098] Additionally or alternatively, the sensing server may check its database for any available WTRUs supporting requested sensing service and data types, for example that are D2D sensing services capable and / or authorized to exchange sensing data. The sensing server may send a sensing service response message to the first WTRU (e.g., WTRU1). The sensing service response may include one or more of WTRU IDs of available WTRUs, supported sensing services, and / or a list of N3GPP data that can be shared by the WTRUs. A server may send a sensing data collection request, for example to the selected WTRUs. The server may authorize the WTRU to access to the sensing data, for example once approved by the end WTRU.

[0099] The sensing NF may determine a target area, for example based on one or more WTRUs location(s). The sensing NF may determine the target area to discover one or more available WTRUs supporting requested sensing service and data types. The one or more WTRUs may be D2D sensing services capable and / or authorized to exchange sensing data. The sensing NF may coordinate with the NEF to discover one or more available WTRUs, for example in a given area based on the sensing requirements. The sensing NF may coordinate with UDM / UDR for a respective target area, for example, to learn about the serving AMF, which may (e.g., then) assist to discover available devices supporting D2D sensing services (e.g., D2D capabilities) and / or data sharing as requested by the WTRU.

[0100] FIG. 2 is an example diagram of a 5G network 200. The diagram may include a reference model of a potential architecture of 5G and / or NextGen network. RAN 202 may refer to a radio access network, for example based on the 5G RAT and / or Evolved E-UTRA that connects to the NextGen core network. The Access Control and Mobility Management Function (AMF) 204 may include one or more of registration management, connection management, reachability management, mobility management, and / or etc. The Session Management Function (SMF) 206 may include one or more of session management (e.g., including session establishment, modify and release), WTRU IP address allocation, selection, and control of UP function, and / or etc. The User plane function (UPF) 208 may include one or more of packet routing and forwarding, packet inspection, traffic usage reporting, and / or etc.

[0101] There may be integrated sensing. Integrated sensing may be used for and / or utilize enhancement of 5G system to provide sensing services addressing different target verticals / applications (e.g., autonomous / assisted driving, V2X, UAVs, 3D map, smart city, smart home, factories, healthcare, maritime sector). For integrated sensing, there may be a process of collecting sensing measurement data. Sensing measurement data may include data collected from radio / wireless signals impacted (e.g., reflected, refracted, diffracted) by an object and / or environment of interest, for example for sensing purposes. Sensing results may be derived, for example from processing sensing measurement data. There may be an area defined for sensing, (e.g., sensing service area location), which may be an area location with or without an obstacle (e.g., object). The 5G system may provide sensing service(s) with certain quality. N3GPP entities (e.g., other N3GPP entities) may be considered. Sensing measurement data may be transparent to 5GS, for example such that the data may be communicated using a standard protocol to an interface defined by the 5GS.

[0102] FIG. 3 is an example diagram 300 of pedestrian / animal intrusion detection. A core network 302 may receive sensing measurement data, for example from one or more base stations 304. A base station 304 may collect sensing measurement data including data collected from radio / wireless signals impacted (e.g., reflected, refracted, diffracted) by an object 306 and / or environment of interest. Example objects 306 may include a vehicle, an animal, and / or a person. An area 308, for example around a home 311 , and / or a roadway 312 may be defined for sensing, (e.g., sensing service area location). The area 310 and / or the roadway 312 may include one or more objects 306 which may be sensed (e.g., detected). The base station 304 may sense the object 306 in the area 310 or roadway 312, for example by collecting from radio / wireless signals impacted (e.g., reflected, refracted, diffracted) by an object 306. The base station 304 may (e.g., then) send sensing measurement data to the core network 302. The core network 302 may be configured to derive sensing results, for example by processing sensing measurement data. Additionally, or alternatively, the core network 302 may send the measurement data to a detection element 314 (e.g., intrusion detection) for processing.

[0103] FIG. 4 is an example diagram 400 of intruder detection in surroundings of a smart home. A base station 404 and / or WTRU 401 may detect the intrusion, for example in a sensing area. The base station 404 may detect an intrusion into the sensing area, for example in collaboration with one or more WTRUs 401 . For example, the base station 404 and / or the WTRU 401 may collect sensing measurement data including data collected from radio / wireless signals impacted by an object 406 and / or environment of interest. The base station 404 and / or the WTRU 401 may send a sensing signal 403, for example into the sensing area. The radio / wireless signalsimpacted by the object 406 may include a reflected signal 405 (e.g., of the sensing signal 403). The base station 404 and / or the WTRU 401 may send a sensing measurement, for example to a network. The network may process the sensing measurement, for example to detect intrusion.

[0104] FIG. 5 is an example diagram 500 of a base station 502 and WTRU 501 with object detection. Systems and methods may be configured for transparent sensing. In transparent sensing, sensing data may be captured by the WTRU 501 and / or communicated, for example so that 5GS is aware of the sensing information. A user terminal (e.g., WTRU 501) may acquire sense signals from (e.g., many) 3GPP and / or non-3GPP devices. 5GC may determine (e.g., various) available sensing services, for example by processing collated sensing data.

[0105] Sensing capabilities of a WTRU 501 may be insufficient and / or unavailable for performing sensing tasks (e.g., sensing devices are blocked by the environmental conditions), for example. Systems and methods are provided that may use sensing capabilities of other WTRUs 501 over Uu and / or ProSe direct communication, and / or of RAN entities, for example that are capable of performing sensing tasks (e.g., as herein).

[0106] Some systems may not allow a WTRU 501 to use and / or employ sensing capabilities of another WTRU 501 for sensing services. In order to enable the sensing service using sensing capabilities of another WTRU 501 for example, the information of sensing capabilities of other WTRU 501 may be available (e.g., made available) to the entity (e.g., WTRU 501) request sensing service. The sensing data may be collected (e.g., only) from the legitimate entity, for example for security. Sensing data from another entity (e.g., not legitimate) may be used to attack the entity. Systems and methods disclosed herein may address a WTRU 501 is authorized and / or configured to access sensing data from another WTRU 501 for sensing operation and / or how to perform discovery and / or selection of another WTRU 501 , for example by offering sensing data sharing for sensing services in proximity of a WTRU 501 .

[0107] There may be a sensing network function(s) (NF). To enable integrated sensing, there may be (e.g., new) network functions. A sensing NF may include multiple network functions. For example, the network functions (e.g., comprised in the sensing NF) may be an integrated sensing assistance NF (ISANF) and / or a sensing operation management function (SOMF). ISANF and / or SOMF may be logical entities and / or may be collocated with another entity. For example, ISANF may be collocated with NEF, ISANF and SOMF may (e.g., both) be collocated with NEF, SOMF may be collocated with AMF, and / or SOMF may be collocated with RAN).

[0108] ISANF may oversee interaction with application function for a sensing service. ISANF may understand the service request from an application function (AF) and / or may derive a corresponding requested sensing mechanism. Based on the sensing mechanism for example,ISANF may forward the request to the relevant NFs within 5GC. The (e.g., relevant) NFs may serve the region of interest and / or requested entities, for example such as WTRUs. When an AF is a third party application which is not a trusted entity of 5GS for example, the AF and ISANF may communicate through a network exposure function (NEF).

[0109] A SOMF may handle coordinate sensing operation(s), for example among BSs and / or WTRUs. The SOMF may determine (e.g., derive) coordination information for a sensing operation. Based on information received from AMF, for example one or more of a requested sensing region, BSs and WTRUs’ list, and / or requested sensing mechanism with QoS requirement, the SOMF may derive coordination information for sensing operation.

[0110] The SOMF may decide the role of sensing operation. For example the role may be one or more of sender(s) of sensing signal(s), receiver(s) of sensing signal(s), an entity to collect the sensing measurement data, and / or an entity to calculate sensing result. The SOMF may decide one or more of a sensing period, and / or the waveform of sensing signal. The SOMF may send a message, for example to a BS(s) and / or a sender(s) resource assignment, for sending a sensing signal at the sensing period.

[0111] There may be sensing capabilities. Systems and methods may communicate sensing related capability parameters (e.g., in messages) as described herein. Parameters may include information of sensing capabilities of other WTRUs, for example over ProSe direct communication, and / or of RAN entities (e.g., gNB).

[0112] Parameters (e.g., sensing related capability parameters) may include one or more of sensing type (e.g., monostatic sensing and / or bistatic sensing), requested sensing services, supported sensing services, 3GPP sidelink sensing capabilities, 3GPP Uu sensing capabilities, 3GPP RAN sensing capabilities (e.g., gNB), non-3GPP sensing capabilities (e.g., lidar, Wi-Fi), sensor output data type (e.g., raw), type of sensing data processing (e.g., anonymization), data compression capabilities, protocol Information for sensing data and control data (e.g., UDP for sensing data, TCP for control / meta data), network transmission information for sensing data and control data (e.g., 3GPP Uu for Control data, and Wi-Fi for sensing data), other data processing and analytics capabilities (e.g., object detection), sensing node role (e.g., data consumer, data provider, service provider, service consumer), and / or device availability / utilization. Device availability / utilization may include one or more of an indication of how many (e.g., other) sensing tasks are performed by the WTRU, how many (e.g., new) sensing tasks may be accepted by the WTRU, and / or a level of priority the WTRU may decide for (e.g., new) tasks. For example at a given time, there may be only one high priority sensing task.

[0113] There may be sensing / data requirements. Systems and methods herein may include communication of sensing related requirement parameters (e.g., in messages). Parameters (e.g., sensing related requirement parameters) may include one or more of data time validity (e.g., time a portion of data valid for), delay requirements (e.g., minimum delay must be met for transmitting sensing data), proximity (e.g., proximity to a user or an object), location (e.g., location of the WTRU), location of interest (e.g., may not be the location of the WTRU but the location for which the sensing data is required by the consumer WTRU), sensing data communication preferences (e.g., Control plane, User Plane, Sidelink, Uu), data buffer / storage destination (e.g., specifies if data to be sent over to a different location to the requesting WTRU, for example, data may be requested to be sent to an AF), periodicity / frequency (e.g., data reporting frequency), and / or sampling size (e.g., sampling size of the data).

[0114] Sensing data communication preferences may indicate how sensing data and / or control data may be transferred. For example, sensing data communication preferences may indicate that control data may be transferred over sidelink and / or sensing data may be transferred over the Uu reference point.

[0115] A wireless transmit / receive unit (WTRU) may send a registration message, for example to a network function (NF). The registration message may include one or more WTRU sensing capabilities. The WTRU may receive a response message, for example from the NF. The response message may include an indication of authorization, for example for one or more sensing and provisioning parameters. The WTRU may send a registration complete message. The WTRU may receive configuration information, for example associated with the one or more sensing and provisioning parameters.

[0116] The one or more sensing and provisioning parameters may include one or more of a proximity service (ProSe) parameter and / or a discovery code. The one or more sensing capabilities may include an indication of one or more of a sensing type, a sensing service, and / or a sensing role. The sensing type may include one or more of monostatic sensing and / or bistatic sensing, for example. The sensing service may include one or more of radar, camera, proximity, location, and / or temperature service(s), for example. The sensing role may include one or more of transmitter and / or receiver.

[0117] There may be registration and / or discovery, for example via NF. There may be policy provisioning and / or authorization, for example via a NF for D2D Sensing. A D2D sensing capable WTRU may obtain authorization and / or policy parameter provisioning, for example to access sensing data from another WTRU. To obtain authorization for D2D, the WTRU maysend its sensing capabilities to the CN. The CN may (e.g., then) authorize the WTRU for D2D sensing and / or provide policy provisioning.

[0118] FIG. 6 illustrates an example 600 flowchart of policy provisioning and authorization procedures. At 622 a WTRU 620 may send a registration message. The registration message may include its D2D sensing capabilities, as described herein for example. At 624 the RAN 602 node may select the corresponding AMF 604 associated with the WTRU 620. At 626 the AMF 604 may send a subscription data request message to unified data management (UDM) and / or unified data repository (UDR) 616. The subscription data request message may indicate that the request is for the authorization of sensing.

[0119] Alternatively, or additionally, the AMF 604 may request the sensing server for the WTRU’s 620 authorization of D2D sensing. The request message may include the WTRU’s 620 sensing capabilities, and / or the WTRU’s 620 ID (e.g., GPSI). At 628 the AMF 604 may send a message / configuration notification to PCF 612. The message may include a sensing service indication and / or requested data types and / or other information described herein. The PCF 612 may coordinate with UDM / UDR 616 to extract standardized 3GPP / N3GPP sensing capabilities, for example for parameters provisioning. The PCF 612 may derive QoS policy and / or parameters for sensing, for example based on the sensing configuration information received.

[0120] At 630 PCF 612 and / or AMF 604 may perform policy generation and / or association procedures. The PCF 612 may send the generated policy information to AMF 604. The generated policy information may include authorization for sensing and / or policy parameters. At 632 the WTRU 620 may receive a response message (e.g., registration accept) from the network. The response message may include authorization for sensing and / or provisioning parameters (e.g., as described herein).

[0121] At 634 the WTRU 620 may send a registration complete message 634, for example to the AMF 604. At 636 the WTRU may receive a UCU for policy parameters provisioning for D2D sensing. The parameters may include one or more of ProSe parameters to discover a WTRU 620 for sensing operation, any discovery codes, and / or other relevant parameters. The WTRU 620 may be (e.g., already) provisioned for a sensing service via Uu. Additional or alternative parameters may be sent to the WTRU 620 (e.g., by another WTRU) for D2D sensing over PC5.

[0122] There may be NF-Based WTRU discovery, for example for sensing. FIGs. 7A and 7B illustrate an example 700 flowchart of a procedure for network based WTRU discovery for sensing. At 732 WTRUs 720, 722 may be authorized and / or provisioned for D2D sensing. AMF / SMF 704, 706 may coordinate with UDM / UDR and / or Sensing NF 724, for example to identify WTRUs (e.g., WTRU 720 and / or WTRU 722) that support sensing capabilities. At 734WTRU 720 may be triggered to request sensing services from one or more WTRUs (e.g., 722). The trigger may include an application that generates a real-time map of user’s environment, additional information related to WTRU 720 sensor blockage, and / or environmental changes (e.g., any change detected by the sensor). The application may include sensing data from other WTRUs (e.g., 722) in proximity.

[0123] At 736 WTRU 720 may send a sensing request message, for example to the sensing NF 724. The sensing request message may indicate / include a device discovery request for D2D sensing. The sensing request message may include a criteria, that for example the discovered devices must meet. Examples of parameters used for such a criteria are presented herein.

[0124] Additionally, or alternatively, WTRU 720, for example via PC5 discovery, may discover any WTRUs (e.g., 722) supporting D2D sensing. A WTRU may report to the NW for the requested sensing service and / or a list of discovered WTRUs. For example a WTRU may send information to a sensing NF 724 and / or via NAS signalling to an AMF 704. The AMF 704 may (e.g. then) coordinate with a sensing NF 724 to select WTRUs among the discovered WTRUs for D2D sensing based on requested sensing service. At 738 the sensing NF 724 may send a sensing capability query message to NEF 728, for example to obtain a list of WTRUs in an area. The area may be an area where WTRU 720 is located and / or any area of interest for WTRU 720’s desired sensing operation. The sensing capability query message may include sensing capability of WTRU 720 and / or sensing requirements (e.g., location information).

[0125] At 740 the NEF 728 may collect WTRU IDs of registered WTRUs in the area, and / or send the list of WTRU IDs and / or their supported sensing services to the sensing NF 724. The NEF 728 may collect the WTRU IDs based on the received sensing capabilities and requirements.

[0126] At 742 the sensing NF may match available sensing capabilities to requested sensing requirements from each WTRU in the list, for example based on the information received from the NEF 728 and / or the information available to the sensing NF 724 of previously known WTRUs (e.g., previously discovered, registered or configured WTRUs). The sensing NF 724 may query the AMF 704, for example for obtaining information of WTRUs supporting D2D sensing available in the request location and / or registered within the same PLMN. At 744, the sensing NF 724 may send a sensing response message, for example with / including the information of discovered WTRUs. The sensing response message may include the IDs of the WTRUs and / or the capabilities of those WTRUs (e.g., as discussed herein). The sensing response message may indicate if available sensing capabilities may satisfy the sensingrequirements. The sensing response message may indicate whether sensing request is accepted, for example where the D2D sensing services are controlled by the network.

[0127] The sensing NF 724 may indicate if the available sensing capabilities may fully and / or partially satisfy the requested sensing requirements. Partially satisfying the requirement may include respective WTRU (e.g., only) supporting some of the requirements (e.g., not all requirements). Additionally, or alternatively, partially satisfying the requirement may include respective WTRU being a D2D sensing capable WTRU.

[0128] The sensing NF 724 may determine if the sensing capabilities of available WTRUs satisfy the requirements received, and / or (e.g., therefore if D2D sensing can be performed). At 746, once WTRU 720 has received one or more WTRU IDs provided by the sensing NF 724 for example, the WTRU 720 may send a discovery request to DDNMF 726. The discovery request may include D2D sensing capabilities of the selected WTRUs and / or WTRU IDs (e.g., to obtain ProSe Codes).

[0129] The WTRU 720 may receive a list of selected WTRUs offering D2D sensing for the desired services. Selection (e.g., of the list) may be made by the sensing NF 724, for example based on the requirements from the WTRU 720. Alternatively, or additionally, the WTRU 720 may receive a detailed list of WTRUs from the sensing NF 724 including, for example the WTRU IDs associated with the full and / or partial support of D2D sensing capabilities. The WTRU 720 may select one or more WTRUs from the list.

[0130] At 748, the DDNMF 726 may interact with the application server for the authorization of the discovery request. The request may include D2D sensing capabilities of the WTRU. The DDNMF 726 may receive D2D sensing capabilities from the WTRU 720. Additionally, or alternatively, the DDNMF 726 may coordinate with another DDNMF in another PLMN (e.g., if the WTRU providing sensing services doesn’t belong to the same PLMN as WTRU 720), and / or may request authorization from the sensing NF 724 and / or the application server 730.

[0131] At 750, the DDNMF 726 may assign ProSe discovery codes and / or discovery filters (e.g., depending on model A or model B discovery type) to the WTRU, for example based on the D2D sensing capabilities of the WTRU as received in the discovery request. The DDNMF 726 may assign the codes and / or filters based on the authorization information, for example received at 748. At 752 WTRU 720 may receive ProSe code(s), for example assigned by the DDNMF 726. The ProSe code(s) may contain an (e.g., extra) indication whether other WTRUs (e.g., WTRU 722) are discoverable. A WTRU (e.g., WTRU 722) may be discoverable if, for example the WTRU has performed the discovery procedure with the DDNMF 726. There may be scenarios when the other WTRUs (e.g., WTRU 722) has not received its discovery codesand / or filters from the DDNMF 726. In such a case for example, the DDNMF 726 may send a trigger message to WTRU 720 to start the PC5 discovery after the other WTRU (e.g., WTRU 722) has received its discovery code and / or discovery filter.

[0132] Before 754 for example, the (e.g., other) WTRUs may have performed discovery procedure with the DDNMF 726 and / or may have received the corresponding ProSe discovery code and / or discovery filter from the DDNMF 726. At 754 WTRU 720 may perform discovery procedures for the list of WTRUs (e.g., received at 746) and / or may make connection establishment with the discovered and / or selected WTRUs (WTRU 722), for example over PC5 using the ProSe codes as received at 752.

[0133] Additionally, or alternatively, the PC5 discovery message may include a requested sensing service type and / or requested sensing data type. A WTRU may discover other WTRUs using the information of supported sensing service type and / or supported sensing data type. A WTRU may send a request to 5GC, for example once the WTRU has discovered other WTRU(s) in proximity. The request may confirm whether the discovered WTRUs’ supported sensing service type and / or supported sensing data type are (e.g., truly) validated or not.

[0134] The WTRU 720 (e.g., after discovery of WTRU 722) may send an (e.g., another) authorization request to the 5GC for the selected WTRU 722, for example with more discrete parameters (e.g., a list of requested sensing service or sensing data). The WTRU 720 may initiate connection establishment, for example once the authorization is successful. This may ensure that the WTRU 722 confirms the data sharing for the required sensing service in a location of interest. For example, WTRU 722 may agree to provide WTRU 720 video capability in the city center, but not at a WTRU 722 home address. Alternatively, or additionally, DDNMF 726 may be collocated with sensing NF server based D2D sensing, for example as in the procedure illustrated in FIGS. 7A and 7B.

[0135] FIGs. 8A and 8B illustrate an example 800 flowchart of procedures for server based D2D sensing. At 834 the WTRUs 820, 822 may register with a sensing server 832, for example by sending a sensing service request message to the sensing server 832. The sensing service request message may include some or all of the information elements (e.g., as herein).

[0136] At 836 WTRU 820 may be triggered to request sensing services from one or more WTRUs. The trigger may include an application that generates a real-time map of user’s environment and / or additional information of WTRU 820 sensor blockage and / or sensing data from other WTRUs in proximity.

[0137] At 838 WTRU 820 may establish a connection with the sensing server 832 and / or send a sensing service request for a sensing service(s). The sensing service request may include some and / or all of the parameters (e.g., described herein).

[0138] The WTRU 820 may perform PC5 based discovery (e.g., after 836), for example using ProSe to discover available WTRUs in the proximity that are D2D sensing capable and / or offering the desired sensing services. WTRU 820 may include a list of the target WTRUs in the request for sensing services.

[0139] The WTRU 820 may utilize network assistance to locate D2D sensing capable WTRUs in an area. The WTRU 820 may include location information, for example such as WTRU 820’s location and / or a target service area, in the request for sensing services.

[0140] At 840 a sensing server 832 may send a sensing capability query, for example to a sensing NF 824. The sensing capability query may include one or more of the input parameters, for example received at 838, to check the availability of WTRUs that match the criteria specified at 838. The sensing server 832 may determine the target area, for example based on WTRU 820’s reported location and / or from the target service area as requested in the sensing capability query message. Depending on the input parameters, sensing NF 824 may have different actions. Some examples are listed herein.

[0141] There may be collection of WTRU IDs from the HPLMN (e.g., at 842, 844, and / or 846). At 842, the sensing NF 824 may send a sensing capability query to UDM and / or UDR 816, for example to learn about the serving AMFs information and / or include the list of the target WTRUs and / or target service area info. The service AMF(s) 804 may assist in discovering available devices that support D2D sensing services and / or data sharing, for example as requested by the WTRU 820. If a list of the target WTRUs is included at 842 for example, (e.g., then) the request may be to locate the serving AMF(s) 804 of the target WTRUs. If the target service area is included at 842 for example, (e.g., then) the request may be to locate one or more (e.g., all) available AMF(s) 804 serving in the target area. A list of AMF(s) 804 may already be configured in the sensing NF 824, for example by the operator. The sensing NF 824 may determine the serving AMF 804, for example based on the location information.

[0142] At 844, the sensing NF 824 may receive a sensing capability response. The sensing capability response may include the information of the serving AMF(s) 804 from UDM / UDR 816. At 846, if the location information is provided (e.g., at 838) and / or the sensing NF 824 has received a list of serving AMFs for the target area (e.g., at 844), (e.g., then) the sensing NF 824 may send a request to the serving AMF(s) 804. The request may include sensing requirementsto collect a list of available WTRUs supporting D2D sensing service. An AMF 804 may respond with WTRU IDs the WTRUs registered to the serving AMF 804.

[0143] WTRU IDs may be collected from a (e.g., another) PLMN (e.g., at 848 and / or 850). At 848 sensing NF 824 may send a sensing capability query message to NEF 828, for example to obtain a list of WTRUs in an area. An NEF 828, for example based on the sensing capability and requirements, may collect WTRU IDs of registered WTRUs in the area and / or send the list to the sensing NF 824. At 850 an NEF 828 may collect WTRU IDs of registered WTRUs in the area, and / or send the list of WTRU IDs to the sensing NF 824. The NEF 828 may collect the WTRU IDs of registered WTRUs in the area based on the available sensing capabilities and requirements.

[0144] At 852, a sensing NF 824 may select WTRUs that may satisfy some or all sensing requirements, for example received from the sensing server 832. The sensing NF 824 may be populated with WTRUs and / or their sensing capabilities. For example, the sensing NF 824 may coordinate with UDM / UDR 816 to validate the subscription of the WTRUs, and / or to identify WTRUs that support D2D sensing capabilities.

[0145] At 854, the sensing server 832 may receive the information of the selected WTRUs. The information may include IDs of the WTRUs and / or the capabilities of the WTRUs (e.g., as herein). At 856, the sensing server 832 may update a local sensing capabilities database, for example with the received information of the WTRUs. The sensing server 832 may alternatively, or additionally, select and / or determine the WTRU(s) that meet the sensing requirements, for example sent by WTRU 820 at 838.

[0146] The sensing server 832 may be aware of the proximity and / or sensing capabilities of the other WTRU. This information (e.g., the proximity and / or sensing capabilities of the other WTRU) may be used by the sensing server 832, for example to select the list of suitable WTRUs. The list of suitable WTRUs may be sent to WTRU 820 (e.g., at 858).

[0147] At 858 WTRU 820 may receive a sensing service response message, for example from a sensing server 832. The sensing service response message may include WTRU IDs of available WTRUs and / or the capabilities of the WTRUs (e.g., as herein). The sensing service response message may indicate if the capabilities of the available WTRUs (e.g., as herein) fully and / or partially satisfy the sensing requirements. For example, the sensing server 832 may pick one or more (e.g., only) the most suitable WTRU(s) and / or provide a ranking to the WTRUs in the list. The ranking may be from most suitable to least suitable WTRUs. WTRU 820 may select the WTRUs from the list, for example based on the ranking.

[0148] At 860 WTRU 820 may select one or more WTRUs from the list, for example that match the requirements. The selection may be based on a parameter (e.g., as herein), and / or any other information available to the WTRU. The other information may include the WTRUs in the list and / or their associated information (e.g., supported sensing services and / or supported sensing data). For example, WTRU 820 may filter out (e.g., not select) WTRUs that WTRU 820 has (e.g., recently) determined to be out of coverage. Additionally, or alternatively, WTRU 820 may filter out (e.g., not select) WTRUs that may have terminated sensing data sharing support temporarily and / or may experience (e.g., higher) delays to communicate with those WTRUs.

[0149] At 862, WTRU 820 may send an authorization request message to the server to access those WTRUs. The authorization request message may include WTRU authorization information for the respective services and / or WTRUs, and / or some or all of the sensing requirements (e.g., as herein). Alternatively, or additionally, the authorization request message may include WTRU authentication information. Authentication information may include WTRU IDs of the selected WTRUs.

[0150] At 864, sensing server 832 may send a sensing data collection request message to the requested WTRU(s) (e.g., WTRU 822). The sensing data collection request message may include data requirements (e.g., as herein). At 866, WTRU 822 may send a data collection response message, for example to a sensing server 832. The data collection response message may include conditions under which the request may be approved. Examples conditions may include one or more of the time duration the WTRU 822 may provide its sensing services, a periodicity that the data will be reported (e.g., may be reduced for reduced bandwidth consumption / QoS or for power saving reasons), a sampling size (e.g., may be reduced for reduced bandwidth consumption or for power saving reasons), any other parameter specified (e.g., at 864) as sensing requirements that WTRU 822 is not able to satisfy (e.g., delay requirements, partial sensing data sharing enabled), and / or sensing type (e.g. 3GPP based sensing or non-3GPP based sensing).

[0151] At 868 WTRU 820 may receive a sensing authorization message. The sensing authorization message may include an indication of whether the sensing request is accepted per each requested WTRU. The sensing authorization message may also include conditions (e.g., received in step 866). Alternatively, or additionally, the sensing server 832 may (e.g., already) have data collection approval for the WTRU(s) selected (e.g., at 860), and (e.g., therefore) the sensing server 832 may skip / ignore 864 and / or 866 for the respective WTRU(s). Alternatively, or additionally, the sensing authorization message may include WTRUauthentication information. Authentication information may include WTRU IDs of the selected WTRUs.

[0152] At 870 WTRU 820 may perform direct discovery and / or connection establishment procedures with the selected WTRUs (e.g., WTRU 822), for example depending on the agreed mode of sensing data communication. Data may (e.g., then) be exchanged over the application layer between WTRU 820 and WTRU 822, for example through the sensing server (e.g., buffered). Data may be (e.g., then) exchanged directly between the WTRU 820 and WTRU 822 over PC5, for example once peer WTRUs use authorization information to establish PC5 connections. Discovery and / or connection establishment over PC5 may follow the procedure(s) specified as herein (e.g., at 848, 850, 852, 854, and / or 856).

[0153] The sensing server 832 may track the WTRUs location, for example based on reported WTRU locations and / or by subscribing to LMF for location updates for the selected WTRU. Peer WTRU(s), using the prose proximity service for example, may keep track of the other (e.g., peer) WTRU(s) location(s). The sensing server 832 may notify the WTRU 820 that WTRU is not in the area with an indication, for example when the WTRU 822 is not in the proximity of the WTRU and / or is no longer in the target service area. Alternatively, or additionally, the sensing server 832 may be collocated with sensing NF 824 based, for example as in the procedure illustrated in FIGS 8A and 8B.

Claims

CLAIMS:

1. A wireless transmit / receive unit (WTRU) comprising a processor, the processor configured to: send a sensing request message to a network, the sensing request message comprising an indication of sensing criteria associated with device-to-device (D2D) sensing services; receive a sensing response message from the network, the sensing response message comprising an indication associated with a second WTRU; send a discovery request to the network, the discovery request comprising an indication of at least one D2D sensing capability of the second WTRU; and receive a proximity service (ProSe) code associated with the second WTRU in response to the discovery request.

2. The WTRU of claim 1, wherein the indication of sensing criteria associated with D2D sensing services comprises at least one of a data time validity, a delay requirement, a proximity, a location, a location of interest, a sensing data communication preference, a data storage destination, a periodicity, a frequency, or a sampling size associated with D2D sensing services.

3. The WTRU of claim 1 , wherein the ProSe code comprises the indication of the at least one D2D sensing capability of the second WTRU.

4. The WTRU of claim 1 , wherein the processor is configured to determine to request the D2D sensing services from one or more second WTRUs based on a trigger.

5. The WTRU of claim 4, further comprising a sensor, wherein the trigger comprises at least one of a real-time map, an indication of blockage associated with the sensor, or an indication of data associated with the sensor.

6. The WTRU of claim 1 , wherein the processor is configured to receive a discovery code for the D2D sensing services.

7. The WTRU of claim 1 , wherein the sensing response message comprises an indication of whether a sensing request is accepted.

8. The WTRU of claim 1 , wherein the sensing response message comprises an indication of a list of WTRUs, and wherein the processor is configured to select the second WTRU from the list of WTRUs.

9. The WTRU of claim 8, wherein the indication of the list of WTRUs comprises an indication of a sensing service for each of the WTRUs of the list of WTRUs, and wherein the processor configured to select the second WTRU from the list of WTRUs comprises the processor being configured to select the second WTRU from the list of WTRUs based on the indication of the sensing service for at least one of the second WTRUs of the list of WTRUs.

10. The WTRU of claim 1 , wherein the at least one D2D sensing capability comprises a sensing capability associated with at least one of a sensing type, a sensing service, or a sensing role.

11. A method performed by wireless transmit / receive unit (WTRU), the method comprising: sending a sensing request message to a network, the sensing request message comprising an indication of sensing criteria associated with device to device (D2D) sensing services; receiving a sensing response message from the network, the sensing response message comprising an indication associated with a second WTRU; sending a discovery request to the network, the discovery request comprising an indication of at least one D2D sensing capability of the second WTRU; and receiving a proximity service (ProSe) code associated with the second WTRU in response to the discovery request.

12. The method of claim 11 , wherein the indication of sensing criteria associated with D2D sensing services comprises at least one of a data time validity, a delay requirement, a proximity, a location, a location of interest, a sensing data communication preference, a data storage destination, a periodicity, a frequency, or a sampling size associated with D2D sensing services.

13. The method of claim 11 , wherein the ProSe code comprises the indication of the at least one D2D sensing capability of the second WTRU.

14. The method of claim 11 , comprising determining to request the D2D sensing services from one or more second WTRUs based on a trigger, wherein the trigger comprises at least one of a real-time map, an indication of blockage associated with a sensor, or an indication of data associated with a sensor.

15. The method of claim 11 , comprising receiving a discovery code for the D2D sensing services.

16. The method of claim 11, wherein the sensing response message comprises an indication of a list of WTRUs, and wherein the method comprises selecting the second WTRU from the list of WTRUs.

17. The method of claim 16, wherein the indication of the list of WTRUs comprises an indication of a sensing service for each of the WTRUs of the list of WTRUs, and wherein selecting the second WTRU from the list of WTRUs comprises selecting the second WTRU from the list of WTRUs based on the indication of the sensing service for at least one of the WTRUs of the list of WTRUs.

18. A base station comprising a processor, the processor configured to: receive a sensing request message from a first wireless transmit / receive unit (WTRU), the sensing request message comprising an indication of sensing criteria associated with device to device (D2D) sensing services; send a sensing response message to the first WTRU, the sensing response message comprising an indication associated with a second WTRU; receive a discovery request from the first WTRU, the discovery request comprising an indication of at least one D2D sensing capability of the second WTRU; and send a proximity service (ProSe) code associated with the second WTRU in response to the discovery request.

19. The base station of claim 18, wherein the ProSe code comprises the indication of the at least one D2D sensing capabilities of the second WTRU.

20. The base station of claim 18, wherein the sensing response message comprises an indication of information associated with a plurality of second WTRUs.

Images