Communication method and device

Abstract

The invention provides a communication method which can be applied to a first terminal or a chip in the first terminal. The method comprises: receiving first indication information, the first indication information being used for indicating a first terminal to send a carrier and / or charge to a first device, the first indication information being determined according to the capability and / or type of the first device; and sending the carrier and / or charging to the first device according to the first indication information. In the embodiment of the invention, under the condition that the terminal equipment is used as an excitation source, carrier waves and / or energy charging can be flexibly provided for the AIoT equipment under different topological structures.

Description

Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a communication method and apparatus. Background Technology

[0002] With the development of communication technology, the 3rd generation partnership project (3GPP) defined the ambient internet of things (AIoT) technology.

[0003] In AIoT and other related technologies, communication systems can include readers and tags. Readers can be implemented by network devices (e.g., base stations), and tags can be implemented by IoT terminals, such as passive / semi-passive / active tags. Tags have simple functions; some tags may require carrier-assisted communication provided by an excitation source (e.g., a terminal, access network equipment); others may require charging by an excitation source. In some topologies, the reader and excitation source of a tag can be the same device; in other topologies, the reader and excitation source of a tag may be different devices.

[0004] When the terminal device serves as the excitation source, how to flexibly provide carrier and / or power to the tag in different topologies becomes a problem that needs to be solved. Summary of the Invention

[0005] This application provides a communication method and apparatus that, when a terminal device acts as an excitation source, can flexibly provide carrier waves and / or power to AIoT devices under different topologies.

[0006] In a first aspect, a communication method is provided, which can be executed by a first terminal or by a component (such as a chip, chip system, processor or circuit) for the first terminal, without limitation thereof.

[0007] The method includes: receiving first indication information, the first indication information being used to instruct a first terminal to send a carrier wave and / or charge a first device, the first indication information being determined based on the capability and / or type of the first device; and sending a carrier wave and / or charge a first device based on the first indication information.

[0008] In this application, since the first instruction information is determined based on the capabilities and / or type of the AIoT device, even if the reader and the excitation source of the AIoT device are not the same device, the terminal acting as the reader cannot affect the excitation source from sending carrier waves and / or charging to the AIoT device. This makes the technical solution of this application applicable to different topologies, and can flexibly provide carrier waves and / or charging to AIoT devices under different topologies.

[0009] In one possible implementation, the method may further include: receiving service request information, which is used to request the first terminal to communicate with the first device.

[0010] In one possible implementation, the first device may include at least one device, and the first indication information may be used to indicate that the first terminal sends a carrier wave and / or charges to each of the at least one device.

[0011] In one possible implementation, the first device may include a first group of devices, which may include one or more devices. First indication information may be used to indicate that the first terminal transmits a carrier wave and / or charges the first group of devices.

[0012] In one possible implementation, the first indication information can be carried in a non-access stratum (NAS) message.

[0013] In one possible implementation, the first instruction information comes from a first access network device or a second terminal.

[0014] Secondly, a communication method is provided, which can be executed by a first core network element or by a component (such as a chip, chip system, processor or circuit) used in the first core network element, and this application does not limit the method.

[0015] The method includes: acquiring the capabilities and / or type of a first device; sending second information or second indication information, the second information including the capabilities and / or type of the first device, and the second indication information being used to instruct a first terminal to send a carrier wave and / or charge the first device.

[0016] In one possible implementation, obtaining the capabilities and / or type of the first device may include: receiving third information from a second access network device, the third information including the capabilities and / or type of the first device, the second access network device being used to communicate with the first device.

[0017] In one possible implementation, obtaining the capabilities and / or type of the first device may include: receiving fourth information reported by the first device, the fourth information including the capabilities and / or type of the first device.

[0018] In one possible implementation, the capability and / or type of the first device are used to determine whether it is necessary to send a carrier wave and / or charge the first device.

[0019] In one possible implementation, the first device may include at least one device, and the second information may include: the capability and / or type of each of the at least one device; or, the second indication information may be used to indicate: the first terminal to send a carrier and / or charge each of the at least one device.

[0020] In one possible implementation, the first device may include a first group of devices, which may include one or more devices. The second information may include: the capabilities and / or types of the first group of devices; or, second indication information may be used to indicate: the first terminal transmits a carrier wave and / or charges the first group of devices.

[0021] In one possible implementation, the second instruction information or second information is carried in the NAS message.

[0022] Thirdly, a communication method is provided, which can be executed by a first access network device, or by a component (such as a chip, chip system, processor, or circuit) used in the first access network device, without limitation thereof.

[0023] The method includes: receiving fifth information, the fifth information including the capabilities and / or type of the first device; and sending sixth information or third indication information, the sixth information including the capabilities and / or type of the first device, and the third indication information for instructing the first terminal to send a carrier wave and / or charge the first device.

[0024] In one possible implementation, the fifth piece of information may originate from a first core network element. Alternatively, the fifth piece of information may originate from a third access network device, which is different from the first access network device; the fifth piece of information may also originate from a first device.

[0025] In one possible implementation, the fifth piece of information may come from a third access network device; wherein the first access network device is a first distributed unit and the third access network device is a first centralized unit.

[0026] In one possible implementation, the first device may include at least one device. The sixth information may include: the capability and / or type of each of the at least one device; or, the third indication information may be used to indicate: the first terminal to send a carrier wave and / or charge each of the at least one device.

[0027] In one possible implementation, the first device may include a first group of devices, which may include one or more devices. The sixth information may include: the capabilities and / or types of the first group of devices; or, the third indication information may be used to indicate: the first terminal transmits a carrier wave and / or charges the first group of devices.

[0028] In one possible implementation, the capability and / or type of the first device can be used to determine whether it is necessary to send a carrier wave and / or charge the first device.

[0029] In one possible implementation, the sixth message or third instruction message can be carried in a NAS message.

[0030] In one possible implementation, sending the sixth information or the third indication information may include: sending the sixth information or the third indication information to the first terminal; or, sending the sixth information or the third indication information to the second terminal, wherein the second user equipment includes user equipment capable of communicating with the first terminal.

[0031] Fourthly, a communication method is provided, which can be executed by a first access network device, or by a component (such as a chip, chip system, processor, or circuit) for the first access network device, without limitation thereof.

[0032] The method includes: receiving fourth indication information, the fourth indication information being used to instruct a first terminal to send a carrier wave and / or charge to a first device; and sending fifth indication information, the third indication information being used to instruct the first terminal to send a carrier wave and / or charge to the first device.

[0033] In one possible implementation, the fourth indication information may come from the first core network element; or, the fourth indication information may come from the third access network device, which is different from the first access network device.

[0034] In one possible implementation, the fourth indication information may come from a third access network device; wherein the first access network device may be a first distributed unit, and the third access network device may be a first centralized unit.

[0035] In one possible implementation, the first device may include at least one device, and the fifth indication information may be used to indicate that the first terminal sends a carrier wave and / or charges to each of the at least one device.

[0036] In one possible implementation, the first device may include a first group of devices, which may include one or more devices. The fifth indication information may be used to indicate that the first terminal transmits a carrier wave and / or charges the first group of devices.

[0037] In one possible implementation, the fourth instruction information may be determined based on the capabilities and / or type of the first device.

[0038] In one possible implementation, the fourth instruction information can be carried in a NAS message.

[0039] In one possible implementation, sending the fifth instruction information includes: sending the fifth instruction information to a first terminal; or, sending the fifth instruction information to a second terminal, wherein the second user equipment may include user equipment capable of communicating with the first terminal.

[0040] Fifthly, a communication method is provided, which can be executed by a first terminal or by a component (such as a chip, chip system, processor, or circuit) for the first terminal, without limitation thereof.

[0041] The method includes: receiving seventh information, the seventh information including the capabilities and / or type of the first device; and transmitting a carrier wave and / or charging to the first device based on the seventh information.

[0042] In one possible implementation, the seventh information may come from the first access network device, or from the second terminal device, or from the first device.

[0043] In one possible implementation, the seventh message can be carried in a NAS message.

[0044] In one possible implementation, the first device may include at least one device that transmits a carrier wave and / or charges the first device, which may include transmitting a carrier wave and / or charging the first device to each of the at least one device.

[0045] In one possible implementation, the first device may include a first group of devices, which may include one or more devices. Sending a carrier wave and / or charging the first device may include sending a carrier wave and / or charging the first group of devices.

[0046] In a sixth aspect, a communication device is provided, which may include modules or units for implementing the methods of any one of the first to fifth aspects.

[0047] For example, the communication device may include a transceiver unit. In some possible implementations, the communication device may also include a processing unit.

[0048] In one design, the communication device is used to implement the method in the first aspect and any possible implementation thereof. The transceiver unit can be configured to: receive first indication information, the first indication information being used to instruct a first terminal to transmit a carrier wave and / or charge to a first device, the first indication information being determined based on the capabilities and / or type of the first device; and transmit the carrier wave and / or charge to the first device according to the first indication information.

[0049] In another design, the communication device is used to implement the method in the second aspect and any of its possible implementations. The processing unit may be used to: acquire the capabilities and / or type of the first device; the transceiver unit may be used to: transmit second information or second indication information, the second information including the capabilities and / or type of the first device, and the second indication information used to instruct the first terminal to transmit a carrier wave and / or charge the first device.

[0050] In another design, the communication device is used to implement the method in the third aspect and any of its possible implementations. The transceiver unit can be used to: receive fifth information, the fifth information including the capabilities and / or type of the first device; and transmit sixth information or third indication information, the sixth information including the capabilities and / or type of the first device, the third indication information being used to instruct the first terminal to transmit a carrier wave and / or charge the first device.

[0051] In another design, the communication device is used to implement the method in the fourth aspect and any possible implementation thereof. The transceiver unit can be used to: receive fourth indication information, which instructs the first terminal to send a carrier wave and / or charge to the first device; and send fifth indication information, which instructs the first terminal to send a carrier wave and / or charge to the first device.

[0052] A seventh aspect provides an apparatus. The apparatus includes at least one processor coupled to at least one memory for storing computer programs or instructions. The at least one processor is configured to retrieve and execute the computer program or instructions from the at least one memory, causing the apparatus to perform methods of any one of the first to fifth aspects and any possible implementation thereof.

[0053] Eighthly, a chip or chip system is provided, the chip including a processor and a communication interface, the processor reading instructions through the communication interface and executing the methods of any one of the first to fifth aspects and any possible implementation thereof.

[0054] Ninthly, a computer-readable storage medium is provided, which stores computer instructions that, when executed on a computer, cause the methods of any one of the first to fifth aspects and any possible implementation thereof to be implemented.

[0055] In a tenth aspect, a computer program product is provided, the computer program product including computer program code, which, when run on a computer, causes the methods in any of the first to fifth aspects and any possible implementation thereof to be implemented.

[0056] Eleventhly, a communication system is provided. The communication system includes a first terminal. The first terminal is used to perform the methods described in the first or fifth aspect and any possible implementation thereof.

[0057] In some possible implementations, the communication system may further include a first core network element. The first core network element is used to perform the methods in the second aspect described above and in any of its possible implementations.

[0058] In some possible implementations, the communication system may further include a first access network device. This first access network device is used to perform the methods described in the third or fourth aspect and any of their possible implementations. Attached Figure Description

[0059] Figure 1 This is a schematic diagram of an excitation source transmitting a carrier wave for reflective communication, provided in an embodiment of this application.

[0060] Figure 2 This is a schematic diagram of a communication system applicable to an embodiment of this application;

[0061] Figure 3 This is a schematic diagram of another communication system to which the embodiments of this application are applicable;

[0062] Figure 4 This is a typical topology of an AIoT system;

[0063] Figure 5 It is the excitation source architecture in a typical AIoT topology;

[0064] Figure 6 These are the topologies of several AIoT systems that rely on carrier reflection for communication;

[0065] Figure 7 This is a flowchart illustrating a communication method provided in an embodiment of this application;

[0066] Figure 8 This is a flowchart illustrating a communication method provided in an embodiment of this application;

[0067] Figure 9 This is a flowchart illustrating a communication method provided in an embodiment of this application;

[0068] Figure 10 This is a flowchart illustrating a communication method provided in an embodiment of this application;

[0069] Figure 11 This is a flowchart illustrating a communication method provided in an embodiment of this application;

[0070] Figure 12This is a flowchart illustrating a communication method provided in an embodiment of this application;

[0071] Figure 13 This is a flowchart illustrating a communication method provided in an embodiment of this application;

[0072] Figure 14 This is a flowchart illustrating a communication method provided in an embodiment of this application;

[0073] Figure 15 This is an exemplary block diagram of an apparatus provided in an embodiment of this application;

[0074] Figure 16 This is an exemplary block diagram of another device provided in the embodiments of this application;

[0075] Figure 17 This is a schematic diagram of a chip system provided in an embodiment of this application. Detailed Implementation

[0076] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0077] The technical solutions provided in this application can be applied to various communication systems, such as 5th generation (5G) or new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, and LTE time division duplex (TDD) systems. The technical solutions provided in this application can also be applied to future communication systems, such as 6th generation (6G) mobile communication systems. Furthermore, the technical solutions provided in this application can be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), and Internet of Things (IoT) communication systems or other communication systems.

[0078] The technical solutions provided in this application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), Internet of Things (IoT) communication systems, or other communication systems.

[0079] In the aforementioned communication system, one device can send signals to or receive signals from another device. These signals may include information, signaling, or data. The device can also be replaced by an entity, network entity, network element, communication device, communication module, node, user equipment, mobile device, communication node, etc. This application describes the system using a device as an example. For instance, the communication system may include at least one terminal device and at least one network device. The network device can send downlink signals to the terminal device, and / or the terminal device can send uplink signals to the network device.

