[go: up one dir, main page]

WO2025035789A1 - Détection et mise à jour de dispositif aiot - Google Patents

Détection et mise à jour de dispositif aiot Download PDF

Info

Publication number
WO2025035789A1
WO2025035789A1 PCT/CN2024/085623 CN2024085623W WO2025035789A1 WO 2025035789 A1 WO2025035789 A1 WO 2025035789A1 CN 2024085623 W CN2024085623 W CN 2024085623W WO 2025035789 A1 WO2025035789 A1 WO 2025035789A1
Authority
WO
WIPO (PCT)
Prior art keywords
aiot
aiot device
serving
device discovery
aiotf
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/085623
Other languages
English (en)
Inventor
Lizhuo ZHENG
Haiyan Luo
Mingzeng Dai
Shuigen Yang
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/085623 priority Critical patent/WO2025035789A1/fr
Publication of WO2025035789A1 publication Critical patent/WO2025035789A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/005—Discovery of network devices, e.g. terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Definitions

  • the present disclosure relates to wireless communications, and more specifically to apparatuses and methods for ambient internet of things (AIoT) device discovery and update.
  • AIoT ambient internet of things
  • 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
  • AIoT has been regarded as an important internet of things (IoT) service and is being extensively studied.
  • SA1 is considering devices being either battery-less or with limited energy storage capability (i.e., using a capacitor) and the energy is provided through the harvesting of radio waves, light, motion, heat, or any other power source that could be seen suitable.
  • SA2 has decided to study two main types of AIoT device in Release 19, i.e., device-terminated (DT) and device-originated -device-terminated triggered (DO-DTT) .
  • DT device-terminated
  • DO-DTT device-originated -device-terminated triggered
  • AIoT Topology 1 An AIoT device directly and bidirectionally communicates with a network entity.
  • AIoT Topology 2 an AIoT device communicates bidirectionally with an intermediate node between the AIoT device and a network entity. The intermediate node transfers Ambient IoT data and/or signalling between the network entity and the AIoT device.
  • AIoT Topology 2 a UE can act as the intermediate node which is under the network control.
  • the present disclosure relates to UE reader, apparatuses and methods for AIoT device discovery and update.
  • the first apparatus or the second apparatus may determine association between the at least one AIoT device and the UE. Therefore, when an AIoT application (APP) server sends a service request with a certain target area or a certain device identity (ID) , based on the locally stored location and association information between the UE and the AIoT device, the AIoTF or the AMF will be able to find the corresponding UE and forward the service request for the AIoT device to the UE directly. Based on that, the UE can further send the service request to the target AIoT device. This can greatly help the first apparatus or the second apparatus to handle the AIoT services.
  • APP AIoT application
  • ID device identity
  • Some implementations of a UE described herein may include a processor and a transceiver coupled to the processor, wherein the processor is configured to: perform at least one of an AIoT device discovery procedure or an AIoT device discovery update procedure; and transmit, via the transceiver to a first apparatus or a second apparatus, first information about at least one AIoT device to be served by the UE.
  • the processor is further configured to: receive an AIoT device discovery request via the transceiver from the first apparatus, the second apparatus or an AIoT application server. In such implementations, the processor is configured to perform the AIoT device discovery procedure based on the AIoT device discovery request.
  • the AIoT device discovery request received from the AIoT application server comprises an inventory request.
  • the processor is configured to perform the AIoT device discovery procedure based on the inventory request.
  • the first information about the at least one AIoT device comprises at least one of the following: at least one identity (ID) of the at least one AIoT device, at least one location of the at least one AIoT device, at least one status of the at least one AIoT device, at least one type of the at least one AIoT device, capability of the at least one AIoT device, or a timestamp when the first information is obtained.
  • ID identity
  • the first information about the at least one AIoT device comprises at least one of the following: at least one identity (ID) of the at least one AIoT device, at least one location of the at least one AIoT device, at least one status of the at least one AIoT device, at least one type of the at least one AIoT device, capability of the at least one AIoT device, or a timestamp when the first information is obtained.
  • ID identity
  • the processor is further configured to: transmit, via the transceiver to the first apparatus, second information about the UE associated with the first information about the at least one AIoT device.
  • the second information about the UE comprises at least one of the following: an identity (ID) of the UE, a serving area of the UE, a location of the UE, or capability of the UE.
  • ID an identity of the UE
  • the processor is further configured to: receive an AIoT device discovery update request via the transceiver from the first apparatus, the second apparatus or an AIoT application server. In such implementations, the processor is configured to perform the AIoT device discovery update procedure based on the AIoT device discovery update request.
  • the AIoT device discovery update request received from the AIoT application server comprises an inventory request.
  • the processor is configured to perform the AIoT device discovery update procedure based on the inventory request.
  • the processor is further configured to: before performing the AIoT device discovery update procedure, transmit a first message via the transceiver to the first apparatus or the second apparatus, wherein the first message comprises at least one of the following: an indication indicating that the at least one AIoT device that the UE is serving is updated, a reason why the at least one AIoT device that the UE is serving is updated, an identity (ID) of the UE, a location of the UE, or timestamp when the at least one AIoT device that the UE is serving is updated; and receive an AIoT device discovery update request via the transceiver from the first apparatus or the second apparatus,
  • the AIoT device discovery update request comprises the ID of the UE.
  • the processor is configured to perform the AIoT device discovery update procedure by: performing the AIoT device discovery update procedure based on the AIoT device discovery update request.
  • the processor is configured to transmit the first information about the at least one AIoT device by: transmitting, via the transceiver to the first apparatus or the second apparatus, an AIoT device discovery update result which comprises the first information about the at least one AIoT device.
  • the processor is configured to perform the AIoT device discovery update procedure by: based on determining that the at least one AIoT device that the UE is serving is updated, performing the AIoT device discovery update procedure.
  • the processor is configured to transmit the first information about the at least one AIoT device by: transmitting, via the transceiver to the first apparatus or the second apparatus, an AIoT device discovery update result which comprises the first information about the at least one AIoT device.
  • the AIoT device discovery update result further comprises at least one of the following: second information about the UE associated with the first information about the at least one AIoT device, an indication indicating that the at least one AIoT device that the UE is serving is updated, a reason why the at least one AIoT device that the UE is serving is updated, an identity (ID) of the UE, a location of the UE, or timestamp when the at least one AIoT device that the UE is serving is updated.
  • second information about the UE associated with the first information about the at least one AIoT device an indication indicating that the at least one AIoT device that the UE is serving is updated, a reason why the at least one AIoT device that the UE is serving is updated, an identity (ID) of the UE, a location of the UE, or timestamp when the at least one AIoT device that the UE is serving is updated.
  • Some implementations of a first apparatus described herein may include: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the first apparatus to: determine that at least one AIoT device that a UE is serving is updated; and cause an AIoT device discovery update procedure to be performed.
  • the first apparatus causes the AIoT device discovery update procedure to be performed by transmitting a first message to a second apparatus, wherein the first message comprises at least one of the following: an indication indicating that the at least one AIoT device that the UE is serving is updated, a reason why the at least one AIoT device that the UE is serving is updated, an identity (ID) of the UE, a location of the UE, or timestamp when the at least one AIoT device that the UE is serving is updated; receiving an AIoT device discovery update request from the second apparatus, wherein the AIoT device discovery update request comprises the ID of the UE; and transmitting the AIoT device discovery update request to the UE.
  • the first message comprises at least one of the following: an indication indicating that the at least one AIoT device that the UE is serving is updated, a reason why the at least one AIoT device that the UE is serving is updated, an identity (ID) of the UE, a location of the UE, or timestamp when the at least
  • the first apparatus causes the AIoT device discovery update procedure to be performed by: based on determining that the UE is updated, transmitting an AIoT device discovery update request to the UE, wherein the AIoT device discovery update request comprises the ID of the UE.
  • the first apparatus is further caused to: receive, from the UE, an AIoT device discovery update result which comprises the first information about the at least one AIoT device; and transmit the AIoT device discovery update result to the second apparatus.
  • the AIoT device discovery update result further comprises at least one of the following: second information about the UE associated with the the first information about the at least one AIoT device, a reason why the at least one AIoT device that the UE is serving is updated, an indication indicating that the at least one AIoT device that the UE is serving is updated, timestamp when the at least one AIoT device that the UE is serving is updated, an identity (ID) of the UE, or a location of the UE.
  • the first apparatus is caused to determine that the UE is updated based on determining one of the following: a tracking area update request message is received from the UE; a path switch request is received from a target network entity serving the UE, wherein the path switch request comprises a location of the UE and an identity (ID) of the UE; or a handover required request message is received from a source network entity serving the UE, wherein the handover required request message comprises the ID of the UE.
  • a tracking area update request message is received from the UE
  • a path switch request is received from a target network entity serving the UE, wherein the path switch request comprises a location of the UE and an identity (ID) of the UE
  • ID identity
  • the first apparatus implements a source access and mobility management function (AMF) serving the UE, and the second apparatus implements an AIoT function (AIoTF) .
  • the first apparatus is further caused to transmit at least one of the following to a target AMF serving the UE: an identity (ID) of the second apparatus, an ID of the UE, a location of the UE, or an indication indicating that the at least one AIoT device that the UE is serving is updated.
  • AMF source access and mobility management function
  • AIoTF AIoT function
  • the first apparatus implements a source access and mobility management function (AMF) serving the UE
  • the second apparatus implements an AIoT function (AIoTF)
  • the first apparatus is further caused to transmit at least one of the following to the second apparatus: an indication indicating that the at least one AIoT device that the UE is serving is updated, an identity (ID) of the UE, a location of the UE, or an ID of a target AMF serving the UE.
  • AMF source access and mobility management function
  • AIoTF AIoT function
  • the first apparatus is implemented as an access and mobility management function (AMF) serving the UE, and the second apparatus implements a source AIoT function (AIoTF) serving the UE.
  • AIoTF source AIoT function
  • the first apparatus is further caused to transmit at least one of the following to the second apparatus: an identity (ID) of a target AIoTF serving the UE, an ID of the UE, or a location of the UE.
  • the first apparatus is implemented as an access and mobility management function (AMF) serving the UE, and the second apparatus implements a target AIoT function (AIoTF) serving the UE.
  • the first apparatus is further caused to transmit at least one of the following to the second apparatus: an identity (ID) of a source AIoTF serving the UE, an ID of the UE, or a location of the UE.
  • AMF access and mobility management function
  • AIoTF target AIoT function
  • the first apparatus is further caused to: transmit, to the UE, an AIoT device discovery request to the UE.
  • Some implementations of a second apparatus described herein may include: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the second apparatus to: receive a first message from a first apparatus or a UE serving at least one AIoT device, wherein the first message comprises at least one of the following: an indication indicating that the at least one AIoT device that the UE is serving is updated, a reason why the at least one AIoT device that the UE is serving is updated, an identity (ID) of the UE, a location of the UE, or timestamp when the at least one AIoT device that the UE is serving is updated; and transmit an AIoT device discovery update request to the first apparatus or the UE, wherein the AIoT device discovery update request comprises the ID of the UE; and receive, from the first apparatus or the UE, an AIoT device discovery update result which comprises first information about the at least one AIoT device.
  • the first message comprises at least one of the following: an indication indicating that the at least one AI
  • the second apparatus is further caused to: determine association between the UE and the at least one AIoT device based on second information about the UE and the first information about the at least one AIoT device.
  • the AIoT device discovery update result further comprises at least one of the following: second information about the UE associated with the the first information about the at least one AIoT device, an indication indicating that the at least one AIoT device that the UE is serving is updated, a reason why the at least one AIoT device that the UE is serving is updated, an identity (ID) of the UE, a location of the UE, or timestamp when the at least one AIoT device that the UE is serving is updated.
  • second information about the UE associated with the the first information about the at least one AIoT device an indication indicating that the at least one AIoT device that the UE is serving is updated, a reason why the at least one AIoT device that the UE is serving is updated, an identity (ID) of the UE, a location of the UE, or timestamp when the at least one AIoT device that the UE is serving is updated.
  • the second apparatus is further caused to expose at least one of the following to an AIoT application server: second information about the UE, an indication indicating that the at least one AIoT device that the UE is serving is updated, or a location of the UE.
  • the first apparatus implements a source access and mobility management function (AMF) serving the UE
  • the second apparatus implements an AIoT function (AIoTF)
  • the second apparatus is further caused to receive at least one of the following from the first apparatus or a target AMF serving the UE: an indication indicating that the at least one AIoT device that the UE is serving is updated, an identity (ID) of the UE, a location of the UE, or an ID of the target AMF.
  • AMF source access and mobility management function
  • AIoTF AIoT function
  • the first apparatus is implemented as an access and mobility management function (AMF) serving the UE
  • the second apparatus implements a source AIoT function (AIoTF) serving the UE.
  • AIoTF source AIoT function
  • the second apparatus is further caused to receive at least one of the following from the first apparatus: an identity (ID) of a target AIoTF serving the UE, an ID of the UE, or a location of the UE.
  • the second apparatus is further caused to transmit at least one of the following to a target AIoTF serving the UE: the ID of the UE, the location of the UE, or context information of the UE.
  • the first apparatus is implemented as an access and mobility management function (AMF) serving the UE, and the second apparatus implements a target AIoT function (AIoTF) serving the UE.
  • AIoTF target AIoT function
  • the second apparatus is further caused to receive at least one of the following from the first apparatus: an identity (ID) of a source AIoTF serving the UE, an ID of the UE, or a location of the UE.
  • the second apparatus is further caused to obtain, based on the ID of the UE, context information of the UE from a source AIoTF serving the UE.
  • the second apparatus is further caused to: transmit, to the UE, an AIoT device discovery request to the UE.
  • the second apparatus is further caused to: receive, from an AIoT application server an inventory request.
  • the second apparatus is caused to transmit the AIoT device discovery request by transmitting the inventory request to the UE.
  • Some implementations of a method described herein may include: performing at least one of an AIoT device discovery procedure or an AIoT device discovery update procedure; and transmitting, to a first apparatus or a second apparatus, first information about at least one AIoT device to be served by the UE.
  • Some implementations of a method described herein may include: determining that at least one AIoT device that a user equipment (UE) is serving is updated; and causing an AIoT device discovery update procedure to be performed.
  • UE user equipment
  • Some implementations of a method described herein may include: receiving a first message from a first apparatus or a UE serving at least one AIoT device, wherein the first message comprises at least one of the following: an indication indicating that the at least one AIoT device that the UE is serving is updated, a reason why the at least one AIoT device that the UE is serving is updated, an identity (ID) of the UE, a location of the UE, or timestamp when the at least one AIoT device that the UE is serving is updated; and transmitting an AIoT device discovery update request to the first apparatus or the UE, wherein the AIoT device discovery update request comprises the ID of the UE; and receiving, from the first apparatus or the UE, an AIoT device discovery update result which comprises first information about the at least one AIoT device.
  • the first message comprises at least one of the following: an indication indicating that the at least one AIoT device that the UE is serving is updated, a reason why the at least one AIoT device that the
  • Some implementations of a processor described herein may include at least one memory and a controller coupled with the at least one memory and configured to cause the controller to: perform at least one of an AIoT device discovery procedure or an AIoT device discovery update procedure; and transmit, via the transceiver to a first apparatus or a second apparatus, first information about at least one AIoT device to be served by the UE.
  • Figs. 1A and 1B illustrate an example of a wireless communications system that supports AIoT device discovery and update in accordance with aspects of the present disclosure, respectively;
  • Fig. 2 illustrates an example of a protocol stack for AIoT Topology 2 in accordance with aspects of the present disclosure
  • Fig. 3 illustrates a signaling diagram illustrating an example process that supports AIoT device discovery and update in accordance with aspects of the present disclosure
  • Figs. 4 to 7 illustrate a signaling diagram illustrating an example process that supports AIoT device discovery in accordance with aspects of the present disclosure, respectively;
  • Figs. 8 to 21 illustrate a signaling diagram illustrating an example process that supports AIoT device discovery update in accordance with aspects of the present disclosure, respectively;
  • Fig. 22 illustrates an example of a device that supports AIoT device discovery and update in accordance with some aspects of the present disclosure
  • Fig. 23 illustrates an example of a processor that supports AIoT device discovery and update in accordance with aspects of the present disclosure
  • Figs. 24 to 26 illustrate a flowchart of a method that supports AIoT device discovery and update in accordance with aspects of the present disclosure, respectively.
  • 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 or the like 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. As used herein, the term “and/or” includes any and all combinations of one or more of the listed terms.
  • a UE In AIoT Topology 2, a UE is working between an AIoT device and a network entity to process and transfer the message. It is necessary for the 5GC to know about the information of the UE and then handle the AIoT services. It is proposed that the UE can firstly initiate the registration procedure by itself towards the AIoT function/AMF in the 5GC so that it will have the information about the UE.
  • a UE acting as an intermediate node between an AIoT device and a network entity is also referred to as a UE reader or reader.
  • AIoT function AIoTF
  • AMF access and mobility management function
  • the present disclosure provides a solution that supports AIoT device discovery and update.
  • a UE performs at least one of an AIoT device discovery procedure or an AIoT device discovery update procedure.
  • the UE transmits, to a first apparatus or a second apparatus, first information about at least one AIoT device to be served by the UE.
  • the first apparatus or the second apparatus may determine association between the at least one AIoT device and the UE.
  • an AIoT application (APP) server sends a service request with a certain target area or a certain device identity (ID) , based on the locally stored location and association information between the UE and the AIoT device, the AIoTF or the AMF will be able to find the corresponding UE and forward the service request for the AIoT device to the UE directly. Based on that, the UE can further send the service request to the target AIoT device. This can greatly help the first apparatus or the second apparatus to handle the AIoT services.
  • APP AIoT application
  • ID device identity
  • Fig. 1A illustrates an example of a wireless communications system 100A that supports AIoT device discovery and update in accordance with aspects of the present disclosure.
  • the wireless communications system 100A may include one or more network entities 102 (also referred to as network equipment (NE) ) , one or more terminal devices or UEs 104, a core network 106, and a packet data network 108.
  • the wireless communications system 100A may support various radio access technologies.
  • the wireless communications system 100A 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 100A may be a 5G network, such as an NR network.
  • the wireless communications system 100A 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 100A may support radio access technologies beyond 5G. Additionally, the wireless communications system 100A 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 100A.
  • 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.
  • 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 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 100A.
  • 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 100A.
  • a UE 104 may be mobile in the wireless communications system 100A.
  • 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 100A.
  • 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) .
  • TRPs transmission-reception points
  • 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 DUsor 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 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
  • 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 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 (APP) server 118.
  • APP application
  • 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 100A (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 100A, 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 subcarrier spacing e.g., 15 kHz
  • 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 100A.
  • 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 100A 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) .
  • 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. 1B illustrates an example of a wireless communications system 100B that supports AIoT device discovery and update in accordance with aspects of the present disclosure.
  • Fig. 1B illustrates network entities or network functions (NFs) in the core network 106 as shown in Fig. 1A.
  • NFs network functions
  • the core network 106 may comprise an AMF 120, an AIoTF 122, an authentication server function (AUSF) 124, a unified data management (UDM) 126, a network exposure function (NEF) 128 and an application function (AF) 130.
  • AMF authentication server function
  • AUSF authentication server function
  • UDM unified data management
  • NEF network exposure function
  • AF application function
  • the AIoTF 122 may be a dedicated NF in the 5GC that handles the AIoT related service. Alternatively, the AIoTF 122 may be co-located with the AMF 120.
  • the AIoTF 122 may implement at least one of the following functions:
  • the wireless communications system 100B also comprises the network entity 102, the UE 104 and at least one AIoT device 140.
  • the at least one AIoT device 140 communicates bidirectionally with an intermediate node between the AIoT device 140 and the network entity 102.
  • the intermediate node transfers AIoT data and/or signalling between the network entity 102 and the at least one AIoT device 140.
  • the UE 104 may act as the intermediate node between the AIoT device 140 and the network entity 102.
  • the AF 132 may support interaction with the core network 106 to provide services, such as influencing data routing decisions, policy control functions or providing third-party services to the network.
  • the AF 132 may comprise an AIoT APP server 132.
  • each NF as described above is only exemplary.
  • the AIoTF 122 may be named differently.
  • the wireless communications system 100B may comprise more than one AIoT devices.
  • Fig. 2 illustrates an example of a protocol stack for AIoT Topology 2 in accordance with aspects of the present disclosure.
  • Fig. 2 there can be a direct connection between the UE 104 and the AIoTF 122 in the 5GC via an AIoT Layer.
  • the UE 104 can communicate with each other directly, i.e., the AMF 120 transparently transfers a message between the AIoTF 122 and the UE 104.
  • the UE 104 can have an N1 NAS layer like connection with the AMF 120, and the AMF 120 can have an interface Nxx based on the service-based interface (SBI) with the AIoTF 122, just like the AMF 120 interacting with other 5GC NF.
  • SBI service-based interface
  • Fig. 3 illustrates a signaling diagram illustrating an example process 300 that supports AIoT device discovery and update in accordance with aspects of the present disclosure.
  • the process 300 may involve a first apparatus and a second apparatus.
  • the first apparatus may perform the AMF 120 in Fig. 1B.
  • the first apparatus may perform other network function than the AMF 120 in Fig. 1B.
  • the second apparatus may perform the AIoTF 122 in Fig. 1B.
  • the second apparatus may perform other network function than the AIoTF 122 in Fig. 1B.
  • the process 300 will be described with reference to Fig. 1B.
  • the process 300 may involve the at least one AIoT device 140, the UE 104, the AMF 120 and the AIoTF 122 in Fig. 1B.
  • the UE 104 performs 310 at least one of an AIoT device discovery procedure or an AIoT device discovery update procedure with the at least one AIoT device 140.
  • the UE 104 transmits 320, to the AMF 120, first information about the at least one AIoT device 140 to be served by the UE 104.
  • first information about at least one AIoT device is also referred to as device information or AIoT device information for brevity.
  • the UE 104 transmits 330, to the AIoTF 122, the first information about the at least one AIoT device 140 to be served by the UE 104.
  • the AMF 120 or the AIoTF 122 may determine association between the at least one AIoT device 140 and the UE 104. Therefore, when an AIoT APP server sends a service request indicating a certain target area or a certain device ID, based on the locally stored location and association information between the UE 104 and the AIoT device 140, the AMF 120 or the AIoTF 122 will be able to find the corresponding UE 104 and forward the service request for the AIoT device 140 to the UE 104 directly. Based on that, the UE 104 can further send the service request to the target AIoT device 140. This can greatly help the AMF 120 or the AIoTF 122 to handle the AIoT services.
  • Fig. 4 illustrates a signaling diagram illustrating an example process 400 that supports AIoT device discovery in accordance with aspects of the present disclosure.
  • the process 400 may be considered as an example implementation of the process 300.
  • the process 400 may involve a first apparatus and a second apparatus.
  • the first apparatus may perform the AMF 120 in Fig. 1B.
  • the first apparatus may perform other network function than the AMF 120 in Fig. 1B.
  • the second apparatus may perform the AIoTF 122 in Fig. 1B.
  • the second apparatus may perform other network function than the AIoTF 122 in Fig. 1B.
  • the process 400 will be described with reference to Fig. 1B.
  • the process 400 may involve the at least one AIoT device 140, the UE 104, the AMF 120 and the AIoTF 122, the AUSF 124, the UDM 126, the NEF 128 and the AIoT APP server 132 in Fig. 1B.
  • Fig. 4 illustrates a registration procedure and an AIoT device discovery procedure.
  • the registration procedure may involve actions 410, 415, 420, 425, 430 and 435.
  • the AIoT device discovery procedure may involve actions 440A, 445 and 450.
  • the AIoT reader 104 i.e., UE 104 registers itself at both the AMF 120 and the AIoTF 122.
  • the AIoTF 122, the AMF 120 or the UE 104 can actively initiate the AIoT device discovery procedure to find the at least one AIoT device 140 within a serving area of the UE 104.
  • the AMF 120, the AIoTF 122 and the UE 104 will have first information about the at least one AIoT device 140 within the serving area of the UE 104 and determine association between the UE 104 and the at least one AIoT device 140.
  • the AIoT device discovery procedure may be initiated by UE 104, the AMF 120, or the AIoTF 122 actively.
  • An AIoT device discovery result e.g., the first information about the at least one AIoT device 140 and second information about the associated UE 104, will be provided to the AMF 120 and/or the AIoTF 122 to find the corresponding UE 104 for at least one target AIoT device.
  • the AIoT device discovery result may be exposed to the AIoT APP server 132 as inventory results upon request.
  • the UE 104 transmits an AIoT reader registration request towards the AMF 120.
  • the AIoT reader registration request may comprise registration information of an AIoT reader (such as the UE 104) .
  • the registration information of the UE 104 may comprise a reader indication indicating that the UE 104 acts as an AIoT reader.
  • the registration information of the UE 104 may comprise an ID of the UE 104.
  • the ID of the UE 104 is also referred to as UE ID or reader ID for brevity.
  • the ID of the UE 104 may be an internal UE ID, e.g., subscription permanent identifier (SUPI) .
  • SUPI subscription permanent identifier
  • the registration information of the UE 104 may comprise at least one of the following: a location of the UE 104 (e.g., GPS coordinate) , capability of the UE 104, registration type, and a serving area of the UE 104.
  • a location of the UE 104 e.g., GPS coordinate
  • capability of the UE 104 e.g., registration type
  • a serving area of the UE 104 e.g., a location of the UE 104 (e.g., GPS coordinate)
  • UE location e.g., GPS coordinate
  • UE capability of the UE 104 e.g., registration type
  • serving area of the UE 104 e.g., UE serving area
  • the capability of the UE 104 may comprise at least one of the following: support transmission type (CP/UP) , radio capability, or group support capability.
  • CP/UP support transmission type
  • radio capability e.g., radio capability, or group support capability.
  • the registration type may comprise one of the following: initial registration, periodic registration, or mobility registration.
  • the reader indication may be no longer needed.
  • the AMF 120 receives the registration request from the UE 104, stores the registration information of the UE 104, and selects an AIoTF serving the UE 104 from a network repository function (NRF, which is not shown) based on the location of the UE 104.
  • the NRF returns NF ID of the selected AIoTF (such as the AIoTF 122) to the AMF 120. It is assumed that the AIoTF 122 has registered itself in the NRF, together with its supporting capability.
  • the AMF 120 forwards the AIoT reader registration request to the selected the AIoTF 122.
  • the AIoT reader registration request may comprise registration information of the UE 104.
  • the registration information of the UE 104 may comprise at least one of the following: UE ID, registration type, UE capability, UE serving area or UE location.
  • the AIoTF 122 interacts with the UDM 126 to check and retrieve subscription data of the UE 104. It is assumed that subscription data of the UE 104 and the at least one AIoT device 140 has been pre-configured and stored at the UDM 126. Then, the AIoTF 122 registers for the UE 104, optionally stores UE capability, UE serving area and UE location in the UDM 126.
  • the AIoTF 122 may obtain second information about the UE 104 from the registration information of the UE 104.
  • second information about the UE 104 is also referred to as reader information for brevity.
  • the AIoTF 122 may also store the second information about the UE 104 and create a context for the UE 104 locally.
  • the second information about the UE 104 may comprise at least one of the following: UE ID, UE capability, UE serving area or UE location.
  • the UDM 126 or unified data repository (UDR, which is not shown) stores subscription data of the at least one AIoT device 140, the subscription data of the UE 104 and (AIoT) application subscription data.
  • the application subscription data may comprise configuration information for the AIoT application including credentials.
  • the subscription data of the at least one AIoT device 140 may comprise individual device ID and corresponding credentials.
  • the AIoTF 122 transmits an AIoT reader registration response to the AMF 120 first, together with the UE ID.
  • the AIoT reader registration response may comprise configuration data for the UE 104 acting as AIoT reader.
  • the configuration data for the UE 104 acting as AIoT reader may comprise at least one of the following: AIoTF UP information (e.g., IP address, tunnel endpoint identifier (TEID) ) for potential UP transmission, transmission indication (CP/UP) , aggregation indication, or a discovery indication indicating the UE 104 to perform the AIoT device discovery procedure so that the AIoTF 122 can have the association between the UE and its serving AIoT devices.
  • the AMF 120 will store and forward the information in the AIoT reader registration response to the target UE (such as the UE 104) .
  • the configuration data for the UE 104 acting as AIoT reader may also be provided to the UE 104.
  • the discovery indication may also be transmitted separately at 440A after the registration procedure is finished. Therefore, when the AIoT APP server 132 transmits a message towards some specific device (s) , the AIoTF 122, based on the association or binding between the UE 104 and the at least one AIoT device 140 obtained by the AIoT device discovery procedure, will then know the corresponding UE to contact and forward the message to the UE 104 and then to the at least one AIoT device 140.
  • the AIoT APP server 132 transmits a message towards some specific device (s)
  • the AIoTF 122 based on the association or binding between the UE 104 and the at least one AIoT device 140 obtained by the AIoT device discovery procedure, will then know the corresponding UE to contact and forward the message to the UE 104 and then to the at least one AIoT device 140.
  • the discovery indication may also be transmitted by the AMF 120 separately after the registration of the UE 104 is finished, which will be described with reference to Fig. 5 later.
  • the AMF 120 forwards the AIoT reader registration response and the optional discovery indication to the UE 104.
  • the AMF 120 may also include, in the AIoT reader registration response, an activation indication of the UE 104 as AIoT reader based on an indication from the AIoTF 122 (whether the AIoTF 122 has allowed or not) .
  • the AIoTF 122 may directly transmit the AIoT reader registration response to the UE 104, transparently to the AMF 120.
  • the AIoTF 122 transmits an AIoT device discovery request to the UE 104 to initiate the AIoT device discovery procedure.
  • the AIoT device discovery request may comprise the discovery indication indicating the UE 104 to perform the AIoT device discovery procedure.
  • the configuration information of the AIoT device discovery procedure may be the same as that of the inventory procedure configured by the AIoT APP server 132, or pre-configured. If the AIoT APP server 132 initiates the inventory procedure, the configuration information will be transmitted to the UE 104 within the AIoT device discovery request.
  • the UE 104 performs the AIoT device discovery procedure towards at least one AIoT device (such as the AIoT device 140) within its serving area, using a process like Paging or random access channel (RACH) to obtain the first information about the at least one AIoT device 140.
  • at least one AIoT device such as the AIoT device 140
  • RACH random access channel
  • the first information about the at least one AIoT device 140 may comprise at least one of the following: at least one ID of the at least one AIoT device 140, at least one location of the at least one AIoT device 140, at least one status of the at least one AIoT device 140, at least one type of the at least one AIoT device 140, capability of the at least one AIoT device 140, or a timestamp when the first information is obtained.
  • At least one ID of the at least one AIoT device 140 is also referred to as device ID for brevity.
  • the device ID may comprise group-based ID or individual IDs of AIoT devices.
  • At least one location of the at least one AIoT device 140 is also referred to as device location for brevity.
  • At least one status of the at least one AIoT device 140 is also referred to as device status for brevity.
  • the device status may comprise one of the following: enable, disable, or permanently disable.
  • At least one type of the at least one AIoT device 140 is also referred to as device type for brevity. Capability of the at least one AIoT device 140 is also referred to as device capability for brevity.
  • the UE 104 transmits an AIoT device discovery report to either the AMF 120, or the AIoTF 122 directly.
  • the AIoT device discovery report may comprise the first information about the at least one AIoT device 140. In some implementations, the AIoT device discovery report may comprise the first information about the at least one AIoT device 140 associated with second information about the UE 104. For example, the AIoT device discovery report may comprise the first information about the at least one AIoT device 140 associated with the reader ID (such as the ID of the UE 104)
  • the AIoT device discovery report may comprise at least one of the following: device ID, device location, device status, device type, and so on.
  • the AIoTF 122 may obtain second information about the UE 104 from the registration information of the UE 104.
  • the AIoTF 122 may determine association between the UE 104 and the at least one AIoT device 140 based on the first information about the at least one AIoT device 140 and the second information about the UE 104.
  • the association between the UE 104 and the at least one AIoT device 140 may be in the form of UE ID # 1/device ID #1, device ID #2, ..., device ID #N.
  • the association between the UE 104 and the at least one AIoT device 140 may be in the form of UE ID # 1/device ID #1, device ID #2, ..., device ID #N, together with other information about the UE 104 and the at least one AIoT device, e.g., UE location and device location, UE serving area, device type, device status, UE capability, and so on.
  • the AIoTF 122 may store the association between the UE 104 and the at least one AIoT device 140 locally.
  • the AIoT APP server 132 transmits a service request with certain device ID or device location to the core network 106, the AIoTF 122 or the AMF 120 can refer to the locally saved association to find the corresponding UE and continue to transmit the message to it.
  • the AIoTF 122 may interact with the AUSF 124, the UDM 126 to authenticate the device ID using the credential.
  • This credential can be provided to the at least one AIoT device 140.
  • Fig. 5 illustrates a signaling diagram illustrating an example process 500 that supports AIoT device discovery in accordance with aspects of the present disclosure.
  • the process 500 may be considered as an example implementation of the process 300.
  • the process 500 may involve a first apparatus and a second apparatus.
  • the first apparatus may perform the AMF 120 in Fig. 1B.
  • the first apparatus may perform other network function than the AMF 120 in Fig. 1B.
  • the second apparatus may perform the AIoTF 122 in Fig. 1B.
  • the second apparatus may perform other network function than the AIoTF 122 in Fig. 1B.
  • the process 500 will be described with reference to Fig. 1B.
  • the process 500 may involve the at least one AIoT device 140, the UE 104, the AMF 120 and the AIoTF 122, the AUSF 124, the UDM 126, the NEF 128 and the AIoT APP server 132 in Fig. 1B.
  • the process 500 is similar to the process 400.
  • the process 500 is different from the process 400 in an action 440B.
  • the AMF 120 transmits an AIoT device discovery request to the UE 104 to initiate the AIoT device discovery procedure.
  • the AIoT device discovery request may comprise the discovery indication.
  • the configuration information of the AIoT device discovery procedure may be the same as that of the inventory procedure configured by the AIoT APP server 132, or pre-configured.
  • Fig. 6 illustrates a signaling diagram illustrating an example process 600 that supports AIoT device discovery in accordance with aspects of the present disclosure.
  • the process 600 may be considered as an example implementation of the process 300.
  • the process 600 may involve a first apparatus and a second apparatus.
  • the first apparatus may perform the AMF 120 in Fig. 1B.
  • the first apparatus may perform other network function than the AMF 120 in Fig. 1B.
  • the second apparatus may perform the AIoTF 122 in Fig. 1B.
  • the second apparatus may perform other network function than the AIoTF 122 in Fig. 1B.
  • the process 600 will be described with reference to Fig. 1B.
  • the process 600 may involve the at least one AIoT device 140, the UE 104, the AMF 120 and the AIoTF 122, the AUSF 124, the UDM 126, the NEF 128 and the AIoT APP server 132 in Fig. 1B.
  • the process 600 is similar to the process 400.
  • the process 600 is different from the process 400 in an action 440C.
  • the UE 104 determines to initiate the AIoT device discovery procedure by itself. For example, the UE 104 may determine to initiate the AIoT device discovery procedure based on the per-configured configuration information of the AIoT device discovery procedure, or be the same as that of the inventory procedure configured by the AIoT APP server 132.
  • the AIoT APP server 132 may trigger an inventory request, and the inventory request can be included in an AIoT device discovery request sent to the UE 104.
  • the UE 104 may perform the AIoT device discovery procedure based on the inventory request.
  • an inventory result can be included in the AIoT device discovery report.
  • the AIoTF 122 can expose the inventory result to the APP server 132. This will be described with reference to Fig. 7.
  • Fig. 7 illustrates a signaling diagram illustrating an example process 700 that supports AIoT device discovery in accordance with aspects of the present disclosure.
  • the process 700 may be considered as an example implementation of the process 300.
  • the process 700 may involve a first apparatus and a second apparatus.
  • the first apparatus may perform the AMF 120 in Fig. 1B.
  • the first apparatus may perform other network function than the AMF 120 in Fig. 1B.
  • the second apparatus may perform the AIoTF 122 in Fig. 1B.
  • the second apparatus may perform other network function than the AIoTF 122 in Fig. 1B.
  • the process 700 will be described with reference to Fig. 1B.
  • the process 700 may involve the at least one AIoT device 140, the UE 104, the AMF 120 and the AIoTF 122, the AUSF 124, the UDM 126, the NEF 128 and the AIoT APP server 132 in Fig. 1B.
  • Fig. 7 illustrates an AIoT device discovery procedure triggered by the AIoT APP server 132 as an inventory request procedure.
  • the registration procedure of the UE 104 may be performed as described with reference to Fig. 4.
  • Fig. 7 does not illustrate the registration procedure of the UE 104.
  • the AIoT reader 104 i.e., UE 104 registers itself at both the AMF 120 and the AIoTF 122.
  • the AIoTF 122 may expose 710 the second information about the UE 104 to the AIoT APP server 132 via the NEF 128, e.g., in the external UE ID format, together with the location (may be transferred into external location information) of the UE 104.
  • the AIoT APP server 132 may trigger an inventory request procedure to know the AIoT devices by transmitting an inventory request towards the AIoTF 122.
  • the AIoT APP server 132 may transmit the inventory request together with the reader ID, a target area, inventory filtering criteria, inventory timer and destination report address.
  • the inventory filtering criteria may comprise certain filtering principles for the inventory results, of which can be performed by the UE 104 or the AIoTF 122, e.g., device type (DT, DO-DTT) , device location, device status (enable/disable/permanently disable) . Only those devices matching the inventory filtering criteria will be reported to the AIoT APP server 132.
  • the inventory timer is set to limit the inventory implementation duration at UE 104 side. When the timer is expired, the UE 104 will not wait for more response from the at least one AIoT device and may aggregate the responses and transmit them to the AIoTF 122 for further actions.
  • the NEF 128 When the NEF 128 receives the inventory request, it will interact with the UDM 126 and the AUSF 124 to performing at least one of the following: authorizing the inventory request based on the pre-stored subscription information of the APP; authenticating the reader ID (if any) ; or translating the external UE ID (e.g., Generic Public Subscription Identifier (GPSI) ) into internal UE ID (SUPI) ; or translating the external location information into internal location information.
  • GPSI Generic Public Subscription Identifier
  • the NEF 128 will interact with the NRF to select an AIoTF (such as the AIoTF 122) based on the reader ID and/or the target area. Then, the NEF 128 forwards the inventory request towards the selected AIoTF 122.
  • an AIoTF such as the AIoTF 122
  • the AIoTF 122 transmits the inventory request towards the UE 104 either based on the target area, or the reader ID.
  • the UE 104 may initiate the AIoT device discovery procedure to get the response from at least one AIoT device.
  • the UE 104 transmits an AIoT device discovery report to the AIoTF 122.
  • the AIoT device discovery report may comprise an inventory response.
  • the inventory response may comprise the first information about the at least one AIoT device 140.
  • the inventory response may comprise at least one of the following: device ID, device location, device status, device type, device capability, or a timestamp when the first information is obtained.
  • the AIoTF 122 authenticates the device ID with the AUSF 124 and the UDM 126.
  • the AIoTF 122 may obtain the second information about the UE 104 from the registration information of the UE 104.
  • the AIoTF 122 may determine association between the UE 104 and the at least one AIoT device 140 based on the first information about the at least one AIoT device 140 and the second information about the UE 104.
  • the AIoTF 122 stores the association between the UE 104 and the at least one AIoT device 140 locally and exposes the inventory result to the AIoT APP server 132 via the NEF 128.
  • the AMF 120 and/or the AIoTF 122 After the registration procedure of the UE 104 and the AIoT device discovery procedure, the AMF 120 and/or the AIoTF 122 has already stored the association between the UE 104 and the at least one AIoT device 140 within its serving area. Therefore, when device ID (s) is provided by the AIoT APP server 132 for certain services, the AMF 120 and/or the AIoTF 122 can immediately determine which UE to forward the message to.
  • the at least one AIoT device 140 when the UE 104 is serving as an AIoT reader, there is a possibility that the at least one AIoT device 140 within the serving area of the UE 104 could be updated or change.
  • the update or change of the at least one AIoT device 140 may lead to the change of the association between the UE 104 and the at least one AIoT device 140.
  • UE mobility may lead to the update or change of the at least one AIoT device 140.
  • the UE 104 may move to another place (e.g., out of certain area limit that leads to the unreachability of the at least one AIoT device 140) .
  • This kind of UE mobility will lead to the update or change of the at least one AIoT device 140 that UE is serving and then lead to the change of the association between the UE 104 and the at least one AIoT device 140.
  • the UE 104 may need an AIoT device discovery update procedure to check the current serving AIoT devices situation.
  • All these kinds of changes may alter the association between the UE 104 and the at least one AIoT device 140, and at least one of the AMF 120 and the AIoTF 122 needs to be notified about the changes and use the AIoT device discovery update procedure or inventory update procedure to obtain the updated association so that it can always find the exact UE serving at least one AIoT device.
  • Fig. 8 illustrates a signaling diagram illustrating an example process 800 that supports AIoT device discovery update in accordance with aspects of the present disclosure.
  • the process 800 may be considered as an example implementation of the process 300.
  • the process 800 may involve a first apparatus and a second apparatus.
  • the first apparatus may perform the AMF 120 in Fig. 1B.
  • the first apparatus may perform other network function than the AMF 120 in Fig. 1B.
  • the second apparatus may perform the AIoTF 122 in Fig. 1B.
  • the second apparatus may perform other network function than the AIoTF 122 in Fig. 1B.
  • the process 800 will be described with reference to Fig. 1B.
  • the process 800 may involve the UE 104, the AMF 120 and the AIoTF 122 in Fig. 1B as well as at least one AIoT device 150 which is not shown in Fig. 1B.
  • the UE 104 may trigger an AIoT device discovery update procedure by transmitting a first message to the AMF 120 or the AIoTF 122 based on subscription from the AMF 120 or the AIoTF 122, or based on pre-configuration.
  • the process 800 may be related to UE mobility or other factors such as radio link failure.
  • the registration procedure of the UE 104 may be performed as described with reference to Fig. 4 and an AIoT device discovery procedure may be performed as described with reference to Figs. 4 to 7.
  • Fig. 8 does not illustrate the registration procedure of the UE 104 and the AIoT device discovery procedure.
  • the UE 104 determines 805 that the at least one AIoT device 140 that the UE 104 is serving is updated.
  • the AIoTF 122 or the AMF 120 may subscribe to the UE 104 for the UE location and/or the UE status after registration of the UE 104. For example, if the UE 104 moves to a certain place that has beyond certain area limit which leads to the unreachability of the at least one AIoT device 140, the UE 104 may determine, based on the subscription or configuration from the AIoTF 122 or the AMF 120, that the at least one AIoT device 140 that the UE 104 is serving is updated.
  • the UE 104 may determine, based on pre-configuration, that the at least one AIoT device 140 that the UE 104 is serving is updated.
  • the UE 104 transmits 810 a first message to the AMF 120.
  • the first message may comprise an indication indicating that the at least one AIoT device 140 that the UE 104 is serving is updated.
  • the indication is also referred to as a device update indication.
  • the first message may comprise a reason why the at least one AIoT device 140 that the UE 104 is serving is updated.
  • the reason is also referred to as an update reason.
  • the first message may comprise at least one of the following: an ID of the UE 104 (i.e., UE ID) , a location of the UE 104 (i.e., UE location) , or timestamp when the at least one AIoT device 140 that the UE 104 is serving is updated.
  • an ID of the UE 104 i.e., UE ID
  • a location of the UE 104 i.e., UE location
  • timestamp when the at least one AIoT device 140 that the UE 104 is serving is updated.
  • the AIoTF 122 if a different UE location associated with the ID of the UE 104 is sent to the AIoTF 122, there may be no need for the update reason and the discovery update indication to be provided.
  • the AMF 120 Upon receiving the first message, the AMF 120 forwards 820 the first message to the AIoTF 122.
  • the UE 104 may transmit the first message to the AIoTF 122 directly (transparent to the AMF 120) based on subscription from the AIoTF 122 or pre-configuration.
  • the AIoTF 122 Upon receiving the first message, the AIoTF 122 transmits 830 an AIoT device discovery update request to the AMF 120.
  • the AMF 120 Upon receiving the AIoT device discovery update request, the AMF 120 forwards 840 the AIoT device discovery update request to the UE 104.
  • the AIoTF 122 may transmit the AIoT device discovery update request to the UE 104 directly.
  • the AIoT device discovery update request may comprise the ID of the UE 104.
  • the AIoT device discovery update request may comprise at least one of the following: discovery criteria, discovery timer, or discovery report address.
  • the UE 104 performs 850, based on the AIoT device discovery update request, the AIoT device discovery update procedure towards the at least one AIoT device 150.
  • the at least one AIoT device 150 may be the same as or different from the at least one AIoT device 140.
  • the UE 104 may obtain first information about the at least one AIoT device 150.
  • the first information about the at least one AIoT device 150 may comprise at least one of the following: device ID, device location, or device status.
  • the UE 104 may transmit 860 an AIoT device discovery update result to the AMF 120.
  • the AIoT device discovery update result may comprise the first information about the at least one AIoT device 150.
  • the AIoT device discovery update result may comprise timestamp when the at least one AIoT device 140 is updated.
  • the AMF 120 Upon receiving the AIoT device discovery update result, the AMF 120 forwards 870 the AIoT device discovery update result to the AIoTF 122.
  • the UE 104 may transmit the AIoT device discovery update result to the AIoTF 122 directly (transparent to the AMF 120) .
  • the AIoTF 122 may interact 880 with the AUSF 124 and the UDM 126 to authenticate and authorize the at least one AIoT device 150.
  • the AIoTF 122 may update the first information about the at least one AIoT device 140 with the first information about the at least one AIoT device 150.
  • the AIoTF 122 may determine association between the UE 104 and the at least one AIoT device 150 based on the first information about the at least one AIoT device 150 and the second information about the UE 104.
  • the AIoTF 122 may store the association between the UE 104 and the at least one AIoT device 150 locally, and delete the association between the UE 104 and the at least one AIoT device 140. In other words, the AIoTF 122 may update the association between the UE 104 and the at least one AIoT device 140 with the association between the UE 104 and the at least one AIoT device 150.
  • the AIoTF 122 may report the first message to the AIoT APP server 132 via the NEF 128.
  • the first message may comprise at least one of the following: the device update indication, the update reason, an ID of the UE 104 (i.e., UE ID) , a location of the UE 104 (i.e., UE location) , or timestamp when the at least one AIoT device 140 that the UE 104 is serving is updated.
  • the AIoT APP server 132 can determine whether to initiate the inventory update procedure for this situation or not.
  • Fig. 9 illustrates a signaling diagram illustrating an example process 900 that supports AIoT device discovery update in accordance with aspects of the present disclosure.
  • the process 900 may be considered as an example implementation of the process 300.
  • the process 900 may involve a first apparatus and a second apparatus.
  • the first apparatus may perform the AMF 120 in Fig. 1B.
  • the first apparatus may perform other network function than the AMF 120 in Fig. 1B.
  • the second apparatus may perform the AIoTF 122 in Fig. 1B.
  • the second apparatus may perform other network function than the AIoTF 122 in Fig. 1B.
  • the process 900 will be described with reference to Fig. 1B.
  • the process 900 may involve the UE 104, the AMF 120 and the AIoTF 122 in Fig. 1B as well as at least one AIoT device 150 which is not shown in Fig. 1B.
  • the UE 104 may trigger an AIoT device discovery update procedure by transmitting a first message to the AMF 120 or the AIoTF 122 based on subscription from the AMF 120 or the AIoTF 122, or based on pre-configuration.
  • the process 900 may be related to UE mobility or other factors such as radio link failure.
  • the registration procedure of the UE 104 may be performed as described with reference to Fig. 4 and an AIoT device discovery procedure may be performed as described with reference to Figs. 4 to 7.
  • Fig. 9 does not illustrate the registration procedure of the UE 104 and the AIoT device discovery procedure.
  • the UE 104 determines 905 that the at least one AIoT device 140 that the UE 104 is serving is updated.
  • the UE 104 may determine, based on the subscription from the AIoTF 122 or the AMF 120, that the at least one AIoT device 140 that the UE 104 is serving is updated. Alternatively, the UE 104 may determine, based on pre-configuration, that the at least one AIoT device 140 that the UE 104 is serving is updated.
  • the UE 104 performs 910 the AIoT device discovery update procedure towards the at least one AIoT device 150.
  • the UE 104 may obtain first information about the at least one AIoT device 150.
  • the first information about the at least one AIoT device 150 may comprise at least one of the following: device ID, device location, or device status.
  • the UE 104 may transmit 920 an AIoT device discovery update result to the AMF 120.
  • the AIoT device discovery update result may comprise the first information about the at least one AIoT device 150.
  • the AIoT device discovery update result may further comprise the second information about the UE 104 associated with the first information about the at least one AIoT device 150.
  • the AIoT device discovery update result may further comprise at least one of the following: the update indication, the update reason, the UE ID, the UE location, or timestamp when the at least one AIoT device 140 that the UE 104 is serving is updated.
  • the AMF 120 Upon receiving the AIoT device discovery update result, the AMF 120 forwards 930 the AIoT device discovery update result to the AIoTF 122.
  • the UE 104 may transmit the AIoT device discovery update result to the AIoTF 122 directly (transparent to the AMF 120) .
  • the AIoTF 122 may interact 940 with the AUSF 124 and the UDM 126 to authenticate and authorize the at least one AIoT device 150. In turn, the AIoTF 122 may update the first information about the at least one AIoT device 140 with the first information about the at least one AIoT device 150. The AIoTF 122 may determine association between the UE 104 and the at least one AIoT device 150 based on the first information about the at least one AIoT device 150 and the second information about the UE 104.
  • the AIoTF 122 may store the association between the UE 104 and the at least one AIoT device 150 locally, and delete the association between the UE 104 and the at least one AIoT device 140. In other words, the AIoTF 122 may update the association between the UE 104 and the at least one AIoT device 140 with the association between the UE 104 and the at least one AIoT device 150.
  • the AMF may initiate the AIoT device discovery update procedure. This will be described with reference to Figs. 10 to 12.
  • Fig. 10 illustrates a signaling diagram illustrating an example process 1000 that supports AIoT device discovery update in accordance with aspects of the present disclosure.
  • the process 1000 may involve a first apparatus.
  • the first apparatus may perform the AMF 120 in Fig. 1B.
  • the first apparatus may perform other network function than the AMF 120 in Fig. 1B.
  • the process 1000 will be described with reference to Fig. 1B.
  • the process 1000 may involve the UE 104, the AMF 120 in Fig. 1B as well as at least one AIoT device 150 which is not shown in Fig. 1B.
  • the AMF 120 determine 1010 that at least one AIoT device 140 that the UE 104 is serving is updated.
  • the AMF 120 causes 1020 an AIoT device discovery update procedure to be performed.
  • Fig. 11 illustrates a signaling diagram illustrating an example process 1100 that supports AIoT device discovery update in accordance with aspects of the present disclosure.
  • the process 1100 may be considered as an example implementation of the process 300 or the process 1000.
  • the process 1100 may involve a first apparatus and a second apparatus.
  • the first apparatus may perform the AMF 120 in Fig. 1B.
  • the first apparatus may perform other network function than the AMF 120 in Fig. 1B.
  • the second apparatus may perform the AIoTF 122 in Fig. 1B.
  • the second apparatus may perform other network function than the AIoTF 122 in Fig. 1B.
  • the process 1100 will be described with reference to Fig. 1B.
  • the process 1100 may involve the UE 104, the AMF 120 and the AIoTF 122 in Fig. 1B as well as at least one AIoT device 150 which is not shown in Fig. 1B.
  • the AMF 120 may trigger an AIoT device discovery update procedure by transmitting a first message to the AIoTF 122 based on subscription from the AIoTF 122, or based on pre-configuration.
  • the process 1100 may be related to UE mobility or other factors such as radio link failure.
  • the registration procedure of the UE 104 may be performed as described with reference to Fig. 4 and an AIoT device discovery procedure may be performed as described with reference to Figs. 4 to 7.
  • Fig. 11 does not illustrate the registration procedure of the UE 104 and the AIoT device discovery procedure.
  • the AMF 120 determines 1105 that the at least one AIoT device 140 that the UE 104 is serving is updated.
  • the AIoTF 122 may subscribe to the AMF 120 for the UE location and/or the UE status by providing the UE ID (e.g., SUPI) after registration of the UE 104. For example, if the UE 104 moves to a certain place that has beyond certain area limit which leads to the unreachability of the at least one AIoT device 140, the AMF 120 may determine, based on the subscription from the AIoTF 122, that the at least one AIoT device 140 that the UE 104 is serving is updated.
  • the UE ID e.g., SUPI
  • the AMF 120 may determine, based on pre-configuration, that the at least one AIoT device 140 that the UE 104 is serving is updated.
  • the AMF 120 may determine that the at least one AIoT device 140 that the UE 104 is serving is updated.
  • the AMF 120 may determine that the at least one AIoT device 140 that the UE 104 is serving is updated.
  • the path switch request may comprise the location of the UE 104 and the ID of the UE 104.
  • the AMF 120 may determine that the at least one AIoT device 140 that the UE 104 is serving is updated.
  • the handover required request message may comprise the ID of the UE 104.
  • the AIoTF 122 may set up a timer, or the update periodicity for the UE 104, and the AMF 120 may determine that the at least one AIoT device 140 that the UE 104 is serving is updated accordingly.
  • the AMF 120 causes the AIoT device discovery update procedure to be performed by transmitting 910 a first message to the AIoTF 122.
  • the first message may comprise an indication indicating that the at least one AIoT device 140 that the UE 104 is serving is updated.
  • the indication is also referred to as a device update indication.
  • the first message may comprise a reason why the at least one AIoT device 140 that the UE 104 is serving is updated.
  • the reason is also referred to as an update reason.
  • the first message may comprise at least one of the following: an ID of the UE 104 (i.e., UE ID) , a location of the UE 104 (i.e., UE location) , or timestamp when the at least one AIoT device 140 that the UE 104 is serving is updated.
  • an ID of the UE 104 i.e., UE ID
  • a location of the UE 104 i.e., UE location
  • timestamp when the at least one AIoT device 140 that the UE 104 is serving is updated.
  • the AIoTF 122 if a different UE location associated with the ID of the UE 104 is sent to the AIoTF 122, there may be no need for the update reason and the discovery update indication to be provided.
  • the AIoTF 122 Upon receiving the first message, the AIoTF 122 transmits 1120 an AIoT device discovery update request to the AMF 120.
  • the AMF 120 Upon receiving the AIoT device discovery update request, the AMF 120 forwards 1130 the AIoT device discovery update request to the UE 104.
  • the AIoTF 122 may transmit the AIoT device discovery update request to the UE 104 directly.
  • the AIoT device discovery update request may comprise the ID of the UE 104.
  • the AIoT device discovery update request may comprise at least one of the following: discovery criteria, discovery timer, or discovery report address.
  • the UE 104 performs 1140, based on the AIoT device discovery update request, the AIoT device discovery update procedure towards the at least one AIoT device 150.
  • the at least one AIoT device 150 may be the same as or different from the at least one AIoT device 140.
  • the UE 104 may obtain first information about the at least one AIoT device 150.
  • the first information about the at least one AIoT device 150 may comprise at least one of the following: device ID, device location, or device status.
  • the UE 104 may transmit 1150 an AIoT device discovery update result to the AMF 120.
  • the AIoT device discovery update result may comprise the first information about the at least one AIoT device 150.
  • the AIoT device discovery update result may comprise timestamp when the at least one AIoT device 140 is updated.
  • the AMF 120 Upon receiving the AIoT device discovery update result, the AMF 120 forwards 1160 the AIoT device discovery update result to the AIoTF 122.
  • the UE 104 may transmit the AIoT device discovery update result to the AIoTF 122 directly (transparent to the AMF 120) .
  • the AIoTF 122 may interact 1170 with the AUSF 124 and the UDM 126 to authenticate and authorize the at least one AIoT device 150. In turn, the AIoTF 122 may update the first information about the at least one AIoT device 140 with the first information about the at least one AIoT device 150. The AIoTF 122 may determine association between the UE 104 and the at least one AIoT device 150 based on the first information about the at least one AIoT device 150 and the second information about the UE 104.
  • the AIoTF 122 may store the association between the UE 104 and the at least one AIoT device 150 locally, and delete the association between the UE 104 and the at least one AIoT device 140. In other words, the AIoTF 122 may update the association between the UE 104 and the at least one AIoT device 140 with the association between the UE 104 and the at least one AIoT device 150.
  • Fig. 12 illustrates a signaling diagram illustrating an example process 1200 that supports AIoT device discovery update in accordance with aspects of the present disclosure.
  • the process 1200 may be considered as an example implementation of the process 300 or the process 1000.
  • the process 1200 may involve a first apparatus and a second apparatus.
  • the first apparatus may perform the AMF 120 in Fig. 1B.
  • the first apparatus may perform other network function than the AMF 120 in Fig. 1B.
  • the second apparatus may perform the AIoTF 122 in Fig. 1B.
  • the second apparatus may perform other network function than the AIoTF 122 in Fig. 1B.
  • the process 1200 will be described with reference to Fig. 1B.
  • the process 1200 may involve the UE 104, the AMF 120 and the AIoTF 122 in Fig. 1B as well as at least one AIoT device 150 which is not shown in Fig. 1B.
  • the AMF 120 may initiate an AIoT device discovery update procedure by transmitting an AIoT device discovery update request to the UE 104 based on subscription from the AIoTF 122 or pre-configuration.
  • the process 1200 may be related to UE mobility or other factors such as radio link failure.
  • the registration procedure of the UE 104 may be performed as described with reference to Fig. 4 and an AIoT device discovery procedure may be performed as described with reference to Figs. 4 to 7.
  • Fig. 12 does not illustrate the registration procedure of the UE 104 and the AIoT device discovery procedure.
  • the AMF 120 determines 1205 that the at least one AIoT device 140 that the UE 104 is serving is updated.
  • the AMF 120 may determine, based on the subscription from the AIoTF 122, that the at least one AIoT device 140 that the UE 104 is serving is updated. Alternatively, the AMF 120 may determine, based on pre-configuration, that the at least one AIoT device 140 that the UE 104 is serving is updated.
  • the AMF 120 may determine that the at least one AIoT device 140 that the UE 104 is serving is updated.
  • the AMF 120 may determine that the at least one AIoT device 140 that the UE 104 is serving is updated.
  • the path switch request may comprise the location of the UE 104 and the ID of the UE 104.
  • the AMF 120 may determine that the at least one AIoT device 140 that the UE 104 is serving is updated.
  • the handover required request message may comprise the ID of the UE 104.
  • the AIoTF 122 may set up a timer, or the update periodicity for the UE 104, and the AMF 120 may determine that the at least one AIoT device 140 that the UE 104 is serving is updated accordingly.
  • the AMF 120 transmits 1210 the AIoT device discovery update request to the UE 104.
  • the AIoT device discovery update request may comprise the ID of the UE 104.
  • the AIoT device discovery update request may comprise at least one of the following: discovery criteria, discovery timer, or discovery report address.
  • the UE 104 performs 1220 the AIoT device discovery update procedure towards the at least one AIoT device 150 based on the AIoT device discovery update request.
  • the UE 104 may obtain first information about the at least one AIoT device 150.
  • the first information about the at least one AIoT device 150 may comprise at least one of the following: device ID, device location, or device status.
  • the UE 104 may transmit 1230 an AIoT device discovery update result to the AMF 120.
  • the AIoT device discovery update result may comprise the first information about the at least one AIoT device 150.
  • the AIoT device discovery update result may further comprise the second information about the UE 104 associated with the first information about the at least one AIoT device 150.
  • the AIoT device discovery update result may further comprise at least one of the following: the update indication, the update reason, the UE ID, the UE location, or timestamp when the at least one AIoT device 140 that the UE 104 is serving is updated.
  • the AMF 120 Upon receiving the AIoT device discovery update result, the AMF 120 forwards 1240 the AIoT device discovery update result to the AIoTF 122.
  • the UE 104 may transmit the AIoT device discovery update result to the AIoTF 122 directly (transparent to the AMF 120) .
  • the AIoTF 122 may interact 1250 with the AUSF 124 and the UDM 126 to authenticate and authorize the at least one AIoT device 150. In turn, the AIoTF 122 may update the first information about the at least one AIoT device 140 with the first information about the at least one AIoT device 150. The AIoTF 122 may determine association between the UE 104 and the at least one AIoT device 150 based on the first information about the at least one AIoT device 150 and the second information about the UE 104.
  • the AIoTF 122 may store the association between the UE 104 and the at least one AIoT device 150 locally, and delete the association between the UE 104 and the at least one AIoT device 140. In other words, the AIoTF 122 may update the association between the UE 104 and the at least one AIoT device 140 with the association between the UE 104 and the at least one AIoT device 150.
  • the update configuration could also be sent, together with the ID of the UE, such as the reporting address, update filtering criteria, target location, etc.
  • the AMF 120 may implement a source AMF serving the UE 104. This will be described with reference to Figs. 13 to 15.
  • Fig. 13 illustrates a signaling diagram illustrating an example process 1300 that supports AIoT device discovery update in accordance with aspects of the present disclosure.
  • the process 1300 may be considered as an example implementation of the process 300 or the process 1000.
  • the process 1300 may involve a first apparatus and a second apparatus.
  • the first apparatus may perform the AMF 120 in Fig. 1B.
  • the first apparatus may perform other network function than the AMF 120 in Fig. 1B.
  • the second apparatus may perform the AIoTF 122 in Fig. 1B.
  • the second apparatus may perform other network function than the AIoTF 122 in Fig. 1B.
  • the process 1300 will be described with reference to Fig. 1B.
  • the process 1300 may involve the UE 104, the AMF 120 and the AIoTF 122 in Fig. 1B as well as an AMF 160 which is not shown in Fig. 1B.
  • the UE 104 has moved to a serving area of a different AMF from the AMF 120, but still within the same serving area of the AIoTF 122.
  • the AMF 120 may implement a source AMF (S-AMF) 120 serving the UE 104 and the AMF 160 may implement a target AMF (T-AMF) 160 serving the UE 104.
  • S-AMF source AMF
  • T-AMF target AMF
  • the registration procedure of the UE 104 may be performed as described with reference to Fig. 4 and an AIoT device discovery procedure may be performed as described with reference to Figs. 4 to 7.
  • Fig. 13 does not illustrate the registration procedure of the UE 104 and the AIoT device discovery procedure.
  • the source AMF 120 receives a handover required request message from the source network entity.
  • the handover required request message may comprise the ID of the UE 104.
  • the target AMF 160 receives the location of the UE 104 from the target network entity via handover notify message.
  • the source AMF 120 may transmit 1310 at least one of the following to the target AMF 160: an ID of the AIoTF 122 (i.e., AIoTF ID) , the UE ID, the UE location, or the device update indication.
  • an ID of the AIoTF 122 i.e., AIoTF ID
  • the UE ID the UE location
  • the device update indication the device update indication
  • the target AMF 160 may transmit 1320, based on the AIoTF ID, at least one of the following to the AIoTF 122: the UE ID, the UE location, the device update indication, the update reason.
  • the UE location is provided to the AIoTF 122, there is no need to provide the update reason and device update indication.
  • the AIoTF 122 transmits 1330 an AIoT device discovery update request to the UE 104.
  • the UE 104 may perform the AIoT device discovery update procedure as described with reference to Figs. 8, 10, 11 and 12.
  • Fig. 14 illustrates a signaling diagram illustrating an example process 1400 that supports AIoT device discovery update in accordance with aspects of the present disclosure.
  • the process 1400 may be considered as an example implementation of the process 300 or the process 1000.
  • the process 1400 will be described with reference to Fig. 1B.
  • the process 1400 may involve the UE 104, the AMF 120 and the AIoTF 122 in Fig. 1B as well as an AMF 160 which is not shown in Fig. 1B.
  • the UE 104 has moved to a serving area of a different AMF from the AMF 120, but still within the same serving area of the AIoTF 122.
  • the AMF 120 may implement a source AMF (S-AMF) 120 serving the UE 104 and the AMF 160 may implement a target AMF (T-AMF) 160 serving the UE 104.
  • S-AMF source AMF
  • T-AMF target AMF
  • the registration procedure of the UE 104 may be performed as described with reference to Fig. 4 and an AIoT device discovery procedure may be performed as described with reference to Figs. 4 to 7.
  • Fig. 14 does not illustrate the registration procedure of the UE 104 and the AIoT device discovery procedure.
  • the source AMF 120 receives a handover required request message from the source network entity.
  • the handover required request message may comprise the ID of the UE 104.
  • the target AMF 160 receives the location of the UE 104 from the target network entity via handover notify message.
  • the source AMF 120 may transmit 1410 at least one of the following to the AIoTF 122: the device update indication, the UE ID, the UE location, or an ID of the target AMF 160 (i.e., target AMF ID) .
  • the device update indication and the update reason may be optional.
  • the AIoTF 122 can use the target AMF ID to send a message to the UE 104.
  • the AIoTF 122 transmits 1420 an AIoT device discovery update request to the UE 104.
  • the UE 104 may perform the AIoT device discovery update procedure as described with reference to Figs. 8, 10, 11 and 12.
  • Fig. 15 illustrates a signaling diagram illustrating an example process 1500 that supports AIoT device discovery update in accordance with aspects of the present disclosure.
  • the process 1500 may be considered as an example implementation of the process 300 or the process 1000.
  • the process 1500 will be described with reference to Fig. 1B.
  • the process 1500 may involve the UE 104, the AMF 120 and the AIoTF 122 in Fig. 1B as well as an AMF 160 which is not shown in Fig. 1B.
  • the UE 104 has moved to a serving area of a different AMF from the AMF 120, but still within the same serving area of the AIoTF 122.
  • the AMF 120 may implement a source AMF (S-AMF) 120 serving the UE 104 and the AMF 160 may implement a target AMF (T-AMF) 160 serving the UE 104.
  • S-AMF source AMF
  • T-AMF target AMF
  • the registration procedure of the UE 104 may be performed as described with reference to Fig. 4 and an AIoT device discovery procedure may be performed as described with reference to Figs. 4 to 7.
  • Fig. 15 does not illustrate the registration procedure of the UE 104 and the AIoT device discovery procedure.
  • the source AMF 120 receives a handover required request message from the source network entity.
  • the handover required request message may comprise the ID of the UE 104.
  • the target AMF 160 receives the location of the UE 104 from the target network entity via handover notify message.
  • the UE 104 may transmit 1510 at least one of the following to the AIoTF 122: the device update indication, the update reason, or the UE location (such as the updated location of the UE 104) .
  • the AIoTF 122 transmits 1520 an AIoT device discovery update request to the UE 104.
  • the UE 104 may perform the AIoT device discovery update procedure as described with reference to Figs. 8, 10, 11 and 12.
  • the UE 104 may transmit the first information about the at least one AIoT device 150 at the action 1510.
  • the UE 104 initiates the AIoT device discovery update procedure by performing the process 900.
  • the action 1520 may not be performed.
  • the AIoTF 122 may implement a source AIoTF serving the UE 104. This will be described with reference to Figs. 16 to 18.
  • Fig. 16 illustrates a signaling diagram illustrating an example process 1600 that supports AIoT device discovery update in accordance with aspects of the present disclosure.
  • the process 1600 may be considered as an example implementation of the process 300 or the process 1000.
  • the process 1600 may involve a first apparatus and a second apparatus.
  • the first apparatus may perform the AMF 120 in Fig. 1B.
  • the first apparatus may perform other network function than the AMF 120 in Fig. 1B.
  • the second apparatus may perform the AIoTF 122 in Fig. 1B.
  • the second apparatus may perform other network function than the AIoTF 122 in Fig. 1B.
  • the process 1600 will be described with reference to Fig. 1B.
  • the process 1600 may involve the UE 104, the AMF 120 and the AIoTF 122 in Fig. 1B as well as an AIoTF 170 which is not shown in Fig. 1B.
  • the UE 104 has moved to a serving area of a different AIoTF from the AIoTF 122, but still within the same serving area of the AMF 120.
  • the AIoTF 122 may implement a source AIoTF (S-AIoTF) 122 serving the UE 104 and the AIoTF 170 may implement a target AIoTF (T-AIoTF) 170 serving the UE 104.
  • S-AIoTF source AIoTF
  • T-AIoTF target AIoTF
  • the registration procedure of the UE 104 may be performed as described with reference to Fig. 4 and an AIoT device discovery procedure may be performed as described with reference to Figs. 4 to 7.
  • Fig. 16 does not illustrate the registration procedure of the UE 104 and the AIoT device discovery procedure.
  • the AMF 120 may transmit 1610 at least one of the following to the source AIoTF 122: an ID of the target AIoTF 170 (i.e., target AIoTF ID) , the UE ID or the UE location (such as the updated location of the UE 104) .
  • an ID of the target AIoTF 170 i.e., target AIoTF ID
  • the UE ID or the UE location such as the updated location of the UE 104 .
  • the AMF 120 may indicate the source AIoTF 122 to transmit context information of the UE 104 to the target AIoTF 170.
  • the source AIoTF 122 transmits 1620, based on the target AIoTF ID, at least one of the following to the target AIoTF 170: the UE ID, the UE location (such as the updated location of the UE 104) or the context information of the UE 104.
  • the target AIoTF 170 initiates 1630 the AIoT device discovery update procedure towards the UE 104 by transmitting an AIoT device discovery update request to the UE 104.
  • Fig. 17 illustrates a signaling diagram illustrating an example process 1700 that supports AIoT device discovery update in accordance with aspects of the present disclosure.
  • the process 1700 may be considered as an example implementation of the process 300 or the process 1000.
  • the process 1700 may involve a first apparatus and a second apparatus.
  • the first apparatus may perform the AMF 120 in Fig. 1B.
  • the first apparatus may perform other network function than the AMF 120 in Fig. 1B.
  • the second apparatus may perform the AIoTF 122 in Fig. 1B.
  • the second apparatus may perform other network function than the AIoTF 122 in Fig. 1B.
  • the process 1700 will be described with reference to Fig. 1B.
  • the process 1700 may involve the UE 104, the AMF 120 and the AIoTF 122 in Fig. 1B as well as an AIoTF 170 which is not shown in Fig. 1B.
  • the UE 104 has moved to a serving area of a different AIoTF from the AIoTF 122, but still within the same serving area of the AMF 120.
  • the AIoTF 122 may implement a source AIoTF (S-AIoTF) 122 serving the UE 104 and the AIoTF 170 may implement a target AIoTF (T-AIoTF) 170 serving the UE 104.
  • S-AIoTF source AIoTF
  • T-AIoTF target AIoTF
  • the registration procedure of the UE 104 may be performed as described with reference to Fig. 4 and an AIoT device discovery procedure may be performed as described with reference to Figs. 4 to 7.
  • Fig. 17 does not illustrate the registration procedure of the UE 104 and the AIoT device discovery procedure.
  • the AMF 120 may transmit 1710 at least one of the following to the target AIoTF 170: an ID of the source AIoTF 122 (i.e., source AIoTF ID) , the UE ID or the UE location (such as the updated location of the UE 104) .
  • an ID of the source AIoTF 122 i.e., source AIoTF ID
  • the UE ID or the UE location such as the updated location of the UE 104 .
  • the target AIoTF 170 may be selected from the NRF based on the updated location of the UE 104.
  • the target AIoTF 170 uses the UE ID to obtain 1720 context information of the UE 104 from the source AIoTF 122 based on the source AIoTF ID received from the AMF 120.
  • the target AIoTF 170 initiates 1730 the AIoT device discovery update procedure towards the UE 104 by transmitting an AIoT device discovery update request to the UE 104.
  • Fig. 18 illustrates a signaling diagram illustrating an example process 1800 that supports AIoT device discovery update in accordance with aspects of the present disclosure.
  • the process 1800 may be considered as an example implementation of the process 300 or the process 1000.
  • the process 1800 may involve a first apparatus and a second apparatus.
  • the first apparatus may perform the AMF 120 in Fig. 1B.
  • the first apparatus may perform other network function than the AMF 120 in Fig. 1B.
  • the second apparatus may perform the AIoTF 122 in Fig. 1B.
  • the second apparatus may perform other network function than the AIoTF 122 in Fig. 1B.
  • the process 1800 will be described with reference to Fig. 1B.
  • the process 1800 may involve the UE 104, the AMF 120 and the AIoTF 122 in Fig. 1B as well as an AIoTF 170 which is not shown in Fig. 1B.
  • the UE 104 has moved to a serving area of a different AIoTF from the AIoTF 122, but still within the same serving area of the AMF 120.
  • the AIoTF 122 may implement a source AIoTF (S-AIoTF) 122 serving the UE 104 and the AIoTF 170 may implement a target AIoTF (T-AIoTF) 170 serving the UE 104.
  • S-AIoTF source AIoTF
  • T-AIoTF target AIoTF
  • the registration procedure of the UE 104 may be performed as described with reference to Fig. 4 and an AIoT device discovery procedure may be performed as described with reference to Figs. 4 to 7.
  • Fig. 18 does not illustrate the registration procedure of the UE 104 and the AIoT device discovery procedure.
  • the UE 104 may transmit 1810 at least one of the following to the target AIoTF 170: the device update indication, the update reason, or the UE location (such as the updated location of the UE 104) .
  • the target AIoTF 170 transmits 1820 an AIoT device discovery update request to the UE 104.
  • the UE 104 may perform the AIoT device discovery update procedure as described with reference to Figs. 8, 10, 11 and 12.
  • the UE 104 may transmit the first information about the at least one AIoT device 150 at the action 1810.
  • the UE 104 initiates the AIoT device discovery update procedure by performing the process 900.
  • the action 1820 may not be performed.
  • the AMF 120 can help the UE 104 to register to the target AIoTF 170.
  • the UE 104 can send a registration request to the target AIoTF 170 via the AMF 120 as illustrated in Fig. 4.
  • the AIoT device discovery procedure will be triggered accordingly. This will be described with reference to Figs. 19 to 21.
  • Fig. 19 illustrates a signaling diagram illustrating an example process 1900 that supports AIoT device discovery update in accordance with aspects of the present disclosure.
  • the process 1900 may be considered as an example implementation of the process 300 or the process 1000.
  • the process 1900 may involve a first apparatus and a second apparatus.
  • the first apparatus may perform the AMF 120 in Fig. 1B.
  • the first apparatus may perform other network function than the AMF 120 in Fig. 1B.
  • the second apparatus may perform the AIoTF 122 in Fig. 1B.
  • the second apparatus may perform other network function than the AIoTF 122 in Fig. 1B.
  • the process 1900 will be described with reference to Fig. 1B.
  • the process 1900 may involve the UE 104, the AMF 120, the AIoTF 122 in Fig. 1B as well as an AMF 160 and an AIoTF 170 which is not shown in Fig. 1B.
  • the UE 104 has moved to a serving area of a different AIoTF from the AIoTF 122 and to a serving area of a different AMF from the AMF 120.
  • the AIoTF 122 may implement a source AIoTF (S-AIoTF) 122 serving the UE 104 and the AIoTF 170 may implement a target AIoTF (T-AIoTF) 170 serving the UE 104.
  • the AMF 120 may implement a source AMF (S-AMF) 120 serving the UE 104 and the AMF 160 may implement a target AMF (T-AMF) 160 serving the UE 104.
  • S-AIoTF source AIoTF
  • T-AIoTF target AIoTF
  • the registration procedure of the UE 104 may be performed as described with reference to Fig. 4 and an AIoT device discovery procedure may be performed as described with reference to Figs. 4 to 7.
  • Fig. 19 does not illustrate the registration procedure of the UE 104 and the AIoT device discovery procedure.
  • the source AMF 120 transmits 1910 at least one of the following to the target AMF 160: the UE ID, the UE location, the source AIoTF ID, or the target AIoTF ID.
  • the target AMF 160 transmits 1920 at least one of the following to the source AIoTF 122: the UE ID, the UE location, the target AIoTF ID, or the update indication to the source AIoTF 122.
  • the target AMF 160 may ask the source AIoTF 122 to transfer the UE context of the UE 104 to the target AIoTF 170.
  • the source AIoTF 122 transmits 1930 at least one of the following to the target AIoTF 170: the UE ID, the UE location or UE context of the UE 104.
  • the target AIoTF 170 initiates 1940 the AIoT device discovery update procedure towards the UE 104 by transmitting an AIoT device discovery update request to the UE 104 via the target AMF 160.
  • the UE 104 may perform the AIoT device discovery update procedure as described with reference to Figs. 8, 10, 11 and 12.
  • the source AMF 120 directly sends the UE ID, the UE location, the source AIoTF ID and the target AMF ID to the target AIoTF 170.
  • the target AIoTF 170 can retrieve the UE context from the source AIoTF 122.
  • the source AMF 120 can send the UE ID, the UE location, the target AMF ID and the target AIoTF ID to the source AIoTF 122.
  • the source AIoTF 122 can forward the UE ID, the UE location, the target AMF ID and the UE context to the target AIoTF 170.
  • Fig. 20 illustrates a signaling diagram illustrating an example process 2000 that supports AIoT device discovery update in accordance with aspects of the present disclosure.
  • the process 2000 may be considered as an example implementation of the process 300 or the process 1000.
  • the process 2000 may involve a first apparatus and a second apparatus.
  • the first apparatus may perform the AMF 120 in Fig. 1B.
  • the first apparatus may perform other network function than the AMF 120 in Fig. 1B.
  • the second apparatus may perform the AIoTF 122 in Fig. 1B.
  • the second apparatus may perform other network function than the AIoTF 122 in Fig. 1B.
  • the process 2000 will be described with reference to Fig. 1B.
  • the process 2000 may involve the UE 104, the AMF 120, the AIoTF 122 in Fig. 1B as well as an AMF 160 and an AIoTF 170 which is not shown in Fig. 1B.
  • the UE 104 has moved to a serving area of a different AIoTF from the AIoTF 122 and to a serving area of a different AMF from the AMF 120.
  • the AIoTF 122 may implement a source AIoTF (S-AIoTF) 122 serving the UE 104 and the AIoTF 170 may implement a target AIoTF (T-AIoTF) 170 serving the UE 104.
  • the AMF 120 may implement a source AMF (S-AMF) 120 serving the UE 104 and the AMF 160 may implement a target AMF (T-AMF) 160 serving the UE 104.
  • S-AIoTF source AIoTF
  • T-AIoTF target AIoTF
  • the registration procedure of the UE 104 may be performed as described with reference to Fig. 4 and an AIoT device discovery procedure may be performed as described with reference to Figs. 4 to 7.
  • Fig. 20 does not illustrate the registration procedure of the UE 104 and the AIoT device discovery procedure.
  • the source AMF 120 transmits 2010 at least one of the following to the target AMF 160: the UE ID, the UE location, the source AIoTF ID, or the target AIoTF ID.
  • the target AMF 160 transmits 2020 at least one of the following to the target AIoTF 170: the UE ID, the UE location, the source AIoTF ID.
  • the target AIoTF 170 uses the UE ID to obtain 2030 the UE context of the UE 104 from the source AIoTF 122 based on the received source AIoTF ID from the target AMF 160.
  • the target AIoTF 170 initiates 2040 the AIoT device discovery update procedure towards the UE 104 by transmitting an AIoT device discovery update request to the UE 104 via the target AMF 160.
  • the UE 104 may perform the AIoT device discovery update procedure as described with reference to Figs. 8, 10, 11 and 12.
  • Fig. 21 illustrates a signaling diagram illustrating an example process 2100 that supports AIoT device discovery update in accordance with aspects of the present disclosure.
  • the process 2100 may be considered as an example implementation of the process 300 or the process 1000.
  • the process 2100 may involve a first apparatus and a second apparatus.
  • the first apparatus may perform the AMF 120 in Fig. 1B.
  • the first apparatus may perform other network function than the AMF 120 in Fig. 1B.
  • the second apparatus may perform the AIoTF 122 in Fig. 1B.
  • the second apparatus may perform other network function than the AIoTF 122 in Fig. 1B.
  • the process 2100 will be described with reference to Fig. 1B.
  • the process 2100 may involve the UE 104, the AMF 120, the AIoTF 122 in Fig. 1B as well as an AMF 160 and an AIoTF 170 which is not shown in Fig. 1B.
  • the UE 104 has moved to a serving area of a different AIoTF from the AIoTF 122 and to a serving area of a different AMF from the AMF 120.
  • the AIoTF 122 may implement a source AIoTF (S-AIoTF) 122 serving the UE 104 and the AIoTF 170 may implement a target AIoTF (T-AIoTF) 170 serving the UE 104.
  • the AMF 120 may implement a source AMF (S-AMF) 120 serving the UE 104 and the AMF 160 may implement a target AMF (T-AMF) 160 serving the UE 104.
  • S-AIoTF source AIoTF
  • T-AIoTF target AIoTF
  • the registration procedure of the UE 104 may be performed as described with reference to Fig. 4 and an AIoT device discovery procedure may be performed as described with reference to Figs. 4 to 7.
  • Fig. 21 does not illustrate the registration procedure of the UE 104 and the AIoT device discovery procedure.
  • the UE 104 may transmit 2110 at least one of the following to the target AIoTF 170: the device update indication, the update reason, or the UE location (such as the updated location of the UE 104) .
  • the target AIoTF 170 transmits 2120 an AIoT device discovery update request to the UE 104.
  • the UE 104 may perform the AIoT device discovery update procedure as described with reference to Figs. 8, 10, 11 and 12.
  • the UE 104 may transmit the first information about the at least one AIoT device 150 at the action 2110.
  • the UE 104 initiates the AIoT device discovery update procedure by performing the process 900.
  • the action 2120 may not be performed.
  • Fig. 22 illustrates an example of a device 2200 that supports AIoT device discovery and update in accordance with aspects of the present disclosure.
  • the device 2200 may be an example of a network entity 102 or a UE 104 as described herein.
  • the device 2200 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof.
  • the device 2200 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 2202, a memory 2204, a transceiver 2206, and, optionally, an I/O controller 22014. 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 2202, the memory 2204, the transceiver 2206, 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 2202, the memory 2204, the transceiver 2206, or various combinations or components thereof may support a method for performing one or more of the operations described herein.
  • the processor 2202, the memory 2204, the transceiver 2206, 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 2202 and the memory 2204 coupled with the processor 2202 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 2202, instructions stored in the memory 2204) .
  • the processor 2202 may support wireless communication at the device 2200 in accordance with examples as disclosed herein.
  • the processor 2202 may be configured to operable to support a means for performing the following: performing at least one of an AIoT device discovery procedure or an AIoT device discovery update procedure; and transmitting, to a first apparatus or a second apparatus, first information about at least one AIoT device to be served by the UE.
  • the processor 2202 may be configured to operable to support a means for performing the following: determining that at least one AIoT device that a user equipment (UE) is serving is updated; and causing an AIoT device discovery update procedure to be performed.
  • UE user equipment
  • the processor 2202 may be configured to operable to support a means for performing the following: receiving a first message from a first apparatus or a UE serving at least one AIoT device, wherein the first message comprises at least one of the following: an indication indicating that the at least one AIoT device that the UE is serving is updated, a reason why the at least one AIoT device that the UE is serving is updated, an identity (ID) of the UE, a location of the UE, or timestamp when the at least one AIoT device that the UE is serving is updated; and transmitting an AIoT device discovery update request to the first apparatus or the UE, wherein the AIoT device discovery update request comprises the ID of the UE; and receiving, from the first apparatus or the UE, an AIoT device discovery update result which comprises first information about the at least one AIoT device.
  • the first message comprises at least one of the following: an indication indicating that the at least one AIoT device that the UE is serving is updated, a reason why the at least
  • the processor 2202 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 2202 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 2202.
  • the processor 2202 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 2204) to cause the device 2200 to perform various functions of the present disclosure.
  • the memory 2204 may include random access memory (RAM) and read-only memory (ROM) .
  • the memory 2204 may store computer-readable, computer-executable code including instructions that, when executed by the processor 2202 cause the device 2200 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 2202 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the memory 2204 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 22014 may manage input and output signals for the device 2200.
  • the I/O controller 22014 may also manage peripherals not integrated into the device M02.
  • the I/O controller 22014 may represent a physical connection or port to an external peripheral.
  • the I/O controller 22014 may utilize an operating system such as or another known operating system.
  • the I/O controller 22014 may be implemented as part of a processor, such as the processor 2202.
  • a user may interact with the device 2200 via the I/O controller 22014 or via hardware components controlled by the I/O controller 22014.
  • the device 2200 may include a single antenna 2210. However, in some other implementations, the device 2200 may have more than one antenna 2210 (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 2206 may communicate bi-directionally, via the one or more antennas 2210, wired, or wireless links as described herein.
  • the transceiver 2206 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 2206 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 2210 for transmission, and to demodulate packets received from the one or more antennas 2210.
  • the transceiver 2206 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 2210 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 2210 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. 23 illustrates an example of a processor 2300 that supports AIoT device discovery and update in accordance with aspects of the present disclosure.
  • the processor 2300 may be an example of a processor configured to perform various operations in accordance with examples as described herein.
  • the processor 2300 may include a controller 2302 configured to perform various operations in accordance with examples as described herein.
  • the processor 2300 may optionally include at least one memory 2304, such as L1/L2/L3 cache. Additionally, or alternatively, the processor 2300 may optionally include one or more arithmetic-logic units (ALUs) 2306.
  • ALUs arithmetic-logic units
  • the processor 2300 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 2300) 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 2302 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 2300 to cause the processor 2300 to support various operations in accordance with examples as described herein.
  • the controller 2302 may operate as a control unit of the processor 2300, generating control signals that manage the operation of various components of the processor 2300. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
  • the controller 2302 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 2304 and determine subsequent instruction (s) to be executed to cause the processor 2300 to support various operations in accordance with examples as described herein.
  • the controller 2302 may be configured to track memory address of instructions associated with the memory 2304.
  • the controller 2302 may be configured to decode instructions to determine the operation to be performed and the operands involved.
  • the controller 2302 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 2300 to cause the processor 2300 to support various operations in accordance with examples as described herein.
  • the controller 2302 may be configured to manage flow of data within the processor 2300.
  • the controller 2302 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 2300.
  • ALUs arithmetic logic units
  • the memory 2304 may include one or more caches (e.g., memory local to or included in the processor 2300 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.
  • the memory 2304 may reside within or on a processor chipset (e.g., local to the processor 2300) .
  • the memory 2304 may reside external to the processor chipset (e.g., remote to the processor 2300) .
  • the memory 2304 may store computer-readable, computer-executable code including instructions that, when executed by the processor 2300, cause the processor 2300 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 2302 and/or the processor 2300 may be configured to execute computer-readable instructions stored in the memory 2304 to cause the processor 2300 to perform various functions.
  • the processor 2300 and/or the controller 2302 may be coupled with or to the memory 2304, the processor 2300, the controller 2302, and the memory 2304 may be configured to perform various functions described herein.
  • the processor 2300 may include multiple processors and the memory 2304 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 2306 may be configured to support various operations in accordance with examples as described herein.
  • the one or more ALUs 2306 may reside within or on a processor chipset (e.g., the processor 2300) .
  • the one or more ALUs 2306 may reside external to the processor chipset (e.g., the processor 2300) .
  • One or more ALUs 2306 may perform one or more computations such as addition, subtraction, multiplication, and division on data.
  • one or more ALUs 2306 may receive input operands and an operation code, which determines an operation to be executed.
  • One or more ALUs 2306 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 2306 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 2306 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 2306 to handle conditional operations, comparisons, and bitwise operations.
  • the processor 2300 may support wireless communication at the device 2200 in accordance with examples as disclosed herein.
  • the processor 2300 may be configured to operable to support a means for performing the following: performing at least one of an AIoT device discovery procedure or an AIoT device discovery update procedure; and transmitting, to a first apparatus or a second apparatus, first information about at least one AIoT device to be served by the UE.
  • the processor 2300 may be configured to operable to support a means for performing the following: determining that at least one AIoT device that a user equipment (UE) is serving is updated; and causing an AIoT device discovery update procedure to be performed.
  • UE user equipment
  • the processor 2300 may be configured to operable to support a means for performing the following: receiving a first message from a first apparatus or a UE serving at least one AIoT device, wherein the first message comprises at least one of the following: an indication indicating that the at least one AIoT device that the UE is serving is updated, a reason why the at least one AIoT device that the UE is serving is updated, an identity (ID) of the UE, a location of the UE, or timestamp when the at least one AIoT device that the UE is serving is updated; and transmitting an AIoT device discovery update request to the first apparatus or the UE, wherein the AIoT device discovery update request comprises the ID of the UE; and receiving, from the first apparatus or the UE, an AIoT device discovery update result which comprises first information about the at least one AIoT device.
  • the first message comprises at least one of the following: an indication indicating that the at least one AIoT device that the UE is serving is updated, a reason why the at least
  • Fig. 24 illustrates a flowchart of a method 2400 that supports AIoT device discovery and update in accordance with aspects of the present disclosure.
  • the operations of the method 2400 may be implemented by a device or its components as described herein.
  • the operations of the method 2400 may be performed by the UE 104 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 performing at least one of an AIoT device discovery procedure or an AIoT device discovery update procedure.
  • the operations of 2410 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2410 may be performed by a device as described with reference to Fig. 1A or 1B.
  • the method may include transmitting, to a first apparatus or a second apparatus, first information about at least one AIoT device to be served by the UE.
  • the operations of 2420 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2420 may be performed by a device as described with reference to Fig. 1A or 1B.
  • Fig. 25 illustrates a flowchart of a method 2500 that supports AIoT device discovery and update in accordance with aspects of the present disclosure.
  • the operations of the method 2500 may be implemented by a device or its components as described herein.
  • the operations of the method 2500 may be performed by a first apparatus 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 determining that at least one AIoT device that a user equipment (UE) is serving is updated.
  • UE user equipment
  • the operations of 2510 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2510 may be performed by a device as described with reference to Fig. 1A or 1B.
  • the method may include causing an AIoT device discovery update procedure to be performed.
  • the operations of 2520 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2520 may be performed by a device as described with reference to Fig. 1A or 1B.
  • Fig. 26 illustrates a flowchart of a method 2600 that supports AIoT device discovery and update in accordance with aspects of the present disclosure.
  • the operations of the method 2600 may be implemented by a device or its components as described herein.
  • the operations of the method 2600 may be performed by a second apparatus 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 receiving a first message from a first apparatus or a UE serving at least one AIoT device.
  • the first message comprises at least one of the following: an indication indicating that the at least one AIoT device that the UE is serving is updated, a reason why the at least one AIoT device that the UE is serving is updated, an identity (ID) of the UE, a location of the UE, or timestamp when the at least one AIoT device that the UE is serving is updated.
  • the operations of 2610 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2610 may be performed by a device as described with reference to Fig. 1A or 1B.
  • the method may include transmitting an AIoT device discovery update request to the first apparatus or the UE, wherein the AIoT device discovery update request comprises the ID of the UE.
  • the operations of 2620 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2620 may be performed by a device as described with reference to Fig. 1A or 1B.
  • the method may include receiving, from the first apparatus or the UE, an AIoT device discovery update result which comprises first information about the at least one AIoT device.
  • the operations of 2630 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 2630 may be performed by a device as described with reference to Fig. 1A or 1B.
  • 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)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Divers aspects de la présente divulgation concernent des appareils et des procédés de détection et de mise à jour de dispositif AIoT. Selon un aspect, un UE effectue une procédure de détection de dispositif AIoT et/ou une procédure de mise à jour de détection de dispositif AIoT. À son tour, l'UE transmet, à un premier appareil ou à un second appareil, des premières informations concernant au moins un dispositif AIoT à desservir par l'UE.
