Core network assisted sensor discovery and control session establishment

Abstract

Systems, methods, and instrumentalities disclosed herein relate to spatial mapping (SM). A first network node can receive, from a WTRU, a SM registration request to register the WTRU as a SM client device. The first network node can also receive, from a second network node, a SM discovery request that can indicate one or more SM selection criteria. The first network node can determine, based on the SM registration request received from the WTRU and the SM discovery request received from the second network node, that the WTRU satisfies the one or more SM selection criteria. The first network node can send, to the second network node, a SM discovery response that can indicate information about the WTRU. The first network node can send, to the WTRU, a notification about a SM operation.

Description

Cross-reference to related applications

[0001] This application claims the benefit of U.S. Provisional Patent Application 63 / 574,430, filed April 4, 2024, the disclosure of which is incorporated herein by reference in its entirety. Background Technology

[0002] Mobile communications using wireless communication continue to evolve. The fifth generation can be called 5G. For example, the previous generation (traditional) mobile communications could be the fourth generation (4G) Long Term Evolution (LTE). Summary of the Invention

[0003] This document discloses systems, methods, and means associated with space sensor registration, discovery, and control session establishment. As described herein, a first network node may receive a Space Mapping (SM) registration request from a Wireless Transmit / Receive Unit (WTRU) to register the WTRU as an SM client device. The first network node may also receive an SM discovery request from a second network node, wherein the SM discovery request may indicate one or more SM selection criteria. The first network node may determine that the WTRU meets the one or more SM selection criteria based on the SM registration request received from the WTRU and the SM discovery request received from the second network node. The first network node may send a space sensor discovery response to the second network node, wherein the space sensor discovery response may include information about the WTRU. The first network node may send a notification to the WTRU regarding SM operation.

[0004] In the example, the SM registration request received from the WTRU may indicate one or more of the following: the type of SM information that the WTRU can provide, the location or position of the WTRU, and the availability of the WTRU as the SM client device. The type of SM information may indicate whether the SM information was acquired using a color camera, a LiDAR camera, or a high-resolution camera.

[0005] In the example, the first network node may register the WTRU as the SM client device in response to receiving the SM registration request. The registration may include authenticating the WTRU and storing information about the WTRU on the first network node.

[0006] In the example, the one or more SM selection criteria received from the second network node may indicate one or more of the following: the type of SM information requested by the second network node, the SM location or position desired by the second network node, and the region of interest of the second network node.

[0007] In these examples, the SM operation instructed to the WTRU may include an SM measurement to be performed by the WTRU or a space sensor associated with the WTRU. In these examples, the notification sent to the WTRU may include measurement configuration information indicating one or more of the following: the quality of the SM measurement, the frequency of the SM measurement, the area of ​​the SM measurement, the target of the SM measurement, and the reporting address of the SM measurement. In these examples, the notification sent to the WTRU may be triggered at least in part by an SM discovery request from the second network node.

[0008] In these examples, the SM operation indicated to the WTRU may be associated with establishing a control session between the second network node and the WTRU, or with establishing a control session between the second network node and a space sensor associated with the WTRU. In these examples, the first network node may send the notification regarding the SM operation to the WTRU in response to receiving a control session establishment request from the second network node that includes one or more of the following: WTRU information, space sensor information, and SM control session configuration information. In these examples, the control session establishment request received from the second network node may also indicate a Quality of Service (QoS) requirement associated with the control session, and wherein the first network node may indicate the QoS requirement to a communication network device responsible for maintaining the control session. In these examples, the first network node may receive a response from the WTRU indicating whether the control session has been successfully established, contact information associated with the control session, or the method of acquiring SM data from the WTRU or the space sensor associated with the WTRU. In these examples, the first network node may send a control session establishment response to the second network node, wherein the control session establishment response may indicate whether the control session has been successfully established, the contact information associated with the control session, or the method of acquiring SM data from the WTRU or the space sensor associated with the WTRU.

[0009] In this example, the first network node described herein may be an SM management server, and the second network node may be an application server. Attached Figure Description

[0010] Figure 1A This is a system diagram illustrating an exemplary communication system that can implement one or more of the disclosed embodiments.

[0011] Figure 1B This illustrates that, according to one embodiment, it is possible to... Figure 1AThe system diagram shows an exemplary wireless transmit / receive unit (WTRU) used in the communication system.

[0012] Figure 1C This illustrates that, according to one embodiment, it is possible to... Figure 1A The system diagram shows an exemplary radio access network (RAN) and an exemplary core network (CN) used in the communication system shown.

[0013] Figure 1D This illustrates that, according to one embodiment, it is possible to... Figure 1A The system diagram shows another exemplary RAN and another exemplary CN used in the communication system shown.

[0014] Figure 2 This is a system diagram illustrating the Space Sensor Management Function (SSMF) deployed within the Application Client (AC) and / or Application Server (AS) on the WTRU.

[0015] Figure 3 This is a system diagram illustrating an SSMF that includes an enabled client on the WTRU and / or an enabled server in the data network.

[0016] Figure 4 This is a flowchart illustrating an exemplary process for registering a space sensor.

[0017] Figure 5 This is a flowchart illustrating an exemplary process of space sensor discovery triggered by a network.

[0018] Figure 6 This is a flowchart illustrating an exemplary process for acquiring measurements from space sensors.

[0019] Figure 7 This is a flowchart illustrating an exemplary process for establishing a space sensor control session. Detailed Implementation

[0020] Figure 1AThis diagram illustrates an example communication system 100 in which one or more of the disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, and broadcasting to multiple wireless users. The communication system 100 enables multiple wireless users to access such content by sharing system resources, including wireless bandwidth. For example, the communication system 100 may employ one or more channel access methods, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), Single Carrier FDMA (SC-FDMA), Zero-Tail Unique Word DFT Extended OFDM (ZT-UW DTS-s OFDM), Unique Word OFDM (UW-OFDM), Resource Block Filtered OFDM, Filter Bank Multicarrier (FBMC), etc.

[0021] like Figure 1A As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, Public Switched Telephone Network (PSTN) 108, Internet 110, and other networks 112. However, it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Any of the WTRUs 102a, 102b, 102c, and 102d may be any type of device configured to operate and / or communicate in a wireless environment. For example, WTRUs 102a, 102b, 102c, and 102d (any of which may be referred to as a “station” and / or “STA”) may be configured to transmit and / or receive wireless signals and may include user equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or MiFi devices, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. Any of WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

[0022] The communication system 100 may also include base station 114a and / or base station 114b. Each of base stations 114a and 114b can be any type of device configured to wirelessly connect to at least one of WTRUs 102a, 102b, 102c, and 102d to facilitate access to one or more communication networks, such as CN 106 / 115, Internet 110, and / or other networks 112. As an example, base stations 114a and 114b may be base transceiver stations (BTS), NodeBs, eNodeBs, home NodeBs, home eNodeBs, gNBs, NR NodeBs, site controllers, access points (APs), wireless routers, etc. Although base stations 114a and 114b are each depicted as a single element, it will be understood that base stations 114a and 114b may include any number of interconnected base stations and / or network elements.

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

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

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

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

[0027] In one embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as NR radio access, which can use New Radio (NR) to establish air interface 116.

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

[0029] In other embodiments, base station 114a and WTRUs 102a, 102b, 102c may implement wireless technologies such as IEEE 802.11 (i.e., Wi-Fi), IEEE 802.16 (i.e., Global Microwave Access Interoperability (WiMAX)), CDMA2000, CDMA 2000 1X, CDMA 2000 EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rate GSM Evolution (EDGE), GSMEDGE (GERAN), etc.

[0030] Figure 1A Base station 114b can be, for example, a wireless router, a home NodeB, a home eNodeB, or an access point, and can utilize any suitable RAT to facilitate wireless connectivity in a local area such as a business premises, home, vehicle, campus, industrial facility, air corridor (e.g., for drone use), road, etc. In one embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, base station 114b and WTRUs 102c, 102d can utilize cellular-based RATs (e.g., WCDMA, CDMA 2000, GSM, LTE-A, LTE-A Pro, NR, etc.) to establish picocells or femtocells. Figure 1A As shown, base station 114b can have a direct connection to Internet 110. Therefore, base station 114b does not need to access Internet 110 via CN 106 / 115.