[0080] In this application, the terminal device may also be referred to as a terminal, access terminal, user unit, user equipment (UE), user station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or user device. A terminal device is a device that includes wireless communication capabilities and can provide voice / data connectivity to users. Examples include handheld devices and in-vehicle devices with wireless connectivity. In the embodiments of this application, the terminal device may be a mobile phone, tablet computer, computer with wireless transceiver capabilities, train, airplane, mobile internet device (MID), virtual reality (VR) terminal, augmented reality (AR) terminal, cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), computing device or other processing device connected to a wireless modem, wearable device, etc. Terminal devices can also include wireless terminals in scenarios such as industrial control, vehicle networking, autonomous driving, telemedicine, smart grid, transportation safety, smart cities, and smart homes.

[0081] In some embodiments, the terminal device may be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices; they achieve powerful functions through software support, data interaction, and cloud interaction. Broadly defined, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functionality without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific application function and require the use of other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0082] In this embodiment, the device for implementing the functions of the terminal device can be the terminal device itself, or it can be a device (e.g., a chip system) that supports the terminal device in implementing the functions. This device can be installed in the terminal device or used in conjunction with the terminal device. The chip system can consist of chips or include chips and other discrete components. In this embodiment, the terminal device is used as an example to illustrate the device for implementing the functions of the terminal device, and this does not constitute a limitation on the solution of this embodiment.

[0083] The network device in this application embodiment can be a device used to communicate with terminal devices. The network device can also be called an access network device or a wireless access network device, such as a base station. In this application embodiment, the network device can refer to a radio access network (RAN) node (or device) that connects the terminal device to the wireless network.

[0084] Access network equipment refers to radio access network (RAN) nodes (or devices) that connect terminals to a wireless network; it can also be called a base station. Examples of RAN nodes include: Node B (NB), evolved Node B (eNB), next-generation Node B (gNB), transmission reception point (TRP), radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved Node B, or home Node B (HNB)), base band unit (BBU), or wireless fidelity (Wi-Fi) access point (AP). Furthermore, in a network architecture, access network equipment may include centralized unit (CU) nodes, distributed unit (DU) nodes, or RAN equipment comprising both CU and DU nodes. This includes the RAN equipment of CU nodes and DU nodes, which separates the protocol layer of the eNB in ​​the long term evolution (LTE) system. Some protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU, which is centrally controlled by the CU.

[0085] A base station can be a macro base station, micro base station, relay node, donor node, or a combination thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. A base station can also be a mobile switching center and equipment performing base station functions in D2D, V2X, and M2M communications, network-side equipment in 6G networks, or equipment performing base station functions in future communication systems. A base station can support networks using the same or different access technologies. Optionally, a RAN node can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, access network equipment in V2X technology can be a roadside unit (RSU). The embodiments of this application do not limit the specific technologies or equipment forms used in the network equipment.

[0086] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0087] Core network elements (also known as core network equipment, core network nodes, core network functions, etc.) are a collective term for various functional entities on the network side used to manage users, data transmission, and base station configuration. For example, they may include: access and mobility management function (AMF) network elements, user plane function (UPF) network elements, session management function (SMF) network elements, unified data management (UDM) network elements, and unified data repository (UDR) network elements, etc.

[0088] In some deployments, network devices can be devices that include CUs or DUs, or devices that include both CUs and DUs, or devices that consist of control plane CU nodes (central unit-control plane, CU-CP) and user plane CU nodes (central unit-user plane, CU-UP) and DU nodes. For example, network devices may include gNB-CU-CP, gNB-CU-UP, and gNB-DU.

[0089] In different communication systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an open radio access network (ORAN) system, CU can also be called an open CU (open CU, O-CU), DU can also be called an open DU (open DU, O-DU), CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules.

[0090] In some deployments, multiple RAN nodes collaborate to assist terminals in achieving wireless access, with different RAN nodes each implementing some of the base station's functions. For example, RAN nodes can be CUs, DUs, CU-CPs, CU-UPs, or RUs. CUs and DUs can be configured separately or included in the same network element, such as a BBU. RUs can be included in radio frequency equipment or radio units, such as RRUs, AAUs, or RRHs.

[0091] RAN nodes can support one or more types of fronthaul interfaces, each corresponding to a DU and RU with different functions. If the fronthaul interface between the DU and RU is a common public radio interface (CPRI), the DU is configured to implement one or more baseband functions, and the RU is configured to implement one or more radio frequency functions. If the fronthaul interface between the DU and RU is another type of interface, relative to CPRI, some downlink and / or uplink baseband functions, such as, for downlink, precoding, digital beamforming (BF), or one or more of inverse fast Fourier transform (IFFT) / cyclic prefix addition (CP), are moved from the DU to the RU; for uplink, digital beamforming (BF), or one or more of fast Fourier transform (FFT) / cyclic prefix removal (CP), are moved from the DU to the RU.

[0092] In this embodiment, the apparatus for implementing the functions of a network device can be a network device itself; it can also be an apparatus capable of supporting the network device in implementing those functions, such as a chip system, hardware circuit, software module, or a hardware circuit plus a software module. This apparatus can be installed in the network device or used in conjunction with the network device. In this embodiment, the example of a network device being used to implement the functions of a network device is provided only and does not constitute a limitation on the solutions described in this embodiment.

[0093] Network devices and / or terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network devices and terminal devices are located. Furthermore, terminal devices and network devices can be hardware devices, or software functions running on dedicated hardware or general-purpose hardware, such as virtualization functions instantiated on a platform (e.g., a cloud platform), or entities that include dedicated or general-purpose hardware devices and software functions. This application does not limit the specific form of the terminal devices and network devices.

[0094] With the development of communication technology, the 3rd Generation Partnership Project (3GPP) defined the Ambient Internet of Things (AIoT) technology. AIoT can be based on cellular network communication infrastructure and consists of readers (such as base stations) and passive / semi-passive / active tags (in AIoT technology, tags are terminals within the cellular network, which can be understood as extremely low-power, extremely low-complexity IoT terminals). Its main functions include inventory management, positioning, sensing, and command processing. Typical application scenarios include logistics, warehousing, industrial manufacturing, identity recognition, and environmental monitoring.

[0095] AIoT technology can include network devices and Type I terminal devices; in other words, an AIoT-based communication system can include network devices and Type I terminal devices. The Type I terminal devices can be devices with tag-like functionality. In this case, both the reader / writer and the tag device can be implemented based on cellular network infrastructure. In other words, both the reader / writer and the tag device can be devices within a cellular network. For example, the reader / writer's functionality can be implemented by network devices (such as base stations) or terminals. The tag device can be implemented by terminals within a cellular network, such as ultra-low power, ultra-low complexity IoT terminals, i.e., Type I terminals. Non-contact data communication can be performed between the network device and the Type I terminal, thereby allowing the network device to read information from the Type I terminal and / or write information that needs to be stored into the Type I terminal.

[0096] The main business of AIoT will be described in further detail below.

[0097] For example, the inventory management service can utilize a reader (which can be a base station / terminal) to access tags (AIoT devices) within its coverage area. Successfully connected devices need to send their unique identifier to the reader. This inventory management service, also known as a checklist operation, can obtain tag identification information. For instance, the reader can use query and acknowledge (ACK) commands to retrieve tag identification information. To facilitate tag inventory, tags include four session identifiers, each corresponding to two inventory states: A and B. The inventory state is indicated by a sessionInventoried flag. When the reader selects a tag, the select command sent to it carries a session identifier, and the tag stores this session identifier. When the reader performs an inventory management operation on the tag, the query command sent to it includes this session identifier, at which point the tag can flip its inventory state corresponding to that session identifier from A to B. If the reader sends a query command to perform inventory operations again, the tag will not respond to the reader because the inventory status of the tag is B, thus avoiding the same tag being inventoried multiple times in the same inventory cycle.

[0098] For example, location services use some location signals to locate the position of a tag.

[0099] For example, a sensing service involves tags reporting sensing data to a base station, such as temperature data.

[0100] For example, a command service can be a series of operational instructions. It is understood that a command service can include at least one of a read service, a write service, or a lock service. A read service can read the electronic product code (EPC), tag identifier (TID), content stored in the tag's reserved area, or content stored in the user's storage area from the tag's memory. A write service can perform a write operation on the tag's memory area; that is, the base station (BS) sends a downlink command and data, instructing the tag to write data into its own memory area. A kill service can permanently disable the tag. A lock service can lock the tag's information, preventing read or write operations on the tag. Alternatively, a lock service can also lock a storage area, preventing or allowing read or write operations on that storage area.

[0101] It should be understood that the above business processes are only a specific way of implementing business. Other business processes or operations can also be performed between the tag and the reader, which will not be elaborated here.

[0102] AIoT technology is an extremely low-power, low-complexity Internet of Things (IoT) technology defined at the 3GPP plenary meeting. It can be understood as an extension of passive radio frequency identification (RFID) within 3GPP. Although it shares some principles with RFID, such as similar inventory management processes, 3GPP introduces more value-added scenarios.

[0103] Tags, also known as electronic tags, are commonly referred to as RFID tags. RFID is an abbreviation for Radio Frequency Identification. RFID technology can be divided into three types: active, passive, and semi-active. Passive tags can also be called passive IoT, meaning passive Internet of Things devices. Therefore, they can also be considered a type of terminal.

[0104] A reader / writer can be a handheld or fixed device that reads (and sometimes writes) tag information, as defined in the original definition. It can also be understood as a device that communicates with the tag; its form can be a terminal, a base station, or a node that transmits signals, such as a headend, a Pico Radio Unit (PRU), or a transmission reception point (TRP), or simply a device with read / write capabilities. It can also be an integrated access and backhaul (IAB) node, a smart repeater, or a relay node, etc.

[0105] In AIoT systems and related systems, tags can also be called electronic tags, RFID tags, or tag devices. Alternatively, tags can also be called AIoT terminal devices or AIoT devices. In this application, tags can also be considered as a type of terminal device.

[0106] In one classification method, tags can be categorized into passive tags, semi-passive tags, and active tags. Passive and semi-passive tags can employ backscatter-based communication, while active tags utilize actively generated carrier waves.

[0107] Another classification method divides the tags into the following three types of devices: 1) Device A: No energy storage, cannot generate signals independently, and uses backscatter to transmit signals; 2) Device B: Has energy storage, but cannot generate signals independently, and uses backscatter to transmit signals. Its stored energy can amplify the reflected signal; 3) Device C: Has energy storage, can generate signals independently, and has active radio frequency components for transmission.

[0108] Another classification method can divide the tags into the following types: 1) Device 1: ~1μW peak power consumption, with energy storage function, and initial sampling frequency offset (SFO) of up to 10. X 1) ppm cannot amplify DL and UL signals; it requires an external carrier signal for backscatter communication to enable uplink transmission. 2) Device 2a has a peak power consumption of less than or equal to several hundred μW, possesses energy storage capabilities, and has an initial sampling frequency offset (SFO) of 10. X ppm, capable of DL and / or UL signal amplification, requires an external carrier signal for backscatter communication to enable uplink transmission. 3) Device 2b: Peak power consumption less than or equal to several hundred μW, with energy storage function, and initial sampling frequency offset (SFO) reaching 10. X ppm can amplify DL and / or UL signals and can perform uplink transmission without relying on an externally provided carrier.

[0109] Another classification method involves classifying tags based on one or more of their reflectivity, energy storage capacity, signal amplification capability, or signal generation capability. This application does not limit the specific classification of tags in its embodiments.

[0110] The tag uses a low-precision, low-power mid-to-low frequency ring oscillator or a completely oscillator-less receiver to receive downlink signals. When the tag is working, the energy and carrier for communication are supplied by the reader, and communication is based on a reflected carrier.

[0111] For devices A and B mentioned above, the tags need to rely on carrier wave (CW) for reflection communication, such as... Figure 1 As shown.

[0112] Figure 1 This illustration shows a schematic diagram of an excitation source transmitting a carrier for reflective communication, provided in an embodiment of this application.

[0113] For devices A and B mentioned above, they cannot generate signals independently and use backscattering to transmit signals. Figure 1 The illustrated tag represents a specific implementation of devices A and B mentioned above. The tag is wirelessly powered by the base station and receives downlink communication signals from the base station, but cannot independently send uplink signals to the base station. An auxiliary node transmits an excitation carrier (CW), and the tag uses carrier reflection communication to conduct uplink communication with the base station. The base station transmits a downlink signal (transmit, TX) to the tag and receives an uplink signal (receive, RX) from the tag.

[0114] In one specific implementation, the base station receives uplink signals from the tag via frequency division duplex uplink (FDD UL) and sends downlink signals to the tag via frequency division duplex downlink (FDD DL).

[0115] In one specific implementation, the device that transmits the carrier wave can be a terminal, network device, etc.

[0116] It should be understood that the device that transmits the carrier wave is generally referred to as the helper, or carrier source. The helper can be a terminal, a base station, or a small station. The device only transmits downlink data with the tag, and transmits uplink and downlink data with the reader. This data transmission may be over the air or via a wired connection. This application does not impose any special limitations on this.

[0117] It should be understood that the reader / writer involved in this embodiment can be a handheld or fixed device for reading or writing tag information, or it can be understood as a device that communicates with the tag. The reader / writer can be a terminal device, an access network device, or a device with read / write functionality. The reader / writer can also be an IAB node or a relay node.

[0118] like Figure 1 As shown, the reader / writer can act as an auxiliary node to send carrier signals to the AIoT device, which then receives the carrier signals via an antenna. The AIoT device can adjust the information to be transmitted based on the reflected signal. Through this method, the AIoT device can receive downlink signals using a low-precision, low-power mid-to-low frequency ring oscillator or a completely oscillator-less approach, further reducing the power consumption of downlink reception.

[0119] An AIoT device is a miniature wireless transceiver, primarily consisting of a built-in antenna, coupling element, and chip. The chip in an AIoT device contains storage space that enables a reader to read or write data to the device. After receiving a radio frequency (RF) signal from a reader via its antenna, the AIoT device can couple the RF signal through the coupling element. This coupling channel allows power to be supplied to the chip and the data stored in the chip to be fed back to the reader via the antenna. A communication network based on cellular network infrastructure, consisting of readers and AIoT devices, can be called a passive Internet of Things (IoT) network or an ambient IoT (AIoT or AIoT). AIoT devices can also be considered terminal devices, and can be active, passive, or semi-active AIoT devices (or active tags, passive tags, or semi-passive tags).

