Communication method and apparatus

Abstract

The application provides a communication method and device, and belongs to the field of communication. When a first device reports the capability of the first device to a second device, the first capability is reported first, and after receiving a second message from the second device, the second capability is reported to the second device. The reporting of the capability information can be realized under the condition that the resource used for message scheduling by the second device is limited, the bit overhead occupied by the capability information is reduced, and thus the transmission efficiency of the capability information is improved.

Description

Technical Field

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

[0002] When a terminal device engages in passive IoT communication with the network, the network device sends a capability request message to the terminal device to request wireless access capabilities. Upon receiving the capability request message, the terminal device sends a capability message to the network device, indicating the terminal device's wireless access capabilities.

[0003] However, with the continuous development of communication technology, the content of capability messages is also increasing. Network devices may have limited resources for message scheduling due to channel quality and other reasons, which may lead to the failure of terminal devices to report capability information, or the increased bit overhead of capability information may lead to lower transmission efficiency. Summary of the Invention

[0004] This application provides a communication method and apparatus that enables terminal devices to successfully report capability information and improves transmission efficiency.

[0005] To achieve the above objectives, this application adopts the following technical solution:

[0006] Firstly, a communication method is provided. This method can be executed by a first device, for example, by the first device itself, or by a module applied to the first device (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the functions of the first device. For ease of description, the following description assumes that the method is executed by the first device. The method includes: sending a first message to a second device, the first message including information indicating a first capability of the first device; and after receiving a second message from the second device, sending a third message to the second device, the third message including information indicating a second capability of the first device.

[0007] Based on the first aspect, it is known that when the first device reports its capabilities to the second device, it first reports the first capability, and after receiving the second message from the second device, it then reports the second capability to the second device. This enables the reporting of capability information when the resources available for message scheduling on the second device are limited, thus avoiding situations where the capability is too large to be reported.

[0008] In one possible implementation, the first device is an ambient IoT (AIoT) device, and the second device is a reader.

[0009] Optionally, the priority of the first capability is higher than the priority of the second capability. The priority of the first capability can be the priority at which the first capability is transmitted / reported, and the priority of the second capability can be the priority at which the second capability is transmitted / reported. By setting the priorities of the first and second capabilities, the first device can utilize limited message resources to report higher-priority capabilities to the second device as early as possible. This segmented reporting method of capability information can reduce the bit overhead occupied by capability information and improve the transmission efficiency of capability information.

[0010] Optionally, the first message can be a message used by the first device to access the second device. The first message can be carried in a device-to-reader (D2R) message or a message added in a future protocol, without limitation. Optionally, the first message can be an existing message in the random access process, such as Msg1, or a newly added message used for access. The first message can be any possible message exchanged between the first device and the second device, and there are no restrictions on the specific message naming.

[0011] Optionally, the first message may also include first identification information, which is used to identify this random access process, such as random identifier #1.

[0012] Optionally, the first capability may be the capability of the first device for access. This access capability may be the capability related to the scheduling and / or receiving of the first device during communication between the first device and the second device. The second device can configure access parameters and / or schedule access resources based on the first capability, thus ensuring the subsequent access process.

[0013] Optionally, the third message may include upper layer data. For example, the third message may include second identification information used to identify the first device. This second identification information could be a device ID, or it could refer to the identification of the AIoT device mentioned above; there is no limitation in this regard. As another example, the third message may include responses to read commands, write commands, or deactivation / activation commands. The third message may be carried within a D2R message or a message added in a future protocol; there is no limitation in this regard. The third message can be an existing message in the random access process, such as Msg3, or a subsequent D2R message like Msg3, or a newly added message used for access; there is no limitation in this regard.

[0014] Optionally, the second capability may include the first device's access capabilities and / or its ability to transmit upper-layer data. The first device's ability to transmit upper-layer data is also related to communication between the first and second devices, and may include the ability to receive third messages, whether segmentation is supported, etc. In other words, both the second and first capabilities can include the first device's access capabilities, and the second capability may include access capabilities not reported in the first capability. For example, the first device's access capabilities include at least one capability, such as access capability #1, access capability #2, and access capability #3. The first capability includes access capability #1 and access capability #2, and the second capability includes access capability #3. The second device can configure parameters for transmitting upper-layer data and / or schedule resources for transmitting upper-layer data for the first device based on the second capability, thus ensuring the transmission of subsequent upper-layer data.

[0015] In one possible implementation, the first message and / or the third message may further include information indicating that the first device has unreported capabilities. The first device indicates this unreported capability information through explicit information in the first and / or third messages, such as adding an information bit to indicate remaining capability to be reported, for example, adding 1 bit. Alternatively, the remaining capability to be reported can be indicated by setting a special value (a third value) in the information field of the MAC subheader. By indicating the remaining unreported capability to the second device, the first device can promptly learn of the remaining unreported capability and allocate sufficient resources for sending the capability information.

[0016] Optionally, the information type or format of the carrying capacity information in the first message and / or the third message can be used to indicate whether the first device has unreported capabilities. Here, information can also be understood as signaling or an element, and information type or format can be understood as signaling type or format, or element type or format. This reduces the indication overhead of the first message.

[0017] Capability information in the first and / or third messages can be carried by different types or formats of information.

[0018] Optionally, the first message and / or the third message are MAC layer messages. The first type of information type or format can be a protocol-predefined MAC information type or format, such as truncated MAC signaling, or other signaling formats, without limitation. If the first device carries capability information using the first type of information type or format in the first message and / or the third message, it implicitly indicates that there is remaining capability to be reported. The second type of information type or format can be a protocol-predefined MAC information type or format, such as normal or full signaling, or other signaling formats, without limitation. If the first device carries capability information using the second type of information type or format in the first message and / or the third message, it implicitly indicates that the capability report is complete, or that there is no remaining capability to be reported.

[0019] In one possible implementation, the first message has K available bits. Information indicating the first capability is carried by M1 bits, information indicating the second capability is carried by M2 bits, and K bits are used to carry information indicating the first capability. Here, K, M1, and M2 are integers greater than or equal to 1, M1 is less than K, and M1 + M2 is greater than K. After the K available bits in the first message carry information indicating the higher-priority first capability, the remaining bits are insufficient to carry information indicating the lower-priority second capability. The first device needs to carry the information indicating the second capability in a subsequent third message. Alternatively, if the K available bits in the first message are insufficient to carry information indicating both the first and second capabilities, but sufficient to carry information indicating the higher-priority first capability, then the higher-priority first capability information is prioritized in the first message. This allows for capability information reporting even with limited resources for message scheduling in the second device, and reduces the bit overhead of capability information, thereby improving transmission efficiency.

[0020] Optionally, the priority of the first identification information is higher than the priority of the first device's access capability. The priority of the second identification information is higher than the priority of the first device's ability to transmit upper-layer data. The priority of the first identification information can be the priority at which the first identification information is transmitted / reported, and the priority of the second identification information can be the priority at which the second identification information is transmitted / reported.

[0021] In other words, when the first device fills in the first message, it first fills in the first identification information and then fills in the capabilities used by the first device for access; that is, it fills in both the first identification information and the first capability. When the first device fills in the third message, it first fills in the second identification information and then fills in the capabilities used by the first device for transmitting upper-layer data. Furthermore, if any of the capabilities used by the first device for access were not filled in the first message, then when the first device fills in the third message, it first fills in the second identification information and then fills in the capabilities used by the first device for access that were not filled in the first message, as well as the capabilities used by the first device for transmitting upper-layer data. In other words, when the first device fills in the third message, the second identification information has a higher priority than the capabilities used by the first device for access.

[0022] Optionally, the priority of upper-layer data is higher than the priority of the first device's ability to transmit upper-layer data. The priority of upper-layer data can be the priority of upper-layer data transmission / reporting. That is, when the first device fills in the third message, it fills in the upper-layer data first, and then fills in the first device's ability to transmit upper-layer data.

[0023] Optionally, the upper-layer data may include second identification information and other types of data, with the second identification information having a higher priority than the other types of data. That is, when the first device fills in the third message, it fills in the second identification information first and then fills in the other types of data.

[0024] In this way, by flexibly defining the priority of different content, it can be applied to different scenarios. Moreover, this method of reporting content by defining priority can achieve the reporting of capability information when the resources of the second device for message scheduling are limited, avoiding the situation where the capability is too large to be reported.

[0025] Secondly, a communication method is provided. This method can be executed by a second device, for example, by the second device itself, or by a module applied to the second device (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the functions of the second device. For ease of description, the following description assumes that the method is executed by a second device. The method includes: receiving a first message from a first device, the first message including information indicating a first capability of the first device; and after sending a second message to the first device, receiving a third message from the first device, the third message including information indicating a second capability of the first device.

[0026] In one possible implementation, the first capability has a higher priority than the second capability.

[0027] Optionally, the first capability is the capability of the first device for access, and the second message includes the parameters configured by the second device for access and / or the resources scheduled for access based on the first capability.

[0028] Optionally, the second capability includes the first device's capability for access and / or the first device's capability for transmitting upper-layer data. The method further includes: according to the second capability, performing at least one of the following: configuring parameters for access for the first device, scheduling resources for access for the first device, configuring parameters for transmitting upper-layer data for the first device, or scheduling resources for transmitting upper-layer data for the first device.

[0029] It is understood that the technical effects of the method in the second aspect mentioned above can also be referred to the relevant introduction in the first aspect mentioned above, and will not be repeated here.

[0030] Thirdly, a communication method is provided. This method can be executed by a first device, for example, by the first device itself, or by a module applied to the first device (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the functions of the first device. For ease of description, the following description assumes that the method is executed by the first device. The method includes: obtaining at least one capability index, the at least one capability index being associated with at least one capability set, the capability set including at least one capability of the first device; and sending the at least one capability index to a second device.

[0031] Based on the third aspect, it can be seen that the first device can reduce the bit overhead for indicating capability information by obtaining the association relationship between at least one capability index and at least one capability set in advance. The first device can reduce message overhead by indirectly indicating the capabilities of the first device by reporting the capability index.

[0032] Optionally, obtaining at least one capability index may include: receiving a first message from a second device, the first message including the association between multiple capability indexes and multiple capability sets, the multiple capability indexes including at least one capability index, and the multiple capability sets including at least one capability set.

[0033] Optionally, the first device is an environmental IoT (AIoT) device, and the second device is a reader.

[0034] Fourthly, a communication method is provided. This method can be executed by a second device, for example, by the second device itself, or by a module applied to the second device (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the functions of the second device. For ease of description, the following description assumes that the method is executed by a second device. The method includes: sending a first message to a first device, the first message including the association between multiple capability indices and multiple capability sets, the capability sets including the capabilities of multiple devices, and the multiple devices including the first device; receiving at least one capability index from the first device, the at least one capability index being associated with at least one capability set, the at least one capability set including at least one capability of the first device, and the multiple capability indices including at least one capability index.

[0035] It is understandable that the technical effects of the method in the fourth aspect mentioned above can also be referred to the relevant introduction in the third aspect mentioned above, and will not be repeated here.

[0036] Fifthly, a communication device is provided. The communication device includes a processor configured to perform the method according to any one of the embodiments of the first to fourth aspects.

[0037] In one possible implementation, the communication device described in the fifth aspect may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the fifth aspect and other communication devices.

[0038] In one possible implementation, the communication device described in the fifth aspect may further include a memory. This memory may be integrated with the processor or disposed separately. The memory may be used to store computer programs and / or data relating to the methods of any of the embodiments of the first to fourth aspects.

[0039] Furthermore, the technical effects of the communication device described in the fifth aspect can be referred to the technical effects of any of the embodiments in the first to fourth aspects, and will not be repeated here.

[0040] A sixth aspect provides a communication device. The communication device includes a processor coupled to a memory, the processor being configured to execute a computer program or instructions stored in the memory, causing the communication device to perform the method of any one of the embodiments of the first to fourth aspects.

[0041] In one possible implementation, the communication device may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device and other communication devices.

[0042] In one possible implementation, the communication device further includes the memory for storing the aforementioned computer program or instructions. Optionally, the memory and processor are integrated together.

[0043] Furthermore, the technical effects of the communication device described in the sixth aspect can be referred to the technical effects of any of the embodiments in the first to fourth aspects, and will not be repeated here.

[0044] A seventh aspect provides a communication system. The communication system includes: a first device for performing the method described in any embodiment of the first or third aspect, and a second device for performing any embodiment of the second or fourth aspect.

[0045] Eighthly, a computer-readable storage medium is provided, comprising: a computer program or instructions; when the computer program or instructions are executed, causing the method as described in any of the first to fourth aspects above to be implemented.

[0046] Ninth aspect, a computer program product is provided, including a computer program or instructions that, when executed, cause the method as described in any of the first to fourth aspects above to be implemented. Attached Figure Description

[0047] Figure 1 A schematic diagram of the AIoT architecture provided for embodiments of this application;

[0048] Figure 2 A schematic diagram illustrating the process of terminal device capability reporting provided in this application embodiment;

[0049] Figure 3 A schematic diagram of the architecture of a communication system to which the method provided in the embodiments of this application is applicable. Figure 1 ;

[0050] Figure 4 A schematic diagram of the architecture of a communication system to which the method provided in the embodiments of this application is applicable. Figure 2 ;

[0051] Figure 5 Flowchart of the communication method provided in the embodiments of this application Figure 1 ;

[0052] Figure 6 A schematic diagram of the fixed-bit MAC signaling format provided in the embodiments of this application;

[0053] Figure 7 Flowchart of the communication method provided in the embodiments of this application Figure 2 ;

[0054] Figure 8Schematic diagram of the communication device provided in the embodiments of this application Figure 1 ;

[0055] Figure 9 Schematic diagram of the communication device provided in the embodiments of this application Figure 2 . Detailed Implementation

[0056] The technical solutions of this application embodiment can be applied to various communication systems, such as Wi-Fi systems, vehicle-to-everything (V2X) communication systems, device-to-device (D2D) communication systems, vehicle-to-everything (V2X) communication systems, fourth-generation (4G) mobile communication systems, such as long-term evolution (LTE) systems, worldwide interoperability for microwave access (WiMAX) communication systems, fifth-generation (5G) mobile communication systems, such as new radio (NR) systems, and future communication systems.

[0057] The technical terms and related technical solutions in this application will be described below with reference to the accompanying drawings.

[0058] 1. Ambient IoT (AIoT):

[0059] With the development of communication technology, the 3rd Generation Partnership Project (3GPP) defined AIoT. AIoT is also known as ambient power-enabled IoT or passive IoT (P-IoT). AIoT can be applied to a variety of valuable scenarios.

[0060] For example, in warehousing / transportation / materials: by embedding or attaching passive or semi-passive IoT tags to goods stored in warehouses, shopping malls, etc., the relevant information of the goods is automatically collected by the reader during the logistics process. Managers can quickly query the information of the goods in the system, reducing the risk of loss or theft, improving the speed of goods handover, increasing accuracy, and preventing cross-selling and counterfeiting.

[0061] For example, fixed asset management: places with large assets or valuable items, such as libraries, art galleries and museums, need complete management procedures or rigorous protection measures. When there are abnormal changes in the storage information of books or valuable items, the system will immediately remind the administrator to handle the relevant situation.

[0062] Figure 1 This is a schematic diagram of the AIoT architecture provided in the embodiments of this application, such as... Figure 1 As shown, the architecture may include: a server, an ambient IoT function (AIoTF), a reader, an AIoT device, or an AIoT-enabled terminal.

[0063] The server can be an application function (AF), an application server (AS), or an environmental IoT / passive IoT application function (AIoT / P-IoT AF), etc., and there are no restrictions on the specific name.

[0064] AIoTF can process service requests from service requesters (AFs) and execute corresponding service operations (such as instructing the reader to perform inventory procedures for AIoT terminals) and transmit instructions (such as read operations, write operations, and deactivation operations). AIoTF can also manage IoT devices and perform security authentication processes.

[0065] AIoT devices can be categorized into three types: Device A (also known as Device 1), Device B (also known as Device 2), or Device C (also known as Device 3). Device A or Device 1a can be understood as similar to passive AIoT devices. Passive AIoT devices can be in the form of tags or any other terminal form, without restriction. Device B or Device 1b can be understood as similar to semi-passive AIoT devices. Semi-passive AIoT devices can obtain energy through solar, radio frequency, wind, hydro, or tidal power, without restriction on the energy acquisition method. These nodes do not have their own power supply devices such as batteries, but obtain energy from the environment to support data sensing, transmission, and distributed computing. Device C or Device 1c can be understood as similar to active AIoT devices. For ease of understanding, the terms "AIoT device" and "tag" can be used interchangeably. Alternatively, an AIoT device can also be considered as an AIoT terminal or tag, etc.

[0066] A reader can be an access network (RAN) device, such as a base station, pole station, micro base station, or macro station, or it can be a terminal device, such as a mobile phone, IoT device, or handheld reader. Readers can conduct contactless two-way data communication via radio frequency (RF) to read and write tags, thereby achieving target identification and data exchange. For example, for passive tags, when they enter the effective identification range of the reader, they can receive the RF signal emitted by the reader and transmit the information stored in the chip using the energy obtained from the induced current. Alternatively, for semi-passive or active tags, they can actively transmit signals at a specific frequency. The reader receives and decodes the information and sends it to the central information system for relevant data processing. Furthermore, a reader can also be called a reader-writer.

[0067] Specifically, when a server (or service requester, such as an application function (AF) or application server (AS)) operates on a tag, it can send operation instructions through the core network (CN). These instructions can include, but are not limited to: obtaining tag information, inventory operations (or storage operations), read operations, write operations, expiration operations, and interacting with the tag. Operation instructions can include area location information, tag identification information, etc. The reader sends an access instruction to the tag. After a tag successfully connects randomly, the reader sends instructions to the tag, such as forwarding the aforementioned operation instructions. The tag obtains or sends corresponding information according to the instructions. For example, when the operation instruction is an inventory instruction or an inventory operation, the tag sends its identification information; when the operation instruction is a read instruction or a read operation, the tag sends the data information stored in its storage area; when the operation instruction is a write instruction or a write operation, the tag stores the data information to be written to the tag, included in the operation instruction, in its storage area. The reader then sends (or forwards) the information sent by the tag to the core network, which in turn sends it to the server.

[0068] It should be understood that the server can send operation commands via the control plane channel. For example, the AF / AS / AIoT / P-IoT AF sends operation commands to the AIoTF (or ambient IoT management function, AIoTMF), which then sends the operation commands to the reader via the access and mobility management function (AMF). Alternatively, the AIoT / P-IoT AF sends operation commands to the AIoTMF via network function elements, which then send them to the reader. These network function elements can include, but are not limited to, network exposure functions (NEF), session management functions (SMF), policy control functions (PCF), user plane functions (UPF), unified data management functions (UDM), and network slice-specific and SNPN authentication and authorization functions (NSSAAF). Alternatively, the server can also send operation commands via the user plane channel. For example, the server sends the operation command to the reader via UPF. If the reader is a terminal device, the server also sends the operation command to the RAN device via the user plane device first, and the RAN device forwards it to the reader.

[0069] Servers or business requesters can perform different operations on AIoT devices. The following are some common business operations.

[0070] Inventory processing, or taking stock of existing AIoT devices, can also be understood as acquiring the identifiers of AIoT devices. Each AIoT device has a unique identifier. These identifiers can be assigned by the enterprise (i.e., written into the AIoT device when it's printed) or by the operator. In one possible implementation, the AIoT device identifier can be a globally unique code, such as an electronic product code (EPC), or it can be a temporary identifier or a non-globally unique identifier. During the inventory process, the server can issue inventory instructions. Typically, these instructions include information such as the AIoT device's identifier range, reader identifier, and location information. Upon receiving the inventory instruction, the reader will perform an inventory check on the AIoT devices according to the instructions and send the AIoT device identifiers to the server. Alternatively, the server can send the inventory instruction, and the reader can transmit the instruction transparently to the AIoT devices. The AIoT device recognizes the inventory operation based on the content of the inventory instruction. The AIoT device sends its identifier to the reader, and the reader sends the identifier to the server; alternatively, the AIoT device sends its identifier to the core network through the reader, and the core network then sends the identifier to the server.

[0071] A read operation refers to the process of reading data from an AIoT device. AIoT devices can have storage capabilities, and their storage areas can store data. If a server wants to perform a read operation on an AIoT device, it sends a read command. The reader or core network then performs the read operation according to the command, retrieving data from the AIoT device's storage area and sending the data back to the server.

[0072] A write operation refers to writing data to an AIoT device. The server can send a write command, and the reader or core network will then perform a write operation on the AIoT device according to the command, writing data to the AIoT device's storage area.

[0073] Deactivation is an operation that disables or deactivates AIoT devices. The server can send a deactivation command, which may include the AIoT device identifier (i.e., the identifier of the AIoT device to be deactivated or disabled). The reader or core network then performs the deactivation operation on the AIoT device according to the command. After the operation is completed, the AIoT device will be deactivated or disabled and cannot be inventoried or subjected to other operations.

[0074] Obtaining AIoT device information can be understood as a higher-level description of the various operations mentioned above (such as a higher-level description of inventory and read operations). It does not distinguish whether the server is inventorying AIoT devices or reading AIoT device data. This operation will obtain AIoT device information, which may be the identification information of the AIoT device or the information stored in the AIoT device's storage area.

[0075] The message interaction operation with AIoT devices can be understood as a higher-level description of the various operations mentioned above. After receiving instructions from the server, the reader interacts with the AIoT devices by exchanging information or messages and sends information from the AIoT devices back to the server. This operation is mainly applicable to situations where the reader does not view the content of the instructions but only forwards messages sent by the server to the AIoT devices and messages sent by the AIoT devices to the server. Therefore, in this scenario, the operations performed by the reader on the AIoT devices can be understood as message interaction operations with the AIoT devices.

[0076] 2. The process of random access for AIoT devices in AIoT:

[0077] The process for AIoT devices to randomly connect includes the following S1-S2.

[0078] S1: The AIoT device sends the first message (Msg1) to the reader, and the reader receives Msg1 accordingly.

[0079] When an AIoT device recognizes that its access time has begun, it sends a random identity (random ID) generated by the AIoT device to the reader.

[0080] S2: The reader sends the second message (Msg2) to the AIoT device, and the AIoT device receives Msg2 accordingly.

[0081] Msg2 is used in response to Msg1. If the AIoT device receives Msg2 containing the aforementioned random identifier, it considers the contention resolved successfully, and the AIoT device can then proceed with the subsequent random access process to the reader.

[0082] 3. Terminal equipment (UE) capability reporting:

[0083] After a terminal device accesses a network, it enters the connected state of radio resource control (RRC). For example, when a mobile phone is powered on, it searches for the network information of an operator and accesses a base station in the operator's network. The terminal device needs to report its capabilities to the base station and the core network so that the base station can configure it appropriately based on the capabilities supported by the terminal device. Under appropriate configuration, the terminal device can communicate with the base station.

[0084] Figure 2 This is a schematic diagram of the terminal device capability reporting process provided in the embodiments of this application, such as... Figure 2 As shown, the process may include S201-S202.

[0085] S201: The network device sends a UE Capability Enquiry message to the terminal device.

[0086] The UE capability request message is used to request the UE's radio access capability for one or more radio access technologies (RATs).

[0087] S202: The terminal device sends a UE Capability Information message to the network device.

[0088] UE capability messages are used to indicate the UE's radio access capabilities on one or more RATs. If the UE capability request message includes a certain RAT, the UE needs to include the capability information of that RAT in the UE capability message. The capability information may specifically include the features and functions supported by the UE.

[0089] The above describes the UE capability reporting scheme in NR. However, how to report the capabilities of AIoT devices in AIoT is a problem that urgently needs to be solved. Furthermore, if the AIoT device has a lot of capabilities (such as physical layer parameter-related capabilities, buffers, and other higher-level capabilities), but the reader has limited D2R resources due to channel quality and other reasons, it may be that the D2R resources cannot fill all the capability information, or the bit overhead occupied by the capability information is too large, resulting in low transmission efficiency.

[0090] To address the aforementioned technical problems, this application proposes the following technical solutions. The technical solutions in this application will now be described in conjunction with the accompanying drawings.

[0091] This application will present various aspects, embodiments, or features relating to systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that individual systems may include additional devices, components, modules, etc., and / or may not include all the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Furthermore, combinations of these approaches are also possible.

[0092] Furthermore, in the embodiments of this application, words such as "exemplarily" and "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as an "example" in this application should not be construed as being better or more advantageous than other embodiments or designs. Rather, the use of the word "example" is intended to present the concept in a specific manner.

[0093] First, in this application, "for indicating" can include both direct and indirect indication. When describing "information" for indicating A, it can include whether the information directly indicates A or indirectly indicates A, but does not necessarily mean that the information carries A.

[0094] The information indicated by a given piece of information is called the information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated, such as, but not limited to, directly indicating the information to be indicated, such as the information to be indicated itself or its index. It can also be indirectly indicated by indicating other information, where there is a relationship between the other information and the information to be indicated. It can also indicate only a part of the information to be indicated, while the other parts are known or pre-agreed upon. For example, the indication of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing the indication overhead to some extent. Simultaneously, the common parts of various pieces of information can be identified and indicated uniformly to reduce the indication overhead caused by individually indicating the same information. Furthermore, the specific indication method can also be any existing indication method, such as, but not limited to, the above-mentioned indication methods and their various combinations. Specific details of various indication methods can be found in existing technologies, and will not be elaborated upon here. As can be seen from the above, for example, when multiple pieces of information of the same type need to be indicated, the indication methods for different pieces of information may differ. In the specific implementation process, the required instruction method can be selected according to specific needs. This application embodiment does not limit the selected instruction method. Therefore, the instruction methods involved in this application embodiment should be understood to cover various methods that can enable the party to be instructed to know the information to be instructed.

[0095] The information to be indicated can be sent as a whole or divided into multiple sub-information messages, and the sending period and / or timing of these sub-information messages can be the same or different. This application does not limit the specific sending method. The sending period and / or timing of these sub-information messages can be predefined, for example, according to a protocol, or configured by the transmitting device by sending configuration information to the receiving device. This configuration information can include, for example, but not limited to, one or a combination of at least two of RRC signaling, medium access control (MAC) layer signaling, and physical layer signaling. MAC layer signaling includes, for example, a MAC control element (CE); physical (PHY) layer signaling includes, for example, downlink control information (DCI).

[0096] Second, in the embodiments shown below, the first, second, and various numerical designations are merely distinctions for descriptive convenience and are not intended to limit the scope of the embodiments of this application. For example, to distinguish different indication information.

[0097] Third, "pre-defined," "pre-configured," or "pre-specified" can be achieved by pre-saving corresponding codes, tables, or other means of indicating relevant information in the device (e.g., including terminal devices and network devices), or by pre-defining them in a protocol. This application does not limit the specific implementation method. "Saving" can refer to saving in one or more memories. These memories can be separate installations or integrated into the encoder, decoder, processor, or communication device. Alternatively, some memories can be separately installed, while others are integrated into the decoder, processor, or communication device. The type of memory can be any form of storage medium, and this application does not limit this.

[0098] Fourth, the “protocol” involved in the embodiments of this application may refer to standard protocols in the field of communication, such as 3GPP’s LTE protocols (such as technical specification (TS) 36, i.e., the TS36 series of technical specifications), NR protocols (such as the TS38 series of technical specifications), and related protocols applied to future communication systems. This application does not limit this.

[0099] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0100] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0101] To facilitate understanding of the embodiments of this application, let's first take... Figure 3 The communication system illustrated herein is used as an example to illustrate a communication system applicable to embodiments of this application. For example, Figure 3 A schematic diagram of the architecture of a communication system to which the method provided in the embodiments of this application is applicable. Figure 1 .

[0102] like Figure 3 As shown, the communication system mainly includes: a first device and a second device.

[0103] The first device can be a device capable of wirelessly connecting to a network and transmitting data, such as the AIoT device mentioned above. The device form can be a terminal, i.e., a device or module with corresponding communication functions. A terminal can also be called a terminal device, user equipment (UE), mobile station, mobile terminal, etc. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), the Internet of Things (IoT), such as the ambient internet of networks (AIoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, transportation vehicles with wireless communication capabilities, communication modules, etc. The embodiments of this application do not limit the device form of the terminal. Terminals typically contain communication modules, circuits, or chips that perform the corresponding communication functions. They may also contain program instructions configured to perform these functions.

[0104] The second device can be the reader mentioned above. The device form of the second device can be referred to the description of the reader mentioned above, and will not be repeated here.

[0105] For example, the first device has two types. Type 1 first device has an output power consumption of approximately 1 μW, has energy storage, lacks downlink and uplink signal amplification capabilities, and can only transmit information via backscatter on an externally provided carrier wave. Type 2 first device has a peak power of no more than several hundred μW, has energy storage capabilities, and can amplify downlink and / or uplink signals. Type 2 first device can generate signals internally or reflect signals via an external carrier wave.

[0106] Different application scenarios are listed based on the different types of the first device mentioned above. For example, Figure 4 A schematic diagram of the architecture of a communication system to which the method provided in the embodiments of this application is applicable. Figure 2 .like Figure 4 As shown in (a), in the application scenario of the first device of type 1 above, the base station is generally in a small-scale operating mode, and the base station communicates directly with the AIoT device. Figure 4As shown in (b), in the application scenario of the first device of type 1 above, the base station is generally located outdoors and communicates with the AIoT device through an intermediate node (such as UE) indoors.

[0107] In this communication system, when the first device reports its capabilities to the second device, it first reports the first capability, and after receiving the second message from the second device, it reports the second capability. This enables the reporting of capability information even when the second device has limited resources for message scheduling, and reduces the bit overhead of capability information, thereby improving the transmission efficiency of capability information.

[0108] It should be understood that the communication method provided in the embodiments of this application can be applied to... Figure 3 The network / entity / function shown can be specifically implemented as described in the following method embodiments, and will not be repeated here. The solutions in this application embodiment can also be applied to other communication systems, and the corresponding names can be replaced by the names of the corresponding functions in other communication systems.

[0109] It should also be understood that Figure 3 This is a simplified diagram for ease of understanding only; other devices may also be included in this communication system. Figure 3 It was not drawn in the middle.

[0110] The following will combine Figures 5-7 This application provides a detailed description of the interaction process between various networks / entities / functions in the aforementioned communication system through method embodiments. The communication method provided in this application can be applied to the aforementioned communication system, specifically involving the interaction between a first device and a second device, which will be described in detail below.

[0111] Figure 5 Flowchart of the communication method provided in this application Figure 1 ,like Figure 5 As shown, the flow of this communication method is as follows:

[0112] S501, the first device sends a first message to the second device, and correspondingly, the second device receives the first message from the first device.

[0113] The first message includes information indicating a first capability of the first device. The first message is used to report the capabilities of the first device to the second device.

[0114] Optionally, the first message is a message used by the first device to access the second device. The first message can be carried in D2R signaling or signaling added in a future protocol, without restriction. Optionally, the first message can reuse existing messages in the random access process, such as Msg1, or newly added messages used for access. The first message can be any possible message exchanged between the first device and the second device, and there are no restrictions on the specific message naming.

[0115] The first message can be MAC layer signaling, for example, Figure 6 The embodiments provided in this application are schematic diagrams of a fixed-bit MAC signaling format, such as... Figure 6 As shown, in the MAC signaling (i.e., the first message), the bits corresponding to capabilities 1, 2 and 5 in capabilities 1-6 are 1, that is, the first device indicates capability 1, capability 2 and capability 5 (i.e. the first capability) to the second device through this MAC signaling.

[0116] In the case where the first message is for the first device to access the second device, optionally, the first capability can be a capability used by the first device for access. The capability for access can be a capability related to the scheduling and / or receiving of the first device during communication between the first device and the second device.

[0117] A first capability can characterize one or more capabilities of a first device, or it can characterize one or more sets of capabilities of a first device. Each set of capabilities may include one or more capabilities.

[0118] In the embodiments of this application, the first capability may also be replaced with other possible expressions, such as a first capability set, a first capability group, etc., which are not limited here.

[0119] Optionally, the first message may also include first identification information, which is used to identify this random access procedure. For example, the first identification information may be random identifier #1. For instance, the first device generates a random identifier and encapsulates the random identifier and the first capability in the first message. Then, the first device sends it to the second device via a D2R message.

[0120] S502, after the first device receives the second message from the second device, the first device sends a third message to the second device, and correspondingly, the second device receives the third message from the first device.

[0121] The third message includes information indicating the second capability of the first device. There may be one or more third messages, without limitation.

[0122] The second message is used in response to the first message. The second message may include access parameters configured by the second device based on the first capability and / or resources scheduled for access, ensuring the subsequent access process. The second message can be carried in a reader-to-device (R2D) message or a message added in a future protocol; there are no restrictions on this. Optionally, the second message can be an existing message in the random access process, such as Msg2, or a newly added response message. The second message can be any possible message exchanged between the first and second devices; there are no restrictions on the specific message naming.

[0123] Optionally, the second message can be used to instruct the first device to continue the access process, i.e., to successfully receive Msg1 from the first device. For example, the second message may include a random identifier #2, which is the same as the random identifier #1. Optionally, the second message may also schedule D2R resources for the first device to continue sending D2R messages, such as Msg3.

[0124] The third message can be carried within a D2R message or a message added in a future protocol; there are no restrictions on this. The third message can be an existing message in the random access process, such as Msg3, or a subsequent D2R message like Msg3, or a newly added message used for access; there are no restrictions on this.

[0125] Optionally, the third message may include upper-layer data. For example, the third message may include second identification information used to identify the first device. For instance, the second identification information may be a device ID, or it may refer to the identification of the AIoT device mentioned above, without limitation. As another example, the third message may include responses to read commands, write commands, and deactivation / activation commands.

[0126] Optionally, the second capability includes the first device's ability to access and / or the first device's ability to transmit upper-layer data.

[0127] In other words, both the second capability and the first capability can include the access capabilities of the first device, and the second capability can include access capabilities that were not reported in the first capability. For example, the access capabilities of the first device include at least one capability, such as access capability #1, access capability #2, and access capability #3. The first capability includes access capability #1 and access capability #2, and the second capability includes access capability #3.

[0128] The first device's ability to transmit upper-layer data, that is, its ability to communicate with the second device, may include the ability to receive third messages and whether it supports segmentation, etc.

[0129] The second capability can represent one or more capabilities of the first device, or it can represent a collection of one or more capabilities of the first device. The second capability can also be replaced by other possible expressions, such as a set of second capabilities, a group of second capabilities, etc., which are not limited here.

[0130] Optionally, the second device performs at least one of the following actions based on the second capability: configuring parameters for access of the first device, scheduling resources for access of the first device, configuring parameters for transmitting upper-layer data of the first device, or scheduling resources for transmitting upper-layer data of the first device. This ensures the transmission of subsequent upper-layer data.

[0131] In this way, when the first device reports its capabilities to the second device, it first reports the first capability, and after receiving the second message from the second device, it reports the second capability to the second device. This enables the reporting of capability information when the resources available for message scheduling on the second device are limited, and avoids the situation where the capability is too large to be reported.

[0132] The following describes how the first device determines the content filled in each D2R message, specifically including Method 1 and Method 2.

[0133] Method 1: Determine the content to be filled in the D2R message based on the priority of the content to be filled in.

[0134] In one possible implementation, the first capability has a higher priority than the second capability.

[0135] The priority of the first capability can be the priority at which the first capability is transmitted / reported, and the priority of the second capability can be the priority at which the second capability is transmitted / reported.

[0136] In one possible implementation, the first message has K padding (available) bits. Information indicating a higher-priority first capability is carried by M1 bits, information indicating a lower-priority second capability is carried by M2 bits, and K bits are used to carry information indicating the first capability. Here, K, M1, and M2 are integers greater than or equal to 1, M1 is less than K, and M1 + M2 is greater than K.

[0137] In other words, after the first message has enough padding (available) K bits to carry information indicating a higher-priority first capability, the remaining bits are insufficient to carry information indicating a lower-priority second capability. Therefore, the first device needs to carry the information indicating the second capability in a subsequent third message. Alternatively, if the first message has enough padding (available) K bits to carry both information indicating the first and second capabilities, but can carry information indicating the higher-priority first capability, then the higher-priority first capability information will be carried in the first message first.

[0138] For example, assume that capability #1 of the first device has a higher priority than capability #2. After filling capability #1 in the D2R message #1 (i.e., the first message mentioned above) sent by the first device to the second device, if there are still resources, capability #2 can be filled in. That is, the higher-priority capability is filled in the D2R message #1 first, and if there are still resources, the next higher-priority capability is filled in. If there are no resources in the D2R message #1 after filling capability #1, or if there are not enough resources to fill capability #2, capability #2 can be filled in the D2R message #2 (i.e., the third message mentioned above) after receiving a message from the second device (i.e., the second message mentioned above). It can be understood that if some capabilities have the same priority, the capabilities filled in the D2R message #1 and D2R message #2 can be determined by the rules predefined by the first device.

[0139] In addition, other content in the D2R message can also be configured to have a priority for filling / transmitting, and be prioritized together with the capabilities of the first device (such as the capabilities for access and the capabilities for transmitting upper-layer data mentioned above). The relationship between the priorities of other content and capabilities is illustrated below as an example.

[0140] Optionally, the priority of the first identification information is higher than the priority of the first device's access capability. The priority of the second identification information is higher than the priority of the first device's ability to transmit upper-layer data. The priority of the first identification information can be the priority at which the first identification information is transmitted / reported, and the priority of the second identification information can be the priority at which the second identification information is transmitted / reported.

[0141] In other words, when the first device fills in the first message, it first fills in the first identification information and then fills in the capabilities used by the first device for access; that is, it fills in both the first identification information and the first capability. When the first device fills in the third message, it first fills in the second identification information and then fills in the capabilities used by the first device for transmitting upper-layer data. Furthermore, if any of the capabilities used by the first device for access were not filled in the first message, then when the first device fills in the third message, it first fills in the second identification information and then fills in the capabilities used by the first device for access that were not filled in the first message, as well as the capabilities used by the first device for transmitting upper-layer data. In other words, when the first device fills in the third message, the second identification information has a higher priority than the capabilities used by the first device for access.

[0142] For example, the first device's access capabilities include capabilities #1 and #2. The first device's ability to transmit upper-layer data includes capability #3. The priorities, from highest to lowest, are: capability #1, capability #2, capability #3. A random identifier (i.e., the aforementioned first identifier information) is filled into the D2R message #1 (i.e., the first message mentioned above) sent by the first device to the second device. If resources are still available, the access capabilities of the first device can continue to be filled. After filling capability #1, if the resources in D2R message #1 are insufficient to fill capability #2, then after receiving a message from the second device (i.e., the aforementioned second message), a device identifier (i.e., the aforementioned second identifier information) can be filled into D2R message #2 (i.e., the aforementioned third message). If resources are available in D2R message #2, capabilities #2 and #3 can continue to be filled. It can be understood that if, after filling capability #2 in D2R message #2, the remaining resources are insufficient to fill capability #3, then capability #3 is filled through D2R message #3 (i.e., the aforementioned third message). That is, the third message can be multiple subsequent D2R messages.

[0143] Optionally, the priority of upper-layer data is higher than the priority of the first device's ability to transmit upper-layer data. The priority of upper-layer data can be the priority of upper-layer data transmission / reporting. That is, when filling in the third message, the first device fills in the upper-layer data first, then fills in the first device's ability to transmit upper-layer data. Optionally, the upper-layer data may include second identification information and other types of data, with the second identification information having a higher priority than the other types of data. That is, when filling in the third message, the first device fills in the second identification information first, then fills in the other types of data.

[0144] Optionally, different data types among the aforementioned other data types may have different priorities, and at least one of the following can be prioritized together: first identification information, second identification information, different types of data, first capability, second capability. For example, the contents of the first message and the third message may be sorted separately, with the priority of the contents of the first message from high to low as: first identification information, first capability. The priority of the contents of the first message from high to low as: second identification information, different types of data, second capability. Alternatively, the contents of the first message and the third message may be sorted together, with the priority from high to low as: first identification information, second identification information, first capability, different types of data, second capability.

[0145] The priority of filling the third message can be used in combination. For example, when filling the third message, the first device first fills the second identification information, then the upper-layer data, and finally the capability of the first device to transmit upper-layer data. Alternatively, the first device may fill the third message in the following order: second identification information, the capability of the first device to transmit upper-layer data, and upper-layer data. Another example is that the first device may fill the third message in the following order: second identification information, the capability of the first device for access, upper-layer data, and the capability of the first device for transmitting upper-layer data. Yet another example is that the first device may fill the third message in the following order: second identification information, the capability of the first device for access, the capability of the first device for transmitting upper-layer data, and upper-layer data. Finally, the first device may fill the third message in the following order: second identification information, upper-layer data 1, the capability of the first device for transmitting upper-layer data, and upper-layer data 2.

[0146] In one possible implementation, the priorities of the various contents filled in the D2R messages (e.g., the first and third messages) are defined in a predefined manner according to the protocol. Alternatively, the second device can determine the priorities of the various contents filled in the D2R messages (e.g., the first and third messages) and send them to the first device. For example, the first device receives configuration information from the second device, which indicates at least one of the following: the priority of a first capability, the priority of a second capability, the priority of first identification information, the priority of second identification information, and the priority of upper-layer data. Optionally, the paging message carries this configuration information.

[0147] It should be noted that the above definition of priority is only an example, and there are other possible definition methods, which are not specifically limited in this application embodiment.

[0148] Method 2: Determine the content to be filled in the first message and / or the third message according to predefined rules.

[0149] In one possible implementation, the content to be filled in the first message and / or the third message is predefined. The size of the resources scheduled for the first message and / or the third message is predefined, so that when the second device schedules the first message and / or the third message, it can schedule enough resources to allow the first device to fill in the predefined content. For example, the first capability is predefined as being contained in the first message, and the second capability is contained in the third message.

[0150] Optionally, a minimum amount of resources can be predefined for the first and / or third message scheduling.

[0151] For example, the first message needs to include a random identifier and capability set 1 (i.e., the first capability mentioned above), and the minimum amount of resources scheduled for the first message is the resource size required for the random identifier and capability set 1. The third message needs to include a device identifier and capability set 2 (i.e., the second capability mentioned above), and the minimum amount of resources scheduled for the third message is the resource size required for the device identifier and capability set 2.

[0152] In this embodiment, methods 1 and 2 can be used in combination. For example, the content #1 to be filled in the first message and the content #2 to be filled in the third message are predefined. No priority needs to be defined for content #1 and content #2. Content #3, excluding content #1 and content #2, needs to have its priority defined. After the first message contains content #1, if resources are still available, such as remaining padding bits, the first message can be filled according to the priority order of content #3. The third message follows the same principle and will not be elaborated further. Content #1, content #2, or content #3 may include the aforementioned first identification information, second identification information, first capability, second capability, upper-layer data, and other possible data or capability information, without limitation.

[0153] In one possible implementation, the first device can record which capabilities have been reported. When reporting capabilities subsequently, it can report based on this record. For example, if the first device records the first capability reported in the first message, when reporting capabilities via the third message, it can determine the next capability to be reported based on priority. Optionally, the first device can also report based on instructions from the second device, such as the second device instructing the first device on which capabilities to start reporting from, or the second device instructing the first device on which capabilities have already been reported.

[0154] The following describes several implementations of how the first device indicates the remaining unreported capabilities to the second device in D2R messages (e.g., the first message and the third message).

[0155] In one possible implementation, the first message and / or the third message may also include information indicating that the first device has an unreported capability.

[0156] The first device indicates that it has unreported capabilities through explicit information in the first message and / or the third message. For example, it can add information bits to indicate that there is remaining capability to be reported, such as adding 1 information indication bit. Alternatively, it can indicate that there is remaining capability to be reported by setting the information field in the MAC subheader to a special value (the third value). By indicating the remaining unreported capability to the second device, the first device can promptly learn that there is remaining unreported capability and thus allocate sufficient resources for sending capability information.

[0157] In another possible implementation, the first device may have unreported capability information indicated by the information type or information format of the capability information carried in the first message and / or the third message. Here, information can also be understood as signaling or element, and information type or information format can be understood as signaling type or signaling format, or element type or element format.

[0158] Capability information in the first and / or third messages can be carried by different types or formats of information.

[0159] Optionally, the first message and / or the third message are MAC layer messages. The first type of information type or format can be a predefined MAC information type or format, such as truncated MAC signaling, or other signaling formats, without limitation. If the first device carries capability information in the first message and / or the third message using the first type of information type or format, it implicitly indicates that there is remaining capability to be reported.

[0160] The second type of information or information format can be a predefined MAC information type or information format, such as normal or full signaling, or other signaling formats, without limitation. If the first device carries capability information through the second type of information or information format in the first message and / or the third message, it implicitly indicates that the capability report is complete, or that there is no remaining capability to be reported.

[0161] Optionally, different information types or formats can be distinguished by information fields in the MAC subheader.

[0162] In another possible implementation, the first device does not indicate the existence of remaining unreported capabilities. The second device pre-configures the bits (i.e., resource occupancy) corresponding to the capabilities that the first device needs to report. If the bits corresponding to the content received by the second device are inconsistent with the bits corresponding to the capabilities that the first device needs to report, i.e., the second device has not received complete content, then the second device can determine that the first device has remaining capabilities that need to be reported. Alternatively, the second device can interpret the capabilities that the first device has not reported as "not supported," "default capability (which can be predefined in the protocol)," or "mandatory capability (which can be predefined in the protocol)."

[0163] Figure 7 Flowchart of the communication method provided in this application Figure 2 ,like Figure 7 As shown, the flow of this communication method is as follows:

[0164] S701, the first device acquires at least one capability index.

[0165] In this context, at least one capability index is associated with at least one capability set, which includes at least one capability of the first device.

[0166] At least one capability index may correspond to a capability set, and each capability set may include one or more capabilities of the first device.

[0167] The capabilities of the first device can be found in the descriptions of the first capability in S501 and the second capability in S502, and will not be elaborated upon further.

[0168] In this embodiment of the application, the capability index can be replaced with other possible expressions, such as capability identifiers, without limitation.

[0169] The following describes two implementations of the first device acquiring at least one capability index.

[0170] In one possible implementation, the second device sends a first message to the first device, and correspondingly, the first device receives the first message from the second device. The first message includes associations between multiple capability indices and multiple capability sets, wherein the multiple capability indices include at least one capability index, and the multiple capability sets include at least one capability set.

[0171] Optionally, the first message can be RRC signaling, MAC layer signaling, or physical layer signaling, without restriction.

[0172] Optionally, the first message can be an R2D message, such as a message used by a second device to page a first device.

[0173] Optionally, the first message is a broadcast message.

[0174] In the association between multiple capability indexes and multiple capability sets, each capability index can correspond to a capability set.

[0175] It is understandable that, considering that the second device may not support some functions, the multiple capability sets in the association provided by the second device can be filtered capability sets, that is, the capabilities contained in the multiple capability sets in the association are all capabilities supported by the second device.

[0176] In another possible implementation, the first device and the second device pre-configure the association between multiple capability indexes and multiple capability sets of the first device, wherein the multiple capability indexes include at least one capability index and the multiple capability sets include at least one capability set.

[0177] S702, the first device sends at least one capability index to the second device, and correspondingly, the second device receives at least one capability index from the first device.

[0178] The second device can determine at least one capability corresponding to at least one capability index based on at least one capability index received from the first device and the aforementioned association relationship.

[0179] Thus, by obtaining the association between at least one capability index and at least one capability set in advance, the first device can reduce the bit overhead used to indicate capability information. The first device can indirectly indicate its capabilities by reporting capability indexes, which can reduce signaling overhead.

[0180] The various implementations of the above embodiments can be used individually or in combination. For example, if the first device is not pre-configured to report in the form of a capability index, or has not obtained the association between the capability index and the capability set, and therefore cannot report via the capability index, the first device can use... Figure 5 The corresponding implementation method directly reports the specific first capability and second capability.

[0181] The above combination Figures 5-7 The communication method provided in the embodiments of this application is described in detail below. Figure 8 and Figure 9 This document describes in detail the communication apparatus used to perform the communication method provided in the embodiments of this application.

[0182] For example, Figure 8 This is a schematic diagram of the structure of the communication device provided in the embodiments of this application. Figure 1 .like Figure 8 As shown, the communication device 800 includes a processing module 801 and a transceiver module 802. For ease of explanation, Figure 8 Only the main components of the communication device are shown.

[0183] In some embodiments, the communication device 800 may be adapted to Figure 3 In the communication system shown, the execution Figure 5 or Figure 7 The function of the first device in the communication method shown.

[0184] The transceiver module 802 is used to perform the transceiver functions of the first device.

[0185] The processing module 801 is used to perform functions of the first device other than the transmit and receive functions.

[0186] Optionally, the communication device 800 may also include a storage module. Figure 8 (Not shown in the image), this storage module stores programs or instructions. When the processing module 801 executes the program or instructions, it enables the communication device 800 to perform... Figure 5 or Figure 7 The function of the first device in the communication method shown.

[0187] It should be understood that the processing module 801 involved in the communication device 800 can be implemented by a processor or processor-related circuit components, and can be a processor or processing unit; the transceiver module 802 can be implemented by a transceiver or transceiver-related circuit components, and can be a transceiver or transceiver unit.

[0188] Furthermore, the communication device 800 can be an AIoT device, a chip (system) or other component or assembly disposed within an AIoT device, or a device containing the AIoT device; this application embodiment does not limit this. The technical effects of the communication device 800 can be referred to separately. Figure 5 or Figure 7 The technical effects of any of the communication methods shown in the examples are not elaborated here.

[0189] In other embodiments, the communication device 800 may be adapted to Figure 3 In the communication system shown, the execution Figure 5 or Figure 7 The function of the second device in the communication method shown.

[0190] The transceiver module 802 is used to perform the transceiver functions of the second device.

[0191] The processing module 801 is used to perform functions of the second device other than the transmit and receive functions.

[0192] Optionally, the communication device 800 may also include a storage module. Figure 8 (Not shown in the image), this storage module stores programs or instructions. When the processing module 801 executes the program or instructions, it enables the communication device 800 to perform... Figure 5 or Figure 7 The function of the second device in the communication method shown.

[0193] It should be understood that the processing module 801 involved in the communication device 800 can be implemented by a processor or processor-related circuit components, and can be a processor or processing unit; the transceiver module 802 can be implemented by a transceiver or transceiver-related circuit components, and can be a transceiver or transceiver unit.

[0194] Furthermore, the communication device 800 can be a reader, a chip (system) or other component or assembly disposed in the reader, or a device containing the reader; this application embodiment does not limit this. The technical effects of the communication device 800 can be referred to separately. Figure 5 or Figure 7 The technical effects of any of the communication methods shown in the examples are not elaborated here.

[0195] Figure 9 Schematic diagram of the communication device provided in the embodiments of this application Figure 2For example, the communication device can be a terminal, or a chip (system) or other component or assembly that can be set in the terminal. Figure 9 As shown, the communication device 900 may include a processor 901. Optionally, the communication device 900 may also include a memory 902 and / or a transceiver 903. The processor 901 is coupled to the memory 902 and the transceiver 903, for example, they can be connected via a communication bus.

[0196] The following is combined Figure 9 A detailed description of each component of the communication device 900 is provided below:

[0197] The processor 901 is the control center of the communication device 900. It can be a single processor or a collective term for multiple processing elements. For example, the processor 901 can be one or more central processing units (CPUs), application-specific integrated circuits (ASICs), or one or more integrated circuits configured to implement the embodiments of this application, such as one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs).

[0198] Optionally, the processor 901 can perform various functions of the communication device 900 by running or executing software programs stored in the memory 902 and calling data stored in the memory 902, such as performing the aforementioned functions. Figure 5 or Figure 7 The communication method shown.

[0199] In a specific implementation, as one example, the processor 901 may include one or more CPUs, for example... Figure 9 CPU0 and CPU1 are shown in the diagram.

[0200] In a specific implementation, as one example, the communication device 900 may also include multiple processors, for example... Figure 9 The processors 901 and 904 are shown. Each of these processors can be a single-core processor or a multi-core processor. Here, "processor" can refer to one or more devices, circuits, and / or processing cores used to process data (e.g., computer program instructions).

[0201] The memory 902 is used to store the software program that executes the solution of this application, and is controlled by the processor 901 to execute it. The specific implementation method can be referred to the above method embodiment, and will not be repeated here.

[0202] Optionally, the memory 902 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory 902 may be integrated with the processor 901 or exist independently, and may be connected via the interface circuit of the communication device 900. Figure 9 (Not shown in the image) is coupled to the processor 901, but this embodiment does not specifically limit this.

[0203] Transceiver 903 is used for communication with other communication devices. For example, if communication device 900 is a terminal, transceiver 903 can be used to communicate with a network device or with another terminal device. As another example, if communication device 900 is a network device, transceiver 903 can be used to communicate with a terminal or with another network device.

[0204] Alternatively, transceiver 903 may include a receiver and a transmitter. Figure 9 (Not shown separately). The receiver is used to implement the receiving function, and the transmitter is used to implement the sending function.

[0205] Optionally, the transceiver 903 can be integrated with the processor 901, or it can exist independently and be connected via the interface circuit of the communication device 900. Figure 9 (Not shown in the image) is coupled to the processor 901, but this embodiment does not specifically limit this.

[0206] Understandable Figure 9 The structure of the communication device 900 shown does not constitute a limitation on the communication device. Actual communication devices may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0207] Furthermore, the technical effects of the communication device 900 can be referred to the technical effects of the method described in the above method embodiments, and will not be repeated here.

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

[0209] It should also be understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous DRAM (DDR SDRAM), enhanced synchronous DRAM (ESDRAM), synchronous linked DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0210] The above embodiments can be implemented, in whole or in part, by software, hardware (such as circuits), firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more sets of available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. A semiconductor medium can be a solid-state drive.

