Communication method and communication device

By providing a backhaul link and pre-generating registration parameters when the network topology changes, the communication latency problem of terminal devices when the network topology changes frequently is solved, resulting in lower registration process frequency and communication latency.

CN121665267APending Publication Date: 2026-03-13HUAWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-09-13
Publication Date
2026-03-13

AI Technical Summary

Technical Problem

In scenarios where network topology changes frequently, the frequent execution of registration processes by terminal devices leads to increased communication latency.

Method used

By providing initial configuration information, the terminal device and access network equipment are notified that other networks have a return link to the original registered core network, and registration parameters are generated in advance to reduce the frequency of the registration process.

Benefits of technology

This reduces the frequency of registration processes for terminal devices when the network topology changes, and reduces communication latency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN121665267A_ABST
    Figure CN121665267A_ABST
Patent Text Reader

Abstract

The invention provides a communication method and a communication device, relates to the field of communication, and can be applied to the field of satellite communication, such as NTN. The method comprises: a terminal device receiving first configuration information, the first configuration information being used for indicating that a first access network device has a first communication link for accessing a first core network, the first core network comprising a registration parameter of the terminal device, the first access network device being associated with a second core network, the first core network is different from the second core network; and the terminal equipment accesses the first core network through the first access network equipment. According to the embodiment of the invention, the terminal equipment is informed that other networks have the return visit link, such as the first communication link, of returning to the original registered core network through the first configuration information, so that conditions are provided for returning to the original registered core network when the terminal equipment resides in the coverage range of other networks, the frequency of executing a registration process by the terminal equipment is reduced, and the user experience is improved. And thus, the communication time delay can be reduced.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of communications, specifically to a communication method and a communication device. Background Technology

[0002] During communication, terminal devices typically need to register with the network to access its services. When the network topology changes, the terminal device needs to re-register. In scenarios with frequent network topology changes, such as non-terrestrial networks (NTN) communication, the terminal device needs to frequently perform the registration process, which will introduce communication latency. Summary of the Invention

[0003] This application provides a communication method and a communication device that can reduce communication latency caused by frequent execution of registration processes.

[0004] In a first aspect, a communication method is provided, the method comprising: a terminal device receiving first configuration information, the first configuration information being used to indicate that a first access network device has a first communication link for accessing a first core network, the first core network including registration parameters of the terminal device, the first access network device being associated with a second core network, and the first core network and the second core network being different; the terminal device accessing the first core network through the first access network device.

[0005] For example, the communication method can be implemented by a terminal device. The terminal device can be a terminal equipment, a module or component with terminal equipment functions, or a communication chip that can be applied to a terminal equipment, such as a processor, circuit, chip, or chip system.

[0006] For example, this communication method can be applied to various communication scenarios, such as terrestrial network scenarios and NTN scenarios.

[0007] For example, the first core network may be a core network that manages and / or maintains the registration parameters of the terminal device, or the terminal device may have registered in the first core network. For instance, the first core network may be the core network in the home network of the terminal device. Alternatively, the first core network may be the core network in a roaming network, but the terminal device may have registered in that roaming network.

[0008] For example, the second core network is the core network that the first access network device accesses by default, or in other words, the second core network is the core network that the first access network device prefers to access.

[0009] For example, the first core network is the core network that the second access network device accesses by default, or in other words, the first core network is the core network that the second access network device prefers to access.

[0010] For example, the registration parameters of the terminal devices managed and / or maintained by the second core network and the first core network are not exactly the same.

[0011] For example, the second core network and the first core network belong to different public land mobile networks (PLMNs), or in other words, the second core network and the first core network are core networks in different PLMNs.

[0012] For example, the second core network and the first core network are core networks of different operators.

[0013] For example, the second core network and the first core network are core networks of the same operator, but the second core network and the first core network can provide network services for different geographical areas.

[0014] In this embodiment of the application, the terminal device is notified by the first configuration information that other networks have a return link to the original registration core network, such as the first communication link. This provides the conditions for the terminal device to return to the original registration core network when it is stationed within the coverage area of ​​other networks, which helps to reduce the frequency of the terminal device performing the registration process, thereby helping to reduce communication latency.

[0015] In some embodiments, the first communication link includes a gateway or a second access network device, the second access network device being associated with the first core network.

[0016] For example, the gateway can serve as an intermediate node in the first communication link, meaning that the communication nodes in the first communication link include the first access network device, the gateway, and the first core network. This solution is easy to implement.

[0017] For example, the second access network device can serve as an intermediate node in the first communication link, meaning that the communication nodes in the first communication link include the first access network device, the second access network device, and the first core network. Since there is a communication link between the second access network device and the first core network, the first communication link can reuse this communication link, thereby saving configuration overhead.

[0018] In some embodiments, the terminal device accesses the first core network through the first access network device, including: the terminal device sending first information to the first access network device, the first information being used to indicate the first core network and / or the first communication link; and the terminal device receiving information from the first core network.

[0019] Since the first access network device can access both the first core network and the second core network, the first information helps the first access network device determine the core network that the terminal device wants to access.

[0020] In some embodiments, the first configuration information is carried in a registration success feedback message from the first core network, or the first configuration information is carried in a system message from the first access network device.

[0021] Multiple methods for carrying the first configuration information help improve configuration flexibility. For example, the method for carrying the first configuration information can be selected based on usage requirements and resource status.

[0022] In a second aspect, a communication method is provided, the method comprising: receiving first configuration information, the first configuration information being used to indicate that a first access network device has a first communication link to access a first core network, the first core network including registration parameters of a terminal device, the first access network device being associated with a second core network, and the first core network and the second core network being different; and sending the first configuration information to the terminal device.

[0023] For example, the communication method can be implemented by a first access network device, or by components within the first access network device, such as a processor, circuit, chip, or chip system. Optionally, the first access network device can be a fourth-generation (4G) base station, a fifth-generation (5G) base station, or a base station in a future communication system.

[0024] In this embodiment of the application, the terminal device is notified by the first configuration information that other networks have a return link to the original registration core network, such as the first communication link. This provides the conditions for the terminal device to return to the original registration core network when it is stationed within the coverage area of ​​other networks, which helps to reduce the frequency of the terminal device performing the registration process, thereby helping to reduce communication latency.

[0025] In some embodiments, first information is received from the terminal device, the first information being used to indicate the first core network and / or the first communication link; and configuration information for activating the first communication link is received.

[0026] In other words, after generating the configuration information for the first communication link, this configuration information does not need to be activated immediately. For example, the configuration information for the first communication link can be activated when it is used, which helps reduce system overhead.

[0027] Thirdly, a communication method is provided, the communication method comprising: sending first configuration information, the first configuration information being used to indicate that a first access network device has a first communication link to access a first core network, the first core network including registration parameters of a terminal device, the first access network device being associated with a second core network, and the first core network and the second core network being different.

[0028] For example, the communication method can be implemented by a first core network or by components within the first core network, such as processors, circuits, chips, or chip systems.

[0029] Optionally, this communication method can be implemented by network elements within the first core network. As an example, the communication method can be implemented by the access and mobility management function (AMF) network element in the first core network, or by circuits, chips, or chip systems that implement the AMF network element functions.

[0030] In this embodiment of the application, the terminal device is notified by the first configuration information that other networks have a return link to the original registration core network, such as the first communication link. This provides the conditions for the terminal device to return to the original registration core network when it is stationed within the coverage area of ​​other networks, which helps to reduce the frequency of the terminal device performing the registration process, thereby helping to reduce communication latency.

[0031] In some embodiments, the first communication link includes a gateway or a second access network device, the second access network device being associated with the first core network.

[0032] For example, the gateway can serve as an intermediate node in the first communication link, meaning that the communication nodes in the first communication link include the first access network device, the gateway, and the first core network. This solution is easy to implement.

[0033] For example, the second access network device can serve as an intermediate node in the first communication link, meaning that the communication nodes in the first communication link include the first access network device, the second access network device, and the first core network. Since there is a communication link between the second access network device and the first core network, the first communication link can reuse this communication link, thereby saving configuration overhead.

[0034] In some embodiments, before sending the first configuration information, the method further includes: sending second information to the gateway or the second access network device, the second information being used to instruct the establishment of the first communication link.

[0035] The timing for creating the first communication link can be determined using the second piece of information. Since the first core network can communicate with the nodes in the first communication link, initiating the creation of the first communication link by the first core network is simple.

[0036] In some embodiments, the first configuration information includes one or more of the following: indication information of the first access network device; indication information of the first communication link; or priority information of the first communication link.

[0037] For example, the first configuration information may include indication information of the first access network device, wherein the indication information of the first access network device may include: identification information of the first access network device; identification information of the network to which the first access network device belongs, such as the identification information of the PLMN to which the first access network device belongs; or identification information of the cell to which the first access network device provides services, etc. In this way, the terminal device can determine the access network device with the ability to revisit the first core network based on the first configuration information. When the area where the terminal device is stationary is covered by multiple access network devices, the terminal device can prioritize accessing the access network device with the ability to revisit the first core network, which helps reduce the registration frequency and thus helps reduce the communication latency caused by registration.

[0038] For example, the indication information of the first communication link can be used to indicate the target core network of the first communication link, i.e., the first core network, which helps to reduce indication overhead.

[0039] For example, the indication information of the first communication link can be used to indicate the path information of the first communication link. When multiple communication links exist that revisit the first core network, the path information of the first communication link can be used to assist the terminal device in selecting the communication link that revisits the first core network, thereby helping to improve system performance.

[0040] For example, configuration information and identifier of the first communication link can be pre-configured, and the identifier of the first communication link can be dynamically indicated through the first configuration information to save indication overhead.

[0041] For example, the first configuration information may include priority information of the first communication link. The priority information of the first communication link can assist the terminal device in selecting the communication link for revisiting the first core network, thereby improving the reliability and / or timeliness of the revisit traffic transmission.

[0042] Fourthly, a communication method is provided, the method comprising: receiving second information, the second information being used to instruct the establishment of a first communication link, the first communication link being used by a first access network device to access a first core network, the first core network including registration parameters of a terminal device, the first access network device being associated with a second core network, and the first core network and the second core network being different; establishing a mapping relationship between a first interface and a second interface, the first interface being used to communicate with the first core network, and the second interface being used to communicate with the first access network device.

[0043] For example, when the second access network device acts as an intermediate node in the first communication link, the communication method can be implemented by the second access network device itself, or by components within the second access network device, such as processors, circuits, chips, or chip systems. The second access network device can be, for example, a 4G base station, a 5G base station, or a base station in a future communication system.

[0044] For example, when the gateway acts as an intermediate node in the first communication link, the communication method can be implemented by the gateway device or by components inside the gateway device, such as processors, circuits, chips, or chip systems.

[0045] In this embodiment of the application, the terminal device is notified by the first configuration information that other networks have a return link to the original registration core network, such as the first communication link. This provides the conditions for the terminal device to return to the original registration core network when it is stationed within the coverage area of ​​other networks, which helps to reduce the frequency of the terminal device performing the registration process, thereby helping to reduce communication latency.

[0046] The first to fourth aspects describe the methods for creating the first communication link and revisiting the original registered core network through the first communication link. The fifth to eighth aspects below describe the pre-registration methods.

[0047] Fifthly, a communication method is provided, comprising: a terminal device sending a first registration request message to a second access network device, the second access network device being associated with a first core network, wherein the first registration request message includes first indication information, the first indication information being used to indicate the first core network and the second core network; or, the first registration request message includes second indication information and auxiliary information, the second indication information being used to indicate the first core network, and the auxiliary information being used to determine the second core network; the terminal device receiving first registration parameters and second registration parameters, the first registration parameters being registration parameters of the terminal device in the first core network, and the second registration parameters being registration parameters of the terminal device in the second core network.

[0048] For example, the communication method can be implemented by a terminal device. The terminal device can be a terminal equipment, a module or component with terminal equipment functions, or a communication chip that can be applied to a terminal equipment, such as a processor, circuit, chip, or chip system.

[0049] For example, the first instruction information can be determined by the terminal device, that is, the terminal device determines the multiple networks for which the terminal device performs registration.

[0050] For example, the first core network can determine the second core network based on auxiliary information. That is, the core network side determines the network for the terminal device to perform pre-registration, or in other words, the core network side determines the candidate network.

[0051] This application embodiment pre-completes the registration process of the terminal device in other networks, or in other words, pre-generates the registration parameters of the terminal device in other networks. This allows the terminal device to directly obtain the pre-generated registration parameters when accessing other networks, without waiting for the generation process of the registration parameters, thereby helping to reduce the communication latency caused by registration.

[0052] In some embodiments, the auxiliary information includes one or more of the following: location information of the terminal device; a first time period, where it is desired not to execute the registration process of the terminal device during the first time period; or a first location area, where it is desired not to execute the registration process of the terminal device within the first location area.

[0053] In some embodiments, the first indication information is carried in a non-access stratum (NAS) message, or the first indication information is carried in a radio resource control (RRC) establishment completion message.

[0054] In some embodiments, the first registration parameter is carried in a registration success feedback message from the first core network, the second registration parameter is carried in a registration success feedback message from the first core network, or the second registration parameter is carried in a registration success feedback message from the second core network.

[0055] The multiple ways of carrying the second registration parameter help to improve the flexibility of configuring the registration parameter.

[0056] In some embodiments, the method further includes: activating the second registration parameter if a first condition is met, wherein the first condition includes one or more of the following: the terminal device establishes a connection with the first access network device, and the first access network device is associated with the second core network; the terminal device is located within the coverage area of ​​the first access network device; it is predicted that the terminal device is located within the coverage area of ​​the first access network device; an instruction to activate the second registration parameter is received; or the public land mobile network (PLMN) to which the terminal device is camped is the PLMN to which the second core network belongs.

[0057] It should be noted that "activating registration parameters" can be understood as meaning the registration parameter is valid, or that the registration parameter is being used; conversely, "deactivating registration parameters" can be understood as meaning the registration parameter is invalid, or that the registration parameter is not being used. The following explanation uses the first registration parameter as an example to illustrate the meaning of "activation" and "deactivation".

[0058] Activating the first registration parameter can be understood as: the first registration parameter is a valid registration parameter or is used as the registration parameter of the terminal device. Deactivating the first registration parameter can be understood as: the first registration parameter is an invalid registration parameter or is not used as the registration parameter of the terminal device.

[0059] In some embodiments, the second registration parameters include multiple sets of registration parameters, which are the registration parameters of the terminal device in multiple second core networks. The step of activating the second registration parameters if the first condition is met includes: if the first condition is met, determining a target registration parameter among the second registration parameters based on the priority of the multiple sets of registration parameters; and activating the target registration parameter.

[0060] Priority information for registration parameters can help terminal devices select appropriate registration parameters.

[0061] In some embodiments, the registration parameters in the home network have a higher priority than the registration parameters in the roaming network, and / or the size of the tracking area provided by the second core network is proportional to the priority of the terminal device's registration parameters in the second core network.

