Resource set coherency and management in a wireless system

Abstract

Disclosed herein are systems, methods, and instrumentalities associated with the management and / or maintenance of coherency of a resource set (e.g., for a metaverse service). A network device (e.g., a resource management function) may receive a message from a wireless transmit / receive unit (WTRU) regarding a first type of information associated with a first service and a second type of information associated with a second service that are interrelated; determine that the information set is to be updated in response to a change to one or more values associated with the first type of information, one or more values associated with the second type of information, or a location of the WTRU; determine an information set update based on at least one of the first service or the second service; and send a message to the WTRU regarding the information set update and an identifier of the information set.

Description

I5GCN_2024P00596WO PATENTRESOURCE SET COHERENCY AND MANAGEMENT IN A WIRELESS SYSTEMCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 683,925, filed August 16, 2024, the contents of which is incorporated by reference herein.BACKGROUND

[0002] A metaverse may be related to virtual technologies such as augmented reality (AR), mixed reality (MR), and / or virtual reality (VR), all of which may be termed as extended reality (XR). A metaverse may include persistent, shared, or perceived set of interactive spaces. A metaverse may evoke new experiences, products and services as the aforementioned virtual technologies (e.g., VR and AR) become commonly available. Metaverse applications may be diverse and may provide new experiences in work, leisure, and other activities. Metaverse services may be defined to foster the adoption of metaverse technologies and / or to provide new mobile user experiences.SUMMARY

[0003] Disclosed herein are systems, methods and instrumentalities associated with the management of a resource set (e.g., for a metaverse service) and / or the maintenance of coherency of the resource set. A network device or entity (e.g., a resource management function or RMF) as described herein may be configured to receive a first message from a wireless transmit / receive unit (WTRU) regarding a first type of information and a second type of information that are interrelated. The first type of information may be associated with a first service. The second type of information may be associated with a second service. The device may send a second message to the WTRU regarding an information set that includes one or more values associated with the first type of information, one or more values associated with the second type of information, and an identifier of the information set. The device may determine that the information set is to be updated in response to a change to the one or more values associated with the first type of information, the one or more values associated with the second type of information, or a location of the WTRU. The device may determine an information set update based on at least one of the first service or the second service. The device may send a third message to the WTRU regarding the information set update and an identifier of the information set.I5GCN_2024P00596WO PATENT

[0004] The first type of information may be a first type of spatial information related to a (e.g., spatial) sensor. The second type of information may be a second type of spatial information related to a spatial map.

[0005] Determining the information set is to be updated in response to the change may involve determining that the one or more values associated with the first type of information have changed; and determining a corresponding change to the one or more values associated with the second type of information.

[0006] At least one of the first service or the second service may be associated with a metaverse. The device may determine the information set update by determining that the information set update maintains a coherency of the information set.

[0007] The device may send a fifth message to the WTRU. The fifth message may indicate a notification to the WTRU regarding a dependency of resources in the information set. The information set update may be associated with a management of the information set. The device may send a fifth message to the WTRU regarding a deletion or disablement of one or more resources in the information set. The information set update may be associated with a mobility of the WTRU.

[0008] The device may receive a request from a wireless transmit / receive unit (WTRU) to create or modify a resource set, wherein the resource set may include information about multiple resources, each of which may include information regarding a service (e.g., a metaverse service). The network device may send a response to the WTRU regarding the creation or the modification of the resource set. The network device may determine that a change has occurred to one or more resources associated with the resource set or to the WTRU and, based on such a determination, may perform one or more operations associated with the resource set.

[0009] In examples, the one or more operations may be associated with maintaining a coherency of the resource set such as, for example, sending a notification to the WTRU regarding a dependency of resources associated with the resource set. In examples, the one or more operations may be associated with a management of the resource set such as, for example, sending a notification to the WTRU regarding deletion or disablement of one or more resources associated with the resource set. In examples, the change described herein may be associated with the mobility (e.g., movement) of the WTRU.BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

[0014] FIG. 2 is a diagram illustrating an example of a distributed mobile metaverse system.

[0015] FIG. 3 is a diagram illustrating an example of a resource set lifecycle.

[0016] FIG. 4 is a diagram illustrating an example of a procedure for managing a resource set.

[0017] FIG. 5 is a diagram illustrating an example of resource set coherency based on associated resource modification.

[0018] FIG. 6 is a diagram illustrating an example of resource set coherency based on WTRU mobility.DETAILED DESCRIPTION

[0019] A more detailed understanding can be had from the following description, given by way of example in conjunction with the accompanying drawings.

[0020] FIG. 1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments can be implemented. The communications system 100 can be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system 100 can enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communications systems 100 can employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tail unique-word DFT-Spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.

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

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

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

[0024] The base stations 114a, 114b can communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an 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.). The air interface 116 can be established using any suitable radio access technology (RAT).

[0025] More specifically, as noted above, the communications 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, and the like. For example, the base station 114a in the RAN 104 / 113 and the WTRUs 102a, 102b, 102c can implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which can establish the air interface 115 / 116 / 117 using wideband CDMA (WCDMA). 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 an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c can implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which can establish the air interface 116 using Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) and / or LTE-Advanced Pro (LTE-A Pro).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0053] In representative embodiments, the other network 112 can be a WLAN.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0067] The AMF 182a, 182b can be connected to one or more of the base stations 180a, 180b, 180c in the RAN 113 via an N2 interface and can serve as a control node. For example, the AMF 182a, 182b can be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like. Network slicing can be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c. For example, different network slices 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, services for machine type communication (MTC) access, and / or the like. The AMF 162 can provide aI5GCN_2024P00596WO PATENT control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi.

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

[0069] The UPF 184a, 184b can be connected to one or more of the base stations 180a, 180b, 180c in the RAN 113 via an N3 interface, which can provide the WTRUs 102a, 102b, 102c with access to packet- switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b 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, providing mobility anchoring, and the like.

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

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

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

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