[0211] It should be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. A and B can be singular or plural. Additionally, the character " / " in this article generally indicates an "or" relationship between the preceding and following related objects, but it can also represent an "and / or" relationship. Please refer to the context for a more accurate understanding.

[0212] In this application, "at least one" means one or more, and "more than one" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0213] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

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

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

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

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

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

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

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

Claims

1. A communication method, characterized in that, Applied to the first device, including: Send a first message to the second device, the first message including information indicating a first capability of the first device; After receiving a second message from the second device, a third message is sent to the second device, the third message including information indicating a second capability of the first device.

2. The method according to claim 1, characterized in that, The first device is an environmental IoT (AIOT) device, and the second device is a reader.

3. The method according to claim 1 or 2, characterized in that, The first capability has a higher priority than the second capability.

4. The method according to any one of claims 1 to 3, characterized in that, The first message is a message used by the first device to access the second device.

5. The method according to claim 4, characterized in that, The first capability is the capability that the first device uses for access.

6. The method according to any one of claims 1 to 5, characterized in that, The third message includes upper-layer data.

7. The method according to claim 6, characterized in that, The second capability includes the first device's ability to access, and / or the first device's ability to transmit the upper-layer data.

8. The method according to any one of claims 1 to 7, characterized in that, The first message and / or the third message also include information indicating that the first device has an unreported capability.

