Communication method and apparatus

Abstract

The present application belongs to the technical field of communications. Provided are a communication method and apparatus. The method comprises: sending first information, and receiving a first identifier of a first terminal, wherein the first information comprises at least one of M identifier lengths or N length intervals, M and N being positive integers, and the length of the first identifier and a first identifier length among the M identifier lengths satisfy a preset rule, and / or the length of the first identifier is located within a first length interval among the N length intervals.

Description

Communication method and apparatus

[0001] The present application claims priority from the Chinese patent application No. 202411098230.6 filed on August 9, 2024, and entitled "A communication method and apparatus", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] The present application relates to the field of communication technology, and in particular to a communication method and apparatus. BACKGROUND

[0003] With the development of communication technology, the 3rd generation partnership project (3GPP) defines ambient IoT (A-IoT). A-IoT terminals communicate with the network by harvesting energy from the environment to implement business processes in various scenarios, such as warehouse / transportation / material inventory, fixed asset management, etc. In these business processes, A-IoT terminals need to send their own device identifiers to the reader. Due to the diversity of A-IoT business scenarios, device identifiers can be diverse.

[0004] For diverse device identifiers, how to ensure the efficiency of business processes is a current research problem. SUMMARY

[0005] To solve the above technical problems, the embodiments of the present application provide a communication method and apparatus to implement, for device identifiers of different lengths, that the network side can still ensure the efficiency of business processes.

[0006] To achieve the above object, the present application adopts the following technical solutions:

[0007] In a first aspect, a communication method is provided. The method is applied to a first network entity. The method includes: sending first information and receiving a first identifier of a first terminal. The first information includes M identifier lengths and / or N length intervals, M and N are positive integers; the length of the first identifier meets a preset rule with a first identifier length in the M identifier lengths, and / or the length of the first identifier is located in a first length interval in the N length intervals.

[0008] Therefore, the first network entity can specify the identity length and / or the length interval by sending the first information. If the first terminal determines, after receiving the first information, that the length of the device identity of the first terminal meets the preset rule and / or is located in the length interval, the first terminal can report the device identity of the first terminal, such as the first identity, otherwise, the first terminal does not report, to realize batch and orderly reporting, so that the network side can still ensure the efficiency of the business process for device identities of different lengths.

[0009] In a possible design, the length of the first identity and the first identity length meet the preset rule includes that the length of the first identity is the same as the first identity length, or the first identity is determined according to the second identity of the first terminal, and the length of the second identity is the same as the first identity length. That is, the first identity can be an identity directly reported by the first terminal, or can be an identity reported after processing, which can be selected flexibly according to implementation. For example, if the types of identity lengths are less, the network can select the direct reporting mode, otherwise, the network can select the reporting mode after processing, such as processing to the same length and then reporting.

[0010] Optionally, the first information further includes a reporting length, and in the case that the first identity is determined according to the second identity, the length of the first identity is the same as the reporting length, such as the second identity can be truncated or padded to the reporting length, so as to obtain the first identity. In this way, identities of different lengths can be processed to the same length and then reported, to improve the execution efficiency of the business process.

[0011] In a possible design, the M identity lengths include K types of identity lengths, or the M identity lengths include the same length and / or different lengths, and there are K types of lengths, and K is a positive integer. For example, the M identity lengths are 3, the first identity length is L1, the second identity length is L2, and the third identity length is L2, and the three identity lengths include two types of identity lengths L1 and L2. The K types of identity lengths belong to L types of identity lengths, L is an integer greater than or equal to K, and the first network entity can select K types of identity lengths from the L types of identity lengths as the lengths required to be met by the identities reported this time according to actual needs. For example, if the types of identity lengths are more, that is, L is larger, the first network entity can select identity lengths of part of the types as the lengths required to be met by the identities reported this time each time, that is, batch reporting, to reduce the cost of each reporting, and vice versa. The first network entity can select identity lengths of all types as the lengths required to be met by the identities reported this time at a time, that is, one-time reporting, to reduce the overall delay of the business process.

[0012] Optionally, the method of the first aspect can further comprise receiving a service request from a second network entity, and determining the L identity lengths according to the service request. The second network entity is a requester of the first service, and the service request can indicate that the first service is to be performed on terminals satisfying a preset condition, and the first terminals are the terminals satisfying the preset condition. The determination of the L identity lengths can be triggered by the service request, so as to achieve on-demand determination according to service requirements.

[0013] Further, the third network entity is preconfigured with the L identity lengths, and the determination of the L identity lengths according to the service request comprises: obtaining the L identity lengths from the third network entity according to the service request. In this case, the service request can not contain the L identity lengths, so as to reduce signaling overhead. Alternatively, the service request can contain the L identity lengths, and the determination of the L identity lengths according to the service request comprises: obtaining the L identity lengths from the service request, so as to reduce the interaction overhead between network elements / entities.

[0014] Further, the terminals satisfying the preset condition can include at least one of the following: terminals located in an indicated area, or terminals identified as an identity type. In this case, the first network entity does not determine whether the identities of these terminals are all of the same identity length, and thus the L identity lengths can be determined accordingly.

[0015] Further, the first service can be an environmental Internet of Things (A-IoT) service, or any other possible service, without limitation.

[0016] Optionally, the L identity lengths can also be the default identity lengths of the first network entity. That is, the first network entity can be preconfigured or protocol-predefined with the L identity lengths, without the need to obtain them from signaling or other network elements / entities, so as to further reduce overhead.

[0017] In a possible design, the first information is carried in a mask, that is, the first information is delivered by multiplexing an existing information element, so as to reduce implementation difficulty, or the first information can also be delivered independently and decoupled from the existing information element, so as to achieve more flexible information delivery.

[0018] Optionally, the mask includes an identity type, and the type of the first identity matches the identity type included in the mask. For example, the identity type can be any one of the following: an identity allocated by an operator network, an identity allocated by a non-operator network, a product electronic identity, or a non-product electronic identity, so as to achieve ordered reporting according to length and type.

[0019] In a possible design, the method of the first aspect can further comprise sending second information, the second information including P identity lengths and / or Q length intervals, P and Q being positive integers, the P identity lengths being different from the M identity lengths, and the Q length intervals being different from the N length intervals, so as to achieve batch reporting.

[0020] Optionally, the first information and the second information can be carried in the same message. For example, the first network entity is an A-IoTMF, the A-IoTMF can send a message containing the first information and the second information to the access network device, and the access network device can send the first information and the second information in batches, for example, the first information and the second information are sent in different random access procedures. Alternatively, the first information and the second information can also be carried in different messages. For example, the first network entity is an A-IoTMF, the A-IoTMF can send the first information and the second information to the access network device through different messages, and the access network device can directly forward the first information and the second information to the corresponding A-IoT terminal.

[0021] In a possible design, the first network entity supports the reader function, and the first terminal is an A-IoT terminal.

[0022] In a second aspect, a communication method is provided. The method is applied to a first terminal or a chip in the first terminal. Taking the application to the first terminal as an example, the method includes: receiving first information, and sending a first identifier of the first terminal according to the first information. The first information includes M identifier lengths and / or N length intervals, M and N are positive integers; the length of the first identifier meets a preset rule with a first identifier length in the M identifier lengths, and / or the length of the first identifier is located in a first length interval in the N length intervals.

[0023] In a possible design, the length of the first identifier meets the preset rule with the first identifier length includes: the length of the first identifier is the same as the first identifier length, or the first identifier is determined according to a second identifier of the first terminal, and the length of the second identifier is the same as the first identifier length.

[0024] Optionally, the first information further includes a reporting length, and in the case that the first identifier is determined according to the second identifier, the length of the first identifier is the same as the reporting length.

[0025] In a possible design, the method in the second aspect further includes: if the length of the second identifier is greater than the reporting length, the second identifier is truncated to the reporting length to obtain the first identifier; if the length of the second identifier is less than the reporting length, the second identifier is padded to the reporting length to obtain the first identifier; and if the length of the second identifier is equal to the reporting length, the second identifier and the first identifier are the same identifier.

[0026] In a possible design, the receiving of the first information includes: receiving a mask, and the first information is carried in the mask.

[0027] Optionally, the mask includes an identifier type, and the type of the first identifier matches the identifier type included in the mask.

[0028] Further, the identification type is any one of: an operator network assigned identification, a non-operator network assigned identification, a product electronic identification, or a non-product electronic identification.

[0029] In a possible design, the first terminal is an environmental Internet of Things (A-IoT) terminal.

[0030] It can be understood that the technical effects of the method in the second aspect can also be referred to the related description of the method in the first aspect, and details are not repeated.

[0031] In a third aspect, a communication method is provided. The method is applied to a reader, and includes: obtaining a length of a device identification; determining a transmission resource according to the length of the device identification, the transmission resource having a size matching the length of the device identification, and the transmission resource being used to carry the device identification.

[0032] Therefore, for device identifications of different lengths, the reader can allocate transmission resources (or wireless resources) matching the lengths of the device identifications, for example, for a device identification with a relatively large length, relatively more transmission resources are allocated, and for a device identification with a relatively small length, relatively less transmission resources are allocated, so as to avoid waste of transmission resources and improve communication efficiency.

[0033] In a possible design, the obtaining of the length of the device identification includes: receiving the length of the device identification from the first terminal; or receiving the length of the device identification from a core network element for managing terminals, that is, the length of the device identification can be reported by the terminal or provided by the network side, and the specific implementation is not limited and can be flexibly selected according to actual conditions.

[0034] In a possible design, the method in the third aspect further includes: transmitting the device identification of the first terminal on the transmission resource.

[0035] In a possible design, the first terminal is an environmental Internet of Things (A-IoT) terminal.

[0036] It can be understood that the technical effects of the method in the third aspect can also be referred to the related description of the first aspect, and details are not repeated.

[0037] In a fourth aspect, a communication apparatus is provided. The communication apparatus includes modules for performing the communication method in any one of the implementation manners of the first aspect or the third aspect.

[0038] In the present application, the communication apparatus can be a terminal device or a network device, or a chip (system) or other components or assemblies, or an apparatus containing the terminal device or the network device. The chip (system) or other components or assemblies can be arranged in the terminal device or the network device.

[0039] It should be understood that the communication apparatus includes corresponding modules, units, or means for implementing the communication method described in any of the first aspect or the third aspect, which can be implemented by hardware, software, or by executing corresponding software by hardware. The hardware or software includes one or more modules or units for performing the functions involved in the communication method.

[0040] In a fifth aspect, a communication apparatus is provided. The communication apparatus includes a processor, configured to perform the communication method in any possible implementation of the first aspect or the third aspect.

[0041] In a possible design, the communication apparatus can further include a transceiver. The transceiver can be a transceiver circuit or an interface circuit. The transceiver can be configured to enable the communication apparatus in the fifth aspect to communicate with another communication apparatus.

[0042] In a possible design, the communication apparatus can further include a memory. The memory can be integrated with the processor, or can be separately arranged. The memory can be configured to store a computer program and / or data related to the communication method in any of the first aspect or the third aspect.

[0043] In this application, the communication apparatus can be a terminal device or a network device, or a chip (system) or other components or assemblies, or an apparatus containing the terminal device or the network device. The chip (system) or other components or assemblies can be arranged in the terminal device or the network device.

[0044] In a sixth aspect, a communication apparatus is provided. The communication apparatus includes a processor coupled to a memory, and the processor is configured to execute a computer program stored in the memory, so that the communication apparatus performs the communication method in any possible implementation of the first aspect or the third aspect.

[0045] In a possible design, the communication apparatus can further include a transceiver. The transceiver can be a transceiver circuit or an interface circuit. The transceiver can be configured to enable the communication apparatus to communicate with another communication apparatus.

[0046] In this application, the communication apparatus can be a terminal device or a network device, or a chip (system) or other components or assemblies, or an apparatus containing the terminal device or the network device. The chip (system) or other components or assemblies can be arranged in the terminal device or the network device.

[0047] In a seventh aspect, a communication apparatus is provided, which comprises a processor and a memory. The memory is configured to store a computer program, and the processor is configured to execute the computer program to cause the communication apparatus to perform the communication method in any one of the implementation manners of the first aspect or the third aspect.

[0048] In a possible design, the communication apparatus can further include a transceiver. The transceiver can be a transceiver circuit or an interface circuit. The transceiver can be configured to enable the communication apparatus to communicate with another communication apparatus.

[0049] In this application, the communication apparatus can be a terminal device or a network device, or a chip (system) or other components or assemblies, or an apparatus including the terminal device or the network device. The chip (system) or other components or assemblies can be arranged in the terminal device or the network device.

[0050] In an eighth aspect, a communication apparatus is provided, which comprises a processor. The processor is configured to be coupled with a memory, and to read a computer program in the memory and execute the communication method in any one of the implementation manners of the first aspect or the third aspect according to the computer program.

[0051] In a possible design, the communication apparatus can further include a transceiver. The transceiver can be a transceiver circuit or an interface circuit. The transceiver can be configured to enable the communication apparatus to communicate with another communication apparatus.

[0052] In this application, the communication apparatus can be a terminal device or a network device, or a chip (system) or other components or assemblies, or an apparatus including the terminal device or the network device. The chip (system) or other components or assemblies can be arranged in the terminal device or the network device.

[0053] In a ninth aspect, a processor is provided. The processor is configured to execute the communication method in any one of the implementation manners of the first aspect or the third aspect.

[0054] In a tenth aspect, a chip is provided. The chip can include a processor, and the processor is configured to execute the communication method in any one of the implementation manners of the first aspect or the third aspect.

[0055] Optionally, the chip further includes a memory coupled with the processor. The memory stores a program for executing the communication method in any one of the implementation manners of the first aspect or the third aspect.

[0056] In an eleventh aspect, a communication system is provided. The communication system includes one or more terminal devices configured to implement any possible implementation of the first aspect or the third aspect, and one or more network devices configured to implement any possible implementation of the first aspect or the third aspect.

[0057] In a twelfth aspect, a computer-readable storage medium is provided. The computer-readable storage medium includes computer programs or instructions, which, when executed, cause the communication method of any possible implementation of the first aspect or the third aspect to be implemented.

[0058] In a thirteenth aspect, a computer program product is provided. The computer program product includes computer programs or instructions, which, when executed, cause the communication method of any possible implementation of the first aspect or the third aspect to be implemented.

[0059] In addition, the technical effects of the communication apparatus of the fourth aspect to the thirteenth aspect can refer to the technical effects of the communication method of the first aspect or the third aspect, which will not be repeated here. BRIEF DESCRIPTION OF DRAWINGS

[0060] FIG. 1 is a schematic diagram of an architecture of an A-IoT;

[0061] FIG. 2 is a schematic diagram of a flow of an A-IoT;

[0062] FIG. 3 is a schematic diagram of a flow of an A-IoT;

[0063] FIG. 4 is a schematic diagram of an architecture of a communication system according to an embodiment of the present application;

[0064] FIG. 5 is a schematic diagram of an architecture of a communication system according to an embodiment of the present application;