[0074] Disclosed herein are systems, methods and instrumentalities associated with the management of a resource set (e.g., for a metaverse service) and / or the maintenance of coherency of the resource set. A network device or entity (e.g., a resource management function or RMF) as described herein may be configured to receive a first message from a wireless transmit / receive unit (WTRU) regarding a first type of information and a second type of information that are interrelated. The first type of information may be associated with a first service. The second type of information may be associated with a second service. The device may send a second message to the WTRU regarding an information set that includes one or more values associated with the first type of information, one or more values associated with the second type of information, and an identifier of the information set. The device may determine that the information set is to be updated in response to a change to the one or more values associated with the first type of information, the one or more values associated with the second type of information, or a location of the WTRU. The device may determine an information set update based on at least one of the first service or the second service. The device may send a third message to the WTRU regarding the information set update and an identifier of the information set.

[0075] The first type of information may be a first type of spatial information related to a spatial sensor. The second type of information may be a second type of spatial information related to a spatial map.I5GCN_2024P00596WO PATENT

[0076] Determining the information set is to be updated in response to the change may involve determining that the one or more values associated with the first type of information have changed; and determining a corresponding change to the one or more values associated with the second type of information.

[0077] At least one of the first service or the second service may be associated with a metaverse. The device may determine the information set update by determining the information set update maintains a coherency of the information set.

[0078] The device may send a fifth message to the WTRU. The fifth message may indicate a notification to the WTRU regarding a dependency of resources in the information set. The information set update may be associated with a management of the information set. The device may send a fifth message to the WTRU regarding a deletion or disablement of one or more resources in the information set. The information set update may be associated with a mobility of the WTRU.

[0079] A wireless communication system as described herein may be configured to use resource sets, and some of the examples described herein may be related to resource set management and / or resource set coherency from the perspective of a resource management function (RMF) (e.g., implemented on a network entity or network device such as a core network entity or device).

[0080] The RMF may receive a request message from a WTRU to create a resource set. The request message may include a WTRU identifier and / or information about an area of interest and / or resources of interest. The request message may include other parameters as defined later in this disclosure. The RMF may request and / or subscribe to resource information associated with one or more services based on information included in the request message. The term WTRU may be used interchangeably with the term user equipment (UE) in this disclosure.

[0081] The RMF may subscribe to WTRU location information (e.g., including WTRU location prediction) that may be provided by a network exposure function (NEF) or a service enabler architecture layer (SEAL) location management (LM) service (e.g., based on a WTRU identifier). The RMF may start a resource set refresh period (RsRP) (e.g., by starting an RsRP timer) for mitigating resource set incoherency. The RMF may create a resource set with a unique resource set identifier (RsID). The resource set may be created based on information received in the request message described herein, and / or based on information obtained from one or more services.

[0082] The RMF may send a response message to the WTRU. The response message may include a resource set identifier and / or resource information obtained via the operations described above.I5GCN_2024P00596WO PATENT

[0083] The RMF may detect a resource information change, a WTRU location change and / or a predicted WTRU location change. The detection of the resource information change may be triggered by a notification message received by the RMF, for example, as a result of subscribing to a service via the operations described above. The detection of the WTRU location change may also be triggered by a notification message received by the RMF, for example, as a result of subscribing to a core network or a SEAL LM service via the operations described above. The detection of the resource information change, the WTRU location change and / or the predicted WTRU location change may trigger the RMF to determine affected resources associated with the resource set, to determine inter-dependent resources associated with the resource set, to update determined resources information, to increment a resource set revision (RsRev) value, and / or to send a notification message to the WTRU.

[0084] The RMF may detect an incoherency and / or a maintenance refresh. The detection of the incoherency may be triggered by a request message received by the RMF, and / or by detecting a difference between the RsRev value in a request and the RsRev value in an RMF resource set. The detection of a maintenance refresh may be triggered by the expiration of the RsRP time period (e.g., the RsRP timer) described above. The detection of the incoherency and / or the maintenance refresh may trigger the RMF to request a resource information update from different services and / or to send a notification message to a WTRU.

[0085] The RMF may send a notification message to a WTRU. The notification message may include a resource set identifier and / or updated resource information as described herein.

[0086] When referred to herein, a metaverse may be related to virtual technologies such as AR, MR, and / or VR, all of which may be termed as extended reality (XR). The metaverse may include a persistent, shared, and / or perceived set of interactive spaces. The metaverse may evoke possible new experiences, products and services as VR and / or AR becomes commonly available. Metaverse applications may be diverse and may provide new experiences in work, leisure, and other activities. Metaverse services may be defined to foster the adoption of metaverse technologies and / or to provide new mobile user experiences.

[0087] When referred to herein, localized user experiences may refer to experiences in a user’s local environment. To enable such localized user experiences, metaverse media (e.g., such as virtual information) provided to a given user may be adapted and / or integrated with the local physical world surrounding the user.I5GCN_2024P00596WO PATENT

[0088] When referred to herein, a localized mobile metaverse service may be associated with specific places (e.g., 3D locations in the physical world). The association between a physical place and service (e.g., a service associated with the physical place) may be referred to herein as a localized spatial anchor.

[0089] A localized mobile metaverse service may allow third parties to provision localized spatial anchors via a service offered by a mobile network. The localized mobile metaverse may allow mobile network users to discover the provisioned localized spatial anchors, for example, for the purpose of displaying media associated with the localized spatial anchors.

[0090] A spatial mapping service may provide digital three-dimensional (3D) spatial representations of the physical world to one or more applications. The spatial mapping service may create the 3D spatial representations based on sensor information (e.g., information from a spatial sensor), for example. A spatial sensor may be a type of sensor that may sense and report spatial information.

[0091] In examples, a 3D spatial representation may be used by an application to position and / or overlay virtual content over reality (e.g., a view of the physical world) so as to provide an XR experience to a user. In examples, a 3D spatial representation may be used by an application in the context of autonomous driving, unmanned aerial systems, or various other automation scenarios to assist with the execution of a specific task that may be based on the 3D awareness of a physical environment.

[0092] A localization service may provide localization information about physical users, WTRUs, and / or objects within a 3D spatial representation. A localization service may help position virtual media (e.g., virtual users and / or objects) within a 3D spatial representation.

[0093] In examples, an application may offload (e.g., to a localization service) localization tasks associated with physical users, WTRUs, and objects. In examples, an application may offload (e.g., to a localization service) tasks associated with the positioning of virtual media within a 3D spatial representation.

