Communication method and apparatus

Abstract

The present application provides a communication method and apparatus. A relay device can communicate with a core network element through a first radio access network device, so that the relay device can obtain an identifier of a terminal device within the coverage area of ​​the relay device and transmit the identifier to a first access and mobility management function network element through the first radio access network device. In this way, communication between a terminal device and a network device can be achieved in scenarios where the indoor coverage of a 5G network is weak and where the uplink signal of an RFID terminal device is weak, and communication between a terminal device and a network device can also be achieved in large-coverage, large-scale, and wide-area scenarios.

Description

[Technical Field]

[0001] TECHNICAL FIELD Embodiments of the present application relate to the field of communications, and more particularly to communication methods and devices. [Background technology]

[0002] This application claims priority to Chinese Patent Application No. 202211128523.5, entitled "COMMUNICATION METHOD AND APPARATUS," filed with the State Intellectual Property Office of China on September 16, 2022, and incorporated herein by reference in its entirety.

[0003] Radio frequency identification (RFID) technology is a contactless automatic identification technology, and an RFID terminal device is a typical Internet of Things terminal device. An RFID system usually includes a reader / writer, an RFID identifier, and an application management system. When an RFID tag approaches a reader / writer, it receives the radio frequency signal transmitted by the reader / writer, generates an induced current, and can obtain energy. The RFID tag can use the collected energy to transmit information to the reader / writer and communicate with it. RFID technology is widely used in product manufacturing, logistics, sales, and other areas.

[0004] However, RFID technology can only be used in small-scale and small-range scenarios. In large-scale and large-coverage scenarios, such as some long-distance scenarios, continuing to use the aforementioned technology will not only increase costs but also reduce communication effectiveness. Therefore, considering large-scale, wide-area, and large-coverage scenarios, how passive terminal devices should communicate with network devices becomes a technical problem that needs to be solved. Summary of the Invention

[0005] The present application provides a communication method, in which a relay device can communicate with a core network element through a first radio access network device, and the relay device can obtain an identifier of a terminal device within the coverage area of ​​the relay device and transmit the identifier to a first access and mobility management function network element through the first radio access network device. In this way, communication between the terminal device and the network device can be achieved in scenarios where the indoor coverage of a 5G network is weak or the uplink signal of an RFID terminal device is weak, and communication between the terminal device and the network device can also be achieved in scenarios where the coverage is large, large-scale, and wide area.

[0006] According to a first aspect, a communication method is provided. The method may be performed by a relay device or a component (e.g., a chip or circuit) of the relay device. This is not limited thereto.

[0007] The method includes: a relay device receiving a first non-access stratum message from a first access and mobility management function network element via a first radio access network device, the first non-access stratum message being used to request obtaining an identifier of a terminal device, the terminal device including one or more terminal devices; the relay device transmitting radio frequency information to a terminal device within a coverage area of ​​the relay device based on the first non-access stratum message, the radio frequency information being used to provide an excitation signal for the terminal device; the relay device receiving a second non-access stratum message from the first terminal device, the second non-access stratum message carrying an identifier of the first terminal device, the first terminal device being a terminal device within the coverage area of ​​the relay device that successfully performs random access; and the relay device transmitting the second non-access stratum message to the first access and mobility management function network element via the first radio access network device.

[0008] It should be noted that the "terminal device" referred to in this application may be understood as, for example, an Internet of Things terminal device. Specifically, it may be understood as a "passive Internet of Things (passive IoT) device," which is also referred to as an "ambient Internet of Things (Ambient IoT) terminal device." For example, the Internet of Things terminal device may be a passive RFID, a semi-passive RFID, etc.

[0009] In a possible implementation, the method further includes: the relay device sending a first radio resource control message to a first radio access network device, the first radio resource control message carrying a registration request message and first indication information, the first indication information indicating that the relay device supports communication with the ambient internet of things terminal device, the registration request message being used to request registration with an access and mobility management function network element, the first access and mobility management function network element being selected by the first radio access network device for the relay device based on the first indication information and supporting communication with the ambient internet of things terminal device.

[0010] According to the aforementioned technical solution, in the present application, when a relay device registers with a core network, first indication information is transmitted, and the indication information indicates that the relay device supports communication with a terminal device (for example, the terminal device is an ambient Internet of Things terminal device). Therefore, the first radio access network device can select a first access and mobility management function network element for the relay device, and then the first radio access network device transmits a message sent by the relay device to the access and mobility management function network element to the first access and mobility management function network element. This can facilitate inventory and management performed by the first access and mobility management function network element in the terminal device.

[0011] In a possible implementation, the method further includes: the relay device receiving, via the first radio access network device, a third non-access stratum message from the first access and mobility management function network element, the third non-access stratum message carrying second indication information, the second indication information indicating to perform a target operation at the first terminal device; the relay device transmitting the third non-access stratum message to the first terminal device; the relay device receiving, from the first terminal device, a fourth non-access stratum message, the fourth non-access stratum message carrying information regarding an execution result corresponding to the target operation performed at the first terminal device; and the relay device transmitting the fourth non-access stratum message to the first access and mobility management function network element via the first radio access network device.

[0012] As used herein, a "target operation" may include at least one of the following: a read operation, a write operation, an access operation, a kill operation, a lock operation, a block write operation, a block erase operation, and the like.

[0013] According to the above technical solution, in this application, a first access and mobility management function network element may obtain an identifier of a terminal device, perform a target operation on the first terminal device, and indicate to perform inventory on the terminal device. In other words, according to the technical solution provided in this application, communication between the terminal device and the network device can be implemented in large-coverage, large-scale, and wide-area scenarios.

[0014] In a possible implementation, the method further includes: the relay device receiving, via the first radio access network device, third indication information from the first access and mobility management function network element, the third indication information indicating at least one of the following: indicating that the target operation has been completed at the first terminal device, indicating to inquire about an identifier of a next terminal device, or indicating to perform a next random access procedure for the terminal device; the relay device receiving, via the first radio access network device, a fifth non-access stratum message from the second terminal device, the fifth non-access stratum message carrying an identifier of the second terminal device; and the relay device transmitting, via the first radio access network device, the fifth non-access stratum message to the first access and mobility management function network element.

[0015] It should be noted that in this application, the second terminal device is different from the first terminal device, and the second terminal device is another terminal device located within the coverage area of ​​the relay device that successfully performs random access.

[0016] According to the aforementioned technical solution, in the present application, when it is determined that the inventory at the first terminal device is completed, the first access and mobility management function network element may instruct the relay device to obtain an identifier of the second terminal device, perform inventory at the second terminal device, and complete inventory at the terminal device within the coverage area of ​​the relay device.

[0017] In a possible implementation, the first non-access stratum message carries at least one of the following contents: a value interval of an identifier of a terminal device, an identifier list of terminal devices, an identifier of a group of terminal devices, an identifier of an application, an identifier of an enterprise user, or information indicating a query of any terminal device.

[0018] According to the aforementioned technical solution, in the present application, the application function network element may further send an inventory object to the first access and mobility management function network element to indicate that an inventory needs to be performed on the terminal device.

[0019] In a possible implementation, the method further includes: the relay device performs a handover from the first radio access network device to the second radio access network device; the relay device sends a second radio resource control message to the second radio access network device, the second radio resource control message carrying a registration request message and first indication information, the first indication information indicating that the relay device supports communication with the ambient internet of things terminal device, the registration request message being used to request registration with an access and mobility management function network element; the relay device receives a registration accept message from the second access and mobility management function network element, the second access and mobility management function network element being selected for the relay device by the second radio access network device based on the first indication information after the relay device is handed over from the first radio access network device to the second radio access network device and supporting communication with the ambient internet of things terminal device.

[0020] According to the above technical solution, the present application further considers that the location of the relay device moves during the inventory process. In this case, the relay device may switch between the radio access network device and the access and mobility management function network element, and the target access and mobility management function network element may obtain context information of the relay device from the source access and mobility management function network element, so that the core network element (e.g., the second access and mobility management function network element) can continue to perform inventory on the terminal device. In this way, communication between the terminal device and the network device can be implemented in a large-coverage scenario.

[0021] According to a second aspect, there is provided a communication method, which may be performed by a radio access network device or a component (e.g., a chip or circuit) of the radio access network device, without being limited thereto.

[0022] The method includes: a first radio access network device receives a first radio resource control message from a relay device, the first radio resource control message carrying a registration request message and first indication information, the first indication information indicating that the relay device supports communication with an ambient Internet of Things terminal device, and the registration request message is used to request registration with an access and mobility management function network element; the first radio access network device selects, for the relay device, a first access and mobility management function network element that supports communication with the ambient terminal device based on the first indication information; and the first radio access network device sends the registration request message to the first access and mobility management function network element.

[0023] In a possible implementation, a first radio access network device receives a first non-access stratum message from a first access and mobility management function network element, the first non-access stratum message being used to request obtaining an identifier of a terminal device, the terminal device including one or more terminal devices. The first radio access network device transmits the first non-access stratum message to a relay device. The first radio access network device receives a second non-access stratum message from the relay device, the second non-access stratum message carrying an identifier of the first terminal device, the first terminal device being a terminal device within the coverage area of ​​the relay device that successfully performs random access. The first radio access network device determines to transmit the second non-access stratum message to the first access and mobility management function network element.

[0024] According to the aforementioned technical solution, in the present application, first indication information is transmitted when a relay device registers with a core network, and the indication information indicates that the relay device supports communication with a terminal device. Therefore, the first radio access network device can select a first access and mobility management function network element for the relay device, and then the first radio access network device transmits a message sent by the relay device to the access and mobility management function network element to the first access and mobility management function network element. This facilitates inventory and management performed by the first access and mobility management function network element in the terminal device.

[0025] According to a third aspect, there is provided a communication method, which may be performed by a first access and mobility management function network element, or may be performed by a component (e.g., a chip or circuit) of the first access and mobility management function network element, without being limited thereto.

[0026] Corresponding to the technical solution on the network side, the same beneficial effects as on the relay device side and the first radio access network device side will not be described again.

[0027] The method includes: a first access and mobility management function network element receiving a seventh non-access stratum message from the first network element, the seventh non-access stratum message being used to request obtaining an identifier of a terminal device, the seventh non-access stratum message carrying an identifier of a relay device, the terminal device including one or more terminal devices; the first access and mobility management function network element sending a first non-access stratum message to the relay device based on the identifier of the relay device, the first non-access stratum message being used to request obtaining an identifier of the terminal device; the first access and mobility management function network element receiving a second non-access stratum message from the first terminal device via the relay device, the second non-access stratum message carrying an identifier of the first terminal device, the first terminal device being a terminal device located within a coverage area of ​​the relay device that successfully performs random access. The first access and mobility management function network element sends an eighth non-access stratum message to the first network element, where the eighth non-access stratum message carries an identifier of the first terminal device.

[0028] According to the above technical solution, in this application, a first access and mobility management function network element can send a first non-access stratum message to a relay device, so that the relay device obtains an identifier of a terminal device within the coverage area of ​​the relay device. In this way, communication between the terminal device and the network device is implemented in a large-coverage, wide-area, and large-scale scenario.

[0029] In a possible implementation, the first access and mobility management function network element receiving the second non-access stratum message from the first terminal device via the relay device includes: the first access and mobility management function network element receiving the second non-access stratum message from the first terminal device via the relay device and the first radio access network device, the first access and mobility management function network element being an access and mobility management function network element selected by the first radio access network device for the relay device and supporting communication with the ambient Internet of Things terminal device.

[0030] According to the aforementioned technical solution, in the present application, the first radio access network device may transmit a message transmitted to the access and mobility management function network element by the relay device to the first access and mobility management function network element, which facilitates an inventory performed by the first access and mobility management function network element in the terminal device.

[0031] In a possible implementation, the seventh non-access stratum message further carries second indication information, where the second indication information indicates to perform a target operation at the first terminal device, and the method further includes: the first access and mobility management function network element sends a third non-access stratum message to the relay device, where the third non-access stratum message carries the second indication information; the first access and mobility management function network element receives a fourth non-access stratum message from the relay device, where the fourth non-access stratum message carries information about an execution result corresponding to the target operation performed at the first terminal device.

[0032] In a possible implementation, the method further includes: the first access and mobility management function network element sending third indication information to the relay device, the third indication information indicating at least one of the following: indicating that the target operation has been completed at the first terminal device, indicating to inquire about an identifier of a next terminal device, or indicating to perform a next random access procedure for the terminal device; and the first access and mobility management function network element receiving a fifth non-access stratum message from the second terminal device via the relay device, the fifth non-access stratum message carrying an identifier of the second terminal device.

[0033] In a possible implementation, the method further includes: the first access and mobility management function network element receives fourth indication information from the relay device, the fourth indication information indicating that the target operation has been completed in the terminal device, and the eighth non-access stratum message further carries information about an execution result corresponding to the target operation performed in the terminal device.

[0034] In a possible implementation, the method further includes: the first access and mobility management function network element sending context information of the relay device to a second access and mobility management function network element, the context information including a seventh non-access stratum message, the second access and mobility management function network element being an access and mobility management function network element selected for the relay device by the second radio access network device after the relay device is handed over from the first radio access network device to the second radio access network device and supporting communication with the ambient internet of things terminal device.

[0035] According to a fourth aspect, there is provided a communication method, which may be performed by a relay device or a component (e.g., a chip or circuit) of the relay device, without being limited thereto.

[0036] The method includes: a relay device receiving a first non-access stratum message from a fourth access and mobility management function network element via a first radio access network device, the first non-access stratum message being used to request obtaining an identifier of a terminal device, the terminal device including one or more terminal devices; the relay device transmitting radio frequency information to a terminal device within a coverage area of ​​the relay device based on the first non-access stratum message, the radio frequency information being used to provide an excitation signal for the terminal device; the relay device receiving a second non-access stratum message from a first terminal device, the second non-access stratum message carrying an identifier of the first terminal device, the first terminal device being a terminal device within the coverage area of ​​the relay device that successfully performs random access; and the relay device transmitting the second non-access stratum message to a third access and mobility management function network element via the first radio access network device.

[0037] According to the above technical solution, in this application, a relay device can interact with different access and mobility management function network elements, so that the relay device can report the identifier of the terminal device to the access and mobility management function network element. In this way, communication between the terminal device and the network device is implemented in a large-coverage, large-scale, and wide-area scenario.

[0038] In a possible implementation, the method further includes: the relay device receiving, via the first radio access network device, a third non-access stratum message from a third access and mobility management function network element, the third non-access stratum message carrying second indication information, the second indication information indicating to perform a target operation at the first terminal device; the relay device transmitting the third non-access stratum message to the first terminal device; the relay device receiving, via the first radio access network device, a fourth non-access stratum message from the first terminal device, the fourth non-access stratum message carrying information regarding an execution result corresponding to the target operation performed at the first terminal device; and the relay device transmitting, via the first radio access network device, the fourth non-access stratum message to the third access and mobility management function network element.

[0039] In a possible implementation, the method further includes: the relay device receives third indication information from the fourth access and mobility management function network element via the first radio access network device, the third indication information indicating at least one of the following: indicating that the target operation has been completed in the first terminal device, indicating to query an identifier of the next terminal device, or indicating to perform a next random access procedure for the terminal device; the relay device receives a fifth non-access stratum message from the second terminal device, the fifth non-access stratum message carrying an identifier of the second terminal device; and the relay device transmits the fifth non-access stratum message to the third access and mobility management function network element via the first radio access network device.

[0040] According to the above technical solution, in this application, the relay device can send information about the execution result corresponding to the target operation executed in the terminal device to the network device, obtain the identifier of the next terminal device based on the indication of the network device, and start executing inventory on the next terminal device. In other words, in a large-coverage scenario, the network device can complete inventory on all terminal devices.

[0041] According to a fifth aspect, there is provided a communication method. The method may be performed by a fourth access and mobility management function network element, or may be performed by a component (e.g., a chip or a circuit) of the fourth access and mobility management function network element. This is not limited thereto. Alternatively, the method may be performed by a third access and mobility management function network element, or may be performed by a component (e.g., a chip or a circuit) of the third access and mobility management function network element. This is not limited thereto.

[0042] The method includes: a fourth access and mobility management function network element receives a seventh non-access stratum message from a second network element, the seventh non-access stratum message being used to request obtaining an identifier of a terminal device, the seventh non-access stratum message carrying an identifier of a relay device, the terminal device including one or more terminal devices; a fourth access and mobility management function network element sends a first non-access stratum message to the relay device based on the identifier of the relay device, the first non-access stratum message being used to request obtaining an identifier of the terminal device; a third access and mobility management function network element receives a second non-access stratum message from a first terminal device via the relay device, the second non-access stratum message carrying an identifier of the first terminal device, the first terminal device being a terminal device located within the coverage area of ​​the relay device that successfully performs random access; and a third access and mobility management function network element sending the second non-access stratum message to the second network element.

[0043] According to the above technical solution, in the present application, a relay device can communicate with a core network element through a radio access network element and an access and mobility management function network element, so that the relay device can obtain an identifier of a terminal device within the coverage area of ​​the relay device and send the identifier to a second network element through the access and mobility management function network element, and the second network element can perform inventory on the terminal device. In this way, communication between the terminal device and the network device can be implemented in a large-coverage, large-scale, and wide-area scenario.

[0044] In a possible implementation, the fourth access and mobility management function network element is an access and mobility management function network element that supports communication with a relay device.

[0045] In a possible implementation, if the seventh non-access stratum message carries an inventory identifier, the first non-access stratum message carries an inventory identifier and the second non-access stratum message carries an inventory identifier, and the inventory identifier is used by the second network element to determine that the second non-access stratum message is a response message corresponding to the seventh non-access stratum message.

[0046] According to the above technical solution, in this application, the second network element sends an inventory identifier to the fourth access and mobility management function network element. Then, if the second network element receives a second non-access stratum message from the third access and mobility management function network element and carries the inventory identifier, the second network element can determine that the message is a response message to the seventh non-access stratum message.

[0047] In a possible implementation, the seventh non-access stratum message further carries second indication information, the second indication information indicating to perform a target operation at the first terminal device, and the method further includes: a fourth access and mobility management function network element receives a third non-access stratum message from the second network element, the third non-access stratum message carrying the second indication information; a fourth access and mobility management function network element transmits the third non-access stratum message to the first terminal device via a relay device, the third non-access stratum message carrying the second indication information; a third access and mobility management function network element receives a fourth non-access stratum message from the first terminal device via the relay device, the fourth non-access stratum message carrying information regarding an execution result corresponding to the target operation performed at the first terminal device; and a third access and mobility management function network element transmits the fourth non-access stratum message to the second network element.

