Communication method and apparatus

Abstract

A communication method and apparatus. The method comprises: after a device receives a paging message, the device maintaining (e.g., continuing to store) state information of an original identifier, such that after the device receives a retransmitted paging message including the original identifier, the device can acquire the state information of the original identifier, thereby preventing repeat reporting of service data of the original identifier, and thus saving on transmission resources.

Description

Communication method and apparatus

[0001] Cross-reference to Related Applications

[0002] This application claims priority to the Chinese Patent Application No. 202411401217.3, filed on September 30, 2024, and entitled “A Communication Method and Apparatus”, the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

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

[0004] Current wireless communication systems, such as ambient internet of things (A-IoT) systems, or internet of things (IoT) systems, etc., can be composed of readers (such as access devices) and tag devices (such as A-IoT terminals); the readers and the tag devices perform non-contact data communication, such as the readers reading out information in the tag devices, or writing information to be stored into the tag devices. The main services include inventory, positioning, sensing, and commands, etc., and the typical application scenarios include logistics, warehousing, industrial manufacturing, identity recognition, and environmental monitoring, etc.

[0005] In the current scheme, the tag device (such as a first device) does not support the parallel of multiple services. For example, the tag device can only perform another identification corresponding service process after completing an identification corresponding service process. The subsequent service needs to wait for the completion of the previous service before it can be performed, which brings a certain time delay to the execution of the subsequent service. SUMMARY

[0006] A communication method and apparatus, when a first device receives a message including a new identification (such as a second identification), the first device maintains state information corresponding to the original identification (such as a first identification); the first device maintains / preserves the state information corresponding to the first identification, so that the first device can execute the service corresponding to the first identification according to the state information corresponding to the first identification during the execution of the service corresponding to the second identification, and the first device can support the parallel of multiple services, thereby reducing the time delay of the subsequent service.

[0007] In a first aspect, a communication method is provided. The method is performed by a first device, or a module, unit or component (e.g., a chip, a chip system, a circuit, a processor, or the like) applied in the first device. The first device is a device with a tag function. The method comprises: receiving a first message, the first message being used for paging the first device, the first message comprising a first identifier; receiving a second message, the second message being used for paging the first device, the second message comprising a second identifier, or the second message comprising the second identifier and a first indication, the first indication being used for instructing the first device to maintain state information corresponding to the first identifier; the second identifier being different from the first identifier, or the state information corresponding to the first identifier is maintained according to the first indication.

[0008] According to the above design, when the first device receives a message comprising a new identifier (e.g., the second identifier), the first device maintains the state information corresponding to the original identifier (e.g., the first identifier), so that when the first device receives a message comprising the original identifier, the first device responds to the message according to the state information corresponding to the original identifier, thereby avoiding repeated responses.

[0009] In an implementation, the state information corresponding to the first identifier comprises: successful transmission of a service corresponding to the first identifier; or unsuccessful transmission of the service corresponding to the first identifier.

[0010] In an implementation, the method further comprises: receiving a third message, the third message being used for paging the first device, the third message comprising the first identifier; and determining whether to respond to or not to respond to the third message according to the maintained state information corresponding to the first identifier.

[0011] According to the above design, the third message can be a retransmitted paging message. If the state information corresponding to the first identifier maintained by the first device is successful transmission or completion, the first device can not respond to the third message, such as not accessing a second device. Or if the state information corresponding to the first identifier maintained by the first device is unsuccessful transmission or incomplete, the first device can respond to the third message and / or re-access. For example, the first device accesses the second device according to the paging of the third message, thereby avoiding repeated responses to the third message in the case of successful transmission of the service corresponding to the first identifier.

[0012] In an implementation, the method further comprises: receiving a second indication, the second indication being used for instructing to reset the state information corresponding to one or more identifiers maintained by the first device.

[0013] In an implementation, the method further comprises: receiving the one or more identifiers, the one or more identifiers being in an association relationship with the second indication.

[0014] In an implementation, the method further includes: receiving a fourth message, the fourth message being used for at least one of the following: triggering the at least one access opportunity, indicating the number of access opportunities, indicating the resource configuration information, or indicating the random access success, the first identity being included in the fourth message; and responding to or not responding to the fourth message according to the state information corresponding to the first identity.

[0015] In an implementation, the first identity and the second identity are assigned by a first core network element, and the first identity and the second identity are used to identify a service request initiated by the first core network element.

[0016] In an implementation, the first identity and the second identity are identities of a device.

[0017] In a second aspect, a communication method is provided, an execution subject of the method is a first device, or a module, unit or component (for example, a chip, a chip system, a circuit, a processor, or other etc.) applied in the first device; it can be understood that the first device is a device with a tag function, and the method includes: receiving a first message, the first message being used for paging the first device, the first message including a first identity; the first identity being different from a second identity maintained by the first device, and resetting state information corresponding to the second identity.

[0018] In an implementation, the state information corresponding to the second identity includes: service transmission success corresponding to the second identity; or service transmission failure corresponding to the second identity.

[0019] In an implementation, the method further includes: receiving a third indication, the third indication being used for indicating that the first device maintains state information corresponding to one or more identities, the one or more identities including the second identity.

[0020] In an implementation, the method further includes: receiving the one or more identities, the one or more identities being in an association relationship with the third indication.

[0021] In an implementation, the first identity and the second identity are assigned by a first core network element, and the first identity and the second identity are used to identify a service request initiated by the first core network element.

[0022] In an implementation, the first identity and the second identity are identities of a device.

[0023] In a third aspect, a communication method is provided. An execution subject of the method is a first device, or a module, unit or component (e.g., a chip, a chip system, a circuit, a processor, or the like) applied in the first device. It can be understood that the first device is a device with a tag function. The method comprises: receiving a first message, wherein the first message comprises an identifier of a second device, and the first message is a reader-to-device (R2D) message; and determining whether to respond to the first message according to the identifier of the second device and an identifier of a third device stored by the first device.

[0024] Through the above design, the first device receives a first message, which can be an R2D message. The first message comprises an identifier of a device (e.g., a reader), which is referred to as an identifier of a second device. The first device determines whether to respond to the first message according to the identifier of the second device and an identifier of a third device stored by the first device. Thus, in a scenario where multiple readers are parallel, the first device can avoid re-reading by multiple readers or incorrect response to R2D signaling sent by multiple readers.

[0025] In an implementation, the determining whether to respond to the first message according to the identifier of the second device and the identifier of the third device stored by the first device comprises: when the identifier of the second device is the same as the identifier of the third device, responding to the first message; or when the identifier of the second device is different from the identifier of the third device, not responding to the first message.

[0026] In an implementation, the method further comprises: receiving a second message, wherein the second message comprises the identifier of the third device, and the second message is an R2D message.

[0027] In a fourth aspect, an apparatus is provided. The apparatus can implement the method of any one of the first aspect to the third aspect. For example, the apparatus comprises a module, unit or component for implementing the method described in any one of the first aspect to the third aspect. The module, unit or component can be implemented by hardware, or by software, or by a combination of hardware and software.

[0028] In a design, the apparatus comprises a unit for implementing the method of any one of the first aspect to the third aspect.

[0029] In a design, the apparatus comprises a processor for implementing the method of the first aspect or the fourth aspect. Optionally, the apparatus further comprises a memory, and the processor is coupled to the memory. The processor is configured to execute a computer program or instructions stored in the memory, so that the apparatus implements the method of any one of the first aspect to the third aspect.

[0030] In one design, the apparatus includes a processor and an interface circuit for receiving signals from other apparatuses outside the apparatus and transmitting signals to the processor or sending signals from the processor to other apparatuses outside the apparatus, and the processor is configured to implement the method of any of the first aspect to the third aspect by logic circuit or executing code instructions.

[0031] In one design, the apparatus can be the first apparatus, or a module, unit or component (e.g., a chip, chip system, circuit or processor, etc.) in the first apparatus that implements the method / operation / step / action described in the first aspect to the third aspect one by one, or can be matched with the first apparatus.

[0032] In a fifth aspect, a computer readable storage medium is provided, which stores a computer program or instructions, when the computer program or instructions are run on a computer, the computer is caused to implement the method of any of the first aspect to the third aspect.

[0033] In a sixth aspect, a computer program product is provided, which includes a computer program or instructions, when the computer program or instructions are run on a computer, the method of any of the first aspect to the third aspect is executed.

[0034] In a seventh aspect, a chip is provided, which includes a processor for implementing the method of any of the first aspect to the third aspect. Optionally, the chip further includes a memory, and the processor is coupled to the memory, and the processor is configured to execute the computer program or instructions stored in the memory, so that the chip implements the method of any of the first aspect to the third aspect.

[0035] In an eighth aspect, a communication system is provided, which includes a first communication apparatus and a second communication apparatus; wherein the first communication apparatus is configured to implement the method of the first aspect; and the second communication apparatus is configured to implement the method of the second device, and the second device can be a device with a reader function, such as an access network device or a terminal, etc. BRIEF DESCRIPTION OF DRAWINGS

[0036] FIG. 1 is a schematic diagram of a communication system (e.g., an RFID system / A-IoT system / IoT system) according to an embodiment of the present application;

[0037] FIG. 2, FIG. 3, FIG. 4a, FIG. 4b and FIG. 5 are schematic diagrams of network architecture according to embodiments of the present application;

[0038] FIG. 6 is a schematic diagram of an ORAN system according to an embodiment of the present application;

[0039] FIG. 7 is a schematic diagram of protocol layer division of an ORAN device according to an embodiment of the present application;

[0040] FIG. 8 is a schematic diagram of protocol layer division of an access network device according to an embodiment of the present application;

[0041] FIG. 9 is a schematic diagram of a process of an inventory service according to an embodiment of the present application;

[0042] FIG. 10 is a schematic diagram of a current scheme according to an embodiment of the present application;

[0043] FIG. 11 is a schematic diagram of a process according to an embodiment of the present application;

[0044] FIG. 12 to FIG. 17 are schematic diagrams according to embodiments of the present application;

[0045] FIG. 18 is another schematic diagram of a process according to an embodiment of the present application;

[0046] FIG. 19 is still another schematic diagram of a process according to an embodiment of the present application;

[0047] FIG. 20 is a schematic diagram of overlapping coverage of multiple readers and writers according to an embodiment of the present application;

[0048] FIG. 21 is a schematic diagram according to an embodiment of the present application;

[0049] FIG. 22 and FIG. 23 are schematic diagrams of a device according to embodiments of the present application. DETAILED DESCRIPTION

[0050] In order to make the purpose, technical scheme and advantages of the present application more clear, the embodiments of the present application are described in detail below with reference to the drawings. The specific operation methods, function descriptions and the like in the method embodiments can also be applied to the device embodiments or system embodiments.

[0051] In the embodiments of the present application, the number of a noun means "a singular noun or a plural noun" unless otherwise specified, that is, "one or more". "At least one" means one or more, and "multiple" means two or more. "And / or" describes the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B can represent the following three cases: A exists alone, A and B exist together, and B exists alone, where A and B can be singular or plural. In the textual description of the present application, the character " / " generally represents an "or" relationship between the associated objects; in the formula of the present application, the character " / " represents a "division" relationship between the associated objects. "Including at least one of A, B or C" or similar expressions can mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B and C, where A, B, C can be singular or plural.

[0052] In the embodiments of the present application, various numerical numbers involved are distinguished for the convenience of description, and are not used to limit the scope of the embodiments of the present application. The size of the serial number of the above processes does not mean the order of execution, and the execution order of the processes should be determined according to their functions and internal logic. The ordinal numbers such as "first" and "second" involved in the embodiments of the present application are used to distinguish a plurality of objects, and do not limit the size, order, timing, priority or importance of the plurality of objects.

[0053] A radio frequency identification (RFID) system includes a reader and a tag device. The reader can read out information in the tag device, or write information to be stored into the tag device. The reader and the tag device perform non-contact data communication. The tag device has a simple function and needs to rely on the excitation of the reader to send information, that is, the tag device converts the wireless signal transmitted by the reader into energy to drive itself to work. The tag device supports micro-watt or hundreds of micro-watt functions and cannot support complex designs. The tag device can also be referred to as an electronic tag, an RFID tag, or a tag. In the following description, the name "tag" is mainly taken as an example for illustration.