[0062] Prioritizing the activation of registration parameters in the home network helps reduce data transmission overhead between the roaming network and the home network. The larger the tracking area associated with a registration parameter, the higher its priority. In other words, prioritizing the activation of registration parameters with the largest corresponding tracking area helps reduce the frequency of mobility registration updates, thereby further reducing communication latency.

[0063] In some embodiments, the first condition is carried in the registration success feedback message of the first core network or the registration success feedback message of the second core network.

[0064] In some embodiments, the tracking area provided by the first core network is a first tracking area, and the tracking area provided by the second core network is a second tracking area. The method further includes: receiving indication information of a third tracking area from a third access network device, wherein the third access network device provides coverage for the area where the terminal device is currently residing; if the first tracking area does not include the third tracking area, and the second tracking area also does not include the third tracking area, then a mobility registration process is triggered.

[0065] This method helps reduce the frequency with which terminal devices trigger mobility registration updates, thereby helping to reduce system overhead.

[0066] A sixth aspect provides a communication method, the method comprising: receiving a first registration request message from a terminal device, the first registration request message including first indication information, the first indication information being used to indicate a first core network and a second core network; sending the first registration request message to the first core network; or sending the first registration request message to the first core network and sending the first registration request message to the second core network.

[0067] For example, the communication method can be implemented by a second access network device, or by components within the second access network device, such as a processor, circuit, chip, or chip system. The second access network device can be, for example, a 4G base station, a 5G base station, or a base station in a future communication system.

[0068] This application embodiment pre-completes the registration process of the terminal device in other networks, or in other words, pre-generates the registration parameters of the terminal device in other networks. This allows the terminal device to directly obtain the pre-generated registration parameters when accessing other networks, without waiting for the generation process of the registration parameters, thereby helping to reduce the communication latency caused by registration.

[0069] A seventh aspect provides a communication method, the method comprising: receiving a first registration request message, the first registration request message including first indication information, the first indication information being used to indicate a first core network and a second core network, or the first registration request message including second indication information and auxiliary information, the second indication information being used to indicate the first core network, the auxiliary information being used to determine the second core network; sending a registration success feedback message, the registration success feedback message including a first registration parameter, or the registration success feedback message including the first registration parameter and a second registration parameter, the first registration parameter being a registration parameter of a terminal device in the first core network, and the second registration parameter being a registration parameter of the terminal device in the second core network.

[0070] For example, the communication method can be implemented by the first core network or by components within the first core network, such as processors, circuits, chips, or chip systems. Optionally, the communication method can be implemented by network elements in the first core network, such as AMFs.

[0071] This application embodiment pre-completes the registration process of the terminal device in other networks, or in other words, pre-generates the registration parameters of the terminal device in other networks. This allows the terminal device to directly obtain the pre-generated registration parameters when accessing other networks, without waiting for the generation process of the registration parameters, thereby helping to reduce the communication latency caused by registration.

[0072] In some embodiments, the method further includes: determining the second core network based on the auxiliary information; and sending a second registration request message to the second core network, the second registration request message being used to request the second registration parameters.

[0073] In other words, the core network side determines the network for the terminal device to perform pre-registration, or in other words, the core network side determines the candidate network.

[0074] For example, the first core network can determine when to send the second registration request message to the second core network. If there are multiple second core networks, the timing of the first core network sending the second registration request message to the multiple second core networks is not exactly the same, thereby helping to avoid congestion of registration signaling on the first core network side.

[0075] In some embodiments, the auxiliary information includes one or more of the following: location information of the terminal device; a first time period, where it is desired not to execute the registration process of the terminal device during the first time period; or a first location area, where it is desired not to execute the registration process of the terminal device within the first location area.

[0076] In some embodiments, the method further includes: generating first registration parameters; and sending some or all of the parameters in the first registration parameters to the second core network.

[0077] In other words, the second core network can reuse some or all of the first registration parameters during the generation of the second registration parameters, thereby omitting some steps in the registration process and helping to reduce the processing overhead of the second core network.

[0078] In some embodiments, the method further includes: deactivating the first registration parameter in response to receiving an instruction to deactivate the first registration parameter, or when a first timer expires, wherein the start time of the first timer is the activation time of the first registration parameter.

[0079] Eighthly, a communication method is provided, the method comprising: receiving a second registration request message from a second access network device or a first core network, the second registration request message being used to request second registration parameters of a terminal device in the second core network, the second access network device being associated with the first core network; and sending the second registration parameters.

[0080] For example, the communication method can be implemented by a second core network, or by components within the second core network, such as processors, circuits, chips, or chip systems. Optionally, the communication method can be implemented by network elements in the second core network.

[0081] In some embodiments, before sending the second registration parameters, the method further includes: receiving some or all of the parameters in the first registration parameters, wherein the first registration parameters are the registration parameters of the terminal device in the first core network; and generating the second registration parameters based on the some or all of the parameters.

[0082] In other words, the second core network can reuse some or all of the first registration parameters during the generation of the second registration parameters, thereby omitting some steps in the registration process and helping to reduce the processing overhead of the second core network.

[0083] In some embodiments, the method further includes: activating the second registration parameter if a first condition is met, wherein the first condition includes one or more of the following: the terminal device establishes a connection with the first access network device, and the first access network device is associated with the second core network; the terminal device is located within the coverage area of ​​the first access network device; it is predicted that the terminal device is located within the coverage area of ​​the first access network device; an instruction to activate the second registration parameter is received; or the public land mobile network (PLMN) to which the terminal device is camped is the PLMN to which the second core network belongs.

[0084] This application embodiment pre-completes the registration process of the terminal device in other networks, or in other words, pre-generates the registration parameters of the terminal device in other networks. This allows the terminal device to directly obtain the pre-generated registration parameters when accessing other networks, without waiting for the generation process of the registration parameters, thereby helping to reduce the communication latency caused by registration.

[0085] A ninth aspect provides a communication device comprising: a unit for performing each step in any possible implementation of the first or fifth aspect above. Exemplarily, the communication device may be a terminal device.

[0086] In a tenth aspect, a communication apparatus is provided, comprising: units for performing the steps of the possible implementations of the second aspect above. Exemplarily, the communication apparatus may be a first access network device.

[0087] Eleventhly, a communication device is provided, comprising: a unit for performing each step in any possible implementation of the third or seventh aspect above. Exemplarily, the communication device may be a first core network, or a functional node within the first core network.

[0088] In a twelfth aspect, a communication device is provided, comprising: units for performing the steps of the possible implementations of the fourth aspect above. Exemplarily, the communication device may be a gateway.

[0089] In a thirteenth aspect, a communication apparatus is provided, comprising: a unit for performing each step in any possible implementation of the fourth or sixth aspect above. Exemplarily, the communication apparatus may be a second access network device.

[0090] In a fourteenth aspect, a communication device is provided, comprising: a unit for performing the steps of the possible implementations of the eighth aspect above. Exemplarily, the communication device may be a second core network, or a functional node within the second core network.

[0091] In a fifteenth aspect, a communication device is provided, the communication device including at least one processor coupled to a memory for storing a program or instructions, wherein when the program or instructions are executed by the processor, the method of any possible implementation of the first or fifth aspect is performed.

[0092] In a sixteenth aspect, a communication device is provided, comprising at least one processor coupled to a memory for storing programs or instructions which, when executed by the processor, perform the methods of the possible implementations of the second aspect above.

[0093] In a seventeenth aspect, a communication device is provided, the communication device including at least one processor coupled to a memory for storing a program or instructions, wherein when the program or instructions are executed by the processor, the method of any possible implementation of the third or seventh aspect above is performed.

[0094] In an eighteenth aspect, a communication device is provided, the communication device including at least one processor coupled to a memory for storing a program or instructions, which, when executed by the processor, perform the method of the possible implementation of the fourth aspect above.

[0095] In a nineteenth aspect, a communication device is provided, the communication device including at least one processor coupled to a memory for storing a program or instructions, wherein when the program or instructions are executed by the processor, the method of any possible implementation of the fourth or sixth aspect above is performed.

[0096] In a twentieth aspect, a communication device is provided, comprising at least one processor coupled to a memory for storing programs or instructions which, when executed by the processor, perform the methods of the possible implementations of the eighth aspect above.

[0097] In a twenty-first aspect, a communication device is provided, comprising at least one processor and a memory coupled together, the memory storing program instructions, wherein when the program instructions stored in the memory are executed by the processor, the method of any possible implementation of the first aspect or the fifth aspect above is performed.

[0098] In a twenty-second aspect, a communication device is provided, comprising at least one processor and a memory coupled together, the memory storing program instructions, wherein when the program instructions stored in the memory are executed by the processor, the method in the possible implementation of the second aspect is performed.

[0099] In a twentieth aspect, a communication device is provided, comprising at least one processor and a memory coupled together, the memory storing program instructions, wherein when the program instructions stored in the memory are executed by the processor, the method of any possible implementation of the third or seventh aspect is performed.

[0100] In a twentieth aspect, a communication device is provided, comprising at least one processor and a memory coupled together, the memory storing program instructions, wherein when the program instructions stored in the memory are executed by the processor, the method in the possible implementation of the fourth aspect above is performed.

[0101] In a twenty-fifth aspect, a communication device is provided, comprising at least one processor and a memory coupled together, the memory storing program instructions, wherein when the program instructions stored in the memory are executed by the processor, the method of any possible implementation of the fourth or sixth aspect above is performed.

[0102] In a twenty-sixth aspect, a communication device is provided, comprising at least one processor and a memory coupled together, the memory storing program instructions, wherein when the program instructions stored in the memory are executed by the processor, the method in the possible implementation of the eighth aspect above is performed.

[0103] In a twenty-seventh aspect, a communication device is provided, the communication device including at least one processor and an interface circuit, the interface circuit being used to transmit and / or receive signals, causing the processor to perform the method in any possible implementation of the first aspect or the fifth aspect above.

[0104] In a twentieth aspect, a communication device is provided, comprising at least one processor and an interface circuit for transmitting and / or receiving signals, such that the processor performs the method described in the possible implementations of the second aspect above.

[0105] In a twentieth aspect, a communication apparatus is provided, comprising at least one processor and an interface circuit for transmitting and / or receiving signals, such that the processor performs a method in any of the possible implementations of the third or seventh aspect above.

[0106] In a thirtieth aspect, a communication device is provided, comprising at least one processor and an interface circuit for transmitting and / or receiving signals, such that the processor performs the method described in the possible implementations of the fourth aspect above.

[0107] In a thirty-first aspect, a communication device is provided, comprising at least one processor and an interface circuit for transmitting and / or receiving signals, such that the processor performs a method in any of the possible implementations of the fourth and sixth aspects above.

[0108] In a thirty-second aspect, a communication device is provided, comprising at least one processor and an interface circuit for transmitting and / or receiving signals, such that the processor performs the method of the possible implementations of the eighth aspect above.

[0109] In a thirty-third aspect, a computer program product is provided, comprising a computer program that, when executed by a processor, performs a method in any possible implementation of any of the first to eighth aspects.

[0110] In a thirty-fourth aspect, a computer-readable storage medium is provided, wherein a computer program is stored therein, which, when executed, performs the method in any possible implementation of any of the first to eighth aspects above.

[0111] In a thirty-fifth aspect, a chip is provided, comprising: a processor for calling and running a computer program from a memory, causing a communication device having the chip installed to perform the methods in any possible implementations of any of the first to eighth aspects above. Attached Figure Description

[0112] Figure 1 This is a schematic diagram of the architecture of the communication system used in the embodiments of this application;

[0113] Figure 2 This application provides a schematic diagram of an application architecture for a satellite communication network.

[0114] Figure 3 This is a schematic diagram of a roaming architecture provided in an embodiment of this application;

[0115] Figure 4 A flowchart illustrating a communication method provided in an embodiment of this application;

[0116] Figure 5 A schematic diagram of the first communication link provided in an embodiment of this application;

[0117] Figure 6 for Figure 5 An example diagram of the first communication link in the process;

[0118] Figure 7 Another example diagram of the first communication link provided in the embodiments of this application;

[0119] Figure 8 A flowchart illustrating another communication method provided in an embodiment of this application;

[0120] Figure 9 A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0121] Figure 10 A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0122] Figure 11 A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0123] Figure 12 This is a schematic block diagram of a communication device provided in an embodiment of this application;

[0124] Figure 13 This is a schematic block diagram of another communication device provided in the embodiments of this application. Detailed Implementation

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

[0126] 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. "And / or" in the embodiments of this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural. 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 single or plural 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 essentially the same function and effect. Those skilled in the art will understand that the words "first" and "second" do not limit the quantity or the order of execution, and that the words "first" and "second" do not necessarily imply that they are different.

[0127] In the various method embodiments of this application, the order of the sequence numbers does not imply the order of execution. The execution order should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0128] It is understood that in the embodiments of this application, descriptions such as "under the circumstances," "if," "when," and "if..." can be used interchangeably. Furthermore, these descriptions all refer to the corresponding processing that will be carried out under certain objective circumstances, and are not limited to a specific time, nor do they require any judgment action during implementation, nor do they imply any other limitations.

[0129] It is understood that some optional features in the embodiments of this application can be implemented independently in certain scenarios without relying on other features, such as the current solution on which they are based, to solve the corresponding technical problems and achieve the corresponding effects. Alternatively, they can be combined with other features as needed in certain scenarios. Correspondingly, the apparatus given in the embodiments of this application can also implement these features or functions, which will not be elaborated here.

[0130] In the embodiments of this application, unless otherwise specified, the same or similar parts between the various embodiments can be referred to each other. In the various embodiments of this application, and in the various implementation methods / methods / implementations within each embodiment, unless otherwise specified or logically conflicting, the terminology and / or descriptions between different embodiments and between the various implementation methods / methods / implementations within each embodiment are consistent and can be mutually referenced. The technical features in different embodiments and the various implementation methods / methods / implementations within each embodiment can be combined according to their inherent logical relationships to form new embodiments, implementation methods, methods, or implementation approaches. The embodiments of this application described below do not constitute a limitation on the scope of protection of this application.

[0131] The embodiments of this application can be applied to various communication systems. For ease of understanding, the following examples are used... Figure 1 Taking the communication system 10 shown as an example, the communication system applicable to the embodiments of this application will be described.

