[go: up one dir, main page]

WO2025208517A1 - Procédé de communication, dispositif, système de communication, dispositif de communication et support de stockage - Google Patents

Procédé de communication, dispositif, système de communication, dispositif de communication et support de stockage

Info

Publication number
WO2025208517A1
WO2025208517A1 PCT/CN2024/086101 CN2024086101W WO2025208517A1 WO 2025208517 A1 WO2025208517 A1 WO 2025208517A1 CN 2024086101 W CN2024086101 W CN 2024086101W WO 2025208517 A1 WO2025208517 A1 WO 2025208517A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
aiot
devices
request
trp
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/086101
Other languages
English (en)
Chinese (zh)
Inventor
李丽丝
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.)
Beijing Xiaomi Mobile Software Co Ltd
Original Assignee
Beijing Xiaomi Mobile Software Co 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 Beijing Xiaomi Mobile Software Co Ltd filed Critical Beijing Xiaomi Mobile Software Co Ltd
Priority to CN202480026643.5A priority Critical patent/CN121080019A/zh
Priority to PCT/CN2024/086101 priority patent/WO2025208517A1/fr
Publication of WO2025208517A1 publication Critical patent/WO2025208517A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition

Definitions

  • a communication method is proposed, which is executed by a first device, including: obtaining first information, where the first information is used to indicate the functions and/or tasks of multiple second devices; based on the first information, determining a target device from the multiple second devices, where the target device is used to perform a first operation.
  • a communication method is proposed, which is executed by a second device, including: sending first information, the first information is used to indicate the function and/or task of the second device, the first information is used to assist the first device in determining a target device, and the target device is used to perform a first operation.
  • a communication method is proposed, which is executed by a fifth device, including: sending first information, the first information is used to indicate the functions of one or more candidate devices among multiple second devices, the first information is used to assist the first device in determining a target device from one or more candidate devices, and the target device is used to perform a first operation.
  • a second device including a transceiver module for sending first information, the first information being used to indicate the function and/or task of the second device, the first information being used to assist the first device in determining a target device, and the target device being used to perform a first operation.
  • a fourth device including a transceiver module for sending first information, the first information being used to indicate tasks of multiple second devices, the first information being used to assist the first device in determining a target device, and the target device being used to perform a first operation.
  • a fifth device including a transceiver module for sending first information, the first information being used to indicate the functions of one or more candidate devices among a plurality of second devices, the first information being used to assist the first device in determining a target device from one or more candidate devices, and the target device being used to perform a first operation.
  • a communication device including a transceiver; a memory; and a processor, which are connected to the transceiver and the memory respectively, and are configured to control the wireless signal reception and transmission of the transceiver by executing computer-executable instructions on the memory, and can implement the method described in any one of the first to fourth aspects.
  • AIoT-related operations can be performed. Based on the AIoT functions and/or tasks, a more suitable AIoT reader can be selected according to needs to provide AIoT services.
  • FIG1A is a schematic diagram of a topology structure 1 provided according to an embodiment of the present disclosure.
  • FIG1B is a schematic diagram of a topology structure 2 provided according to an embodiment of the present disclosure.
  • FIG1C is a schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.
  • FIG2A is an interactive schematic diagram of a communication method provided according to an embodiment of the present disclosure.
  • FIG3A is a flow chart of a communication method for a first device according to an embodiment of the present disclosure
  • FIG3C is a flow chart of a communication method provided by a first device according to an embodiment of the present disclosure.
  • FIG4A is a flow chart of a communication method for a second device according to an embodiment of the present disclosure
  • FIG4B is a flow chart of a communication method for a second device according to an embodiment of the present disclosure.
  • FIG4C is a flow chart of a communication method for a second device according to an embodiment of the present disclosure.
  • FIG6A is a flow chart of a communication method for a fifth device according to an embodiment of the present disclosure.
  • FIG6B is a schematic flow chart of a communication method for a fifth device according to an embodiment of the present disclosure.
  • FIG7B is an interactive diagram of a communication method providing a service-based architecture according to an embodiment of the present disclosure
  • FIG8A is a schematic structural diagram of a first device provided according to an embodiment of the present disclosure.
  • FIG8C is a schematic structural diagram of a fourth device provided according to an embodiment of the present disclosure.
  • FIG8D is a schematic structural diagram of a fifth device provided according to an embodiment of the present disclosure.
  • FIG9B is a schematic diagram of the structure of the chip proposed in an embodiment of the present disclosure.
  • the embodiments of the present disclosure provide a communication method and device, a communication system, a communication device, and a storage medium.
  • the first information is information of one or more candidate devices
  • the one or more candidate devices are determined by the fifth device from multiple second devices
  • the one or more candidate devices are determined by the fifth device based on the second request and the first information received from multiple second devices.
  • obtaining the first information includes at least one of the following: receiving the first information from multiple second devices, the first information being functional configuration information of the multiple second devices; receiving the first information from a fourth device, the first information being task information of the multiple second devices.
  • an embodiment of the present disclosure provides a communication method, which is executed by a second device, including: sending first information, the first information is used to indicate the function and/or task of the second device, the first information is used to assist the first device in determining a target device, and the target device is used to perform a first operation.
  • the method further includes: receiving a first request sent by the first device, where the first request is used to request multiple second devices to send first information to the first device.
  • the first request includes at least one item of the following information: a requested sending and receiving point TRP list; a requested configuration information type, the configuration information type including at least one item of the following information: location information; cell information; AIoT configuration capability; AIoT receiving capability; time-frequency resource information; and power information.
  • the first operation includes at least one of the following: sending second information to a third device; receiving third information from a third device; performing an inventory; performing positioning; performing a read operation; or performing a write operation.
  • the first information includes at least one of the following: functional configuration information of multiple second devices.
  • the functional configuration information includes one or more TRP information supporting AIoT, and each TRP information includes at least one item of the following information: TRP identifier; cell identifier; TRP location information, used to indicate the geographical location of the TRP; support for AIoT configuration function, used to indicate that the TRP or the second device to which the TRP belongs or the cell to which the TRP belongs supports transmission of configuration information to a third device; support for AIoT reception function, used to indicate that the TRP or the second device to which the TRP belongs or the cell to which the TRP belongs supports receiving information from a third device; support for time and/or frequency information for sending AIoT configuration signaling; support for time and/or frequency information for AIoT receiving capability; power information for sending AIoT configuration; identifier of the second device; IP address or domain name information.
  • the first information includes at least one of the following: task information of multiple second devices.
  • an embodiment of the present disclosure provides a communication method, which is executed by a fifth device, and includes sending first information, where the first information is used to indicate the functions of one or more candidate devices among multiple second devices, and the first information is used to assist the first device in determining a target device from one or more candidate devices, and the target device is used to perform a first operation.
  • the method also includes: receiving a third request sent by multiple second devices, the third request is used to request registration of multiple second devices in the fifth device, and the third request includes first information of the multiple second devices.
  • the method further includes: sending first feedback to multiple second devices, the first feedback being used to indicate that the third request is received and/or that the multiple second devices complete registration in the fifth device.
  • the method further includes: receiving a second request sent by the first device, where the second request is used to request the fifth device to send the first information to the first device.
  • the method further includes: determining one or more candidate devices from a plurality of second devices based on the second request and the third request.
  • the method further includes: sending a second feedback to the first device, the second feedback including the first information of one or more candidate devices
  • first information of multiple second devices is included in the third request, and first information of one or more candidate devices is included in the second feedback.
  • the functional configuration information includes one or more TRP information supporting AIoT, and each TRP information includes at least one item of the following information: TRP identifier; cell identifier; TRP location information, used to indicate the geographical location of the TRP; support for AIoT configuration function, used to indicate that the TRP or the first device to which the TRP belongs supports transmission of configuration information to a third device; support for AIoT receiving function, used to indicate that the TRP or the first device to which the TRP belongs supports receiving information from a third device; support for time and/or frequency information for sending AIoT configuration signaling; support for time and/or frequency information for AIoT receiving capability; power information for sending AIoT configuration; identifier of the second device; IP address or domain name information.
  • an embodiment of the present disclosure provides a fifth device, including a transceiver module, for sending first information, the first information being used to indicate the functions of one or more candidate devices among a plurality of second devices, the first information being used to assist the first device in determining a target device from one or more candidate devices, and the target device being used to perform a first operation.
  • an embodiment of the present disclosure provides a communication system, comprising: a first device and a second device, or comprising a first device, a second device, and a fifth device, wherein the first device is configured to implement the method described in any one of the embodiments in the first aspect of the present disclosure; the second device is configured to implement the method described in any one of the embodiments in the second aspect of the present disclosure; and the fifth device is configured to implement the method described in any one of the embodiments in the fourth aspect of the present disclosure.
  • the communication system further includes a fourth device, and the fourth device is configured to implement the method described in any one of the embodiments of the third aspect of this disclosure.
  • an embodiment of the present disclosure provides a storage medium, which stores instructions.
  • the instructions When the instructions are executed on a communication device, the communication device executes the method described in any one of the embodiments of the first to fourth aspects of the present disclosure.
  • an embodiment of the present disclosure proposes a program product.
  • the program product is executed by a communication device
  • the communication device executes the method described in the optional implementation of the first to fourth aspects.
  • an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in the optional implementation of the first to fourth aspects.
  • an embodiment of the present disclosure provides a chip or a chip system, wherein the chip or chip system includes a processing circuit configured to execute the method described in the optional implementation of the first to fourth aspects above.
  • the present disclosure provides a communication method and device, a communication system, a communication device, and a storage medium.
  • the terms communication method and information processing method are interchangeable
  • the terms network device and information processing device and communication device are interchangeable
  • the terms information processing system and communication system are interchangeable.
  • plurality refers to two or more.
  • the terms “at least one of,” “at least one of,” “at least one of,” “one or more,” “a plurality of,” “multiple,” etc. may be used interchangeably.
  • descriptions such as "in one case A, in another case B,” or “in response to one case A, in response to another case B,” may include the following technical solutions depending on the situation: executing A independently of B (in some embodiments, A); executing B independently of A (in some embodiments, B); selectively executing A and B (in some embodiments, selecting between A and B); and executing both A and B (in some embodiments, A and B).
  • executing A independently of B in some embodiments, A
  • executing B independently of A in some embodiments, B
  • selectively executing A and B in some embodiments, selecting between A and B
  • executing both A and B in some embodiments, A and B.
  • prefixes such as “first” and “second” in the embodiments of the present disclosure are only used to distinguish different description objects, and do not constitute any restrictions on the position, order, priority, quantity or content of the description objects.
  • the description object please refer to the description in the context of the claims or embodiments, and no unnecessary restrictions should be imposed due to the use of prefixes.
  • the description object is a "field”
  • the ordinal number before the "field” in the "first field” and the "second field” does not limit the position or order between the "fields”
  • “first” and “second” do not limit whether the "fields” they modify are in the same message, nor do they limit the order of the "first field” and the "second field”.
  • the description object is a "level”
  • the ordinal number before the "level” in the “first level” and the “second level” does not limit the priority between the "levels”.
  • the description of The number of objects is not limited by ordinal numbers and can be one or more.
  • the phrase "first device” the number of "devices” can be one or more.
  • the objects modified by different prefixes can be the same or different.
  • the object being described is “device,” then “first device” and “second device” can be the same or different devices, and their types can be the same or different.
  • the object being described is "information,” then “first information” and “second information” can be the same or different information, and their content can be the same or different.
  • “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.
  • terms such as “in response to", “in response to determining", “in the case of", “at the time of", “when!, “if", “if", etc. can be used interchangeably.
  • terms such as “greater than”, “greater than or equal to”, “not less than”, “more than”, “more than or equal to”, “not less than”, “higher than”, “higher than or equal to”, “not less than”, and “above” can be replaced with each other, and terms such as “less than”, “less than or equal to”, “not greater than”, “less than”, “less than or equal to”, “not more than”, “lower than”, “lower than or equal to”, “not higher than”, and “below” can be replaced with each other.
  • devices, etc. can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments.
  • Terms such as “device”, “equipment”, “device”, “circuit”, “network element”, “node”, “function”, “unit”, “section”, “system”, “network”, “chip”, “chip system”, “entity”, and “subject” can be used interchangeably.
  • network can be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).
  • the terms “access network device (AN device)”, “radio access network device (RAN device)”, “base station (BS)”, “radio base station”, “fixed station”, “node”, “access point”, “transmission point (TP)”, “reception point (RP)”, “transmission/reception point (TRP)”, “panel”, “antenna panel”, “antenna array”, “cell”, “macro cell”, “small cell”, “femto cell”, “pico cell”, “sector”, “cell group”, “carrier”, “component carrier”, “bandwidth part (BWP)” and the like may be used interchangeably.
  • terminal In some embodiments, the terms "terminal”, “terminal device”, “user equipment (UE)”, “user terminal” “mobile station (MS)”, “mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc. can be used interchangeably.
  • the access network device, the core network device, or the network device can be replaced by a terminal.
  • the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device, or the network device and the terminal is replaced by communication between multiple terminals (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.).
  • D2D device-to-device
  • V2X vehicle-to-everything
  • terms such as "uplink” and “downlink” can also be replaced by terms corresponding to communication between terminals (for example, "side”).
  • uplink channels, downlink channels, etc. can be replaced by side channels
  • uplinks, downlinks, etc. can be replaced by side links.
  • obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.
  • each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.
  • IoT networks In today's IoT networks, traditional IoT devices are often powered by conventional batteries with limited lifespans, negatively impacting user experience.
  • Billions of conventional batteries are discarded annually, with only a small fraction effectively recycled, negatively impacting the Earth's ecosystem. Maintaining IoT network operations and replacing batteries can be extremely challenging in extreme environmental conditions.
  • Battery-free IoT communications have been proposed, promising improved network performance and sustainability, while expanding their application scenarios. Furthermore, battery-free communications are more environmentally friendly and safer for children and the elderly. By eliminating traditional batteries, device size and cost can be significantly reduced, paving the way for a variety of new applications.
  • the present disclosure proposes a communication method and device, a communication system, a communication device, and a storage medium, which assist the AIoT control device in determining the target device based on the first information by receiving the first information from multiple candidate devices to perform AIoT related operations.
  • the fourth device 103 may be a device that sends the first information.
  • the embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), G
  • GSM registered trademark
  • CDMA2000 Code Division Multiple Access
  • UMB Ultra Mobile Broadband
  • IEEE 802.11 Wi-Fi (registered trademark)
  • IEEE 802.16 WiMAX (registered trademark)
  • IEEE 802.20 Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle
  • FIG2A is an interactive diagram of a communication method provided by an embodiment of the present disclosure.
  • the communication method provided by the present disclosure supports signaling processes and interactions based on a non-service-based architecture (SBA).
  • the method can be executed by a communication system, for example, the communication system 100 shown in FIG1C , wherein the communication system includes a first device and a second device, or the communication system includes a first device and a fourth device, or the communication system includes a first device, a second device, and a fourth device.
  • the communication system further includes a third device.
  • the method includes the following steps:
  • Step 2101 The first device sends a first request to the second device.
  • multiple second devices are multiple candidate AIoT readers.
  • the AIoT controller sends AIoT configuration request information to multiple candidate AIoT readers to request functional configuration information of multiple AIoT readers.
  • the first request may be implemented through an implicit indication.
  • the AIoT controller indicates that the AIoT reader supports the AIoT control function.
  • the AIoT receiving capability includes whether to support receiving information from an AIoT device.
  • Step 2102 The second device sends first information to the first device.
  • the second device sending the first information to the first device may be sending functional configuration information of the second device to the first device based on pre-configuration.
  • the AIoT server sends functional configuration information of multiple AIoT readers to the AIoT controller based on pre-configuration, such as OAM.
  • the functional configuration information can be configured for each TRP, or for each cell, or for each node.
  • the time and/or frequency information of supporting AIoT configuration function, supporting AIoT receiving function, and supporting sending AIoT configuration signaling can be based on the information of each second device, that is, the above information of different second devices may be different.
  • Step 2104 The first device determines a target device.
  • the first device determines a target device from a plurality of second devices based on the first information, where the target device is used to perform the first operation.
  • the first device determines a target device from the plurality of second devices based on received functional configuration information of the plurality of second devices, where the target device is used to perform the first operation.
  • the AIoT controller determines the AIoT reader that configures the AIoT device based on at least one of supporting the AIoT configuration function, supporting the time and/or frequency information of sending AIoT configuration signaling, and power information of sending AIoT configuration.
  • the AIoT controller determines the AIoT reader that receives AIoT device information based on the time and/or frequency information that supports the AIoT receiving function and/or supports the AIoT receiving capability.
  • the AIoT controller selects an AIoT reader from multiple AIoT readers according to task information of the multiple AIoT readers to perform the first operation.
  • the third device may be an AIoT device.
  • the target device performs the first operation based on a service request received from the first device.
  • the AIoT controller sends a RAN perception service request to a specific AIoT reader to request RAN to perform AIoT-related operations.
  • step 2101, step 2102, and step 2103 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.
  • FIG2B is an interactive diagram of a communication method provided by an embodiment of the present disclosure.
  • the communication method provided by the present disclosure supports signaling processes and interactions based on a service-based architecture (SBA).
  • SBA service-based architecture
  • the method can be performed by a communication system, such as the communication system 100 shown in FIG1C , which includes a first device, a second device, and a fifth device.
  • the communication system also includes a third device.
  • the method includes the following steps:
  • Step 2201 The second device sends a third request to the fifth device.
  • the third request is for requesting registration of the second device in the fifth device.
  • the third request includes first information of the plurality of second devices, and the first information may be functional configuration information of the plurality of second devices.
  • the second device may be a RAN AIoT function (or may also be referred to as a RAN AIoT function instance), the fifth device may be an NRF, and the third request may be an AIoT function registration request message.
  • the time and/or frequency information for supporting AIoT configuration function, supporting AIoT receiving function, and supporting sending AIoT configuration signaling may be information based on each TRP, that is, the above information for different TRPs may be different.
  • the time and/or frequency information of supporting AIoT configuration function, supporting AIoT receiving function, and supporting sending AIoT configuration signaling can be based on the information of each second device, that is, the above information of different second devices may be different.
  • the fifth device may be an NRF, which may be a logical function responsible for RAN AIoT function management.
  • the fifth device receives the third request and stores the functional configuration information of the second device.
  • the first feedback is used to indicate that the third request is received and/or that the plurality of second devices complete registration in the fifth device.
  • the NRF receives and stores or updates the AIoT reader function configuration information of the RAN AIoT function instance, and marks the AIoT reader function as being in an available state.
  • the second request is used to request the fifth device to send first information to the first device.
  • the first information is obtained by the fifth device from multiple second devices.
  • the requested AIoT service type may be, for example, inventory, found items, etc.
  • the AIoT controller when an AIoT service is requested, the AIoT controller discovers an optional RAN AIoT function instance that can perform sensing tasks based on local configuration or through the NRF.
  • the AIoT controller sends an AIoT reader function discovery request message to the NRF, where the AIoT reader function discovery request message includes information about the requested service.
  • the requested service information includes at least one of the following: the requested AIoT service type; the AIoT device to be configured; and information about the AIoT device to be received.
  • Step 2204 The fifth device determines a candidate device.
  • the candidate device determined by the fifth device may be one or more candidate devices determined from a plurality of second devices based on the second request and the third request.
  • the fifth device selects one or more candidate devices from the plurality of second devices based on the requested AIoT service type, the requested configuration of the AIoT device, or the requested reception of information about the AIoT device, and the functional configuration information of the plurality of second devices. In other words, the selected candidate devices satisfy the information included in the second request.
  • NRF selects an instance of the AIoT reader function that meets the conditions based on the information of the requested service.
  • the second feedback includes first information of one or more candidate devices.
  • the first information is the same as the first information included in the third request in step 2201, and will not be repeated here.
  • the second feedback can be an AIoT reader function discovery feedback message.
  • the NRF sends an AIoT reader function discovery feedback message to the AIoT controller.
  • the AIoT reader function discovery feedback message includes one or more instances of the AIoT reader function that meet the conditions, and each instance includes at least one of the following information: RANAIoT function instance ID; RANAIoT function instance IP address or domain name information; AIoT reader function configuration information.
  • the function configuration information of the AIoT reader includes one or more AIoT TRP information, wherein each TRP information supporting AIoT includes at least one of the following: TRP ID; cell ID; TRP location information; support for TRP configuration function, used to indicate that the TRP or cell or node supports the transmission of configuration information to the AIoT device; support for AIoT receiving function, used to indicate that the TRP or cell or node supports the reception of information from the AIoT device; support for the time and/or frequency information of sending AIoT configuration signaling; support for the time and/or frequency information of AIoT receiving capability; power information for sending AIoT configuration; RAN AIoT function instance ID; IP address or domain name information.
  • the first information sent by the fourth device to the first device may include task information of multiple second devices.
  • Step 2207 The first device determines the target device.
  • the AIoT controller determines the AIoT reader that configures the AIoT device based on at least one of supporting the AIoT configuration function, supporting the time and/or frequency information of sending AIoT configuration signaling, and power information of sending AIoT configuration.
  • the AIoT controller determines the AIoT reader that receives IOT device information based on the time and/or frequency information that supports the AIoT receiving function and/or supports the AIoT receiving capability.
  • the first device selects a target device from the plurality of second devices to perform the first operation based on task information of the plurality of second devices.
  • the first operation includes at least one of: sending the second information to a third device; receiving the third information from the third device; performing an inventory; performing a locate; performing a read operation; or performing a write operation.
  • Step 2208 perform the first operation.
  • the target device performs the first operation based on the AIoT service request sent by the first device.
  • the third device may be an AIoT device.
  • obtaining comprehensive and accurate AIoT reader function configuration information helps to select a suitable AIoT reader to perform AIoT-related operations, thereby improving flexibility and reliability.
  • the communication method involved in the embodiment of the present disclosure may include at least one of steps 2201 to 2208.
  • step 2201 may be tried as an independent embodiment
  • step 2203 may be implemented as an independent embodiment, and so on, but the present invention is not limited thereto.
  • step 2202 and step 2206 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.
  • Figure 3A is a flow chart of the communication method provided by the first device according to an embodiment of the present disclosure.
  • the present disclosure embodiment relates to a communication method, which includes:
  • Step 3101 Send a first request to the second device.
  • step 3101 can refer to the optional implementation of step 2101 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.
  • Step 3102 Receive first information sent by the second device.
  • step 3102 please refer to the optional implementations of step 2102 in FIG. 2A and other related parts of the embodiment involved in FIG. 2A, which will not be described in detail here.
  • step 3103 please refer to the optional implementations of step 2103 in FIG. 2A and other related parts of the embodiment involved in FIG. 2A , which will not be described in detail here.
  • step 3104 please refer to the optional implementations of step 2104 in FIG. 2A and other related parts of the embodiment involved in FIG. 2A , which will not be described in detail here.
  • step 3105 please refer to the optional implementations of step 2105 in FIG. 2A and other related parts of the embodiment involved in FIG. 2A , which will not be described in detail here.
  • the communication method involved in the embodiment of the present disclosure may include at least one of steps 3101 to 3105.
  • step 3101 may be tried as an independent embodiment
  • step 3102 may be implemented as an independent embodiment, and so on, but is not limited thereto.
  • Step 3101+3102, step 3102+3104, step 3103+3104, step 3101+3102+3104, step 3102+3104+3105, step 3101+3102+3103, step 3102+3103+3104, step 3103+3104+3105, step 3101+3102+3103+3104, step 3102+3103+3104+3105, step 3101+3102+3103+3104+3105 can be implemented as independent embodiments, but are not limited to this.
  • step 3103 the execution order of step 3103 is not limited, and it can be executed at any time before step 3104.
  • each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.
  • Step 3201 Send a second request to the fifth device.
  • step 3201 can refer to the optional implementation of step 2203 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.
  • Step 3202 Receive second feedback sent by the fifth device.
  • step 3202 can refer to the optional implementation of step 2205 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.
  • Step 3205 perform the first operation.
  • step 3205 can refer to the optional implementation of step 2208 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.
  • the communication method involved in the embodiments of the present disclosure may include at least one of steps 3201 to 3205.
  • step 3201 can be implemented as an independent embodiment
  • step 3202 can be implemented as an independent embodiment, and so on, but is not limited thereto.
  • Steps 3201+3202, step 3203+3204, step 3203+3204+3205, step 3201+3202+3204, step 3201+3202+3203+3204, step 3201+3202+3204+3205, and step 3201+3202+3203+3204+3205 can be implemented as independent embodiments, but are not limited thereto.
  • steps 3201 , 3202 , and 3203 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • the execution order of step 3203 is not limited.
  • each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.
  • FIG3C is a flow chart of a communication method provided by a first device according to an embodiment of the present disclosure.
  • the present disclosure embodiment relates to a communication method, which includes:
  • Step 3301 obtain first information.
  • the first information is used to indicate functions and/or tasks of the plurality of second devices.
  • step 3301 can be found in step 2102 and step 2103 of Figure 2A, step 2205 and step 2206 of Figure 2B, step 3102 of Figure 3A, step 3202 and step 3203 of Figure 3B, and other related parts in the embodiments involved in Figures 2A, 2B, 3A and 3B, which will not be repeated here.
  • Step 3302 Determine a target device from multiple second devices based on the first information.
  • step 3301 can be found in step 2104 of Figure 2A, step 2206 of Figure 2B, step 3103 of Figure 3A, the optional implementation of step 3204 of Figure 3B, and other related parts in the embodiments involved in Figures 2A, 2B, 3A, and 3B, which will not be repeated here.
  • Figure 4A is a flow chart of the communication method provided by the second device according to an embodiment of the present disclosure.
  • the present disclosure embodiment relates to a communication method, which includes:
  • Step 4101 Receive a first request sent by a first device.
  • step 4101 can refer to the optional implementation of step 2101 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.
  • Step 4102 Send first information to the first device.
  • step 4102 can refer to the optional implementation of step 2102 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.
  • Step 4103 perform the first operation.
  • the communication method involved in the embodiments of the present disclosure may include at least one of steps 4101 to 4103.
  • step 4101 can be implemented as an independent embodiment
  • step 4102 can be implemented as an independent embodiment, and so on, but the present invention is not limited thereto.
  • steps 4102+4103 and steps 4101+4102+4103 can be implemented as independent embodiments, but the present invention is not limited thereto.
  • step 4101 is optional and may be omitted or replaced in different embodiments.
  • each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.
  • Figure 4B is a flow chart of the communication method provided by the second device according to an embodiment of the present disclosure.
  • the embodiment of the present disclosure relates to a communication method, which includes:
  • Step 4201 Send a third request to the fifth device.
  • step 4201 can refer to the optional implementation of step 2201 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.
  • Step 4202 Receive first feedback sent by the fifth device.
  • step 4202 can refer to the optional implementation of step 2202 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.
  • Step 4203 perform the first operation.
  • step 4203 can refer to the optional implementation of step 2207 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.
  • the communication method involved in the embodiments of the present disclosure may include at least one of steps 4201 to 4203.
  • step 4201 can be implemented as an independent embodiment
  • step 4202 can be implemented as an independent embodiment, and so on, but the present invention is not limited thereto.
  • steps 4201+4202 and steps 4201+4202+4203 can be implemented as independent embodiments, but the present invention is not limited thereto.
  • step 4202 is optional and may be omitted or replaced in different embodiments.
  • FIG4C is a flow chart of a communication method for a second device according to an embodiment of the present disclosure.
  • the present disclosure embodiment relates to a communication method, which includes:
  • Step 4301 sending the first message.
  • step 4301 can be found in step 2102 of Figure 2A, step 2201 of Figure 2B, step 4102 of Figure 4A, the optional implementation of step 4201 of Figure 4B, and other related parts in the embodiments involved in Figures 2A, 2B, 4A, and 4B, which will not be repeated here.
  • Step 5101 sending the first message.
  • the first information is used to indicate tasks of the plurality of second devices.
  • the first information is used to assist the first device in determining a target device, and the target device is used to perform the first operation.
  • step 5101 can refer to the optional implementation of step 2103 in Figure 2A, step 2206 in Figure 2B, and other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.
  • FIG6A is a flow chart of the communication method provided by the fifth device according to an embodiment of the present disclosure.
  • the present disclosure embodiment relates to a communication method, which includes:
  • Step 6101 Receive a third request sent by the second device.
  • step 6101 can refer to the optional implementation of step 2201 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.
  • step 6102 can refer to the optional implementation of step 2202 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.
  • Step 6103 Receive a second request sent by the first device.
  • step 6103 can refer to the optional implementation of step 2203 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.
  • Step 6104 determine candidate devices.
  • step 6104 can refer to the optional implementation of step 2204 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.
  • Step 6105 Send second feedback to the first device.
  • step 6105 can refer to the optional implementation of step 2205 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.
  • the communication method may include at least one of steps 6101 to 6105.
  • step 6101 may be implemented as an independent embodiment
  • step 6103 may be implemented as an independent embodiment, and so on, but is not limited thereto.
  • Steps 6101+6102, step 6101+6103, step 6101+6103+6104, step 6101+6103+6104+6105, and step 6101+6102+6103+6104+6105 may be implemented as independent embodiments, but are not limited thereto.
  • each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.
  • Step 6201 sending the first message.
  • the first information is used to indicate functions of one or more candidate devices among the multiple second devices.
  • the first information is used to assist the first device in determining a target device from the one or more candidate devices.
  • the target device is used to perform the first operation.
  • step 6201 can refer to the optional implementation of step 2205 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.
  • Step 6201 may be combined with step 6104 of FIG. 6A .
  • the above method may include the method described in the above embodiments of the first device side, the second device side, the fourth device side, the fifth device side, etc., which will not be repeated here.
  • each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.
  • FIG7A is an interactive diagram of a communication method provided by an embodiment of the present disclosure:
  • the configuration request information is a display indication, for example, the configuration request information indicates the requested configuration information in detail, and the functional configuration information includes at least one of the following information: the requested TRP list; the requested configuration information type, wherein the requested configuration information type includes at least one of the following information: location information; cell information; AIoT configuration capability; AIoT receiving capability; time-frequency resource information; power information.
  • step 101 can refer to the optional implementation of step 2101 in Figure 2A and other related parts involved in Figure 2A, which will not be repeated here.
  • step 102 one or more AIoT readers send their function configuration information to the AIoT controller.
  • the AIoT server sends task information to the AIoT controller.
  • the AIoTreader sends the function configuration information of the AIoTreader to the AIoTcontroller according to the AIoT configuration request information received in step 101 .
  • the AIoT reader sends the AIoT reader's functional configuration information to the AIoT controller based on pre-configuration (e.g., OAM).
  • the AIoT reader's functional configuration information includes one or more AIoT-supported TRP information, wherein each AIoT-supported TRP information includes at least one of the following information: TRP ID; Cell ID; TRP location information, used to indicate the geographic location of the TRP; support for AIoT configuration function, used to indicate that the TRP or node supports transmission of configuration information to AIoT devices; support for AIoT reception function, used to indicate that the TRP or node supports receiving information from AIoT devices; support for time and/or frequency information for sending AIoT configuration signaling; support for time and/or frequency information for AIoT reception capability; and power information for sending AIoT configuration.
  • Configuration information can be configured per TRP, per cell or per node.
  • the AIoTcontroller can determine the AIoTreader to perform the search or inventory based on at least one of the TRP location information and Cell ID.
  • the AIoT controller can determine the AIoT reader to configure the AIoT device based on at least one of supporting the AIoT configuration function, supporting the time and/or frequency information of sending the AIoT configuration signaling, and power information of sending the AIoT configuration.
  • the AIoT controller can determine the AIoT reader that receives the AIoT device information based on the time and/or frequency information that supports the AIoT receiving function and/or supports the AIoT receiving capability.
  • the TRP location information includes at least one of geographic location information, moving speed information, and a timestamp.
  • step 102 please refer to the optional implementations of steps 2102, 2103, and 2104 in Figure 2A, and other related parts involved in Figure 2A, which will not be repeated here.
  • FIG7B is an interactive diagram of a communication method provided by an embodiment of the present disclosure:
  • the RAN AIoT function instance sends an AIoT function registration request message to the NRF, where the AIoT function registration request message includes the configuration information of the AIoTreader function.
  • the AIoTreader function configuration information may also be included in the AIoTreader function update message to update the configuration information of the AIoTreader function.
  • the configuration information of the AIoT reader function is consistent with the description in step 102 of Figure 7A.
  • NRF receives and stores (or updates) the AIoT READER function configuration information of the RAN AIoT function instance, and marks the AIoT READER function as available.
  • step 201 please refer to the optional implementations of step 2201 in FIG. 2B and other related parts involved in FIG. 2B, which will not be described in detail here.
  • step 202 the NRF confirms that the registration request of the RAN AIoT function is received and sends an AIoT READER function registration feedback message to the AIoT READER function.
  • Step 203 When there is an AIoT business demand, the AIoT CONTROLLER discovers the optional RAN AIoT function instance that performs the perception task based on local configuration or through NRF.
  • the AIoT CONTROLLER sends an AIoT READER function discovery request message to the NRF.
  • the AIoT READER function discovery request message includes information about the requested service.
  • the requested service information includes at least one of the following: the requested AIoT service type, such as inventory or finder; a request to configure an AIoT device; or a request to receive information about an AIoT device.
  • step 203 can refer to the optional implementation of step 2203 in Figure 2B and other related parts involved in Figure 2B, which will not be repeated here.
  • the NRF selects an AIoT READER function instance that meets the conditions based on the information of the requested service, and sends an AIoT READER function discovery feedback message to the AIoT CONTROLLER, wherein the AIoT READER function discovery feedback message includes one or more AIoT READER function instances, and each instance includes at least one of the following information: RAN AIoT function instance ID; RAN AIoT function instance IP address or domain name information; AIoT READER function configuration information.
  • the AIoT server sends task information to the AIoT controller.
  • the AIoT CONTROLLER selects at least one AIoT READER function instance to perform AIoT-related operations based on AIoT business requirements, local configuration, and/or qualified AIoT READER function instance(s) obtained from the NRF.
  • the AIoT CONTROLLER selects at least one AIoT READER function instance to perform AIoT-related operations based on AIoT business requirements, local configuration, and/or task information received from the AIoT server.
  • the factors that determine whether AIoT CONTROLLER selects RAN AIoT function may include at least one of the following information: AIoT TRP information, location, etc.; AIoT function information, such as configuration, reception, etc.; AIoT time and frequency resource information.
  • step 204 can refer to the optional implementation of steps 2204, 2205, 2206, and 2207 in Figure 2B, and other related parts involved in Figure 2B, which will not be repeated here.
  • the AIoT CONTROLLER sends a RAN awareness service request to the specific AIoT READER function instance, requesting the RAN to perform an AIoT-related operation.
  • the AIoT-related operation includes at least one of the following: sending a configuration to an AIoT device; receiving information from an AIoT device; performing an inventory; performing a location; performing a read operation; or performing a write operation.
  • step 205 can refer to the optional implementation of step 2208 in Figure 2B and other related parts involved in Figure 2B, which will not be repeated here.
  • the embodiments of the present disclosure further provide an apparatus for implementing any of the above methods.
  • an apparatus comprising units or modules for implementing each step performed by a terminal in any of the above methods.
  • another apparatus comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.
  • a network device e.g., an access network device, a core network function node, a core network device, etc.
  • the division of the various units or modules in the above device is only a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated.
  • the units or modules in the device can be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and instructions are stored in the memory.
  • the processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device.
  • CPU central processing unit
  • microprocessor a microprocessor
  • the units or modules in the device may be implemented in the form of hardware circuits, and the functions of some or all of the units or modules may be implemented by designing the hardware circuits.
  • the above-mentioned hardware circuits may be understood as one or more processors.
  • the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), and the functions of some or all of the above-mentioned units or modules may be implemented by designing the logical relationship between the components in the circuit.
  • ASIC application-specific integrated circuit
  • the above-mentioned hardware circuit may be implemented by a programmable logic device (PLD).
  • PLD programmable logic device
  • FPGA field programmable gate array
  • it may include a large number of logic gate circuits, and the connection relationship between the logic gate circuits may be configured through a configuration file, thereby implementing the functions of some or all of the above-mentioned units or modules. All units or modules of the above-mentioned devices may be implemented entirely by the processor calling software, or entirely by hardware circuits, or partially by the processor calling software, and the remaining part by hardware circuits.
  • the processor is a circuit with signal processing capabilities.
  • the processor may be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP).
  • the processor may implement certain functions through the logical relationship of a hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable.
  • the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • FIG8A is a schematic diagram of the structure of a first device according to an embodiment of the present disclosure.
  • the first device 8100 includes a transceiver module 8101 and a processing module 8102 .
  • the transceiver module is used to obtain first information, and the first information is used to indicate the functions and/or tasks of multiple second devices.
  • the transceiver module is used to perform at least one of the communication steps such as receiving and/or sending performed by the first device 8100 in any of the above methods (for example, steps 2101, 2102, 2103, 2203, 2205, and 2206, but not limited thereto), which will not be repeated here.
  • the processing module is used to determine a target device from a plurality of second devices based on the first information, and the target device is used to perform the first operation.
  • the above-mentioned processing module is used to execute at least one of the other steps (such as step 2104, step 2207, step 2208, but not limited to these) performed by the first device 8100 in any of the above methods, which will not be repeated here.
  • FIG8B is a schematic diagram of the structure of a second device according to an embodiment of the present disclosure.
  • the second device 8200 may include a transceiver module 8201 .
  • the above-mentioned transceiver module is used to send first information, the first information is used to indicate the function and/or task of the second device, the first information is used to assist the first device in determining the target device, and the target device is used to perform the first operation.
  • the above-mentioned transceiver module is used to execute at least one of the communication steps such as sending and/or receiving performed by the second device 8200 in any of the above methods (for example, step 2102, step 2201, step 2202, but not limited to these), which will not be repeated here.
  • FIG8C is a schematic diagram of the structure of a fourth device according to an embodiment of the present disclosure.
  • the fourth device 8300 may include a transceiver module 8301 .
  • the transceiver module is used to send first information, the first information is used to indicate tasks of multiple second devices, the first information is used to assist the first device in determining a target device, and the target device is used to perform the first operation.
  • the above-mentioned transceiver module is used to execute at least one of the communication steps such as sending and/or receiving (for example, step 2103, step 2206, but not limited to this) performed by the fourth device 8300 in any of the above methods, which will not be repeated here.
  • the communication steps such as sending and/or receiving (for example, step 2103, step 2206, but not limited to this) performed by the fourth device 8300 in any of the above methods, which will not be repeated here.
  • FIG8D is a schematic diagram of the structure of a fifth device according to an embodiment of the present disclosure.
  • the fifth device 8400 may include a transceiver module 8401 .
  • the above-mentioned transceiver module is used to send first information
  • the first information is used to indicate the functions of one or more candidate devices among multiple second devices
  • the first information is used to assist the first device to determine the target device from one or more candidate devices
  • the target device is used to perform the first operation.
  • the fifth device further includes a processing module for executing other steps (eg, step 2204) performed by the fifth device in any of the above methods, which will not be described in detail here.
  • the communication device 9100 includes one or more processors 9101.
  • the processor 9101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit.
  • the baseband processor can be used to process the communication protocol and communication data
  • the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data.
  • the communication device 9100 is used to perform any of the above methods.
  • one or more processors 9101 are used to call instructions to enable the communication device 9100 to perform any of the above methods.
  • the communication device 9100 further includes one or more transceivers 9102.
  • the transceiver 9102 performs the communication steps such as sending and/or receiving in the above method (e.g., steps 2101, 2102, 2103, 2201, 2202, 2203, 2205, 2206, 3101, 3102, 3103, 3201, 3202, 3203, 3301, 4101, 4102, 4201, 4 202, 4301, 5101, 6101, 6102, 6103, 6105, 6201, but not limited thereto), and the processor 9101 executes at least one of the other steps (e.g., steps 2104, 2105, 2204, 2206, 2207, 3104, 3105, 3204, 3205, 3302, 4103, 4203, 6104, but not limited thereto).
  • the communication device 9100 further includes one or more memories 9103 for storing data. Alternatively, all or part of the memories 9103 may be located outside the communication device 9100.
  • the communication device 9100 may include one or more interface circuits 9104.
  • the interface circuits 9104 are connected to the memory 9102 and may be configured to receive data from the memory 9102 or other devices, or to send data to the memory 9102 or other devices. For example, the interface circuits 9104 may read data stored in the memory 9102 and send the data to the processor 9101.
  • the processor 9101 may store a computer program 9105.
  • the computer program 9105 runs on the processor 9101, enabling the communication device 9000 to perform the method described in the above method embodiment.
  • the computer program 9105 may be fixed in the processor 9101. In this case, the processor 9101 may be implemented by hardware.
  • the communication device 9100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 9100 described in the present disclosure is not limited thereto, and the structure of the communication device 9100 may not be limited by FIG. 9A.
  • the communication device may be an independent device or may be part of a larger device.
  • the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.
  • the chip 9200 includes one or more processors 9201.
  • the chip 9200 is configured to execute any of the above methods.
  • chip 9200 further includes one or more interface circuits 9202. Terms such as interface circuit, interface, and transceiver pins may be used interchangeably.
  • chip 9200 further includes one or more memories 9203 for storing data. Alternatively, all or part of memory 9203 may be located external to chip 9200.
  • interface circuit 9202 is connected to memory 9203 and may be used to receive data from memory 9203 or other devices, or may be used to send data to memory 9203 or other devices. For example, interface circuit 9202 may read data stored in memory 9203 and send the data to processor 9201.
  • processor 9201 performs at least one of the other steps (e.g., steps 2104, 2105, 2204, 2206, 2207, 3104, 3105, 3204, 3205, 3302, 4103, 4203, 6104, but not limited thereto).
  • the present disclosure also provides a program product, which, when executed by the communication device 9100, enables the communication device 9100 to perform any of the above methods.
  • the program product is a computer program product.
  • the present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention appartient au domaine technique des communications et concerne un procédé de communication, un dispositif, un système de communication, un dispositif de communication et un support de stockage. Le procédé comprend : un premier dispositif acquérant des premières informations, les premières informations étant utilisées pour indiquer des fonctions et/ou des tâches d'une pluralité de seconds dispositifs ; et sur la base des premières informations, déterminer un dispositif cible parmi la pluralité de seconds dispositifs, le dispositif cible étant utilisé pour exécuter une première opération. En acquérant des informations sur les fonctions et/ou les tâches d'une pluralité de lecteurs AIoT, un dispositif cible est déterminé parmi la pluralité de lecteurs AIoT sur la base des informations sur les fonctions et/ou les tâches afin d'exécuter une opération liée à l'AIoT, améliorant ainsi la flexibilité et la fiabilité.
