Communication method and communication apparatus

Abstract

Provided in the present application are a communication method and a communication apparatus. The method is applied to an intermediate node in an ambient Internet of Things (A-IoT) system. The method comprises: sending first information, which is used for requesting authentication performed on an intermediate node to be used as an excitation source of an A-IoT system, wherein the excitation source is used for providing a carrier to a tag in the A-IoT system; and receiving second information, which is used for indicating an authentication result, wherein the authentication result is used for indicating whether the intermediate node is used as the excitation source of the A-IoT system, and the intermediate node is further used as a reader-writer in the A-IoT system to communicate with the tag. The present application provides an implementation process of authenticating an intermediate node to be used as an excitation source of a system, and can also perform carrier transmission in a multi-subcarrier mode, thereby improving the capability, in terms of the resistance against frequency-selective fading, of a carrier sent by the excitation source, and also improving the anti-interference capability of the carrier.

Description

Communication method and communication device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on April 3, 2024, with application number 202410417197.2 and invention name “Communication Method and Communication Device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and more specifically, to a communication method and a communication device. Background Art

[0003] With the development of communication technology, the 3rd Generation Partnership Project (3GPP) has defined the ambient internet of things (A-IoT) technology.

[0004] The A-IoT communication system in A-IoT technology includes readers and tags. Readers can be implemented by network devices, such as base stations, and tags can be implemented by IoT terminals, such as passive, semi-passive, or active tags. Tags have simple functions and rely on the carrier provided by the excitation source device to assist in communication. When the base station serves as the excitation source, the communication coverage between the tag and the base station is relatively limited, and the power consumption of the base station is relatively high. In addition, the carrier transmitted by the commonly used excitation source device only supports single-tone transmission, and the carrier has poor resistance to frequency selective fading.

[0005] Therefore, how to implement other devices as the excitation source of the system and improve the ability of the carrier sent by the excitation source to resist frequency selective fading is a technical problem that those skilled in the art urgently need to solve. Summary of the Invention

[0006] The present application provides a communication method and a communication device, provides an implementation process of using intermediate node authentication as a system excitation source, and can transmit carriers in a multi-subcarrier mode, thereby improving the ability of the carrier sent by the excitation source to resist frequency selective fading and enhancing the anti-interference ability of the carrier.

[0007] In a first aspect, a communication method is provided, which is applied to an intermediate node in an Ambient Internet of Things (A-IoT) system. The method includes sending first information requesting authentication of the intermediate node as an excitation source for the A-IoT system, where the excitation source provides carrier waves to tags in the A-IoT system. The method also includes receiving second information indicating an authentication result, which indicates whether the intermediate node serves as an excitation source for the A-IoT system. The intermediate node is also configured to communicate with tags as a reader / writer in the A-IoT system.

[0008] The implementation entity of the solution described in the first aspect can be an intermediate node, a module within the intermediate node (such as a chip system), or a logical node, logic module, or software that implements all or part of the intermediate node's functions, without limitation. For ease of description, the following description uses an intermediate node as an example.

[0009] In the above solution, the intermediate node requests to act as an excitation source in the A-IoT system, providing carrier waves for the tags. The intermediate node can also function as a reader / writer in the system, possessing read / write capabilities and supporting the reception of reflected signals from the tags. Before acting as an excitation source, the intermediate node must first pass capability authentication. This authentication process for intermediate nodes is made public and specific, standardizing the network access process for intermediate nodes.

[0010] In conjunction with the first aspect, in certain implementations of the first aspect, the authentication result is used to instruct the intermediate node to serve as an excitation source for the system. The method further includes receiving first configuration information indicating a configuration of a carrier transmitted by the intermediate node. The intermediate node transmits the carrier to the tag based on the first configuration information.

[0011] In the above solution, the intermediate node is authenticated as the excitation source of the system, and the intermediate node also receives the first configuration information, performs carrier configuration according to the first configuration information, and sends the corresponding configured carrier to the tag.

[0012] With reference to the first aspect, in certain implementations of the first aspect, the carrier configuration includes configuration information of the carrier in a single subcarrier mode and / or a multi-subcarrier mode. The carrier configuration information in the multi-subcarrier mode includes at least one of the following parameters: frequency domain position, number of subcarriers, carrier transmit power, guard interval, carrier transmit start time, carrier transmit end time, carrier transmit cycle, and carrier duration.

[0013] In the above solution, the first configuration information indicates the carrier configuration sent by the intermediate node. The first configuration information instructs the intermediate node to send multiple subcarriers and / or a single subcarrier. When the first configuration information instructs the intermediate node to send multiple subcarriers, the carrier configuration information in the multiple subcarrier mode also includes relevant parameters. Based on the corresponding parameters, the intermediate node can send subcarriers applicable to the current system. When sending multiple subcarriers, it can also improve the resistance to frequency selective fading of the channel, improve the reflected signal capability, and improve the anti-interference capability.

[0014] In conjunction with the first aspect, in certain implementations of the first aspect, the configuration of the carrier includes that the carrier transmitted in the multi-subcarrier mode is in a frequency hopping mode, and different single subcarriers are present in different time units in the frequency hopping mode.

[0015] In the above solution, the first configuration information instructs the intermediate node to transmit multiple subcarriers, and the multiple subcarriers are transmitted in a frequency hopping manner. In the frequency hopping mode, different single subcarriers are used in different time units, so that different subcarriers occupy different times. Different subcarriers are located in different time domains.

[0016] In conjunction with the first aspect, in certain implementations of the first aspect, the first information is further used to indicate capability information of the intermediate node. The capability information includes at least one of the following: the intermediate node's ability to support single subcarrier and / or multiple subcarriers, the intermediate node's ability to transmit carriers, and the intermediate node's ability to receive signals and / or reflected signals based on carriers.

[0017] In the above solution, the first information reported by the intermediate node also includes its own capability information, indicating its supported single and / or multi-subcarrier capabilities, its ability to transmit carrier signals, and its ability to receive and / or reflect carrier signals. This allows the network unit to authenticate the most appropriate stimulus source for the current system, tag, etc. based on appropriate conditions. By properly utilizing the intermediate node's capability information, system power consumption can be further reduced, the time it takes for tags to receive carrier signals, and the overall system response speed can be improved.

[0018] In conjunction with the first aspect, in certain implementations of the first aspect, the capability information of the intermediate node includes a capability of the intermediate node to support multiple subcarriers. The carrier sent by the intermediate node to the tag includes at least two subcarriers for uplink data transmission, and the number of subcarriers is allocated based on the demodulation capability of the intermediate node and remaining resources.

[0019] In the above scheme, the intermediate node's capability information includes its ability to support multiple subcarriers. Therefore, the network unit can configure the number of subcarriers in the configuration information it sends, and the intermediate node sends the corresponding carriers based on the configuration information. The carriers sent by the intermediate node to the tag include at least two subcarriers for uplink data transmission. The number of subcarriers is allocated by the network equipment based on the intermediate node's demodulation capabilities and remaining resources. This allows the intermediate node to send a reasonable number of subcarriers while ensuring normal operation, fully utilizing demodulation capabilities and remaining resources, further improving system operational efficiency and resource utilization.

[0020] It should be understood that the network equipment in the implementation of this application includes but is not limited to base stations, core network equipment, operations, administration, and maintenance (OAM) equipment, and this application does not make any special restrictions on this.

[0021] In combination with the first aspect, in some implementations of the first aspect, the authentication result is used to indicate that the intermediate node does not serve as an excitation source for the system.

[0022] In the above scheme, the authentication result for the intermediate node indicates that the intermediate node is not used as the system's excitation source. It should be understood that the number of intermediate nodes that initiate the excitation source authentication request in this application is not specifically limited and can be one or more. The failure of the intermediate node to authenticate does not affect the authentication process of other intermediate nodes.

[0023] In a second aspect, a communication method is provided, which is applied to an Ambient Internet of Things (A-IoT) system. The method includes receiving first information and, based on the first information, authenticating an intermediate node as an excitation source for the A-IoT system. The excitation source is used to provide a carrier wave to tags in the A-IoT system. The method also includes sending second information based on the first information, the second information indicating an authentication result. The authentication result indicates whether the intermediate node serves as an excitation source for the A-IoT system. The intermediate node is also used to communicate with tags as a reader / writer in the A-IoT system.

[0024] The implementation entity of the solution described in the second aspect can be a network device, a module within the network device (such as a chip system), or a logical node, logic module, or software that implements all or part of the network device's functions, without limitation. For ease of description, the following description uses a network device as an example.

[0025] It should be understood that the network equipment in the implementation of this application includes but is not limited to base stations, core network equipment, operations, administration, and maintenance (OAM) equipment, and this application does not make any special restrictions on this.

[0026] In conjunction with the second aspect, in certain implementations of the second aspect, the authentication result is used to instruct the intermediate node to serve as an excitation source for the system. The method further includes sending first configuration information, the first configuration information being used to instruct the configuration of the carrier sent by the intermediate node.

[0027] In conjunction with the second aspect, in certain implementations of the second aspect, the carrier configuration includes configuration information of the carrier in a single subcarrier mode and / or a multi-subcarrier mode. When the configuration information indicates transmitting a carrier in a multi-subcarrier mode, the carrier configuration information includes at least one of the following parameters: frequency domain position, number of subcarriers, carrier transmit power, guard interval time, carrier transmit start time, carrier transmit end time, carrier transmit cycle, and carrier duration.

[0028] In combination with the second aspect, in some implementations of the second aspect, the configuration of the carrier includes that the carrier transmitted in the multi-subcarrier mode is in a frequency hopping mode, and different single subcarriers are present in different time units in the frequency hopping mode.

[0029] In conjunction with the second aspect, in certain implementations of the second aspect, the first information is further used to indicate capability information of the intermediate node. The capability information includes at least one of the following: the intermediate node's ability to support single subcarrier and / or multiple subcarriers, the intermediate node's ability to transmit carriers, and the intermediate node's ability to receive signals and / or reflected signals based on carriers.

[0030] In conjunction with the second aspect, in certain implementations of the second aspect, the capability information of the intermediate node includes a capability of the intermediate node to support multiple subcarriers. The method further includes: indicating, based on the demodulation capability and remaining resources of the intermediate node, the number of subcarriers to be sent by the intermediate node for uplink data transmission. The number of subcarriers is included in the information indicating the carrier configuration.

[0031] In a specific implementation manner, the number of subcarriers is included in the first configuration information.

[0032] In combination with the second aspect, in certain implementations of the second aspect, the authentication result is used to indicate that the intermediate node does not serve as an excitation source for the system.

[0033] In conjunction with the second aspect, in certain implementations of the second aspect, the authentication result is used to indicate that the intermediate node serves as an excitation source for the system. The method further includes: the base station and / or the OAM sending first synchronization information to the first network element to inform the first network element that the A-IoT system uses the intermediate node as an excitation source.

[0034] In a specific implementation, the first network element includes a core network element. Specifically, it includes but is not limited to a tag management function (TMF) network element, an access and mobility management function (AMF) network element, an ambient IoT management function (AIoTMF), etc. It can also be other network elements, which are not specifically limited in this application.

[0035] It should be understood that the relevant schemes and technical effects in the implementation of the second aspect can refer to the technical effects in the implementation of the first aspect, and this application will not go into details here.

[0036] In a third aspect, a communication method is provided, which is applied to a network device in an Ambient Internet of Things (A-IoT) system. The system also includes an auxiliary terminal device and a tag, wherein the auxiliary terminal device is configured to transmit a carrier wave to enable communication between the tag and the network device. The method includes: transmitting second configuration information, the second configuration information being configured to instruct the auxiliary terminal device to transmit configuration information for a carrier wave supporting transmission in multi-subcarrier mode.

[0037] The implementation entity of the solution described in the third aspect can be a network device, a module within the network device (such as a chip system), or a logical node, logic module, or software that implements all or part of the network device's functions, without limitation. For ease of description, the following description uses a network device as an example.

[0038] It should be understood that the network equipment in the implementation of this application includes but is not limited to base stations, core network equipment, operations, administration, and maintenance (OAM) equipment, and this application does not make any special restrictions on this.

[0039] In the above solution, the network device sends second configuration information to the authenticated auxiliary terminal device, instructing the auxiliary terminal device to transmit a carrier in multi-subcarrier mode. Transmitting multiple subcarriers can also improve resistance to frequency-selective fading, enhance reflected signal capabilities, and enhance anti-interference capabilities.

[0040] In combination with the third aspect, in certain implementations of the third aspect, the configuration information of the carrier includes at least one of the following parameters: frequency domain position, the number of subcarriers, the transmission power of the carrier, the protection interval time, the transmission start time of the carrier, the transmission end time of the carrier, the transmission period of the carrier, and the duration of the carrier.

[0041] In conjunction with the third aspect, in certain implementations of the third aspect, the carrier configuration information further includes configuring the carrier transmitted in the multi-subcarrier mode to be in a frequency hopping mode. In the frequency hopping mode, different single subcarriers are present in different time units.

[0042] In conjunction with the third aspect, in certain implementations of the third aspect, the method further includes the network device indicating, based on the demodulation capability and remaining resources of the auxiliary terminal device, the number of subcarriers to be sent by the auxiliary terminal device for uplink data transmission. The number of subcarriers is included in the information indicating the configuration of the carrier.

[0043] In a specific implementation manner, the number of subcarriers is included in the second configuration information.

[0044] It should be understood that the relevant schemes and technical effects in the implementation of the third aspect can refer to the technical effects in the implementation of the first aspect, and this application will not go into details here.

[0045] In a fourth aspect, a communication method is provided, which is applied to an auxiliary terminal device in an Ambient Internet of Things (A-IoT) system. The system also includes a network device and a tag, wherein the auxiliary terminal device is configured to transmit a carrier wave to enable communication between the tag and the network device. The method includes receiving second configuration information, the second configuration information instructing the auxiliary terminal device to transmit configuration information for a carrier wave supporting transmission in multi-subcarrier mode. The auxiliary terminal device transmits the carrier wave to the tag based on the second configuration information.

[0046] The implementation entity of the solution described in the fourth aspect may be an auxiliary terminal device, a module within the auxiliary terminal device (such as a chip system), or a logical node, logic module, or software that implements all or part of the auxiliary terminal device's functions, without limitation. For ease of description, the following description uses an auxiliary terminal device as an example.

[0047] In combination with the fourth aspect, in certain implementations of the fourth aspect, the configuration information of the carrier includes at least one of the following parameters: frequency domain position, the number of subcarriers, the transmission power of the carrier, the protection interval time, the transmission start time of the carrier, the transmission end time of the carrier, the transmission period of the carrier, and the duration of the carrier.

[0048] In conjunction with the fourth aspect, in certain implementations of the fourth aspect, the carrier configuration information further includes configuring the carrier transmitted in the multi-subcarrier mode to be in a frequency hopping mode. In the frequency hopping mode, different single subcarriers are present in different time units.