[0094] Metaverse services may be provided in a mobile network based on resource information that may be maintained by different entities (e.g., different services). For example, spatial anchors may be maintained by a localized spatial anchor service, spatial maps may be maintained by a spatial mapping service, sensor information may be maintained by a sensing service or via a 3rd party application, WTRU location may be provided by a mobile core network and / or a SEAL LM service, etc.

[0095] Combining and using resource information that may be maintained by different entities (e.g., different services) may pose coherency challenges. For example, when different functional entities (e.g., WTRUs and / or network services) obtain and use resource information maintained by different services, theI5GCN_2024P00596WO PATENT resource information may become desynchronized between the different functional entities. For example, resource information known by the different functional entities may be different or incoherent for a period of time. If the different functional entities use desynchronized resource information in computational tasks, incoherent results may be obtained by the different functional entities, which may make their interoperability unreliable. Examples of using desynchronized resource information may include a scenario where a first entity may possess or use a first copy of resource information, a second entity may possess or use a second copy of resource information, and the first and second copies may be different even though they are supposed to be the same. To solve this problem, coherency and / or synchronization of resource information across distributed (e.g., different) functional entities may be enforced or enabled.

[0096] A first type of information and a second type of information (e.g., resource information) maintained by different services (e.g., a first service and a second service) may be interrelated. A first type of resource information may be independent of other resource information, in which case, the resource information may change without impacting other resource information (e.g., the resource information may be independent). For example, spatial anchor related resource information maintained at a spatial anchor service may be independent of location related resource information maintained by a core network or a SEAL LM service. A second type of resource information may be dependent on other resource information, in which case, some resource information may have impacts on other resource information. For example, the first type of information may be a first type of spatial information related to a spatial sensor and the second type of information may be a second type of spatial information related to a spatial map. For example, sensor related resource information used to maintain a spatial map may indicate the presence of a WTRU / user, and may be dependent on resource information indicating the location of another WTRU (e.g., the latter resource information may be maintained by a core network or a SEAL LM service).Dependent resource information may be identified, and the coherency and / or synchronization of dependent resource information may be maintained. More generally, coherency in a distributed mobile metaverse system that may use resource information may be maintained.

[0097] As described herein, a distributed mobile metaverse system may use information maintained by different functional entities. FIG. 2 illustrates an example deployment of a distributed mobile metaverse system. It should be noted that the services depicted in FIG. 2 and described herein may be deployed as network functions within a mobile network, or they may be deployed as application functions interacting with the mobile network.I5GCN_2024P00596WO PATENT

[0098] The integrated sensing service shown in FIG. 2 may provide sensor information. For example, the sensor information associated with an area of interest may be consumed by a spatial mapping service (e.g., for creating and / or maintaining spatial maps).

[0099] The SEAL LM service shown in FIG. 2 may provide WTRU location information. For example, such WTRU location information may be consumed by a spatial mapping service to discover WTRU(s) in a location of interest and / or to position the WTRU(s) within a spatial map. Even though not shown in FIG. 2, a core network may provide WTRU location information through a network exposure function (NEF).

[0100] The spatial anchor service shown in FIG. 2 may provide spatial anchor information. For example, the spatial anchor information may be consumed by a spatial mapping service (e.g., for discovering spatial anchors in a location of interest and / or for positioning the spatial anchors within a spatial map).

[0101] The spatial mapping service shown in FIG. 2 may provide spatial maps and may include additional information such as WTRU information or spatial anchor information. For example, the spatial map and additional information may be obtained by one or more WTRU(s) and may be provided to applications residing on the WTRU(s). For example, an application residing on a WTRU may be an XR application and may use the spatial map information for rendering of virtual data. The application may use the spatial anchor information to obtain and position virtual content in the XR environment. The application may use the WTRU information to identify other WTRUs or users in the XR environment.

[0102] A resource management function (RMF) may be implemented and / or used to preserve coherent resource information across functional entities of a distributed mobile metaverse system. One or more resource sets may be configured and / or used to identify, manage, and / or coordinate distributed resource information.

[0103] When referred to herein, resource information may include information or data associated with (e.g., maintained by) a service. For example, resource information maintained by a service may include information about a WTRU (e.g., such as the location of the WTRU), information about a spatial anchor, etc. The resource information may be accessed via an API provided by a service. The type of resource information maintained by a service may vary depending on the service type. Resource information maintained by different services may be dependent (e.g., interrelated) or independent (e.g., unrelated). When referred to herein, a resource set may include information about one or more (e.g., multiple) resources (e.g., locations, spatial maps, spatial anchors, etc., which may be maintained by different services). The one or more resources may be grouped together (e.g., via the resource set) to ensure coherency and / or synchronization between the resource information. The resources may be groupedI5GCN_2024P00596WO PATENT together (e.g., into the resource set) based on application requirements (e.g., which resource information may be needed by an application).

[0104] When referred to herein, resource information coherency may include a state that may be determined based on the coherency of a set of resources information (e.g., a resource set). A coherent resource set state may be state in which information provided by a resource set may be up to date and representing the same reality. An incoherent resource set state may be a state in which information provided by a resource set may be partially outdated and not representing the same reality. For example, assuming a spatial map of a room (e.g., an area of interest) with a single WTRU in the room, a resource set may be considered coherent if both the sensor resource information and WTRU location resource information indicate the presence of the WTRU in the area of interest. Conversely, the resource set may be considered incoherent if the sensor resource information indicates the presence of the WTRU, but the WTRU location resource information indicates that no WTRU is present in the area of interest.

[0105] An RMF may allow for the creation, configuration and management of resource sets. The resource information included in a resource set may be distributed and maintained across different functional entities (e.g., services), and the RMF may maintain coherency between the distributed resource information.

[0106] The RMF may offer a resource set management service. The service may be offered to a resource set consumer via an application programming interface (API). The RMF may be implemented as a standalone application function (AF) or as a network function (NF). The RMF’s functionality may be combined with an existing AF or NF, and the API may be offered as an extension of an existing API.

[0107] The RMF service may be offered via a communication protocol including, for example, the hypertext transfer protocol (HTTP) or a non-access stratum (NAS) protocol.

[0108] The RMF may create and / or manage resource sets. The RMF may store information related to a managed resource set and / or information about the resource information comprised in a resource set. The RMF may perform processing related to the management of resource sets and / or the maintenance of coherency between resource sets or the resource information of a resource set. The RMF may enable concurrent management of resource sets and may offer resource management services to multiple (e.g., concurrent) resource set consumers.

