Communication method and related apparatus

Abstract

A communication method and a related apparatus, which relate to the technical field of communications. The method comprises: a first device acquiring first information, wherein the first information is used for instructing the updating of first registration state information of a terminal device, and the first registration state information comprises registration state information of the terminal device that is associated with the first device and maintained by the first device and / or registration state information of the terminal device that is associated with a second device and maintained by the first device; and the first device sending second information to the second device, wherein the second information is used for instructing the updating of second registration state information of the terminal device, the second registration state information comprises registration state information of the terminal device that is associated with the first device and maintained by the second device and / or registration state information of the terminal device that is associated with the second device and maintained by the second device, a first network and a second network are in a management relationship, the first device is configured in the first network, and the second device is configured in the second network. By means of the method, the registration management states maintained by a main network and a subnet can be enabled to remain consistent.

Description

A communication method and related apparatus

[0001] This application claims priority to Chinese Patent Application No. 202510124326.3, filed with the State Intellectual Property Office of China on January 26, 2025, entitled "A Communication Method and Related Device", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to a communication method and related apparatus. Background Technology

[0003] In fifth-generation communication systems, a private network architecture is introduced. This architecture comprises a central network and subnets. Subnets, for example, are networks deployed near service servers and must deploy at least a user plane function (UPF). The UPFs within a subnet are located near the customer server. The central network can correspond to multiple subnets, meaning it supports establishing sessions through UPFs in multiple subnets. The central network can be a public network, such as a centrally deployed network (e.g., a core network) by an operator. Subnets can be local networks deployed near customers. User equipment (UEs) can access the central network of the private network architecture via base stations. The central network establishes sessions via UPFs in the local network for transmitting user plane data. This allows UEs to obtain service data from the customer server through the UPFs in the local network. Since the UPFs in the local network are deployed near the customer server, the transmission latency of service data between the UE and the customer server can be reduced.

[0004] Currently, communication between the subnet and the Radio Access Network (RAN) typically requires forwarding through the core network function (NF) of the main network. When the subnet's UPF and Mobility Management (MM) network elements are deployed at the subnet level, both the main network and the subnet maintain a Registration Management (RM) status.

[0005] Due to the deployment of subnet network elements, there may be inconsistencies in the registration status information of terminal devices maintained by the main network and the subnet respectively. Summary of the Invention

[0006] This application provides a communication method and related apparatus that enables the registration management status of the main network and subnets to remain consistent, allowing user equipment to smoothly conduct business communications.

[0007] Firstly, a communication method is provided, which can be applied to a large network (or central network) and / or a subnet network (or local network). Specifically, the executing entity of the method is a first device, which can be a network element in the large network, for example, an access management (AM) function network element in the large network, or a component of the access management function network element, such as a chip; it can also be a network element in the subnet network, for example, a mobility management function network element in the subnet network, or a component of the mobility management function network element, such as a chip; the executing entity of the method can also be other devices capable of implementing the functions of the first device, which is not limited in this application. The method is described below using the first device as an example. The first device can perform the following operations:

[0008] The first device acquires first information, which is used to indicate the updating of the first registration status information of the terminal device; the first registration status information includes the registration status information of the terminal device associated with the first device maintained by the first device and / or the registration status information of the terminal device associated with the second device maintained by the first device.

[0009] The first device sends second information to the second device. The second information is used to instruct the updating of the second registration status information of the terminal device. The second registration status information includes the registration status information of the terminal device associated with the first device maintained by the second device and / or the registration status information of the terminal device associated with the second device maintained by the second device. The first network and the second network have a management relationship. The first device is configured on the first network and the second device is configured on the second network.

[0010] Optionally, the first registration status information and the second registration status information can be the registration status of the same terminal device. It should be understood that the first registration status information is the registration status information of the terminal device in the first device, and the second registration status information is the registration status information of the terminal device in the second device.

[0011] Optionally, the first registration status information can be either unregistered (dereg) or registered (reg), and the second registration status information can also be either unregistered (dereg) or registered (reg). Furthermore, the first and second registration status information may be consistent or inconsistent. The method provided in this application mainly addresses the problem of inconsistencies between the registration statuses represented by the first and second registration status information.

[0012] Considering that some network elements in the subnet are deployed in a decentralized manner, resulting in some network elements in the subnet not having direct connection interfaces with the shared RAN, but instead forwarding data through the main network, in cases where the registration status represented by the first registration status information and the second registration status information is inconsistent, the data packets of the terminal device may not be able to be delivered to the subnet network. For example, if the registration status represented by the first registration status information and the second registration status information is inconsistent, such as the first registration status being unregistered and the second registration status information being registered, and the first device is a network element in the main network and the second device is a network element in the subnet, since the registration status corresponding to the terminal device in the main network is unregistered, the services of the terminal device and the subnet cannot be forwarded through the main network, thereby causing the service process to be interrupted.

[0013] In this embodiment, the first device acquires first information and sends second information to the second device, enabling the second device to recognize changes in the registration status information of the terminal device and maintaining consistency between the registration status information corresponding to the terminal device in the second device and the first device. This avoids data packet transmission failures and business process interruptions caused by inconsistent registration status.

[0014] Optionally, the first device is a network element in the subnet, and the first information can be sent from the terminal device to the first device or from the second device to the first device. The second device is a network element in the main network.

[0015] Optionally, the first device is a network element in the main network, and the first information can be sent from the terminal device to the first device or from the second device to the first device. The second device is a network element in the subnet.

[0016] Optionally, the first registration status information includes registration status information of terminal devices associated with the first device maintained by the first device, and / or registration status information of terminal devices associated with the second device maintained by the second device. This means that in the case where the first device is a large network element and the second device is a subnet element, the large network element stores registration status information of terminal devices associated with the large network, or stores registration status information of terminal devices associated with the subnet, or both.

[0017] Optionally, the second registration status information includes the registration status information of terminal devices associated with the first device maintained by the second device and / or the registration status information of terminal devices associated with the second device maintained by the second device. This means that in the case where the first device is a large network element and the second device is a subnet element, the subnet element stores the registration status information of terminal devices associated with the large network, or stores the registration status information of terminal devices associated with the subnet, or both.

[0018] Optionally, the first registration status information and the second registration status information are registration status information associated with the same device and corresponding to the terminal device. For example, the first registration status information is the registration status information maintained by the subnet element and associated with it, and the second registration status information is the registration status information maintained by the main network element and associated with it. In this case, both the main network element and the subnet element maintain the registration status information associated with the subnet element. This means that the registration status information in the first device and the second device can actually be the same registration status information, but it is maintained by two different devices.

[0019] Optionally, the first registration status information and the second registration status information are registration status information associated with different devices and corresponding to the terminal device. For example, the first registration status information is the registration status information maintained by the subnet element and associated with that subnet element, and the second registration status information is the registration status information maintained by the main network element and associated with that main network element. In this case, the main network element maintains the registration status information associated with that main network element, and the subnet element maintains the registration status information associated with that subnet element. This means that the registration status information in the first device and the second device can be different registration status information maintained by the two devices respectively.

[0020] In one optional implementation, the second information is specifically used to notify the first device to update the second registration status information to the third registration status information, and the device may perform the following operations:

[0021] The first device updates the first registration status information to the third registration status information.

[0022] In this embodiment, the first device directly updates the second registration status information by notifying the second device, which simplifies the update process, reduces the negotiation process, and improves the update efficiency.

[0023] In one optional implementation, the second information is specifically used to request an update of the second registration status information to the third registration status information, and the first device can perform the following operations:

[0024] The first device receives a first response message from the second device. The first response message is used to indicate whether the registration status update is successful or the registration status update fails. If the registration status update is successful, it is used to indicate that the second registration status information is updated to the third registration status information. If the registration status update fails, it is used to indicate that the second registration status information has not been updated.

[0025] In this embodiment, by receiving the first response information from the second device, the first device can confirm whether the registration status update was successful, thereby ensuring the accuracy of the update operation.

[0026] In one optional implementation, the first response information is used to indicate that the registration status update was successful, and the first device can perform the following operations:

[0027] Based on the first response information, the first device updates the first registration status information to the third registration status information.

[0028] In this embodiment, by sending a second response message to the terminal device to inform it of the registration status update result, the user can promptly understand the registration status of the terminal device.

[0029] In one alternative implementation, the following operations are included:

[0030] The first device sends a second response message to the terminal device, the second response message indicating at least one of the following:

[0031] The first registration status information has been successfully updated;

[0032] First registration status information update failed;

[0033] The second registration status information has been successfully updated;

[0034] Second registration status information update failed;

[0035] The first and second registration status information have been successfully updated.

[0036] The first and second registration status information updates failed.

[0037] Secondly, a communication method is provided, which can be applied to a large network (or central network) and / or a subnet network (or local network). Specifically, the executing entity of the method is a second device, which can be a network element in the large network, for example, an access management (AM) function network element or a component of an access management function network element, such as a chip; or a network element in the subnet network, for example, a mobility management function network element or a component of a mobility management function network element, such as a chip. The executing entity of the method can also be other devices capable of implementing the functions of the second device, and this application does not limit this. It should be understood that the first device and the second device belong to different networks. For example, if the first device is a network element or a component of a network element in the large network, the second device is a network element or a component of a network element in the subnet network.

[0038] The following explanation uses a second device as an example to illustrate this method. The second device can perform the following operations:

[0039] The second device receives second information from the first device. The second information is used to instruct the updating of the second registration status information of the terminal device. The second registration status information includes the registration status information of the terminal device associated with the first device maintained by the second device and / or the registration status information of the terminal device associated with the second device maintained by the second device. The first network and the second network have a management relationship. The first device is configured in the first network and the second device is configured in the second network.

[0040] The second device updates the second registration status information.

[0041] In this embodiment, the second device receives second information from the first device and updates its maintained registration status information accordingly, ensuring the synchronization of terminal device registration status information between the two devices. Furthermore, by updating the registration status information in a timely manner, the second device can more effectively handle services related to the terminal device.

[0042] In one optional implementation, the second information is specifically used to request an update of the second registration status information to the third registration status information, where the third registration status information is in a non-registered state. Updating the second registration status information includes the following operations:

[0043] If the first condition is met, the second device will update the second registration status information to the third registration status information. The first condition includes that there are no pending services related to the registration status information of the terminal device.

[0044] In one optional implementation, the second information is specifically used to request an update of the second registration status information to the third registration status information, where the third registration status information is a registered state. Updating the second registration status information includes the following operations:

[0045] If the second condition is met, the second device will update the second registration status information to the third registration status information. The second condition includes the existence of pending business related to the registration status information of the terminal device.

[0046] In this embodiment, the second device can flexibly choose whether to update the registration status information based on whether there are any pending services related to the registration status information of the terminal device, thus avoiding service interruptions caused by blind updates. Furthermore, status updates are only performed under specific conditions, reducing unnecessary system overhead and improving resource utilization efficiency.

[0047] In one alternative implementation, the following operation is also included:

[0048] The second device sends a first response message to the first device. The first response message is used to indicate that the registration status update is successful. The successful registration status update is used to indicate that the second registration status information is updated to the third registration status information.

[0049] In one alternative implementation, the following operation is also included:

[0050] If the third condition is met, the second device sends a first response message to the first device. The first response message indicates that the registration status update has failed. The registration status update failure indicates that the second registration status information has not been updated. The third condition includes the existence of pending business related to the registration status information of the terminal device.

[0051] In one alternative implementation, the following operation is also included:

[0052] If the fourth condition is met, the second device sends a first response message to the first device. The first response message indicates that the registration status update has failed. The registration status update failure indicates that the second registration status information has not been updated. The fourth condition includes the absence of any pending business related to the registration status information of the terminal device.

[0053] In this embodiment, by sending a first response message to the first device, the second device can confirm the result of the registration status update, thus enhancing the reliability of communication. Furthermore, in the event of an update failure, the first device can quickly locate the problem based on the response message (the first response message), facilitating subsequent troubleshooting and repair.

[0054] In one optional implementation, the second information is specifically used to notify the user to update the second registration status information to the third registration status information. Updating the second registration status information includes the following operations:

[0055] The second device updates the second registration status information to the third registration status information.

[0056] Thirdly, a communication method is provided, wherein the executing entity of the method can be a terminal device or a component of the terminal device, such as a chip. The executing entity of the method can also be other devices capable of performing functions similar to those of the terminal device; this application does not limit this.

[0057] The following explanation uses a terminal device as an example to illustrate this method. The terminal device can perform the following operations:

[0058] The terminal device sends first information to the first device, the first information being used to instruct the terminal device to update its first registration status information; the first registration status information includes the registration status information of the terminal devices associated with the first device maintained by the first device and / or the registration status information of the terminal devices associated with the second device maintained by the first device.

[0059] The terminal device receives a second response information from the first device. The second response information is used to indicate whether the registration status update of the terminal device was successful or failed. The first network and the second network are in a management relationship, with the first device configured on the first network and the second device configured on the second network.

[0060] In this embodiment, the terminal device activates the first device to detect / update registration status information by actively triggering the first device (such as sending the first information as described above), thereby ensuring the consistency of registration status information between the first device and the second device and avoiding unexpected interruption of the business process.

[0061] Fourthly, a communication method is provided, wherein the executing entity of the method can be an access network device or a component of the access network device, such as a chip. The executing entity of the method can also be other devices capable of performing functions similar to those of the access network device; this application does not limit this.

[0062] The following explanation uses an access network device as an example to illustrate this method. The access network device can perform the following operations:

[0063] The access network device receives first information sent by the terminal device. The first information is used to indicate the updating of the terminal device's first registration status information. The first registration status information includes the registration status information of the terminal device associated with the first device maintained by the first device and / or the registration status information of the terminal device associated with the second device maintained by the first device. The first network and the second network have a management relationship. The first device is configured in the first network and the second device is configured in the second network.

[0064] The access network device sends the first information to the first device.

[0065] In this embodiment, the entity that actively triggers the consistency detection / update of registration status information is the access network device. This is mainly achieved by receiving the first information sent by the terminal device and forwarding it to the first device, thereby enhancing inter-network collaboration. Furthermore, the access network device can participate in the registration status management of the terminal device, which helps optimize the allocation and utilization of network resources.

[0066] Fifthly, a communication method is provided, which can be applied to a large network (or central network) and / or a subnet network (or local network). Specifically, the executing entity of the method is a first device, which can be a network element in the large network, for example, an access management (AM) function network element in the large network, or a component of the access management function network element, such as a chip; it can also be a network element in the subnet network, for example, a mobility management function network element in the subnet network, or a component of the mobility management function network element, such as a chip; the executing entity of the method can also be other devices capable of implementing the functions of the first device, which is not limited in this application. The method is described below using the first device as an example. The first device can perform the following operations:

[0067] The first device acquires third and fourth information. The third information is used to indicate the first registration status information of the terminal device being updated and maintained. The first registration status information includes the registration status information of the terminal device associated with the first device maintained by the first device and / or the registration status information of the terminal device associated with the second device maintained by the first device. The fourth information includes the second registration status information of the terminal device. The second registration status information includes the registration status information of the terminal device associated with the first device maintained by the second device and / or the registration status information of the terminal device associated with the second device maintained by the second device.

[0068] The first device updates the first registration status information based on the fourth information.

[0069] Optionally, the third and fourth information are acquired asynchronously. For example, the first device acquires the fourth information after acquiring the third information.

[0070] In this embodiment of the application, changes to the first registration status information of the first device also refer to the second registration status information in order to maintain the consistency of registration status information between devices for the same terminal device.

[0071] In one optional implementation, the third information is specifically used to indicate updating the first registration status information to the fourth registration status information. Updating the first registration status information based on the fourth information includes the following operations:

[0072] If the fifth condition is met, the first device updates the first registration status information to the fourth registration status information; wherein the fifth condition includes at least one of the following:

[0073] The fourth information includes the second registration status information, which is the fourth registration status information;

[0074] Data packets were not transmitted to the terminal device within the first available time.

[0075] In this embodiment, the first device can flexibly choose whether to update the registration status information based on the specific content of the fourth information and the communication status between the first device and the terminal device, thus optimizing the update strategy. Furthermore, status updates are only performed under specific conditions, reducing unnecessary system overhead and the number of updates.

[0076] Optionally, the fourth information includes second registration status information from different second devices. If the second registration status information of all second devices is consistent and all of them are the fourth registration status information, the first device updates the first registration status information.

[0077] Optionally, the fourth piece of information is determined by the first device itself. If the first device does not engage in any business communication with the terminal device related to the registration status information within a certain period of time (the first time) and does not transmit any data packets, the first device updates the first registration status information.

[0078] In one alternative implementation, obtaining the fourth information includes the following operations:

[0079] The first device receives the fourth information sent by the second device, which is used to indicate the second registration status information.

[0080] In one alternative implementation, obtaining the fourth information includes the following operations:

[0081] The first device sends a fifth message to the second device, which is used to request the second registration status information.

[0082] The first device receives the fourth message from the second device.

[0083] In one alternative implementation, the following operations are further included before obtaining the fourth information:

[0084] The first device sends a sixth message to the second device, the sixth message being used to request that the registration status information of the terminal device be updated to the second registration status information;

[0085] The first device receives a third response message from the second device. The third response message indicates that the registration status information has been successfully updated. The successful update of the registration status information indicates that the second registration status information has been updated to the fourth registration status information.

[0086] It should be understood that the first device may determine the fourth information based on the third response information, or the third response information may be the fourth information.

[0087] In one alternative implementation, the following operations are further included before obtaining the fourth information:

[0088] The first device receives the seventh message sent by the second device. The seventh message is used to request an update of the first registration status information to the fourth registration status information.

[0089] The first device sends a fourth response message to the second device. The fourth response message is used to indicate that the first registration status information has been successfully updated. The successful update of the first registration status information is used to indicate that the first registration status information has been updated to the fourth registration status information.

[0090] It should be understood that before obtaining the fourth information, the first device and the second device had interacted regarding the first registration status information, such as the aforementioned seventh information being used to request an update of the first registration status information to the fourth registration status information, and the first device updating the first registration status information to the fourth registration status information. Based on this, the first device determines the fourth information.

[0091] In one alternative implementation, the following operations are further included before obtaining the fourth information:

[0092] The first device receives the eighth message sent by the second device. The eighth message is used to notify the user to update the first registration status information to the fourth registration status information.

[0093] In this embodiment, the first device can acquire the fourth information through multiple methods, improving the flexibility and reliability of information acquisition. Furthermore, the aforementioned multiple acquisition methods enable the first device to better adapt to the needs of different network environments and device types, enhancing system compatibility.

[0094] In one alternative implementation, the following operations are further included before obtaining the fourth information:

[0095] The first device parses the ninth information transmitted between the terminal device and the second device. The ninth information is used to indicate the second registration status information.

[0096] In one alternative implementation, the following operations are also included:

[0097] The first device receives the tenth information sent by the terminal device, which is used to indicate the second registration status information.

[0098] Optionally, the tenth message sent by the terminal device may include some of the second registration status information of the second device.

[0099] The first device can determine the fourth information based on the aforementioned tenth information.

[0100] In one alternative implementation, the following operations are also included:

[0101] The first device receives the eleventh message sent by the third device. The eleventh message is used to indicate the registration status information of the terminal device maintained by the second device.

[0102] Optionally, the third device is an access network device, and the eleventh message sent by the third device includes registration status information of one or more terminal devices maintained by the second device.

[0103] In the above embodiments, the first device can obtain registration status information not only through the second device, but also through other channels such as terminal devices and access network devices, thus broadening the information source channels.

[0104] Optionally, the first device can obtain registration status information through multiple channels and make a comprehensive judgment, which can improve the accuracy and reliability of the information.

[0105] Sixthly, embodiments of this application provide a communication device, the communication device including a processor coupled to a memory, wherein: the memory is used to store instructions; the processor is used to execute the methods in any one of the possible designs of the first to fifth aspects or more above according to the instructions stored in the memory. Optionally, the communication device may further include the memory. Optionally, the communication device may further include a transceiver for supporting the communication device in sending and / or receiving information in the above methods. Optionally, the communication device may be a terminal device or a device in a terminal device, such as a chip or a chip system, wherein the chip system includes at least one chip, and the chip system may also include other circuit structures and / or discrete devices.

[0106] In a seventh aspect, embodiments of this application provide a communication device for implementing the method in any of the possible designs of the first to fifth aspects or above, including corresponding functional modules, such as processing units, communication units, etc., respectively for implementing the steps in the above methods.

[0107] Eighthly, embodiments of this application provide a computer-readable storage medium storing computer-readable instructions that, when read and executed by a computer, cause a communication device to perform any of the possible designs in the first to fifth aspects or more.

[0108] Ninthly, embodiments of this application provide a computer program product that, when read and executed by a computer, causes a communication device to perform any one of the possible designs in the first to fifth aspects or more.

[0109] In a tenth aspect, embodiments of this application provide a chip connected to a memory for reading and executing software programs stored in the memory to perform a method in any of the possible designs in the first to fifth aspects or more.

[0110] Eleventhly, embodiments of this application provide a communication device including a processor, the processor being coupled to a transceiver to read and execute instructions in the memory to perform a method in any of the first to fifth aspects or more.

[0111] In a twelfth aspect, embodiments of this application provide a communication system including means for performing a method in the first aspect or any possible design of the first aspect and means for performing a method in the second aspect or any possible design of the second aspect.

[0112] Optionally, the communication system may also include means for performing the methods in the third aspect or any of the possible designs in the third aspect.

[0113] Optionally, the communication system may also include means for performing the methods in the fourth aspect or any of the possible designs in the fourth aspect.

[0114] The beneficial effects of aspects six through twelfth above can be referred to the descriptions of the beneficial effects in aspects one through five. Attached Figure Description

[0115] Figure 1 is a schematic diagram of a single-SIM single-network and a dual-SIM dual-network embodiment provided in this application;

[0116] Figure 2 is a schematic diagram of a single-card dual-network solution provided in an embodiment of this application;

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

[0118] Figure 4 is a schematic diagram of a 5GS architecture provided in an embodiment of this application;

[0119] Figure 5 is a schematic diagram of the architecture of another communication system provided in an embodiment of this application;

[0120] Figure 6 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0121] Figure 7 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0122] Figure 8 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0123] Figure 9 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0124] Figure 10 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0125] Figure 11 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0126] Figure 12 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0127] Figure 13 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0128] Figure 14 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0129] Figure 15 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0130] Figure 16 is a schematic diagram of the structure of another communication device provided in an embodiment of this application. Detailed Implementation

[0131] First, let's introduce the key terms that may be involved in the embodiments of this application.

[0132] 1. Registration Status Information (RM state)

[0133] In current fifth-generation communication systems, the Access Mobility Function (AMF) maintains two UE state states, specifically the RM state and the CM state.

[0134] RM state: includes registered state (reg) and unregistered state (dereg); it represents whether the core network (CN) retains the UE context; if the UE context exists, the UE can directly perform services, otherwise re-authentication is required.

[0135] Connection Management (CM) state: includes idle state (CM_idle) and connected state (CM_connected). From the UE's perspective, when Radio Resource Control (RRC) is released, it is considered to have entered the CM_idle state; otherwise, it is considered to be in the CM_connected state.

[0136] In addition, the CN also maintains the UE context, and the existence of information in the UE context is strongly correlated with the RM state. If the RM state maintained by the AMF is the registered state, then there is a UE context; otherwise, there is no UE context.

[0137] The current RM state transition relationships include: transitioning from a registered state to a non-registered state, which can be achieved by the UE actively requesting release or by the network releasing the state (e.g., timer timeout). Transitioning from a non-registered state to a registered state can be achieved by the UE initiating a service request (either by the UE actively initiating an uplink service or by a downlink paging triggered by a downlink service).

[0138] The current triggering conditions for RM state changes include: a UE requesting context deregistration; if the AMF accepts, the UE context is cleared, and the UE's RM state is changed from registered to unregistered. Alternatively, an AMF requesting context deregistration; if the UE accepts, both the AMF and the UE clear their respective maintained UE contexts, and the UE's RM state is changed from registered to unregistered.

[0139] An AMF anomaly causes an abnormal release of the UE context, changing the UE's RM state from a registered state to a non-registered state.

[0140] The following describes communication scenarios related to registration status information.

[0141] Currently, 5G only supports UEs to access the network via a single SIM card and a single network. For example, a UE can access the ToC (To Consumer) network with one SIM card, or access the ToB (To Business) network with one SIM card. If the same UE has both main network services (ToC) and sub-network services (ToB) at the same time, the UE needs two SIM cards to complete the task.