[0120] Environmental IoT systems can be applied to passive or semi-passive IoT scenarios. For example, in logistics and warehousing scenarios, AIoT devices can be used for inventory and tracking of goods, as well as for monitoring the status of goods during transportation. In industrial manufacturing scenarios, AIoT devices can be used for environmental and equipment status monitoring.

[0121] Figure 2 A schematic diagram of a communication system to which an embodiment of this application applies is shown.

[0122] First, let's briefly describe the commonly used network elements in the O-RAN system.

[0123] O-RAN central unit (O-CU): Used to implement the radio resource control (RRC) layer, packet data convergence protocol (PDCP) layer, service data adaptation protocol (SDAP) layer, and other control functions in the 3GPP standard.

[0124] O-RAN Central Unit Control Plane (O-CU-CP): Similar to the CU-CP in new radio (NR) systems, it implements the functions of the RRC layer and the control plane functions of the PDCP layer. It is part of the O-CU.

[0125] O-RAN Central Unit User Plane (O-CU-UP): Similar to the CU-UP in the NR system, it is used to implement the functions of the SDAP layer and the user plane functions of the PDCP layer. It is part of the O-CU.

[0126] O-RAN distributed unit (O-DU): Based on low-layer function partitioning, it is used to implement the radio link control (RLC) layer, media access control (MAC) layer, and higher physical layer (Higher PHY) layer in the 3GPP standard. The higher physical layer functions include one or more of the following: forward error correction (FEC) encoding / decoding, scrambling / descrambling, or modulation / demodulation.

[0127] The O-RAN radio unit (O-RU) is based on low-layer function partitioning and is used to implement lower physical layer (PHY) functions and radio frequency (RF) functions in the 3GPP standard. These PHY functions include one or more of the following: Fast Fourier Transform (FFT) / Inverse Fast Fourier Transform (iFFT), digital beamforming, or extraction and filtering of the Physical Random Access Channel (PRACH). It is similar to the Transmission Reception Point (TRP) or Remote Radio Head (RRH) in 3GPP, but includes PHY functions such as FFT / iFFT or PRACH extraction.

[0128] O-RAN Cloud (O-Cloud): As a cloud computing platform, it includes physical infrastructure nodes for hosting O-RAN functions such as RIC and O-DU; it supports software components (such as operating systems, virtual machine monitoring, container runtimes), management and orchestration functions.

[0129] like Figure 2As shown, the communication system includes: a first network unit, a second network unit, a third network unit, an O-eNB, an O-CU-CP, an O-CU-UP, an O-DU, an O-RU, and an O-cloud.

[0130] The aforementioned network elements (also referred to as nodes) can be interconnected. For example, the first network unit connects to the O-cloud via the O2 interface; the first network unit connects to the third network unit, O-eNB, O-CU-CP, O-CU-UP, O-DU, and O-RU via the O1 interface; the first network unit connects to the O-RU via the open fronthaul M-Plane interface; the O-DU connects to the O-RU via the open fronthaul M-Plane interface and the open fronthaul C / U / S-Plane interface; the third network unit connects to the O-eNB, O-CU-CP, O-CU-UP, and O-DU via the E2 interface; the O-CU-CP connects to the O-DU via the F1-c interface; the O-CU-UP connects to the O-DU via the F1-u interface; and the O-CU-CP connects to the O-CU-UP via the E1 interface. Figure 2 For a detailed description of the interface shown, please refer to the existing standards; it will not be repeated here.

[0131] One possible example is that the first network unit can be a service management and orchestration framework (SMO), which functions similarly to a network management system. Alternatively, it can be a network unit with similar functions to the SMO, without limitation.

[0132] One possible example is that the second network unit can be a non-real-time RIC (Non-RTTRIC), used to implement non-real-time intelligent management of RAN functions. This enables AI / ML workflows including model training and updates, and guides applications / functions within the Near-RT RIC based on policies. The Non-RT RIC resides within the SMO module. The second network unit can also be a network unit with similar functionality to the Non-RT RIC; this is not limited.

[0133] One possible example is that the third network unit could be a near-real-time RIC (Near-RTTRIC), used to achieve near real-time intelligent management of the RAN. Through data collection and related operations on the E2 interface, it enables near real-time control and optimization of O-RAN modules and resources. The third network unit could also be a network unit with similar functionality to the Near-RT RIC; there is no limitation on this.

[0134] Figure 3 A schematic diagram of another communication system to which embodiments of this application are applicable is shown.

[0135] like Figure 3 As shown, the access network equipment (RAN, such as eNB, gNB, or next-generation access network equipment) can communicate with the core network (CN) through the backhaul link and with the user equipment (UE) through the air interface.

[0136] In one specific implementation, the baseband unit (BBU) in the access network equipment can communicate with the core network (CN) via a backhaul link, and the radio unit (RU) in the access network equipment can communicate with at least one UE via an air interface. The BBU can communicate with at least one RU via a fronthaul link, and the BBU and RU can be co-located or not.

[0137] The BBU includes at least one control unit (CU) and at least one distributed unit (DU), which can communicate via at least one midhaul link.

[0138] Below, on Figure 2 and Figure 3 A brief description is given of the interfaces involved in the O-RAN architecture shown, as well as the 3GPP interfaces.

[0139] A1 Interface: The interface between Non-RT RIC and Near-RT RIC, used for intelligent and dynamic control of radio resources within the O-RAN. Non-RT RIC provides policies, rich information, and ML model updates to Near-RT RIC through the A1 interface, while Near-RT RIC provides policy feedback to Non-RT RIC through the A1 interface.

[0140] E2 Interface: The E2 interface is an open interface between two endpoints used to connect the Near-RT RIC and the RAN node. RAN nodes include, for example, CU and DU in 5G, O-RAN compatible eNB in ​​4G, O-CU (O-CU-CP and / or O-CU-UP) in O-RAN, and / or O-DU, etc. The RIC can obtain data collection and feedback from the RAN node through the E2 node, and the RAN node can obtain control feedback from the Near-RT RIC through the E2 node.

[0141] O1 Interface: The interface between the management entity in the SMO and the O-RAN module, used for operation management. FCAPS management, software management, and file management are implemented through this interface.

[0142] O2 Interface: The interface between the SMO and the infrastructure management framework that supports O-RAN virtual network functionality.

[0143] The Open Fronthaul CUS-Plane interface includes the control plane (C-Plane), user plane (U-Plane), and synchronization plane (S-Plane). The control plane is used for real-time control between the O-DU and O-RU, such as transmitting beamforming weights from the O-DU to the O-RU or performing power control from the O-DU to the O-RU. The user plane is used to transmit communication data between the DU and RU for access network devices and terminals. The synchronization plane is used by the O-DU to provide clock synchronization for the O-RU.

[0144] NG interface: The interface between NR RAN equipment (such as base stations, CUs, CU-CPs, or CU-UPs) and the NR core network; among them, NG-u is the user plane NG interface, and NG-c is the control plane NG interface.

[0145] Xn interface: The interface between NR RAN devices (such as base stations, CUs, CU-CPs, or CU-UPs); where Xn-u is the user plane Xn interface and Xn-c is the control plane Xn interface.

[0146] X2 Interface: The interface between LTE RAN devices; X2-u is the user plane X2 interface, and X2-c is the control plane X2 interface. In NR, the X2 interface is mainly used in E-UTRA-NR dual connectivity (EN-DC) scenarios, where the master station is an LTE RAN device that connects to the LTE core network through the X2 interface.

[0147] E1 interface: The interface between CU-CP and CU-UP.

[0148] F1-C interface: The interface between CU-CP and DU.

[0149] F1-U interface: The interface between CU-UP and DU.

[0150] 3GPP RAN TR 38.848 specifies four typical topologies for AIoT, as follows: Figure 4 As shown.

[0151] Figure 4 A typical topology of an AIoT system is shown.

[0152] Topology 1: can include base stations (BS) and AIoT devices.

[0153] In Topology 1, AIoT devices communicate directly with the base station bidirectionally, exchanging AIoT data and / or signaling.

[0154] In one specific implementation, the communication between the base station and the AIoT device is via the Uu interface, i.e., air interface communication.

[0155] Topology 2: can include base stations (BS), intermediate nodes (i-nodes), and AIoT devices.

[0156] In the structure of Topology 2, there are intermediate nodes between AIoT devices and base stations. AIoT devices communicate bidirectionally with intermediate nodes, and intermediate nodes communicate bidirectionally with base stations.

[0157] It should be understood that intermediate nodes include, but are not limited to, relays, integrated access and backhaul (IAB) nodes, UEs, etc., and intermediate nodes transmit AIoT data and / or signaling between BS and AIoT devices.

[0158] In one specific implementation, the communication between the intermediate node and the base station is via the Uu interface, i.e., air interface communication.

[0159] Topology 3: can include base stations (BS), auxiliary nodes, and AIoT devices.

[0160] The topology 3 structure is divided into two cases: downlink auxiliary and uplink auxiliary.

[0161] In downlink assisted communication, downlink communication occurs between the base station and the assisted node. The assisted node receives data and / or signaling from the base station, the AIoT device receives data and / or signaling from the assisted node, and the base station receives data and / or signaling from the AIoT device.

[0162] In uplink assisted communication, the base station and the auxiliary node communicate uplink. The base station receives data and / or signaling from the auxiliary node, the auxiliary node receives data and / or signaling from the AIoT device, and the AIoT device receives data and / or signaling from the base station.

[0163] In one specific implementation, the communication between the intermediate node and the base station is via the Uu interface, i.e., air interface communication.

[0164] Topology 4: can include terminal UE and AIoT devices.

[0165] In Topology 4, AIoT devices communicate directly with UE devices in two directions, exchanging AIoT data and / or signaling.

[0166] In one specific implementation, the UE device and the AIoT device communicate via a sidelink.

[0167] In the four topologies mentioned above, when the AIoT device is a passive or semi-passive AIoT device, it cannot actively send signals and needs to rely on carrier reflection communication.

[0168] Figure 5 The excitation source architecture in a typical AIoT topology is shown.

[0169] exist Figure 4 Based on the illustrated topology, the UE can also be located within the coverage area provided by the reader. When the reader is a terminal, the communication between the reader and the UE can be considered as transmission between terminals. When the reader is a base station, the communication between the reader and the UE can be conducted through the Uu interface, i.e., air interface communication.

[0170] like Figure 5 As shown, based on the direct connection architecture of Topology 1, a terminal device can be added as an excitation source to provide carriers for AIoT devices, and the communication between the base station and the terminal device is the Uu interface.

[0171] Based on the topology 2 split architecture, a terminal device can be added as an excitation source. This terminal device only provides a carrier for AIoT devices, and the base station conducts communication.

[0172] Based on the topology 3 split architecture, for the UE-assisted downlink architecture, a carrier can be provided by either the UE or the base station; downlink data from the AIoT device comes from the UE, and uplink data from the AIoT device is sent to the base station. The base station and the terminal device communicate via the Uu interface.

[0173] Based on the topology 3 split architecture, for the UE-assisted uplink architecture, the carrier can be provided by the UE or the base station. The downlink data of the AIoT device comes from the base station, and the uplink data of the AIoT device is sent to the UE.

[0174] It should be understood that the split architecture shown in Topology 3 decouples the uplink and downlink data links of AIoT devices.

[0175] In some alternative implementations, the base station can be an access network device (RAN), such as an eNB, gNB, or next-generation access network device.

[0176] In some alternative implementations, the terminal device can co-locate with the AIoT device, that is, the terminal device and the AIoT device's service base station establish a Uu interface connection.

[0177] In some alternative implementations, the terminal device can be connected to an AIoT device at a different location, that is, the terminal device can establish a Uu interface connection with a service base station that is not an AIoT device.

[0178] Based on the topology 4 direct connection architecture, terminal device 2 can be added as an excitation source to provide carrier for AIoT devices.

[0179] Figure 6 Several AIoT system topologies that rely on carrier-based reflection communication are shown.

[0180] exist Figure 6 In this diagram, the AIoT device is denoted as D, the reader / writer as R, and the excitation source as CW. A link from the reader / writer to the AIoT device that sends data and / or signaling can be denoted as R2D; a link from the AIoT device to the reader / writer that sends data and / or signaling can be denoted as D2R; and a link from the CW node to the AIoT device that sends a carrier wave can be denoted as CW2D.

[0181] like Figure 6 As shown in (a), a base station can be used as a CW node.

[0182] The D1T1-A1 architecture can include two readers (R1 and R2). AIoT devices can receive data and / or signaling from R1; AIoT devices can send data and / or signaling to R2. The CW node and R1 can be the same device, but not the same device as R2.

[0183] In the D1T1-A2 structure, the reader can send data and / or signaling to the AIoT device; the same reader can also receive data and / or signaling sent by the AIoT device.

[0184] In the D1T1-A1 and D1T1-A2 structures, the CW node can be within the topology, and the CW node and the reader / writer can be the same device.

[0185] In the D1T1-B structure, the reader can send data and / or signaling to AIoT devices; the same reader can also receive data and / or signaling from AIoT devices. Unlike the D1T1-A2 structure, the CW node can be outside the topology, and the CW node and the reader are different devices.

[0186] In the D1T1-C structure, the CW node can be omitted.

[0187] like Figure 6As shown in (b), the UE can be used as a CW node.

[0188] Similar to the D1T1-A1 structure, the D2T2-A1 structure can include two readers (R1 and R2). The AIoT device receives data and / or signaling from R1; the AIoT device sends data and / or signaling to R2. The CW node and R1 are the same device, but not the same device as R2. Unlike the D1T1-A1 structure, the D2T2-A1 structure can also include a base station capable of communicating with R1 and / or R2.