[0054] As shown in FIG. 1, the reader can send a carrier signal to the tag, and the tag receives the carrier signal through an antenna. The solid line in FIG. 1 represents the carrier signal transmitted by the reader, and the dashed line represents the signal reflected and transmitted by the tag based on the carrier signal. The tag can adjust the information to be transmitted in the reflected signal. In the above manner, the tag uses a low-precision low-power mid-low frequency ring oscillator or a completely non-local oscillator to receive the downlink signal, which can further reduce the power consumption of the tag in downlink reception. The tag is a miniature wireless transceiver device, mainly including a built-in tag device antenna, a coupling element, and a chip. The chip of the tag has a storage space that can support reading or writing tag data by the reader. After receiving the radio frequency signal transmitted by the reader through the antenna, the tag can realize coupling of the radio frequency signal through the coupling element, and then provide energy to the chip of the tag in the coupling channel, and feed back the data stored in the chip to the reader through the antenna.

[0055] With the development of communication technology, the 3rd generation partnership project (3GPP) defines ambient internet of things (A-IoT) technology. A-IoT technology is an extremely low-power and extremely low-complexity internet of things technology, which can be understood as an extension of RFID in 3GPP. Although A-IoT technology has some principles in common with RIFD technology, more value scenarios will be introduced in 3GPP.

[0056] In A-IoT, both the reader and the tag can be implemented based on the infrastructure in the cellular network. In other words, both the reader and the tag can be devices in the cellular network. For example, the function of the reader can be implemented by an access network device, such as a base station. The tag can be implemented by a terminal in the cellular network, such as an extremely low power consumption, extremely low complexity Internet of Things terminal. Non-contact data communication can be performed between the access network device and the terminal, so as to read information from the terminal and / or write information to be stored into the terminal. In the A-IoT technology, the terminal can be an extremely low power consumption, extremely low complexity Internet of Things terminal, which can be referred to as an A-IoT terminal or an A-IoT device.

[0057] FIG. 2 shows a schematic diagram of a communication system suitable for embodiments of the present application. As shown in FIG. 2, the communication system includes an access network device and an A-IoT terminal. The A-IoT terminal can be a standalone device, or the A-IoT terminal can be integrated with a terminal device, i.e., the A-IoT terminal is part of the terminal device. In the communication system, the access network device can have the function of a reader, and the A-IoT terminal can have the function of a tag. The access network device can communicate with the A-IoT terminal as a tag via the Uu interface, i.e., the air interface.

[0058] FIG. 3 shows a schematic diagram of another communication system applicable to the embodiments of the present application. As shown in FIG. 3, the communication system includes an access network device, an intermediate node and an A-IoT terminal. The access network device communicates with the A-IoT terminal through the intermediate node, which can be considered as a relay node and mainly plays a relay role. For example, the intermediate node can forward signaling and / or data sent by the access network device to the A-IoT terminal, or forward signaling and / or data sent by the A-IoT terminal to the access network device. The intermediate node can be a repeater, an integrated access and backhaul (IAB) node, or a terminal device, without limitation. The A-IoT terminal can be a separate device, or the A-IoT terminal can be integrated with a terminal. The access network device is connected with the intermediate node through a Uu interface, and the intermediate node is directly connected with the A-IoT terminal. In one understanding, the access network device can have the function of a reader / writer, and the A-IoT terminal can have the function of a tag. The access network device can send data and / or signaling to the A-IoT terminal through the intermediate node, and the A-IoT terminal can send data and / or signaling to the access network device through the intermediate node. Alternatively, in another understanding, the intermediate node can have the function of a reader / writer, and the A-IoT terminal can have the function of a tag. For example, the access network device can pre-configure the communication resources of the intermediate node, and the intermediate node communicates with the A-IoT terminal by using the pre-configured communication resources.

[0059] FIG. 4a or FIG. 4b shows a schematic diagram of another communication system applicable to the embodiments of the present application. As shown in FIG. 4a or FIG. 4b, the communication system includes an access network device, an auxiliary node and an A-IoT terminal. The auxiliary node can be a repeater, an IAB node or a terminal device, etc. The access network device or the auxiliary node can have the function of a reader / writer, and the A-IoT terminal can have the function of a tag. The communication interface between the access network device and the auxiliary node can be a Uu interface. The auxiliary node can assist the communication between the access network device and the A-IoT terminal. FIG. 4a is a schematic diagram of downlink assistance, in which the access network device communicates with the A-IoT terminal through the auxiliary node. For example, the access network device can send downlink data to the auxiliary node, and the auxiliary node forwards the downlink data to the A-IoT terminal. FIG. 4b is a schematic diagram of uplink assistance, in which the A-IoT terminal can send uplink data to the auxiliary node, and the auxiliary node forwards the uplink data to the access network device.

[0060] FIG. 5 shows a schematic diagram of another communication system suitable for the embodiments of the present application. As shown in FIG. 5, the communication system includes a terminal device and an A-IoT terminal. The A-IoT terminal can be a standalone device, or the A-IoT terminal can be integrated with the terminal device. In the communication system, the terminal device can have the function of a reader, the terminal can have the function of a tag, and the terminal device and the A-IoT terminal can communicate through a sidelink.

[0061] FIG. 6 is a schematic diagram of an open radio access network (O-RAN or ORAN) system suitable for the embodiments of the present application. As shown in FIG. 6, the ORAN system includes a core network device, an access network device, and a terminal. The access network device communicates with the core network device through a backhaul and communicates with the terminal through an air interface. The access network device includes a baseband unit (BBU) and a radio unit (RU), the BBU communicates with at least one RU through a fronthaul, and the BBU and the RU can be co-located or not co-located. Specifically, the BBU communicates with the core network device through the backhaul, and the RU communicates with the terminal through the air interface. The BBU includes at least one CU and at least one DU, which can communicate through at least one midhaul. In the ORAN system, the CU can also be referred to as an open CU (O-CU), and the DU can also be referred to as an open DU (O-DU).

[0062] FIG. 7 is a schematic diagram of a network element function division and a protocol layer structure of an ORAN device to which the present application is applicable. It can be understood that the access network device adopts an ORAN architecture, and the access network device can be referred to as an ORAN device, which is used to implement wireless access of a terminal. Communication between the access network device and the terminal follows a certain protocol layer structure. The protocol layer structure can include a control plane protocol layer structure and a user plane protocol layer structure. For example, the control plane protocol layer structure can include functions of protocol layers such as a radio resource control (RRC) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, a media access control (MAC) layer, and a physical layer. For example, the user plane protocol layer structure can include functions of protocol layers such as a PDCP layer, an RLC layer, a MAC layer, and a physical layer, and in a possible implementation, a service data adaptation protocol (SDAP) layer can be further included above the PDCP layer.

[0063] As shown in FIG. 7, the access network device includes logical nodes such as a CU, a DU, and an RU. The CU can be connected to a core network through an interface, for example, the interface can be referred to as an E2 interface. Alternatively, the CU can have part of the functions of the core network. The CU can control at least one DU, and the CU can be connected to the DU through an interface, for example, the interface can be referred to as an F1 interface. Further, a control panel (CP) interface can be referred to as an F1-C, and a user panel (UP) interface can be referred to as an F1-U. The DU can control at least one RU, and the DU can be connected to the RU through an interface, for example, the interface can be a fronthaul interface.

[0064] 1. CU

[0065] The CU can be a logical node that carries an RRC layer, an SDAP layer, a PDCP layer, and other control functions of the access network device. That is, the CU can implement functions of an RRC layer, an SDAP layer, a PDCP layer, and certain control functions.

[0066] Further, the CU can be split into a CU-CP and a CU-UP. Referring to FIG. 7, the CU-CP is a logical node carrying a control plane part of PDCP (PDCP-C) of an RRC layer and a PDCP layer, for implementing a control plane function of the CU. The CU-CP can interact with a network element for implementing a control plane function in a core network. The network element for implementing the control plane function in the core network can be an access and mobility function network element, for example, an access and mobility management function (AMF) in a 5G communication system. Continuing to refer to FIG. 7, the CU-UP is a logical node carrying a user plane part of PDCP (PDCP-U) layer of an SDAP layer and a PDCP layer, for implementing a user plane function of the CU. The CU-UP can interact with a network element for implementing a user plane function in a core network. The network element for implementing the user plane function in the core network, for example, a user plane function (UPF) in a 5G communication system.

[0067] 2、DU

[0068] The DU can be a logical node carrying an RLC layer, a MAC layer, a higher physical (Higher PHY) layer, and other functions. For example, the higher physical layer can include partial processing functions of the PHY layer, such as forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, and the like. That is, the DU can implement the functions of the RLC layer, the MAC layer, the higher physical layer, and other functions.

[0069] It can be understood that 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 protocol layers above the RLC layer are provided in the CU, and the remaining functions of the RLC layer and functions of protocol layers below the RLC layer are provided 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. Functions that need to meet a relatively low delay requirement in terms of processing time are provided in the DU, and functions that do not need to meet the delay requirement are provided in the CU.

[0070] 3、RU

[0071] The RU can be a logical node that carries lower physical layer (Lower PHY) and radio frequency (RF) chain processing. For example, the lower physical layer includes partial processing functions of the physical layer, such as fast Fourier transform (FFT), inverse fast Fourier transformation (IFFT), digital beamforming, and filtering, etc. That is, the RU can implement the functions of the physical layer and the radio frequency.

[0072] In one possible implementation, the RU can be a 3GPP transmission reception point (TRP) or a remote radio head (RRH) or other similar functional entity. The RU communicates with one or more terminals over a wireless link.

[0073] The DU and the RU can be co-located or not co-located, without limitation. Referring to FIG. 7, the DU and the RU can include an O-RAN control user and synchronization (CUS-Plane) plane and an O-RAN management plane (M-Plane). The O-RAN CUS plane can be referred to as the CUS plane, and the O-RAN management plane can be referred to as the management plane. Further, the CUS plane can be split into a control plane (C-Plane) and a user plane (U-Plane). Optionally, the control plane refers to a real-time control plane between the DU and the RU. The management plane refers to a non-real-time management operation between the DU and the RU.

[0074] Referring to FIG. 7, the DU and the RU exchange information of the control plane and information of the user plane through a lower-layer split CUS-Plane (LLS-CUS) interface via a fronthaul link. Further, the LLS-CUS interface can include an LLS-C interface corresponding to the control plane and an LLS-U interface corresponding to the user plane. The DU and the RU exchange information of the management plane through an LLS-M interface of the fronthaul link. Referring to FIG. 7, the LLS-M interface can also be connected to an external management system.

[0075] It can be understood that the DU and the RU can cooperate to jointly implement the functions of the physical layer. One DU can be connected with 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 medium radio frequency functions. For another example, the DU is configured to implement high-layer functions in the physical layer, and the RU is configured to implement low-layer functions in the physical layer or implement the low-layer functions and radio frequency functions. The high-layer functions in the physical layer can include a part of functions of the physical layer that are closer to the MAC layer, and the low-layer functions in the physical layer can include another part of functions of the physical layer that are closer to the medium radio frequency side.

[0076] The following explains some terms related to the embodiments of the present application to facilitate understanding by those skilled in the art.

[0077] 1. Access network device

[0078] The access network device can be a device in a wireless network, configured to help a terminal access a wireless access. For example, the access network device is a radio access network (RAN) node that accesses the terminal to the wireless network, which can also be referred to as a RAN node. The access network device includes but is not limited to: a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next generation NodeB (gNB) in a 5th generation (5G) mobile communication system, an access network device in an open radio access network (O-RAN), a next generation base station or base station in a future communication network, or an access node in a wireless fidelity (WiFi) system, etc. The access network device can be a macro base station, a micro base station or an indoor station, or a relay node or a donor node, etc. The specific technology and specific device form adopted by the access network device in the present application are not limited.

[0079] Alternatively, the access network device can also be a device that implements the function of the access network device, for example, the access network device can be a module or unit that completes the function of the base station part, for example, can be a centralized unit (CU), a distributed unit (DU), a centralized unit control plane (CU-CP), or a centralized unit user plane (CU-UP), etc. As shown in FIG. 8, in some implementations, the access network device can include a centralized unit (CU) and a distributed unit (DU). The access network device including the CU node and the DU node splits the protocol layers of the gNB in the new radio (NR) system, the functions of part of the protocol layers are placed in the CU for centralized control, and the remaining part or all of the protocol layers are distributed in the DU, which is controlled by the CU. Further, the CU can also be divided into a control plane (CU-CP) and a user plane (CU-UP). The CU-CP is responsible for the control plane function, mainly including the radio resource control (RRC) and the packet data convergence protocol (PDCP) corresponding to the control plane (PDCP-C). The PDCP-C is mainly responsible for the encryption and decryption of the control plane data, the integrity protection, the data transmission, etc. The CU-UP is responsible for the user plane function, mainly including the service data adaptation protocol (SDAP) and the PDCP corresponding to the user plane (PDCP-U). The SDAP is mainly responsible for processing the data of the core network and mapping the flow to the bearer. The PDCP-U is mainly responsible for the encryption and decryption of the data plane, the integrity protection, the header compression, the sequence number maintenance, the data transmission, etc. The CU-CP and the CU-UP are connected through an E1 interface. The CU-CP represents the access network device to connect with the core network through an NG interface, and is connected with the DU through an F1 interface control plane (F1-C). The CU-UP is connected with the DU through an F1 interface user plane (F1-U). Of course, there is also a possible implementation that the PDCP-C is also in the CU-UP.