[0142] Please refer to Figures 1 and 2 for details. Figure 1 is a schematic diagram of a single-SIM single-network and a dual-SIM dual-network configuration provided in an embodiment of this application. Figure 2 is a schematic diagram of a single-SIM dual-network configuration provided in an embodiment of this application.

[0143] Figure 1 includes three scenarios: Scenario 1, Scenario 2, and Scenario 3. Scenario 1 corresponds to a terminal device with a single SIM card accessing the main network, Scenario 2 corresponds to a terminal device with a single SIM card accessing the subnet network, and Scenario 3 corresponds to a terminal device with two SIM cards accessing the main network and the subnet network respectively.

[0144] To eliminate the limitation that a single SIM card in a terminal device cannot access two networks simultaneously, current communication technology is considering an architecture adjustment that allows a single SIM card to access two networks, such as the aforementioned deployment of subnet UPF and Mobility Management (MM) network elements, as shown in Figure 2.

[0145] In Figures 2(a) and (b), the UPF2 and MM2 of the subnet are deployed in a recessed manner, separate from the UPF1 and MM1 of the main network. Terminal devices can access the main network and the subnet network respectively through the access network. In this scenario, the main network and the subnet can maintain the same registration status information or different registration status information. For example, if the main network and the subnet maintain the same registration status information, then the main network can maintain the registration status information associated with the main network, and the subnet can also maintain the registration status information associated with the main network; if the main network and the subnet maintain different registration status information, for example, the main network maintains the registration status information of the terminal devices associated with the main network, and the subnet maintains the registration status information associated with the subnet.

[0146] In Figure 2(a), the subnet is not directly connected to the access network. Since the main network and the subnet maintain their respective registration status information, but the signaling and data of the subnet depend on the main network for transmission, the registration status information of the subnet is constrained by the registration status information of the main network. For example, if the UE is performing subnet services and the subnet is in a registered state, it is abnormal for the main network to be in a non-registered state. This will cause the subnet and the terminal device to be unable to transmit data normally.

[0147] In Figure 2(b), both the main network and the subnet are directly connected to the access network. If the main network and the subnet maintain their own registration status information respectively, and the registration status information of the two is relatively independent, then the registration status information of the two may be out of sync. Although the services between the terminal device and the subnet can still be carried out, the services between the two networks related to the terminal device may not be able to proceed smoothly.

[0148] Based on this, embodiments of this application provide a communication method and related equipment to solve the problem of inconsistent registration status information between the main network and subnets for the same terminal device.

[0149] The following describes the key information and actions that may be involved in the embodiments of this application.

[0150] In the embodiments of this application, "instruction" can include direct and indirect instructions, as well as explicit and implicit instructions. The information indicated by a certain piece of information is called the information to be instructed. In the specific implementation process, there are many ways to instruct the information to be instructed, such as, but not limited to, directly instructing the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly instruct the information to be instructed by instructing other information, where there is a relationship between the other information and the information to be instructed. It can also instruct only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent. At the same time, common parts of various pieces of information can be identified and uniformly indicated to reduce the instruction overhead caused by individually indicating the same information.

[0151] Furthermore, the specific indication method can also be any existing indication method, such as, but not limited to, the above-mentioned indication methods and their various combinations. Specific details of various indication methods can be found in existing technologies, and will not be repeated here. As described above, for example, when multiple pieces of information of the same type need to be indicated, the indication methods for different pieces of information may differ. In the specific implementation process, the required indication method can be selected according to specific needs. This application embodiment does not limit the selected indication method; therefore, the indication methods involved in this application embodiment should be understood to cover various methods that enable the party to be indicated to obtain the information to be indicated.

[0152] It should be understood that the information to be indicated can be sent as a whole or divided into multiple sub-information messages sent separately, and the sending period and / or timing of these sub-information messages can be the same or different. The specific sending method is not limited in this application embodiment. The sending period and / or timing of these sub-information messages can be predefined, for example, according to a protocol, or configured by the sending device by sending configuration information to the receiving device.

[0153] In this application, "sending information" can be understood as one device sending information to another device, or it can also be understood as one logical module within a device sending information to another logical module. For example, "network device sending information" can be understood as a network device sending information to another device (such as a terminal or other network device), or it can be understood as logical module 1 in the network device sending information to logical module 2 in the network device.

[0154] In this application, "receiving information" can be understood as one device receiving information from another device, or it can also be understood as a logical module within a device receiving information from another logical module. For example, "network device receiving information" can be understood as a network device receiving information from another device (such as a terminal or other network device), or it can be understood as logical module 1 in the network device receiving information from logical module 2 in the network device.

[0155] In this application, phrases such as "sending information to... (e.g., a terminal)" or related illustrations in the accompanying drawings can be understood as indicating that the destination of the information is a terminal. This can include sending information directly or indirectly to a terminal. Similarly, phrases such as "receiving information from... (e.g., a terminal)," "receiving information from... (e.g., a terminal)," or "receiving information sent by (e.g., a terminal)," or related illustrations in the accompanying drawings, can be understood as indicating that the source of the information is a terminal. This can include receiving information directly or indirectly from a terminal. Information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be interpreted similarly and will not be elaborated further here.

[0156] "Predefined" or "pre-configured" can be achieved by pre-saving corresponding codes, tables, or other means that can be used to indicate relevant information in the device. This application does not limit the specific implementation method. "Saving" can refer to saving in one or more memories. These memories can be separate installations or integrated into the encoder, decoder, processor, or communication device. Alternatively, some memories can be separately installed, while others are integrated into the decoder, processor, or communication device. The type of memory can be any form of storage medium, and this application does not limit this.

[0157] The “protocol” mentioned in the embodiments of this application may refer to a protocol family in the field of communication, a standard protocol with a similar protocol family frame structure, or a related protocol applied to future communication systems. The embodiments of this application do not specifically limit this.

[0158] In the embodiments of this application, descriptions such as "when," "under the circumstances," "if," and "if" all refer to the device making corresponding processing under certain objective circumstances, and are not limited to a specific time. They do not require the device to make a judgment action during implementation, nor do they imply any other limitations.

[0159] In the description of the embodiments of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can represent A or B. In the embodiments of this application, "and / or" is merely a description of the relationship between the related objects, indicating that there can be three relationships. For example, A and / or B can represent three cases: A exists alone, A and B exist simultaneously, and B exists alone. A and B can be singular or plural.

[0160] In the embodiments of this application, the terms "system" and "network" can be used interchangeably; "cell", "base station" and "network device" can also be used interchangeably. For example, "target cell" can also be called "target base station" or "target network device", and "source cell" can also be called "source base station" or "source network device".

[0161] Furthermore, in the description of the embodiments of this application, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of a single item or a plurality of items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. Additionally, to facilitate a clear description of the technical solutions of the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and that "first" and "second" do not necessarily imply difference. Meanwhile, in the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. To be precise, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete way to facilitate understanding.

[0162] 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.

[0163] To facilitate understanding of the embodiments of this application, a communication system will be used as an example to describe in detail the communication system applicable to the embodiments of this application.

[0164] The communication method involved in this application can be applied to the communication system shown in Figure 3. This network system may include terminal devices and network devices. The network devices may include access network devices and core network devices; the core network devices may also be referred to as core network devices. It is understood that the communication system shown in Figure 3 is merely illustrative, and the communication system may also include other network devices, such as wireless relay devices and wireless backhaul devices, which are not shown in Figure 3. The embodiments of this application do not limit the number of access network devices, core network devices, and terminals included in this wireless communication system.

[0165] It can be further understood that the wireless communication system of this application embodiment is a network that provides wireless communication functions. The wireless communication system can employ different communication technologies, such as Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency-Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), and Carrier Sense Multiple Access with Collision Avoidance. Based on factors such as capacity, speed, and latency, networks can be categorized into 2G (Generation) networks, 3G networks, 4G networks, future evolution networks, or future communication networks, such as the 5th Generation Wireless Communication System (5G) network. 5G networks can also be referred to as New Radio (NR), or in the context of next-generation wireless communication networks, such as the sixth generation (6G). For ease of description, this application may sometimes simply refer to wireless communication networks as "networks." The aforementioned wireless communication networks / systems also include radio access networks (RAN).

[0166] RAN can be a 3GPP-related cellular system, such as a 5G / NR mobile communication system, or a future-oriented evolution system / network. RAN can also be an open RAN (O-RAN or ORAN), a cloud radio access network (CRAN), a virtualized RAN (vRAN), a non-terrestrial network (NTN), a satellite communication network, a high altitude platform station (HAPS) communication network, an integrated access and backhaul (IAB) communication network, a reconfigurable intelligent surface (RIS) communication network, an integrated sensing and communication (ISAC) network, etc. RAN can also be a communication system that integrates two or more of the above systems.

[0167] Furthermore, the access network device in this application embodiment can be a device with wireless transceiver capabilities for communicating with terminal devices, or it can be a device that connects terminal devices to a wireless network. The access network device can be a node in the radio access network, also known as a base station, or a radio access network (RAN) node (or device). The access network device can be an evolved Node B (eNB or eNodeB) in LTE; or a next-generation Node B (gNB) in a 5G network; or a base station in a future evolved public land mobile network (PLMN), a broadband network gateway (BNG), an aggregation switch, or a non-3GPP access device, etc. Optionally, the access network equipment in this application embodiment may include various forms of base stations, such as: macro base stations, micro base stations (also known as small stations), relay stations, access points, equipment that implements base station functions in communication systems evolved after 5G, access points (APs), transmitting and receiving points (TRPs), transmitting points (TPs) in WiFi systems, mobile switching centers, and equipment that performs base station functions in device-to-device (D2D), vehicle-to-everything (V2X), and machine-to-machine (M2M) communications. It may also include centralized units (CUs) and distributed units (DUs) in cloud radio access networks (C-RAN) systems, and access network equipment in non-terrestrial network (NTN) communication systems, i.e., it can be deployed on high-altitude platforms or satellites. This application embodiment does not specifically limit this.

[0168] The core network equipment involved in this application may include, in LTE, the Mobile Management Entity (MME) and Serving Gateway (S-GW); in 3G, the Service General Packet Radio Service Support Node (SGSN) and Gateway General Packet Radio Service Support Node (GGSN); in 5G, the Next Generation Core (NG-core); and the Sensing Function Entity in this application. It should be understood that the embodiments of this application do not limit the specific technologies or equipment forms used in the core network equipment.

[0169] In this application embodiment, the means for implementing the functions of the network device can be the network device itself, or a chip (or chip system) or other functional module capable of implementing the functions of the network device. For example, the chip or functional module is disposed in the network device. Other functional modules can be combined devices or components capable of implementing the functions of the network device. Optionally, the means for implementing the functions of the network device can also have virtual devices or software that possess the functions of the network device, such as a computer-readable storage medium, computer program product, etc., capable of executing methods related to the network device. The embodiments of this application do not limit the specific technology or specific device form adopted by the network device.

[0170] In the embodiments of this application, the first device and the second device may be network devices, or some devices in a network device, or a certain device in a network device.

[0171] Furthermore, the terminal device involved in this application can also be referred to as a terminal device, user equipment (UE), mobile station (MS), mobile terminal (MT), etc., and is a device that provides voice and / or data connectivity to a user. For example, the terminal can be a handheld device with wireless connectivity, an in-vehicle device, a wearable device, etc. Currently, some examples of terminals include: smartphones (Mobile Phones), pocket personal computers (PPCs), handheld computers, personal digital assistants (PDAs), laptops, tablets, wearable devices, or in-vehicle devices, etc. In addition, when it is a vehicle-to-everything (V2X) communication system, the terminal device can also be an in-vehicle device. It should be understood that the embodiments of this application do not limit the specific technology or specific device form used by the terminal.

[0172] In this application embodiment, the means for implementing the functions of the terminal device can be the terminal device itself, or a chip (or chip system) or other functional module, which can implement the functions of the terminal device. For example, the chip or functional module is disposed in the terminal device. Other functional modules can be combined devices or components that can implement the functions of the terminal device. Optionally, the means for implementing the functions of the terminal device can also have virtual devices or software that have the functions of the terminal device, such as a computer-readable storage medium, computer program product, etc., capable of executing methods related to the terminal device. The embodiments of this application do not limit the specific technology or specific device form adopted by the terminal device.

[0173] In this embodiment, the access network device and the terminal device can employ any feasible wireless communication technology to transmit data to each other. The transmission channel corresponding to the access network device sending data or control information to the terminal device is called the downlink channel (DL), and the transmission channel corresponding to the terminal device sending data or control information to the access network device is called the uplink channel (UL). It is understood that the access network device involved in this embodiment can be a base station. Of course, the access network device can also be any other possible access network device, and the terminal can be any possible terminal; this application does not impose any limitations.