[0049] In conjunction with the fourth aspect, in certain implementations of the fourth aspect, the carrier configuration information includes the number of subcarriers. The carrier transmitted by the auxiliary terminal device to the tag includes at least two subcarriers for uplink data transmission, and the number of subcarriers is allocated based on the demodulation capability of the auxiliary terminal device and the remaining resources.

[0050] It should be understood that in some specific implementations, the auxiliary terminal device only acts as an excitation source of the system to send carrier signals to the tags, does not support the reception of tag reflection signals, and does not have read and write functions.

[0051] In a fifth aspect, a communication system is provided, comprising one or more of a first device, a second device, and a third device, wherein the first device is used to implement the method provided by the first aspect and any possible implementation of the first aspect; the second device is used to implement the method provided by the second aspect and any possible implementation of the second aspect; and the third device is used to implement the method provided by the third aspect and any possible implementation of the third aspect.

[0052] In the sixth aspect, a communication system is provided, comprising a first device and a second device, wherein the first device is used to implement the method provided by the first aspect and any possible implementation of the first aspect; the second device is used to implement the method provided by the second aspect and any possible implementation of the second aspect.

[0053] In the seventh aspect, a communication system is provided, comprising a second device and a third device, wherein the second device is used to implement the method provided by the second aspect and any possible implementation of the second aspect; the third device is used to implement the method provided by the third aspect and any possible implementation of the third aspect.

[0054] In an eighth aspect, a communication device is provided, the device being configured to execute the method of any possible implementation of aspects 1 to 4. Specifically, the device may include units and / or modules, such as a processing unit and / or a communication unit, for executing the method of any possible implementation of aspects 1 to 4.

[0055] In one implementation, the apparatus is a communication device (e.g., an intermediate node, a network device, or an auxiliary terminal device). When the apparatus is a communication device, the communication unit may be a transceiver or an input / output interface; the processing unit may be at least one processor. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input / output interface may be an input / output circuit.

[0056] In another implementation, the apparatus is a chip, chip system, or circuit for a communication device (e.g., an intermediate node, a network device, or an auxiliary terminal device). When the apparatus is a chip, chip system, or circuit for a communication device, the communication unit may be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; and the processing unit may be at least one processor, processing circuit, or logic circuit.

[0057] In a ninth aspect, a communication device is provided, comprising: at least one processor configured to execute a computer program or instruction to perform the method of any possible implementation of aspects 1 to 4. Optionally, the device further comprises a memory configured to store the computer program or instruction. Optionally, the device further comprises a communication interface, through which the processor reads the computer program or instruction.

[0058] In one implementation, the apparatus is a communication device (such as an intermediate node, a network device, or an auxiliary terminal device).

[0059] In another implementation, the apparatus is a chip, a chip system, or a circuit used in a communication device (such as an intermediate node, a network device, or an auxiliary terminal device).

[0060] In a tenth aspect, a processor is provided for executing the methods provided in the first to fourth aspects above.

[0061] For the operations such as sending and acquiring / receiving involved in the processor, unless otherwise specified, or if they do not conflict with their actual functions or internal logic in the relevant descriptions, they can be understood as processor output, reception, input and other operations, and can also be understood as sending and receiving operations performed by the radio frequency circuit and antenna. This application does not limit this.

[0062] Optionally, the device further includes: a memory for storing programs; accordingly, at least one processor is used to execute computer programs or instructions in the memory.

[0063] Optionally, the device further includes a communication interface, which is coupled to the processor and can be used to input information to the processor or output information from the processor.

[0064] In an eleventh aspect, a computer-readable storage medium is provided, which stores a program code for execution by a device, wherein the program code includes a method for executing any possible implementation of the first to fourth aspects above.

[0065] In a twelfth aspect, a computer program product comprising instructions is provided, which, when run on a computer, enables the computer to execute the method in any possible implementation of the first to fourth aspects above.

[0066] In the thirteenth aspect, a chip is provided, which includes a processor and a communication interface. The processor reads instructions on the memory through the communication interface and executes the method provided by any of the above-mentioned implementation methods of any of the above-mentioned first to fourth aspects.

[0067] Optionally, as an implementation method, the chip also includes a memory, in which a computer program or instruction is stored, and the processor is used to execute the computer program or instruction on the memory. When the computer program or instruction is executed, the processor is used to execute the method provided in any one of the above implementation methods of any one of the first to fourth aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0068] FIG1 shows a schematic diagram of an excitation source sending a carrier wave for reflection communication provided by an embodiment of the present application.

[0069] FIG2 shows a schematic diagram of a communication system applicable to an embodiment of the present application.

[0070] FIG3 shows a schematic diagram of another communication system applicable to an embodiment of the present application.

[0071] Figure 4 shows a typical topology of an A-IoT system.

[0072] Figure 5 shows the excitation source architecture in a typical A-IoT topology.

[0073] FIG6 is a schematic diagram of a communication method provided in an embodiment of the present application.

[0074] FIG7 is a schematic diagram of a communication method provided in another embodiment of the present application.

[0075] FIG8 is a schematic diagram of a communication method provided in yet another embodiment of the present application.

[0076] FIG9 is a schematic diagram of another communication method provided in an embodiment of the present application.

[0077] FIG10 is a schematic diagram of a communication device provided in an embodiment of the present application.

[0078] FIG11 is a schematic diagram of a communication device provided in another embodiment of the present application. DETAILED DESCRIPTION

[0079] The technical solution in this application will be described below with reference to the accompanying drawings.

[0080] In order to facilitate understanding of the embodiments of the present application, the following points are first explained.

[0081] 1. In this application, unless otherwise specified, "a plurality of or at least two" means two or more.

[0082] 2. In each embodiment of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their internal logical relationships.

[0083] 3. The various numerical numbers involved in this application are only used for the convenience of description and are not used to limit the scope of protection of this application. The size of the serial numbers involved in this application does not mean the order of execution. The order of execution of each process should be determined by its function and internal logic. For example, the terms "first", "second", "third", "fourth" and other various terminology labels (if any) in the specification and claims and drawings of this application are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. Among them, the data used in this way can be interchangeable where appropriate, so that the embodiments described here can be implemented in an order other than what is illustrated or described here.

[0084] At the same time, any embodiment or design described in this application as "exemplary" or "for example" should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner to facilitate understanding.

[0085] 4. The terms "comprise" and "have" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or apparatus that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such process, method, product or apparatus.

[0086] 5. In this application, "used to indicate" can be understood as "enabling," and "enabling" can include direct enabling and indirect enabling. When describing that certain information is used to enable A, it can include that the information directly enables A or indirectly enables A, and does not necessarily mean that the information contains A.

[0087] The information enabled by the information is called information to be enabled. In the specific implementation process, there are many ways to enable the enabled information, such as but not limited to, directly enabling the information to be enabled, such as the information to be enabled itself or the index of the information to be enabled. The information to be enabled can also be indirectly enabled by enabling other information, wherein there is an association between the other information and the information to be enabled. It is also possible to enable only a part of the information to be enabled, while the other parts of the information to be enabled are known or agreed in advance. For example, it is also possible to enable specific information with the help of the arrangement order of each piece of information agreed in advance (such as specified in the protocol), thereby reducing the enabling overhead to a certain extent. At the same time, it is also possible to identify the common parts of each piece of information and enable them uniformly to reduce the enabling overhead caused by enabling the same information separately.

[0088] 6. In this application, "pre-configuration" may include pre-definition, such as protocol definition. "Pre-definition" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., including each network element). This application does not limit the specific implementation method.

[0089] 7. "Storage" or "saving" as used in this application may refer to storage in one or more memories. The one or more memories may be provided separately or integrated into an encoder or decoder, a processor, or a communication device. The one or more memories may also be provided in part separately and in part integrated into a decoder, processor, or communication device. The type of memory may be any form of storage medium and is not limited thereto.

[0090] 8. The “protocol” referred to in this application may refer to a standard protocol in the field of communications, for example, it may include the fourth generation (4G) network, the fifth generation (5G) network protocol, the new radio (NR) protocol, the 5.5G network protocol, and related protocols used in future communication systems. This application does not limit this.

[0091] 9. The arrows or boxes indicated by dotted lines in the schematic diagrams in the accompanying drawings of this application specification represent optional steps or optional modules.

[0092] 10. In this application, unless otherwise specified, “ / ” indicates that the objects associated with each other are in an “or” relationship. For example, A / B can represent A or B. “And / or” in this application is only a description of the association relationship between the associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. A and B can be singular or plural.

[0093] 11. In this application, indication includes direct indication (also called explicit indication) and implicit indication. Direct indication of information A means including information A. Implicit indication of information A means indicating information A through the correspondence between information A and information B and the direct indication of information B. The correspondence between information A and information B can be predefined, pre-stored, pre-burned, or pre-configured.

[0094] 12. In this application, the use of information C to determine information D includes both situations where information D is determined solely based on information C and situations where information D is determined based on information C and other information. Furthermore, information C can also be used to determine information D indirectly, for example, where information D is determined based on information E, and information E is determined based on information C.

[0095] 13. In this application, "device A sends information A to device B" can be understood as the destination end of the information A or the intermediate network element in the transmission path between the destination end and the device B, which may include sending information to device B directly or indirectly.

[0096] 14. In this application, the phrase "Device B receives information A from Device A" should be understood to mean that the source of information A or an intermediate network element in the transmission path between the source and the device A is Device A, and may include directly or indirectly receiving the information from Device A. Information may undergo necessary processing between the source and destination, such as formatting changes, but the destination can still understand the valid information from the source. Similar expressions in this application should be understood similarly and are not elaborated on here.

[0097] The technical solution provided in this application can be applied to various communication systems, such as: fifth-generation communication system (5G), new radio (NR) system, long-term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, wireless local area network (WLAN) system, satellite communication system and other communication systems, or future communication systems.

[0098] The technical solution 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) and Internet of Things (IoT) communication systems or other communication systems.

[0099] A device in the above-mentioned communication system can send signals to another device or receive signals from another device. The signals may include information, signaling, or data. The term "device" may also be replaced by an entity, network entity, network element, communication device, communication module, node, user equipment, mobile device, communication node, etc. The embodiments of this application are described using devices as an example. For example, the communication system may include at least one terminal device and at least one network device. The network device may send downlink signals to the terminal device, and / or the terminal device may send uplink signals to the network device.

[0100] In an embodiment of the present application, the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device.

[0101] The terminal device may be a device that provides voice / data, such as a handheld device or vehicle-mounted device with a wireless connection function. At present, some examples of terminals are: mobile phones, tablet computers, laptop computers, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, wearable devices, terminal devices in 5G networks or future evolved public land mobile communication networks (PLMNs). The terminal equipment in the network (PLMN), etc., is not limited to this in the embodiments of the present application.

[0102] In the embodiment of the present application, the terminal device may also be a wearable device. Wearable devices may also be called wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0103] In the embodiments of the present application, the device for realizing the function of the terminal device can be a terminal device, or a device capable of supporting the terminal device to realize the function, such as a chip system, which can be installed in the terminal device or used in combination with the terminal device. In the embodiments of the present application, the chip system can be composed of a chip, or it can include a chip and other discrete devices. In the embodiments of the present application, only the terminal device is used as an example for description, and the embodiments of the present application are not limited to the solutions of the embodiments of the present application.

[0104] The network device in the embodiments of the present application may be a device for communicating with a terminal device, and may also be referred to as an access network device or a radio access network device, such as a base station. The network device in the embodiments of the present application may refer to a radio access network (RAN) node (or device) that connects a terminal device to a wireless network. The base station can broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmission point (TRP), transmitting point (TP), master station, secondary station, multi-standard radio (motor slide retainer, MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), CU, DU, RU, positioning node, RAN intelligent controller (RIC), etc. RAN equipment, including CU and DU nodes, splits the protocol layers of the eNB in ​​the Long Term Evolution (LTE) system. Some protocol layer functions are centrally controlled by the CU, while some or all of the remaining protocol layer functions are distributed in the DU, which is centrally controlled by the CU. Access network equipment can also be reader / writer devices.

[0105] The base station can be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof. The base station can also refer to a communication module, a modem or a chip used to be set in the aforementioned equipment or device. The base station can also be a mobile switching center and a device that performs the base station function in D2D, V2X, and M2M communications, a network side device in a future communication network, a device that performs the base station function in a future communication system, etc. The base station can support networks with the same or different access technologies. Optionally, the RAN node can also be a server, a wearable device, a vehicle or an on-board device, etc. For example, the access network device in the V2X technology can be a road side unit (RSU). The embodiments of the present application do not limit the specific technology and specific device form adopted by the network equipment.

[0106] 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 based on the location of the mobile base station. In other examples, a helicopter or drone can be configured to act as a device that communicates with another base station.

[0107] Core network equipment is a general term for various functional entities on the network side used to manage users, data transmission and base station configuration, including access and mobility management function (AMF) network elements, user plane function (UPF) network elements, session management function (SMF) network elements, tag management function (TMF) network elements, etc.

[0108] In some deployments, the network device may include a CU or a DU, or both a CU and a DU, or a control plane CU node (central unit-control plane (CU-CP)), a user plane CU node (central unit-user plane (CU-UP)), and a DU node. For example, the network device may include a gNB-CU-CP, a gNB-CU-UP, and a gNB-DU.

[0109] In different communication systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, in an open radio access network (ORAN) system, CU may also be referred to as an open CU (open CU, O-CU), DU may also be referred to as an open DU (open DU, O-DU), CU-CP may also be referred to as O-CU-CP, CU-UP may also be referred to as O-CU-UP, and RU may also be referred to as O-RU. Any of the CU (or CU-CP, CU-UP), DU and RU in this application may be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0110] In some deployments, multiple RAN nodes collaborate to assist terminals in achieving wireless access, with different RAN nodes implementing portions of the base station's functionality. For example, a RAN node can be a CU, DU, CU-CP, CU-UP, or RU. The CU and DU can be separate or included in the same network element, such as the BBU. The RU can be included in a radio frequency device or radio unit, such as the RRU, AAU, or RRH.

[0111] The RAN node may support one or more types of fronthaul interfaces, with different fronthaul interfaces corresponding to DUs and RUs with different functions. If the fronthaul interface between the DU and the 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 the RU is another type of interface, relative to the CPRI, some of the downlink and / or uplink baseband functions, such as precoding, digital beamforming (BF), or one or more of inverse fast Fourier transform (IFFT) / cyclic prefix (CP) for downlink, are moved from the DU to the RU for implementation; and for uplink, one or more of digital beamforming (BF), or fast Fourier transform (FFT) / cyclic prefix (CP) removal, are moved from the DU to the RU for implementation.