[0031] RAN 104 / 113 can communicate with CN 106 / 115, which can be any type of network configured to provide voice, data, application, and / or Voice over Internet Protocol (VoIP) services to one or more of WTRUs 102a, 102b, 102c, and 102d. Data may have varying Quality of Service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. CN 106 / 115 can provide call control, billing services, location-based services, prepaid calling, internet connectivity, video distribution, etc., and / or perform advanced security functions (such as user authentication). Although in Figure 1AAlthough not shown, it should be understood that RAN 104 / 113 and / or CN 106 / 115 can communicate directly or indirectly with other RANs using the same RAT as or a different RAT than RAN 104 / 113. For example, in addition to being connected to RAN 104 / 113, which can utilize NR radio technology, CN 106 / 115 can also communicate with another RAN (not shown) using GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

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

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

[0034] Figure 1B This is a system diagram illustrating example WTRU 102. (See diagram below.) Figure 1B As shown, WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keyboard 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power supply 134, a Global Positioning System (GPS) chipset 136, and / or other peripheral devices 138, etc. It is understood that WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with the embodiments.

[0035] Processor 118 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. Processor 118 may perform signal encoding, data processing, power control, input / output processing, and / or any other functions that enable WTRU 102 to operate in a wireless environment. Processor 118 may be coupled to transceiver 120, and transceiver 120 may be coupled to transmitting / receiving element 122. Although Figure 1B While the processor 118 and transceiver 120 are depicted as separate components, it should be understood that the processor 118 and transceiver 120 may be integrated together in an electronic package or chip.

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

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

[0038] Transceiver 120 can be configured to modulate signals transmitted by transmitting / receiving element 122 and demodulate signals received by transmitting / receiving element 122. As described above, WTRU 102 can have multimode capability. Therefore, transceiver 120 can include multiple transceivers to enable WTRU 102 to communicate via various RATs, such as NR and IEEE 802.11.

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

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

[0041] 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) about the current location of the WTRU 102. In addition to, or alternatively to, the information from the GPS chipset 136, the WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114b) via the air interface 116, and / or determine its location based on the timing of signals received from two or more neighboring base stations. It should be understood that the WTRU 102 may acquire location information using any suitable location determination method, while remaining consistent with the embodiments.

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

[0043] WTRU 102 may include a full-duplex radio, for which the transmission and reception of some or all of the signals (e.g., signals associated with specific subframes for uplink (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit to reduce and / or substantially eliminate self-interference through hardware (e.g., chokes) or through signal processing by a processor (e.g., a separate processor (not shown) or processor 118). In one embodiment, WTRU 102 may include a half-duplex radio, for which the transmission and reception of some or all of the signals (e.g., signals associated with specific subframes for uplink (e.g., for transmission) or downlink (e.g., for reception)) are separate.

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

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

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

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

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

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

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

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

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

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

[0054] A WLAN in Infrastructure Basic Services Set (BSS) mode can have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP can access or interface with a distribution system (DS) or another type of wired / wireless network that carries traffic entering and / or leaving the BSS. Traffic originating outside the BSS destined for a STA can be delivered to the STA via the AP. Traffic originating from a STA destined for a destination outside the BSS can be sent to the AP for delivery to the appropriate destination. Traffic between STAs within the BSS can be sent via the AP, for example, where a source STA can send traffic to the AP, and the AP can deliver the traffic to the destination STA. Traffic between STAs within the BSS can be considered and / or referred to as peer-to-peer traffic. This peer-to-peer traffic can be sent between the source and destination STAs (e.g., directly between the source and destination STAs) using Direct Link Establishment (DLS). In some representative embodiments, the DLS may use 802.11e DLS or 802.11z Tunneled DLS (TDLS). WLANs using the Standalone BSS (IBSS) mode cannot have access points (APs), and STAs within the IBSS or using the IBSS (e.g., all STAs) can communicate directly with each other. The IBSS communication mode may sometimes be referred to as the "ad-hoc" communication mode in this document.

[0055] When using 802.11ac infrastructure operating mode or a similar operating mode, the AP can transmit beacons on a fixed channel, such as the primary channel. The primary channel can be of fixed width (e.g., a bandwidth of 20 MHz) or dynamically set via signaling. The primary channel can be the operating channel of the BSS and can be used by the STA to establish a connection with the AP. In some representative embodiments, such as in an 802.11 system, Carrier Sense Multiple Access (CSMA / CA) with collision avoidance can be implemented. For CSMA / CA, STAs including the AP (e.g., each STA) can listen on the primary channel. If the primary channel is listened to / detected and / or determined to be busy by a particular STA, that particular STA can back off. A single STA (e.g., only one station) can transmit at any given time within a given BSS.

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

[0057] Very High Throughput (VHT) STAs can support channels with widths of 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz. 40 MHz and / or 80 MHz channels can be formed by combining consecutive 20 MHz channels. A 160 MHz channel can be formed by combining eight consecutive 20 MHz channels, or by combining two non-consecutive 80 MHz channels; this can be referred to as an 80+80 configuration. For the 80+80 configuration, after channel coding, the data can pass through a segmented parser that divides the data into two streams. Each stream can be processed separately using Inverse Fast Fourier Transform (IFFT) and time-domain processing. The streams can be mapped onto the two 80 MHz channels, and the data can be transmitted by the transmitting STA. At the receiver of the receiving STA, the operation of the 80+80 configuration can be reversed, and the combined data can be sent to the Media Access Control (MAC).

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

[0059] WLAN systems that can support multiple channels and channel bandwidths (e.g., 802.11n, 802.11ac, 802.11af, and 802.11ah) include a channel that can be designated as the primary channel. The primary channel can have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and / or limited by the STA that supports the minimum bandwidth operating mode among all STAs operating in the BSS. In the 802.11ah example, for STAs that support (e.g., only support) the 1MHz mode (e.g., MTC type devices), the primary channel can be 1 MHz wide even if the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier Sense and / or Network Assignment Vector (NAV) settings can depend on the status of the primary channel. If the primary channel is busy, for example, because an STA (which only supports the 1 MHz operating mode) is transmitting to the AP, the entire available band can be considered busy even if most of the band remains idle and available.

[0060] In the United States, the available frequency bands for 802.11ah are from 902 MHz to 928 MHz. In South 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.11ah is 6 MHz to 26 MHz, depending on the country code.

[0061] Figure 1D This is a system diagram illustrating RAN 113 and CN 115 according to an embodiment. As described above, RAN 113 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using NR wireless technology. RAN 113 can also communicate with CN 115.

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

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

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

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

[0066] Figure 1DThe CN 115 shown may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and may include data networks (DN) 185a, 185b. While each of the foregoing elements is depicted as part of the CN 115, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0067] AMF 182a and 182b can connect to one or more of gNBs 180a, 180b, and 180c in RAN 113 via the N2 interface and can act as control nodes. For example, AMF 182a and 182b can be responsible for authenticating users of WTRU 102a, 102b, and 102c, supporting network slicing (e.g., handling different PDU sessions with different needs), selecting specific SMF 183a and 183b, managing registration areas, terminating NAS signaling, mobility management, and so on. AMF 182a and 182b can use network slicing to customize CN support for WTRU 102a, 102b, and 102c based on the type of service being used by WTRU 102a, 102b, and 102c. For example, different network slices can 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, and services for Machine Type Communication (MTC) access. AMF 182 can provide control plane functions for handover between RAN 113 and other RANs (not shown) employing other radio technologies (such as LTE, LTE-A, LTE-A Pro and / or non-3GPP access technologies (such as WiFi)).

[0068] SMFs 183a and 183b can connect to AMFs 182a and 182b in CN 115 via the N11 interface. SMFs 183a and 183b can also connect to UPFs 184a and 184b in CN 115 via the N4 interface. SMFs 183a and 183b can select and control UPFs 184a and 184b, and configure them to route traffic through UPFs 184a and 184b. SMFs 183a and 183b can perform other functions, such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, and providing downlink data notifications. PDU session types can be IP-based, non-IP-based, Ethernet-based, etc.

[0069] UPF 184a and 184b can connect to one or more of gNB 180a, 180b, and 180c in RAN 113 via the N3 interface. This provides WTRU 102a, 102b, and 102c with access to packet-switched networks (such as Internet 110) to facilitate communication between WTRU 102a, 102b, and 102c and IP-enabled devices. UPF 184 and 184b can perform other functions such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, and providing mobility anchoring.

[0070] CN 115 can facilitate communication with other networks. For example, CN 115 may include, or communicate with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) serving as an interface between CN 115 and PSTN 108. Furthermore, CN 115 may provide WTRUs 102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In one embodiment, WTRUs 102a, 102b, and 102c can be connected to DNs 185a and 185b via UPFs 184a and 184b through their N3 interfaces and their N6 interfaces with local data networks (DNs) 185a and 185b.

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

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