[0048] In a possible implementation, the method further includes: the fourth access and mobility management function network element sending third indication information to the relay device, the third indication information indicating at least one of the following: indicating that the target operation has been completed at the first terminal device, indicating to inquire about an identifier of a next terminal device, or indicating to perform a next random access procedure for the terminal device; and the fourth access and mobility management function network element receiving a fifth non-access stratum message from the second terminal device via the relay device, the fifth non-access stratum message carrying an identifier of the second terminal device.

[0049] In a possible implementation, the method further includes: a fourth access and mobility management function network element receiving fourth indication information from the relay device, the fourth indication information indicating that the target operation has been completed at the terminal device; and the fourth access and mobility management function network element sending a ninth non-access stratum message to the second network element, the ninth non-access stratum message including information about an execution result corresponding to the target operation performed at the terminal device.

[0050] In a possible implementation, the fourth access and mobility management function network element is connected to the first radio access network device, and the first radio access network device provides a service for the relay device, and the method further includes: the fourth access and mobility management function network element sends context information of the relay device to the second access and mobility management function network element, where the context information includes a seventh non-access stratum message, and the second access and mobility management function network element is a target access and mobility management function network element selected for the relay device by the second radio access network device after the relay device is handed over from the first radio access network device to the second radio access network device; the second access and mobility management function network element receives a sixth non-access stratum message from the relay device, where the sixth non-access stratum message carries an identifier and an inventory identifier of the third terminal device, and the inventory identifier is used by the second network element to determine that the second non-access stratum message is a response message corresponding to the seventh non-access stratum message.

[0051] In the present application, the third terminal device is different from the first terminal device and the second terminal device, and the third terminal device is another terminal device located within the coverage area of ​​the relay device that successfully performs random access.

[0052] According to a sixth aspect, there is provided a communication method, which may be performed by a tag manager network element or a component (e.g., a chip or circuit) of the tag manager network element, without being limited thereto.

[0053] The method includes: a second network element receiving a tenth non-access stratum message from an application function network element, the tenth non-access stratum message being used to request obtaining identifiers of terminal devices, the tenth non-access stratum message carrying an identifier of a relay device, the terminal devices including one or more target terminal devices; the second network element determining, based on the identifier of the relay device, that an access and mobility management function network element serving the relay device is a fourth access and mobility management function network element; the second network element sending a seventh non-access stratum message to the fourth access and mobility management function network element, the seventh non-access stratum message being used to request obtaining identifiers of terminal devices; and the second network element receiving a second non-access stratum message from a third access and mobility management function network element, the second non-access stratum message carrying an identifier of a first terminal device, the first terminal device being a terminal device located within the coverage area of ​​the relay device that successfully performs random access.

[0054] According to the above technical solution, in the present application, a relay device can communicate with a core network element through a radio access network element and an access and mobility management function network element, so that the relay device can obtain an identifier of a terminal device within the coverage area of ​​the relay device and send the identifier to a second network element through the access and mobility management function network element, and the second network element can perform inventory on the terminal device. In this way, communication between the terminal device and the network device can be implemented in large-coverage, large-scale, and wide-area scenarios.

[0055] In a possible implementation, when the seventh non-access stratum message carries an inventory identifier and the second non-access stratum message carries an inventory identifier, the method further includes: the second network element determines, based on the inventory identifier, that the second non-access stratum message is a response message corresponding to the seventh non-access stratum message.

[0056] In a possible implementation, the tenth non-access stratum message further carries inventory indication information, and the inventory indication information includes at least one of the following contents: a value interval of an identifier of a terminal device, an identifier list of terminal devices, an identifier of a group of terminal devices, or information indicating an inquiry about an identifier of any terminal device. The method further includes: if the second network element determines that the identifier of the first terminal device satisfies at least one of the indication information, the second network element determines that the second non-access stratum message is a response message corresponding to the seventh non-access stratum message.

[0057] According to the above technical solution, in the present application, the second network element may determine whether the second non-access stratum message from the third access and mobility management function network element is a response message to the seventh non-access stratum message based on the inventory identifier or inventory indication information (alternatively, it may be understood as an "inventory object"). In other words, according to the technical solution provided in the present application, the second network element may perform an inventory in the terminal device.

[0058] In a possible implementation, the tenth non-access stratum message further carries second indication information, the second indication information indicating to perform a target operation in the first terminal device, and the method further includes: the second network element sending a third non-access stratum message to a fourth access and mobility management function network element, the third non-access stratum message carrying the second indication information; the second network element receiving a fourth non-access stratum message from the third access and mobility management function network element, the fourth non-access stratum message carrying information about an execution result corresponding to the target operation of the first terminal device, and the fourth non-access stratum message being sent by the first terminal device to the third access and mobility management function network element via a relay device.

[0059] In a possible implementation, the method further includes: the second network element sending third indication information to the fourth access and mobility management function network element, the third indication information indicating at least one of the following: indicating that the target operation has been completed in the first terminal device, indicating to inquire about an identifier of a next terminal device, or indicating to perform a next random access procedure for the terminal device; the second network element receiving a fifth non-access stratum message from the third access and mobility management function network element, the fifth non-access stratum message carrying an identifier of the second terminal device, the fifth non-access stratum message being sent by the second terminal device to the third access and mobility management function network element via the relay device.

[0060] In a possible implementation, the method further includes: the second network element receives a ninth non-access stratum message from the fourth access and mobility management function network element, the ninth non-access stratum message including information about an execution result corresponding to the target operation performed in the terminal.

[0061] According to a seventh aspect, there is provided a communication device configured to perform a method according to any one of the first to sixth aspects. Specifically, the device may include a unit and / or module, such as a transceiver unit and / or a processing unit, configured to perform a method according to any one of the first to sixth aspects.

[0062] In some implementations, the apparatus is a communication device (e.g., a relay device, a first access and mobility management function network element, a fourth access and mobility management function network element, or a tag management function network element). When the apparatus is a communication device, the communication unit may be a transceiver or an input / output interface, and the processing unit may be at least one processor. Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0063] In another implementation, the apparatus is a chip, chip system, or circuit used in a communication device (e.g., a relay device, a first access and mobility management function network element, a fourth access and mobility management function network element, or a tag management function network element). When the apparatus is a chip, chip system, or circuit used in a communication device, the communication unit may be an input / output interface, interface circuit, output circuit, input circuit, pin, associated circuit, etc. on the chip, chip system, or circuit, and the processing unit may be at least one processor, processing circuit, logic circuit, etc.

[0064] According to an eighth aspect, there is provided a communications device. The device includes at least one processor configured to execute a computer program or instructions stored in a memory to perform the method of any one of the possible implementations of the first and sixth aspects. Optionally, the device further includes a memory configured to store the computer program or instructions. Optionally, the device further includes a communications interface, and the processor reads the computer program or instructions stored in the memory via the communications interface.

[0065] In one implementation, the apparatus is a relay device.

[0066] In another implementation, the apparatus is a chip, chip system, or circuit used in a relay device.

[0067] In the implementation, the device is a first access and mobility management function network element.

[0068] In another implementation, the device is a chip, chip system, or circuit used in the first access and mobility management function network element.

[0069] In the implementation, the device is a fourth access and mobility management function network element.

[0070] In another implementation, the device is a chip, chip system, or circuit used in a fourth access and mobility management function network element.

[0071] In an implementation, the device is a tag management function network element.

[0072] In another implementation, the device is a chip, chip system, or circuitry used in a tag management function network element.

[0073] According to a ninth aspect, the present application provides a processor including an input circuit, an output circuit, and a processing circuit configured to receive signals via the input circuit and send signals via the output circuit so that the processor can perform a method in any one of the possible implementations of the first to sixth aspects.

[0074] In a particular implementation, the processor may be one or more chips, the input circuits may be input pins, the output circuits may be output pins, and the processing circuits may be transistors, gate circuits, triggers, any type of logic circuit, etc. An input signal received by an input circuit may be, for example, but not limited to, received and input by a transceiver, a signal output by an output circuit may be, for example, but not limited to, output to a transmitter and transmitted by the transmitter, and the input circuit and the output circuit may be the same circuit used as an input circuit and an output circuit at different times. The specific implementation of the processor and various circuits is not limited to this embodiment of the present application.

[0075] Operations such as transmitting and acquiring / receiving related to a processor may be understood as operations such as output and receiving or input of the processor, or as operations such as transmitting and receiving performed by a radio frequency circuit and an antenna, unless otherwise specified or unless the operations contradict the actual function or internal logic of the operations in the relevant description. This is not a limitation in this application.

[0076] According to a tenth aspect, a processing device is provided, the processing device including a processor and a memory, the processor is configured to read instructions stored in the memory, receive signals via a transceiver, and transmit signals via a transmitter to perform the method in any one of the possible implementations of the first to sixth aspects.

[0077] Optionally, there are one or more processors and one or more memories.

[0078] Optionally, the memory may be integrated with the processor, or the memory and the processor may be located separately.

[0079] In a specific implementation, the memory may be a non-transitory memory, such as a read-only memory (ROM). The memory and the processor may be integrated on the same chip or may be located separately on different chips. The type of memory and the manner of location of the memory and the processor are not limited to this embodiment of the present application.

[0080] It should be understood that a related data exchange process, such as transmitting indication information, may be a process of outputting indication information from a processor, and receiving capability information may be a process of receiving input capability information by a processor. Specifically, data output by a processor may be output to a transmitter, and input data received by a processor may be from a transceiver. The transmitter and transceiver may be collectively referred to as a transceiver.

[0081] The processing device of the tenth aspect may be one or more chips. The processor in the processing device may be implemented using hardware or software. When the processor is implemented using hardware, the processor may be a logic circuit, an integrated circuit, or the like. When the processor is implemented using software, the processor may be a general-purpose processor and is implemented by reading software code stored in a memory. The memory may be integrated into the processor or may be located outside the processor and exist independently.

[0082] According to an eleventh aspect, there is provided a computer-readable storage medium storing program code for execution by a device, the program code being for performing the method in any one of the possible implementations of the first to sixth aspects.

[0083] According to a twelfth aspect, there is provided a computer program product comprising instructions which, when run on a computer, enable the computer to perform the method of any one of the possible implementations of the first to sixth aspects.

[0084] According to a thirteenth aspect, there is provided a communication system. The communication system includes a relay device, a first access and mobility management function network element, and a first radio access network device. The relay device is configured to perform the method according to any one of possible implementations of the first aspect. The first radio access network device is configured to perform the method according to any one of possible implementations of the second aspect. The first access and mobility management function network element is configured to perform the method according to any one of possible implementations of the third aspect.

[0085] According to a fourteenth aspect, there is provided a communication system. The communication system includes a third access and mobility management function network element, a fourth access and mobility management function network element, and a tag management function network element. The third access and mobility management function network element and the fourth access and mobility management function network element are configured to perform a method corresponding to the third access and mobility management function network element and the fourth access and mobility management function network element in any one of the possible implementations of the fifth aspect. The tag management function network element is configured to perform the method in any one of the possible implementations of the sixth aspect.

[0086] In a possible implementation, the system further includes a relay device, wherein the relay device is configured to perform the method in any one of the possible implementations of the fourth aspect. [Brief explanation of the drawings]

[0087] [Figure 1] FIG. 1 is a diagram of a system architecture applicable to the present application. [Figure 2] Figure 2 is a diagram of the RFID system architecture. [Figure 3] Figure 3 is a block diagram of proximity service technology in a 5G system. [Figure 4] FIG. 4 is a diagram of two communication system architectures according to the present application. [Figure 5] FIG. 5 is a simplified flowchart of a communication method 500 according to the present application. [Figure 6] FIG. 6 is a simplified flowchart of a communication method 600 according to the present application. [Figure 7] FIG. 7 is a simplified flowchart of a communication method 700 according to the present application. [Figure 8A] FIG. 8A is a simplified flowchart of a communication method 800 according to the present application. [Figure 8B] FIG. 8B is a simplified flowchart of a communication method 800 according to the present application. [Figure 9A] FIG. 9A is a schematic flow chart of a communication method 900 according to the present application. [Figure 9B] FIG. 9B is a simplified flowchart of a communication method 900 according to the present application. [Figure 10A] FIG. 10A is a schematic flow chart of a communication method 1000 according to the present application. [Figure 10B] FIG. 10B is a schematic flow chart of a communication method 1000 according to the present application. [Figure 11] FIG. 11 is a block diagram of a communication device 100 according to the present application. [Figure 12] FIG. 12 is a block diagram of a communication device 200 according to the present application. DETAILED DESCRIPTION OF THE INVENTION

[0088] The following describes the technical solutions in the embodiments of the present application with reference to the accompanying drawings.

[0089] Wireless communication systems referred to in this application include, but are not limited to, global system for mobile communications (GSM), long term evolution (LTE) frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, LTE systems, long term evolution advanced (LTE-Advanced, LTE-A) systems, next generation communication systems (e.g., 6G communication systems), integrated systems of multiple types of access systems, or evolved systems.

[0090] The technical solutions provided in this application may further be applied to machine-type communication (MTC), long-term evolution-machine (LTE-M), device-to-device (D2D) networks, machine-to-machine (M2M) networks, Internet of Things (IoT) networks, or other networks. IoT networks may include, for example, the Internet of Vehicles. Communication methods in the Internet of Vehicle Systems are collectively referred to as vehicle-to-X (V2X, where X can represent anything). For example, V2X may include vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-pedestrian (V2P) communication, vehicle-to-network (V2N) communication, etc.

[0091] First, a network architecture applicable to the present application will be briefly described. In the example, Figure 1 is a diagram of a network architecture applicable to the present application.

[0092] As shown in Figure 1, the 5th generation system (5GS) is used as an example of a network architecture. The 5G system architecture is divided into two parts: an access network and a core network. The network architecture may include, but is not limited to, a unified data management (UDM), a network exposure function (NEF), a network repository function (NRF), a policy control function (PCF), an application function (AF), an access and mobility management function (AMF), a session management function (SMF), a user equipment (UE), a radio access network device, a user plane function (UPF), and a data network (DN). The DN may be the Internet. The UDM, NEF, NRF, PCF, AF, AMF, SMF, and UPF are network elements in the core network. Since a 5G system is used as an example in Figure 1, the core network may be referred to as a 5G core network (5GC or 5GCN).

[0093] The network elements shown in FIG. 1 are briefly described below.

[0094] 1. User equipment (UE) (101) may be referred to as a terminal device, access terminal, subscriber unit, subscriber station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user equipment.

[0095] The terminal device may be a device that provides voice / data to a user, for example, a handheld device or an in-vehicle device with wireless connectivity. Currently, examples of terminals include the following: a mobile phone, a tablet computer, a laptop computer, a palmtop computer, a mobile internet device (MID), a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, a cellular telephone, a cordless telephone, a session initiation protocol (SIP) telephone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication capabilities, a computing device, another processing device connected to a wireless modem, a terminal device in a 5G network, and a terminal device in a future evolved public land mobile network. The present invention is not limited to this embodiment.

[0096] For example, but not by way of limitation, in embodiments of the present application, the terminal device may alternatively be a wearable device. A wearable device, also referred to as a wearable intelligent device, is a general term for wearable devices such as glasses, gloves, watches, clothes, and shoes developed by applying wearable technology to the intelligent design of everyday clothing. A wearable device is a portable device that is worn directly on the body or integrated into a user's clothing or accessories. A wearable device is not only a hardware device, but also performs powerful functions through software support, data exchange, and cloud interaction. In a broad sense, a wearable intelligent device includes a full-function large device, such as a smart watch or smart glasses, that can perform all or part of its functions independently of a smartphone, and also includes a device that is personalized for only one type of application function and must operate in conjunction with another device, such as a smartphone, such as various smart bands and smart jewelry for monitoring physical signs.

[0097] In addition, in the embodiments of the present application, the terminal device may alternatively be a terminal device in an IoT system. IoT is an important part of the future development of information technology. The main technical feature of IoT is to use communication technology to connect objects to a network and implement an intelligent network for the interconnection between humans and machines and between things.

[0098] It should be noted that the terminal device and the access network device may communicate with each other using an air interface technology (e.g., NR technology or LTE technology). The terminal devices may also communicate with each other using an air interface technology (e.g., NR technology or LTE technology).

[0099] In an embodiment of the present application, an apparatus configured to perform the functions of a terminal device may be the terminal device itself, or may be an apparatus that can support the terminal device in performing the functions, such as a chip system or a chip. The apparatus may be installed in the terminal device. In an embodiment of the present application, a chip system may include a chip, or may include a chip and another individual device.

[0100] 2. A (radio) access network ((R)AN) device 102 may provide access to a communication network for authorized users within a specific area, and may specifically include a wireless network device in a 3rd generation partnership project (3GPP) network or an access point in a non-3GPP network. For ease of explanation, the following will use an AN device as a representative.

[0101] RAN devices may use different radio access technologies. Currently, there are two types of radio access technologies: 3GPP access technologies (e.g., radio access technologies used in third-generation (3G), fourth-generation (4G), or 5G systems) and non-3GPP access technologies. 3GPP access technologies are access technologies that comply with 3GPP standard specifications. For example, access network devices in 5G systems are referred to as next-generation node base stations (gNBs) or RAN devices. Non-3GPP access technologies may include air interface technologies represented by access points (APs) in wireless fidelity (Wi-Fi), world wide interoperability for microwave access (WiMAX), code division multiple access (CDMA), etc. AN devices may use non-3GPP technologies to enable interconnection and interworking between terminal devices and 3GPP core networks.

[0102] The RAN device is responsible for air interface side functions such as radio resource management, quality of service (QoS) management, data compression and encryption, etc. The AN device provides access services for terminal devices to complete the transfer of control signals and user data between the terminal devices and the core network.