[0174] In this embodiment, the third device is the aforementioned access network device, and the terminal device communicates with the first device and / or the second device through the third device.

[0175] Of course, any feasible wireless communication technology can be used between access network equipment and core network equipment, as well as between terminal equipment and core network equipment, to achieve mutual data transmission. The core network equipment can also be any other possible core network equipment; this application does not limit it.

[0176] Figure 4 is a schematic diagram of a 5GS architecture provided in an embodiment of this application. As shown in Figure 4, 5GS includes an access network (AN) and a core network (CN), and may also include a terminal.

[0177] The aforementioned terminal can be a terminal with transceiver capabilities, or a chip or chip system that can be installed on the terminal. This terminal can also be referred to as user equipment (UE), access terminal, subscriber unit, user station, mobile station (MS), mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user apparatus. The terminals in the embodiments of this application may be mobile phones, cellular phones, smartphones, tablets, wireless data cards, personal digital assistants (PDAs), wireless modems, handsets, laptop computers, machine-type communication (MTC) terminals, computers with wireless transceiver capabilities, virtual reality (VR) terminals, augmented reality (AR) terminals, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, vehicle-mounted terminals, roadside units (RSUs) with terminal functions, etc. The terminal of this application may also be an on-board module, on-board unit, on-board component, on-board chip or on-board unit that is built into a vehicle as one or more components or units.

[0178] The aforementioned AN is used to implement access-related functions, providing network access capabilities for authorized users and determining transmission links of different quality levels to transmit user data based on user level, service requirements, etc. The AN forwards control signals and user data between the terminal and the CN. The AN may include access network equipment, also known as radio access network (RAN) equipment.

[0179] The CN (Network Access Center) is primarily responsible for maintaining the subscription data of the mobile network and providing terminals with functions such as session management, mobility management, policy management, and security authentication. The CN mainly includes all or some of the following functions: 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), and Application Function (AF).

[0180] As shown in Figure 4, 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, or AF, interact using service-oriented interfaces. For example, AUSF provides the service interface Nausf; AMF provides the service interface Namf; SMF provides the service interface Nsmf; NSSF provides the service interface Nnssf; NEF provides the service interface Nnef; NRF provides the service interface Nnrf; PCF provides the service interface Npcf; UDM provides the service interface Nudm; UDR provides the service interface Nudr; and AF provides the service interface Naf.

[0181] RAN equipment can be a device that provides access to terminals. For example, RAN equipment may include: access network equipment for next-generation mobile communication systems, such as 6G, such as 6G base stations; or in next-generation mobile communication systems, the network equipment may have other naming conventions, 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 5G base station, 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.

[0182] The User-Defined Processing (UPP) is primarily responsible for user data processing (forwarding, receiving, billing, etc.). For example, a UPF can receive user data from a data network (DN) and forward it to the terminal through access network equipment. Alternatively, a UPF can receive user data from the terminal through access network equipment and forward it to the DN. A DN refers to the operator's network that provides data transmission services to users. Examples include Internet Protocol (IP) multimedia services (IMS) and the Internet. A DN can be an external network of the operator or a network controlled by the operator, used to provide services to terminals. In a Protocol Data Unit (PDU) session, the UPF directly connected to the DN via N6 is also called the Protocol Data Unit Session Anchor (PSA).

[0183] AUSF is primarily used to perform security authentication for terminals.

[0184] AMF is primarily used for mobility management in mobile networks. Examples include user location updates, user network registration, and user handover.

[0185] SMF is primarily used for session management in mobile networks. This includes session establishment, modification, and release. Specific functions include assigning Internet Protocol (IP) addresses to users and selecting a UPF (User-Defined Provider) to handle packet forwarding.

[0186] 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.

[0187] NSSF is primarily used to select network slices for terminals.

[0188] NEF is primarily used to support the opening of capabilities and events.

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

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

[0191] 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.

[0192] 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.

[0193] In addition, the terms "function" and "functional network element" are used interchangeably in the following text. For example, "PCF" and "PCF network element" have the same meaning. This will be explained uniformly here and will not be repeated below.

[0194] Please refer to Figure 5, which is a schematic diagram of the architecture of another communication system provided in an embodiment of this application. It includes a main network, subnet networks, access network equipment, and terminal equipment.

[0195] In Figure 5, in parts (1) and (2), the large network (or central network) can deploy network functions such as AM and UPF. For ease of explanation, the above network functions deployed in the large network are referred to as AM1 and UPF1, respectively.

[0196] Subnets can also deploy network functions such as MM and UPF. For ease of explanation, the above network functions deployed in a subnet are referred to as MM2 and UPF2, respectively.

[0197] In part (1) of Figure 5, the main network is directly connected to the access network, while the subnet network is not directly connected to the access network. The terminal device communicates with the subnet network through the main network. This corresponds to part (a) of Figure 2.

[0198] In part (2) of Figure 5, the main network and subnet network are directly connected to the access network, and the terminal device can communicate with the main network and subnet network respectively. For example, in part (2), the subnet network can include network functions deployed near the campus in a campus scenario. For instance, UPF2 can be deployed near the campus. In this case, the UE in the campus can preferentially access the subnet network through the RAN near the campus and obtain service from the nearest location through UPF2, which can reduce service latency. This corresponds to part (b) of Figure 2.

[0199] Optionally, the main network and the subnet network can maintain the same RM state. For example, the subnet network element maintains the registration status information associated with the subnet network element, and the main network element also maintains the registration status information associated with the subnet network element. This means that the RM state in the main network and the subnet network is the same registration status information, but it is maintained by two different devices.

[0200] Optionally, the main network and the subnet network can maintain different RM states. For example, the main network element maintains the registration status information associated with the main network element, while the subnet element maintains the registration status information associated with the subnet element. This means that the RM states in the main network and the subnet network are different registration status information maintained by two different devices.

[0201] Optionally, in the above communication system, the network element in the large network can be called the first device, and the network element in the subnet can be called the second device. For example, AM1 in the large network can be called the first device, and MM2 in the subnet can be called the second device. The second device communicates with the terminal device through the first device.

[0202] Optionally, in the above communication system, the network element in the subnet network can be called the first device, and the network element in the main network network can be called the second device. For example, the second device communicates with the terminal device through the first device. For example, AM1 in the main network network can be called the second device, and MM2 in the subnet network can be called the first device. The second device communicates with the terminal device through the first device.

[0203] The method provided in this application will now be described in detail with reference to the accompanying drawings. In the embodiments of this application, communication devices (including terminal devices and network devices) can perform some or all of the steps in the embodiments of this application. These steps or operations are merely examples, and the embodiments of this application can also perform other operations or variations thereof. Furthermore, the steps can be performed in different orders as presented in the embodiments of this application, and it is not necessary to perform all the operations in the embodiments of this application.

[0204] The communication method provided in the embodiments of this application will be described in detail below with reference to Figure 6. This communication method can be applied to the communication system shown in Figures 3, 4, or 5, and can also be applied to any of the scenarios in Figure 2. The embodiments of this application are not limited thereto.

[0205] The flowchart shown in Figure 6 illustrates the method from the perspective of communication device interaction, but this application does not limit the subject executing the method. The method is described below using the application of the above method to a first device (large network element or subnet element) and a second device (large network element or subnet element) in the communication system shown in Figure 5 as examples. Exemplarily, the first device can be a network element in a large network, for example, it can be an Access Management (AM) function network element in the large network, or a component of the Access Management (AM) function network element, such as a chip or processor; it can also be a network element in a subnet network, for example, it can be a Mobility Management (MLM) function network element in the subnet network, or a component of the Mobility Management (MLM) function network element, such as a chip or processor; the first device can also be other devices capable of implementing some or all of the functions of the first device, which this application does not limit.

[0206] The second device can be a network element in a large network, such as an access management (AM) function network element or a component of an access management function network element, such as a chip; or it can be a network element in a subnet network, such as a mobility management function network element or a component of a mobility management function network element, such as a chip. The second device can also be other devices capable of performing some or all of the functions of the second device; this application does not limit this.

[0207] It should be understood that the first device and the second device belong to different networks. For example, if the first device is a network element or a component of a network element in a large network, the second device is a network element or a component of a network element in a subnet network.

[0208] Figure 6 is a flowchart illustrating a communication method provided in an embodiment of this application. As shown in Figure 6, the method may include steps S601 to S604. The steps shown in Figure 6 are described in detail below.

[0209] Step S601: The first device acquires the first information.

[0210] Step S602: The first device sends second information to the second device. Correspondingly, the second device receives the second information from the first device.

[0211] Step S603: The second device updates the second registration status information.

[0212] Step S604: The first device updates the first registration status information.

[0213] For step S601, the first information is used to indicate updating the first registration status information of the terminal device; the first registration status information includes the registration status information of the terminal devices associated with the first device maintained by the first device and / or the registration status information of the terminal devices associated with the second device maintained by the first device.

[0214] It should be understood that the first registration status information is the RM state of the terminal device stored in the first device. Optionally, the RM state can be the RM state associated with the first device, the RM state associated with the second device, or two RM states respectively associated with the first device and the second device.

[0215] In one optional implementation, the first registration status information includes registration status information of terminal devices associated with the first device maintained by the first device, and / or registration status information of terminal devices associated with the second device maintained by the second device. This means that in the case where the first device is a large network element and the second device is a subnet element, the large network element stores registration status information of terminal devices associated with the large network, or stores registration status information of terminal devices associated with the subnet, or both.

[0216] Optionally, the first device is a network element in the subnet, and the first information can be sent from the terminal device to the first device or from the second device to the first device. The second device is a network element in the main network.

[0217] Optionally, the first device is a network element in the main network, and the first information can be sent from the terminal device to the first device or from the second device to the first device. The second device is a network element in the subnet.

[0218] Optionally, the first information is triggered by the first device itself. For example, the first device is a network element in a large network, such as the change in registration status information caused by the UPF anomaly mentioned above.

[0219] Optionally, if the first information is information sent by the terminal device, then the method shown in Figure 6 should also include the following operation (not shown in the figure): the terminal device sends the first information to the first device.

[0220] Specifically, step S601 described above may involve the first device receiving first information from the terminal device.

[0221] In this embodiment, the terminal device activates the first device to detect / update registration status information by actively triggering the first device (such as sending the first information as described above), thereby ensuring the consistency of registration status information between the first device and the second device and avoiding unexpected interruption of the business process.

[0222] Optionally, the entity that actively activates the first device to detect / update registration status information can also be an access network device, where the first information is information sent by the access network device. For example, the access network device forwards the first information sent by the terminal device.

[0223] If the first information is sent by the access network device, then the method shown in Figure 6 should also include the following operations (not shown in the figure):

[0224] The access network device sends the first information to the first device.

[0225] Specifically, step S601 described above may involve the first device receiving first information from the access network device.

[0226] Furthermore, if the first information is forwarded by the access network device from the terminal device, then the above method should also include the following operation (not shown in the figure): the access network device receives the first information sent by the terminal device. Correspondingly, the above method should also include the terminal device sending the first information to the access network device.

[0227] In one alternative implementation, the first information may be a notification message, used to notify the first device to update the registration status information.

[0228] In an alternative implementation, the first information may also be a request message, used to request the first device to update the registration status information.

[0229] It should be understood that the first information is the information that triggers the first device to update the registration status information (first registration status information) of the terminal device. This is because there are three main reasons that trigger the update of the registration status information.

[0230] Reason 1: The terminal device requests to cancel the context.

[0231] Reason 2: The large network element requests to register the context.

[0232] Reason 3: Network element anomaly leading to abnormal context release. This anomaly can be understood as various situations where the network element is unable to communicate with the terminal device, such as communication link blockage or disconnection.

[0233] In summary, the registration status information update can be triggered by a request from the terminal device, a request from a network element (such as an AMF), or an anomaly in the network element. Therefore, the first information can be related to any of these three reasons. For example, the first information specifically requests the first device to deregister the terminal device context. Upon receiving the first information, the first device determines to perform a first registration status information update.

[0234] It should be understood that "used for" in the embodiments of this application does not mean that the device performs the operation, or that the information contains information after "used for", but rather that the corresponding operation can be achieved based on the information.

