Mechanism for sensing services handling in roaming

Abstract

In some implementations, a method implemented in a WTRU may include transmitting, to a first network device, a request for sensing service information for a visiting public land mobile network (vPLMN), the request including WTRU location information, an indication of sensing capabilities of the WTRU, and an indication of a sensing service requested by the WTRU. In addition, the device may include receiving, from the first network device, wireless sensing network selection assistance information (WSNSAI), the WSNSAI including a prioritized list of one or more vPLMNs, where each of the one or more vPLMNs is associated with a sensing service type. The method may include selecting a first vPLMN from the prioritized list of one or more vPLMNs. Moreover, the method may include initiating registration with a second network device associated with the selected first vPLMN, where the second network device provides the requested sensing service.

Description

MECHANISM FOR SENSING SERVICES HANDLING IN ROAMINGCROSS REFERENCE TO RELATED APPLICATION

[0001] This application claims the benefit of U.S. Provisional Application Serial No. 63 / 520,264 filed August 17, 2023, the contents of which are hereby incorporated by reference herein.BACKGROUND

[0002] Radio networks, including 5G or NextGen networks, provide communications and other features to wireless devices. In some implementations, such other features may include sensing services, or using measurements of radio interference, reflections, or other environmental characteristics to perform measurements of physical entities in proximity to the wireless device. For example, a device may be able to detect pedestrian or animal intrusion on a highway or vehicle-restricted area, or may be able to detect an intruder in the surroundings of a smart home. Sensing services typically require significant knowledge about the local environment, and accordingly, may be difficult to provide when the device is not in a “home” location or when the device is roaming. Thus, the need exists for a method, process, and / or techniques that enable a roaming user or wireless device to experience sensing services in a visited network that are the same or similar to sensing services the user or device experiences in the home network.SUMMARY

[0003] The present disclosure is directed to implementations of methods and devices for handling sensing services while roaming. In one general aspect, a wireless transmit / receive unit (WTRU) may include a transceiver configured to transmit, to a first network device, a request for sensing service information for a visiting public land mobile network (vPLMN) where the request includes WTRU location information, an indication of sensing capabilities of the WTRU, and an indication of a sensing service requested by the WTRU, and configured to receive, from the first network device, wireless sensing network selection assistance information (WSNSAI) where the WSNSAI includes a prioritized list of one or more vPLMNs, each of the one or more vPLMNs associated with a sensing service type The WTRU may also include processing circuitry configured to select a first vPLMN from the prioritized list of one or more vPLMNs, and initiate registration with a second network device associated with the selected first vPLMN, where the second network device provides the requested sensing service. Other embodiments of this aspect include corresponding computer systems, apparatus, and computer programs recorded on one or more computer storage devices, each configured to perform the actions of the methods.

[0004] Implementations may include one or more of the following features. The WTRU where the sensing service is identified by a sensing service identification (SSID) The WTRU where the processing circuitry is configured to select the first vPLMN based on the SSID of the first vPLMN corresponding to a highest priority vPLMN associated with the requested sensing service, and where the highest priority vPLMN is the highest priority vPLMN associated with the requested sensing service not subject to time or location restriction, an invalid subscription, or congestion. The WTRU where the transceiver is further configured to transmit, to the second network device, a request to register with a first sensing service associated with the selected first vPLMN and receive, from the second network device, a response indicating authorization to utilize the first sensing service. The WTRU where the request to register with the first sensing service may include transmitting the request for registration via an uplink non-access-stratum (UL NAS) message, and where receiving the response indicating authorization to utilize the first sensing service may include receiving the indication of the authorization via a downlink non-access-stratum (DL NAS) message. The WTRU where the processing circuitry is configured to select the first vPLMN over a second vPLMN in the prioritized list of one or more vPLMNs having a higher priority than the first vPLMN based on one or more additional attributes included in the WSNSAI, where the one or more attributes include: support for 3GPP sensing only, non-3GPP sensing, privacy protection enabled / disabled, location restriction information, or an unsupported kind of sensing data sent or received The WTRU where the request for sensing service information further includes identification of a second vPLMN when the second vPLMN has rejected a sensing service requested by the WTRU prior to transmitting the request for sensing service information. The WTRU where the requested sensing service associated with the selected first vPLMN is a restricted access via subscription sensing service, and where the transceiver is further configured to: transmit a registration request to the selected first vPLMN via the second network device, subscription information associated with the requested sensing service; and receiving an acknowledgment of successful registration with the selected first vPLMN when subscription to the requested sensing service is granted. The WTRU where the indication of a sensing service requested by the WTRU comprises a bitmap. Implementations of the described techniques may include hardware, a method or process, or a computer tangible medium.BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0007] 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;

[0008] 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;

[0009] FIG. 1D 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;

[0010] FIG. 2 is an illustration of an example sensing service area location, according to some implementations;

[0011] FIG. 3 is a signal flow diagram of an implementation of a process with broadcast-based handling of sensing services in roaming scenarios;

[0012] FIG. 4 is a signal flow diagram of an implementation of a process with notification of sensing service subscription availability;

[0013] FIG. 5 is a signal flow diagram of an implementation of a process utilizing wireless sensing network selection assistance information; and

[0014] FIG. 6 is aflowchart of an example processof utilizing wireless sensing network selection assistance information.DETAILED DESCRIPTION

[0015] Table 1 is a non-exhaustive list of acronyms that may be used herein.Table 1

[0016] 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), singlecarrier FDMA (SC-FDMA), zero-tail unique-word discrete Fourier transform Spread OFDM (ZT-UW-DFT-S- OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.

[0017] As shown in FIG. 1A, the communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network (CN) 106, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though itwill be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a station (STA), may be configured to transmit and / or receive wireless signals and may include 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 UE.

[0018] 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, 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 NodeB, an eNode B (eNB), a Home Node B, a Home eNode B, a next generation NodeB, such as a gNode B (gNB), a new radio (NR) NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0019] The base station 114a may be part of the RAN 104, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, and the like. 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.