[0103] For example, a RAN device may include, but is not limited to, a macro base station, a micro base station (also referred to as a small cell), a radio network controller (RNC), a NodeB (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (e.g., a Home Evolved NodeB, or Home NodeB (HNB)), a baseband unit (BBU), an AP in a Wi-Fi system, a wireless relay node, a wireless backhaul node, a transmission point (TP), or a transmission and reception point (TRP), or may be a gNB or transmission point (TRP or TP) in a 5G (e.g., NR) system, or one antenna panel or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or may be a network node forming a gNB or transmission point, such as a distributed unit (DU) or base station in a next-generation 6G communication system. The particular technology used by the AN device and the particular device configuration are not limited to the embodiments of this application.

[0104] 3. A user plane function (UPF) network element (103) may be for packet routing and forwarding, quality of service (QoS) handling of user plane data, etc. User data may be accessed to a data network (DN) through the network element. In an embodiment of the present application, the user plane function network element may be configured to perform the functions of a user plane network element.

[0105] 4. A digital network (DN) (104) is a network used to provide data transmission, such as an operator service network, the Internet, or a third-party service network.

[0106] 5. The access and mobility management function (AMF) network element (105) is mainly for mobility management, access management, etc., and may be configured to perform functions other than session management in the mobility management entity (MME) function, such as lawful interception or access permission (or authentication). In an embodiment of the present application, the access and mobility management function network element may be configured to perform the functions of the access and mobility management function network element.

[0107] 6. The session management function (SMF) network element (106) is mainly for session management, IP address allocation and management of terminal devices, selection and management of user plane functions, termination of interfaces to policy control or charging functions, downlink data notification, etc. In an embodiment of the present application, the session management function network element may be configured to implement the functions of a session management network element.

[0108] 7. The policy control function (PCF) network element (107) is a unified policy framework for guiding network behavior and provides policy rule information to control plane function network elements (e.g., AMF or SMF network elements).

[0109] 8. An application function (AF) network element (108) is configured to perform application-influenced data routing, access network exposed functions network elements, interact with a policy framework for policy control, etc. In this application, an AF may alternatively be understood as an application server.

[0110] 9. Unified Data Management (UDM) network element (109) is for unified data management, 5G user data management, user identity processing, access authentication, registration, mobility management, etc.

[0111] 10. Network Exposure Function (NEF) network element. The NEF is located at the boundary between the 5GC network element and the third-party function network element AF and is for collecting, analyzing, reconfiguring, and publishing network capabilities.

[0112] In the network architecture shown in FIG. 1, network elements may communicate with each other via the interfaces shown in the figure. As shown in the figure, the N1 interface is a reference point between a terminal device and an AMF. The N2 interface is a reference point between the RAN and the AMF and is used to transmit non-access stratum (NAS) messages, etc. The N3 interface is a reference point between the RAN and the UPF and is used to transmit user plane data, etc. The N4 interface is a reference point between the SMF and the UPF and is used to transmit information, such as tunnel identification information, data buffer indication information, and downlink data notification messages, for the N3 connection. The N5 interface is a reference point between the PCF and the AF. The N6 interface is a reference point between the UPF and the DN and is used to transmit user plane data, etc. The N7 interface is a reference point between the SMF and the PCF. The N8 interface is a reference point between the AMF and the UDM. The N11 interface is a reference point between the AMFs. The relationships between the other interfaces and network elements are shown in FIG. 1. For brevity, details will not be described herein.

[0113] It should be understood that the network architecture shown in Figure 1 is merely an example for explanation purposes, and that the network architecture applicable to the embodiments of the present application is not limited thereto. Any network architecture capable of implementing the functions of the network elements described above is applicable to the embodiments of the present application.

[0114] It should be further understood that functions or network elements such as the AMF, NEF, and AF shown in Figure 1 may be understood as network elements configured to perform different functions and may be combined, for example, into a network slice, as needed. These network elements may be independent devices, may be integrated into the same device to perform different functions, may be network elements within a hardware device, may be software functions running on dedicated hardware, or may be virtualized functions instantiated on a platform (e.g., a cloud platform). The specific form of the network elements is not limited in this application.

[0115] It should be further understood that the above names are simply defined to facilitate distinguishing between different functions and do not constitute any limitation to the present application. The present application does not exclude the possibility of using other names in 6G networks and other future networks. For example, in a 6G network, some or all of the above network elements may continue to use 5G terminology or may use other names.

[0116] In order to facilitate understanding of the technical solutions in this application, the following first briefly describes some technical terms in this application.

[0117] 1. Radio frequency identification (RFID) is a contactless automatic identification technology. The basic principle of radio frequency identification is to use the transmission characteristics of radio frequency signals and spatial coupling (e.g., inductance or electromagnetic coupling) or radar reflection to perform automatic identification of identified objects. Typically, the identification process can be as follows: After entering a reader / writer (which can also be understood as a reader), the tag receives the radio frequency signal transmitted by the reader / writer. The tag (e.g., a passive tag) can transmit the product information stored in the chip by using the energy obtained based on the induced current, or the tag (e.g., an active tag) can actively transmit a signal at a specific frequency. After reading and decoding the information, the reader / writer transmits the information to a central information system for related data processing.

[0118] 2. A passive Internet of Things terminal device is essentially a passive terminal device. For example, this type of terminal device may not have a power cable or a built-in battery, but obtains energy from the environment. For example, a passive Internet of Things terminal device may be an Internet of Things terminal device based on wireless electromagnetic energy acquisition technology. A passive Internet of Things terminal device obtains and collects energy by collecting radio waves transmitted from the network side, and completes data collection, transmission, and distributed computing. An RFID terminal device is a typical passive Internet of Things terminal device. A passive Internet of Things terminal device is also called an "Ambient Internet of Things (Ambient IoT) terminal device."

[0119] 3. Proximity service (ProSe).

[0120] Proximity services are provided when terminal devices are adjacent to each other based on short-range communication technologies in communication systems defined by the 3rd Generation Partner Project (3GPP). They enable two or more terminal devices with ProSe functionality to communicate directly with each other without a relay or base station. The aforementioned "short distance" refers not only to physical distance but also to proximity based on channel quality, signal-to-noise ratio, or throughput. Proximity services mainly include the following three functions: direct discovery, direct communication, and UE-to-network relay. The direct discovery function allows a terminal device to discover nearby terminal devices that can be directly connected, and the direct communication function allows a terminal device to perform data transmission with the terminal device. In UE-to-network relay, a relay UE provides functionality to support a connection between a remote UE and a network. The UE-to-network relay in this application may include Layer 2 (L2) UE-to-network relay.

[0121] Figure 2 shows the RFID system architecture. As shown in Figure 2, a complete RFID system generally includes three parts: a reader / writer, an electronic tag, and a data management system (e.g., an application server). The working principle of an RFID system is as follows: the reader / writer transmits radio wave energy of a specific frequency to drive a circuit and transmit internal data. In this case, the reader / writer can receive and interpret the data in turn and send it to an application program for corresponding processing. In other words, when an RFID tag approaches the reader / writer, it receives the radio frequency signal transmitted by the reader / writer and generates an induced current to obtain energy. The tag can then use the collected energy to transmit information and communicate with the reader / writer.

[0122] An RFID reader / writer can perform wireless communication with an RFID electronic tag via an antenna and perform read or write operations on tag identification codes and memory data. A typical reader includes a radio frequency module (e.g., a transmitter or receiver), a control unit, and a reader antenna. An RFID reader / writer can alternatively be understood as a device that communicates with tags and can be in the form of a terminal, a base station, or a device with read / write capabilities.

[0123] An electronic tag includes a tag antenna and a separate tag chip. Generally, electronic tags can be classified into active, passive, and semi-passive tags based on their different power supply modes. Active tags are equipped with batteries, passive radio frequency tags are not equipped with batteries, and semi-passive tags partially rely on batteries to operate. Electronic tags can be classified into low-frequency, high-frequency, very high-frequency, and microwave tags based on different frequencies. Of course, classification can alternatively be performed based on different encapsulation forms, and details will not be described herein. Passive tags can also be referred to as passive Internet of Things (IOT) devices. Therefore, RFID tags can alternatively be considered terminal devices.

[0124] "Inventory" in this application can be understood as follows: After receiving mask information and flag bits specified by the reader / writer, if the information in the tag storage area matches the received mask information and the flag bits stored by the tag match those indicated by the reader / writer, the electronic tag can enter the inventory procedure. That is, the electronic tag initiates random access to the reader / writer and completes the corresponding command or operation of the reader / writer. For example, in current technology, the reader / writer can usually perform operations such as read, write, access, kill, lock, block write, or block erase on the tag based on an indication from an application server.

[0125] In a 5G system, a terminal device outside a network coverage area can access a data network through a relay of a terminal device within the network coverage area, solving the problem of a terminal device outside the network coverage area being unable to communicate with a network device. This technology is called "UE-to-network relay UE (U2NrelayUE)" and is a 5G system proximity service (ProSe) technology. The UE-to-network relay technology includes a Layer 2 (L2)-based relay technology. Figure 3 is an architecture diagram. Figure 3 includes a remote terminal device, a relay terminal device, a radio access network, a core network of the remote terminal device, and a core network of the relay device. The relay device can register with the AMF of the relay device via the RAN based on a common terminal device registration procedure and establish a protocol data unit (PDU) session to access the data network. The remote terminal device can establish a PC5 connection to the relay device. The remote terminal device may forward radio resource control (RRC) messages to the RAN via the relay device. The RAN selects an AMF for the remote terminal device and then sends RRC messages providing service for the remote terminal device to the AMF. In this application, a "U2N relay UE" is referred to as a "relay UE" or "relay device" for short.

[0126] The solution shown in Figure 2 is applicable to small-scale, small-range, and short-distance scenarios. In large-scale, wide-area, and long-distance scenarios, if the solution in Figure 2 is used as is, a large number of card readers will be required, resulting in increased costs and poor communication quality. Therefore, when considering large-scale, wide-area, and large-coverage scenarios, how passive terminal devices communicate with network devices becomes a technical problem that needs to be solved.

[0127] This application proposes that 5G networks be introduced to perform operations such as reading and writing on RFID terminal devices, so that tag costs can be reduced and communication quality in 5G network coverage areas can be ensured. However, the indoor coverage of 5G networks is weak, and the uplink signal of RFID terminal devices is weak, so indoor RFID cannot be read, i.e., cannot be operated. Therefore, in indoor coverage scenarios, how passive terminal devices should communicate with network devices becomes a technical problem that needs to be solved.

[0128] In consideration of this, the present application provides a communication method, in which a relay device can communicate with a core network element through a first radio access network device, so that the relay device can obtain an identifier of a terminal device within the coverage area of ​​the relay device and transmit the identifier to a first access and mobility management function network element through the first radio access network device. In this way, communication between the terminal device and the network device can be achieved in scenarios where the indoor coverage of a 5G network is weak or where the uplink signal of an RFID terminal device is weak, and communication between the terminal device and the network device can also be achieved in scenarios where the coverage is large, large-scale, and wide-area.

[0129] It should be noted that the "terminal device" referred to in this application may be understood as, for example, an Internet of Things terminal device. Specifically, it may be understood as an ambient Internet of Things (Ambient IoT) terminal device or a passive IoT device. For example, the Internet of Things terminal device may be a passive terminal device, a semi-passive terminal device, a passive Internet of Things terminal device, a tag, etc.

[0130] Furthermore, this application provides two communication system architectures. (a) in FIG. 4 shows one of the architectures. As shown in (a) of FIG. 4, the communication system may include a terminal device, a relay device, a RAN, an AMF#1, and an AF. Optionally, a NEF network element may be further included. The relay device may register with the AMF#1 via the RAN. In the architecture, the AMF#1 supports tag management functions. For example, the AMF#1 supports tag management operations (e.g., inventory). In a possible implementation, the AMF#1 may communicate with the AF via the NEF. In another possible implementation, the AMF#1 may receive an inventory command directly from the AF and perform a target operation on the tag via the relay device. The terminal device may send a non-access stratum (NAS) message to the AMF#1 via the relay device to report information about the execution result corresponding to the target operation. In this architecture, the AMF providing services for the relay device and the terminal device may be understood to be the same AMF, for example, AMF#1.

[0131] (b) in FIG. 4 illustrates another architecture. In the architecture, the AMFs providing services for the relay device and the terminal device may be different AMFs. For example, the AMF providing services for the relay device is denoted as AMF#4, and the AMF providing services for the terminal device is denoted as "AMF#3." The architecture further includes a tag management function (TMF) network element, which may support tag management operations. In a possible implementation, the TMF may communicate directly with the AF. In another possible implementation, the TMF may communicate with the AF via the NEF. The TMF may receive an inventory command from the AF and send the inventory command to the relay device via AMF#4 to perform a target operation on the tag. The terminal device may send a NAS message carrying information about the execution result corresponding to the target operation to AMF#3 via the relay device, and the AMF#3 may send the NAS message to the TMF.

[0132] 5 is a schematic flowchart of a communication method 500 according to the present application. The method is applicable to the architecture of FIG. 4(a). The method includes the following steps:

[0133] Step 501: A relay device receives a first non-access stratum message from a first access and mobility management function network element via a first radio access network device, the first non-access stratum message is used to request to obtain identifiers of terminal devices, and the terminal devices include one or more terminal devices.

[0134] It should be noted that a "relay device" in this application is a device that supports communication with an Internet of Things device. For example, a "relay device" is a device that supports communication with an ambient Internet of Things terminal device. For example, a "relay device" is a terminal device with relay functionality. For example, the antenna of the "relay device" may be installed outdoors and configured to communicate with a network device. The physical equipment of the "relay device" may be installed indoors and configured to communicate with a terminal device. In other words, when a "terminal device" in this application performs uplink transmission, the strength of the transmitted signal is weak and insufficient to transmit the signal to a network device. Therefore, a "relay device" is needed to perform "relaying." In this application, a "relay device" has this functionality and can be configured to connect a terminal device to a network device. In this application, the specific implementation and form of the "relay device" are not limited, and any device that has the function of connecting a terminal device to a network device can be understood as a "relay device" referred to in this application.

[0135] For example, a relay device may be a "UE-to-network relay UE (U2N relay UEE)" in 5G ProSe, and has a function of providing a connection ("connection" in this application may alternatively be understood as "communication") between a terminal device and a network device of 5G ProSe. In this application, a "U2N relay UE" is abbreviated to a "relay UE," "relay terminal device," or "relay device." A relay terminal device in this application may include an L2 relay terminal device.

[0136] Optionally, before step 501, the method further includes: the relay device sends a first radio resource control message to the first radio access network device, where the first radio resource control message carries the registration request message and the first indication information.

[0137] In the present application, the registration request message is used to request registration with an access and mobility management function network element, and the first indication information indicates that the relay device supports communication with an ambient Internet of Things terminal device.

[0138] In this embodiment, after receiving the radio resource control message, the first radio access network device may select a first access and mobility management function network element for the relay device that supports communication with the terminal device (e.g., the ambient terminal device) based on the first indication information. The relay device may register with the first access and mobility management function network element. For example, the relay device may register with the core network using a general UE registration procedure.

[0139] It should be understood that in this embodiment, after the first radio access network device selects a first access and mobility management function network element for the relay device, and then, after receiving any message from the relay device, the first radio access network device sends the message from the relay device to the first access and mobility management function network element.

[0140] Step 502: The relay device sends, based on the first non-access stratum message, a query request message to a terminal device within the coverage area of ​​the relay device.

[0141] Specifically, for example, a relay device may transmit radio frequency information to terminal devices within its coverage area. The radio frequency information may provide an excitation signal to the terminal devices within the coverage area of ​​the relay device. After receiving the excitation signal, the terminal devices within the coverage area may transmit a signal to the relay device. In addition, the relay device may perform a selection operation on the terminal devices within its coverage area, and select one or more target terminal devices through the selection operation. Information about the target terminal devices of the selection operation may be determined based on the inventory object received in the inventory request. Furthermore, the relay device may send an inquiry request message to one or more selected terminal devices to request to obtain identifiers of the one or more terminal devices.

[0142] Step 503: The relay device receives a second non-access stratum message from a first terminal device, the second non-access stratum message carrying an identifier of the first terminal device, the first terminal device being a terminal device within the coverage area of ​​the relay device that successfully performs random access.

[0143] Specifically, for example, one or more selected target terminal devices initiate a random access process, and one of the terminal devices that successfully performs the random access is referred to as a "first terminal device." A specific random access process may include the following: a relay device includes a first random number in an inquiry message, and one or more selected terminal devices locally set a second random number based on the first random number. If the second random number set by one terminal device is 0, the terminal device sends a third random number to the access network device. If the access network device can correctly receive the third random number, the access network device sends the third random number to the terminal device. When the terminal device receives the third random number, the terminal device determines that the random access is successful.

[0144] Step 504: The relay device sends a second non-access stratum message to the first access and mobility management function network element through the first radio access network device.

[0145] As described above, after receiving the second non-access stratum message from the relay device, the first radio access network device decides to send the second non-access stratum message to the first access and mobility management function network element. This is because, in the present application, the first indication information is transmitted during the previous registration of the relay device, and the first radio access network device selects the first access and mobility management function network element for the relay device. Therefore, the first radio access network device then sends the received message sent by the relay device to the access and mobility management function network element to the first access and mobility management function network element.

[0146] In the prior art, each time the first radio access network device receives a message sent by the relay device to the access and mobility management function network element, the first radio access network device randomly selects an access and mobility management function network element for the relay device. Therefore, according to the technical solution of the prior art, it is inconvenient for the access and mobility management function network element to perform inventory on the terminal device. Based on the architecture provided in the present application, in a scenario where the indoor coverage of the 5G network is weak and the uplink signal of the RFID terminal device is weak, the first mobility management function network element can perform inventory on the terminal device.

[0147] Consider a scenario in which the relay device moves. In this case, the relay device may be handed over from a first radio access network device to a second radio access network device. In this case, the relay device may send a second radio resource control message to the second radio access device, which message carries a registration request message and first indication information. Based on the first indication information, the second radio access network device selects a second mobility management function network element for the relay device that supports communication with a terminal device (e.g., the terminal device is an ambient Internet of Things terminal device). The relay device may register with the second access and mobility management function network element.

[0148] According to the above technical solution, in this application, a relay device can communicate with a core network element through a first radio access network device, so that the relay device can obtain an identifier of a terminal device within the coverage area of ​​the relay device and send the identifier to a first access and mobility management function network element through the first radio access network device. In this way, communication between the terminal device and the network device can be implemented in scenarios where the indoor coverage of the 5G network is weak and the uplink signal of the RFID terminal device is weak, and communication between the terminal device and the network device can also be implemented in scenarios with large coverage, large scale, and wide area.

[0149] In addition, first indication information is transmitted when the relay device registers with the core network, and the indication information indicates that the relay device supports communication with the terminal device. Therefore, the first radio access network device may select a first access and mobility management function network element for the relay device, and then the first radio access network device transmits a message sent by the relay device to the access and mobility management function network element to the first access and mobility management function network element. This can facilitate inventory and management performed on the terminal device by the first access and mobility management function network element.

[0150] 6 is a schematic flowchart of a communication method 600 according to the present application. The method is applicable to the architecture of FIG. 4(b). The method includes the following steps:

[0151] Step 601: A second network element receives a tenth non-access stratum message from an application function network element, the tenth non-access stratum message is used to request to obtain an identifier of a terminal device, the tenth non-access stratum message carries an identifier of a relay device, and the terminal device includes one or more target terminal devices.

[0152] In this application, the second network element supports management or inventory of terminal devices. For example, the second network element may be referred to as a "tag management network element." It should be noted that the specific name of the second network element is not a limitation in this application.

[0153] Step 602: The second network element determines, based on the identifier of the relay device, that the access and mobility management function network element serving the relay device is the fourth access and mobility management function network element.

[0154] It should be understood that when registering with the core network, the relay device may report an identifier of the relay device to the core network element, and the core network element may select a fourth access and mobility management function network element for the terminal device based on the identifier of the relay device to serve the terminal device.

[0155] Step 603: The second network element sends a seventh non-access stratum message to the fourth access and mobility management function network element, where the seventh non-access stratum message is used to request to obtain an identifier of the terminal device.

[0156] In a possible implementation, the seventh non-access stratum message carries an inventory identifier, which may be understood as a specific identifier assigned to the current inventory service by the application function network element. Upon receiving the message from a different access and mobility management function network element, the second network element may determine that the message is associated with the current inventory service based on the inventory identifier.

[0157] In another possible implementation, the seventh non-access stratum message further carries inventory indication information, which includes at least one of the following contents: a value interval of an identifier of a terminal device, an identifier list of a terminal device, an identifier of a group of terminal devices, or information indicating a query regarding an identifier of any terminal device. Then, upon receiving a message from a network element of a different access and mobility management function, the second network element may determine whether the identifier of the terminal device carried in the message satisfies at least one of the aforementioned indication information, and thereby determine whether the message is associated with a current inventory service.

[0158] Step 604: The second network element receives a second non-access stratum message from the third access and mobility management function network element, the second non-access stratum message carrying an identifier of a first terminal device, the first terminal device being a terminal device located within the coverage area of ​​the relay device that successfully performs random access.

[0159] As described above, in architecture (b), the access mobility management function network element serving the relay device may be different from the access and mobility management function network element serving the terminal device. In this embodiment, upon receiving the message sent by the relay device to the access and mobility management function network element, the radio access network device may randomly select an access and mobility management function network element. Therefore, the fourth access and mobility management function network element may be different from the third access and mobility management function network element.

[0160] In this embodiment, in a possible implementation, the second network element sends an inventory identifier to the fourth access and mobility management function network element. If the second non-access stratum message received by the second network element from the third access and mobility management function network element then carries the inventory identifier, the second network element may determine that the message is a response message for the seventh non-access stratum message. In another possible implementation, the application function network element sends inventory indication information to the second network element. If the identifier carried in the second non-access stratum message received by the second network element from the third access and mobility management function network element of the terminal device satisfies at least one of the inventory indication information, the second network element may determine that the message is a response message for the seventh non-access stratum message. In other words, according to the technical solution provided herein, the second network element may perform management and inventory of the terminal device.

[0161] According to the above technical solution, in the present application, a relay device can communicate with a core network element through a radio access network device and an access and mobility management function network element, so that the relay device can obtain an identifier of a terminal device within the coverage area of ​​the relay device and send the identifier to a second network element through the access and mobility management function network element, and the second network element can determine a response message for the inventory command based on the inventory identifier or the inventory indication information, and perform inventory in the terminal device. In this way, communication between the terminal device and the network device can be implemented in large-coverage, large-scale, and wide-area scenarios.

[0162] In this application, in the following specific embodiments, an example in which the terminal device is a tag is used to describe the technical solution of the application.

[0163] Figure 7 is a schematic flowchart of another communication method 700 according to the present application. In the method 700, it is assumed that the AMF providing services for the relay device and the AMF providing services for the tag are the same, and both are AMF#1. That is, the method 700 is applicable to the architecture of Figure 4(a). The steps shown in Figure 7 will be described below. It should be noted that steps represented by dashed lines in Figure 7 are optional and will not be described in detail below. The method includes the following steps:

[0164] Step 701: The relay device registers with the core network.

[0165] For example, the relay device may register with the core network based on the general terminal device registration procedure. For details, please refer to the 3GPP technical specification (TS.23.502 4.2.2.2). Details will not be described.

[0166] Optionally, in the registration process, the relay device sends a radio resource control (RRC) message to the RAN, where the RRC message carries a registration request message #1 and indication information #1, where the indication information #1 indicates that the relay device supports communication with tags (an example of an ambient terminal device). In a possible implementation, the RAN may select an AMF for the relay device that supports communication with tags, where the AMF is denoted as AMF#1. In another implementation, if the AMF selected by the RAN for the relay device does not support communication with tags, the AMF may initiate a forwarding procedure. Specifically, the registration request message of the relay device is forwarded to an AMF that supports communication with tags, where the AMF is denoted as AMF#1. In yet another implementation, the RAN may alternatively select an AMF for the relay device that supports communication with tags by using configuration information, where the AMF is denoted as AMF#1.

[0167] Optionally, the registration request message #1 may further carry an identifier of the relay device, for example, a subscription concealed identifier (SUCI) of the relay device, a 5th generation globally unique temporary UE identity (5G-GUTI) of the relay device, etc.

[0168] Furthermore, AMF#1 may send a registration request message#2 (e.g., Nudm_UECM_Registration) to the UDM, where the registration request message#2 may include an identifier of AMF#1 and an identifier of the relay device. The AMF may obtain subscription information of the relay device from the UDM based on the identifier of the relay device and perform authentication of the relay device. After successful authentication, AMF#1 may send a registration accept message to the relay device.

[0169] Step 702: The AF sends an inventory request message to the NEF, which is used to request to obtain the identifier of the tag.

[0170] Optionally, the inventory request message includes an identifier of the relay device. For example, the identifier may be a generic public subscription identifier (GPSI) of the relay device. It should be understood that the generic GPSI is usually required to handle 3GPP users in a different data network than the 3GPP system. For example, a UDM in the 3GPP system stores a mapping relationship between the GPSI and the corresponding SUPI.

[0171] Optionally, the inventory request message further includes an inventory object. For example, the inventory object may be at least one of the following: a tag identifier value interval, a tag identifier list, a tag group identifier, an application identifier, an enterprise user identifier, or information indicating a query regarding any tag identifier. For example, the tag identifier value interval may be, for example, tag identifier #10 to tag identifier #150, i.e., AF may indicate that an inventory needs to be performed on all tags including tag #10 to tag #150. For example, the tag identifier list may be, for example, an identifier corresponding to each tag. For example, the list may include tag identifier #10, tag identifier #13, tag identifier #20, tag identifier #25, etc., i.e., AF may clearly indicate the tag identifiers on which an inventory needs to be performed. For example, the tag group identifier may be, for example, tag group identifier #1 or tag group identifier #, and the tags included in tag group #1 are tag identifier #1 to tag identifier #50, and the tags included in tag group #2 are tag identifier #160 to tag identifier #200. For example, an identifier of an application may be understood as application #1, which includes multiple tags, i.e., the AF may indicate that an inventory is to be performed on the tags of the application. For example, an identifier of an enterprise user may be understood as the tags included in the enterprise user. For example, if enterprise user #1 includes tags #100 to #1000, the AF may indicate that an inventory is to be performed on the tags included in the enterprise user. For example, the AF may alternatively indicate a query regarding the identifier of any tag. i.e., the AF may alternatively not explicitly indicate that a tag is to be specifically queried.

[0172] Optionally, the inventory request message further includes indication information #2, which indicates the command and command execution parameters that need to be executed on the tag. Alternatively, the inventory request message may be understood to further include an indication of a target operation that needs to be executed on the tag. For example, the command indication may be one or more of the following: a read command (sometimes referred to as a "read operation"), a write command, an erase command, a block read command, a block erase command, a kill command, a lock command, an access command, etc. For example, for a read command, the command execution parameters may include a read storage area, a starting word address of the read storage area, a quantity of words, etc. In another example, for a write command, the command execution parameters include a write storage area, a starting word of the write storage area, and write data. For write information, the same write information may be transmitted for all inventory objects, or different write information may be transmitted for different inventory objects, respectively.

[0173] Step 703: The NEF determines that the AMF serving the relay device is AMF#1.

[0174] As described above, the UDM may store a mapping relationship between the SUCI and the GPSI, or the UDM may store a mapping relationship between the 5G-GUTI and the GPSI and determine an identifier of the relay device based on the mapping relationship. For example, the NEF may interact with the UDM and determine an AMF#1 that serves the relay device based on the identifier of the relay device.

[0175] Step 704: The NEF sends an inventory request message to the AMF#1.

[0176] Optionally, the inventory message may include at least one of the following contents: an identifier of the relay device, an inventory object, or indication information #2.

[0177] Step 705: AMF#1 sends a configuration update request message to the relay device, and this message is used to request the identifier of the tag.

[0178] Optionally, the configuration update request message may include at least one of the following contents: inventory object, indication information #2, etc.

[0179] Step 706: The relay device sends an inquiry request message to the tag within the coverage area of ​​the relay device, and the message is used to inquire about the tag's identifier.

[0180] For example, a relay device may transmit radio frequency information to tags within its coverage area. The radio frequency information may provide an excitation signal to the tags within the coverage area of ​​the relay device. After receiving the excitation signal, the tags within the coverage area may transmit a response signal to the relay device. For example, if there are 200 tags within the coverage area, 170 tags transmit a response signal to the relay device.

[0181] Furthermore, after receiving the response signals of one or more tags, the relay device may select tags. It is assumed that the relay device receives inventory object information. In this case, the relay device may perform a selection operation on the responding tags and select one or more tags based on the selection operation. The relay device may send an inquiry request message to one or more selected tags to request to obtain identifiers of the one or more tags.

[0182] Step 707: The first tag performs random access successfully.

[0183] For example, one or more selected tags can initiate a random access process, and one of the tags that successfully performs the random access is referred to as the "first tag." In a possible implementation, the random access process may include the following: the relay device includes a first random number in the inquiry message, and one or more selected tags locally set a second random number based on the first random number. If the second random number set by one tag is 0, the tag sends a third random number to the RAN. If the RAN successfully receives the third random number, the RAN sends the third random number to the tag. When the tag receives the third random number, it indicates that the tag has successfully performed the random access.

[0184] Step 708: The first tag sends a registration request message #3 to the AMF #1, where the registration request message #3 carries the identifier of the first tag.

[0185] Optionally, the registration request message #3 may further include a type of the first tag, for example, the first tag type is a passive tag, or the first tag type is a semi-passive tag.

[0186] In a possible implementation, the first tag may send message #1 through the relay device, where a registration request message #3 is encapsulated in message #1, and this registration request message #3 carries the identifier of the first tag. After receiving message #1, the RAN may decapsulate message #1 to obtain registration request message #3, encapsulate the registration request message using message #2, and send message #2 to AMF #1. The AMF #1 decapsulates message #2 to obtain registration request message #3. The above implementation may alternatively be understood as the RAN sending the identifier of the first tag by transparently sending a message. As described above, in the architecture of FIG. 4(a), indication information #1 was transmitted during the previous relay device registration, and the RAN selects AMF #1 for the relay device. Therefore, the RAN then sends the received message sent by the relay device to AMF #1.

[0187] Specifically, for example, if the relay device includes indication information #1 in the RRC message in step 701, then in this step the RAN may send a registration request message #3 to the AMF #1 selected in step 701. If the relay device includes indication information #1 in the NAS message in step 701, then in this step the first tag may include the first indication information in message #1, and the RAN may send a registration request message #3 to the AMF #1 selected in step 701 based on the indication information #1. In this step, the relay device forwards the message #1 received from the first tag to the RAN.

[0188] Step 709: AMF#1 sends a registration acceptance message to the first tag, where the registration acceptance message indicates that the first tag has been successfully registered.

[0189] In a possible implementation, AMF#1 encapsulates the registration accept message into message #3 and sends message #3 to the RAN. The RAN decapsulates message #3 to obtain the registration accept message, encapsulates this registration accept message into message #4, and sends this message #4 to the first tag via the relay device. The above implementation can be understood as an alternative in which the relay device forwards the received message #4 to the first tag.

[0190] Optionally, the method further includes step 710: AMF#1 sends a configuration update request message to the first tag, where the configuration update request message includes an execution command.

[0191] Optionally, the configuration update request message further includes execution parameters corresponding to the execution command.

[0192] It is assumed that AMF#1 further receives an execution command in step 704. In this case, AMF#1 may send a configuration update request message to the first tag via the RAN, where the configuration update request message includes the execution command.

[0193] In a possible implementation, AMF#1 encapsulates the configuration update request message into message #5 and sends message #5 to the RAN. After receiving message #5 from AMF#1, the NG-RAN decapsulates message #5 to obtain the configuration update request message, encapsulates the configuration update request message into message #6, and then sends message #6 to the first tag via the relay device. In this step, the relay device may be responsible for forwarding message #6.

[0194] Optionally, the method further includes step 711: the first tag sends a configuration update completion message to AMF#1, where the configuration update completion message includes information about the execution result corresponding to the execution command.

[0195] For example, when the execution command includes a read operation, the information about the execution result corresponding to the execution command may include read data. The read data included in the information about the execution result corresponding to the execution command may be encrypted, for example, may be encrypted using a key. There are multiple ways to obtain the key. For example, another device may send the key to the first tag. In a possible implementation, in an authentication procedure for the first tag, the authentication server sends the key to the first tag. In response, the first tag receives the key from the authentication server. The authentication server may send the key directly to the first tag or may send the key via another device. In another example, the authentication server sends the key to AMF#1. In response, AMF#1 receives the key from the authentication server. Furthermore, AMF#1 sends the key to the first tag. In another possible implementation, the key may be pre-configured in the tag.

[0196] For example, if the execution command includes a write operation, the information about the execution result corresponding to the execution command may include indication information that the write operation has been completed for the first tag.

[0197] For example, if the execution command includes an access operation, the information about the execution result corresponding to the execution command may include indication information that the access operation has been completed for the first tag.

[0198] For example, if the execution command includes a kill operation, the information about the execution result corresponding to the execution command may include indication information that the kill operation has been completed for the first tag.

[0199] For example, if the execution command includes a locking operation, the information about the execution result corresponding to the execution command may include indication information that the locking operation has been completed for the first tag.

[0200] For example, if the execution command includes a block write operation, the information about the execution result corresponding to the execution command may include indication information that the block write operation has been completed for the first tag.

[0201] For example, if the execution command includes a block erase, the information about the execution result corresponding to the execution command may include indication information that the block erase operation has been completed for the first tag.

[0202] Specifically, the first tag may send a configuration update complete message to AMF#1 via the RAN. For example, the first tag may encapsulate the configuration update complete message in message #7. After receiving message #7 from the first tag, the RAN may encapsulate message #7 to obtain a configuration update complete message, then encapsulate the configuration update complete message in message #8, and send message #8 to the AMF. In this step, the relay terminal device may forward message #7.

[0203] Step 712: AMF#1 determines that the inventory on the first tag is completed, and sends an inventory request message to the relay device.

[0204] For example, AMF#1 sends an inventory request to the relay device, where the inventory request includes indication information #3, where the indication information #3 indicates at least one of the following: indicating that the target operation has been completed for the first tag, indicating an inquiry regarding the identifier of the next tag, or indicating that the next random access procedure is to be performed on the tag. For example, the inventory request may be encapsulated in a configuration update request message, where the configuration update request message is sent to the relay device.

[0205] Step 713: The relay device performs an inventory on the next tag.

[0206] In a possible implementation, after receiving the indication information #3, the relay device determines that the inventory on the current first tag is completed, and in this case, may continue to perform the inventory on the next tag, i.e., may inquire about the identification information of the next tag, which will be referred to as the second tag for the sake of distinction.

[0207] The relay device may send an inquiry request message to one or more selected tags to request to obtain the identifiers of the one or more tags. In a possible implementation, the inquiry request message may be an inquiry repeat message. After receiving the inquiry message, the first tag may actively terminate the inventory process, i.e., may no longer respond to operation requests for the one or more selected tags. After receiving the inquiry message, one or more other selected tags may initiate a random access process, and one terminal device that successfully performs the random access among them is referred to as the second tag in this embodiment.

[0208] Specifically, the random access process may include: one or more other selected tags subtract 1 from the previously set second random number; if the second random number of one tag decreases to 0, the tag sends a fourth random number to the RAN; if the RAN can successfully receive the fourth random number, the RAN can send the fourth random number to the tag; when the tag receives the fourth random number, it indicates that the tag has successfully performed random access; after the second tag successfully performs random access, the second tag sends identification information of the second tag to the AMF.

[0209] For the process of processing the second tag by AMF#1, please refer to the above process of processing the first tag (e.g., step 708 to step 711), and the details will not be described again.

[0210] Step 714: The relay device determines that the inventory on all tags is complete.

[0211] The above process (e.g., steps 706 to 713) is performed periodically until the relay device does not receive a random access request message initiated by any tag within a set time period (e.g., within a first time period). In this case, the relay device determines that an inventory is complete for all tags within the coverage area of ​​the relay device. Alternatively, the relay device may be understood to determine that a query, command execution, or target operation is complete for tags within the coverage area of ​​the relay device.

[0212] Step 715: The relay device sends an inventory completion message to AMF#1.

[0213] For example, an inventory complete message indicates that the relay device has completed an inventory of discoverable tags for the current inventory initiated by the AF.

[0214] Step 716: AMF#1 sends an inventory report message to the NEF.

[0215] For example, the message may include identifiers of one or more tags. In another example, the message may alternatively include information about the execution results corresponding to the identifiers of one or more tags.

[0216] Step 717: The NEF sends an inventory report message to the AF.

[0217] For example, the message may include one or more tag identifiers. As another example, the message may alternatively include information about the execution results corresponding to the one or more tag identifiers.

[0218] According to the above technical solution, in this application, a relay device can communicate with a core network element through a first radio access network element, and the relay device can obtain an identifier of a terminal device within the coverage area of ​​the relay device and send the identifier to a first access and mobility management function network element through the first radio access network element. In this way, communication between the terminal device and the network element is realized in a large-coverage, large-scale, and wide-area scenario.

[0219] 8A and 8B are schematic flowcharts of yet another communication method 800 according to the present application. In the method 800, it is assumed that the AMF serving the relay device and the AMF serving the tag are the same. That is, the method 800 is applicable to the architecture of FIG. 4(a). In addition, the method 800 further takes into account that when the relay device moves during the tag inventory process, the RAN serving the relay device and the AMF serving the relay device change. For example, the RAN serving the relay device is switched from RAN#1 to RAN#2, and similarly, the AMF serving the relay device is switched from AMF#1 to AMF#2. The following describes in detail how to continue completing the inventory after the relay device moves during the tag inventory process. The following describes the steps shown in FIGS. 8A and 8B. The method includes the following steps:

[0220] For steps 801 to 813, please refer to steps 701 to 713 of method 700. The details will not be described again.

[0221] In this embodiment, it is assumed that when the relay device performs an inventory on the third tag, the location of the relay device moves and moves out of the coverage area of ​​the current RAN#1 (which may alternatively be understood as the source RAN).

[0222] In this case, step 814 is executed. The relay device sends a registration request message #4 to RAN #2, which includes the identifier of the relay device.

[0223] For example, the identifier may be a subscription concealed identifier (SUCI) of the relay device, a 5th generation globally unique temporary UE identity (5G-GUTI) of the relay device, etc.

[0224] Step 815: RAN#2 sends a registration request message#5 to AMF#2 (which may alternatively be understood as the target AMF).

[0225] Optionally, if the relay device includes indication information #1 in the registration request message #4, and this indication information #1 indicates that the relay device supports communication with tags, RAN #2 may select an AMF (denoted as AMF #2 in this embodiment) that supports communication with tags for the relay device. Specifically, for an implementation in which RAN #2 determines AMF #2, please refer to the description of determining AMF #1 by RAN #1 in step 601 of method 600.

[0226] Step 816: AMF#2 obtains user context information of the relay device from AMF#1 (which may alternatively be understood as the source AMF) based on the identifier of the relay device.

[0227] In this embodiment, the user context information includes inventory request information. Optionally, the inventory message may include at least one of the following contents: an identifier of the relay device, which may be, for example, a generic public subscription identifier (GPSI) of the relay device; an inventory object; or indication information #2 indicating the command and command execution parameters that need to be executed on the tag. For details, see the description of step 602 of method 600.

[0228] Step 817: AMF#2 registers with the UDM.

[0229] For example, AMF#2 may send a registration request message #6 (e.g., Nudm_UECM_Registration) to the UDM, which includes an identifier of AMF#2 and an identifier of the relay device.

[0230] Step 818: AMF#2 sends a registration acceptance message to the relay device.

[0231] Step 819: The third tag performs random access normally.

[0232] Specifically, for the random access process of the third tag, see step 707 of method 700.

[0233] Step 820: The third tag sends a registration request message #7 to the AMF #2, where the registration request message #7 includes the identifier of the third tag.

[0234] Optionally, the registration request message #7 may further include a third tag type, for example, the third tag type is a passive tag, or the third tag type is a semi-passive tag.

[0235] Specifically, for the implementation of step 720, please refer to the description of step 708 of method 700.

[0236] Step 821: AMF#2 sends a registration acceptance message to the third tag, where the registration acceptance message indicates that the third tag has been successfully registered.

[0237] Specifically, for the implementation of step 821, please refer to the description of step 709 of method 700.

[0238] Optionally, the method further includes step 822: AMF#2 sends a configuration update request message to the third tag, where the configuration update request message includes an execution command.

[0239] Optionally, the configuration update request message further includes execution parameters corresponding to the execution command.

[0240] Specifically, for the implementation of step 822, please refer to the description of step 710 of method 700.

[0241] Optionally, the method further includes step 823: the third tag sends a configuration update completion message to AMF#2, where the configuration update completion message includes information about the execution result corresponding to the execution command.

[0242] Specifically, for the implementation of step 823, please refer to the description of step 711 of method 700.

[0243] Step 824: AMF#2 determines that the inventory on the third tag is completed, and sends an inventory request message to the relay device.

[0244] For example, AMF#2 sends an inventory request to the relay device, where the inventory request includes indication information #4, where indication information #4 indicates at least one of the following: indicating that the target operation has been completed for the third tag, indicating a query for the identifier of the next tag, or indicating that the next random access procedure is to be performed on the tag. For example, the inventory request may be encapsulated in a configuration update request message, where the configuration update request message is sent to the relay device.

[0245] Step 825: The relay device performs an inventory on the next tag.

[0246] In a possible implementation, after receiving indication information #4, the relay device may determine that the inventory on the current third tag is complete, and may then continue to perform inventory on the next tag, i.e., inquire about the identity of the next tag, which will be referred to as the fourth tag for the sake of distinction.

[0247] Specifically, see step 713 of method 700 for a specific implementation in which the relay device performs an inventory on the fourth tag.

[0248] Step 826: The relay device determines that the operation for all tags is complete.

[0249] The above-described process (e.g., steps 819 to 825) is performed periodically until the relay device does not receive a random access request message initiated by any tag within a set time period (e.g., within a first time period). In this case, the relay device determines that an inventory is complete for all tags within the coverage area of ​​the relay device. Alternatively, the relay device may be understood to determine that a query, command execution, or target operation is complete for tags within the coverage area of ​​the relay device.

[0250] Step 827: The relay device sends an inventory completion message to AMF#2.

[0251] For example, an inventory complete message indicates that the relay device has completed an inventory of discoverable tags for the current inventory initiated by the AF.

[0252] Step 828: AMF#2 sends an inventory report message to the NEF.

[0253] For example, the message may include identifiers of one or more tags. In another example, the message may alternatively include information about the execution results corresponding to the identifiers of one or more tags.

[0254] Step 829: The NEF sends an inventory report message to the AF.

[0255] For example, the message may include one or more tag identifiers. As another example, the message may alternatively include information about the execution results corresponding to the one or more tag identifiers.

[0256] According to the above technical solution, the present application further considers that the location of the relay device moves during the tag inventory process. In this case, the relay device may switch RAN and AMF, and the target AMF may obtain context information of the relay device from the source AMF, so that the core network element can continue to perform inventory on the tag. In this way, communication between the tag and the network device can be implemented in a large coverage scenario.

[0257] 9A and 9B are schematic flowcharts of yet another communication method 900 according to the present application. In the method 900, it is assumed that the AMF providing a service for the relay device is different from the AMF providing a service for the remote terminal device. That is, the method 900 is applicable to the architecture of FIG. 4(b). In this embodiment, it is assumed that the AMF providing a service for the relay device is AMF#4, and the AMF providing a service for the tag is AMF#3. The method includes the following steps:

[0258] Step 901: The relay device registers with the core network.

[0259] Specifically, for example, a relay device may register with the core network based on a typical terminal device registration procedure.

[0260] Step 902: The AF sends an inventory request message to the TMF, which is used to request the identifier of the tag.

[0261] Optionally, the inventory request message includes: an identifier of the relay device, which may be, for example, a generic public subscription identifier (GPSI) of the relay device; an inventory object, which may be at least one of the following: a tag identifier value interval, a tag identifier list, a tag group identifier, an application identifier, an enterprise user identifier, or information indicating a query regarding any tag identifier; and indication information #2, indicating the command and command execution parameters that need to be executed on the tag. For details, see the description of step 702 of method 700.

[0262] In a possible implementation, the AF may alternatively send an inventory request message to the TMF via the NEF.

[0263] Step 903: The TMF determines that the AMF serving the relay device is AMF#4.

[0264] For example, the TMF may interact with the UDM to obtain the AMF#4 that provides services to the relay device based on the identifier of the relay device.

[0265] Step 904: The TMF sends an inventory request message to the AMF#4.

[0266] Optionally, the inventory message may include at least one of the following contents: an identifier of the relay device, an inventory object, or indication information #2.

[0267] In a possible implementation, the inventory request message may further include an inventory identifier, which may be assigned by the TMF. For example, the "inventory identifier" may be inventory identifier #1, which indicates that the inventory should be performed on all passive tags. In another example, the "inventory identifier" may be inventory identifier #2, which indicates that the inventory should be performed on all semi-passive tags. The inventory identifier may be understood as a specific identifier assigned by the TMF to the current inventory service. When receiving a message from a different AMF, the TMF may determine that the message is associated with the current inventory service based on the inventory identifier.

[0268] In another possible implementation, the inventory request message further carries inventory indication information (which may alternatively be understood as an inventory object), and the inventory indication information includes at least one of the following content: a value interval of an identifier of a terminal device, an identifier list of a terminal device, an identifier of a group of terminal devices, or information indicating a query regarding an identifier of any terminal device. Then, upon receiving a message from a different AMF, the TMF can determine whether the identifier of the terminal device carried in the message satisfies at least one of the aforementioned indication information, and determine whether the message is associated with the current inventory service.

[0269] Step 905: AMF#4 sends a configuration update request message to the relay device, which is used to request the tag's identifier.

[0270] Optionally, the configuration update request message may include at least one of the following contents: inventory object, indication information #2, etc.

[0271] Optionally, the configuration update request message may further include an inventory identifier.

[0272] Step 906: The relay device sends an inquiry request message to the tag within the coverage area of ​​the relay device, and the message is used to inquire about the identifier of the tag.

[0273] Specifically, for the implementation of step 906, please refer to the description of step 706 of method 700.

[0274] Optionally, in step 806, the query request message further includes an inventory identifier.

[0275] Step 907: The first tag performs random access successfully.

[0276] Specifically, for the implementation of step 907, please refer to the description of step 707 of method 700.

[0277] Step 908: The first tag sends a registration request message #3 to the AMF #3, where the registration request message #3 carries the identifier of the first tag.

[0278] Specifically, for the implementation of step 908, please refer to the description of step 708 of method 700.

[0279] Step 909: AMF#3 sends the inventory result report to the TMF.

[0280] For example, the inventory results report may include an identifier of the first tag.

[0281] Optionally, the inventory result further includes an inventory identifier. Optionally, the TMF may initiate an authentication procedure for the first tag.

[0282] Step 910: The TMF sends an inventory result response to the AMF#3.

[0283] For example, the TMF may determine that the first tag is the tag requested in the inventory request of step 802 based on the identifier (or inventory identifier) ​​of the first tag belonging to the scope of the inventory object.

[0284] Step 911: AMF#3 sends a registration acceptance message to the first tag, where the registration acceptance message indicates that the first tag has been successfully registered.

[0285] Specifically, for the implementation of step 911, please refer to step 709 of method 700.

[0286] Optionally, the method further includes step 912: the TMF sends a command execution request message to the AMF#3, indicating that the command is to be executed on the tag.

[0287] If the TMF receives indication information #2 from the AF in step 902, in this step the TMF sends a command execution request message to AMF#3.

[0288] Optionally, the request message further includes execution parameters corresponding to the execution command.

[0289] Optionally, the method further includes step 913: AMF#3 sends a configuration update request message to the first tag, where the configuration update request message includes an execution command.

[0290] Specifically, for the implementation of step 913, see step 710 of method 700.

[0291] Optionally, the method further includes step 914: the first tag sends a configuration update completion message to AMF#3, where the configuration update completion message includes information about the execution result corresponding to the execution command.

[0292] Specifically, for the implementation of step 914, see step 711 of method 700.

[0293] Step 915: AMF#3 sends an inventory command response message to the TMF, and this response message includes the information received in step 814 about the execution result of the first tag.

[0294] For example, an inventory command response message carries an inventory identifier.

[0295] In a possible implementation, the TMF may determine that the inventory command response message is a response message to the inventory request message based on the inventory identifier transmitted in the inventory command response message. In another possible implementation, since the application function network element transmits inventory indication information (i.e., inventory objects) to the TMF, if the tag identifier transmitted in the inventory command response message or the inventory result response message received by the TMF and transmitted by the AMF#3 satisfies at least one of the inventory indication information, the TMF may determine that the message is a response message to the inventory request message. In other words, according to the technical solution provided in this application, the TMF may perform tag management and inventory.

[0296] Step 916: The TMF determines that the inventory on the first tag is complete and sends an inventory request message to AMF#4.

[0297] For example, the TMF sends an inventory request to AMF#4, which includes indication information #3, which indicates at least one of the following: indicating that the target operation has been completed for the first tag, indicating an inquiry regarding the identifier of the next tag, or indicating that the next random access procedure should be performed on the tag.

[0298] Step 917: AMF#4 sends an inventory request message to the relay device.

[0299] For example, AMF#4 sends an inventory request to the relay device, where the inventory request includes indication information #3, where indication information #3 indicates at least one of the following: indicating that the target operation has been completed for the first tag, indicating an inquiry regarding the identifier of the next tag, or indicating that the next random access procedure is to be performed on the tag. For example, the inventory request may be encapsulated in a configuration update request message, and the configuration update request message is sent to the relay device.

[0300] Step 918: The relay device performs an inventory on the next tag.

[0301] Specifically, for the implementation of step 914, see step 713 of method 700.

[0302] Step 919: The relay device determines that the operation for all tags is complete.

[0303] The above-described process (e.g., steps 906 through 918) is performed periodically until the relay device does not receive a random access request message initiated by any tag within a set time period (e.g., within a first time period). In this case, the relay device determines that an inventory is complete for all tags within the coverage area of ​​the relay device. Alternatively, the relay device may be understood to determine that a query, command execution, or target operation is complete for tags within the coverage area of ​​the relay device.

[0304] Step 920: The relay device sends an inventory completion message to AMF#4.

[0305] For example, an inventory complete message indicates that the relay device has completed an inventory of discoverable tags for the current inventory initiated by the AF.

[0306] Step 921: AMF#4 sends an inventory report message to the TMF.

[0307] For example, the message may include identifiers of one or more tags. In another example, the message may alternatively include information about the execution results corresponding to the identifiers of one or more tags.

[0308] Step 923: The TMF sends an inventory report message to the AF.

[0309] For example, the message may include identifiers of one or more tags. In another example, the message may alternatively include information about the execution results corresponding to the identifiers of one or more tags.

[0310] In a possible implementation, the TMF may further send an inventory report message to the AF.

[0311] According to the above technical solution, in the present application, a relay device can communicate with a core network element through a radio access network element and an access and mobility management function network element, so that the relay device can obtain an identifier of a terminal device within the coverage area of ​​the relay device and send the identifier to a second network element through the access and mobility management function network element, and the second network element can perform inventory on the terminal device. In this way, communication between the terminal device and the network device is implemented in a large-coverage, large-scale, and wide-area scenario.

[0312] 10A and 10B are schematic flowcharts of yet another communication method 1000 according to the present application. In the method 1000, it is assumed that the AMF serving the relay device is different from the AMF serving the tag. That is, the method 1000 is applicable to the architecture of FIG. 4(b). Additionally, the method 1000 further takes into consideration that, when the relay device moves during the tag inventory process, the RAN serving the relay device and the AMF serving the relay device change. For example, the RAN serving the relay device is switched from RAN#1 to RAN#2, and similarly, the AMF serving the relay device is switched from AMF#4 to AMF#2. The following describes in detail how to continue completing the inventory after the relay device moves during the tag inventory process. The following describes the steps shown in FIGS. 10A and 10B. The method includes the following steps:

[0313] For steps 1001 to 1018, please refer to steps 901 to 918 of the method 900. The details will not be described again.

[0314] In this embodiment, it is assumed that when the relay device performs an inventory on the third tag, the location of the relay device moves and moves out of the coverage area of ​​the current RAN#1 (which may alternatively be understood as the source RAN).

[0315] In this case, step 1019 is executed. The relay device sends a registration request message #4 to RAN #2, which includes the identifier of the relay device.

[0316] For example, the identifier may be a subscription concealed identifier (SUCI) of the relay device, a 5th generation globally unique temporary UE identity (5G-GUTI) of the relay device, etc.

[0317] Step 1020: RAN#2 sends a registration request message#5 to AMF#2 (which may alternatively be understood as the target AMF).

[0318] Step 1021: #2 obtains user context information of the relay device from AMF #4 (which may alternatively be understood as the source AMF) based on the identifier of the relay device.

[0319] In this embodiment, the user context information includes inventory request information. Optionally, the inventory message may include at least one of the following contents: an identifier of the relay device, which may be, for example, a generic public subscription identifier (GPSI) of the relay device; an inventory object; or indication information #2 indicating the command and command execution parameters that need to be executed on the tag. For details, see the description of step 702 of method 700.

[0320] Step 1022: AMF#2 registers with the UDM.

[0321] For example, AMF#2 may send a registration request message #6 (e.g., Nudm_UECM_Registration) to the UDM, which includes an identifier of AMF#2 and an identifier of the relay device.

[0322] Step 1023: AMF#2 sends a registration acceptance message to the relay device.

[0323] Step 1024: The third tag performs random access normally.

[0324] Specifically, for the random access process of the third tag, see step 707 of method 700.

[0325] Step 1025: The third tag sends a registration request message #7 to the AMF #3, where the registration request message #7 includes the identifier of the third tag.

[0326] Optionally, the registration request message #7 may further include a third tag type, for example, the third tag type is a passive tag, or the third tag type is a semi-passive tag.

[0327] Specifically, for the implementation of step 1025, please refer to the description of step 708 of method 700.

[0328] Step 1026: AMF#3 sends an inventory result report message to the TMF.

[0329] For example, the inventory result report may include an identifier for the third tag.

[0330] Optionally, the inventory result further includes an inventory identifier. Optionally, the TMF may initiate an authentication procedure for the third tag.

[0331] Step 1027: The TMF sends an inventory result response message to the AMF#3.

[0332] For example, the TMF may determine that the third tag is the tag requested in the inventory request of step 1002 based on the identifier (or inventory identifier) ​​of the third tag belonging to the range of inventory objects.

[0333] Step 1028: AMF#3 sends a registration acceptance message to the third tag, where the registration acceptance message indicates that the third tag has been successfully registered.

[0334] Specifically, for the implementation of step 1028, see step 709 of method 700.

[0335] Optionally, the method further includes step 1029: the TMF sends a command execution request message to the AMF#2, indicating that the command should be executed on the tag.

[0336] If the TMF receives indication information #2 from the AF in step 1002, then in this step the TMF sends a command execution request message to AMF#2.

[0337] Optionally, the request message further includes execution parameters corresponding to the execution command.

[0338] Optionally, the method further includes step 1030: AMF#3 sends a configuration update request message to the third tag, where the configuration update request message includes an execution command.

[0339] Specifically, for the implementation of step 1030, please refer to step 710 of method 700.

[0340] Optionally, the method further includes step 1031: the third tag sends a configuration update completion message to AMF#3, where the configuration update completion message includes information about the execution result corresponding to the execution command.

[0341] Specifically, for the implementation of step 1031, please refer to step 711 of method 700.

[0342] Step 1032: AMF#3 sends an inventory command response message to the TMF, and this response message includes the information received in step 1031 about the execution result of the third tag.

[0343] Step 1033: The TMF determines that the inventory on the third tag is complete and sends an inventory request message to AMF#2.

[0344] For example, the TMF may send an inventory request to AMF#2, the inventory request including indication information #3, which indicates at least one of the following: indicating that the target operation has been completed for the third tag, indicating an inquiry regarding the identifier of the next tag, or indicating that the next random access procedure is to be performed on the tag.

[0345] Step 1034: AMF#2 sends an inventory request message to the relay device.

[0346] For example, AMF#2 sends an inventory request to the relay device, where the inventory request includes indication information #3, where indication information #3 indicates at least one of the following: indicating that the target operation has been completed for the third tag, indicating a query for the identifier of the next tag, or indicating that the next random access procedure is to be performed on the tag. For example, the inventory request may be encapsulated in a configuration update request message, and the configuration update request message is sent to the relay device.

[0347] Step 1035: The relay device performs an inventory on the next tag.

[0348] Specifically, for the implementation of step 1035, see step 713 of method 700.

[0349] Step 1036: The relay device determines that the operation for all tags is complete.

[0350] The above process (e.g., steps 1024 to 1035) is performed periodically until the relay device does not receive a random access request message initiated by any tag within a set time period (e.g., within a first time period). In this case, the relay device determines that an inventory is complete for all tags within the coverage area of ​​the relay device. Alternatively, the relay device may be understood to determine that a query, command execution, or target operation is complete for tags within the coverage area of ​​the relay device.

[0351] Step 1037: The relay device sends an inventory completion message to AMF#2.

[0352] For example, an inventory complete message indicates that the relay device has completed an inventory of discoverable tags for the current inventory initiated by the AF. Step 1038: AMF#2 sends an inventory report message to the TMF.

[0353] For example, the message may include identifiers of one or more tags. In another example, the message may alternatively include information about the execution results corresponding to the identifiers of one or more tags.

[0354] Step 1039: The TMF sends an inventory report message to the AF.

[0355] For example, the message may include identifiers of one or more tags. In another example, the message may alternatively include information about the execution results corresponding to the identifiers of one or more tags.

[0356] In a possible implementation, the TMF may also send an inventory report message to the AF.

[0357] According to the above technical solution, in this embodiment, when the AMF serving the relay device and the AMF serving the tag are different, and the location of the relay device is further considered to move in the tag inventory process, the relay device may switch RAN and AMF, and the target AMF may obtain the context information of the relay device from the source AMF, so that the core network element can continue to perform inventory on the tag. In this way, communication between the terminal device and the network device can be implemented in a large coverage scenario.

[0358] 5 to 10A and 10B of the embodiments of the present application are intended to merely help those skilled in the art understand the embodiments of the present application, but are not intended to limit the embodiments of the present application to the specific scenarios of these examples. Those skilled in the art can certainly make various equivalent modifications or variations based on the examples of Figures 5 to 10A and 10B, and such modifications or variations also fall within the scope of the embodiments of the present application.

[0359] It may be further understood that some optional features in the embodiments of the present application may be independent of other features in some scenarios, or may be combined with other features in some scenarios, without limitation.

[0360] It can be further understood that the embodiments described herein may be independent solutions or may be combined based on internal logic. All of these solutions fall within the scope of protection of the present application. In addition, the descriptions or descriptions of the terms of the embodiments may be mutually referenced or described in various embodiments. This is not limited.

[0361] In this application, "when" may be understood to mean that the device executes the corresponding process in the intended instance. This term is not intended to be time-limited, does not require the device to determine the action when it is performed, and does not imply any other limitations.

[0362] The above mainly describes the solutions provided in the embodiments of the present application from the perspective of interactions between nodes. It can be understood that, to implement the aforementioned functions, nodes, such as access and mobility management function network elements, relay devices, and tag management function network elements, include corresponding hardware structures and / or software modules for performing the functions. Those skilled in the art can recognize that, in combination with the example units and algorithm steps described in the embodiments disclosed herein, the present application can be implemented by hardware or a combination of hardware and computer software. Whether the functions are implemented by hardware or hardware driven by computer software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0363] In the embodiments of the present application, the division into functional modules may be performed on the access and mobility management function network element and the associated core network element based on the above-mentioned method example. For example, the division into functional modules may be performed based on corresponding functions, or two or more functions may be integrated into one processing module. The integrated module may be implemented in the form of hardware or in the form of a software function module. It should be noted that in the embodiments of the present application, the division into modules is an example and is merely a logical division of functions. In actual implementation, other division methods may be used. An example in which the division into functional modules is performed based on corresponding functions is used below for explanation.