[0065] FIG. 6 is a schematic diagram of a flow of a communication method according to an embodiment of the present application;

[0066] FIG. 7 is a schematic diagram of a flow of a communication method according to an embodiment of the present application;

[0067] FIG. 8 is a schematic diagram of a flow of a communication method according to an embodiment of the present application;

[0068] FIG. 9 is a schematic diagram of a flow of a communication method according to an embodiment of the present application;

[0069] FIG. 10 is a schematic diagram of a flow of a communication method according to an embodiment of the present application;

[0070] FIG. 11 is a schematic diagram of a structure of a communication apparatus according to an embodiment of the present application;

[0071] FIG. 12 is a schematic diagram of a structure of a communication apparatus according to an embodiment of the present application. DETAILED DESCRIPTION

[0072] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as a wireless network (Wi-Fi) system, a vehicle to everything (V2X) communication system, a device to device (D2D) communication system, a vehicle networking communication system, a 4th generation (4G) mobile communication system such as a long term evolution (LTE) system, a worldwide interoperability for microwave access (WiMAX) communication system, a 5th generation (5G) mobile communication system such as a new radio (NR) system, and a future communication system.

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

[0074] 1. Ambient IoT (A-IoT):

[0075] With the development of communication technology, the 3rd generation partnership project (3GPP) defines A-IoT. A-IoT is also called ambient power-enabled IoT, or passive IoT (P-IoT). A-IoT can be applied to various value scenarios.

[0076] For example, warehouse / transportation / supplies: by embedding or pasting passive or semi-passive IoT tags on goods, the information of the goods in the logistics process is automatically collected by the reader, and the management personnel can quickly query the goods information in the system, reduce the risk of loss or theft, improve the speed of goods handover, improve the accuracy, and prevent counterfeiting and anti-fake.

[0077] For another example, fixed asset management: some places with large assets or valuable goods such as libraries, art galleries and museums need complete management procedures or strict protection measures. When the storage information of books or valuable goods changes abnormally, the administrator will be reminded in the system in the first time, so as to handle the relevant situation.

[0078] Figure 1 is a schematic diagram of an A-IoT architecture, as shown in Figure 1, the architecture can include: a server, an ambient IoT management function (AIoTMF), a reader, an A-IoT terminal, or a terminal supporting A-IoT.

[0079] The server can be an application function (AF), an application server (AS), or an ambient IoT / passive IoT application function (A-IoT / P-IoT AF), etc., and the specific naming is not limited.

[0080] The AIoTMF can process service requests from a service requester (AF) and perform corresponding service operations (such as instructing the reader to perform an inventory process of the A-IoT terminal), transmit instructions (such as read operations, write operations, deactivation operations, etc.). The AIoTMF can also manage IoT devices, perform security authentication processes, etc.

[0081] The A-IoT terminal can be divided into three categories: device A, device B, or device C. Device A or device 1a can be understood as a passive A-IoT terminal. The passive A-IoT terminal can be in the form of a tag, or any other terminal form, without limitation. Device B or device 1b can be understood as a semi-passive A-IoT terminal. The semi-passive A-IoT terminal can obtain energy through solar energy, radio frequency, wind energy, water energy, or tidal energy, etc., and the way of obtaining energy is not limited. These nodes do not have or rely on 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 an active A-IoT terminal. For ease of understanding, A-IoT terminals and tags can be replaced with each other in expression.

[0082] The reader can be a radio access network (RAN) such as a base station, a pole station, a micro base station, a macro station, etc., or the reader can also be a terminal device such as a mobile phone, an IoT device, a handheld reader, etc. The reader can perform non-contact bidirectional data communication through wireless radio frequency, and read and write the tag through wireless radio frequency, so as to achieve the purpose of identifying the target and data exchange. For example, for a passive tag, when it enters the effective identification range of the reader, it can receive the radio frequency signal emitted by the reader, and emit the information stored in the chip by means of the induced current, or for a semi-passive tag or an active tag, it can actively send a signal of a certain frequency, and the reader receives the information and decodes it, and then sends it to the central information system for relevant data processing. In addition, the reader can also be called a reader / writer.

[0083] Specifically, when a server (or referred to as a service requester, such as an application function (AF) or an application server (AS)) operates on a tag, an operation instruction can be sent to the tag through a core network (CN), which can include but is not limited to: obtaining tag information, inventory operation (or referred to as inventorying operation), read operation, write operation, invalidation operation, and interacting with tag information operation. The operation instruction can include area location information, tag identification information, etc. The reader sends an access instruction to the tag. When the tag successfully accesses randomly, the reader sends an instruction to the tag, such as forwarding the above operation instruction. The tag obtains or sends corresponding information according to the instruction. For example, when the operation instruction is an inventory instruction or performs an inventory operation, the tag sends the identification information of the tag; when the operation instruction is a read instruction or performs a read operation, the tag sends the data information stored in the tag storage area; when the operation instruction is a write instruction or performs a write operation, the tag stores the data information to be written into the tag in the tag storage area. Then the reader sends (or forwards) the above information sent by the tag to the core network, which is sent to the server by the core network.

[0084] It should be understood that the manner in which the server sends the operation instruction can be through the control plane channel. For example, the AF / AS / A-IoT / P-IoT AF sends the operation instruction to the ambient IoT management function (or referred to as the ambient IoT function (AIoTF)), and the ambient IoT management function sends the operation instruction to the reader through the access and mobility management function (AMF). Alternatively, the A-IoT / P-IoT AF sends the operation instruction to the AIoTF through a network function network element, and the AIoTF sends the operation instruction to the reader, and the network function network element can include but is not limited to: a network exposure function device (NEF), a session management device (SMF), a policy control device (PCF), a user plane device (UPF), a unified data management device (UDM), a network slice and an independent non-public network (SNPN) authentication and authorization function (network slice-specific and SNPN authentication and authorization function, NSSAAF), etc. Alternatively, the manner in which the server sends the operation instruction can also be through the user plane channel. For example, the server sends the operation instruction to the reader through the UPF, and in the case of the reader being a terminal device, the server also sends the operation instruction to the RAN device through the user plane device, and the RAN device forwards the operation instruction to the reader.

[0085] The server or service requester can perform different operations on the ambient IoT device (or referred to as the ambient IoT terminal (A-IoT terminal)), such as a tag. The following lists several common service operations. The following describes the tag as a specific device form of the ambient IoT device, but the invention is not limited to the device form of the ambient IoT device.

[0086] The inventory operation, i.e. inventorying the existing tags, can also be understood as obtaining the identity of the tags. Each tag has its corresponding identity. The identity of the tag can be assigned by the enterprise (i.e. written into the tag when the enterprise prints the tag) or by the operator. In one possible implementation, the identity of the tag can be a globally unique code, such as an electronic product code (EPC), or a temporary identity or an identity that is not globally unique. In the inventory process, the server can issue an inventory instruction. Generally, the inventory instruction can include the identity range of the tag, the reader identity, the location information, etc. After receiving the inventory instruction, the reader can inventory the tag according to the inventory instruction and send the identity of the tag to the server. Alternatively, the server sends the inventory instruction, and the reader transmits the inventory instruction to the tag. The tag learns that it is an inventory operation according to the content of the inventory instruction, and sends the identity of the tag to the reader, and the reader sends the identity of the tag to the server; or the tag sends the identity of the tag to the core network through the reader, and the core network sends the identity of the tag to the server.

[0087] The read operation, i.e. reading data from the tag. The tag can have a storage function, and its storage area can store data. If the server wants to perform a read operation on the tag, it will send a read instruction, and the reader or core network will perform a read operation on the tag according to the instruction, read data from the tag storage area, and send the data to the server. The write operation, i.e. writing data to the tag. The server can send a write instruction, and the reader or core network will perform a write operation on the tag according to the instruction, and write data to the storage area of the tag.

[0088] The inactivation operation, i.e. disabling or inactivating the tag. The server can send an inactivation instruction, which can include the identity of the tag (i.e. the identity of the tag that is desired to be disabled or inactivated). The reader or core network will perform a disabling operation on the tag according to the instruction, and after the operation is completed, the tag will be disabled or inactivated and can no longer be inventoried or perform other operations.

[0089] Obtaining tag information can be understood as a high-level description of the above-mentioned various operations (e.g. a high-level description of the inventory operation and the read operation), which does not distinguish whether the server is inventorying the tag or reading the data of the tag. The operation will obtain tag information, which can be identity information of the tag or information stored in the storage area of the tag.

[0090] The message interaction with the tag can be understood as a high-level description of the above-mentioned various operations. After receiving the instruction sent by the server, the reader interacts with the tag for information or messages, and sends the information from the tag to the server. The operation is mainly aimed at the above-mentioned reader not viewing the content of the instruction, and only responsible for forwarding the message sent by the server to the tag and the message sent by the tag to the server. Therefore, in this scenario, the operation of the reader on the tag can be understood as the message interaction with the tag.

[0091] 2. Operation flow of A-IoT:

[0092] As shown in FIG. 2, one flow is as follows.

[0093] S200, the core network sends an inventory message to the reader.

[0094] The inventory message contains instructions, such as read / write / inventory instructions, which are not limited in detail, and the following examples are taken as read instructions for reference. In addition, the inventory message also contains inventory session, action, mask, etc.

[0095] 1) The session and the following flag bit are in a binding relationship, each flag bit corresponds to a session, and the inventory session specifies which session flag bit is set.

[0096] 2) The action specifies how to set, such as action indicating 1 or 0, and if the mask matches after the tag receives it, the session corresponding flag bit will be set, such as A (action = 1) or B (action = 0).

[0097] 3) The mask can be understood as a prefix of the identification of the tag. The mask is used to screen which tags are selected, such as the tag storing a complete 96-bit identification, and the mask can indicate that the tag with the first 16 bits of 111…111 is selected.

[0098] The core network can send an inventory message to the reader after determining to perform an A-IoT business operation (such as a read / write / inventory operation).

[0099] S201, the reader sends a select message or a paging message.

[0100] The select message or the paging message is used to select a group of tags, and the select message or the paging message can contain the information in the above-mentioned inventory message.

[0101] When a tag receives a selection message, the matching tag sets the selection message and the corresponding flag. For example, if the inventory session indicates session S0 and the behavior indicator is 0, and the mask matches, the tag sets the flag for session S0 to A, which is the initial flag setting. Afterwards, the device identifier (e.g., EPC) success flag will be flipped to B. Thus, A represents tags that haven't yet transmitted EPC, and B represents tags that have successfully transmitted it. If the mask matches, the tag can further set its flag according to the session's indication and then listen for subsequent paging messages (queries).

[0102] S202, the reader sends a query message or a query duplicate message (queryRep).

[0103] Query messages can carry Q-values, session information, or flags.

[0104] Suppose that the session carried by the query message is S0 and the flag bit is A. The session and flag bit of the tag are matched with it, so a random number between 0 and 2^Q-1 is randomly generated according to Q as the initial value of the counter.

[0105] Querying duplicate messages does not require carrying content, has no Q value or session, and can be sent multiple times.

[0106] If no tag sends a response, such as RN16, the reader continues to send duplicate query messages. If a tag receives a duplicate query message, the tag decrements its counter by 1, e.g., Counter = Counter - 1.

[0107] S203, tag sent RN16.

[0108] If the tag's count value is 0, the tag responds with RN16; otherwise, it does not respond. RN16 is a 16-bit random number (or it could be 16 bits or 8 bits) used for contention resolution. For example, after the tag receives (potentially multiple) duplicate query messages, its count value decreases to 0, and the tag responds with RN16; otherwise, it does not respond. For example, each duplicate query message corresponds to the start or end of an access time slot. Each duplicate query message received by the tag signifies the end of the previous time slot and the start of the next time slot. The tag can randomly select an access time slot to initiate access, send uplink data (EPC), or receive downlink data.

[0109] S204, the reader returns an acknowledgment message (ACK).