[0189] In the D2T2-A2 structure, similar to the D1T1-A2 structure, the reader R can send data and / or signaling to the AIoT device; the same reader can also receive data and / or signaling sent by the AIoT device. Unlike the D1T1-A2 structure, this structure may also include a base station capable of communicating with R.

[0190] In the D2T2-B structure, similar to the D1T1-B structure, the reader (denoted as R) can send data and / or signaling to the AIoT device; the same reader can also receive data and / or signaling from the AIoT device. The CW node is outside the topology and is a different device from the reader. Unlike the D1T1-A2 structure, this structure can also include a base station capable of communicating with R.

[0191] In the D2T2-C architecture, a CW node may not be required. This architecture may also include a base station capable of communicating with the R.

[0192] In one possible approach, the UE is used as a reader / writer. Based on the UE's capabilities, it is authenticated and authorized, enabling the UE to act as an excitation source for AIoT devices, providing carrier waves to passive / semi-passive devices. Figure 6 In the scenario shown, other terminals besides the reader / writer may serve as the excitation source for the AIoT device. How to control the excitation source to send carrier waves and / or charge the AIoT device becomes a problem that needs to be solved.

[0193] In summary, this application provides a communication method for providing a carrier wave and / or charging to an AIoT device. In the technical solution of this application, it can be determined whether to provide a carrier wave and / or charging to the AIoT device based on its capabilities and / or type.

[0194] For example, Figure 7This is a flowchart illustrating a communication method provided in an embodiment of this application. The executing entity of this method 700 can be a first terminal, or a component of the first terminal, such as a chip, chip system, processor, or processing circuit; this embodiment does not limit this. The method 700 may include the following steps:

[0195] S710, receive first instruction information, the first instruction information being used to instruct the first terminal to send a carrier wave and / or charge to the first device.

[0196] The first device can be an AIoT device (also known as a tag). The first indication information can be determined based on the capabilities and / or type of the first device. For example, the capabilities of the AIoT device may include one or more of the following: reflection capability (or backscattering capability), energy storage capability, signal amplification capability (such as uplink and / or downlink signal amplification capability, reflection signal amplification capability), and signal generation capability. As another example, the type of AIoT device can be one of device 1, device 2a, or device 2b. In some possible implementations, other methods can be used to classify AIoT devices, and this application embodiment does not limit this.

[0197] For example, core network elements and access network elements can determine whether it is necessary to send carrier waves and / or charge AIoT devices.

[0198] In one embodiment, it is assumed that a first core network element determines whether it is necessary to send a carrier and / or charge to the AIoT device. For example, the first core network element can obtain the capabilities and / or type of the AIoT device, and determine whether it is necessary to send a carrier and / or charge to the AIoT device based on the capabilities and / or type of the AIoT device. When it is necessary to send a carrier and / or charge to the AIoT device, the first core network element can send indication information #1 to instruct the UE to send a carrier and / or charge to the AIoT device; correspondingly, the access network device (such as a base station, CU, DU, etc.) can receive the indication information #1 and send indication information #2 to the UE to instruct the UE to send a carrier and / or charge to the AIoT device.

[0199] In another embodiment, the access network device (such as a base station, CU, DU, etc.) can determine whether it is necessary to send a carrier and / or charge to the AIoT device. For example, a first core network element can obtain the capabilities and / or type of the AIoT device and send information to the access network device, which can indicate the capabilities and / or type of the AIoT device. Accordingly, the access network device can receive this information; when it is necessary to send a carrier and / or charge to the AIoT device, the access network device can send indication information to instruct the UE to send a carrier and / or charge to the AIoT device. For another example, the access network device can act as a reader / writer for the AIoT device, or can communicate with such a reader / writer; the AIoT device can report information containing its capabilities and / or type to its reader / writer, and the access network device can obtain this information.

[0200] For example, under different network architectures, the first information or the first indication information can be sent by different devices. For instance, the first indication information can originate from an access network device. Or, for example, the first indication information can originate from another terminal, such as a second terminal.

[0201] In one embodiment, a first core network element or access network device may determine whether it is necessary to send a carrier wave and / or charge to the AIoT device. The first core network element or access network device may directly or indirectly send indication information to a second terminal to instruct the first terminal to provide a carrier wave and / or charge to the AIoT device; correspondingly, the second terminal may receive the indication information. The second terminal is a terminal device capable of communicating with the first terminal, and the second terminal may send indication information to the first terminal to instruct the first terminal to provide a carrier wave and / or charge to the AIoT device.

[0202] When the first terminal is used to provide a carrier and / or charge the AIoT device, the first terminal can also be referred to as the excitation source of the AIoT device.

[0203] In some possible implementations, the excitation source and the reader / writer of the AIoT device can be the same device, such as the first terminal. That is, the first terminal can also act as the reader / writer of the AIoT device. The method may further include: receiving service request information, which is used to request the first terminal to communicate with the first device.

[0204] In some possible implementations, the first indication information can be carried in a non-access stratum (NAS) message.

[0205] S720, according to the first instruction information, transmits a carrier wave and / or charges to the first device.

[0206] In one embodiment, the first terminal can send a carrier wave to the AIoT device; the AIoT device can then use this carrier wave to perform backscattering transmission and send data / signaling to its reader / writer.

[0207] In another embodiment, when it is necessary to charge the AIoT device, the first terminal can send carrier waves, radio frequency signals, etc. to the AIoT device; the AIoT device can receive the carrier waves and radio frequency signals and convert them into energy, store the energy, or use the energy to communicate with its reader.

[0208] In some possible implementations, the first terminal can act as an excitation source for at least one AIoT device; the first device may include at least one other device. First indication information can be used to instruct the first terminal to send a carrier wave and / or charge each of the at least one device. The first terminal can send a carrier wave and / or charge each of the at least one device according to the first indication information.

[0209] In some possible implementations, the first device may include a first group of devices, which may include one or more devices. The first indication information is used to instruct the first terminal to send a carrier wave and / or charge the first group of devices. That is, the first terminal can act as an excitation source for a certain group of AIoT devices; the first indication information can instruct the first terminal to send a carrier wave and / or charge the group of AIoT devices. The first terminal can send a carrier wave and / or charge the group of AIoT devices according to the first indication information.

[0210] In one embodiment, the first indication information may include a first identifier (ID) of the AIoT device that requires / does not require a carrier wave. This first identifier can indicate which AIoT device requires the first terminal to send a carrier wave and / or charge it. For example, the first identifier can reuse existing identifiers, such as task ID, session ID, or transaction ID. Alternatively, the first identifier may be identification information defined to indicate whether a carrier wave needs to be sent to the AIoT device and / or charge it.

[0211] In another embodiment, bit information can be used to indicate whether the first terminal needs to send a carrier wave and / or charge to the first device. For example, when the bit is 0 or 1, it can indicate that a carrier wave and / or charge needs to be sent to the AIoT device; correspondingly, when the bit is 1 or 0, it can indicate that a carrier wave and / or charge does not need to be sent to the AIoT device.

[0212] Through the above technical solution, the first terminal can send a carrier and / or charge to the first device according to the first instruction information, which can be applied to different topologies and application scenarios, so that the excitation source of the AIoT device can send a carrier and / or charge to the AIoT device under different topologies and application scenarios.

[0213] In some possible scenarios, the core network element (e.g., the first core network element) and the access network equipment (e.g., the first access network equipment) can determine whether it is necessary to send a carrier and / or charge to the first device. The following section combines... Figure 8 Describe the methods that the first core network element may execute. Figure 8 The described scheme can be independent of Figure 7 The aforementioned solution, or may also be related to... Figure 7 The aforementioned schemes are combined to form a new scheme, which will be explained in this document and will not be repeated below.

[0214] For example, Figure 8 This is a flowchart illustrating a communication method provided in an embodiment of this application. The executing entity of this method 800 can be a first core network element, or a component of the first core network element, such as a chip, chip system, processor, or processing circuit; this embodiment does not limit this. The method 800 may include the following steps:

[0215] S810, acquire the capability and / or type of the first device.

[0216] For example, the first core network element can be an AMF or tag management function (TMF) network element, an AIoT function (AIoTF) network element, an AIoT management function (AIoTMF) network element, an AIoT-aware core network element / device, an AIoT-enabled core network element / device, or other network elements capable of implementing method 800. This application embodiment does not limit the specific name of the first core network element.

[0217] In one embodiment, an access network device (such as a second access network device) may send information (such as third information) to a first core network element. This information may include the capabilities and / or type of the AIoT device. The second access network device and the first access network device may be the same access network device or different access network devices.

[0218] In another embodiment, the AIoT device may report information (such as fourth information) to the first core network element, which may include its capabilities and / or type.

[0219] In another embodiment, the first core network element can obtain the capabilities and / or types of AIoT devices from other core network elements (such as UDM, UDR, etc.).

[0220] S820, send second information or second instruction information, the second information including the capability and / or type of the first device, the second instruction information being used to instruct the first terminal to send a carrier wave and / or charge the first device.

[0221] In one embodiment, it is assumed that a first core network element determines whether it is necessary to send a carrier and / or charge to the AIoT device. When it is necessary to send a carrier and / or charge to the AIoT device, the first core network element may send second indication information to instruct a first terminal to send a carrier and / or charge to the AIoT device. Accordingly, the access network device may obtain the second indication information and send indication information to instruct the first terminal to send a carrier and / or charge to the AIoT device.

[0222] In another embodiment, it is assumed that the access network device determines whether a carrier wave and / or power supply needs to be sent to the AIoT device. A first core network element can send second information; correspondingly, the access network device can receive this second information. For example, the access network device used to receive the second information and the access network device used to determine whether a carrier wave and / or power supply needs to be sent to the AIoT device can be the same access network device or different access network devices. For another example, assuming the access network device used to receive the second information is a CU, and the access network device used to determine whether a carrier wave and / or power supply needs to be sent to the AIoT device can be a DU, the CU can send information to the DU, which may include the capabilities and / or type of the AIoT device.

[0223] In some possible implementations, the first device includes at least one device, and the second information may include: the type and / or type of each of the at least one device; or, the second indication information may be used to indicate: the first terminal sends a carrier wave and / or charges each of the at least one device.

[0224] In some possible implementations, the first device may include a first group of devices, which may include one or more devices. The second information may include: the type of the first group of devices; or, the second indication information may be used to indicate: the first terminal sends a carrier wave and / or charges the first group of devices.

[0225] In some possible implementations, the second information or second instruction information can be carried in the NAS message.

[0226] Through the above technical solution, the first core network element can send second information or second instruction information, so that the first terminal can know that it needs to send a carrier and / or charge to the first device. It can be applied to different topologies and application scenarios, so that the excitation source of AIoT devices can send carriers and / or charge to AIoT devices under different topologies and application scenarios.

[0227] In some possible scenarios, the first core network element may not communicate directly with the first terminal, but rather through access network equipment; the first indication information received by the first terminal may originate from the access network equipment, such as the first access network equipment. The following section combines... Figure 9 , Figure 10 Describe the methods that the first access network device may perform. Figure 9 or Figure 10 The described solution can be independent of Figure 7 and / or Figure 8 The proposed solution; or, Figure 9 and / or Figure 10 The described solution can Figure 7 and / or Figure 8 The aforementioned schemes are combined to form a new scheme, which will be explained in a unified manner here and will not be repeated below.

[0228] For example, Figure 9 This is a flowchart illustrating a communication method provided in an embodiment of this application. The executing entity of this method 900 can be a first access network device, or it can be a component of the first access network device, such as a chip, chip system, processor, or processing circuit; this embodiment does not limit this. The method 900 may include the following steps:

[0229] S910, receive fifth information, the fifth information including the capability and / or type of the first device.

[0230] For example, the first access network device can be different devices under different network architectures. For instance, the first access network device can be a base station, CU, DU, O-CU, O-DU, etc.

[0231] Assume that the first core network element does not need to determine whether to send a carrier wave and / or charge the AIoT device. In this scenario, the first core network element sends second information, which may include the capabilities and / or type of the AIoT device. The first core network element can send the second information directly or indirectly to the first access network device.

[0232] For example, under different network architectures, the fifth information can be transmitted by different devices. For instance, the fifth information received by the first access network device can originate from a first core network element. In this scenario, the fifth information can correspond to the second information in method 800. As another example, the fifth information received by the first access network device can originate from other access network devices (such as a third access network device). Yet another example is that the fifth information received by the first access network device can originate from the first device. That is, the AIoT device can report its capabilities and / or type to the first access network device. For example, in the case where the first access network device can act as a reader / writer for the AIoT device.

[0233] In one embodiment, the third access network device may receive second information from the first core network element, thereby obtaining the capabilities and / or type of the first device.

[0234] In another embodiment, the third access network device may obtain the capabilities and / or type of the first device from other access network devices.

[0235] S920, transmit sixth information or third instruction information, the sixth information including the capability and / or type of the first device, and the third instruction information used to instruct the first terminal to transmit a carrier wave and / or charge the first device.

[0236] In one embodiment, it is assumed that a first access network device determines whether it is necessary to send a carrier wave and / or charge to the AIoT device. In this scenario, the first access network device may send third indication information.

[0237] In another embodiment, it is assumed that the first access network device does not need to determine whether it needs to send a carrier wave and / or charge to the AIoT device. In this scenario, the first access network device can send the sixth information.

[0238] For example, under different network architectures, the fifth information can be received by different devices. For instance, a first access network device sends third indication information; correspondingly, a first terminal can receive the third indication information and send a carrier wave and / or charge to the AIoT device based on the third indication information. In this scenario, the third indication information can correspond to the first indication information in method 700. As another example, the first access network device sends third indication information or sixth information; correspondingly, other access network devices can receive the third indication information or sixth information and send first indication information to the first terminal based on the third indication information or sixth information. As yet another example, the first access network device sends third indication information; correspondingly, a second terminal receives the third indication information, and the second terminal can send first indication information to the first terminal.

[0239] In some possible implementations, the first device includes at least one device. The sixth information may include: the capability and / or type of each of the at least one device; or, the third indication information may be used to indicate: the first terminal to transmit a carrier wave and / or charge each of the at least one device.