[0080] It can be understood that in different systems, the CU (including CU-CP or CU-UP) or DU can also have different names, but those skilled in the art can understand their meanings. For example, in an O-RAN or ORAN system, the CU can also be referred to as an open CU (O-CU), the DU can also be referred to as an open DU (O-DU), the CU-CP can also be referred to as an O-CU-CP, and the CU-UP can also be referred to as an O-CU-UP. For ease of description, the CU, CU-CP, CU-UP and DU are taken as examples for description in the present application.

[0081] In some embodiments, the access network device can also include an active antenna unit (AAU). The CU implements part of the functions of the gNB, and the DU implements part of the functions of the gNB. For example, the CU is responsible for processing non-real-time protocols and services, and implementing the functions of the RRC layer. The DU is responsible for processing physical layer protocols and real-time services, and implementing the functions of the radio link control (RLC) layer, the media access control (MAC) layer and the physical (PHY) layer.

[0082] 2. Terminal

[0083] A terminal is a device with wireless transceiving function. For example, the terminal can be referred to as a terminal device, a user equipment (UE), a mobile station, a mobile terminal device, etc. The terminal can be widely applied to various scenarios, such as device-to-device (D2D) communication, vehicle to everything (V2X) communication, machine-type communication (MTC), internet of things (IoT), 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. Currently, some examples of the terminal are: a mobile phone, a tablet computer, a computer with wireless transceiving function, a wearable device, a vehicle, a drone, a helicopter, an airplane, a ship, a robot, a mechanical arm, a smart home device, etc. The terminal device form is not limited in the embodiments of the present application.

[0084] Alternatively, the terminal can also be an apparatus implementing terminal functions, for example, the terminal can be a module, a unit or a component implementing terminal functions, etc., such as a chip, a chip system, a circuit or a processor applied to the terminal, etc. For example, the terminal can be a chip or a system on chip (SOC), and the above-mentioned chip or system on chip can be installed in the terminal.

[0085] 3. Ambient Internet of Things (A-IoT)

[0086] A-IoT, a communication infrastructure based on cellular network, is composed of a reader / writer and an A-IoT terminal. For example, in a cellular network, an access network device can implement the function of a reader / writer, or a traditional terminal can implement the function of a reader / writer, such as a smartphone terminal in 3GPP Release 15 (R15) or Release 16 (R16), or a reduced capability (RedCap) terminal in Release 17 (R17), etc. Even an intermediate node or an auxiliary node can implement the function of a reader / writer. For the intermediate node or the auxiliary node, please refer to the description of FIG. 3 or FIG. 4a / 4b.

[0087] In A-IoT, typical application scenarios include logistics, warehousing, industrial manufacturing, identity recognition, environmental detection, etc., and main businesses include at least one of the following: inventory, positioning, sensing, command. It can be understood that the command business can include at least one of read business, write business or lock business. Among them, the inventory business: the inventory business can also be called the inventory operation, which can obtain the identification information of the tag, for example, the reader can obtain the identification information of the tag through query, acknowledgment (ACK) and the like. Read business: the read business can read the electronic product code (EPC) in the storage area of the tag, the tag identifier (TID), the content stored in the reserved area of the tag or the content stored in the user storage area, etc. Write business: the write business can perform write operation on the storage area of the tag. Kill business: the kill business can make the tag never work. Lock business: the lock business can lock the information of the tag, which can prevent the read business or the write business on the tag. Or, the lock business can also lock the storage area, which can prevent or allow the read business or the write business on the storage area. The above are only examples, and other businesses or operations can be performed between the tag and the reader / writer, which will not be illustrated one by one here.

[0088] 4. A-IoT terminal (or AIoT terminal)

[0089] An A-IoT terminal is a device with a receiving or reflecting function. For example, the A-IoT terminal can be a terminal in an IoT system, which is an important component of future information technology development, and its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-object interconnection. The A-IoT terminal can also be referred to as an A-IoT device. The A-IoT terminal can be a terminal with extremely low power consumption and extremely low complexity. Some examples of A-IoT terminals are: smart speakers, train detectors, gas stations, inventory tags, and other sensors, and their main functions include collecting data, receiving control information and downlink data from access network devices or terminals, and sending uplink data to access network devices or terminal devices.

[0090] In one classification manner, the types of A-IoT terminals can include passive A-IoT terminals, semi-passive A-IoT terminals, and active A-IoT terminals. Among them, the passive A-IoT terminal and the semi-passive A-IoT terminal can adopt a backscatter-based communication manner. For example, this type of A-IoT terminal does not have the function of generating uplink signals and supports reflection. The access network device, the auxiliary terminal, or the intermediate node can send a carrier signal to the A-IoT terminal. The A-IoT terminal reflects the signal according to the received carrier signal, thereby realizing the uplink transmission of the A-IoT terminal. For example, the A-IoT terminal can adjust the received carrier signal so that the carrier signal can carry certain uplink information, and the A-IoT terminal reflects the adjusted carrier signal. The access network device or the intermediate node can obtain the uplink information according to the received reflected signal. Alternatively, in a period of time, the A-IoT terminal reflects the carrier signal at some time, and the A-IoT terminal does not reflect the carrier signal at some time. In this period of time, when the access network device or the intermediate node receives the reflected signal, the access network device or the intermediate node can identify the uplink signal as 1; when no reflected signal is received, the access network device or the intermediate node identifies the uplink signal as 0, thereby achieving the purpose of uplink information transmission. The main difference between the passive A-IoT terminal and the semi-passive A-IoT terminal is that the passive A-IoT terminal has no energy storage, and the semi-passive A-IoT terminal has energy storage and supports amplifying the reflected signal. The active A-IoT terminal adopts a communication manner of generating a carrier by itself. For example, the active A-IoT terminal has energy storage and supports amplifying the uplink and / or downlink signal. The access network device or the intermediate node can indicate the uplink transmission resource to the A-IoT terminal, and the A-IoT terminal can generate the uplink signal and send the uplink signal on the indicated uplink transmission resource.

[0091] In another classification manner, the A-IoT terminal can be divided into the following three types:

[0092] Device A or device 1: no energy storage, cannot independently generate signals, uses backscatter to transmit signals; its function is similar to a passive A-IoT terminal.

[0093] Device B or device 1b: has energy storage, but cannot independently generate signals, uses backscatter to transmit signals, and the stored energy can amplify the reflected signals; its function is similar to a semi-passive A-IoT terminal.

[0094] Device C or device 2: has energy storage, can independently generate signals, and has active radio frequency elements for transmission; its function is similar to an active A-IoT terminal.

[0095] Taking inventory business as an example, as shown in FIG. 9, a flowchart of inventory / access is provided, including:

[0096] Optionally, step 900a: the server sends an inventory service request to the first core network element, and the first core network element receives the inventory service request from the server, which is used to indicate that the A-IoT terminal is subjected to inventory service.

[0097] Step 900b: the first core network element sends an inventory service request to the access network device, and the access network device receives the inventory service request from the first core network element.

[0098] Optionally, step 900c: the access network device sends a response message to the first core network element, and the first core network element receives the response message from the access network device.

[0099] It can be understood that the response message is the response message of the inventory service request in step 900b.

[0100] Step 910: the access network device sends a paging or selection message to the A-IoT terminal, and the A-IoT terminal receives the paging or selection message from the access network device.

[0101] The paging or selection message is used to select a group of A-IoT terminals. For example, the paging or selection message includes session, action, mask, and the like. When receiving the paging or selection message, the A-IoT terminal can obtain the session, action, and mask, and the like from the message. The session information is used to indicate a session, and the action information is used to indicate that the session flag position of the session is a specified value, for example, the specified value can be A or B. Assuming that the session indicated by the session information is S0, and the action information is 0. Then, for the A-IoT terminal, if the mask information of the A-IoT terminal is consistent or matched with the mask information in the paging or selection message, the A-IoT terminal sets the flag position of the session S0 to A.

[0102] Step 920: The access network device sends a query command to the A-IoT terminal, and the A-IoT terminal receives the query command from the access network device.

[0103] The query command is used to initialize an inventory period. For example, the query command carries a flag bit A and a Q value, and the like. For example, if the session carried in the query command is S0, and the flag bit is A. The A-IoT terminal determines whether the flag bit of its own session S0 is A; if it is A, it is considered to be matched; and the A-IoT terminal can respond to the query command. Further, the A-IoT terminal can generate a random number between [0, 2 Q -1] according to the Q value, and the A-IoT terminal takes the random number as the initial value of the counter. For example, if Q=4, the A-IoT terminal generates a random number in [0, 15], for example, the A-IoT terminal generates a random number 10, and the initial value of the counter is 10.

[0104] The A-IoT terminal can determine whether the initial value of the counter is 0. If the initial value of the counter is 0, the A-IoT terminal can send a 16-bit random number (RN16) to the access network device, and the 16-bit random number is used to trigger a random access procedure and can be used as a random access request message. Alternatively, if the initial value of the counter is not 0, the A-IoT terminal can not send the RN16 to the access network device. Correspondingly, if the access network device does not receive the RN16 sent by the A-IoT terminal within a preset time after sending the query command, the access network device continues to send a repeated query (Query Rep) command to the A-IoT terminal. When the A-IoT terminal receives the repeated query command, the current value of the counter is decremented by 1, that is, the A-IoT terminal performs: counter = counter - 1. If the value of the counter is still not 0 after the above process, the A-IoT terminal can not send the RN16 to the access network device, and the access network device continues to send the repeated query command to the A-IoT terminal until the value of the counter is 0. When the value of the counter is 0, the A-IoT terminal can send the RN16 to the access network device.

[0105] Step 930: The A-IoT terminal sends a first random access request message (such as RN16) to the access network device, and the access network device receives the first random access request message (such as RN16) from the A-IoT terminal.

[0106] For example, the first random access request message can be the RN16 generated by the A-IoT terminal as described above. Alternatively, the A-IoT terminal can also generate a random number of other lengths, such as a random number of 8 bits, etc. In the description of the present application, the generation of a 16-bit random number RN16 by the terminal is mainly described as an example.

[0107] Step 940: The access network device sends an acknowledge (ACK) to the A-IoT terminal, and the A-IoT terminal receives the ACK from the access network device.

[0108] For example, the A-IoT terminal can send the RN16 to the access network device by using the first time-frequency resource. The access network device can determine whether only one RN16 is received on the first time-frequency resource; if one RN16 is received, it can be considered that no collision occurs, and the access network device sends an ACK to the A-IoT terminal, and the ACK includes the RN16. The ACK can also be referred to as a random access response message or a collision resolution message. Alternatively, the access network device receives multiple RN16s on the first time-frequency resource, and it can be considered that a collision occurs, and the access network device no longer sends the ACK to the A-IoT terminal, or can select one RN16 from the multiple RN16s and send the ACK carrying the RN16. Correspondingly, the A-IoT terminal can obtain the RN16 from the ACK when the ACK is received, and the A-IoT terminal can determine whether the RN16 is the same as the RN16 sent by the A-IoT terminal; if the RN16 is the same as the RN16 sent by the A-IoT terminal, it is considered that the access is successful, and the step 950 is performed; otherwise, the A-IoT terminal can continue to access.

[0109] Step 950: The A-IoT terminal sends uplink data to the access network device, and the access network device receives the uplink data from the A-IoT terminal.

[0110] For example, the uplink data includes service data related to the inventory service. For example, the uplink data includes at least one of the following: electronic product coding (EPC) of the A-IoT terminal, device ID, sensing data collected by the A-IoT terminal, or storage area data of the A-IoT terminal, and the like, which are not limited in the present application. In the subsequent description of the present application, the device ID in the uplink data is mainly described as an example. It can be understood that the A-IoT terminal can send multiple uplink data to the access network device. In the description of the present application, the A-IoT terminal sends one uplink data as an example, and the number of uplink data sent by the A-IoT terminal is not limited in the embodiments of the present application.