[0110] When the reader receives the RN16 sent by the tag, if there is no collision (e.g., only one tag's RN16 is received), it sends back an ACK, which includes the received RN16 and indicates that the contention has been successfully resolved.

[0111] S205, the tag sends a device ID.

[0112] If the tag receives the ACK and the RN16 matches, the tag feeds back the device ID, otherwise, it does not feed back. In one possible implementation, the device ID can be carried in an uplink (UL) non-access-stratum (NAS) message, and the UL NAS message can also carry data, such as data read according to the read instruction.

[0113] S206, the reader sends a queryRep message.

[0114] If the tag sends the device ID and receives the queryRep message, it indicates that the transmission is successful, and the flag bit is flipped, i.e., flipped to B. For example, the flag bit can be used to prevent a tag that has been inventoried from being inventoried repeatedly. For example, if the flag bit carried in a subsequent paging message is A, the tag will not respond if the flag bit is flipped to B.

[0115] S207, the reader sends an N2 message to the core network.

[0116] The N2 message contains the UL NAS message described above. In addition, the execution order of S206 and S207 is not limited. In one possible implementation, if the interface between the reader and the core network is not an NGAP interface, the N2 message can be replaced by other message types, i.e., messages corresponding to the interface between the reader and the core network, for example, AIoT NGAP. The present application is not limited.

[0117] As can be seen, in the flow shown in FIG. 2, the tag only needs to report the device ID and / or data to be read through a single UL NAS message, without subsequent signaling interaction. Therefore, when the reader receives the UL NAS message from the tag, it can continue to trigger the random access procedure of other tags, such as continuing to broadcast the paging message or repeating the query, so as to avoid waiting for other instructions from the core network element.

[0118] For another example, as shown in FIG. 3, still taking the A-IoT terminal as the tag, another flow is as follows.

[0119] S300, the core network sends an inventory message to the reader.

[0120] The inventory message contains an inventory session, behavior, or mask, etc. Unlike S200 described above, the inventory message does not carry an instruction.

[0121] S301, the reader sends a selection message or a paging message.

[0122] S302, the reader sends a query message or a queryRep message.

[0123] S303, the tag sends the RN 16.

[0124] S304, the reader returns an ACK.

[0125] S305, the tag sends a device identity.

[0126] The device identity is carried in an UL NAS message.

[0127] In one possible implementation, the device identity is carried in the UL NAS message, but unlike S206 described above, the UL NAS message in S306 does not carry data.

[0128] S306, the reader sends a query repetition message.

[0129] S307, the reader sends an N2 message to the core network.

[0130] The N2 message contains the UL NAS message in S306. In one possible implementation, if the interface between the reader and the core network is not an NGAP interface, the N2 message can be replaced by other message types, i.e., messages corresponding to the interface between the reader and the core network, such as AIoT NGAP. The present application does not make any limitation.

[0131] It can be understood that S300-S308 can refer to the related description of S200-S208 described above, and will not be repeated here.

[0132] Up to now, the tag random access is completed.

[0133] S308, the core network sends an instruction to the reader.

[0134] In one possible implementation, the core network sends a downlink (DL) NAS message to the reader.

[0135] The DL NAS message carries the instruction, such as the instruction to read.

[0136] S309, the reader sends the instruction to the tag.

[0137] The instruction can be the instruction to read.

[0138] In one possible implementation, the reader sends the DL NAS message from the core network to the tag, and the DL NAS message includes the instruction.

[0139] S310, the tag sends data to the reader.

[0140] The data is the data read according to the instruction to read. In one possible implementation, the data is carried in an UL NAS message.

[0141] S311, the reader sends an N2 message to the core network.

[0142] The N2 message in S311 contains the UL NAS message in S310. In a possible implementation, if the interface between the reader and the core network is not an NGAP interface, the N2 message can be replaced by another message type, i.e., a message corresponding to the interface between the reader and the core network, which can be AIoT NGAP, for example. The present application does not make any limitation.

[0143] S312, the core network sends an inventory message to the reader.

[0144] The inventory message in S312 can carry an indication of inventory continue.

[0145] In the flow shown in FIG. 2 and FIG. 3, the device identity of the A-IoT terminal can be of different kinds or implementations, such as an operator allocated identity, such as an operator allocated A-IoT device ID, a subscription permanent identifier (SUPI), an international mobile subscriber identity (IMSI), a generic public subscription identifier (GPSI), a globally unique temporary UE identity (GUTI), a permanent equipment identifier (PEI), a 3GPP-defined identifier, an ambient IoT device ID, and the like, or an enterprise (or third party) allocated identity, one possible implementation of which is an electronic product code (EPC). Since there are various application scenarios of A-IoT, the type and length of the device identity can be different in different application scenarios. For wireless resource scheduling, the network usually allocates wireless resources according to the maximum length of the device identity (such as 496 bits) to ensure the stability and reliability of transmission. However, how the network can guarantee the efficiency of the service (such as efficient inventory) in the face of multiple device identities coexisting is a problem to be solved. In addition, the reporting of the device identity usually relies on a tail pilot, which can be understood as an end symbol as a symbol for the end of the reporting of the device identity. However, in a wireless communication system, wireless resources are directly scheduled by the base station and cannot be determined by the A-IoT terminal itself, so the tail pilot method cannot be applied to the wireless communication system.

[0146] To solve the above technical problems, the embodiments of the present application propose the following technical solutions. The technical solutions in the present application will be described below with reference to the accompanying drawings.

[0147] The present application will present various aspects, embodiments or features around a system that can include multiple devices, components, modules, etc. It should be understood and appreciated that each system can include additional devices, components, modules, etc., and / or can not include all of the devices, components, modules, etc. discussed in connection with the accompanying drawings. In addition, combinations of these solutions can also be used.

[0148] In addition, in the present application, the words "for example", "for instance", "such as", and "like", are used merely to illustrate examples of the present application. Any embodiment or design solution described as "for example" in the present application should not be interpreted as being more preferred or advantageous than other embodiments or design solutions. In fact, the use of the words "for example" is meant to present concepts in a concrete manner.

[0149] First, in the present application, "indication" can include direct indication and indirect indication. When describing that certain "information" indicates A, it can include that the information directly indicates A or indirectly indicates A, and does not mean that A must be carried in the information.

[0150] The information indicated by one information is referred to as to-be-indicated information. In the implementation process, there are many ways to indicate the to-be-indicated information, for example, but not limited to, the to-be-indicated information can be directly indicated, such as the to-be-indicated information itself or an index of the to-be-indicated information. The to-be-indicated information can also be indirectly indicated by indicating other information, where the other information and the to-be-indicated information have an association relationship. The to-be-indicated information can also be only indicated in part, and the other part of the to-be-indicated information is known or agreed in advance. For example, the indication of a specific information can also be achieved by means of the arrangement order of each information agreed in advance (for example, a protocol stipulates), thereby reducing the indication overhead to a certain extent. At the same time, the common part of each information can be identified and uniformly indicated, so as to reduce the indication overhead caused by separately indicating the same information.

[0151] In addition, the specific indication manner can also be various existing indication manners, for example, but not limited to, the above-mentioned indication manners and various combinations thereof. The specific details of various indication manners can refer to the prior art, which will not be described herein. As can be seen from the above, for example, when multiple information of the same type needs to be indicated, the indication manner of different information can not be the same. In the implementation process, the required indication manner can be selected according to the specific needs, and the selected indication manner is not limited in the embodiments of the present application. In this way, the indication manner involved in the embodiments of the present application should be understood as covering various methods that can enable the to-be-indicated party to know the to-be-indicated information.

[0152] The to-be-indicated information can be sent as a whole or can be divided into multiple sub-information and sent separately, and the sending period and / or sending occasion of the sub-information can be the same or different. The specific sending method is not limited in the present application. The sending period and / or sending occasion of the sub-information can be predefined, for example, predefined according to a protocol, or configured by the transmitting end device to the receiving end device through sending configuration information. The configuration information can include, for example but not limited to, one or a combination of at least two of radio resource control (RRC) signaling, medium access control (MAC) layer signaling and physical layer signaling. The MAC layer signaling can include, for example, MAC control element (CE), and the physical (PHY) layer signaling can include, for example, downlink control information (DCI).

[0153] Secondly, in the embodiments shown below, “first”, “second” and various numerical numbers are only used for differentiation for convenience of description, and do not limit the scope of the embodiments of the present application. For example, different indication information is differentiated.

[0154] Thirdly, “preset” or “predefined” or “preconfigured” can be implemented by pre-storing corresponding codes, tables or other information indicating manners in devices (for example, including terminal devices and network devices), or can be predefined in a protocol, and the specific implementation manner is not limited in the present application. The “storing” can mean storing in one or more memories. The one or more memories can be separately set or integrated in an encoder or decoder, a processor or a communication device. The one or more memories can be partially separately set and partially integrated in a decoder, a processor or a communication device. The type of the memory can be any form of storage medium, which is not limited in the present application.

[0155] Fourthly, the “protocol” involved in the embodiments of the present application can refer to a standard protocol in the communication field, for example, can include the LTE protocol (such as technical specification (TS) 36, that is, the technical specification of TS36 series) of 3GPP, the NR protocol (such as the technical specification of TS38 series) and the related protocol applied to the future communication system, which is not limited in the present application.

[0156] The network architecture and service scenarios described in the embodiments of the present application are used to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those skilled in the art can know that, with the evolution of network architecture and the emergence of new service scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

[0157] The network architecture and service scenarios described in the embodiments of the present application are used to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those skilled in the art can know that, with the evolution of network architecture and the emergence of new service scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

[0158] To facilitate understanding of the embodiments of the present application, first, a communication system shown in FIG. 4 is taken as an example to illustrate the communication system applicable to the embodiments of the present application in detail. Exemplarily, FIG. 4 is a schematic diagram of the architecture of a communication system applicable to the method provided by the embodiments of the present application.

[0159] FIG. 4 is a schematic diagram of the architecture of a communication system, which mainly includes a terminal and a network entity.

[0160] The terminal can be a device or module with corresponding communication functions for accessing the communication system. The terminal can also be referred to as a terminal device, user equipment (UE), mobile station, mobile terminal, and can be virtual reality, augmented reality, industrial control, autonomous driving, remote medical treatment, smart power grid, smart furniture, smart office, smart wear, smart transportation, smart city, etc., or can be a mobile phone, tablet computer, computer with wireless transceiver function, wearable device, vehicle, unmanned aerial vehicle, helicopter, airplane, ship, robot, mechanical arm, smart home device, wireless communication function transport vehicle, communication module, etc.

[0161] The terminal can be widely used in various scenarios, such as device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-type communication (MTC), and internet of things (IoT), such as A-IoT, which is referred to as A-IoT terminal. The embodiments of the present application do not limit the device form of the terminal. The terminal is usually provided with a communication module, circuit or chip for executing corresponding communication functions. The terminal is also configured with program instructions for executing corresponding communication functions.

[0162] It can be understood that the terminal can be one or more, and for convenience of description, a first terminal is taken as an example in the following description.

[0163] The network entity can be a core network element, such as an element performing an IoT management function, which can be an A-IoT MF, mainly responsible for an IoT management function or an environmental IoT management function, or the element can also be an IoT terminal management function (IDMF), mainly responsible for transmission of service data of an IoT device, management of an IoT terminal, a security process of an IoT terminal, or instructing a reader to perform an IoT service operation according to a service requestor instruction, etc. The naming of the network element performing the IoT management function is not limited in the present application, which can be other names, such as an access and mobility management function (AMF), or any other possible named network element.

[0164] Alternatively, the network entity can also be an access network device, also referred to as a radio access network (RAN) node, or a network device having a logical function of a core network. The RAN node can be a 3GPP related cellular system, for example, a 4G, 5G mobile communication system, or a future-oriented evolution system. The RAN node can also be an open RAN (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system. The RAN node can also be a communication system that combines two or more of the above systems. The RAN node can also be referred to as an access network device, a RAN entity or an access node, etc., which constitutes a part of a communication system to help a terminal to realize wireless access. Multiple RAN nodes in a communication system can be nodes of the same type or nodes of different types.

[0165] In a possible scenario, the RAN node can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next generation NodeB (gNB), a base station in a future mobile communication system, or an access node in a WiFi system, etc. The RAN node can be a macro base station, a micro base station or an indoor station, a relay node or a donor node, or a wireless controller in a CRAN scenario. Optionally, the RAN node can also be a server, a wearable device, a vehicle or a vehicle-mounted device, etc. For example, the access network device in vehicle to everything (V2X) technology can be a road side unit (RSU). All or part of the functions of the RAN node in the present application can also be implemented by software functions running on hardware, or by virtualized functions instantiated on a platform such as a cloud platform. The RAN node can also be provided with a communication module, circuit or chip for performing corresponding communication functions, and program instructions for performing corresponding communication functions. The RAN node in the present application can also be a logical node, a logical module or software that can implement all or part of the functions of the RAN node.

[0166] In another possible scenario, a terminal is assisted by multiple RAN nodes to implement wireless access, and different RAN nodes respectively implement part of the functions of a base station. For example, the RAN node can be a central unit (CU), a distributed unit (DU) or a radio unit (RU), etc.

[0167] In some examples, the CU is a logical node that carries radio resource control (RRC) layer, service data adaptation protocol (SDAP) layer, packet data convergence protocol (PDCP) layer and other control functions of the access network device. The CU is connected to network nodes such as core network through some interfaces, which can be E2 interface or the like. Optionally, the CU can have part of the functions of the core network. The CU (e.g. PDCP layer and higher layer) is connected to the DU (e.g. RLC layer and lower layer) through some interfaces, which can be F1 interface or the like. In some examples, these interfaces (e.g. F1 interface) can provide control plane (C-plane) and user plane (U-plane) functions (e.g. interface management, system information management, UE context management, RRC message transmission, etc.). F1AP is an application protocol of F1 interface, which defines signaling procedures of F1 in some examples. The F1 interface supports control plane F1-C and user plane F1-U.

[0168] In some examples, the CU can be split into CU control plane (CU-CP) and CU user plane (CU-UP), wherein the CU-CP is a logical node that carries RRC layer and PDCP control plane part (PDCP-C) layer, used to implement the control plane function of the CU. The CU-CP can interact with network elements in the core network for implementing control plane functions. The network element in the core network for implementing control plane functions can be an access and mobility function network element, such as AMF in 5G system. The AMF is used to be responsible for mobility management in the mobile network, such as location update of terminal device, registration network of terminal device, handover of terminal device, etc. The CU-UP is a logical node that carries SDAP layer and PDCP user plane part (PDCP-U) layer, used to implement the user plane function of the CU. The CU-UP can interact with network elements in the core network for implementing user plane functions.

[0169] The above configuration of the CU and the DU is merely an example, and the CU and the DU can be configured to have functions as needed. For example, the CU or the DU can be configured to have functions of more protocol layers, or the CU or the DU can be configured to have partial processing functions of the protocol layers. For example, partial functions of the RLC layer and functions of the protocol layers above the RLC layer are arranged in the CU, and the remaining functions of the RLC layer and functions of the protocol layers below the RLC layer are arranged in the DU. For another example, the functions of the CU or the DU can be divided according to a service type or other system requirements, for example, according to a delay requirement. For example, functions that require a shorter delay requirement for processing time are arranged in the DU, and functions that do not require the delay requirement are arranged in the CU.

[0170] In some examples, the DU is a logical node that carries a radio link control (RLC) layer, a medium access control (MAC) layer, a higher physical layer (higher PHY), and other functions. In some examples, the DU can control at least one RU. The DU is connected to the RU through some interfaces, which can be a front-haul interface. In some examples, the higher physical layer includes part of the PHY layer processing, such as forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, and other processing functions.

[0171] In some examples, the RU can be included in a radio frequency device or a radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH). The RU is a logical node that carries a lower physical layer (Lower PHY) and radio frequency (RF) processing. In some examples, the RU can be a 3GPP transmission reception point (TRP) or a remote radio head (RRH) or other similar functional entity. In some examples, the Low-PHY includes part of the PHY processing, such as fast fourier transform (FFT), inverse fast fourier transformation (IFFT), digital beamforming and filtering, and other processing functions. The RU communicates with one or more UEs through a wireless link.

[0172] The DU and the RU can or can not be co-located. The DU and the RU exchange control plane information and user plane information via a lower-layer split-control, user and synchronization (LLS-CUS) interface over a fronthaul link. The LLS-CUS can include a LLS-C interface and a LLS-U interface that provide control plane (C-plane) and user plane (U-plane), respectively. In some examples, the control plane (C-plane) refers to real-time control between the DU and the RU. The DU and the RU have an interface of the fronthaul link to exchange management information, and the management plane (M-plane) refers to non-real-time management operation between the DU and the RU.

[0173] The DU and the RU can cooperate to jointly implement the functions of the PHY layer. One DU can be connected to one or more RUs. The functions of the DU and the RU can be configured in multiple ways according to design. For example, the DU is configured to implement baseband functions, and the RU is configured to implement intermediate radio frequency functions. For another example, the DU is configured to implement high-layer functions in the PHY layer, and the RU is configured to implement low-layer functions in the PHY layer or to implement the low-layer functions and radio frequency functions. The high-layer functions in the PHY layer can include a portion of the functions of the PHY layer that are closer to the MAC layer, and the low-layer functions in the PHY layer can include another portion of the functions of the PHY layer that are closer to the intermediate radio frequency side.

[0174] The CU (or CU-CP and CU-UP), the DU, or the RU can also have different names in different systems, but those skilled in the art can understand their meanings. For example, in an ORAN system, the CU can also be referred to as an O-CU (open CU), the DU can also be referred to as an O-DU, the CU-CP can also be referred to as an O-CU-CP, the CU-UP can also be referred to as an O-CU-UP, and the RU can also be referred to as an O-RU. For the convenience of description, the CU, the CU-CP, the CU-UP, the DU, and the RU are taken as examples for description in this application. Any of the CU (or CU-CP, CU-UP), the DU, and the RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0175] In the ORAN system, the RAN node communicates with the core network (CN) through a backhaul link and communicates with the terminal through an air interface. The ORAN system also includes a RAN intelligent controller (RIC), which can specifically include a non-real time RAN intelligent controller (Non-RT RIC) and a near-real time RAN intelligent controller (Near-RT RIC). The Non-RT RIC is used to implement non-real-time intelligent management of RAN functions, and the Non-RT RIC is located in a service management and orchestration framework (SMO) module. The Near-RT RIC is used to implement near-real-time intelligent management of the RAN, and implements near-real-time control and optimization of modules and resources of the O-RAN through data collection and related operations on the E2 interface.