PCT/CN2024/086101 2024-04-03 2024-04-03 Procédé de communication, dispositif, système de communication, dispositif de communication et support de stockage Pending WO2025208517A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202480026643.5A CN121080019A (zh) 2024-04-03 2024-04-03 一种通信方法及设备、通信系统、通信设备、存储介质
PCT/CN2024/086101 WO2025208517A1 (fr) 2024-04-03 2024-04-03 Procédé de communication, dispositif, système de communication, dispositif de communication et support de stockage

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/086101 WO2025208517A1 (fr) 2024-04-03 2024-04-03 Procédé de communication, dispositif, système de communication, dispositif de communication et support de stockage

Publications (1)

Publication Number Publication Date
WO2025208517A1 true WO2025208517A1 (fr) 2025-10-09

Family

ID=97265890

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/086101 Pending WO2025208517A1 (fr) 2024-04-03 2024-04-03 Procédé de communication, dispositif, système de communication, dispositif de communication et support de stockage

Country Status (2)

Country Link
CN (1) CN121080019A (fr)
WO (1) WO2025208517A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112817665A (zh) * 2021-01-22 2021-05-18 北京小米移动软件有限公司 设备交互方法及装置、存储介质
CN114978899A (zh) * 2022-05-11 2022-08-30 业成科技（成都）有限公司 AIoT设备更新方法和装置
CN116450113A (zh) * 2022-01-06 2023-07-18 青岛海尔科技有限公司 智能设备的业务配置方法和装置、存储介质及电子设备
CN117121569A (zh) * 2023-07-04 2023-11-24 北京小米移动软件有限公司 设备激活方法及设备
US20240070160A1 (en) * 2022-08-31 2024-02-29 Nec Corporation Data processing method and electronic device

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112817665A (zh) * 2021-01-22 2021-05-18 北京小米移动软件有限公司 设备交互方法及装置、存储介质
CN116450113A (zh) * 2022-01-06 2023-07-18 青岛海尔科技有限公司 智能设备的业务配置方法和装置、存储介质及电子设备
CN114978899A (zh) * 2022-05-11 2022-08-30 业成科技（成都）有限公司 AIoT设备更新方法和装置
US20240070160A1 (en) * 2022-08-31 2024-02-29 Nec Corporation Data processing method and electronic device
CN117121569A (zh) * 2023-07-04 2023-11-24 北京小米移动软件有限公司 设备激活方法及设备