[0364] 11 is a block diagram of a communication device 100 according to an embodiment of the present application. As shown in the figure, the device 100 may include a transceiver unit 110 and a processing unit 120.

[0365] In a possible design, the apparatus 100 may be a relay device in the aforementioned method embodiments, or may be a chip configured to perform the functions of the relay device in the aforementioned method embodiments. The apparatus 100 may correspond to the relay device in methods 500 to 1000 according to the embodiments of the present application.

[0366] For example, the apparatus 100 may correspond to a relay device in the methods 500, 700, and 800 according to the embodiments of the present application, and the apparatus 100 may perform steps corresponding to the relay device in the methods 500, 700, and 800 according to the embodiments of the present application.

[0367] In this implementation, the transceiver unit is configured to receive a first non-access stratum message from a first access and mobility management function network element via a first radio access network device. The processing unit is configured to control the transceiver unit to transmit radio frequency information to a terminal device within a coverage area of ​​the communication device based on the first non-access stratum message. The transceiver unit is configured to receive a second non-access stratum message from the first terminal device, the second non-access stratum message carrying an identifier of the first terminal device. The transceiver unit is configured to transmit the second non-access stratum message to the first access and mobility management function network element via the first radio access network device.

[0368] In a possible implementation, the transceiver unit is configured to transmit a first radio resource control message to the first radio access network device, the first radio resource control message carrying the registration request message and the first indication information.