[0112] In the embodiments of the present application, the device for implementing the functions of the network device can be a network device; it can also be a device that can support the network device to implement the functions, such as a chip system, a hardware circuit, a software module, or a hardware circuit and a software module. The device can be installed in the network device or used in conjunction with the network device. In the embodiments of the present application, only the device for implementing the functions of the network device is used as an example to illustrate, and does not constitute a limitation on the solutions of the embodiments of the present application.

[0113] The network device and / or terminal device can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on the water surface; it can also be deployed on aircraft, balloons and satellites in the air. The embodiments of this application do not limit the scenarios in which the network device and the terminal device are located. In addition, the terminal device and the network device can be hardware devices, or they can be software functions running on dedicated hardware, software functions running on general-purpose hardware, such as virtualization functions instantiated on a platform (e.g., a cloud platform), or entities including dedicated or general-purpose hardware devices and software functions. This application does not limit the specific forms of the terminal device and the network device.

[0114] When the present application is applied to an A-IoT or IoT system, both the reader and the tag device can be implemented based on the infrastructure in the cellular network. In other words, both the reader and the tag can be devices in the cellular network. For example, the function of the reader can be implemented by an access network device, such as a base station. The tag can be implemented by a terminal device in the cellular network, such as an extremely low-power, extremely low-complexity IoT terminal. Contactless data communication can be performed between the access network device and the terminal device, thereby reading information from the terminal device and / or writing information to be stored into the terminal device. It can be understood that in the present application, the access network device can have the function of a reader; the terminal device has the function of a tag, or the terminal device can be a terminal device in an A-IoT or IoT system.

[0115] With the advancement of communications technology, the Third Generation Partnership Project (3GPP) has defined the ambient internet of things (A-IoT) technology. A-IoT is based on cellular network communications infrastructure and consists of readers (such as base stations) and passive, semi-passive, or active tags (tags are terminals in cellular networks and can be understood as extremely low-power, low-complexity IoT terminals). Its main services include inventory, positioning, sensing, and command. Typical application scenarios include logistics, warehousing, industrial manufacturing, identity recognition, and environmental monitoring.

[0116] The A-IoT in A-IoT technology includes network devices and first-class terminal devices, or in other words, the communication system based on A-IoT includes network devices and first-class terminal devices. Among them, the first-class terminal device can be a device with the function of a tag device. In this case, both the reader and the tag device can be implemented based on the infrastructure in the cellular network. In other words, both the reader and the tag device can be devices in the cellular network. For example, the function of the reader and the tag device can be implemented by a network device, such as a base station. The tag device can be implemented by a terminal in the cellular network, such as an extremely low-power, extremely low-complexity Internet of Things terminal, that is, a first-class terminal. Contactless data communication can be carried out between the network device and the first-class terminal, thereby reading information from the first-class terminal and / or writing information to be stored into the first-class terminal.

[0117] The following is a further description of the main services of A-IoT.

[0118] Specifically, the inventory service uses a reader (which can be a base station or terminal) to access tags (A-IoT devices) within the coverage area. Devices that successfully access the service need to send their unique identifiers to the reader. The inventory service, also known as an inventory operation, can obtain the tag's identification information. For example, the reader can use commands such as query and acknowledgement (ACK) to obtain the tag's identification information. To facilitate tag inventory, tags include four session identifiers, each of which corresponds to two inventory states: A and B. The inventory state is indicated by the inventory flag (sessInventoried flag). When the reader selects a tag, the select command sent to it will carry a session identifier, and the tag will store the session identifier. When the reader performs an inventory service on the tag, the query command sent to it will include the session identifier. At this time, the tag can flip the inventory state corresponding to the session identifier from A to B. If the reader sends a query command again to perform inventory operations, the tag will not respond to the reader because the inventory status in the tag is B, thus preventing the same tag from being inventoried multiple times in the same inventory cycle.

[0119] Specifically, the positioning service uses some positioning signals to locate the position of the tag.

[0120] Specifically, the sensing service is that the tag reports sensing data to the base station, such as temperature data.

[0121] Specifically, the command service may be some operation instructions. It is understandable that the command service may include at least one of a read service, a write service or a lock service. The read service may read the electronic product code (EPC) in the tag's storage area, the tag identifier (TID), the content stored in the tag's reserved area or the content stored in the user's storage area, etc. The write service may perform a write operation on the tag's storage area, that is, the base station (BS) sends a downlink instruction and data to instruct the tag to write the data into its own storage area. The kill service may make the tag unable to work forever. The lock service may lock the tag's information, preventing the tag from being read or written. Alternatively, the lock service may also lock the storage area, preventing or allowing the tag from being read or written.

[0122] It should be understood that the above business process is only a specific business implementation method. Other businesses or operations can also be performed between the tag and the reader, which will not be described in detail here.

[0123] A-IoT, defined by the 3GPP plenary meeting, is an extremely low-power, low-complexity IoT technology. It can be considered a 3GPP extension of passive radio frequency identification (RFID). While it shares some principles with RFID, such as similar inventory management processes, 3GPP introduces more valuable scenarios.

[0124] Tags, electronic tags, and RFID tags are the common name for RFID. RFID stands for Radio Frequency Identification. RFID technology can be categorized into three types: active, passive, and semi-active. Passive tags are also called passive IoT devices, and can therefore be considered a terminal.

[0125] The original definition of a reader / writer includes handheld or fixed devices that read (and sometimes write) tag information. It can also be understood as a device that communicates with tags. It can be a terminal, a base station, a signal-transmitting node such as a headend, a Pico Radio Unit (PRU), a transmission reception point (TRP), or a device with read / write capabilities. It can also be an integrated access and backhaul (IAB) node, a smart repeater, or a relay node.

[0126] In the A-IoT system, a tag can also be called an electronic tag, RFID tag, or tag device. Alternatively, a tag can also be called an A-IoT terminal device or A-IoT device. In this application, a tag can also be regarded as a terminal device.

[0127] In one classification method, tags can be divided into passive tags, semi-passive tags, and active tags. Passive tags and semi-passive tags can use a backscatter-based communication method, while active tags use an actively generated carrier communication method.

[0128] Another classification method can divide tags into the following three types of devices: Device A: has no energy storage, cannot generate signals independently, and uses backscattering to transmit signals; Device B: has energy storage, but cannot generate signals independently. It uses backscattering to transmit signals, and its stored energy can amplify the reflected signal; Device C: has energy storage, can generate signals independently, and has active RF elements for transmission.

[0129] The tag uses a low-precision, low-power medium-to-low-frequency ring oscillator or no local oscillator at all to receive downlink signals. When the tag is operating, the communication energy and carrier are provided by the reader, and communication is based on the reflected carrier.

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

[0131] FIG1 shows a schematic diagram of an excitation source sending a carrier wave for reflection communication provided by an embodiment of the present application.

[0132] For the above-mentioned devices A and B, they cannot generate signals independently and use backscattering to transmit signals. The tag shown in Figure 1 is a specific implementation of the above-mentioned devices A and B. The tag is wirelessly powered by the base station. The tag receives the downlink communication signal from the base station, but the tag cannot independently send uplink signals to the base station. The auxiliary node sends an excitation carrier CW, and the tag performs reflection communication based on the carrier and performs uplink communication with the base station. The base station sends (transmit, TX) downlink signals to the tag, and the base station receives (receive, RX) uplink signals from the tag.

[0133] In a specific implementation, the base station receives an uplink signal from the tag via frequency division duplex uplink (FDD UL) and sends a downlink signal to the tag via frequency division duplex downlink (FDD DL).

[0134] In a specific implementation, the device that transmits the carrier wave may be a terminal, a network device, or the like.

[0135] It should be understood that the device that sends the carrier is generally called an excitation source (helper). The excitation source can be a terminal, or a base station or a small station. There is only downlink data transmission between the device and the tag, and uplink and downlink data transmission between the device and the reader / writer, which may be through the air interface or through a wired connection. This application does not make any special restrictions on this.

[0136] It should be understood that the reader / writer involved in this embodiment can be a handheld or fixed device that reads or writes tag information, or can be understood as a device that communicates with tags. The reader / writer can be a terminal device, an access network device, or a device with reading and writing functions. The reader / writer can also be an IAB node or a relay node.

[0137] As shown in Figure 1, the reader / writer acts as an auxiliary node to transmit a carrier signal to the tag, which then receives it via its antenna. The tag can then adjust the information it needs to transmit based on the reflected signal. This approach allows the tag to receive downlink signals using a low-precision, low-power, medium- to low-frequency ring oscillator, or even a completely local oscillator-free approach. This further reduces the tag's downlink power consumption.

[0138] A tag is a miniature wireless transceiver, which mainly includes a built-in tag device antenna, a coupling element and a chip. The tag chip has a storage space that can support the reader to read or write tag data. After the tag receives the radio frequency signal sent by the reader through the antenna, it can couple the radio frequency signal through the coupling element, and then provide energy to the tag chip within the coupling channel, and feed back the data stored in the chip to the reader through the antenna. A communication network based on cellular network infrastructure, consisting of readers and tags, can be called a passive Internet of Things (IoT) network, or an ambient Internet of Things (AIoT or A-IoT), in which the tag device can also be regarded as a terminal device, which can be an active tag device, a passive tag device or a semi-active tag device.

[0139] Environmental IoT systems can be applied to passive or semi-passive IoT scenarios. For example, in logistics and warehousing scenarios, tags can be used to inventory and track goods, and to monitor the status of goods during transportation. In industrial manufacturing scenarios, tags can be used to monitor the environment and equipment status.

[0140] FIG2 shows a schematic diagram of a communication system applicable to an embodiment of the present application.

[0141] First, we briefly describe the common network elements in the O-RAN system.

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

[0143] O-RAN central unit control plane (O-CU-CP): Similar to the CU-CP in the new radio (NR) system, it implements the functions of the RRC layer and the control plane functions of the PDCP layer. It is part of the O-CU.

[0144] O-RAN central unit user plane (O-CU-UP): Similar to the CU-UP in the NR system, it implements the SDAP layer and the user plane functions of the PDCP layer. It is part of the O-CU.

[0145] O-RAN distributed unit (O-DU): Based on low-layer functionality, it implements the radio link control (RLC), medium access control (MAC), and higher physical layer (Higher PHY) layers specified in the 3GPP standard. Higher physical layer functions include one or more of the following: feedforward error correction (FEC) encoding / decoding, scrambling / descrambling, or modulation / demodulation.

[0146] O-RAN radio unit (O-RU): Based on low-layer functional division, it is used to implement the lower physical layer (Lower PHY) functions and radio frequency functions in the 3GPP standard. Among them, the lower physical layer functions include one or more of the following: fast Fourier transform (FFT) transform / inverse fast Fourier transform (iFFT transform), digital beamforming, or physical random access channel (PRACH) extraction and filtering. It is similar to the transmission reception point (TRP) or remote radio head (RRH) in 3GPP, but includes low physical layer functions such as FFT / iFFT or PRACH extraction.

[0147] O-RAN cloud (O-Cloud): A cloud computing platform that includes physical infrastructure nodes for hosting O-RAN functions such as RIC and O-DU; supporting software components (such as operating systems, virtual machine monitoring, and container runtimes), management, and orchestration capabilities.

[0148] As shown in FIG2 , 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.

[0149] The above-mentioned network elements (also referred to as nodes) can be connected to each other. For example, the first network unit is connected to the O-cloud through the O2 interface, the first network unit is connected to the third network unit, O-eNB, O-CU-CP, O-CU-UP, O-DU and O-RU through the O1 interface, the first network unit is connected to the O-RU through the open fronthaul M-Plane interface, the O-DU is connected to the O-RU through the open fronthaul M-Plane interface and the open fronthaul C / U / S-Plane interface, the third network unit is connected to the O-eNB, O-CU-CP, O-CU-UP and O-DU through the E2 interface, the O-CU-CP is connected to the O-DU through the F1-c interface, the O-CU-UP is connected to the O-DU through the F1-u interface, and the O-CU-CP is connected to the O-CU-UP through the E1 interface. For the specific description of the interface shown in Figure 2, please refer to the existing standards and will not be repeated here.

[0150] As a possible example, the first network unit may be a service management and orchestration framework (SMO), and the function of the SMO network element is similar to that of a network management, or it may be a network unit with similar functions to that of the SMO, which is not limited to this.

[0151] As a possible example, the second network unit may be a non-real time RIC (Non-RT RIC), which is used to implement non-real-time intelligent management of RAN functions, capable of implementing artificial intelligence (AI) / machine learning (ML) workflows including model training and model updates, and guiding applications / functions in Near-RT RIC based on policies. The Non-RT RIC is located in the SMO module. The second network unit may also be a network unit with functions similar to those of the Non-RT RIC, which is not limited.

[0152] In one possible example, the third network element may be a near-real time RIC (Near-RT RIC), which is used to implement near-real-time intelligent management of the RAN. By collecting data and performing related operations on the E2 interface, near-real-time control and optimization of O-RAN modules and resources are achieved. The third network element may also be a network element with similar functionality to the Near-RT RIC, without limitation.

[0153] FIG3 shows a schematic diagram of another communication system applicable to an embodiment of the present application.

[0154] As shown in Figure 3, the access network equipment (RAN, which can be, for example, an eNB or gNB or access network equipment of a future communication system) communicates with the core network (CN) through a backhaul link and communicates with the user equipment (UE) through an air interface.

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

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

[0157] Below, a brief description is given of the interfaces involved in the O-RAN architecture shown in Figures 2 and 3, as well as the 3GPP interface.

[0158] A1 interface: The interface between the Non-RT RIC and the Near-RT RIC is used for intelligent and dynamic control of O-RAN internal radio resources. The Non-RT RIC provides policies, enriched information, and machine learning (ML) model updates to the Near-RT RIC via the A1 interface, while the Near-RT RIC provides policy feedback to the Non-RT RIC via the A1 interface.

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

[0160] O1 interface: The interface between the management entity in the SMO and the O-RAN module, used for operation management. This interface implements fault management, configuration management, account management, performance management, security management, software management, and file management.

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

[0162] Open Fronthaul CUS-Plane interfaces: These include 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. For example, the O-DU transmits beamforming weights to the O-RU and performs power control on the O-RU. The user plane transmits communication data between the DU and RU, between access network equipment and terminals. The synchronization plane is used by the O-DU to provide clock synchronization for the O-RU.

[0163] NG interface: The interface between NR RAN equipment (such as base station, CU, CU-CP or CU-UP) and the NR core network; among them, NG-u is the user plane NG interface and NG-c is the control plane NG interface.

[0164] Xn interface: The interface between NR RAN devices (such as base station, CU, CU-CP or CU-UP); among them, Xn-u is the user plane Xn interface and Xn-c is the control plane Xn interface.

[0165] 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 primarily used in E-UTRA-NR dual connectivity (EN-DC) scenarios, where the master station is an LTE RAN device connected to the LTE core network via the X2 interface.

[0166] E1 interface: the interface between CU-CP and CU-UP.

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

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