[0176] It can be understood that the network entity can also be one or more, and for convenience of description, the first network entity is taken as an example in the following.

[0177] In some examples, the communication system of the embodiments of the present application can be applied to an A-IoT scenario.

[0178] As shown in (a) of FIG. 5, the A-IoT terminal directly communicates with the reader in a bidirectional manner, including interaction of environmental Internet of Things data and / or signaling, such as the reader sending downlink data / signaling to the A-IoT terminal and the reader receiving uplink data / signaling from the A-IoT terminal.

[0179] As shown in (b) of FIG. 5, the A-IoT terminal and the reader communicate with each other through an intermediate node, which can be a repeater, an integrated access and backhaul (IAB) node, a UE, or other devices capable of implementing environmental Internet of Things, to transmit environmental Internet of Things data and / or signaling between the A-IoT terminal and the reader.

[0180] As shown in (c) of FIG. 5, the A-IoT terminal receives data / signaling from the auxiliary node and sends data / signaling to the reader, or the A-IoT terminal receives data / signaling from the reader and sends data / signaling to the auxiliary node. The auxiliary node can be a repeater, an IAB, a UE, or other devices capable of implementing environmental Internet of Things.

[0181] As shown in (d) of FIG. 5, the A-IoT terminal communicates with the terminal device in a bidirectional manner, such as interacting with the environmental IoT data and / or signaling. The terminal device can be a terminal device supporting the function of a reader, that is, the reader can also be understood as a terminal device.

[0182] On this basis, the first terminal in the communication system can be the A-IoT terminal in FIG. 5, and the first network entity in the communication system can be an access network device, which can support the function of a reader, and can be a combination of one or more of the reader, the intermediate node, the auxiliary node in FIG. 5, such as the reader, the intermediate node, the reader+intermediate node, the reader+auxiliary node, etc., or the access network device can also be replaced by the terminal device in (d) of FIG. 5 to be implemented. When the first network entity is an access network device, the device form thereof can be a pole station, a micro base station, a base station, a small station, a macro station, etc., and is not limited in particular.

[0183] The first terminal can interact with the environmental IoT data and / or signaling with the first network entity to implement corresponding environmental IoT services, such as inventory, positioning, sensing, and commands. For example, the first terminal usually needs to send its own identifier to the first network entity. In this case, the first network entity can first specify the identifier length and / or length interval by sending the first information. If the first terminal determines that the length of its own device identifier meets the preset rule and / or is located in the length interval after receiving the first information, the first terminal can report its own device identifier, such as the first identifier, otherwise, it does not report, to achieve batch and orderly reporting, so as to ensure the efficiency of the business process on the network side for different lengths of device identifiers.

[0184] Additionally, for the access network device, for different lengths of identifiers of different terminals, the access network device can allocate transmission resources, or wireless resources, matching the lengths according to the lengths, that is, for identifiers with relatively large lengths, relatively more transmission resources are allocated, and for identifiers with relatively small lengths, relatively less transmission resources are allocated, which can avoid the waste of transmission resources and provide communication efficiency compared with the prior art of allocating transmission resources according to the maximum length.

[0185] It should be understood that the communication method provided by the embodiments of the present application can be applied to the device shown in FIG. 4, and the specific implementation can refer to the method embodiments described below, which will not be described here. The scheme in the embodiments of the present application can also be applied to other communication systems, and the corresponding function names in other communication systems can also be replaced.

[0186] It should also be understood that FIG. 4 is only a simplified schematic diagram for understanding, and other network devices and / or other terminal devices can also be included in the communication system, which are not shown in FIG. 4.

[0187] The interaction process between devices in the communication system will be specifically introduced below by method embodiments in combination with FIG. 6 to FIG. 10. The communication method provided by the embodiments of the present application can be applied to the above communication system, and the communication method will be specifically introduced below.

[0188] FIG. 6 is a flowchart of the communication method, which is applicable to the interaction between the first terminal and the first network entity. As shown in FIG. 6, the flow of the communication method is as follows:

[0189] S601, the first network entity sends first information. Correspondingly, the first terminal receives the first information.

[0190] The first information can include M identification lengths and / or N length intervals, M and N are positive integers.

[0191] The identification length can refer to the length of the terminal identification, or the length of the device ID. The length of the device ID can be various, which can also be understood as that there are various lengths of device IDs in the network, such as 496 / 128 / 96 bits, or there can be other lengths, which are not specifically limited in the embodiments of the present application. In one possible implementation, the device ID can have various types, such as the operator-assigned identification, specifically the operator-assigned A-IoT device ID, SUPI, IMSI, etc., or it can also be the identification assigned by an enterprise (or a third party or a business requester), such as EPC, which can be referred to the above related introduction. The lengths of device IDs of different types can be different, or the device IDs of the same type can also have various lengths, such as the lengths of EPCs of different enterprises can be different.

[0192] In addition, the specific implementation of the device ID can also be referred to the related introduction of the “first identification” and “second identification” below, which will not be repeated here.

[0193] For any one of the M identification lengths, the identification length can be a quantized length value, for example, the identification length can be a number of length units, or expressed by a number of length units. The length unit can be a bit, such as 16 bits, 24 bits, 36 bits, 96 bits, 128 bits, 192 bits, 256 bits, 496 bits, etc.; or the length unit can also be a word, such as 16 bits as one word, and the identification length is how many 16 bits, that is, how many words; or the length unit can also be a byte, such as 8 bits as one byte, and the identification length is how many 8 bits, that is, how many bytes. Or the identification length can also be in the form of an index, for example, for the 8 lengths of 16 bits, 24 bits, 36 bits, 96 bits, 128 bits, 192 bits, 256 bits, and 496 bits, the index can be a 3-bit bitmap, such as index0 = 000, indicating that the identification length is 16 bits, index1 = 001, indicating that the identification length is 24 bits, index1 = 010, indicating that the identification length is 36 bits, and so on, until index7 = 111, indicating that the identification length is 496 bits. Or the index can also be replaced by any other possible name, such as gear, length gear, rank, length rank, type, length type, level, length level, etc., without limitation on the specific naming.

[0194] The M identification lengths can include K identification lengths, or the M identification lengths include the same length and / or different lengths, a total of K lengths, K being a positive integer. For example, the M identification lengths are 3, the first identification length is L1, the second identification length is L2, and the third identification length is L2, that is, the second identification length and the third identification length have the same length, both being L2, so the 3 identification lengths include L1 and L2, which are 2 identification lengths. For another example, the M identification lengths are 3, the first identification length is L1, the second identification length is L2, and the third identification length is L3, so the 3 identification lengths include L1, L2, and L3, which are 3 identification lengths.

[0195] K kinds of identifier lengths can belong to L kinds of identifier lengths, L is an integer greater than or equal to K, that is, L kinds of identifier lengths can be understood as a collection of different kinds of identifier lengths, and K kinds of identifier lengths can be understood as a subset of the collection. L kinds of identifier lengths can be a relatively local length type, such as applicable to a certain service requester or a certain service (such as the first service or the service requester of the first service described below), the device identifiers involved in the service requester or the service share L kinds of identifier lengths, and the kinds of identifier lengths involved in different service requesters or services can also be different. Alternatively, L kinds of identifier lengths can also be a relatively global length type, such as applicable to multiple service requesters or multiple services (including the first service or the service requester of the first service described below), the device identifiers involved in these service requesters or services share L kinds of identifier lengths. L kinds of identifier lengths can be defaulted by the first network entity (or pre-configured to the first network entity), or can also be dynamically obtained by the first network entity, which will be introduced below.

[0196] Case 1, dynamic acquisition:

[0197] The first network entity can receive a service request from the second network entity, and determine L kinds of identifier lengths according to the service request, that is, the determination of L kinds of identifier lengths can be triggered by the service request to achieve on-demand determination according to service requirements, which will be introduced in detail below.

[0198] The second network entity can be a requester of the first service, or a service requester, for example, the second network entity can be an application function (AF) or an application server (AS), which can be a third-party application function or application server, or an application function or application server within an operator network, without specific limitation. Among them, the first network entity can receive a service request through other network functions (such as network exposure functions (network exposure function, NEF)). The message type of the service request received by the first network entity from other network functions can be the same as or different from the message type of the service request received by the other network functions from the second network entity, that is, the other network functions can transmit the service request to the first network entity, or process (such as replace the message type) the received service request and then send it to the first network entity, without specific limitation.

[0199] The first service can be an A-IoT service or any other possible service, without limitation.

[0200] For example, the first service can be a service related to an application scenario, such as at least one of the following: inventory service, command service, positioning service, sensing service, proximity, read service, write service, deactivation service, lock service, or security service (such as authentication, authorization, registration, etc.), or can also be a newly defined service type in the future, and the specific name is not limited.

[0201] For another example, the first service can also be a service related to a process, such as at least one of the following: access process, or data transmission process, etc., and it can be understood that performing the first service is to perform the corresponding process. The access process can be random access, such as contention-based random access, or contention-free random access. Optionally, the access process can include reporting the device identifier. The data transmission process can be device (such as A-IoT terminal) - reader (D2R) / uplink data transmission, reader - device (R2D) / downlink data transmission, etc. Optionally, the data transmission process can also include reporting the device identifier. Optionally, the access process and the data transmission process are not strictly distinguished, and the two can also be combined for execution, such as in the access process, data transmission can also be performed, such as contention-free random access, and the device can send D2R / uplink data in the first message.

[0202] The service request can indicate that the first service is performed for a terminal that meets a preset condition. The terminal that meets the preset condition can include at least one of the following: a terminal located in an indicated area, a terminal identified as an identification type, a terminal identified as containing a specified feature, or any other possible condition, and the specific name is not limited. For example, the service request can include at least one of the following information elements: service requestor identifier, type of first service, identifier of first service, information indicating an area, identification type information (denoted as identification type information #1), or identification description information (denoted as identification description information #1), which are introduced below.

[0203] 1) The service requestor identifier can indicate the service requestor, such as AF ID, etc. The operator network can store subscription information related to the service requestor, such as the area or device identifier range allowed to perform the first service, etc., so that the operator network can perform authorization on the first service according to the subscription information.

[0204] 2) The type of first service can indicate the type of first service, such as inventory service, command service, positioning service, sensing service, proximity, read service, write service, deactivation service, lock service, or security service (such as authentication, authorization, registration, etc.), or can also be a newly defined service type in the future, and the specific name is not limited.

[0205] 3) The first service identifier can be used to uniquely identify the first service, and the specific identification type is not limited. In one possible implementation, the first service identifier can identify the type of the first service. In another possible implementation, the first service identifier can identify the service request, for example, a transaction ID.

[0206] 4) The information indicating the area can indicate a certain area, such as represented by geometric (geographical) location information, such as XX province, XX city, XX district, or coordinate values, latitude and longitude ranges, and the like, or can also be represented by topology (network) location information that can be recognized by a network element in the core network, such as a data network access identifier (DNAI), a track area identifier (TAI), a TAI list, an area ID, an area ID list, a reader identifier, a reader identifier set, a cell ID, or a cell ID list, and the like. In another possible implementation, the information indicating the area can be represented by configuration information configured in the core network element, which can include an index and location information correspondence, or an index and reader ID (reader ID set) correspondence. The index can be a target ID or a target set ID, and the location information can be the geometric (geographical) location information described above, or topology (network) location information that can be recognized by a core network element, and the like. If the reader is an access network device, the reader identifier can be a gNodeB ID, a RAN ID, and the like, and if the reader is a terminal device, the reader identifier can be a UE ID, a GPSI, a SUPI, or a GUTI, and the like.

[0207] 5) The identification type information #1 can indicate the identification type of the device identifier, which can be one or more of the following: an operator network assigned identifier, a non-operator network assigned identifier, a product electronic identifier such as an EPC, or a non-product electronic identifier such as a non-EPC.

[0208] 6) The identification description information #1 (or identification feature information) can indicate a specific value in the device identifier, or a part of the identifier that needs to be matched, such as a specific value of the xth bit of the device identifier, for example, the value of the 3rd bit is 1, or a specific value of the xth bit to yth bit, for example, the 0th bit to 7th bit is 11001110.

[0209] Thus, the information elements contained in the service request jointly indicate that the first service is performed on at least one of the following: a terminal located in the indicated area, a terminal whose device identity belongs to the identity type indicated by the identity type information #1, or a terminal whose device identity contains a specific value indicated by the identity description information #1.

[0210] It should be understood that the service request is an exemplary designation, which can also be replaced by a more specific designation. For example, the first service is an inventory service, and the service request can be replaced by an inventory request. For another example, the first service is a deactivation service, and the service request can be replaced by a deactivation request. For yet another example, the first service is a command such as read / write / lock, and the service request can be replaced by a command. At this time, the message name of the service request can be used as the information indicating the type of the first service.

[0211] It can be seen that the terminal to which the service request is directed is usually an uncertain terminal. The first network entity can consider that the device identity of these terminals can have multiple lengths, or consider that the device identity of these terminals cannot be determined to be a single length. Alternatively, the first network entity cannot determine the specific mask, and also considers that the device identity of these terminals can have multiple lengths. Thus, the first network entity can obtain L kinds of identification lengths.

[0212] For example, the third network entity is pre-configured with L kinds of identification lengths. The third network entity can be a data management network element, such as a unified data management (UDM) network element, or a data storage network element, such as a unified data repository (UDR) network element. In this way, the first network entity can obtain the L kinds of identification lengths from the third network entity according to the service request. For example, the first network entity can schedule a service interface of the third network entity to request the identification lengths. The third network entity can determine the L kinds of identification lengths according to the request of the first network entity. In one possible implementation, the L kinds of identification lengths are relatively local length types, such as applicable to the first service or a service requestor of the first service. In this case, the third network entity can select the identification lengths related to the first service or the service requestor of the first service from global length types according to the request of the first network entity, that is, the L kinds of identification lengths. For example, the global length types are 8 kinds of identification lengths, and the identification lengths related to the service requestor are the first to third kinds of identification lengths among them. Alternatively, the L kinds of identification lengths are relatively global length types, and the third network entity can obtain the global length types, that is, the L kinds of identification lengths, by default according to the request of the first network entity. Then, the third network entity can send the L kinds of identification lengths to the first network entity. Alternatively, the service request can also contain the L kinds of identification lengths, that is, the L kinds of identification lengths can be pre-configured by the second network entity, and the service request is delivered to the first network entity. In this case, the first network entity can obtain the L kinds of identification lengths from the service request to reduce the interaction overhead between network elements / entities.