PCT/CN2024/085623 2024-04-02 2024-04-02 Détection et mise à jour de dispositif aiot Pending WO2025035789A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/085623 WO2025035789A1 (fr) 2024-04-02 2024-04-02 Détection et mise à jour de dispositif aiot

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/085623 WO2025035789A1 (fr) 2024-04-02 2024-04-02 Détection et mise à jour de dispositif aiot

Publications (1)

Publication Number Publication Date
WO2025035789A1 true WO2025035789A1 (fr) 2025-02-20

Family

ID=94632084

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/085623 Pending WO2025035789A1 (fr) 2024-04-02 2024-04-02 Détection et mise à jour de dispositif aiot

Country Status (1)

Country Link
WO (1) WO2025035789A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114600482A (zh) * 2019-10-29 2022-06-07 高通股份有限公司 侧行链路发现过程
WO2023131341A1 (fr) * 2022-01-10 2023-07-13 Mediatek Inc. Procédé et appareil pour procédure de découverte entre un noeud relais et un équipement utilisateur source
WO2024045166A1 (fr) * 2022-09-02 2024-03-07 Qualcomm Incorporated Découverte de dispositifs radiofréquences de l'internet des objets

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114600482A (zh) * 2019-10-29 2022-06-07 高通股份有限公司 侧行链路发现过程
US20230319540A1 (en) * 2019-10-29 2023-10-05 Qualcomm Incorporated Sidelink discovery procedure
WO2023131341A1 (fr) * 2022-01-10 2023-07-13 Mediatek Inc. Procédé et appareil pour procédure de découverte entre un noeud relais et un équipement utilisateur source
WO2024045166A1 (fr) * 2022-09-02 2024-03-07 Qualcomm Incorporated Découverte de dispositifs radiofréquences de l'internet des objets