[0240] In some possible implementations, the first device includes a first group of devices, which may include one or more devices. The sixth information may include: the capabilities and / or types of the first group of devices; or, the third indication information may be used to indicate: the first terminal transmits a carrier wave and / or charges the first group of devices.

[0241] In some possible implementations, the sixth or third instruction information can be carried in a NAS message.

[0242] For example, Figure 10 This is a flowchart illustrating a communication method provided in an embodiment of this application. The executing entity of this method 1000 can be a first access network device, or it can be a component of the first access network device, such as a chip, chip system, processor, or processing circuit; this embodiment does not limit this. The method 1000 may include the following steps:

[0243] S1010, Receive fourth instruction information, the fourth instruction information is used to instruct the first terminal to send a carrier wave and / or charge to the first device.

[0244] For example, suppose a first core network element determines whether it needs to send a carrier wave and / or charge the AIoT device. In this scenario, the first core network element sends a second indication message, which instructs the first terminal to send a carrier wave and / or charge the first device.

[0245] For example, under different network architectures, the fourth indication information can come from different devices. For instance, the fourth indication information received by the first access network device can come from a first core network element. In this scenario, the fourth indication information can correspond to the second indication information in method 800. As another example, the fourth indication information received by the first access network device can come from other access network devices (such as a third access network device). In one possible implementation, the third access network device can receive the second indication information from a first core network element.

[0246] S1020, send fifth instruction information, the fifth instruction information is used to instruct the first terminal to send a carrier wave and / or charge to the first device.

[0247] For example, under different network architectures, the fifth indication information can be received by different devices. For instance, a first access network device sends the fifth indication information; correspondingly, a first terminal can receive the fifth indication information and send a carrier wave and / or charge to the AIoT device according to the fifth indication information. In this scenario, the fifth indication information can correspond to the first indication information in method 700. As another example, a first access network device sends the fifth indication information; correspondingly, other access network devices can receive the fifth indication information and send the first indication information to the first terminal according to the fifth indication information. As yet another example, a first access network device sends the fifth indication information; correspondingly, a second terminal can receive the fifth indication information and send the first indication information to the first terminal.

[0248] In some possible implementations, the fourth instruction information can be carried in a NAS message.

[0249] For ease of explanation, the following is combined with Figures 11 to 14 The information transmission methods of methods 700 to 1000 under different network structures and topologies are illustrated by example.

[0250] For example, Figure 11 This is a flowchart illustrating a communication method provided in an embodiment of this application. Figure 11 In the scenario shown, the AIoT device, UE, access network device #1, and first network element can respectively correspond to the first device, first terminal, first access network device, and first core network element in methods 700 to 1000. Figure 11 The scenario shown can serve as an example of the D2T2-A2 topology. For instance, the first network element could be an AMF, TMF, AIoTF, or AIoTMF, etc. Another example is that access network device #1 could be a base station. Yet another example is that the second network element could be a UDM, UDR, etc.

[0251] S1101, the first network element acquires the capabilities and / or type of the AIoT device.

[0252] In one embodiment, the UE can be the excitation source for at least one AIoT device or a group of AIoT devices. Each AIoT device / group of AIoT devices can report its capabilities and / or type, as well as its device ID, to the first network element. For example, the device ID can be a mask for the AIoT device, an electronic product code (EPC), etc. Alternatively, each AIoT device / group of AIoT devices can carry its capabilities and / or type in the registration request message when sending it to the first network element. Or, the capabilities and / or type of the AIoT devices can be carried in other messages; or, each AIoT device / group of AIoT devices can report its capabilities and / or type in a message defined for reporting the capabilities and / or type of the AIoT devices. In this embodiment, the capabilities and / or types of the AIoT devices contained in the above messages can correspond to the fourth information in method 800.

[0253] In another embodiment, the AIoT device may directly report its capabilities and / or type to the first network element; or, the AIoT device may report its capabilities and / or type to the access network device #1, and the access network device #1 may send or forward the capabilities and / or type of the AIoT device to the first network element.

[0254] In another embodiment, through inventory management, the reader of the AIoT device can obtain the IDs and capabilities and / or types of each AIoT device. Assuming the reader can be access network device #1, or a terminal / base station capable of communicating with access network device #1; in this scenario, access network device #1 can obtain the capabilities and / or types of each AIoT device and can send or forward the capabilities and / or types of each AIoT device to the first network element. For example, after one round of inventory management, a list of device IDs can be obtained, which may include one or more AIoT devices; access network device #1 can send the IDs, capabilities, and / or types of the one or more AIoT devices received during inventory management to the first network element via NG application protocol (NGAP) messages. In this embodiment, access network device #1 may correspond to a second access network device; the capabilities and / or types of the AIoT devices contained in the messages sent by access network device #1 may correspond to the third information in method 800.

[0255] In another embodiment, the second network element may pre-store / pre-configure the subscription information of the AIoT device, such as the AIoT device ID, the security protection credential corresponding to the AIoT device ID, the verification status of the AIoT device ID, the location information of the AIoT device (e.g., the ID of the reader / writer most recently used by the AIoT device, the ID of the cell to which it belongs, etc.), the capabilities and / or type of the AIoT device, etc. The first network element can obtain the capabilities and / or type of the AIoT device from the second network element.

[0256] In some possible implementations, the first network element can verify the ID of the AIoT device and / or store the capabilities and / or type of the AIoT device.

[0257] In some possible implementations, after obtaining the IDs and capabilities and / or types of each AIoT device, access network device #1 may not need to report the capabilities and / or types of the AIoT devices to the core network element, or after reporting the capabilities and / or types of the AIoT devices to the core network element, it may not need to wait for instructions from the core network element; and Figure 7 The methods shown are different. Access network device #1 can determine whether it is necessary to send a carrier and / or charge to the AIoT device based on the AIoT device's capabilities and / or type.

[0258] For example, the first network element can send service request information to the reader / writer of the AIoT device via the access network device. This service request information can be carried in a NAS message or a non-NAS message.

[0259] In one embodiment, the service request information may be carried in the same message as the indication information used to instruct the first terminal to send a carrier and / or charge to the AIoT device, or it may be carried in a different message.

[0260] In another embodiment, the service request information may be carried in the same message as information containing the capabilities and / or performance of the AIoT device, or it may be carried in a different message.

[0261] S1102, the core network authenticates the UE.

[0262] By authenticating the UE, it can be determined whether the UE can act as a reader / relay device for AIoT devices.

[0263] For example, the core network's authentication process for the UE may include steps S1102-1 to S1102-4:

[0264] S1102-1, the UE may send a first request message and / or the UE's capability information to the access network device #1. Accordingly, the access network device #1 receives the first request message and / or the UE's capability information.

[0265] The first request information can be used to request authentication of whether the UE can function as a reader / relay device for AIoT devices. The UE's capability information can include the UE's ability to function as a reader / relay device.

[0266] In one embodiment, the UE may send a UECapabilityInformation message to the base station, which may carry the UE's capability information and / or first request information.

[0267] In another embodiment, the UE's capability information and / or first request information can be carried in the NAS message within the RRC establishment completion message. For example, the NAS message can be a registration request message or a timing advance (TA) update message.

[0268] In another embodiment, the UE's capability information and / or first request information may be carried in the NAS message within the RRC Re-establishment Complete Message / RRC Recovery Complete Message.

[0269] In another embodiment, the UE's capability information and / or first request information may be simultaneously carried in other RRC messages sent by the UE to the access network device #1, such as UEAssistanceInformation messages.

[0270] In another embodiment, the UE's capability information and the first request information can be carried in the same or different messages. For example, the UE's capability information and the first request information can be carried in different RRC messages respectively.

[0271] In another embodiment, the first request information may be encrypted using an encryption method negotiated between the UE and the base station.

[0272] S1102-2, Access network device #1 may send a second request message to the core network element to request authentication of whether the UE can act as a reader / relay device for AIoT devices; and / or, Access network device #1 may send the UE's capability information to the core network element.

[0273] For example, a base station can send the NAS message received in the RRC establishment completion message to a core network element. This NAS message may include second request information and / or UE capability information. Alternatively, the NAS message received in the RRC establishment completion message can be sent via an initial UE message.

[0274] S1102-3, the core network authenticates the UE based on the second request information and / or the UE's capability information.

[0275] For example, a core network element can determine whether a UE can act as a reader / relay device for AIoT devices based on the second request information. For instance, the first and second request information may include one or more of the following: UE identification information, key information, encryption algorithm indication information, random numbers, or parameters calculated based on the key algorithm. For example, after receiving the first indication information, the core network element can perform symmetric encryption calculations and compare them with the parameters calculated based on the key algorithm contained in the second request information. If they match, authentication is successful; otherwise, authentication fails.

[0276] In some possible implementations, core network elements can also authenticate the UE by combining the UE's capability information.

[0277] S1102-4, the core network sends the first response information.

[0278] The first response information can indicate that the UE has passed the verification as a reader / relay device for AIoT devices.

[0279] In one embodiment, access network device #1 can receive first response information from the core network and can send the second response information to the UE. For example, access network device #1 can decode the first response information to determine whether the UE's verification as an AIoT device reader / relay device has passed; access network device #1 sends the second response information to the UE to indicate whether its verification as an AIoT device reader / relay device has passed; the second response information can be carried in an existing or new message. As another example, the first response information can be carried in a NAS message, and access network device #1 can forward the NAS message to the UE without needing to decode it.

[0280] For example, when the first network element determines whether it needs to send a carrier and / or charge the AIoT device, method 1100 may include steps S1103 to S1105. When the access network device #1 determines whether it needs to send a carrier and / or charge the AIoT device, method 1100 may include steps S1108 to S1110.

[0281] S1103, the first network element determines whether it needs to send a carrier wave and / or charge the AIoT device based on the type and / or capabilities of the AIoT device.

[0282] When it is necessary to send a carrier and / or charge an AIoT device, steps S1104 and S1105 can be executed. For example, when the second indication information is carried in a non-NAS message, steps S1104a and S1105a can be executed; when the second indication information is carried in a NAS message, steps S1104b and S1105b can be executed.

[0283] S1104a, the first network element sends message #1. Correspondingly, access network device #1 can receive message #1.

[0284] Message #1 includes indication information for instructing the UE to send carrier waves and / or charge power to AIoT devices. The UE can act as an excitation source for at least one AIoT device / a group of AIoT devices. For example, the indication information can instruct the UE to send carrier waves and / or charge power to each of the at least one AIoT device / a group of AIoT devices.

[0285] The first network element can correspond to the first core network element in method 800, and the indication information in message #1 can be used as an example of the second indication information in method 800. Access network device #1 can correspond to the first access network device in method 1000, and the indication information in message #1 can also be used as an example of the fourth indication information in method 1000.

[0286] In some possible implementations, message #1 may also include business request information. That is, the business request information and the second instruction information can be carried in the same message, i.e., message #1.

[0287] Business request information can be used to request a first business activity. For example, business request information may include at least one of a task ID, session ID, and transaction ID. The task ID, session ID, and transaction ID can be used to identify / identify / indicate the first business activity. As another example, the first business activity may include one or more activities such as inventory management, positioning, sensing, and commands (e.g., read / write / lock / deactivate commands). Business request information can be used to trigger AIoT business processes.

[0288] In some possible implementations, the service request information may also include the ID of a non-device-associated radio network layer protocol assigned by the first network element on the interface between the first network element and access network device #1, used by the first network element to identify / identify the first service on the CN-RAN interface. Assume the interface between the first network element and access network device #1 is the first interface. For example, when the first network element is an AMF, the interface between the AMF and access network device #1 is an NG interface, meaning the first interface can be an NG interface. In this scenario, the radio network layer protocol of the first interface, or in other words, the application protocol providing signaling services between the NG-RAN node and the first network element, can be NGAP, a simplified NGAP, or XXAP (where XX refers to the interface defined for the interface between the access network device and the first network element, and AP refers to the application protocol). For example, the first network element can be another network element that supports AIoT (such as TMF / AIoTF / AIoTMF / AIoT-aware CN, or other core network elements / devices that support / enable AIoT). The first interface can be an NG interface, or it can be an interface between another network element that supports AIoT and the access network device. The radio network layer protocol of the first interface (or the application protocol that provides signaling services between the NG-RAN node and the first network element) can be NGAP, or a simplified NGAP, or XXAP. In one embodiment, the first network element can assign a non-device-associated XXAP ID on the first interface, such as an AIoT-associated XXAP ID.

[0289] In some possible implementations, the business request information may also include at least one of the following: device ID, a list of device IDs, a group ID, a cell ID, a RAN ID, an application function (AF) ID, the service area of ​​the AIoT device, the target area of ​​the AIoT device, the inventory cycle, and related data / information for inventory / location / sensing / commands (such as read / write / lock / deactivation commands). For example, for a write command, the related data for the write command could be the data that needs to be written to the AIoT device.

[0290] In some possible implementations, message #1 may also include carrier configuration information.

[0291] For example, the carrier configuration information includes at least one of the following: frequency domain location, number of subcarriers, carrier transmission power, guard interval time, carrier transmission start time, carrier transmission end time, carrier transmission period, and carrier duration.

[0292] For example, by decoding message #1, access network device #1 can obtain the indication information, service request information and / or carrier configuration information carried by message #1.

[0293] S1105a, Access network device #1 sends message #2. Correspondingly, UE receives message #2.

[0294] Message #2 may include indication information for instructing the UE to send a carrier and / or charge to the AIoT device.

[0295] The UE can correspond to the first terminal in method 700, and the indication information in message #2 can be used as an example of the first indication information in method 700. The access network device #1 can correspond to the first access network device in method 1000, and the indication information in message #2 can be used as an example of the fifth indication information in method 1000.

[0296] In some possible implementations, message #2 may also include service request information and / or carrier configuration information.

[0297] In one embodiment, the carrier configuration information can be determined by the access network device #1. For example, message #1 may not include the carrier configuration information; message #2 may include the carrier configuration information.