[0213] Case 2, pre-configuration or default:

[0214] The L kinds of identification lengths can also be the default identification lengths of the first network entity, that is, the first network entity can pre-configure or protocol-predefine the L kinds of identification lengths. If the first network entity determines that there can be multiple lengths of device identification according to the service request, the first network entity can obtain the L kinds of identification lengths locally without obtaining them from signaling or other network elements / entities to further reduce the overhead.

[0215] The first network entity can select K kinds of identification lengths from the L kinds of identification lengths as the lengths that the reported identification needs to meet according to actual needs. For example, if the kinds of identification lengths are relatively large, that is, L is large, the first network entity can select part of the kinds of identification lengths as the lengths that the reported identification needs to meet each time, such as L = 8, and 4 lengths are selected this time, that is, K = 4, that is, batch reporting, to reduce the overhead of each reporting. Conversely, the first network entity can select all kinds of identification lengths as the lengths that the reported identification needs to meet this time, that is, one-time reporting, to reduce the overall time delay of the service process.

[0216] The length interval refers to an interval in which the length of the terminal identifier, or the device identifier, is located.

[0217] For any length interval of the N length intervals, the length interval can be represented by the quantized length value, such as [Lmin, Lmax], or (Lmin, Lmax], or [Lmin, Lmax), or (Lmin, Lmax). Lmin and Lmax are end point values, which can be a specific number of bits, or can also be a number of length units, which can be referred to in the above description of the length of the identifier, and will not be described here. Alternatively, the length interval can also be represented by an index, such as index0 = 000, indicating that the length interval is [16 bits, 24 bits], index1 = 001, indicating that the length interval is (24 bits, 36 bits], and so on. For details, please refer to the above description of the length of the identifier, and will not be described here. In addition, the interval open or closed form of the length interval is not limited, and the minimum value or the maximum value of the length of the identifier can be a closed interval, such as L1 as the minimum value and L2 as the maximum value, which can be divided into two length intervals, represented as [L1, Ln1], (Ln1, L2] or also represented as [L1, Ln1), [Ln1, L2], which can be divided into three length intervals, represented as [L1, Ln1], (Ln1, Ln2], (Ln2, L2] or also represented as [L1, Ln1), [Ln1, Ln2), [Ln2, L2], and so on, where Ln1 and Ln2 are between L1 and L2.

[0218] The N length intervals can include S length intervals, or the N length intervals include the same length and / or different length intervals, a total of S intervals, S being a positive integer. For example, the N length intervals are three, the first length interval is [L1, Ln1), the second length interval is [L1, Ln1], and the third length interval is (Ln1, L2], that is, the first length interval and the second length interval are the same, so the three length intervals include [L1, Ln1] and (Ln1, L2] these two intervals. For example, the N length intervals are three, the first length interval is [L1, Ln1), the second length interval is [Ln1, Ln2), and the third length interval is [Ln2, L2], so the three length intervals include [L1, Ln1), [Ln1, Ln2) and [Ln2, L2] these three intervals.

[0219] S length intervals can belong to T length intervals, T is an integer greater than or equal to S, that is, T length intervals can be understood as a union set of different intervals, and S length intervals can be understood as a subset in the union set. The T length intervals can be defaulted by the first network entity, or can also be dynamically obtained by the first network entity, and the specific implementation manner is similar to the above-mentioned L identification length, which can be understood with reference, and will not be repeated here. Alternatively, the T length intervals can also be determined according to the L identification length, for example, any two identification lengths in the L identification length are taken as end point values to determine the T length intervals.

[0220] Optionally, the first information can also include a reporting length. The reporting length can be a unique reporting length applicable to the M identification lengths and / or the N length intervals. Alternatively, the reporting length can also be a reporting length corresponding to each of the M identification lengths and / or the N length intervals, which can be the same or different. For example, for the same identification length, the corresponding reporting length is usually the same, and vice versa, the corresponding reporting length is usually different. Similarly, for the same length interval, the corresponding reporting length is usually the same, and vice versa, the corresponding reporting length is usually different. The reporting length corresponding to each length interval is usually located in the length interval. For the identification length matched with a certain length interval, such as the identification length located in the length interval, the reporting length corresponding to the length interval and the identification length can be the same, for example, the identification lengths are 24 bits and 36 bits respectively, and are located in the length interval of 0 to 50 bits, and the corresponding reporting length can be 30 bits. In addition, similar to the above-mentioned identification length, the reporting length can also be represented by the quantized length value or by the index, which can be understood with reference to the related introduction of the identification length, and will not be repeated here. In addition, the first network entity obtains the reporting length in a manner similar to the above-mentioned obtaining of the identification length or the length interval, such as being provided by the second network entity, or being obtained from the third network entity, or being determined by the first network entity itself, which can be understood with reference, and will not be repeated here.

[0221] The first information can be carried in a mask, that is, multiplexing an existing information element to deliver the first information, to reduce the implementation difficulty, or can also be independently delivered, decoupled from the existing information element, and the information delivery is more flexible. Optionally, the mask can also include at least one of the identification type information (denoted as identification type information #2) or the identification description information (denoted as identification description information #2).

[0222] The identification type information #2 can be determined according to the identification type information #1 described above, such as the first network entity determining the identification type information #1 as the identification type information #2, or selecting part of the identification type indicated by the identification type information #1 as the identification type indicated by the identification type information #2, which can also be one or more of the following four identification types: an operator network assigned identification, a non-operator network assigned identification, a product electronic identification, or a non-product electronic identification, to realize ordered reporting by length and / or by type; or the identification type information #2 can also be determined by the first network entity itself, such as deciding by itself what type of identification to inventory this time and carrying it into the mask; or the identification type information #2 can also be determined according to the identification of the service requester. Exemplarily, the operator network (such as the third network entity or the first network entity locally) stores a correspondence between the identification of the service requester and the identification type. The first network entity can determine the identification type information #2 corresponding to the identification of the service requester according to the identification of the service requester and the correspondence, and carry it into the mask. The contents indicated by different identification type information #2 can be different, and the implementation of each identification type information #2 is similar and will not be repeated.

[0223] The identification description information #2 can indicate a specific value in the device identification, or a part of the identification that needs to be matched. The identification description information #2 can also be determined according to the identification description information #1 described above, such as the first network entity determining the identification description information #1 as the identification description information #2, or the first network entity selecting part of the information contained in the identification description information #1 as the identification description information #2, such as the identification description information #1 containing the specific value of the xth bit of the device identification or the specific value of the xth bit to the yth bit, and the first network entity selecting the specific value of the xth bit to the yth bit as the identification description information #2. The identification description information #2 can have one or more, and the contents indicated by different identification description information #2 can be different, and the implementation of each identification description information #2 is similar and will not be repeated.

[0224] For example, an exemplary structure of the mask can be as shown in Table 1.

[0225] Table 1

[0226] As shown in Table 1, the mask can specifically include at least one of the first information, the length field, the offset field, and the value field. In the mask, the first information can be a 12 / 16 / 24-bit information element, or can also be an information element of other bit number; the first information can be carried as an independent information element, or can also be encapsulated into other information elements of the mask, and the specific implementation manner is not limited. The length field and the offset field can be information elements of the same bit number, such as 8-bit information elements, or can also be information elements of different bit numbers, and the limitation is not made. The value field can be a 256-bit information element, or can also have other values, and the limitation is not made. At least one of the length field, the value field, and the offset field can be used to represent the identification description information #2 or the identification type information #2.

[0227] For example, for the identification description information #2, taking the length field #1, the offset field #1, and the value field #1 as an example:

[0228] The length field #1 can indicate the length corresponding to the value field #1. For example, when the value field #1 represents a value 3, if the length field #1 indicates a length of 3 bits, the value field #1 can represent the identification description information #2 as 011 through 3 bits; if the length field #1 indicates a length of 5 bits, the value field #1 can represent the identification description information #2 as 00011 through 5 bits. If the mask does not include the length field #1, the value field #1 can be a specific form of bit, such as a bit string, for example, 011 or 00011, to represent the identification description information #2. The offset field #1 can indicate that the value field #1 (or the identification description information #2) is the bit at the starting position of the device identification, or the offset compared to the highest bit. Similarly, if the mask includes multiple identification description information #2, it can also be represented by the length field #2, the offset field #2, and the value field #2, and the length field #3, the offset field #3, and the value field #3 (not shown in Table 1), and the principle is similar, which will not be repeated here.

[0229] For example, for the identification type information #2, still taking the length field #1, the offset field #1, and the value field #1 as an example:

[0230] When there are 4 device identification type, the identification type information #2 can be one of them. The length field #1 can indicate 2 bits length, and the value field #1 is 2 bits, such as 00 indicates value 0, i.e. the identification type information #2 is the 1st device identification type, 01 indicates value 1, i.e. the identification type information #2 is the 2nd device identification type, 10 indicates value 2, i.e. the identification type information #2 is the 3rd device identification type, and 11 indicates value 3, i.e. the identification type information #2 is the 4th device identification type. In addition, when the device identification also contains the identification type information #2 (which can be referred to in the following description), the offset field #1 can indicate the value field #1 (or the identification type information #2) is at the starting position of the device identification for the first several bits, or the offset compared to the highest bit. In this case, it can also be considered that the identification description information #2 also includes the identification type information #2, i.e. the specific value contained in the identification description information #2 can implicitly indicate the identification type information #2. Similarly, if the mask includes multiple identification type information #2, it can also be represented by the length field #2, the offset field #2 and the value field #2, and the length field #3, the offset field #3 and the value field #3 (not shown in Table 1), and the principle is similar, which will not be repeated here.

[0231] It should be understood that if there is only one identification type information #2 or identification description information #2, there can be no length field #2, offset field #2 and value field #2. In addition, the mask can be optional information, and when the mask is not provided, it can be indicated as any terminal (or all terminals). Or the identification type information #2 and / or identification description information #2 contained in the mask does not indicate the value, or indicates the value as any value, which can also indicate any terminal (or all terminals).

[0232] It should also be understood that the mask is an example of a name, which can also be replaced by any other possible name, such as a paging identifier, a paging code, etc., which is not limited in particular.

[0233] For the first network entity, if the first network entity is a core network element, such as an A-IoT MF, and the access network device supports the function of the reader, or in other words, as a reader, the core network element can send a mask to the access network device, which is forwarded by the access network device, such as carrying the mask in the selection message and / or the paging message, or any other possible message, and then broadcasted. Alternatively, if the first network entity is a core network element, and the terminal device supports the function of the reader, or in other words, as a reader, the core network element can first send a mask to the access network device, which is forwarded to the terminal device by the access network device, and the terminal device carries the mask in the selection message and / or the paging message, or any other possible message, and then broadcasted. If the first network entity is an access network device supporting the function of the reader, the access network device can directly broadcast the mask, such as broadcasting the selection message and / or the paging message carrying the mask, or any other possible message, without limitation to the specific message type. Of course, the first information can also not be carried in the mask, such as the first network entity can send the first information separately, and the sending manner can be referred to the above-mentioned mask type for understanding, and will not be described again. In this case, the first network entity can still send the mask, or not send the mask, without limitation. Correspondingly, the first terminal can receive the first information, such as receiving the mask and obtaining the first information from the mask, or receiving the first information separately. The first terminal is a terminal satisfying the above-mentioned preset condition.

[0234] S602, the first terminal sends the first identifier of the first terminal according to the first information. Correspondingly, the first network entity receives the first identifier of the first terminal.

[0235] The first identifier can be an identifier reported by the first terminal. If the information contained in the first information is different, the implementation of the first identifier is also correspondingly different, which will be introduced in the following cases.

[0236] Case 1: The first information includes M identifier lengths.

[0237] The length of the first identifier can satisfy a preset rule with the first identifier length in the M identifier lengths, such as satisfying the preset rule can include that the length of the first identifier is the same as the first identifier length, or the length of the first identifier is determined according to the second identifier of the first terminal, and the length of the second identifier is the same as the first identifier length. The second identifier can be an identifier of the first terminal, which is used to uniquely identify the first terminal. As shown in Table 2 below, the second identifier can include one or more of the following parts.

[0238] Table 2

[0239] In the above-mentioned Table 2:

[0240] 1) The sequence (or entity / instance) can be used to identify the first terminal, i.e. the second identity can identify the first terminal through the sequence contained therein, such as at least one of continuous characters, character strings, numbers, arrays, codes, etc. If the second identity is an identity allocated by an operator network, since the identity of the public land mobile network (PLMN) of the operator network (PLMN ID) itself can distinguish different operator networks, the operator network only needs to ensure that the sequence is unique within the operator network when allocating the sequence, so as to shorten the length of the sequence. If the second identity is a product electronic identity, it can be impossible to distinguish different operator networks due to the special value of the home network identity (see below), and the third party organization needs to ensure that the sequence is globally unique when allocating the sequence.

[0241] 2) The home network identity can represent the network that manages the first terminal or allocates the terminal identity of the first terminal, such as the network that performs identity verification, security authentication, etc. on the first terminal, and the network saves the subscription data, information, or security parameters such as secret keys, etc. of the first terminal. The home network identity can be a PLMN ID, such as a mobile country code (MCC) and a mobile network code (MNC). If the second identity is not an identity allocated by an operator, or in other words, is not an identity allocated by an operator, such as an identity allocated by a third party organization, such as an EPC, the home network identity can be a special value, i.e. does not represent any specific network or operator, such as 999999, or any other possible value, to indicate that the second identity is not allocated by an operator. In addition, the home network identity is optional, and the second identity can also not contain this information.

[0242] 3) The device identity length can be used to indicate the length of the second identity, and the device identity length can also be represented by a quantized length value or by an index. For details, please refer to the above description of the identity length, which will not be repeated here. The device identity length can be part of the second identity or stored independently of the second identity. Alternatively, the device identity length can also be dynamically calculated, and there is no need to store this information. For details, please refer to the relevant description below, which will not be repeated here. In addition, the device identity length is optional, and the second identity can also not contain this information.