9. The method according to claim 8, characterized in that, The information indicating that the first device has an unreported capability is indicated by the type of the first message and / or the third message.

10. The method according to claim 9, characterized in that, The first message and / or the third message are of type 1 MAC message.

11. The method according to any one of claims 1 to 10, characterized in that, The first message has K fillable bits. Information indicating the first capability needs to be carried by M1 bits, and information indicating the second capability needs to be carried by M2 bits. The K bits are used to carry information indicating the first capability. Wherein, K, M1, and M2 are integers greater than or equal to 1, M1 is less than K, and M1+M2 is greater than K.

12. A communication method, characterized in that, Applied to a second device, including: Receive a first message from a first device, the first message including information indicating a first capability of the first device; After sending a second message to the first device, a third message is received from the first device, the third message including information indicating a second capability of the first device.

13. The method according to claim 12, characterized in that, The first capability has a higher priority than the second capability.

14. The method according to claim 12 or 13, characterized in that, The first capability is the capability of the first device for access, and the second message includes the parameters configured by the second device for access and / or the resources scheduled for access based on the first capability.

15. The method according to any one of claims 12 to 14, characterized in that, The second capability includes the first device's ability to access and / or the first device's ability to transmit upper-layer data, and the method further includes: Based on the second capability, perform at least one of the following: configure parameters for access for the first device, schedule resources for access for the first device, configure parameters for transmitting upper-layer data for the first device, or schedule resources for transmitting upper-layer data for the first device.