[0109] FIG. 3 illustrates an example lifecycle of a resource set. The resource set consumer shown in FIG. 3 may be a WTRU, an NF or an AF. The lifecycle of the resource set for the consumer may include one or more of the following phases.I5GCN_2024P00596WO PATENT

[0110] In a first phase, the resource set consumer may request an RMF to create an instance of a resource set, and the RMF may create the resource set based on information provided by the resource set consumer, or based on information available in a network. The resource set instance may include information that may uniquely identify the resource set instance. The resource set instance may include information describing an area of interest and / or a location associated with the resource set. The resource set instance may include information about the resource information associated with the resource set.

[0111] In a second phase, the resource set consumer may request the RMF to perform management operations on the resource set, and the RMF may provide the resource set consumer with resource set information that may result from the management operations. The resource set management operations may include configuring, enabling, disabling, and / or modifying the resource set. The information resulting from the resource set management operations may be sent (e.g., as a response or notification) to the resource set consumer. The information may include updated resource set information.

[0112] The operations of the RMF may be triggered (e.g., via a request sent to the RMF) by services that maintain the resource information included in the resource set, by the resource set consumer, or by a network (e.g., a core network device). The operations may be related to maintaining the coherency of a resource set.

[0113] In a third phase, the resource set consumer may request the RMF to delete the resource set instance, and the RMF may, in response, delete resource information associated with the resource set instance. In examples, the resource set instance may have an expiration time (e.g., be scheduled to expire after a time period subsequent to the instance’s creation), and the RMF may delete the resource set instance at the expiration time. The RMF may notify the resource set consumer about the deletion of the resource set instance.

[0114] When referred to herein, a resource set instance may include information that associates multiple pieces of resource information with each other. The associated resource information may be managed by different functional entities. A resource set instance may include policy information, which may describe spatial conditions (e.g., area of interest, location, orientation, viewport, etc.) for using the resource set instance, or validity conditions for the resource set instance (e.g., based on time, duration, WTRU context, etc.).

[0115] Information elements (lEs) may be used to describe a resource set instance. For example, a resource set identifier (RsID) may be used to identify the resource set instance. The RsID may be assigned by an RMF when the resource set instance is created. The RsID may be an identifier derived from resourceI5GCN_2024P00596WO PATENT information associated with the resource set. The RsID may be sent from a resource set consumer to the RMF (e.g., when requesting management operations from the RMF on the resource set instance). The RsID may be sent from the RMF to the resource set consumer (e.g., when notifying the consumer about a resource set instance change).

[0116] A resource set type (RsT) IE may be used to identify the type of a resource set. The RsT may indicate what resource information is included in the resource set. The RsT may indicate pre-determined resource information associated with the resource set such as, for example, information about the service(s) (e.g., at a URL, URI, or IP address) that maintain or manage the resource information associated with the resource set.

[0117] A resource set area of interest (RsAol) IE may be used to identify an area of interest for a resource set. The RsAol may indicate an area and / or a location to which the resource set may apply (e.g., the area or location may be a pre-determined area of interest or location that may be used when discovering resource information of the resource set).

[0118] A resource set resource of interest (RsRol) IE may be used to identify resource information of interest to be included in a resource set. The RsRol may indicate the types and characteristics of the resource information to be included in the resource set. These characteristics may include, for example, filters used by the RMF when discovering the resource information to be included in the resource set. The RsRol may indicate a resource information type, a service (e.g., at a URL, URI, or IP address) where resource information may be managed, and / or a resource information filter for discovering resource information.

[0119] A resource set resource list (RsRL) IE may include a list of resource information (e.g., Rlnfo) instances that may be included in a resource set. The RsRL may be managed by an RMF. The RsRL may include Rlnfo instances about each resource information included in the resource set. The RsRL may be a single list of all resource information maintained by the RMF, or may include multiple lists (e.g., one per resource information type).

[0120] A resource information (Rlnfo) IE may include resource information. The Rlnfo may be included in the RsRL of a resource set. The Rlnfo may include resource metadata and / or resource raw data. The resource metadata may indicate a resource information type, a service (e.g., at a URL, URI, IP address) where resource information may be managed, a subscription identifier for receiving resource information updates from a service, connectivity information to access a service, a timestamp indicating when a resource information was last refreshed, an indication (e.g., a policy) indicating that certain resourceI5GCN_2024P00596WO PATENT information may be dependent or interrelated with other resource information. The resource raw data may include information associated with resource information. For example, if the resource information type is a spatial anchor, the raw data may include information about the spatial anchor (e.g., spatial coordinates and / or associated services). If the resource information type is a WTRU location, the raw data may include information about the WTRU location (e.g., WTRU identifier and / or location).

[0121] A resource set policy (RsP) IE may indicate resource information dependencies within a resource set and / or may provide a set of rules for maintaining resource set coherency. For example, the RsP may indicate that certain resource information may be dependent or interrelated with other resource information. The RsP may provide rules for determining when interrelated resource information may no longer be coherent and / or may request (e.g., require) an update. The RsP rules may include triggers for detecting incoherent resource information and / or corresponding actions for re-establishing resource set coherency. Triggers for the RsP rules may include WTRU mobility, resource information update notifications, resource information timestamp differences (e.g., maximum timestamp difference between different copies or versions of resource information), etc. Actions corresponding to the RsP rules may include updating dependent resource information, adding resource information to a resource set, removing resource information from a resource set, notifying related services about a resource set change, etc. The RsP may include spatial and / or validity conditions for a resource set and / or resource set access permissions. The RSP may indicate conditions that may be used to determine whether first resource information is independent or dependent of second resource information.

[0122] A resource set revision (RsRev) IE may be used to identify a version of a resource set. For example, an RMF may maintain an iteration counter, a timestamp and / or a checksum based on the resource information of the resource set to indicate a revision of the resource set. The RsRev may be used by a resource set consumer to identify the revision of the resource set used and to perform an operation on the resource set. For example, a WTRU requesting localization information from the localization service may indicate the RsRev that may be used by a localization service.