[0243] 4) identification type information (denoted as identification type information #3), such as IsEPC, which can represent the type of the sequence. The identification type information can indicate whether it is an operator-allocated identifier or a third-party-allocated identifier, such as whether it is constructed based on an electronic product code (EPC). If the sequence is constructed based on an EPC or is a third-party-allocated identifier or a non-operator-allocated identifier, the identification type information can be set to 1, and if the sequence is not constructed based on an EPC or is an operator-allocated identifier or is not a third-party-allocated identifier, the identification type information can be set to 0, or vice versa. Alternatively, the identification type information #3 can also be implemented instead of the identification type information #2 described above. The identification type information is optional, for example, if the sequence is a non-operator-network-allocated identifier, the home network identifier being a special value can also implicitly indicate that the sequence is a third-party-allocated identifier, or is constructed based on an EPC, and thus the second identifier can not contain the identification type information. However, for the scenario where the operator network manages the first terminal, the operator-network-allocated identifier (such as the sequence described above) can also be a third-party-allocated identifier, or be constructed based on an EPC. In this case, the home network identifier being a special value cannot represent whether it is a third-party-allocated identifier, or is constructed based on an EPC, and thus needs to be indicated by the identification type information.

[0244] On this basis, if the first information does not include the reporting length, the first terminal can determine that the length of the second identifier is the same as a certain identifier length in the M identifier lengths. For example, the first terminal can obtain the device identifier length from the second identifier, or obtain the device identifier length from other storage areas, or determine the device identifier length according to the address of the second identifier in the storage area. The address of the storage area can be pre-configured in the first terminal or provided by the first network entity, such as the start address and the end address. If the length unit described above is a bit, the end address is set as addr1, the start address is set as addr2, addr1-addr2=Δaddr, and the number of bits contained in Δaddr is the device identifier length. If the length unit described above is a word or a byte, the end address is set as addr1, the start address is set as addr2, addr1-addr2=Δaddr, and the number of bits contained in Δaddr divided by the number of bits contained in a word or a byte is the device identifier length. The first terminal can determine whether the device identifier length is the same as a certain identifier length in the M identifier lengths. If the device identifier length is the same as the first identifier length, the first terminal reports the second identifier as the first identifier, i.e., the second identifier and the first identifier are the same identifier.

[0245] If the first information further comprises a report length, the first terminal can further determine the length relationship between the length of the second identity and the report length, in the case that the length of the second identity is determined to be the same as the length of the first identity.

[0246] For example, if the length of the second identity is greater than the report length, the first terminal can truncate the second identity to the report length to obtain the first identity. The truncation can be in a forward-to-backward order or in a backward-to-forward order. For example, if the length of the second identity is 120 bits and the report length is 96 bits, the first terminal can remove the last 24 bits or the first 24 bits of the second identity to obtain the first identity. Alternatively, the truncation can be from the middle, such as truncating the part before the xth bit and the part after the yth bit of the second identity, and the specific manner is not limited, or other manners can also be used, for example, the first x1 bits after the part indicated by the mask in the second identity are taken as the first identity, and x1 is the report length.

[0247] For another example, if the length of the second identity is less than the report length, the first terminal can pad the second identity to the report length to obtain the first identity. The padding can be padding bits of 0 / 1 at the end of the second identity, for example, if the length of the second identity is 70 bits and the report length is 96 bits, the first terminal can pad 26 bits of 0 at the end of the 70 bits to obtain the first identity.

[0248] For example, for the padding after the end, whether the second identity specifically pads bit 0 or bit 1 can be determined according to the bit value of the last character in the second identity. If the bit value of the last character in the second identity is 0, bit 1 is padded, and if the bit value of the last character in the second identity is 1, bit 0 is padded. Similarly, for the padding before the first, whether the second identity specifically pads bit 0 or bit 1 can be determined according to the bit value of the first character in the second identity. If the bit value of the first character in the second identity is 0, bit 1 is padded, and if the bit value of the first character in the second identity is 1, bit 0 is padded. That is, the difference in bit value indicates that the subsequent bit 1 is the padding part, so that the network side can correctly identify the padding part in the first identity and obtain the second identity.

[0249] For another example, if the length of the second identity is equal to the report length, the second identity and the first identity are the same identity.

[0250] Case 2: The first information comprises N length intervals.

[0251] The length of the second identity can be in the first length interval of the N length intervals.

[0252] For example, if the first information does not include the report length, the first terminal can determine that the length of the second identifier is located in the first length interval, and report the second identifier as the first identifier, i.e., the second identifier is the same as the first identifier.

[0253] For another example, if the first information further includes the report length corresponding to each of the N length intervals, in the case that the first terminal determines that the length of the second identifier is located in the first length interval, the first terminal can further determine the length relationship between the length of the second identifier and the report length. If the length of the second identifier is greater than the report length, the first terminal can truncate the second identifier to the report length to obtain the first identifier. If the length of the second identifier is less than the report length, the first terminal can pad the second identifier to the report length to obtain the first identifier. If the length of the second identifier is equal to the report length corresponding to the first length interval, the second identifier is the same as the first identifier. The specific implementation of truncation and padding can also refer to the related description of case 1 above, and will not be described here.

[0254] In addition, case 1 and case 2 above can also be combined for implementation. For example, the first information includes M identifier lengths and N length intervals, and the first terminal needs to determine whether the length of the second identifier meets the same as one of the M identifier lengths, and whether the length of the second identifier meets located in one of the N length intervals. If these conditions are met, the first terminal reports the second identifier as the first identifier, otherwise, no report is made. Optionally, if the first information further includes the report length, in the case that the above conditions are met, the first terminal further truncates / pads / does not process the second identifier according to the report length to obtain the first identifier, and then reports the first identifier.

[0255] It can be seen that the first identifier described above can be an identifier directly reported by the first terminal, or can be an identifier reported after processing, which can be selected flexibly according to the implementation. For example, if the types of identifier lengths are less, the network (such as the first network entity) can select the direct reporting mode, otherwise, the network can select the reporting mode after processing, such as truncating / padding to the same report length and then reporting, to improve the execution efficiency of the business process.

[0256] Optionally, if the mask further includes identification type information #2, the first terminal further determines whether the type of the first identification matches (or is the same as) the identification type indicated by the identification type information #2. For example, if the identification type is a product electronic identification, and the type of the first identification / second identification is also a product electronic identification, it is considered to match, and the first terminal reports the first identification, otherwise, it does not report. Similarly, if the mask further includes identification description information #2, the first terminal further determines whether the second identification contains a specific value indicated by the identification description information #2. For example, if the specific value is that the xth to yth bits of the device identification are 1011, and the xth to yth bits of the second identification are also 1011, it is considered to match, and the first terminal reports the first identification, otherwise, it does not report.

[0257] If the first network entity is a core network element, such as an A-IoTMF, and the access network device supports the function of a reader, or in other words, acts as a reader, the first terminal can send the first identification to the access network device, which forwards it to the core network element. Alternatively, if the first network entity is a core network element, and the terminal device supports the function of a reader, or in other words, acts as a reader, the first terminal can first send the first identification to the terminal device, which forwards it to the access network device, which then forwards it to the core network element. If the first network entity is an access network device that supports the function of a reader, the first terminal can directly send the first identification to the access network device. The first identification can be carried in any possible message, which can be an existing message or a newly defined message, and the specific naming or type is not limited.

[0258] In summary, the first network entity can specify the identification length and / or length interval by sending the first information. If the first terminal determines that the length of its own device identification meets the preset rule and / or is located in the length interval after receiving the first information, the first terminal can report its own device identification, such as the first identification, otherwise, it does not report, to achieve batched and orderly reporting, so that the network side can still ensure the efficiency of the business process for device identifications of different lengths. In addition, since the length of the first identification reported by the first terminal is determined, the network side can allocate corresponding transmission resources according to the length of the first identification, improve resource utilization, and does not need to rely on a tail pilot frequency to determine which bit the first identification ends at, so it can be applied to a wireless communication system.

[0259] Optionally, in combination with the above S601-S602, the method further includes that the first network entity sends second information.

[0260] The second information includes P identification lengths and / or Q length intervals, and P and Q are positive integers.

[0261] P pieces of identification lengths are different from M pieces of identification lengths, and the identification length types contained in the P pieces of identification lengths belong to L pieces of identification lengths. Q pieces of length intervals are different from N pieces of length intervals, and the different intervals contained in the Q pieces of length intervals also belong to T pieces of length intervals, so as to realize batch reporting. For example, L pieces of identification lengths are 4, and M pieces of identification lengths include the first 2 / 3 pieces of identification lengths, and P pieces of identification lengths include the last 2 / 3 pieces of identification lengths. For another example, T pieces of length intervals are 4, and N pieces of length intervals include the first 2 / 3 pieces of length intervals, and Q pieces of length intervals include the last 2 / 3 pieces of length intervals.

[0262] The first information and the second information can be carried in the same message. For example, the first network entity is a core network element, and the core network element can send a message to a reader (such as an access network device or a terminal device supporting a reader function), which can include a task identification allocated by the core network element, and the first information and the second information. The access network device sends the first information and the second information in batches, such as sending the first information and the second information in different random access procedures. Alternatively, the first information and the second information can also be carried in different messages. For example, the first network entity is a core network element, and the core network element can send the first information and the second information to the reader (such as an access network device or a terminal device supporting a reader function) through different messages, respectively. The different messages can also carry different task identifications allocated by the core network element, respectively, and be forwarded to the corresponding terminal by the reader.

[0263] In addition, the terminal receiving the second information, such as the second terminal, reports the identification in a similar manner to the first terminal, which can be understood by reference, and will not be described here.

[0264] It should be understood that in the method shown in the above FIG. 6, the first network entity can also be replaced by a terminal device supporting a reader function. The method shown in FIG. 6 is only an example. For example, the first information can also be replaced by a reporting length, that is, the first network entity can issue a reporting length to indicate reporting the device identification according to the reporting length. The first terminal fills or truncates its own device identification to the reporting length according to the reporting length, and then reports.

[0265] The above describes the arrangement process of the communication method provided by the embodiments of the present application in combination with FIG. 6. The specific process of the communication method provided by the embodiments of the present application will be described in detail in combination with FIGS. 7-8.

[0266] FIG. 7 is a flowchart of a communication method provided by an embodiment of the present application. As shown in FIG. 7, the flowchart involves an AF (such as a second network entity), a NEF network element, a UDM / UDR network element (such as a third network entity), an A-IoT MF network element (such as a first network entity), a reader, an A-IoT device #1 (such as a first terminal), and an A-IoT device #2 (such as a second terminal).

[0267] Specifically, as shown in FIG. 7, the flow of the communication method is as follows:

[0268] S700a, the UDM / UDR network element preconfigures an identifier length and / or a length interval.

[0269] The identifier length preconfigured by the UDM / UDR network element can be the L identifier lengths described above, and the length interval can be the S length intervals described above. For details, refer to the related description in S601 above, which will not be repeated here. Alternatively, the UDM / UDR network element can also preconfigure a length interval. For details, refer to the related description in S601 above, which will not be repeated here.

[0270] It should be understood that S700a is optional, and the L identifier lengths and / or the S length intervals can also be carried in the service request described below.

[0271] S700b, the A-IoT device #1 preconfigures the device identifier length of the A-IoT device #1.

[0272] The identifier length of the A-IoT device #1 can be the length of the device identifier #1 (such as the second identifier described above) of the A-IoT device #1.

[0273] S700c, the A-IoT device #2 preconfigures the device identifier length of the A-IoT device #2.

[0274] The device identifier length of the A-IoT device #2 can be the length of the device identifier #A of the A-IoT device #2.

[0275] It should be understood that S700c is optional, and the embodiments of the present application can only involve the A-IoT device #1 without the A-IoT device #2.

[0276] S701, the AF sends a service request #1 to the NEF network element.

[0277] The service request #1 can indicate performing a first service, such as an inventory service, on a terminal that meets a preset condition.

[0278] The service request #1 can include at least one of the following: a service request party identifier, such as an AF ID, a type of the first service, such as an inventory service, information of the first service, such as an identifier of the inventory service, information indicating a region, identifier type information #1, or identifier description information #1. Optionally, it can also include the L identifier lengths and / or the S length intervals, and optionally, include a reporting length. For details, refer to the related description of the service request in FIG. 6 above, which will not be repeated here.

[0279] S702, the NEF network element sends a service request #2 to the A-IoTMF network element.

[0280] Wherein, the service request #2 can be the same message as the service request #1, or can also be a different message, without limitation, if the service request #2 is a different message from the service request #1, the service request #2 also contains the content in the service request #1, that is, the NEF network element obtains the content in the service request #1, and then carries it into the service request #2.

[0281] In an implementation manner, the AF can send the service request #1 to the AIoT MF (for example, when the AF is trusted).

[0282] S703, the A-IoT MF network element determines that batch inventory is needed.

[0283] The A-IoT MF network element can determine that there can be multiple identification lengths according to the terminal of the preset condition being a non-deterministic terminal, and thus determine that batch inventory is needed, that is, inventory is performed according to different identification lengths. In a possible implementation manner, batch inventory can be understood as splitting the service operation corresponding to the service request #1 into several processes to complete, or splitting into several tasks to complete. For example, inventory request is sent to the reader multiple times, and each inventory request performs an inventory process for different A-IoT devices. Wherein, in the multiple inventory processes, different A-IoT devices can be distinguished by different device identification lengths.

[0284] S704, the A-IoT MF network element obtains L identification lengths and / or S length intervals from the UDM / UDR network element.

[0285] Wherein, S704 is optional, if the L identification lengths and / or S length intervals are carried in the service request #2, the A-IoT MF network element can also obtain the L identification lengths and / or S length intervals from the service request #2, and S704 can also refer to the related introduction in S601 described above, which will not be repeated here.

[0286] Optionally, the A-IoT MF network element can also obtain the reporting length from the UDM / UDR network element or the service request #2.

[0287] S705, the A-IoT MF network element sends inventory #1 to the reader.

[0288] The inventory #1 can also be referred to as inventory message #1, or inventory indication #1, or any other possible naming, without limitation.

[0289] The inventory #1 can contain at least one of the following: task identification #1 (task ID1), identification length #1 and / or length interval #1, mask #1.

[0290] The task identifier #1 can be an identifier assigned by the A-IoT MF network element for the batch inventory, such as assigning the first round of inventory as a task, such as task #1, and assigning a task identifier #1 for the task #1 to indicate the task #1. Or the task identifier #1 can be an identifier assigned by the NEF according to the service request #1 sent by the AF. The task identifier #1 can also be referred to as a transaction ID or other names, and the present application does not limit the name of the task identifier. Information that can be used to identify the service operation or process performed for the service request #1 can also be used as the task identifier. The identifier length #1 can be one of L identifier lengths, and the length interval #1 can be one of S length intervals. The identifier length #1 and / or the length interval #1 can be understood as the first information described above, and specific reference can be made to the related description of the first information above, which will not be repeated. The identifier length #1 can be carried in the mask #1, or can be an independent information element other than the mask #1. The mask #1 can refer to the related description of the mask above, which will not be repeated.

[0291] Optionally, if the A-IoT MF network element obtains the reporting length in S703, the inventory #1 can also include the reporting length.

[0292] S706, the reader sends a selection message #1 or a paging message #1.

[0293] The selection message #1 or the paging message #1 can carry the identifier length #1 and / or the length interval #1, and the mask #1, and optionally can also include the reporting length.

[0294] S707, the A-IoT device #1 determines that the device identifier length matches.

[0295] Optionally, if the reader sends the identifier length #1 and / or the length interval #1 in S706 (such as an independent information element or carried in the mask #1), the A-IoT device #1 can determine whether the device identifier length of the A-IoT device #1 is the same as the identifier length #1, and / or whether the device identifier length of the A-IoT device #1 is located within the length interval #1. If yes, the A-IoT device #1 determines that the device identifier length matches, otherwise, the A-IoT device #1 determines that the device identifier length does not match, or determines not to continue to execute the subsequent steps.

[0296] Optionally, if the message #1 or the paging message #1 contains the reporting length, the A-IoT device #1, in the case that the device identity length matches, can further determine the size relationship between the device identity length and the reporting length. If the A-IoT device #1 determines that the device identity length is greater than the reporting length, the A-IoT device #1 can truncate the device identity #1 (i.e., the second identity) to the reporting length to obtain the device identity #2 (i.e., the first identity). If the A-IoT device #1 determines that the device identity length is less than the reporting length, the A-IoT device #1 can pad the device identity #1 to the reporting length to obtain the device identity #2. If the A-IoT device #1 determines that the device identity length is equal to the reporting length, the A-IoT device #1 can not process, and the device identity #1 is the device identity #2.

[0297] It can be understood that the device identity #1 can refer to the related description of the second identity described above, and the device identity #2 can refer to the related description of the first identity described above, which will not be described here.

[0298] In the case that the device identity length matches, the A-IoT device #1 performs random access, such as performing S708.

[0299] Optionally, if the reader sends the mask #1 in step S706, the A-IoT device #1, in the case that the device identity #1 matches the mask #1, performs random access, such as performing S708.

[0300] Optionally, if the reader sends the identity length #1 and / or the length interval #1, and the mask #1 in step S706, the A-IoT device #1, in the case that the device identity length matches and the device identity #1 matches the mask #1, performs random access, such as performing S708.

[0301] S708, the A-IoT device #1 sends the device identity #2.

[0302] In one possible implementation, the A-IoT device #1 sends the device identity #2 to the reader, and the reader sends the device identity #2 to the A-IoT MF network element.

[0303] In another possible implementation, the A-IoT device #1 sends the UL NAS message #1 (through the reader) to the A-IoT MF network element. The UL NAS message #1 can carry the device identity #2.

[0304] S709, the A-IoT MF network element performs verification on the device identity #2.

[0305] The A-IoTMF network element can check the device identifier #2 for whether its length matches, whether its content is complete, whether the device identifier #2 is a valid device identifier, and the like. In addition, S709 is an optional step, and the A-IoTMF network element can also not perform the check or perform other operations, and the specific operations are not limited.

[0306] It can be understood that the A-IoT device #1 can have one or more, that is, the above S705-S709 process can be applied to the A-IoT device whose device identifier length is the same as the identifier length #1 and / or whose device identifier length is in the length interval #1.

[0307] S710, the A-IoTMF network element sends the inventory #2 to the reader.

[0308] Similar to the inventory #1, the inventory #2 can also be referred to as an inventory message #2, or an inventory indication #2, or any other possible name, and the specific operations are not limited. The inventory #2 can include at least one of the following: a task identifier #2, a device identifier length #2 and / or a length interval #2, and a mask #2.

[0309] The task identifier #2 can be an identifier allocated by the A-IoTMF network element for batch inventory, such as taking the second round of inventory as a task, such as task #2, and allocating a task identifier #2 for indicating the task #2 for the task #2. Or the task identifier #2 can be an identifier allocated by the NEF according to the service request #2 sent by the AF. The task identifier #2 can also be referred to as a transaction identifier or other names, and the present application does not limit the name of the task identifier. Information that can be used to identify the service operation or process performed for the service request #2 can also be used as the task identifier. The device identifier length #2 can also be one of L identifier lengths, and can be different from the identifier length #1. The length interval #2 can also be one of S length intervals, and can also be different from the length interval #1. The identifier length #1 and / or the length interval #1 can be understood as the second information described above, and the specific principle is similar to that of the first information described above, and can be understood by referring to the above description, and will not be repeated. The device identifier length #2 can be carried in the mask #2, or can be an independent information element other than the mask #2. The implementation principle of the mask #2 is similar to that of the mask #1, and can also be referred to the above description of the mask, and will not be repeated.

[0310] Optionally, if the A-IoTMF network element obtains the reporting length in S703, the inventory #2 can also include the reporting length.

[0311] S711, the reader sends a selection message #2 or a paging message #2.

[0312] The selection message #2 or the paging message #2 can carry the identification length #2 and / or the length interval #2, and the mask #1, and optionally contain the report length.

[0313] S712, the A-IoT device #2 determines that the device identification length matches.

[0314] Optionally, if the reader sends the identification length #2 and / or the length interval #2 in S711 (such as being carried in the mask #2 or as an independent information element), the A-IoT device #2 can determine whether the device identification length of the A-IoT device #2 is the same as the device identification length #2, and / or whether the device identification length of the A-IoT device #2 is within the length interval #2. If yes, the A-IoT device #2 determines that the device identification length matches, otherwise the A-IoT device #2 determines that the device identification length does not match, or determines not to continue the subsequent steps.

[0315] Optionally, if the selection message #2 or the paging message #2 further contains the report length, the A-IoT device #2, in the case of determining that the device identification length matches, can further determine the size relationship between the device identification length and the report length. If the A-IoT device #2 determines that the device identification length is greater than the report length, the A-IoT device #2 can truncate the device identification #A to the report length to obtain the device identification #B. If the A-IoT device #2 determines that the device identification length is less than the report length, the A-IoT device #2 can pad the device identification #A to the report length to obtain the device identification #B. If the A-IoT device #2 determines that the device identification length is equal to the report length, the A-IoT device #2 can not process, and the device identification #A is the device identification #B.

[0316] It can be understood that the device identification #A can refer to the above description of the second identification, and the device identification #B can also refer to the above description of the first identification, which will not be repeated here.

[0317] In the case of the device identification length matching, the A-IoT device #2 performs random access, such as performing S713.

[0318] Optionally, if the reader sends the mask #2 in step S711, the A-IoT device #2, in the case of the device identification #2 matching the mask #2, performs random access, such as performing S713.

[0319] Optionally, if the reader sends the identification length #2 and / or the length interval #2, and the mask #2 in step S711, the A-IoT device #2, in the case of the device identification length matching and the device identification #2 matching the mask #2, performs random access, such as performing S713.

[0320] S713, the A-IoT device #2 sends the device identity #B.

[0321] In a possible implementation, the A-IoT device #2 sends the device identity #B to the reader, and the reader sends the device identity #B to the A-IoT MF network element.

[0322] In another possible implementation, the A-IoT device #2 sends an UL NAS message #B to the A-IoT MF network element (through the reader). The UL NAS message #2 can carry the device identity #B.

[0323] S714, the A-IoT MF network element performs a check on the device identity #B.

[0324] The check of the A-IoT MF network element on the device identity #B can be a check on whether the length matches, the content is complete, the device identity #2 is a valid device identity, and the like. In addition, S714 is an optional step, and the A-IoT MF network element can also not perform the check, or perform other operations, which are not limited in particular.

[0325] It can be understood that the A-IoT device #2 can also have one or more, that is, the above S710-S714 process can be applied to the A-IoT device whose device identity length is the same as the device identity length #2, and / or whose device identity length is in the length interval #2.

[0326] It can also be understood that S710-S714 is optional, and if there is no A-IoT device #2, S710-S714 is not performed.

[0327] In addition, the above process shown in FIG. 7 takes the A-IoT device #1 and the A-IoT device #2 as examples, but is not limited thereto, and there can be other devices with different lengths, such as the A-IoT device #3, and the like, and the specific principle is similar, which will not be described herein again.

[0328] FIG. 8 is a flow diagram of a communication method provided by an embodiment of the present application. As shown in FIG. 8, the flow involves an AF (such as a second network element), an NEF network element, a UDM / UDR network element (such as a third network element), an A-IoT MF network element (such as a first network element), a reader, an A-IoT device #1 (such as a first terminal), and an A-IoT device #2 (such as a second terminal).

[0329] Specifically, as shown in FIG. 8, the flow of the communication method is as follows:

[0330] S800a, the UDM / UDR network element preconfigures an identity length and / or a length interval.

[0331] S800b, A-IoT device #1 preconfigures the device identification length of A-IoT device #1.

[0332] S800c, A-IoT device #2 preconfigures the device identification length of A-IoT device #2.

[0333] S801, the AF sends a service request #1 to the NEF network element.

[0334] S802, the NEF network element sends a service request #2 to the A-IoT MF network element.

[0335] S803, the A-IoT MF network element obtains L kinds of identification lengths and / or S kinds of length intervals from the UDM / UDR network element.

[0336] Among them, S803 is optional. If the L kinds of identification lengths and / or S kinds of length intervals are carried in the service request #2, the A-IoT MF network element can also obtain the L kinds of identification lengths and / or S kinds of length intervals from the service request #2. S803 can also refer to the related introduction in S601 described above, and will not be repeated here.

[0337] Optionally, the A-IoT MF network element can also obtain the reporting length from the UDM / UDR network element or the service request #2.

[0338] S800a-S803 can refer to the related introduction of S700a-S702 and S704 described above, and will not be repeated here.

[0339] S804, the A-IoT MF network element sends an inventory to the reader.

[0340] The inventory can also be called an inventory message, or an inventory indication, or any other possible naming, which is not limited in particular.

[0341] The inventory can contain at least one of the following: task identification (task ID), K kinds of identification lengths and / or S kinds of length intervals, and a plurality of masks, etc. That is, the difference from S705 and S710 described above is that the A-IoT MF network element can send all the received information to the reader, and the reader can split and execute the distribution inventory. In addition, the information element can also refer to the related introduction of S705 and S710 described above, and will not be repeated here.

[0342] Optionally, if the A-IoT MF network element obtains the reporting length in the service request #2 of S802, the inventory can also contain the reporting length.

[0343] S805, the reader sends a selection message #1 or a paging message #1.

[0344] The selection message #1 or the paging message #1 can carry the identification length #1 and / or the length interval #1, and the mask #1, and optionally contain the reporting length. That is, the reader can select the identification length #1 from the L identification lengths in the inventory, and / or select the length interval #1 from the S length intervals in the inventory, and can also select the mask #1 from the multiple masks in the inventory, and then carry them into the selection message #1 or the paging message #1.

[0345] S806, the A-IoT device #1 determines that the device identification length matches.

[0346] S807, the A-IoT device #1 sends the device identification #2.

[0347] S808, the A-IoT MF network element performs verification on the device identification #2.

[0348] Wherein, S806-S808 can also refer to the related description of S707-S709 described above, and will not be repeated here.

[0349] S809, the reader sends the selection message #2 or the paging message #2.

[0350] The selection message #2 or the paging message #2 can carry the identification length #2 and / or the length interval #2, and the mask #2, and optionally contain the reporting length. That is, the reader can select the identification length #2 from the L identification lengths in the inventory, and / or select the length interval #2 from the S length intervals in the inventory, and can also select the mask #2 from the multiple masks in the inventory, and then carry them into the selection message #2 or the paging message #2.

[0351] S810, the A-IoT device #2 determines that the device identification length matches.

[0352] S811, the A-IoT device #2 sends the device identification #B.

[0353] S812, the A-IoT MF network element performs verification on the device identification #B.

[0354] Wherein, S810-S812 can also refer to the related description of S712-S714 described above, and will not be repeated here.

[0355] In addition, the flowchart shown in the above Figure 8 takes the A-IoT device #1 and the A-IoT device #2 as an example, but is not limited to this, and there can be other identification length devices, such as the A-IoT device #3, and the specific principle is similar, and will not be repeated here.

[0356] Figure 9 is a flowchart of the communication method, which is applicable to the interaction between the first terminal and the reader, as shown in Figure 9, the flowchart of the communication method is as follows:

[0357] S901, the reader acquires the length of the device identity.

[0358] The reader can be the access network device as described above, such as an access network device supporting reader function, or can also be the terminal device as described above, such as a terminal device supporting reader function.

[0359] The length of the device identity can also be referred to as the identity length, or the device identity length, and the specific naming is not limited. The length of the device identity can be measured by the number of length units, and the length unit can be bit, word, byte, etc. For details, please refer to the relevant description of FIG. 6 above, which will not be repeated here.

[0360] The reader can receive the length of the device identity from the core network network element (such as the first network entity described above) for managing the terminal (such as the A-IoT device), such as receiving M kinds of identity lengths, and the length of the device identity is the first identity length among them. For details, please refer to the relevant description of FIG. 6, which will not be repeated here. Alternatively, the reader can receive the length of the device identity from the first terminal (such as the A-IoT terminal described above), that is, the length of the device identity (such as the second identity described above) of the first terminal itself. For example, the length of the device identity can be transmitted together with the RN16 (i.e. 16-bit random number) of the first terminal, or transmitted separately, and the specific implementation is not limited.

[0361] As can be seen, the length of the device identity can be reported by the terminal or provided by the network side, and the specific implementation is not limited, which can be flexibly selected according to the actual situation.

[0362] S902, the reader determines the transmission resource according to the length of the device identity.

[0363] The transmission resource (or wireless resource / wireless transmission resource / air interface resource) can be at least one of a time domain resource, a frequency domain resource, a space domain resource, and the like. The time domain resource can be one or more continuous or discontinuous symbols, slots, mini-slots, subframes, radio frames, and the like. The frequency domain resource can be one or more continuous or discontinuous sub-channels, resource pools, carriers, subcarriers, bandwidth parts (BWPs), and the like. The space domain resource can be one or more continuous or discontinuous space domain vectors, ports, antenna ports, reference signal ports, and the like. The time domain resource and the frequency domain resource can form a resource block (RB) or a resource element (RE), and be layered in the space domain through the space domain resource, that is, the same time-frequency location can multiplex multiple RBs or REs to further improve resource utilization.

[0364] The transmission resource is used to carry the device identifier. The size of the transmission resource matches the length of the device identifier. For example, the length of the device identifier is the number of bits, such as X length units, and X is an integer greater than 1. The size of the transmission resource can be the number of RBs or REs, such as Y RBs or REs, and Y is an integer greater than or equal to 1. The number of length units that Y RBs or REs can carry is X, or slightly more than X, such as 110% of X, 105% of X, and the like, and the specific ratio is not limited. That is, the transmission resource can exactly carry the length of the device identifier to avoid resource waste.

[0365] If the reader is an access network device, the reader can self-allocate the transmission resource. Alternatively, if the reader is a terminal device, the reader can report the length of the device identifier to the access network device to request the access network device to allocate the transmission resource.

[0366] Optionally, in combination with S901-S902, the method can further include that the reader transmits the device identifier of the first terminal on the transmission resource, such as sending the device identifier of the first terminal, or receiving the device identifier of the first terminal from the first terminal. For example, the reader can configure the transmission resource to the first terminal, such as sending configuration information indicating the transmission resource to the first terminal, and the configuration information can include the resource location index of the transmission resource, such as the index of the time domain resource, such as the sequence number of the time slot or symbol, the index of the frequency domain resource, such as the sequence number of the carrier or subcarrier, the index of the space domain resource, such as the antenna port number, etc. In this way, the reader can transmit the device identifier of the first terminal on the transmission resource. In addition, the device identifier of the first terminal can be an existing identifier, or also the first identifier or the second identifier described above, and details can be referred to the related description of FIG. 6 above, which will not be repeated here.

[0367] In summary, for device identifiers of different lengths, the reader can allocate transmission resources matching the length of the device identifier, or in other words, wireless resources, such as for device identifiers with relatively large length, relatively more transmission resources are allocated, and for device identifiers with relatively small length, relatively less transmission resources are allocated, so as to avoid waste of transmission resources and improve communication efficiency.

[0368] FIG. 10 is a flow diagram of a communication method provided by an embodiment of the application. As shown in FIG. 10, the flow involves the interaction between an A-IoT device (such as a first terminal) and a reader.

[0369] Specifically, as shown in FIG. 10, the flow of the communication method is as follows:

[0370] S1000, the A-IoT device pre-configures the length of the device identifier of the A-IoT device.

[0371] S1001, the reader sends a selection message or a paging message.

[0372] S1002, the reader sends a query message or a query repetition message.

[0373] S1001-S1002 can refer to the related description of S201-S202 above, and will not be repeated here.

[0374] S1003, the A-IoT device sends RN16 and the length of the device identifier of the A-IoT device.

[0375] That is, when deciding the random access, the A-IoT device can transmit RN16 and the length of the device identifier of the A-IoT device to the reader.

[0376] S1004, the reader determines the transmission resource.

[0377] The size of the transmission resource matches the length of the device identifier, and details can be referred to the description of S902.

[0378] S1005, the reader returns an acknowledgement message.

[0379] Optionally, the acknowledgement message can contain configuration information indicating the transmission resource.

[0380] S1006, the A-IoT device sends the device identifier of the A-IoT device on the transmission resource.

[0381] S1007, the reader returns a query repetition message.

[0382] Details of S1005-S1007 can be referred to the description of S204-S206.

[0383] FIG. 11 is a structural schematic diagram of a communication apparatus according to an embodiment of the present application. As shown in FIG. 11, the communication apparatus 1100 includes a transceiver module 1102 and a processing module 1101. For the convenience of description, FIG. 11 only shows the main components of the communication apparatus.

[0384] The communication apparatus 1100 can be applied to the communication method shown in FIGS. 6-10 to realize the corresponding functions. For example, the transceiver module 1102 can be used to realize the transceiving function in the communication method shown in FIGS. 6-10, and the processing module 1101 can be used to realize the functions other than the transceiving function in the communication method shown in FIGS. 6-10.

[0385] Optionally, the transceiver module 1102 can include a sending module (not shown in FIG. 11) and a receiving module (not shown in FIG. 11). The sending module is used to realize the sending function of the communication apparatus 1100, and the receiving module is used to realize the receiving function of the communication apparatus 1100.

[0386] Optionally, the communication apparatus 1100 can further include a storage module (not shown in FIG. 11), which stores programs or instructions. When the processing module 1101 executes the programs or instructions, the communication apparatus 1100 can execute the functions in the method shown in FIGS. 5-8.

[0387] It can be understood that the communication apparatus 1100 can be a network device, a chip (system) or other components or assemblies that can be arranged in the network device, or an apparatus containing the network device, and the present application does not limit the same.

[0388] In addition, the technical effects of the communication apparatus 1100 can be referred to the technical effects of the communication method, which will not be repeated here.

[0389] Fig. 12 is a schematic diagram of a structure of a communication apparatus according to an embodiment of the present application. The communication apparatus can be a terminal, a chip (system) or other components or assemblies that can be arranged in the terminal. As shown in Fig. 12, the communication apparatus 1200 can include a processor 1201. Optionally, the communication apparatus 1200 can also include a memory 1202 and / or a transceiver 1203. The processor 1201 is coupled to the memory 1202 and the transceiver 1203, for example, through a communication bus.

[0390] The components of the communication apparatus 1200 will be described in detail below in conjunction with Fig. 12.

[0391] The processor 1201 is the control center of the communication apparatus 1200, which can be one processor or a plurality of processing elements. For example, the processor 1201 can be one or more central processing units (CPUs), application specific integrated circuits (ASICs), or one or more integrated circuits configured to implement one or more of the embodiments of the present application, such as one or more digital signal processors (DSPs), or one or more field programmable gate arrays (FPGAs).

[0392] Optionally, the processor 1201 can perform various functions of the communication apparatus 1200 by running or executing software programs stored in the memory 1202 and by calling data stored in the memory 1202, such as the communication methods shown in Figs. 6-10.

[0393] In a specific implementation, as an embodiment, the processor 1201 can include one or more CPUs, such as CPU0 and CPU1 shown in Fig. 12.

[0394] In a specific implementation, as an embodiment, the communication apparatus 1200 can also include a plurality of processors, such as the processor 1201 and the processor 1204 shown in Fig. 12. Each of the processors can be a single-CPU or a multi-CPU. The processor herein can refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0395] The memory 1202 is configured to store software programs for implementing the solutions of the present application, and the processor 1201 is configured to control the execution of the software programs. The specific implementation manners can refer to the methods in the above embodiments, and will not be described here.