[0298] Optionally, in step S1106, access network device #1 can send response information #1; correspondingly, the first network element can receive response information #1.

[0299] Response information #1 may include a response to the service request information. After receiving the service request information, access network device #1 can send response information #1.

[0300] In some possible implementations, the response information #1 may include: the ID of a non-device-associated radio network layer protocol assigned by access network device #1 on the interface between the first network element and access network device #1, used by the access network device to identify / identify the first service on the CN-RAN interface. For example, similar to the first interface mentioned above, this interface can be an NG interface or an XX interface. The radio network layer protocol of this interface, or in other words, the application protocol providing signaling services between the RAN node and the first network element, can be NGAP, or a simplified version of NGAP, or XXAP.

[0301] Optionally, in S1107, the UE can send response information #2; correspondingly, the access network device #1 can receive the response information #2.

[0302] Response information #2 may include a response to message #2.

[0303] For example, if steps S1106 and S1107 do not need to be performed, the process can jump to step S1113 after performing step S1105a.

[0304] S1104b, the first network element sends NAS message #1; correspondingly, the access network device #1 can receive the NAS message #1.

[0305] Similar to message #1 in step S1104a, NAS message #1 may include indication information to instruct the UE to send a carrier and / or charge to the AIoT device. In some possible implementations, NAS message #1 may also include service request information and / or carrier configuration information.

[0306] S1105b, Access network device #1 forwards NAS message #1. Correspondingly, the UE receives the NAS message #1.

[0307] Compared to step S1104a, when the NAS message carries indication information, service request information and / or carrier configuration information, the access network device #1 does not need to decode the NAS message #1 and can forward / transmit the NAS message #1.

[0308] For example, after performing step S1105b, you can jump to step S1113.

[0309] S1108, the first network element sends message #3. Correspondingly, access network device #1 can receive message #3.

[0310] Message #3 may include the capabilities and / or types of AIoT devices. For example, message #3 may include the capabilities and / or types of each AIoT device / group of AIoT devices.

[0311] In some possible implementations, message #3 may also include business request information. That is, the capabilities and / or type of the AIoT device, along with the business request information, can be carried in the same message, i.e., message #3.

[0312] The first network element can correspond to the first core network element in method 800. The capabilities and / or type of the AIoT device carried in message #3 can serve as an example of the second information in method 800. The access network device #1 can correspond to the first access network device in method 900. The capabilities and / or type of the AIoT device carried in message #3 can also serve as an example of the fifth information in method 900.

[0313] S1109, Access network device #1 determines whether it is necessary to send a carrier and / or charge to the AIoT device based on the capabilities and / or type of the AIoT device.

[0314] When it is necessary to send a carrier wave and / or charge an AIoT device, step S1110 can be performed.

[0315] S1110, Access network device #1 sends message #4. Correspondingly, UE receives message #4.

[0316] Message #4 may include indication information to instruct the UE to send a carrier and / or charge to the AIoT device.

[0317] In some possible implementations, message #4 may also include service request information and / or carrier configuration information.

[0318] For example, indication information sent by the access network device to the UE, or carrier configuration information configured by the access network device for the UE, can be sent via RRC messages, media access control control element (MAC CE), or downlink control information (DCI). For instance, message #4 can be an RRC message.

[0319] The UE may correspond to the first terminal in method 700, and the indication information may serve as an example of the first indication information in method 700. Access network device #1 may correspond to the first access network device in method 900, and the indication information in message #4 may serve as an example of the third indication information in method 900.

[0320] Optionally, in step S1111, access network device #1 can send response information #3; correspondingly, the first network element can receive response information #3.

[0321] Response information #3 may include responses to business request information.

[0322] Optionally, in S1112, the UE can send response information #2; correspondingly, the access network device #1 can receive the response information #2.

[0323] Response information #2 may include a response to message #4.

[0324] For example, if steps S1111 and S1112 do not need to be executed, step S1110 can be skipped to step S1113.

[0325] S1113, sends a carrier wave and / or charges the AIoT device.

[0326] In one embodiment, the UE can function as both a reader / writer for the AIoT device and an excitation source for the AIoT device.

[0327] For example, Figure 12 This is a flowchart illustrating a communication method provided in an embodiment of this application. Figure 12 In the scenario shown, the AIoT device, UE, and first network element can respectively correspond to the first device, first terminal, and first core network element in methods 700 to 1000. For example, Figure 12 The scenario shown can also serve as an example of the topology of D2T2-A2; and Figure 11 The scenarios shown are different, in Figure 12 In the scenario shown, the base station can adopt a separate architecture. For example, access network device #2 can be a CU, and access network device #3 can be a DU. For another example, when access network device #2 corresponds to the first access network device, access network device #3 can be an example of other access network devices besides the first access network device; when access network device #3 corresponds to the first access network device, access network device #2 can be an example of other access network devices besides the first access network device (such as a third access network device).

[0328] S1201, the first network element acquires the capabilities and / or type of the AIoT device.

[0329] For a description of the capabilities and / or types of AIoT devices acquired by the first network element, please refer to step S1101.

[0330] S1202, the core network authenticates the UE.

[0331] For a description of the core network authenticating the UE, please refer to the description of step S1102.

[0332] For example, when the first network element determines whether it needs to send a carrier and / or charge the AIoT device, method 1200 may include steps S1203 to S1209. When the access network device #2 determines whether it needs to send a carrier and / or charge the AIoT device, method 1200 may include steps S1210 to S1216. When the access network device #3 determines whether it needs to send a carrier and / or charge the AIoT device, method 1200 may include steps S1218 to S1223.

[0333] S1203, the first network element determines whether it needs to send a carrier wave and / or charge the AIoT device based on the type and / or capabilities of the AIoT device.

[0334] In one embodiment, the first terminal can serve as an excitation source / carrier source for at least one AIoT device / a group of AIoT devices. The first network element can determine whether it is necessary to send a carrier and / or charge to each AIoT device / group of AIoT devices based on the capabilities and / or type of each of the at least one AIoT device / group of AIoT devices.

[0335] When it is necessary to send a carrier and / or charge an AIoT device, steps S1204 to S1206 can be executed. For example, when the fourth indication information is carried in a non-NAS message, steps S1204a to S1206a can be executed; when the fourth indication information is carried in a NAS message, steps S1204b to S1206b can be executed.

[0336] S1204a, the first network element sends message #1. Correspondingly, access network device #2 can receive message #1.

[0337] Similar to step S1104a, message #1 may include indication information for instructing the UE to send a carrier and / or charge to the AIoT device.

[0338] The first network element can correspond to the first core network element in method 800, and this indication information can serve as an example of the second indication information in method 800. Access network device #2 can correspond to the first access network device in method 1000, and this indication information can also serve as an example of the fourth indication information in method 1000.

[0339] In some possible implementations, message #1 may also include service request information and / or carrier configuration information.

[0340] For example, by decoding message #1, access network device #2 can obtain the indication information, service request information and / or carrier configuration information carried by message #1.

[0341] S1205a, access network device #2 can send message #2; correspondingly, access network device #3 can receive message #2.

[0342] Message #2 may include indication information to instruct the UE to send a carrier and / or charge to the AIoT device.

[0343] In some possible implementations, message #2 may also include service request information and / or carrier configuration information.

[0344] For example, compared to Figure 11 The scene shown Figure 12The scenario shown involves communication between the interfaces of access network device #2 and access network device #3 (i.e., communication between CU and DU). This service request information may also include: an ID of a non-device-associated radio network layer protocol (or, in other words, an application protocol providing signaling services between CU and DU) assigned by the CU on the interface between CU and DU, used by the CU to identify / identify the first service on that interface. For example, this interface could be an F1 interface; the radio network layer protocol of this interface could be F1AP, or a simplified F1AP; the CU could assign a non-device-associated F1AP ID (e.g., AIoT-associated F1AP) on this interface for the CU to identify / identify the first service on that interface.

[0345] For example, by decoding message #2, access network device #3 can obtain the indication information, service request information and / or carrier configuration information carried in message #2.

[0346] S1206a, Access network device #3 can send message #3; correspondingly, UE can receive message #3.

[0347] Message #3 may include indication information to instruct the UE to send a carrier and / or charge to the AIoT device.

[0348] In some possible implementations, message #3 may also include service request information and / or carrier configuration information.

[0349] The UE can correspond to the first terminal in method 700, and the indication information carried in message #3 can be used as an example of the first indication information in method 700. The access network device #3 can correspond to the first access network device in method 1000, and the indication information carried in message #3 can also be used as an example of the fifth indication information in method 1000; correspondingly, the access network device #2 can correspond to the third access network device in method 1000, and the indication information carried in message #2 can be used as an example of the fourth indication information.

[0350] Optionally, in S1207, access network device #2 can send response information #1; correspondingly, the first network element can receive response information #1.

[0351] Response information #1 may include a response to the business request information in message #1.

[0352] In one embodiment, after receiving the service request information, the access network device #2 can send response information #1.

[0353] Optionally, in S1208, access network device #3 can send response information #2; correspondingly, access network device #2 can receive response information #2.

[0354] Response information #2 may include a response to the business request information in message #2.

[0355] In one embodiment, response message #2 may include: an ID of a non-device-associated radio network layer protocol (or, in other words, an application protocol providing signaling services between the CU and DU) assigned by the DU on the interface between the CU and DU, for the DU to identify / identify the first service on that interface. For example, the interface may be an F1 interface, and the radio network layer protocol of the interface may be F1AP; the DU may assign a non-device-associated F1AP ID (e.g., AIoT-associated F1AP) on that interface for the DU to identify / identify the first service on that interface.

[0356] Optionally, in S1209, the UE may send response information #3; correspondingly, the access network device #3 may receive response information #3.

[0357] Response information #3 may include a response to message #3.

[0358] For example, if steps S1207 to S1209 do not need to be executed, the process can jump directly to step S121 after step S1105a is completed.

[0359] S1204b, the first network element sends NAS message #1; correspondingly, the access network device #2 can receive the NAS message #1.

[0360] Similar to message #1 in step S1204a, NAS message #1 may include indication information to instruct the UE to send a carrier and / or charge to the AIoT device. In some possible implementations, NAS message #1 may also include service request information and / or carrier configuration information.

[0361] S1205b, Access network device #2 sends NAS message #1; correspondingly, access network device #3 can receive the NAS message #1.

[0362] S1206b, Access network device #3 sends NAS message #1; correspondingly, UE can receive the NAS message #1.

[0363] Compared to steps S1204a to S1206a, since the NAS message carries indication information, service request information and / or carrier configuration information, access network device #2 and access network device #3 do not need to decode the NAS message #1 and can directly forward the NAS message #1.

[0364] For example, after performing step S1206b, the process can jump to step S1224.

[0365] S1210, the first network element sends message #4. Correspondingly, access network device #2 can receive message #4.

[0366] Message #4 may include the capabilities and / or type of the AIoT device. In some possible implementations, message #4 may also include business request information.

[0367] The first network element can correspond to the first core network element in method 800. The capabilities and / or type of the AIoT device carried in message #4 can serve as an example of the second information in method 800. The access network device #2 can correspond to the first access network device in method 900. The capabilities and / or type of the AIoT device carried in message #4 can also serve as an example of the fifth information in method 900.

[0368] S1211, Access network device #2 determines whether it is necessary to send a carrier and / or charge to the AIoT device based on the capabilities and / or type of the AIoT device.

[0369] When it is necessary to send a carrier wave and / or charge an AIoT device, step S1212 can be performed.

[0370] S1212, Access network device #2 sends message #5. Correspondingly, access network device #3 receives message #5.

[0371] Message #5 may include indication information to instruct the UE to send a carrier and / or charge the AIoT device. Access network device #2 may correspond to the first access network device in method 900, and the capabilities and / or type of the AIoT device carried in message #5 may also serve as an example of the fifth information in method 900.

[0372] In some possible implementations, message #5 may also include service request information and / or carrier configuration information.

[0373] In one embodiment, similar to message #2, the service request information may further include: an ID of a non-device-associated radio network layer protocol assigned by the CU on the interface between the CU and DU, for the CU to identify / identify the first service on that interface.

[0374] S1213, Access network device #3 sends message #6. Correspondingly, UE receives message #6.

[0375] Message #6 may include indication information to instruct the UE to send a carrier and / or charge to the AIoT device.

[0376] The UE may correspond to the first terminal in method 700, and the indication information carried by message #6 may serve as an example of the first indication information in method 700.

[0377] Access network device #3 can correspond to the first access network device in method 1000, and the indication information carried in message #6 can be used as an example of the fifth indication information in method 1000; correspondingly, access network device #2 can correspond to the third access network device in method 1000, and the indication information carried in message #5 can be used as an example of the fourth indication information.

[0378] In some possible implementations, message #6 may also include service request information and / or carrier configuration information.

[0379] Optionally, in S1214, access network device #2 can send response information #4; correspondingly, the first network element can receive response information #4.

[0380] Response information #4 may include a response to the business request information in message #4.

[0381] Optionally, in step S1215, access network device #3 can send response information #5; correspondingly, access network device #2 can receive response information #5.

[0382] Response information #5 may include a response to the business request information in message #5.

[0383] In some possible implementations, similar to response information #2, response information #5 may include: the ID of a non-device-associated radio network layer protocol (or, in other words, the application protocol that provides signaling services between the CU and DU) assigned by the DU on the interface between the CU and DU, for the DU to identify / identify the first service on that interface.

[0384] Optionally, in S1216, the UE may send response information #6; correspondingly, the access network device #3 may receive response information #6.

[0385] Response information #6 can include a response to message #6.

[0386] For example, if steps S1214 to S1216 do not need to be executed, the process can jump directly to step S1224 after step S1213 is completed.

[0387] S1217, the first network element sends message #7. Correspondingly, access network device #2 can receive message #7.

[0388] Similar to message #4 in step S1210, message #7 may include the capabilities and / or types of the AIoT devices. For example, message #7 may include the capabilities and / or types of each of at least one AIoT device / a group of AIoT devices. In some possible implementations, message #7 may also include service request information.