[0123] A resource set consumer identifier (RsCID) IE may be used to indicate the identity of a resource set consumer. In examples, the RsCID may be static and may represent the consumers allowed to use a resource set instance. In examples, the RsCID may be a dynamic list of consumers that may have been provided with resource set instance information. The RsCID may be used to control access to a resource set or to track the existing users of a resource set.

[0124] One or more resource set consumers may use a resource set. For example, different WTRUs may use the resource set. In this case, a WTRU or resource set consumer that may request to create,I5GCN_2024P00596WO PATENT update or delete a resource set may be differentiated from a WTRU or resource set consumer that may only use resource information and / or provide information to an RMF.

[0125] A resource set notification (RsNotif) IE may indicate a notification endpoint for a resource set consumer. The RsNotif may be provided by the consumer and stored by an RMF. The RMF may use the RsNotif to notify the resource set consumer of resource set updates.

[0126] A resource set may serve one or more areas of interest (RsAol). For each area of interest, there may be an associated resource set policy RsP that may provide different policies and / or resource information related treatments for the area of interest.

[0127] A resource set refresh period (RsRP) IE may indicate a time period for refreshing a resource set. The RsRP may be provided by a resource set consumer or determined by an RMF (e.g., based on configuration, policy, or application requirements). The RMF may use the RsRP to refresh the resource information included in the resource set and / or to notify the resource set consumer (e.g., on a periodic basis). The RsRP may be used to mitigate the resource set that may become incoherent with the resource information managed by other services, or to mitigate the resource set consumer that may be becoming incoherent with the resource set at the RMF. For example, if the resource set consumer cannot receive a notification due to a connectivity issue, a refresh triggered by the RsRP may prevent incoherency for the consumer.

[0128] FIG. 4 illustrates an example procedure for managing a resource set. At 1 , a WTRU (e.g., as a resource set consumer) may request the creation of a resource set with an RMF. For example, the WTRU may send a resource set GET request to the RMF. The request may include a WTRU identifier (e.g., a GPSI), a WTRU location, an area of interest, information about the resource information to be included in the resource set, and / or an RsP (e.g., which may indicate resource information dependencies, rules for maintaining resource information coherency, and / or resource set validity and access conditions). The request may indicate that the resource set may include spatial anchor resource information and / or WTRU location resource information. The request may indicate that the spatial anchor and / or the WTRU may be in the provided area of interest. The request may indicate supplemental filtering information such as, for example, the identifiers of specific spatial anchors and / or WTRUs. The request may include an RsID to indicate that an existing (e.g., already created) resource set may be requested.

[0129] At 2, the RMF may (e.g., upon receiving the request sent at 1) determine to create a new resource set or to identify an existing resource set based on the presence of an RsID in the request. If the RsID is present in the request, the RMF may identify an existing resource set with a matching RsID andI5GCN_2024P00596WO PATENT may proceed to 3, wherein the RMF may indicate a successful acceptance of the request and may provide the identified resource set information in a resource set GET response. The RMF may perform access control checks to validate if the WTRU is allowed to request the specific RsID. The access control check may be based on an RsCID present in resource set or based on access permissions indicated by the RsP. The RMF may return a failure at 3 if the WTRU is not allowed to request the specific RsID.

[0130] If an RsID is not present in the request, the RMF may create a resource set. The RMF may assign a RsID and / or an RsRev to the created resource set and may store information included in the request (e.g., at 2a). If the request includes an RsT, the RMF may use the RsT to identify pre-configured resource information to be included in the resource set; otherwise, the RMF may identify the requested resource information based on an RsRol and / or an RsAol.

[0131] Upon successfully identifying an existing resource set or creating a new resource set, the RMF may add the WTRU (e.g., the requestor) as a subscriber to receive resource set updates. A subscription identifier may be assigned by the RMF to identify the subscription. The RsID and / or the RsCID may be part of the identifier. RsNotif information may be provided in the request.

[0132] The subscription identifier may be changed or updated after a period of time or when certain events take place. For example, when a consumer is no longer part of a subscription, or when a new consumer starts to use a resource set, the RMF may update the subscription identifier and may notify the relevant subscribers about the subscription identifier change. The refreshment of the subscription identifier may trigger the verification of access permissions. For example, the RMF may add or remove a consumer to or from a list of authorized consumers (e.g., identified by RsCIDs).

[0133] The RMF may send a message at 2b and / or 2c regarding an information set that includes one or more values associated with the first type of information, one or more values associated with the second type of information, and an identifier of the information set (e.g., to get one or more identified resource information and / or to subscribe to updates of the identified resource information). Different messages may be sent to different services depending on the identified resource information. The messages may include filters (e.g., based on an RsRol and / or an RsAol) for obtaining a resource information of interest. Upon receiving information about the identified resource information, the RMF may store the retrieved resource information (e.g., Rlnfo) on a list (e.g., RsRL).

[0134] At 3 of FIG. 4, the RMF may send a message to the WTRU. The message may include an RsID and the requested resource information. The WTRU may provide the requested resource information to an application client present on the WTRU, and that application client may use the provided resourceI5GCN_2024P00596WO PATENT information to perform application layer operations. For example, the application client may be an augmented reality application and may use a spatial map and / or spatial anchor resource information included in the requested resource set to render virtual contents to a user. For example, the application client may be an unmanned aerial vehicle performing infrastructure inspection and may use spatial map and WTRU location resource information included in the requested resource set to perform localization of the infrastructure and / or other unmanned aerial vehicles.

[0135] At 4 of FIG. 4, the WTRU (e.g., as a resource set consumer) may request to update a resource set with the RMF. The WTRU may send a resource set update request to the RMF. The request may include a WTRU identifier (e.g., GPSI), a resource set identifier, and / or updated resource set information. For example, updated resource set information may indicate an updated WTRU location, an updated area of interest, and / or updated information about the resource information to be included in the resource set.

[0136] At 5 of FIG. 4, the RMF may validate if the WTRU is authorized to update the resource set and may reject the request at 6 if the WTRU is not authorized or if the RsID is not found. If the WTRU is authorized, the RMF may update the resource set with the information provided in the request. The RMF may, at 5a and / or 5b, create new subscriptions or update / delete existing subscriptions based on the provided updates. The RMF may get updated resource information from services included in the resource set to reflect the updated information. The RMF may, at 5c, store the updated resource information.