[0132] Figure 1 This is a schematic diagram of the architecture of the communication system 10 used in an embodiment of this application. Figure 1 As shown, the communication system includes a radio access network (RAN) 100, wherein the RAN 100 includes at least one RAN node (e.g., Figure 1 110a and 110b, collectively referred to as 110, may also include at least one terminal (such as...). Figure 1RAN100, denoted as RAN100, comprises RAN nodes 120a-120j, collectively referred to as RAN120. RAN100 may also include other RAN nodes, such as wireless relay equipment and / or wireless backhaul equipment. Figure 1 (Not shown in the image). Terminal 120 is wirelessly connected to RAN node 110. Terminals and RAN nodes can be interconnected via wired or wireless means. Communication system 10 may also include core network 200. RAN node 110 is connected to core network 200 via wireless or wired means. The core network equipment in core network 200 and RAN node 110 in RAN 100 can be independent physical devices, or they can be the same physical device integrating the logical functions of core network equipment and RAN node. Communication system 10 may also include Internet 300.

[0133] RAN 100 can be an evolved universal terrestrial radioaccess (E-UTRA) system, a new radio (NR) system, or a future radio access system as defined in the 3rd generation partnership project (3GPP). RAN 100 can also be an open RAN (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system. RAN 100 can also be a communication system that integrates two or more of the above systems.

[0134] RAN node 110 (also known as access network equipment, RAN entity, or access node, etc.) is used to help terminals access the communication system wirelessly. In one possible scenario, the RAN node can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a base station in a future mobile communication system, or an access node in a WiFi system, etc. The RAN node can also be a macro base station (such as...) Figure 1 110a), micro base stations or indoor stations (such as Figure 1In CRAN scenarios, RAN nodes can be 110b), relay nodes or donor nodes, or wireless controllers. In satellite communication scenarios, such as NTN, RAN nodes can be base stations deployed on satellites, such as 4G base stations, 5G base stations, or base stations in future communication systems. When access network equipment is deployed on satellites, RAN nodes can also refer to satellites with access network capabilities. Optionally, RAN nodes can also be servers, wearable devices, vehicles, or in-vehicle equipment. For example, in vehicle-to-everything (V2X) technology, the access network equipment can be a roadside unit (RSU).

[0135] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, with different RAN nodes implementing some of the base station's functions. For example, RAN nodes can be central units (CUs), distributed units (DUs), or radio units (RUs). Here, the CU can perform the functions of the base station's radio resource control protocol and PDCP, as well as the service data adaptation protocol (SDAP). The DU can perform the functions of the base station's radio link control layer and medium access control (MAC) layer, and can also perform some or all of the physical layer functions. For specific descriptions of these protocol layers, refer to the relevant 3GPP technical specifications. The RU can be used to implement radio frequency signal transmission and reception. The CU and DU can be two independent RAN nodes, or they can be integrated into the same RAN node, such as within a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs). CUs can be further divided into two types of RAN nodes: CU-control plane (CP) and CU-user plane (UP).

[0136] In different systems, RAN nodes may have different names. For example, in an O-RAN system, a CU can be called an open CU (O-CU), a DU can be called an open DU (O-DU), and an RU can be called an open RU (O-RU). Similarly, a CU-CP can be called an O-CU-CP, a CU-UP can be called an O-CU-UP, and an RU can be called an O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples in its embodiments.

[0137] All or part of the functions of the RAN node in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The RAN node may also be equipped with communication modules, circuits, or chips that perform corresponding communication functions. The RAN node may also be configured with program instructions for performing corresponding communication functions and corresponding program instructions. The RAN node in this application can also be a logical node, logical module, or software capable of implementing all or part of the RAN node functions. The embodiments of this application do not limit the specific technology or specific device form used in the RAN node.

[0138] Terminal 120 is a device with wireless transceiver capabilities, capable of sending signals to or receiving signals from a base station. The terminal can also be referred to as user equipment (UE), terminal equipment, access terminal, user unit, user station, mobile station (MS), remote station, remote terminal, mobile terminal (MT), user terminal, wireless communication equipment, user agent, and user device, etc. Terminal 120 can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, wearable device, vehicle, drone, helicopter, airplane, ship, robot, robotic arm, smart home device, etc. The embodiments of this application do not limit the device form of the terminal.

[0139] For example, terminal 120 can be an Internet of Things (IoT) device (e.g., a sensor, electricity meter, water meter, etc.), a V2X device, a station (ST) in a wireless local area network (WLAN), a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device (also known as a wearable smart device), a tablet computer or a computer with wireless transceiver capabilities, a virtual reality (VR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical care, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, or a wireless terminal in a smart home. Wireless terminals in the home, vehicle terminals, vehicles with vehicle-to-vehicle (V2V) communication capabilities, intelligent connected vehicles, drones with drone-to-drone (UAV-to-UAV, U2U) communication capabilities, etc.

[0140] The roles of base stations and terminals can be relative, for example, Figure 1 The 120i network element can be a helicopter or a drone, and it can be configured as a mobile base station. For terminals 120j that access the wireless access network 100 via the 120i, terminal 120i is a base station; however, for base station 110a, 120i is a terminal, meaning that 110a and 120i communicate via a wireless air interface protocol. Of course, 110a and 120i can also communicate via a base station-to-base station interface protocol; in this case, relative to 110a, 120i is also a base station. Therefore, both base stations and terminals can be collectively referred to as communication devices. Figure 1 The 110a and 110b in the text can be referred to as communication devices with base station functions. Figure 1 The 120a-120j in the text can be referred to as communication devices with terminal functions.

[0141] Base stations and terminals can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can be deployed on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of the base stations and terminals.

[0142] With the development of information technology, there are more urgent demands for efficient, mobile, and diverse communications. Currently, a key development area in the field of communication systems is global mobile communications (GSM), and a crucial component of GSM is satellite communications, a typical example of which is satellite communication. In some important fields, such as space communications, aviation communications, and maritime communications, satellites play an irreplaceable role.

[0143] The 5G mobile communication network technology standard released by the 3GPP standards organization studies the space-ground converged communication technology, which mainly integrates the existing 5G standard and satellite communication technology to achieve full coverage on a global scale.

[0144] Satellite communication boasts advantages such as long communication distance, large coverage area, and flexible networking, providing services to both fixed and various mobile terminals. Satellites are categorized by orbital altitude into low Earth orbit (LEO), medium Earth orbit (MEO), geostationary earth orbit (GEO), and highly elliptical orbit (HEO) satellites. In addition to satellites, NTN can also include aircraft such as high altitude platforms (HAPs) and unmanned aircraft systems (UAS).

[0145] The NTN involved in the embodiments of this application can be implemented using any of the following: satellite, altitude platform, or unmanned aerial vehicle (UAV) systems. Furthermore, the NTN in the embodiments of this application can be a 4G-based NTN, an NR-based NTN, an Internet of Things (IoT)-based NTN, a narrowband Internet of Things (NB-IoT)-based NTN, or an NTN based on other current or future technologies.

[0146] Compared to traditional terrestrial networks, NTN typically uses satellites for network deployment. For example, it deploys access network equipment or some access network equipment functions on satellites to provide coverage for terminal devices, or it uses satellites as relays to forward signals from terrestrial access network equipment to provide coverage for terminal devices.

[0147] For example, Figure 2 This is a schematic diagram of the application architecture of a satellite communication network provided in an embodiment of this application. Figure 2 The architecture shown integrates satellite communication technology and 5G communication technology. Figure 2 The architecture shown may include: terminal device 201, access network device 202, ground station 203, core network (including 204a and 204b), and data network 205. The terminal device can access the network via 5G New Radio; the access network device is deployed on satellites and connected to the ground core network via a wireless link. Simultaneously, a wireless link exists between the satellites, which is used for signaling interaction and user data transmission between the access network devices. The following section... Figure 2 The various units and their interfaces are described.

[0148] Terminal device 201: A mobile device that supports 5G New Radio. For example, terminal device 201 can be a mobile device such as a smartphone, smartwatch, or tablet, or any of the terminal devices mentioned above. Terminal device 201 can access the satellite network via the air interface and initiate services such as making calls and accessing the internet.

[0149] Access network equipment 202: mainly provides wireless access services, such as scheduling wireless resources to access terminals, and providing reliable wireless transmission protocols and data encryption protocols. Figure 2 The access network device 202 shown can be a 5G base station.

[0150] Core network: Provides services such as user access control, mobility management, session management, user security authentication, and accounting. The core network may include multiple functional units. In some embodiments, the core network can be divided into control plane functional entities 204a and data plane functional entities (also referred to as user plane functional entities) 204b. It should be noted that functional entities can be understood as network elements, network functions, etc., and this application does not limit them in this regard.

[0151] User plane function (UPF) network elements are used to manage user plane data transmission, traffic statistics, etc. Control plane function entities may include at least access and mobility management (AMF) network elements and session management (SMF) network elements. AMF network elements can be used for user access management, security authentication, and mobility management, such as terminal location updates, network registration, access control, terminal mobility management, and terminal attachment and detachment. SMF network elements can be used to select user plane network elements for terminal devices, redirect user plane network elements for terminals, assign Internet Protocol (IP) addresses to terminals, establish bearers (also known as sessions) between terminals and UPF network elements, modify and release sessions, and perform QoS control.

[0152] Ground station 203: Also known as a gateway, it is responsible for forwarding signaling and service data between the satellite and the 5G core network.

[0153] 5G New Radio: The wireless link between terminal equipment and access network equipment.

[0154] Xn interface: The interface between 5G access network devices and other access network devices, mainly used for signaling interactions such as handover.

[0155] NG interface: The interface between 5G access network equipment and 5G core network, mainly used for exchanging non-access stratum (NAS) signaling of the core network and user service data.

[0156] During communication, terminal devices typically need to register with the network to access its services. During registration, the core network assigns an identifier to the terminal device and obtains its location, routing, and subscription information. In some embodiments, registration types can be categorized as initial registration, mobility registration, and periodic registration. Initial registration occurs when a terminal device powers on for the first time or enters a network coverage area. After initial registration, the terminal device can periodically update its registration parameters to ensure the network understands its current location and status; this is periodic registration (or periodic registration update). When the network topology accessed by the terminal device changes, such as when it switches from one cell to another, mobility registration (or mobility registration update) may be triggered to ensure communication continuity. Additionally, registration can be triggered when the terminal device updates its capabilities, renegotiates protocol parameters, or in emergency situations.

[0157] Taking roaming scenarios as an example, the original registration network of the terminal device is the home public land mobile network (HPLMN). When the terminal device is camped on the visited public land mobile network (VPLMN), it needs to re-register and access the VPLMN. During the VPLMN re-registration process, the HPLMN can provide session anchors, policies, and subscription data.

[0158] Figure 3 This is a schematic diagram of a roaming architecture provided in an embodiment of this application. Figure 3 The architecture shown supports the registration and access of the aforementioned terminal devices to the VPLMN. See also... Figure 3 Both HPLMN and VPLMN core networks can include user plane function (UPF) network elements, access and mobility management function (AMF) network elements, session management function (SMF) network elements, policy control function (PCF) network elements, application function (AF) network elements, data network (DN), network slice selection function (NSSF), authentication server function (AUSF), and unified data management (UDM) functions. It should be noted that some network elements... Figure 3 The network elements involved in the registration process and their functions are not shown in the diagram. The following is a brief introduction to the network elements involved in the registration process and their functions.

[0159] AMF (Access Authentication and Authorization) network elements can be used to manage access authorization and authentication. When a terminal device registers with the serving network, the AMF network element of the serving network sends an initial authentication request to the home network AUSF (Authorization and Authorization Service Provider) network element and receives the authentication vector from the home AUSF network element, completing the authentication of the terminal device in the serving network. After the terminal device is successfully authenticated in the serving network, the AMF network element initiates the registration process, retrieving the user's subscription data from the UDM (User Authentication and Authorization) network element.

[0160] The AUSF network element is used to receive AMF requests for authentication of terminal devices. It requests a key from the UDM and then forwards the issued key to the AMF for authentication processing.

[0161] UDM network elements are used for generating and storing user subscription data, managing authentication data, etc., and support interaction with external third-party servers. During the registration process, after receiving the registration message from the AMF, the UDM network element can return the subscription data.

[0162] For example, HPLMN and VPLMN can interact through a security edge protection proxy (SEPP). Specifically, control plane data can be exchanged between the visited SEPP (vSEPP) and the home SEPP (hSEPP); user plane data can be exchanged through the security edge protection proxy for user plane (SEPP-U).

[0163] In scenarios where network topology changes frequently, such as NTN scenarios, terminal devices need to frequently execute registration processes, which will introduce certain communication latency. The following section uses a typical NTN communication scenario, i.e., satellite communication, as an example to illustrate this problem.

[0164] Due to the motion characteristics of satellites, satellite network topology is dynamically changing. This satellite motion causes changes in the core network parameters of terminal devices, or in other words, changes in the core network that the terminal devices access. This is because: when the core network is deployed on the ground, the satellites connected to the terminal devices change as the satellites move, and the terminal devices access different core networks through different satellites; when the core network is deployed on satellites, the satellites connected to the terminal devices change as the satellites move (i.e., the core network itself moves), thus causing changes in the core network that the terminal devices access.

[0165] As a result, terminal devices need to frequently perform operations such as registration updates and inter-network roaming. Only after completing these operations can the terminal device communicate with the newly connected core network. Therefore, frequent registration processes will introduce a certain amount of communication latency.

[0166] To address the aforementioned issues, this application provides a communication method that establishes a communication link between the original registration core network and other networks, enabling terminal devices to revisit the original registration core network when they reside within the coverage area of ​​other networks. In this case, the terminal device does not need to perform the registration process on the aforementioned other networks, which helps reduce the frequency of the terminal device performing the registration process, thereby helping to reduce communication latency.

[0167] Figure 4This is a flowchart illustrating a communication method provided in an embodiment of this application. Figure 4 The method shown may involve interaction between a terminal device, a first access network device, a second access network device, and a first core network.

[0168] It should be understood that a terminal device can be a terminal equipment, a module or component with terminal equipment functions, or a communication chip that can be applied to a terminal equipment, such as a processor, circuit, chip or chip system.

[0169] It should be understood that the first access network device and the second access network device can be any type of access network device mentioned above, or they can be chips, chip systems, or processors that support the implementation of this method in the access network devices. For example, the first access network device and the second access network device can be 4G base stations, 5G base stations, or base stations in future communication systems. Furthermore, the first access network device and the second access network device can be deployed partially or entirely on satellites.

[0170] It should be understood that the first core network can be any functional entity (such as any network element) or logical unit in the core network, or it can be a chip, chip system, or processor that supports the core network in implementing this method.

[0171] The method provided in the embodiments of this application will now be described from the perspective of interaction between the terminal device, the first access network device, and the first core network.

[0172] Figure 4 The method shown may include steps S410 and S420. The following description uses a terminal device as an example to illustrate the method provided in the embodiments of this application.

[0173] S410, the terminal device receives first configuration information. The first configuration information can be used to instruct the first access network device to have a first communication link to access the first core network.

[0174] In some embodiments, the first core network may include registration parameters for the terminal device. For example, the first core network may be a core network that manages and / or maintains the terminal device's registration parameters, or the terminal device may have registered in the first core network. For instance, the first core network may be the core network in the terminal device's home network. Alternatively, the first core network may be the core network in a roaming network, but the terminal device may have registered in that roaming network.

[0175] In some embodiments, the first access network device is associated with a second core network. For example, the first access network device may be used to access the second core network but cannot access other core networks. For example, the first access network device may be used to access multiple core networks, with the second core network being the default core network accessed by the first access network device, or in other words, the second core network being the preferred core network accessed by the first access network device.

[0176] In some embodiments, the second access network device is associated with the first core network. For example, the second access network device may be used to access the first core network but cannot access other core networks. For example, the second access network device may be used to access multiple core networks, with the first core network being the default core network accessed by the second access network device, or in other words, the first core network being the preferred core network accessed by the second access network device.

[0177] The second core network differs from the first core network.

[0178] For example, the registration parameters of the terminal devices managed and / or maintained by the second core network and the first core network are not exactly the same. For instance, the second core network and the first core network can be used to manage and / or maintain different registration parameters of terminal devices.

[0179] Taking the first core network used to manage and / or maintain the registration parameters of the first terminal device, and the second core network used to manage and / or maintain the registration parameters of the second terminal device as examples, the first core network and the second core network are introduced.

[0180] For example, the first terminal device and the second terminal device may be provided by different operators. Alternatively, the first terminal device and the second terminal device may be provided by the same operator, but they may be located in different regions.

[0181] It should be understood that in the future, the same operator may deploy more than one core network in the same home region. In this case, if multiple core networks in the same home region are used to manage and / or maintain the registration parameters of different terminal devices, then the first core network and the second core network can also be core networks in the same home region.

[0182] For example, the second core network and the first core network belong to different PLMNs, or in other words, the second core network and the first core network are core networks in different PLMNs.

[0183] For example, the second core network and the first core network are core networks of different operators.

[0184] For example, the second core network and the first core network are core networks of the same operator, but the second core network and the first core network can provide network services for different geographical areas.

[0185] As mentioned earlier, the first access network device accesses the second core network by default. Therefore, the first configuration information can be used to indicate that the first access network device has a first communication link to access the first core network. This can be understood as the first configuration information being used to indicate that the first access network device has a path to access a non-default core network (the core network registered by the terminal device), i.e., a first communication link.

[0186] S420: Terminal devices access the first core network through the first access network device.

[0187] In some embodiments, the terminal device may send first information to the first access network device, the first information being used to indicate the first core network and / or the first communication link; the terminal device may also receive information from the first core network. That is, the terminal device can request a revisit to the first core network through the first information. Since the first access network device can access both the first and second core networks, the first information helps the first access network device determine the core network the terminal device wants to access.

[0188] In this embodiment of the application, the terminal device is notified by the first configuration information that other networks have a return link to the original registration core network, such as the first communication link. This provides the conditions for the terminal device to return to the original registration core network when it is stationed within the coverage area of ​​other networks. This helps to reduce the frequency of the terminal device performing the registration process, thereby helping to reduce the communication latency caused by registration.

[0189] The first configuration information may include various types of information. The following is a description of the information that the first configuration information may include.

[0190] In some embodiments, the first configuration information may include third indication information, which indicates the existence of a first communication link, i.e., a communication link for reconnecting to the first core network from another network. In this way, when the network topology changes, such as when the network where the terminal device is hosted changes, the terminal device can first determine whether the hosted network has a communication link for reconnecting to the first core network. If a first communication link exists, the terminal device can reconnect to the first core network through the first communication link, thereby avoiding re-registration in the hosted network, helping to reduce the frequency of registration, and thus helping to reduce the communication latency caused by registration.

[0191] In some embodiments, the first configuration information may include indication information for a first access network device. For example, the indication information for the first access network device may include: identification information of the first access network device; identification information of the network to which the first access network device belongs, such as the identification information of the PLMN to which the first access network device belongs; or identification information of the cell to which the first access network device provides services. In this way, the terminal device can determine the access network device with the capability to revisit the first core network based on the first configuration information. When the area where the terminal device is located is covered by multiple access network devices, the terminal device can preferentially access the access network device with the capability to revisit the first core network, which helps reduce the registration frequency and thus helps reduce the communication latency caused by registration.

[0192] In some embodiments, the first configuration information may include indication information of the first communication link.

[0193] For example, the indication information of the first communication link can be used to indicate the target core network of the first communication link, i.e., the first core network, which helps to reduce indication overhead. Since the first core network includes the registration information of the terminal device, the terminal device can avoid re-registration when revisiting the first core network. Therefore, the terminal device can determine the communication link to revisit its registered core network based on the target core network of the communication link.

[0194] For example, the indication information of the first communication link can be used to indicate the path information of the first communication link. For instance, the indication information of the first communication link can be used to indicate one or more communication nodes included in the first communication link, such as the indication information of the one or more communication nodes may include the identification information of the one or more communication nodes.

[0195] When multiple communication links exist to access the first core network, the path information of the first communication link can be used to assist the terminal device in selecting the appropriate link, thereby improving system performance. For example, the path information of the first communication link can determine its communication quality, latency, and other information. As an example, the terminal device can choose a communication link with low latency to access the first core network, helping to reduce latency. As another example, the terminal device can choose a communication link with good communication quality to access the first core network, helping to improve communication reliability.

[0196] For example, terminal devices can select the appropriate communication link based on the needs of their service data. If the service data between the terminal device and the first core network has high reliability requirements, a communication link with good communication quality can be selected to reconnect to the first core network. If the service data between the terminal device and the first core network has high latency requirements, a communication link with low latency can be selected to reconnect to the first core network.

[0197] For example, the configuration information and identifier of the first communication link can be pre-configured, and the identifier of the first communication link can be dynamically indicated through the first configuration information to save indication overhead. In this case, the terminal device can determine the configuration information of the first communication link based on the correspondence between the identifier of the first communication link and the configuration information of the first communication link. For example, the configuration information of the first communication link may include the target core network information of the first communication link. Alternatively, the configuration information of the first communication link may include the path information of the first communication link, such as one or more communication nodes included in the first communication link, and / or the port number, IP address, etc. of the communication ports involved in the first communication link.

[0198] In some embodiments, the first configuration information may include priority information for a first communication link. This priority information may be related to, for example, the communication quality (e.g., quality of service (QoS)) and / or communication latency of the communication link. As an example, the priority of the first communication link is proportional to the communication quality of the communication link. As yet another example, the priority of the first communication link is proportional to the communication latency of the communication link.

[0199] For example, the priority information of the first communication link can be indicated by the values ​​of several bits. For instance, the larger the value of the several bits, the higher the priority, or the smaller the value of the several bits, the higher the priority.

[0200] For example, the priority information of the first communication link may include information such as the communication quality and / or communication duration of the first communication link.

[0201] It should be noted that the first configuration information may include one or more of the above information, and this application does not limit it.

[0202] In some embodiments, S410 can be replaced by: the terminal device receiving first configuration information from the first core network.

[0203] For example, the terminal device may receive first configuration information sent by the second access network device. Before the terminal device receives the first configuration information sent by the second access network device, the second access network device may receive first configuration information sent by the first core network. The first configuration information may, for example, be carried in a registration success feedback message from the first core network. Specifically, in response to the registration request of the terminal device, the first core network configures the first configuration information for the terminal device and sends the first configuration information to the terminal device in a registration success feedback message.

[0204] For example, the terminal device can receive first configuration information sent by the first access network device, and correspondingly, the first access network device can send the first configuration information to the terminal device. The first configuration information can, for example, be carried in a system message of the first access network. Before the first access network device sends the first configuration information to the terminal device, the first access network device can receive the first configuration information sent by the first core network.

[0205] For example, the terminal device may receive part of the first configuration information from the first access network device and part of the first configuration information from the second access network device. Some examples are given below.

[0206] For example, the first configuration information received by the terminal device from the second access network device may include the third indication information mentioned above, and the first configuration information received by the terminal device from the first access network device may include indication information of the first communication link. In this case, the indication information of the first communication link may, for example, include indication information of the target core network of the first communication link and / or identification information of the first communication link. Optionally, the first configuration information received by the terminal device from the first access network device may also include priority information of the first communication link and path information of the first communication link.

[0207] Specifically, when a terminal device is stationed in an area served by the first core network, it can determine whether the first core network has a backhaul link, or in other words, whether there is a communication link between the first core network and access network devices in other networks, by receiving first configuration information from the second access network device. If a communication link for backhauling to the first core network exists, then when the terminal device leaves the area served by the first core network, or is stationed in an area served by another core network, the terminal device can first determine whether the access network device providing coverage for the terminal device's current location can backhaul to the first core network.

[0208] Taking the access network device providing coverage to the current location of the terminal device as the first access network device as an example, the terminal device can determine, based on the first configuration information obtained from the first access network device, that the first access network device has a communication link for revisiting the first core network, i.e., the first communication link. Furthermore, the terminal device can initiate a request to the first access network device to revisit the first core network based on the indication information of the first communication link.

[0209] For example, the first configuration information received by the terminal device from the second access network device may include indication information from the first access network device, and the first configuration information received by the terminal device from the first access network device may include indication information of the first communication link. Optionally, the first configuration information received by the terminal device from the first access network device may also include priority information and path information of the first communication link.

[0210] Specifically, based on the first configuration information received from the second access network device, the terminal device can determine which access network device has the capability to revisit the first core network. Therefore, when the terminal device is camped in an area covered by the first access network device, it can initiate a request to revisit the first core network instead of registering with the second core network. When the area where the terminal device is camped is covered by multiple access network devices, the terminal device can prioritize accessing the first access network device based on the first configuration information received from the second access network device, thereby helping to reduce the frequency of registration. Furthermore, based on the first configuration information from the first access network device, the terminal device can determine the indication information of the first communication link, and then initiate a request to revisit the first core network based on this indication information.

[0211] In the above scenario, the first configuration information sent by the first core network to the first access network device may be the same as the first configuration information sent by the first access network device to the terminal device, or it may include other information besides the first configuration information sent by the first access network device to the terminal device. Similarly, the first configuration information sent by the first core network to the second access network device may be the same as the first configuration information sent by the second access network device to the terminal device, or it may include other information besides the first configuration information sent by the second access network device to the terminal device.

[0212] Based on the main communication nodes included in the first communication link, the first communication link can be divided into the following two types: the first communication link includes a gateway; the first communication link includes a second access network device. The gateway and the second access network device can also be referred to as intermediate nodes or relay nodes of the first communication link.

[0213] In addition, the communication nodes included in the first communication link also include the access node (first access network device) of the first communication link and the target node of the first communication link, namely the first core network. For example, the target node of the first communication link can be a network element in the first core network, such as AMF.

[0214] In some embodiments, the communication link between the first core network and the intermediate node can be referred to as Link A, and the communication link between the first access network device and the intermediate node can be referred to as Link B. Based on this, creating the first communication link may include establishing a mapping relationship between Link A and Link B, or creating the first communication link may include creating Link A and / or Link B, and establishing a mapping relationship between Link A and Link B. When a communication link exists between the first core network and the intermediate node, Link A can reuse the existing communication link. When a communication link exists between the first access network device and the intermediate node, Link B can reuse the existing communication link.

[0215] For example, the first communication link, link A, and link B can be based on a point-to-point protocol consisting of Stream Control Transmission Protocol / Internet Protocol (SCTP / IP); Transmission Control Protocol / IP (TCP / IP); User Datagram Protocol / IP (UDP / IP); and Layer 2 (L2 / L2).

[0216] In some embodiments, an intermediate node may include a first interface for communicating with a first core network and a second interface for communicating with a first access network device. Correspondingly, the first core network may include a third interface for communicating with the intermediate node, and the first access network device may include a fourth interface for communicating with the intermediate node. Based on this, creating a first communication link may include establishing a mapping relationship between the first interface and the second interface. Optionally, before establishing the mapping relationship between the first interface and the second interface, one or more interfaces from the first interface to the fourth interface may be created. Some or all of the communication interfaces from the first interface to the fourth interface may reuse existing communication interfaces or may be newly created interfaces during the process of creating the first communication link.

[0217] For example, some or all of the interfaces among the first to fourth interfaces mentioned above may be transport network layer (TNL) interfaces.

[0218] It should be noted that the communication link between the first core network and the intermediate node may or may not include other communication nodes (communication devices); the communication link between the first access network device and the intermediate node may or may not include other communication nodes.

[0219] The following is combined Figures 5 to 7 An example of the first communication link is provided.

[0220] Figure 5 A schematic diagram illustrating the principle of the first communication link provided in an embodiment of this application. See also... Figure 5 PLMN 1 includes a first core network, PLMN 2 includes a second core network, and the first communication link may include link A and link B, and the first communication link includes a gateway. In other words, terminal devices can access the first access network device, transit through the gateway, and then access the first core network in PLMN 1.

[0221] Figure 6 for Figure 5 An example diagram of the first communication link in the system. Figure 6 This includes terminal equipment, first access network equipment, gateways, and the first core network. See also... Figure 6 The first communication link may include link A (which may be statically configured), link B, and a gateway. The gateway is used to establish the mapping relationship between link A and link B. Additionally, the terminal device can communicate with the first core network via Non-Access Stratum (NAS) messages, and the terminal device can communicate with the first access network device via the Uu interface.

[0222] For example, the communication interface between the first access network device and the gateway, and the communication interface between the gateway and the first core network, can be a TNL interface.

[0223] In some embodiments, the first communication link can be implemented by a UPF network element. For example, data transmission through the first communication link may include data transmission via multi-hop UPF relay. During this process, the application layer transmission between the access network device and the first core network is user plane data. Specifically, a protocol data unit (PDU) session is established between the access network device and the first core network for transmitting next-generation application protocol (NGAP) messages.

[0224] Figure 7 Another example diagram of the first communication link provided in the embodiments of this application. Figure 7 The first communication link shown is the communication link mentioned above where the intermediate node is the second access network device. Figure 7 This includes terminal equipment, first access network equipment, second access network equipment, and a first core network. See also... Figure 7 The first communication link may include link A, link B, and a second access network device. The second access network device is used to establish a mapping relationship between link A and link B. For example, the return traffic of the terminal device can be transmitted to the second access network device via the Xn interface between the first and second access network devices, and then transmitted from the second access network device to the first core network.

[0225] For example, the communication interface between the first access network device and the second access network device, and the communication interface between the second access network device and the first core network, can be a TNL interface.

[0226] If the first access network device and the second access network device are deployed on a satellite, then the return traffic of the terminal device can be transmitted to the second access network device via the inter-satellite link between the first access network device and the second access network device, and then transmitted to the first core network by the second access network device.

[0227] In some embodiments, creating a first communication link may include generating configuration information for the first communication link (such as context information of a first access network device) and activating the configuration information for the first communication link (such as activating the context of the first access network device). Exemplarily, the configuration information for the first communication link is not activated immediately. That is, after generating the configuration information for the first communication link, it is not activated immediately. For example, the configuration information for the first communication link can be activated when the first communication link is used, which helps reduce system overhead. As an example, the configuration information for the first communication link can be activated upon receiving the first information mentioned above.

[0228] As mentioned above, the first communication link includes multiple communication nodes, and the configuration information of the first communication link may include configuration information associated with each of the multiple communication nodes. Specifically, each communication node may include at least the configuration information associated with it.

[0229] For example, the configuration information of the first communication link may include the configuration information of the communication interface and the configuration information of the communication interface mapping relationship. For instance, the configuration information of the first communication link in the first access network device may at least include the configuration information of the fourth interface, the configuration information of the first communication link in the first core network may at least include the configuration information of the third interface, and the configuration information of the first communication link in the intermediate node may at least include the configuration information of the first interface, the configuration information of the second interface, and the configuration information of the mapping relationship between the first interface and the second interface.

[0230] Based on this, as a possible implementation, multiple communication nodes in the first communication link can all activate the configuration information of the first communication link associated with them when they receive the first information. For example, when the first access network device receives the first information, it can activate the configuration information of the first communication link associated with it, such as the configuration information of the fourth interface; when the intermediate node receives the first information, it can activate the configuration information of the first communication link associated with it, such as the configuration information of the first interface, the configuration information of the second interface, and the configuration information of the mapping relationship between the first interface and the second interface; when the first core network receives the first information, it can activate the configuration information of the first communication link associated with it, such as the configuration information of the third interface.

[0231] As another possible implementation, upon receiving the first information, the first access network device can activate the configuration information of the first communication link associated with it and send an indication message to other nodes in the first communication link to activate the configuration information of the first communication link. In this way, intermediate nodes do not need to decode the first information, which helps reduce the processing complexity of the intermediate nodes.

[0232] In some embodiments, the first communication link can be a communication link between a first access network device and a first core network. For example, the first communication link may include a fifth interface, such as a next-generation (NG) interface, which can be used for communication between the first access network and the first core network. That is, the first access network device may include a fifth interface, the first core network may include a fifth interface, and the first core network and the first access network device can communicate directly through the fifth interface. For example, a network element of the first core network, such as an AMF network element, can initiate NG interface establishment to the first access network device, thereby creating the first communication link. Optionally, before establishing the first communication link, it can be determined whether the first access network device and the first core network have mutual access permissions.

[0233] In some embodiments, the creation of the first communication link can be initiated by the terminal device or by the first core network.

[0234] For example, the terminal device can determine whether to initiate the creation of the first communication link based on the usage scenario, such as whether the network topology of the terminal device will change frequently. For instance, when the terminal device is provided by NTN, the terminal device can initiate the creation of the first communication link, such as when performing registration in the first core network.

[0235] For example, the first core network may send second information to the communication nodes involved in the first communication link, such as a second access network device or a gateway, the second information being used to instruct the creation of the first communication link. For instance, when a terminal device initiates a registration process in the first core network, during the execution of the registration process, or after the terminal device completes registration in the first core network, the first core network may send the second information to the communication nodes involved in the first communication link.

[0236] In some embodiments, the first core network may release the first communication link, such as by deactivating the configuration information of the first communication link or deleting the configuration information of the first communication link. For example, the first core network may determine the timing of releasing the first communication link as needed, such as after the terminal device transmits data and / or signaling to the first core network through the first communication link.

[0237] For example, the first core network can release the first communication link when the second timer expires. The second timer is started or restarted when the first communication link is used to transmit data and / or signaling. In other words, if the first communication link is not used within the duration of the second timer, the first core network releases the first communication link.

[0238] For example, the first core network can determine the timing of releasing the first communication link based on fourth indication information from the first access network device or terminal device. The fourth indication information indicates whether there is still data and / or signaling to be transmitted, or in other words, it indicates whether to release the first communication link. As an example, the data and / or signaling transmitted between the terminal device and the first core network can carry the fourth indication information, which indicates whether there is still data and / or signaling to be transmitted. It should be understood that the data and / or signaling to be transmitted mentioned here refers to the data and / or signaling to be transmitted between the terminal device and the first core network.

[0239] As an example, the fourth indication information can be a 1-bit value. When the value of this bit is the first value, the first core network releases the first communication link. When the value of this bit is the second value, the first core network does not release the first communication link.

[0240] In some embodiments, the communication links accessing the first core network include a first communication link and a second communication link. If the first core network receives return traffic from the terminal device through the first communication link, the first core network may choose to release the second communication link as needed to save resources.

[0241] This application embodiment creates a communication link between the original registration core network and other networks, such as a first communication link between the first core network and the first access network device, enabling the terminal device to revisit the first core network through the first access network device. In this case, the terminal device does not need to perform a registration process in the second core network, which helps reduce the frequency of the terminal device performing the registration process, thereby helping to reduce communication latency. In addition, eliminating the need for the terminal device to perform a registration process in the second core network helps to reduce the mobility management overhead on the core network side.

[0242] As mentioned earlier, in scenarios with frequent changes in network topology, terminal devices need to frequently execute registration processes, which will introduce certain communication latency. To address this issue, embodiments of this application provide an alternative communication method. By pre-completing the registration process of the terminal device in other networks, or in other words, pre-generating the registration parameters of the terminal device in other networks, the terminal device can directly obtain the pre-generated registration parameters when accessing other networks, without waiting for the generation process of the registration parameters, thereby helping to reduce the communication latency caused by registration.

[0243] Figure 8 This is a flowchart illustrating another communication method provided in an embodiment of this application. Figure 8The method shown may involve the interaction between a terminal device, a second access network device, a first core network, and the second core network. It should be understood that the terminal device can be any of the terminal devices mentioned above, or a chip, chip system, or processor that supports the implementation of this method in the terminal device; the second access network device can be any of the access network devices mentioned above, or a chip, chip system, or processor that supports the implementation of this method in the access network device; the first core network and the second core network can be any functional entity (such as any network element) or logical unit in the core network, or a chip, chip system, or processor that supports the implementation of this method in the core network.

[0244] The method provided in the embodiments of this application will now be described from the perspective of the interaction between the terminal device, the second access network device, the first core network, and the second core network.

[0245] It should be noted that, in this embodiment, the first access network device is associated with the second core network, and the second access network device is associated with the first core network. The association between the access network devices and the core network can be referred to the above description, and will not be repeated here.

[0246] Figure 8 The method shown may include steps S810 and S820.

[0247] S810, the terminal device sends a first registration request message to the second access network device. Correspondingly, the second access network device receives the first registration request message sent by the terminal device.

[0248] In some embodiments, the second access network device sends a first registration request message to the first core network, and correspondingly, the first core network receives the first registration request message sent by the second access network device.

[0249] In some embodiments, the first registration request message may include first indication information. This first indication information can be used to indicate multiple core networks, such as a first core network and a second core network. That is, the terminal device can initiate a registration process with multiple networks. This method can be applied to initial registration, periodic registration, and mobility registration processes. Exemplarily, the first indication information can indicate the core network that needs to perform the terminal device registration process through a network identifier, such as a PLMN identifier. The first indication information can be, for example, a list of network identifiers, such as a list of PLMNs.

[0250] For example, the first indication information can be determined by the terminal device, that is, by the terminal device determining the multiple networks for which the terminal device performs registration.

[0251] The first indication information can be carried in a NAS message. In this case, the second access network device does not decode the first indication information, but instead passes it through to the first core network, such as an AMF network element. Furthermore, the first core network can forward the first registration request to the second core network, such as to an AMF network element within the second core network. For example, the first core network can forward only the information in the first registration request related to the second core network, or it can forward all the information in the first registration request to the second core network.

[0252] In some embodiments, the first indication information may be carried in a Radio Resource Control (RRC) establishment completion message. In this case, the second access network device can forward the first registration request to both the first core network (e.g., an AMF network element) and the second core network (e.g., an AMF network element) based on the first indication information. Specifically, the second access network device can select the AMF network element of the first core network and the second core network based on the first indication information, and forward the first registration request to the selected AMF network element.

[0253] In some embodiments, the second access network device may send a first registration request message to the first core network. In this case, the first core network may forward the first registration request message to the second core network. That is, the first core network forwards the first registration request message to a candidate network, such as the second core network.

[0254] In some embodiments, the second access network device may send a first registration request message to the first core network and a registration request message to the second core network. That is, the second access network device forwards the first registration request message to the candidate network, such as the second core network.

[0255] In some embodiments, the first registration request message may include second indication information and auxiliary information. For example, the second indication information may be used to indicate a first core network, and the auxiliary information may be used to determine a second core network. The first core network may be the core network where the terminal device is currently executing the registration process (or, in other words, the core network providing coverage for the area where the terminal device is currently residing, which may be referred to as the service network), while the second core network may be a core network that requires the terminal device registration process to be executed beforehand (or, in other words, another core network besides the first core network, which may be referred to as a candidate network).

[0256] In some embodiments, the first core network can determine the second core network based on auxiliary information. That is, the core network side determines the network for the terminal device to perform pre-registration, or in other words, the core network side determines the candidate network.

[0257] In some embodiments, the first core network may send a second registration request message to the second core network. For example, the second registration request message may be used to request the second core network to generate second registration parameters (or, in other words, the second registration request may be used to initiate a pre-registration process with the second core network). The second registration parameters are the registration parameters of the terminal device in the second core network.

[0258] For example, if a terminal device initiates a pre-registration process to multiple networks, or if there are multiple second core networks, the first core network can determine the timing for sending a second registration request to multiple second core networks. If the timing for sending the second registration request to multiple core networks is not exactly the same, it helps to avoid signaling congestion.

[0259] For example, based on when the terminal device might access the second core network (i.e., time t1), the timing when the first core network sends the second registration request to the second core network (i.e., time t2) can be determined. As an example, time t2 is before time t1.

[0260] In some embodiments, the auxiliary information may include one or more of the following: location information of the terminal device; a first time, where it is expected that the registration process of the terminal device will not be executed within the first time; or a first location area, where it is expected that the registration process of the terminal device will not be executed within the first location area.

[0261] For example, changes in network topology can be predicted based on the location information of terminal devices. Taking an NTN network as an example, the location information of terminal devices and the movement of satellites can be used to determine the second core network and predict when terminal devices will access the second core network.

[0262] The location information of the terminal device mentioned here can include the location information of the terminal device carried in the registration request, and can also include real-time location information reported by the terminal device in the connected state. For example, the location information of the terminal device can include the location information reported by the terminal device during cell handover. Alternatively, the location information of the terminal device can include the tracking area information reported by the idle terminal device.

[0263] For example, the location information of a terminal device may include the cell where the terminal device is located and / or the location coordinates of the terminal device, such as global positioning system (GPS) coordinates.

[0264] For example, the second core network can be determined based on the first time period. For instance, the second core network can be determined based on the changes in the network topology of the terminal devices within the first time period. A smaller first time period value means fewer networks the terminal devices need to pre-register with, so the terminal devices need to re-register after the first time period ends. A larger first time period value means more networks the terminal devices need to pre-register with, resulting in higher management overhead on the core network side. Therefore, the terminal device can determine the first time period value based on its needs.

[0265] For example, a second core network can be determined based on a first location area. For instance, the core network providing services to the first location area is the second core network.

[0266] S820: The terminal device receives a first registration parameter and a second registration parameter. The first registration parameter is the registration parameter of the terminal device in the first core network, and the second registration parameter is the registration parameter of the terminal device in the second core network.

[0267] In some embodiments, the first registration parameter and the second registration parameter are carried in a registration success feedback message from the first core network. Step S820 can be replaced by: the terminal device receiving the first registration parameter and the second registration parameter sent by the second access network device. Before step S820, the second access network device may receive the first registration parameter and the second registration parameter sent by the first core network. The second registration parameter in the first core network may be received from the second core network.

[0268] In some embodiments, the first registration parameter may be carried in a registration success feedback message from the first core network, and the second registration parameter may be carried in a registration success feedback message from the second core network.

[0269] Step S820 can be replaced by: the terminal device receiving the first registration parameter sent by the second access network device and receiving the second registration parameter sent by the first access network device. Before step S820, the second access network device can receive the first registration parameter sent by the first core network, and the first access network device can receive the second registration parameter sent by the second core network.

[0270] For example, the terminal device sends a registration request message to the first access network device, and the terminal device receives the second registration parameters sent by the first access network device.

[0271] This application embodiment pre-generates registration parameters for terminal devices in the second core network, enabling terminal devices to directly obtain the pre-generated registration parameters when accessing the second core network without waiting for the registration parameter generation process, thereby helping to reduce the communication latency caused by registration.

[0272] In some embodiments, the first core network may send some or all of the parameters from the first registration parameters to the second core network. Prior to this step, the first core network may generate the first registration parameters. Exemplarily, the second core network may generate second registration parameters based on some or all of the parameters received from the first registration parameters.

[0273] In other words, the second core network can reuse some or all of the first registration parameters during the generation of the second registration parameters, thereby omitting some steps in the registration process and helping to reduce the processing overhead of the second core network. For example, the second core network skips the authentication process of the terminal device. Optionally, the terminal device can determine whether the second core network allows skipping the authentication process based on a security policy.

[0274] As mentioned earlier, the registration parameters of a terminal device can include multiple sets of registration parameters. Therefore, determining the activation and deactivation timing of these registration parameters is a problem that needs to be solved. The activation and deactivation timing of registration parameters will be introduced below.

[0275] When a terminal device initiates the registration process, it resides in the area where the first core network provides services. Therefore, the first registration parameters can take effect immediately. In other words, the first registration parameters are activated immediately after they are generated.

[0276] In some embodiments, if the first condition is met, the second registration parameter is activated.

[0277] For example, the first condition is associated with one or more of the following: handover of access network devices, location information of terminal devices, satellite ephemeris information, and current time. Alternatively, the first condition includes one or more of the following: the terminal device establishes a connection with the first access network device; the first access network device is associated with the second core network; the terminal device is located within the coverage area of ​​the first access network device; or it is predicted that the terminal device is located within the coverage area of ​​the first access network device.

[0278] When the first condition is associated with the handover of an access network device, the first condition may include, for example, the establishment of a connection between the terminal device and the first access network device.

[0279] When the first condition is associated with the location information of the terminal device, the first condition may include, for example, the terminal device being located within the coverage area of ​​the first access network device.

[0280] When the first condition is associated with the location information of the terminal device, satellite ephemeris information, and the current time, the first condition may include, for example, predicting that the terminal device is within the coverage area of ​​the first access network device based on the location information of the terminal device, satellite ephemeris information, and the current time.

[0281] For example, the first condition may include receiving an instruction to activate the second registration parameter. The instruction to activate the second registration parameter may be sent, for example, by the first access network device or the first core network. Before the first access network device sends the instruction to activate the second registration parameter to the second core network, the first access network device may receive the instruction to activate the second registration parameter sent by the terminal device.

[0282] For example, the first condition may include the PLMN where the terminal device is camped being a PLMN belonging to the second core network. For instance, the terminal device may receive a PLMN from the access network equipment in the camped area. Specifically, the PLMN information may be carried in the tracing area identity (TAI). The fact that the PLMN where the terminal device is camped is a PLMN belonging to the second core network can be understood as the terminal device camped within the area provided by the second core network.

[0283] For example, the first condition can be associated with the priority of the second registration parameter. For instance, if the second registration parameter includes multiple sets of registration parameters, which are registration parameters of the terminal device in multiple second core networks, then if the first condition is met, a target registration parameter is determined from the second registration parameter based on the priority of the multiple sets of registration parameters; and the target registration parameter is activated. Specifically, if all the first conditions associated with the multiple sets of registration parameters are met, the terminal device can select the target registration parameter based on the priority of the multiple sets of registration parameters and activate the target registration parameter. For example, the target registration parameter is the registration parameter with the highest priority among the multiple sets of registration parameters.

[0284] As an example, registration parameters in the home network have higher priority than those in the roaming network, and / or, the size of the tracking area served by the second core network is proportional to the priority of the terminal device's registration parameters in the second core network. In other words, the larger the tracking area, the higher the priority of the registration parameters in the corresponding core network.

[0285] As another example, the registration parameters in the home network have a higher priority than the registration parameters corresponding to the largest tracking area. In other words, the registration parameters of the home network are activated first, and then the registration parameters corresponding to the network with the largest tracking area are activated.

[0286] In some embodiments, the first condition is carried in the registration success feedback message of the first core network or the registration success feedback message of the second core network.

[0287] In some embodiments, the first registration parameter can be deactivated when the first condition is met.

[0288] In some embodiments, the first registration parameter is deactivated in response to receiving an instruction to deactivate the first registration parameter. The instruction to deactivate the first registration parameter is sent by the second access network device or the second core network. Before the second access network device sends the instruction to deactivate the first registration parameter to the first core network, the second access network device may receive the instruction to deactivate the first registration parameter sent by the terminal device.

[0289] In some embodiments, if the first timer expires, the first registration parameter is deactivated. The start time of the first timer is the activation time of the first registration parameter. The duration of the first timer is the validity period of the first registration parameter.

[0290] It should be noted that "activating registration parameters" can be understood as meaning the registration parameter is valid, or that the registration parameter is being used; conversely, "deactivating registration parameters" can be understood as meaning the registration parameter is invalid, or that the registration parameter is not being used. The following explanation uses the first registration parameter as an example to illustrate the meaning of "activation" and "deactivation".

[0291] Activating the first registration parameter can be understood as: the first registration parameter is a valid registration parameter or is used as the registration parameter for the terminal device. Deactivating the first registration parameter can be understood as: the first registration parameter is an invalid registration parameter or is not used as the registration parameter for the terminal device.

[0292] It should be understood that activating registration parameters can include activation by the terminal device and activation by the network side (such as access network equipment and core network). When the terminal device activates a registration parameter, it can trigger the network side to activate the same parameter. Similarly, when the network side activates a registration parameter, it can trigger the terminal device to activate the same parameter. For example, if the first condition is met, the terminal device activates a second registration parameter, and the terminal device triggers the network side to activate the second registration parameter. As an example, the terminal device can send its identity information, such as a subscription permanent identifier (SUPI) or a globally unique temporary UE identity (GUTI), to the network side to trigger the network side to activate the second registration parameter.

[0293] In related technologies, after the terminal device completes registration, it receives a TAI list in the registration success feedback from the network. If the terminal device moves within the tracking area described in the TAI list, a mobility registration update is not required; however, if the terminal device moves outside the tracking area described in the TAI list, a mobility registration update is required.

[0294] TAI = Mobile Country Code (MCC) + Mobile Network Code (MNC) + Tracking Area Code (TAC). The MCC and MNC uniquely identify the operator, while the TAC is a unique code assigned by the operator to each tracking area.

[0295] In this embodiment, a mobility registration update strategy different from related technologies can be adopted to reduce the frequency of mobility registration updates triggered by the terminal device. The mobility registration update strategy in this embodiment is described below.

[0296] The tracking area provided by the first core network is the first tracking area (e.g., a list of first tracking areas), and the tracking area provided by the second core network is the second tracking area (e.g., a list of second tracking areas). In some embodiments, the terminal device receives indication information of a third tracking area (e.g., a list of third tracking areas) from a third access network device, and the third access network device provides coverage for the area where the terminal device is currently residing. If the first tracking area does not include the third tracking area, and the second tracking area also does not include the third tracking area, then a mobility registration process is triggered. Alternatively, if neither the first tracking area list nor the second tracking area list includes any tracking area from the third tracking area list, then a mobility registration process is triggered.

[0297] In other words, the union of the tracking area list issued by the serving network and the tracking area list issued by the candidate networks is used as the criterion for triggering the mobility registration process. If the tracking area issued by the serving network is neither in the serving network's tracking area list nor in the candidate network's tracking area list, then the mobility registration process is triggered. This method helps reduce the frequency of terminal devices triggering mobility registration updates, thereby helping to reduce system overhead.

[0298] In some embodiments, registration parameters may include a GUTI assigned by the AMF, a periodic registration timer, a tracking area list, slice parameters, or a list of functions supported by the core network. It should be understood that registration parameters may also include other parameters not shown, and this application does not limit their inclusion.

[0299] It should be noted that, in the embodiments of this application, the registration parameters and registration information can be substituted for each other.

[0300] It should be noted that registration frequency can be understood as registration frequency and / or number of registrations.

[0301] It should be noted that the method provided in this application embodiment can be applied to terrestrial network scenarios as well as NTN scenarios.

[0302] For ease of understanding, the following text will combine... Figures 9 to 11 The methods provided in the embodiments of this application will be described by way of example. It should be noted that RAN 1 described below can be the second access network device mentioned above, and RAN 2 can be the first access network device mentioned above.

[0303] Figure 9 This is a flowchart illustrating yet another communication method provided in an embodiment of this application. Figure 9 In the method shown, by pre-creating a return link (such as the first communication link mentioned above), conditions are provided for the terminal device to access the original registered core network (such as the first core network mentioned above).

[0304] It should be noted that, Figure 9 RAN 1 is associated with core network 1, and RAN 2 is associated with core network 2 (not shown in the figure). The backhaul link includes the area gateway.

[0305] Figure 9 The method shown may include at least steps 1 through 6b.

[0306] Step 1: The terminal device initiates a registration request to the core network 1 through RAN 1.

[0307] Specifically, the terminal device sends a registration request to RAN 1, and RAN 1 forwards the terminal device's registration request to 5GC.

[0308] Step 2: Core network 1 completes the registration of terminal devices, such as generating registration parameters for the terminal devices.

[0309] Step 3: Core Network 1 initiates the establishment of the return visit link.

[0310] By establishing a backhaul link, an interface is created for terminal devices on potentially accessible RAN nodes that can access the core network 1. Taking the backhaul link between RAN 2 and core network 1 as an example, creating a backhaul link can include establishing a RAN 2 context in core network 1, the area gateway, and RAN 2.

[0311] First, the area gateway can establish a TNL interface between RAN2 and core network 1, as described above. Figure 6 As shown. Specifically: 1) The area gateway establishes a transmission link A with core network 1 (this link can be statically configured); 2) The area gateway establishes a transmission link B with RAN2; 3) The transmission link can be a point-to-point protocol based on SCTP / IP, TCP / IP, UDP / IP, and L2 / L2.