Also Published As

Publication number Publication date
CN121080019A (zh) 2025-12-05

Similar Documents

Publication Publication Date Title
WO2025007281A1 (fr) Procédés et dispositifs d'activation de dispositif
WO2025025123A1 (fr) Procédé et appareil de réception de message
WO2025208517A1 (fr) Procédé de communication, dispositif, système de communication, dispositif de communication et support de stockage
WO2025030327A1 (fr) Procédé de détermination d'informations, élément réseau et terminal
CN117336820A (zh) 通信方法、通信装置和系统
WO2025160966A1 (fr) Procédé de communication, premier dispositif, second dispositif et support de stockage
WO2025208538A1 (fr) Procédés de communication, terminaux, dispositifs internet des objets ambiants, dispositifs de réseau et support de stockage
WO2025000165A1 (fr) Procédé d'indication d'informations, terminal, nœud de communication, système de communication et support d'enregistrement
WO2025111947A1 (fr) Procédés de gestion de cycle de vie, procédé d'envoi d'indication, terminaux et dispositifs de réseau
WO2025208279A1 (fr) Procédé et appareil de communication, dispositif de communication, système de communication et support de stockage
WO2025231676A1 (fr) Procédé de communication, et dispositif, système de communication, dispositif de communication et support de stockage
WO2025175585A1 (fr) Procédé d'autorisation de nœud intermédiaire, appareils, dispositifs, système de communication et support de stockage
CN120642531A (zh) 基于环境物联网的通信方法、终端、网络设备及通信系统
WO2025000146A1 (fr) Procédé de traitement d'informations, dispositif de communication, système de communication et support de stockage
WO2025076719A1 (fr) Procédé d'envoi de capacité, procédé d'acquisition de capacité et appareil de communication
WO2025059872A1 (fr) Procédé d'association d'unité de référence de positionnement, terminal, dispositif de réseau et support de stockage
WO2025152049A1 (fr) Procédés et appareils de communication de dispositifs, dispositif, système de communication et support de stockage
WO2025086166A1 (fr) Procédés de mesure de positionnement, appareil, dispositif, système de communication et support de stockage
WO2025050413A1 (fr) Procédé de positionnement, et terminal, dispositif de réseau et support de stockage
WO2025007283A1 (fr) Procédé d'activation de dispositif et dispositif
WO2025208302A1 (fr) Procédé et appareil de communication, dispositif de communication, système de communication et support de stockage
WO2025208519A1 (fr) Procédés et appareils de communication, et support de stockage
CN119605144A (zh) 模型更新方法、终端设备、网络侧设备
WO2025152013A1 (fr) Procédé de communication, premier dispositif, second dispositif, système de communication et support de stockage
WO2025194312A1 (fr) Procédé de communication et système de communication

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

Country of ref document: EP

Kind code of ref document: A1