[0073] One or more simulation devices can perform one or more functions (including all functions) without being implemented / deployed as part of a wired and / or wireless communication network. For example, simulation devices can be used in test scenarios within a test laboratory and / or an undeployed (e.g., tested) wired and / or wireless communication network to perform testing of one or more components. One or more simulation devices can be test equipment. Simulation devices can transmit and / or receive data using direct RF coupling and / or wireless communication via RF circuitry (e.g., which may include one or more antennas).

[0074] The term "timer" as used in this document can refer to time, time period, time tracking, time period tracking, combinations thereof, and / or similar items. The term "timer expiration" as used in this document can refer to the determination that a time has begun or that a time period has expired.

[0075] The terms “measurement” and “measurement report” are used interchangeably in this document. The terms “AS” and “AF” are used interchangeably in this document.

[0076] A sensing NF can be a network function (NF) that understands service requests from application functions (AFs) and has a sensing mechanism that can derive the corresponding requests. Based on this sensing mechanism, the sensing NF can forward the request to a relevant NF within the core network (e.g., 5GC), which can then serve the area of ​​interest or the requesting entity (e.g., WTRU). When the AF is a third-party application not trusted by the system (e.g., 5GS), the AF and / or integrated sensing and network functions (ISANF) can communicate via network open functions (NEF).

[0077] An application server (AS) may lack the ability to discover space-sensing WTRUs based on application-layer mapping and location requirements. For example, the AS may lack the ability to establish a space sensor control session with the discovered space sensor. The embodiments described herein can provide space sensor management and control.

[0078] Service enabling layer functions (e.g., SSMF) can provide discovery capabilities, measurement collection capabilities, and / or control session establishment capabilities within a system (e.g., 5GS). When requested by an AS, a server enabling function (e.g., SSMF-S) can use discovery filters (e.g., space sensor selection criteria) and / or the core network (e.g., 5GC) to discover registered and / or available space sensors associated with (e.g., on or connected to) a WTRU. The server enabling function can facilitate space sensor measurement collection and / or remote space sensor control session establishment by exchanging messages with a client enabling function (e.g., SSMF-C), which can be installed on the WTRU associated with one or more discovered space sensors.

[0079] An enabler server with SSMF-S capability can perform one or more actions to discover and / or control space sensors associated with the WTRU. For example, the SSMF-S can receive a space sensor registration request from the SSMF-C (e.g., which may be part of the WTRU) to register the space sensor. The request may include information about the space sensor (e.g., the identifier (ID) of the SSMF-C, the type of the space sensor or sensing information, metadata associated with the sensing data, and / or an indication of whether the space sensor can be remotely controlled).

[0080] In one example, the SSMF-S can receive a space sensor discovery request from an application server (AS). The request may include one or more space sensor information filters (e.g., space sensor selection criteria). The SSMF-S can identify space sensors registered with the SSMF and matching the space sensor information filters provided in the discovery request. For example, the SSMF-S may do so upon receiving the space sensor discovery request. In this example, the SSMF-S may perform a process with the core network (e.g., 5GC) to obtain (e.g., as indicated by the space sensor discovery request) a list of WTRUs in the requested area. The SSMF-S may send a space sensor discovery response to the AS. The response may include space sensor information and / or WTRU information for the discovered space sensor.

[0081] In one example, the SSMF-S can receive a space sensor control session request from the AS. The request may include space sensor information, WTRU information, and / or space sensor control session configuration. The SSMF-S can use the space sensor information and / or the WTRU information to determine the WTRU for which it requests the control session. For example, the SSMF-S may do so upon receiving the space sensor control session request.

[0082] The SSMF-S can send a space sensor control session request or notification to at least one WTRU, requesting (e.g., demanding) a control session. The request or notification may include space sensor information, WTRU information, and / or space sensor control session configuration. The SSMF-S can receive a space sensor control session response from the WTRU. The response may include an indication of whether the space sensor control session configuration has been successfully received and applied. The response may include contact information for the space sensor and / or SSMF-C, or information that can be used to obtain sensing data from the SSMF-C.

[0083] The SSMF-S can send a space sensor control session response to the AS. The response may include an indication of whether the space sensor control session configuration has been successfully received and applied. The response may also include contact information for the space sensor and / or SSMF-C, or information that can be used to obtain sensing data from the SSMF-C.

[0084] If the space sensor control session configuration includes control session QoS, the SSMF-S can perform the process of configuring the requested QoS on the IP flow between the AS and the space sensor (e.g., or SSMF-C) with the core network (e.g., 5GC).

[0085] A positioning system can be provided to determine the geographic location (e.g., longitude, latitude, altitude, etc.), three-dimensional (3D) location, and / or orientation (e.g., pitch, yaw, roll, etc.) of an object in space. The location can be a global location on Earth or a relative location with respect to a known reference point.

[0086] Geolocation systems allow radio receivers to determine their geographic location using microwave signals from satellites and / or ground-based transmitters. For example, Global Navigation Satellite Systems (GNSS) (such as the Global Positioning System (GPS)) can have global coverage and enable radio receivers to determine their geographic location by measuring microwave signals from a set of satellites within range of the receiver. Geolocation accuracy can be within a few meters in outdoor environments, but decreases rapidly in most underground or indoor environments.

[0087] Indoor positioning systems (IPS) can be used to locate people or objects in an indoor environment. These systems can use the network of devices to acquire device-specific positioning measurements (e.g., wireless technology, magnetic fields, ultra-wideband, etc.) and can use various positioning techniques to determine location. For example, an IPS may include a physical deployment of wireless access points and software on the WTRU to collect and report measurements from the access points. Based on these measurements, algorithms can be used to determine the location of the WTRU. The positioning accuracy of an indoor positioning system can be deployment-specific and can vary from coarse to very precise (e.g., within a few centimeters).

[0088] Visual positioning systems can use image processing algorithms to compare images captured from a device (such as a WTRU camera) with a database of captured images to determine the device's position and / or orientation. Positioning accuracy depends on the quality of the specific algorithm and the quality and quantity of information available in the visual positioning database.

[0089] Cellular positioning systems can use reference signal measurements and / or cell tower triangulation to determine the location of the WTRU (e.g., a mobile network operator (MNO) can use many technologies for WTRU positioning). Mobile devices can support a variety of radio and / or sensors (e.g., GPS, Wi-Fi, etc.), which can be utilized by positioning systems (e.g., 3GPP positioning systems). For example, deployments (e.g., 4G deployments) can support LTE positioning architectures and protocols that enable location servers in the network to obtain 3GPP and / or non-3GPP location information from the WTRU to determine more accurate WTRU positioning. Deployments (e.g., 5G deployments) can support 5G positioning architectures, which may include enhancements to the LTE positioning architecture (e.g., with new radio (NR) sensing technologies to provide more accurate WTRU positioning).

[0090] Spatial mapping and positioning can be provided. Spatial mapping can be a 3D digital model of the physical environment. Spatial mapping may include collecting and processing sensor measurements at different locations to construct an environmental map. Spatial mapping can use (for example, required) sensor location information, wireless sensing data, and / or non-3GPP sensor data to create an accurate spatial map of a physical area.