[0369] In a possible implementation, the transceiver unit is configured to receive a third non-access stratum message from a first access and mobility management function network element via a first radio access network device. The transceiver unit is configured to transmit the third non-access stratum message to a first terminal device. The transceiver unit is configured to receive a fourth non-access stratum message from the first terminal device. The transceiver unit is configured to transmit the fourth non-access stratum message to the first access and mobility management function network element via the first radio access network device.

[0370] In a possible implementation, the transceiver unit is configured to receive third indication information from a first access and mobility management function network element via a first radio access network device, the transceiver unit is configured to receive a fifth non-access stratum message from a second terminal device, and the transceiver unit is configured to transmit the fifth non-access stratum message to the first access and mobility management function network element via the first radio access network device.

[0371] In a possible implementation, the apparatus is handed over from a first radio access network device to a second radio access network device, the transceiver unit is configured to send a second radio resource control message to the second radio access network device, the second radio resource control message carrying the registration request message and the first indication information, and the transceiver unit is configured to receive a registration accept message from the second access and mobility management function network element.

[0372] For example, the apparatus 100 may correspond to a relay device in the methods 600, 900, and 1000 according to the embodiments of the present application, and the apparatus 100 may perform steps corresponding to the relay device in the methods 600, 900, and 1000 according to the embodiments of the present application.