[0020] 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).

[0021] 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 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 116 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 Uplink (UL) Packet Access (HSUPA).

[0022] 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).

[0023] 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 NR.

[0024] 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).

[0025] 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 (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.

[0026] The base station 114b in FIG 1A 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 cellular-based 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.

[0027] The RAN 104 may be in communication with the CN 106, which may be any type of network configured to provide voice, data, applications, and / or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. 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 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. 1A, it will be appreciated that the RAN 104 and / or the CN 106 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 or a different RAT. For example, in addition to being connected to the RAN 104, which may be utilizing a NR radio technology, the CN 106 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0028] The CN 106 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or 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 or a different RAT.

[0029] 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. 1 A may be configured to communicate with the base station 114a, which may employ a cellularbased radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0030] FIG. 1 B 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.

[0031] 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 moremicroprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), 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.

[0032] 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.

[0033] Although the transmit / receive element 122 is depicted in FIG. 1 B 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.

[0034] 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.

[0035] 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).

[0036] 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.

[0037] 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

[0038] 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 handsfree 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, a humidity sensor and the like.

[0039] 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 DL (e.g., for reception) may be concurrent and / or simultaneous. The full duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via 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 WTRU 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 DL (e g., for reception)).

[0040] 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.

[0041] 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-Bs160a, 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.

[0042] 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.

[0043] 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 (PGW) 166. While 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.

[0044] 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 for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA

[0045] 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.

[0046] 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.

[0047] 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.

[0048] 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.

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

[0050] 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 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 representative embodiments, the DLS may use an 802.11e DLS or an 802.11z tunneled DLS (TDLS). A WLAN 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.

[0051] 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. 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 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.

[0052] 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.

[0053] 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 noncontiguous 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).

[0054] 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.11n, and 802.11ac. 802.11 af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11 ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11 ah may support Meter Type Control / Machine- Type Communications (MTC), such as 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).

[0055] WLAN systems, which may support multiple channels, and channel bandwidths, such as 802 11 n, 802.11ac, 802.11 af, and 802.11 ah, 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, all available frequency bands may be considered busy even though a majority of the available frequency bands remains idle.

[0056] In the United States, the available frequency bands, which may be used by 802.11 ah, 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.

[0057] FIG. 1 D 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 NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0058] The RAN 104 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 104 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 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 transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while theremaining 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).

[0059] 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 a varying number of OFDM symbols and / or lasting varying lengths of absolute time).

[0060] 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.

[0061] 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, DC, 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. 1D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.

[0062] The CN 106 shown in FIG. 1 D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While the 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.