Similar Documents

Publication Publication Date Title
WO2024183312A1 (fr) Procédés et appareils pour des procédures ltm intra-bs et inter-bs
WO2025035789A1 (fr) Détection et mise à jour de dispositif aiot
WO2024109166A1 (fr) Changement de trajet indirect dans un trajet multiple
WO2025097794A1 (fr) Acquisition de sib dans une communication relais
WO2024098839A1 (fr) Ajout de trajet indirect pour communication u2n
WO2025011026A1 (fr) Sélection de groupe de ressources
WO2025107655A1 (fr) Règle de politique pour transmission de données ido-a
WO2024093439A1 (fr) Ajout ou libération de trajet dans un trajet multiple inter-gnb
WO2024207740A1 (fr) Mobilité déclenchée de couche 1 ou de couche 2
WO2024244539A1 (fr) Transfert d'informations de radiomessagerie dans une communication relais
WO2024094228A1 (fr) Procédure de défaillance de trajet indirect en multi-trajet
WO2024199052A1 (fr) Procédure de défaillance de trajet indirect due à ltm de l'ue relais dans un trajet multiple
WO2025123740A1 (fr) Service d'ido-a de support
WO2024179093A1 (fr) Apprentissage fédéré assisté
WO2024259991A1 (fr) Défaillance dans une communication par relais
WO2025107677A1 (fr) Dispositifs et procédés de communication
WO2025097801A1 (fr) Dispositifs et procédés de communication
WO2024093337A1 (fr) Dispositifs et procédés de communication
WO2025030889A1 (fr) Double connectivité dans une architecture basée sur un service
WO2025035808A1 (fr) Gestion de connexion pc5 de bout en bout dans un relais u2u
WO2024093380A1 (fr) Positionnement de liaison latérale avec des changements dans un scénario de couverture
WO2025246425A1 (fr) Gestion de ressource
WO2025060464A1 (fr) Procédé et appareil de prise en charge d'applications d'intelligence artificielle (ia) dans des communications sans fil
WO2025251726A1 (fr) Mobilité déclenchée par couche 1 ou couche 2 conditionnelle
WO2025148422A1 (fr) Procédés et appareils pour prendre en charge une mobilité déclenchée par l1/l2 (ltm) conditionnelle

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: 24853205

Country of ref document: EP

Kind code of ref document: A1