[0373] In one possible implementation, the transceiver unit is configured to receive a first non-access stratum message from a fourth access and mobility management function network element via a first radio access network device. The processing unit is configured to control the transceiver unit to transmit radio frequency information to a terminal device within a coverage area of ​​the apparatus based on the first non-access stratum message. The transceiver unit is configured to receive a second non-access stratum message from the first terminal device. The transceiver unit is configured to transmit the second non-access stratum message to a third access and mobility management function network element via the first radio access network device.

[0374] In a possible implementation, the transceiver unit is configured to receive a third non-access stratum message from a third access and mobility management function network element via the first radio access network device. The transceiver unit is configured to transmit the third non-access stratum message to the first terminal device. The transceiver unit is configured to receive a fourth non-access stratum message from the first terminal device, the fourth non-access stratum message carrying information about an execution result corresponding to a target operation performed at the first terminal device. The transceiver unit is configured to transmit the fourth non-access stratum message to the third access and mobility management function network element via the first radio access network device.

[0375] In a possible implementation, the transceiver unit is configured to receive third indication information from a fourth access and mobility management function network element via the first radio access network device. The transceiver unit is configured to receive a fifth non-access stratum message from a second terminal device, the fifth non-access stratum message carrying an identifier of the second terminal device. The transceiver unit is configured to transmit the fifth non-access stratum message to the third access and mobility management function network element via the first radio access network device.