[0312] Secondly, the regional gateway can establish a mapping between transmission links A and B to form a backhaul link. Optionally, backhaul traffic from a specific terminal device can be associated with this backhaul link.

[0313] As an example, the backhaul link can be implemented by a UPF. For instance, the application layer transmission between core network 1 and RAN2 can be used as user plane data and the backhaul to core network 1 can be achieved through multi-hop UPF relay.

[0314] Optionally, core network 1 can create multiple backhaul links and describe the priority information of the backhaul links to assist terminal devices in selecting backhaul links.

[0315] Step 4: The terminal device receives a registration success notification from core network 1.

[0316] For example, the registration success feedback may include the terminal device's registration parameters, whether it has a communication link to reconnect to core network 1, the access network device that can reconnect to core network 1, the identifier of the reconnection link, and the target core network of the reconnection link. Optionally, the registration success feedback message may also include the priority information of the reconnection link.

[0317] Step 5: The terminal device connects to RAN2.

[0318] For example, the terminal device accesses RAN 2 through a random access procedure.

[0319] If a terminal device wishes to revisit its original registered core network, it can indicate the identifier of the target core network, the identifier of the revisit link, and the identifier of the terminal device during the access process. RAN 2, based on this information, determines that the terminal device wishes to revisit core network 1 and can activate the transmission configuration of the revisit link generated in step 3, such as activating the RAN 2 context established in step 3 (i.e., step 6a), thus providing conditions for data transmission between the terminal device and core network 1.