[0111] Step 960: The access network device sends a repeated query command to the A-IoT terminal, and the A-IoT terminal receives the repeated query command from the access network device.

[0112] For example, the A-IoT terminal sends uplink data to the access network device, and receives the repeated query command, which means that the data transmission of the A-IoT terminal is successful. At this time, the A-IoT terminal can flip the flag bit corresponding to the session from A to B. For example, the repeated query command includes a session identifier, for example, session S0. When the A-IoT terminal receives the repeated query command, the A-IoT terminal can flip the flag bit corresponding to session S0 from A to B. The purpose of such operation is that in one round of inventory, the access network device may send the query command multiple times to perform the inventory service. After step 950, if the access network device sends the query command again to perform the inventory service, since the flag bit corresponding to the session of the A-IoT terminal is B, the A-IoT terminal will not respond to the query command of the access network device again, thereby avoiding that the same A-IoT terminal is inventoried multiple times in one inventory period.

[0113] Step 970: The access network device sends uplink data to the first core network element, and the first core network element receives the uplink data from the access network device.

[0114] For example, the uplink data includes one or more device identifiers (device IDs) of the A-IoT terminal. It can be understood that the access network device can inventory one or more A-IoT terminals through one inventory, and the one or more A-IoT terminals may all meet the conditions in steps 910 to 940. The A-IoT terminal reports its device identifier to the access network device through the uplink data in step 950. The access network device reports the received device identifier of the one or more A-IoT terminals to the first core network element. For example, the access network device reports a device list including the device identifier of the one or more A-IoT terminals to the first core network element. The first core network element can take the device identifier included in the device list as the inventory result corresponding to the inventory service request sent in step 900b.

[0115] Different from the flowchart in FIG. 9, in the present application, the flag bit can not be introduced. For example, when the A-IoT terminal receives the paging or selection message, if the mask carried in the paging or selection message is consistent with the mask information of the A-IoT terminal, the A-IoT terminal considers that it is paged or selected, and the A-IoT terminal can access the access network device.

[0116] In the current scheme, the A-IoT terminal cannot support the parallel of multiple services. For example, in order to ensure the smooth progress of the service, the reader needs to send services with different session IDs without overlapping, the later service needs to wait until the previous service is completed, and if the device is out of power during the execution of the previous service, the device needs to wait for charging (for tens of seconds), which brings additional delay to the subsequent service.

[0117] For example, as shown in FIG. 10, for the service with session ID 1, the reader sends a paging message including session ID 1. When the device receives the paging message, the mask carried in the paging message matches the mask information of the device, the device is paged, and the device accesses the reader. The device receives a query message carrying Q value and other information. According to the Q value, random access can be performed, the corresponding uplink data is reported, the transmission of the service corresponding to session ID 1 is successful, and the device saves the state information corresponding to session ID 1 (the transmission of the service is successful). The device receives a paging message including session ID 2. In the current scheme, when the device receives a paging message including a new session ID (such as session ID 2), there is no corresponding solution for how the device processes the state information of the original session ID (such as session ID 1). For example, in one design, when the device receives a paging message including a new session ID, the device releases / empties the state information of session ID 1 saved by the device. For the reader side, in order to avoid that some devices do not receive the initial paging message due to low power, the reader also sends a retransmitted paging message. In the above design, since the device releases the state information corresponding to session ID 1, the device cannot obtain the state information corresponding to session ID 1 (such as the successful transmission of the service corresponding to session ID 1), and the device will respond to the retransmitted paging message including session ID 1, and the device will repeatedly report the uplink data of the service corresponding to session ID 1, resulting in repeated reporting of uplink data and wasting of transmission resources.

[0118] In view of the above, the present application provides a communication method, including: when the device receives a paging message, the device maintains (for example, continues to save) the state information of the original session ID, so that when the device receives a retransmitted paging message including the original session ID, the device can obtain the state information of the original session ID, avoid repeatedly reporting the service data of the original session ID, and save transmission resources.

[0119] In the following description, a first device and a second device are described as performing subjects. The first device can be a device with a tag / device function, and the second device can be a device with a reader function. The method of the present application can be applied to various network architectures. For example, in the network architectures shown in FIG. 2, FIG. 3, FIG. 4a, FIG. 4b and FIG. 5, the first device is an A-IoT terminal, and the second device can be an access network device or a terminal, respectively, or even the second device can be an intermediate node or an auxiliary node. It can be understood that in the flowcharts shown in FIG. 11 and FIG. 19 of the present application, the performing subjects can be the first device and the second device, or can be a module, unit or component (such as a chip, chip system, processor, circuit or other) in the first device or the second device. When the performing subject is a module, unit or component in the first device / second device, the receiving / sending can be understood as input / output, i.e., the module communicates with other modules or components of the first device or the second device. In addition, the processing performed by a single performing subject can also be divided into processing performed by multiple performing subjects, which can be logically and / or physically separated. For example, when the second device is an access network device, the processing performed by the access network device can be divided into processing performed by at least one of a CU, a DU, an RU, etc.

[0120] As shown in FIG. 11, a flowchart is provided, including:

[0121] Step 1110: The second device sends a first message, and the first device receives the first message.

[0122] The first message is used to page or select or trigger the first device, and the first message includes a first identifier. For example, the first identifier can be a session identifier, which can be seen from the description of Example 1 below, or the first identifier can be a device identifier (such as an identifier of the second device), which can be seen from the description of Example 2 below.

[0123] Step 1120: The second device sends a second message, and the first device receives the second message.

[0124] The second message includes a second identifier, which can be seen from the description of Case A in Example 1 below, or the second message includes the second identifier and a first indication, and the first indication is used to instruct the first device to maintain state information corresponding to the first identifier, which can be seen from the description of Case B in Example 1 below. Similarly, the second identifier can be a session identifier, or a device identifier (such as an identifier of a third device).

[0125] The first message is used to page or select or trigger the first device, and there is no limitation on whether the second message is used to page the first device. For example, the second message is used to page at least one device, which includes or does not include the first device. For example, the first message or the second message can carry identification information, which is used to select, page or screen a group of devices. For example, the identification information can be mask information, a group ID, a device ID, or a temporary ID, and there is no limitation. Alternatively, the first message or the second message can not carry identification information, and in this case, the first message can be used to select, page or screen all devices that receive the first message or the second message. Taking the mask as an example: for example, the first message or the second message does not carry a mask, and it can be considered that all devices that receive the corresponding message are selected or paged. Alternatively, the first message or the second message carries a mask, and the device that receives the message can determine whether it meets the condition of being paged or selected according to the value of the mask. For example,

[0126] In an implementation, the first message or the second message includes a mask, which is used to select or page a group of devices. For example, the mask indicates the following three pieces of information: a start position (such as the first field), a bit length (such as 4 bits), and bit information (such as 1001). When the first device receives the mask information, the first device obtains 4 bits of information starting from the first field of the device ID of the first device, and if the 4 bits of information are 1001, it means that the first device is paged or selected. In this application, the first message or the second message does not carry mask information, and includes at least one of the following: the value of the mask information carried in the first message or the second message is equal to 0 (such as mask = 0), or the value of the mask field is equal to 0 (such as mask field = 0), or the value of the information used to indicate the bit length in the mask is equal to 0.

[0127] The first message or the second message is not limited in name. For example, the first message or the second message can be referred to as a select message, a paging message, an initial trigger message, a trigger message, a downlink trigger message, a paging-like message, or the like. The first message or the second message is used to instruct a first device (e.g., a device device) to access a second device (e.g., a reader). For example, when the second device is an access network device, the first message or the second message is used to instruct the first device to access the access network device. Alternatively, when the second device is a terminal, the first message or the second message is used to instruct the first device to access the terminal. It can be understood that the first device can access a network (e.g., an access network device) through the terminal. In addition, the first message or the second message is also used to trigger / instruct the first device to send uplink data, or to trigger / instruct / request the first device to perform a certain service. For example, the first message is used to trigger / instruct / request the first device to perform a service corresponding to a first session identifier, and the second message is used to trigger / instruct / request the first device to perform a service corresponding to a second session identifier. The service can be at least one of the following: a paging service, an inventory service, a command service (such as reading, writing, deactivation, locking, etc.), a positioning service, a sensing service, and the like.

[0128] In an implementation, the first message or the second message can be triggered by a first core network element. For example, before receiving the first message or the second message, the second device receives a service request (e.g., an A-IoT service request) sent by the first core network element, which is used to request an inventory service, a read / write command service, a sensing service, a positioning service, a locking service, or a deactivation service, etc. Optionally, the service request includes the first identifier or the second identifier. The second device sends the first message including the first identifier or the second message including the second identifier according to the trigger of the service request. The second device can send the first message or the second message in a broadcast or groupcast manner.

[0129] Step 1130: The second identifier is different from the first identifier, or the state information corresponding to the first identifier is maintained according to the first indication.

[0130] The maintaining of the state information corresponding to the first identifier can also be referred to as: no longer releasing the state information corresponding to the first identifier, or continuing to save the state information corresponding to the first identifier, or saving the state information corresponding to the first identifier within a first time length (which can be predefined (e.g., specified by a protocol) or preconfigured, or indicated by another device (e.g., a second device) to the first device), or the state information corresponding to the first identifier being valid for a long time, etc. It can be understood that the state information corresponding to the first identifier refers to state-related information of the first identifier; for example, the state information corresponding to the first identifier can be alternatively described as: transmission state information of a service corresponding to the first identifier, or service information corresponding to the first identifier, etc., as described below. Alternatively, the state information corresponding to the first identifier can refer to a paging state of the first identifier, for example, the first identifier is not paged, that is, the first device does not receive a first message (e.g., a paging message) including the first identifier. At this time, the state information corresponding to the first identifier can be alternatively described as: paging state information corresponding to the first identifier, or paging information corresponding to the first identifier, etc.

[0131] In one implementation, when the first device receives a second message including a second identifier, the first device determines whether the first device satisfies a paging condition, for example, the first device matches the identifier information (e.g., a mask) included in the second message, and then the first device maintains the state information corresponding to the first identifier.

[0132] In one implementation, when the first device receives a first message including a first identifier, for example, the first message does not satisfy a paging condition, for example, the identifier information (e.g., a mask) included in the first message does not match the first device, and then the first device sets / reset the state of the first identifier as not paged or not successful.

[0133] In one implementation, the state information corresponding to the first identifier includes: successful / completed transmission of a service corresponding to the first identifier; or unsuccessful / failed / uncompleted transmission of the service corresponding to the first identifier. The successful / completed transmission of the service corresponding to the first identifier includes at least one of the following:

[0134] 1. Successful (random) access, or successful contention resolution / conflict resolution, for example, the first device successfully receives an ACK (acknowledgement) including an RN16 sent by the first device.

[0135] 2. Successful data transmission, for example, successful transmission of uplink data (e.g., a device identifier), and / or successful transmission of data related to a command. It can be understood that the uplink data can be sent in a random access process, or the first device can send the uplink data after successful random access.

[0136] For example, in the case that the first device successfully receives the first message (e.g., the first message is a paging message), the first device can perform at least one of the following: not responding to a retransmission of the first message (e.g., responding to a retransmission of the first message); not performing a subsequent random access procedure and / or data transmission procedure (e.g., not responding to an access opportunity trigger message (e.g., a Query) after the first message); and / or responding to a new transmission of the first message.

[0137] Correspondingly, in the case that the first device does not successfully receive the first message (e.g., the first message is a paging message), the first device can perform at least one of the following: reattempting a random access procedure and / or retransmitting data; responding to a retransmission of the first message; performing a retransmission of the first message (e.g., the first device can respond to a retransmission of the first message if the retransmission satisfies a paging condition, such as a mask match); and / or responding to a new transmission of the first message.

[0138] 1. a random access failure or a contention resolution failure (e.g., the first device does not receive an ACK from a RN 16 that includes a transmission from the first device).

[0139] 2. a data transmission failure (e.g., an uplink data transmission failure, a command-related data transmission failure, etc.).

[0140] Correspondingly, in the case that the first device does not successfully receive the first message (e.g., the first message is a paging message), the first device can perform at least one of the following: reattempting a random access procedure and / or retransmitting data; responding to a retransmission of the first message; performing a retransmission of the first message (e.g., the first device can respond to a retransmission of the first message if the retransmission satisfies a paging condition, such as a mask match); and / or responding to a new transmission of the first message.