[0169] 3GPP RAN TR 38.848 specifies four typical topologies of A-IoT, as shown in Figure 4.

[0170] Figure 4 shows a typical topology of an A-IoT system.

[0171] Topology 1: includes base station BS and A-IoT devices.

[0172] In the structure of topology 1, A-IoT devices communicate directly with the base station in a two-way manner to exchange A-IoT data and / or signaling.

[0173] In a specific implementation, the communication between the base station and the A-IoT device is a uu interface, that is, air interface communication.

[0174] In this topology, the AIoT radio access network (RAN) and the AIoT core network (CN) communicate via the XX interface. The XX interface is a next-generation (NG) interface, and XXAP is the control plane protocol for the XX interface (NG interface). One possible implementation of XXAP is to include ambient IoT function (AIoTF) information / cells in the NGAP. Another possible implementation is to implement it by carrying a newly defined protocol layer on top of the NGAP protocol.

[0175] For example, in various embodiments of the present application, the interface between the access network device and the core network device can be an NG interface. The AIoT device communicates with the AIoT radio protocol layer of the AIoT RAN through the AIoT radio protocol layers. The XXAP layer of the AIoT RAN communicates with the XXAP layer of the AIoT CN, the stream control transmission protocol (SCTP) layer of the AIoT RAN communicates with the SCTP layer of the AIoT CN, the Internet protocol (IP) layer of the AIoT RAN communicates with the IP layer of the AIoT CN, the layer (layer 2, L2) of the AIoT RAN communicates with the L2 of the AIoT CN, and the L1 of the AIoT RAN communicates with the L1 of the AIoT CN.

[0176] In topology 1, there are two types of connections between AIoT RAN and AIoTF: direct connection and indirect connection (indirect path via AMF).

[0177] Optionally, for topology 1, whether in direct or indirect connection situations, "AIoT RAN" can be replaced by "access network equipment", for example, by "gNB".

[0178] Topology 2: includes base station BS, intermediate node (i-node) and A-IoT devices.

[0179] In the structure of topology 2, there is an intermediate node between the A-IoT device and the base station. The A-IoT device communicates with the intermediate node in a two-way manner, and the intermediate node and the base station communicate in a two-way manner.

[0180] 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 A-IoT data and / or signaling between the BS and the A-IoT device.

[0181] In a specific implementation, the communication between the intermediate node and the base station is a uu interface, that is, air interface communication.

[0182] In this topology, the XX interface between the AIoT-enabled gNB and the A-IoT CN is the NG interface, and the AIoT-enabled UE and the AIoT device communicate through the AIoT interface (e.g., AIoT radio).

[0183] The AIoT-enabled gNB includes the AIoT RAN node function, and the AIoT-enabled UE includes the common reader function. The common reader function refers to the function of communicating with A-IoT devices through the AIoT interface (such as the A-IoT radio); the AIoT RAN node function includes the function of controlling AIoT radio resources.

[0184] Topology 2 supports three modes: radio resource control (RRC) based solution, non-access stratum (NAS) based solution, and user plane based solution.

[0185] solution1:RRC based solution.

[0186] The basic idea is that after an access network device (such as a base station) receives an AIoT service-related request from an AIoT CN via XXAP, the base station further sends the relevant information to the A-IoT-enabled UE via the A-IoT-enabled UE's RRC message. When the base station receives AIoT service-related data or signaling from an A-IoT-enabled UE via RRC, it transmits the relevant information to the AIoT CN via XXAP / NGAP.

[0187] For an RRC-based solution, a possible protocol stack may include protocol stacks between the AIoT device, the AIoT RAN, and the AIoT CN. The AIoT device communicates with the AIoT radio protocol layer of the AIoT RAN through the AIoT radio protocol layers. The RRC layer of the AIoT-enabled UE communicates with the RRC layer of the AIoT-enabled gNB, the PDCP layer of the AIoT-enabled UE communicates with the PDCP layer of the AIoT-enabled gNB, the radio link control (RLC) layer of the AIoT-enabled UE communicates with the RLC layer of the AIoT-enabled gNB, the media access control (MAC) layer of the AIoT-enabled UE communicates with the MAC layer of the AIoT-enabled gNB, and the physical (PHY) layer of the AIoT-enabled UE communicates with the physical layer of the AIoT-enabled gNB. The XXAP layer of the AIoT-enabled gNB communicates with the XXAP layer of the AIoT CN, the SCTP layer of the AIoT-enabled gNB communicates with the SCTP layer of the AIoT CN, the IP layer of the AIoT-enabled gNB communicates with the IP layer of the AIoT CN, the layer (layer 2, L2) of the AIoT-enabled gNB communicates with the L2 of the AIoT CN, and the L1 of the AIoT-enabled gNB communicates with the L1 of the AIoT CN.

[0188] Among them, the XX interface is the NG-C interface (i.e., the NG control plane interface). One possible implementation of "XXAP" is to include AIoTF information / element in NGAP. Another possible implementation is to carry a newly defined protocol layer on the NGAP protocol.

[0189] For the RRC-based solution, there are two scenarios: direct connection and indirect connection (indirect path via AMF) between the AIoT-enabled gNB and AIoTF:

[0190] (1) Direct connection between AIoT-enabled gNB and AIoTF.

[0191] (2) The AIoT-enabled gNB and AIoTF are not directly connected (indirect path via AMF), that is, the AIoT data / signaling transmitted between AIoTF and AIoT-enabled gNB is carried on NGAP.

[0192] solution 2: NAS based solution.

[0193] The basic idea is that access network devices (such as base stations) cannot see AIoT-related processes. AIoT-related data / signaling is transmitted between the AIoT CN and the AIoT-enabled UE through the DL / UL NAS packets of the AIoT-enabled UE (transparently transmitted to the AIoT-enabled gNB). The base station can use the DL NAS Transport process and the UL NAS Transport process to process the DL / UL NAS packets of the AIoT-enabled UE on the NGAP.

[0194] solution 3: UP based solution.

[0195] The basic idea is that access network equipment (such as base stations) cannot see AIoT-related processes. AIoT service-related data / signaling between the AIoT CN and the IoT-enabled UE is carried on the PDU Session of the AIoT-enabled UE (transparently transmitted to the AIoT-enabled gNB), and the gNB processes the user plane data of the AIoT-enabled UE through the NG-U GTP-U channel.

[0196] It should be noted that "AIoT-enabled UE" can also be replaced by "UE reader", "intermediate UE" or "intermediate node", etc.

[0197] Topology 3: includes base station BS, assisting node and A-IoT devices.

[0198] Topology 3 is divided into two cases: downlink assistance and uplink assistance.

[0199] In downlink assistance, downlink communication is performed between the base station and the auxiliary node. The auxiliary node receives data and / or signaling from the base station, the A-IoT device receives data and / or signaling from the auxiliary node, and the base station receives data and / or signaling from the A-IoT device.

[0200] In uplink assistance, uplink communication is performed between the base station and the auxiliary node. The base station receives data and / or signaling from the auxiliary node, the auxiliary node receives data and / or signaling from the A-IoT device, and the A-IoT device receives data and / or signaling from the base station.

[0201] In a specific implementation, the communication between the intermediate node and the base station is a uu interface, that is, air interface communication.

[0202] Topology 4: includes terminal UE and A-IoT devices.

[0203] In the structure of topology 4, the A-IoT device directly communicates bidirectionally with the UE device to exchange A-IoT data and / or signaling.

[0204] In a specific implementation, the UE device and the A-IoT device communicate via a sidelink.

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

[0206] Figure 5 shows the excitation source architecture in a typical A-IoT topology.

[0207] Based on the topology shown in Figure 4, the UE can also be located within the coverage provided by the reader. When the reader is a terminal, the communication between it and the UE can be regarded as transmission between terminals. When the reader is a base station, the communication between it and the UE is the Uu interface, that is, air interface communication.

[0208] Based on the direct connection architecture of topology 1, the terminal device is added as the excitation source to provide a carrier for the A-IoT device. The communication between the base station and the terminal device is the uu interface.

[0209] Based on the split architecture of topology 2, terminal devices are added as excitation sources. Terminal devices only provide carriers for A-IoT devices, and base stations perform peering.

[0210] Based on the split architecture of topology 3, the UE-assisted downlink architecture uses a carrier provided by the UE or base station. Downlink data for A-IoT devices comes from the UE, and uplink data for A-IoT devices is sent to the base station. Communication between the base station and the terminal device is through the uu interface.

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

[0212] It should be understood that topology 3 shows a split architecture in which the uplink and downlink data links of the A-IoT device are decoupled.

[0213] In some optional implementations, the base station may be an access network device RAN, such as an eNB or gNB or an access network device of a future communication system.

[0214] In some optional implementations, the terminal device and the A-IoT device share a station, that is, the terminal device and the service base station of the A-IoT device establish a Uu interface connection.

[0215] In some other optional implementations, the terminal device and the A-IoT device are at different stations, that is, the terminal device establishes a Uu interface connection with a service base station that is not an A-IoT device.

[0216] Based on the direct connection architecture of topology 4, terminal device 2 is added as an excitation source to provide a carrier for the A-IoT device.

[0217] In the A-IoT system topology 2 shown in Figure 4, when an intermediate node communicates with an A-IoT device, it may need to act as an excitation source and provide a CW to the A-IoT device to facilitate communication. The system authenticates the intermediate node's excitation capability and only those nodes that pass the authentication are authorized to send CWs.

[0218] In summary, the present application provides a communication method for authenticating whether an intermediate node can serve as an excitation source for an A-IoT system and configuring the carrier sent by the intermediate node.

[0219] FIG6 is a schematic diagram of a communication method provided in an embodiment of the present application.

[0220] FIG6 provides a communication method 700 , in which, in a topology of an A-IoT system, a network device instructs an excitation source to transmit a carrier wave propagating in a multi-tone mode.

[0221] In a specific implementation, under a topology of an A-IoT system, an intermediate node requests to be used as an excitation source and is authenticated by a network device, which specifically includes the following steps.

[0222] S701: The intermediate node sends first information to a network device.

[0223] The first information is used to request authentication of the intermediate node as an excitation source of the A-IoT system, where the excitation source is used to provide a carrier to a tag in the A-IoT system.

[0224] Among them, the intermediate node is also used to communicate between the reader and the tag in the A-IoT system.

[0225] In an optional implementation, the first information is further used to indicate capability information of the intermediate node, wherein the capability information includes at least one of the following: the intermediate node's ability to support single subcarrier and / or multiple subcarriers, the intermediate node's ability to transmit carriers, and the intermediate node's ability to receive signals and / or reflected signals based on carriers.

[0226] S702: The network device authenticates the intermediate node as an incentive source based on the second information.

[0227] In an optional implementation, the network device includes a base station, and after receiving the first information, the base station authenticates the excitation source of the intermediate node.

[0228] In another optional implementation, the network device includes an OAM network element, and the OAM network element authenticates the stimulus source of the intermediate node after receiving the first information.

[0229] In another optional implementation, the network device includes a core network element, and the core network element authenticates the excitation source of the intermediate node after receiving the first information.

[0230] S703: The intermediate node receives the second information.

[0231] The second information is used to indicate an authentication result, and the authentication result is used to indicate whether the intermediate node serves as an excitation source of the A-IoT system.

[0232] In a specific implementation, the authentication result is used to indicate that the intermediate node is not used as the system's excitation source. If the authentication result indicates that the intermediate node failed authentication, the authentication node is not used as the system's excitation source. The request process for the intermediate node ends.

[0233] In another specific implementation, the authentication result is used to indicate that the intermediate node serves as the excitation source of the system. Then the method 700 further includes the following steps:

[0234] S704: The intermediate node receives first configuration information.

[0235] The first configuration information is used to indicate the configuration of the carrier sent by the intermediate node.

[0236] In an optional implementation, the carrier configuration includes configuration information of the carrier in a single subcarrier mode and / or a multi-subcarrier mode. The configuration information of the carrier in the multi-subcarrier mode includes at least one of the following parameters: frequency domain position, number of subcarriers, carrier transmit power, guard interval time, carrier transmit start time, carrier transmit end time, carrier transmit cycle, and carrier duration.

[0237] In one optional implementation, the carrier configuration includes transmitting the carrier in a multi-subcarrier mode in a frequency hopping manner. In the frequency hopping manner, different single subcarriers are present in different time units. In the frequency hopping manner, the carrier transmitted to the tag includes at least two subcarriers, and the tag occupies the at least two subcarriers for different periods of time.

[0238] S705: The intermediate node sends carrier 1.

[0239] The intermediate node sends carrier 1 to the tag according to the first configuration information.

[0240] In one optional implementation, the intermediate node's capability information includes its ability to support multiple subcarriers, and Carrier 1 sent by the intermediate node to the tag includes at least two subcarriers for uplink data transmission. The number of subcarriers is allocated and scheduled by the network device based on the intermediate node's demodulation capability and remaining resources.

[0241] Among them, network equipment includes but is not limited to base stations, core network elements, OAM network elements, etc.

[0242] In another specific implementation, in a topology of the A-IoT system, the auxiliary device acts as an excitation source to send a carrier to enable communication between the tag and the network device, and the network device instructs the auxiliary device to send a carrier that supports propagation in a multi-tone mode, which specifically includes the following steps.

[0243] S706: The auxiliary device receives the second configuration information.

[0244] The second configuration information is used to instruct the auxiliary terminal device to send configuration information of a carrier supporting transmission in a multi-subcarrier mode.

[0245] In an optional implementation, the configuration information of the carrier includes at least one of the following parameters: frequency domain position, number of subcarriers, carrier transmission power, protection interval time, carrier transmission start time, carrier transmission end time, carrier transmission period, and carrier duration.

[0246] In another optional implementation, the carrier configuration information further includes configuring the carrier transmitted in multi-tone mode to operate in a frequency hopping mode. In the frequency hopping mode, different single subcarriers are present in different time units. In the frequency hopping mode, the carrier transmitted to the tag includes at least two subcarriers, and the tag occupies the at least two subcarriers for different periods of time.

[0247] S707: The auxiliary device sends carrier 2.

[0248] The auxiliary device sends carrier 2 to the tag according to the second configuration information.

[0249] In one optional implementation, the auxiliary device's capability information includes the intermediate node's ability to support multiple subcarriers, and the carrier 2 sent by the auxiliary device to the tag includes at least two subcarriers for uplink data transmission. The number of subcarriers is allocated and scheduled by the network device based on the auxiliary device's demodulation capability and remaining resources.

[0250] Among them, network equipment includes but is not limited to base stations, core network elements, OAM network elements, etc.

[0251] It should be understood that in some implementations, the single-subcarrier (single tone) mode is also referred to as the single-tone mode. This is merely a difference in name and does not limit the scope of protection of this application. The carrier waveform (CW waveform) of a single subcarrier includes a sinusoidal carrier wave, etc. This application does not specifically limit the carrier waveform of a single subcarrier.