[0091] Localization can refer to the position and orientation of an object in 3D space (e.g., pitch, yaw, roll, etc.). An object's localization can be determined by processing measurements from sensors within the object's visible range (e.g., using RGBD cameras, high-resolution cameras, etc.), from sensors within the object's wireless range (e.g., using Wi-Fi access points, Bluetooth devices, etc.), and / or from sensors attached to the object itself (e.g., gyroscopes, accelerometers, magnetometers, GPS, RGBD cameras, high-resolution cameras, Wi-Fi devices, Bluetooth devices, etc.). Localization can be determined by comparing sensor measurements with mapped measurements stored in an environmental spatial map. Localization accuracy can vary depending on the type of sensors used to acquire the measurements and / or the precision and latency of the measurements used to calculate the position.

[0092] Some extended reality (XR) and metaverse use cases may use (e.g., require) accurate WTRU positioning in different environments. For example, XR applications may request (e.g., require) real-time and accurate WTRU positioning information to correctly overlay augmented reality (AR) content in outdoor sporting events or indoor concerts. As another example, metaverse AR applications may request (e.g., require) WTRU positioning information to determine whether spatial anchors in the digital world can be seen and detected by the WTRU as it moves through a park or indoor shopping mall.

[0093] Some positioning systems with WTRU positioning capabilities can operate under certain conditions and in specific environments. Many indoor environments require (e.g., specific wireless deployment and positioning technologies) to achieve accurate WTRU positioning. To enable adoption of certain use cases, efficient methods for achieving accurate WTRU positioning in a variety of environments can be provided. Systems (e.g., 3GPP systems) can offer standardized architectures and broad coverage (e.g., outdoor and indoor), making them highly useful for providing broad and accurate WTRU positioning.

[0094] Spatial maps of the world can be created and / or managed to enable several XR and metaverse use cases. Some spatial mapping technologies may have limited indoor coverage. Sensing technologies can be diverse and can provide different levels of measurement accuracy. In one example, a system (e.g., a 3GPP system) can be used to integrate and / or aggregate sensing and spatial mapping technologies.

[0095] To support spatial mapping and positioning, systems (such as 3GPP systems) can enable space sensors to provide spatial sensing measurements (e.g., to space map owners) to create and / or update space maps and / or accurately locate WTRUs. The system can (e.g., to space map owners) provide the ability to request and manage spatial sensing data from relevant space sensors based on sensor location and / or capabilities.

[0096] The examples disclosed herein can use 3GPP systems to assist in the discovery and selection of spatially sensing WTRUs based on application layer mapping and / or location requirements. The examples disclosed herein can use 3GPP systems to implement measurement requests and reports from discovered sensors and assist in establishing application layer control sessions.

[0097] The examples disclosed herein can provide enhancements to enable the application server (AS) to discover, acquire measurements from space sensors associated with the WTRU, and / or establish control sessions with said space sensors.

[0098] The examples disclosed herein enable access to space sensor information in various environments by leveraging network coverage (e.g., 3GPP network coverage) and by providing space sensor discovery, measurement collection, and remote control capabilities. In one example, a Space Sensor Management Function (SSMF) can be provided, and the SSMF can be an enhancement to a service enabling layer (e.g., a 3GPP service enabling layer). The SSMF can manage space sensors and enable space sensor control sessions.

[0099] In one example, when requested by an AS, a server enabler function (e.g., SSMF-S) can use one or more discovery filters (e.g., space sensor selection criteria) and a core network (e.g., 5GC) to discover registered and available space sensors associated with a WTRU. The server enabler function can facilitate space sensor measurement collection and establish remote space sensor control sessions by exchanging messages with a client enabler function (e.g., SSMF-C) located on the WTRU associated with the discovered space sensor.

[0100] Although the examples discussed in this paper address service enablement layer enhancement for space sensor management, it should be noted that the implementations described herein are not limited to service enablement layer enhancement and can be applied to other sensing scenarios.

[0101] When referred to in this document, an application client (AC) can be a user application residing on a WTRU and communicating with an AS. A WTRU can use one or more ACs.

[0102] When used in this document, an application server (AS) can be an application server residing in a data network (DN) or a software server running on general-purpose hardware and providing services to an AC. An AS can serve one or more AC instances that may reside on different WTRUs.

[0103] When mentioned in this document, an enabling client (EC) may be a service enabler residing on a WTRU that communicates with the ES and / or provides client-side functionality to the AC for enabling services.

[0104] When mentioned in this document, an enabling server (ES) can be a service enabler residing in a DN and / or providing server-side functionality to the AS for enabling services. An ES can serve one or more EC instances that may reside on different WTRUs.

[0105] When referred to herein, WTRU information may be and / or may include information about the WTRU that enables the AC to communicate with the AS. The WTRU information may include WTRU identifiers (e.g., Subscription Persistent Identifier (SUPI), General Public Subscription Identifier (GPSI), telephone numbers, etc.).

[0106] When referred to herein, WTRU status can be and / or may include information about the WTRU that indicates its device status. The WTRU status may include power status (e.g., battery level), connectivity status (e.g., signal quality, RAT), and / or similar items.

[0107] A spatial sensor can be a sensor that captures information about an object to determine the object's position in space. The spatial sensor can be co-located with the object (e.g., the object whose position is determined) or it can be separate from the object. For example, a gyroscope on a smartphone can be used to determine the smartphone's orientation. As another example, a wall-mounted RGBD camera can be used to determine the position of a box moving in a factory.

[0108] Spatial maps can be 2D or 3D digital models of the physical environment. Spatial mapping can include collecting and processing sensor measurements at different locations to construct an environmental map. Spatial mapping can use (for example, requires) sensor location information, wireless sensing data, and / or non-3GPP sensor data to create an accurate spatial map of a physical area.

[0109] Positioning can refer to the location and / or orientation of an object in 3D space (e.g., pitch, yaw, roll, etc.). Positioning can be determined by processing measurements from sensors and comparing them to a spatial map of the environment. Positioning accuracy can vary depending on the type of sensor used to acquire the measurements and / or the precision and latency of the measurements used for positioning.

[0110] Space sensor information may include information determined and / or received from space sensors. Space sensor information may include one or more of the following: space sensor identifier (e.g., unique identifier), space sensor type (e.g., RGBD camera, LiDAR camera, high-resolution camera), space sensor location (e.g., geographic location, positioning), space sensor status (e.g., availability), space sensor configuration (e.g., power level, scaling level, resolution), space sensor measurement capabilities (e.g., accuracy, QoS requirements), space sensor control information, and / or similar items.

[0111] Space sensor control information may include information related to or associated with the controllability of space sensors. This information may include space sensor control capabilities, such as space sensor mobility (e.g., geographic region, 2D and / or 3D location range, etc.), space sensor rotation (e.g., camera orientation, angle, range, etc.), and / or space sensor scaling (e.g., camera resolution range). Space sensor control information may also include control session QoS parameters (e.g., QoS requirements).

[0112] Space sensor management capabilities can be provided. The examples disclosed herein can provide enhancements to the service enablement layer (e.g., the 3GPP service enablement layer) and / or the core network (e.g., the 5G core network) to enable the discovery, management, and control of space sensors (e.g., for creating or updating spatial maps or determining accurate WTRU locations). These enhancements can be provided by Space Sensor Management Functions (SSMF).

[0113] In a system (such as a 3GPP system), SSMF can provide space sensor management services to WTRUs and application servers (such as AFs or NFs). Space sensor management services may include processes for registering space sensors, discovering space sensors, acquiring measurements from space sensors, and / or establishing control sessions with space sensors.

[0114] Deployment options are available. Different combinations of deployments described herein are possible. In one example, a 3GPP deployment can be used, and the WTRU can request services from the AS. The WTRU can establish a connection to access the AS, which can be via a network (e.g., a 3GPP wireless communication network). SSMF can follow a client-server model by splitting the SSMF into client and server components. The SSMF client (SSMF-C) can reside on the WTRU or an end component, and the SSMF server (SSMF-S) can be accessed via a network (e.g., on a core network node or device) or located within the network. Together, the SSMF-C and SSMF-S can provide SSMF services to applications. For example, an application consuming the service can run on the WTRU and can be called an application client (AC), and can use the functionality on the WTRU and / or provided by the SSMF-C. The application providing the service can run within the network and can be called an application server (AS).