[0137] At 6 of FIG. 4, the RMF may send a resource set update response to the WTRU. The response may include the resource set identifier and / or updated resource information. If other WTRUs or resource set consumers are using the resource set, the RMF may concurrently send a resource set update message to the other WTRUs or consumers.

[0138] At 7 of FIG. 4, the WTRU (e.g., as a resource set consumer) may request to delete a resource set with the RMF. The request may include the WTRU identifier and the resource set identifier.

[0139] At 8 of FIG. 4, the RMF may verify that the WTRU is authorized to delete the resource set. If the WTRU is authorized, the RMF may determine if the resource set may be deleted. For example, the resource set may be deleted if there is no other consumer of the resource set (e.g., the other consumers of the resource set may be determined based on an RsCID). If the RMF determines that the resource set may be deleted, the RMF may, at 8b and / or 8c, unsubscribe from the services associated with the resource information included in the resource set.

[0140] A resource set instance may be scheduled to expire at a pre-determined time. When a resource set expires, the RMF may be triggered (e.g., by an expiration timer) to remove information related to theI5GCN_2024P00596WO PATENT resource set and / or to notify the consumers of the resource set about the expiry. The RMF may disable (e.g., temporarily) the resource set. In examples, the disabled resource set may not be available and the RMF may not notify consumers of the disabled resource set until it is enabled again. The RMF may preserve information associated with the disabled set instance.

[0141] At 9 of FIG. 4, the RMF may send a response message to the WTRU indicating that a resource set has been deleted. If other WTRUs or resource set consumers are using the resource set, the RMF may send a resource set delete notification (e.g., a message) to the other WTRUs or consumers (e.g., at the same time).

[0142] FIG. 5 illustrates an example procedure for preserving resource set coherency (e.g., when resource information included in the resource set is modified).

[0143] At 1 of FIG. 5, a resource information included in a resource set may be modified. The resource information modification may be triggered by a resource owner. For example, if the resource information is a spatial anchor, a spatial anchor may be added in an area of interest of the resource set. The modification may be triggered by a location change. For example, if the resource information is a WTRU location, the WTRU may move away from an area of interest. The modification may be triggered by an environmental change. For example, if the resource information is a spatial map, sensing may indicate that objects present in an area of interest may have moved and that the spatial map may need to be updated.

[0144] At 2 of FIG. 5, the network may determine that the information set is to be updated in response to a change to the one or more values associated with the first type of information, the one or more values associated with the second type of information, or a location of the WTRU. For example, the network may determine (e.g., from the first service) that the one or more values associated with the first type of information have changed and / or determine (e.g., from the second service) a corresponding change to the one or more values associated with the second type of information. For example a service (e.g., service-1) associated with the modified resource may detect the resource information change and may notify the RMF about the change. The notification may include information about the modified resource information.

[0145] At 3 of FIG. 5, the network may determine, from at least one of the first service or the second service, an information set updated based on (e.g., the RMF may determine that the modified resource information indicated in the notification may be associated with a resource set). The information set updated may be an updated needed for the information set. The RMF may, at 3a, use resource set information (e.g., RsP, RsRL, Rlnfo, etc.) to determine if the updated resource information is dependent on or interrelated with another resource information. The RMF may use the RsP to identify dependentI5GCN_2024P00596WO PATENT resource information and / or to determine whether the resource information is no longer coherent and / or synchronized. The RMF may determine that certain triggering criteria may have been met and / or that an action may be performed to re-establish resource information coherency. For example, the RMF may determine that the timestamps on dependent resource information exceed a maximum timestamp difference and / or that the RMF should request an update of the dependent resource information to reestablish resource information coherency. The RMF may, at 3b, request updates from other resource information of the resource set. The RMF may include the update information received at 2 in the request update (e.g., performed at 3b) associated with the dependent or interrelated resource information. The RMF may, at 3c, receive a resource information update response from the dependent or interrelated resource information. The RMF may, at 3d, update the resource set to reflect the updated information. The RMF may store the updated resource information.

[0146] At 4 of FIG. 5, the network may send a message to the WTRU regarding the update to the information set (e.g., the information set update) and an identifier of the information set (e.g., the RMF may send a resource set update response to the WTRU). The response may include the resource set identifier and / or updated resource information.

[0147] In examples, the expiration of the RsRP timer described herein may trigger the RMF to perform a resource set update (e.g., as described with reference to 3 and 4 of FIG. 5).

[0148] FIG. 6 illustrates an example procedure for preserving resource set coherency (e.g., when a WTRU mobility event occurs).

[0149] At 1 of FIG. 6, a WTRU may move. The WTRU movement may or may not trigger a mobility event (e.g., a change in the WTRU connectivity with a network) and / or a WTRU location change (e.g., a change in the WTRU location detected by the network).

[0150] At 2 of FIG. 6, the WTRU may send a resource set update request as described herein. The request may include an updated area of interest and / or a WTRU location based on the WTRU movement.

[0151] At 3 of FIG. 6 (e.g., instead of or concurrent with the operations at 2), a core network may (e.g., at 3a) notify an RMF about the WTRU mobility event. The RMF may have subscribed (e.g., via an NEF API) with the core network for WTRU mobility events or WTRU location change events. For example, the RMF may have subscribed to the core network notification when the WTRU created the resource set. The RMF may have subscribed to the core network notification based on resource set information received during resource set creation. An RsP rule may indicate WTRU mobility as a trigger for actions to maintain resource information coherency, in which case, the RMF may subscribe to the core network to receiveI5GCN_2024P00596WO PATENTWTRU mobility notifications for the indicated WTRU. The RMF may, at 3b, identify the resource set associated with the WTRU (e.g., by correlating WTRU information included in the notification with the RsCID of the resource set).

[0152] At 4 of FIG. 6, the RMF may determine a change (e.g., in an area of interest) caused by the WTRU movement.

[0153] If the WTRU sent a resource set update request at 2, the RMF may, at 4a, obtain information regarding an updated area of interest from the WTRU based on the request. The RMF may, at 4b, obtain information regarding an area of interest from the WTRU, for example, by sending an area of interest update notification to the WTRU. Upon receiving the notification, the WTRU may respond to the RMF with the updated area of interest.