[0141] Optionally, the status information corresponding to the first identity further includes an unpaged state, i.e., the first device does not receive the first message (e.g., a paging message) or receives the first message but the identity information (e.g., a mask) of the first message does not match the identity information (e.g., a mask) of the first device. In the unpaged state, the first device can perform one or more of the following: not reattempting a random access procedure and / or retransmitting data; responding to a retransmission of the first message (e.g., if the retransmission satisfies a paging condition, such as a mask match); and / or responding to a new transmission of the first message.

[0142] Correspondingly, in the case that the first device does not successfully receive the first message (e.g., the first message is a paging message), the first device can perform at least one of the following: reattempting a random access procedure and / or retransmitting data; responding to a retransmission of the first message; performing a retransmission of the first message (e.g., the first device can respond to a retransmission of the first message if the retransmission satisfies a paging condition, such as a mask match); and / or responding to a new transmission of the first message.

[0143] In one implementation, one identity can correspond to one status information, which can be referred to as the status information corresponding to the identity, such as the status information corresponding to the first identity, or the status information corresponding to the second identity. For example, the status information corresponding to one identity can be represented by 1 bit. For example, identity 1 corresponds to 1 bit, and identity 2 corresponds to another 1 bit. For example, 1 represents that the transmission status corresponding to the identity is successful, and 0 represents that the transmission status corresponding to the identity is unsuccessful. Of course, the status corresponding to one identity can also be greater than 2 states, such as 3 states, at which time 2 bits can be allocated for one identity. Or, it can be implemented by hardware. For example, each identity corresponds to a module (such as a capacitor or a latch); if the module corresponding to one identity has electricity, it means that the status corresponding to the identity is maintained, and discharging the module means that the status corresponding to the identity is no longer maintained, that is, if the module corresponding to one identity has no electricity, it means that the status corresponding to the identity is not maintained. At this time, 1 bit or high and low levels, etc. can be used to represent different states corresponding to the identity.

[0144] In one implementation, the first message received by the first device includes mask 1 and identity 1 (such as the first identity), and mask 1 matches the mask information of the first device, indicating that the first device is paged, or the first message is used to page the first device. The second message received by the first device includes mask X and identity 2 (such as the second identity), and X is used to identify a mask, such as X taking the value of 1, mask X is essentially mask 1, and the value of X can be a positive integer. In one understanding, the first device obtains identity 2 in the second message; when identity 2 is different from identity 1, the action of step 1130 is performed, such as the action of maintaining the status information corresponding to the first identity, or the action of maintaining the status information corresponding to the first identity according to the first indication. At this time, whether the second message pages the first device is not concerned, that is, mask X can match or not match the mask information of the first device. Or, the first device obtains mask X in the second message, and determines whether the mask X matches the mask information of the first device. If it is matched, the first device is paged by the second message, or described as the second message is used to page the first device. At this time, the action of step 1130 is performed: when the first identity is different from the second identity, the status information corresponding to the first identity is maintained, or the status information corresponding to the first identity is maintained according to the first indication. If it is not matched, the first device is not paged by the second message, or described as the second message is not used to page the first device. At this time, the first device no longer responds to the second message, and no longer performs the action in step 1130.

[0145] Optionally, in an implementation, the second device can also reset the state information corresponding to one or more identities maintained by the first device. For example, the second device sends a second indication, and the first device receives the second indication, where the second indication is used to indicate to reset the state information corresponding to one or more identities maintained by the first device. The first device resets the state information corresponding to the one or more identities maintained by the first device according to the second indication. Further, the second device can also send one or more identities, and the first device receives the one or more identities, where the one or more identities are associated with the second indication, i.e., the first device resets the state information corresponding to the one or more identities associated with the second indication according to the second indication. For example, the one or more identities and the second indication can be carried in the same message, and the one or more identities are used to indicate that the one or more identities are associated with the second indication. For example, the second device sends a message, and the first device receives the message, where the message includes the one or more identities. The first device can determine to reset the state information corresponding to the one or more identities according to the name of the message or the like. Alternatively, the message includes the second indication in addition to the one or more identities, and the first device resets the state information corresponding to the one or more identities according to the second indication. In a possible implementation, the second device sends a paging message, and the first device receives the paging message, where the paging message includes a first identity and the second indication. The first device resets the state information corresponding to the first identity according to the second indication. Alternatively, the first device resets the state information corresponding to all identities maintained by the first device according to the second indication. The first device resetting the state information corresponding to a session identity can be specifically resetting the state information corresponding to the session identity to none, or resetting the state information corresponding to the session identity to unsuccessful, or discarding / clearing / releasing the state information corresponding to the session identity, or the like.

[0146] In an implementation, the first device maintains the state information corresponding to an identity for a maximum time, e.g., the first device maintains the state information corresponding to an identity for no more than Tmax, where Tmax can be predefined, e.g., defined by a protocol, or indicated or configured to the first device by another device. Alternatively, for an identity, the first device stops maintaining or resetting the state information corresponding to the identity when the maximum number of transmissions of services corresponding to the identity reaches a first value, e.g., the first device stops maintaining or resetting the state information corresponding to the identity when the number of times of receiving a paging message including the session identity reaches the first value. The first value can be predefined, or indicated or configured to the first device by another device.

[0147] In one implementation, the first message or the second message can be called a paging message. For example, the first message or the second message can be an initial paging message or a re-paging message. In one implementation, the initial paging message carries an identifier indicating the initial transmission, and / or the re-paging message carries an identifier indicating a retransmission. Based on these identifiers, the first device can identify whether a paging message is an initial paging message or a re-paging message. The purpose of a re-paging message is to allow devices that did not receive the initial paging message to be paged. For example, due to battery issues, some devices did not receive the initial paging message. After these devices have finished charging, they can receive the re-paging message, thus enabling these devices to participate in the corresponding business process (such as inventory management).

[0148] Similarly, query messages can also be retransmitted. For example, a retransmitted query message might be used to reallocate Q values, triggering multiple rounds of random access. The Q value carried in the query message is related to the number of remaining unconnected devices. For instance, if the initial query message sent by the second device carries a Q value of 10, it indicates that 2 devices will be allocated access. 10 There are 2 access opportunities, and each device occupies one access opportunity. 10 One access opportunity can achieve 2 10 One device can access the network. The Q value carried in the retransmission query message sent by the second device can be less than 10, for example, Q can be equal to 5. This is mainly because some devices have already successfully accessed the network according to the initial query message. Therefore, the retransmission query message can allocate fewer transmission opportunities. By reducing the Q value, efficiency is improved, and excessive retransmission opportunities and access opportunities are avoided.

[0149] In this application, the second device has the function of a reader / writer, and the first device has the function of a tag / device. The transmission direction from the second device to the first device is called downlink or reader-to-device (R2D). The transmission direction from the first device to the second device is called uplink or device-to-reader (D2R).

[0150] Optionally, in an implementation, the second device sends a third message, and the first device receives the third message. The third message includes the first identity. The first identity can be a first session identity, an identity of the second device, and / or the like. Further, the third message includes the mask information. The mask information included in the third message matches the mask information of the first device. The first device is paged or selected. The first device can determine whether to respond to the third message or not according to the maintained state information corresponding to the first identity. For example, the third message can be a retransmitted paging message. If the first identity maintained by the first device corresponds to the state information of successful or completed transmission, the first device can not respond to the third message, such as not accessing the second device. Or if the first identity maintained by the first device corresponds to the state information of failed or incomplete transmission, the first device can respond to the third message and / or re-access. For example, the first device accesses the second device according to the paging of the third message, and / or the like. For example, the first device can access the second device according to the random access configuration information (such as random access time domain and / or frequency domain resource configuration information, and / or the like).

[0151] In an implementation, the first device responds to the third message. It can be understood that the first device performs random access after receiving the third message, and / or monitors the access opportunity trigger message, and / or performs data transmission. For example, the first device can not immediately respond to the access opportunity trigger message or perform data transmission, but confirms the access opportunity after one or more R2D messages or a time offset, and then performs random access and / or data transmission. Optionally, the first device can access the second device according to the random access configuration information (such as random access time domain and / or frequency domain resource configuration information) indicated by the third message.

[0152] In an implementation, the "maintaining" the corresponding behavior can further include: if the status information corresponding to the first identity is not successful, after the first device receives the second identity (e.g., receives the second message associated with the second identity), the first device can continue to respond to the service procedure associated with the first identity, such as performing (the service procedure associated with the first identity) re-access / re-transmission, to continue to complete the service associated with the first identity. For example, if the status information corresponding to the first identity is successful, after the first device receives the second identity (e.g., receives the second message associated with the second identity), the first device does not need to perform the service procedure associated with the first identity, such as not responding to / dropping the re-transmission paging message associated with the first identity, not performing the subsequent random access procedure and / or data transmission procedure (such as not responding to the access opportunity trigger message (e.g., Query) after the paging message), or not performing re-access / re-transmission data. For example, if the status information corresponding to the first identity is not paged, after the first device receives the second identity (e.g., receives the second message associated with the second identity), the first device does not perform the subsequent random access procedure and / or data transmission procedure (such as not responding to the access opportunity trigger message (e.g., Query)), or does not perform re-access / re-transmission data.

[0153] Example 1 (may be considered as an example): The first identity and the second identity can be allocated by a first core network element, for example, the first core network element can be an access and mobility management function (AMF), an ambient IoT management function (AIoTMF), a tag management function (TMF), an ambient IoT function (AIoTF), or an application function (AF), etc. The first identity and the second identity are used to identify a service request initiated by the first core network element. For example, the first identity and the second identity can be session identities, for example, the first identity is called the first session identity, and the second identity is called the second session identity. The first identity is associated with a first service request / procedure, and the second identity is associated with a second service request / procedure, the first service request / procedure and the second service request / procedure are different, and the first service request / procedure and the second service request / procedure correspond to a service request or procedure sent by the first core network element, respectively.

[0154] In the present application, the "session" in the session ID can also be replaced by the following descriptions: service, task, request, transaction, process, procedure, etc., and the present application does not limit the name. In the present application, the "service" can be replaced by the following descriptions: task, procedure, or transaction, etc. For example, the inventory service can be replaced by: inventory task, inventory procedure, inventory transaction, etc. It can be understood that the "service" is a service related to the procedure, including at least one of the following: access procedure, data transmission procedure, etc., or it can be understood that the service is to perform the corresponding procedure. Among them, the access procedure can be a random access procedure, such as contention-based random access or contention-free random access. The access procedure and the data transmission procedure are not strictly distinguished. After the access procedure is completed, the data transmission procedure is executed. Or, in the access procedure, data transmission can be performed. For example, in the access procedure, the uplink data related to the service is reported, such as the device ID. For example, the message 1 sent by the device to the reader includes the RN16 and the uplink data related to the service. Or in the contention-free random access, the device can send D2R / uplink data in message 1.

[0155] In the present application, the service and the session ID may not be a one-to-one correspondence. For example, there are four session IDs, S0 to S3, and each time the first core network device triggers a service paging, it can assign a session ID to the current triggered service paging, which can be any one of S0 to S3. Therefore, even for the same service, the session ID assigned by the first core network element may be different. Similarly, for paging of different services, the session ID assigned by the first core network element may also be the same. In one implementation, when the first core network device triggers a service paging, it can assign the identifier S0 to it; then, when the first access network device triggers the paging of the current service or another service, it can assign the identifier S1 to it; and so on, when the session identifier S3 is used up, the session identifier 1 can be used again.

[0156] Taking the first identifier and the second identifier as session identifier 1 and session identifier 2, and the second device and the first device as the reader and the device, respectively, the present application is described in combination with the following case A and case B:

[0157] Case A: The first session identifier and the second session identifier are different, and the first device maintains the state information corresponding to the first session.

[0158] As shown in FIG. 12, the reader sends a paging message to the device, and the paging message includes session identifier 1 and mask 1. The paging message can be an initial transmission of the paging message or a retransmission of the paging message, and the like, without limitation. The mask 1 matches the mask information of the device, and the device is paged. The reader sends a query message and a query Rep message to the device; the session identifier 1 corresponds to a failed or incomplete service transmission.