[0396] Optionally, the memory 1202 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of dynamic storage device that can store information and instructions, and can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, an optical disc storage (including a compact disc, a laser disc, an optical disc, a digital versatile disc, a Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium capable of carrying or storing desired program codes in the form of instructions or data structures and capable of being accessed by a computer, but is not limited to this. The memory 1202 can be integrated with the processor 1201 or exist independently and be coupled to the processor 1201 through the interface circuit (not shown in FIG. 12) of the communication device 1200, and the embodiments of the present application do not make a specific limitation in this regard.

[0397] The transceiver 1203 is configured to communicate with other communication devices. For example, the communication device 1200 is a terminal, and the transceiver 1203 can be configured to communicate with a network device or another terminal device. For another example, the communication device 1200 is a network device, and the transceiver 1203 can be configured to communicate with a terminal or another network device.

[0398] Optionally, the transceiver 1203 can include a receiver and a transmitter (not shown separately in FIG. 12). The receiver is configured to implement the receiving function, and the transmitter is configured to implement the transmitting function.

[0399] Optionally, the transceiver 1203 can be integrated with the processor 1201 or exist independently and be coupled to the processor 1201 through the interface circuit (not shown in FIG. 12) of the communication device 1200, and the embodiments of the present application do not make a specific limitation in this regard.

[0400] It can be understood that the structure of the communication device 1200 shown in FIG. 12 does not constitute a limitation on the communication device, and the actual communication device can include more or fewer components than those shown, or combine certain components, or different component arrangements.

[0401] In addition, the technical effects of the communication device 1200 can refer to the technical effects of the methods described in the above method embodiments, which will not be repeated here.

[0402] It should be understood that the processor in the embodiments of the present application can be a central processing unit (CPU), and the processor can also 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 gates or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor.

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

[0404] The above-described embodiments can be implemented in whole or in part by software, hardware (such as a circuit), firmware, or any combination thereof. When implemented in software, the above-described embodiments can be implemented 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, the processes or functions described in the embodiments of the present application are wholly or partially generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center through a wired (such as infrared, wireless, microwave, etc.) manner. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. containing one or more available medium collections. The available medium can be a magnetic medium (such as a floppy disk, a hard disk, a magnetic tape), an optical medium (such as a DVD), or a semiconductor medium. The semiconductor medium can be a solid-state disk.

[0405] The embodiments of the present application also provide a computer-readable storage medium storing a computer program, which can make a computer execute the above-described communication method when the computer program is executed by the computer. In other words, the computer program includes instructions for implementing the above-described communication.

[0406] The embodiments of the present application also provide a computer program product, which includes computer program code, and when the computer program code is executed on a computer, the computer can execute the above-described communication method.

[0407] The embodiments of the present application also provide a communication system, which includes a first device and a second device executing the above-described communication method.

[0408] The embodiments of the present application also provide a chip, which can include a processor executing the above-described communication method. Optionally, the chip further includes a memory coupled to the processor, and the memory stores a program for executing the above-described communication method.

[0409] It should be understood that the term "and / or" in this document is merely used to describe associated relationship, and it can mean three relationships, for example, A and / or B can mean that A exists alone, A and B exist together, and B exists alone, where A and B can be singular or plural. In addition, the character " / " in this document generally means that the associated objects before and after the " / " are in an "or" relationship, but can also mean an "and / or" relationship, which can be understood according to the context before and after.

[0410] In this application, "at least one" means one or more, and "multiple" means two or more. "At least one of the following" or the like means any combination of the items, including any combination of single or multiple items. For example, at least one of a, b, or c can mean a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, and c can be single or multiple.

[0411] It should be understood that the order of the above processes in various embodiments of the present application does not mean the order of execution, and the execution order of the processes should be determined according to its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0412] Those skilled in the art can realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be realized by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are realized in hardware or software depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0413] Those skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working process of the above-described system, device and unit can refer to the corresponding process in the foregoing method embodiments, which will not be repeated here.