[0389] S1218, Access network device #2 sends message #8. Correspondingly, access network device #3 receives message #8.

[0390] Message #8 may include the capabilities and / or type of the AIoT device. In some possible implementations, message #8 may also include business request information.

[0391] S1219, Access network device #3 determines whether it is necessary to send a carrier and / or charge to the AIoT device based on the capabilities and / or type of the AIoT device.

[0392] When it is necessary to send a carrier wave and / or charge an AIoT device, step S1220 can be performed.

[0393] S1220, Access network device #3 sends message #9. Correspondingly, the UE receives message #9.

[0394] Message #9 may include indication information to instruct the UE to send a carrier and / or charge to the AIoT device.

[0395] The UE may correspond to the first terminal in method 700, and the indication information carried by message #9 may serve as an example of the first indication information in method 700.

[0396] Optionally, in S1221, access network device #2 can send response information #7; correspondingly, the first network element can receive response information #7.

[0397] Response information #7 may include a response to the business request information in message #7.

[0398] Optionally, in S1222, access network device #3 can send response information #8; correspondingly, access network device #2 can receive response information #8.

[0399] Response information #8 may include a response to the business request information in message #8.

[0400] In some possible implementations, similar to response information #2, response information #5 may include: the ID of a non-device-associated radio network layer protocol (or, in other words, the application protocol that provides signaling services between the CU and DU) assigned by the DU on the interface between the CU and DU, for the DU to identify / identify the first service on that interface.

[0401] Optionally, in S1223, the UE may send response information #9; correspondingly, the access network device #3 may receive response information #9.

[0402] Response information #9 can include a response to message #9.

[0403] For example, if steps S1221 to S1223 do not need to be executed, the process can jump directly to step S1224 after step S1220 is completed.

[0404] S1224, Sending carrier waves and / or charging to AIoT devices.

[0405] In one embodiment, the UE can function as both a reader / writer for the AIoT device and an excitation source for the AIoT device.

[0406] For example, Figure 13 This is a flowchart illustrating a communication method provided in an embodiment of this application. Figure 13 In the scenario shown, the AIoT device, UE1, UE2, access network device #1, and the first network element can respectively correspond to the first device, first terminal, second terminal, first access network device, and first core network element in methods 700 to 1000. For example, Figure 13 The scenario shown can serve as an example of the D2T2-A1 topology. For instance, the first network element could be AMF, TMF, AIoTF, or AIoTMF, etc. For example, with... Figure 11 The scenario shown is similar, and access network device #1 can be a base station.

[0407] S1301, the first network element acquires the capabilities and / or type of the AIoT device.

[0408] S1302, the core network authenticates UE2.

[0409] By certifying UE2, it can be determined whether UE2 can serve as a reader / relay device for AIoT devices.

[0410] For example, the first network element can send service request information to UE2. When the service request information is carried in a non-NAS message, steps S1303a and S1304a can be executed; when the service request information is carried in a NAS message, steps S1303b and S1304b can be executed.

[0411] S1303a, the first network element sends message #1. Correspondingly, access network device #1 can receive message #1.

[0412] Message #1 may include business request information. For details regarding business request information, please refer to the relevant documentation in method 1100.

[0413] S1304a, Access network device #1 can send message #2; correspondingly, UE2 can receive message #2.

[0414] Message #2 may include business request information.

[0415] Optionally, in S1305, access network device #1 can send response information #1; correspondingly, the first network element can receive response information #1.

[0416] Response information #1 may include a response to the business request information in message #1.

[0417] Optionally, in S1306, UE2 can send response information #2; correspondingly, access network device #1 can receive response information #2.

[0418] Response information #2 may include a response to the business request information in message #2.

[0419] S1303b, the first network element sends NAS message #1; correspondingly, the access network device #1 can receive the NAS message #1.

[0420] NAS message #1 may include service request information.

[0421] S1304b, Access network device #1 sends NAS message #1; correspondingly, UE2 can receive the NAS message #1.

[0422] Compared to steps S1303a and S1304a, by using NAS messages to carry service request information, access network device #1 does not need to decode the NAS message #1 and can directly forward the NAS message #1.

[0423] For example, when the first network element determines whether it needs to send a carrier and / or charge the AIoT device, method 1300 may include steps S1307 to S1311. When the access network device #1 determines whether it needs to send a carrier and / or charge the AIoT device, method 1300 may include steps S1312 to S1316.

[0424] S1307, the first network element determines whether it needs to send a carrier wave and / or charge the AIoT device based on the capabilities and / or type of the AIoT device.

[0425] When it is necessary to send a carrier and / or charge an AIoT device, steps S1308 and S1309 can be executed. For example, when the second indication information is carried in a non-NAS message, steps S1308a and S1309a can be executed; when the second indication information is carried in a NAS message, steps S1306b and S1307b can be executed.

[0426] S1308a, the first network element sends message #3. Correspondingly, access network device #1 can receive message #3.

[0427] Message #3 includes indication information for instructing the UE to send a carrier and / or charge to the AIoT device.

[0428] In some possible implementations, message #3 may also include carrier configuration information.

[0429] The first network element can correspond to the first core network element in method 800, and the indication information in message #3 can be used as an example of the second indication information in method 800. Access network device #1 can correspond to the first access network device in method 1000, and the indication information in message #3 can also be used as an example of the fourth indication information in method 1000.

[0430] S1309a, Access network device #1 sends message #4. Correspondingly, UE1 receives message #4.

[0431] Message #4 may include indication information for instructing the UE to send a carrier and / or charge the AIoT device. The UE may correspond to the first terminal in method 700, and the indication information in message #4 may serve as an example of the first indication information in method 700. Access network device #1 may correspond to the first access network device in method 1000, and the indication information in message #4 may serve as an example of the fifth indication information in method 1000.

[0432] Optionally, in S1310, access network device #1 can send response information #3; correspondingly, the first network element can receive response information #3.

[0433] Response information #3 can be the response information for message #3.

[0434] Optionally, in S1311, UE1 can send response information #4; correspondingly, access network device #1 can receive the response information #4.

[0435] S1308b, the first network element sends NAS message #2; correspondingly, access network device #1 can receive the NAS message #2.

[0436] S1309b, Access Network Device #1 sends NAS message #2; correspondingly, UE1 can receive the NAS message #2.

[0437] NAS message #2 may include indication information to instruct the UE to send a carrier and / or charge the AIoT device. In some possible implementations, NAS message #2 may also include carrier configuration information.

[0438] S1312, the first network element sends message #5. Correspondingly, access network device #1 can receive message #5.

[0439] Message #5 may include the capabilities and / or types of AIoT devices. For example, message #5 may include the capabilities and / or types of each of at least one AIoT device / a group of AIoT devices.

[0440] S1313, Access network device #1 determines whether it is necessary to send a carrier and / or charge to the AIoT device based on the capabilities and / or type of the AIoT device.

[0441] When it is necessary to send a carrier wave and / or charge an AIoT device, step S1312 can be performed.

[0442] S1314, Access network device #1 sends message #6. Correspondingly, UE1 receives message #6.

[0443] Message #6 may include indication information to instruct the UE to send a carrier and / or charge to the AIoT device.

[0444] In some possible implementations, message #5 and / or message #6 may also include carrier configuration information.

[0445] Optionally, in step S1315, access network device #1 can send response information #5; correspondingly, the first network element can receive response information #5.

[0446] Optionally, in S1316, the UE may send response information #6; correspondingly, the access network device #1 may receive the response information #6.

[0447] Response information #5 and response information #6 can be used as response information for messages #5 and #6, respectively.

[0448] S1317, UE1 sends a carrier wave and / or charges the AIoT device.

[0449] In one possible implementation, Figure 13 The base station in the scenario shown can adopt a separate architecture, consisting of a CU and a DU. In this scenario, with Figure 12 Similarly, actions previously performed by access network device #1 can now be performed by access network device #2 (e.g., corresponding to CU) or access network device #3 (e.g., corresponding to DU). For example, access network device #2 or access network device #3 can determine whether it is necessary to send a carrier wave and / or charge the AIoT device.

[0450] In another possible implementation, Figure 13 The method shown differs from the one described above. When it is necessary to send a carrier and / or charge to the AIoT device, the access network device #1 does not send indication information to UE1 (refer to steps S1307 to S1314), but instead sends it to the reader / relay device of the AIoT device (i.e., Figure 13 UE2 sends indication information to UE1. Further, UE2 sends indication information to UE1, instructing UE1 to send a carrier wave and / or charge the AIoT device; UE1 sends a carrier wave and / or charges the AIoT device according to the indication information. In this scenario, UE2 can correspond to the second terminal in method 700; UE1 can correspond to the first terminal in method 700; the indication information sent by UE2 to UE1 can be used as an example of the first indication information.

[0451] For example, Figure 14 This is a flowchart illustrating a communication method provided in an embodiment of this application. Figure 14 In the scenario shown, the AIoT device and the first network element can respectively correspond to the first device and the first core network element in methods 700 to 1000. Assuming that in... Figure 14 In the scenario shown, the tag is provided with a carrier and / or power by a node outside the topology. For example, Figure 14 The scenario shown can serve as an example of the D2T2-B topology. For instance, access network device #1 can be a base station.

[0452] S1401, the first network element acquires the capabilities and / or type of the AIoT device.

[0453] S1402, the core network authenticates the UE.

[0454] S1403, the first network element sends a service request message to the UE.

[0455] For example, in Figure 14 In the scenario shown, the UE can act as a reader / writer for the AIoT device. The first network element can send service request information to the UE via the access network device. The service request information can be carried in a NAS message or a non-NAS message. The method by which the first network element sends service request information to the UE can be found in steps S1303 to S1304, and will not be repeated here.

[0456] S1404, the first network element determines whether it needs to send a carrier and / or charge to the AIoT device based on the capabilities and / or type of the AIoT device.

[0457] S1405, the first network element sends message #1. Correspondingly, access network device #1 can receive message #1.

[0458] Message #1 includes indication information for instructing the sending of carrier waves and / or charging to AIoT devices.

[0459] In some possible implementations, message #1 may also include carrier configuration information.

[0460] Optionally, in S1406, access network device #1 can send response information #1; correspondingly, the first network element can receive response information #1.

[0461] Response information #1 may include the response information for message #1.

[0462] S1407, Access network device #1 sends a carrier wave and / or charges the AIoT device.

[0463] In one possible implementation, Figure 14 The base station in the scenario shown can adopt a separate architecture, consisting of a CU and a DU. In this scenario, with Figure 12 Similar to the method shown, actions originally performed by access network device #1 can now be performed by access network device #2 (e.g., corresponding to CU) or access network device #3 (e.g., corresponding to DU). For example, unlike method 1400, the first network element does not need to determine whether it needs to send a carrier and / or charge the AIoT device. Similar to method 1200, access network device #2 or access network device #3 can determine whether it needs to send a carrier and / or charge the AIoT device.

[0464] In one embodiment, it is assumed that access network device #2 determines whether it is necessary to send a carrier and / or charge to the AIoT device. Access network device #2 can obtain the capabilities and / or type of the AIoT device (refer to step S1210); based on the capabilities and / or type of the AIoT device, it can send indication information to access network device #3 to instruct the third access network device to send a carrier and / or charge to the AIoT device, similar to steps S1211 to S1212, except that the content indicated by the indication information is different.

[0465] In another embodiment, it is assumed that access network device #3 determines whether it is necessary to send a carrier and / or charge to the AIoT device. Access network device #3 can obtain the capabilities and / or type of the AIoT device (refer to steps S1217 and S1218); based on the capabilities and / or type of the AIoT device, access network device #3 can send a carrier and / or charge to the AIoT device.

[0466] In one possible implementation, with Figure 14 The method shown differs; instead of the access network device #1 sending a carrier and / or charging power to the AIoT device, the UE outside the topology sends a carrier and / or charging power to the AIoT device. Figure 13The scenario is similar, but the UE acting as the reader / writer of the AIoT device (e.g., UE2) and the UE acting as the excitation source of the AIoT device (e.g., UE1) are not the same UE. In this scenario, access network device #1 can send indication information to UE2 to instruct UE1 to send a carrier and / or charge to the AIoT device; UE1 receives the indication information from UE2 and sends a carrier and / or charges to the AIoT device for uplink data / signaling transmission of the AIoT device.

[0467] Among some possible implementations, different Figures 7 to 14 In the described scheme, the first terminal can receive indication information indicating not to send a carrier wave and / or charge to the first device. The first terminal can then, based on this indication information, refrain from sending a carrier wave and / or charge to the corresponding AIoT device. Similarly, the first core network element, the first access network device, etc., can send indication information to instruct the first terminal not to send a carrier wave and / or charge to the first device. The transmission method of this indication information can be similar to... Figures 7 to 14 The transmission method of the indication information used to indicate the transmission of carrier waves and / or charging to the first device is similar and will not be described again here.

[0468] Among some possible implementations, different Figures 7 to 14 In the described scheme, the first terminal can receive information containing the capabilities and / or type of the first device (denoted as the seventh information). Based on this information, the first terminal can determine whether to send a carrier wave and / or charge the AIoT device. This information can come from access network devices, such as base stations, DUs, O-DUs, etc., which can send the information to the first terminal after acquiring the capabilities and / or type of the AIoT device. This information can also come from other terminals; for example, a second terminal can act as a reader / writer for the AIoT device, and the AIoT device can report its capabilities and / or type to the second terminal; the second terminal can then send the seventh information to the first terminal. The seventh information can also come from the first device itself; for example, the first terminal can also act as a reader / writer for the AIoT device, and the AIoT device can report its capabilities and / or type to the first terminal.

[0469] The following combination Figures 1 to 14 The apparatus embodiments of this application are described in detail below. It should be understood that the descriptions of the apparatus embodiments correspond to the descriptions of the method embodiments. Therefore, for details not described in detail, please refer to the method embodiments above; for brevity, some details are omitted.