[0159] The reader sends a paging message to the device, and the paging message includes mask 1 and session identifier 2. The paging message can be an initial transmission of the paging message or a retransmission of the paging message, and the like, without limitation. The session identifier 2 is different from the session identifier 1, and the device maintains the state information corresponding to the session identifier 1. For example, the state information maintained by the device corresponding to the session identifier 1 can be that the session identifier 1 corresponds to a failed or incomplete service transmission. The reader sends a query message to the device, the device sends a message 1 (msg1) to the reader, the reader sends a message 2 (msg2) to the device, the device sends a message 3 (msg3) to the reader, the reader sends a query Rep message to the device, and the session identifier 2 corresponds to a successful service transmission. The message 1 can be an RN16, the message 2 can be an ACK corresponding to the RN16, and the message 3 can be uplink data, and the like.

[0160] The device sends a retransmission of the paging message to the reader, and the retransmission of the paging message includes the session identifier 1 and the mask 1. The session identifier 1 is different from the session identifier 2, and the device maintains the state information corresponding to the session identifier 2. For example, the state information maintained by the device corresponding to the session identifier 2 is that the session identifier 2 corresponds to a successful service transmission. It can be understood that, at this time, the device maintains a total of two pieces of state information of the session identifiers, i.e., the state information corresponding to the session identifier 1 and the state information corresponding to the session identifier 2, and the like. The reader sends a query message to the device, the device sends a message 1 to the reader, the reader sends a message 2 to the device, the device sends a message 3 to the reader, the reader sends a query Rep message to the device, and the session identifier 2 corresponds to a successful service transmission.

[0161] The device sends a paging message to the reader, and the paging message includes the session identifier 1, the mask 1, and second indication information. The paging message can be an initial transmission of the paging message or a retransmission of the paging message, without limitation. The second indication information can be referred to as a non-maintenance or reset indication. The device resets the state information corresponding to the session identifier 1 according to the second indication, and the device can continue to maintain the state information corresponding to the session identifier 2 (FIG. 12 mainly describes this case), or the device can reset the state information corresponding to the session identifier 1 and the session identifier 2 according to the second indication, that is, the device can reset all the state information of the session identifiers maintained according to the second indication.

[0162] Figure 13 differs from Figure 12 in that in Figure 13, the service transmission corresponding to session identity 1 is successful or completed. When the device receives the paging message including session identity 2 and the mask 1, since the session identity 2 is not the same as the session identity 1, the device maintains the state information corresponding to the session identity 1, such as the state information corresponding to the session identity 1 maintained by the device is that the service transmission corresponding to the session identity 1 is completed or successful. When the device receives the retransmitted paging message including the session identity 1 and the mask 1, since the state information corresponding to the session identity 1 maintained by the device is that the service transmission corresponding to the session identity 1 is successful or completed, the device no longer responds to the retransmitted paging message including the session identity 1, such as the device no longer accesses the reader according to the paging message.

[0163] In an implementation, in the case A, when the device receives a paging message including a first session identity, the device can maintain the state information of other session identities (different from the first session identity) which the device has responded by default; when the device receives a paging message including a second indication (reset indication), the device can reset the state information of all the session identities maintained by the device.

[0164] In case B, the first device maintains the state information corresponding to the first identity according to the first indication.

[0165] As shown in Figure 14, the reader sends a paging message to the device, the paging message including the session identity 1 and the mask 1. The paging message can be an initial paging message or a retransmitted paging message, without limitation. The mask 1 matches the mask information of the device, and the device is paged. The reader sends a query and a repeated query to the device; the service transmission corresponding to the session identity 1 fails or is not completed.

[0166] The reader sends a paging message to the device, the paging message including the session identity 2, the mask 1 and a first indication. The paging message can be an initial paging message or a retransmitted paging message. The first indication can also be referred to as a maintenance indication, and the first indication is used to instruct the device to maintain the state information corresponding to the session identity (such as the session identity 1). The device maintains the state information corresponding to the session identity 1 according to the first indication. The state information corresponding to the session identity 1 maintained by the device can be that the service transmission corresponding to the session identity 1 fails or is not completed. The reader sends a query message to the device, the device sends a message 1 (msg1) to the reader, the reader sends a message 2 (msg2) to the device, the device sends a message 3 (msg3) to the reader, the reader sends a repeated query message to the device, and the service transmission corresponding to the session identity 2 is successful.

[0167] The reader sends a retransmission paging message to the device, the retransmission paging message including session identifier 1, mask 1 and the first indication. The device maintains the state information corresponding to session identifier 2 according to the first indication, e.g. the transmission of the service corresponding to session identifier 2 is successful or completed. It can be understood that the device maintains the state information corresponding to two session identifiers, i.e. the state information corresponding to session identifier 1 and the state information corresponding to session identifier 2. Further, since the state information corresponding to session identifier 1 maintained or saved by the device is that the transmission of the service corresponding to session identifier 1 is not completed or failed, the device responds to the retransmission paging message including session identifier 1. The device receives a query message from the reader, the device sends message 1 to the reader, the reader sends message 2 to the device, the device sends message 3 to the reader, and the reader sends a repeated query message to the device. The transmission of the service corresponding to session identifier 1 is successful or completed.

[0168] The reader sends a paging message to the device, the paging message including session identifier 1 and mask 1. The paging message can be a first transmission paging message or a retransmission paging message. Since the paging message does not carry the first indication for indicating maintenance, the device can reset the state information corresponding to session identifier 1. Further, the device can also reset the state information corresponding to session identifier 2.

[0169] The difference between FIG. 15 and FIG. 14 is that in FIG. 15, the transmission of the service corresponding to session identifier 1 is successful, and the state information corresponding to session identifier 1 maintained by the device is that the transmission of the service corresponding to session identifier 1 is successful or completed. When the device receives the retransmission paging message including session identifier 1, since the device can determine that the transmission of the service corresponding to session identifier 1 is successful or completed according to the state information of session identifier 1 maintained by the device, the device no longer responds to the retransmission paging message including session identifier 1.

[0170] In an implementation, when the device receives a paging message including the first indication (maintenance indication), the device maintains the state information of all session identifiers, e.g. the device maintains the state information of the current session identifier and the session identifier that has been responded to before. When the device receives a paging message without carrying the first indication (maintenance indication), the device resets the state information of all sessions (whether the transmission of the service of the session is successful or failed) maintained by the device.

[0171] In the solution of case B, the reader needs to know which service of which session, such as buffered in the reader, is scheduled at different time. In addition, if multiple readers have concurrent services, case B can not be as applicable as case A. Because in case B, the reader indicates the action of maintaining or resetting other sessions in the paging message of the current session, but there are corresponding solutions, such as, the readers cooperate with each other to obtain the session information, such as, the access network device implements the function of the reader, and then the different access network devices can interact the session information through the Xn interface. Or, the terminal implements the function of the reader, and then the terminal can know the session information of the surrounding readers through the session information configured / indicated / informed by the access network device.

[0172] Example 2 (which can be regarded as another example): the first identifier and the second identifier are identifiers of devices (such as readers). For example, the first message is from a second device (such as reader 1), and the first identifier is an identifier of the second device (such as an identifier of reader 1); the second message is from a third device (such as reader 2), and the second identifier is an identifier of the third device (such as an identifier of reader 2).

[0173] Taking the first message and the second message as paging messages, and the first identifier and the second identifier as reader identifier 1 (read ID 1, RID 1) and reader identifier 2 (read ID 2, RID 2) as an example, the present application is explained as follows:

[0174] As shown in FIG. 16, the reader 1 sends a paging message to the device, and the paging message includes the reader identifier 1 and the mask 1. The paging message can be an initial transmission paging message or a retransmission paging message. The mask 1 matches the mask information of the device, and the device is paged. The reader 1 sends a query message and a repeated query message to the device, and the query message and the repeated query message both include the reader identifier 1. The corresponding service transmission of the reader 1 fails or is not completed.

[0175] The reader 2 sends a paging message to the device, and the paging message includes the reader identifier 2 and the mask 1. The paging message can be an initial transmission paging message or a retransmission paging message. Since the reader identifier 2 is different from the reader identifier 1, the device maintains the state information of the reader identifier 1, such as that the corresponding service transmission of the reader identifier 1 is not successful or fails. The reader 2 sends a query message and a repeated query message to the device, and the query message and the repeated query message both include the reader identifier 2.

[0176] The reader 1 sends a retransmitted paging message to the device, the retransmitted paging message including the reader identification 1. Further, the retransmitted paging message also includes the mask 1. Since the reader identification 1 is different from the reader identification 2, the device maintains the state information of the reader identification 2, such as the transmission of the service corresponding to the reader identification 2 fails or is not completed. Meanwhile, the device can obtain the state information corresponding to the reader identification 1 as the transmission is not completed or fails according to the reader identification 1 included in the retransmitted paging message; the device sends a message 1 to the reader 1 in response to the retransmitted paging message, the device receives a message 2 from the reader 1, the device sends a message 3 to the reader 1, the device receives a repeated query message from the reader 1, and the transmission of the service corresponding to the reader 1 is successful or completed.

[0177] The device receives a retransmitted paging message from the reader 1, the retransmitted paging message including the reader identification 1 and a second indication, such as a non-maintenance or reset indication. The device resets the state information corresponding to the reader identification 1 according to the second indication, and maintains the state information corresponding to the reader identification 2 (mainly described in FIG. 16).

[0178] The example shown in FIG. 16 has a principle similar to the case A of the example 1. The scheme of the example 1 case B can also be applied to the scheme of this example 2. The paging message sent by the reader includes a first indication. The device maintains the state information corresponding to the original reader identification according to the first indication. When the device receives a paging message not including the first indication, the device resets the state information corresponding to the reader identification.

[0179] It can be understood that the downlink message (or R2D message) sent by the reader to the device carries the identification of the reader. For example, the R2D message such as the paging message, the query message, the message 2 and the repeated query message sent by the reader to the device carries the identification of the reader (reader identification 1). The uplink message (or D2R message) sent by the device to the reader can carry the identification of the reader. For example, the message 1 and the message 3 sent by the device to the reader can carry the identification of the reader.

[0180] The scheme of the above example 1 and the scheme of the example 2 can also be combined, for example, the first message or the second message sent by the second device includes a session identification and / or a reader identification.

[0181] Through the above design, the parallel of multiple reader services can be realized.

[0182] Optionally, in an implementation, the second device can send a fourth message to the first device, and the first device receives the fourth message from the second device, the fourth message can be referred to as a downlink message or R2D message. For example, the fourth message is used for at least one of the following: triggering at least one access opportunity, indicating the number of access opportunities, indicating resource configuration information, indicating random access success (e.g., indicating contention resolution success, or indicating contention-free random access), data transmission success / failure, command, etc. For example, the fourth message can be a query message, or a repeated query message, the query message or the repeated query message is used for at least one of the following: triggering at least one access opportunity, indicating the number of access opportunities, or indicating resource configuration information, etc. The name of the query message is not limited, for example, the query message can also be referred to as an access round trigger / indication. Meanwhile, in the description of the present application, the name of the repeated query message is not limited. For example, the repeated query message is used for triggering or indicating the next access opportunity, which can also be understood as indicating / associating with the boundary (start or end) of an access opportunity, the repeated query message can also be referred to as an access occasion indication / trigger. In the present application, the access opportunity can also be referred to as an access occasion, an access time slot, etc., each access opportunity can allow the device to send at least one of the following: access (request), contention resolution, and / or data transmission, etc. Alternatively, the fourth message can be a message 2, for example, the message 2 is an ACK including RN16, and the fourth message is used for at least one of the following: indicating random access success, or indicating contention resolution success, etc. In the present application, the ACK is used to indicate contention resolution success, and the RN16 of the device with contention resolution success can be carried in the ACK, the name of the ACK is not limited, for example, the ACK can also be referred to as an access ID response, an access response, a UE / device contention resolution identity; the RN (e.g., RN16, or RN with other length) is used for contention resolution, or is used to distinguish different devices in the random access or contention resolution process, the name of the RN is not limited, for example, the RN can be referred to as a random access ID, or a random ID.

[0183] The fourth message includes the first identifier. The first identifier is a first session identifier or an identifier of the device (e.g., an identifier of the second device). The first device responds to or does not respond to the fourth message according to state information corresponding to the first identifier. For example, if the state information corresponding to the first identifier indicates that the service transmission is successful, the first device does not respond to the fourth message. If the state information corresponding to the first identifier indicates that the service transmission is failed or not completed, the first device responds to the fourth message.