[0154] The RMF may, at 4c, predict an area of interest of the WTRU, for example, by sending a request to a Network Data Analytics Function (NWDAF) via an NEF API. The NWDAF may predict the WTRU area of interest based on the WTRU location predicted by the NWDAF.

[0155] At 5 of FIG. 6, the RMF may update resource set information based on the updated area of interest. The RMF may, at 5a and / or 5b, update an existing subscription based on the provided update. The RMF may get updated resource information from services included in the resource set (e.g., to reflect the updated information). The RMF may, at 5c, store the updated resource information.

[0156] At 6 of FIG. 6, the RMF may send a resource set update response to the WTRU. The response may include a resource set identifier and / or updated resource information.

[0157] Resource information stored by the RMF may indicate a spatial map resource (e.g., the spatial map resource information may include information about the spatial map). The RMF may receive a request to create the spatial map resource information from an application server. The RMF may receive an RsP rule from the application server. The RsP rule may be associated with the spatial map resource information. The RsP rule may be part of the spatial map resource information.

[0158] As shown at 3a of FIG. 6, the RMF may receive a notification from a core network node (e.g., an NEF). The notification may indicate location information, orientation information, and / or trajectory information for a WTRU. The location information may indicate geographical coordinates, a cell identity, and / or a tracking area identity. The orientation information may include information about the position and / or pose of the WTRU, which may indicate, for example, the direction which a camera may be facing. The trajectory information may include the speed of the WTRU, the rate of acceleration of the WTRU,I5GCN_2024P00596WO PATENT and / or an anticipated path that the WTRU may be following. The anticipated path may be a location to which the WTRU is anticipated to move.

[0159] As shown at 3b of FIG. 6, the RMF may use the information included in the notification from the core network and / or the RsP rule to determine if first resource information and second resource information may no longer be dependent (e.g., have become independent). The RMF may use the information in the notification from the core network and / or the RsP rule to determine if first resource information and second resource information may no longer be independent (e.g., have become dependent).

[0160] In examples, the RsP rule may identify spatial map resource information. The RsP rule may indicate that the spatial map resource information may be dependent on another type of resource information (e.g., the spatial map resource information may be associated with location resource information). For example, the spatial map resource information may be associated with a certain geographical location and the RsP rule may indicate that the spatial map resource information may be dependent on resource information that holds temperature information if that resource information is associated with the same location as the spatial map resource information.

[0161] Resource information that holds sensor information (e.g., pose information) may be associated with a WTRU. Such resource information may be stored in an enabler client hosted in the WTRU. The notification from the core network at 3a of FIG. 6 may indicate that the location information, orientation information, and / or trajectory information of the WTRU may have changed. The RMF may compare the new location information, orientation information, and / or trajectory information with the information from an RsP rule associated with spatial map resource information.

[0162] The RMF may determine that the location information of the WTRU overlaps with the location information in the RsP rule. In response, the RMF may determine that the spatial map resource information may be dependent on the sensor information resource information (e.g., because the sensor resource information is associated with the WTRU).

[0163] The RMF may determine that the location information of the WTRU does not overlap with the location information in the RsP rule. In response, the RMF may determine that the spatial map resource information may be independent of the sensor resource information (e.g., because the sensor resource information is associated with the WTRU).

[0164] The RMF may determine that the trajectory information of the WTRU indicates that the location of the WTRU may (e.g., soon) overlap with the location information in the RsP rule. In response, the RMFI5GCN_2024P00596WO PATENT may determine that the spatial map resource information may be dependent on the sensor resource information (e.g., because the sensor resource information is associated with the WTRU).

[0165] The RMF may detect that the trajectory information of the WTRU indicates that the location of the WTRU may (e.g., soon) cease to overlap with the location information in the RsP rule. In response, the RMF may determine that the spatial map resource information may be independent of the sensor resource information (e.g., because the sensor resource information is associated with the WTRU).

[0166] If the RMF detects that spatial map resource information is dependent on sensor information, theRMF may send a subscribe message to an enabler client in the WTRU that may store the sensor information. The RMF may receive the most update-to-date sensor information from the WTRU and may keep a coherent copy of the information associated with the spatial map.

[0167] If the RMF detects that spatial map resource information is independent of sensor information, the RMF may send an unsubscribe message to an enabler client in the WTRU that may store the sensor information. As a result, the WTRU may cease sending the sensor information to the RMF

[0168] If new resource information becomes available in the area of interest of a resource set, the RMF may determine to revise the dependency information of potentially impacted resource set(s). For example, if new resource information becomes available, the RMF may determine that the new resource information may be associated with (e.g., dependent on) an existing resource set and may update the resource set information (e.g., a resource set policy) to indicate the dependency. If existing resource information becomes unavailable (e.g., due to an outage or maintenance), the RMF may determine that the dependency between such resource information and other resource information (e.g., such as information about a spatial anchor) may no longer be maintained. The RMF may update the relevant dependency information to indicate that the spatial anchor resource information has become independent.

[0169] The dependency between the resource information of a resource set may be unidirectional. For example, first resource information of a resource set may depend on second resource information of the resource set, and the second resource information may not be dependent on the first resource information. For example, sensor resource information may not be dependent on WTRU location resource information, while the WTRU location resource information may be dependent on the sensor resource information.

[0170] This unidirectional dependency may be considered by the RMF when refreshing and / or updating a resource set. For example, if there is an update to sensor resource information (e.g., first resource information), the RMF may update WTRU location resource information (e.g., second resource information) accordingly, whereas an update of the WTRU location resource information (e.g., the second resourceI5GCN_2024P00596WO PATENT information) may not trigger an update to the sensor resource information (e.g., the first resource information).

[0171] A resource set may have an associated RsRev, which may be used to identify a revision of the resource set in time. The RsRev may be an immutable parameter maintained by the RMF. For example, the RMF may be the only entity allowed to modify and / or increment the RsRev. The RsRev value of an RMF local resource set may indicate the latest revision of the resource set.

[0172] The RsRev may be used to detect incoherency and / or to ensure that operations performed on a resource set are coherent. For example, a WTRU may have obtained a resource set from an RMF. The obtained resource set may include a given RsID and / or a RsRev with a first value (e.g., RsRev of 10). The RMF may have a local resource set with the same RsID and a RsRev with a second value (e.g., RsRev of 12). This desynchronization between the WTRU RsRev and the RMF RsRev may be caused by the WTRU not receiving resource set updates (e.g., if the WTRU had lost connectivity while these updates were happening).