[0115] SSMF client and server functionalities can be deployed within an application. Figure 2 This is a system diagram illustrating an example where SSMF is deployed within an application client (AC) and / or application server (AS) on a WTRU. For example, Figure 2 This illustrates SSMF functionality deployed within an AC on a WTRU and an AS within a data network. For example, the SSMF functionality can be encapsulated in a library that is statically linked to the AC or AS, or dynamically loaded by the AC or AS.

[0116] SSMF can be deployed as a stand-alone functional element in a WTRU or data network. Figure 3 This is a system diagram illustrating an example where SSMF is deployed as an enabling client on a WTRU and / or as an enabling server in a data network. The AC and AS can access the functionality provided by the enabling client and enabling server, respectively, via defined application programming interfaces (APIs) or interfaces.

[0117] Various SSMF deployment configurations can be used. For example, SSMF-S can be deployed in an ES that is not located in the same DN as the AS. For example, the ES can be deployed in a central MNO DN, EDN, another DN, or a cloud DN.

[0118] For example, the SSMF-C can be deployed in an EC that is not located on the same WTRU as the AC. For example, an AC deployed on the TE can interact with an EC deployed in the MT section of the WTRU using AT commands. For example, an AC deployed on the TE can interact with an EC that can also be deployed in the TE section of the WTRU. For example, the AC can communicate with an EC running in the WTRU using a tethered connection (e.g., a D2D connection, such as Bluetooth, WiFi, or PC5).

[0119] In a network (e.g., network-only) deployment example, SSMF capabilities can be fully provided by SSMF-S.

[0120] Space sensor management and registration can be provided. SSMF supports space sensor registration. Space sensor registration allows producers of space sensing data (such as space sensors) to expose their sensing and control capabilities to consumer applications and services. By registering with SSMF, space sensors can be discovered by consumers, perform space sensing measurements upon consumer requests and configurations, be remotely controlled by consumers, combinations thereof, and similar operations.

[0121] In one example, the SSMF architecture enables application servers that wish to create or update spatial maps to discover sensors (e.g., cameras, LiDAR cameras, etc.), establish connections with the sensors, control the sensors, acquire data from the sensors (e.g., video, images, LiDAR measurement data) and / or perform similar operations to create and update spatial maps.

[0122] Figure 4 The process of registering a space sensor is illustrated. In one example, the space sensor can be deployed on the terminal equipment (TE) of the WTRU and establish a local connection with the mobile terminal (MT) portion of the WTRU (the SSMF-C can reside in said MT portion). It should be understood that other space sensor deployments are possible. For example, the space sensor can be deployed on a device connected to a 3GPP wireless network via a non-3GPP network (e.g., the SSMF-S can reside in a 3GPP wireless network), in which case the space sensor can register directly with the SSMF-S. It should also be understood that the space sensor can reside on a device tethered to the WTRU (e.g., an AR headset), and said device can access the SSMF-C residing on the WTRU via the tethered connection.

[0123] exist Figure 4At point 1, the space sensor can send a space sensor registration request to the SSMF-C. The space sensor registration request may include space sensor information. For example, the registration request may indicate one or more of the following: space sensing capability, the number of sensors available per WTRU, sensor type, and similar items. For example, the information may indicate that the space sensor is a wall-mounted RGBD camera on the ground floor of an indoor art gallery with precise measurement capabilities and has (e.g., required) a preset bandwidth for uploading measurements. The information may indicate that the camera can be remotely controlled to change its viewing angle and resolution.

[0124] The registration request may include metadata information describing what the sensor senses. For example, if the sensor is a camera, the sensor information may identify the sensor's location and the direction the camera can view. For example, if the sensor is an environmental sensor, the sensor information may identify the location where the sensor can collect environmental data.

[0125] The spatial sensor information may indicate that a sensor is associated with a service, may indicate how to access the service (e.g., URL, Universal Resource Identifier (URI), IP address), may indicate how to access sensor measurements (e.g., via URI), and / or may provide information about APIs associated with the service.

[0126] The space sensor information may include information about the deployment of the sensor relative to the associated WTRU. For example, the space sensor information may indicate that the sensor is locally connected to the WTRU or tethered to the WTRU.

[0127] The space sensor information may include information about the delay in performing measurements (e.g., measurement delay and control delay), information about the energy consumption associated with the measurement, and / or information about the energy capabilities of the sensor or associated WTRU (e.g., energy source). This information can be used to select sensors that can provide information in a timely manner or that may not be battery-powered (e.g., using the power grid instead of batteries).

[0128] At point 2 in Figure 4, SSMF-C can send a space sensor registration request to SSMF-S. The space sensor registration request may include space sensor information and / or WTRU information from a list of space sensors (e.g., obtained from it). For example, the registration request may provide WTRU IDs (e.g., GPSI, SUPI, etc.) and / or endpoint information for interacting with the sensors. The space sensor registration may include information received from the AC at point 1 (e.g., metadata information further describing what the sensors sense).

[0129] The space sensor registration request may include an identifier for the SSMF-C. The identifier for the SSMF-C may be a user identifier (e.g., the identifier may be in the format of a user identifier, such as a network access identifier (NAI)).

[0130] SSMF-C can support multiple sensors simultaneously and can combine space sensor information in a space sensor registration request. If a space sensor is already registered, SSMF-C can send a space sensor registration update request to SSMF-S to provide updates to either the space sensor information or the WTRU information.

[0131] A WTRU can have a capacity, which refers to the count of the number of sensors that can be registered to that WTRU simultaneously. For example, if a sensor wants to register with it and the WTRU associated with it has reached its sensor support capacity, the space sensor registration request can be rejected, delayed, or shelved.

[0132] A space sensor may be able to attach to or associate with a WTRU or SSMF-C that it may have a connection with. For example, a tethering device may be associated with WTRU1 (e.g., the first WTRU) that may have EC1, or with WTRU2 (e.g., the second WTRU) that may have EC2. In one example, a space sensor may be associated with one or more WTRUs. In one example, a space sensor may be connected to a wireless communication system (e.g., 5GS) via one WTRU at a time. If the space sensor happens to be associated with WTRU2 instead of WTRU1, a registration process can be performed, in which the WTRU2 identifier is ultimately used.

[0133] exist Figure 4 At three points, SSMF-S can determine whether a WTRU (e.g., SSMF-C) is authorized to register as a space sensor. If authorized, SSMF-S can store space sensor information and WTRU information. If not authorized, SSMF-S can indicate an error in its response to SSMF-C, along with an error reason value to indicate the cause of failure. For example, SSMF-S can store the space sensor information of authorized space sensors in a local database. If space sensor functionality is authorized to a group of WTRUs within a network operator, WTRUs from certain network operators (e.g., WTRUs only) can be authorized to register as space sensors. This authorization can depend on WTRU capabilities or WTRU mobility patterns (e.g., stationary WTRUs can be preferentially registered as space sensors compared to highly mobile WTRUs). For example, the authorization for a WTRU to act as a space sensor can depend on sensor type or sensor metadata (e.g., content type).

[0134] SSMF-S can invoke the NEF API to check whether SSMF-C is authorized for registration as a space sensor. For example, SSMF-S can provide the NEF with the identifier of SSMF-C and request the core network (e.g., 5GC) to authorize SSMF-C for registration as a space sensor. NEF can check whether SSMF-C is authorized by querying UDM / UDR and can respond to SSMF-S with an indication of whether SSMF-C can be authorized.