[0320] Optionally, RAN2 can broadcast in system messages whether it has links to access other core networks and the paths for backhaul links. Terminal devices can determine whether RAN2 includes a communication link for backhauling to core network 1 based on the system messages from RAN2. If RAN2 includes a communication link for backhauling to core network 1, the terminal device can access core network 1 through RAN2; if RAN2 does not include a communication link for backhauling to core network 1, the terminal device can access core network 1 through other access network devices, or perform a registration process in core network 2.

[0321] Step 6b: Transmit data / signaling via the return link.

[0322] For example, after receiving backhaul traffic from a terminal device, core network 1 can instruct other alternative backhaul links to be released as needed. For instance, communication links accessing core network 1 include backhaul link 1 and backhaul link 2. If core network 1 receives backhaul traffic from a terminal device through backhaul link 1, core network 1 can instruct backhaul link 2 to be released as needed.

[0323] The previous section introduced the backhaul link with the regional gateway as the intermediate node. The following section introduces two other types of backhaul links.

[0324] For example, the communication nodes in the backhaul link may include core network 1, RAN 1, and RAN 2. That is, the backhaul link can use RAN 1 as an intermediate node, as mentioned above. Figure 7 As shown. In this case, the return traffic of the terminal device can be sent back to RAN1 via the Xn interface between RAN1 and RAN2, and then sent back to core network 1 by RAN1.