[0252] It should be understood that in some implementations, the multi-subcarrier (multi tone) mode is also referred to as the multi-tone mode. This is merely a difference in name and does not limit the scope of protection of this application. The multi-subcarrier carrier waveform (CW waveform) includes an orthogonal frequency division multiplexing (OFDM) signal mapped on continuous subcarriers; it also includes multiple single subcarriers, such as n discontinuous subcarriers in the frequency domain. This application does not specifically limit the multi-subcarrier waveform.

[0253] When the carrier signal sent by the intermediate node and / or the auxiliary device is multi-subcarrier, multi-subcarrier (multi-tone) is more helpful in combating frequency selective fading than single-tone.

[0254] It should be noted that the main difference between auxiliary nodes and intermediate nodes in this application is that intermediate nodes can act as readers and writers, or are said to have read and write functions. However, auxiliary nodes do not have read and write functions. For example, auxiliary nodes only support sending carrier signals to AIoT devices and do not support receiving reflected signals from AIoT devices. Intermediate nodes not only support sending carrier signals to AIoT devices, but also support receiving reflected signals from AIoT devices.

[0255] It should be noted that in the implementation disclosed in this application, intermediate nodes include but are not limited to UE readers and A-IoT-enabled UEs. In other words, in the implementation disclosed in this application, intermediate nodes, UE readers, and A-IoT-enabled UEs are interchangeable, and this application does not impose any special restrictions on this.

[0256] The authentication process for an intermediate node requesting to be used as an excitation source can be performed by core network equipment, or by a base station or OAM network element. The following describes the authentication process for a central node by a core network element and for an intermediate node by a base station / OAM, respectively, with reference to Figures 7 and 8.

[0257] FIG7 is a schematic diagram of a communication method provided in another embodiment of the present application.

[0258] Figure 7 provides a communication method 800. Under a topology structure of an A-IoT system, an intermediate node and / or an auxiliary device requests to be an excitation source and is authenticated by a core network element. The communication method 800 includes the following four stages, specifically including the following steps.

[0259] S801: The intermediate node sends first request information and / or first capability information to a base station / core network element.

[0260] The first request information is used to request authentication of whether the intermediate node can serve as a reader or relay point for the Tag / AIoT device; the first capability information is the intermediate node's capability as a reader / relay for the Tag / AIoT device.

[0261] In a specific implementation manner, the intermediate node sends first request information and / or first capability information to the base station.

[0262] In an optional implementation manner, the intermediate node sends the first capability information and / or the first request information by sending UECapabilityInformation (user equipment capability information) to the base station.

[0263] In another optional implementation, the first capability information and / or the first request information of the intermediate node may also be included in a NAS message in the RRC setup complete message. For example, the NAS message may be a registration request message or a timing advance (TA) update message.

[0264] In another optional implementation manner, the first capability information and / or the first request information of the intermediate node may also be included in a NAS message in the RRC re-establishment complete message / RRC recovery complete message.

[0265] In another optional implementation manner, the first capability information and / or the first request information of the intermediate node may also be simultaneously included in other RRC messages sent by the intermediate node to the network, such as UEAssistanceInformation (user equipment assistance information) and the like.

[0266] In another optional implementation manner, the first capability information and / or the first request information of the intermediate node may also be carried by different RRC messages.

[0267] In another optional implementation manner, the first request information may be encrypted using an encryption method negotiated between the intermediate node and the base station.

[0268] In another specific implementation manner, the base station sends first request information and / or first capability information to the core network device / network element.

[0269] In an optional implementation manner, the base station may send a NAS message received in an RRC setup complete message to the core network device / network element, where the NAS message includes the first request information and / or UE capability information.

[0270] In another optional implementation, the NAS message received in the RRC setup complete message may be sent via an initial UE message.

[0271] S802: The core network element authenticates the intermediate node as a reader / writer.

[0272] After receiving the first request information, the core network device determines whether the intermediate node can serve as the reader / relay of the AIoT device.

[0273] In a specific implementation, the first request information includes one or more of the following: UE identification information, secret key information, indication information of the encryption algorithm, a random number, or a parameter calculated based on the secret key algorithm. After receiving the first indication information, the core network device may perform a symmetric encryption calculation and then compare the calculation with the parameters calculated based on the secret key in the first request information. If they are consistent, authentication succeeds; otherwise, authentication fails.

[0274] In another specific implementation, the core network device / network element receives the capability information of the intermediate node at the same time as / after receiving the first request information. The core network device / network element may further authenticate the intermediate node based on the capability information of the intermediate node.

[0275] It should be understood that in some implementations, the intermediate node may also be referred to as a UE, and this application does not impose any special limitation on this.

[0276] S803: The core network element sends first response information to the intermediate node.

[0277] The first response information is used to indicate the authorization of the intermediate node as the reader / writer of the system.

[0278] Correspondingly, the intermediate node receives the first response information, wherein the first response information indicates that the intermediate node has been verified as a reader / relay of the AIoT device.

[0279] After the core network device successfully authenticates the intermediate node, it can send a first response message to the base station. After receiving the first response message, the base station forwards it to the UE.

[0280] In a specific implementation, the base station can decode the first response information to learn whether the authentication of the intermediate node as a reader / relay of the AIoT device has passed or failed.

[0281] In another specific implementation manner, the core network sends a first response message to the base station, including a NAS message, where the NAS message includes first response information; after receiving the NAS message, the base station forwards it to the UE.

[0282] In an optional implementation, the first response message also includes second indication information, and the base station can decode the indication information to learn whether the authentication of the UE as a reader / relay of the AIoT device has passed / failed.

[0283] In another optional implementation, the second indication information may also not be included in the first response message, but included in other messages / information and sent separately by the core network to the base station.

[0284] It should be understood that after receiving the instruction to authenticate the intermediate node as a reader / writer, the base station needs to configure resource configuration information dedicated to the intermediate node for A-IoT services. Among them, A-IoT services may include but are not limited to inventory, positioning, sensing, command, etc.

[0285] It should be understood that in some implementations, A-IoT can also be written as A-IOT, AIOT, etc., all of which represent ambient internet of things (A-IoT) technology, and this application does not make any special limitations on this.

[0286] It should be understood that the above steps S801 to S803 are steps for authenticating the intermediate node as a reader / writer, which are optional steps; if the intermediate node has been configured as a reader / writer or relay point, there is no need to authorize authentication again, and the following four stages of steps can be directly executed.

[0287] Phase 1: Identify incentive needs.

[0288] In Phase 1, the A-IoT system confirms that an excitation source is required in the system and that one or more excitation sources are needed to transmit a carrier wave. This includes the following steps.

[0289] S804a: The base station sends excitation source requirement information 1 to the intermediate node and / or auxiliary device.

[0290] Excitation source requirement information 1 indicates the frequency range of the carriers supported by the current base station in the current A-IoT system. Excitation source requirement information 1 also indicates the capabilities of the excitation source required by the current A-IoT system. Intermediate nodes and / or auxiliary devices access the network based on excitation source requirement information 1. Intermediate nodes and / or auxiliary devices that access the network can provide carrier configurations that meet the requirements of excitation source requirement information 1.

[0291] It should be understood that the excitation source requirement information 1 sent by the base station can be included in the system information (SIB), such as being carried in SIB1, or can be sent through other messages or information. This application does not impose any special restrictions on this.

[0292] S804b: The intermediate node sends excitation source requirement information 2 to the base station.

[0293] The excitation source requirement information 2 is used to indicate that the base station (intermediate node when communicating with the tag) needs an excitation source.

[0294] In a specific implementation, the excitation source requirement information 2 includes UECapabilityInformation (user equipment capability information), that is, the intermediate node sends UECapabilityInformation to the base station to indicate its capability information.

[0295] In another specific implementation, the excitation source requirement information 2 does not include capability information for indicating the excitation of the excitation source, and then the base station sends other information to the intermediate node and / or auxiliary UE to indicate the capability information of the excitation source required by the system and / or the frequency range of the carrier supported by the current base station.

[0296] It should be understood that in stage 1, either step S804a or step S804b can be performed.

[0297] Phase 2: Core network authentication phase.

[0298] In Phase 2, the core network may authenticate intermediate nodes and / or auxiliary devices as activation sources.

[0299] Phase 2a: Core network equipment authentication intermediate node.

[0300] S805a: The intermediate node sends excitation source request information 1.

[0301] Stimulus source request information 1 is used to instruct the core network element to authenticate whether the intermediate node can serve as the stimulus source for the A-IoT device, that is, to instruct the core network element to authenticate whether the intermediate node can serve as the stimulus source for providing carriers. Stimulus source request information 1 may also include capability information of the intermediate node.

[0302] It should be understood that the excitation source request information 1 and the reader / writer request information 1 in S801 can be sent through one message or sent separately through two messages, and this application does not make any special limitation on this.

[0303] In a specific implementation method, the excitation source request information 1 also includes the capability information of the intermediate node, and the capability information of the intermediate node includes the intermediate node's ability to support single-tone and / or multi-tone, the ability to send carriers, the ability to receive signals based on carriers, and / or the ability to reflect signals, etc.

[0304] In a specific implementation manner, the excitation source request information 1 is included in a radio resource control (RRC) message and sent.

[0305] In an optional implementation manner, the intermediate node may send the excitation source request information 1 of the intermediate node by sending UECapabilityInformation information to the base station.

[0306] In another optional implementation, the intermediate node's excitation source request information 1 is included in a non-access stratum (NAS) message in the RRC setup complete message. For example, the NAS message may be a registration request message or a timing advance (TA) update message.

[0307] In another optional implementation manner, the excitation source request information 1 of the intermediate node is included in a NAS message in an RRC re-establishment complete message or an RRC recovery complete message.

[0308] In another optional implementation, the stimulus source request information 1 of the intermediate node includes request information requesting the core network element to perform stimulus source authentication, and also includes capability information indicating the intermediate node. The request information and / or capability information are also included in other RRC messages sent by the UE to the network, such as UEAssistanceInformation (user equipment assistance information).

[0309] In another optional implementation, the stimulus source request information 1 of the intermediate node includes request information requesting the core network element to perform stimulus source authentication and also includes capability information indicating the intermediate node, wherein the request information and / or capability information are carried by different RRC messages.

[0310] In another optional implementation, the stimulus source request information 1 may be encrypted using an encryption method negotiated between the intermediate node and the base station. When the stimulus source request information 1 of the intermediate node includes request information requesting a core network element to perform stimulus source authentication and also includes capability information indicating the intermediate node, only the request information may be encrypted, and the capability information may not be encrypted.

[0311] In a specific implementation manner, the intermediate node sends or forwards the excitation source request information 1 to the core network element.

[0312] In another specific implementation, the intermediate node sends the excitation source request information 1 to the base station, which then forwards or sends the excitation source request information 1 to the core network element. Exemplarily, the base station may send a NAS message received in an RRC setup complete message / RRC re-establishment complete message / RRC recovery complete message to the core network element, where the NAS message includes the excitation source request information 1. Exemplarily, the NAS message received in the above RRC messages may be sent to the core network via an initial UE message.

[0313] It should be understood that in some specific implementations, the core network element may be referred to as a core network device, etc., which is merely a name reference and does not constitute any limitation on the scope of protection of this application.

[0314] It should be understood that the base station can forward the excitation source request information 1 and the reader request information 1 in S801 at the same time, or can forward them separately. This application does not impose any special limitation on this.

[0315] It should be understood that the excitation source request information 1 is a specific implementation of the first information in the above implementation, and this application does not make any special limitation on this.

[0316] S806a: The core network element authenticates the intermediate node as an excitation source.

[0317] The core network element authenticates the intermediate node according to the stimulus source request information 1.

[0318] It should be understood that the core network element's authentication of the intermediate node as a reader / writer and / or the core network element's authentication of the intermediate node as an excitation source can be performed simultaneously or separately, and this application does not impose any specific restrictions on this. That is, S806a and S802 can be performed simultaneously or separately, and this application does not impose any specific restrictions on this.

[0319] It should be understood that there may be one or more intermediate nodes that make incentive authentication requests to the core network, and this application does not impose any special restrictions on this.

[0320] After receiving the excitation source request information 1, the core network element authenticates and authorizes the intermediate node as the excitation source based on the request information and / or capability information contained in the excitation source request information 1 to determine whether the intermediate node can serve as the excitation source of the AIoT device.

[0321] In a specific implementation, the request information included in the stimulus source request information 1 includes one or more of the following: intermediate node identification information, secret key information, information indicating an encryption algorithm, a random number, or parameters calculated based on a secret key algorithm. After receiving the stimulus source request information 1, the core network device may perform a symmetric encryption calculation and then compare the parameters with the parameters calculated based on the secret key in the request information. If they are consistent, authentication succeeds; otherwise, authentication fails.

[0322] In another specific implementation, the stimulus source request information 1 includes not only the authentication request of the central node but also the capability information of the central node. Then the core network can also authenticate the intermediate node in combination with the capability information of the intermediate node.

[0323] It should be understood that the authentication request information and capability information of the central node can be sent separately or together. If the core network element receives the capability information of the intermediate node at the same time or after receiving the request information, the core network can also authenticate the intermediate node in combination with the capability information of the intermediate node.

[0324] In an optional implementation, the excitation source request information 1 may further include other auxiliary information, such as location information of the intermediate node and / or auxiliary device and the tag, beam information, etc. The core network element may also determine whether to authorize the intermediate node and / or auxiliary device as an excitation source based on the auxiliary information included in the excitation source request information 1.

[0325] S807a: The core network element sends authentication instruction information 1.

[0326] After the core network element verifies the intermediate node, it sends authentication indication information 1, which indicates the authentication result, including success or failure. When the intermediate node is successfully authenticated, authentication indication information 1 indicates that the intermediate node has been verified as an excitation source for the AIoT device, or that the intermediate node has been verified as a carrier.

[0327] The core network element sends authentication instruction information 1 to the base station. The base station then forwards the authentication result to the intermediate node.

[0328] It should be understood that the authorization indication information 1 and the authentication indication information 1 sent by the core network network element can be sent through the same message or sent separately, and this application does not make any special restrictions on this.

[0329] In a specific implementation manner, the base station may decode the authentication indication information 1, and obtain the authentication result (pass or fail) of the intermediate node according to the decoded authentication indication information 1, and send the authentication result to the intermediate node.

[0330] It should be understood that the base station can directly forward the authentication indication information 1 to the intermediate node, and the base station can also send the authentication result to the intermediate node through other information. This application does not make any special limitations on this.

[0331] In another specific implementation, the base station is unable to decode authentication indication information 1, that is, the base station is unable to obtain the authentication result of the intermediate node based on authentication indication information 1, and the base station directly forwards authentication indication information 1 to the intermediate node. For example, when a core network element sends an NAS message carrying authentication indication information 1 to the base station, the base station is unable to decode the NAS message. After receiving the NAS message, the base station forwards it to the intermediate node.