[0135] exist Figure 4 At four points, SSMF-S can send a space sensor registration response to SSMF-C. This response may include an indication of whether the space sensor has been successfully registered, and a registration identifier (e.g., a unique registration identifier), which can be used to identify stored space sensor information during calls to SSMF-S (e.g., subsequent calls). The authorization may be time-limited, and a timer value may be provided to the SSMF-C of each WTRU, where the WTRU can perform re-registration upon timer expiration. The core network (e.g., 5GC) or SSMF-S can track the timer value and the current timer value to prevent the WTRU from performing a registration update with the reason "timer expired" when the timer may not have expired at SSMF-S.

[0136] exist Figure 4 At point 5, SSMF-C can create a notification channel to receive notifications from SSMF-S. This can be used to support situations where messages from SSMF-S cannot reach SSMF-C. For example, a notification channel might be requested (e.g., needed) to handle user plane connections between the WTRU and SSMF-S DN that may require Network Address Translation (NAT) traversal, and there might be no underlying session between SSMF-C and SSMF-S. This step can be skipped in examples where the control plane is available for transmitting messages between SSMF-C and SSMF-S, and in examples where SSMF-C may have a pre-established transport session with SSMF-S.

[0137] exist Figure 4 At point 6, SSMF-C can send a space sensor registration response to AC. This service registration response may include a unique registration identifier received from SSMF-S. AC can use this registration identifier (e.g., a unique registration identifier) ​​to identify stored space sensor information during calls to SSMF-S (e.g., subsequent calls). If a timer value is provided at point 4, SSMF-C can start a timer so that it can trigger re-registration if the timer may have expired.

[0138] Space sensor discovery can be provided. SSMF supports network-triggered space sensor discovery, enabling ASs in the network to discover space sensors that match the provided space sensor information discovery filters. Space sensors can register with SSMF to become discoverable. ASs can select one or more space sensors from the discovered list to obtain measurements or perform remote control.

[0139] Figure 5 This is a flowchart illustrating an exemplary process of network-triggered space sensor discovery. In the example, a space sensor registration process can be performed to register one or more space sensors.

[0140] exist Figure 5 At one point in the map, the AS can trigger a discovery by a spatial sensor. For example, a shopping mall spatial mapping application can request (e.g., require) spatial sensor measurements to improve the accuracy of spatial maps of recently renovated areas of the shopping mall.

[0141] exist Figure 5 At two points, the AS can send a spatial sensor discovery request to the SSMF-S. This request can include spatial sensor information filters (e.g., spatial sensor selection criteria) to discover available spatial sensors in the area of ​​interest. The spatial sensor information filters can be used to describe to the SSMF-S the desired attributes of the sensors to be discovered, including information about the area of ​​interest. The provided filter information can include any of the spatial sensor information described herein (e.g., sensor type, duration of requested sensing measurements, requested sensor accuracy, etc.). The filter information can specify location data for the area of ​​interest (e.g., geographic region, town address, building identifier, floor, etc.), where the spatial sensors may have the sensing capabilities to be discovered. For example, a shopping mall owner could attempt to discover spatial sensors in an area under renovation by providing a discovery filter with the requested location and the requested sensing capabilities.

[0142] exist Figure 5In three locations, SSMF-S can identify space sensors registered with SSMF and match the space sensor information filters provided in the discovery request. SSMF-S can, for example, invoke the core network (e.g., 5GC) API (e.g., via NEF or via dedicated sensing NF), and can include information such as the space sensor information filters and / or the requested area in the request to the core network (e.g., 5GC) to obtain the latest location information of space sensors associated with WTRUs with space sensing capabilities. For example, SSMF-S can search a local database of registered space sensors to find a set of available space sensors that support the requested sensing capabilities (e.g., attributes described in the space sensor information filters). SSMF-S can then (e.g., based on WTRU identifiers) request the latest space sensor locations from the core network (e.g., 5GC) to determine if the sensor is within the requested area.

[0143] In one example, a core network deployment with enhanced sensing capabilities and functions (such as 5GC) can be used to retrieve a list of available sensors (e.g., including both 3GPP and non-3GPP sensors).

[0144] exist Figure 5 Between points 3 and 4, SSMF-S can select (e.g., filter) relevant sensors based on space sensor information received at point 2. For example, SSMF-S can apply filters to locally stored information about registered sensors and / or to a list of sensors received from the core network (e.g., 5GC) at point 3.

[0145] exist Figure 5 At four points, the SSMF-S can send a space sensor discovery response to the AS. This response can include a list of space sensor information and / or associated WTRU information for space sensors discovered and matched against the discovery filter. If a space sensor is registered directly to the SSMF-S and not attached to a WTRU, the WTRU information can be omitted. For example, the response can identify a RESTful resource hosted on the SSMF-S that stores sensor information. As another example, the response can identify a RESTful resource hosted on the SSMF-C that stores sensor information. When the response identifies a resource stored in the SSMF-C, it can also include a WTRU identifier, which the AS can use to contact the WTRU hosting the SSMF-C and / or read sensor information. As yet another example, the response can indicate whether the identified sensor is controllable by the AS.

[0146] The space sensor discovery response can provide information about service parameters (e.g., requirements) associated with acquiring sensor information. For example, the discovery information may indicate the data rate at which data is streamed from the sensor and delay parameters (e.g., requirements) that can be used to control the sensor.

[0147] The space sensor discovery response may include information such as an address that can be contacted to control the sensor (e.g., the address may be a fully qualified domain name (FQDN), URI, IP, endpoint, etc.).

[0148] exist Figure 5 At the five locations identified, the AS can select one or more spatial sensors from the list to obtain measurements or perform remote control. For example, a shopping mall owner can select one of the identified spatial sensors to obtain spatial measurements from a newly renovated area. The shopping mall owner can then use these measurements to improve the accuracy of the shopping mall's spatial map.

[0149] In one example, the AS might not select any space sensor from the discovered list because none of those space sensors meet the criteria, or because the sensor discovery request may have timed out. If the initial space sensor discovery is unsuccessful, the AS can update the space sensor information filter before initiating a rediscovery attempt.

[0150] In one example, more than one AS may want to select spatial sensors for a service at that AS. For example, if AS0 (e.g., the first AS) has already selected some spatial sensors that may be associated with AS1 (e.g., the second AS), AS1 may be unable to select such sensors as long as AS0 is using them. In this regard, AS1 may receive sensor status information along with a list of discovered sensors. For example, sensors selected and used by another AS may have a sensor availability status of "used," "busy," or "selected," while sensors not used by another AS may have an availability status of "available." In this example, the discovery response may provide AS1 (e.g., only) a list of sensors not used by other ASs.

[0151] Space sensor measurements can be provided. SSMF can support the process of acquiring space sensor measurements. The space sensor measurement process enables the AS to request immediate measurement reports and / or configure event-based or time-based measurement reports from discovered space sensors. SSMF can also configure service flows in the core network (e.g., 5GC) to set QoS on the measurement report stream.

[0152] Figure 6 This is a flowchart illustrating an exemplary process for acquiring measurements from space sensors.

[0153] AS can perform a space sensor discovery process and discover at least one available space sensor (e.g., in...). Figure 6 (at position 0 in the text). AS can select one or more space sensors and trigger a request for measurements from the space sensors.

[0154] exist Figure 6 At point 1, the AS can send a space sensor measurement request to the SSMF-S. The space sensor measurement request may include space sensor information, WTRU information, and / or space sensor measurement report configuration. The space sensor measurement report configuration may include the following parameters (e.g., requirements): the number of measurement reports to be generated (e.g., a single report or multiple reports), measurement quality (e.g., accuracy, error, etc.), measurement frequency (e.g., instantaneous, periodic, time-based, event-based, or continuous), measurement location (e.g., localization, 6D pose, etc.), measurement path, measurement area, measurement target (e.g., identified from space sensor measurement processing), measurement report address (e.g., FQDN, URI, IP, endpoint), and / or similar items. For example, a space map owner may send a measurement request to a set of discovered and selected space sensors in a region of interest to acquire periodic image captures from RGBD cameras installed on WTRUs at specific locations.