[0325] For example, the communication nodes in the backhaul link may include core network 1 and RAN 2; that is, the backhaul link may not include intermediate nodes. For instance, core network 1 may initiate NG interface establishment to RAN 2 to create the backhaul link. In this case, the networks to which core network 1 belongs and the networks to which RAN 2 belongs have mutual access permissions.

[0326] This application embodiment creates a backhaul link between core network 1 and RAN 2, allowing terminal devices to access the registration core network (core network 1) via the backhaul link without needing to access core network 2, thus avoiding triggering re-registration. This solution helps reduce the frequency of terminal devices performing the registration process, thereby reducing communication latency caused by registration. Furthermore, since terminal devices do not need to perform the registration process in the second core network, it helps reduce mobility management overhead on the core network side.

[0327] Figure 10 This is a flowchart illustrating yet another communication method provided in an embodiment of this application. Figure 10 In the method shown, by pre-triggering the registration process of the terminal device in the candidate network, the terminal device can directly obtain the registration parameters when accessing the candidate network without waiting for the generation process of the registration parameters, thereby helping to reduce the communication latency caused by registration.

[0328] It should be noted that, Figure 10 As shown, RAN 1 is associated with core network 1, and RAN 2 (not shown in the figure) is associated with core network 2. Core network 1 belongs to PLMN 1, and core network 2 belongs to PLMN 2. In other words, core network 1 and core network 2 belong to different PLMNs.

[0329] Figure 10 The method shown may include steps 1 through 5.

[0330] Step 1: The terminal device initiates a registration request.

[0331] This registration request can be used to trigger the registration process of multiple core network execution terminal devices.

[0332] For example, the registration request may include instruction information (such as the first instruction information mentioned above), which may be used to instruct multiple networks performing the terminal device registration process. For example, the instruction information may be a list of PLMNs.

[0333] Optionally, the aforementioned indication information can be carried in a NAS message. RAN 1 can forward the NAS message to the AMF in core network 1, and the AMF can forward the registration request to the AMF corresponding to other PLMNs (such as PLMN2) in the PLMN list;

[0334] Optionally, the aforementioned indication information can be carried in the RRC establishment completion message and sent to RAN 1, whereby RAN 1 selects the AMF based on the indication message. If the terminal device indicates that multi-PLMN registration is required (e.g., the registration request carries the aforementioned indication information), RAN 1 will forward the registration request to the corresponding AMF of each PLMN. This scheme is applicable when RAN 1 already has interfaces with the core networks of multiple PLMNs.

[0335] Step 2: The terminal device completes the registration process with multiple PLMNs.

[0336] During this process, the terminal device can complete two-way authentication with multiple PLMNs, the AMF registers registration information (location information, network information, etc.) with the UDM, and at the same time, the AMF further obtains the user's subscription information, policy information, etc. from the UDM.

[0337] Step 3a: The terminal device receives a registration success feedback message from core network 1.

[0338] The successful registration feedback message may include the registration parameters assigned to the terminal device by core network 1, namely the first registration parameters mentioned above.

[0339] Step 4a: The terminal device receives a registration success feedback message from core network 2.

[0340] Before performing step 4a, the terminal device may send a registration request to core network 2. At this time, the terminal device resides in the area where core network 2 provides services. In response to the registration request, core network 2 may send a registration success feedback message to the terminal device. This registration success feedback message may include the registration parameters assigned to the terminal device by core network 2, namely the second registration parameters mentioned above.

[0341] Alternatively, the registration success feedback message from core network 1 may include registration parameters assigned to the terminal device by multiple networks. In other words, steps 3a and 4a above can be replaced by steps 3b and 4b below.

[0342] Step 3b: Core network 1 receives registration parameters, such as subscription data, allocated by core network 2 to the terminal device.

[0343] Step 4b: The terminal device receives a registration success feedback message from core network 1. This registration success feedback message may include the registration parameters assigned to the terminal device by core network 1 and the registration parameters assigned to the terminal device by core network 2.

[0344] Step 5: Activate the registration parameters assigned to the terminal device by core network 2. Correspondingly, deactivate other registration parameters, such as deactivating the registration parameters assigned to the terminal device by core network 1.

[0345] For example, a terminal device can switch its registration parameters according to changes in the network topology. The activation and deactivation conditions of the registration parameters can be associated with, for example, air interface handover and / or time / location information, or the activation and deactivation conditions can include receiving indication information sent by the core network.

[0346] As an example, when an access network device switches from RAN 1 to RAN 2, the registration parameters allocated to the terminal device by core network 2 can be activated, and correspondingly, the registration parameters allocated to the terminal device by core network 1 can be deactivated.

[0347] As another example, network topology can be predicted based on time / location information. If it is predicted that the terminal device will be provided by core network 2, or that the terminal device will soon be provided by core network 2, the registration parameters allocated by core network 2 to the terminal device can be activated, and correspondingly, the registration parameters allocated by core network 1 to the terminal device can be deactivated.