[0470] Figure 15 This is an exemplary block diagram of an apparatus provided in an embodiment of this application. Figure 15 As shown, the device 10 may include modules or units for implementing the above method embodiments.

[0471] For example, the device 10 may include a transceiver unit 11. The transceiver unit 11 can implement corresponding communication functions. The transceiver unit 11 may also be referred to as a transceiver module, a communication interface, or a communication module.

[0472] In some possible implementations, the device 10 may also include a processing unit 12. The processing unit 12 may also be referred to as a processing module.

[0473] In one design, the device 10 may correspond to the first terminal in the above method embodiments, or to a component of the first terminal (such as a chip, chip system, processor, or circuit).

[0474] The device 10 can implement the steps or processes corresponding to those executed by the first terminal in the above method embodiments, wherein the transceiver unit 11 can be used to perform transceiver-related operations of the first terminal in the above method embodiments.

[0475] For example, the transceiver unit 11 is configured to: receive first instruction information; and transmit a carrier wave and / or charge to the first device according to the first instruction information.

[0476] In some possible implementations, the transceiver unit 11 is also used to receive service request information.

[0477] In another design, the device 10 may correspond to the first core network element in the above method embodiment, or a component of the first core network element (such as a chip, chip system, processor, or circuit).

[0478] For example, processing unit 12 is configured to: acquire the capabilities and / or type of the first device. Transceiver unit 11 is configured to: transmit second information or second instruction information.

[0479] In some possible implementations, the transceiver unit 11 is also used to receive third information from the second access network device.

[0480] In some possible implementations, the processing unit 12 is further configured to: determine whether it is necessary to send a carrier wave and / or charge the first device based on the capability and / or type of the first device.

[0481] In another design, the device 10 may correspond to the first access network device in the above method embodiment, or a component of the first access network device (such as a chip, chip system, processor, or circuit).

[0482] For example, the transceiver unit 11 is configured to: receive the fifth information; and send the sixth information or the third instruction information.

[0483] In some possible implementations, the processing unit 12 is configured to: determine whether it is necessary to send a carrier wave and / or charge the first device based on the capability and / or type of the first device.

[0484] In another design, the device 10 may correspond to the first access network device in the above method embodiment, or a component of the first access network device (such as a chip, chip system, processor, or circuit).

[0485] For example, the transceiver unit 11 is configured to: receive fourth instruction information; and send fifth instruction information.

[0486] It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0487] It should also be understood that the device 10 here is embodied in the form of a functional module. The terms "unit" and "module" here can refer to application-specific integrated circuits (ASICs), electronic circuits, processors (e.g., shared processors, proprietary processors, or group processors, etc.) and memories for executing one or more software or firmware programs, integrated logic circuits, and / or other suitable components supporting the described functions. In an alternative example, those skilled in the art will understand that device 10 may specifically be a terminal device in the above embodiments, used to execute the various processes and / or steps corresponding to the terminal device in the above method embodiments; or, device 10 may specifically be a network device in the above embodiments, used to execute the various processes and / or steps corresponding to the terminal device in the above method embodiments. To avoid repetition, further details are omitted here.

[0488] The apparatus 10 of each of the above-described solutions has the function of implementing the corresponding steps performed by the devices (such as terminal devices, network devices) in the above-described methods. This function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described functions; for example, the transceiver module can be replaced by a transceiver (for example, the sending unit in the transceiver module can be replaced by a transmitter, and the receiving unit in the transceiver module can be replaced by a receiver), and other units, such as processing modules, can be replaced by processors, which respectively execute the transceiver operations and related processing operations in each method embodiment.

[0489] In addition, the transceiver unit 11 can also be a transceiver circuit (for example, it may include a receiving circuit and a transmitting circuit), and the processing unit 12 can be a processing circuit.

[0490] Figure 16This is a schematic diagram of another communication device 20 provided in an embodiment of this application. The device 20 includes a processor 21, which is used to execute computer programs or instructions stored in a memory 22, or to read data / signaling stored in the memory 22, to perform the methods in the above-described method embodiments. Optionally, there may be one or more processors 21.

[0491] Optionally, such as Figure 16 As shown, the device 20 also includes a memory 22 for storing computer programs or instructions and / or data. The memory 22 may be integrated with the processor 21 or may be disposed separately. Optionally, there may be one or more memories 22.

[0492] Optionally, such as Figure 16 As shown, the device 20 also includes a transceiver 23 for receiving and / or transmitting signals. For example, the processor 21 controls the transceiver 23 to receive and / or transmit signals.

[0493] As one approach, the device 20 is used to implement the operations performed by the first terminal in the various method embodiments described above.

[0494] As an alternative, the device 20 can be used to implement the operations performed by the first core network element in the various method embodiments described above.

[0495] As an alternative, the device 20 can be used to implement the operations performed by the first access network device in the various method embodiments described above.

[0496] It should be understood that the processor mentioned in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0497] It should also be understood that the memory mentioned in the embodiments of this application can be volatile memory and / or non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM includes the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0498] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory (storage module) can be integrated into the processor.

[0499] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0500] Figure 17 This is a schematic diagram of a chip system 30 provided in an embodiment of this application. The chip system 30 (or processing system) includes logic circuitry 31 and an input / output interface 32.

[0501] The logic circuit 31 can be a processing circuit in the chip system 30. The logic circuit 31 can be coupled to a memory unit, calling instructions from the memory unit, enabling the chip system 30 to implement the methods and functions of the embodiments of this application. The input / output interface 32 can be an input / output circuit in the chip system 30, outputting processed information from the chip system 30, or inputting data or signaling information to be processed into the chip system 30 for processing.

[0502] As one option, the chip system 30 can be used to implement the operations performed by the first terminal in the various method embodiments described above.

[0503] For example, logic circuit 31 is used to implement the processing-related operations performed by the first terminal in the above method embodiment; input / output interface 32 is used to implement the sending and / or receiving-related operations performed by the first terminal in the above method embodiment.

[0504] As an alternative, the chip system 30 can be used to implement the operations performed by the first core network element in the various method embodiments described above.

[0505] As an alternative, the chip system 30 can be used to implement the operations performed by the first access network device in the various method embodiments described above.

[0506] This application also provides a computer-readable storage medium storing computer instructions for implementing the methods executed by the device in the above-described method embodiments.

[0507] For example, when the computer program is executed by a computer, it enables the computer to implement the methods executed by the terminal device or network device in the various embodiments of the above methods.

[0508] This application also provides a computer program product comprising instructions which, when executed by a computer, implement the methods performed by a terminal device or network device in the above-described method embodiments.

[0509] This application also provides a communication system, including the aforementioned first terminal and first core network element.

[0510] In some possible implementations, the communication system may also include a first access network device.

[0511] The explanations and beneficial effects of the relevant contents in any of the devices provided above can be found in the corresponding method embodiments provided above, and will not be repeated here.

[0512] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0513] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0514] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0515] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0516] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0517] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory, random access memory, magnetic disks, or optical disks.

[0518] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, The method, which applies to a first terminal or a chip in the first terminal, includes: Receive first indication information, the first indication information being used to instruct the first terminal to send a carrier wave and / or charge to the first device, the first indication information being determined based on the capabilities and / or type of the first device; According to the first instruction information, a carrier wave and / or power is sent to the first device.

2. The method according to claim 1, characterized in that, The method further includes: Receive service request information, which is used to request the first terminal to communicate with the first device.

3. The method according to claim 1 or 2, characterized in that, The first device includes at least one device. The first indication information is used to indicate that the first terminal sends a carrier wave and / or charges to each of the at least one device.

4. The method according to any one of claims 1 to 3, characterized in that, The first device includes a first group of devices, which in turn includes one or more devices. The first indication information is used to indicate that the first terminal sends a carrier wave and / or charges the first group of devices.

5. The method according to any one of claims 1 to 4, characterized in that, The first indication information is carried in a non-access stratum (NAS) message.

6. The method according to any one of claims 1 to 5, characterized in that, The first indication information comes from the first access network device or the second terminal.

7. A communication method, characterized in that, The method includes applying a chip to a first core network element or a chip within the first core network element: Acquire the capability and / or type of the first device; Send a second message or a second instruction message, the second message including the capabilities and / or type of the first device, the second instruction message being used to instruct the first terminal to send a carrier wave and / or charge the first device.

8. The method according to claim 7, characterized in that, The capability and / or type of acquiring the first device includes: The third information received from a second access network device includes the capabilities and / or type of the first device, the second access network device being used to communicate with the first device.

9. The method according to claim 7, characterized in that, The capability and / or type of acquiring the first device includes: Receive fourth information reported by the first device, the fourth information including the capabilities and / or type of the first device.

10. The method according to any one of claims 7 to 9, characterized in that, The capability and / or type of the first device are used to determine whether it is necessary to send a carrier wave and / or charge the first device.

11. The method according to any one of claims 7 to 10, characterized in that, The first device includes at least one device. The second information includes: the capabilities and / or type of each of the at least one device; or, The second indication information is used to indicate that the first terminal sends a carrier wave and / or charges to each of the at least one device.

12. The method according to any one of claims 7 to 11, characterized in that, The first device includes a first group of devices, which includes one or more devices; The second information includes: the capabilities and / or type of the first group of devices; or, The second indication information is used to indicate that the first terminal sends a carrier wave and / or charges the first group of devices.

13. The method according to any one of claims 7 to 12, characterized in that, The second indication information or the second information is carried in a non-access stratum (NAS) message.

14. A communication method, characterized in that, The method includes applying a chip to a first access network device or a chip in the first access network device: Receive fifth information, the fifth information including the capabilities and / or type of the first device; Send a sixth message or a third instruction message, the sixth message including the capability and / or type of the first device, and the third instruction message for instructing the first terminal to send a carrier wave and / or charge to the first device.

15. The method according to claim 14, characterized in that, The fifth piece of information comes from the first core network element; or, The fifth piece of information comes from a third access network device, which is different from the first access network device; or... The fifth piece of information comes from the first device.

16. The method according to claim 15, characterized in that, The fifth piece of information comes from the third access network device; Wherein, the first access network device is a first distributed unit (DU), and the third access network device is a first centralized unit (CU).

17. The method according to any one of claims 14 to 16, characterized in that, The first device includes at least one device. The sixth information includes: the capability and / or type of each of the at least one device; or, The third indication information is used to indicate that the first terminal sends a carrier wave and / or charges to each of the at least one device.

18. The method according to any one of claims 14 to 17, characterized in that, The first device includes a first group of devices, which includes one or more devices; The sixth piece of information includes: the capabilities and / or type of the first group of devices; or, The third indication information is used to indicate that the first terminal sends a carrier wave and / or charges the first group of devices.

19. The method according to any one of claims 14 to 18, characterized in that, The capability and / or type of the first device are used to determine whether it is necessary to send a carrier wave and / or charge the first device.

20. The method according to any one of claims 14 to 19, characterized in that, The sixth information or the third indication information is carried in a non-access stratum (NAS) message.

21. The method according to any one of claims 14 to 20, characterized in that, The sending of the sixth message or the third instruction message includes: Send the sixth information or the third indication information to the first terminal; or, The sixth information or the third indication information is sent to the second terminal, wherein the second user equipment includes user equipment capable of communicating with the first terminal.

22. A communication method, characterized in that, The method includes applying a chip to a first access network device or a chip in the first access network device: Receive a fourth instruction message, the fourth instruction message being used to instruct the first terminal to send a carrier wave and / or charge to the first device; Send a fifth instruction message, which instructs the first terminal to send a carrier wave and / or charge to the first device.

23. The method according to claim 22, characterized in that, The fourth instruction information is for the first core network element; or, The fourth indication information comes from a third access network device, which is different from the first access network device.

24. The method according to claim 23, characterized in that, The fourth indication information comes from the third access network device; Wherein, the first access network device is a first distributed unit (DU), and the third access network device is a first centralized unit (CU).

25. The method according to any one of claims 22 to 24, characterized in that, The first device includes at least one device. The fifth indication information is used to indicate that the first terminal sends a carrier wave and / or charges to each of the at least one device.

26. The method according to any one of claims 22 to 25, characterized in that, The first device includes a first group of devices, which includes one or more devices; The fifth indication information is used to indicate that the first terminal sends a carrier wave and / or charges the first group of devices.

27. The method according to any one of claims 22 to 26, characterized in that, The fourth indication information is determined based on the capabilities and / or type of the first device.

28. The method according to any one of claims 22 to 27, characterized in that, The fourth indication information is carried in the Non-Access Stratum (NAS) message.

29. The method according to any one of claims 22 to 28, characterized in that, The sending of the fifth instruction information includes: Send the fifth instruction information to the first terminal; or, The fifth instruction information is sent to the second terminal, wherein the second user equipment includes user equipment capable of communicating with the first terminal.

30. A communication device, characterized in that, include: A module or unit for implementing the method of any one of claims 1 to 29.

31. A communication device, characterized in that, The device includes at least one processor coupled to at least one memory, the at least one processor being configured to execute a computer program or instructions stored in the at least one memory to cause the communication device to perform the method as described in any one of claims 1 to 29.

32. A communication system, characterized in that, It includes a first terminal and a first core network element, wherein the first terminal is used to perform the method as described in any one of claims 1 to 6, and the first core network element is used to perform the method as described in any one of claims 7 to 13.

33. The system according to claim 32, characterized in that, The system further includes a first access network device, which is configured to perform the method as described in any one of claims 14 to 21, or the first access network device is configured to perform the method as described in any one of claims 22 to 29.

34. A chip, characterized in that, The system includes a communication interface for receiving data and / or information and transmitting the received data and / or information to a processor, which processes the data and / or information to perform the method as described in any one of claims 1 to 29.

35. A computer-readable storage medium, characterized in that, Used to store computer program code or instructions for implementing the method as described in any one of claims 1 to 29.

36. A computer program product, characterized in that, The computer program product includes computer program code or instructions, which, when executed by a data transmission device, cause the data transmission device to perform the method of any one of claims 1 to 29.

Images