Communication method and apparatus

Abstract

The present application relates to the field of communications. Provided are a communication method and apparatus, which are used for allowing an RAN and an AMF to forward a service request of a terminal device to an appropriate TMF when the AMF and the TMF are separately deployed and a temporary identifier is allocated to the terminal device by the TMF. In the method, after receiving a first identifier and a service request message from a terminal device, an access network device can determine an appropriate first access and mobility management network element on the basis of the first identifier and identifier association information, such that the access network device can forward the service request message and the first identifier to the first access and mobility management network element by means of a first message; and the first access and mobility management network element can determine a first tag management network element on the basis of the first identifier. In this way, when a temporary identifier is allocated to the terminal device by the first tag management network element, the access network device and the first access and mobility management network element can send the service request message of the terminal device to the appropriate first tag management network element.

Description

Communication methods and devices

[0001] This application claims priority to Chinese Patent Application No. 202411014609.4, filed on July 25, 2024, entitled "Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

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

[0003] Currently, access and mobility management network elements, such as the access and mobility management function (AMF), can be used for access and mobility management of terminal devices. For example, the AMF can assign a temporary identifier to a terminal device, which can include an AMF identifier and a terminal device identifier. The radio access network (RAN) device can select the appropriate AMF to forward the service request based on the AMF identifier sent by the terminal device. Ambient Internet of Things (A-IoT) devices differ significantly from existing terminal devices in form and function. New network elements, such as the tag management function (TMF), are needed to provide access and mobility management for these A-IoT devices.

[0004] However, after the introduction of TMF, how to forward the service requests of terminal devices to the appropriate TMF is an urgent problem to be solved. Summary of the Invention

[0005] This application provides a communication method and apparatus for forwarding service requests from a terminal device to a suitable TMF when the AMF and TMF are deployed separately and the TMF assigns a temporary identifier to the terminal device.

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

[0007] Firstly, a communication method is provided. This method can be executed by an access network device, by a module (e.g., processor, chip, or chip system) applied to the access network device, or by a logical node, logical module, or software capable of implementing all or part of the functions of the access network device. For ease of description, the following description uses the execution of the method by an access network device as an example. The method includes: the access network device receiving a first identifier and a service request message from a terminal device, and determining a first access and mobility management network element based on the first identifier and identifier association information. The access network device sends a first message to the first access and mobility management network element. The first identifier is used to identify the first tag management network element, the service request message is used to request communication services from the first tag management network element; the identifier association information includes the association relationship between the first access and mobility management network element and the tag management network element, and the tag management network element includes the first tag management network element; the first message includes the service request message and the first identifier.

[0008] As described in the first aspect, after receiving a first identifier (a temporary identifier assigned to the terminal device by the first tag management network element, including the first identifier) ​​and a service request message from the terminal device, the access network device determines a suitable first access and mobility management network element based on the first identifier and identifier association information including the association relationship between the first access and mobility management network element and the tag management network element (including the first tag management network element). This allows the access network device to forward the service request message and the first identifier to the first access and mobility management network element via a first message. Subsequently, the first access and mobility management network element can determine the first tag management network element based on the first identifier, thereby forwarding the service request message to the suitable first tag management network element. In this way, when the first tag management network element assigns a temporary identifier to the terminal device, the access network device and the first access and mobility management network element can send the terminal device's service request message to the suitable first tag management network element to meet the terminal device's needs.

[0009] In one possible design, the terminal device is an IoT device. Before the access network device receives the first identifier and service request message from the terminal device, the first aspect of the method further includes: the access network device sending its capability information to a first access and mobility management network element (MLM element), and receiving identifier association information returned by the MLM element based on the access network device's capability information. The access network device's capability information is used to indicate that the access network device supports the access of IoT devices. That is, the first MLM element only sends the identifier association information to the access network device if it supports IoT device access; otherwise, it does not need to send the identifier association information. This allows for on-demand reporting, providing flexibility and saving resources.

[0010] In one possible design scheme, the method of the first aspect further includes: the access network device assigning a second identifier. The second identifier is used to identify the terminal device, and the first message also includes the second identifier. Optionally, the method of the first aspect further includes: the access network device receiving a response message of the first message from the first access and mobility management network element, and sending a response message of the service request message to the terminal device according to the second identifier. The response message of the first message includes the response message of the service request message and the second identifier. That is, when the access network device sends a response message of the service request message to the terminal device, it can directly use the second identifier in the response message of the first message to quickly and accurately determine the terminal device, so as to send the response message of the service request message to the terminal device.

[0011] Secondly, a communication method is provided. This method can be executed by an access network device, by a module (e.g., processor, chip, or chip system) applied to the access network device, or by a logical node, logical module, or software capable of implementing all or part of the functions of the access network device. For ease of description, the following description uses the execution of the method by an access network device as an example. The method includes: the access network device receiving a first identifier and a service request message from a terminal device, and determining a first access and mobility management network element based on the first identifier. The access network device sends a first message to the first access and mobility management network element. The first identifier is used to identify the first tag management network element, and the service request message is used to request communication services from the first tag management network element; the first identifier is also used to identify the first access and mobility management network element; the first message includes the service request message and the first identifier.

[0012] Based on the method described in the second aspect, after the access network device receives a first identifier (the first identifier is included in the temporary identifier assigned to the terminal device by the first tag management network element) and a service request message from the terminal device, the first identifier can identify either the first access and mobility management network element or the first tag management network element. The access network device can directly determine the first access and mobility management network element based on the first identifier. This allows the access network device to forward the service request message and the first identifier to the first access and mobility management network element via a first message. Subsequently, the first access and mobility management network element can determine the first tag management network element based on the first identifier, thereby forwarding the terminal device's service request message to the appropriate first tag management network element. In this way, when the first tag management network element assigns a temporary identifier to the terminal device, the access network device and the first access and mobility management network element can send the terminal device's service request message to the appropriate first tag management network element to meet the terminal device's needs.

[0013] In one possible design, the second aspect of the method further includes: the access network device assigning a second identifier. The second identifier is used to identify the terminal device, and the first message also includes the second identifier. Optionally, the first aspect of the method further includes: the access network device receiving a response message to the first message from the first access and mobility management network element, and sending a response message to the terminal device for a service request message based on the second identifier. The response message to the first message includes the response message to the service request message and the second identifier.

[0014] Furthermore, other technical effects of the method described in the second aspect can be referred to the technical effects of the method described in the first aspect, and will not be repeated here.

[0015] Thirdly, a communication method is provided. This method can be executed by a first access and mobility management network element, by a module (e.g., processor, chip, or chip system) applied to the first access and mobility management network element, or by a logical node, logical module, or software capable of implementing all or part of the functions of the first access and mobility management network element. For ease of description, the following description assumes that the method is executed by the first access and mobility management network element. The method includes: the first access and mobility management network element receiving a first message from an access network device, and sending a second message to a first tag management network element based on a first identifier. The first message includes a first identifier and a service request message; the first identifier identifies the first tag management network element, and the service request message requests communication services from the first tag management network element; the second message includes the service request message.

[0016] In one possible design, before the first access and mobility management network element receives the first message from the access network device, the method described in the third aspect may further include: the first access and mobility management network element receiving capability information of the access network device sent by the access network device, and sending identification association information to the access network device. The capability information of the access network device is used to indicate that the access network device supports the access of IoT devices; the identification association information includes the association relationship between the first access and mobility management network element and the tag management network element, and the tag management network element includes the first tag management network element.

[0017] In one possible design, the first identifier is further used to identify the first access and mobility management network element; before the first access and mobility management network element receives the first message from the access network device, the method described in the third aspect further includes: the first access and mobility management network element sending a fourth identifier to the first tag management network element. The fourth identifier is used to identify the first access and mobility management network element. Optionally, the fourth identifier is also used by the first tag management network element when allocating a temporary identifier for the terminal device, and the temporary identifier includes the first identifier. That is, the first tag management network element can use the fourth identifier allocated by the first access and mobility management network element to allocate a temporary identifier for the terminal device, and the temporary identifier may include the first identifier, thus enabling the first identifier to identify both the first access and mobility management network element and the first tag management network element.

[0018] In one possible design, the first message further includes a second identifier, which is assigned to the access network device and used to identify the terminal device. Optionally, the second message further includes a second identifier and a third identifier. The third identifier is used to identify the access network device. Optionally, the method described in the third aspect further includes: a first access and mobility management network element receiving a response message of the second message from a first tag management network element, and sending a response message of the first message to the access network device according to the third identifier. The response message of the second message includes a response message of the service request message, the second identifier, and the third identifier; the response message of the first message includes a response message of the service request message and the second identifier. That is, when the first tag management network element sends a response message of the service request message to the first access and mobility management network element, it can directly use the third identifier in the response message of the second message to quickly and accurately determine the terminal device, and then send the response message of the service request message to the terminal device. In this way, the first access and mobility management network element can achieve stateless forwarding without the need for the context of the terminal device, saving resources.

[0019] Furthermore, other technical effects of the method described in the third aspect can be referred to the technical effects of the methods described in the first and second aspects, and will not be repeated here.