[0414] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be realized by other ways. For example, the above-described device embodiments are only schematic, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the shown or discussed objects can be indirect coupling or communication connection through some interfaces, devices or units, and can be electrical, mechanical or other forms.

[0415] The units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, i.e., may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment scheme.

[0416] In addition, the functional units in each embodiment of the present application can be integrated in one processing unit, or each unit can be physically present separately, or two or more units can be integrated in one unit.

[0417] If the functions are realized in the form of software functional units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application or the parts that essentially contribute to the prior art or the parts of the technical solutions can be embodied in the form of software products. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various program code storage media.

[0418] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A communication method characterized by comprising: The method applied to a first network entity comprises: sending first information, the first information comprising at least one of M identifier lengths or N length intervals, M and N being positive integers; receiving a first identifier of a first terminal, a length of the first identifier satisfying a preset rule with a first identifier length in the M identifier lengths, and / or the length of the first identifier being located in a first length interval in the N length intervals.

2. The method of claim 1, wherein, The length of the first identifier satisfies the preset rule with the first identifier length, comprising: the length of the first identifier is the same as the first identifier length; or the first identifier is determined according to a second identifier of the first terminal, the length of the second identifier being the same as the first identifier length.

3. The method of claim 2, wherein, The first information further comprises a reporting length, in the case that the first identifier is determined according to the second identifier, the length of the first identifier being the same as the reporting length.

4. The method according to any one of claims 1-3, characterized in that, The M identifier lengths comprise K kinds of identifier lengths, the K kinds of identifier lengths belonging to L kinds of identifier lengths, K being a positive integer, and L being an integer greater than or equal to K.

5. The method of claim 4, wherein, The method further comprises: receiving a service request from a second network entity, the second network entity being a requestor of a first service, the service request indicating that the first service is performed on a terminal satisfying a preset condition, the first terminal being the terminal satisfying the preset condition; determining the L kinds of identifier lengths according to the service request.

6. The method of claim 5, wherein, The determining the L kinds of identifier lengths according to the service request, comprising: obtaining the L kinds of identifier lengths from a third network entity according to the service request; or the service request containing the L kinds of identifier lengths.

7. The method of claim 5, wherein, The determining the L kinds of identifier lengths according to the service request, comprising: obtaining the L kinds of identifier lengths from the service request.

8. The method according to claim 5 or 6, characterized in that, The terminal satisfying the preset condition comprises at least one of the following: a terminal located in an indicated area or a terminal with an identifier of an identifier type.

9. The method according to claim 5 or 6, characterized in that, The first service is an environmental Internet of Things (A-IoT) service.

10. The method of claim 4, wherein, The L kinds of identifier lengths are default identifier lengths of the first network entity.

11. The method according to any one of claims 1-10, characterized in that, The first information is carried in a mask.

12. The method of claim 11, wherein, The mask comprises an identifier type, a type of the first identifier matching the identifier type comprised in the mask.

13. The method of claim 12, wherein, The identifier type is any one of the following: an identifier allocated by an operator network, an identifier not allocated by an operator network, a product electronic identifier, or a non-product electronic identifier.

14. The method of any one of claims 1-13, wherein, The method further comprises: sending second information, the second information comprising P identifier lengths and / or Q length intervals, P and Q being positive integers, the P identifier lengths being different from the M identifier lengths, and the Q length intervals being different from the N length intervals.

15. The method of claim 14, wherein, The first information and the second information are carried in a same message, or the first information and the second information are respectively carried in different messages.

16. The method of any one of claims 1-15, wherein, The first network entity supports a reader function, and the first terminal is an environmental Internet of Things (A-IoT) terminal.

17. A method of communication, comprising: The method comprises: receiving first information, the first information comprising at least one of M identifier lengths or N length intervals, M and N being positive integers; According to the first information, a first identifier of the first terminal is sent, a length of the first identifier satisfies a preset rule with a first identifier length in the M identifier lengths, and / or the length of the first identifier is located in a first length interval in the N length intervals.

18. The method of claim 17, wherein, The length of the first identifier satisfies the preset rule with the first identifier length includes: The length of the first identifier is the same as the first identifier length; or The first identifier is determined according to a second identifier of the first terminal, and the length of the second identifier is the same as the first identifier length.

19. The method of claim 18, wherein, The first information further includes a reporting length, and in a case where the first identifier is determined according to the second identifier, the length of the first identifier is the same as the reporting length.

20. The method of claim 18 or 19, wherein, The method further includes: If the length of the second identifier is greater than the reporting length, the second identifier is truncated to the reporting length to obtain the first identifier; If the length of the second identifier is less than the reporting length, the second identifier is padded to the reporting length to obtain the first identifier; If the length of the second identifier is equal to the reporting length, the second identifier and the first identifier are the same identifier.

21. The method according to any one of claims 17-20, characterized by, The receiving first information includes: Receiving a mask, and the first information is carried in the mask.

22. A method of communication, comprising: The method applied to a reader includes: Obtaining a length of a device identifier; According to the length of the device identifier, determining a transmission resource, a size of the transmission resource matches the length of the device identifier, and the transmission resource is used to carry the device identifier.

23. The method of claim 22, wherein, The obtaining the length of the device identifier includes: Receiving the length of the device identifier from a first terminal; or Receiving the length of the device identifier from a core network network element for managing terminals.

24. The method of claim 22 or 23, wherein, The method further includes: Transmitting the device identifier of the first terminal on the transmission resource.

25. The method of any one of claims 22-24, wherein: The first terminal is an environmental Internet of Things (A-IoT) terminal.

26. A communications apparatus, the communications apparatus being a first network entity, the communications apparatus comprising: The communication apparatus includes a module for performing the method of any one of claims 1-16.

27. A communications device, characterized by The communication apparatus includes a module for performing the method of any one of claims 17-21.

28. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a computer program or instructions, when the computer program or instructions are executed, cause the method of any one of claims 1-16 to be implemented, or cause the method of any one of claims 17-21 to be implemented, or cause the method of any one of claims 22-25 to be implemented.

29. A computer program product, characterised in that, The computer program product includes: a computer program or instructions, when the computer program or instructions are executed, cause the method of any one of claims 1-16 to be implemented, or cause the method of any one of claims 17-21 to be implemented, or cause the method of any one of claims 22-25 to be implemented.

Images