[0235] Regarding step S602, the second information is used to indicate updating the second registration status information of the terminal device. The second registration status information includes the registration status information of the terminal device associated with the first device maintained by the second device and / or the registration status information of the terminal device associated with the second device maintained by the second device. It should be understood that the RM state maintained by the second device can be the RM state associated with the first device, the RM state associated with the second device, or two RM states respectively associated with the first device and the second device.

[0236] In one optional implementation, the second registration status information includes registration status information of terminal devices associated with the first device maintained by the second device and / or registration status information of terminal devices associated with the second device maintained by the second device. This means that in the case where the first device is a large network element and the second device is a subnet element, the subnet element stores registration status information of terminal devices associated with the large network, or stores registration status information of terminal devices associated with the subnet, or both.

[0237] In one optional implementation, the first registration status information and the second registration status information may be the registration status of the same terminal device. It should be understood that the first registration status information is the registration status information of the terminal device in the first device, and the second registration status information is the registration status information of the terminal device in the second device.

[0238] In one optional implementation, the first registration status information and the second registration status information are registration status information associated with the same device and corresponding to the terminal device. For example, the first registration status information is the registration status information maintained by the subnet element and associated with it, and the second registration status information is the registration status information maintained by the main network element and associated with it. In this case, both the main network element and the subnet element maintain the registration status information associated with the subnet element, which means that the registration status information in the first device and the second device can actually be the same registration status information, but it is maintained by two different devices.

[0239] In one optional implementation, the first registration status information and the second registration status information are registration status information associated with different devices and corresponding to the terminal device. For example, the first registration status information is the registration status information maintained by a subnet element and associated with that subnet element, and the second registration status information is the registration status information maintained by a main network element and associated with that main network element. In this case, the main network element maintains the registration status information associated with that main network element, and the subnet element maintains the registration status information associated with that subnet element. This means that the registration status information in the first device and the second device can be different registration status information maintained by the two devices respectively.

[0240] In one optional implementation, the first registration status information can be either unregistered or registered, and the second registration status information can also be either unregistered or registered. Furthermore, the first and second registration status information may be identical or inconsistent. The method provided in this application primarily addresses the problem of inconsistencies between the registration statuses represented by the first and second registration status information.

[0241] Considering that some network elements in the subnet are deployed in a decentralized manner, resulting in some network elements in the subnet not having direct connection interfaces with the shared RAN, but instead forwarding data through the main network, in cases where the registration status represented by the first registration status information and the second registration status information is inconsistent, the data packets of the terminal device may not be able to be delivered to the subnet network. For example, if the registration status represented by the first registration status information and the second registration status information is inconsistent, such as the first registration status being unregistered and the second registration status information being registered, and the first device is a network element in the main network and the second device is a network element in the subnet, since the registration status corresponding to the terminal device in the main network is unregistered, the services of the terminal device and the subnet cannot be forwarded through the main network, thereby causing the service process to be interrupted.

[0242] In this embodiment, the first device acquires first information and sends second information to the second device, enabling the second device to recognize changes in the registration status information of the terminal device and maintaining consistency between the registration status information corresponding to the terminal device in the second device and the first device. This avoids data packet transmission failures and business process interruptions caused by inconsistent registration status.

[0243] In this embodiment of the application, the first network and the second network are in a management relationship, the first device is configured in the first network, and the second device is configured in the second network.

[0244] Optionally, if the first device is a large network element, such as AM, and the second device is a subnet element, such as MM, then the first network manages the second network. This management relationship can be understood as a hierarchical relationship, where the first network is the superior network of the second network, and the second network is the subordinate network of the first network. Alternatively, it can be understood as a subordinate relationship, where the first network is a subordinate network of the second network.

[0245] Optionally, if the first device is a subnet element, such as MM, and the second device is a large network element, such as AM, then the first network is managed by the second network.

[0246] In one optional implementation, the second information may be a notification, specifically used to notify the user of an update to the second registration status information. It should be understood that after receiving the second information, the second device updates the second registration status information, as illustrated in step S603.

[0247] Optionally, when the first device and the second device maintain the same registration status information, the second information can be notification information. For example, the first registration status information is the registration status information associated with the first device maintained by the first device, and the second registration status information is the registration status information associated with the first device maintained by the second device. As illustrated below, the first device is a large network element, the second device is a subnet element, the first registration status information is the registration status information associated with the subnet element maintained by the large network element, and the second registration status information is the registration status information associated with the subnet element maintained by the subnet element. Both the large network element and the subnet element maintain the registration status information associated with the subnet element. In other words, in the above example, both the large network element and the subnet element maintain the subnet RM state of the terminal device.

[0248] It should be noted that the devices associated with the registration status information are the same, which can be understood as the devices maintaining the same registration status information.

[0249] Optionally, the second information is specifically used to notify the user to update the second registration status information to the third registration status information. The second device can perform the following operations:

[0250] The second device updates the second registration status information to the third registration status information.

[0251] Furthermore, before the second device performs the above operations, the first device may perform the following operations: The first device updates the first registration status information to the third registration status information. This means that the first device updates the first registration status information before sending the notification information (second information). Also, both the first and second devices update the RM state of the terminal devices to the third registration status information, indicating that the two devices maintain consistency in their updated registration status information.

[0252] It should be understood that the third registration status information refers to one of the registration status (RM state). For example, the third registration status information can be a non-registered state or a registered state.

[0253] Optionally, if the registration status information maintained by the first device and the second device is inconsistent—for example, the first device's first registration status information is unregistered, while the second device's second registration status information is registered—then the first device / second device may not perform the update action. For instance, if the third registration status information is registered, and the first device is aware of the second device's second registration status information, then the first device may not send the second information.

[0254] Optionally, in cases where the first device and the second device maintain different registration status information, the second information may be notification information. For example, the first registration status information is the registration status information associated with the first device maintained by the first device, and the second registration status information is the registration status information associated with the second device maintained by the second device.

[0255] Considering that in some scenarios, the peer (second device) may determine whether to update the second registration status information based on the terminal device and its own business situation, in an optional implementation, the second information can be request information, specifically used to request the update of the second registration status information.

[0256] In an optional implementation, the second information is specifically used to request an update of the second registration status information to the third registration status information, where the third registration status information is a non-registered state. Step S603 may include the following operations:

[0257] If the first condition is met, the second device will update the second registration status information to the third registration status information. The first condition includes that there are no pending services related to the registration status information of the terminal device.

[0258] Optionally, the first condition also includes the absence of data packet transmission with the terminal device.

[0259] Optionally, the first condition also includes not communicating with the terminal device for more than a second period of time.

[0260] In one optional implementation, the second information is specifically used to request an update of the second registration status information to the third registration status information, and the second device can perform the following operations:

[0261] The second device sends a first response message to the first device. The first response message is used to indicate whether the registration status update is successful or the registration status update fails. If the registration status update is successful, it is used to indicate that the second registration status information has been updated to the third registration status information. If the registration status update fails, it is used to indicate that the second registration status information has not been updated.

[0262] Accordingly, the first device can perform the following operations:

[0263] The first device receives a first response message from the second device. The first response message is used to indicate whether the registration status update is successful or the registration status update fails. If the registration status update is successful, it is used to indicate that the second registration status information is updated to the third registration status information. If the registration status update fails, it is used to indicate that the second registration status information has not been updated.

[0264] It should be understood that, under the condition that the first condition is met, the second device sends a first response message to the first device. The first response message is used to indicate that the registration status update is successful. The successful registration status update is used to indicate that the second registration status information is updated to the third registration status information.

[0265] If the first condition is not met, the second device sends a first response message to the first device, the first response message indicating that the registration status update failed. In an optional implementation, the following operation is also included:

[0266] If the third condition is met, the second device sends a first response message to the first device. The first response message indicates that the registration status update has failed. The registration status update failure indicates that the second registration status information has not been updated. The third condition includes the existence of pending business related to the registration status information of the terminal device.

[0267] In one optional implementation, the second information is specifically used to request an update of the second registration status information to the third registration status information, where the third registration status information is a registration state. Step S603 may include the following operations:

[0268] If the second condition is met, the second device will update the second registration status information to the third registration status information. The second condition includes the existence of pending business related to the registration status information of the terminal device.

[0269] It should be understood that, under the condition that the second condition is met, the second device sends a first response message to the first device. The first response message is used to indicate that the registration status update is successful. The successful registration status update is used to indicate that the second registration status information is updated to the third registration status information.

[0270] If the second condition is not met, the second device sends a first response message to the first device, the first response message indicating that the registration status update failed. In an optional implementation, the following operation may also be included:

[0271] If the fourth condition is met, the second device sends a first response message to the first device. The first response message indicates that the registration status update has failed. The registration status update failure indicates that the second registration status information has not been updated. The fourth condition includes the absence of any pending business related to the registration status information of the terminal device.

[0272] Considering that the registration status information in the main network and subnets must be consistent, and in the case where the second information is a request information, there is a possibility that the second device will refuse to update. Therefore, after receiving the first response information from the second device, the first device determines whether to update the first registration status information.

[0273] In an optional implementation, the first response information is used to indicate that the registration status update was successful, and step S604 may include the following operations:

[0274] Based on the first response information, the first device updates the first registration status information to the third registration status information.

[0275] It should be understood that if the first response information is used to indicate that the registration status update has failed, then the first device will not execute step S604.

[0276] Optionally, if the second device determines not to update the second registration status information, then the first response information may not be sent.

[0277] In one alternative implementation, since the first information is sent by the terminal device, the first device, after determining the update result, feeds back the update result to the terminal device.

[0278] Specifically, the above method may also include the following operations:

[0279] The first device sends a second response message to the terminal device. The second response message is used to indicate the update results of the first and second devices.

[0280] For example, the second response information is used to indicate at least one of the following:

[0281] The first registration status information has been successfully updated;

[0282] First registration status information update failed;

[0283] The second registration status information has been successfully updated;

[0284] Second registration status information update failed;

[0285] The first and second registration status information have been successfully updated.

[0286] The first and second registration status information updates failed.

[0287] It should be understood that the second response information can indicate the update result of the first device or the update result of the second device.

[0288] The above mainly describes the communication method with the first device and the second device as the execution subjects. Considering that the first device can be a large network element or a subnet element, and the second device can be a subnet element or a large network element, and the first registration status information and the second registration status information may be RM states associated with the same device or RM states associated with different devices, there are many different situations. The following provides illustrative examples of each situation.

[0289] It should be noted in advance that in the process of describing various situations below, the same terms or actions may appear as in the above embodiments. Generally speaking, if the same terms or actions appear, they can be regarded as the same, and the corresponding possible implementations can also be referred to the possible implementations of the same terms or actions mentioned above. Special cases will be specifically explained.

[0290] Scenario 1: The first device is a large network element, and the second device is a subnet network element. Both the large network element and the subnet network element maintain the subnet RM state. The first registration status information is the registration status information associated with the subnet network element maintained by the large network element, and the second registration status information is the registration status information associated with the subnet network element maintained by the subnet network element. The following description uses an example where the first device is an Access Management (AM) function network element in the large network (AM1 in Figure 5), and the second device is a Mobility Management (MM) function network element in the subnet network (MM2 in Figure 5). Please refer to Figure 7, which is a flowchart illustrating another communication method provided in this application embodiment. Specifically, it may include the following operations:

[0291] Step S701: The terminal device sends first information to the access management function network element in the large network. Correspondingly, the access management function network element in the large network receives the first information from the terminal device.

[0292] Step S702: The access management function network element in the main network sends the second information to the mobility management function network element in the subnet network. Correspondingly, the mobility management function network element in the subnet network receives the second information sent from the access management function network element in the main network.

[0293] The second piece of information is used to request an update of the second registration status information to the third registration status information.

[0294] Step S703: The mobility management function network element in the subnet network determines whether to update the registration status information.

[0295] The above determination of whether to update the registration status information can be based on the first condition or the second condition. For details, please refer to the relevant explanations and possible implementations of the first and second conditions above. This will not be repeated hereafter.

[0296] Step S704: If the mobility management function element in the subnet network determines to update the registration status information, it sends a first response message to the access management function element in the main network. Correspondingly, the access management function element in the main network receives the first response message from the mobility management function element in the subnet network.

[0297] The first response message indicates that the registration status update was successful.

[0298] Step S705: The mobility management function network element in the subnet network updates the second registration status information.

[0299] Step S706: The access management function network element in the large network updates the first registration status information.

[0300] Step S707: The access management function network element in the large network sends a second response message to the terminal device. Correspondingly, the terminal device receives the second response message from the access management function network element in the large network.