[0332] In an optional implementation, the information sent by the core network element to the base station includes, in addition to the NAS message containing the authentication indication information 1, separate indication information. The base station can obtain the authentication result by decoding the indication information.

[0333] In an optional implementation, in addition to sending a NAS message including authentication indication information 1 to the base station, the core network element also sends other indication information to the base station, and the base station can obtain the authentication result by decoding the indication information.

[0334] It should be understood that the authentication indication information 1 is a specific implementation of the second information in the above implementation, and this application does not impose any special limitation on this.

[0335] Phase 2b: Core network equipment authentication auxiliary equipment.

[0336] S805b: The auxiliary device sends excitation source request information 2.

[0337] S806b: The core network element authenticates the auxiliary device as an excitation source.

[0338] S807b: The core network element sends authentication instruction information 2.

[0339] It should be understood that steps S805b to S807b in stage 2b are similar to steps S805a to S807a in stage 2a, with the intermediate node being replaced by an auxiliary device, and this application will not elaborate on this.

[0340] It should be understood that the steps of the above-mentioned phase 2a and phase 2b can be performed in full or in a selective manner. That is, the core network device can authenticate the intermediate node and / or auxiliary device as the excitation source of the current system according to actual conditions, and this application does not impose any special restrictions on this.

[0341] It should be understood that the above-mentioned stage 2a can be performed simultaneously with the steps in steps S801 to S803, or they can be performed separately. That is, the core network's authentication process for the intermediate node requesting authentication as a reader and / or excitation source of an A-IoT device can be performed simultaneously, or the two authentication processes can be performed separately. This application does not specifically limit this.

[0342] Phase 3: Configure carrier information.

[0343] In phase 3, the base station sends carrier configuration information to the authenticated intermediate node and / or auxiliary device.

[0344] S808a: The base station sends carrier configuration information 1 to the intermediate node.

[0345] The base station sends carrier configuration 1 to the authenticated excitation source. Carrier configuration information 1 is used to indicate the configuration of the carrier sent by the intermediate node, and may include carrier configuration information in single-tone and / or multi-tone mode.

[0346] It should be understood that the authenticated excitation source includes one or more intermediate nodes and / or auxiliary devices, and this application does not impose any special limitation on this.

[0347] In a specific implementation method, the carrier configuration information 1 is used to instruct the intermediate node to send a carrier in a multi-tone mode, which may specifically include at least one of the following configuration information: frequency domain position, number of tones (that is, the number of subcarriers that the base station can allocate at one time for label upload data transmission), transmission power information, protection interval, transmission start time, transmission end time, transmission cycle, duration, etc.

[0348] In an optional implementation, the carrier configuration information 1 is also used to indicate that the carrier in the multi-tone mode is configured in a frequency hopping mode, so that different tones occupy different times, so as to improve the effect of resisting the frequency selective fading of the channel, improve the reflected signal capability, improve the anti-interference capability, etc.

[0349] It should be understood that carrier configuration information 1 is a specific implementation of the first configuration information in the above implementation, and this application does not make any special limitation on this.

[0350] S808b: The base station sends carrier configuration information 2 to the auxiliary device.

[0351] The base station sends carrier configuration 2 to the authenticated excitation source. Carrier configuration information 2 is used to indicate the configuration of the carrier sent by the auxiliary device, and may include carrier configuration information in single-tone and / or multi-tone mode.

[0352] It should be understood that the execution steps of S808b are similar to those of S808a, and are not described in detail herein. Carrier configuration information 1 and carrier configuration information 2 may include the same configuration parameters or different configuration parameters, and this application does not impose any special restrictions on this.

[0353] It should be understood that S808a and S808b can be executed one by one or both, which is determined by the excitation source device that has actually passed the authentication. This application does not impose any special restrictions on this.

[0354] It should be understood that carrier configuration information 2 is a specific implementation of the second configuration information in the above implementation, and this application does not make any special limitation on this.

[0355] It should be noted that the base station can provide corresponding carrier configuration information to the intermediate node (intermediate node) / excitation source through downlink control information (DCI), MAC layer control element (CE) or RRC message, that is, the base station can send carrier configuration information 1 to the intermediate node through DCI / MAC CE / RRC message, and send carrier configuration information 2 to the excitation source through DCI / MAC CE / RRC message. This application does not make any special restrictions on this.

[0356] It should be noted that in the carrier configuration information provided by the base station to the intermediate node / excitation source, the carrier configuration information can be a single-tone mode and / or a multi-tone mode, where the multi-tone mode can be configured as frequency hopping to enable different tones to operate at different times.

[0357] It should be understood that the base station may send the frequency hopping configuration to the intermediate node / stimulation source via a DCI / MAC CE / RRC message.

[0358] Phase 4: Send carrier.

[0359] In phase 4, the successfully authenticated stimulus source sends the corresponding carrier according to the carrier configuration information sent by the base station.

[0360] S809a: The intermediate node sends carrier 1.

[0361] The intermediate node sends carrier 1 that meets the configuration according to carrier configuration information 1.

[0362] It should be understood that carrier 1 can be a carrier that specifically sends one or more tags, or it can be a carrier that covers a specific range, and this application does not impose any special restrictions on this.

[0363] S809b: The auxiliary device sends carrier 2.

[0364] The auxiliary device sends carrier 2 that meets the configuration according to carrier configuration information 2.

[0365] It should be understood that carrier 2 can be a carrier that specifically sends one or more tags, or it can be a carrier that covers a specific range, and this application does not impose any special restrictions on this.

[0366] It should be understood that S809a and S809b can be executed one by one or both, which is determined by the excitation source device that has passed the actual authentication. This application does not make any special restrictions on this.

[0367] The tag receives the carrier 1 and / or carrier 2 signals and reflects them according to the carrier.

[0368] It should be understood that the intermediate node also sends downlink data to the tag, and the tag receives the downlink data and reflects the uplink signal according to the carrier.

[0369] It should be understood that the implementation described in this application may include one or more intermediate nodes, and this application does not impose any special limitation on this.

[0370] It should be understood that the implementation described in this application may include one or more auxiliary devices, and this application does not impose any special limitation on this.

[0371] It should be understood that in the implementation described in this application, the tag can be a terminal device such as an A-IoT device, and this application does not impose any special limitations on this.

[0372] It should be understood that in the implementation method described in this application, the core network network element can be a tag management function (TMF) network element, or an access and mobility management function (AMF) network element, or an ambient IoT management function (AIoTMF), or other network elements, and this application does not limit this.

[0373] In one specific implementation, the core network element includes a TMF element. This can be understood as the TMF element assuming some of the functions of the AMF element. After receiving a service request (for AIOT), the TMF element sends the service request to the AMF element. In another specific implementation, the core network element includes an AMF element, and the AMF element receives the service request directly from the server. This application does not impose any special restrictions on this.

[0374] It should be understood that in the communication method 800 shown in FIG7 , both the intermediate node and the auxiliary device are controlled by the network. The auxiliary device can also be controlled by the intermediate node via the PC5 interface. The specific steps of controlling the auxiliary device via the PC5 interface and performing stimulus source authentication are similar to S805b to S807b in the above-mentioned stage 2b and will not be repeated here.

[0375] The core network element authenticates the authentication request of the intermediate node as the excitation source, thereby ensuring the legitimacy of the carrier sent by the intermediate node. In addition, the technical solution of the present application also supports the excitation source to send the carrier in a multi-tone mode.

[0376] In one A-IoT system topology, intermediate nodes and / or auxiliary devices requesting to be the stimulus source can be authenticated not only by core network elements but also by base stations or operations, administration, and maintenance (OAM) elements. The steps for authenticating the stimulus source through base stations or OAM elements are shown in Figure 8.

[0377] FIG8 is a schematic diagram of a communication method provided in yet another embodiment of the present application.

[0378] FIG8 provides a communication method 900 , in which, in a topology of an A-IoT system, an intermediate node and / or an auxiliary device requests to be an excitation source and is authenticated by a base station or an OAM network element. The communication method 900 is similar to some steps in method 800 .

[0379] It should be understood that the steps of requesting the intermediate node and / or auxiliary device as the excitation source are similar to those in method 800. Therefore, in method 900, the requests of the intermediate node and the auxiliary device are no longer described separately. The request steps of the intermediate node and the auxiliary device can be performed one by one or both, and this application does not make any special restrictions on this. In the A-IoT system, one or more intermediate nodes can be used as the excitation source, or one or more auxiliary devices can be used as the excitation source. In the A-IoT system, only the intermediate node or the auxiliary device can be used as the excitation source, or both the intermediate node and the auxiliary device can be used as the excitation source. This application does not make any special restrictions on this, nor should it be considered that the above possible implementation methods exceed the scope of protection of this application.

[0380] It should be understood that method 900 may also include a step in which the intermediate node sends a request to the base station and / or core network element to act as a reader and performs authentication (not shown in the figure). The specific steps can be referred to S801 to S803 in method 800, and this application will not repeat them here.

[0381] Method 900 also includes four stages, specifically including the following steps:

[0382] Phase 1: Identify stimulus requirements.

[0383] In Phase 1, the A-IoT system confirms that an excitation source is required and that one or more excitation sources are needed to transmit a carrier wave. Specifically, the base station sends excitation requirement information to the intermediate node and / or auxiliary device, and the intermediate node also sends excitation source requirement information to the base station. The specific steps are similar to S804a and S804b and will not be further described in this application.

[0384] Phase 2: Identify the stimulus source.

[0385] In phase 2, the base station or OAM network element needs to authenticate the request reported by the intermediate node and / or auxiliary device as the stimulus source. Specifically, the authentication can be performed by the base station or OAM network element.

[0386] Phase 2a: Base station authentication stimulus source.

[0387] S901a: The intermediate node and / or the auxiliary device sends excitation source request information 3 to the base station.

[0388] It should be understood that step S901a includes the following execution modes: only the intermediate node sends the excitation source request information 3 to the base station, only the auxiliary device sends the excitation source request information 3 to the base station, and both the intermediate node and the auxiliary device send the request information 3 to the excitation source.

[0389] Stimulus source request information 3 is used to instruct the base station whether the intermediate node and / or auxiliary device can serve as the excitation source of the A-IoT device. In other words, it is used to instruct the base station whether the intermediate node and / or auxiliary device can serve as the excitation source for providing the carrier. Stimulus source request information 3 may also include capability information of the intermediate node and / or auxiliary device.

[0390] In a specific implementation method, the excitation source request information 3 also includes the capability information of the intermediate node, and the capability information of the intermediate node includes the intermediate node's ability to support single-tone and / or multi-tone, the ability to send carriers, the ability to receive signals based on carriers, and / or the ability to reflect signals, etc.

[0391] It should be understood that the excitation source request information 3 and the excitation source request information 1 and the excitation source request information 2 can be information of the same field or information of different fields, and this application does not make any special limitation on this.

[0392] It should be understood that the sending method of excitation source request information 3 is similar to that of excitation source request information 1 and excitation source request information 2. For details, please refer to the sending method of excitation source request information 1 in method 800, and this application will not go into details here.

[0393] It should be understood that when the intermediate node sends the stimulus source request information 3 to the base station, it can also send the base station a reader / writer request information 1 requesting to serve as the A-IoT system. The reader / writer request information 1 and the stimulus source request information 3 can be sent in the same message or separately, and this application does not impose any special restrictions on this.

[0394] It should be understood that the excitation source request information 3 is a specific implementation of the first information in the above implementation, and this application does not make any special limitation on this.

[0395] S902a: The base station authenticates the intermediate node and / or auxiliary device as an excitation source.

[0396] The base station authenticates the intermediate node and / or the auxiliary device according to the stimulus source request information 3 .

[0397] In a specific implementation manner, the base station may further authenticate the intermediate node as a reader / writer according to the reader / writer request information 1 .

[0398] It should be understood that the authentication of the intermediate node as a reader / writer by the base station and / or the authentication of the intermediate node as an excitation source by the base station can be performed simultaneously or separately, and this application does not impose any special restrictions on this.

[0399] It should be understood that there may be one or more intermediate nodes making an incentive authentication request to the base station, and there may be one or more auxiliary devices making an incentive authentication request to the base station, and this application does not make any special restrictions on this.

[0400] After receiving the excitation source request information 3, the base station authenticates and authorizes the intermediate node and / or auxiliary device as the excitation source according to the request information and / or capability information contained in the excitation source request information 3, and determines whether the intermediate node and / or auxiliary device can serve as the excitation source of the AIoT device.

[0401] In a specific implementation, the excitation source request information 3 also includes other auxiliary information, such as location information of the intermediate node and / or auxiliary device and the tag, beam information, etc. The base station can also determine whether to authorize the intermediate node and / or auxiliary device as an excitation source based on the auxiliary information included in the excitation source request information 3.

[0402] S903a: The base station sends authentication instruction information 3.

[0403] After verifying the intermediate node and / or the auxiliary device, the base station sends authentication indication information 3, where the authentication indication information 3 is used to indicate the result of the authentication, including authentication success or authentication failure.

[0404] It should be understood that the base station's indication information for authenticating or refusing the intermediate node as a reader / writer and the base station's indication information for authenticating or refusing the intermediate node as an excitation source can be carried on the same message and sent, or can be carried separately on different messages and sent to the intermediate node. This application does not impose any special restrictions on this.

[0405] It should be understood that the authentication indication information 3 is a specific implementation of the second information in the above implementation, and this application does not make any special limitation on this.

[0406] In an optional implementation manner, the base station further executes S904a.

[0407] S904a: The base station sends authentication synchronization information 1 to the core network element.

[0408] The base station synchronizes the authentication results of the intermediate node and / or auxiliary device with the core network element via authentication synchronization information 1. Authentication synchronization information 1 is used to indicate whether the intermediate node and / or auxiliary device is accepted or rejected by the base station as an excitation source.

[0409] It should be understood that if the steps in stage 2a are performed by an intermediate node, they can be performed simultaneously with steps S801 to S803 in method 800, or they can be performed separately. That is, the base station can perform the authentication process for the intermediate node's request to authenticate itself as a reader and / or excitation source for an A-IoT device simultaneously, or the two authentication processes can be performed separately. This application does not impose any specific restrictions on this.

[0410] Phase 2b: OAM authentication stimulus source.

[0411] S901b: The intermediate node and / or auxiliary device sends an excitation source request message 4 to the OAM.

[0412] It should be understood that the excitation source request information 4 is a specific implementation of the first information in the above implementation, and this application does not make any special limitation on this.

[0413] S902b: OAM authenticates the intermediate node and / or auxiliary device as an excitation source.

[0414] S903b: OAM sends authentication instruction information 4.

[0415] After the OAM verifies the intermediate node, it sends authentication indication information 4, which is used to indicate the result of the authentication, including authentication success or authentication failure.

