[go: up one dir, main page]

WO2024239690A1 - Procédés de gestion d'une tâche informatique infructueuse - Google Patents

Procédés de gestion d'une tâche informatique infructueuse Download PDF

Info

Publication number
WO2024239690A1
WO2024239690A1 PCT/CN2024/073370 CN2024073370W WO2024239690A1 WO 2024239690 A1 WO2024239690 A1 WO 2024239690A1 CN 2024073370 W CN2024073370 W CN 2024073370W WO 2024239690 A1 WO2024239690 A1 WO 2024239690A1
Authority
WO
WIPO (PCT)
Prior art keywords
computing task
message
processor
network entity
lmf
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/073370
Other languages
English (en)
Inventor
Congchi ZHANG
Lianhai WU
Bingchao LIU
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Lenovo Beijing Ltd
Original Assignee
Lenovo Beijing Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lenovo Beijing Ltd filed Critical Lenovo Beijing Ltd
Priority to PCT/CN2024/073370 priority Critical patent/WO2024239690A1/fr
Publication of WO2024239690A1 publication Critical patent/WO2024239690A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
    • G06F11/0709—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
    • G06F11/0736—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in functional embedded systems, i.e. in a data processing system designed as a combination of hardware and software dedicated to performing a certain function
    • G06F11/0742—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in functional embedded systems, i.e. in a data processing system designed as a combination of hardware and software dedicated to performing a certain function in a data processing system embedded in a mobile device, e.g. mobile phones, handheld devices
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0766—Error or fault reporting or storing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities

Definitions

  • the present disclosure relates to wireless communications, and more specifically to a user equipment (UE) , a network entity, a processor for wireless communication, methods, an apparatus for handling an unsuccessful computing task.
  • UE user equipment
  • a wireless communications system may include one or multiple network communication devices, such as base stations, which may be otherwise known as an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology.
  • Each network communication devices such as a base station may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE) , or other suitable terminology.
  • the wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) .
  • the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G) ) .
  • 3G third generation
  • 4G fourth generation
  • 5G fifth generation
  • 6G sixth generation
  • An entity may be requested by another entity (gNB or LMF) to perform computing tasks (for example, but not limited to, AI inference) to make prediction or compression or positioning estimation which are association with the wireless communication.
  • entity (UE/gNB) being requested may be not capable of the requested AI inference.
  • the entity (UE/gNB) being requested for AI inference shall notify the requesting entity (gNB/LMF) about the unsuccessful AI inference. Therefore, how and which procedures should be enhanced to serve this purpose need to be further studied and investigated.
  • the present disclosure relates to a user equipment (UE) , a network entity, a processor for wireless communication, methods, a base station, an apparatus for handling an unsuccessful computing task.
  • UE user equipment
  • a user equipment comprising: a processor; and a transceiver coupled to the processor, wherein the processor is configured to: receive, via the transceiver, a first message from a network entity requesting the UE to perform a computing task associated with wireless communication; and transmit, via the transceiver, a second message indicating that the UE fails in performing the computing task to the network entity.
  • network entity comprising: a processor; and a transceiver coupled to the processor, wherein the processor is configured to: transmit, via the transceiver, a first message to a user equipment (UE) requesting the UE to perform a computing task associated with wireless communication; and receive, via the transceiver, a second message indicating that the UE fails in performing the computing task from the UE.
  • UE user equipment
  • base station comprising: a processor; and a transceiver coupled to the processor, wherein the processor is configured to: receive, from a location management function (LMF) , a first message requesting the base station to perform a computing task associated with wireless communication; and transmit, to the LMF, a second message indicating that the base station fails in performing the computing task.
  • LMF location management function
  • a location management function comprising, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to: transmit, to a base station, a first message requesting the base station to perform a computing task associated with wireless communication; and receive, from the base station, a second message indicating that the base station fails in performing the computing task.
  • processor for wireless communication comprising: at least one memory; and a controller coupled with the at least one memory and configured to cause the controller to: receive, from a network entity, a first message requesting the processor to perform a computing task associated with wireless communication; and transmit, to the network entity, a second message indicating that the processor fails in performing the computing task.
  • a method performed by a first device comprising: receiving, from a second device, a first message requesting the first device to perform a computing task associated with wireless communication; and transmitting, to the second device, a second message indicating that the first device fails in performing the computing task.
  • a seventh aspect there is provided performed by a second device, the method comprising: transmitting, to a first device, a first message requesting the first device to perform a computing task associated with wireless communication; and receiving, from the first device, a second message indicating that the first device fails in performing the computing task.
  • a computer readable medium having instructions stored thereon, the instructions, when executed by a processor of an apparatus, causing the apparatus to perform the method according to any of the sixth and the seventh aspect of the disclosure.
  • the computing task associated with wireless communication comprise one of: a first computing task identifier; a first computing task type; a first computing task object; a first computing task time window; or a first computing task condition
  • the second message indicates one of: the computing task is not supported at the UE, or the computing task is supported at the UE while the UE is unable to perform the computing task temporarily.
  • the second message further indicates at least one of the following: the first computing task identifier; or a reason of failing of the computing task.
  • the UE, the network entity, the base station, or the LMF described herein in case that the computing task is not supported at the UE the reason of failing comprises at least one of: performing the computing task of the first computing task type is not supported; performing the computing task with the first computing task object is not supported; performing the computing task within the first computing task time window is not supported; or performing the computing task with the first computing task condition is not supported.
  • the second message in case that the computing task is not supported at the UE, the second message further indicates one of: a second computing task type, a second computing task object, or a second computing task time window that is supported at the UE.
  • the UE, the network entity, the base station, or the LMF described herein wherein in case that the computing task is supported at the UE while the UE is unable to perform the computing task temporarily, the reason of failing comprises at least one of: low battery energy; overheating; overloading; lack of configuration or input; or the first computing task condition is not fulfilled.
  • the second message further indicates at least one of the following: an estimated time that the time duration will last; or a required configuration or input which is missing currently.
  • the UE, the network entity, the base station, or the LMF described herein the first message is a radio resource control (RRC) reconfiguration message
  • the second message is a RRC reconfiguration complete message in response to the RRC reconfiguration message.
  • RRC radio resource control
  • the UE, the network entity, the base station, or the LMF described herein the first message requests for performing the computing task which has been pre-configured at the UE, and the second message is transmitted in response to the first message.
  • the UE may transmit the second message by transmitting, in case that the UE is unable to report a result of the computing task at a reporting instance, a reporting message as the second message to the network entity.
  • the reporting message comprises measurements result for the same object of the computing task.
  • the computing task is for UE positioning
  • the UE may receive, from the LMF, a configuration indicating a secondary positioning method; generate, based on determining a failure in performing the UE positioning, location information or assisting information using the secondary positioning method; and transmit the location information or the assisting information to the LMF.
  • the UE may transmit a third message to the network entity to abort the computing task based on determining that the UE cannot perform the computing task.
  • FIG. 1 illustrates an example of a wireless communications system in which some embodiments of the present disclosure can be implemented.
  • FIG. 2 illustrates an example of a process flow in which an unsuccessful computing task is notified to a requesting entity in accordance with some example embodiments of the present disclosure.
  • FIGS. 3A and 3B illustrate examples of process flows in which an unsuccessful computing task is notified from UE to gNB in request/response manner in accordance with some example embodiments of the present disclosure.
  • FIG. 4 illustrates an example of a process flow in which an unsuccessful computing task is notified from UE to gNB in reporting manner in accordance with some example embodiments of the present disclosure.
  • FIG. 5 illustrates an example of a process flow in which an unsuccessful computing task is notified from UE to LMF in accordance with some example embodiments of the present disclosure.
  • FIG. 6 illustrates an example of a process flow in which an unsuccessful computing task is notified from gNB to LMF in accordance with some example embodiments of the present disclosure.
  • FIG. 7 illustrates an example of a device that is suitable for implementing some embodiments of the present disclosure.
  • FIG. 8 illustrates an example of a processor that is suitable for implementing some embodiments of the present disclosure.
  • FIG. 9 illustrates a flowchart of a method performed by a first device in accordance with aspects of the present disclosure.
  • FIG. 10 illustrates a flowchart of a method performed by a second device in accordance with aspects of the present disclosure.
  • references in the present disclosure to “one embodiment, ” “an example embodiment, ” “an embodiment, ” “some embodiments, ” and the like indicate that the embodiment (s) described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment (s) . Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • first and second may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first element could also be termed as a second element, and similarly, a second element could also be termed as a first element, without departing from the scope of embodiments.
  • the term “and/or” includes any and all combinations of one or more of the listed terms. In some examples, values, procedures, or apparatuses are referred to as “best, ” “lowest, ” “highest, ” “minimum, ” “maximum, ” or the like. It will be appreciated that such descriptions are intended to indicate that a selection among many used functional alternatives can be made, and such selections need not be better, smaller, higher, or otherwise preferable to other selections.
  • the term “includes” and its variants are to be read as open terms that mean “includes, but is not limited to. ”
  • the term “based on” is to be read as “based at least in part on. ”
  • the term “one embodiment” and “an embodiment” are to be read as “at least one embodiment. ”
  • the term “another embodiment” is to be read as “at least one other embodiment. ”
  • the use of an expression such as “A and/or B” can mean either “only A” or “only B” or “both A and B. ”
  • Other definitions, explicit and implicit, may be included below.
  • FIG. 1 illustrates an example of a wireless communications system 100 in which some embodiments of the present disclosure can be implemented.
  • the wireless communications system 100 may include one or more network entities 102 (also referred to as network equipment (NE) ) , one or more UEs 104, a core network 106, and a packet data network 108.
  • the wireless communications system 100 may support various radio access technologies.
  • the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network.
  • LTE-A LTE-Advanced
  • the wireless communications system 100 may be a 5G network, such as an NR network.
  • the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20.
  • IEEE Institute of Electrical and Electronics Engineers
  • Wi-Fi Wi-Fi
  • WiMAX IEEE 802.16
  • IEEE 802.20 The wireless communications system 100 may support radio access technologies beyond 5G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA) , frequency division multiple access (FDMA) , or code division multiple access (CDMA) , etc.
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • CDMA code division multiple access
  • the one or more network entities 102 may be dispersed throughout a geographic region to form the wireless communications system 100.
  • One or more of the network entities 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a radio access network (RAN) , a base transceiver station, an access point, a NodeB, an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology.
  • RAN radio access network
  • eNB eNodeB
  • gNB next-generation NodeB
  • a network entity 102 and a UE 104 may communicate via a communication link 110, which may be a wireless or wired connection.
  • a network entity 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.
  • a network entity 102 in form of a satellite can directly communicate to UE 104 using NR/LTE Uu interface.
  • the satellite may be a transparent satellite or a regenerative satellite.
  • a base station on earth may communicate with a UE via the satellite.
  • the base station may be on board and directly communicate with the UE.
  • a network entity 102 may provide a geographic coverage area 112 for which the network entity 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc. ) for one or more UEs 104 within the geographic coverage area 112.
  • a network entity 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc. ) according to one or multiple radio access technologies.
  • a network entity 102 may be moveable, for example, a satellite associated with a non- terrestrial network.
  • different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas 112 may be associated with different network entities 102.
  • Information and signals described herein may be represented using any of a variety of different technologies and techniques.
  • data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
  • the one or more UEs 104 may be dispersed throughout a geographic region of the wireless communications system 100.
  • a UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a remote unit, a handheld device, or a subscriber device, or some other suitable terminology.
  • the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples.
  • the UE 104 may be referred to as an Internet-of-Things (IoT) device, an Internet-of-Everything (IoE) device, or machine-type communication (MTC) device, among other examples.
  • IoT Internet-of-Things
  • IoE Internet-of-Everything
  • MTC machine-type communication
  • a UE 104 may be stationary in the wireless communications system 100.
  • a UE 104 may be mobile in the wireless communications system 100.
  • the one or more UEs 104 may be devices in different forms or having different capabilities. Some examples of UEs 104 are illustrated in FIG. 1.
  • a UE 104 may be capable of communicating with various types of devices, such as the network entities 102, other UEs 104, or network equipment (e.g., the core network 106, the packet data network 108, a relay device, an integrated access and backhaul (IAB) node, or another network equipment) , as shown in FIG. 1.
  • a UE 104 may support communication with other network entities 102 or UEs 104, which may act as relays in the wireless communications system 100.
  • a UE 104 may also be able to support wireless communication directly with other UEs 104 over a communication link 114.
  • a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link.
  • D2D device-to-device
  • the communication link 114 may be referred to as a sidelink.
  • a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.
  • a network entity 102 may support communications with the core network 106, or with another network entity 102, or both.
  • a network entity 102 may interface with the core network 106 through one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) .
  • the network entities 102 may communicate with each other over the backhaul links 116 (e.g., via an X2, Xn, or another network interface) .
  • the network entities 102 may communicate with each other directly (e.g., between the network entities 102) .
  • the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106) .
  • one or more network entities 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC) .
  • An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs) .
  • the network entity 102 may include an entity for performing a location management function (LMF) .
  • LMF location management function
  • a network entity 102 may be configured in a disaggregated architecture, which may be configured to utilize a protocol stack physically or logically distributed among two or more network entities 102, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance) , or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN) ) .
  • IAB integrated access backhaul
  • O-RAN open RAN
  • vRAN virtualized RAN
  • C-RAN cloud RAN
  • a network entity 102 may include one or more of a central unit (CU) , a distributed unit (DU) , a radio unit (RU) , a RAN Intelligent Controller (RIC) (e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC) ) , a Service Management and Orchestration (SMO) system, or any combination thereof.
  • CU central unit
  • DU distributed unit
  • RU radio unit
  • RIC RAN Intelligent Controller
  • RIC e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC)
  • SMO Service Management and Orchestration
  • An RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote radio unit (RRU) , or a transmission reception point (TRP) .
  • One or more components of the network entities 102 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 102 may be located in distributed locations (e.g., separate physical locations) .
  • one or more network entities 102 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU) ) .
  • VCU virtual CU
  • VDU virtual DU
  • VRU virtual RU
  • Split of functionality between a CU, a DU, and an RU may be flexible and may support different functionalities depending upon which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof) are performed at a CU, a DU, or an RU.
  • functions e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof
  • a functional split of a protocol stack may be employed between a CU and a DU such that the CU may support one or more layers of the protocol stack and the DU may support one or more different layers of the protocol stack.
  • the CU may host upper protocol layer (e.g., a layer 3 (L3) , a layer 2 (L2) ) functionality and signaling (e.g., Radio Resource Control (RRC) , service data adaption protocol (SDAP) , Packet Data Convergence Protocol (PDCP) ) .
  • RRC Radio Resource Control
  • SDAP service data adaption protocol
  • PDCP Packet Data Convergence Protocol
  • the CU may be connected to one or more DUs or RUs, and the one or more DUs or RUs may host lower protocol layers, such as a layer 1 (L1) (e.g., physical (PHY) layer) or an L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160.
  • L1 e.g., physical (PHY) layer
  • L2 e.g., radio link control (RLC) layer, medium access
  • a functional split of the protocol stack may be employed between a DU and an RU such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack.
  • the DU may support one or multiple different cells (e.g., via one or more RUs) .
  • a functional split between a CU and a DU, or between a DU and an RU may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU, a DU, or an RU, while other functions of the protocol layer are performed by a different one of the CU, the DU, or the RU) .
  • a CU may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions.
  • a CU may be connected to one or more DUs via a midhaul communication link (e.g., F1, F1-c, F1-u)
  • a DU may be connected to one or more RUs via a fronthaul communication link (e.g., open fronthaul (FH) interface)
  • FH open fronthaul
  • a midhaul communication link or a fronthaul communication link may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 102 that are in communication via such communication links.
  • the core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions.
  • the core network 106 may be an evolved packet core (EPC) , or a 5G core (5GC) , which may include a server 117 for performing a location management function (LMF) , a control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management functions (AMF) ) , and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) .
  • EPC evolved packet core
  • 5GC 5G core
  • LMF location management function
  • MME mobility management entity
  • AMF access and mobility management functions
  • S-GW serving gateway
  • PDN gateway Packet Data Network gateway
  • UPF user plane function
  • control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc. ) for the one or more UEs 104 served by the one or more network entities 102 associated with the core network 106.
  • NAS non-access stratum
  • the LMF may be defined in the core network 106 and/or the network entity 102 to provide positioning functionality by means to determine the geographic position of a UE 104 based on downlink and uplink location measuring radio signals.
  • the packet data network 108 may include an application server 118.
  • the core network 106 may communicate with the packet data network 108 over one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) .
  • the packet data network 108 may include an application server 118.
  • one or more UEs 104 may communicate with the application server 118.
  • a UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the core network 106 via a network entity 102.
  • the core network 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server 118 using the established session (e.g., the established PDU session) .
  • the PDU session may be an example of a logical connection between the UE 104 and the core network 106 (e.g., one or more network functions of the core network 106) .
  • the network entities 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) ) to perform various operations (e.g., wireless communications) .
  • the network entities 102 and the UEs 104 may support different resource structures.
  • the network entities 102 and the UEs 104 may support different frame structures.
  • the network entities 102 and the UEs 104 may support a single frame structure.
  • the network entities 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures) .
  • the network entities 102 and the UEs 104 may support various frame structures based on one or more numerologies.
  • One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix.
  • a first subcarrier spacing e.g., 15 kHz
  • a normal cyclic prefix e.g. 15 kHz
  • the first numerology associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe.
  • a time interval of a resource may be organized according to frames (also referred to as radio frames) .
  • Each frame may have a duration, for example, a 10 millisecond (ms) duration.
  • each frame may include multiple subframes.
  • each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration.
  • each frame may have the same duration.
  • each subframe of a frame may have the same duration.
  • a time interval of a resource may be organized according to slots.
  • a subframe may include a number (e.g., quantity) of slots.
  • the number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100.
  • Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols) .
  • the number (e.g., quantity) of slots for a subframe may depend on a numerology.
  • a slot For a normal cyclic prefix, a slot may include 14 symbols.
  • a slot For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing) , a slot may include 12 symbols.
  • an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc.
  • the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz –7.125 GHz) , FR2 (24.25 GHz –52.6 GHz) , FR3 (7.125 GHz –24.25 GHz) , FR4 (52.6 GHz –114.25 GHz) , FR4a or FR4-1 (52.6 GHz –71 GHz) , and FR5 (114.25 GHz –300 GHz) .
  • FR1 410 MHz –7.125 GHz
  • FR2 24.25 GHz –52.6 GHz
  • FR3 7.125 GHz –24.25 GHz
  • FR4 (52.6 GHz –114.25 GHz)
  • FR4a or FR4-1 52.6 GHz –71 GHz
  • FR5 114.25 GHz
  • the network entities 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands.
  • FR1 may be used by the network entities 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data) .
  • FR2 may be used by the network entities 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.
  • FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies) .
  • FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies) .
  • FIG. 2 illustrates an example of a process flow in which an unsuccessful computing task is notified to a requesting entity in accordance with some example embodiments of the present disclosure.
  • the process flow 200 may involve a network entity 202 as the requesting entity and an UE 204 as a requested entity.
  • the process flow 200 may be applied to the wireless communications system 100 with reference to FIG. 1, for example, the UE 204 may be any of UEs 104.
  • the network entity 202 may be or deployed at any of the network entities 102; for example, the network entity 202 may be a base station (e.g., gNB) .
  • the network entity 202 may be or deployed at the server 117 in the core network 106; for example, the network entity 202 may be an LMF.
  • the UE 204 may be any of the UEs 104 as show in FIG. 1. It would be appreciated that the process flow 200 may be applied to other communication scenarios, which will not be described in detail.
  • the network entity 202 may transmit a first message 215 to the UE 204 requesting the UE 204 to perform a computing task associated with wireless communication. Accordingly, at 220, the UE 204 receives the first message 215.
  • the computing task may comprise or be associated with one or more of a first computing task identifier, a first computing task type, a first computing task object, a first computing task time window; or a first computing task condition of the computing task.
  • the first message 215 may further indicate relevant information depending on implementations which will be described below.
  • the UE 204 may transmit a second message 235 indicating that the UE 204 fails in performing the computing task to the network entity 202. Accordingly, at 240, the network entity 202 receives the second message 235. Depending on UE’s capability, the second message 235 may indicate that the computing task is not supported at the UE. That is, the UE 204 is not capable of performing the computing task at all. In this case, the network entity 202 may not request the UE 204 to perform the same computing task any more or at least in a near future. The second message 235 may indicate that the computing task is supported at the UE 204 but the UE 204 is unable to perform the computing task for a time duration. That is, the UE 204 is capable of the requested computing task but cannot perform the computing task temporarily for some reason.
  • the second message 235 may indicate a computing task identifier of the computing task. Additionally, the second message 235 may further indicate a reason of failing of the computing task. In addition to such information, the second message 235 may include relevant information depending on implementation which will be described below.
  • the reason may be that one or more of the requirements associated with the first message are not supported at the UE 204.
  • the reason may comprise one or more of the following: performing the computing task of the first computing task type is not supported, performing the computing task with the first computing task object is not supported, performing the computing task within the first computing task time window is not supported, performing the computing task with the first computing task condition is not supported.
  • the second message 235 may further indicate a second computing task that is supported at the UE 204 , including, for example, a second computing task type, a second computing task object, or a second computing task time window.
  • the reason of failing may comprise one or more of the following: low battery energy, overheating, overloading, lack of configuration or input, or the first computing task condition is not fulfilled.
  • the second message further indicates at least one of the following: an estimated time that the time duration (i.e. the reason of failing) will last; or a required configuration or input which is missing currently.
  • the network entity 202 may be a gNB requesting the UE 204 to perform a computing task associated with wireless communication, and the UE 204 informs the gNB about the unsuccessfulcomputing task.
  • the gNB may request the UE to perform PHY layer operation, such as channel state information (CSI) compression, time domain CSI prediction, time domain beam prediction, spatial domain beam prediction, direct positioning, AI assisted positioning.
  • PHY layer operation can be performed using AI/ML model at UE side.
  • the gNB may also request the UE to perform radio resource management (RRM) prediction, such as time domain cell/beam L3 measurement prediction, intra frequency L3 measurement prediction of other cells/beams, inter frequency L3 measurement prediction of other cells/beams.
  • RRM radio resource management
  • the UE may receive a first message (e.g., the first message 215) from the gNB which requests or configures the UE to perform time/spatial domain prediction or compression (which can be determined using AI/ML model) and report the result in one-time, event-triggered, or periodic manner.
  • a first message e.g., the first message 215
  • the UE may be not capable of the requested prediction/compression, or the UE may be capable but temporarily suspended due to some reasons.
  • the UE will not transmit any result of time/spatial domain prediction or compression (which can be determined using AIML model) to gNB, instead the UE may transmit measurement result and may notify the gNB about the unsuccessful time/spatial domain prediction or compression (which can be determined using AI/ML model) and in addition relevant information in a second message (e.g., the second message 235) via RRC procedures.
  • time/spatial domain prediction or compression which can be determined using AIML model
  • the UE may transmit measurement result and may notify the gNB about the unsuccessful time/spatial domain prediction or compression (which can be determined using AI/ML model) and in addition relevant information in a second message (e.g., the second message 235) via RRC procedures.
  • the relevant information in the second message may include an indication that the requested prediction/compression is not supported, and the concerned object (e.g., frequency/cell/beam to perform prediction) represented by e.g., measId or measObjId or predictionObjId or reportConfigId or eventId.
  • the second message may further include the reason of the unsuccessful prediction/compression which can be represented by enumerated values.
  • the reason of the unsuccessful Prediction/compression may include but not limited to: requested use case or task type (e.g., CSI prediction, beam prediction) is not supported, UE is not capable of performing the prediction/compression on the given object (e.g., frequency/cell/beam, or RRM event) , UE is not capable of predicting in current condition (indoor, outdoor, large cell, small cell) , UE is not capable of time domain prediction with given time window (e.g., cannot predict what happens after 10mins) .
  • the UE may further indicate other task type/use case, object, condition, or time window that the UE is capable of, which can be represented by enumerated values.
  • the relevant information in the second message may include an indication that the requested prediction/compression is temporarily not supported, and the concerned object (e.g., frequency/cell/beam to perform prediction) represented by e.g., measId or measObjId or predictionObjId or reportConfigId or eventId.
  • the second message may further include the reason of the unsuccessful prediction/compression which can be represented by enumerated values.
  • the reason of the unsuccessful prediction/compression may include but not limited to: low battery energy, overheating, overloading, task condition is not fulfilled, or lack of configuration or input.
  • the gNB configures or requests UE to predict the quality of Cell #A, but the gNB has not configured the UE with enough information about Cell #A, e.g., reference signals.
  • the UE can predict Cell #A quality, but need its neighbor cells’ quality as input, however the UE does not have the measurement configuration of neighbor cells.
  • beam prediction may be divided into intra-cell beam measurement result prediction and Inter-cell beam measurement result prediction.
  • Inter-cell beam the UE may have less information e.g., no CSI-RS configuration. Therefore, the UE can predict intra-cell beam measurement result but cannot predict inter-cell beam measurement result. The above cases result in that the UE cannot perform the requested prediction temporarily, because the UE lacks configuration or input.
  • the prediction/compression requested by gNB may include but not limited to PHY layer AI operation and RRM prediction.
  • the PHY layer AI operation may include but not limited to: CSI compression; time domain CSI prediction, i.e., predicting the future CSI based on measured CSI in the past; time domain beam prediction, i.e., predicting the future L1 beam quality based on measured L1 beam quality in the past; or spatial domain beam prediction, i.e., predicting Set A of beams using measurement of Set B of beams.
  • the RRM prediction may include but not limited to: time domain cell/beam L3 measurement prediction, i.e., predicting the future L3 cell/beam quality based on measured L3 cell/beam quality in the past; intra frequency L3 measurement prediction of other cells/beams, i.e., within the same frequency, predicting L3 measurement of Set A cells/beams using L3 measurement of Set B of cells/beams; inter frequency L3 measurement prediction of other cells/beams, i.e., cross different frequencies, predicting L3 measurement of Set A cells/beams using L3 measurement of Set B of cells/beams.
  • time domain cell/beam L3 measurement prediction i.e., predicting the future L3 cell/beam quality based on measured L3 cell/beam quality in the past
  • intra frequency L3 measurement prediction of other cells/beams i.e., within the same frequency, predicting L3 measurement of Set A cells/beams using L3 measurement of Set B of cells/beams
  • the UE may determine that it is either not capable of the requested prediction/compression, or the UE is capable but temporarily suspended due to some reasons.
  • the UE may indicate the unsuccessful prediction/compression in the response message sent to the gNB.
  • FIG. 3A illustrate an example of a process flow in which an unsuccessful computing task is notified from UE to gNB in request/response manner in accordance with some example embodiments of the present disclosure.
  • the process flow in FIG. 3A is an example implementation of the process flow 200 in FIG. 2, where the UE 304 is an example of UE 204, and the gNB 302 is an example of the network entity 202.
  • the gNB 302 requests the UE 304 to perform prediction/compression (e.g., predicting L1/L3 measurement in the future) via an RRCReconfiguration message, wherein the RRCReconfiguration message may contain configuration (s) related to the prediction/compression configuration, e.g., frequency/cell/beam object to predict, time window to predict.
  • the UE 304 cannot perform the prediction/compression as requested but can comply the rest configuration in the RRCReconfiguration message, the UE 304 still considers the RRC procedure successful and reply an RRCReconfigurationComplete message to the gNB 302 at step 2.
  • the RRCReconfigurationComplete message notifies the gNB 302 about the unsuccessful prediction/compression and in addition relevant information as described above.
  • FIG. 3B illustrates another example of a process flow in which an unsuccessful computing task is notified from UE to gNB in request/response manner in accordance with some example embodiments of the present disclosure.
  • the process flow in FIG. 3B is another example implementation of the process flow 200 in FIG. 2.
  • the UE 304 Assuming the configuration for prediction/compression (e.g., predicting L1/L3 measurement using AI/ML model at UE side) has been configured at the UE 304, e.g., frequency/cell/beam object to predict, time window to predict. The UE 304 does not perform prediction/compression directly after receiving the configuration. Instead, the UE 304 waits until receiving another message from the gNB 302 to trigger the prediction/compression. In one example, at step 1, the gNB 302 may use a UEInformationRequest message to trigger the UE 304 to perform the prediction/compression and report the inference result in the UEInformationResponse message at step 2.
  • the gNB 302 may use a dedicated indicator or information element (e.g., predictionResultRequest IE) to request the prediction/compression result from the UE 304.
  • the gNB 302 may use a measId or measObjId or predictionObjId or reportConfigId or eventId to link the prediction/compression request to a previously configured prediction/compression configuration. If the UE 304 cannot perform the prediction/compression as requested, in the UEInformationResponse message sent from UE to gNB, it may notify the gNB 302 about the unsuccessful prediction/compression and in addition relevant information as described above. Note that using UEInformationRequest and UEInformationResponse message is one example. It is also possible that other RRC procedures/messages are used for the same purpose, i.e., trigging and report the prediction/compression result.
  • gNB requests UE to perform a computing task (e.g., prediction/compression using AI/ML model at UE side)
  • UE may determine that it is capable of the requested prediction/compression at the moment and thus accept the request in the response message.
  • UE may confront problems and fails to perform prediction/compression.
  • UE will indicate the unsuccessful prediction/compression in the response message sent to gNB in the subsequent message (other than the response message) .
  • FIG. 4 illustrates an example of a process flow in which an unsuccessful computing task is notified from UE to gNB in reporting manner in accordance with some example embodiments of the present disclosure.
  • the process flow in FIG. 4 is an example implementation of the process flow 200 in FIG. 2, where the UE 404 is an example of UE 204, and the gNB 402 is an example of the network entity 202.
  • the gNB 402 configures the UE 404 to perform prediction/compression (e.g., predicting L1/L3 measurement using AI/ML model at UE side) and report the inference result in one time, periodic, or event triggered manner via MeasurementReport.
  • the UE 404 first reply an RRCReconfigurationComplete message.
  • the UE 404 transmits the MeasurementReport messages including prediction result or measurement result to the gNB 402, for example, periodically.
  • the UE 404 may skip the next instance of MeasurementReport and does not send anything to the gNB 402. Alternatively, at step 4 the UE 404 may still send a MeasurementReport message, wherein the UE 404 does not include any measurement result or prediction result, and notify the gNB 402 about the unsuccessful prediction/compression and in addition the relevant information as described above.
  • the UE 404 may still send a MeasurementReport message, wherein the UE 404 includes the measurement result for the same object and reports to the gNB 402, and notify the gNB 402 about the unsuccessful prediction/compression and in addition the relevant information as described above.
  • the UE 404 resumes to transmit MeasurementReport messages including the prediction result to the gNB 402.
  • the network entity 202 is an LMF requesting the UE 204 to perform positioning estimation or provide assisting information for positioning estimation (e.g., using AI/ML model at UE side) , and the UE 204 informs the LMF about unsuccessful prediction. Details will be described with reference to FIG. 5.
  • FIG. 5 illustrates an example of a process flow in which an unsuccessful computing task is notified from UE to LMF in accordance with some example embodiments of the present disclosure.
  • the process flow in FIG. 5 is an example implementation of the process flow 200 in FIG. 2, where the UE 504 is an example of UE 204, and the LMF 501 is an example of the network entity 202.
  • the LMF 501 may request the UE 504 to perform positioning estimation or provide assisting information for positioning estimation.
  • the positioning estimation or assisting information determination could be performed by using AI/ML model.
  • the positioning estimation can be UE-based positioning with UE-side model, UE-assisted/LMF-based positioning with UE-side model, and UE-assisted/LMF-based positioning with LMF-side model.
  • the UE 504 receives a first message (e.g., LPP RequestLocationInformation message) from the LMF 501 which requests or configures the UE 504 to perform a computing task including positioning estimation or providing assisting information for positioning estimation (which could be location estimated by UE AI model, or assisting information determined by UE AI model such as time of arrival (ToA) , path phase, reference signal time difference (RSTD) , timing estimation, line of sight/non-line of sight (LOS/NLOS) indicator, reference signal receive path power (RSRPP) ) in one-time/event-triggered/periodic manner.
  • a first message e.g., LPP RequestLocationInformation message
  • the UE 504 If the UE 504 succeeds in performing the positioning estimation or providing assisting information, it transmits the ProvideLocationInformation message including estimated location results or assisting information to the LMF 501 at step 2. However, the UE 504 may be either not capable of the requested task, or the UE 504 is capable but temporarily suspended due to some reasons. In such case, the UE will not transmit any estimation result or assisting information to the LMF 501, instead at step 3, the UE 504 may transmit measurement result and may notify the LMF 501 about the unsuccessful task and relevant information via LPP procedures.
  • the relevant information may include one or more of the following: an indication that the requested task is not supported; a reason of the unsuccessful task which may be represented by enumerated values; UE is not capable of the given task type of condition (e.g., UE AI based location estimation, AI based assisting information provision for LMF based location estimation) ; UE is not capable of the task in current condition (indoor, outdoor, large cell, small cell) .
  • the relevant information may further indicate the use case, the task type, the condition that UE is capable of, which may be represented by enumerated values.
  • the relevant information may include one or more of the following: an indication that the requested task is temporarily not supported; a reason of the unsuccessful task, which may be represented by enumerated values (e.g., low battery energy, low battery energy, overheating, overloaded by other tasks) .
  • the relevant information may further indicate the estimated time duration that the current problem will last, which can be represented by enumerated values, e.g., 10s, 1min, and others.
  • the computing task requested by the LMF 501 may include UE-based positioning with UE-side model, direct AI/ML or AI/ML assisted positioning, i.e., using AI model UE estimates its current location from its spectrum environment and reports the estimation result to LMF 501.
  • the computing task requested by the LMF 501 may include UE-assisted/LMF-based positioning with UE-side model, and AI/ML assisted positioning, i.e., using AI model UE determines assisting information (e.g., ToA, path phase, RSTD, Timing estimation, LOS/NLOS indicator, RSRPP) and reports the assisting information to LMF 501, then LMF 501 estimates the UE location taking the assisting information into account.
  • assisting information e.g., ToA, path phase, RSTD, Timing estimation, LOS/NLOS indicator, RSRPP
  • the LMF 501 may configure the UE 504 to perform AI based location estimation or AI based assisting information provision in either one-time, event-triggered, or periodic manner. Besides, the LMF 501 may also configure the UE 504 with a secondary method for UE to use as an alternative if the AI based location estimation does not work or currently unavailable due to reasons mentioned above. Then, the UE 504 starts the requested computing task following the configuration from LMF and provides the estimation result (i.e., estimated location or assisting information) to LMF via LPP ProvideLocationInformation message.
  • the estimation result i.e., estimated location or assisting information
  • UE 504 may skip the next instance of ProvideLocationInformation generation/transmission.
  • the UE 504 may transmit a ProvideLocationInformation message, wherein it does not include estimation result or the assisting information, instead it notifies the LMF 501 about the unsuccessful positioning estimation and in addition the relevant information as described above.
  • the secondary method is configured by the LMF 501
  • the UE 504 may generate a location estimation using the secondary method, and may include the estimated location result in the ProvideLocationInformation message and send to LMF.
  • UE may notify the LMF 501 about the unsuccessful positioning estimation and in addition the relevant information as described above.
  • the secondary method may be any of the following positioning methods, including but not limited to: network-assisted GNSS methods, observed time difference of arrival (OTDOA) positioning based on LTE signals, enhanced cell ID methods based on LTE signals, WLAN positioning, Bluetooth positioning, terrestrial beacon system (TBS) positioning, sensor based methods (e.g., barometric pressure sensor, motion sensor) , NR enhanced cell ID methods (NR E-CID) based on NR signals, multi-round trip time positioning (Multi-RTT based on NR signals) ; downlink angle-of-departure (DL-AoD) based on NR signals, downlink time difference of arrival (DL-TDOA) based on NR signals, uplink time difference of arrival (UL-TDOA) based on NR signals, and uplink angle-of-arrival (UL-AoA) including A-AoA and Z-AoA based on NR signals.
  • network-assisted GNSS methods including but not limited to: network-assisted GNSS
  • the UE 504 After the problem is solved and the UE 504 succeeds to make the next positioning estimation, at step 4 the UE 504 resumes to transmit ProvideLocationInformation messages including the estimation result or assisting information to the LMF 501.
  • the UE 504 may transmit a third message (Abort message) to LMF to abort the ongoing LPP procedure reporting the estimation result or assisting information.
  • a third message (Abort message) to LMF to abort the ongoing LPP procedure reporting the estimation result or assisting information.
  • the Abort message it may notify the LMF 501 about the unsuccessful positioning estimation or provision of assisting information, and in addition the relevant information as described above.
  • an LMF may request a network entity (e.g., gNB) to perform a computing task associated with wireless communication, for example, positioning estimation or providing assisting information for positioning estimation using AI/ML model at gNB side, and the network entity may inform the LMF about the unsuccessful computing task. Details will be described with reference to FIG. 6.
  • a network entity e.g., gNB
  • FIG. 6 illustrates an example of a process flow in which an unsuccessful computing task is notified from gNB to LMF in accordance with some example embodiments of the present disclosure.
  • the gNB 602 may be or deployed at any of the network entities 102, and the LMF 601 may be or deployed at the server 117 in the core network 106.
  • the LMF 601 may request the gNB 602 to provide assisting information for positioning estimation.
  • the assisting information determination can be performed using AI/ML model.
  • the positioning estimation can be NG-RAN node assisted positioning with gNB-side model, and NG-RAN node assisted positioning with LMF-side model.
  • the gNB 602 receives a Measurement request message from the LMF 601 which requests or configures the gNB to perform a computing task (e.g., positioning estimation using AI/ML model) and report the computing result (which could be estimation result or assisting information determined by gNB AI model, such as ToA, path phase, RSTD, LOS/NLOS indicator, RSRPP) in one-time/event-triggered/periodic manner.
  • a computing task e.g., positioning estimation using AI/ML model
  • the computing result which could be estimation result or assisting information determined by gNB AI model, such as ToA, path phase, RSTD, LOS/NLOS indicator, RSRPP
  • the gNB 602 may be either not capable of the requested computing task, or the gNB 602 is capable but temporarily suspended due to reasons.
  • the gNB 602 does not transmit any inference result to the LMF 601, instead the gNB 602 may transmit measurement result and may notify the LMF 601 about the unsuccessful positioning estimation and relevant information via NRPPa procedures. In some embodiments, the gNB 602 may notify the LMF 601 about the unsuccessful positioning estimation and relevant information via a NRPPa MEASUREMENT RESPONE message at step 2.
  • the relevant information may include an indication that the requested computing task is not supported, and reason of the unsuccessful computing task, which can be represented by enumerated values.
  • the reason of the unsuccessful computing task may be that the gNB 602 does not support the requested assisting info (ToA, path phase, RSTD, Timing estimation, LOS/NLOS indicator, RSRPP) .
  • the relevant information may further indicate assisting information that the gNB 602 is capable of, which may be represented by enumerated values.
  • the relevant information may include an indication that the requested computing task is temporarily not supported, and reason of the unsuccessful computing task, which can be represented by enumerated values.
  • the reason of the unsuccessful computing task may be overloading of the gNB 602.
  • the relevant information may further indicate the estimated time duration that the current problem will last, which may be represented by enumerated values, e.g., 10s, 1min and others.
  • the computing task requested by the LMF 601 may include but not limited to NG-RAN node assisted positioning (e.g., ToA, path phase, RSTD, Timing estimation, LOS/NLOS indicator, RSRPP) with gNB-side model, AI/ML assisted positioning.
  • NG-RAN node assisted positioning e.g., ToA, path phase, RSTD, Timing estimation, LOS/NLOS indicator, RSRPP
  • the LMF 601 may configure the gNB 602 to perform AI based assisting information provision in either one-time, event-triggered, or periodic manner. Then, the gNB 602 may start the assisting information provision following the configuration from the LMF 601 and provide the inference result (i.e., assisting information) to the LMF 601 via NRPPa MEASUREMENT REPORT message at step 4.
  • the gNB 602 may skip the next instance of MEASURMENET REPORT generation/transmission. Alternatively, the gNB 602 may transmit a MEASUREMENT REPORT message, wherein the gNB 602 does not include positioning estimation or assisting information, but notify the LMF 601 about the unsuccessful task and in addition the relevant information as described above. If the gNB 602 can no longer perform and provide the positioning estimation or assisting information to LMF 601, at step 6 the gNB 602 may send a MEASUREMENT FAILURE INDICAITON message to LMF 601 to abort the task. In this message, it may notify the LMF 601 about the unsuccessful computing task and in addition the relevant information as described above.
  • FIG. 7 illustrates an example of a device that is suitable for implementing some embodiments of the present disclosure.
  • the device 700 may be an example of an LMF or an AMF as described herein.
  • the device 700 may support wireless or wired communication with one or more network entities 102, UEs 104, a server 117 in a core network 106, or any combination thereof.
  • the device 700 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 702, a memory 704, a transceiver 706, and, optionally, an I/O controller 708. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .
  • interfaces e.g., buses
  • the processor 702, the memory 704, the transceiver 706, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein.
  • the processor 702, the memory 704, the transceiver 706, or various combinations or components thereof may support a method for performing one or more of the operations described herein.
  • the processor 702, the memory 704, the transceiver 706, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) .
  • the hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
  • the processor 702 and the memory 704 coupled with the processor 702 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 702, instructions stored in the memory 704) .
  • the processor 702 may support wireless or wired communication at the device 700 in accordance with examples as disclosed herein.
  • the device 700 may be a first device (e.g. any of UEs 104 or any of network entities 102) .
  • the processor 702 may be configured to operable to support means for receiving, from a second device, a first message requesting the first device to perform a computing task associated with wireless communication; and means for transmitting, to the second device, a second message indicating that the first device fails in performing the computing task.
  • the processor 702 may support wireless or wired communication at the device 700 in accordance with examples as disclosed herein.
  • the device 700 may be a second device (e.g. any of network entities 102, or an apparatus for performing LMF in core network) .
  • the processor 702 may be configured to operable to support means for transmitting, to a first device, a first message requesting the first device to perform a computing task associated with wireless communication; and means for receiving, from the first device, a second message indicating that the first device fails in performing the computing task.
  • the processor 702 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) .
  • the processor 702 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 702.
  • the processor 702 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 704) to cause the device 700 to perform various functions of the present disclosure.
  • the memory 704 may include random access memory (RAM) and read-only memory (ROM) .
  • the memory 704 may store computer-readable, computer-executable code including instructions that, when executed by the processor 702 cause the device 700 to perform various functions described herein.
  • the code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory.
  • the code may not be directly executable by the processor 702 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the memory 704 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • BIOS basic I/O system
  • the I/O controller 708 may manage input and output signals for the device 700.
  • the I/O controller 708 may also manage peripherals not integrated into the device 700.
  • the I/O controller 708 may represent a physical connection or port to an external peripheral.
  • the I/O controller 708 may utilize an operating system such as or another known operating system.
  • the I/O controller 708 may be implemented as part of a processor, such as the processor 702.
  • a user may interact with the device 700 via the I/O controller 708 or via hardware components controlled by the I/O controller 708.
  • the device 700 may include a single antenna 710. However, in some other implementations, the device 700 may have more than one antenna 710 (i.e., multiple antennas) , including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the transceiver 706 may communicate bi-directionally, via the one or more antennas 710, wired, or wireless links as described herein.
  • the transceiver 706 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 706 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 710 for transmission, and to demodulate packets received from the one or more antennas 710.
  • the transceiver 706 may include one or more transmit chains, one or more receive chains, or a combination thereof.
  • a transmit chain may be configured to generate and transmit signals (e.g., control information, data, packets) .
  • the transmit chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium.
  • the at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM) , frequency modulation (FM) , or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM) .
  • the transmit chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium.
  • the transmit chain may also include one or more antennas 710 for transmitting the amplified signal into the air or wireless medium.
  • a receive chain may be configured to receive signals (e.g., control information, data, packets) over a wireless medium.
  • the receive chain may include one or more antennas 710 for receive the signal over the air or wireless medium.
  • the receive chain may include at least one amplifier (e.g., a low-noise amplifier (LNA) ) configured to amplify the received signal.
  • the receive chain may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal.
  • the receive chain may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.
  • FIG. 8 illustrates an example of a processor 800 is suitable for implementing some embodiments of the present disclosure.
  • the processor 800 may be an example of a processor configured to perform various operations in accordance with examples as described herein.
  • the processor 800 may include a controller 802 configured to perform various operations in accordance with examples as described herein.
  • the processor 800 may optionally include at least one memory 804. Additionally, or alternatively, the processor 800 may optionally include one or more arithmetic-logic units (ALUs) 806.
  • ALUs arithmetic-logic units
  • One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .
  • the processor 800 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein.
  • a protocol stack e.g., a software stack
  • operations e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading
  • the processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 800) or other memory (e.g., random access memory (RAM) , read-only memory (ROM) , dynamic RAM (DRAM) , synchronous dynamic RAM (SDRAM) , static RAM (SRAM) , ferroelectric RAM (FeRAM) , magnetic RAM (MRAM) , resistive RAM (RRAM) , flash memory, phase change memory (PCM) , and others) .
  • RAM random access memory
  • ROM read-only memory
  • DRAM dynamic RAM
  • SDRAM synchronous dynamic RAM
  • SRAM static RAM
  • FeRAM ferroelectric RAM
  • MRAM magnetic RAM
  • RRAM resistive RAM
  • PCM phase change memory
  • the controller 802 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 800 to cause the processor 800 to support various operations in accordance with examples as described herein.
  • the controller 802 may operate as a control unit of the processor 800, generating control signals that manage the operation of various components of the processor 800. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
  • the controller 802 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 804 and determine subsequent instruction (s) to be executed to cause the processor 800 to support various operations in accordance with examples as described herein.
  • the controller 802 may be configured to track memory address of instructions associated with the memory 804.
  • the controller 802 may be configured to decode instructions to determine the operation to be performed and the operands involved.
  • the controller 802 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 800 to cause the processor 800 to support various operations in accordance with examples as described herein.
  • the controller 802 may be configured to manage flow of data within the processor 800.
  • the controller 802 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 800.
  • ALUs arithmetic logic units
  • the memory 804 may include one or more caches (e.g., memory local to or included in the processor 800 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementation, the memory 804 may reside within or on a processor chipset (e.g., local to the processor 800) . In some other implementations, the memory 804 may reside external to the processor chipset (e.g., remote to the processor 800) .
  • caches e.g., memory local to or included in the processor 800 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.
  • the memory 804 may reside within or on a processor chipset (e.g., local to the processor 800) . In some other implementations, the memory 804 may reside external to the processor chipset (e.g., remote to the processor 800) .
  • the memory 804 may store computer-readable, computer-executable code including instructions that, when executed by the processor 800, cause the processor 800 to perform various functions described herein.
  • the code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory.
  • the controller 802 and/or the processor 800 may be configured to execute computer-readable instructions stored in the memory 804 to cause the processor 800 to perform various functions (e.g., functions or tasks supporting transmit power prioritization) .
  • the processor 800 and/or the controller 802 may be coupled with or to the memory 804, the processor 800, the controller 802, and the memory 804 may be configured to perform various functions described herein.
  • the processor 800 may include multiple processors and the memory 804 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.
  • the one or more ALUs 806 may be configured to support various operations in accordance with examples as described herein.
  • the one or more ALUs 806 may reside within or on a processor chipset (e.g., the processor 800) .
  • the one or more ALUs 806 may reside external to the processor chipset (e.g., the processor 800) .
  • One or more ALUs 806 may perform one or more computations such as addition, subtraction, multiplication, and division on data.
  • one or more ALUs 806 may receive input operands and an operation code, which determines an operation to be executed.
  • One or more ALUs 806 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 806 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 806 to handle conditional operations, comparisons, and bitwise operations.
  • logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 806 to handle conditional operations, comparisons, and bitwise operations.
  • the processor 800 may support wireless communication in accordance with examples as disclosed herein.
  • the processor 800 may be implemented for performing a UE or a network entity as a first device.
  • the processor 800 may be configured to or operable to support means for receiving, from a second device, a first message requesting the first device to perform a computing task associated with wireless communication; and means for transmitting, to the second device, a second message indicating that the first device fails in performing the computing task.
  • the processor 800 may be implemented for performing a network entity or an LMF as a second device.
  • the processor 800 may be configured to or operable to support means transmitting, to a first device, a first message requesting the first device to perform a computing task associated with wireless communication; and means for receiving, from the first device, a second message indicating that the first device fails in performing the computing task.
  • FIG. 9 illustrates a flowchart of a method 900 performed by a first device in accordance with aspects of the present disclosure.
  • the operations of the method 900 may be implemented by a device or its components as described herein.
  • the operations of the method 900 may be performed by a UE or a network entity.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving, from a second device, a first message requesting the first device to perform a computing task associated with wireless communication.
  • the second device may be a network entity, such as a base station (e.g., gNB) or LMF.
  • the first device is a network entity
  • the second device may be an LMF.
  • the operations of 910 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 910 may be performed by a UE 104 or a network entity 102 as described with reference to FIG. 1.
  • the method may include transmitting, to the second device, a second message indicating that the first device fails in performing the computing task.
  • the operations of 920 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 920 may be performed by a UE 104 or a network entity 102 as described with reference to FIG. 1.
  • FIG. 10 illustrates a flowchart of a method performed by a second device in accordance with aspects of the present disclosure.
  • the operations of the method 1000 may be implemented by a device or its components as described herein.
  • the operations of the method 1000 may be performed by a network entity or a server in a core network as described herein.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method may include transmitting, to a first device, a first message requesting the first device to perform a computing task associated with wireless communication.
  • the first device may be a UE.
  • the second device is an LMF
  • the first device may be a UE or a base station (e.g., gNB) .
  • the operations of 1010 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 810 may be performed by a network entity 102 or a server 117 implemented in the core network 106 as described with reference to FIG. 1.
  • the method may include receiving, from the first device, a second message indicating that the first device fails in performing the computing task.
  • the operations of 1020 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1020 may be performed by a network entity 102 or a server 117 implemented in the core network 106 as described with reference to FIG. 1.
  • a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • the functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
  • Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.
  • non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.
  • an article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements.
  • the terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable.
  • a list of items indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) .
  • the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure.
  • the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.
  • a “set” may include one or more elements.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Databases & Information Systems (AREA)
  • Computer Hardware Design (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Divers aspects de la présente divulgation concernent un UE, une entité de réseau, un processeur pour une communication sans fil, des procédés, un appareil pour gérer une tâche informatique infructueuse. Selon un aspect, l'UE reçoit un premier message provenant d'une entité de réseau demandant à l'UE d'effectuer une tâche informatique associée à une communication sans fil. L'UE transmet un second message indiquant que l'UE échoue à effectuer la tâche informatique vers l'entité de réseau. De cette manière, l'UE peut indiquer au réseau qu'il échoue à effectuer la tâche informatique au niveau de l'UE.
PCT/CN2024/073370 2024-01-19 2024-01-19 Procédés de gestion d'une tâche informatique infructueuse Pending WO2024239690A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/073370 WO2024239690A1 (fr) 2024-01-19 2024-01-19 Procédés de gestion d'une tâche informatique infructueuse

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/073370 WO2024239690A1 (fr) 2024-01-19 2024-01-19 Procédés de gestion d'une tâche informatique infructueuse

Publications (1)

Publication Number Publication Date
WO2024239690A1 true WO2024239690A1 (fr) 2024-11-28

Family

ID=93588848

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/073370 Pending WO2024239690A1 (fr) 2024-01-19 2024-01-19 Procédés de gestion d'une tâche informatique infructueuse

Country Status (1)

Country Link
WO (1) WO2024239690A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2025176740A1 (fr) * 2024-02-19 2025-08-28 Telefonaktiebolaget Lm Ericsson (Publ) Mesure de positionnement basée sur un modèle d'intelligence artificielle/d'apprentissage automatique

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109343946A (zh) * 2018-09-19 2019-02-15 长安大学 一种软件定义车联网计算任务迁移和调度方法
CN111212106A (zh) * 2019-12-09 2020-05-29 中国科学院计算机网络信息中心 一种工业互联网环境中边缘计算任务处理与调度方法及装置
CN114095527A (zh) * 2020-08-06 2022-02-25 展讯通信（上海）有限公司 车联网发现过程的计算任务增强方法及相关产品
CN115168031A (zh) * 2022-06-29 2022-10-11 杭州萤石软件有限公司 一种雾计算系统、方法、电子设备及存储介质
WO2023011129A1 (fr) * 2021-08-06 2023-02-09 大唐移动通信设备有限公司 Procédé de positionnement, dispositif de positionnement et support de stockage non transitoire lisible par ordinateur
WO2023018778A1 (fr) * 2021-08-13 2023-02-16 Intel Corporation Support de service informatique de réseau d'accès radio à unités distribuées

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109343946A (zh) * 2018-09-19 2019-02-15 长安大学 一种软件定义车联网计算任务迁移和调度方法
CN111212106A (zh) * 2019-12-09 2020-05-29 中国科学院计算机网络信息中心 一种工业互联网环境中边缘计算任务处理与调度方法及装置
CN114095527A (zh) * 2020-08-06 2022-02-25 展讯通信（上海）有限公司 车联网发现过程的计算任务增强方法及相关产品
WO2023011129A1 (fr) * 2021-08-06 2023-02-09 大唐移动通信设备有限公司 Procédé de positionnement, dispositif de positionnement et support de stockage non transitoire lisible par ordinateur
WO2023018778A1 (fr) * 2021-08-13 2023-02-16 Intel Corporation Support de service informatique de réseau d'accès radio à unités distribuées
CN115168031A (zh) * 2022-06-29 2022-10-11 杭州萤石软件有限公司 一种雾计算系统、方法、电子设备及存储介质

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2025176740A1 (fr) * 2024-02-19 2025-08-28 Telefonaktiebolaget Lm Ericsson (Publ) Mesure de positionnement basée sur un modèle d'intelligence artificielle/d'apprentissage automatique

Similar Documents

Publication Publication Date Title
WO2024159793A1 (fr) Dispositifs et procédés pour des opérations de stockage et de transfert
WO2024239690A1 (fr) Procédés de gestion d'une tâche informatique infructueuse
WO2024093428A1 (fr) Mécanisme pour cho avec des scg candidats
WO2024093414A1 (fr) Mesure de positionnement de phase de porteuse
WO2024148819A1 (fr) Radiomessagerie pour détection d'ue
WO2024164606A1 (fr) Dispositifs et procédés de communication
WO2024234701A1 (fr) Collecte de données assistée par amf pour une lmf
WO2024119856A1 (fr) Positionnement dépendant de la technologie rat amélioré
WO2025213873A1 (fr) Collecte de données de mesure basée sur une couche supérieure
WO2025156295A1 (fr) Continuité de service de multidiffusion ou de diffusion
WO2025107612A1 (fr) Localisation de dispositifs de l'internet des objets ambiants
WO2025241553A1 (fr) Sélection de ressources
WO2025161467A1 (fr) Relais de détection
WO2024093345A1 (fr) Fourniture de prédiction de trajectoire d'ue
WO2024098839A1 (fr) Ajout de trajet indirect pour communication u2n
WO2024109166A1 (fr) Changement de trajet indirect dans un trajet multiple
WO2025107659A1 (fr) Détection coopérative
WO2025246425A1 (fr) Gestion de ressource
WO2025107605A1 (fr) Rapport de faisceaux
WO2024093439A1 (fr) Ajout ou libération de trajet dans un trajet multiple inter-gnb
WO2024159790A1 (fr) Agrégation de bande passante pour positionnement
WO2025107700A1 (fr) Procédé et appareil de prise en charge d'applications d'intelligence artificielle (ia) dans des communications sans fil
WO2024169218A1 (fr) Accès aléatoire pour détection
WO2025123698A1 (fr) Prédiction d'avance temporelle activée par ia/ml
WO2024183315A1 (fr) Positionnement de liaison latérale sur un spectre sans licence

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24809940

Country of ref document: EP

Kind code of ref document: A1