[0301] The second response information is used to indicate that the first registration status information update was successful and the second registration status information update was successful.

[0302] Scenario 2: The first device is a subnet network element, and the second device is a main network element. Both the main network element and the subnet network element maintain the subnet RM state. The first registration status information is the registration status information associated with the subnet network element maintained by the subnet network element, and the second registration status information is the registration status information associated with the subnet network element maintained by the main network element. The following description uses an example where the first device is a Mobility Management (MM) network element in the subnet network (MM2 in Figure 5), and the second device is an Access Management (AM) network element in the main network network (AM1 in Figure 5). Please refer to Figure 8, which is a flowchart illustrating another communication method provided in this embodiment. Specifically, it may include the following operations:

[0303] Step S801: The terminal device sends first information to the mobility management function network element in the subnet network. Correspondingly, the mobility management function network element in the subnet network receives the first information from the terminal device.

[0304] Step S802: The mobility management function (MMS) element in the subnet network sends the second information to the access management function (AMS) element in the main network network. Correspondingly, the AMS element in the main network network receives the second information sent from the mobility management function (MMS) element in the subnet network.

[0305] The second piece of information is used to request an update of the second registration status information to the third registration status information.

[0306] Step S803: The access management function network element in the large network determines whether to update the registration status information.

[0307] Step S804: If the access management function network element in the main network determines to update the registration status information, it sends a first response message to the mobility management function network element in the subnet network. Correspondingly, the mobility management function network element in the subnet network receives the first response message from the access management function network element in the main network.

[0308] The first response message indicates that the registration status update was successful.

[0309] Optionally, if the second registration status information fails to update or is not updated, the first response information will not be sent.

[0310] Step S805: The access management function network element in the large network updates the second registration status information.

[0311] Step S806: The mobility management function network element in the subnet network updates the first registration status information.

[0312] Step S807: The mobility management function (MMU) network element in the subnet network sends a second response message to the terminal device. Correspondingly, the terminal device receives the second response message from the mobility management function (MMU) network element in the subnet network.

[0313] The second response information is used to indicate that the first registration status information update was successful and the second registration status information update was successful.

[0314] Scenario 3: The first device is a large network element, and the second device is a subnet element. Both the large network element and the subnet element maintain the subnet RM state. The first registration status information is the registration status information associated with the subnet element maintained by the large network element, and the second registration status information is the registration status information associated with the subnet element maintained by the subnet element. The following description uses an example where the first device is an Access Management (AM) function network element in the large network (AM1 in Figure 5), and the second device is a Mobility Management (MM) function network element in the subnet network (MM2 in Figure 5). Please refer to Figure 9, which is a flowchart illustrating another communication method provided in this embodiment. Specifically, it may include the following operations:

[0315] Step S901: The terminal device sends first information to the access management function network element in the large network. Correspondingly, the access management function network element in the large network receives the first information from the terminal device.

[0316] Step S902: The access management function network element in the large network updates the first registration status information.

[0317] Step S903: The access management function network element in the main network sends the second information to the mobility management function network element in the subnet network. Correspondingly, the mobility management function network element in the subnet network receives the second information sent from the access management function network element in the main network.

[0318] The second information is used to notify the user to update the second registration status information to the third registration status information.

[0319] Step S904: The mobility management function network element in the subnet network updates the second registration status information.

[0320] Step S905: The mobility management function (MMS) element in the subnet network sends a first response message to the access management function (AMS) element in the main network. Correspondingly, the AMS element in the main network receives the first response message from the mobility management function (MMS) element in the subnet network.

[0321] The first response message indicates that the registration status update was successful.

[0322] Optionally, the first response information is a notification, specifically used to notify the terminal device of the update status of the subnet RM.

[0323] Step S906: The access management function network element in the large network sends a second response message to the terminal device. Correspondingly, the terminal device receives the second response message from the access management function network element in the large network.

[0324] The second response information is used to indicate that the first registration status information update was successful and the second registration status information update was successful.

[0325] Optionally, the above method further includes step S907 (not shown in the figure), step S907: the terminal device updates the registration status information associated with the subnet stored in its own storage.

[0326] Scenario 4: The first device is a subnet network element, and the second device is a large network element. Both the large network element and the subnet network element maintain the subnet RM state. The first registration status information is the registration status information associated with the subnet network element maintained by the subnet network element, and the second registration status information is the registration status information associated with the subnet network element maintained by the large network element. The following description uses an example where the first device is a Mobility Management (MM) network element in the subnet network (MM2 in Figure 5), and the second device is an Access Management (AM) network element in the large network network (AM1 in Figure 5). Please refer to Figure 10, which is a flowchart illustrating another communication method provided in this application embodiment. Specifically, it may include the following operations:

[0327] Step S1001: The terminal device sends first information to the mobility management function network element in the subnet network. Correspondingly, the mobility management function network element in the subnet network receives the first information from the terminal device.

[0328] Step S1002: The mobility management function network element in the subnet network updates the first registration status information.

[0329] Step S1003: The mobility management function (MMS) element in the subnet network sends the second information to the access management function (AMS) element in the main network network. Correspondingly, the AMS element in the main network network receives the second information sent from the mobility management function (MMS) element in the subnet network.

[0330] The second information is used to notify the user to update the second registration status information to the third registration status information.

[0331] Step S1004: The access management function network element in the large network updates the second registration status information.

[0332] Step S1005: If the access management function network element in the main network determines to update the registration status information, it sends a first response message to the mobility management function network element in the subnet network. Correspondingly, the mobility management function network element in the subnet network receives the first response message from the access management function network element in the main network.

[0333] The first response message indicates that the registration status update was successful.

[0334] Step S1006: The mobility management function network element in the subnet network sends a second response information to the terminal device. Correspondingly, the terminal device receives the second response information from the mobility management function network element in the subnet network.

[0335] The second response information is used to indicate that the first registration status information update was successful and the second registration status information update was successful.

[0336] Optionally, the first response information is a notification, specifically used to notify the terminal device of the update status of the subnet RM.

[0337] Case 5: The first device is a large network element, and the second device is a subnet element. The large network element and the subnet element maintain the large network RM state and the subnet RM state, respectively. The first registration status information is the registration status information associated with the large network element maintained by the large network element, and the second registration status information is the registration status information associated with the subnet element maintained by the subnet element. The following description uses an example where the first device is an Access Management (AM) function network element in the large network (AM1 in Figure 5), and the second device is a Mobility Management (MM) function network element in the subnet network (MM2 in Figure 5). Please refer to Figure 11, which is a flowchart illustrating another communication method provided in this application embodiment. Specifically, it may include the following operations:

[0338] Step S1101: The terminal device sends first information to the access management function network element in the large network. Correspondingly, the access management function network element in the large network receives the first information from the terminal device.

[0339] Optionally, the terminal device or the main network triggers an update of the main network's RM state (e.g., reg->dereg, or dereg->reg). In other words, the initial information can be sent by the terminal device or obtained by the access management function network element in the main network.

[0340] The interaction messages between the terminal device and the subnet can be directly forwarded to the subnet by the access network device (uplink messages, downlink messages are the opposite), or they can be forwarded to the main network by the access network device and then forwarded to the subnet by the main network (uplink messages, downlink messages are the opposite).

[0341] In one possible implementation, the first information can also be sent by a subnet element, such as a Mobility Management (MM) element in the subnet network (MM2 in Figure 5).

[0342] This means that subnet elements can also trigger RM state updates in the main network element of the terminal device.

[0343] Step S1102: The access management function network element in the main network sends the second information to the mobility management function network element in the subnet network. Correspondingly, the mobility management function network element in the subnet network receives the second information sent from the access management function network element in the main network.

[0344] The second piece of information is used to request an update of the second registration status information to the third registration status information.

[0345] Step S1103: The mobility management function network element in the subnet network determines whether to update the registration status information.

[0346] Step S1104: If the mobility management function element in the subnet network determines to update the registration status information, it sends a first response message to the access management function element in the main network. Correspondingly, the access management function element in the main network receives the first response message from the mobility management function element in the subnet network.

[0347] The first response message indicates that the registration status update was successful.

[0348] Step S1105: The mobility management function network element in the subnet network updates the second registration status information.

[0349] Step S1106: The access management function network element in the large network updates the first registration status information.

[0350] Step S1107: The access management function network element in the large network sends a second response message to the terminal device. Correspondingly, the terminal device receives the second response message from the access management function network element in the large network.

[0351] Optionally, the second response information is used to indicate that the first registration status information was updated successfully and the second registration status information was updated successfully.

[0352] Optionally, if step S1101 is a terminal device RM state update in the main network element triggered by the subnet element, then the second response information may specifically be sent by the access management function network element in the main network to the mobility management function network element in the subnet network.

[0353] Case 6: The first device is a subnet network element, and the second device is a main network element. The main network element and the subnet network element maintain the main network RM state and the subnet RM state, respectively. The first registration status information is the registration status information associated with the subnet network element maintained by the subnet network element, and the second registration status information is the registration status information associated with the main network element maintained by the main network element. The following description uses an example where the first device is a Mobility Management (MM) network element in the subnet network (MM2 in Figure 5), and the second device is an Access Management (AM) network element in the main network network (AM1 in Figure 5). Please refer to Figure 12, which is a flowchart illustrating another communication method provided in this application embodiment. Specifically, it may include the following operations:

[0354] Step S1201: The terminal device sends first information to the mobility management function network element in the subnet network. Correspondingly, the mobility management function network element in the subnet network receives the first information from the terminal device.

[0355] Step S1202: The mobility management function (MMS) element in the subnet network sends the second information to the access management function (AMS) element in the main network network. Correspondingly, the AMS element in the main network network receives the second information sent from the mobility management function (MMS) element in the subnet network.

[0356] The second piece of information is used to request an update of the second registration status information to the third registration status information.

[0357] Step S1203: The access management function network element in the large network determines whether to update the registration status information.

[0358] Step S1204: If the access management function network element in the main network determines to update the registration status information, it sends a first response message to the mobility management function network element in the subnet network. Correspondingly, the mobility management function network element in the subnet network receives the first response message from the access management function network element in the main network.

[0359] The first response message indicates that the registration status update was successful.

[0360] Optionally, if the second registration status information fails to update or is not updated, the first response information will not be sent.

[0361] Step S1205: The access management function network element in the large network updates the second registration status information.

[0362] Step S1206: The mobility management function network element in the subnet network updates the first registration status information.

[0363] Step S1207: The mobility management function network element in the subnet network sends a second response information to the terminal device. Correspondingly, the terminal device receives the second response information from the mobility management function network element in the subnet network.

[0364] The second response information is used to indicate that the first registration status information update was successful and the second registration status information update was successful.

[0365] Case 7: The first device is a large network element, and the second device is a subnet element. The large network element and the subnet element maintain the large network RM state and the subnet RM state, respectively. The first registration status information is the registration status information associated with the large network element maintained by the large network element, and the second registration status information is the registration status information associated with the subnet element maintained by the subnet element and / or the registration status information associated with the large network element maintained by the subnet element. The following description uses an example where the first device is an Access Management (AM) function network element in the large network (AM1 in Figure 5), and the second device is a Mobility Management (MM) function network element in the subnet network (MM2 in Figure 5). Please refer to Figure 13, which is a flowchart illustrating another communication method provided in this application embodiment. Specifically, it may include the following operations:

[0366] Step S1301: The terminal device sends first information to the access management function network element in the large network. Correspondingly, the access management function network element in the large network receives the first information from the terminal device.

[0367] Step S1302: The access management function network element in the large network updates the first registration status information.

[0368] Step S1303: The access management function network element in the main network sends the second information to the mobility management function network element in the subnet network. Correspondingly, the mobility management function network element in the subnet network receives the second information sent from the access management function network element in the main network.

[0369] The second information is used to notify the user to update the second registration status information to the third registration status information.

[0370] Step S1304: The mobility management function network element in the subnet network updates the second registration status information.

[0371] Step S1305: The mobility management function (MMS) element in the subnet network sends a first response message to the access management function (AMS) element in the main network. Correspondingly, the AMS element in the main network receives the first response message from the mobility management function (MMS) element in the subnet network.

[0372] The first response message indicates that the registration status update was successful.

[0373] Optionally, the first response information is a notification, specifically used to notify the terminal device of the update status of the subnet RM.

[0374] Step S1306: The access management function network element in the large network sends a second response message to the terminal device. Correspondingly, the terminal device receives the second response message from the access management function network element in the large network.