16. A communication method, characterized in that, Applied to the first device, including: Obtain at least one capability index, which is associated with at least one capability set, the capability set including at least one capability of the first device; Send the at least one capability index to the second device.

17. The method according to claim 16, characterized in that, The acquisition of at least one capability index includes: The device receives a first message from the second device, the first message including the association between multiple capability indexes and multiple capability sets, the multiple capability indexes including the at least one capability index, and the multiple capability sets including the at least one capability set.

18. The method according to claim 16 or 17, characterized in that, The first device is an environmental IoT (AIOT) device, and the second device is a reader.

19. A communication method, characterized in that, Applied to a second device, including: Send a first message to a first device, the first message including the association between multiple capability indexes and multiple capability sets, the capability sets including the capabilities of multiple devices, the multiple devices including the first device; Receive at least one capability index from the first device, the at least one capability index being associated with at least one capability set, the at least one capability set including at least one capability of the first device, and the plurality of capability indexes including the at least one capability index.

20. A communication device, characterized in that, The apparatus includes: a module for performing the method as described in any one of claims 1-11, or a module for performing the method as described in any one of claims 12-15, or a module for performing the method as described in any one of claims 16-18, or a module for performing the method as described in claim 19.

21. A communication device, characterized in that, The communication device includes a processing unit and a storage unit; the storage unit is used to store computer instructions, which, when executed by the processing unit, cause the method as described in any one of claims 1-11 to be executed, or cause the method as described in any one of claims 12-15 to be executed, or cause the method as described in any one of claims 16-18 to be executed, or cause the method as described in claim 19 to be executed.

22. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a computer program or instructions that, when executed on a computer, cause the computer to perform the method as claimed in any one of claims 1-11, or the method as claimed in any one of claims 12-15, or the method as claimed in any one of claims 16-18, or the method as claimed in claim 19.

23. A computer program product, characterized in that, The computer program product includes a computer program or instructions that, when executed on a computer, cause the method as described in any one of claims 1-11 to be performed, or the method as described in any one of claims 12-15 to be performed, or the method as described in any one of claims 16-18 to be performed, or the method as described in claim 19 to be performed.

Images