[0155] exist Figure 6 At point 2, SSMF-S can use WTRU information to determine which SSMF-C instance to communicate with. SSMF-S can send a space sensor measurement request to SSMF-C. The space sensor measurement request can include any information received from the AS at point 1. SSMF-S can update / modify the measurement report configuration based on the information received at point 1 before sending the measurement report configuration to SSMF-C (e.g., in the space sensor measurement request). If a notification channel exists between SSMF-C and SSMF-S, SSMF-S can send a space sensor measurement notification to SSMF-C. The notification can include the same information elements as the space sensor measurement request received from the AS.

[0156] exist Figure 6 At three points, SSMF-C can use information received from SSMF-S at two points to determine which space sensors can be requested to acquire measurements. SSMF-C can then send a space sensor measurement request to the requested space sensor. This space sensor measurement request can include any information received from SSMF-S at the two points.

[0157] If a space sensor measurement notification is received by the SSMF-C, the SSMF-C may send the space sensor measurement notification to the requesting space sensor. The notification may include one or more of the information elements from the space sensor measurement request described herein.

[0158] exist Figure 6 At four locations, the space sensor can be configured using the space sensor measurement report configuration obtained from SSMF-C at three locations. Upon request, the space sensor can collect the requested measurements and can include those measurements in the space sensor measurement response.

[0159] exist Figure 6 At five points, the space sensor can send a space sensor measurement response to SSMF-C. This space sensor measurement response may include space measurements and / or indications regarding whether the space sensor measurement configuration has been successfully applied.

[0160] exist Figure 6 At six points, SSMF-C can send space sensor measurement responses to SSMF-S. These space sensor measurement responses may include one or more pieces of information received from the space sensors at five points.

[0161] exist Figure 6 At seven points, the SSMF-S can send space sensor measurement responses to the AS. These responses may include space measurements and / or indications regarding whether the space sensor measurement configuration has been successfully applied.

[0162] exist Figure 6 At point 8 in the measurement request, if the QoS of the measurement flow is requested (e.g., required), SSMF-S can call one or more core network (e.g., 5GC) network APIs (e.g., via NEF) to set the QoS of the requested measurement flow.

[0163] exist Figure 6 At 9 locations, if a measurement request is requested (e.g., an event-based or time-based measurement, or a continuous measurement), the space sensor can collect the necessary measurements.

[0164] exist Figure 6 At 10 locations, the space sensor can send the collected measurements to the reporting address provided in the request.

[0165] exist Figure 6During the process, the request at point 1 can identify spatial sensor information that can be stored in or created by a sensing NF in the core network (e.g., 5GC). In this case, the SSMF-S can invoke the NEF API to request spatial sensor information from the core network (e.g., 5GC) and / or the sensing NF. The service call request may include the WTRU identifier obtained at point 1. The sensing NF and / or NEF can respond to the SSMF-S with the spatial sensor information, which can be provided to the AS at point 7.

[0166] SSMF can provide space sensor control session establishment. SSMF can support the process of establishing a control session with a space sensor. This process allows the AS to request or notify the space sensor associated with the WTRU to initiate a control session with the AS. Once the session is established, the AS can remotely control the space sensor, for example, via application-layer messaging. SSMF can also configure traffic flows in the core network (e.g., 5GC) to set the QoS of the control session.

[0167] Figure 7 This is a flowchart illustrating an exemplary process for establishing a space sensor control session. The AS can perform a space sensor discovery process and discover at least one controllable space sensor (e.g., in...). Figure 7 (at position 0 in the text). AS can select one or more space sensors and trigger the establishment of a space sensor control session.

[0168] exist Figure 7 At point 1, the AS can send a Space Sensor Control Session Request to the SSMF-S. This request may include space sensor information, WTRU information, and / or space sensor control session configuration. The configuration may include connectivity information (e.g., DNN, Single Network Slice Selection Aid (S-NSSAI)), control session address (e.g., FQDN, URI, IP, endpoint, etc.), and / or control session QoS requirements. For example, a space map owner might want to deploy and control a space-mapping robot to acquire spatial sensing data in a new environment. The owner can send a request to establish a control session with the robot. This request may include a space-mapping robot identifier, requested sensor capabilities (e.g., range of motion and image capture resolution), and control session QoS parameters (e.g., requirements) (e.g., guaranteed bit rate, packet error rate, etc.), as well as similar information for transmitting sensor data to the space map owner's application.

[0169] The control session address (e.g., FQDN, URI, IP, endpoint, etc.) may already be... Figure 5The QoS requirements are provided to the AS by SSMF-S during the discovery process. The QoS requirements can be a list of requirements (e.g., guaranteed bit rate, packet error rate, and packet delay budget). For example, the QoS requirements can be represented as a QoS reference. The QoS reference can be a value (e.g., an integer value) mapped to a list of one or more parameters (e.g., requirements) (e.g., guaranteed bit rate, packet error rate, packet delay budget, etc.). Both the AS and SSMF-S can be configured to know the mapping between the QoS reference and the list of requirements (e.g., the configuration can be based on a service layer protocol). The AS can be based on... Figure 5 The QoS parameters or requirements are determined by the service requests received from the four locations.

[0170] exist Figure 7 At point 2, SSMF-S can use WTRU information to determine which SSMF-C instance to communicate with. SSMF-S can send a Space Sensor Control Session Request to SSMF-C. The Space Sensor Control Session Request can include any information received from the AS at point 1 (e.g., connectivity information). SSMF-S can update / modify the Space Sensor Control Session configuration based on the information received at point 1 before sending the Space Sensor Control Session configuration to SSMF-C (e.g., in the Space Sensor Control Session Request). For example, SSMF-S can request SSMF-C to enable a subset of available sensors (e.g., subset only), or SSMF-S can decide to skip control session establishment for SSMF-Cs that are not configured or not allowed to establish a control session. For example, if a notification channel exists between SSMF-C and SSMF-S, SSMF-S can send a Space Sensor Control Session Notification to SSMF-C, and the notification can include one or more information elements from the request.

[0171] exist Figure 7 At three points, SSMF-C can use information received from SSMF-S at two points to determine which space sensor requests (e.g., needs) a control session. SSMF-C can send a space sensor control session request to the requesting space sensor. The space sensor control session request can include any information received from SSMF-S at two points. For example, if a space sensor control session notification is received by SSMF-C, SSMF-C can send a space sensor control session notification to the requesting space sensor. The notification includes the same information elements as the request.

[0172] exist Figure 7In four locations, the space sensor can be configured using the space sensor control session configuration obtained from SSMF-C in three locations. For example, the space sensor can use a DNN to establish a connection with the data network where the remote controller resides, and can use QoS parameters (e.g., QoS requirements) to configure bandwidth limitations on the application measurement stream. For example, in Figure 7 The two receivable connection information (e.g., DNN) can be used by SSMF-C to trigger the PDU session establishment process and trigger WTRU to send a PDU session establishment request including the DNN in the request.

[0173] exist Figure 7 At five points, the space sensor can send a space sensor control session response to the SSMF-C. This response can include indications of whether the space sensor control session configuration has been successfully received and applied, and can specify which control operations are permitted. For example, an RGBD camera mounted on a UAV can indicate that the control session has been successfully configured, and / or that the camera supports image capture in a predetermined 3D space at a specific image resolution. The control operations can be application-layer operations performed on the space sensor. The SSMF-C can determine whether to authorize application-layer requests related to the space sensor (e.g., reading data or sending control commands).

[0174] exist Figure 7 At six points, SSMF-C can send a space sensor control session response to SSMF-S. This space sensor control session response can include one or more messages received from the space sensor at five points.

[0175] exist Figure 7At point 7, SSMF-S can send a space sensor control session response to the AS. This response can include an indication of whether the space sensor control session configuration has been successfully received and applied, and can specify which control operations are permitted. The response can include contact information for the space sensor and / or SSMF-C. This contact information can be an IP address or a URI. If configuration fails, the response can include a reason code indicating the reason for the failure. For example, the reason code could indicate that a connection to the space sensor might not be configurable due to network congestion (e.g., network congestion at the location where the space sensor might be located). Alternatively, the reason code could indicate that a connection might not be configurable because different ASs are currently controlling the sensor, and multiple ASs may not be able to control the space sensor simultaneously. Another reason code could indicate that a connection might not be configurable because the AS is not authorized to read data from or control the space sensor (e.g., SSMF-S can be configured with information indicating which application servers are authorized to control the sensor or read data from it). If configuration fails, the response can include the identities of other space sensors that may provide similar information. For example, the space sensor control session response may include the identity of the sensor located near the sensor associated with the configuration request.