[0375] The second response information is used to indicate that the first registration status information update was successful and the second registration status information update was successful.

[0376] Optionally, the above method further includes step S1307 (not shown in the figure), step S1307: the terminal device updates the registration status information associated with the subnet stored in its own storage.

[0377] Optionally, in cases one through seven above, the entity actively activating the first device to detect / update registration status information can also be an access network device, where the first information is information sent by the access network device. For example, the access network device forwards the first information sent by the terminal device. The access network device can perform the following operations:

[0378] The access network device receives first information sent by the terminal device, the first information being used to indicate updating the terminal device's first registration status information; the access network device sends the first information to the first device.

[0379] This application embodiment, by providing the aforementioned communication method, not only achieves real-time synchronization and updating of terminal device registration status information in the main network and subnet networks, effectively solving the problem of business process interruption caused by inconsistent registration status, but also ensures the accuracy and consistency of terminal device registration status in different network environments through a flexible registration status update mechanism. Furthermore, this embodiment enhances the reliability and transparency of inter-network communication by introducing a response and feedback mechanism, enabling the network to respond more quickly to changes in terminal device status. Ultimately, this technical solution improves the overall network operating efficiency and user experience by optimizing network management processes, laying a solid foundation for building a more efficient, stable, and intelligent communication network system.

[0380] In an optional implementation, the update of the main network RM state can also be achieved by the main network obtaining the subnet RM state and updating it itself. The executing entity of this method is a first device, which can be a network element in the main network. For example, the first device can be an Access Management (AM) function network element in the main network, or a component within the Access Management (AM) function network element, such as a chip. This application does not limit this. The method will be described below using the example of an Access Management (AM) function network element in the main network as the executing entity.

[0381] Please refer to Figure 14 for details. Figure 14 is a flowchart illustrating another communication method provided in an embodiment of this application. Specifically, it may include the following operations:

[0382] Step S1401: Access management function network element obtains third and fourth information.

[0383] The third information is used to indicate the first registration status information of the terminal device being updated and maintained. The first registration status information includes the registration status information of the terminal device associated with the first device maintained by the first device and / or the registration status information of the terminal device associated with the second device maintained by the first device.

[0384] The fourth information includes the second registration status information of the terminal device; the second registration status information includes the registration status information of the terminal device associated with the first device maintained by the second device and / or the registration status information of the terminal device associated with the second device maintained by the second device.

[0385] It should be understood that the access management function network element can determine the registration status of other devices based on the fourth information, and then determine whether it should update its own registration status.

[0386] In one alternative implementation, the fourth information can be determined / obtained in various ways. For example, the fourth information can be historical information of the interaction between the main network and the subnet, new information obtained by the main network through interaction / query with the subnet after receiving the third information, or registration status information reported by other devices. Eight exemplary methods for determining / obtaining the fourth information are described below.

[0387] Method 1: The subnet actively notifies the main network.

[0388] In one alternative implementation, obtaining the fourth information includes the following operations:

[0389] The first device receives fourth information from the second device, the fourth information indicating second registration status information. Accordingly, the above method should also include the second device sending the fourth information to the first device.

[0390] If the second device is a mobility management function network element in the subnet network, then the above operation can specifically be that the access management function network element in the main network receives the fourth information from the mobility management function network element in the subnet network, and the fourth information is used to indicate the second registration status information.

[0391] Optionally, the fourth information includes second registration status information from different second devices.

[0392] Method 2: Query from the main network to the subnet.

[0393] In one alternative implementation, obtaining the fourth information includes the following operations:

[0394] The first device sends a fifth message to the second device, which is used to request the second registration status information; correspondingly, the second device receives the fifth message from the first device.

[0395] The first device receives the fourth message from the second device. Correspondingly, the second device sends the fourth message back to the first device.

[0396] If the second device is a mobility management function (MMS) element in the subnet network, then the above operation can specifically involve the access management function (AMS) element in the main network sending fifth information to the mobility management function (MMS) element in the subnet network, and the AMS element in the main network receiving fourth information from the mobility management function (MMS) element in the subnet network.

[0397] Method 3: Before obtaining the fourth information, the large network sends an RM release request to the subnet, and the RM is successfully released.

[0398] In one alternative implementation, the following operations are further included before obtaining the fourth information:

[0399] The first device sends a sixth message to the second device, which requests that the registration status information of the terminal device be updated to the second registration status information; correspondingly, the second device receives the sixth message from the first device.

[0400] The first device receives a third response message from the second device. This third response message indicates that the registration status information has been successfully updated, and the successful update of the registration status information indicates that the second registration status information has been updated to the fourth registration status information. Accordingly, the second device sends the third response message back to the first device.

[0401] It should be understood that the first device may determine the fourth information based on the third response information, or the third response information may be the fourth information.

[0402] Alternatively, the above operation can also involve the access management function network element in the large network sending the sixth information to the mobility management function network element in the subnet network, and correspondingly, the mobility management function network element in the subnet network sending the sixth information and receiving the sixth information from the access management function network element in the large network network.

[0403] It should be understood that the first device in this embodiment can be equivalently replaced by the access management function network element in the main network, and the first device can be equivalently replaced by the mobility management function network element in the subnet network. In the following description, the first device will replace the access management function network element in the main network, and the second device will replace the mobility management function network element in the subnet network. This will not be repeated hereafter.

[0404] Method 4: Before obtaining the fourth piece of information, the subnet sends an RM release request to the main network and successfully releases it.

[0405] In one alternative implementation, the following operations are further included before obtaining the fourth information:

[0406] The first device receives the seventh message sent by the second device, which is used to request an update of the first registration status information to the fourth registration status information; correspondingly, the second device sends the seventh message to the first device.

[0407] The first device sends a fourth response message to the second device. This fourth response message indicates that the first registration status information has been successfully updated, and the successful update of the first registration status information indicates that the first registration status information has been updated to the fourth registration status information. Correspondingly, the second device receives the fourth response message from the first device.

[0408] It should be understood that before obtaining the fourth information, the first device and the second device had interacted regarding the first registration status information, such as the aforementioned seventh information being used to request an update of the first registration status information to the fourth registration status information, and the first device updating the first registration status information to the fourth registration status information. Based on this, the first device determines the fourth information.

[0409] Method 5: Before obtaining the fourth information, the subnet sends an RM release notification to the main network.

[0410] In one alternative implementation, the following operations are further included before obtaining the fourth information:

[0411] The first device receives the eighth message sent by the second device. The eighth message is used to notify the user to update the first registration status information to the fourth registration status information. Correspondingly, the second device sends the eighth message back to the first device.

[0412] It should be understood that the first device can determine the fourth information based on the eighth information.

[0413] Method 6: RM state change messages between the large network terminal device and the subnet (non-transparent forwarding).

[0414] In one alternative implementation, the following operations are further included before obtaining the fourth information:

[0415] The first device parses the ninth information transmitted between the terminal device and the second device. The ninth information is used to indicate the second registration status information.

[0416] Method 7: The terminal device reports the second registration status information.

[0417] In one alternative implementation, the following operations are also included:

[0418] The first device receives the tenth information sent by the terminal device, which is used to indicate the second registration status information.

[0419] Optionally, the tenth message sent by the terminal device may include some of the second registration status information of the second device.

[0420] The first device can determine the fourth information based on the aforementioned tenth information.

[0421] Method 8: The access network device reports the second registration status information.

[0422] In one alternative implementation, the following operations are also included:

[0423] The first device receives the eleventh message sent by the third device. The eleventh message is used to indicate the registration status information of the terminal device maintained by the second device.

[0424] Optionally, the third device is an access network device, and the eleventh message sent by the third device includes registration status information of one or more terminal devices maintained by the second device.

[0425] In the above embodiments, the first device can obtain registration status information not only through the second device, but also through other channels such as terminal devices and access network devices, thus broadening the information source channels.

[0426] Optionally, the first device can obtain registration status information through multiple channels and make a comprehensive judgment, which can improve the accuracy and reliability of the information.

[0427] Step S1402: The access management function network element updates the first registration status information based on the fourth information.

[0428] Optionally, the third information is specifically used to indicate updating the first registration status information to the fourth registration status information, and step S1402 may include the following operations:

[0429] If the fifth condition is met, the first device updates the first registration status information to the fourth registration status information; wherein the fifth condition includes at least one of the following:

[0430] The fourth information includes the second registration status information, which is the fourth registration status information;

[0431] Data packets were not transmitted to the terminal device within the first available time.

[0432] For example, the fourth registration status information is used to indicate whether the registration status of the terminal device is unregistered or registered. The fourth information including the second registration status information can be understood as either the second registration status information included in the fourth information being unregistered or the second registration status information included in the fourth information being registered.

[0433] Optionally, the fourth information includes second registration status information from different second devices. If the second registration status information of all second devices is consistent and all of them are the fourth registration status information, the first device updates the first registration status information.

[0434] Optionally, the fourth piece of information is determined by the first device itself. If the first device does not engage in any business communication with the terminal device related to the registration status information within a certain period of time (the first time) and does not transmit any data packets, the first device updates the first registration status information.

[0435] In this embodiment, the first device can flexibly choose whether to update the registration status information based on the specific content of the fourth information and the communication status between the first device and the terminal device, thus optimizing the update strategy. Furthermore, status updates are only performed under specific conditions, reducing unnecessary system overhead and the number of updates.

[0436] The methods of the embodiments of this application have been described above. Below, some apparatuses for implementing the aforementioned methods are described. It should be understood that the division of units in the apparatuses provided in the embodiments of this application is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units in the apparatus can be implemented in the form of a processor calling software; for example, the apparatus includes a processor connected to a memory, the memory storing instructions, and the processor calling the instructions stored in the memory to implement any of the above methods or to implement the functions of each unit of the apparatus. The processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is either internal to the apparatus or external to the apparatus. Alternatively, the units in the device can be implemented as hardware circuits. The functionality of some or all units can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the above units is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through a configuration file, thereby achieving the functionality of some or all of the above units. All units of the above device can be implemented entirely through processor-invoked software, entirely through hardware circuits, or partially through processor-invoked software with the remaining parts implemented through hardware circuits.

[0437] In this application embodiment, a processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a type of microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. These logical relationships of hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0438] As can be seen, each unit in the above device can be one or more processors (or processing circuits) configured to implement the above methods, such as: CPU, GPU, NPU, TPU, DPU, microprocessor, DSP, ASIC, FPGA, or a combination of at least two of these processor forms.

[0439] Furthermore, the units in the above devices can be integrated in whole or in part, or they can be implemented independently. In one implementation, these units are integrated together as a system-on-a-chip (SOC). The SOC may include at least one processor for implementing any of the above methods or implementing the functions of the units in the device. The at least one processor may be of different types, such as CPU and FPGA, CPU and artificial intelligence processor, CPU and GPU, etc.

[0440] Several possible devices are listed below.

[0441] Please refer to Figure 15, which is a schematic diagram of a communication device provided in an embodiment of this application. Optionally, the communication device 150 can be an independent device, such as a personal computer. Alternatively, the communication device 150 can also be a component in an independent device (such as a node), such as a chip or integrated circuit. The communication device 150 is used to implement the methods executed by the communication device in the aforementioned communication methods, such as the methods executed by the communication device in any one or more embodiments shown in Figure 4.

[0442] As shown in Figure 15, the communication device 150 includes a transceiver module 1501 and a processing module 1502. The transceiver module 1501 performs one or more operations such as acquiring, receiving, transmitting, establishing a connection, and responding, and further includes other operations for implementing the communication method. The processing module 1502 performs one or more operations such as processing, calculating, determining, and generating, and further includes other operations for implementing the communication method. Optionally, the transceiver module 1501 may be referred to as a first transceiver module when executing a method on the first device side, and may be referred to as a second transceiver module when executing a method on the second device side. Optionally, the processing module 1502 may be referred to as a first processing module when executing a method on the first device side, and may be referred to as a second processing module when executing a method on the second device side.

[0443] For related descriptions, please refer to the descriptions of any of the embodiments shown in Figures 6 to 14, which will not be described in detail here.

[0444] Please refer to Figure 16, which is a schematic diagram of another communication device provided in an embodiment of this application. The communication device 160 can be a standalone device, such as a node, or a component included in a standalone device, such as a chip, software module, or integrated circuit. The communication device 160 may include at least one processor 1601 and a communication interface 1602. Optionally, it may also include at least one memory 1603. Further optionally, it may also include a connection line 1604, wherein the processor 1601, the communication interface 1602, and / or the memory 1603 are connected via the connection line 1604, and / or communicate with each other via the connection line 1604 to transmit control signals and / or data signals.