[0416] In one specific implementation, the OAM directly sends authentication indication information 4 to the intermediate node and / or auxiliary device to indicate the authentication result. In this case, the OAM also needs to send synchronization information to the base station to synchronize the authentication result. If the authentication result indicates that the intermediate node and / or auxiliary device is accepted as the stimulus source, the base station executes step S905 based on the synchronization information and sends carrier configuration information to the intermediate node and / or auxiliary device.

[0417] In another specific implementation, the OAM sends authentication indication information 4 to the base station, which then forwards it to the intermediate node and / or auxiliary device to indicate the authentication result. It should be understood that the base station may directly forward the authentication indication information 4 to the intermediate node and / or auxiliary device, or the base station may send the authentication result to the intermediate node and / or auxiliary device via other information, and this application does not specifically limit this.

[0418] Specifically, if the base station can decode the authentication indication information 4, and obtain the authentication result of the intermediate node and / or the auxiliary device according to the decoded authentication indication information 4, and send the authentication result to the intermediate node and / or the auxiliary device. In response to the authentication result indicating that the intermediate node and / or the auxiliary device is accepted as the stimulation source, the base station performs step S905 based on the authentication result and sends the carrier configuration information to the intermediate node and / or the auxiliary device.

[0419] Specifically, if the base station is unable to decode authentication indication information 4, that is, if the base station is unable to obtain the authentication result of the intermediate node and / or auxiliary device based on authentication indication information 4, the base station directly forwards authentication indication information 4 to the intermediate node and / or auxiliary device. The OAM network element also sends other synchronization information to the base station to indicate the authentication result. Based on this synchronization information, the base station obtains the authentication result and, in response to the authentication result indicating acceptance of the intermediate node and / or auxiliary device as an excitation source, executes step S905 based on the synchronization information and sends carrier configuration information to the intermediate node and / or auxiliary device.

[0420] It should be understood that the authentication indication information 3 is a specific implementation of the second information in the above implementation, and this application does not make any special limitation on this.

[0421] In an optional implementation, the OAM further executes S904b.

[0422] S904b: OAM sends authentication synchronization information 2 to the core network element.

[0423] It should be understood that steps S901b to S904b in stage 2b are similar to steps S901a to S904a in stage 2a, except that the base station is replaced by an OAM network element, and this application will not go into details therein.

[0424] It should be understood that the steps of the above-mentioned stage 2a and stage 2b may be performed in whole or in part. That is, the base station may authenticate the intermediate node and / or auxiliary device as the excitation source of the current system based on actual conditions, and the OAM network element may also authenticate the intermediate node and / or auxiliary device as the excitation source of the current system based on actual conditions. Alternatively, both the base station and the OAM may perform authentication simultaneously, and this application does not impose any specific restrictions on this.

[0425] It should be understood that if the steps in stage 2b are performed by an intermediate node, they can be performed simultaneously with steps S801 to S803 in method 800, or they can be performed separately. That is, the OAM authentication process for the intermediate node's request to authenticate itself as a reader and / or excitation source for an A-IoT device can be performed simultaneously, or the two authentication processes can be performed separately. This application does not impose any specific limitations on this.

[0426] It should be understood that the authentication process of the base station for the intermediate node and / or auxiliary device as the excitation source is similar to the authentication process of the core network network element for the intermediate node and / or auxiliary device as the excitation source. The specific implementation method in stage 2 of method 800 can be referred to. Those skilled in the art can replace the core network network element with the base station device for implementation. This application will not go into details here, and it should not be considered to exceed the scope of protection of this application.

[0427] Phase 3: Configure carrier information.

[0428] In phase 3, the base station sends carrier configuration information to the authenticated intermediate node and / or auxiliary device.

[0429] S905a: The base station sends carrier configuration information 1 / 2 to the intermediate node and / or auxiliary device.

[0430] The base station sends carrier configuration information 1 to the authenticated intermediate node. The carrier configuration information 1 is used to indicate the configuration of the carrier sent by the intermediate node, and may include carrier configuration information in single-tone and / or multi-tone mode.

[0431] The base station sends carrier configuration information 2 to the authenticated auxiliary device. The carrier configuration information 2 is used to indicate the configuration of the carrier sent by the auxiliary device, and may include carrier configuration information in single-tone and / or multi-tone mode.

[0432] In a specific implementation method, carrier configuration information 1 and / or carrier configuration information 2 are used to instruct the intermediate node to send a carrier in multi-tone mode, which may specifically include at least one of the following configuration information: frequency domain position, number of tones (i.e., the number of subcarriers that the base station can allocate at one time for label upload data transmission), transmission power information, protection interval, transmission start time, transmission end time, transmission cycle, duration, etc.

[0433] In an optional implementation, carrier configuration information 1 and / or carrier configuration information 2 is also used to indicate that the carrier in multi-tone mode is configured in frequency hopping mode, so that different tones occupy different times, so as to improve the effect of resisting frequency selective fading of the channel, improve the reflected signal capability, improve the anti-interference capability, etc.

[0434] It should be understood that carrier configuration information 1 is a specific implementation of the first configuration information in the above implementation, and this application does not make any special limitation on this.

[0435] It should be understood that carrier configuration information 2 is a specific implementation of the second configuration information in the above implementation, and this application does not make any special limitation on this.

[0436] It should be understood that if only the steps in Stage 2b are executed in Stage 2, i.e., only the OAM network element authenticates whether the intermediate node and / or auxiliary device can serve as the excitation source for the current system and sends the authentication result directly to the intermediate node and / or auxiliary device, the OAM network element is required to inform the base station of the authentication result through other synchronization information. In response to the OAM accepting the intermediate node and / or auxiliary device as the excitation source for the current system, the base station sends carrier configuration information 1 / 2 to the intermediate node and / or auxiliary device.

[0437] Phase 4: The intermediate node and / or auxiliary device sends the carrier.

[0438] In phase 4, the successfully authenticated stimulus source sends the corresponding carrier according to the carrier configuration information sent by the base station.

[0439] S906: The intermediate node and / or the auxiliary device sends carrier 1 / 2.

[0440] The intermediate node sends carrier 1 that meets the configuration according to carrier configuration information 1.

[0441] The auxiliary device sends carrier 2 that meets the configuration according to carrier configuration information 2.

[0442] The tag receives the carrier 1 and / or carrier 2 signals and reflects them according to the carrier.

[0443] It should be understood that in the implementation method described in this application, the core network network element can be a tag management function (TMF) network element, or an access and mobility management function (AMF) network element, or an ambient IoT management function (AIoTMF), or other network elements, and this application does not limit this.

[0444] In one specific implementation, the core network element includes a TMF element. This can be understood as the TMF element assuming some of the functions of the AMF element. After receiving a service request (for AIOT), the TMF element sends the service request to the AMF element. In another specific implementation, the core network element includes an AMF element, and the AMF element receives the service request directly from the server. This application does not impose any special restrictions on this.

[0445] It should be understood that in the communication method 900 shown in Figure 8, the intermediate node and the auxiliary device are both controlled by the network. The auxiliary device can also be controlled by the intermediate node through the PC5 interface, which will not be described in detail in this application.

[0446] It should be understood that the indication information in some steps of method 900 and method 800 has similar functions, and this application will not elaborate on this. The extension of the indication information with similar functions will not be elaborated on either, and reference may be made to the relevant description in method 800.

[0447] It should be understood that some steps in method 900 may be replaced, performed alternately, performed simultaneously, or performed in combination with steps in method 800 to solve the technical problem of the present application. This application does not list them one by one here, and this application does not make any special limitations thereto. New technical solutions formed by combining the steps in the method of this application should not be considered to exceed the scope of protection of this application.

[0448] The authentication request of the intermediate node as the excitation source is authenticated by the base station and / or OAM network element, thereby ensuring the legitimacy of the carrier transmitted by the intermediate node. In addition, the technical solution of the present application also supports the excitation source to transmit the carrier in a multi-tone mode.

[0449] FIG9 is a schematic diagram of another communication method provided in an embodiment of the present application.

[0450] FIG9 provides a communication method 100 , in which, in a topology of an A-IoT system, an auxiliary device requests to be an excitation source, and a base station sends carrier configuration information in a multi-tone mode to the authenticated auxiliary device.

[0451] It should be understood that, in an optional implementation, the authentication process of the auxiliary device requesting to be used as an excitation source may be performed by a core network element, with the specific steps being as shown in method 800. In another optional implementation, the authentication process of the auxiliary device requesting to be used as an excitation source may be performed by a base station or an OAM network element, with the specific steps being as shown in method 900. This application does not further describe the various authentication methods for the auxiliary device requesting to be used as an excitation source.

[0452] This application describes a communication method 100 in which a base station sends carrier configuration information in a multi-tone mode to an authenticated auxiliary device, taking the authentication of the auxiliary device by a core network element as an example. The communication method 100 includes four stages, specifically the following steps:

[0453] Phase 1: Identify stimulus requirements.

[0454] In Phase 1, the A-IoT system confirms that an excitation source is required and that one or more excitation sources are needed to transmit a carrier wave. This includes the base station sending excitation requirement information to the auxiliary device. The specific steps are similar to those in S804a and will not be described in detail in this application.

[0455] Phase 2: Core network authentication auxiliary equipment.

[0456] S101: The auxiliary device sends an excitation source request message 5.

[0457] The excitation source request information 5 is used to instruct the core network element to authenticate whether the auxiliary device can serve as the excitation source of the A-IoT device, that is, to instruct the core network element to authenticate whether the auxiliary device can serve as the excitation source for providing carriers. The excitation source request information 5 may also include capability information of the auxiliary device.

[0458] It should be understood that the excitation source request information 5 and the excitation source request information 2 and the excitation source request information 4 can be the same information or different information, and this application does not impose any special limitation on this.

[0459] In a specific implementation manner, the auxiliary device sends the excitation source request information 5 to the core network element.

[0460] In another specific implementation manner, the auxiliary device sends the excitation source request information 5 to the base station, and the base station then forwards the excitation source request information 5 to the core network element.

[0461] S102: The core network element authenticates the auxiliary device as an excitation source.

[0462] The core network element authenticates the auxiliary device according to the stimulus source request information 5.

[0463] S103: The core network element sends authentication instruction information 5.

[0464] After the core network element verifies the auxiliary device, it sends authentication indication information 5, which is used to indicate the authentication result, including authentication success or authentication failure. The base station then forwards the authentication result to the intermediate node.

[0465] It should be understood that stage 2 in method 100 may be implemented in other ways, such as stage 2b in method 800, stage 2a and stage 2b in method 900, etc. Those skilled in the art may combine the stages in the different methods described in this application to form new methods, and this application will not cite each of these examples here. However, such combinations should not be considered to exceed the scope of protection of this application.

[0466] Phase 3: Configure carrier information.

[0467] In phase 3, the base station sends carrier configuration information to the authenticated secondary device.

[0468] S104: The base station sends carrier configuration information 2 to the auxiliary device.

[0469] The base station sends carrier configuration 2 to the authenticated excitation source. Carrier configuration information 2 is used to indicate the configuration of the carrier sent by the auxiliary device, including carrier configuration information in the multi-tone mode.

[0470] It should be understood that the authenticated excitation source includes one or more auxiliary devices, and this application does not impose any special limitation on this.

[0471] In a specific implementation method, the carrier configuration information 2 is used to instruct the auxiliary device to send a carrier in a multi-tone mode, which may specifically include at least one of the following configuration information: frequency domain position, number of tones (that is, the number of subcarriers that the base station can allocate at one time for label upload data transmission), transmission power information, protection interval, transmission start time, transmission end time, transmission cycle, duration, etc.

[0472] In an optional implementation, the carrier configuration information 2 is also used to indicate that the carrier in the multi-tone mode is configured in a frequency hopping mode, so that different tones occupy different times, so as to improve the effect of resisting the frequency selective fading of the channel, improve the reflected signal capability, improve the anti-interference capability, etc.

[0473] It should be understood that carrier configuration information 2 is a specific implementation of the second configuration information in the above implementation, and this application does not make any special limitation on this.

[0474] Phase 4: Send carrier.

[0475] In phase 4, the successfully authenticated stimulus source sends the corresponding carrier according to the carrier configuration information sent by the base station.

[0476] S105: The auxiliary device sends carrier 2.

[0477] The auxiliary device sends carrier 2 that meets the configuration according to carrier configuration information 2.

[0478] The tag receives the carrier 2 signal and reflects it according to the carrier.

[0479] It should be understood that in the implementation method described in this application, the core network network element can be a tag management function (TMF) network element, or an access and mobility management function (AMF) network element, or an ambient IoT management function (AIoTMF), or other network elements, and this application does not limit this.

[0480] In one specific implementation, the core network element includes a TMF element. This can be understood as the TMF element assuming some of the functions of the AMF element. After receiving a service request (for AIOT), the TMF element sends the service request to the AMF element. In another specific implementation, the core network element includes an AMF element, and the AMF element receives the service request directly from the server. This application does not impose any special restrictions on this.

[0481] It should be understood that in the communication method 100 shown in Figure 9, the intermediate node and the auxiliary device are both controlled by the network. The auxiliary device can also be controlled by the intermediate node through the PC5 interface, which will not be described in detail in this application.

[0482] It should be understood that the indication information of some steps in method 100, method 900 and method 800 has similar functions, and this application will not elaborate on this. The extension of indication information with similar functions will not be elaborated on either, and reference may be made to the relevant description in method 800.

[0483] It should be understood that some steps in method 100 and method 900 may be replaced with, alternately executed, executed simultaneously, or combined with the steps in method 800. Those skilled in the art may implement these steps to solve the technical problems of this application. This application will not list them one by one here, and this application does not specifically limit this. New technical solutions formed by combining the steps in the method of this application should not be considered to exceed the scope of protection of this application.

[0484] FIG10 is a schematic diagram of a communication device provided in an embodiment of the present application.

[0485] As shown in Figure 10, the communication device 1000 may include a transceiver unit 1010 and a processing unit 1020. The transceiver unit 1010 may be used to implement corresponding communication functions. The transceiver unit 1010 may also be referred to as a communication interface or a communication unit. The processing unit 1020 may be used to determine resources and generate information. Optionally, the transceiver unit 1010 may include a receiving unit and a sending unit. The receiving unit is used to implement the receiving function, and the sending unit is used to implement the sending function.

[0486] Optionally, the communication device 1000 may further include a storage unit, which may be used to store instructions and / or data. The processing unit 1020 may read the instructions and / or data in the storage unit so that the device implements the aforementioned method embodiment.

[0487] As a design, the communication device 1000 is used to execute the steps or processes executed by the tag device, intermediate node, auxiliary device, base station device, OAM network element, or core network element in the above method embodiments, and the transceiver unit 1010 is used to perform the operations related to transceiver in the above method embodiments, for example, the intermediate node sends the first information through the transceiver unit 1010, and the intermediate node receives the second information, first configuration information, etc. through the transceiver unit 1010; the network device receives the first information through the transceiver unit 1010, and the network device sends the second information, first configuration information, etc. through the transceiver unit 1010. The processing unit 1020 is used to execute the operations related to determining resources and generating messages in the above method embodiments, for example, the network device determines whether the intermediate node can serve as an excitation source based on the first information through the processing unit 1020.