[0176] exist Figure 7 In the eight locations mentioned, if the control session request includes session QoS, SSMF-S can call the core network (e.g., 5GC) network API (e.g., via NEF) to set the QoS of the control session request.

[0177] exist Figure 7 At point 9, the space sensor uses the connection information and control session address from the space sensor control session configuration to establish a space sensor control session with the AS. For example, SSMF-C can send a control session establishment request message to the AS. SSMF-C may have already received the AS's address in the connection information at point 2. For example, the AS can use the contact information provided at point 7 to establish a space sensor control session with the space sensor and / or SSMF-C. After establishing the space sensor control session, the AS can then send control messages to the space sensor, such as instructing it to move to a desired location for measurement collection.

[0178] Although the features and elements described above are described in specific combinations, each feature or element may be used alone without other features and elements of the preferred embodiment, or in various combinations with or without other features and elements.

[0179] While the implementations described herein may take into account 3GPP-specific protocols, it should be understood that the implementations described herein are not limited to this scenario and may be applicable to other wireless systems. For example, although the examples described herein take into account LTE, LTE-A, New Radio (NR), or 5G-specific protocols, it should be understood that the examples described herein are not limited to this scenario and may be applicable to other wireless systems.

[0180] The above processes can be implemented in computer programs, software, and / or firmware, which are incorporated in a computer-readable medium for execution by a computer and / or processor. Examples of computer-readable media include, but are not limited to, electronic signals (transmitted via wired and / or wireless connections) and / or computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor storage devices, magnetic media (e.g., but not limited to internal hard disks and removable disks), magneto-optical media, and / or optical media, such as optical disc (CD)-ROM disks and / or digital versatile discs (DVDs). The processor associated with the software can be used to implement a radio frequency transceiver for WTRUs, terminals, base stations, RNCs, and / or any host computer.

Claims

1. A first network node, comprising: The processor is configured as follows: Receive an SM registration request from the Wireless Transmit / Receive Unit (WTRU) to register the WTRU as a Space Mapping (SM) client device; Receive an SM discovery request from a second network node, wherein the SM discovery request indicates one or more SM selection criteria; Based on the SM registration request received from the WTRU and the SM discovery request received from the second network node, it is determined that the WTRU meets one or more SM selection criteria; Send an SM discovery response to the second network node, wherein the SM discovery response includes information about the WTRU; as well as Send a notification about the SM operation to the WTRU.

2. The first network node of claim 1, wherein the SM registration request received from the WTRU indicates one or more of the following: the type of SM information that the WTRU can provide, the location or position of the WTRU, and the availability of the WTRU as the SM client device.

3. The first network node according to claim 2, wherein the type of the SM information indicates whether the SM information was acquired using a color camera, a light detection and ranging (LiDAR) camera, or a high-resolution camera.

4. The first network node of claim 1, wherein the processor is further configured to register the WTRU as the SM client device based on the SM registration request received from the WTRU.

5. The first network node of claim 4, wherein the processor is configured to register the WTRU as the SM client device, comprising: The processor is configured to authenticate the WTRU and store information about the WTRU on the first network node.

6. The first network node of claim 1, wherein the one or more SM selection criteria indicate one or more of the following: the type of SM information requested by the second network node, the SM location or position desired by the second network node, and the region of interest of the second network node.

7. The first network node of claim 1, wherein the SM operation includes SM measurements to be performed by the WTRU or a space sensor associated with the WTRU.

8. The first network node of claim 7, wherein the notification sent to the WTRU includes SM measurement configuration information indicating one or more of the following: the quality of the SM measurement, the frequency of the SM measurement, the area of ​​the SM measurement, the target of the SM measurement, and the reporting address of the SM measurement, and wherein the notification is at least partially triggered by the SM discovery request from the second network node.

9. The first network node of claim 1, wherein the SM operation is associated with establishing a control session between the second network node and the WTRU, or with establishing a control session between the second network node and a space sensor associated with the WTRU.

10. The first network node of claim 9, wherein the processor is configured to send the notification regarding the SM operation to the WTRU in response to receiving a control session establishment request from the second network node, including one or more of the following: WTRU information, space sensor information, and SM control session configuration information.

11. The first network node of claim 10, wherein the control session establishment request received from the second network node further indicates a quality of service (QoS) requirement associated with the control session, and wherein the processor is further configured to indicate the QoS requirement to a communication network device responsible for maintaining the control session.

12. The first network node of claim 9, wherein the processor is further configured to receive from the WTRU a response indicating whether the control session has been successfully established, contact information associated with the control session, or a method for acquiring SM data from the WTRU or the space sensor associated with the WTRU.

13. The first network node of claim 12, wherein the processor is further configured to send a control session establishment response to the second network node, the control session establishment response indicating whether the control session has been successfully established, the contact information associated with the control session, or the method of acquiring SM data from the WTRU or the space sensor associated with the WTRU.

14. The first network node according to claim 1, wherein the first network node is an SM management server and the second network node is an application server.

15. A method implemented by a first network node, the method comprising: Receive an SM registration request from the Wireless Transmit / Receive Unit (WTRU) to register the WTRU as a Space Mapping (SM) client device; Receive an SM discovery request from a second network node, wherein the SM discovery request indicates one or more SM selection criteria; Based on the SM registration request received from the WTRU and the SM discovery request received from the second network node, it is determined that the WTRU meets one or more SM selection criteria; Send an SM discovery response to the second network node, wherein the SM discovery response includes information about the WTRU; as well as Send a notification about the SM operation to the WTRU.

16. The method of claim 15, wherein the SM registration request received from the WTRU indicates one or more of the following: the type of SM information that the WTRU can provide, the location or position of the WTRU, and the availability of the WTRU as the SM client device.

17. The method of claim 16, wherein the type of the SM information indicates whether the SM information was acquired using a color camera, a light detection and ranging (LiDAR) camera, or a high-resolution camera.

18. The method of claim 15, further comprising registering the WTRU as the SM client device based on the SM registration request received from the WTRU, wherein the registration includes authenticating the WTRU and storing information about the WTRU on the first network node.

19. The method of claim 15, wherein the one or more SM selection criteria indicate one or more of the following: the type of SM information requested by the second network node, the SM location or position desired by the second network node, and the region of interest of the second network node.

20. The method of claim 15, wherein the SM operation includes an SM measurement to be performed by the WTRU or a space sensor associated with the WTRU, wherein the notification sent to the WTRU includes SM measurement configuration information indicating one or more of the following: the quality of the SM measurement, the frequency of the SM measurement, the area of ​​the SM measurement, the target of the SM measurement, and the reporting address of the SM measurement, and wherein the notification is triggered at least in part by the SM discovery request from the second network node.

21. The method of claim 20, wherein the SM operation is associated with establishing a control session between the second network node and the WTRU, or with establishing a control session between the second network node and a space sensor associated with the WTRU.

22. The method of claim 21, wherein the notification regarding the SM operation is sent to the WTRU in response to receiving a control session establishment request from the second network node, comprising one or more of the following: WTRU information, space sensor information, and SM control session configuration information.

23. The method of claim 22, wherein the control session establishment request received from the second network node further indicates a quality of service (QoS) requirement associated with the control session, and wherein the processor is further configured to indicate the QoS requirement to a communication network device responsible for maintaining the control session.

24. The method of claim 21, further comprising receiving from the WTRU a response indicating whether the control session has been successfully established, contact information associated with the control session, or a manner in which SM data is acquired from the WTRU or the space sensor associated with the WTRU.

25. The method of claim 24, further comprising sending a control session establishment response to the second network node, wherein the control session establishment response indicates whether the control session has been successfully established, the contact information associated with the control session, or the manner in which SM data is acquired from the WTRU or the space sensor associated with the WTRU.

Images