[0348] From the perspective of the terminal device, activating the registration parameters allocated to the terminal device by core network 2 and deactivating the registration parameters allocated to the terminal device by core network 1 can be understood as the terminal device switching the registration parameters from those allocated by core network 1 to those allocated by core network 2.

[0349] For example, the successful registration feedback message of the service network may carry the activation conditions, deactivation conditions, or switching conditions of the registration parameters.

[0350] When activating a registration parameter, a timer associated with that parameter can be started. For example, when the timer expires, the registration parameter can be deactivated, and / or a re-registration can be triggered.

[0351] For example, when the PLMN information carried in the TAI issued by the base station where the terminal device is camped changes, the terminal device is triggered to activate the corresponding registration parameters and deactivate the old registration parameters. For instance, when the PLMN carried in the TAI issued by the base station where the terminal device is camped changes from PLMN 1 to PLMN 2, the registration parameters allocated to the terminal device by core network 2 are activated, and the registration parameters allocated to the terminal device by core network 1 are deactivated. At the same time, the terminal device can send identity information (SUPI / GUTI, etc.) to core network 2 to trigger the activation of network-side registration parameters.

[0352] For example, when activating the registration parameters assigned to the terminal device by the core network 2 and deactivating the registration parameters assigned to the terminal device by the core network 1, the terminal device or the core network 2 may send an instruction to the core network 1 to deactivate the registration parameters.

[0353] For example, the terminal device can activate registration parameters according to a preset priority, such as prioritizing the activation of registration parameters of the home network, and then selecting the registration parameters corresponding to the network with the largest tracking area.

[0354] For example, the union of the TAI lists allocated by PLMN 1 and PLMN 2 can be used as the condition for mobility registration update. That is, the terminal device will only trigger mobility registration when it camps on a certain base station and the TAI issued by that base station does not belong to any TAI in the union.

[0355] In this embodiment of the application, the terminal device can trigger multi-network registration. For example, the core network 2 can pre-allocate registration parameters for the terminal device, so that when the terminal device accesses the core network 2, it can directly obtain the pre-generated registration parameters without waiting for the registration parameter generation process, thereby helping to reduce the communication latency caused by registration.

[0356] Figure 11 This is a flowchart illustrating yet another communication method provided in an embodiment of this application. Figure 11 In the method shown, by pre-triggering the registration process of the terminal device in the candidate network, the terminal device can directly obtain the registration parameters when accessing the candidate network without waiting for the generation process of the registration parameters, thereby helping to reduce the communication latency caused by registration.

[0357] Figure 11 The method shown is the same as Figure 10 The main difference between the methods shown is: 1) Figure 10 In the method shown, the candidate network is determined by the terminal device. Figure 11 In the method shown, the candidate network is determined by the network side, such as core network 1; 2) Figure 10 In the method shown, the candidate network and the service network assign registration parameters to the terminal device independently; Figure 11 In the method shown, the registration parameters allocated to the terminal device by the serving network can be reused during the process of the candidate network allocating registration parameters to the terminal device.

[0358] It should be noted that, Figure 11 As shown, RAN 1 is associated with core network 1, and RAN 2 (not shown in the figure) is associated with core network 2. Core network 1 belongs to PLMN 1, and core network 2 belongs to PLMN 2. In other words, core network 1 and core network 2 belong to different PLMNs.

[0359] Figure 11 The method shown may include steps 1 through 6.

[0360] Step 1: The terminal device initiates a registration request.

[0361] The registration request may include the PLMN identifier corresponding to core network 1 (i.e., the second indication information mentioned above) and auxiliary information.

[0362] The auxiliary information may include the expected duration of the registration-free period and a description of the geographical scope of the registration-free area.

[0363] For example, network topology prediction results can be obtained based on information such as time, location information of terminal devices, and ephemeris information.

[0364] Step 2: The terminal device completes the registration process with the core network 1.

[0365] Step 3: Core Network 1 identifies the PLMNs that need to be pre-registered.

[0366] In core network 1, when the AMF in core network 1 receives the registration request in step 1, it can determine the PLMN (list) that needs to be pre-registered based on auxiliary information and the prediction results of network topology, such as the PLMN corresponding to core network 2.

[0367] For example, after identifying the PLMN that needs pre-registration, the serving network can send a registration request to the PLMN to trigger pre-registration. For instance, after core network 1 determines that terminal devices need to be pre-registered with core network 2, it can initiate a registration request to core network 2. As an example, core network 1 can determine the timing of initiating the registration request to core network 2 to avoid registration signaling congestion.

[0368] Optionally, the timing for core network 1 to initiate a registration request to core network 2 can be determined based on the real-time location information reported by the connected terminal device. For example, if the location information of the terminal device predicts that the terminal device will soon be stationed in the area where core network 2 provides services, then core network 1 will initiate a registration request to core network 2.

[0369] It should be noted that the execution order of steps 2 and 3 above can be interchanged, and this application embodiment does not limit this.

[0370] Step 4: Core Network 1 and Core Network 2 exchange registration parameters.

[0371] The registration parameters exchanged between core network 1 and core network 2 may include core network 1 sending registration parameters assigned by core network 1 to the terminal device to core network 2, and core network 1 receiving registration parameters assigned by core network 2 to the terminal device.

[0372] For example, based on the registration parameters configured for the terminal device by the core network 1, the core network 2 can skip the authentication process of PLMN 2 when allocating registration parameters for the terminal device.

[0373] Step 5: The terminal device receives a registration success feedback message from core network 1.

[0374] The successful registration feedback message may include registration parameters assigned to the terminal device by core network 1 (i.e., the first registration parameters mentioned above), or registration parameters assigned to the terminal device by core network 2 (i.e., the second registration parameters mentioned above). These registration parameters may include, for example, the GUTI assigned by AMF, a periodic registration timer, a tracking area list, slice parameters, and a list of functions supported by the core network.

[0375] Step 6: Activate the registration parameters assigned to the terminal device by core network 2. Correspondingly, deactivate other registration parameters, such as deactivating the registration parameters assigned to the terminal device by core network 1.

[0376] For the conditions of activating, deactivating, and updating registration parameters, please refer to [link / reference]. Figure 10 The relevant descriptions of the methods shown will not be repeated here.

[0377] The method embodiments provided in this application have been described above. The apparatus embodiments provided in this application will be described below. It should be understood that the description of the apparatus embodiments corresponds to the description of the method embodiments. Therefore, any content not described in detail can be referred to the method embodiments above. For the sake of brevity, it will not be repeated here.

[0378] Figure 12 This is a schematic block diagram of a communication device provided in an embodiment of this application. Figure 12 As shown, the communication device 1200 may include a transceiver unit 1210 and / or a processing unit 1220. The transceiver unit 1210 can implement corresponding communication functions, and the processing unit 1220 is used for data processing. The transceiver unit 1210 may also be referred to as a communication interface or communication unit. Optionally, the device 1200 may further include a storage unit, which can be used to store instructions and / or data. The processing unit 1220 can read the instructions and / or data from the storage unit to enable the device to implement the aforementioned method embodiments.

[0379] In one possible design, the device 1200 can be the terminal device in the above method embodiments. For example, the terminal device can be a terminal equipment, a module or component with terminal equipment functions, or a communication chip that can be applied in a terminal equipment, such as a processor, circuit, chip, or chip system.

[0380] Specifically, the transceiver unit 1210 can be used to receive first configuration information, which indicates that the first access network device has a first communication link to access the first core network. The first core network includes the registration parameters of the terminal device. The first access network device is associated with a second core network, and the first core network and the second core network are different. The transceiver unit 1210 can be used to access the first core network through the first access network device.

[0381] In some embodiments, the first communication link includes a gateway or a second access network device, the second access network device being associated with the first core network.

[0382] In some embodiments, the terminal device accesses the first core network through the first access network device, including: the terminal device sending first information to the first access network device, the first information being used to indicate the first core network and / or the first communication link; and the terminal device receiving information from the first core network.

[0383] In some embodiments, the first configuration information is carried in a registration success feedback message from the first core network, or the first configuration information is carried in a system message from the first access network device.

[0384] In one possible design, the device 1200 may be a first access network device in the above method embodiments, or it may be a chip, processor, or chip system that implements the functions of the first access network device. The first access network device may be, for example, a 4G base station, a 5G base station, or a base station in a future communication system.

[0385] Specifically, the transceiver unit 1210 can be used to receive first configuration information, which indicates that the first access network device has a first communication link to access the first core network. The first core network includes registration parameters of the terminal device. The first access network device is associated with a second core network. The first core network and the second core network are different. The first configuration information is sent to the terminal device.

[0386] In some embodiments, first information is received from the terminal device, the first information being used to indicate the first core network and / or the first communication link; and configuration information for activating the first communication link is received.

[0387] In one possible design, the device 1200 can be the first core network in the above method embodiments, or it can be a chip, processor, or chip system that implements the functions of the first core network. Optionally, the device can be a network element in the first core network.

[0388] Specifically, the transceiver unit 1210 can be used to send first configuration information, which is used to indicate that the first access network device has a first communication link to access the first core network. The first core network includes the registration parameters of the terminal device. The first access network device is associated with a second core network, and the first core network and the second core network are different.

[0389] In some embodiments, the first communication link includes a gateway or a second access network device, the second access network device being associated with the first core network.

[0390] In some embodiments, before sending the first configuration information, the transceiver unit 1210 may be used to: send second information to the gateway or the second access network device, the second information being used to indicate the establishment of the first communication link.

[0391] In some embodiments, the first configuration information includes one or more of the following: indication information of the first access network device; indication information of the first communication link; or priority information of the first communication link.

[0392] In one possible design, the device 1200 can be a second access network device in the above method embodiments, or it can be a chip, processor, or chip system that implements the functions of a second access network device. The second access network device can be, for example, a 4G base station, a 5G base station, or a base station in a future communication system.

[0393] Specifically, the transceiver unit 1210 can be used to receive second information, which instructs the establishment of a first communication link. This first communication link is used for a first access network device to access a first core network. The first core network includes registration parameters for the terminal device. The first access network device is associated with a second core network, and the first and second core networks are different. The processing unit 1220 can be used to establish a mapping relationship between a first interface and a second interface. The first interface is used to communicate with the first core network, and the second interface is used to communicate with the first access network device.

[0394] In one possible design, the device 1200 may be the gateway in the above method embodiments, or it may be a chip, processor, or chip system that implements gateway functionality.

[0395] Specifically, the transceiver unit 1210 can be used to receive second information, which instructs the establishment of a first communication link. This first communication link is used for a first access network device to access a first core network. The first core network includes registration parameters for the terminal device. The first access network device is associated with a second core network, and the first and second core networks are different. The processing unit 1220 can be used to establish a mapping relationship between a first interface and a second interface. The first interface is used to communicate with the first core network, and the second interface is used to communicate with the first access network device.

[0396] In one possible design, the device 1200 can be the terminal device in the above method embodiments. For example, the terminal device can be a terminal equipment, a module or component with terminal equipment functions, or a communication chip that can be applied in a terminal equipment, such as a processor, circuit, chip, or chip system.

[0397] Specifically, the transceiver unit 1210 can be used to send a first registration request message to a second access network device, the second access network device being associated with a first core network. The first registration request message includes first indication information, which is used to indicate the first core network and the second core network. Alternatively, the first registration request message includes second indication information and auxiliary information, whereby the second indication information indicates the first core network and the auxiliary information is used to determine the second core network. It can also receive first registration parameters and second registration parameters, where the first registration parameters are the registration parameters of the terminal device in the first core network, and the second registration parameters are the registration parameters of the terminal device in the second core network.

[0398] In some embodiments, the auxiliary information includes one or more of the following: location information of the terminal device; a first time period, where it is desired not to execute the registration process of the terminal device during the first time period; or a first location area, where it is desired not to execute the registration process of the terminal device within the first location area.

[0399] In some embodiments, the first indication information is carried in a Non-Access Stratum (NAS) message, or the first indication information is carried in a Radio Resource Control (RRC) establishment completion message.

[0400] In some embodiments, the first registration parameter is carried in a registration success feedback message from the first core network, the second registration parameter is carried in a registration success feedback message from the first core network, or the second registration parameter is carried in a registration success feedback message from the second core network.

[0401] In some embodiments, the processing unit 1220 may be configured to: activate the second registration parameter if a first condition is met, wherein the first condition includes one or more of the following: the terminal device establishes a connection with the first access network device, the first access network device is associated with the second core network; the terminal device is located within the coverage area of ​​the first access network device; it is predicted that the terminal device is located within the coverage area of ​​the first access network device; an instruction to activate the second registration parameter is received; or the public land mobile network (PLMN) to which the terminal device is camped is the PLMN to which the second core network belongs.

[0402] In some embodiments, the second registration parameters include multiple sets of registration parameters, which are the registration parameters of the terminal device in multiple second core networks. The step of activating the second registration parameters if the first condition is met includes: if the first condition is met, determining a target registration parameter among the second registration parameters based on the priority of the multiple sets of registration parameters; and activating the target registration parameter.

[0403] In some embodiments, the registration parameters in the home network have a higher priority than the registration parameters in the roaming network, and / or the size of the tracking area provided by the second core network is proportional to the priority of the terminal device's registration parameters in the second core network.

[0404] In some embodiments, the first condition is carried in the registration success feedback message of the first core network or the registration success feedback message of the second core network.

[0405] In some embodiments, the tracking area provided by the first core network is a first tracking area, and the tracking area provided by the second core network is a second tracking area. The transceiver unit 1210 can be used to: receive indication information of a third tracking area from a third access network device, wherein the third access network device provides coverage for the area where the terminal device is currently residing. The processing unit 1220 can be used to: trigger a mobility registration process if the first tracking area does not include the third tracking area, and the second tracking area also does not include the third tracking area.

[0406] In one possible design, the device 1200 can be a second access network device in the above method embodiments, or it can be a chip, processor, or chip system that implements the functions of a second access network device. The second access network device can be, for example, a 4G base station, a 5G base station, or a base station in a future communication system.

[0407] Specifically, the transceiver unit 1210 can be used to receive a first registration request message from a terminal device, the first registration request message including first indication information, the first indication information being used to instruct a first core network and a second core network; send the first registration request message to the first core network; or send the first registration request message to the first core network and send the first registration request message to the second core network.

[0408] In one possible design, the device 1200 can be the first core network in the above method embodiments, or it can be a chip, processor, or chip system that implements the functions of the first core network. Optionally, the device can be a network element in the first core network.

[0409] Specifically, the transceiver unit 1210 can be used to receive a first registration request message, the first registration request message including first indication information, the first indication information being used to indicate the first core network and the second core network; or, the first registration request message including second indication information and auxiliary information, the second indication information being used to indicate the first core network and the auxiliary information being used to determine the second core network; and send a registration success feedback message, the registration success feedback message including a first registration parameter, or the registration success feedback message including the first registration parameter and the second registration parameter, the first registration parameter being the registration parameter of the terminal device in the first core network and the second registration parameter being the registration parameter of the terminal device in the second core network.