[0063] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 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 protocol data unit (PDU) sessions with different requirements), selecting a particular SMF 183a, 183b,management of the registration area, termination of non-access stratum (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 MTC access, and the like The AMF 182a, 182b may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi.

[0064] The SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 106 via an N11 interface. The SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 106 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 UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing DL data notifications, and the like. A PDU session type may be IP-based, non-IP based, Ethernet-based, and the like.

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

[0066] The CN 106 may facilitate communications with other networks For example, the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that 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 In one embodiment, the WTRUs 102a, 102b, 102c may be connected to a local 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.

[0067] In view of FIGs. 1A-1 D, and the corresponding description of FIGs. 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-b, 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.

[0068] 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 mayperform 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 performing testing using over-the-air wireless communications.

[0069] 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.

[0070] Functional nodes, sometimes referred to as network functions (NF), may be provided by one or more physical devices, or a physical device may provide multiple functional nodes, for example an Access Point (AP) may provide multiple functions to WTRUs, and accordingly, one or more network connections may be virtual or internal within a device. As an example, an Access Control and Mobility Management Function (AMF) includes one or more of the following functionalities: Registration management, Connection management, Reachability management, Mobility Management, etc. A Session Management Function (SMF) may include one or more of the following functionalities: session management (including session establishment, modify and release), UE IP address allocation, selection and control of UP function, etc. A User plane function (UPF) may include one or more of the following functionalities: packet routing & forwarding, packet inspection, traffic usage reporting, etc.

[0071] In some implementations, other features provided by the network may include sensing services, or using measurements of radio interference, reflections, or other environmental characteristics to perform measurements of physical entities in proximity to the wireless device. For example, integrated sensing is an enhancement of 5G systems that provides sensing services addressing different target verticals and applications, e.g. autonomous / assisted driving, V2X, UAVs, 3D map reconstruction, smart city, smart home, factories, healthcare, maritime sector, etc. In some implementations, 5G access points (AP) can provide not only communication capabilities but can also sense the surrounding environment, e g. obstacles or people, in the desired trajectory. The APs may transmit the sensing signals and receive the reflected signals to get sensing information. Specifically, for integrated sensing, sensing measurement data may be collected about radio / wireless signals impacted (e.g. reflected, refracted, diffracted, etc.) by an object or environment of interest for sensing purposes and sensing results may be derived from processing sensing measurement data. The environment may be defined as a service area or sensing service area location and may include obstacles or entities for which the 5G system can provide sensing services with a certain or known quality.

[0072] In some implementations, other N3GPP entities may be utilized. Sensing measurement data may be considered transparent or agnostic to 5GS management services or overhead such that the data may be communicated using a standard protocol to an interface defined by the 5GS. The core network may process and analyse the 3GPP sensing data for outputting the sensing result. Such sensing result can be exposed to a trusted third-party application(s).

[0073] FIG. 2 is an illustration of an example sensing service area location, according to some implementations. Integrated sensing may include object detection, for example an automobile / pedestrian / animal intrusion or intruder detection in surroundings of smart home. Bases stations 202A and 202B may transmit signals and through detection of changes in reflections, absorption, angles of arrival of reflections, etc., a system may identify entities moving within a sensed area, and in some implementations, may determine additional details about the entities such as size, speed, direction, type (e.g. mechanical vs. organic), or any other such information. Bases stations 202a and 202b may transmit signals to perform measurements of physical entities in proximity to a wireless device or smart home. The skilled artisan should appreciate that smart home 204 may be equipped with one or more WTRUs or equivalent. The measurements may be transferred to a network 206 and to a sensing service system, for example intrusion detection 208 for further processing. As illustrated, in FIG. 2, a smart home has detection sensing enabled in home area 204. Signals transmitted by one of both of base stations 202a and 202b are used to perform measurements of a person 210 and / or an automobile 212 according to changes in reflections, absorption, angles of arrival of reflections, etc. of transmitted signals. The sensing may be performed by one or both base stations 202a and 202b by themselves and may also be performed by a collaboration between a WTRU(s) of the smart home and base station 202a / 202b.

[0074] In this scenarios, a base station(s) or AP and / or WTRU may detect the intrusion on the sensing area 204 alone or in collaboration with other base stations, APs, and / or WTRUs. In some implementations, the sensing measurement may be transferred to the network 206 and further processed by sensing service system 208 to derive the sensing result. This may be done to reduce processor or other resource requirements on the individual devices, to allow for large training data sets for neural networks or other machine learning techniques, or other such reasons.

[0075] In one example implementation, integrated sensing may be utilized for sports monitoring, for example monitoring a human when doing exercises via wireless signals instead of cameras or wearable devices. With enhanced privacy preservation, wireless signals that propagate in a wireless system, for example between 5G WTRUs, and between the Base Station / APs and WTRUs, can be further reused and processed to retrieve the target sensing object’s characteristics. In a sports monitoring situation, the target object is frequently a human and the target object’s characteristic are human body gestures (e.g. jumping jacks, pull- ups, running between two positions, sit-ups, push-ups, etc ). By comparing the detected body gesture with the correct or normal body gesture when people are performing a corresponding exercise, the sport monitoringapplication may provide feedback, for example, counting the number or rate of the exercise, calculating calories utilized, etc

[0076] Sensing services typically require significant knowledge about the local environment, and accordingly, may be difficult to provide when the device is not in a “home” location or when the device is roaming. For example, when a user (WTRU) and a device (e.g. network element) are in a different physical environment or coverage area from the user’s home operator (i.e. in a visited environment and camped / registered with the visited PLMN), providing location services may be difficult.

[0077] Accordingly, the technological solutions described herein are directed to systems and methods for providing sensing services while roaming, including enhancement of the 5G system to provide availability of the sensing services while the target WTRU is not in the coverage of the home operator and is served by the visiting operator i.e., in roaming. The solutions described enable a wireless system, for example a 5G system, to provide seamless availability of sensing subscription information while the target WTRU is roaming. In other words, when the WTRU is not in the coverage of the home operator and is served by a visiting operator.

[0078] Techniques described allow a WTRU in a visited PLMN (vPLMN) to receive sensing services, and the technological solutions address how a WTRU is informed of the sensing services that are available in a vPLMN and any access restrictions that may be tied to accessing these services, and how a WTRU selects a VPLMN for seamless availability of sensing services. Provided are description details for implementations of systems and methods to address these and other issues to enable the sensing service availability while the target WTRU is not served by the home operator and is in roaming environment. To simplify the description and for ease of understanding, the description may reference a 5G system. However, it should be understood that this is for ease of description, and the described techniques may be applied to similar wireless systems without limitation.

[0079] In an aspect, a WTRU may use the broadcast information from a gNB to select the appropriate visited PLMN (with open access) as per the desired sensing services. The gNB may transmit a registration request to the selected VPLMN providing desired sensing services as part of the uplink non-access stratum (UL NAS) signaling message. The normal registration flow with the vPLMN may then proceed. In some implementations, if the WTRU is interested in sensing services provided by the gNB or vPLMN which are restricted by the subscription as per the broadcasted access control information, then the WTRU may select the appropriate vPLMN with restricted access via subscription, and trigger registration by providing additional information, e g. requested sensing services, subscription identification (Subscription ID), etc. If a subscription is granted / successfully verified by the VPLMN, then successful registration is responded back by the vPLMN.

[0080] FIG. 3 Illustrates sensing service support in roaming with a broadcast-based implementation of handling sensing services in roaming scenarios. As an overview, WTRU 302 is roaming in a vPLMN 306 and WTRU 302 desires or requests to enable the sensing service or services provided by its home network (hPLMN) WTRU 302 may look for a vPLMN which supports the desired / requested sensing service For example, WTRU 302 may desire or request a sensing service that supports sports monitoring as describedabove. WTRU 302 may listen to broadcast information transmitted by a number of different APs or gNBs. WTRU 302 may build up a list of APs / gNB associated with corresponding vPLMNs and the sensing services supported by the corresponding vPLMNs. WTRU 302 may select a gNB that is associated with a vPLMN that supports the sensing service desired by WTRU 302, for example sports monitoring. The sensing services supported and the related access information may flow from h-SNF 310 to v-gNB 304 through v-SNF 308 and vPLMN 306 via a configuration on sensing service supported.

[0081] NG-RAN node v-gNB 304 may broadcast via a broadcast channel information about the support of sensing services provided by vPLMN 306. This broadcast information about the support of the sensing services provided may comprise a bit map including the supported sensing service(s) along with the list of neighboring APs / gNBs which support the respective sensing service(s). The broadcast information 316 may also include restriction information associated with the respective sensing service(s) i.e. if the services are open to all WTRUs or if they require a subscription This information may be part of the system information blocks (SIBs), and / or can be provided to the WTRU as an on demand SIBs. The information is provided or sent by home sensing network function (h-SNF) 310 to the visited sensing network function (v-SNF) 308, which is further sent to a respective visited base station (v-gNB) 304 via existing communication mechanisms for the wireless network functions, for example 5G network functions While not shown, the storage and transfer of the information may involve other network functions including UDM / UDR / PCF etc. As illustrated in FIG. 3, this information is configuration information 314.

[0082] For purposes of this description, it is assumed that v-gNB 304 is associated with a vPLMN that supports the sensing service desired / requested by WTRU 302, and WTRU 302 selects v-gNB 304 based on broadcast channel information 316 being associated with vPLMN 306 where vPLMN 306 supports the sensing services requested by WTRU 302.

[0083] WTRU 302 may select vPLMN 306 based on broadcast information 316. In an aspect, WTRU 302 may select vPLMN 306 based on broadcast information from v-gNB 304 indicating the desired sensing service. At 318, WTRU 302 selects vPLMN 306 in a case where the sensing service desired or requested is with open access. In this case WTRU 302 triggers registration with vPLMN 306 as part of the uplink non-access-stratum (UL-NAS) signaling message, and a normal registration process with the vPLMN follows.

[0084] In another aspect, WTRU 302 may select vPLMN 306 based on broadcast information 316 received from v-gNB 304 indicating the desired / requested sensing service where the desired / requested sensing service is with subscription restricted 320. In this case, WTRU 302, at 322 triggers registration with the selected vPLMN 306 via uplink non-access-stratum (UL-NAS) signaling message 322. UL-NAS 322 will include information identifying the requested sensing service and subscription identification information. UL-NAS 322 is sent to vPLMN 306 via v-gNB 304. The subscription information is verified at 324. When verification of the subscription information is successful, downlink non-access-stratum (DL-NAS) signaling message 326 is sent from vPLMN 306 to WTRU 302 through v-gNB 304. At 328, WTRU 302 experiences the sensing service in the visited or roaming network that is the same sensing service that WTRU 302 experiences in its home network. Thesubscription verification information may include identification information of the WTRU (SUPI / GPSI), identification of the sensing service (SSID), identification of the home PLMN, and identification of the home sensing function (h-SNF ID). The subscription information may be provided by the WTRU.

[0085] In another aspect, implementations of management and notification of sensing services subscription availability in roaming scenarios are described. As a brief overview, a Sensing Service Provider (SSP) or an external application function (AF) may provide and / or update sensing subscription information with the home sensing network function (hSNF), for example in a 5GS. The hSNF may store the subscription information about a user (WTRU) based on the service level agreements / roaming agreements to co-ordinate and update the subscription information to visited SNF’s via a new service-based interface. The subscription information may contain a list of WTRUs, along with their identifiers (GPSI), subscription information (i.e., lists of sensing services the WTRU has a subscription with, along with any time / location validity restrictions), or other such information. In some implementations, a Nsnf_SensingSubscriptionlnfo (create / update) API may be used for creating or updating sensing subscription information with the sensing network function. The hSNF may coordinate and update the subscription information with the visited SNF’s. The vSNF’s may store this information in their internal databases, and the WTRU in a roaming environment may trigger UL NAS signaling (submitting a Registration / Service request) with the VPLMN and may provide additional information (e.g., requested sensing services (sensing service Identifier), subscription identification (Subscription ID), etc.). Upon reception of the UL NAS message along with the request for sensing services with the additional subscription information identified via subscription ID, the vPLMN / AMF may invoke subscription verification with the vSNF. For example, in some implementations, a Nsnf_SubscriptionVerification (Request / Response) API may be utilized for invoking subscription verification. In a scenario where vSNF does not have the subscription information for the requesting WTRU, it may coordinate with the WTRU’s hSNF to verify subscription details and any time / location restrictions for providing sensing services.

[0086] FIG. 4 is a signal flow diagram of an implementation of a process with notification of sensing service subscription availability. In some implementations, the system may provide management and notification of sensing services subscription availability in roaming scenarios. A 5G system, for example, is enhanced to ensure availability of the sensing services subscription while the user (the target WTRU) is in the roaming environment, not served by its home PLMN or home sensing network function (hSNF).

[0087] In an embodiment, a sensing service provider (SSP), or an external application function (AF) may provide the subscription information to the sensing network function (SNF). The hSNF (home sensing network function) may store the subscription information about the user and based on the service level agreements / roaming agreements it may co-ordinate and update the subscription information to visited SNF’s via the new service-based interface. The WTRU in the visited environment may share its subscription information with the visited PLMN / AMF, which will coordinate with the vSNF or hSNF for subscription verification and accordingly respond back to the WTRU with a success or failure response.

[0088] WTRU 402 is roaming at 414. At 416, the sensing service provider (SSP) or an external application function (AF) SSP / AF 412 may provide / update the 5GS home sensing network function (hSNF) 410 with the sensing subscription information or necessary details which may be used by hSNF 410 to create sensing subscription information. At 418, hSNF 410 may store this information in its database The sensing subscription information may contain list of WTRUs, along with their identifiers (GPSI), subscription data per WTRU (e.g. lists of sensing services the WTRU or user has subscribed to, along with any time / location validity restrictions).

[0089] Sensing subscription information may be communicated via a Nsnf_SensingSubscriptionlnfo (create / update) API call in some implementations. At 420, hSNF 410 may coordinate and update the subscription information with the v-SNF 408. At 422, v-SNF 408 may store this information in its internal database according to service level agreements and MNO’s roaming agreements. The information about the v-SNF which may need to be updated with the subscription information may be provided by hSNF 410 as well. Although only one v-SNF is shown, this is for simplicity and in many implementations subscription information may be shared with multiple v-SNFs.

[0090] WTRU 402 is in a roaming environment (i.e., in an area which is not served by the Home PLMN), and may desire to find and / or select a vPLMN based on a desired / requested sensing service. At 424, WTRU 402 initiates UL NAS signaling (e.g a Registration / Service request). The UL NAS message may include additional information (e.g. an identification of requested sensing services (via a sensing service identifier), subscription identification (Subscription ID), or any other such information. In some implementations, WTRU 402 may select vPLMN / AMF 406 based on a broadcast identification as discussed above in connection with FIG. 3, or a randomly visited PLMN selection, or any other such methods (e.g. based on an operator controlled PLMN selection list (OPLMN) or user controlled PLMN selection list, etc.).

[0091] At 426, on reception of the UL NAS message along with the request for sensing service with additional subscription information identified via subscription ID, vPLMN / AMF 406 may authenticate or verify the subscription information by transmitting a verification request to v-SNF 408. In an implementation where v- SNF408 does not have the subscription information for WTRU 402, it may coordinate with h-SNF 410 to verify the subscription and any time / location restrictions for providing sensing services (e.g. backoff timers, validity times, a list of allowed locations and / or times, etc.).

[0092] For example, if WTRU 402 has a valid subscription for the requested sensing service in the network, v-SNF 408 may coordinate with h-SNF 410 to check / verify a subscription by forwarding the subscription information or identifier, WTRU 402 identifier, or any other such information. If verification fails (e.g. if h-SNF 410 does not respond indicating that the subscription is valid), WTRU 402 may not be allowed or may be excluded from using the requested sensing service with subscription (this may be communicated via DL NAS signaling indicating a rejection). In such a case where subscription is not successful, vPLMN / AMF 406 may send a rejection to WTRU 402 in a DL NAS message, providing the rejection cause, for example time / location restrictions applicable, subscription not valid or congestion and WTRUs backed-off with the back-off timer.

[0093] In a case where verification is successful and / or where v-SVF 408 coordinates with h-SNF 410 to verify the subscription, h-SNF 410 will send a Nsnf_SubscriptionVerification response to v-SNF 408 at 428 and v-SNF 408 sends the Nsnf_SubscriptionVerification response to vPLMN / AMD 406. In the case where v-SVF 408 verifies the subscription, v-SVF 408 sends a Nsnf_SubscriptionVerification response to vPLMN / AMD 406 without the need to coordinate with h-SNF 410.

[0094] In some implementations, WTRU 402 may have multiple subscriptions, and the SSID may be supported by one subscription and not another. In such implementations, WTRU 402 may send a list of subscription identifiers to the network, and each may be independently verified or not by v-SNF 408 and h-SNF 410. In a case where subscription verification is necessary, at 428, v-SNF 408 may send Nsnf_SubscriptionVerification (Request / Response) message to vPLMN / AMF 406.

[0095] At 430, vPLMN / AMF 406 sends a DL NAS message to WTRU 402 via v-gNB 404 indicating a successful registration. The DL NAS message may also indicate a successful subscription verification in the case where the requested sensing service is with subscription. At 432, WTRU 402 has been accepted by the vPLMN and is able to utilize the desired sensing service.

[0096] In another aspect, implementations of handling sensing services in roaming scenarios using wireless sensing network selection assistance information (WSNSAI) are described. In some implementations, a WTRU initiates UL NAS signaling toward the vPLMN and provides additional information that includes WTRU assistance information to be transparently passed on by the vPLMN to the HPLMN / UDM. In some implementations, the WTRU assistance information may include the WTRU’s location, a vPLMN-ID where the sensing service request was rejected, rejected / desired sensing services (bit map of the desired sensing services by the target WTRU), sensing capabilities and other classmark related information (e g. support for N3GPP sensing, limiting sensing to 3GPP sensing data only, authorized sensing data providers only, etc.), or any other such information. In some implementations, this may happen in the home environment in which the WTRU provides this information directly to the HPLMN / UDM via UL NAS signaling prior to roaming. In some implementations, the HPLMN may consider the provided WTRU assistance information, existing service level agreements with the mobile network operators (MNO’s) and sensing service providers (SSP’s) to construct the WSNSAI. The HPLMN may pass on the WSNSAI to the WTRU via a DL NAS message (e.g. DL NAS Transport, SoR etc.). The WSNSAI may include a prioritized list of visited PLMNs per sensing service type, (e.g. a sensing service type identified with Sensing Service ID SSID-1, may have preferred vPLMNs such as vPLMN-1, vPLMN-2 & vPLMN-3), and additionally may contain sensing attributes per respective vPLMNs (e.g. support for 3GPP sensing only, or 3GPP and / or non-3GPP sensing, privacy protection (enabled / disabled), location restriction info, restrictions on what kind of sensing data can be sent or received, etc.). The WTRU may use the provided WSNSAI for the visited PLMN selection. For example, if the WTRU is looking for a particular sensing service (e.g SSID-1), it may use a priority provided by the WSNSAI to select a first vPLMN (e.g. vPLMN-1) if it’s available or else pick the next in the priority list for selection. The WTRU may trigger UL NAS signaling with the selected vPLMN (e.g. vPLMN-1), providing the desired sensing service as part of a new- 72 -information element (e.g with requested sensing services, including SSID-1). The selected vPLMN (e.g. vPLMN-1) may respond back with positive DL NAS message, including the desired / request sensing service (e g. SSID-1) as part of the new information element (e.g Allowed Sensing Services including SSID-1). The target WTRU may therefore successfully registered for the desired sensing service.

[0097] In some implementations, sensing services in roaming scenarios may be handled or managed using wireless sensing network selection assistance information (WSNSAI). In such embodiments, a 5G system, for example, is enhanced to ensure availability of the sensing services while the user (the target WTRU) is in the roaming environment.

[0098] In example embodiments, the WTRU provides WTRU assistance information, which includes one or more of the WTRU’s location, VPLMN-ID, rejected / desired sensing services, sensing capabilities, or other such information to the hPLMN / UDM via UL NAS signaling. This information may be provided directly to the hPLMN or via a vPLMN. The hPLMN / UDM may take into consideration the provided WTRU assistance information, along with the service level agreements with the mobile network operators (MNO’s) and sensing service providers (SSP’s) to create wireless sensing network selection assistance information (WSNSAI) and provide it to the WTRU. The WSNSAI will assist the WTRU in the visited location or location where the hPLMN does not have the coverage to select the appropriate vPLMN which can provide the desired sensing services.

[0099] FIG. 5 is a signal flow diagram of an implementation of a process for utilizing wireless sensing network selection assistance information. WTRU 502 may be in a roaming environment 510 (i.e., in an area which is not served by the Home PLMN). At 512, in various embodiments, either the WTRU has been rejected for the requested sensing service by the visited PL N, the requested sensing service is not available according to sensing restrictions (e.g. time or place restrictions), or the WTRU does not have configured wireless sensing network selection assistance information (WSNSAI). The WSNSAI may either be pre-configured in the WTRU via the mobile operator or the sensing service provider via a control or user plane connection, or may be provided by the HPLMN / UDM during the registration procedure in the home / visited location.

[0100] At 514, while in the visited location, WTRU 502 may initiate UL NAS signaling (e.g. Registration or other mobility management procedures, UL NAS transport, service requests, etc.) toward vPLMN-1 / AMF 504 and may provide additional information via a transparent or agnostic container to be forwarded to the HPLMN / UDM 506. For example, in some implementations, the WTRU assistance information may include one or more of the WTRU’s location, the vPLMN-ID where the sensing service request was rejected / restricted / not allowed (e.g. a bit map of the desired sensing services by the target WTRU), sensing capabilities and other WTRU related information (e g. support for N3GPP sensing, limiting sensing to 3GPP sensing data only, authorized sensing data providers only, etc.). As utilized herein the “transparent or agnostic container” may refer to transmission of the WTRU assistance information via higher layers of the network stack or as a payload in an otherwise standard communication. This may allow for legacy support by intermediary network devices that could not otherwise interpret the WTRU assistance information In some implementations, this exchange may happen in the home environment prior to initiating roaming or leaving the HPLM. WTRU 502 may providethe information directly to HPLMN / UDM 506 via UL NAS signaling. For example, HPLMN 506 may request the WTRU assistance information from WTRU 502 via a DL NAS signaling / paging procedure or WTRU 502 may share the WTRU assistance information with HPLMN / UDM 506 as per the stored configuration in the USIM / ME (i.e. an Elementary File in the USIM) which directs the WTRU to share WTRU assistance information with the HPLMN at power on / initial registration, a set time of day, or any other such preconfigured instance. HPLMN / UDM 506 may utilize the provided WTRU assistance information, along with existing service level agreements with the mobile network operators (MNO’s) and sensing service providers (SSP’s) to construct the WSNSAI at 516. HPLMN / UDM 506 will pass on the WSNSAI to WTRU 502 via the DL NAS signaling (e.g. DL NAS Transport, SoR etc.) at 518 The WSNSAI may comprise one or more of a prioritized list of visited PLMNs per sensing service type (e.g sensing service type identified with Sensing Service ID SSID-1 , would have preferred VPLMNs as vPLMN-1, vPLMN-2 & vPLMN-3) and may contain sensing attributes per respective vPLMNs. These are attributes associated with the PLMN / gNB. For example, if it supports 3GPP sensing only or3GPP and / or non-3GPP sensing, privacy protection (enabled / disabled), location restrictions info, restrictions on what kind of sensing data can be sent or received, etc. During vPLMN selection, a WTRU may have a preference from a user / application where it wants to ensure that only 3GPP sensing data should be used for the sensing service etc

[0101] In some implementations, the consumer of the WTRU assistance information could be a vPLMN rather than hPLMN / UDM / hSNF. The vPLMN may take into consideration provided WTRU assistance information from the WTRU camped on the VPLMN to build the WSNSAI and provide it back to the WTRU. The vPLMN may coordinate with the vSNF (visited Sensing Network Function) to construct the WSNSAI. As discussed above, the WSNSAI may include a list of prioritized networks (e.g. vPLMNs) per wireless sensing service, and may include additional attributes of any type and form At 518, the WSNAI information is sent to WTRU 502.

[0102] At 520, WTRU 502 may use the WSNSAI, provided by the HPLMN or the vPLMN in some implementations, for a visited PLMN selection procedure. For example, if the WTRU is looking for a given sensing service, for example SSID-1 as discussed above, it may use the priority information provided in the WSNSAI and select a corresponding vPLMN. For example vPLMN-1 , if it’s available (e.g. sensing service not subject to time or location restriction, an invalid subscription, or congestion); otherwise it may select the next vPLMN in the priority list. WTRU 502 may consider any additional attributes provided in the WSNSAI to choose the vPLMN, for example if privacy protection is required, WTRU might choose a VPLMN which is lower in priority but supports privacy protection as compared to a VPLMN which is higher in priority but does support privacy protection. In an implementation in which WTRU 502 wants to restrict the sensing data to be only3GPP, it may choose the highest priority vPLMN which supports only 3GPP sensing data. Similarly, WTRU 502 might prefer a vPLMN which does not request certain kind of sensing data (e.g. sensors data which are connected to the WTRU, any non-3GPP sensing data, D2D sensing data, etc.), which may help maintain privacy. Such preferences may be configured by a user or administrator of the system or network, dynamically by an application or operating system of the WTRU, or via any other such means.

[0103] At 522, WTRU 502 may initiate or trigger UL NAS Signaling (e.g. Registration, service request, UL NAS transport) with the selected vPLMN (vPLMN-1 504) providing the desired / requested sensing service, and may include a requested sensing service identifier (SSID-1) as an information element in the communication. In some implementations, WTRU 502 may contact the sensing server (provisioned by the vPLMN / HPLMN) requesting the desired sensing service.

[0104] At 524, the selected vPLMN, vPLMN-1 504, may respond back with positive DL NAS message (registration accept, service accept or DL NAS transport) including the desired / requested sensing service identifier (SSID-1) This may be included in an information element (e g. allowed sensing services) in a communication. Accordingly, the WSNSAI provides guidance on the vPLMN selection and once WTRU 502 has selected vPL N-1 504, the allowed sensing services element provides a list of sensing services which are allowed within the selected vPLMN. In some implementations, WTRU 502 may compare this information element with the allowed sensing service(s) and may take corresponding actions. For example, the WTRU may trigger selection of a different vPLMN, and / or back off some services until location or time restrictions are inapplicable (e.g. outside of not-allowed location area identity ((LAI's), etc.)). The allowed sensing services information element may include additional information (i.e. support for 3GPP sensing only or 3GPP and / or non-3GPP sensing, privacy protection (enabled / disabled), location restrictions info (allowed / not allowed location areas), restrictions on what kind of sensing data can be sent or received, etc.). Once registration is successfully completed, WTRU 502 may utilize the desired sensing service. If registration is unsuccessful, in some implementations, WTRU 502 may select a next-priority vPLMN from the WSNSAI, for example vPLMN- 2, for registration and repeat the process at 522 and 524.

[0105] FIG. 6 is a flowchart of an example process 600. In some implementations, one or more process blocks of FIG.6 may be performed by a WTRU and / or network element / function. As shown in FIG. 6, process 600 may include, at 602, transmitting, to a first network device, a request for sensing service information for a visiting public land mobile network (vPLMN), the request including WTRU location information, an indication of sensing capabilities of the WTRU, and an indication of a sensing service requested by the WTRU. For example, a WTRU may transmit, to a first network device, a request for sensing service information for a visiting public land mobile network (vPLMN), the request including WTRU location information, an indication of sensing capabilities of the WTRU, and an indication of a sensing service requested by the WTRU, as described above. As also shown in FIG.6, process 600 may include, at 604, receiving, from the first network device, wireless sensing network selection assistance information (WSNSAI), the WSNSAI including a prioritized list of one or more vPLMNs, each of the one or more vPLMNs associated with a sensing service type. For example, the WTRU may receive, from the first network device, the WSNSAI including a prioritized list of one or more vPLMNs, each of the one or more vPLMNs associated with a sensing service type, as described above. As further shown in FIG.6, process 600 may include selecting a first vPLMN from the prioritized list of one or more vPLMNs at 606. For example, the WTRU may select a first vPLMN from the prioritized list of one or more vPLMNs, as described above. As also shown in FIG.6, process 600 may include initiating registration with a second network device associated with the selected first vPLMN, where the second network device providesthe requested sensing service at 608 For example, the WTRU may initiate registration with a second network device associated with the selected first vPLMN, where the second network device provides the requested sensing service, as described above.

[0106] Process 600 may include additional implementations, such as any single implementation or any combination of implementations described below and / or in connection with one or more other processes described elsewhere herein. In a first implementation, the sensing service is identified by a sensing service identification (SSID). In a second implementation, alone or in combination with the first implementation, selecting the first vPLMN is based on the SSID of the first vPLMN corresponding to a highest priority vPLMN associated with the requested sensing service, and where the highest priority vPLMN is the highest priority vPLMN associated with the requested sensing service not subject to time or location restriction, an invalid subscription, or congestion.

[0107] In a third implementation, alone or in combination with the first and second implementation, process 600 may include selecting the first vPLMN over a second vPLMN in the prioritized list of one or more vPLMNs having a higher priority than the first vPLMN based on one or more attributes included in the WSNSAI, where the one or more attributes include: support for 3GPP sensing only, non-3GPP sensing, privacy protection enabled / disabled, location restriction information, or an unsupported kind of sensing data sent or received.

[0108] In a fourth implementation, alone or in combination with one or more of the first through third implementations, initiating the registration further may include: transmitting, to the second network device, a request to register with a first sensing service associated with the selected first vPLMN; and receiving, from the second network device, a response indicating authorization to utilize the first sensing service.

[0109] In a fifth implementation, alone or in combination with one or more of the first through fourth implementations, transmitting the request to register with the first sensing service further may include transmitting the request for registration via an uplink non-access-stratum (UL NAS) message, and where receiving the response indicating authorization to utilize the first sensing service further may include receiving the indication of the authorization via a downlink non-access-stratum (DL NAS) message.

[0110] In a sixth implementation, alone or in combination with one or more of the first through fifth implementations, the request for sensing service information further includes identification of a second vPLMN when the second vPLMN has rejected a sensing service requested by the WTRU prior to transmitting the request for sensing service information.

[0111] In a seventh implementation, alone or in combination with one or more of the first through sixth implementations, the requested sensing service associated with the selected first vPLMN is a restricted access via subscription sensing service, and where the initiating registration with the second network device associated with the selected first vPLMN may include: transmitting to the selected first vPLMN via the second network device, subscription information associated with the requested sensing service; and receiving an acknowledgment of a successful registration with the selected first vPLMN when subscription to the requested sensing service is granted. In an eighth implementation, alone or in combination with one or more of the firstthrough seventh implementations, the indication of a sensing service requested by the WTRU may comprise a bitmap

[0112] Although FIG.6 shows example blocks of process 600, in some implementations, process 600 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG.6. Additionally, or alternatively, two or more of the blocks of process 600 may be performed in parallel.

[0113] Although features and elements are described above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magnetooptical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.-7J -

Claims

CLAIMSWhat is Claimed:

1. A method implemented in a wireless transmit / receive unit (WTRU), the method comprising: transmitting, to a first network device, a request for sensing service information for a visiting public land mobile network (vPLMN), the request including WTRU location information, an indication of sensing capabilities of the WTRU, and an indication of a sensing service requested by the WTRU; receiving, from the first network device, wireless sensing network selection assistance information (WSNSAI), the WSNSAI including a prioritized list of one or more vPLMNs, each of the one or more vPLMNs associated with a sensing service type; selecting a first vPLMN from the prioritized list of one or more vPLMNs; and initiating registration with a second network device associated with the selected first vPLMN, wherein the second network device provides the requested sensing service.

2. The method of claim 1 , wherein the sensing service is identified by a sensing service identification (SSID).

3. The method of claim 2, wherein selecting the first vPLMN is based on the SSID of the first vPLMN corresponding to a highest priority vPLMN associated with the requested sensing service, and wherein the highest priority vPLMN is the highest priority vPLMN associated with the requested sensing service not subject to time or location restriction, an invalid subscription, or congestion4. The method of claim 1 , further comprising selecting the first vPLMN over a second vPLMN in the prioritized list of one or more vPLMNs having a higher priority than the first vPLMN based on one or more attributes included in the WSNSAI, wherein the one or more attributes include: support for 3GPP sensing only, non-3GPP sensing, privacy protection enabled / disabled, location restriction information, or an unsupported kind of sensing data sent or received.

5. The method of claim 1 , wherein initiating the registration further comprises: transmitting, to the second network device, a request to register with a first sensing service associated with the selected first vPLMN; and receiving, from the second network device, a response indicating authorization to utilize the first sensing service.

6. The method of claim 5, wherein transmitting the request to register with the first sensing service further comprises transmitting the request for registration via an uplink non-access-stratum (UL NAS) message, and wherein receiving the response indicating authorization to utilize the first sensing service further comprises receiving the indication of the authorization via a downlink non-access-stratum (DL NAS) message.

7. The method of claim 1 , wherein the request for sensing service information further includes identification of a second vPLMN when the second vPLMN has rejected a sensing service requested by the WTRU prior to transmitting the request for sensing service information.

8. The method of claim 1, wherein the requested sensing service associated with the selected first vPLMN is a restricted access via subscription sensing service, and wherein the initiating registration with the second network device associated with the selected first vPLMN comprises: transmitting to the selected first vPLMN via the second network device, subscription information associated with the requested sensing service; and receiving an acknowledgment of a successful registration with the selected first vPLMN when subscription to the requested sensing service is granted.

9. The method of claim 1, wherein the indication of a sensing service requested by the WTRU comprises a bitmap.

10. A wireless transmit / receive unit (WTRU) comprising: a transceiver configured to: transmit, to a first network device, a request for sensing service information for a visiting public land mobile network (vPLMN), the request including WTRU location information, an indication of sensing capabilities of the WTRU, and an indication of a sensing service requested by the WTRU; and receive, from the first network device, wireless sensing network selection assistance information (WSNSAI), the WSNSAI including a prioritized list of one or more vPLMNs, each of the one or more vPLMNs associated with a sensing service type; and processing circuitry configured to: select a first vPLMN from the prioritized list of one or more vPLMNs; and initiate registration with a second network device associated with the selected first vPLMN, wherein the second network device provides the requested sensing service.

11. The WTRU of claim 10, wherein the sensing service is identified by a sensing service identification (SSID).

12. The WTRU of claim 11 , wherein the processing circuitry is configured to select the first vPLMN based on the SSID of the first vPLMN corresponding to a highest priority vPLMN associated with the requested sensing service, and wherein the highest priority vPLMN is the highest priority vPLMN associated with the requested sensing service not subject to time or location restriction, an invalid subscription, or congestion.

13. The WTRU of claim 10, wherein the processing circuitry is configured to select the first vPLMN over a second vPLMN in the prioritized list of one or more vPLMNs having a higher priority than the first vPLMNbased on one or more additional attributes included in the WSNSAI, wherein the one or more attributes include: support for 3GPP sensing only, non-3GPP sensing, privacy protection enabled / disabled, location restriction information, or an unsupported kind of sensing data sent or received.

14. The WTRU of claim 12, wherein the transceiver is further configured to: transmit, to the second network device, a request to register with a first sensing service associated with the selected first vPLMN; and receive, from the second network device, a response indicating authorization to utilize the first sensing service.

15. The WTRU of claim 14, wherein the request to register with the first sensing service comprises transmitting the request for registration via an uplink non-access-stratum (UL NAS) message, and wherein receiving the response indicating authorization to utilize the first sensing service comprises receiving the indication of the authorization via a downlink non-access-stratum (DL NAS) message.

16. The WTRU of claim 10, wherein the request for sensing service information further includes identification of a second vPLMN when the second vPLMN has rejected a sensing service requested by the WTRU prior to transmitting the request for sensing service information.

17. The WTRU of claim 10, wherein the requested sensing service associated with the selected first vPLMN is a restricted access via subscription sensing service, and wherein the transceiver is further configured to: transmit a registration request to the selected first vPLMN via the second network device, subscription information associated with the requested sensing service; and receiving an acknowledgment of successful registration with the selected first vPLMN when subscription to the requested sensing service is granted.

18. The WTRU of claim 10, wherein the indication of a sensing service requested by the WTRU comprises a bitmap.

Images