[0184] For example, after a paging message, there can be multiple rounds of random access for re-accessing some devices that fail to access. For example, the fourth message is a query message that carries a session identifier, as shown in FIG. 17. The reader sends a paging message to the device, and the paging message includes a session identifier 1 and a mask 1. The mask 1 matches the mask information of the device, and the device is currently screened. For the session identifier 1, the reader initiates a round of random access, and the reader sends a query message and a repeated query message to the device. The device fails to randomly access due to various reasons. The reader sends a paging message to the device, and the paging message includes a session identifier 2 and the mask 1. The reader sends a query message to the device, and the query message includes the session identifier 2. The reader and the tag interact through message 2 and message 3, and the device successfully randomly accesses. The device sends message 3 to the reader to report corresponding uplink data. The reader sends a repeated query message to the device, and the service transmission corresponding to the session identifier 2 is successful. For the session identifier 1, the reader initiates a second round of random access, and the reader sends a query message to the device, and the query message includes the session identifier 1. The device can determine, according to the session identifier 1 included in the query message, that the current process is the process of the service corresponding to the session identifier 1. The reader and the device interact through message 2 and message 3, and the device successfully randomly accesses. The device reports uplink data corresponding to the session identifier 1 in message 3. The reader sends a repeated query message to the device, and the service transmission corresponding to the session identifier 1 is successful.

[0185] Further, in FIG. 17, when the device receives the paging message including the session identifier 2, since the session identifier 2 is different from the previous session identifier 1, the device can maintain the state information corresponding to the session identifier 1, such as that the corresponding service transmission corresponding to the session identifier 1 is not completed. When the device receives the query message including the session identifier 1, the device can query the state information corresponding to the session identifier 1 according to the session identifier 1. Since the state information corresponding to the session identifier 1 maintained by the device 1 is that the corresponding service transmission is not completed, the device responds to the query message including the session identifier 1. It can be understood that the device can respond to the query message including the session identifier 1 when the session identifier 1 is paged (such as the device previously receives or responds to the paging message including the session identifier 1) and the corresponding service / data transmission / access corresponding to the session identifier 1 is not successful (all can be considered as that the transmission of the service corresponding to the session identifier 1 is not successful). For example, according to the Q value included in the query message, the access opportunity is determined, and the reader is accessed.

[0186] Through the above design, in the scenario of multiple services in parallel, multiple rounds of random access can be implemented for one service (such as a session identifier).

[0187] As shown in FIG. 18, a flowchart of a communication method is provided, which is different from the flowchart shown in FIG. 11. In the flowchart shown in FIG. 18, when the first device receives a paging message, if the first identifier included in the new paging message is different from the second identifier currently maintained by the first device (or the second identifier included in the previously received paging message), the first device resets the state information of the second identifier. The flowchart specifically includes the following steps.

[0188] Step 1810: The second device sends a first message, and the first device receives the first message.

[0189] The first message is used to page the first device, and the first message can also be referred to as a paging message or a selection message, etc. The first message includes a first identifier, which can be allocated by the first core network element. The first identifier is used to identify a service request initiated by the first core network element, and the first identifier can be referred to as a first session identifier. Alternatively, the first identifier can be an identifier of the device (such as a reader), such as an identifier of the second device.

[0190] Step 1820: The first identifier is different from the second identifier maintained by the first device, and the first device resets the state information corresponding to the second identifier.

[0191] The first device can maintain the state information of one or more identifiers, at least including the second identifier. The second identifier can be an identifier allocated by the first core network element, such as a second session identifier. Alternatively, the second identifier can be an identifier of the device (such as a reader), such as an identifier of the third device.

[0192] When the first identity is different from the second identity maintained by the first device, the first device resets the state information corresponding to the second identity. It can be understood that the state information corresponding to the second identity can be specifically: the service transmission corresponding to the second identity is successful, or the service transmission corresponding to the second identity is unsuccessful. Resetting the state information corresponding to the second identity can include: discarding / clearing / releasing the state information corresponding to the second identity, or setting the state information corresponding to the second identity to be null, or setting the state information corresponding to the second identity to be unsuccessful, etc.

[0193] It can be understood that in the state information of one or more identities maintained by the first device, in addition to the state information of the second identity, the state information of a third identity is also included. If the third identity is different from the first identity, the first device can also reset the state information corresponding to the third identity.

[0194] In an implementation, when the first device resets the state information corresponding to the second identity, the first device also needs to satisfy the paging condition included in the second message, for example, the first device matches the identity information (such as a mask) included in the second message.

[0195] In an implementation, the first device resets the state information corresponding to the first identity. For example, when the first device receives the first message including the first identity, the first device does not satisfy the paging message, for example, the first device does not match the identity information (such as a mask) included in the first message, and the first device resets the state information of the first identity to be not paged or unsuccessful.

[0196] As an example of steps 1810 and 1820, it includes: the first device receives a second message, the second message including a second identity, and the first device maintains state information corresponding to the second identity; the first device receives a first message, the first message including a first identity; the second message is used to page the first device, for example, the mask included in the second message matches the mask information of the first device. The second message is used to page at least one device, and whether the at least one device includes the first device is not limited. The first identity is different from the second identity, and the first device resets the state information corresponding to the second identity.

[0197] Optionally, in one implementation, the second device can send a third indication, and the first device receives the third indication, the third indication indicating the first device to maintain the state information of the one or more identities. For example, the first device receives a paging message including the third indication, and the first device maintains the state information of the one or more identities according to the third indication. For example, referring to FIG. 14, the retransmitted paging message sent by the reader includes the session identity 1, the mask 1, and the first indication (in this example, the first indication is referred to as the third indication, and the two have the same or similar functions), and the device maintains the state information of the previous session identity 2 and the session identity 1 according to the third indication (or the first indication). Further, the second device can also send one or more identities associated with the third indication information. The first device maintains the state information of the one or more identities according to the third indication.

[0198] In one implementation, the first device resets the state information corresponding to the second identity, and the behavior of the first device includes at least one of the following: for example, if the state information corresponding to the second identity is unsuccessful / successful / unsuccessful, or regardless of the current state information of the second identity, after the first device receives the first identity (such as receiving a paging message associated with the first identity): the first device can reset the state information of the second identity to an unpaged state, such as the first device can not perform re-entry / retransmission regarding the second identity. It can be understood that if it is reset to unsuccessful, it may be misinterpreted: for example, the first device needs to respond to the trigger message associated with the first identity, such as continuing re-entry / retransmission, to continue to complete the service associated with the first identity. In another implementation, after the first device receives the first identity (such as receiving a paging message associated with the first identity): the first device can reset the state information of the second identity to unsuccessful, which can also be an implementation, such as in this scenario, since the second device has sent the first identity, it means that the second identity has ended, and the first device resets the unsuccessful and continues to re-enter the process of the first identity (for the first device, it can be understood as a re-entry, but for the second device, it can be considered as an initial access of a new service). It should be noted that, optionally, before determining whether to (re) enter, it is determined whether it is paged (satisfies the paging condition).

[0199] The application also provides a communication method, comprising: a first device receiving a first message, the first message can be an R2D message, and the first message comprises an identifier of a device (e.g., a reader), such as an identifier of a second device. The first device responds to or does not respond to the first message according to the identifier of the second device and an identifier of a third device saved by the first device, so that in a multi-reader parallel scenario, re-reading of the first device by multiple readers can be avoided, or the first device can avoid incorrect responses to R2D signaling sent by multiple readers.

[0200] As shown in FIG. 19, a flow of a communication method is provided, comprising:

[0201] Step 1910: The second device sends a first message, and the first device receives the first message, wherein the first message comprises an identifier of the second device.

[0202] The first message is a reader-to-device (R2D) message, and the type of the first message is not limited. For example, the first message can be used for at least one of the following: triggering at least one access opportunity, indicating the number of access opportunities, indicating resource configuration information, indicating random access success, data transmission success / failure, or a command. For example, the first message can be a paging message, a query message, a repeated query message, a command message, an acknowledgement (ACK) message, etc.

[0203] Step 1920: The first device responds to or does not respond to the first message according to the identifier of the second device and an identifier of a third device saved by the first device.

[0204] For example, when the identifier of the second device is the same as the identifier of the third device saved by the first device, the first device responds to the first message; or when the identifier of the second device is different from the identifier of the third device saved by the first device, the first device does not respond to the first message.

[0205] In an implementation, the first device responding to the first message can mean that the first device performs random access after receiving the first message, and / or monitors an access opportunity trigger message, and / or performs data transmission. For example, the first device can not immediately respond to the access opportunity trigger message or perform data transmission, but rather confirms the access opportunity after one or more R2D messages or a time offset, and then performs random access and / or data transmission. Alternatively, the first device can access the second device according to random access configuration information (such as random access time domain and / or frequency domain resource configuration information) indicated by the first message.

[0206] In an implementation, the third device sends a second message, and the first device receives the second message, wherein the second message includes the identity of the third device. The second message can be an R2D message, and the type of the second message is not limited. For example, the second message is used for at least one of the following: triggering at least one access opportunity, indicating the number of access opportunities, indicating resource configuration information, or indicating random access success. The first device obtains or saves the identity of the third device. Further, the first device can maintain state information corresponding to the identity of the third device. The first device receives a first message from the second device, and the first message includes the identity of the second device. When the identity of the second device is different from the identity of the third device previously responded or saved by the first device, the first device no longer responds to the first message, thereby avoiding re-reading of the first device by the third device. Optionally, the first device receives a third message, and the third message includes a fourth indication. The first device resets the state information maintained by the first device according to the fourth indication, such as resetting the state information corresponding to the identity of the third device maintained by the first device.

[0207] For example, in a scenario where the coverage areas of multiple readers overlap, the devices located in the overlapping area can be repeatedly read, or the devices in the overlapping area can have problems in responding to R2D messages. For example, as shown in FIG. 20, the coverage areas of reader 1 and reader 2 overlap, and if reader 1 and reader 2 perform inventory operations at the same time, the devices can respond to R2D messages incorrectly. For example, a device receives an R2D message from reader 2 during a random access process of reader 1, which affects the device to select an access resource of reader 1 and an access opportunity trigger process. For example, the device receives an incorrect neighbor zone competition resolution identifier, which causes access failure, or the device receives a repeated query from a neighbor zone after sending message 1, which causes a misjudgment of the end of a current time slot or failure. In this application, the R2D message sent by the reader carries the identity of the corresponding reader, so that the device can identify which reader the R2D message comes from, thereby avoiding the problem of incorrect response to R2D messages.

[0208] In an implementation, as shown in FIG. 21, reader 1 sends a paging message to the device, and the paging message includes reader identifier 1 and mask 1. The device obtains / determines / reads reader identifier 1 from the paging message, and saves reader identifier 1. Reader 1 sends a query message and a repeated query message to the device, and the query message and the repeated query message include reader identifier 1.

[0209] The device receives a paging message, a query message, or a repeated query message from the reader 2, and the paging message, the query message, or the repeated query message includes the reader identification 2. Since the reader identification 2 is different from the previously saved reader identification 1, the device does not respond to the paging message, the query message, or the repeated query message including the reader identification 2. Further, since the reader identification 2 is different from the reader identification 1, the device maintains the state information corresponding to the reader identification 1, and the maintained state information corresponding to the reader identification 1 is that the service transmission corresponding to the reader identification 1 is not successful or not completed.

[0210] The device receives a retransmitted paging message from the reader 1, and the retransmitted paging message includes the reader identification 1. Since the reader identification 1 included in the retransmitted paging message is the same as the previously saved reader identification 1, the device accesses the reader 1 in response to the retransmitted paging message. For example, the device can respond to the retransmitted paging message according to the maintained state information corresponding to the reader identification 1 being that the transmission is not successful or not completed. The device sends message 1 to the reader 1, receives message 2 from the reader 1, the message 2 includes the reader identification 1, sends message 3 to the reader 1, and receives a repeated query message from the reader 1, the repeated query message includes the reader identification 1. The service transmission corresponding to the reader 1 is successful.

[0211] The device receives a retransmitted paging message from the reader 1, and the retransmitted paging message includes the reader identification 1 and a second indication (such as a do not maintain or reset indication). Optionally, the reader identification 1 is different from the reader identification 2, and the device can maintain the state information corresponding to the reader identification 2, and the state information corresponding to the reader identification 2 is that the service transmission corresponding to the reader identification 2 is successful. According to the second indication, the device resets the state information corresponding to the reader identification 1, maintains the state information corresponding to the reader identification 2 (FIG. 21 mainly describes this case), or according to the second indication, the device resets the state information corresponding to all the reader identifications (including the reader identification 1 and the reader identification 2) maintained by the device.