[0410] In some embodiments, processing unit 1220 may be used to: determine the second core network based on the auxiliary information. Transceiver unit 1210 may be used to: send a second registration request message to the second core network, the second registration request message being used to request the second registration parameters.

[0411] In some embodiments, the auxiliary information includes one or more of the following: location information of the terminal device; a first time period, where it is desired not to execute the registration process of the terminal device during the first time period; or a first location area, where it is desired not to execute the registration process of the terminal device within the first location area.

[0412] In some embodiments, processing unit 1220 may be used to generate first registration parameters. Transceiver unit 1210 may be used to send some or all of the parameters in the first registration parameters to the second core network.

[0413] In some embodiments, the processing unit 1220 may be used to: deactivate the first registration parameter in response to receiving an indication message to deactivate the first registration parameter, or when a first timer expires, wherein the start time of the first timer is the activation time of the first registration parameter.

[0414] In one possible design, the device 1200 can be a second core network in the above method embodiments, or it can be a chip, processor, or chip system that implements the functions of the second core network. Optionally, the device can be a network element in the second core network.

[0415] Specifically, the transceiver unit 1210 can be used to receive a second registration request message from a second access network device or a first core network, the second registration request message being used to request second registration parameters of the terminal device in the second core network, the second access network device being associated with the first core network; and to send the second registration parameters.

[0416] In some embodiments, before sending the second registration parameters, the transceiver unit 1210 may be configured to: receive some or all of the parameters in the first registration parameters, wherein the first registration parameters are the registration parameters of the terminal device in the first core network. The processing unit 1220 may be configured to: generate the second registration parameters based on the partial or all of the parameters.

[0417] In some embodiments, the processing unit 1220 may be configured to: activate the second registration parameter if a first condition is met, wherein the first condition includes one or more of the following: the terminal device establishes a connection with the first access network device, the first access network device is associated with the second core network; the terminal device is located within the coverage area of ​​the first access network device; it is predicted that the terminal device is located within the coverage area of ​​the first access network device; an instruction to activate the second registration parameter is received; or the public land mobile network (PLMN) to which the terminal device is camped is the PLMN to which the second core network belongs.

[0418] It should be understood that the "unit" in device 1200 can be implemented in hardware, software, or by hardware executing corresponding software. For example, the "unit" can refer to an application-specific integrated circuit (ASIC), electronic circuitry, a processor (e.g., a shared processor, a proprietary processor, or a group processor, etc.) and memory for executing one or more software or firmware programs, combined logic circuitry, and / or other suitable components supporting the described functions. As another example, transceiver unit 1210 can be replaced by transceiver circuitry (e.g., may include receiving and transmitting circuitry), and processing unit 1220 can be replaced by a processor or processing circuitry.

[0419] Figure 13 A schematic block diagram of another communication device provided in an embodiment of this application is shown. This communication device 1300 may be a terminal device, access network device, core network device, gateway, etc., or it may be a chip, chip system, or processor implementing the above methods in a terminal device, access network device, core network device, or gateway. This device can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0420] The communication device 1300 may include one or more processors 1310, which may also be referred to as processing units, and can implement certain control functions. The processor 1310 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device, execute software programs, and process data from the software programs.

[0421] In an alternative design, the processor 1310 may also store instructions and / or data that can be executed by the processor 1310 to cause the communication device 1300 to perform the methods described in the above method embodiments.

[0422] In another alternative design, the communication device 1300 may include a communication interface 1320 for implementing receiving and transmitting functions. For example, the communication interface 1320 may be a transceiver circuit, interface, interface circuit, or transceiver. The transceiver circuit, interface, interface circuit, or transceiver for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, interface circuit, or transceiver may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0423] Optionally, the communication device 1300 may include one or more memories 1330, which may store instructions that can be executed on the processor 1310, causing the communication device 1300 to perform the methods described in the above method embodiments. Optionally, the memories 1330 may also store data. Optionally, the processor 1310 may also store instructions and / or data. The processor 1310 and the memories 1330 may be provided separately or integrated together.

[0424] It should be understood that, in one possible design, the steps in the method embodiments provided in this application can be implemented by integrated logic circuits in the processor's hardware or by instructions in software form. The steps of the method disclosed in the embodiments of this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are not provided here.

[0425] It should be noted that the processor in the embodiments of this application can be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiments can be completed by the integrated logic circuitry in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied as being executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above methods.

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

[0427] This application also provides a computer program product, which includes computer program code. When the computer program code is run on a computer, it causes the computer to execute the various steps or processes performed by the terminal device / access network device / core network device / gateway in any of the above method embodiments.

[0428] This application also provides a computer-readable storage medium storing program code that, when run on a computer, causes the computer to execute the various steps or processes performed by the terminal device / access network device / core network device / gateway in any of the above method embodiments.

[0429] This application also provides a communication device, including a processor and an interface, the interface being used to send and / or receive signals, causing the processor to execute the various steps or processes performed by the terminal device / access network device / core network device / gateway in any of the above method embodiments.

[0430] The above-described device and method embodiments are completely corresponding, with corresponding modules or units performing corresponding steps. For example, a communication unit or communication interface performs the receiving or sending steps in the method embodiment, while other steps besides sending and receiving can be performed by a processing unit or processor.

[0431] In the embodiments of this application, the terms and English abbreviations are exemplary examples given for ease of description and should not be construed as limiting the application in any way. The embodiments of this application do not preclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.

[0432] As used in this specification, the terms "component," "module," "system," etc., are used to refer to computer-related entities, hardware, firmware, combinations of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, and / or a computer. As illustrated, applications running on computing devices and computing devices can both be components. One or more components may reside in a process and / or an execution thread, and components may be located on a single computer and / or distributed among two or more computers. Furthermore, these components can be executed from various computer-readable storage media on which various data structures are stored. Components can communicate, for example, via local and / or remote processes based on signals having one or more data packets (e.g., data from two components interacting with another component between a local system, a distributed system, and / or a network, such as the Internet interacting with other systems via signals).

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

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

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

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

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

[0438] In the above embodiments, the functions of each functional unit can be implemented entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions (programs). When the computer program instructions (programs) are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks, SSDs), etc.

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

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

Claims

1. A communication method, characterized in that, include: The terminal device receives first configuration information, which is used to indicate that the first access network device has a first communication link to access the first core network. The first core network includes the registration parameters of the terminal device. The first access network device is associated with a second core network. The first core network and the second core network are different. The terminal device accesses the first core network through the first access network device.

2. The method according to claim 1, characterized in that, The first communication link includes a gateway or a second access network device, and the second access network device is associated with the first core network.

3. The method according to claim 1 or 2, characterized in that, The terminal device accesses the first core network through the first access network device, including: The terminal device sends first information to the first access network device, the first information being used to indicate the first core network and / or the first communication link; The terminal device receives information from the first core network.

4. The method according to any one of claims 1-3, characterized in that, The first configuration information is carried in a registration success feedback message from the first core network, or the first configuration information is carried in a system message from the first access network device.

5. A communication method, characterized in that, include: Send first configuration information, which is used to indicate that the first access network device has a first communication link to access the first core network. The first core network includes the registration parameters of the terminal device. The first access network device is associated with a second core network. The first core network and the second core network are different.

6. The method according to claim 5, characterized in that, The first communication link includes a gateway or a second access network device, and the second access network device is associated with the first core network.

7. The method according to claim 6, characterized in that, Before sending the first configuration information, the method further includes: Send a second message to the gateway or the second access network device, the second message being used to instruct the establishment of the first communication link.

8. The method according to any one of claims 5-7, characterized in that, The first configuration information includes one or more of the following: Indication information of the first access network device; The indication information of the first communication link; or Priority information of the first communication link.

9. A communication method, characterized in that, include: Receive second information, the second information is used to instruct the establishment of a first communication link, the first communication link is used for a first access network device to access a first core network, the first core network includes the registration parameters of the terminal device, the first access network device is associated with a second core network, and the first core network and the second core network are different; A mapping relationship is established between a first interface and a second interface, wherein the first interface is used to communicate with the first core network and the second interface is used to communicate with the first access network device.

10. A communication method, characterized in that, include: The terminal device sends a first registration request message to a second access network device, which is associated with a first core network. The first registration request message includes first indication information, which is used to indicate the first core network and the second core network. Alternatively, the first registration request message includes second indication information and auxiliary information, whereby the second indication information is used to indicate the first core network and the auxiliary information is used to determine the second core network. The terminal device receives a first registration parameter and a second registration parameter, wherein the first registration parameter is the registration parameter of the terminal device in the first core network, and the second registration parameter is the registration parameter of the terminal device in the second core network.

11. The method according to claim 10, characterized in that, The auxiliary information includes one or more of the following: The location information of the terminal device; Ideally, the registration process for the terminal device should not be executed within the first time period. or In the first location area, it is expected that the registration process of the terminal device will not be executed within the first location area.

12. The method according to claim 10, characterized in that, The first indication information is carried in a Non-Access Stratum (NAS) message, or the first indication information is carried in a Radio Resource Control (RRC) establishment completion message.

13. The method according to any one of claims 10-12, characterized in that, The first registration parameter is carried in the registration success feedback message from the first core network, and the second registration parameter is carried in the registration success feedback message from the first core network, or the second registration parameter is carried in the registration success feedback message from the second core network.

14. The method according to any one of claims 10-13, characterized in that, The method further includes: If the first condition is met, the second registration parameter is activated, wherein the first condition includes one or more of the following: The terminal device establishes a connection with the first access network device, and the first access network device is associated with the second core network. The terminal device is located within the coverage area of ​​the first access network device; It is predicted that the terminal device is located within the coverage area of ​​the first access network device; Received an instruction to activate the second registration parameter; or The public land mobile network (PLMN) on which the terminal device resides is the PLMN to which the second core network belongs.

15. The method according to claim 14, characterized in that, The second registration parameters include multiple sets of registration parameters, which are the registration parameters of the terminal device in multiple second core networks. The step of activating the second registration parameter if the first condition is met includes: If the first condition is met, then the target registration parameter in the second registration parameter is determined based on the priority of the multiple sets of registration parameters; Activate the target registration parameters.

16. The method according to claim 15, characterized in that, The registration parameters in the home network have a higher priority than the registration parameters in the roaming network, and / or the size of the tracking area provided by the second core network is proportional to the priority of the terminal device's registration parameters in the second core network.

17. The method according to any one of claims 14-16, characterized in that, The first condition is contained in the registration success feedback message of the first core network or the registration success feedback message of the second core network.

18. The method according to any one of claims 10-17, characterized in that, The tracking area provided by the first core network is the first tracking area, and the tracking area provided by the second core network is the second tracking area. The method further includes: Receive indication information from a third tracking zone from a third access network device, the third access network device providing coverage for the area where the terminal device is currently residing; If the first tracking area does not include the third tracking area, and the second tracking area also does not include the third tracking area, then the mobility registration process is triggered.

19. A communication method, characterized in that, include: Receive a first registration request message, the first registration request message including first indication information, the first indication information being used to indicate a first core network and a second core network; or, the first registration request message including second indication information and auxiliary information, the second indication information being used to indicate the first core network, the auxiliary information being used to determine the second core network; Send a registration success feedback message, which includes a first registration parameter, or the registration success feedback message includes the first registration parameter and a second registration parameter, wherein the first registration parameter is the registration parameter of the terminal device in the first core network, and the second registration parameter is the registration parameter of the terminal device in the second core network.

20. The method according to claim 19, characterized in that, The method further includes: The second core network is determined based on the auxiliary information; A second registration request message is sent to the second core network, the second registration request message being used to request the second registration parameters.

21. The method according to claim 19 or 20, characterized in that, The auxiliary information includes one or more of the following: The location information of the terminal device; Ideally, the registration process for the terminal device should not be executed within the first time period. or In the first location area, it is expected that the registration process of the terminal device will not be executed within the first location area.

22. The method according to any one of claims 19-21, characterized in that, The method further includes: Generate the first registration parameters; Send some or all of the parameters from the first registration parameters to the second core network.

23. The method according to any one of claims 19-22, characterized in that, The method further includes: In response to receiving an instruction to deactivate the first registration parameter, or when the first timer expires, the first registration parameter is deactivated, wherein the start time of the first timer is the activation time of the first registration parameter.

24. A communication method, characterized in that, include: Receive a second registration request message from a second access network device or a first core network. The second registration request message is used to request a second registration parameter for the terminal device in the second core network. The second access network device is associated with the first core network. Send the second registration parameter.

25. The method according to claim 24, characterized in that, Before sending the second registration parameter, the method further includes: Receive some or all of the parameters in the first registration parameters, where the first registration parameters are the registration parameters of the terminal device in the first core network; The second registration parameters are generated based on some or all of the parameters.

26. The method according to claim 24 or 25, characterized in that, The method further includes: If the first condition is met, the second registration parameter is activated, wherein the first condition includes one or more of the following: The terminal device establishes a connection with the first access network device, and the first access network device is associated with the second core network. The terminal device is located within the coverage area of ​​the first access network device; It is predicted that the terminal device is located within the coverage area of ​​the first access network device; Received an instruction to activate the second registration parameter; or The public land mobile network (PLMN) on which the terminal device resides is the PLMN to which the second core network belongs.

27. A communication device, characterized in that, It includes units for performing the steps of the method as described in any one of claims 1-4, or units for performing the steps of the method as described in any one of claims 10-18.

28. A communication device, characterized in that, It includes units for performing the steps of the method as described in any one of claims 5-8, or units for performing the steps of the method as described in any one of claims 19-23.

29. A communication device, characterized in that, It includes units for performing the various steps of the method as described in claim 9.

30. A communication device, characterized in that, Includes units for performing the various steps of the method as described in any one of claims 24-26.

31. A communication device, characterized in that, The device includes a processor coupled to a memory for storing programs or instructions that, when executed by the processor, cause the device to perform the method as claimed in any one of claims 1-4, or the method as claimed in any one of claims 10-18.

32. A communication device, characterized in that, The device includes a processor coupled to a memory for storing programs or instructions that, when executed by the processor, cause the device to perform the method as claimed in any one of claims 5-8, or the method as claimed in any one of claims 19-23.

33. A communication device, characterized in that, The device includes a processor coupled to a memory for storing programs or instructions that, when executed by the processor, cause the device to perform the method as described in claim 9.

34. A communication device, characterized in that, The device includes a processor coupled to a memory for storing programs or instructions that, when executed by the processor, cause the device to perform the method as described in any one of claims 24-26.

35. A readable storage medium having a computer program or instructions stored thereon, characterized in that, When the computer program or instructions are executed, the computer performs the method as described in any one of claims 1-26.

36. A computer program product, characterized in that, It includes computer program instructions that cause the computer to perform the method as described in any one of claims 1-26.