[0445] in:

[0446] Processor 1601 is a module that performs arithmetic and / or logical operations, and may specifically include one or more of the following modules: filter, modem, power amplifier, low noise amplifier (LNA), baseband processor, radio frequency processor, radio frequency circuit, central processing unit (CPU), application processor (AP), microcontroller unit (MCU), electronic control unit (ECU), graphics processing unit (GPU), microprocessor unit (MPU), application specific integrated circuit (ASIC), image signal processor (ISP), digital signal processor (DSP), field programmable gate array (FPGA), complex programmable logic device (CPLD), or coprocessor, etc.

[0447] The communication interface 1602 can be used to provide information input or output to the at least one processor, or to receive signals sent from the outside and / or send signals to the outside.

[0448] For example, communication interface 1602 may include interface circuitry.

[0449] For example, the communication interface 1602 may include a wired link interface such as an Ethernet cable, or a wireless link interface (Wi-Fi, Bluetooth, general wireless transmission, vehicle short-range communication technology and other short-range wireless communication technologies, etc.).

[0450] Optionally, the communication interface 1602 may also include a radio frequency transmitter, an antenna, etc. When the communication interface 1602 includes an antenna, the number of antennas can be one or more.

[0451] As one possible design, if the communication device 160 is a standalone device, the communication interface 1602 may include a receiver and a transmitter. The receiver and transmitter may be the same component or different components. When the receiver and transmitter are the same component, this component may be referred to as a transceiver.

[0452] As another possible design, if the communication device 160 is a chip or circuit, the communication interface 1602 may include an input interface and an output interface, which may be the same interface or different interfaces.

[0453] Alternatively, the functionality of the communication interface 1602 can be implemented via a transceiver circuit or a dedicated transceiver chip.

[0454] The memory 1603 provides storage space, in which data such as the operating system and computer programs can be stored. The memory 1603 can be one or a combination of several of the following: random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM).

[0455] The functions and operations of each module or unit in the communication device 160 listed above are merely illustrative examples.

[0456] Each functional unit in the communication device 160 can be used to implement the methods implemented by the communication device in the aforementioned communication methods, such as the methods implemented by the communication device in the communication methods shown in Figures 6 to 14.

[0457] Optionally, the processor 1601 may be a processor specifically designed to perform the aforementioned methods (for ease of distinction, referred to as a dedicated processor), or a processor that performs the aforementioned methods by calling a computer program (for ease of distinction, referred to as a dedicated processor). Optionally, at least one processor may include both dedicated processors and general-purpose processors.

[0458] Optionally, if the communication device 160 includes at least one memory 1603, and the processor 1601 implements the aforementioned communication method by calling a computer program, the computer program can be stored in the memory 1603.

[0459] This application also provides a chip, which includes logic circuitry and a communication interface. The communication interface is used to receive or transmit signals; the logic circuitry is used to receive or transmit signals through the communication interface. The chip is used to implement the aforementioned communication method, such as the communication method shown in Figures 6 to 14.

[0460] This application also provides a computer-readable storage medium storing instructions that, when executed on at least one processor (or communication device), implement the aforementioned communication method, such as the communication method shown in Figures 6 to 14.

[0461] This application also provides a computer program product, which includes computer instructions for implementing the aforementioned communication method, such as the communication method shown in Figures 6 to 14.

[0462] In the description of this application, the terms “center,” “upper,” “lower,” “vertical,” “horizontal,” “inner,” “outer,” “left,” “side,” etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are used only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on this application.

[0463] In the embodiments of this application, the term "end" appearing in terms such as "one end", "the other end", "left end", "right end", "upper end", "lower end", and "connecting end" is not limited to end head, end point, or end face, but also includes a portion extending axially and / or radially from the end head, end point, or end face on the device or element to which the end head, end point, or end face belongs.

[0464] In this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0465] In this application, "at least one" in the embodiments refers to one or more items, and "more than one" refers to two or more items. "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 represent: a, b, c, (a and b), (a and c), (b and c), or (a and b and c), where a, b, and c can be single or multiple. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship.

[0466] Furthermore, unless otherwise stated, the use of ordinal numbers such as "first" and "second" in the embodiments of this application is for distinguishing multiple objects and is not for limiting the order, timing, priority, or importance of multiple objects. Similarly, terms like "first angle measurement data" and "second angle measurement data" are merely for the convenience of describing new parameters in different implementations and do not indicate differences in their execution operations, importance, data content, etc.

[0467] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

Claims

A communication method characterized by comprising: The method is applied to a first device, and the method includes: Obtain first information, which is used to indicate updating the first registration status information of the terminal device; the first registration status information includes the registration status information of the terminal device associated with the first device maintained by the first device and / or the registration status information of the terminal device associated with the second device maintained by the first device. Send a second message to the second device. The second message is used to instruct the updating of the second registration status information of the terminal device. The second registration status information includes the registration status information of the terminal devices associated with the first device maintained by the second device and / or the registration status information of the terminal devices associated with the second device maintained by the second device. The first network and the second network have a management relationship. The first device is configured in the first network and the second device is configured in the second network. The method of claim 1, wherein The second information is specifically used to notify the user to update the second registration status information to the third registration status information. The method further includes: Update the first registration status information to the third registration status information. The method of claim 1, wherein The second information is specifically used to request an update of the second registration status information to the third registration status information, and the method further includes: The system receives a first response message from the second device. The first response message indicates whether the registration status update is successful or failed. The successful registration status update indicates that the second registration status information has been updated to the third registration status information. The failed registration status update indicates that the second registration status information has not been updated. The method according to claim 3, characterized in that The first response information is used to indicate that the registration status update was successful, and the method further includes: Based on the first response information, the first registration status information is updated to the third registration status information. The method according to any one of claims 1 to 4, characterized in that The method further includes: Send a second response message to the terminal device, the second response message indicating at least one of the following: The first registration status information was updated successfully; The first registration status information update failed; The second registration status information has been successfully updated; The second registration status information update failed; The first registration status information and the second registration status information have been successfully updated; The first registration status information and the second registration status information failed to be updated. A communication method characterized by comprising: The method is applied to a second device, and the method includes: The system receives second information from a first device, which is used to instruct the updating of the second registration status information of the terminal device. The second registration status information includes the registration status information of the terminal device associated with the first device maintained by the second device and / or the registration status information of the terminal device associated with the second device maintained by the second device. The first network and the second network have a management relationship, with the first device configured on the first network and the second device configured on the second network. Update the second registration status information. The method according to claim 6, characterized in that The second information is specifically used to request an update of the second registration status information to the third registration status information, where the third registration status information is a non-registered state. Updating the second registration status information includes: If the first condition is met, the second registration status information is updated to the third registration status information. The first condition includes that there are no pending services related to the registration status information of the terminal device. The method according to claim 6, characterized in that The second information is specifically used to request an update of the second registration status information to the third registration status information, where the third registration status information is a registration state. Updating the second registration status information includes: If the second condition is met, the second registration status information is updated to the third registration status information. The second condition includes the existence of pending business related to the registration status information of the terminal device. The method according to claim 7 or 8, characterized in that The method further includes: Send a first response message to the first device. The first response message is used to indicate that the registration status update is successful. The successful registration status update is used to indicate that the second registration status information is updated to the third registration status information. The method of claim 7, wherein The method further includes: If the third condition is met, a first response message is sent to the first device. The first response message indicates that the registration status update has failed. The registration status update failure indicates that the second registration status information has not been updated. The third condition includes the existence of pending services related to the registration status information of the terminal device. The method of claim 8, wherein The method further includes: If the fourth condition is met, a first response message is sent to the first device. The first response message is used to indicate that the registration status update failed. The registration status update failure is used to indicate that the second registration status information has not been updated. The fourth condition includes the absence of any pending business related to the registration status information of the terminal device. The method according to claim 6, characterized in that The second information is specifically used to notify the user to update the second registration status information to the third registration status information. The updating of the second registration status information includes: Update the second registration status information to the third registration status information. A communication method characterized by comprising: The method is applied to a terminal device, and the method includes: Send first information to the first device, the first information being used to instruct the updating of the first registration status information of the terminal device; the first registration status information includes the registration status information of the terminal device associated with the first device maintained by the first device and / or the registration status information of the terminal device associated with the second device maintained by the first device; The system receives a second response message from a first device, which indicates whether the registration status update of the terminal device was successful or failed. The first network and the second network are in a management relationship, with the first device configured on the first network and the second device configured on the second network. A communication method characterized by comprising: The method is applied to a first device, and the method includes: Obtain third and fourth information, wherein the third information is used to indicate the first registration status information of the terminal device being updated and maintained, the first registration status information including the registration status information of the terminal device associated with the first device maintained by the first device and / or the registration status information of the terminal device associated with the second device maintained by the first device; the fourth information includes the second registration status information of the terminal device; the second registration status information includes the registration status information of the terminal device associated with the first device maintained by the second device and / or the registration status information of the terminal device associated with the second device maintained by the second device. Based on the fourth information, update the first registration status information. The method of claim 14, wherein The third information is specifically used to indicate updating the first registration status information to the fourth registration status information. Based on the fourth information, updating the first registration status information includes: If the fifth condition is met, the first registration status information is updated to the fourth registration status information; wherein the fifth condition includes at least one of the following: The fourth information includes the second registration status information, which is the fourth registration status information; The data packet was not transmitted to the terminal device within the first time limit. The method according to claim 14 or 15, characterized in that The acquisition of the fourth information includes: The system receives a fourth message sent by the second device, the fourth message being used to indicate the second registration status information. The method according to claim 14 or 15, characterized in that The acquisition of the fourth information includes: Send a fifth message to the second device, the fifth message being used to request the acquisition of the second registration status information; Receive fourth information from the second device. The method of claim 15, wherein Before obtaining the fourth information, the method further includes: Send a sixth message to the second device, the sixth message being used to request that the registration status information of the terminal device be updated to the second registration status information; The system receives a third response message from the second device, which indicates that the registration status information has been successfully updated. The successful update of the registration status information indicates that the second registration status information has been updated to the fourth registration status information. The method of claim 15, wherein Before obtaining the fourth information, the method further includes: The device receives a seventh message sent by the second device, the seventh message being used to request an update of the first registration status information to the fourth registration status information; A fourth response message is sent to the second device. The fourth response message is used to indicate that the first registration status information has been successfully updated. The successful update of the first registration status information is used to indicate that the first registration status information has been updated to the fourth registration status information. The method of claim 15, wherein Before obtaining the fourth information, the method further includes: The device receives an eighth message sent by the second device, the eighth message being used to notify the user to update the first registration status information to the fourth registration status information. The method of claim 14, wherein Before obtaining the fourth information, the method further includes: The ninth information transmitted between the terminal device and the second device is parsed, and the ninth information is used to indicate the second registration status information. The method of claim 14, wherein The method further includes: The terminal device sends a tenth message, which is used to indicate the second registration status information. The method of claim 14, wherein The method further includes: The device receives an eleventh message sent by a third device, the eleventh message being used to indicate the registration status information of the terminal device maintained by the second device. A communication device, characterized by The communication device includes a module or unit for performing the method of any one of claims 1-5, or includes a module or unit for performing the method of any one of claims 6-12, or includes a module or unit for performing the method of claim 13, or includes a module or unit for performing the method of any one of claims 14-23. A communication device, characterized by The communication device includes at least one processor, the at least one processor being configured to, through logic circuitry and / or execution of instructions, cause the communication device to perform the method as claimed in any one of claims 1-5, or cause the communication device to perform the method as claimed in any one of claims 6-12, or cause the communication device to perform the method as claimed in claim 13, or cause the communication device to perform the method as claimed in any one of claims 14-23. A computer-readable storage medium, characterized by The computer-readable storage medium includes instructions that, when executed, cause the method of any one of claims 1-5 to be implemented, or the method of any one of claims 6-12 to be implemented, or the method of claim 13 to be implemented, or the method of any one of claims 14-23 to be implemented. A computer program product, characterized by The computer program product includes instructions that, when executed, cause the method of any one of claims 1-5 to be implemented, or the method of any one of claims 6-12 to be implemented, or the method of claim 13 to be implemented, or the method of any one of claims 14-23 to be implemented.

Images