[0212] Through the above design, in the scenario of multiple readers in parallel, the device only responds to the R2D message of one reader, and the problem of responding to the R2D message by mistake is avoided.

[0213] It can be understood that in the scheme of embodiment three, the reader identification can also be carried in the D2R message, such as the reader identification carried in the message 1 and the message 3 sent by the first device. In this application, the paging message and the query message can also be combined into one message, such as an initial message.

[0214] The solution of the present application can be applicable to an ORAN architecture. For example, the second device is an access network device, and the access network device can adopt the ORAN architecture. Under the ORAN architecture, the access network device includes a CU, a DU, a RAN intelligent controller (RIC), and the like. The actions performed by the second device in the above embodiments one to three can be specifically performed by the CU, the DU, the RIC, and the like. For example, the RIC can estimate the number of devices (e.g., the first device) of the current service and the processing time of the service according to the priori information. The RIC can send indication information to the CU, to indicate the end time corresponding to the service, and the CU can instruct the first device to maintain / reset the state information of the identifier corresponding to the service according to the indicated end time. For example, the CU can send the instruction of maintenance / reset to the first device through the DU.

[0215] In the above embodiments of the present application, the method provided by the embodiments of the present application is introduced from the perspective of the interaction between the first device and the second device. In order to implement each function in the method provided by the embodiments of the present application, the first device or the second device can include a hardware structure and / or a software module, and each function is implemented in the form of a hardware structure, a software module, or a hardware structure plus a software module. Whether a certain function in the above functions is executed in the form of a hardware structure, a software module, or a hardware structure plus a software module depends on the design constraint conditions of the specific application of the technical solution.

[0216] Based on the same design concept as the above method embodiments, FIG. 22 and FIG. 23 are structural schematic diagrams of possible communication apparatuses provided by the embodiments of the present application. These communication apparatuses can implement the functions of the first device or the second device and the like in the above method embodiments, and thus can achieve the beneficial effects possessed by the above method embodiments. In the embodiments of the present application, the communication apparatus can be the first device or the second device, or a unit, a module, or a component and the like (such as a chip, a chip system, a circuit, a processor, or the like) applied in the first device or the second device. In the following description, the “unit” is taken as an example. For example, in the following description, the communication apparatus includes a processing unit and a transceiver unit. The processing unit in the following description can also be replaced by: a processing module or a processing component, and the like. The transceiver unit can also be replaced by: a transceiver unit or a transceiver component. For example, the transceiver component can refer to a communication module.

[0217] As shown in FIG. 22, the communication apparatus 2200 includes a processing unit 2210 and a transceiver unit 2220. The communication apparatus 2200 is used to implement the functions of the first device or the second device in the above FIG. 11, FIG. 18, or FIG. 19.

[0218] Optionally, the transceiver 2220 can also be referred to as an output unit, an interface unit, or a communication unit, etc. In a possible implementation, the transceiver 2220 includes at least one of a transmitting unit or a receiving unit. The transmitting unit and the receiving unit can be integrated together or be two independent units, etc.

[0219] In an implementation, when the communication apparatus 2200 is configured to implement the functions of the first device in FIG. 11, specifically: the transceiver 2220 is configured to receive a first message, the first message being used for paging the first device, and the first message including a first identifier; the transceiver 2220 is further configured to receive a second message, the second message being used for paging the first device, and the second message including a second identifier, or the second message including the second identifier and a first indication, the first indication being used for instructing the first device to maintain state information corresponding to the first identifier; and the processing unit 2210 is configured to maintain the state information corresponding to the first identifier when the second identifier is different from the first identifier or according to the first indication.

[0220] In an implementation, when the communication apparatus 2200 is configured to implement the functions of the first device in FIG. 18, specifically: the transceiver 2220 is configured to receive a first message, the first message being used for paging the first device, and the first message including a first identifier; and the processing unit 2210 is configured to reset state information corresponding to a second identifier maintained by the first device when the first identifier is different from the second identifier.

[0221] In an implementation, when the communication apparatus 2200 is configured to implement the functions of the first device in FIG. 19, specifically: the transceiver 2220 is configured to receive a first message, the first message including an identifier of a second device, and the first message being a reader-to-device (R2D) message; and the processing unit 2210 is configured to respond to or not respond to the first message according to the identifier of the second device and an identifier of a third device saved by the first device.

[0222] For specific implementations of the transceiver 2220 and the processing unit 2210, refer to the descriptions in the method embodiments in FIG. 11, FIG. 18, and FIG. 19.

[0223] It can be understood that the division of units in the embodiments of the present application is illustrative, and is merely a logical function division. In actual implementation, another division manner can be used. In addition, each functional unit in the embodiments of the present application can be integrated in one physical device (for example, in a processor), or each functional unit can be a separate physical device, or two or more units can be integrated in one unit for implementation. The integrated unit can be implemented in the form of hardware, or in the form of a software functional module, etc.

[0224] As shown in FIG. 23, the communication apparatus 2300 includes a processor 2310 and an interface circuit 2320. The processor 2310 and the interface circuit 2320 are coupled with each other. It can be understood that the interface circuit 2320 can be a transceiver or an input / output interface. Optionally, the communication apparatus 2300 can further include a memory 2330, used to store instructions executed by the processor 2310 or store input data required by the processor 2310 to execute instructions or store data generated after the processor 2310 executes instructions.

[0225] When the communication apparatus 2300 is used to implement the method shown in FIG. 11, FIG. 18 or FIG. 19, the processor 2310 is used to implement the functions of the processing unit 2210, and the interface circuit 2320 is used to implement the functions of the transceiver unit 2220.

[0226] When the communication apparatus is a chip applied to the first device, the chip implements the functions of the first device in the above method embodiments. The chip receives information sent by the second device to the first device through other modules (such as a radio frequency module or an antenna) in the first device; or the chip sends information to other modules (such as a radio frequency module or an antenna) in the first device, and the information is sent by the first device to the second device.

[0227] The embodiments of the present application further provide a communication apparatus, which includes a processor, and the processor is used to implement the functions of the first device or the second device in the above FIG. 11, FIG. 18 or FIG. 19. Optionally, the communication apparatus further includes a memory, and the processor and the memory are coupled, and the processor is used to execute computer programs or instructions stored in the memory to implement the functions of the first device or the second device in the above FIG. 11, FIG. 18 or FIG. 19. Optionally, the communication apparatus can be a chip or a chip system.

[0228] The embodiments of the present application further provide a communication apparatus, which includes a processor and an interface circuit, the interface circuit is used to receive signals from other devices outside the apparatus and transmit the signals to the processor or send signals from the processor to other devices outside the apparatus, and the processor is used to implement the functions of the first device or the second device in the above FIG. 11, FIG. 18 or FIG. 19 through logic circuits or execution of code instructions.

[0229] The embodiments of the present application further provide a computer readable storage medium, and the computer readable storage medium stores instructions, which can also be referred to as computer programs, computer program codes, etc. The instructions run on a computer, so that the computer executes the functions of the first device or the second device in the above FIG. 11, FIG. 18 or FIG. 19.

[0230] The embodiment of the present application further provides a computer program product, comprising a computer program or instructions, which, when running on a computer, realizes the functions of the first device or the second device in FIG. 11, FIG. 18 or FIG. 19.

[0231] It can be understood that the processor in the embodiment of the present application can be a central processing unit (CPU), and can also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. The general-purpose processor can be a microprocessor or any conventional processor.

[0232] The memory in the embodiment of the present application can be a random access memory (RAM), a flash memory, a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically EPROM (EEPROM), a register, a hard disk, a mobile hard disk, a CD-ROM or any other form of storage medium well known in the art.

[0233] The method steps in the embodiment of the present application can be implemented in hardware or software instructions executable by a processor. The software instructions can be composed of corresponding software modules, which can be stored in a random access memory, a flash memory, a read-only memory, a programmable ROM, an erasable programmable ROM, an electrically EPROM, a register, a hard disk, a mobile hard disk, a CD-ROM or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor, so that the processor can read information from and write information to the storage medium. The storage medium can also be an integral part of the processor. The processor and the storage medium can be located in an ASIC.

[0234] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer programs or instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are performed. The computer can be a general purpose computer, a special purpose computer, a computer network, a network device, a user equipment or other programmable apparatus. The computer programs or instructions can be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer programs or instructions can be transmitted from one website site, computer, server or data center to another website site, computer, server or data center through wired or wireless 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 and the like integrated with one or more available media. The available medium can be a magnetic medium, for example, a floppy disk, a hard disk, a magnetic tape; or an optical medium, for example, a digital video disc; or a semiconductor medium, for example, a solid state disk. The computer readable storage medium can be a volatile or non-volatile storage medium, or can include both volatile and non-volatile storage media.

[0235] In various embodiments of the present application, the terms and / or descriptions of different embodiments are consistent and can be referred to each other if there is no special description and logical conflict, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.

Claims

1. A communication method characterized by comprising: The method is applied to a first device, comprising: receiving a first message, the first message being used for paging the first device, the first message comprising a first identity; receiving a second message, the second message being used for paging the first device, the second message comprising a second identity, or the second message comprising the second identity and a first indication, the first indication being used for instructing the first device to maintain state information corresponding to the first identity; the second identity is different from the first identity, or according to the first indication, the state information corresponding to the first identity is maintained.

2. The method of claim 1, wherein, The state information corresponding to the first identity comprises: successful service transmission corresponding to the first identity; or unsuccessful service transmission corresponding to the first identity.

3. The method of claim 1 or 2, wherein, Further comprising: receiving a third message, the third message being used for paging the first device, the third message comprising the first identity; determining whether to respond to or not respond to the third message according to the maintained state information corresponding to the first identity.

4. The method of any one of claims 1 to 3, wherein, Further comprising: receiving a second indication, the second indication being used for instructing resetting of state information corresponding to one or more identities maintained by the first device.

5. The method of claim 4, wherein, Further comprising: receiving the one or more identities, the one or more identities being in an association relationship with the second indication.

6. The method of any one of claims 1 to 5, wherein, Further comprising: receiving a fourth message, the fourth message being used for at least one of the following: triggering at least one access opportunity, indicating a number of access opportunities, indicating resource configuration information, or indicating successful random access, the fourth message comprising the first identity; responding to or not responding to the fourth message according to the state information corresponding to the first identity.

7. The method of any one of claims 1 to 6, wherein, The first identity and the second identity are assigned by a first core network element, and the first identity and the second identity are used for identifying a service request initiated by the first core network element.

8. The method of any one of claims 1 to 6, wherein, The first identity and the second identity are identities of the device.

9. A communication method characterized by comprising: The method is applied to a first device, comprising: receiving a first message, the first message being used for paging the first device, the first message comprising a first identity; the first identity is different from a second identity maintained by the first device, and state information corresponding to the second identity is reset.

10. The method of claim 9, wherein, The state information corresponding to the second identity comprises: successful service transmission corresponding to the second identity; or unsuccessful service transmission corresponding to the second identity.

11. The method of claim 9 or 10, wherein, Further comprising: receiving a third indication, the third indication being used for instructing the first device to maintain state information corresponding to one or more identities, the one or more identities comprising the second identity.

12. The method of claim 11, wherein, Further comprising: receiving the one or more identities, the one or more identities being in an association relationship with the third indication.

13. The method according to any one of claims 9 to 12, characterized in that, The first identity and the second identity are assigned by a first core network element, and the first identity and the second identity are used for identifying a service request initiated by the first core network element.

14. The method of any one of claims 9 to 12, wherein, The first identity and the second identity are identities of the device.

15. A communications device, characterized by The unit for implementing the method of any one of claims 1 to 8, or the unit for implementing the method of any one of claims 9 to 14.

16. A communications device, characterized by A processor configured to cause the communication device to perform the method of any one of claims 1 to 8, or the method of any one of claims 9 to 14.

17. A computer readable storage medium characterized by: A computer readable storage medium having stored thereon instructions that, when executed, cause a communication device to perform the method of any one of claims 1 to 8, or the method of any one of claims 9 to 14.

18. A computer program product, characterised in that, A computer program product comprising instructions which, when executed, cause a communication device to perform the method of any one of claims 1 to 8, or the method of any one of claims 9 to 14.

19. A chip, characterized by A processor coupled with a memory for executing a computer program or instructions stored in the memory to cause the chip to implement the method of any one of claims 1 to 8, or the method of any one of claims 9 to 14.

Images