[0173] The WTRU may send a localization request to a localization service, for example, as shown in FIG. 2. The WTRU may request the localization service to localize another WTRU. The WTRU may include the RsID and / or the first RsRev in the request sent to the localization service.

[0174] In some examples, the localization service may access the resource set local to the RMF and provide the RsID and / or the first RsRev to the RMF. The RMF may detect incoherency by determining that the first RsRev is different from the second RsRev. As a result of the incoherency detection, the RMF may indicate to the localization service and / or the WTRU that resource set incoherency has been detected (e.g., by sending an error message with a failure reason indicating that incoherency is detected). The RMF may trigger an update of the resource set by notifying the consumers of the resource set (e.g., the WTRU and / or the localization service).

[0175] In some examples, the localization service itself may be a consumer of the resource set and may have a local copy of the resource set with the RsID and a third RsRev. The localization service may detect incoherency by determining that the first RsRev is different from the third RsRev. As a result of the incoherency detection, the localization service may indicate to the WTRU that resource set incoherency has been detected (e.g., by sending an error message with a failure reason indicating that incoherency is detected). The localization service may update its local resource set by requesting the RMF to send the latest resource set.I5GCN_2024P00596WO PATENT

[0176] Incoherency detection may be performed by functional entities sharing a resource set. These functional entities may include, for example, WTRUs, NFs, and / or AFs.

[0177] The resource set messages described herein may include an RsRev as a message parameter. Functional entities receiving an RsRev may perform incoherency detection based on the received RsRev and the RsRev of a local copy of the resource set.

[0178] The RMF described herein may enable resource set coherency and / or management in a distributed wireless system. The functionalities of the RMF may include providing information and / or performing procedures related to the management of a resource set lifecycle, the maintenance of resource set coherency, the detection of resource information interdependencies, and / or the detection of resource information incoherency.

[0179] Although features and elements described above are described in particular combinations, each feature or element may be used alone without the other features and elements of the preferred embodiments, or in various combinations with or without other features and elements. Although the implementations described herein may consider 3GPP specific protocols, it is understood that the implementations described herein are not restricted to this scenario and may be applicable to other wireless systems. For example, although the solutions described herein consider LTE, LTE-A, New Radio (NR) or 5G specific protocols, it is understood that the solutions described herein are not restricted to this scenario and are applicable to other wireless systems as well.

[0180] The processes described above may be implemented in a computer program, software, and / or firmware 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 over wired and / or wireless connections) and / or computer-readable storage media. Examples of computer- readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as, but not limited to, internal hard disks and removable disks, magneto-optical media, and / or optical media such as compact disc (CD)-ROM disks, and / or digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, terminal, base station, RNC, and / or any host computer.

Claims

I5GCN_2024P00596WO PATENTCLAIMS1. A network device, comprising: a processor configured to: receive a first message from a wireless transmit / receive unit (WTRU) regarding a first type of information and a second type of information that are interrelated, wherein the first type of information is associated with a first service, and the second type of information is associated with a second service; send a second message to the WTRU regarding an information set that includes one or more values associated with the first type of information, one or more values associated with the second type of information, and an identifier of the information set; determine that the information set is to be updated in response to a change to the one or more values associated with the first type of information, the one or more values associated with the second type of information, or a location of the WTRU; determine an information set update based on at least one of the first service or the second service; and send a third message to the WTRU regarding the information set update and an identifier of the information set.

2. The network device of claim 1 , wherein the first type of information is a first type of spatial information related to a sensor, and wherein the second type of information is a second type of spatial information related to a spatial map.

3. The network device of claim 1 , wherein the processor being configured to determine the information set is to be updated in response to the change comprises the processor being configured to: determine that the one or more values associated with the first type of information have changed; and determine a corresponding change to the one or more values associated with the second type of information.

4. The network device of claim 1 , wherein at least one of the first service or the second service is associated with a metaverse.I5GCN_2024P00596WO PATENT5. The network device of claim 1 , wherein the processor being configured to determine the information set update comprises the processor being configured to determine that the information set update maintains a coherency of the information set.

6. The network device of claim 5, wherein the processor is further configured to send a fifth message to the WTRU, wherein the fifth message indicates a notification to the WTRU regarding a dependency of resources in the information set.

7. The network device of claim 1 , wherein the processor wherein the information set update is associated with a management of the information set.

8. The network device of claim 7, wherein processor is further configured to send a fifth message to the WTRU regarding a deletion or disablement of one or more resources in the information set.

9. The network device of claim 1 , wherein the information set update is associated with a mobility of the WTRU.

10. A method comprising: receiving a first message from a wireless transmit / receive unit (WTRU) regarding a first type of information and a second type of information that are interrelated, wherein the first type of information is associated with a first service, and the second type of information is associated with a second service; sending a second message to the WTRU regarding an information set that includes one or more values associated with the first type of information, one or more values associated with the second type of information, and an identifier of the information set; determining that the information set is to be updated in response to a change to the one or more values associated with the first type of information, the one or more values associated with the second type of information, or a location of the WTRU; determining an information set update based on at least one of the first service or the second service; and sending a third message to the WTRU regarding the information set update and an identifier of the information set.I5GCN_2024P00596WO PATENT11 . The method of claim 10, wherein the first type of information is a first type of spatial information related to a sensor, and wherein the second type of information is a second type of spatial information related to a spatial map.

12. The method of claim 10, wherein the determining the information set is to be updated in response to the change comprises: determining that the one or more values associated with the first type of information have changed; and determining a corresponding change to the one or more values associated with the second type of information.

13. The method of claim 10, wherein at least one of the first service or the second service is associated with a metaverse.

14. The method of claim 10, wherein the determining the information set update further comprises determining that the information set update maintains a coherency of the information set.

15. The method of claim 14, wherein the fifth message indicates a notification to the WTRU regarding a dependency of resources in the information set.

16. The method of claim 10, wherein the information set update is associated with a management of the information set.

17. The method of claim 16, wherein the method further comprises sending a fifth message to the WTRU regarding a deletion or disablement of one or more resources in the information set.

18. The method of claim 10, wherein the information set update is associated with a mobility of the WTRU.

Images