[0488] It should be understood that the specific process of each unit executing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0489] It should also be understood that the communication device 1000 here is embodied in the form of a functional unit. The term "unit" here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a dedicated processor or a group processor, etc.) and a memory for executing one or more software or firmware programs, a combined logic circuit and / or other suitable components that support the described functions. In an optional example, those skilled in the art will understand that the communication device 1000 can be specifically a device in the above-mentioned embodiment (such as a tag device, an intermediate node, an auxiliary device, a base station device, an OAM network element or a core network element, etc.), which can be used to execute the various processes and / or steps corresponding to the device in the above-mentioned method embodiments. To avoid repetition, they will not be described here.

[0490] The communication device 1000 of each of the above-mentioned schemes has the function of implementing the corresponding steps performed by the device or network element (such as a tag device, an intermediate node, an auxiliary device, a base station device, an OAM network element or a core network element, etc.) in the above-mentioned method. The function can be implemented by hardware, or the corresponding software can be implemented by hardware. The hardware or software includes one or more modules corresponding to the above-mentioned functions; for example, the transceiver unit can be replaced by a transceiver (for example, the sending unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver), and other units, such as the determination unit, can be replaced by a processor to respectively perform the transceiver operations and related determination operations in each method embodiment.

[0491] In addition, the transceiver unit 1010 may also be a transceiver circuit (for example, may include a receiving circuit and a transmitting circuit), and the processing unit 1020 may be a processing circuit.

[0492] It should be noted that the communication device 1000 in FIG10 may be a chip or a chip system, such as a system on a chip (SoC). The transceiver unit may be an input / output circuit or a communication interface, and the determination unit may be a processor, microprocessor, or integrated circuit integrated on the chip. This is not limited here.

[0493] FIG11 is a schematic diagram of a communication device provided in another embodiment of the present application.

[0494] As shown in FIG. 11 , the communication device 2000 may include a processor 2010 .

[0495] Optionally, as shown in FIG11 , the apparatus 2000 further includes a transceiver 2020, which is configured to receive and / or transmit signals. For example, the processor 2010 is configured to control the transceiver 2020 to receive and / or transmit signals. Optionally, the transceiver 2020 may include a receiver and a transmitter, the receiver being configured to receive signals and the transmitter being configured to transmit signals.

[0496] The processor 2010 can be coupled to the memory 2030, which is used to store computer programs or instructions and / or data. The processor 2010 is used to execute the computer programs or instructions stored in the memory 2030, or read the data stored in the memory 2030 to execute the methods in the above method embodiments.

[0497] Optionally, there are one or more processors 2010 .

[0498] Optionally, the memory 2030 is one or more.

[0499] Optionally, the memory 2030 is integrated with the processor 2010 or provided separately.

[0500] As an example, the processor 2010 may have the function of the processing unit 1020 shown in FIG. 10 , the memory 2030 may have the function of a storage unit, and the transceiver 2020 may have the function of the transceiver unit 1010 shown in FIG. 10 .

[0501] As a solution, the device 2000 is used to implement the operations performed by devices or network elements (such as label devices, intermediate nodes, auxiliary devices, base station devices, OAM network elements or core network elements, etc.) in the above method embodiments.

[0502] For example, the processor 2010 is used to execute the computer program or instructions stored in the memory 2030 to implement the relevant operations of the devices or network elements (such as label devices, intermediate nodes, auxiliary devices, base station devices, OAM network elements or core network elements, etc.) in the above method embodiments.

[0503] It should be understood that the processor mentioned in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0504] It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory and / or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a 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 link dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0505] 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, discrete hardware component, the memory (storage module) can be integrated into the processor.

[0506] The apparatus in FIG11 may be a device in the aforementioned embodiment, or may be a chip or chip system, such as a system on chip (SoC). The transceiver may be an input / output circuit or a communication interface; the processor may be a processor, microprocessor, or integrated circuit integrated on the chip. This is not limited here.

[0507] 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.

[0508] When the device is a chip system (or may also be called a processing system), it may include a logic circuit and an input / output interface.

[0509] The logic circuit may be a processing circuit in a chip system. The logic circuit may be coupled to a storage unit and call instructions in the storage unit so that the chip system can implement the methods and functions of each embodiment of the present application. The input / output interface may be an input / output circuit in a chip system that outputs information processed by the chip system or inputs data or signaling information to be processed into the chip system for processing.

[0510] An embodiment of the present application also provides a computer-readable storage medium on which computer program instructions are stored for implementing the methods executed by a device or network element (such as a label device, an intermediate node, an auxiliary device, a base station device, an OAM network element or a core network element, etc.) in the above-mentioned method embodiments.

[0511] For example, when the computer program instructions are executed by a computer, the computer can implement the methods performed by devices or network elements (such as label devices, intermediate nodes, auxiliary devices, base station devices, OAM network elements or core network elements, etc.) in each embodiment of the above method.

[0512] An embodiment of the present application also provides a computer program product comprising program instructions, which, when executed by a computer, implement the methods performed by a device or network element (such as a label device, an intermediate node, an auxiliary device, a base station device, an OAM network element or a core network element, etc.) in the above-mentioned method embodiments.

[0513] An embodiment of the present application also provides a communication system, which includes the label device and / or intermediate node and / or auxiliary device and / or base station device and / or OAM network element and / or core network element in the above embodiments.

[0514] The explanation of the relevant contents and beneficial effects of any of the above-mentioned devices can be referred to the corresponding method embodiments provided above, which will not be repeated here.

[0515] Those skilled in the art will appreciate that the units and algorithm steps of each example 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 performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel 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.

[0516] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0517] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0518] Units described as separate components may or may not be physically separate, and 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 these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0519] In addition, each functional unit in each embodiment of the present application may be integrated into a specific unit, each unit may exist physically separately, or two or more units may be integrated into one unit.

[0520] If the functions are implemented in the form of 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 the present application, or the part that contributes to the field, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0521] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A communication method, characterized in that: The method is applied to an intermediate node in an A-IoT system, and includes: Sending first information, where the first information is used to request authentication of the intermediate node as an excitation source of the A-IoT system, where the excitation source is used to provide a carrier to a tag in the A-IoT system; receiving second information, where the second information is used to indicate an authentication result, where the authentication result is used to indicate whether the intermediate node serves as an excitation source for the A-IoT system; The intermediate node is also used as a reader / writer in the A-IoT system to communicate with the tag.

2. The method according to claim 1, characterized in that The authentication result is used to instruct the intermediate node to serve as an excitation source of the system, and the method further includes: receiving first configuration information, where the first configuration information is used to indicate a configuration of a carrier sent by the intermediate node; Send a carrier wave to the tag according to the first configuration information.

3. The method according to claim 2, characterized in that The configuration of the carrier includes configuration information of the carrier in a single subcarrier mode and / or a multi-subcarrier mode, and the configuration information of the carrier in the multi-subcarrier mode includes at least one of the following parameters: Frequency domain position, number of subcarriers, transmit power of the carrier, guard interval time, transmit start time of the carrier, transmit end time of the carrier, transmit period of the carrier, and duration of the carrier.

4. The method according to claim 2 or 3, characterized in that The configuration of the carrier includes that the carrier sent in the multi-subcarrier mode is in a frequency hopping mode, and different single subcarriers are present in different time units in the frequency hopping mode.

5. The method according to any one of claims 1 to 4, characterized in that The first information is further used to indicate capability information of the intermediate node, where the capability information includes at least one of the following: The intermediate node supports single subcarrier and / or multi-subcarrier capabilities, the intermediate node has carrier transmission capabilities, and the intermediate node has carrier-based signal reception and / or reflected signal capabilities.

6. The method according to claim 5, characterized in that The capability information of the intermediate node includes the capability of the intermediate node to support multiple subcarriers, The carrier sent to the tag includes at least two subcarriers for uplink data transmission, and the number of the subcarriers is allocated according to the demodulation capability and remaining resources of the intermediate node.

7. The method according to claim 1, characterized in that The authentication result is used to indicate that the intermediate node does not serve as an excitation source for the system.

8. A communication method, characterized in that: The method is applied to an A-IoT system, and includes: receiving first information, and authenticating, based on the first information, an intermediate node as an excitation source of the A-IoT system, the excitation source being used to provide a carrier to a tag in the A-IoT system; Sending second information based on the first information, where the second information is used to indicate an authentication result, where the authentication result is used to indicate whether the intermediate node serves as an excitation source for the A-IoT system; The intermediate node is also used as a reader / writer in the A-IoT system to communicate with the tag.

9. The method according to claim 8, characterized in that The authentication result is used to instruct the intermediate node to serve as an excitation source of the system, and the method further includes: Sending first configuration information, where the first configuration information is used to indicate configuration of a carrier sent by the intermediate node.

10. The method according to claim 9, characterized in that The configuration of the carrier includes configuration information of the carrier in a single subcarrier mode and / or a multi-subcarrier mode, and the configuration information of the carrier in the multi-subcarrier mode includes at least one of the following parameters: Frequency domain position, number of subcarriers, transmit power of the carrier, guard interval time, transmit start time of the carrier, transmit end time of the carrier, transmit period of the carrier, and duration of the carrier.

11. The method according to claim 9 or 10, characterized in that The configuration of the carrier includes that the carrier sent in the multi-subcarrier mode is in a frequency hopping mode, and different single subcarriers are present in different time units in the frequency hopping mode.

12. The method according to any one of claims 8 to 11, characterized in that The first information is further used to indicate capability information of the intermediate node, where the capability information includes at least one of the following: The intermediate node supports single subcarrier and / or multi-subcarrier capabilities, the intermediate node has carrier transmission capabilities, and the intermediate node has carrier-based signal reception and / or reflected signal capabilities.

13. The method according to claim 12, characterized in that The capability information of the intermediate node includes a capability of the intermediate node to support multiple subcarriers, and the method further includes: Instructing the intermediate node, based on the demodulation capability and remaining resources of the intermediate node, the number of subcarriers for uplink data transmission to be sent; The number of subcarriers is included in the information indicating the configuration of the carriers.

14. The method according to claim 8, characterized in that The authentication result is used to indicate that the intermediate node does not serve as an excitation source for the system.

15. The method according to any one of claims 9 to 14, characterized in that The authentication result is used to instruct the intermediate node to serve as an excitation source of the system, and the method further includes: Sending first synchronization information to the first network element to inform the first network element that the A-IoT system uses the intermediate node as an excitation source.

16. A communication method, characterized in that: The method is applied to a network device in an A-IoT system. The system further includes an auxiliary terminal device and a tag. The auxiliary terminal device is configured to transmit a carrier wave to enable communication between the tag and the network device. The method includes: Sending second configuration information, where the second configuration information is used to instruct the auxiliary terminal device to send configuration information of a carrier supporting transmission in a multi-subcarrier mode.

17. The method according to claim 16, characterized in that The carrier configuration information includes at least one of the following parameters: Frequency domain position, number of subcarriers, transmit power of the carrier, guard interval time, transmit start time of the carrier, transmit end time of the carrier, transmit period of the carrier, and duration of the carrier.

18. The method according to claim 16 or 17, characterized in that The configuration information of the carrier also includes configuring the carrier sent in the multi-subcarrier mode to be in a frequency hopping mode, where different single subcarriers are present in different time units in the frequency hopping mode.

19. The method according to claim 17, wherein The method further comprises: Instructing the auxiliary terminal device on the number of subcarriers for uplink data transmission to be sent based on the demodulation capability and remaining resources of the auxiliary terminal device; The number of subcarriers is included in the information indicating the configuration of the carriers.

20. A communication method, characterized in that: The method is applied to an auxiliary terminal device in an A-IoT system, wherein the system further includes a network device and a tag, and the auxiliary terminal device is configured to transmit a carrier wave to enable communication between the tag and the network device. The method includes: receiving second configuration information, where the second configuration information is used to instruct the auxiliary terminal device to send configuration information of a carrier supporting transmission in a multi-subcarrier mode; Send a carrier wave to the tag according to the second configuration information.

21. The method according to claim 20, characterized in that The carrier configuration information includes at least one of the following parameters: Frequency domain position, number of subcarriers, transmit power of the carrier, guard interval time, transmit start time of the carrier, transmit end time of the carrier, transmit period of the carrier, and duration of the carrier.

22. The method according to claim 20 or 21, characterized in that The configuration information of the carrier also includes configuring the carrier sent in the multi-subcarrier mode to be in a frequency hopping mode, where different single subcarriers are present in different time units in the frequency hopping mode.

23. The method according to claim 21, characterized in that The configuration information of the carrier includes the number of the subcarriers, The carrier sent to the tag includes at least two subcarriers for uplink data transmission, and the number of the subcarriers is allocated according to the demodulation capability and remaining resources of the auxiliary terminal equipment.

24. A communication system, characterized in that: It includes a first device and a second device, wherein: The first device is used to perform the method according to any one of claims 1 to 7, The second device is configured to execute the method according to any one of claims 8 to 15.

25. A communication system, characterized in that: comprising a second device and a third device, wherein, The second device is used to perform the method according to any one of claims 16 to 19, The third device is configured to execute the method according to any one of claims 20 to 23.

26. A communication device, characterized in that: comprising a processor configured to, by executing computer programs or instructions, or by executing logic circuits, causing the communication device to perform the method according to any one of claims 1 to 7; or, causing the communication device to perform the method according to any one of claims 8 to 15; or, causing the communication device to perform the method according to any one of claims 16 to 19; or, The communication device is caused to perform the method according to any one of claims 20 to 23.

27. A computer-readable storage medium, characterized in that The computer readable storage medium stores a computer program or instruction. When the computer program or instruction is executed on a computer, causing the method of any one of claims 1 to 7 to be performed; or, causing the method of any one of claims 8 to 15 to be performed; or, causing the method of any one of claims 16 to 19 to be performed; or, Such that the method of any one of claims 20 to 23 is performed.

28. A computer program product, characterized in that Contains instructions that, when executed on a computer, causing the method of any one of claims 1 to 7 to be performed; or, causing the method of any one of claims 8 to 15 to be performed; or, causing the method of any one of claims 16 to 19 to be performed; or, Such that the method of any one of claims 20 to 23 is performed.

29. A chip system, characterized in that: The chip system includes a processor, a memory and an input / output port, wherein the memory is used to store a computer program; the processor is used to execute the computer program stored in the memory. so that the processor performs the method according to any one of claims 1 to 7; or, so that the processor performs the method according to any one of claims 8 to 15; or, so that the processor performs the method according to any one of claims 16 to 19; or so that the processor executes the method according to any one of claims 20 to 23.

Images