[0020] Fourthly, a communication method is provided. This method can be executed by a first tag management network element, by a module applied to the first tag management network element (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the functions of the first tag management network element. For ease of description, the following description uses the execution of the method by the first tag management network element as an example. The method includes: during the registration process of a terminal device, the first tag management network element assigns a temporary identifier and sends the temporary identifier to the terminal device; receives a second message from a first access and mobility management network element; and determines whether to provide communication services to the terminal device based on the temporary identifier. The temporary identifier includes a first identifier, which is used to identify the first tag management network element; the second message includes a service request message, which is used to request communication services from the first tag management network element, and the service request message includes the temporary identifier.

[0021] Based on the methods described in the fourth aspect and the fifth aspect below, during the terminal device registration process, the first tag management network element can assign a temporary identifier to the terminal device. This temporary identifier includes a first identifier, which identifies the first tag management network element. The terminal device can then obtain the first identifier based on the temporary identifier and send a service request message and the first identifier to the access network device. This allows the access network device and the first access and mobility management network element determined by the access network device to forward the terminal device's service request message to the first tag management network element. Simultaneously, the first tag management network element can determine that the service request message is a request message from the terminal device (authentication successful) based on the temporary identifier in the service request message. At this point, the first tag management network element can determine to provide communication services to the terminal device.

[0022] In one possible design, during the terminal device registration process, the tag management network element allocates a temporary identifier and sends the temporary identifier to the terminal device. This includes: the first tag management network element receiving a registration request message from the first access and mobility management network element; in response to the registration request message, the first tag management network element allocates a temporary identifier to the terminal device and sends the temporary identifier to the terminal device. That is, the first tag management network element can trigger the allocation of a temporary identifier to the terminal device and send the temporary identifier to the terminal device based on the registration request message (sent by the terminal device), thereby achieving on-demand allocation, flexibility, and resource conservation.

[0023] In one possible design, the method described in the fourth aspect further includes: the first label management network element receiving a fourth identifier from the first access and mobility management network element, and using the fourth identifier to allocate a temporary identifier. The fourth identifier is used to identify the first access and mobility management network element.

[0024] In one possible design, the second message further includes a second identifier and a third identifier. The second identifier is assigned to the access network device and used to identify the terminal device, while the third identifier is used to identify the access network device.

[0025] Optionally, the method described in the fourth aspect further includes: the first tag management network element sending a response message of the second message to the first access and mobility management network element. The response message of the second message includes a response message to the service request message, a second identifier, and a third identifier.

[0026] Furthermore, other technical effects of the method described in the fourth aspect can be referred to the technical effects of the methods described in the first, second, and third aspects, and will not be repeated here.

[0027] Fifthly, a communication method is provided. This method can be executed by a terminal device, by a module applied to the terminal device (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the terminal device's functions. For ease of description, the following description uses the method executed by a terminal device as an example. The method includes: the terminal device acquiring a temporary identifier, and sending a first identifier and a service request message to the access network device based on the temporary identifier. The service request message is used to request communication services from the first tag management network element, and the service request message contains the temporary identifier.

[0028] In one possible design, the terminal device obtains a temporary identifier by receiving a temporary identifier assigned by a first tag management network element during the terminal device registration process.

[0029] Furthermore, other technical effects of the method described in the fifth aspect can be referred to the technical effects of the method described in the fourth aspect, and will not be repeated here.

[0030] Sixthly, a communication method is provided. The method includes: a first access and mobility management network element receiving capability information of an access network device sent by an access network device; determining a second access and mobility management network element based on the capability information of the access network device; and sending indication information to the access network device. The capability information of the access network device is used to indicate that the access network device supports Internet of Things (IoT) services; the second access and mobility management network element supports IoT services; and the indication information includes the identifier of the second access and mobility management network element.

[0031] Based on the methods described in the sixth aspect and the seventh aspect below, the access network device can send its capability information (i.e., support for IoT devices) to the first access and mobility management network element. The first access and mobility management network element can then determine the redirected second access and mobility management network element based on this capability information and send the identifier of the second access and mobility management network element to the access network device via indication information. When the access network device receives a request message from a terminal device, it can directly forward the request message to the second access and mobility management network element via the identifier of the second access and mobility management network element and a first message. The second access and mobility management network element can then forward the request message to (e.g., by default) the first tag management network element. This ensures that the access network device can select a suitable access and mobility management network element (e.g., the second access and mobility management network element), and that the access and mobility management network element can select a suitable tag management network element (e.g., the first tag management network element). Furthermore, the access network device and the second access and mobility management network element can be addressed using temporary identifiers, simplifying the process.

[0032] In one possible design, the first access and mobility management network element (AMI) determines the second AMI based on the capability information of the access network device. This includes: the first AMI determining the second AMI based on a first condition and the capability information of the access network device; wherein the first condition is that the first AMI does not support IoT services, or the first AMI supports IoT services but does not support the IoT services corresponding to the access network device. That is, the first AMI can determine the redirected second AMI according to a certain strategy, so that the access network device can select a suitable default second AMI to process the request message from the terminal device. The above first condition is only an example; the first condition can also include any other possible conditions, which will not be elaborated further.

[0033] In one possible design, the indication information also includes the identifier of the first tag management network element, which supports IoT services. That is, the first access and mobility management network element can also determine the tag management network element, such as the first tag management network element, so that the subsequent second access and mobility management network element can select a suitable default tag management network element, i.e., the first tag management network element, to handle the (IoT) terminal device's request.

[0034] In one possible design, the method described in the sixth aspect further includes: the second access and mobility management network element receiving a first message from the access network device and sending a request message to the first tag management network element. The first message includes a request message used to request communication services from the tag management network element or to request registration with the tag management network element. That is, the second access and mobility management network element can choose any tag management network element that supports IoT devices, such as the first tag management network element, to establish a connection with the second access and mobility management network element, simplifying implementation.

[0035] In one possible design, the first message also includes the identifier of the first label management network element. The second access and mobility management network element sends a request message to the first label management network element, including: the second access and mobility management network element sending a request message to the first label management network element based on the identifier of the first label management network element. That is, the second access and mobility management network element can quickly identify the first label management network element directly based on its identifier, without having to select it itself.

[0036] Seventhly, a communication method is provided. This method can be executed by an access network device, by a module (e.g., processor, chip, or chip system) applied to the access network device, or by a logical node, logical module, or software capable of implementing all or part of the functions of the access network device. For ease of description, the following description assumes the method is executed by an access network device. The method includes: the access network device receiving indication information from a first access and mobility management network element, receiving a request message from a terminal device, and sending a first message to a second access and mobility management network element according to the indication information. The indication information includes the identifier of the second access and mobility management network element; the request message is used to request communication services from a tag management network element or to request registration with a tag management network element; the first message includes the request message, which is used to request communication services from a tag management network element or to request registration with a tag management network element.

[0037] In one possible design, the access network device receives indication information from a first access and mobility management network element, including: the access network device sending its capability information to the first access and mobility management network element, and receiving indication information returned by the first access and mobility management network element based on the capability information. The capability information of the access network device is used to indicate that the access device supports processing Internet of Things (IoT) services.

[0038] In one possible design, the indication information also includes the identifier of the first tag management network element, and the first tag management network element identified by the identifier of the first tag management network element supports IoT services.

[0039] In one possible design, the first message also includes the identifier of the first tag management network element.

[0040] In one possible design, the method in the seventh aspect further includes: the access network device assigning a second identifier. The second identifier is used to identify the terminal device, and the first message also includes the second identifier. Optionally, the method in the seventh aspect further includes: the access network device receiving a response message to the first message from the first access and mobility management network element, and sending a response message to the terminal device for the request message based on the second identifier. The response message to the first message includes the response message to the request message and the second identifier.

[0041] Furthermore, other technical effects of the method described in the seventh aspect can be referred to the technical effects of the methods described in the first aspect, the second aspect, and the seventh aspect, and will not be repeated here.

[0042] Eighthly, a communication apparatus is provided, which can be the access network device described in the first aspect above. The communication apparatus includes: modules for performing the method as described in the first aspect. For example, a transceiver module and a processing module. The transceiver module is used to perform the transceiver functions of the communication apparatus, and the processing module is used to perform functions of the communication apparatus other than the transceiver functions.

[0043] The transceiver module is used to receive a first identifier and a service request message from a terminal device. The processing module is used to determine a first access and mobility management network element based on the first identifier and identifier association information. The transceiver module is also used to send a first message to the first access and mobility management network element. The first identifier is used to identify the first tag management network element, and the service request message is used to request communication services from the first tag management network element; the identifier association information includes the association relationship between the first access and mobility management network element and the tag management network element, and the tag management network element includes the first tag management network element; the first message includes the service request message and the first identifier.

[0044] In one possible design, the terminal device is an IoT device. Before the communication device described in the eighth aspect receives the first identifier and service request message from the terminal device, the transceiver module is further configured to send the capability information of the communication device to the first access and mobility management network element, and receive identifier association information returned by the first access and mobility management network element based on the capability information of the communication device. The capability information of the communication device is used to indicate that the communication device supports the access of IoT devices.

[0045] In one possible design, the processing module is further configured to allocate a second identifier. This second identifier is used to identify the terminal device, and the first message also includes the second identifier.

[0046] Optionally, the transceiver module is further configured to receive a response message to the first message from the first access and mobility management network element. The processing module is further configured to send a response message to the terminal device for the service request message based on the second identifier. The response message to the first message includes the response message to the service request message and the second identifier.

[0047] Optionally, the transceiver module may include a transmitting module and a receiving module. The transmitting module implements the transmitting function of the communication device described in the eighth aspect, and the receiving module implements the receiving function of the communication device described in the eighth aspect.

[0048] Optionally, the communication device described in the eighth aspect may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the method described in the first aspect.

[0049] Furthermore, the technical effects of the communication device described in the eighth aspect can be referred to the technical effects of the method described in the first aspect, and will not be repeated here.

[0050] A ninth aspect provides a communication apparatus, which can be the access network device described in the second aspect above. The communication apparatus includes modules for performing the method described in the second aspect. For example, a transceiver module and a processing module. The transceiver module performs the transceiver functions of the communication apparatus, and the processing module performs functions of the communication apparatus other than the transceiver functions.

[0051] The transceiver module is used to receive a first identifier and a service request message from a terminal device. The processing module is used to determine a first access and mobility management network element based on the first identifier. The transceiver module is also used to send a first message to the first access and mobility management network element. The first identifier is used to identify the first tag management network element, and the service request message is used to request communication services from the first tag management network element; the first identifier also identifies the first access and mobility management network element; the first message includes the service request message and the first identifier.

[0052] In one possible design, the processing module is further configured to allocate a second identifier. This second identifier is used to identify the terminal device, and the first message also includes the second identifier.

[0053] Optionally, the transceiver module is further configured to receive a response message to the first message from the first access and mobility management network element. The processing module is further configured to send a response message to the terminal device for the service request message based on the second identifier. The response message to the first message includes the response message to the service request message and the second identifier.

[0054] Optionally, the transceiver module may include a transmitting module and a receiving module. The transmitting module implements the transmitting function of the communication device described in the ninth aspect, and the receiving module implements the receiving function of the communication device described in the ninth aspect.

[0055] Optionally, the communication device described in the ninth aspect may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the method described in the second aspect.

[0056] Furthermore, the technical effects of the communication device described in the ninth aspect can be referred to the technical effects of the method described in the second aspect, and will not be repeated here.

[0057] A tenth aspect provides a communication apparatus, which can be the first access and mobility management network element described in the third aspect above. The communication apparatus includes modules for performing the method as described in the third aspect. For example, a transceiver module and a processing module. The transceiver module is used to perform the transceiver functions of the communication apparatus, and the processing module is used to perform functions of the communication apparatus other than the transceiver functions.

[0058] The transceiver module is used to receive a first message from the access network device. The processing module is used to send a second message to the first tag management network element according to a first identifier. The first message includes a first identifier and a service request message. The first identifier is used to identify the first tag management network element, and the service request message is used to request communication services from the first tag management network element. The second message includes the service request message.

[0059] In one possible design, before the communication device described in the tenth aspect receives the first message from the access network device, the transceiver module is further configured to receive access network device capability information sent by the access network device, and send identification association information to the access network device. The access network device capability information is used to indicate that the access network device supports the access of IoT devices; the identification association information includes the association relationship between the first access and mobility management network element and the tag management network element, and the tag management network element includes the first tag management network element.

[0060] In one possible design, the first identifier is further used to identify the first access and mobility management network element; before the communication device described in the tenth aspect receives the first message from the access network device, the transceiver module is further used to send a fourth identifier to the first tag management network element. The fourth identifier is used to identify the first access and mobility management network element.

[0061] Optionally, the fourth identifier is also used when the first tag management network element assigns a temporary identifier to the terminal device, and the temporary identifier includes the first identifier.

[0062] In one possible design, the first message also includes a second identifier, which is assigned by the access network device and used to identify the terminal device.

[0063] Optionally, the second message may also include a second identifier and a third identifier. The third identifier is used to identify the access network device.

[0064] Optionally, the transceiver module is further configured to receive a response message for the second message from the first tag management network element. The processing module is further configured to send a response message for the first message to the access network device based on the third identifier. The response message for the second message includes a response message for the service request message, a second identifier, and a third identifier; the response message for the first message includes a response message for the service request message and a second identifier.

[0065] Optionally, the transceiver module may include a transmitting module and a receiving module. The transmitting module implements the transmitting function of the communication device described in the tenth aspect, and the receiving module implements the receiving function of the communication device described in the tenth aspect.

[0066] Optionally, the communication device according to the tenth aspect may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the method described in the third aspect.

[0067] Furthermore, the technical effects of the communication device described in the tenth aspect can be referred to the technical effects of the method described in the third aspect, and will not be repeated here.

[0068] Eleventhly, a communication device is provided, which can be the first tag management network element described in the fourth aspect above. The communication device includes: modules for performing the method described in the fourth aspect. For example, a transceiver module and a processing module. The transceiver module is used to perform the transceiver function of the communication device, and the processing module is used to perform functions of the communication device other than the transceiver function.

[0069] During the terminal device registration process, the processing module allocates a temporary identifier and sends it to the terminal device. The transceiver module receives a second message from the first access and mobility management network element. The processing module also determines whether to provide communication services to the terminal device based on the temporary identifier. The temporary identifier includes a first identifier used to identify the communication device described in the eleventh aspect; the second message includes a service request message used to request communication services from the communication device, and the service request message includes the temporary identifier.

[0070] In one possible design, the transceiver module is further configured to receive a registration request message from the first access and mobility management network element. In response to the registration request message, the processing module is further configured to allocate a temporary identifier to the terminal device. The transceiver module is further configured to send the temporary identifier to the terminal device.

[0071] In one possible design, the transceiver module is further configured to receive a fourth identifier from the first access and mobility management network element. The processing module is further configured to allocate a temporary identifier using the fourth identifier. The fourth identifier is used to identify the first access and mobility management network element.

[0072] In one possible design, the second message further includes a second identifier and a third identifier. The second identifier is assigned to the access network device and used to identify the terminal device, while the third identifier is used to identify the access network device.

[0073] Optionally, the transceiver module is further configured to send a response message for the second message to the first access and mobility management network element. The response message for the second message includes a response message to the service request message, a second identifier, and a third identifier.

[0074] Optionally, the transceiver module may include a sending module and a receiving module. The sending module implements the sending function of the communication device described in the eleventh aspect, and the receiving module implements the receiving function of the communication device described in the eleventh aspect.

[0075] Optionally, the communication device described in the eleventh aspect may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the method described in the fourth aspect.

[0076] Furthermore, the technical effects of the communication device described in the eleventh aspect can be referred to the technical effects of the method described in the fourth aspect, and will not be repeated here.

[0077] In a twelfth aspect, a communication device is provided, which can be the terminal device described in the fifth aspect above. The communication device includes: modules for performing the method as described in the fifth aspect. For example, a transceiver module and a processing module. The transceiver module is used to perform the transceiver functions of the communication device, and the processing module is used to perform functions of the communication device other than the transceiver functions.

[0078] The processing module is used to obtain a temporary identifier and, based on the temporary identifier, send a first identifier and a service request message to the access network device. The service request message, which includes the temporary identifier, is used to request communication services from the first tag management network element.

[0079] In one possible design, during the registration process of the communication device described in the twelfth aspect, the transceiver module is used to receive a temporary identifier assigned by the first tag management network element.

[0080] Optionally, the transceiver module may include a transmitting module and a receiving module. The transmitting module implements the transmitting function of the communication device described in the twelfth aspect, and the receiving module implements the receiving function of the communication device described in the twelfth aspect.

[0081] Optionally, the communication device described in the twelfth aspect may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the method described in the fifth aspect.

[0082] Furthermore, the technical effects of the communication device described in the twelfth aspect can be referred to the technical effects of the method described in the fifth aspect, and will not be repeated here.

[0083] In a thirteenth aspect, a communication apparatus is provided, which can be the access network device described in the fifth aspect above. The communication apparatus includes modules for performing the method described in the seventh aspect. For example, a transceiver module and a processing module. The transceiver module is used to perform the transceiver functions of the communication apparatus, and the processing module is used to perform functions of the communication apparatus other than the transceiver functions.

[0084] The transceiver module is used to receive indication information from the first access and mobility management network element and to receive request messages from the terminal device. The processing module is used to send a first message to the second access and mobility management network element according to the indication information. The indication information includes the identifier of the second access and mobility management network element; the request message is used to request communication services from the tag management network element or to request registration with the tag management network element; the first message includes the request message, which is used to request communication services from the tag management network element or to request registration with the tag management network element.

[0085] In one possible design, the transceiver module is further configured to send the capability information of the communication device described in aspect thirteen to the first access and mobility management network element, and to receive indication information returned by the first access and mobility management network element based on the capability information. The capability information of the communication device is used to indicate that the access device supports processing Internet of Things (IoT) services.

[0086] In one possible design, the indication information also includes the identifier of the first tag management network element, and the first tag management network element identified by the identifier of the first tag management network element supports IoT services.

[0087] In one possible design, the first message also includes the identifier of the first tag management network element.

[0088] In one possible design, the processing module is further configured to allocate a second identifier. This second identifier is used to identify the terminal device, and the first message also includes the second identifier.

[0089] Optionally, the transceiver module is further configured to receive a response message to the first message from the first access and mobility management network element. The processing module is further configured to send a response message to the request message to the terminal device based on the second identifier. The response message to the first message includes a response message to the request message and the second identifier.

[0090] Optionally, the transceiver module may include a transmitting module and a receiving module. The transmitting module implements the transmitting function of the communication device described in the thirteenth aspect, and the receiving module implements the receiving function of the communication device described in the thirteenth aspect.

[0091] Optionally, the communication device described in aspect thirteen may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the method described in aspect seven.

[0092] Furthermore, the technical effects of the communication device described in aspect thirteen can be referred to the technical effects of the method described in aspect seven, and will not be repeated here.

[0093] In a fourteenth aspect, a communication device is provided, comprising: a processor; the processor being coupled to a memory for storing a computer program, wherein when the processor executes the computer program, the communication device is configured to perform the method described in any one of the first to fifth aspects and the seventh aspect.

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

[0095] In the embodiments of this application, the communication device described in the fourteenth aspect can be an access network device as described in any of the implementations of the first, second, or seventh aspects, or a chip (system) or other component or assembly disposed in the access network device, or a device comprising the access network device; or, the communication device described in the fourteenth aspect can be a first access and mobility management network element as described in the third aspect, or a chip (system) or other component or assembly disposed in the first access and mobility management network element, or a device comprising the first access and mobility management network element; or, the communication device described in the fourteenth aspect can be a first tag management network element as described in the fourth aspect, or a chip (system) or other component or assembly disposed in the first tag management network element, or a device comprising the first tag management network element; or, the communication device described in the fourteenth aspect can be a terminal device as described in the fifth aspect, or a chip (system) or other component or assembly disposed in the terminal device, or a device comprising the terminal device.

[0096] Furthermore, the technical effects of the communication device described in the fourteenth aspect can be referenced from the technical effects of the method described in any of the first to fifth aspects and the seventh aspect, which will not be repeated here.

[0097] In a fifteenth aspect, a communication device is provided. The communication device includes a processor coupled to a memory, the processor being configured to execute a computer program stored in the memory, such that the communication device performs the method described in any possible implementation of the fifth and seventh aspects.

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

[0099] In the embodiments of this application, the communication device described in the fifteenth aspect can be an access network device as described in any of the implementations of the first, second, or seventh aspects, or a chip (system) or other component or assembly disposed in the access network device, or a device comprising the access network device; or, the communication device described in the fifteenth aspect can be a first access and mobility management network element as described in the third aspect, or a chip (system) or other component or assembly disposed in the first access and mobility management network element, or a device comprising the first access and mobility management network element; or, the communication device described in the fifteenth aspect can be a first tag management network element as described in the fourth aspect, or a chip (system) or other component or assembly disposed in the first tag management network element, or a device comprising the first tag management network element; or, the communication device described in the fifteenth aspect can be a terminal device as described in the fifth aspect, or a chip (system) or other component or assembly disposed in the terminal device, or a device comprising the terminal device.

[0100] Furthermore, the technical effects of the communication device described in the fifteenth aspect can be referred to the technical effects of the method described in any of the first to fifth aspects and the seventh aspect, which will not be repeated here.

[0101] In a sixteenth aspect, a communication device is provided, comprising: a processor and a memory; the memory being configured to store a computer program, which, when executed by the processor, causes the communication device to perform the method described in any one of the first to fifth aspects and the seventh aspect.

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

[0103] In the embodiments of this application, the communication device described in the sixteenth aspect can be an access network device as described in any of the implementations of the first, second, or seventh aspects, or a chip (system) or other component or assembly disposed in the access network device, or a device comprising the access network device; or, the communication device described in the sixteenth aspect can be a first access and mobility management network element as described in the third aspect, or a chip (system) or other component or assembly disposed in the first access and mobility management network element, or a device comprising the first access and mobility management network element; or, the communication device described in the sixteenth aspect can be a first tag management network element as described in the fourth aspect, or a chip (system) or other component or assembly disposed in the first tag management network element, or a device comprising the first tag management network element; or, the communication device described in the sixteenth aspect can be a terminal device as described in the fifth aspect, or a chip (system) or other component or assembly disposed in the terminal device, or a device comprising the terminal device.

[0104] Furthermore, the technical effects of the communication device described in the sixteenth aspect can be referenced from the technical effects of the method described in any of the first to fifth aspects and the seventh aspect, and will not be repeated here.

[0105] In a seventeenth aspect, a communication system is provided. The communication system includes: an access network device for performing the method of the first aspect; a first access and mobility management network element for performing the method of the third aspect; a first tag management network element for performing the method of the fourth aspect; and a terminal device for performing the method of the fifth aspect.

[0106] Eighteenth aspect: A communication system is provided. The communication system includes: an access network device for performing the method of the second aspect; a first access and mobility management network element for performing the method of the third aspect; a first tag management network element for performing the method of the fourth aspect; and a terminal device for performing the method of the fifth aspect.

[0107] In a nineteenth aspect, a communication system is provided. The communication system includes: a first access and mobility management network element and a second access and mobility management network element for performing the method described in the sixth aspect, and an access network device for performing the method described in the seventh aspect.

[0108] In a twentieth aspect, a communication chip is provided, wherein instructions are stored that, when the chip is operated on a communication device, cause the communication method described in any one of the first to fifth aspects and the seventh aspect to be implemented.

[0109] A twenty-first aspect provides a computer-readable storage medium comprising: a computer program or instructions; wherein, when the computer program or instructions are executed on a computer, the computer causes the computer to perform the method described in any one of the first to fifth aspects and the seventh aspect.

[0110] In a twenty-second aspect, a computer program product is provided, comprising: a computer program or instructions that, when executed on a computer, cause the computer to perform the method described in any one of the first to fifth aspects and the seventh aspect. Attached Figure Description

[0111] Figure 1 is a schematic diagram of a 5GS architecture;

[0112] Figure 2 is a structural diagram of an AMF logo;

[0113] Figure 3 is a schematic diagram of the architecture of the communication system provided in an embodiment of this application;

[0114] Figure 4 is a schematic diagram of the architecture of the communication system provided in an embodiment of this application;

[0115] Figure 5 is a flowchart illustrating the communication method provided in an embodiment of this application;

[0116] Figure 6 is a schematic flowchart of the communication method provided in an embodiment of this application;

[0117] Figure 7 is a flowchart illustrating the communication method provided in an embodiment of this application.

[0118] Figure 8 is a flowchart illustrating the communication method provided in an embodiment of this application.

[0119] Figure 9 is a flowchart illustrating the communication method provided in an embodiment of this application.

[0120] Figure 10 is a schematic flowchart of the communication method provided in an embodiment of this application;

[0121] Figure 11 is a schematic flowchart of the communication method provided in an embodiment of this application;

[0122] Figure 12 is a schematic diagram of the communication device provided in an embodiment of this application;

[0123] Figure 13 is a schematic diagram of the structure of the communication device provided in the embodiment of this application. Detailed Implementation

[0124] For ease of understanding, the technical terms involved in the embodiments of this application will be introduced below.

[0125] 1. Fifth generation (5G) mobile communication system (abbreviated as 5G system (5GS))

[0126] Figure 1 is a schematic diagram of the 5GS architecture. As shown in Figure 1, 5GS includes: access network (AN), core network (CN), and terminal equipment.

[0127] The aforementioned terminal equipment can be a terminal device with transceiver functions, or it can be a chip or chip system disposed in the terminal device. This terminal equipment can also be referred to as user equipment (UE), access terminal equipment, subscriber unit, user station, mobile station (MS), mobile station, remote station, remote terminal equipment, mobile device, user terminal equipment, target terminal equipment, wireless communication equipment, user agent or user device, tag, or device. In the embodiments of this application, the terminal equipment can be an Internet of Things (IoT) device, such as an ambient IoT (A-IoT) device, and can be a passive IoT terminal device, also referred to as a tag. The terminal can be a passive device, which can be a passive tag, including but not limited to radio frequency identification (RFID), Bluetooth, Zigbee, and other power-free terminal tags. The terminal equipment can also be a semi-passive device or an active device. Active devices can be devices with wireless transceiver capabilities, such as mobile phones, tablets, computers with wireless transceiver capabilities, virtual reality (VR) terminals, augmented reality (AR) terminals, wireless terminal equipment in industrial control, wireless terminal equipment in self-driving vehicles, wireless terminal equipment in remote medical care, wireless terminal equipment in smart grids, wireless terminal equipment in transportation safety, wireless terminal equipment in smart cities, wireless terminal equipment in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, and roadside units with terminal device functions. Units (RSUs), etc., and flight equipment (e.g., intelligent robots, hot air balloons, drones, airplanes), etc.The terminal device of this application can also be an on-board module, on-board component, on-board chip, or on-board unit built into a vehicle as one or more components or units, a transportation vehicle with wireless communication capabilities, or a communication module. The terminal device can also be other devices with terminal device functions; for example, it can be a device that functions as a terminal device in D2D communication. Alternatively, the terminal device can be a terminal device in a 5G mobile communication system or a terminal device in a future evolved network.

[0128] Terminal devices can acquire ambient energy to receive or transmit data. Energy acquisition methods can include radio waves, solar energy, light energy, wind energy, hydropower, thermal energy, kinetic energy, etc. This application does not limit the energy acquisition method for the terminal device. It should be understood that the passive IoT devices involved in this application can be in the form of passive IoT devices or any terminal form.

[0129] The aforementioned Access Network (AN) is used to implement access-related functions. It can provide network access functionality for authorized users in a specific area and determine transmission links of different quality based on user level and service requirements to transmit user data. The AN forwards control signals and user data between the terminal and the Network Access Network (CN). The AN may include access network equipment, also known as radio access network (RAN) equipment. The CN is primarily responsible for maintaining the mobile network's subscription data and providing terminal equipment with functions such as session management, mobility management, policy management, and security authentication.

[0130] The CN mainly includes the following: User plane function (UPF), Authentication server function (AUSF), Access and mobility management function (AMF), Session management function (SMF), Network slice selection function (NSSF), Network exposure function (NEF), Network repository function (NRF), Policy control function (PCF), Unified data management (UDM), Unified data repository (UDR), Application function (AF), and Tag management function (TMF).

[0131] As shown in Figure 1, the UE accesses the 5G network through the RAN device. The UE communicates with the AMF through the N1 interface (N1 for short); the RAN communicates with the AMF through the N2 interface (N2 for short); the RAN communicates with the UPF through the N3 interface (N3 for short); the SMF communicates with the UPF through the N4 interface (N4 for short); and the UPF accesses the data network (DN) through the N6 interface (N6 for short). Furthermore, the control plane functions shown in Figure 1, such as AUSF, AMF, SMF, NSSF, NEF, NRF, PCF, UDM, UDR, and AF, interact using service-oriented interfaces. For example, the service interfaces provided by AUSF include Nausf; AMF includes Namf; SMF includes Nsmf; NSSF includes Nnssf; NEF includes Nnef; NRF includes Nnrf; PCF includes Npcf; UDM includes Nudm; UDR includes Nudr; and AF includes Naf.

[0132] RAN equipment can be a device that provides access for terminal devices. For example, RAN equipment may include: future mobile communication systems, such as access network equipment (e.g., base stations) in future mobile communication systems, or the network equipment may have other naming conventions in future mobile communication systems, all of which are covered within the protection scope of the embodiments of this application, and this application does not limit them in any way. Alternatively, RAN equipment may also include 5G, such as gNB in ​​a new radio (NR) system, or one or a group of antenna panels (including multiple antenna panels) of a base station in 5G, or it may be a network node constituting a gNB, transmission and reception point (TRP) or transmission point (TP) or transmission measurement function (TMF), such as a building base band unit (BBU), or a centralized unit (CU) or distributed unit (DU), an RSU with base station functionality, or a wired access gateway, or the core network of 5G. Alternatively, RAN equipment may also include access points (APs) in wireless fidelity (WiFi) systems, wireless relay nodes, wireless backhaul nodes, various forms of macro base stations, micro base stations (also known as small stations), relay stations, access points, wearable devices, vehicle-mounted equipment, and so on.

[0133] UPF is primarily responsible for user data processing (forwarding, receiving, billing, etc.).

[0134] AUSF is primarily used to perform security authentication for terminal devices.

[0135] The Active Mobility Controller (AMC) is primarily used for mobility management in mobile networks, such as user location updates, user registration with the network, and user handover. In 5G mobile communication systems, the AMF mainly performs mobility management and access authentication / authorization functions. Furthermore, it is responsible for transmitting user policies between terminal devices and policy control function (PCF) network elements.

[0136] SMF is primarily used for session management in mobile networks, such as session establishment, modification, and release. Specific functions include assigning Internet Protocol (IP) addresses to users and selecting a UPF (User Provider Function) to provide packet forwarding capabilities.

[0137] The PCF primarily supports providing a unified policy framework to control network behavior, delivering policy rules to control-layer network functions, and acquiring user subscription information related to policy decisions. The PCF can provide policies to the AMF and SMF, such as Quality of Service (QoS) policies and slice selection policies.

[0138] NSSF is primarily used to select network slices for end devices.

[0139] The NEF is primarily used to support the opening of capabilities and events. For example, the NEF can expose some capabilities of the 5G network to third-party applications through application program interfaces (APIs). Third-party applications can obtain some capabilities of the 5G network by calling the APIs provided by the NEF through the AF, enabling them to control certain behaviors of the 5G network and terminal devices.

[0140] UDM is primarily used to store user data, such as subscription data and authentication / authorization data.

[0141] UDR is primarily used to store structured data, including contract data, policy data, externally exposed structured data, and application-related data.

[0142] AF primarily supports interaction with CN to provide services, such as influencing data routing decisions, policy control functions, or providing third-party services to the network side.

[0143] It is understood that the functions mentioned in the embodiments of this application can also refer to functional network elements or functional entities. For example, UPF can be referred to as UPF network element, AMF can be referred to as AMF network element, SMF can be referred to as SMF network element, PCF can be referred to as PCF network element, and so on, without limitation.

[0144] 2. 5G globally unique temporary identifier (5G-GUTI)

[0145] The 5G-GUTI is a temporary identifier assigned to a terminal device by the AMF during the registration process, used to globally and uniquely identify the terminal device. The AMF can reassign the 5G-GUTI at any time. The 5G-GUTI can consist of a globally unique AMF identifier (GUAMI) and a 5G-temporary mobile subscriber identity (5G-TMSI).

[0146] Among them, GUAMI can be used to identify one or more AMFs. That is, GUAMI can indicate which AMF assigned the 5G-GUTI, which is the AMF's identifier; 5G-GUTI can indicate the unique ID of the terminal device within the AMF.

[0147] For example, as shown in Figure 2, GUAMI can include a mobile country code (MCC), a mobile network code (MNC), and an AMF identity (AMFI). The AMFI can include: an AMF region ID, an AMF set ID, and an AMF pointer (or number). The AMF region ID is used to identify a region; the AMF set ID uniquely identifies an AMF within an AMF region; and the AMF pointer identifies one or more AMFs within an AMF set.

[0148] The GUAMI can occupy 48 bits, and the 5G-TMSI can occupy 32 bits. The MCC can occupy 12 bits, the MNC can occupy 12 bits, the AMF region ID can occupy 8 bits (with 256 possible values), the AMF set ID can occupy 10 bits (with 1024 possible values), and the AMF pointer can occupy 6 bits (with 64 possible values). The 5G-TMSI can occupy 32 bits.

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

[0150] A-IoT can also be called passive IoT (P-IoT) or other names. In A-IoT, some network nodes can be passive, semi-passive, or active.

[0151] A-IoT can include IoT terminals, readers, IoT functions, and service requesters. IoT terminals can be passive IoT devices, sensors, or any other terminal form, without restriction. Readers can be access network devices, such as base stations, pole stations, micro base stations, macro stations, relay points (such as integrated access and backhaul nodes), mobile base stations, etc.; or they can be terminal devices, such as mobile phones, IoT devices, handheld readers, etc. Readers, also called readers, can conduct contactless two-way data communication via radio frequency (RF) and read and write electronic passive IoT devices or RFID tags using RF to achieve target identification and data exchange. Specific details can be found in existing technologies and will not be elaborated here. IoT functions, also known as passive IoT management functions, environmental energy harvesting IoT functions, or other names, can be used to manage IoT terminals or for the transmission of service data. IoT functions can be at least one network element in the core network, such as the aforementioned AMF or the following tag management function (TMF).

[0152] The requesting party, also known as the operational party or third party, can be a server (such as an AF, application server (AS), or passive IoT application function (P-IoT AF or A-IoT AF)), an application function, or other device capable of sending operational commands. Furthermore, the operational requesting party can correspond to a certain type of user, which can include enterprises, tenants, third parties, or companies, without restriction. The fact that the operational requesting party corresponds to a certain type of user can be understood as the operational requesting party belonging to that type of user, i.e., being managed by that type of user.

[0153] When a service requester operates an IoT terminal, it can send operation commands through the IoT function. These commands can include operations such as obtaining IoT terminal information, inventory checks, reading, writing, disabling or killing, interacting with passive IoT devices, and command-line operations. Furthermore, the command can include information such as the location and the IoT terminal's identifier to indicate which IoT terminal device needs to perform the operation specified in the command. For example, the service requester can send an operation command to the IoT function. Upon receiving the command, the IoT function triggers a reader to randomly connect to the IoT terminal. After the IoT terminal's random connection is complete, i.e., after the IoT terminal connects to the reader, the IoT function can send operation commands to the IoT terminal through the reader to complete the operation of the IoT device.

[0154] 4. Radio Frequency Identification (RFID)

[0155] RFID technology is a contactless automatic identification technology. An RFID system includes tags and readers. The reader integrates an antenna for transmitting and receiving data, or the reader and antenna may be separate. Specifically, the reader charges the tag by sending an excitation signal to it. The tag receives the signaling from the reader and sends its own signaling back to the reader via reflected signals. In this way, the reader can identify the tag's identity (ID). The reader can then perform read and write operations on the tag, and other operations on it, which are not limited here.

[0156] A reader can also be called a reader, exciter, excitation source, radio frequency source, or interrogator, etc., without limitation. An excitation signal can also be called a carrier signal, radio frequency signal, or wireless signal, etc., without limitation. A tag uses a low-precision, low-power, medium-low frequency ring oscillator or a completely non-local oscillator to receive downlink signals. A tag can also be called a low-power terminal device, tag device, passive device, etc. Passive Internet of Things terminals, such as RFID, are mainly used in the following application scenarios: (1) Logistics and warehousing: including inventory and tracking of goods, environmental and cargo status monitoring during the transportation of high-value goods (such as vaccines); (2) Industrial manufacturing: including environmental and equipment status monitoring, etc.

[0157] With technological advancements and environmental regulations, passive IoT is poised for large-scale deployment, projected to cover hundreds of billions of devices in the future. However, the limited functionality of passive or semi-passive terminals necessitates external stimulation to transmit information, typically from a card reader (or card reader / writer). Current deployments suffer from short communication distances between the reader and the terminal, leading to management difficulties. By integrating card readers into base stations using new air interface (NR) technology, the reader's inventory capabilities (including reading, writing, destroying, and locking tags) can be integrated. This allows the base station to support inventory management, stimulating passive tags via NR technology for inventory checks. This achieves functionality similar to the reader / writer in ISO 18000-6C, increasing the communication distance between passive terminals and the reader, and enabling unified management by the operator's base stations. This includes IoT terminals with environmental power supply capabilities, as well as IoT terminals with sensing functions. Besides passive RFID, there is also active RFID technology capable of actively transmitting signals.

[0158] Currently, access and mobility management network elements, such as the AMF (Access Management Function), can be used for access and mobility management of terminal devices. For example, the AMF can assign a temporary identifier to a terminal device, which may include an AMF identifier and a terminal device identifier. The RAN (Radio Router) can select the appropriate AMF to forward the service request based on the AMF identifier sent by the terminal device. A-IoT devices differ significantly from existing terminal devices in form and function, requiring the introduction of new network elements, such as the tag management function (TMF), to provide access and mobility management for these A-IoT devices.

[0159] However, when the AMF and TMF are deployed separately and the TMF assigns temporary identifiers to the terminal devices, how the RAN and AMF can forward the terminal devices' service requests to the appropriate TMF is an urgent problem to be solved.

[0160] For example, the terminal device is a tag, and the AMF and TMF are deployed separately. The TMF is used to allocate temporary identifiers for the tags and to handle the tags' access and mobility management functions. In this case, if the tag initiates a service request message with a temporary identifier (the service request message includes the temporary identifier allocated by the TMF), how the RAN and AMF forward the tag's service request message to the appropriate TMF so that the TMF can provide communication services for the tag is a problem that urgently needs to be solved.

[0161] To address the aforementioned technical issues, this application proposes the following technical solution to enable the RAN and AMF to forward service requests from terminal devices to the appropriate TMF when AMF and TMF are deployed separately and the TMF assigns temporary identifiers to terminal devices.

[0162] The technical solutions in this application will now be described with reference to the accompanying drawings.

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

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

[0165] Furthermore, in the embodiments of this application, the words "exemplary," "for example," etc., are used to indicate that they are examples, illustrations, or descriptions. Any embodiment or design scheme described as "exemplary" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the term "exemplary" is intended to present the concept in a concrete manner.

[0166] In the embodiments of this application, the terms "information," "signal," "message," "channel," and "singaling" may sometimes be used interchangeably. It should be noted that, without emphasizing their distinction, their intended meanings are consistent. Similarly, "of," "corresponding (relevant)," and "corresponding" may sometimes be used interchangeably. It should be noted that, without emphasizing their distinction, their intended meanings are consistent. Furthermore, the " / " mentioned in this application can be used to indicate an "or" relationship.

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

[0168] To facilitate understanding of the embodiments of this application, the communication system applicable to the embodiments of this application will be described in detail first using the communication system shown in FIG3 as an example. For example, FIG3 is a schematic diagram of the architecture of a communication system to which the communication method provided in the embodiments of this application applies.

[0169] As shown in Figure 3, the communication system can be applied to the above-mentioned 5GS, including: terminal equipment (such as UE), access network equipment (such as RAN), access and mobility management network elements (such as AMF, such as the first access and mobility management network element and the second access and mobility management network element below) and tag management network elements (such as the first tag management network element below).

[0170] Among them, the terminal device can be a terminal device in the Internet of Things, such as an A-IoT device. The A-IoT device can also be called an A-IoT terminal, passive A-IoT, terminal device, terminal equipment, passive tag, tag device, passive device, passive equipment, semi-passive device, semi-active device, semiconductor device, battery-free terminal / device, battery-less terminal / device, backscatter terminal, passive IoT, reflector, reflective terminal, or ambient signal device, device, etc.

[0171] Tag management network elements, such as TMFs, can be used to provide access and mobility management for tagged terminal devices. The following description uses TMFs as an example of tag management network elements. For instance, a TMF can perform functions such as selection, query, confirmation, unconfirmation, random number request, inventory, read, write, deactivation, locking, block write, block erase, access, encryption, decryption, timeout, invalidation, mobility management, and access authentication / authorization for terminal devices, without limitation. It is understood that in this embodiment, the tag management network element is deployed separately from the access and mobility management network elements, i.e., separately. Access network devices and access and mobility management network elements can be used to forward data or messages transmitted between terminal devices and tag management network elements. It is understood that the naming of this tag management network element is merely an example and can be replaced with any other possible naming, without limitation.

[0172] It is understandable that for detailed introductions of access network equipment and access and mobility management network elements, please refer to the relevant introductions in the 5GS section above, and will not be repeated here.

[0173] For example, taking UE, RAN, AMF, and TMF as examples, as shown in Figure 4, the UE can communicate with the RAN through the UU interface (UU); the RAN can communicate with the AMF through the N2 interface (N2); the AMF can communicate with the TMF through an interface with the TMF, such as the Nx interface (Nx); and the UE can communicate with the TMF through the N1 interface (N1). It is understood that the N1 and Nx interfaces are merely examples, and can be replaced with any other possible interfaces without limitation. It is understood that in this embodiment, the terminal device (i.e., UE) communicates with the TMF through the RAN and AMF, which will not be elaborated further below.

[0174] In a communication system, a terminal device can send a first identifier and a service request message (including the temporary identifier) ​​to an access network device based on a temporary identifier (including a first identifier used to identify the first tag management network element) assigned to it by the first tag management network element. The access network device can determine the first access and mobility management network element based on the first identifier and identifier association information, including the association relationship between the first access and mobility management network element and the tag management network element (including the first tag management network element), so that the access network device can forward the service request message and the first identifier to the first access and mobility management network element via a first message. The first access and mobility management network element can determine the first tag management network element based on the first identifier. This allows the first access and mobility management network element to forward service request messages to the first tag management network element that needs to provide communication services via a second message. This ensures that the access network equipment can select a suitable access and mobility management network element (such as the first access and mobility management network element), and that the access and mobility management network element can select a suitable tag management network element (such as the first tag management network element). This enables the access network equipment and the first access and mobility management network element to send the service request messages of the terminal equipment to the appropriate first tag management network element when the first tag management network element assigns a temporary identifier to the terminal equipment, thereby meeting the needs of the terminal equipment.

[0175] It is understood that Figures 3 and 4 are simplified schematic diagrams for ease of understanding. The communication system may also include other devices and / or other network elements, which are not shown in Figures 3 and 4.

[0176] The interaction process between various network elements / devices in the above-described communication system will be specifically described below with reference to Figures 5-11 through method embodiments. The communication method provided in this application embodiment can be applied to the above-described communication system, and will be described in detail below.

[0177] For example, Figure 5 is a schematic flowchart of a communication method provided in an embodiment of this application. This method can be applied to the interaction between terminal devices, access network devices, access and mobility management network elements, and tag management network elements in the above-described communication system. For ease of understanding, the communication method will be described below using a first access and mobility management network element and a first tag management network element as examples.

[0178] As shown in Figure 5, the flow of this communication method is as follows:

[0179] In S501, during the terminal device registration process, the first tag management network element assigns a temporary identifier and sends it to the terminal device. The terminal device then obtains the temporary identifier.

[0180] In other words, the temporary identifier can be assigned by the first label management network element. This temporary identifier can be a globally unique temporary identity information for the terminal device. The first label management network element can reassign the temporary identifier to the terminal device at any time without limitation. The access first label management network element can use this temporary identifier to establish the identity of the terminal device during signaling between the network and the terminal device to improve security.

[0181] The temporary identifier may include a first identifier, which can be used to identify the first label management network element. That is, the first identifier can be the identifier of the first label management network element. It can be understood that this temporary identifier is similar to the temporary identifier assigned to the terminal device by the AMF, such as 5G-GUTI. In this case, the first identifier can be similar to the aforementioned GUAMI to indicate that the temporary identifier is assigned by the first label management network element. The temporary identifier may also include a unique identifier for the terminal device within the first label management network element. This unique identifier for the terminal device within the first label management network element can be similar to the aforementioned 5G-TMSI. This can be understood by reference and will not be elaborated further.

[0182] The following is a detailed explanation of this step.

[0183] In one possible design, the first access and mobility management network element sends a registration request message to the first tag management network element. Correspondingly, the first tag management network element receives the registration request message from the first access and mobility management network element.

[0184] In response to the registration request message, the first tag management network element assigns a temporary identifier to the terminal device.

[0185] The first tag management network element sends a temporary identifier to the terminal device. Correspondingly, during the terminal device registration process, the terminal device receives the temporary identifier assigned by the first tag management network element.

[0186] The registration request message can be used to request registration.

[0187] It is understandable that when a terminal device needs to register with the network, such as a tag management network element, the terminal device can send message #1 to the access network device. Message #1 may include a registration request message. The access network device can choose to send message #2 to the default or any access and mobility management network element, such as the first access and mobility management network element. Message #2 may also include a registration request message and a temporary identifier assigned to the terminal device by the access network device, which can be denoted as RAN_NG AP_ID#1. RAN_NG AP_ID#1 can be an identifier that uniquely identifies the terminal device through the NG interface within the scope of the access network device. It is understandable that the principle of RAN NG AP ID#1 is similar to that of the existing RAN UE NGAP ID, which can be referred to for understanding and will not be elaborated further.

[0188] The first access and mobility management network element (AMI) can choose either the default or any label management network element. For example, if the first label management network element sends message #3, message #3 may include the registration request message (or it may be an initial registration request message). Message #3 may also include RAN_NG AP_ID#1 and the identifier of the access network device (which can be denoted as RAN ID). This RAN ID can be the one sent by the access network device to the first AMI when establishing a connection with the first AMI. Based on the registration request message in message #3, after the first label management network element accepts the registration request from the terminal device, it can assign a temporary identifier to the terminal device according to the registration request message. It is understood that messages #1, #2, and #3 may also include any other possible parameters or signaling, without limitation.

[0189] For example, when a UE needs to register with the network, it can send an AN message to the RAN. The AN message can include AN parameters, registration request messages, etc., without limitation. AN parameters can include access network-related parameters used to establish a communication connection, requested network slice selection assistance information (NSSAI), etc. The registration request message can include registration type, terminal device identifiers (such as subscription permanent identifier (SUPI), permanent equipment identifier (PEI), etc.), without limitation.

[0190] The RAN can select the appropriate access and mobility management network element based on the AN message, such as the first access and mobility management network element (denoted as AMF#1). Then, the RAN can forward the registration request message to AMF#1 based on the N2 interface. That is, the RAN can send an N2 message to AMF#1. The N2 message can include the registration request message and N2 parameters, etc., without limitation.

[0191] AMF#1 can select the appropriate label management network element based on the N2 message, such as the first label management network element (denoted as TMF#1). AMF#1 can then forward the registration request message to TMF#1 via the Nx interface. That is, AMF#1 can send an Nx message to TMF#1. The Nx message can include the registration request and other parameters, without limitation. In this way, TMF#1 can allocate a temporary identifier to the UE (i.e., the aforementioned temporary identifier) ​​based on the registration request message in the Nx message, when allowing the terminal device to register with TMF#1.

[0192] It is understood that the registration request message may include the device identifier of the terminal device. This device identifier can be SUPI, PEI, etc., without limitation.

[0193] Based on the above description, the first tag management network element can send a temporary identifier to the terminal device. For example, the first tag management network element can send a response message #3 to the first access and mobility management network element. This response message #3 may include a registration acceptance message, RAN_NG AP_ID#1, and a RAN ID. The registration acceptance message may include a temporary identifier. The first access and mobility management network element can then send a response message #2 to the access network device based on the RAN ID in the response message #3. This response message #2 may include a temporary identifier and RAN_NG AP_ID#1. Thus, the first access and mobility management network element can achieve stateless forwarding. The access network device can then send a response message #1 to the terminal device based on the RAN_NG AP_ID#1 in the response message #2. This response message #1 may include a registration response message, which may include a temporary identifier. Thus, the terminal device can obtain the temporary identifier.

[0194] It is understood that the response messages to message #3, message #2, and message #1 mentioned above may also include any other possible parameters or signaling, without limitation. This process is similar to the process described above where the terminal device sends a registration request message to the first tag management network element through the access network device and the first access and mobility management network element, and can be understood by reference without further elaboration.

[0195] For example, TMF#1 can send a registration acceptance message to AMF#1 via the Nx interface. That is, TMF#1 can send a response message of the Nx message to AMF#1, which may include the registration acceptance message or any other possible parameters and signaling, without limitation. AMF#1 can forward the registration acceptance message to the RAN via the N2 interface. That is, AMF#1 can send a response message of the N2 message to the RAN, which may include the registration acceptance message or any other possible parameters and signaling, without limitation. The RAN can forward the registration acceptance message to the UE via the UU interface. That is, the RAN can send a response message of the AN message to the UE, which may include the registration acceptance message or any other possible parameters and signaling, without limitation. In this way, the UE can obtain the temporary identifier allocated by the TMF based on the registration acceptance message and save or store the temporary identifier for subsequent requests.

[0196] It is understood that the aforementioned registration request message and registration acceptance message can be messages exchanged between the terminal device and the first tag management network element. That is, the registration request message and registration acceptance message can be non-access stratum (NAS) messages, and the access network device and access and mobility management network element (such as the aforementioned first access and mobility management network element) forward the registration request message and registration acceptance message.

[0197] It is understandable that after receiving the registration request message from the first access and mobility management network element, the first tag management network element can also initiate a security process to the terminal device as needed. If the first tag management network element successfully authenticates the terminal device, it can assign a temporary identifier to the terminal device. This security process may include: authenticating and authorizing the terminal device, establishing a security context, negotiating security parameters, etc. Its implementation principle is similar to existing security processes and can be understood by reference; it will not be elaborated further. For example, the first tag management network element can determine whether the terminal device is a subscribed terminal device based on its identifier (permanent identifier) ​​and its subscription information / data (such as data obtained from the UDM).

[0198] It is understood that the naming of the above registration request message, registration acceptance message, temporary identifier, and first identifier is only an example. The registration request message, registration acceptance message, temporary identifier, and first identifier can also be replaced with any other possible names without limitation.

[0199] In step S502, the terminal device sends a first identifier and a service request message to the access network device based on the temporary identifier. Correspondingly, the access network device receives the first identifier and service request message from the terminal device.

[0200] After receiving the temporary identifier assigned by the first tag management network element, the terminal device can obtain the first identifier based on the temporary identifier. When the terminal device has subsequent service requests, it can send a service request message to the access network device through the UU interface to request communication services / services from the first tag management network element. These requests may include requests for selection, query, confirmation, unconfirmation, random number generation, inventory, read, write, deactivation, locking, block write, block erase, access, encryption, decryption, timeout, invalidation, mobility management, access authentication / authorization, etc. This service request message may include the temporary identifier, which the first tag management network element can use to determine whether to provide communication services to the terminal device (i.e., verify the terminal device's identity). It is understood that this service request message is merely an example; the terminal device can also send any other possible request messages (NAS messages, forwarded by the access network device and the first access and management network element to the appropriate tag management network element) to the access network device without limitation.

[0201] It is understood that the aforementioned first identifier and service request message can be carried in the same message or in different messages. For example, the terminal device can first send the first identifier to the access network device, and then send the service request message to the terminal device when there is a service request, i.e., they are carried in different messages; or, the terminal device can send the first identifier and service request message to the access network device through the same message, such as message #a, when there is a service request, etc., without limitation.

[0202] The first identifier can be an identifier applicable to the access stratum (AS) layer. That is, the first identifier can be carried in the AS message so that the access network device can parse and obtain the first identifier at the AS layer. The service request message can be a NAS message, which is forwarded by the access network device and the access and mobility management network element (such as the first access and mobility management network element mentioned above).

[0203] It is understood that the naming of the above business request messages is only an example, and the business request messages can be replaced with any other possible names without limitation.

[0204] S503, the access network device determines the first access and mobility management network element based on the first identifier and the identifier association information.

[0205] The identifier association information (which can be denoted as identifier association information #1, corresponding to the first access and mobility management network element) may include the association relationship between the first access and mobility management network element and the tag management network element. That is, the tag management network element and the first access and mobility management network element can establish a connection, and the tag management network element includes the first tag management network element. The tag management network element can be one or more, without limitation. For example, the identifier association information may include the identifiers of the tag management network elements associated with the first access and mobility management network element, i.e., a list of tag management network element identifiers.

[0206] For example, the first access and mobility management network element can correspond to one tag management network element, that is, the first access and mobility management network element and the tag management network element can be one-to-one, for example, the first access and mobility management network element can correspond one-to-one with the first tag management network element; or, the first access and mobility management network element and the tag management network element can be one-to-many (i.e., at least two tag management network elements), for example, the first access and mobility management network element can be associated with the first tag management network element, the second tag management network element and the third tag management network element.

[0207] It is understandable that the correspondence between access and mobility management network elements and tag management network elements can also be many-to-one. For example, access and mobility management network element #a and access and mobility management network element #b can be associated with tag management network element #a. The access network device can receive identification association information #a from access and mobility management network element #a, which may include: access and mobility management network element #a is associated with tag management network element #a; the access network device can receive identification association information #b from access and mobility management network element #b, which may include: access and mobility management network element #b is associated with tag management network element #a. In this case, the access network device can select any tag management network element associated with tag management network element #a, such as access and mobility management network element #a or access and mobility management network element #b, based on a first identifier (such as the identifier of tag management network element #a) and identification association information #a or identification association information #b, without limitation.

[0208] The correspondence between access and mobility management network elements (AMLEs) and tag management network elements (TANs) can also be many-to-many. For example, AMLEs #c and #d can be associated with TANs #b and #c. The access network device can receive identification association information #c from AMLEs #c, which may include AMLEs #c, associated with TANs #b and #c. Similarly, the access network device can receive identification association information #d from AMLEs #d, which may include AMLEs #d, associated with TANs #b and #c. In this case, the access network device can select any AMLE associated with TANs #b, such as AMLEs #c or #d, based on a first identifier (e.g., the identifier of TANs #b) and identification association information #c or #d, without limitation.

[0209] It is understood that the first access and mobility management network element can also update or modify the identifier association information. For example, if the connection between the first access and mobility management network element and one or more established tag management network elements is released, or if the first access and mobility management network element establishes a connection with a new tag management network element, the first access and mobility management network element can send the updated identifier association information to the access network device. This can be done through an update request message, etc. The access network device can save or store the updated identifier association information. That is, the access network device can update the correspondence between the first access and mobility management network element and the tag management network element for subsequent determination of the service request message from the terminal device to be forwarded to the appropriate access and mobility management network element. This application does not limit this aspect.

[0210] Based on the above introduction, the specific implementation of the access network device obtaining the identifier association information will be described below.

[0211] In one possible design, the terminal device is an IoT device. Before the access network device receives the first message from the terminal device, the above method embodiment may further include:

[0212] The access network device sends its capability information to the first access and mobility management network element. Correspondingly, the first access and mobility management network element receives the capability information of the access network device sent by the access network device.

[0213] The first access and mobility management network element sends identification association information to the access network device. Correspondingly, the access network device receives identification association information returned by the first access and mobility management network element based on the access network device's capability information.

[0214] In cases where the terminal device is an IoT device, such as an A-IoT device, passive device, semi-passive device, semi-active device, or active IoT device, the access network device and subsequent access and mobility management network elements (such as the first access and mobility management network element) and tag management network elements (such as the first tag management network element) need to support IoT device access, or in other words, be able to support IoT services. In this case, the access network device can send its capability information to the first access and mobility management network element.

[0215] For example, during the process of establishing a connection between the access network device and the first access and mobility management network element, the access network device can send a connection establishment request message to the first access and mobility management network element, which can be denoted as connection establishment request message #1, to request the establishment of a connection with the first access and mobility management network element. This connection establishment request message #1 may include the capability information of the access network device to indicate that the access network device supports the access of Internet of Things (IoT) devices. In other words, the capability information of the access network device can be carried in the connection establishment request message #1, that is, carried in an existing message to reduce implementation difficulty, or it can be carried in a new message to improve implementation flexibility; there is no limitation on this.

[0216] When the first access and mobility management network element determines that the access network device supports IoT device access, the first access and mobility management network element can send identification association information to the access network device. For example, when the first access and mobility management network element receives a connection establishment request message #1 from the access network device, the first access and mobility management network element can send a connection establishment response message to the access network device, which can be denoted as connection establishment response message #1, to indicate that a connection has been established between the access network device and the first access and mobility management network element. This connection establishment response message #1 can include the identification association information; in other words, the capability information of the access network device can be carried in the connection establishment request message #1, i.e., carried in an existing message to reduce implementation difficulty, or it can be carried in a new message to improve implementation flexibility, without limitation. In this way, the access network device can obtain the identification association information and save or store it. It is understood that if the access network device does not support IoT device access, the first access and mobility management network element does not need to send the identification association information back to the access network device.

[0217] The following section describes the specific implementation of the first access and mobility management network element in obtaining the identifier association information.

[0218] In one possible design scheme, the above method embodiment may further include:

[0219] The first tag management network element sends a message, such as message #A, to the first access and mobility management network element. Correspondingly, the first access and mobility management network element receives message #A from the first tag management network element.

[0220] Message #A can include the identifier of the first tag management network element, or any other possible parameters, without limitation. Thus, the first access and mobility management network element can automatically record the identifier of the first tag management network element based on message #A. Based on this identifier, the first access and mobility management network element can determine that communication (connection establishment) is possible between itself and the first access and mobility management network element. Similarly, the first access and mobility management network element can also record the identifiers of other tag management network elements communicating with it in this way. Therefore, based on the recorded identifiers, the first access and mobility management network element can determine the identifier association information, meaning it dynamically obtains this identifier association information.

[0221] It is understood that the first access and mobility management network element can also obtain the identifier association information through any other possible means. For example, the first access and mobility management network element can query other network elements, such as the NRF, for a list of tag management network element identifiers that have a service relationship with the first access and mobility management network element to obtain the identifier association information; or, for example, the identifier association information can also be pre-configured or pre-defined, and the first access and mobility management network element can send the pre-configured or pre-defined identifier association information to the access network device, i.e., static configuration, which is not limited in this embodiment of the application.

[0222] In this way, the access network device can obtain the topology information of the tag management network element, and thus route to the correct first identifier based on the first identifier of the AS layer.

[0223] It is understandable that the access network device can also obtain the identification association information corresponding to other access and mobility management network elements. The implementation principle is similar to that of the access network device, which can also obtain the identification association information corresponding to the first access and mobility management network element (i.e., the identification association information #1 mentioned above). It can be understood by reference and will not be elaborated further.

[0224] The naming of the above-mentioned identifier association information is only an example. The identifier association information can be replaced with any other possible names without limitation.

[0225] S504, the access network device sends a first message to the first access and mobility management network element. Correspondingly, the first access and mobility management network element receives the first message from the access network device.

[0226] The first message may include a first identifier and a service request message. That is, the access network device can encapsulate the NAS layer service request message and the first identifier into a first message, and send the first message to the first access and mobility management network element determined in step S503 above through the N2 interface.

[0227] In one possible design, the access network device is assigned a second identifier.

[0228] The second identifier can be used to identify the terminal device. The first message may also include the second identifier, that is, the second identifier can be assigned by the access network device and used to identify the terminal device. This second identifier can be a temporary identifier assigned by the access network device and used to identify the terminal device, which can be denoted as RAN NG AP ID#2. RAN NG AP ID#2 can be an identifier that uniquely identifies the terminal device through the NG interface within the access network device range. It can be understood that this RAN NG AP ID#2 can be the same as or different from RAN_NG AP_ID#1 in step S501 above, without limitation.

[0229] It should be understood that if one tag management network element corresponds to multiple access and mobility management network elements (including the first access and mobility management network element), the access network device can also select one of the access and mobility management network elements according to a strategy, such as random selection or load sharing, i.e., the aforementioned first access and mobility management network element; or, the access network device can also select multiple access and mobility management network elements. In this case, when forwarding (service request) messages from terminal devices, the access network device can carry a unique sequence number for each message. This sequence number is used to identify that the messages from multiple access and mobility management network elements are the same when the first tag management network element receives messages from multiple access and mobility management network elements, thereby discarding the same message that arrives later, thus avoiding the first tag management network element from repeatedly processing the same service request. It can be understood that the sequence number is incremental, and different messages carry different sequence numbers; or the sequence number can also be a timestamp, etc., without limitation. For ease of understanding, this application embodiment uses the access network device selecting the first access and mobility management network element as an example for introduction, and will not be elaborated further thereafter.

[0230] It is understood that the naming of the first message above is only an example, and the first message can be replaced with any other possible name without limitation.

[0231] In step S505, the first access and mobility management network element sends a second message to the first label management network element based on the first identifier. Correspondingly, the first label management network element receives the second message from the first access and mobility management network element.

[0232] The second message may include a service request message. The first access and mobility management network element can determine the first label management network element based on the first identifier carried in the first message, and forward the NAS layer service request message to the first label management network element through the second message (Nx interface).

[0233] In one possible design, the second message may also include a second identifier and a third identifier.

[0234] The second identifier can be the aforementioned RAN NG AP ID#2. The third identifier can be used to identify the access network device and can be denoted as RAN ID or any other possible name, without limitation. For ease of understanding, this application embodiment uses RAN ID as the third identifier for subsequent description, and will not be elaborated further. The third identifier can be sent by the access network device to the first access and mobility management network element when establishing a connection with the first access and mobility management network element. At this time, the first access and mobility management network element can encapsulate the second identifier, the third identifier, and the aforementioned service request message into a second message and send it to the first tag management network element through the Nx interface.

[0235] It is understood that the naming of the second message above is only an example, and the second message can be replaced with any other possible name without limitation.

[0236] S506, the first tag management network element determines whether to provide communication services to the terminal equipment based on the temporary identifier.

[0237] The first tag management network element can determine that the service request message is a request message from the terminal device (authentication passed) based on the temporary identifier in the service request message. At this time, the first tag management network element can determine to provide communication services to the terminal device.

[0238] In summary, the terminal device can send a first identifier and a service request message (including the temporary identifier) ​​to the access network device based on the temporary identifier assigned to it by the first tag management network element (including the first identifier used to identify the first tag management network element). The access network device can determine the first access and mobility management network element based on the first identifier and the identifier association information, which includes the association relationship between the first access and mobility management network element and the tag management network element (including the first tag management network element), so that the access network device can forward the service request message and the first identifier to the first access and mobility management network element through the first message. The first access and mobility management network element can determine the first tag management network element based on the first identifier. This allows the first access and mobility management network element to forward service request messages to the first tag management network element that needs to provide communication services via a second message. This ensures that the access network equipment can select a suitable access and mobility management network element (such as the first access and mobility management network element), and that the access and mobility management network element can select a suitable tag management network element (such as the first tag management network element). This enables the access network equipment and the first access and mobility management network element to send the service request messages of the terminal equipment to the appropriate first tag management network element when the first tag management network element assigns a temporary identifier to the terminal equipment, thereby meeting the needs of the terminal equipment.

[0239] In conjunction with the above embodiments, one possible design scheme for the above method embodiments may further include:

[0240] The first tag management network element sends a response message for the second message to the first access and mobility management network element. Correspondingly, the first access and mobility management network element receives a response message for the second message from the first tag management network element.

[0241] The first access and mobility management network element sends a response message of the first message to the access network device based on the third identifier. Correspondingly, the access network device receives the response message of the first message from the first access and mobility management network element.

[0242] The access network device sends a response message to the terminal device based on the second identifier. Correspondingly, the terminal device receives a response message from the access network device regarding the service request message.

[0243] The response message to the second message may include a response message to the service request message, a second identifier, and a third identifier. The response message to the second message can be used to indicate that the first tag management network element has successfully received the second message, etc., without limitation. Similarly, the response message to the service request message can be used to indicate that the first tag management network element has successfully received the service request message and has provided the communication service to the terminal device, etc., without limitation. It can be understood that the response message to the service request message is similar to the service request message, representing a NAS message exchanged between the terminal device and the first tag management network element. The access network device and the access and mobility management network element (such as the aforementioned first access and mobility management network element) forward the response message to the service request message.

[0244] The response message of the first message may include the response message of the service request message and the second identifier. The response message of the first message may be used to indicate that the first access and mobility management network element has successfully received the first message, etc., without limitation.

[0245] After the first tag management network element provides communication services to the terminal device based on the service request message, it can encapsulate the response message of the service request message, the second identifier, and the third identifier into a response message of the second message, and send the response message of the second message to the first access and mobility management network element through the Nx interface. The first access and mobility management network element can determine the access network device based on the third identifier, and encapsulate the response message of the service request message and the second identifier into a response message of the first message, and send the response message of the first message to the access network device through the N2 interface.

[0246] In this way, the first access and mobility management network element can directly route to the access network device based on the second identifier, enabling the first access and mobility management network element to achieve stateless forwarding without requiring the context of the terminal device. The access network device can determine the terminal device based on the second identifier and send a response message of the service request message to the terminal device through the UU interface, thus forwarding the response message of the service request message to the terminal device. It is understood that the access network device can also send any other possible signaling to the terminal device without limitation.

[0247] It is understandable that the first access and mobility management network elements can also support stateful forwarding without limitation. The naming of the response messages for the second message, the first message, and the service request message mentioned above is merely an example and is not intended to be limiting.

[0248] For example, Figure 6 is a schematic flowchart of the communication method provided in an embodiment of this application. This method can be applied to the interaction between terminal devices, access network devices, access and mobility management network elements, and tag management network elements in the above-described communication system. For ease of understanding, the communication method will be described below using the first access and mobility management network element and the first tag management network element as examples.

[0249] As shown in Figure 6, the flow of this communication method is as follows:

[0250] In S601, during the terminal device registration process, the first tag management network element assigns a temporary identifier and sends it to the terminal device. The terminal device then obtains the temporary identifier.

[0251] The temporary identifier may include a first identifier, which can be used to identify the first label management network element. The first identifier may be similar to the GUAMI mentioned above, indicating that the temporary identifier is assigned by the first label management network element. The temporary identifier may also include a unique identifier for the terminal device within the first label management network element. This unique identifier for the terminal device within the first label management network element may be similar to the 5G-TMSI mentioned above, and can be understood by reference without further explanation.

[0252] The following is a detailed explanation of this step.

[0253] In one possible design, the first tag management network element receives a registration request message from the first access and mobility management network element. Correspondingly, the first tag management network element receives the registration request message from the first access and mobility management network element.

[0254] In response to the registration request message, the first tag management network element assigns a temporary identifier to the terminal device.

[0255] The first tag management network element sends a temporary identifier to the terminal device. Correspondingly, during the terminal device registration process, the terminal device receives the temporary identifier assigned by the first tag management network element.

[0256] It is understandable that the implementation principle can be referred to in the relevant introduction in step S501 above, and will not be repeated here.

[0257] The following section provides a detailed introduction to how the first tag management network element assigns temporary identifiers to terminal devices.

[0258] In one possible design, the first identifier can also be used to identify the first access and mobility management network element; before the first access and mobility management network element receives the first message from the access network device, the above-described method embodiments may further include:

[0259] The first access and mobility management network element sends a fourth identifier to the first label management network element. Correspondingly, the first label management network element receives the fourth identifier from the first access and mobility management network element.

[0260] The first label management network element uses the fourth identifier to assign temporary identifiers.

[0261] The fourth identifier can be used to identify the first access and mobility management network element (AMI), and it can also be used by the first tag management network element (TMI) to allocate temporary identifiers for terminal devices. That is, the first AMI can allocate or reserve its own identifier, the fourth identifier, to the first tag management network element, which can then use this fourth identifier to allocate temporary identifiers for terminal devices. In other words, the first identifier can be generated by the first tag management network element using the fourth identifier allocated by the first AMI. Therefore, this first identifier can be used to identify both the first AMI and the first tag management network element. Alternatively, the first identifier can be the identifier of the first AMI, and some fields occupied by the first identifier can be used to identify the first tag management network element, as detailed below.

[0262] For example, the structure of the first identifier can be the same as that of the AMF identifier. As described above, taking the AMF identifier as GUAMI as an example, GUAMI can be composed of MCC, MNC, and AMFI. The AMFI can include: an AMF region ID field, an AMF set ID field, and an AMF pointer field. The first identifier can be similar to this GUAMI. One or more of the fields in the AMF region ID, AMF set ID, and AMF pointer fields of the GUAMI can be used to identify the label management network element (the label management network element that can establish a connection with the first access and mobility management network element). That is, the access and mobility management network element (i.e., the aforementioned first access and mobility management network element) reserves an AMF identifier for the label management network element (i.e., the aforementioned first label management network element), and the TMF can directly use the AMF identifier to identify the TMF. It can be understood that a physical AMF can be assigned multiple AMF identifiers, some of which are used to identify the AMF itself, and others are used to identify the TMF. It is understandable that if any one of the AMF region ID, AMF pointer, or AMF set ID fields has a different value, it represents a different AMF or TMF. The following example (using AMF#1 and AMF#2 as examples) will illustrate this further.

[0263] For example, the AMF region ID field can have values ​​ranging from #0 to #255, the AMF set ID field can have values ​​ranging from #0 to #1023, and the AMF pointer field can have values ​​ranging from #0 to #63.

[0264] Case 1: The AMF region ID field can be set to values ​​#0-#251 to identify AMF, and values ​​#252-#256 to identify TMF.

[0265] It is understandable that in Case 1, for the AMF identifier whose AMF region ID field takes values ​​from #252 to #256, the values ​​of the AMF set ID field and the AMF pointer field can be used to identify the TMF regardless of their values. That is, if any of the following fields has a different value, it represents a different TMF: AMF region ID (values ​​from #252 to #255), AMF set ID (values ​​from #0 to #1023), AMF pointer (values ​​from #0 to #63), and AMF set ID (values ​​from #0 to #1023).

[0266] For example, the AMF region ID field can take values ​​#1 and #252-#253 to identify AMF #1, and values ​​#2 and #254-#255 to identify AMF #2. Assume that values ​​#252-#253 in the AMF region ID field are used to identify the TMF associated with AMF #1, and values ​​#254-#255 in the AMF region ID field are used to identify the TMF associated with AMF #2.

[0267] At this point, if any of the following fields has a different value: the AMF region ID field (values ​​#252-#253), the AMF set ID field (values ​​#0-#1023), or the AMF pointer field (values ​​#0-#63), it indicates a different TMF associated with AMF#1; if any of the following fields has a different value: the AMF region ID field (values ​​#254-#255), the AMF set ID field (values ​​#0-#1023), or the AMF pointer field (values ​​#0-#63), it indicates a different TMF associated with AMF#2.

[0268] For example, the AMF region ID field takes the value #a1 (a1 belongs to 252-253), the AMF set ID field takes the value #b1 (b1 belongs to 0-1023), and the AMF pointer field takes the value #c1 (c1 belongs to 0-63). In this case, if any of the fields a1, b1, and c1 has a different value, it means that there is a different TMF associated with AMF#1.

[0269] Taking AMF#1 as the first access and mobility management network element and TMF#1 as the first tag management network element as an example, assume that AMF#1 reserves the values ​​#252 for the AMF region ID field, #1 for the AMF set ID field, and #1 for the AMF pointer field to TMF#1; and reserves the values ​​#252 for the AMF region ID field, #1 for the AMF set ID field, and #2 for the AMF pointer field to TMF#2, ..., and so on.

[0270] At this point, TMF#1 can use the values ​​of AMF region ID field #252, AMF set ID field #1, and AMF pointer field #1 to assign a temporary identifier to the terminal device. In other words, the first identifier has the values ​​of AMF region ID field #252, AMF set ID field #1, and AMF pointer field #1.

[0271] Case 2: The AMF set ID field can take values ​​#0-#1019 to identify AMF, and values ​​#1020-#1023 to identify TMF.

[0272] It is understandable that in scenario 2, for AMF identifiers with values ​​ranging from #1000 to #1023 in the AMF set ID field, the value of the AMF pointer can be used to identify the TMF regardless of its value. That is, if either the AMF set ID field (values ​​from #1020 to #1023) or the AMF pointer field (values ​​from #0 to #63) has a different value, it represents a different TMF. It is also understandable that the value of the AMF region ID field is not restricted here.

[0273] Assume that the AMF region ID of AMF#1 is value #a2 (a2 belongs to 0-255), and the AMF region ID of AMF#2 is value #a3 (a3 belongs to 0-255). a2 and a3 can be the same or different, without restriction. In this case, the AMF region ID value of #a2, and the AMF set ID field values ​​of #1, #1020-#1021 can be used to identify AMF#1; the AMF region ID value of #a3, and the AMF set ID field values ​​of #2, #1022-#1023 can be used to identify AMF#2.

[0274] Assume the AMF region ID is value #a2, and the AMF set ID field contains values ​​#1020-#1021 to identify the TMF associated with AMF#1; the AMF region ID is value #a3, and the AMF set ID field contains values ​​#1022-#1023 to identify the TMF associated with AMF#2. In this case, if any value in the AMF set ID (values ​​#1020-#1021) or the AMF pointer field (values ​​#0-#63) differs, it indicates a different TMF associated with AMF#1; similarly, if any value in the AMF set ID (values ​​#1022-#1023) or the AMF pointer field (values ​​#0-#63) differs, it indicates a different TMF associated with AMF#2.

[0275] For example, the AMF region ID field takes the value #a2, the AMF set ID field takes the value #b2 (b2 belongs to 1020-1021), and the AMF pointer field takes the value #c2 (c2 belongs to 0-63). In this case, if the value of any field in b2 and c2 is different, it means that there is a different TMF associated with AMF#1.

[0276] Taking AMF#1 as the first access and mobility management network element and TMF#1 as the first tag management network element as an example, assume that AMF#1 reserves the value of AMF region ID field as value #1 (i.e., a2 = 1), the value of AMF set ID field as value #1020, and the value of AMF pointer field as value #1 for TMF#1; and reserves the value of AMF region ID field as value #1, the value of AMF set ID field as value #1020, the value of AMF pointer field as value #2 for TMF#2, ..., and so on.

[0277] At this point, TMF#1 can use the values ​​of AMF region ID field #1, AMF set ID field #1020, and AMF pointer field #1 to assign a temporary identifier to the terminal device. In other words, the first identifier has the values ​​of AMF region ID field #1, AMF set ID field #1020, and AMF pointer field #1.

[0278] Case 3: The AMF pointer field can be set to values ​​#0-#59 to identify AMF, and values ​​#60-#63 to identify TMF.

[0279] In scenario 3, assume that the AMF region ID of AMF#1 is #a4 (a4 belongs to 0-255), and the AMF set ID of AMF#1 is #b3 (b3 belongs to 0-1023); the AMF region ID of AMF#2 is #a5 (a5 belongs to 0-255), and the AMF set ID of AMF#2 is #b4 (b4 belongs to 0-1023). Here, a4 and a5 can be the same or different, without restriction; b3 and b4 can be the same or different, without restriction.

[0280] In this case, the AMF region ID can be valued as #a4, the AMF set ID field as #b3, the AMF pointer field as #1, and values ​​#60-#61 can be used to identify AMF#1; the AMF region ID can be valued as #a5, the AMF set ID field as #b4, the AMF pointer field as #2, and values ​​#62-#63 can be used to identify AMF#2.

[0281] Assume that the AMF region ID is value #a4, the AMF set ID field is value #b3, and the AMF pointer field is value #60-#61 to identify the TMF associated with AMF #1; the AMF region ID is value #a5, the AMF set ID field is value #b4, and the AMF pointer field is value #62-#63 to identify the TMF associated with AMF #2.

[0282] Taking AMF#1 as the first access and mobility management network element and TMF#1 as the first tag management network element, assuming that AMF#1 reserves the values ​​of AMF region ID field #1 (i.e., a4=1), AMF set ID field #1 (i.e., b3=1), and AMF pointer field #60 for TMF#1; and reserves the values ​​of AMF region ID field #1, AMF set ID field #1, and AMF pointer field #61 for TMF#2, ..., and so on.

[0283] At this point, TMF#1 can use the values ​​of AMF region ID field #1, AMF set ID field #1, and AMF pointer field #60 to assign a temporary identifier to the terminal device. In other words, the first identifier has the values ​​of AMF region ID field #1, AMF set ID field #1, and AMF pointer field #60.

[0284] It is understood that scenarios 1-3 above are merely examples and are not limited to them. For instance, if subsequent standard protocols define other access management network elements to replace AMF, or define new access network element identifiers, a similar number segment reservation method can be used to reserve identifiers for tag management network elements. The implementation principle is similar and can be referenced for understanding; it will not be elaborated further. The AMF region ID field, AMF set ID field, and AMF pointer field mentioned above can also have any other possible values, without limitation.

[0285] Based on the above introduction, the first access and mobility management network element stores the correspondence between the first access and mobility management network element identifier and the tag management network element (including the first tag management network element). For example, in case 1 above, taking AMF#1 as the first access and mobility management network element, AMF#1 can store the following correspondences: AMF region ID field value is #252, AMF set ID field value is #1, AMF pointer field value is #1 corresponding to TMF#1; and AMF region ID field value is #252, AMF set ID field value is #1, AMF pointer field value is #2 corresponding to TMF#2. Similarly, in case 2 above, AMF#1 can store the following correspondences: AMF region ID field value is #1, AMF set ID field value is #1020, AMF pointer field value is #1 corresponding to TMF#1; and AMF region ID field value is #1, AMF set ID field value is #1020, AMF... The pointer field takes the value #2, corresponding to TMF #2. As in case 3 above, AMF #1 can store the following: the AMF region ID field takes the value #1, the AMF set ID field takes the value #1, the AMF pointer field takes the value #60, corresponding to TMF #1; and the AMF region ID field takes the value #1, the AMF set ID field takes the value #1, the AMF pointer field takes the value #61, corresponding to TMF #2, etc.

[0286] It is understood that the correspondence between the first access and mobility management network element identifier and the tag management network element can be pre-configured, pre-defined, or the identifier allocated or reserved by the first access and mobility management network element to the tag management network element, such as the identifier recorded or stored when sending the fourth identifier to the first tag management network element, etc., without limitation. The above is an example of the first access and mobility management network element reserving an identifier for the first tag management network element. Other access and mobility management network elements can use the same implementation process to reserve identifiers for their corresponding (connection-established) tag management network elements, so that these tag management network elements can use the identifiers reserved for themselves to allocate temporary identifiers to terminal devices, which will not be elaborated further.

[0287] After receiving the registration request message from the first access and mobility management network element, the first tag management network element can also initiate a security process to the terminal device as needed. The implementation process can be referred to the relevant description in step S601 above, and will not be repeated here.

[0288] It is understood that the specific descriptions of the temporary identifier and the first identifier can be found in the relevant content of step S501 above, and will not be repeated here. The naming of the above registration request message, registration acceptance message, temporary identifier, first identifier, and fourth identifier is only an example. The registration request message, registration acceptance message, temporary identifier, first identifier, and fourth identifier can also be replaced with any other possible names, without limitation.

[0289] In step S602, the terminal device sends a first identifier and a service request message to the access network device based on the temporary identifier. Correspondingly, the access network device receives the first identifier and service request message from the terminal device.

[0290] The service request message can be used to request communication services from the first tag management network element, and the service request message may contain a temporary identifier. After the terminal device receives the temporary identifier assigned by the first tag management network element, it can obtain the first identifier based on the temporary identifier, which can be used to identify the first tag management network element.

[0291] When a terminal device has a subsequent service request, it can send a service request message to the access network device through the UU interface to request communication services from the first tag management network element. This service request message may include a temporary identifier, which the first tag management network element can use to determine whether to provide communication services to the terminal device (i.e., verify the terminal device's identity). For a detailed description of this service request message, please refer to the relevant description in step S502 above; it will not be repeated here.

[0292] The first identifier can be an identifier applicable to the AS layer, that is, the first identifier can be carried in the AS message so that the access network device can subsequently parse and obtain the first identifier at the AS layer; the service request message can be a NAS message, and the access network device and the access and mobility management network element (such as the first access and mobility management network element mentioned above) forward the service request message.

[0293] It is understood that the naming of the above business request messages is only an example, and the business request messages can be replaced with any other possible names without limitation.

[0294] S603, the access network device determines the first access and mobility management network element based on the first identifier.

[0295] The first identifier can also be used to identify the first access and mobility management network element. That is, the first identifier can identify both the first access and mobility management network element and the first label management network element. In this way, the access network device can directly determine the appropriate first access and mobility management network element based on the first identifier of the AS layer.

[0296] For example, taking the first access and mobility management network element as AMF#1, based on the above situation 1, AMF#1 can be determined according to the value of AMF region ID field #252, AMF set ID field #1, and AMF pointer field #1 in the first identifier; based on the above situation 2, AMF#1 can be determined according to the value of AMF region ID field #1, AMF set ID field #1020, and AMF pointer field #1 in the first identifier; based on the above situation 3, AMF#1 can be determined according to the value of AMF region ID field #1, AMF set ID field #1, and AMF pointer field #60 in the first identifier.

[0297] It is understood that the above implementation is only an example, and the access network device can also determine the first access and mobility management network element based on the first identifier through other implementation processes, without limitation.

[0298] S604, the access network device sends a first message to the first access and mobility management network element. Correspondingly, the first access and mobility management network element receives the first message from the access network device.

[0299] The first message may include a service request message and a first identifier. That is, the access network device can encapsulate the NAS layer service request message and the first identifier into a first message, and send the first message to the first access and mobility management network element determined in step S603 above through the N2 interface.

[0300] In one possible design, the access network device is assigned a second identifier.

[0301] The second identifier can be used to identify the terminal device. The first message may also include the second identifier, that is, the second identifier can be assigned by the access network device and used to identify the terminal device. This second identifier can be a temporary identifier assigned by the access network device and used to identify the terminal device. For ease of understanding, this application embodiment uses RAN NG AP ID#2 as an example for subsequent description, and will not elaborate further.

[0302] It is understood that the specific description of the second identifier can be found in the relevant description in step S504 above, and will not be repeated here. The naming of the first message above is only an example, and the first message can be replaced with any other possible name without limitation.

[0303] S605, the first access and mobility management network element sends a second message to the first label management network element based on the first identifier. Correspondingly, the first label management network element receives the second message from the first access and mobility management network element.

[0304] The second message may include a business request message.

[0305] The first access and mobility management network element can determine the first tag management network element based on the first identifier carried in the first message. For example, based on the relevant description in step S601 above, the first access and mobility management network element stores the correspondence between the first access and mobility management network element identifier and the tag management network element (including the first tag management network element). The first access and mobility management network element can determine the first tag management network element based on the stored correspondence and the first identifier, and forward the NAS layer service request message to the first tag management network element through the second message (Nx interface).

[0306] For example, taking the first access and mobility management network element as AMF#1, based on the above situation 1, taking the first access and mobility management network element as AMF#1, AMF#1 stores the relationship that the AMF region ID field value is #252, the AMF set ID field value is #1, and the AMF pointer field value is #1, corresponding to TMF#1, and the AMF region ID field value is #252, the AMF set ID field value is #1, and the AMF pointer field value is #2, corresponding to TMF#2. At this time, AMF#1 can determine its correspondence with TMF#1 based on the AMF region ID field value is #252, the AMF set ID field value is #1, and the AMF pointer field value is #1 in the first identifier; as in the above situation 2, AMF#1 stores the AMF region ID field value is #1, the AMF set ID field value is #1020, and the AMF pointer field value is #1, and the AMF pointer field value is #252, corresponding to TMF#2. The pointer field has a value of #1 corresponding to TMF#1, and the AMF region ID field has a value of #1, the AMF set ID field has a value of #1020, and the AMF pointer field has a value of #2, all corresponding to TMF#2. In this case, AMF#1 can be determined to correspond to TMF#1 based on the values ​​of AMF region ID, AMF set ID, and AMF pointer in the first identifier. For example, in case 3 above, AMF#1 stores the relationships of AMF region ID, AMF set ID, and AMF pointer corresponding to #60, and AMF#2 corresponding to TMF#2. In this case, AMF#1 can be determined to correspond to TMF#2 based on the values ​​of AMF region ID, AMF set ID, and AMF pointer in the first identifier. The ID field takes the value #1, the AMF set ID field takes the value #1, and the AMF pointer field takes the value #60, thus confirming their correspondence with TMF#1. In this way, AMF#1 can determine TMF#1 based on the first identifier.

[0307] In one possible design, the second message may also include a second identifier and a third identifier.

[0308] The second identifier can be the aforementioned RAN NG AP ID#2. The third identifier can be used to identify the access network device and can be denoted as RAN ID, or any other possible name, without limitation. For ease of understanding, this embodiment uses RAN ID as the third identifier for subsequent description, and will not be repeated. For a detailed description of the third identifier, please refer to the relevant description in step S505 above, and will not be repeated. At this time, the first access and mobility management network element can encapsulate the second identifier, the third identifier, and the aforementioned service request message into a second message, and send it to the first tag management network element through the Nx interface.

[0309] It is understood that the naming of the second message above is only an example, and the second message can be replaced with any other possible name without limitation.

[0310] S606, the first tag management network element determines to provide communication services to the terminal equipment based on the temporary identifier.

[0311] It is understandable that the implementation principle of this step can be referred to in the relevant introduction in step S506 above, and will not be repeated here.

[0312] In summary, the first label management network element can use the fourth identifier allocated by the first access and mobility management network element to allocate a temporary identifier for the terminal device. This temporary identifier may include the first identifier, which can identify either the first access and mobility management network element or the first label management network element. The terminal device can send a first identifier and a service request message (including the temporary identifier) ​​to the access network device based on the temporary identifier allocated to it by the first label management network element. The access network device can directly determine the first access and mobility management network element based on the first identifier, so that the access network device can forward the service request message and the first identifier to the first access and mobility management network element via a first message. The first access and mobility management network element can determine the first tag management network element based on the correspondence between the first identifier and the tag management network element. This allows the first access and mobility management network element to forward service request messages to the first tag management network element that needs to provide communication services via a second message. In this way, it can be ensured that the access network device can select a suitable access and mobility management network element (such as the first access and mobility management network element), and the access and mobility management network element can select a suitable tag management network element (such as the first tag management network element). This enables the access network device and the first access and mobility management network element to send the service request message of the terminal device to the appropriate first tag management network element when the first tag management network element assigns a temporary identifier to the terminal device, so as to meet the needs of the terminal device.

[0313] In conjunction with the above embodiments, one possible design scheme for the above method embodiments may further include:

[0314] The first tag management network element sends a response message for the second message to the first access and mobility management network element. Correspondingly, the first access and mobility management network element receives a response message for the second message from the first tag management network element.

[0315] The first access and mobility management network element sends a response message of the first message to the access network device based on the third identifier. Correspondingly, the access network device receives the response message of the first message from the first access and mobility management network element.

[0316] The access network device sends a response message to the terminal device based on the second identifier. Correspondingly, the terminal device receives a response message from the access network device regarding the service request message.

[0317] The response message to the second message may include the response message to the service request message, a second identifier, and a third identifier. The response message to the first message may include the response message to the service request message and the second identifier.

[0318] It is understood that the implementation process can be referred to the relevant content in the method embodiment shown in Figure 5 above, and will not be repeated here.

[0319] For example, Figure 7 is a schematic flowchart of the communication method provided in this application embodiment. This method can be applied to the interaction between terminal devices, access network devices, access and mobility management network elements, and tag management network elements in the above-described communication system. For ease of understanding, the following description uses a first access and mobility management network element, a second access and mobility management network element, and a first tag management network element as examples to illustrate this communication method.

[0320] As shown in Figure 7, the flow of this communication method is as follows:

[0321] S701, the access network device sends its capability information to the first access and mobility management network element. Correspondingly, the first access and mobility management network element receives the capability information of the access network device sent by the access network device.

[0322] The capability information of the access network device (which can be referred to as access network device #1) can be used to indicate that the access network device supports IoT services, or in other words, that the access network device supports the access of IoT devices. For example, the access network device can handle services from A-IoT devices, passive devices, semi-passive devices, semi-active devices, passive IoT devices, etc., or support the access of A-IoT devices, passive devices, semi-passive devices, semi-active devices, passive IoT devices, etc.

[0323] For example, during the process of establishing a connection between the access network device and the first access and mobility management network element, the access network device can send a connection establishment request message to the first access and mobility management network element, which can be denoted as connection establishment request message #3, to request to establish a connection with the first access and mobility management network element. This connection establishment request message #3 may include the capability information of the access network device to indicate that the access network device supports A-IoT services. In other words, the capability information of the access network device can be carried in the connection establishment request message #3, that is, carried in an existing message to reduce implementation difficulty, or it can be carried in a new message to improve implementation flexibility; there is no limitation on this.

[0324] It is understandable that the connection establishment request message #3 mentioned above may also include the identifier of the access network device, without limitation.

[0325] S702, the first access and mobility management network element determines the second access and mobility management network element based on the capability information of the access network equipment.

[0326] After receiving the capability information of the access network device, the first access and mobility management network element can, according to a certain strategy, instruct the access network device to redirect to the second access and mobility management network element. This allows the access network device to select a suitable default access and mobility management network element, i.e., the second access and mobility management network element processes the request from the (IoT) terminal device. This will be described in detail below.

[0327] In one possible design, the first access and mobility management network element determines the second access and mobility management network element based on the first condition and the capability information of the access network equipment.

[0328] The first condition can be that the first access and mobile management network element does not support IoT services.

[0329] In other words, if the first access and mobility management network element does not support IoT services, or in other words, does not support the access of IoT devices, then the first access and mobility management network element can select an access and mobility management network element that supports IoT services, such as a second access and mobility management network element (which can be one or more). For example, the first access and mobility management network element can be pre-configured with the capability information of other access and mobility management network elements (including the second access and mobility management network element), i.e., whether they support IoT services. Alternatively, the first access and mobility management network element can also exchange its own capability information with other access and mobility management network elements (including the second access and mobility management network element), i.e., whether they support IoT services, and store the capability information of the other access and mobility management network elements. In this way, the first access and mobility management network element can select the second access and mobility management network element based on the pre-configured capability information of other access and mobility management network elements, or the stored capability information of other access and mobility management network elements.

[0330] The first condition also allows for support of IoT services for the first access and mobility management network elements, but does not support IoT services corresponding to access network devices.

[0331] In other words, the first access and mobility management network element can support IoT services, or in other words, it can support the access of IoT devices, but it does not support IoT services from the access network device, i.e., the access network device #1. For example, the first access and mobility management network element does not support the access of terminal devices accessing through access network device #1, or in other words, it does not process the services of terminal devices forwarded through access network device #1. In this case, the first access and mobility management network element can select a specified access and mobility management network element, and then the second access and mobility management network element processes the requests of the terminal devices.

[0332] It is understood that the first condition may also include any other possible conditions, and this application embodiment does not limit this.

[0333] In one possible design, the first access and mobility management network element can also determine the tag management network element based on its capability information, i.e., whether it supports IoT services. This first tag management network element can establish a connection with the previously determined second access and mobility management network element. This first tag management network element can support IoT services, or in other words, support the access of IoT devices. This allows the second access and mobility management network element to subsequently select a suitable default tag management network element, i.e., the first tag management network element, to process the request messages from the (IoT) terminal devices. The implementation process of the first access and mobility management network element determining the first tag management network element is similar to the implementation process of the first access and mobility management network element determining the second access and mobility network element, and can be understood by reference; it will not be elaborated further.

[0334] S703, the first access and mobility management network element sends indication information to the access network device. Correspondingly, the access network device receives the indication information from the first access and mobility management network element.

[0335] The indication information may include the identifiers of the second access and mobility management network elements.

[0336] The first access and mobility management network element (AML) can send the identifier of the redirected second AML to the access network device, instructing the access network device to redirect from the first AML to the second AML. The access network device can store the identifier of the redirected second AML for subsequent forwarding of terminal device request messages to the second AML.

[0337] In one possible design, the indication information may further include the identifier of the first tag management network element, which supports IoT services. That is, the first access and mobility management network element can also send the identifier of the selected first tag management network element to the access network device via the indication information.

[0338] For example, when the first access and mobility management network element receives the connection establishment request message #3 from the access network device, the first access and mobility management network element can send a connection establishment response message to the access network device, which can be denoted as connection establishment response message #3, to indicate that the access network device and the first access and mobility management network element have established a connection. This connection establishment response message #3 may include the aforementioned indication information; in other words, the aforementioned indication information can be carried in the connection establishment response message #3, that is, carried in an existing message to reduce implementation difficulty, or it can be carried in a new message to improve implementation flexibility, without limitation.

[0339] It is understandable that if the first access and mobility management network element determines a second access and mobility management network element (which can be denoted as AMF#b1), the first access and mobility management network element can directly send the identifier of AMF#b1 to the access network device. If the first access and mobility management network element determines multiple second access and mobility management network elements (such as AMF#b1, AMF#b2, and AMF#b3), the first access and mobility management network element can send the identifiers of one or more of AMF#b1, AMF#b2, and AMF#b3 to the access network device. For example, the first access and mobility management network element can send the identifiers of AMF#b2 and AMF#b3 together to the access network device, etc., without limitation.

[0340] It is understood that the naming of the above instructions is only an example, and the instructions can be replaced with any other possible names without limitation.

[0341] S704, the terminal device sends a request message to the access network device. Correspondingly, the access network device receives the request message from the terminal device.

[0342] The request message can be used to request communication services from the tag management network element or to request registration with the tag management network element.

[0343] For example, when a terminal device needs to register with a tag management network element, it can send a registration request message to the access network device; when a terminal device needs the tag management network element to provide communication services, it can send a service request message to the access network device, and so on. There are no limitations on this. It is understood that this request message can also be any other possible request message, without limitation.

[0344] It is understood that this request message can be a NAS message, and the access network device and the access and mobility management network element (such as the second access and mobility management network element described below) forward this service request message. The naming of the above request message is only an example, and the request message can be replaced with any other possible name without limitation.

[0345] S705, the access network device sends a first message to the second access and mobility management network element according to the instruction information. Correspondingly, the second access and mobility management network element receives the first message from the access network device.

[0346] The access network device can identify the second access and mobility management network element based on the indication information, namely the stored identifier of the second access and mobility management network element, and send a first message to the second access and mobility management network element. The first message may include a request message.

[0347] For example, if the access network device stores the identifier AMF#b1, the access network device can directly send a request message to AMF#b1; if the access network device stores the identifiers AMF#b2 and AMF#b3, the access network device can choose to send a request message to either AMF#b2 or AMF#b3, or the access network device can send request messages to both AMF#b2 and AMF#b3 without limitation.

[0348] In one possible design, if the above-mentioned indication information also includes the identifier of the first tag management network element, the first message may also include the identifier of the first tag management network element. That is, the access network device sends the identifier of the first tag management network element to the second access and mobility management network element through the first message, so that the second access and mobility management network element can route to the appropriate first tag management network element.

[0349] Based on the above introduction, in one possible design scheme, the access network device is assigned a second identifier.

[0350] The second identifier can be used to identify the terminal device. The first message may also include the second identifier, that is, the second identifier can be assigned by the access network device and used to identify the terminal device. This second identifier can be a temporary identifier assigned by the access network device and used to identify the terminal device. For ease of understanding, this embodiment uses RAN NG AP ID#2 as an example for subsequent description, and will not be elaborated further. It is understood that a detailed description of this second identifier can be found in the relevant description in step S504 above, and will not be repeated here.

[0351] It is understood that the naming of the first message above is only an example, and the first message can be replaced with any other possible name without limitation.

[0352] S706, the second access and mobility management network element sends a request message to the first label management network element. Correspondingly, the first label management network element receives the request message from the second access and mobility management network element.

[0353] It is understood that if the first message does not include the identifier of the first tag management network element, the second access and mobility management network element can choose any one to establish a connection with the second access and mobility management network element and support the tag management network element of IoT devices, such as the first tag management network element; if the first message includes the identifier of the first tag management network element, the second access and mobility management network element can directly determine the first tag management network element based on the identifier of the first tag management network element.

[0354] Based on the above description, the request message can be carried in a second message, which may also include the aforementioned second identifier and third identifier. The third identifier can be used to identify the access network device and can be denoted as: RAN ID, or any other possible name, without limitation. The third identifier can be sent by the access network device to the first access and mobility management network element when establishing a connection with the first access and mobility management network element. It is understood that a detailed description of the third identifier can be found in the relevant content of step S505 above, without limitation.

[0355] At this time, the first access and mobility management network element can encapsulate the second identifier, the third identifier, and the aforementioned request message into a second message and send it to the first tag management network element through the Nx interface.

[0356] It is understood that after receiving the request message, the first tag management network element can provide communication services to the terminal device or register the terminal device with the first tag management network element. It is also understood that the first tag management network element can assign a temporary identifier to the terminal device. Based on the method embodiment shown in Figure 7, the temporary identifier assigned by the first tag management network element does not need to be used for addressing the access network device and the access and second mobility management network elements. Therefore, this application embodiment does not limit whether the first tag management network element assigns a temporary identifier to the terminal device.

[0357] It should be understood that if the above request message is a registration request message, the first tag management network element can also initiate a security process to the terminal device as needed. This security process may include: authenticating and authorizing the terminal device, establishing a security context, negotiating security parameters, etc. Its implementation principle is similar to the existing security process, which can be understood by reference and will not be elaborated here.

[0358] It is understood that the naming of the second message above is only an example, and the second message can be replaced with any other possible name without limitation.

[0359] In summary, during the initial N2 connection establishment, the access network device can send its capability information (i.e., support for IoT devices) to the first access and mobility management network element (MLM element). Based on this capability information, the first MLM element can determine the redirected second MLM element and send its identifier to the access network device via an indication message. When the access network device receives a request message from a terminal device, it can directly forward the request message to the second MLM element via the identifier of the second MLM element through a first message. The second MLM element can then forward the request message to the first tag management network element (e.g., by default or determined based on the identifier of the first tag management network element in the first message). This ensures that the access network device can select a suitable MLM element (e.g., the second MLM element), and that the access and mobility management network element can select a suitable tag management network element (e.g., the first tag management network element).

[0360] In conjunction with the above embodiments, one possible design scheme for the above method embodiments may further include:

[0361] The first tag management network element sends a response message for the second message to the first access and mobility management network element. Correspondingly, the second access and mobility management network element receives the response message for the second message from the first tag management network element.

[0362] The second access and mobility management network element sends a response message of the first message to the access network device based on the third identifier. Correspondingly, the access network device receives the response message of the first message from the second access and mobility management network element.

[0363] The access network device sends a response message to the terminal device based on the second identifier. Correspondingly, the terminal device receives a response message from the access network device regarding the service request message.

[0364] The response message to the second message may include the response message to the request message, a second identifier, and a third identifier. The response message to the first message may include the response message to the business request message and a second identifier.

[0365] It is understood that the implementation process can be referred to the relevant content in the method embodiment shown in Figure 5 above, and will not be repeated here.

[0366] It should be understood that, based on the above description, the aforementioned second access and mobility management network element may be absent, meaning the first access and mobility management network element has not selected a suitable access and mobility management network element as the redirected second access and mobility management network element. In this case, the first access and mobility management network element may not send the identifier of the second access and mobility management network element to the access network device. That is, the aforementioned indication information may not include the identifier of the second access and mobility management network element, or the indication information may be empty, etc., without limitation. In this situation, when the access network device receives a request message from the terminal device, it may forward the request message to the default or any one (establishing a connection with the access network device) access and mobility management network element, without limitation.

[0367] It is understood that when the first access and mobility management network element (MLM) does not support IoT services, or when the first MLM supports IoT services but does not support the IoT services corresponding to the access network device, the first MLM can also send an indication to the access network device that it does not support IoT services, or that it does not support the IoT services corresponding to the access network device (this information can be carried in the connection establishment response message #3). Alternatively, if the access network device defaults to the first MLM not supporting IoT services, or that it does not support the IoT services corresponding to the access network device, the first MLM may not need to send an indication to the access network device that it does not support IoT services, or that it does not support the IoT services corresponding to the access network device. This application embodiment does not limit this. After the access network device subsequently receives a request message from an (IoT) terminal device, it may not forward the terminal device's request message to the first MLM to save overhead.

[0368] When the first access and mobility management network element supports IoT services, or supports IoT services and the corresponding IoT services of the access network device, the first access and mobility management network element does not need to perform redirection. In this case, the first access and mobility management network element can send information indicating whether it supports IoT services or not, or whether it supports the IoT services corresponding to the access network device, without sending the identifier of the second access network device to the access network device. After the access network device subsequently receives a request message from the (IoT) terminal device, it can directly forward the terminal device's request message to the first access and mobility management network element, which is simple to implement.

[0369] It is understood that the method embodiments shown in Figures 5 and 6 above are introduced using the interaction between the terminal device, the access network device, the first access and mobility management network element, and the first tag management network element as an example. The aforementioned terminal device, access network device, first access and mobility management network element, and first tag management network element can also be replaced with any other possible terminal device, access network device, access and mobility management network element (such as the second access and mobility management network element, etc.) and tag management network element (such as the second tag management network element, etc.). The implementation principle is similar and can be understood by reference, without further elaboration.

[0370] The method embodiment shown in Figure 7 above is described using the interaction between the terminal device, the access network device, the first access and mobility management network element, the second access and mobility management network element, and the first tag management network element as an example. The aforementioned terminal device, access network device, first access and mobility management network element, second access and mobility management network element, and first tag management network element can also be replaced with any other possible terminal device, access network device, access and mobility management network element (such as the third access and mobility management network element, the fourth access and mobility management network element, etc.), and tag management network element (such as the second tag management network element, etc.). The implementation principle is similar and can be understood by reference, without further explanation.

[0371] The above, in conjunction with the method embodiments, provides an overall overview of the communication method provided in this application. For ease of understanding, the following scenario will be used as an example to illustrate the above method.

[0372] Scenario 1: Figure 8 is a schematic flowchart of the communication method provided in the embodiment of this application. It mainly involves the interaction between device #1 (such as the terminal device mentioned above, device #1 is an A-IoT device), RAN #1 (such as the access network device mentioned above), AMF #1 (such as the first access and mobility management network element mentioned above), and TMF #1 (such as the first tag management network element mentioned above). This scenario 1 can correspond to the method embodiment shown in Figure 5 above.

[0373] As shown in Figure 8, the method may include:

[0374] S801, AMF#1 Preset TMF Identifier List #1.

[0375] The TMF identifier list #1 (i.e., the aforementioned identifier association information) may include identifiers of TMFs associated with AMF#1, or in other words, identifiers of TMFs connected to AMF#1. That is, the TMF identifier list #1 can represent the association or correspondence between AMF#1 and TMFs. There can be one or more TMFs, without limitation. For example, the TMF identifier list #1 may include the identifier of TMF#1 and the identifier of TMF#2, thus representing that AMF#1 is associated with both TMF#1 and TMF#2.

[0376] It is understood that the TMF identifier list #1 can be pre-configured statically, pre-defined, automatically established when the connection between AMF#1 and TMF (such as TMF#1 and TMF#2 mentioned above) is established, sent by TMF (such as TMF#1 and TMF#2 mentioned above) to AMF#1 (determined by AMF#1 based on the identifier of the received TMF), or obtained by AMF from other network elements, such as NRF, etc. For the specific implementation, please refer to the relevant introduction in step S503 above, which will not be elaborated here.

[0377] S802, RAN#1 sends a connection establishment request message #a to AMF#1.

[0378] RAN#1 can request to establish a connection with AMF#1 via a connection establishment request message #a. This connection establishment request message #a may also include indications that RAN#1 supports the access of IoT devices.

[0379] It is understandable that the connection establishment request message #a can also include any other possible parameters without limitation.

[0380] S803, AMF#1 sends a connection establishment response message #a to RAN#1.

[0381] In response to the connection establishment request message #a, when AMF#1 accepts the connection establishment request from RAN#1, AMF#1 can send a connection establishment response message #a to RAN#1. Simultaneously, if AMF#1 determines, based on the connection establishment request message #a, that RAN#1 supports IoT device access, AMF#1 can send the TMF identifier list #1 to RAN#1 via the connection establishment response message #a. That is, when AMF#1 and RAN#1 establish connection N2, AMF#1 can feed back routable TMFs to RAN#1 so that RAN#1 can route to the correct AMF, i.e., AMF#1, based on the TMF identifier.

[0382] It is understood that the connection establishment response message #a can also be used to indicate to AMF#1 that it supports the access of IoT devices. That is, AMF#1 can also use the connection establishment response message #a to indicate to RAN#1 that it supports the access of IoT devices. The connection establishment response message #a can also include any other possible parameters, without limitation. It is understood that device #1 can be an IoT device.

[0383] S804, RAN#1 stores the TMF identifier list #1.

[0384] S804a, AMF#1 Update TMF Identifier List #1.

[0385] When AMF#1 needs to update TMF identifier list #1, such as when the connection between AMF#1 and the established TMF is released, or when AMF#1 establishes a connection with a new TMF, AMF#1 can update TMF identifier list #1 to TMF identifier list #2. For example, if AMF#1 also establishes a connection with TMF#3, then TMF identifier list #2 can include: the identifier of TMF#1, the identifier of TMF#2, and the identifier of TMF#3.

[0386] S804b, AMF#1 sends TMF identifier list #2 to RAN#1.

[0387] AMF#1 can send an update request message to RAN#1, which may include TMF identifier list #2.

[0388] S804c, RAN#1 stores TMF identifier list #2.

[0389] It is understood that steps S804a-S804b are optional and not limited. For ease of understanding, the following explanation will use RAN#1 storing TMF identifier list #1 as an example.

[0390] S805, device #1 sends a registration request message #a to TMF#1 via RAN#1 and AMF#1.

[0391] When device #1 needs to register with the network, device #1 can send an AN message to RAN #1.

[0392] The AN message can include AN parameters, registration request message #a, etc., without limitation. AN parameters can include 5G-S-TMSI or GUAMI, the requested NSSAI, etc. The registration request message #a can include registration type, device #1 identifier (such as SUCI, 5G-GUTI, or PEI), etc., without limitation.

[0393] RAN#1 can select a suitable or default AMF based on the AN message, such as AMF#1. In this case, RAN#1 can forward the registration request to AMF#1 via the N2 interface. That is, RAN#1 can send an N2 message to AMF#1. The N2 message can include the registration request message #a, the device #1 policy container, and the temporary identifier RAN_NG AP_ID#1 assigned by RAN#1 to device #1, etc., without limitation. AMF#1 can select a suitable TMF based on the N2 message, such as TMF#1. In this case, AMF#1 can forward the registration request to TMF#1 via the Nx interface. That is, AMF#1 can send an Nx message to TMF#1. The Nx message can include the registration request message #a, RAN_NG AP_ID#1, and the identifier of RAN#1 (sent by RAN#1 to AMF#1 when establishing a connection with AMF#1), etc., without limitation.

[0394] It is understood that the specific implementation of step S805 can be referred to the relevant introduction in step S501 above, and will not be repeated here.

[0395] S806, TMF#1 initiates a security procedure.

[0396] After receiving the registration request message #a, TMF#1 can initiate a security process to device #1 as needed. This security process may include: authenticating and authorizing device #1, establishing a security context, negotiating security parameters, etc., which will not be elaborated further. For example, TMF#1 can determine whether device #1 is the same device #1 in the subscription information based on the device #1 identifier in the registration request message #a and the terminal's subscription information (such as obtained from UDM), in order to authenticate device #1.

[0397] S807, TMF#1 assigns temporary identifier #1 to device #1.

[0398] It is understood that the temporary identifier #1 can be used to globally uniquely identify device #1. The temporary identifier #1 may include the identifier of TMF #1 (such as the first identifier in the method embodiment shown in Figure 5 above). For example, TMF #1 may assign the temporary identifier #1 to device #1 if the security authentication of device #1 is successful.

[0399] S808, TMF#1 sends a registration accept message #a to device #1 via AMF#1 and RAN#1.

[0400] The registration acceptance message #a can indicate that TMF#1 has accepted the registration request from device #1. The registration acceptance message #a can include temporary identifier #1, or any other possible parameters and signaling, without limitation.

[0401] For example, TMF#1 can send a response message of an Nx message to AMF#1. The response message of the Nx message may include the aforementioned registration acceptance message #a, RAN_NG AP_ID#1, and the identifier of RAN#1. AMF#1 can send a response message of an N2 message to RAN#1 based on the identifier of RAN#1. The response message of the N2 message may include the registration acceptance message #a and RAN_NG AP_ID#1. In this way, AMF#1 can achieve stateless forwarding. RAN#1 can send a response message of an AN message to device #1 based on RAN_NG AP_ID#1. The response message of the AN message may include the aforementioned registration acceptance message #a.

[0402] It is understandable that the implementation process of this step is similar to that of step S805 above, and can be understood by reference, so it will not be elaborated further.

[0403] S809, Device #1 stores temporary identifier #1.

[0404] Device #1 can receive message #a upon registration and save temporary identifier #1.

[0405] S810, device #1 sends a registration complete message #a to TMF#1 via AMF#1 and RAN#1.

[0406] The registration completion message #a can be used to indicate that the registration process of device #1 has been completed. The registration completion message #a can also indicate that device #1 has received the temporary identifier #1 assigned by TMF #1, etc., without limitation.

[0407] S811, device #1 sends the identifier and service request message #1 of TMF #1 to RAN #1.

[0408] When device #1 has subsequent service needs, it can send the identifier of TMF #1 (AS layer) and service request message #1 (NAS layer) to RAN #1. This service request message #1 can be used to request communication services for device #1. The service request message #1 can include a temporary identifier #1 or any other possible parameters, without limitation. This NAS layer request message #1 can be an exchange between device #1 and TMF #1, and RAN #1 forwards the service request message #1.

[0409] S812, RAN#1 sends message #1 to AMF#1.

[0410] RAN#1 can obtain the identifier of TMF#1 from the AS layer, and determine the AMF#1 associated with TMF#1 based on the identifier of TMF#1 and the identifier list #1 in step S804 above. RAN#1 can send message #1 to AMF#1. Message #1 may include service request message #1, the identifier of TMF#1, and RAN NG AP_ID#2 (as described in the second identifier above). RAN_NG AP_ID#2 can uniquely identify device #1 within RAN#1 through the NG interface; in other words, RAN_NG AP_ID#2 is a temporary identifier assigned to device #1. RAN_NG AP_ID#2 can be the same as or different from RAN_NG AP_ID#1, without limitation. That is, AMF#1 also forwards service request message #1.

[0411] S813, AMF#1 sends message #2 to TMF#1.

[0412] AMF#1 can identify TMF#1 based on the identifier of TMF#1 and send message #2 to TMF#1. Message #2 may include service request message #1, the identifier of RAN#1 (as described in the third identifier above), and RAN NGAP_ID#2. The identifier of RAN#1 can be the one sent by RAN#1 to AMF#1 when establishing a connection with AMF#1, and this identifier can be used to identify RAN#1.

[0413] S814, TMF#1 provides communication services for device #1.

[0414] TMF#1 can determine that the service request message #1 is a request message from device #1 based on the temporary identifier #1 in the service request message #1. Then, TMF#1 can provide communication services to device #1 based on the service request message #1.

[0415] S815, TMF#1 sends a response message #2 to AMF#1.

[0416] In response to message #2, TMF#1 can send a response message to AMF#1. This response message can include, but is not limited to, a response to service request message #1, the identifier of RAN#1, and RAN_NG AP_ID#2, etc. The response to service request message #1 can be used to indicate that TMF#1 has received service request message #1. It can be understood that this response message to service request message #1 is similar to service request message #1 itself, representing a NAS layer message exchanged between device #1 and TMF#1. AMF#1 and RAN#1 forward this service request message #1.

[0417] S816, AMF#1 sends a response message of message #1 to RAN#1.

[0418] AMF#1 can determine RAN#1 based on the RAN#1 identifier in the response message of message #2, and send the response message of message #1 to RAN#1. The response message of message #1 can include: the response message of service request message #1 and RAN_NG AP_ID#2, etc., without limitation. In this way, AMF#1 can achieve stateless forwarding without needing the context of device #1.

[0419] S817, RAN#1 sends a response message of Service Request Message #1 to device #1.

[0420] RAN#1 can determine device #1 based on RAN_NG AP_ID#2 in the response message of message #1, and send a response message of service request message #1 to device #1. RAN#1 can also send any other possible messages to device #1 without limitation.

[0421] It is understood that the specific implementation of the above steps S801-S817 can be referred to the relevant description in the method embodiment shown in Figure 5 above, and will not be repeated here.

[0422] Scenario 2: Figure 9 is a flowchart illustrating the communication method provided in this application embodiment. It mainly involves the interaction between device #1 (such as the terminal device mentioned above, device #1 is an A-IoT device), RAN #1 (such as the access network device mentioned above), AMF #1 (such as the first access and mobility management network element mentioned above), and TMF #1 (such as the first tag management network element mentioned above). This scenario 2 can correspond to the method embodiment shown in Figure 6 above.

[0423] As shown in Figure 9, the method may include:

[0424] S901, AMF#1 is a reserved identifier for TMF#1.

[0425] For example, AMF#1 can reserve its identifier for TMFs, such as TMF#1 and TMF#2, for use by TMF#1 and TMF#2 when assigning a temporary identifier to a device, such as device #1.

[0426] Taking scenario 3 above as an example, AMF#1 can reserve the values ​​of AMF region ID field #1, AMF set ID field #1, and AMF pointer field #60 for TMF#1 (which is connected to AMF#1), and reserve the values ​​of AMF region ID field #1, AMF set ID field #1, and AMF pointer field #61 for TMF#2 (which is connected to AMF#1).

[0427] It is understandable that the specific implementation of this step can be referred to the relevant introduction in step S601 above, and will not be repeated here.

[0428] S902, RAN#1 sends a connection establishment request message #b to AMF#1.

[0429] Among them, the connection establishment request message #b can be used to request the establishment of a connection with AMF#1, and the connection establishment request message #b can also be used to indicate that RAN#1 supports the access of IoT devices.

[0430] S903, AMF#1 sends a connection establishment response message #b to RAN#1.

[0431] In response to the connection establishment request message #b, when AMF#1 accepts the connection establishment request #b from RAN#1, AMF#1 can send a connection establishment response message #b to RAN#1. This connection establishment response message #b can also be used to indicate that AMF#1 supports the access of IoT devices.

[0432] S904, Device #1 sends a registration request message #b to TMF #1 via RAN #1 and AMF #1.

[0433] S905, TMF#1 initiates a security procedure.

[0434] It is understood that the specific descriptions of steps S904-S905 can be found in steps S805-S806 and the relevant descriptions in step S601, and will not be repeated here.

[0435] S906, TMF#1 assigns temporary identifier #2 to device #1.

[0436] It is understandable that this temporary identifier #2 can be used to identify the globally unique identifier device #1.

[0437] TMF#1 can use the identifier assigned by AMF#, such as the AMF region ID field value being #1, the AMF set ID field value being #1, and the AMF pointer field value being #60, to assign a temporary identifier #2. That is, temporary identifier #2 can include identifier #1 (as shown in the method embodiment of Figure 6 above), which can be used to identify AMF#1. Some fields occupied by identifier #1 (the AMF pointer field value being #60) can also be used to identify TMF#1. In other words, identifier #1 can be used to identify AMF#1 and the TMF#1 associated with AMF#1.

[0438] It is understood that the specific details of steps S904-S905 can be found in the relevant descriptions in step S601 above, and will not be repeated here.

[0439] S907, TMF#1 sends a registration acceptance message #b to device #1 via AMF#1 and RAN#1.

[0440] The registration acceptance message #b can indicate that TMF#1 has accepted the registration request from device #1. The registration acceptance message #b can include temporary identifier #2, or any other possible parameters and signaling, without limitation.

[0441] It is understood that the specific details of this step can be found in step S808 and the relevant descriptions in step S601 above, and will not be repeated here.

[0442] S908, Device #1 stores temporary identifier #2.

[0443] Device #1 can receive message #b upon registration and save temporary identifier #2.

[0444] S909, device #1 sends a registration completion message #b to TMF#1 via AMF#1 and RAN#1.

[0445] The registration completion message #b can be used to indicate that the registration process of device #1 is complete. The registration completion message #b can also indicate that device #1 has received the temporary identifier #2 allocated by TMF #1, etc., without limitation.

[0446] S910, device #1 sends identifier #1 and service request message #1 to RAN #1.

[0447] When device #1 has subsequent service needs, it can send an AS layer identifier #1 and a NAS layer service request message #1 to RAN #1. This service request message #1 can be used to request communication services for device #1. The service request message #1 may include a temporary identifier #2 or any other possible parameters, without limitation. This NAS layer service request message #1 can be a message exchanged between device #1 and TMF #1, and RAN #1 forwards the service request message #1.

[0448] S911, RAN#1 sends message #1 to AMF#1.

[0449] RAN#1 can obtain identifier #1 from the AS layer and send message #1 to AMF#1. Message #1 may include service request message #1, identifier #1, and RAN NG AP_ID#2 (as described in the second identifier above). RAN_NG AP_ID#2 can uniquely identify device #1 within RAN#1 via the NG interface; in other words, RAN_NG AP_ID#2 is a temporary identifier assigned to device #1. That is, AMF#1 also forwards service request message #1.

[0450] S912, AMF#1 sends message #2 to TMF#1.

[0451] AMF#1 can determine that the value #60 in the AMF pointer field occupied by identifier #1 is associated with TMF#1, thus identifying TMF#1. AMF#1 can send message #2 to TMF#1. Message #2 may include service request message #1, the identifier of RAN#1 (as mentioned in the third identifier above), and RAN NG AP_ID#2. The identifier of RAN#1 can be the one sent by RAN#1 to AMF#1 when establishing a connection with AMF#1, and this identifier can be used to identify RAN#1.

[0452] S913, TMF#1 provides communication services for device #1.

[0453] TMF#1 can determine that Service Request Message #1 is a request message from Device #1 based on the temporary identifier #2 in Service Request Message #1. Then, TMF#1 can provide communication services to Device #1 based on Service Request Message #1.

[0454] S914, TMF#1 sends a response message #2 to AMF#1.

[0455] The response message for message #2 may include: the response message for service request message #1, the identifier of RAN #1, and RAN_NG AP_ID #1, etc., without limitation.

[0456] S915, AMF#1 sends a response message #1 to RAN#1.

[0457] AMF#1 can determine RAN#1 based on the RAN#1 identifier in the response message of message #2, and send the response message of message #1 to RAN#1. The response message of message #1 can include: the response message of request message #1 and RAN_NG AP_ID#2, etc., without limitation. In this way, AMF#1 can achieve stateless forwarding without needing the context of device #1.

[0458] S916, RAN#1 sends a response message to service request message #1 to device #1.

[0459] RAN#1 can determine device #1 based on RAN_NG AP_ID#1 in the response message of message #1, and send a response message of service request message #1 to device #1. RAN#1 can also send any other possible messages to device #1 without limitation.

[0460] It is understood that the specific implementation of steps S913-S916 above can be referred to the relevant description in steps S814-S817 above, and will not be repeated here. The specific implementation of steps S901-S916 above can be referred to the relevant description in the method embodiment shown in Figure 6 above, and will not be repeated here.

[0461] Scenario 3: Figure 10 is a flowchart illustrating the communication method provided in this embodiment. It mainly involves the interaction between device #1 (A-IoT device), RAN #1, AMF #1, and TMF #1. It can be understood that Scenario 3 adopts a converged simplified network topology; that is, the relationship between AMF and TMF is many-to-one or one-to-one, without limitation. The following detailed description uses AMF #1 corresponding to TMF #1 and AMF #2 corresponding to TMF #2 as an example.

[0462] As shown in Figure 10, the method may include:

[0463] S1001, RAN#1 sends a connection establishment request message #c to AMF#1 and AMF#2.

[0464] Taking AMF#1 and AMF#2 as examples, RAN#1 can send a connection establishment request message #c to AMF#1 to request a connection to AMF#1; when RAN#1 and AMF#2 establish a connection, RAN#1 can send a connection establishment request message #c to AMF#2 to request a connection to AMF#2. This connection establishment request message #c can also be used to indicate that RAN#1 supports the access of IoT devices.

[0465] S1002, AMF#1 sends a connection establishment response message #c1 to RAN#1.

[0466] In response to the connection establishment request message #c, when AMF#1 accepts the connection establishment request #c from RAN#1, AMF#1 can send a connection establishment response message #c1 to RAN#1. The connection establishment response message #c1 can also be used to indicate that AMF#1 supports the access of IoT devices.

[0467] S1003, AMF#2 sends a connection establishment response message #c2 to RAN#1.

[0468] In response to the connection establishment request message #c, when AMF#2 accepts the connection establishment request #c from RAN#1, AMF#2 can send a connection establishment response message #c2 to RAN#1. The connection establishment response message #c2 can also be used to indicate that AMF#2 supports the access of IoT devices.

[0469] S1004, RAN#1 records AMF#1 and AMF#2 to support the access of IoT devices.

[0470] RAN#1 can establish a response message #c1 based on the connection, record or save AMF#1 to support the access of IoT devices, and establish a response message #c2 based on the connection, record or save AMF#2 to support the access of IoT devices.

[0471] S1005, device #1 sends request message #1 to RAN #1.

[0472] It is understandable that when device #1 needs TMF to provide communication services or needs to register with TMF, device #1 can send a NAS layer request message #1 to RAN #1. This NAS layer request message #1 can be a message exchanged between device #1 and TMF #1.

[0473] S1006, RAN#1 sends message #1 to AMF#1.

[0474] After receiving message #1, RAN#1 can assign RAN NGAP_ID#1 to device #1. This RAN_NG AP_ID#1 can uniquely identify device #1 within RAN#1 via the NG interface. RAN#1 can also forward request message #1 to an AMF (that can establish a connection with RAN#1) that supports IoT device access. If multiple AMFs that have established a connection with RAN#1 can support IoT device access, RAN#1 can select one of the AMFs (such as AMF#1) according to a strategy, such as random selection or load sharing.

[0475] Alternatively, RAN#1 can select multiple AMFs. In this case, when forwarding (service request) messages from devices (including device #1), RAN#1 needs to carry a unique sequence number for each message. This allows TMF#1 to identify that messages from multiple AMFs are the same message when it receives them, thus discarding subsequent messages of the same message to avoid the first label management network element repeatedly processing the same service request. It is understood that this sequence number is incremental, and different messages carry different sequence numbers; alternatively, the sequence number can be a timestamp, etc., without limitation. For ease of understanding, this application uses RAN#1 selecting AMF#1 as an example for illustration, and will not elaborate further thereafter.

[0476] For example, RAN#1 can select either AMF#1 or AMF#2, such as AMF#1, based on the record in step S1004 above, and send message #1 to AMF#1. Message #1 may include request message #1 and RAN NGAP_ID#1.

[0477] S1007, AMF#1 sends message #2 to TMF#1.

[0478] Based on the aforementioned simplified converged networking, AMF#1 is associated with TMF#1. Therefore, AMF#1 can identify TMF#1 and send message #2 to TMF#1. Message #2 may include request message #1, the identifier of RAN#1, and RAN NGAP_ID#1. The identifier of RAN#1 can be the one sent by RAN#1 to AMF#1 when establishing a connection with AMF#1, and this identifier can be used to identify RAN#1.

[0479] It is understandable that, based on the above steps S1006 and S1007, both RAN#1 and AMF#1 can forward request message #1 without needing to be aware of the temporary identifier. TMF#1 can also assign a temporary identifier to device #1. Based on scenario 3, the temporary identifier assigned by TMF#1 does not need to be used for addressing RAN#1 and AMF#1. Therefore, in scenario 3, there is no requirement for TMF#1 to assign a temporary identifier to device #1.

[0480] S1008, TMF#1 provides communication services for device #1 or registers device #1 to TMF#1.

[0481] It is understandable that if TMF#1 assigns a temporary identifier to device #1, such as temporary identifier #a, the request message #1 can contain temporary identifier #a. Then, TMF#1 can determine that the temporary identifier was assigned to device #1 by itself based on the temporary identifier #a. In this case, TMF#1 can provide communication services to device #1 or register device #1 to TMF#1.

[0482] S1009, TMF#1 sends a response message #2 to AMF#1.

[0483] In response to message #2, TMF #1 can send a response message to AMF #1. This response message to message #2 may include, but is not limited to, a response to request message #1, the identifier of RAN #1, and RAN_NG AP_ID #1, etc. The response message to request message #1 can also be used to indicate that TMF #1 has received service request message #1, etc., without limitation.

[0484] It is understandable that the response message to request message #1 is similar to request message #1, and is a NAS layer message exchanged between AMF#1 and RAN#1. AMF#1 and RAN#1 forward the response message to request message #1.

[0485] S1010, AMF#1 sends a response message of message #1 to RAN#1.

[0486] AMF#1 can determine RAN#1 based on the RAN#1 identifier in the response message of message #2, and send the response message of message #1 to RAN#1. The response message of message #1 can include: the response message of request message #1 and RAN_NG AP_ID#1, etc., without limitation. In this way, AMF#1 can achieve stateless forwarding without needing the context of device #1.

[0487] S1011, RAN#1 sends a response message to request message #1 to device #1.

[0488] RAN#1 can determine device #1 based on RAN_NG AP_ID#1 in the response message of message #1, and send a response message of request message #1 to device #1. RAN#1 can also send any other possible messages to device #1 without limitation.

[0489] It is understood that the specific implementation of the above steps S1009-S1011 can be referred to the relevant introduction in the above steps S815-S817, and will not be repeated here.

[0490] Scenario 4: Figure 11 is a flowchart illustrating the communication method provided in this application embodiment. It mainly involves the interaction between device #1 (such as the terminal device mentioned above, device #1 is an A-IoT device), RAN #1 (such as the access network device mentioned above), AMF #1 (such as the first access and mobility management network element mentioned above), AMF #2 (such as the second access and mobility management network element mentioned above), and TMF #1 (such as the first tag management network element mentioned above). This scenario 4 can correspond to the method embodiment shown in Figure 7 above.

[0491] As shown in Figure 11, the method may include:

[0492] S1101, RAN#1 sends a connection establishment request message #d to AMF#1.

[0493] When RAN#1 and AMF#1 establish a connection, RAN#1 can send a connection establishment request message #d to AMF#1 to request to establish a connection with AMF#1. The connection establishment request message #d can also be used to indicate that RAN#1 supports the access of IoT devices.

[0494] It is understandable that the connection establishment request message #d may include the identifier of RAN#1, etc., without limitation.

[0495] S1102, AMF#1 sends a connection establishment response message #d to RAN#1.

[0496] AMF#1 can determine other AMFs after redirection based on the IoT device access supported by RAN#1, such as AMF#2 (which can support IoT services). Optionally, AMF#1 can determine TMFs based on the IoT device access supported by RAN#1, such as TMF#1 (which can support IoT services). It can be understood that AMF#1 can select AMF#2 and TMF#1 according to certain strategies. The specific implementation can be referred to the relevant introduction in steps S701-S702 above, and will not be elaborated here.

[0497] It is understandable that, in response to the connection establishment request message #d, when AMF#1 accepts the connection establishment request #d from RAN#1, AMF#1 can send a connection establishment response message #d to RAN#1. This connection establishment response message #d may also include the identifier of AMF#2 and the identifier of TMF#1, etc., without limitation.

[0498] S1103, AMF#1 record redirected to AMF#2.

[0499] RAN#1 can establish a response message #d based on the connection and record or save the identifier of the redirected AMF#2.

[0500] Optionally, if the connection establishment request message #d also includes the identifier of TMF#1, RAN#1 may also record or save the identifier of TMF#1.

[0501] S1104, Device #1 sends Request Message #1 to RAN #1.

[0502] It is understandable that when device #1 needs TMF to provide communication services or needs to register with TMF, device #1 can send a NAS layer request message #1 to RAN #1. This NAS layer request message #1 can be a message exchanged between device #1 and TMF #1.

[0503] S1105, RAN#1 sends message #1 to AMF#2.

[0504] After receiving request message #1, RAN#1 can forward request message #1 to the redirected AMF#2 based on the stored identifier of AMF#2. That is, RAN#1 can send message #1 to this AMF#2. Message #1 may include request message #1 and RAN NGAP_ID#1 (the second identifier mentioned above). RAN_NG AP_ID can uniquely identify device #1 within RAN#1 via the NG interface. In other words, AMF#1 also forwards the NAS layer request message #1.

[0505] Optionally, if the connection establishment request message #d also includes the identifier of TMF#1, RAN#1 may also send the identifier of TMF#1 to AMF#1 via message #1.

[0506] S1106, AMF#2 sends message #2 to TMF#1.

[0507] If message #1 does not include the identifier of TMF#1, AMF#2 can immediately establish a connection with any TMF that supports IoT devices, such as TMF#1, through the second access and mobility management network element. If message #1 includes the identifier of TMF#1, AMF#2 can directly determine TMF#1 based on TMF#1.

[0508] It is understandable that, based on the above steps S1105 and S1106, both RAN#1 and AMF#2 can forward request message #1 without needing to be aware of the temporary identifier. TMF#1 can also assign a temporary identifier to device #1. Based on scenario 4, the temporary identifier assigned by TMF#1 does not need to be used for addressing of RAN#1 and AMF#2. Therefore, in scenario 4, there is no requirement for TMF#1 to assign a temporary identifier to device #1.

[0509] S1107, TMF#1 provides communication services to device #1 or registers device #1 to TMF#1.

[0510] S1008, TMF#1 sends a response message #2 to AMF#2.

[0511] The response message to message #2 may include: the response message to request message #1, the identifier of RAN #1, and RAN_NG AP_ID #1, etc., without limitation.

[0512] S1109, AMF#2 sends a response message of message #1 to RAN#1.

[0513] AMF#2 can determine RAN#1 based on the identifier of RAN#1 in the response message of message #2, and send the response message of message #1 to RAN#1. The response message of message #1 can include: the response message of request message #1 and RAN_NG AP_ID#1, etc., without limitation. In this way, AMF#1 can achieve stateless forwarding without needing the context of device #1.

[0514] S1110, RAN#1 sends a response message to request message #1 to device #1.

[0515] It is understood that the specific implementation of steps S1008-S1110 above can be referred to the relevant descriptions in steps S815-S817 above, and will not be repeated here. The specific implementation of steps S1101-S1109 above can be referred to the relevant descriptions in the method embodiment shown in Figure 7 above, and will not be repeated here.

[0516] The communication method provided by the embodiments of this application has been described in detail above with reference to Figures 5-11. The communication apparatus used to perform the communication method provided by the embodiments of this application is described in detail below with reference to Figures 12-13.

[0517] Figure 12 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. As exemplarily shown in Figure 12, the communication device 1200 includes a transceiver module 1201 and a processing module 1202. For ease of explanation, Figure 12 only shows the main components of the communication device 1200.

[0518] The transceiver module 1201 is used to perform the transceiver function of the method shown in Figures 5-11, and the processing module 1202 is used to perform other functions of the method shown in Figures 5-11 besides the transceiver function.

[0519] Optionally, the transceiver module 1201 may include a transmitting module (not shown in FIG12) and a receiving module (not shown in FIG12). The transmitting module is used to implement the transmitting function of the communication device 1200, and the receiving module is used to implement the receiving function of the communication device 1200.

[0520] Optionally, the communication device 1200 may further include a storage module (not shown in FIG. 12) that stores programs or instructions. When the processing module 1202 executes the program or instructions, the communication device 1200 can perform the functions of the terminal device and / or network device (such as access network device, access and mobility management network element, tag management network element) in the methods shown in FIG. 5-FIG. 11 above.

[0521] It is understood that the communication device 1200 may be a terminal device, or a chip (system) or other component or assembly that can be disposed in a terminal device, or a device that includes a terminal device; or, the communication device 1200 may be a network device, or a chip (system) or other component or assembly that can be disposed in a network device, or a device that includes a network device. The embodiments of this application do not limit this.

[0522] Furthermore, the technical effects of the communication device 1200 can be referred to the technical effects of the communication methods shown in Figures 5-11, and will not be repeated here.

[0523] For example, Figure 13 is a second schematic diagram of the structure of a communication device provided in an embodiment of this application. This communication device can be a terminal device or a network device, or it can be a chip (system) or other component or assembly of a terminal device or network device. As shown in Figure 13, the communication device 1300 may include a processor 1301. Optionally, the communication device 1300 may also include a memory 1302 and / or a transceiver 1303. The processor 1301 is coupled to the memory 1302 and the transceiver 1303, for example, they can be connected via a communication bus.

[0524] The following is a detailed description of each component of the communication device 1300 with reference to Figure 13:

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

[0526] Optionally, the processor 1301 can perform various functions of the communication device 1300 by running or executing software programs stored in the memory 1302 and calling data stored in the memory 1302, such as performing the communication methods shown in Figures 5-11 above.

[0527] In a specific implementation, as one embodiment, processor 1301 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG13.

[0528] In a specific implementation, as one embodiment, the communication device 1300 may also include multiple processors, such as processors 1301 and 1304 shown in FIG. 13. Each of these processors may be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). Here, a processor may refer to one or more devices, circuits, and / or processing cores used for processing data (e.g., computer program instructions).

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

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

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

[0532] Optionally, transceiver 1303 may include a receiver and a transmitter (not shown separately in Figure 13). The receiver is used to implement the receiving function, and the transmitter is used to implement the transmitting function.

[0533] Optionally, the transceiver 1303 can be integrated with the processor 1301 or exist independently and be coupled to the processor 1301 through the interface circuit of the communication device 1300 (not shown in FIG13). This application embodiment does not specifically limit this.

[0534] It should be noted that the structure of the communication device 1300 shown in Figure 13 does not constitute a limitation on the communication device. The actual communication device may include more or fewer components than shown, or combine certain components, or have different component arrangements.

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

[0536] This application provides a communication system. The communication system may include the terminal device described in the above method embodiments, and network devices (such as access network devices, access and mobility management network elements, and tag management network elements).

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A communication method characterized by comprising: The method comprises: The access network device receives a first identifier and a service request message from a terminal device; the first identifier is used to identify a first label management network element, and the service request message is used to request a communication service from the first label management network element; The access network device determines a first access and mobility management network element according to the first identifier and identification association information; the identification association information comprises an association relationship between the first access and mobility management network element and a label management network element, and the label management network element comprises the first label management network element; The access network device sends a first message to the first access and mobility management network element; the first message comprises the service request message and the first identifier.

2. The method of claim 1, wherein, The terminal device is an IoT device, and before the access network device receives the first identifier and the service request message from the terminal device, the method further comprises: The access network device sends capability information of the access network device to the first access and mobility management network element; the capability information of the access network device is used to indicate that the access network device supports access of an IoT device; The access network device receives the identification association information returned by the first access and mobility management network element according to the capability information of the access network device.

3. A communication method characterized by comprising: The method comprises: The access network device receives a first identifier and a service request message from a terminal device; the first identifier is used to identify a first label management network element, and the service request message is used to request a communication service from the first label management network element; The access network device determines a first access and mobility management network element according to the first identifier; the first identifier is also used to identify the first access and mobility management network element; The access network device sends a first message to the first access and mobility management network element; the first message comprises the service request message and the first identifier.

4. A communication method characterized by comprising: The method comprises: The first access and mobility management network element receives a first message from an access network device; the first message comprises a first identifier and a service request message; the first identifier is used to identify a first label management network element, and the service request message is used to request a communication service from the first label management network element; The first access and mobility management network element sends a second message to the first label management network element according to the first identifier; the second message comprises the service request message.

5. The method of claim 4, wherein, Before the first access and mobility management network element receives the first message from the access network device, the method further comprises: The first access and mobility management network element receives capability information of the access network device sent by the access network device; the capability information of the access network device is used to indicate that the access network device supports access of an IoT device; The first access and mobility management network element sends identification association information to the access network device; the identification association information comprises an association relationship between the first access and mobility management network element and a label management network element, and the label management network element comprises the first label management network element.

6. The method of claim 4, wherein, The first identifier is also used to identify the first access and mobility management network element; before the first access and mobility management network element receives the first message from the access network device, the method further comprises: The first access and mobility management network element sends a fourth identifier to the first label management network element; wherein the fourth identifier is used to identify the first access and mobility management network element.

7. The method of claim 6, wherein, The fourth identifier is also used by the first label management network element when allocating a temporary identifier of a terminal device, and the temporary identifier comprises the first identifier.

8. The method according to any one of claims 4-7, characterized in that, The first message further comprises a second identifier, which is allocated by the access network device and is used to identify a terminal device.

9. The method of claim 8, wherein, The second message further comprises the second identifier and a third identifier; wherein the third identifier is used to identify the access network device.

10. The method of claim 9, wherein, The method further comprises: The first access and mobility management network element receives a response message of the second message from the first label management network element; wherein the response message of the second message comprises a response message of the service request message, the second identifier and the third identifier; The first access and mobility management network element sends a response message of the first message to the access network device according to the third identifier; wherein the response message of the first message comprises the response message of the service request message and the second identifier.

11. A communication method, comprising: Comprise: In the process of terminal device registration, the first label management network element allocates a temporary identifier and sends the temporary identifier to the terminal device; wherein the temporary identifier comprises a first identifier, and the first identifier is used to identify the first label management network element; The first label management network element receives a second message from the first access and mobility management network element; wherein the second message comprises a service request message, the service request message is used to request a communication service from the first label management network element, and the service request message comprises the temporary identifier; The first label management network element determines to provide the communication service for the terminal device according to the temporary identifier.

12. The method of claim 11, wherein, The process of terminal device registration, the label management network element allocates a temporary identifier and sends the temporary identifier to the terminal device, comprising: The first label management network element receives a registration request message from the first access and mobility management network element; In response to the registration request message, the first label management network element allocates the temporary identifier for the terminal device; The first label management network element sends the temporary identifier to the terminal device.

13. The method according to claim 11 or 12, characterized in that, The method further comprises: The first label management network element receives a fourth identifier from the first access and mobility management network element; wherein the fourth identifier is used to identify the first access and mobility management network element; The first label management network element allocates the temporary identifier using the fourth identifier.

14. A communication method, comprising: Comprise: The terminal device acquires a temporary identifier; wherein the temporary identifier is allocated by the first label management network element, and the temporary identifier comprises a first identifier, and the first identifier is used to identify the first label management network element; The terminal device acquires a temporary identifier; wherein the temporary identifier is allocated by the first label management network element, and the temporary identifier comprises a first identifier, and the first identifier is used to identify the first label management network element; The terminal device sends the first identifier and a service request message to an access network device according to the temporary identifier; wherein the service request message is used to request a communication service from the first label management network element, and the temporary identifier is contained in the service request message.

15. The method of claim 14, wherein, The terminal device acquires a temporary identifier, comprising: In the process of registration of the terminal device, the terminal device receives the temporary identifier allocated by the first label management network element.

16. A communications device, characterized by The apparatus comprises modules for performing the method of any of claims 1-15.

17. A communications device, characterized by Comprising: A processor configured to execute a computer program to cause the communication apparatus to perform the method of any of claims 1-15.

18. A communication chip, comprising: The chip has computer programs or instructions stored therein, which, when the chip is run on a communication device, cause the method of any of claims 1-15 to be implemented.

19. A computer-readable storage medium, characterized in that, The computer readable storage medium comprises computer programs or instructions, which, when run on a computer, cause the computer to perform the communication method of any of claims 1-15.

20. A computer program product, characterised in that, The computer program product comprises computer programs or instructions, which, when run on a computer, cause the computer to perform the communication method of any of claims 1-15.

Images