[0376] In a possible design, the apparatus 100 may be a first access and mobility management function network element (e.g., AMF#1) in the aforementioned method embodiments, or may be a chip configured to perform the functions of the first access and mobility management function network element in the aforementioned method embodiments. It should be understood that the apparatus 100 may correspond to the first access and mobility management function network element or AMF#1 in the methods 500, 700, and 800 according to the embodiments of the present application, and the apparatus 100 may perform steps corresponding to the first access and mobility management function network element or AMF#1 in the methods 500 to 800 of the embodiments of the present application.

[0377] In one possible implementation, the transceiver unit is configured to receive a seventh non-access stratum message from the first network element, the seventh non-access stratum message being used to request obtaining an identifier of the terminal device. The processing unit is configured to control the transceiver unit to transmit a first non-access stratum message to the relay device based on the identifier of the relay device. The transceiver unit is configured to receive a second non-access stratum message from the first terminal device via the relay device. The transceiver unit is configured to transmit an eighth non-access stratum message to the first network element, the eighth non-access stratum message carrying the identifier of the first terminal device.

[0378] In a possible implementation, the transceiver unit being configured to receive a second non-access stratum message from the first terminal device via the relay device includes: the transceiver unit being configured to receive a second non-access stratum message from the first terminal device via the relay device and the first radio access network device.

[0379] In a possible implementation, the transceiver unit is configured to transmit a third non-access stratum message to the relay device, the third non-access stratum message carrying the second indication information, and the transceiver unit is configured to receive a fourth non-access stratum message from the relay device.

[0380] In a possible implementation, the transceiver unit is configured to transmit the third indication information to the relay device, and the transceiver unit is configured to receive the fifth non-access stratum message from the second terminal device via the relay device.

[0381] In a possible implementation, the transceiver unit is configured to receive a fourth indication information from the relay device.

[0382] In a possible implementation, the transceiver unit is configured to transmit the context information of the relay device to a second access and mobility management function network element.

[0383] In a possible design, the apparatus 100 may be a first radio access network device (e.g., RAN#1) in the aforementioned method embodiments, or may be a chip configured to perform the functions of the first radio access network device in the aforementioned method embodiments. It should be understood that the apparatus 100 may correspond to the first radio access network device or RAN#1 in the methods 500, 700, and 800 according to the embodiments of the present application, and the apparatus 100 may perform steps corresponding to the first radio access network device or RAN#1 in the methods 500 to 800 of the embodiments of the present application.

[0384] In a possible implementation, the transceiver unit is configured to receive a first radio resource control message from the relay device, the first radio resource control message carrying a registration request message and first indication information, and to transmit the registration request message to a first access and mobility management function network element.

[0385] In a possible implementation, the transceiver unit is configured to receive a first non-access stratum message from a first access and mobility management function network element. The transceiver unit is configured to transmit the first non-access stratum message to a relay device. The transceiver unit is configured to receive a second non-access stratum message from the relay device, the second non-access stratum message carrying an identifier of a first terminal device, the first terminal device being a terminal device within a coverage area of ​​the relay device that successfully performs random access. The processing unit is configured to determine to transmit the second non-access stratum message to the first access and mobility management function network element.

[0386] In a possible design, the apparatus 100 may be a fourth access and mobility management function network element (e.g., AMF#4) in the aforementioned method embodiments, or may be a chip configured to perform the functions of the fourth access and mobility management function network element in the aforementioned method embodiments. It should be understood that the apparatus 100 may correspond to the fourth access and mobility management function network element or AMF#4 in the method 600, the method 900, and the method 1000 according to the embodiments of the present application, and the apparatus 100 may perform steps corresponding to the fourth access and mobility management function network element or AMF#4 in the method 600, the method 900, and the method 1000 of the embodiments of the present application.

[0387] In a possible implementation, the transceiver unit is configured to receive a seventh non-access stratum message from the second network element and control the transceiver unit to transmit the first non-access stratum message to the relay device.

[0388] In a possible implementation, the transceiver unit is configured to receive a third non-access stratum message from the second network element, and to transmit the third non-access stratum message to the first terminal device via the relay device.

[0389] In a possible implementation, the transceiver unit is configured to transmit the third indication information to the relay device. The transceiver unit is configured to receive a fifth non-access stratum message from the second terminal device via the relay device.

[0390] In a possible implementation, the transceiver unit is configured to receive a fourth indication from the relay device. The transceiver unit is configured to transmit a ninth non-access stratum message to the second network element.

[0391] In a possible implementation, the apparatus is connected to a first radio access network device, the first radio access network device providing services for a relay device, and the transceiver unit is configured to transmit context information of the relay device to a second access and mobility management function network element.

[0392] In a possible design, the apparatus 100 may be a tag manager network element (e.g., a TMF) in the aforementioned method embodiments, or may be a chip configured to perform the functions of the tag manager network element in the aforementioned method embodiments. It should be understood that the apparatus 100 may correspond to the tag manager network element or RAN#1 in the method 600, the method 900, and the method 1000 according to the embodiments of the present application, and the apparatus 100 may perform steps corresponding to the tag manager network element or the TMF in the method 600, the method 900, and the method 1000 according to the embodiments of the present application.

[0393] In a possible implementation, the transceiver unit is configured to receive a tenth non-access stratum message from the application function network element. The processing unit is configured to determine, based on the identifier of the relay device, that the access and mobility management function network element serving the relay device is the fourth access and mobility management function network element. The transceiver unit is configured to send a seventh non-access stratum message to the fourth access and mobility management function network element. The transceiver unit is configured to receive a second non-access stratum message from the third access and mobility management function network element.

[0394] In a possible implementation, the processing unit is configured to determine, based on the inventory identifier, that the second non-access stratum message is a response message corresponding to the seventh non-access stratum message.

[0395] In a possible implementation, if the processing unit determines that the identifier of the first terminal device satisfies at least one of the indication information, the processing unit determines that the second non-access stratum message is a response message corresponding to the seventh non-access stratum message.

[0396] In a possible implementation, the transceiver unit is configured to transmit a third non-access stratum message to a fourth access and mobility management function network element, the third non-access stratum message carrying the second indication information, and the transceiver unit is configured to receive a fourth non-access stratum message from the third access and mobility management function network element.

[0397] In a possible implementation, the transceiver unit is configured to transmit the third indication information to a fourth access and mobility management function network element, and the transceiver unit is configured to receive a fifth non-access stratum message from the third access and mobility management function network element.

[0398] In a possible implementation, the transceiver unit is configured to receive a ninth non-access stratum message from a fourth access and mobility management function network element.

[0399] It should be further understood that the apparatus 100 herein is embodied in the form of a functional unit. The term “unit” herein may refer to an application-specific integrated circuit (ASIC), an electronic circuit, a processor (e.g., a shared processor, a dedicated processor, or a group processor) configured to execute one or more software or firmware programs, a memory, a combined logic circuit, and / or another suitable component supporting the described functionality. In an optional example, a person skilled in the art may understand that the apparatus 100 may specifically be the relay device, the first access and mobility management function network element, the fourth access and mobility management function network element, or the tag management function network element in the aforementioned embodiments, and may be configured to perform procedures and / or steps corresponding to the relay device, the first access and mobility management function network element, the fourth access and mobility management function network element, or the tag management function network element in the aforementioned method embodiments.

[0400] The apparatus 100 in the above solution has a function of performing a corresponding step performed by a relay device in the above method, or the apparatus 100 in the above solution has a function of performing a corresponding step performed by a first access and mobility management function network element, a fourth access and mobility management function network element, or a tag management function network element in the above method. This function may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above function. For example, a transceiver unit may be replaced by a transceiver (e.g., a transmitting unit in the transceiver unit may be replaced by a transmitter, and a receiving unit in the transceiver unit may be replaced by a receiver), and another unit, such as a processing unit, may be replaced by a processor to perform receiving and transmitting operations and related processing operations in the method embodiments, respectively.

[0401] Additionally, the transceiver unit 110 may alternatively be a transceiver circuit (which may include, for example, a receiving circuit and a transmitting circuit), and the processing unit may be a processing circuit.

[0402] It should be noted that the apparatus in Figure 11 may be a network element or device of the aforementioned embodiments, or may be a chip or a chip system, such as a system on chip (SoC). The transceiver unit may be an input / output circuit or a communication interface. The processing unit is a processor, a microprocessor, or an integrated circuit integrated on a chip. This is not limited herein.

[0403] 12 is a block diagram of a communication device 200 according to an embodiment of the present application. As shown in the figure, the device 200 includes at least one processor 220. The processor 220 is coupled to a memory and configured to execute instructions stored in the memory to send and / or receive signals. Optionally, the device 200 further includes a memory 230 configured to store instructions. Optionally, the device 200 further includes a transceiver 210, where the processor 220 controls the transceiver 210 to send and / or receive signals.

[0404] It should be understood that the processor 220 and the memory 230 may be combined into one processing device, and that the processor 220 is configured to perform the functions described above by executing program code stored in the memory 230. In particular implementations, the memory 230 may alternatively be integrated into the processor 220 or may be separate from the processor 220.

[0405] It should be further understood that the transceiver 210 may include a transceiver (also called a receiver) and a transmitter (also called a transmitting machine). The transceiver may further include an antenna, of which there may be one or more antennas. The transceiver 210 may be a communications interface or interface circuit.

[0406] In particular, the transceiver 210 of the device 200 may correspond to the transceiver unit 110 of the device 100, and the processor 220 of the device 200 may correspond to the processing unit 120 of the device 200.

[0407] In the solution, the apparatus 200 is configured to perform the operations performed by the relay device in the above method embodiments.

[0408] For example, the processor 220 is configured to execute computer programs or instructions stored in the memory 230 to perform relevant operations of the relay device in the method performed by the relay device of any one of the aforementioned method embodiments, e.g., the embodiments shown in Figures 5 to 10A and 10B.

[0409] In the solution, the apparatus 200 is configured to perform the operations performed by the first access and mobility management function network element (eg, AMF#1) of the above method embodiment.

[0410] For example, the processor 220 is configured to execute computer programs or instructions stored in the memory 230 to perform the relevant operations of the first access and mobility management function network element in the aforementioned method embodiments, e.g., the method performed by the first access and mobility management function network element of any one of the embodiments shown in Figures 5 to 10A and 10B.

[0411] In the solution, the apparatus 200 is configured to perform the operations performed by the fourth access and mobility management function network element (eg, AMF#4) of the above method embodiment.

[0412] For example, the processor 220 is configured to execute computer programs or instructions stored in the memory 230 to perform the relevant operations of the fourth access and mobility management function network element in the aforementioned method embodiments, e.g., the method performed by the fourth access and mobility management function network element of any one of the embodiments shown in Figures 5 to 10A and 10B.

[0413] In the solution, the apparatus 200 is configured to perform the operations performed by a tag management function network element (eg, TMF) of the above method embodiments.

[0414] For example, the processor 220 is configured to execute computer programs or instructions stored in the memory 230 to perform the relevant operations of the tag management function network element in the aforementioned method embodiments, e.g., the methods performed by the tag management function network element of any one of the embodiments shown in Figures 5 to 10A and 10B.

[0415] It should be understood that the specific operations performed by the transceiver and the processor to perform the corresponding steps have been described in detail in the method embodiments above, and for the sake of brevity, the details will not be described again here.

[0416] In the implementation process, the steps of the aforementioned method can be implemented using a hardware integrated logic circuit of a processor or using instructions in the form of software. The steps of the method disclosed with reference to the embodiments of the present application can be directly executed by a hardware processor, or can be executed by a combination of processor hardware and software modules. The software modules can be installed in a mature storage medium in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, or a register. The storage medium is installed in the memory, and the processor reads the information in the memory and completes the steps of the aforementioned method in combination with the hardware of the processor. To avoid repetition, the details will not be described again in this specification.

[0417] It should be noted that the processor in the embodiments of the present application may be an integrated circuit chip and have signal processing capabilities. In the implementation process, the steps of the above-described method embodiments may be performed using hardware integrated logic circuitry of the processor or using instructions in the form of software. The processor may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The methods, steps, and logic block diagrams disclosed in the embodiments of the present application may be implemented or performed. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor, etc. The steps of the methods disclosed with reference to the embodiments of the present application may be performed directly by a hardware decoding processor or by a combination of hardware and software modules of the decoding processor. The software module may be installed in a mature storage medium in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, or a register. The storage medium is installed in the memory, and the processor reads the information in the memory and completes the steps of the aforementioned method in combination with the hardware of the processor.

[0418] It may be understood that the memory of the embodiments of the present application may be volatile memory, non-volatile memory, or may include volatile and non-volatile memory. Non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may be random access memory (RAM) and is used as an external cache. By way of example and not limitation, many forms of RAM may be used, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus random access memory (DR RAM). It should be noted that memory in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0419] According to the method provided in the embodiment of the present application, the present application further provides a computer program product, which stores computer program code, which, when run on a computer, enables the computer to execute the method performed by the relay device in any one of the embodiments of Methods 500 to 1000.

[0420] For example, when the computer program code is executed by a computer, the computer is enabled to perform the methods performed by the first access and mobility management function network element in embodiments of method 500, method 700, and method 800.

[0421] In another example, when the computer program code is executed by a computer, the computer is enabled to perform the methods performed by the fourth access and mobility management function network element in embodiments of method 600, method 900, and method 1000.

[0422] In yet another example, the computer program code, when executed by a computer, enables the computer to perform the methods performed by the tag manager network element in embodiments of methods 500 to 1000.

[0423] According to the methods provided in the embodiments of the present application, the present application further provides a computer-readable medium, which stores program code, which, when run on a computer, enables the computer to execute the methods performed by the relay device, the first access and mobility management function network element, the fourth access and mobility management function network element, or the tag management function network element in the embodiments of Methods 500 to 1000.

[0424] According to a method provided in an embodiment of the present application, the present application further provides a communication system. The system includes a relay device, a first access and mobility management function network element, and a first radio access network device. The relay device is configured to perform steps corresponding to the relay device in the embodiments of Methods 500, 700, and 800. The first access and mobility management function network element is configured to perform steps corresponding to the first access and mobility management function network element in the embodiments of Methods 500, 700, and 800. The first radio access network device is configured to receive a first radio resource control message from the relay device, the first radio resource control message carrying a registration request message and first indication information, the first indication information indicating that the relay device supports communication with an ambient internet of things terminal device, and the registration request message is used to request registration with the access and mobility management function network element. The first radio access network device is configured to select, for the relay device, a first access and mobility management function network element that supports communication with the ambient terminal device based on the first indication information. The first radio access network device is configured to send a registration request message to the first access and mobility management function network element.

[0425] In a possible implementation, the first radio access network device is further configured to receive a first non-access stratum message from a first access and mobility management function network element, the first non-access stratum message being used to request obtaining an identifier of a terminal device, the terminal device including one or more terminal devices. The first radio access network device is configured to transmit the first non-access stratum message to a relay device. The first radio access network device is configured to receive a second non-access stratum message from the relay device, the second non-access stratum message carrying an identifier of the first terminal device, the first terminal device being a terminal device located within the coverage area of ​​the relay device that successfully performs random access. The first radio access network device is configured to determine to transmit the second non-access stratum message to the first access and mobility management function network element.

[0426] According to the method provided in the embodiment of the present application, the present application further provides another communication system. The system includes a third access and mobility management function network element, a fourth access and mobility management function network element, and a second network element. The third access and mobility management function network element and the fourth access and mobility management function network element are configured to perform steps corresponding to the third access and mobility management function network element and the fourth access and mobility management function network element in Methods 600, 900, and 100. The second network element is configured to perform steps corresponding to the tag management function network element in Methods 600, 900, and 100.

[0427] In a possible implementation, the system further includes a relay device, which is configured to perform steps corresponding to those of the relay device in methods 600, 900, and 100.

[0428] For the description of the relevant contents and beneficial effects of any one of the above-provided devices, please refer to the corresponding method embodiments provided above, and the details will not be described again in this specification.

[0429] All or part of the above-described embodiments may be implemented by software, hardware, firmware, or any combination thereof. When software is used to implement the embodiments, all or part of the embodiments may be implemented in the form of a computer program product. A computer program product includes one or more instructions. When the computer instructions are loaded into a computer and executed, the procedures or functions according to the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or another programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optics, or digital subscriber line (DSL)) or wireless (e.g., infrared, radio, or microwave) methods. The computer-readable storage medium may be any available medium accessible by a computer, or a data storage device, such as a server or a data center, that incorporates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disk drives, or magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), semiconductor media (e.g., solid state drives (SSDs)), etc.

[0430] In the above-described device embodiments, corresponding modules or units perform corresponding steps. For example, a transceiver unit (transceiver) may perform a receiving step or a transmitting step in a method embodiment, and a processing unit (processor) may perform steps other than a transmitting step and a receiving step. For the functions of specific units, please refer to the corresponding method embodiment. There may be one or more processors.

[0431] As used herein, terms such as “component,” “module,” and “system” are intended to represent computer-related entities, hardware, firmware, a combination of hardware and software, software, or software being executed. For example, a component may be, but is not limited to, a process running on a processor, a processor, an object, an executable file, a thread of execution, a program, and / or a computer. As illustrated using the figures, both computing devices and applications running on computing devices may be components. One or more components may reside within a process and / or thread of execution, and components may be located on one computer and / or distributed between two or more computers. Additionally, these components may execute from various computer-readable media that store various data structures. Components may communicate using local and / or remote processing, for example, based on signals having one or more data packets (e.g., data from two components interacting with another component in a local system, in a distributed system, and / or across a network such as the Internet that interacts with other systems using signals).

[0432] Those skilled in the art may recognize that, in combination with the examples described in the embodiments disclosed herein, the units and algorithm steps may be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether a function is performed by hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but the implementation should not be considered to go beyond the scope of the present application.

[0433] It may be clearly understood by those skilled in the art that for the sake of convenient and concise description, the detailed work processes of the aforementioned systems, devices and units may be referred to the corresponding processes of the aforementioned method embodiments, and the details will not be described again in this specification.

[0434] In some embodiments provided herein, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the described device embodiments are merely examples. For example, the division into units is merely a logical division of function, and other divisions may be used in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be omitted or not implemented. In addition, the shown or discussed mutual couplings or direct couplings or communication connections may be implemented via some interfaces. Indirect couplings or communication connections between devices or units may be implemented in an electrical, mechanical, or other manner.

[0435] The units described as separate parts may or may not be physically separated, and the parts shown as units may or may not be physical units, i.e., they may be located in one location or distributed across multiple network units. Some or all of the units may be selected based on the actual needs to achieve the objectives of the solutions of the embodiments.

[0436] In addition, the functional units of the embodiments of the present application may be integrated into one processing unit, each of the units may exist physically alone, or two or more units may be integrated into one unit.

[0437] When a function is implemented in the form of a software functional unit and sold or used as an independent product, the function may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or a portion contributing to the prior art, or a portion of the technical solution, may be implemented in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for instructing a computer device (which may be a personal computer, a server, a network device, etc.) to execute all or part of the steps of the method described in the embodiments of the present application. The aforementioned storage medium includes any medium capable of storing program code, such as a USB flash drive, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0438] The above description is merely a specific implementation of the present application and is not intended to limit the scope of protection of the present application. Any modifications or replacements that can be easily conceived by those skilled in the art within the technical scope disclosed in the present application shall fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be determined by the scope of protection of the claims.

Claims

1. 1. A communication method comprising: receiving, by a relay device, a first non-access stratum message from a first access and mobility management function network element via a first radio access network device, the first non-access stratum message being used to request obtaining an identifier of a terminal device, the terminal device comprising one or more terminal devices; transmitting, by the relay device, radio frequency information to a terminal device within a coverage area of ​​the relay device based on the first non-access stratum message, the radio frequency information being used to provide an excitation signal for the terminal device; receiving, by the relay device, a second non-access stratum message from a first terminal device, the second non-access stratum message carrying an identifier of the first terminal device, the first terminal device being a terminal device located within the coverage area of ​​the relay device that successfully performs random access; transmitting, by the relay device, the second non-access stratum message to the first access and mobility management function network element via the first radio access network device; A communication method comprising:

2. The method further comprises: sending, by the relay device, a first radio resource control message to the first radio access network device, the first radio resource control message carrying a registration request message and first indication information, the first indication information indicating that the relay device supports communication with an ambient internet of things terminal device, the registration request message being used to request registration with an access and mobility management function network element; 2. The communication method according to claim 1, wherein the first access and mobility management function network element is an access and mobility management function network element selected by the first radio access network device for the relay device based on the first indication information and supporting communication with the ambient internet of things terminal device.

3. receiving, by the relay device, a third non-access stratum message from the first access and mobility management function network element via the first radio access network device, the third non-access stratum message carrying second indication information, the second indication information indicating to perform a target operation at the first terminal device; transmitting, by the relay device, the third non-access stratum message to the first terminal device; receiving, by the relay device, a fourth non-access stratum message from the first terminal device, the fourth non-access stratum message carrying information about an execution result corresponding to the target operation performed at the first terminal device; transmitting, by the relay device, the fourth non-access stratum message to the first access and mobility management function network element via the first radio access network device; The communication method according to claim 1 or 2, further comprising:

4. receiving, by the relay device, third indication information from the first access and mobility management function network element via the first radio access network device, wherein the third indication information comprises: indicating at least one of: indicating that the target operation is completed at the first terminal device; indicating to inquire about an identifier of a next terminal device; or indicating to the terminal device to perform a next random access procedure; receiving, by the relay device, a fifth non-access stratum message from a second terminal device, the fifth non-access stratum message carrying an identifier of the second terminal device; sending, by the relay device, the fifth non-access stratum message to the first access and mobility management function network element via the first radio access network device; The communication method according to claim 1 , further comprising:

5. performing, by the relay device, a handover from the first radio access network device to a second radio access network device; sending, by the relay device, a second radio resource control message to the second radio access network device, the second radio resource control message carrying the registration request message and the first indication information, the first indication information indicating that the relay device supports the communication with the ambient internet of things terminal device, and the registration request message being used to request registration with the access and mobility management function network element; receiving, by the relay device, a registration accept message from a second access and mobility management function network element, the second access and mobility management function network element being an access and mobility management function network element selected for the relay device by the second radio access network device based on the first indication information after the relay device is handed over from the first radio access network device to the second radio access network device, and supporting communication with the ambient internet of things terminal device; The communication method according to claim 1 , further comprising:

6. 1. A communication method comprising: receiving, by a first access and mobility management function network element, a seventh non-access stratum message from a first network element, the seventh non-access stratum message being used to request obtaining an identifier of a terminal device, the seventh non-access stratum message carrying an identifier of a relay device, the terminal device comprising one or more terminal devices; sending, by the first access and mobility management function network element, a first non-access stratum message to the relay device based on the identifier of the relay device, the first non-access stratum message being used to request obtaining the identifier of the terminal device; receiving, by the first access and mobility management function network element, a second non-access stratum message from a first terminal device via the relay device, the second non-access stratum message carrying an identifier of the first terminal device, the first terminal device being a terminal device located within a coverage area of ​​the relay device that successfully performs random access; sending, by the first access and mobility management function network element, an eighth non-access stratum message to the first network element, the eighth non-access stratum message carrying the identifier of the first terminal device; A communication method comprising:

7. receiving, by the first access and mobility management function network element, a second non-access stratum message from a first terminal device via the relay device; 2. The communication method of claim 1, comprising receiving, by the first access and mobility management function network element, the second non-access stratum message from the first terminal device via the relay device and a first radio access network device, wherein the first access and mobility management function network element is an access and mobility management function network element selected by the first radio access network device for the relay device and supporting communication with an ambient internet of things terminal device.

8. The seventh non-access stratum message further carries second indication information, and the second indication information indicates to perform a target action in the first terminal device, and the communication method includes: sending, by the first access and mobility management function network element, a third non-access stratum message to the relay device, the third non-access stratum message carrying the second indication information; receiving, by the first access and mobility management function network element, a fourth non-access stratum message from the relay device, the fourth non-access stratum message carrying information regarding an execution result corresponding to the target operation performed at the first terminal device; The communication method according to claim 6 or 7, further comprising:

9. sending, by the first access and mobility management function network element, third indication information to the relay device, the third indication information indicating at least one of the following: indicating that the target operation has been completed at the first terminal device; indicating to inquire about an identifier of a next terminal device; or indicating to perform a next random access procedure for the terminal device; receiving, by the first access and mobility management function network element, a fifth non-access stratum message from a second terminal device via the relay device, the fifth non-access stratum message carrying an identifier of the second terminal device; The communication method according to any one of claims 6 to 8, further comprising:

10. receiving, by the first access and mobility management function network element, fourth indication information from the relay device, the fourth indication information indicating that a target operation has been completed at the terminal device; The communication method according to claim 6 , wherein the eighth non-access stratum message further carries information about an execution result corresponding to the target action performed at the terminal device.

11. transmitting, by the first access and mobility management function network element, context information of the relay device to a second access and mobility management function network element, wherein the context information comprises the seventh non-access stratum message; 11. The communication method according to claim 6, wherein the second access and mobility management function network element is an access and mobility management function network element selected for the relay device by the second radio access network device after the relay device is handed over from the first radio access network device to the second radio access network device, and supports communication with the ambient internet of things terminal device.

12. The communication method according to any one of claims 6 to 11, wherein the first network element is a network public function network element, or the first network element is an application function network element.

13. 1. A method of a communication system, comprising: receiving, by a fourth access and mobility management function network element, a seventh non-access stratum message from the second network element, the seventh non-access stratum message being used to request obtaining an identifier of a terminal device, the seventh non-access stratum message carrying an identifier of a relay device, the terminal device comprising one or more terminal devices; sending, by the fourth access and mobility management function network element, a first non-access stratum message to the relay device based on the identifier of the relay device, the first non-access stratum message being used to request obtaining the identifier of the terminal device; receiving, by a third access and mobility management function network element, a second non-access stratum message from a first terminal device via the relay device, the second non-access stratum message carrying an identifier of the first terminal device, the first terminal device being a terminal device located within a coverage area of ​​the relay device that successfully performs random access; sending, by the third access and mobility management function network element, the second non-access stratum message to the second network element; A method for providing

14. The method of claim 13 , wherein the fourth access and mobility management function network element is an access and mobility management function network element that supports communication with the relay device.

15. 15. The method of claim 13 or 14, wherein if the seventh non-access stratum message carries an inventory identifier, the first non-access stratum message carries the inventory identifier, and the second non-access stratum message carries the inventory identifier, and the inventory identifier is used by the second network element to determine that the second non-access stratum message is a response message corresponding to the seventh non-access stratum message.

16. The seventh non-access stratum message further carries second indication information, the second indication information indicating to perform a target operation at the first terminal device, and the method includes: receiving, by the fourth access and mobility management function network element, a third non-access stratum message from the second network element, the third non-access stratum message carrying the second indication information; sending, by the fourth access and mobility management function network element, the third non-access stratum message to the first terminal device via the relay device, wherein the third non-access stratum message carries the second indication information; receiving, by the third access and mobility management function network element, a fourth non-access stratum message from the first terminal device via the relay device, the fourth non-access stratum message carrying information regarding an execution result corresponding to the target operation performed at the first terminal device; sending, by the third access and mobility management function network element, the fourth non-access stratum message to the second network element; 16. The method of any one of claims 13 to 15, further comprising:

17. sending, by the fourth access and mobility management function network element, third indication information to the relay device, the third indication information indicating at least one of the following: indicating that the target operation has been completed at the first terminal device; indicating to inquire about an identifier of a next terminal device; or indicating to perform a next random access procedure for the terminal device; receiving, by the fourth access and mobility management function network element via the relay device, a fifth non-access stratum message from a second terminal device, the fifth non-access stratum message carrying an identifier of the second terminal device; 17. The method of any one of claims 13 to 16, further comprising:

18. receiving, by the fourth access and mobility management function network element, fourth indication information from the relay device, the fourth indication information indicating that a target operation has been completed at the terminal device; sending, by the fourth access and mobility management function network element, a ninth non-access stratum message to the second network element, the ninth non-access stratum message comprising information about an execution result corresponding to the target operation performed at the terminal device; 18. The method of any one of claims 13 to 17, further comprising:

19. The fourth access and mobility management function network element is connected to a first radio access network device, and the first radio access network device provides a service for the relay device, and the method includes: sending, by the fourth access and mobility management function network element, context information of the relay device to a second access and mobility management function network element, the context information comprising the seventh non-access stratum message, the second access and mobility management function network element being a target access and mobility management function network element selected for the relay device by the second radio access network device after the relay device is handed over from the first radio access network device to the second radio access network device; receiving, by the second access and mobility management function network element, a sixth non-access stratum message from the relay device, the sixth non-access stratum message carrying an identifier of a third terminal device and the inventory identifier, the inventory identifier being used by the second network element to determine that the second non-access stratum message is the response message corresponding to a seventh non-access stratum message; 19. The method of any one of claims 13 to 18, further comprising:

20. 1. A communication method comprising: receiving, by a second network element, a tenth non-access stratum message from an application function network element, the tenth non-access stratum message being used to request obtaining an identifier of a terminal device, the tenth non-access stratum message carrying an identifier of a relay device, the terminal device comprising one or more target terminal devices; determining, by the second network element, based on the identifier of the relay device, that an access and mobility management function network element serving the relay device is a fourth access and mobility management function network element; sending, by the second network element, a seventh non-access stratum message to the fourth access and mobility management function network element, the seventh non-access stratum message being used to request obtaining the identifier of the terminal device; receiving, by the second network element, a second non-access stratum message from a third access and mobility management function network element, the second non-access stratum message carrying an identifier of a first terminal device, the first terminal device being a terminal device within a coverage area of ​​the relay device that successfully performs random access; A communication method comprising:

21. The communication method of claim 20, wherein the fourth access and mobility management function network element is an access and mobility management function network element that supports communication with the relay device.

22. When the seventh non-access stratum message carries an inventory identifier and the second non-access stratum message carries the inventory identifier, the communication method includes:

22. The communication method of claim 20, further comprising determining, by the second network element based on the inventory identifier, that the second non-access stratum message is a response message corresponding to the seventh non-access stratum message.

23. The tenth non-access stratum message further carries inventory indication information, the inventory indication information comprising at least one of the following contents: a value interval of the identifier of the terminal device, an identifier list of the terminal device, an identifier of a group of the terminal devices, or information indicating an inquiry regarding an identifier of any terminal device; The communication method includes:

23. The communication method according to claim 20, further comprising: determining, by the second network element, if the second network element determines that the identifier of the first terminal device satisfies at least one of the indication information, that the second non-access stratum message is the response message corresponding to the seventh non-access stratum message.

24. the tenth non-access stratum message further carries second indication information, the second indication information indicating to perform a target action in the first terminal device, and the communication method includes: sending, by the second network element, a third non-access stratum message to the fourth access and mobility management function network element, the third non-access stratum message carrying the second indication information; receiving, by the second network element, a fourth non-access stratum message from the third access and mobility management function network element, the fourth non-access stratum message carrying information about an execution result corresponding to the target operation of the first terminal device, the fourth non-access stratum message being sent by the first terminal device to the third access and mobility management function network element via the relay device; 24. The communication method of claim 20, further comprising:

25. sending third indication information by the second network element to the fourth access and mobility management function network element, wherein the third indication information comprises: indicating at least one of: indicating that the target operation is completed at the first terminal device; indicating to query for an identifier of a next terminal device; or indicating to the terminal device to perform a next random access procedure; receiving, by the second network element, a fifth non-access stratum message from the third access and mobility management function network element, the fifth non-access stratum message carrying an identifier of a second terminal device, the fifth non-access stratum message being sent by the second terminal device to the third access and mobility management function network element via the relay device; 25. The communication method of any one of claims 20 to 24, further comprising:

26. 26. The communication method according to claim 20, further comprising receiving, by the second network element, a ninth non-access stratum message from the fourth access and mobility management function network element, wherein the ninth non-access stratum message comprises information about an execution result corresponding to the target operation performed in the terminal.

27. 27. The method of any one of claims 20 to 26, wherein the second network element is a tag management network element.

28. A communication device comprising a transceiver unit and a processing unit, The transceiver unit is configured to receive a first non-access stratum message from a first access and mobility management function network element via a first radio access network device, the first non-access stratum message being used to request obtaining an identifier of a terminal device, the terminal device comprising one or more terminal devices; the processing unit is configured to control the transceiver unit to transmit radio frequency information to a terminal device within a coverage area of ​​the communication apparatus based on the first non-access stratum message, the radio frequency information being used to provide an excitation signal for the terminal device; The transceiver unit is configured to receive a second non-access stratum message from a first terminal device, the second non-access stratum message carrying an identifier of the first terminal device, the first terminal device being a terminal device located within the coverage area of ​​the relay device that successfully performs random access; The communications apparatus, wherein the transceiver unit is configured to transmit the second non-access stratum message to the first access and mobility management function network element via the first radio access network device.

29. The transceiver unit is configured to send a first radio resource control message to the first radio access network device, the first radio resource control message carrying a registration request message and first indication information, the first indication information indicating that the relay device supports communication with an ambient internet of things terminal device, the registration request message being used to request registration with an access and mobility management function network element; 29. The communications apparatus of claim 28, wherein the first access and mobility management function network element is an access and mobility management function network element selected by the first radio access network device for the relay device based on the first indication information and supporting communication with the ambient internet of things terminal device.

30. the transceiver unit is configured to receive, via the first radio access network device, from the first access and mobility management function network element, a third non-access stratum message, the third non-access stratum message carrying second indication information, the second indication information indicating to perform a target operation at the first terminal device; the transceiver unit is configured to transmit the third non-access stratum message to the first terminal device; the transceiver unit is configured to receive a fourth non-access stratum message from the first terminal device, the fourth non-access stratum message carrying information regarding an execution result corresponding to the target operation performed at the first terminal device; 30. The communications apparatus of claim 28 or 29, wherein the transceiver unit is configured to transmit the fourth non-access stratum message to the first access and mobility management function network element via the first radio access network device.

31. The transceiver unit is configured to receive third indication information from the first access and mobility management function network element via the first radio access network device, and the third indication information comprises the following content: indicating at least one of: indicating that the target operation is completed at the first terminal device; indicating to inquire about an identifier of a next terminal device; or indicating to the terminal device to perform a next random access procedure; the transceiver unit is configured to receive a fifth non-access stratum message from a second terminal device, the fifth non-access stratum message carrying an identifier of the second terminal device; 31. The communications apparatus of claim 28, wherein the transceiver unit is configured to transmit the fifth non-access stratum message to the first access and mobility management function network element via the first radio access network device.

32. the communication device is handed over from the first radio access network device to a second radio access network device; the transceiver unit is configured to send a second radio resource control message to the second radio access network device, the second radio resource control message carrying the registration request message and the first indication information, the first indication information indicating that the relay device supports the communication with the ambient internet of things terminal device, the registration request message being used to request registration with the access and mobility management function network element; 32. The communication apparatus according to claim 28, wherein the transceiver unit is configured to receive a registration accept message from a second access and mobility management function network element, the second access and mobility management function network element being an access and mobility management function network element selected for the relay device by the second radio access network device based on the first indication information after the relay device is handed over from the first radio access network device to the second radio access network device, and supporting communication with the ambient internet of things terminal device.

33. A communication device comprising a transceiver unit and a processing unit, the transceiver unit is configured to receive a seventh non-access stratum message from a first network element, the seventh non-access stratum message being used to request obtaining an identifier of a terminal device, the seventh non-access stratum message carrying an identifier of a relay device, the terminal device comprising one or more terminal devices; The processing unit is configured to control the transceiver unit to send a first non-access stratum message to the relay device based on the identifier of the relay device, the first non-access stratum message being used to request obtaining the identifier of the terminal device; and The transceiver unit is configured to receive a second non-access stratum message from a first terminal device via the relay device, the second non-access stratum message carrying an identifier of the first terminal device, the first terminal device being a terminal device located within a coverage area of ​​the relay device that successfully performs random access; The communications apparatus, wherein the transceiver unit is configured to transmit an eighth non-access stratum message to the first network element, the eighth non-access stratum message carrying the identifier of the first terminal device.

34. The transceiver unit is configured to receive a second non-access stratum message from a first terminal device via the relay device, 34. The communications apparatus of claim 33, further comprising: the transceiver unit configured to receive the second non-access stratum message from the first terminal device via the relay device and a first radio access network device, wherein a first access and mobility management function network element is an access and mobility management function network element selected by the first radio access network device for the relay device and supporting communication with an ambient internet of things terminal device.

35. the seventh non-access stratum message further carries second indication information, the second indication information indicating to perform a target action at the first terminal device; and the transceiver unit is configured to send a third non-access stratum message to the relay device, the third non-access stratum message carrying the second indication information; 35. The communication apparatus of claim 33 or 34, wherein the transceiver unit is configured to receive a fourth non-access stratum message from the relay device, the fourth non-access stratum message carrying information regarding an execution result corresponding to the target operation performed at the first terminal device.

36. the transceiver unit is configured to send third indication information to the relay device, the third indication information indicating at least one of the following: indicating that the target operation has been completed at the first terminal device; indicating to inquire about an identifier of a next terminal device; or indicating to perform a next random access procedure for the terminal device; 36. The communications apparatus of claim 33, wherein the transceiver unit is configured to receive a fifth non-access stratum message from a second terminal device via the relay device, the fifth non-access stratum message carrying an identifier of the second terminal device.

37. 37. The communication apparatus of claim 33, wherein the transceiver unit is configured to receive fourth indication information from the relay device, the fourth indication information indicating that a target operation has been completed at the terminal device.

38. the transceiver unit is configured to transmit context information of the relay device to a second access and mobility management function network element, the context information comprising the seventh non-access stratum message; 38. The communication device according to claim 33, wherein the second access and mobility management function network element is an access and mobility management function network element selected for the relay device by the second radio access network device after the relay device is handed over from the first radio access network device to the second radio access network device, and which supports communication with the ambient internet of things terminal device.

39. 39. The communication device of claim 33, wherein the first network element is a network publication function network element, or the first network element is an application function network element.

40. A communication device comprising a transceiver unit and a processing unit, the transceiver unit is configured to receive a seventh non-access stratum message from a second network element, the seventh non-access stratum message being used to request obtaining an identifier of a terminal device, the seventh non-access stratum message carrying an identifier of a relay device, the terminal device comprising one or more terminal devices; The processing unit is configured to control the transceiver unit to transmit a first non-access stratum message to the relay device based on the identifier of the relay device, the first non-access stratum message being used to request obtaining the identifier of the terminal device.

41. 41. The communications apparatus of claim 40, wherein the communications apparatus is an access and mobility management function network element that supports communications with the relay device.

42. 42. The communications device of claim 40 or 41, wherein if the seventh non-access stratum message carries an inventory identifier, the first non-access stratum message carries the inventory identifier and the second non-access stratum message carries the inventory identifier, and the inventory identifier is used by the second network element to determine that the second non-access stratum message is a response message corresponding to the seventh non-access stratum message.

43. the seventh non-access stratum message further carries second indication information, the second indication information indicating to perform a target operation at the first terminal device; and the transceiver unit is configured to receive a third non-access stratum message from the second network element, the third non-access stratum message carrying the second indication information; 43. The communications apparatus of claim 40, wherein the transceiver unit is configured to transmit the third non-access stratum message to the first terminal device via the relay device, the third non-access stratum message carrying the second indication information.

44. the transceiver unit is configured to send third indication information to the relay device, the third indication information indicating at least one of the following: indicating that the target operation has been completed at the first terminal device; indicating to make an inquiry for an identifier of a next terminal device; or indicating to perform a next random access procedure for the terminal device; 43. The communications apparatus of claim 40, wherein the transceiver unit is configured to receive a fifth non-access stratum message from a second terminal device via the relay device, the fifth non-access stratum message carrying an identifier of the second terminal device.

45. the transceiver unit is configured to receive fourth indication information from the relay device, the fourth indication information indicating that a target operation has been completed at the terminal device; 45. The communications apparatus of claim 40, wherein the transceiver unit is configured to transmit a ninth non-access stratum message to the second network element, the ninth non-access stratum message comprising information about an execution result corresponding to the target action performed at the terminal device.

46. the communication device is connected to a first radio access network device, the first radio access network device providing a service for the relay device; 46. ​​The communications apparatus of claim 40, wherein the transceiver unit is configured to transmit context information of the relay device to a second access and mobility management function network element, the context information comprising the seventh non-access stratum message, the second access and mobility management function network element being an access and mobility management function network element selected for the relay device by the second radio access network device after the relay device is handed over from the first radio access network device to the second radio access network device and supporting communication with an ambient terminal device.

47. A communication device comprising a transceiver unit and a processing unit, The transceiver unit is configured to receive a tenth non-access stratum message from an application function network element, the tenth non-access stratum message being used to request obtaining an identifier of a terminal device, the tenth non-access stratum message carrying an identifier of a relay device, and the terminal device comprising one or more target terminal devices; The processing unit is configured to determine, based on the identifier of the relay device, that an access and mobility management function network element serving the relay device is a fourth access and mobility management function network element; the transceiver unit is configured to send a seventh non-access stratum message to the fourth access and mobility management function network element, the seventh non-access stratum message being used to request obtaining the identifier of the terminal device; The transceiver unit is configured to receive a second non-access stratum message from a third access and mobility management function network element, the second non-access stratum message carrying an identifier of a first terminal device, the first terminal device being a terminal device located within a coverage area of ​​the relay device that successfully performs random access.

48. 48. The communications apparatus of claim 47, wherein the fourth access and mobility management function network element is an access and mobility management function network element that supports communications with the relay device.

49. If the seventh non-access stratum message carries an inventory identifier and the second non-access stratum message carries the inventory identifier, 49. The communications device of claim 47 or 48, wherein the processing unit is configured to determine, based on the inventory identifier, that the second non-access stratum message is a response message corresponding to the seventh non-access stratum message.

50. The tenth non-access stratum message further carries inventory indication information, the inventory indication information comprising at least one of the following contents: a value interval of the identifier of the terminal device, an identifier list of the terminal device, an identifier of a group of the terminal devices, or information indicating an inquiry regarding an identifier of any terminal device; 50. The communication device of claim 47, wherein if the processing unit determines that the identifier of the first terminal device satisfies at least one of the indication information, the processing unit determines that the second non-access stratum message is the response message corresponding to the seventh non-access stratum message.

51. the tenth non-access stratum message further carries second indication information, the second indication information indicating to perform a target operation at the first terminal device; the transceiver unit is configured to send a third non-access stratum message to the fourth access and mobility management function network element, the third non-access stratum message carrying the second indication information; 51. The communications apparatus of claim 47, wherein the transceiver unit is configured to receive a fourth non-access stratum message from the third access and mobility management function network element, the fourth non-access stratum message carrying information about an execution result corresponding to the target operation of the first terminal device, and the fourth non-access stratum message is transmitted by the first terminal device to the third access and mobility management function network element via the relay device.

52. The transceiver unit is configured to send third indication information to the fourth access and mobility management function network element, and the third indication information comprises the following content: indicating at least one of: indicating that the target operation is completed at the first terminal device; indicating to query for an identifier of a next terminal device; or indicating to the terminal device to perform a next random access procedure; 52. The communications apparatus of claim 47, wherein the transceiver unit is configured to receive a fifth non-access stratum message from the third access and mobility management function network element, the fifth non-access stratum message carrying an identifier of a second terminal device, and the fifth non-access stratum message is sent by the second terminal device to the third access and mobility management function network element via the relay device.

53. 53. The communications device of claim 47, wherein the transceiver unit is configured to receive a ninth non-access stratum message from the fourth access and mobility management function network element, the ninth non-access stratum message comprising information regarding an execution result corresponding to the target operation performed at the terminal.

54. 54. A communications device according to any one of claims 47 to 53, which is a Tag Manager Network Element.

55. A communication system comprising: a relay device; a first access and mobility management function network element; and a first radio access network device; The relay device is configured to perform the communication method according to any one of claims 1 to 5, The first access and mobility management function network element is configured to perform the communication method according to any one of claims 6 to 12, wherein the first radio access network device is configured to receive a first radio resource control message from the relay device, the first radio resource control message carrying a registration request message and first indication information, the first indication information indicating that the relay device supports communication with an ambient internet of things terminal device, and the registration request message is used to request registration to the access and mobility management function network element; The first radio access network device is configured to select, for the relay device, the first access and mobility management function network element that supports communication with the ambient terminal device based on the first indication information; A communication system, wherein the first radio access network device is configured to send the registration request message to the first access and mobility management function network element.

56. The first radio access network device is further configured to receive a first non-access stratum message from the first access and mobility management function network element, the first non-access stratum message being used to request obtaining an identifier of a terminal device, the terminal device comprising one or more terminal devices; the first radio access network device is configured to send the first non-access stratum message to the relay device; The first radio access network device is configured to receive a second non-access stratum message from the relay device, the second non-access stratum message carrying an identifier of a first terminal device, the first terminal device being a terminal device located within a coverage area of ​​the relay device that successfully performs random access; 56. The communications system of claim 55, wherein the first radio access network device is configured to determine to transmit the second non-access stratum message to the first access and mobility management function network element.

57. A communication system comprising: a third access and mobility management function network element; a fourth access and mobility management function network element; and a second network element; The third access and mobility management function network element and the fourth access and mobility management function network element are configured to perform the method according to any one of claims 13 to 19, wherein the method is performed by the third access and mobility management function network element and the fourth access and mobility management function network element; 28. A communication system, wherein the second network element is configured to perform the communication method of any one of claims 20 to 27.

58. 28. A communications device comprising a processor and an interface circuit, the interface circuit being configured to receive a signal from another communications device other than the communications device and to transmit the signal to the processor or to transmit a signal from the processor to another communications device other than the communications device, wherein by means of logic circuits or by executing code instructions the processor is configured to implement the communications method of any one of claims 1 to 5, the communications method of any one of claims 6 to 12, the method of any one of claims 13 to 19 executed by the fourth access and mobility management function network element, or the communications method of any one of claims 20 to 27.

59. 28. A communications device comprising a processor, the processor coupled to a memory, the memory configured to store instructions that, when executed by the processor, enable the communications device to perform the communications method of any one of claims 1 to 5; configured to implement the communications method of any one of claims 6 to 12; configured to implement the method of any one of claims 13 to 19 executed by the fourth access and mobility management function network element; or configured to implement the communications method of any one of claims 20 to 27.

60. 28. A computer-readable storage medium storing instructions that, when executed by a communications device, cause the communications method of any one of claims 1 to 5 to be performed, the communications method of any one of claims 6 to 12 to be performed, the method of any one of claims 13 to 19 performed by the fourth access and mobility management function network element to be performed, or the communications method of any one of claims 20 to 27 to be performed.

61. 28. A computer program product, when said computer program product runs on a computer, enabling said computer to execute the communication method of any one of claims 1 to 5, configured to implement the communication method of any one of claims 6 to 12, configured to implement the method of any one of claims 13 to 19 executed by the fourth access and mobility management function network element, or configured to implement the communication method of any one of claims 20 to 27.

Images