Communication method, terminal, and network-side device

Abstract

The present application relates to the technical field of communications, and discloses a communication method, a terminal, and a network-side device. The method in the embodiments of the present application comprises: a terminal acquiring a first GUTI corresponding to a first network and a second GUTI corresponding to a second network that are allocated by a first core network device, the first network being a successor network or a next generation network of the second network; when entering a connected state by means of the first network, the terminal sending a first identifier to an access network device corresponding to the first network, the first identifier being configured for identifying a core network device corresponding to the first network, and the first identifier being determined according to the first GUTI; or, when entering a connected state by means of the second network, the terminal sending a second identifier to an access network device corresponding to the second network, the second identifier being configured for identifying a core network device corresponding to the second network, and the second identifier being determined according to the second GUTI.

Description

Communication methods, terminals and network-side equipment

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 202411791874.3, filed on December 6, 2024, entitled "Communication Method, Terminal and Network Side Device", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application belongs to the field of communication technology, specifically relating to a communication method, terminal, and network-side equipment. Background Technology

[0004] In wireless communication technologies, terminals typically use a globally unique temporary UE identity (GUTI) for communication processes such as network access and registration. However, in these processes, core network equipment may be unable to parse the GUTI sent by the terminal, affecting communication performance.

[0005] For example, for 5G core network equipment that has not been enhanced or upgraded, if a terminal moves from a 6G network to a 5G network, the 5G core network equipment may be unable to resolve the 5G GUTI mapped from the 6G GUTI, affecting communication performance. Summary of the Invention

[0006] This application provides a communication method, a terminal, and a network-side device that can solve the problem that core network devices cannot parse the GUTI sent by the terminal.

[0007] In a first aspect, a communication method is provided, comprising: a terminal acquiring a first GUTI and a second GUTI allocated by a first core network device, wherein the first GUTI corresponds to a first network, the second GUTI corresponds to a second network, and the first network is a successor network or next-generation network of the second network; when the terminal enters a connected state through the first network, the terminal sends a first identifier to an access network device corresponding to the first network, wherein the first identifier is used to identify the core network device corresponding to the first network, and the first identifier is determined based on the first GUTI; or, when the terminal enters a connected state through the second network, the terminal sends a second identifier to an access network device corresponding to the second network, wherein the second identifier is used to identify the core network device corresponding to the second network, and the second identifier is determined based on the second GUTI.

[0008] In a second aspect, a communication method is provided, comprising: a first core network device sending a second message to a terminal; wherein the second message includes a first GUTI and a second GUTI allocated to the terminal, the first GUTI corresponding to a first network, the second GUTI corresponding to a second network, and the first network being a successor network or a next-generation network of the second network.

[0009] Thirdly, a communication method is provided, comprising: a fourth core network device receiving an update message from a first core network device; the fourth core network device performing at least one of the following based on the update message: if the update message includes sixth indication information, determining that a terminal is in a first network or is in a registered state in the first network; if the update message does not include the sixth indication information, determining that the terminal is in a second network or is in a registered state in the second network; wherein the first network is a successor network or next-generation network of the second network, and the sixth indication information is used for at least one of the following: indicating that the update message corresponds to the first network; instructing the terminal to perform a registration or mobility registration update (MRU) in the first network.

[0010] Fourthly, a communication method is provided, comprising: a fifth core network device receiving a first message from a terminal, wherein the first message is used for registration or mobility registration update (MRU) of a second network; the fifth core network device obtaining the context of the terminal in the first network from a first core network device corresponding to the first network according to a context acquisition process corresponding to the second network; wherein the terminal is assigned a first GUTI and a second GUTI by the first core network device, the first GUTI corresponds to a first network, the second GUTI corresponds to a second network, and the first network is a successor network or a next-generation network of the second network.

[0011] Fifthly, a communication device is provided, comprising: a receiving module, configured to acquire a first GUTI and a second GUTI allocated by a first core network device, wherein the first GUTI corresponds to a first network and the second GUTI corresponds to a second network, and the first network is a successor network or next-generation network of the second network; and a sending module, configured to, when entering a connected state through the first network, send a first identifier to an access network device corresponding to the first network, wherein the first identifier is used to identify the core network device corresponding to the first network and is determined based on the first GUTI; or, configured to, when entering a connected state through the second network, send a second identifier to an access network device corresponding to the second network, wherein the second identifier is used to identify the core network device corresponding to the second network and is determined based on the second GUTI.

[0012] A sixth aspect provides a communication device, comprising: a sending module for sending a second message to a terminal; wherein the second message includes a first GUTI and a second GUTI allocated to the terminal, the first GUTI corresponding to a first network, the second GUTI corresponding to a second network, and the first network being a successor network or a next-generation network of the second network.

[0013] A seventh aspect provides a communication apparatus, comprising: a receiving module for receiving an update message from a first core network device; and a processing module for performing at least one of the following based on the update message: if the update message includes sixth indication information, determining that a terminal is in a first network or is in a registration state in the first network; if the update message does not include the sixth indication information, determining that the terminal is in a second network or is in a registration state in the second network; wherein the first network is a successor network or a next-generation network of the second network, and the sixth indication information is used for at least one of the following: indicating that the update message corresponds to the first network; instructing the terminal to perform registration or MRU in the first network.

[0014] Eighthly, a communication device is provided, comprising: a receiving module for receiving a first message from a terminal, wherein the first message is used for registration or MRU in a second network; and a processing module for obtaining the context of the terminal in the first network from a first core network device corresponding to the first network according to a context acquisition process corresponding to the second network; wherein the terminal is assigned a first GUTI and a second GUTI by the first core network device, the first GUTI corresponds to a first network, the second GUTI corresponds to a second network, and the first network is a successor network or a next-generation network of the second network.

[0015] A ninth aspect provides a communication device configured to perform the steps of the method described in the first aspect, or implement the steps of the method described in the second aspect, or implement the steps of the method described in the third aspect, or implement the steps of the method described in the fourth aspect.

[0016] In a tenth aspect, a terminal is provided, the terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0017] Eleventhly, a terminal is provided, including a processor and a communication interface, wherein the communication interface is used to acquire a first GUTI and a second GUTI allocated by a first core network device, the first GUTI corresponding to a first network, the second GUTI corresponding to a second network, and the first network being a successor network or next-generation network of the second network; and the communication interface is further used to send a first identifier to an access network device corresponding to the first network when entering a connected state through the first network, the first identifier being used to identify the core network device corresponding to the first network, the first identifier being determined based on the first GUTI; or, used to send a second identifier to an access network device corresponding to the second network when entering a connected state through the second network, the second identifier being used to identify the core network device corresponding to the second network, the second identifier being determined based on the second GUTI.

[0018] In a twelfth aspect, a network-side device is provided, the network-side device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the second aspect, or implementing the steps of the method as described in the third aspect, or implementing the steps of the method as described in the fourth aspect.

[0019] In a thirteenth aspect, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is used to send a second message to a terminal; wherein the second message includes a first GUTI and a second GUTI allocated to the terminal, the first GUTI corresponding to a first network, the second GUTI corresponding to a second network, and the first network being a successor network or a next-generation network of the second network.

[0020] In a fourteenth aspect, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is configured to receive an update message from a first core network device; the processor is configured to perform at least one of the following based on the update message: if the update message includes sixth indication information, determine that a terminal is in a first network or is in a registration state in the first network; if the update message does not include the sixth indication information, determine that the terminal is in a second network or is in a registration state in the second network; wherein the first network is a successor network or a next-generation network of the second network, and the sixth indication information is used for at least one of the following: indicating that the update message corresponds to the first network; instructing the terminal to perform registration or MRU in the first network.

[0021] In a fifteenth aspect, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is used to receive a first message from a terminal, wherein the first message is used for registration or MRU in a second network; the processor is used to obtain the context of the terminal in the first network from a first core network device corresponding to the first network according to the context acquisition process corresponding to the second network; wherein the terminal is assigned a first GUTI and a second GUTI by the first core network device, the first GUTI corresponds to the first network, the second GUTI corresponds to the second network, and the first network is a successor network or next-generation network of the second network.

[0022] In a sixteenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or the steps of the method described in the second aspect, or the steps of the method described in the third aspect, or the steps of the method described in the fourth aspect.

[0023] In a seventeenth aspect, a wireless communication system is provided, comprising: a terminal and a network-side device, wherein the terminal is configured to perform the steps of the method described in the first aspect, and the network-side device is configured to perform the steps of the method described in the second, third, or fourth aspect.

[0024] Eighteenthly, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run a program or instructions to implement the steps of the method as described in the first aspect, or the steps of the method as described in the second aspect, or the steps of the method as described in the third aspect, or the steps of the method as described in the fourth aspect.

[0025] In a nineteenth aspect, a computer program / program product is provided, the computer program / program product being stored in a storage medium, the computer program / program product being executed by at least one processor to implement the steps of the method as described in the first aspect, or the steps of the method as described in the second aspect, or the steps of the method as described in the third aspect, or the steps of the method as described in the fourth aspect.

[0026] In this embodiment, the first core network device simultaneously assigns a first GUTI corresponding to the first network and a second GUTI corresponding to the second network to the terminal. This allows the terminal to select the corresponding identifier of the network to be accessed when entering the connected state, and perform operations such as network registration or MRU. This enables the access network device to route to the first core network device based on the identifier, thereby effectively solving the problem that the core network device cannot parse the GUTI and ensuring communication performance. Attached Figure Description

[0027] Figure 1a is a schematic diagram of the structure of a wireless communication system provided in an exemplary embodiment of this application.

[0028] Figure 1b is a schematic diagram of a wireless communication architecture provided in an exemplary embodiment of this application.

[0029] Figure 1c is a second schematic diagram of a wireless communication architecture provided in an exemplary embodiment of this application.

[0030] Figure 2 is a flowchart illustrating one of the exemplary embodiments of the communication method provided in this application.

[0031] Figure 3 is a second schematic flowchart of a communication method provided in an exemplary embodiment of this application.

[0032] Figure 4a is a third schematic flowchart of a communication method provided in an exemplary embodiment of this application.

[0033] Figure 4b is a fourth schematic diagram of a sub-process of the communication method provided in an exemplary embodiment of this application.

[0034] Figure 4c is the fifth of the sub-process diagrams of the communication method provided in an exemplary embodiment of this application.

[0035] Figure 5a is one of the schematic diagrams of the interaction flow of the communication method provided in an exemplary embodiment of this application.

[0036] Figure 5b is a second schematic diagram of the interaction flow of the communication method provided in an exemplary embodiment of this application.

[0037] Figure 5c is a schematic diagram of the interaction flow of the communication method provided in an exemplary embodiment of this application.

[0038] Figure 6 is a flowchart of a communication method provided in an exemplary embodiment of this application.

[0039] Figure 7 is a flowchart of a communication method provided in an exemplary embodiment of this application.

[0040] Figure 8 is a schematic diagram of the structure of a communication device provided in an exemplary embodiment of this application.

[0041] Figure 9 is a second schematic diagram of the structure of a communication device provided in an exemplary embodiment of this application.

[0042] Figure 10 is a third schematic diagram of the structure of a communication device provided in an exemplary embodiment of this application.

[0043] Figure 11 is a fourth schematic diagram of the structure of a communication device provided in an exemplary embodiment of this application.

[0044] Figure 12 is a schematic diagram of the structure of a communication device provided in an exemplary embodiment of this application.

[0045] Figure 13 is a schematic diagram of the structure of a terminal provided in an exemplary embodiment of this application.

[0046] Figure 14 is a schematic diagram of the structure of a network-side device provided in an exemplary embodiment of this application. Detailed Implementation

[0047] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0048] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0049] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as one in which the sender explicitly informs the receiver of specific information, the operation to be performed, or the requested result, etc., in the instruction sent. An indirect instruction can be understood as one in which the receiver determines the corresponding information based on the instruction sent by the sender, or makes a judgment and determines the operation to be performed or the requested result, etc., based on the judgment result.

[0050] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used in the systems and radio technologies mentioned above, as well as in other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to systems other than NR systems, such as 6th Generation (6G) communication systems.

[0051] Figure 1a shows a block diagram of a wireless communication system applicable to an embodiment of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. Furthermore, terminal 11 can be any of the terminals described above, or it can be a chip within a terminal, such as a modem chip, a system-on-chip (SoC), etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 can include access network equipment or core network equipment, wherein access network equipment can also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment can include base stations, Wireless Local Area Network (WLAN) access points (APs), or Wireless Fidelity (WiFi) nodes, etc.The term "base station" can be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmit / Receive Point (TRP), or any other suitable term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to any specific technical terminology. It should be noted that this application embodiment only uses a base station in an NR system as an example for description and does not limit the specific type of base station.

[0052] Core network equipment, also known as core network nodes, core network functions, or core network elements, includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), and Binding Support. The core network functions include: BSF (Block Network Function), Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), and Network Data Analytics Function (NWDAF). It should be noted that this application embodiment only uses core network equipment in the NR system as an example and does not limit the specific type of core network equipment. If the name of the core network equipment mentioned in this application embodiment changes in subsequent protocol versions (e.g., 6G), it will still be within the scope of protection of this application.

[0053] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0054] Based on this, as shown in Figures 1b and 1c, two 6G network architectures are provided in this application. In the 6G network architecture shown in Figure 1b, the 6G network and the 5G network share the access control network element, and the terminal can use either the 6G access network device or the 5G access network device to access the shared core network.

[0055] In the 6G network architecture shown in Figure 1c, the 6G network and the 5G network each have independent access control network elements. Terminals can only access the 6G core network (6GC) through 6G access network equipment and access the 5G core network (5GC) through 5G access network equipment.

[0056] It is worth noting that (1) in the network architecture shown in Figure 1b, all 6G network elements are shared with 5G, while in the network architecture shown in Figure 1c, only some network elements are shared with 5G. The shared network elements are used for 6G and 5G interworking.

[0057] (2) In the network architectures shown in Figures 1b and 1c, "e" represents an enhancement of the 5G network element. For example, eAMF represents enhanced AMF, which is obtained by enhancing the 5G AMF. Other names can also be used for the enhanced network elements in the network architectures shown in Figures 1b and 1c. For example, eAMF can be replaced by 6G mobility management function (MMF) or 6G AMF, etc. There are no restrictions here.

[0058] For the aforementioned 5G core network equipment in the two network architectures that are neither enhanced nor upgraded, if a terminal moves from a 6G network to a 5G network, the 5G core network equipment may be unable to resolve the 5G GUTI mapped from the 6G GUTI, leading to the terminal's registration failure on the 5G network and affecting communication performance. To address this, this application provides a communication solution that resolves the issue of the 5G core network equipment being unable to resolve the 5G GUTI mapped from the 6G GUTI, ensuring the smooth execution of network registration or MRU and other communication activities based on the 5G GUTI.

[0059] It should be noted that when a 5G core network device receives a 5G GUTI sent by a terminal, it needs to obtain the terminal's context from the core network device that previously provided services to the terminal based on the 5G GUTI. "Unresolved" here refers to the 5G GUTI mapped from the 6G GUTI. This can be understood as the 5G core network device being unable to find the core network device that previously provided services to the terminal and obtain the terminal's context based on the 5G GUTI mapped from the 6G GUTI.

[0060] Furthermore, the aforementioned 5G and 6G networks are merely examples, meaning that the communication networks provided in this application embodiment may be, but are not limited to, the aforementioned 5G and 6G networks.

[0061] The technical solutions provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0062] Figure 2 shows a flowchart of a communication method 200 provided in an exemplary embodiment of this application. This method 200 can be executed by, but is not limited to, a terminal, specifically by hardware and / or software installed in the terminal. In this embodiment, the method 200 may include at least the following steps.

[0063] S210, the terminal obtains the first GUTI and the second GUTI allocated by the first core network device.

[0064] In this embodiment, the first core network device can be the core network device corresponding to the first network currently registered by the terminal. The first GUTI corresponds to the first network, and the second GUTI corresponds to the second network. That is, in this embodiment, the terminal can be assigned GUTIs corresponding to both the first and second networks simultaneously through the currently registered core network device for subsequent network registration or MRU.

[0065] The first network is a successor or next-generation network of the second network, which can also be understood as the first network being proposed or developed based on the second network. For example, in this embodiment, the first network may include a 6G network, and the second network may include a 5G network or a 4G network; or, the first network may include a 5G network, and the second network may include a 4G network, and so on.

[0066] Optionally, when the first network is a 6G network and the second network is a 5G network, the first core network device may include, but is not limited to, the eAMF shown in Figure 1b or Figure 1c.

[0067] S220, when the terminal enters the connected state through the first network, it sends a first identifier to the access network device corresponding to the first network; or, when the terminal enters the connected state through the second network, it sends a second identifier to the access network device corresponding to the second network.

[0068] It should be noted that the terminal entering the connected state in the first network can be understood or replaced as: the terminal entering the connected state from the idle state in the first network. Similarly, the terminal entering the connected state in the second network can be understood or replaced as: the terminal entering the connected state from the idle state in the second network.

[0069] The first identifier is used to identify the core network device corresponding to the first network, and the first identifier is determined based on the first GUTI. This allows the access network device to route the terminal to the original core network device based on the first identifier, i.e., the first core network device where the terminal was last registered and assigned the first GUTI. This effectively solves the problem of the core network device being unable to resolve the GUTI, ensuring communication performance, such as ensuring the smooth operation of terminal network registration or MRU communication processes.

[0070] Similarly, the second identifier is used to identify the core network device corresponding to the second network, and the second identifier is determined based on the second GUTI. This allows the access network device to route the terminal to the original core network device, i.e., the first core network device to which the terminal was previously registered and assigned the second GUTI, based on the second identifier. This effectively solves the problem of the core network device being unable to resolve the GUTI, ensuring communication performance, such as ensuring the smooth operation of terminal network registration or MRU communication processes.

[0071] In some embodiments, the determination of the first identifier based on the first GUTI can be understood as: the first identifier can be derived from the first GUTI, or the first identifier is obtained from the first GUTI, that is, the first GUTI includes the first identifier.

[0072] Similarly, the second identifier being determined based on the second GUTI can be understood as: the second identifier can be derived from the second GUTI, or the second identifier is obtained from the second GUTI, that is, the second GUTI includes the second identifier.

[0073] Optionally, at least one of the first identifier and the second identifier is a globally unique mobility management function identifier (GUAMI).

[0074] It is understood that, in the case where the first identifier and / or the second identifier is GUMAI, the GUAMI is part of the GUTI, that is, the GUTI may include GUAMI + Temporary Mobile Subscriber Identity (TMSI), etc.

[0075] In this embodiment, the first core network device simultaneously assigns the first GUTI corresponding to the first network and the second GUTI corresponding to the second network to the terminal. This allows the terminal to select the corresponding identifier for network registration or MRU when entering the connected state, based on the network to be registered. This enables the access network device to route to the original core network device based on the identifier, effectively solving the problem that the core network device corresponding to the second network cannot parse the GUTI and ensuring communication performance, such as ensuring the smooth operation of the terminal's network registration or MRU communication process.

[0076] Furthermore, this embodiment, through the aforementioned design, can avoid enhancing or upgrading the core network equipment corresponding to the second network, which is beneficial to the deployment of the first network.

[0077] Optionally, the formats of the first GUTI corresponding to the first network and the GUTI corresponding to the second network are different. That is, in the case where the formats of the first GUTI corresponding to the first network and the GUTI corresponding to the second network are different, in this embodiment, the first core network device can simultaneously allocate the first GUTI corresponding to the first network and the GUTI corresponding to the second network to the terminal.

[0078] In some embodiments, the terminal may also send first indication information to the access network device; wherein, when entering the connected state through the first network, the first indication information is used to indicate that the type of the first identifier is native; or, when entering the connected state through the second network, the first indication information is used to indicate that the type of the second identifier is native.

[0079] Taking the first identifier as an example, the fact that the first identifier is of type Native can be understood as: the first identifier is determined based on the first GUTI assigned to the terminal by the first core network device.

[0080] In some embodiments, the terminal may also send a first message to the core network device corresponding to the target network, the first message being used for registration or MRU of the target network; wherein, if the target network corresponds to the first network, the first message includes the first GUTI; or, if the target network corresponds to the second network, the first message includes the second GUTI.

[0081] The first message is a Non-Access Stratum (NAS) message, such as a registration message, a service request message, a deregistration message, etc. It can be carried together with the aforementioned first identifier (or second identifier) ​​and the first indication information through a Radio Resource Control (RRC) message. This embodiment does not impose any restrictions on this.

[0082] Optionally, the first message may also include type indication information for the first GUTI or the second GUTI, to indicate that the type of the first GUTI or the second GUTI is Native, that is, the first GUTI or the second GUTI was assigned by the core network device that the terminal last registered.

[0083] In some embodiments, when the first core network device allocates a first GUTI and a second GUTI to the terminal, this method embodiment 200 may further include: the terminal sending second indication information to the first core network device, the second indication information being used to indicate that the terminal supports the first network, so that the first core network device can allocate the first GUTI and the second GUTI based on the second indication information, thereby making the first GUTI and the second GUTI allocated by the first core network device to the terminal match the capabilities of the terminal.

[0084] It should be noted that the terminal supports the first network, which can be understood or replaced as: the terminal can access the first network; or, the terminal has the ability to access the first network.

[0085] In some embodiments, when the terminal is configured with the first GUTI and the second GUTI, this method embodiment 200 may further include: the terminal receiving third indication information sent from the first core network device; wherein, the third indication information is used to notify the terminal that the first core network device supports the first network, so that the terminal knows that the first core network device supports the first network, so that when performing network registration or MRU in the next time, it will preferentially initiate the network registration or MRU process based on the first network and the corresponding first GUTI.

[0086] It should be noted that the first core network device supports the first network, which can be understood or replaced as: the first core network device supports communication with the terminal through the first network.

[0087] For example, in this embodiment, when the first core network device assigns the first GUTI and the second GUTI to the terminal, the first core network device further instructs the terminal through the second indication information to notify the terminal that the first core network device supports the first network. This enables the terminal to select or prioritize the first network supported by the first core network device for registration or MRU when it needs to perform network registration or MRU, and to initiate an RRC message based on the first GUTI corresponding to the first network. This allows the access network device to route messages used for first network registration or MRU (such as the first message carried in the RRC message) to the first core network device as much as possible. Thus, it can ensure that the first core network device accurately parses the first GUTI and avoid resource waste caused by information transmission between network elements.

[0088] Optionally, the third indication information can be transmitted with the aforementioned first GUTI and second GUTI through the same message, such as through a registration accept message.

[0089] In some embodiments, the first network and the second network share the first core network device. For example, assuming, as shown in FIG1b, the first network is a 6G network, the second network is a 5G network, and the first core network device is an eAMF, then the 6G network and the 5G network share the eAMF.

[0090] Alternatively, the first network corresponds to the first core network device. For example, assuming, as shown in Figure 1c, the first network is a 6G network, the second network is a 5G network, and the first core network device is an eAMF, then the 6G network corresponds to the eAMF and is not shared with the 5G network.

[0091] Figure 3 shows a flowchart of a communication method 300 provided in an exemplary embodiment of this application. This method 300 can be executed by, but is not limited to, a first core network device, specifically by hardware and / or software installed in the first core network device. In this embodiment, the method 300 may include at least the following steps.

[0092] S310, the first core network device sends the second message to the terminal.

[0093] The first core network device can be the core network device corresponding to the first network currently registered by the terminal.

[0094] The second message includes a first GUTI and a second GUTI assigned to the terminal. The first GUTI corresponds to a first network, and the second GUTI corresponds to a second network. The first network is a successor network or next-generation network of the second network. In other words, this embodiment can simultaneously assign GUTIs corresponding to the first and second networks to the terminal through the currently registered core network device for subsequent network registration or MRU.

[0095] The first network is a successor or next-generation network of the second network, which can also be understood as the first network being proposed or developed based on the second network. For example, in this embodiment, the first network may include a 6G network, and the second network may include a 5G network or a 4G network; or, the first network may include a 5G network, and the second network may include a 4G network, and so on.

[0096] Optionally, when the first network is a 6G network and the second network is a 5G network, the first core network device may include, but is not limited to, the eAMF shown in Figure 1b or Figure 1c.

[0097] Optionally, the second message may be, but is not limited to, a registration accept message transmission.

[0098] In this embodiment, the first core network device simultaneously assigns a first GUTI corresponding to the first network and a second GUTI corresponding to the second network to the terminal. This allows the terminal to select the corresponding identifier for network registration or MRU when entering the connected state, based on the network to be registered. This enables the access network device to route to the first core network device based on the identifier, effectively solving the problem that the core network device cannot parse the GUTI and ensuring communication performance, such as ensuring that the terminal's network registration or MRU communication processes proceed smoothly.

[0099] Optionally, the formats of the first GUTI corresponding to the first network and the GUTI corresponding to the second network are different. That is, in the case where the formats of the first GUTI corresponding to the first network and the GUTI corresponding to the second network are different, in this embodiment, the first core network device can simultaneously allocate the first GUTI corresponding to the first network and the GUTI corresponding to the second network to the terminal.

[0100] The implementation process of "when the terminal enters the connected state, it can select the corresponding identifier of the network to register with or perform network registration or MRU as needed" can be referred to the relevant description in S220 above, and will not be repeated here.

[0101] In some embodiments, in order to achieve the allocation of the first GUTI and the second GUTI, this method embodiment 300 may further include steps S320-S330 as shown in FIG4a.

[0102] S320, the first core network device receives a third message from the terminal, the third message being used for registration or MRU of the first network.

[0103] S330, the first core network device allocates the first GUTI and the second GUTI to the terminal according to the third message.

[0104] In other words, the first GUTI and the second GUTI are allocated by the first core network device when the terminal requests registration or MRU with the first core network device (such as eAMF) corresponding to the first network. This allows the terminal to perform the next network registration or MRU based on the first GUTI and the second GUTI, thereby enabling the access network device to select the original core network device for the next network registration or MRU, that is, the first core network device that allocates the first GUTI and the second GUTI, ensuring the smooth registration or MRU of the terminal.

[0105] In some embodiments, when the first core network device allocates the first GUTI and the second GUTI, it may also receive second indication information from the terminal. The second indication information is used to indicate that the terminal supports the first network, so that the first core network device can allocate the first GUTI and the second GUTI based on the second indication information, thereby enabling the first core network device to allocate the first GUTI and the second GUTI to the terminal in a way that matches the terminal's capabilities.

[0106] Optionally, the second indication information may be carried in the third message.

[0107] It should be noted that the terminal supports the first network, which can be understood or replaced as: the terminal can access the first network; or, the terminal has the ability to access the first network.

[0108] In some embodiments, the process by which the first core network device in S330 allocates the first GUTI and the second GUTI to the terminal according to the third message may include: when the third message includes fourth indication information and a third GUTI corresponding to the first network, and the fourth indication information is used to indicate that the type of the third GUTI is a mapped type, the first core network device allocates the first GUTI and the second GUTI to the terminal according to the fourth indication information.

[0109] The term "Mapped type" for the third GUTI can be understood as follows: the third GUTI is obtained by mapping the GUTI corresponding to the previous network to which the terminal registered. For example, assuming the terminal was previously registered on a 5G (or 6G) network, when the terminal moves from the 5G (or 6G) network or re-registers to the 6G network, the third GUTI included in the third message is obtained by mapping the GUTI corresponding to the 5G (or 6G) network; that is, the type of the third GUTI is "Mapped type".

[0110] In some embodiments, considering that the third message is used for registration or MRU in the first network, the first core network device can determine the context of the terminal in the first network based on the third message in order to register or MRU in the first network.

[0111] As an optional implementation, if the terminal moves or reselects from the second network to the first network, then when the first core network device determines the context of the terminal in the first network, this method embodiment 300 may further include S340 and S350 as shown in FIG4b, the contents of which are as follows.

[0112] S340, the first core network device obtains the context of the terminal in the second network from the second core network device corresponding to the second network according to the third message.

[0113] S350, the first core network device maps the context of the second network to the context of the first network.

[0114] In this embodiment, when obtaining the context of the first network through S340-S350, the method of first obtaining the context of the terminal in the second network and then mapping it locally to the context of the first network can avoid the enhancement and upgrade of the core network equipment (such as 5G AMF) corresponding to the second network, which is conducive to the deployment of the first network and the rapid development of the services corresponding to the first network.

[0115] Optionally, the process by which the first core network device in S340 obtains the context of the terminal in the second network from the second core network device corresponding to the second network according to the third message may include: if the third message includes a third GUTI corresponding to the first network, the first core network device maps the third GUTI to a fourth GUTI corresponding to the second network, and obtains the context of the terminal in the second network from the second core network device according to the fourth GUTI.

[0116] For example, assuming the first network is a 6G network and the second network is a 5G network, and the terminal moves or reselects from the 5G network to the 6G network, the first core network device can first map the 6G GUTI carried in the third message to a 5G GUTI, then obtain the terminal's context in the 5G network from the 5G core network device (i.e., the second core network device) based on the 5G GUTI (i.e., the fourth GUTI), and finally locally map the terminal's context in the 5G network to the context of the 6G network to complete the process of obtaining the terminal's context in the 6G network. In this process, since the terminal's context in the 5G network is obtained from the 5G core network device based on the 5G process, enhancements and upgrades to the core network equipment (such as a 5G AMF) corresponding to the 5G network can be avoided, which is beneficial for the deployment of the first network and the rapid development of services corresponding to the first network.

[0117] In some embodiments, after allocating the first GUTI and the second GUTI to the terminal through the aforementioned first core network device, this method embodiment 300 may further include: the first core network device sending third indication information to the terminal, the third indication information being used to notify the terminal that the first core network device supports the first network, thereby enabling the terminal to understand that the first core network device supports the first network, so that in the next network registration or MRU, the terminal can initiate a network registration or MRU process based on or preferentially based on the first network and the corresponding first GUTI.

[0118] It should be noted that the first core network device supports the first network, which can be understood or replaced as: the first core network device supports communication with the terminal through the first network.

[0119] For example, in this embodiment, when the first core network device assigns the first GUTI and the second GUTI to the terminal, the first core network device further notifies the terminal through the third indication information that the first core network device supports the first network. This enables the terminal to select or prioritize the first network supported by the first core network device for registration or MRU when it needs to perform network registration or MRU, and to initiate an RRC message based on the first GUTI corresponding to the first network. This allows the access network device to route messages used for first network registration or MRU (such as the first message carried in the RRC message) to the first core network device as much as possible. Thus, it can ensure that the first core network device accurately parses the first GUTI and avoid resource waste caused by information transmission between network elements.

[0120] Optionally, the third indication information can be transmitted with the aforementioned first GUTI and second GUTI via the second message.

[0121] In some embodiments, if the terminal needs to perform network registration or MRU based on the first GUTI and the second GUTI, then this method embodiment 300 may further include S360-S370 as shown in FIG4c.

[0122] S360, the first core network device receives a first message from the terminal.

[0123] The first message is used for registration or MRU of the target network.

[0124] When the target network corresponds to the first network, the first message includes the first GUTI, and the type of the first GUTI is Native.

[0125] Alternatively, if the target network corresponds to the second network, the first message includes the second GUTI, and the type of the second GUTI is Native.

[0126] S370, the first core network device obtains the context of the terminal in the target network from the local device according to the first message.

[0127] In this embodiment, by using network registration or MRU based on the first GUTI or the second GUTI, the access network device can select the first core network device that performs the allocation of the first GUTI or the second GUTI, i.e., the original core network device. Thus, on the one hand, it can ensure that the first core network device accurately parses the first GUTI, and on the other hand, it can achieve the purpose of local context acquisition. This avoids the problem of resource waste caused by the transmission of context information between network elements when the newly selected core network device is different from the previously registered old core network device.

[0128] In some embodiments, considering that when an access network device selects a core network device for network registration or MRU for a terminal based on a first identifier (determined based on a first GUTI) or a second identifier (determined based on a second GUTI), it may select a new core network device that is different from the first core network device, in addition to being able to select the first core network device that performs the allocation of the first GUTI and the second GUTI as much as possible. In the case where a new core network device is selected, the process of network registration or MRU may include the following.

[0129] In this scenario, assuming the terminal stores an assigned first GUTI and a second GUTI, and the terminal moves or reselects from a first network to a second network, and the access network device corresponding to the second network selects a new core network device for the terminal that is different from the first core network device and has not been upgraded or enhanced, denoted as the fifth core network device, then upon receiving a first message from the terminal, the fifth core network device can obtain the terminal's context in the first network from the first core network device corresponding to the first network according to the context acquisition process corresponding to the second network. Here, the first message is used for registration or MRU in the second network. Therefore, since the terminal's context in the first network is obtained from the first core network device corresponding to the first network based on the context acquisition process corresponding to the second network, enhancements or upgrades to the fifth core network device (such as a 5G AMF) can be avoided, which is beneficial for the deployment of the first network and the rapid development of services corresponding to the first network.

[0130] Specifically, when the first core network device receives a context request message from the fifth core network device corresponding to the second network, it can send the terminal's context to the fifth core network device depending on whether the context request message includes seventh indication information. The seventh indication information can be understood as a first network indication.

[0131] For example, if the context request message includes the seventh indication information, the first core network device may determine that the context request message is a message of the first network and may directly send the terminal's context of the first network to the fifth core network device; and / or, if the context request message does not include the seventh indication information, the context request message may be determined to be a message of the second network, and the terminal's context in the first network may be mapped to the context of the second network first, and then the context of the second network may be sent to the fifth core network device.

[0132] The seventh indication information is used for at least one of the following a)-c).

[0133] a) Indicates that the context request message corresponds to the first network.

[0134] b) Request the terminal in the context of the first network.

[0135] c) Instruct the terminal to perform registration or MRU on the first network.

[0136] In this embodiment, when the terminal moves or reselects from the first network to or reselects to the second network, if the core network device selected by the access network device for the terminal is a new core network device that has not been upgraded or enhanced, then the new core network device can obtain the context of the terminal in the first network from the first core network device corresponding to the first network according to the context acquisition process corresponding to the second network. This can avoid the enhancement and upgrade of the new core network device (such as 5G AMF), which is beneficial to the deployment of the first network and the rapid development of the services corresponding to the first network.

[0137] Furthermore, for messages between the first core network equipment and the fifth core network equipment, the network from which the message comes can be determined based on whether the received message contains the seventh indication information. This eliminates the need for enhancements or upgrades to the fifth core network equipment (such as 5G AMF), which is conducive to the rapid deployment of 6G services.

[0138] In some embodiments, after the first core network device obtains the context of the terminal in the first network, the first core network device may also send a registration message to a third core network device; and / or send an update message to a fourth core network device.

[0139] The third core network device may be, but is not limited to, UDM, eUDM, etc., and the registration message may include fifth indication information. The fifth indication information is used to indicate the radio access technology (RAT) corresponding to the first network, so that the third core network device can distinguish whether the registration message is from the first network or the second network according to the fifth indication information, thereby improving mobility management efficiency.

[0140] The fourth core network device may be, but is not limited to, SMF, eSMF, etc. The first core network device sends the update message to the fourth core network device to instruct the fourth core network device to update the network context registered by the terminal according to the update message.

[0141] In this embodiment, the update message may include a sixth indication information, which is used to indicate that the update message corresponds to the first network; and / or, the sixth indication information is used to instruct the terminal to perform registration or MRU in the first network, so that the fourth core network device can determine whether the update message is a message of the first network or the second network based on whether the update message includes the sixth indication information, so as to improve mobility management efficiency while avoiding upgrading the first core network device (such as AMF), which is conducive to the rapid development of network services corresponding to the first network.

[0142] For example, if the fourth core network device includes a sixth indication information in the update message, it determines that the update message comes from the first network and determines (or records) that the terminal is in the first network or is in a registered state in the first network.

[0143] Alternatively, if the fourth core network device does not include the sixth indication information in the update message, it determines that the update message comes from the second network and determines (or records) that the terminal is in the second network or is in a registered state in the second network.

[0144] Optionally, the sixth indication information may be represented by at least one of network access type, Subscription Permanent Identifier (SUPI), and first parameter. The first parameter indicates that the terminal performs registration or MRU on the first network; it may be a parameter newly introduced in this application or a parameter already existing in related technologies, and is not limited thereto.

[0145] In some embodiments, after the first core network device or the fifth core network device completes the registration or MRU of the terminal in the target network according to the first message, it may send a response message to the terminal to instruct the terminal to accept the registration or MRU of the terminal in the target network.

[0146] Optionally, if the first message is a registration message, the response message can be a registration accept message. The registration accept message may carry a GUTI reassigned to the terminal by the first core network device for subsequent mobility management.

[0147] Based on the communication methods provided in the aforementioned method embodiments 200 and 300, for ease of understanding, the implementation process of the communication method provided in this application is described below with reference to examples. It is assumed that the first network is a 6G network and the second network is a 5G network.

[0148] Example 1

[0149] Assuming the terminal was previously registered on the 6G network and has stored the 6G GUTI corresponding to the 6G network, then, as shown in Figure 5a, when the terminal needs to re-register on the 6G network (for example, after the user turns the device off and on again) or execute MRU, the implementation flow of the communication method is as follows.

[0150] S511, the terminal sends an RRC message to the 6G RAN.

[0151] The RRC message includes a 6G GUAMI and a third message; the 6G GUAMI is mapped from the 6G GTUI (i.e., the old 6G GTUI) corresponding to the 6G network previously registered by the terminal.

[0152] The third message includes an old 6G GUTI and second indication information, the second indication information being used to indicate that the terminal supports 6G networks. The second indication information can be carried through mobility management capabilities (MM capability).

[0153] Optionally, the RRC message may include, but is not limited to, the .RRC Setup Complete message, and the third message may be, but is not limited to, the registration message.

[0154] S512, the 6G RAN selects the first eAMF (i.e., the first core network device) for the first network registration or MRU based on the 6G GUAMI, and sends a third message to the first eAMF.

[0155] The first eAMF can be either the previously used eAMF or a new eAMF; there is no restriction on this.

[0156] Optionally, the third message can be transmitted via, but is not limited to, the NG interface (NG-AP).

[0157] In this Example 1, it is assumed that the first eAMF is a new eAMF, in order to execute the subsequent process.

[0158] S513, the first eAMF sends a context request message to the second eAMF to request the context of the terminal in the 6G network.

[0159] The second eAMF is the eAMF corresponding to the 6G network that the terminal previously registered with, and can also be called the original eAMF or the old eAMF.

[0160] The context request message may include a seventh indication, which may also be referred to as a 6G indication, for use in at least one of the following a)-c).

[0161] a) Indicates that the context request message corresponds to the 6G network.

[0162] b requests the terminal to operate within the context of the 6G network.

[0163] c) Instruct the terminal to perform registration or MRU on the 6G network.

[0164] Optionally, the context request message may include, but is not limited to, the Namf_Communication_UEContextTransfer message.

[0165] S514, the second eAMF determines that the context request message is a message in the 6G network based on the seventh indication information in the received context request message, and sends the context of the terminal in the 6G network to the first eAMF.

[0166] Optionally, the context request message may include a 6G GUTI, in which case the second eAMF may determine the context of the first eAMF requesting terminal in the 6G network based on the 6G GUTI and provide feedback.

[0167] Optionally, the terminal can transmit the context of the 6G network via the Namf_Communication_UEContextTransfer response message.

[0168] S515, the first eAMF sends a registration message to the eUDM (i.e., the third core network device) to register.

[0169] The registration message includes a fifth indication information, which is used to indicate the RAT type of the 6G network.

[0170] Optionally, the registration message may be, but is not limited to, Nudm_UECM_Registration, etc.

[0171] S516, the first eAMF obtains the terminal's 6G subscription information from the UDM.

[0172] Optionally, the 6G subscription information can be transmitted via the message Nudm_SDM_Get().

[0173] S517, the first eAMF sends an update message to the eSMF (i.e., the fourth core network device).

[0174] The update message includes a sixth indication information, which indicates that the update message corresponds to the first network, and / or the sixth indication information indicates that the terminal performs a registration or mobility registration update MRU on the first network.

[0175] Optionally, the update message may include, but is not limited to, Nsmf_PDUSession_UpdateSMContext.

[0176] S518, eSMF determines, based on the sixth indication information in the update message, that the terminal is in a 6G network or is in a 6G registration state.

[0177] S519, the first eAMF allocates 5G GUTI and 6G GUTI to the terminal simultaneously based on the terminal's ability to support 6G and 5G networks.

[0178] Optionally, the first eAMF sends a third indication message to the terminal, the third indication message being used to notify the terminal that the first eAMF supports the 6G network.

[0179] Optionally, the third indication information, the 5G GUTI and 6G GUTI allocated by the first eAMF to the terminal can be transmitted via, but is not limited to, a Registration accept message.

[0180] S520, the terminal enters idle mode.

[0181] S521, when the terminal moves or reselects to the 5G network and needs to enter the connected state on the 5G network, the terminal carries 5G GUAMI (i.e., the second identifier) ​​and first indication information in the RRC message sent to the 5G RAN. The first indication information is used to indicate that the type of 5G GUAMI is native.

[0182] Similarly, when a terminal moves or reselects to a 6G network and needs to enter the connected state on the 6G network, the terminal carries a 6G GUAMI (i.e., the first identifier) ​​and first indication information in the RRC message sent to the 6G RAN. The first indication information is used to indicate that the type of the 6G GUAMI is native.

[0183] Optionally, the RRC message may include, but is not limited to, the .RRC Setup Complete message.

[0184] S522, the 5G RAN selects the eAMF that allocates the 5G GUTI as much as possible based on the 5G GUAMI in the RRC message, that is, the first eAMF, and forwards the first message carried in the RRC message to the first eAMF for subsequent network registration or MRU.

[0185] Similarly, when a terminal enters the connected state in a 6G network, the 6G RAN tries to select the eAMF that allocates the 6G GUTI, i.e. the first eAMF, based on the 6G GUAMI in the RRC message, and forwards the first message carried in the RRC message to the first eAMF.

[0186] Optionally, in addition to selecting the first eAMF to be assigned a 5G GUTI or a 6G GUTI, if a new eAMF different from the first eAMF is selected, referred to as the fifth eAMF, the first message carried in the RRC message can be forwarded to the fifth eAMF for network registration or MRU.

[0187] Optionally, the first message is a NAS message, which may be, but is not limited to, a registration message, a service request message, a deregistration message, etc.

[0188] Optionally, the first message can be transmitted via, but is not limited to, NG-AP.

[0189] In Example 1, when a terminal moves between 5G and 6G networks, by simultaneously assigning 5G GUTI and 6G GUTI to the terminal, the RAN can select the same AMF for the terminal as much as possible. This ensures correct GUTI resolution and avoids resource waste caused by information transmission between network elements.

[0190] It is understood that each step in this Example 1 can refer to the relevant descriptions in the aforementioned method embodiments 200 or 300 to achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0191] Furthermore, this Example 1 may include more or fewer steps than those described in S511-S522, without limitation.

[0192] Example 2

[0193] Assuming the terminal was previously registered on a 6G network and has stored the 6G GUTI corresponding to the 6G network and the 5G GUTI corresponding to the 5G network, then, as shown in Figure 5b, when the terminal needs to move from the 6G network or reselect to the 5G network, the implementation flow of the communication method is as follows.

[0194] S531, when the terminal moves or reselects to the 5G network and needs to enter the connected state on the 5G network, the terminal carries 5G GUAMI (i.e., the second identifier) ​​and first indication information in the RRC message sent to the 5G RAN. The first indication information is used to indicate that the type of 5G GUAMI is native.

[0195] S532, 5GRAN selects the AMF corresponding to the 5G network based on the 5G GUAMI in the RRC message.

[0196] Specifically, the 5GRAN selects the eAMF that allocates the 5G GUTI (i.e., the first eAMF) based on the 5G GUAMI in the RRC message, and forwards the first message carried in the RRC message to the first eAMF (i.e., the first core network device). The first message also includes the 5G GUTI, and the 5G GUTI is of native type.

[0197] In addition, besides selecting the first eAMF to allocate 5G GUTI, if a new AMF different from the first eAMF is selected, referred to as the fifth AMF (i.e. the fifth core network device), the first message carried in the RRC message can be forwarded to the fifth AMF for network registration or MRU.

[0198] Specifically, for the fifth AMF, if the fifth AMF is an unupgraded 5G AMF, then the fifth AMF can be processed according to the 5G process, such as obtaining the context of the terminal in the first network according to the uplink and downlink acquisition process in the 5G network, so that the 5G AMF does not need to be upgraded or enhanced, which is beneficial to the deployment of 6G.

[0199] In this example 2, assuming the fifth AMF is selected, the implementation process is as follows.

[0200] S533, 5GRAN will forward the first message carried in the RRC message to the fifth AMF for network registration or MRU.

[0201] Optionally, the first message is a NAS message, which may be, but is not limited to, a registration message, a service request message, or a registration / deregistration message.

[0202] Optionally, the first message can be transmitted via, but is not limited to, NG-AP.

[0203] S534, the fifth AMF sends a context request message to the first eAMF (formerly eAMF) according to the 5G procedure in order to obtain the context of the terminal in the 6G network.

[0204] The context request message does not include the seventh indication information, which may also be referred to as the 6G indication, for use in at least one of the following a)-c).

[0205] a) Indicates that the context request message corresponds to the 6G network.

[0206] b requests the terminal to operate within the context of the 6G network.

[0207] c) Instruct the terminal to perform registration or MRU on the 6G network.

[0208] Optionally, the context request message may include, but is not limited to, the Namf_Communication_UEContextTransfer message.

[0209] S535, the first eAMF determines that the context request message is a message in the 5G network based on the fact that the seventh indication information is not included in the received context request message, and maps the context of the terminal in the 6G network to the context in the 5G network.

[0210] Optionally, the context request message may include a 5G GUTI, in which case the second eAMF may determine the context of the fifth eAMF requesting terminal in the 5G network based on the 5G GUTI and provide feedback.

[0211] S536, the first eAMF sends the context of the terminal in the 5G network to the fifth eAMF.

[0212] Optionally, the terminal can transmit information in the context of a 5G network via a Namf_Communication_UEContextTransfer response message.

[0213] S537, the first eAMF sends a registration message to the UDM (i.e., the third core network device) according to the 5G process to register.

[0214] Optionally, the registration message may be, but is not limited to, Nudm_UECM_Registration, etc.

[0215] S538, the first eAMF sends an update message to the eSMF (i.e., the fourth core network device).

[0216] Optionally, the update message may include, but is not limited to, Nsmf_PDUSession_UpdateSMContext.

[0217] The update message does not include a sixth indication information, which is used to indicate that the update message corresponds to the 6G network, and / or the sixth indication information is used to indicate that the terminal performs registration or MRU on the 6G network.

[0218] S539, eSMF determines that the terminal is in a 5G network or is in a 5G registration state based on the fact that the sixth indication information is not included in the update message.

[0219] S540, the first eAMF sends a response message to the terminal.

[0220] The response message corresponds to the first message. When the first message is a registration message, the response message is a registration accept message, which carries the allocated 5G GUTI.

[0221] In Example 2, by simultaneously assigning 5G GUTI and 6G GUTI to the terminal, the RAN can ensure that when the terminal moves from or reselects to a 5G network from a 6G network, the RAN selects the same AMF for the terminal as much as possible. This ensures correct GUTI resolution and avoids resource waste caused by information transfer between network elements. In cases where the same AMF is not selected, such as selecting an unupgraded 5G AMF, subsequent operations can be completed according to the 5G process without upgrading the 5G AMF, which is beneficial for the rapid deployment of 6G services.

[0222] In addition, eAMF and eSMF determine which network a message comes from based on whether the received message contains 6G indications (such as seventh indication information, sixth indication information, etc.), thus eliminating the need to upgrade the AMF and facilitating the rapid deployment of 6G services.

[0223] It is understood that each step in this Example 2 can refer to the relevant descriptions in the aforementioned method embodiments 200 or 300, and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0224] Furthermore, this Example 2 may include more or fewer steps than those described in S531-S540, without limitation.

[0225] Example 3

[0226] Assuming the terminal was previously registered on a 5G network and has stored the 5G GUTI corresponding to the 5G network, then, as shown in Figure 5c, when the terminal needs to move from the 5G network or reselect to the 6G network, the implementation flow of the communication method is as follows.

[0227] S551, when the terminal moves or reselects to the 6G network and needs to enter the connected state in the 6G network, the terminal carries the 6G GUAMI in the RRC message sent to the 6G RAN. The 6G GUAMI is mapped from the 5G GUTI, that is, the type of the 6G GUAMI is the mapped type.

[0228] S552, 6GRAN selects the AMF corresponding to the 6G network according to the 6G GUAMI in the RRC message, and denoted as the first eAMF (i.e. the first core network device).

[0229] The third message carried in the RRC message is used for 6G network registration and MRU. In this example, the third message includes the 6G GUTI mapped from the 5G GUTI.

[0230] Optionally, the third message may also include a second indication message, which indicates that the terminal supports 6G network.

[0231] S553, 6GRAN will forward the third message carried in the RRC message to the first eAMF for network registration or MRU.

[0232] Optionally, the third message may be, but is not limited to, a registration message, a service request message, or a registration request message.

[0233] Optionally, the third message can be transmitted via, but is not limited to, NG-AP.

[0234] In S554, the first eAMF sends a context request message to the second AMF (formerly the 5G AMF, also known as the second core network device) to obtain the context of the terminal in the 5G network.

[0235] The context request message includes a 5G GUTI mapped from a 6G GUTI and does not include a seventh indication information, which may also be referred to as a 6G indication, for use in at least one of the following a)-c).

[0236] a) Indicates that the context request message corresponds to the 6G network.

[0237] b requests the terminal to operate within the context of the 6G network.

[0238] c) Instruct the terminal to perform registration or MRU on the 6G network.

[0239] Optionally, the context request message may include, but is not limited to, the Namf_Communication_UEContextTransfer message.

[0240] S555, the second AMF determines that the context request message is a message in the 5G network based on the fact that the seventh indication information is not included in the received context request message, and sends the context of the terminal in the 5G network to the first eAMF.

[0241] Optionally, the context request message may include a 5G GUTI, in which case the second eAMF may determine the context of the first eAMF requesting terminal in the 5G network based on the 5G GUTI and provide feedback.

[0242] Optionally, the terminal can transmit information in the context of a 5G network via a Namf_Communication_UEContextTransfer response message.

[0243] S556, the first eAMF obtains the context of the terminal in the 6G network based on the received local mapping of the terminal's context in the 5G network.

[0244] S557, the first eAMF sends a registration message to the UDM (i.e., the third core network device) to register.

[0245] Optionally, the registration message may be, but is not limited to, Nudm_UECM_Registration, etc.

[0246] The registration message includes a fifth indication information, which is used to indicate the RAT type of the 6G network.

[0247] S558, the first eAMF sends an update message to the eSMF (i.e., the fourth core network device).

[0248] The update message includes a sixth indication information, which indicates that the update message corresponds to the first network, and / or the sixth indication information indicates that the terminal performs a registration or mobility registration update MRU on the first network.

[0249] Optionally, the update message may include, but is not limited to, Nsmf_PDUSession_UpdateSMContext.

[0250] S559, eSMF determines, based on the sixth indication information in the update message, that the terminal is in a 6G network or is in a 6G registration state.

[0251] S560, the first eAMF allocates 5G GUTI and 6G GUTI to the terminal simultaneously based on the terminal's ability to support 6G and 5G networks.

[0252] S561, the first eAMF sends a response message to the terminal.

[0253] The response message includes simultaneously allocating 5G GUTI and 6G GUTI to the terminal.

[0254] Optionally, the response message may further include third indication information, which is used to notify the terminal that the first eAMF supports the 6G network.

[0255] Optionally, the response message corresponds to the third message. Wherein, when the third message is a registration message, the response message is a registration accept message.

[0256] In Example 3, when a terminal moves from a 5G network or reselects to a 6G network, subsequent operations can be completed according to the 5G process without requiring upgrades or enhancements to the 5G AMF, which facilitates the rapid deployment of 6G services. Furthermore, the eAMF and eSMF determine whether a message originates from a 5G or 6G network based on whether the received message contains a 6G indication, eliminating the need for AMF upgrades and further facilitating the rapid deployment of 6G services.

[0257] In addition, in this example 3, both 5G GUTI and 6G GUTI are assigned to the terminal at the same time, so that during the next network registration, the RAN can select the same AMF for the terminal as much as possible. This ensures the correct resolution of GUTI and avoids the problem of resource waste caused by information transmission between network elements.

[0258] It is understood that each step in this example 3 can refer to the relevant descriptions in the aforementioned method embodiments 200 or 300, and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0259] Furthermore, this Example 3 may include more or fewer steps than those described in S551-S561, without limitation.

[0260] Figure 6 shows a flowchart of a communication method 600 provided in an exemplary embodiment of this application. This method 600 can be executed, but is not limited to, by a fourth core network device, specifically by hardware and / or software installed in the fourth core network device. In this embodiment, the method 600 may include at least the following steps.

[0261] S610, the fourth core network device receives update messages from the first core network device.

[0262] S620, the fourth core network device performs a first operation based on the update message.

[0263] The first operation includes any one of the following: if the update message includes a sixth indication information, determining that the terminal is in a first network or is in a registered state in the first network; if the update message does not include the sixth indication information, determining that the terminal is in a second network or is in a registered state in the second network; wherein the first network is a successor network or a next-generation network of the second network, and the sixth indication information is used for at least one of the following: indicating that the update message corresponds to the first network; instructing the terminal to perform a registration or mobility registration update MRU in the first network.

[0264] In some embodiments, the first network includes a 6G network, and the second network includes one of a 5G network and a 4G network.

[0265] It is understood that each implementation of the present method embodiment 600 has the same or corresponding technical features as the aforementioned method embodiment 200 or 300. Therefore, the implementation of each implementation of the present method embodiment 600 can be referred to the relevant descriptions in the aforementioned method embodiment 200 or 300 to achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0266] Figure 7 shows a flowchart of a communication method 700 provided in an exemplary embodiment of this application. This method 700 can be executed, but is not limited to, by a fifth core network device, specifically by hardware and / or software installed in the fifth core network device. In this embodiment, the method 700 may include at least the following steps.

[0267] S710, the fifth core network device receives the first message from the terminal.

[0268] The first message is used for registration or mobility registration update MRU in the second network.

[0269] S720, the fifth core network device obtains the context of the terminal in the first network from the first core network device corresponding to the first network according to the context acquisition process corresponding to the second network.

[0270] The terminal is assigned a first GUTI and a second GUTI by the first core network device. The first GUTI corresponds to the first network, and the second GUTI corresponds to the second network. The first network is the successor network or the next-generation network of the second network.

[0271] In some embodiments, the first GUTI and the second GUTI have different formats.

[0272] In some embodiments, the first network includes a 6G network, and the second network includes one of a 5G network and a 4G network.

[0273] It is understood that each implementation in this method embodiment 700 has the same or corresponding technical features as the aforementioned method embodiment 200 or 300. Therefore, the implementation of each implementation in this method embodiment 700 can be referred to the relevant descriptions in the aforementioned method embodiment 200 or 300 to achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0274] The communication method provided in this application can be executed by a communication device. This application uses the example of a communication device executing the communication method to illustrate the communication device provided in this application.

[0275] This application provides a communication device. As an example, the communication device may be a communication equipment or a component within a communication equipment, such as a chip. The communication equipment may be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal may include, but is not limited to, the type of terminal 11 listed above, and the network-side device may include, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations.

[0276] The communication device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, such as a Central Processing Unit (CPU), microprocessor, Digital Signal Processor (DSP), Artificial Intelligence (AI) processor, Graphics Processing Unit (GPU), Application Specific Integrated Circuit (ASIC), Network Processor (NP), Field Programmable Gate Array (FPGA), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceiver, pins, circuits, bus, radio frequency unit, etc.

[0277] Specifically, referring to Figure 8, when the communication device is a terminal or a component within a terminal, the communication device 800 includes a receiving module 810, used to acquire a first GUTI and a second GUTI allocated by a first core network device, wherein the first GUTI corresponds to a first network and the second GUTI corresponds to a second network, and the first network is a successor network or next-generation network of the second network; and a sending module 820, used to send a first identifier to an access network device corresponding to the first network when entering a connected state through the first network, wherein the first identifier is used to identify the core network device corresponding to the first network and is determined based on the first GUTI; or, used to send a second identifier to an access network device corresponding to the second network when entering a connected state through the second network, wherein the second identifier is used to identify the core network device corresponding to the second network and is determined based on the second GUTI.

[0278] In some embodiments, the first GUTI and the second GUTI have different formats.

[0279] In some embodiments, the sending module 820 is further configured to send first indication information to the access network device; wherein, when entering the connected state through the first network, the first indication information is used to indicate that the type of the first identifier is native; or, when entering the connected state through the second network, the first indication information is used to indicate that the type of the second identifier is native.

[0280] In some embodiments, at least one of the first identifier and the second identifier is a globally unique mobility management function identifier (GUAMI).

[0281] In some embodiments, the sending module 820 is further configured to send a first message to a core network device corresponding to a target network, the first message being used for registration or mobility registration update MRU of the target network; wherein, if the target network corresponds to the first network, the first message includes the first GUTI; or, if the target network corresponds to the second network, the first message includes the second GUTI.

[0282] In some embodiments, the sending module 820 is further configured to send a second indication information to the first core network device, the second indication information being used to indicate that the terminal supports the first network.

[0283] In some embodiments, the receiving module 810 is further configured to receive third indication information sent from the first core network device; wherein the third indication information is used to notify the terminal that the first core network device supports the first network.

[0284] In some embodiments, the first network includes a 6G network, and the second network includes one of a 5G network and a 4G network.

[0285] In some embodiments, the first network and the second network share the first core network device, or the first network corresponds to the first core network device.

[0286] The communication device 800 provided in this application embodiment can implement the various processes implemented in the method embodiment of FIG2 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0287] Referring to Figure 9, when the communication device is a network-side device or a component of a network-side device, the communication device 900 includes a sending module 910 for sending a second message to the terminal; wherein, the second message includes a first GUTI and a second GUTI allocated to the terminal, the first GUTI corresponds to a first network, the second GUTI corresponds to a second network, and the first network is a successor network or a next-generation network of the second network.

[0288] In some embodiments, the first GUTI and the second GUTI have different formats.

[0289] In some embodiments, as shown in FIG9, the apparatus further includes: a receiving module 910, configured to receive a third message from the terminal, the third message being used for registration or mobility registration update MRU of the first network; and a processing module 930, configured to allocate the first GUTI and the second GUTI to the terminal according to the third message.

[0290] In some embodiments, allocating the first GUTI and the second GUTI to the terminal according to the third message includes: when the third message includes fourth indication information and a third GUTI corresponding to the first network, and the fourth indication information is used to indicate that the type of the third GUTI is Mapped, allocating the first GUTI and the second GUTI to the terminal according to the fourth indication information.

[0291] In some embodiments, the processing module 930 is further configured to obtain the context of the terminal in the second network from the second core network device corresponding to the second network according to the third message; and to map the context of the second network to the context of the first network.

[0292] In some embodiments, obtaining the context of the terminal in the second network from the second core network device corresponding to the second network according to the third message includes: mapping the third GUTI to a fourth GUTI corresponding to the second network when the third message includes a third GUTI corresponding to the first network; and obtaining the context of the terminal in the second network from the second core network device according to the fourth GUTI.

[0293] In some embodiments, the sending module 910 is further configured to: send a registration message to a third core network device, wherein the registration message includes fifth indication information, the fifth indication information being used to indicate the Radio Access Technology (RAT) type of the first network; send an update message to a fourth core network device, the update message including sixth indication information, the sixth indication information being used to: indicate that the update message corresponds to the first network; instruct the terminal to perform a registration or mobility registration update (MRU) on the first network.

[0294] In some embodiments, the receiving module 920 is further configured to: receive a first message from the terminal, wherein the first message is for registration or mobility registration update (MRU) of the target network; the processing module 930 is further configured to obtain the context of the terminal in the target network from the local device according to the first message; wherein, if the target network corresponds to the first network, the first message includes the first GUTI; or, if the target network corresponds to the second network, the first message includes the second GUTI.

[0295] In some embodiments, the receiving module 920 is further configured to receive a context request message from a fifth core network device corresponding to the second network; the sending module 910 is further configured to perform at least one of the following according to the context request message: if the context request message includes seventh indication information, send the context of the terminal in the first network to the fifth core network device; if the context request message does not include the seventh indication information, map the context of the terminal in the first network to the context of the second network, and send the context of the second network to the fifth core network device; wherein the seventh indication information is used for at least one of the following: indicating that the context request message corresponds to the first network; requesting the terminal in the context of the first network; instructing the terminal to perform registration or MRU in the first network.

[0296] The communication device 900 provided in this application embodiment can implement the various processes implemented in the method embodiments of Figures 3-4c and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0297] Referring to Figure 10, when the communication device is a network-side device or a component within a network-side device, the communication device 1000 includes a receiving module 1010 for receiving an update message from a first core network device; and a processing module 1020 for performing at least one of the following based on the update message: if the update message includes sixth indication information, determining that the terminal is in a first network or is in a registered state in the first network; if the update message does not include the sixth indication information, determining that the terminal is in a second network or is in a registered state in the second network; wherein the first network is a successor network or next-generation network of the second network, and the sixth indication information is used for at least one of the following: indicating that the update message corresponds to the first network; instructing the terminal to perform a registration or mobility registration update MRU in the first network.

[0298] In some embodiments, the first network includes a 6G network, and the second network includes one of a 5G network and a 4G network.

[0299] The communication device 1000 provided in this application embodiment can implement the various processes implemented in the method embodiment of FIG6 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0300] Referring to Figure 11, when the communication device is a network-side device or a component within a network-side device, the communication device 1100 includes a receiving module 1110 for receiving a first message from a terminal, wherein the first message is used for registration with a second network or a Mobility Registration Update (MRU); and a processing module 1120 for obtaining the context of the terminal in the first network from a first core network device corresponding to the first network according to the context acquisition process corresponding to the second network; wherein the terminal is assigned a first GUTI and a second GUTI by the first core network device, the first GUTI corresponds to the first network, the second GUTI corresponds to the second network, and the first network is a successor network or a next-generation network of the second network.

[0301] In some embodiments, the first GUTI and the second GUTI have different formats.

[0302] In some embodiments, the first network includes a 6G network, and the second network includes one of a 5G network and a 4G network.

[0303] The communication device 1100 provided in this application embodiment can implement the various processes implemented in the method embodiment of FIG7 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0304] As shown in Figure 12, this application embodiment also provides a communication device 1200, including a processor 1201 and a memory 1202. The memory 1202 stores a program or instructions that can run on the processor 1201. For example, when the communication device 1200 is a terminal, the program or instructions executed by the processor 1201 implement the various steps of the above-described communication method embodiment 200 and achieve the same technical effect. When the communication device 1200 is a network-side device, the program or instructions executed by the processor 1201 implement the various steps of the above-described communication method embodiments 300, 600, or 700 and achieve the same technical effect. To avoid repetition, these will not be described again here.

[0305] This application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps in the method embodiment shown in FIG2. This terminal embodiment corresponds to the above-described terminal-side method embodiment, and all implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and can achieve the same technical effect. The terminal can be the communication device 800 shown in FIG8. Specifically, FIG13 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.

[0306] The terminal 1300 includes, but is not limited to, at least some of the following components: radio frequency unit 1301, network module 1302, audio output unit 1303, input unit 1304, sensor 1305, display unit 1306, user input unit 1307, interface unit 1308, memory 1309, and processor 1310.

[0307] Those skilled in the art will understand that terminal 1300 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to processor 1310 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The terminal structure shown in Figure 13 does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0308] It should be understood that, in this embodiment, the input unit 1304 may include a graphics processor 13041 and a microphone 13042. The graphics processor 13041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 1306 may include a display panel 13061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 1307 includes a touch panel 13071 and at least one of other input devices 13072. The touch panel 13071 is also called a touch screen. The touch panel 13071 may include a touch detection device and a touch controller. Other input devices 13072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0309] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 1301 can transmit it to the processor 1310 for processing; in addition, the radio frequency unit 1301 can send uplink data to the network-side device. Typically, the radio frequency unit 1301 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0310] The memory 1309 can be used to store software programs or instructions, as well as various data. The memory 1309 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 1309 may include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 1309 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0311] Processor 1310 may include one or more processing units; optionally, processor 1310 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 1310.

[0312] The radio frequency unit 1301 is configured to acquire a first GUTI and a second GUTI allocated by a first core network device, wherein the first GUTI corresponds to a first network and the second GUTI corresponds to a second network, and the first network is a successor network or next-generation network of the second network; the radio frequency unit 1301 is further configured to send a first identifier to the access network device corresponding to the first network when entering a connected state through the first network, wherein the first identifier is used to identify the core network device corresponding to the first network and is determined based on the first GUTI; or, when entering a connected state through the second network, to send a second identifier to the access network device corresponding to the second network, wherein the second identifier is used to identify the core network device corresponding to the second network and is determined based on the second GUTI.

[0313] In some embodiments, the first GUTI and the second GUTI have different formats.

[0314] In some embodiments, the radio frequency unit 1301 is further configured to send first indication information to the access network device; wherein, when entering the connected state through the first network, the first indication information is used to indicate that the type of the first identifier is native; or, when entering the connected state through the second network, the first indication information is used to indicate that the type of the second identifier is native.

[0315] In some embodiments, at least one of the first identifier and the second identifier is a globally unique mobility management function identifier (GUAMI).

[0316] In some embodiments, the radio frequency unit 1301 is further configured to send a first message to a core network device corresponding to a target network, the first message being used for registration or mobility registration update MRU of the target network; wherein, if the target network is the first network, the first message includes the first GUTI; or, if the target network is the second network, the first message includes the second GUTI.

[0317] In some embodiments, the radio frequency unit 1301 is further configured to send a second indication information to the first core network device, the second indication information being used to indicate that the terminal supports the first network.

[0318] In some embodiments, the radio frequency unit 1301 is further configured to receive third indication information sent from the first core network device; wherein the third indication information is configured to notify the terminal that the first core network device supports the first network.

[0319] In some embodiments, the first network includes a 6G network, and the second network includes one of a 5G network and a 4G network.

[0320] In some embodiments, the first network and the second network share the first core network device, or the first network corresponds to the first core network device.

[0321] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of method embodiment 200 and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0322] Specifically, this application also provides a network-side device. As shown in FIG14, the network-side device 1400 includes a processor 1401, a network interface 1402, and a memory 1403. The network-side device may be the communication device shown in FIG9, FIG10, or FIG11. The network interface 1402 is, for example, a Common Public Radio Interface (CPRI).

[0323] Specifically, the network-side device 1400 in this application embodiment further includes: instructions or programs stored in memory 1403 and executable on processor 1401, wherein processor 1401 calls the instructions or programs in memory 1403 to execute the methods executed by the modules shown in FIG9, FIG10 or FIG11.

[0324] For example, when the processor 1401 calls the instructions or program in the memory 1403 to execute the method executed by each module shown in FIG9, the network interface 1402 can be used to send a second message to the terminal; wherein, the second message includes a first GUTI and a second GUTI allocated to the terminal, the first GUTI corresponds to a first network, the second GUTI corresponds to a second network, and the first network is a successor network or a next-generation network of the second network.

[0325] For example, when processor 1401 calls instructions or programs in memory 1403 to execute the methods performed by the modules shown in FIG10, network interface 1402 can be used to receive update messages from the first core network device; processor 1401 can be used to perform at least one of the following according to the update message: if the update message includes sixth indication information, determine that the terminal is in the first network or is in a registered state in the first network; if the update message does not include the sixth indication information, determine that the terminal is in the second network or is in a registered state in the second network; wherein, the first network is the successor network or next-generation network of the second network, and the sixth indication information is used for at least one of the following: indicating that the update message corresponds to the first network; indicating that the terminal performs registration or MRU in the first network.

[0326] For example, when processor 1401 calls instructions or programs in memory 1403 to execute the methods performed by the modules shown in FIG11, network interface 1402 can be used to receive a first message from the terminal, wherein the first message is used for registration or MRU of the second network; processor 1401 can be used to obtain the context of the terminal in the first network from the first core network device corresponding to the first network according to the context acquisition process corresponding to the second network; wherein the terminal is assigned a first GUTI and a second GUTI, the first GUTI corresponds to the first network, the second GUTI corresponds to the second network, and the first network is the successor network or next-generation network of the second network.

[0327] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant descriptions of method embodiments 300-700 and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0328] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described communication method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0329] The processor mentioned above is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0330] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described communication method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0331] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0332] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described communication method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0333] This application also provides a wireless communication system, including a terminal and a network-side device. The terminal can be used to implement the various processes of the above-described communication method embodiment 200, and the network-side device can be used to implement the various processes of the above-described communication method embodiments 300, 600, or 700, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0334] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0335] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0336] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. A communication method, comprising: The terminal obtains a first globally unique temporary terminal identifier (GUTI) and a second GUTI assigned by the first core network device. The first GUTI corresponds to a first network, and the second GUTI corresponds to a second network. The first network is a successor network or a next-generation network of the second network. When the terminal enters a connected state through the first network, it sends a first identifier to the access network device corresponding to the first network. This first identifier identifies the core network device corresponding to the first network, and is determined based on the first GUTI; or... When the terminal enters the connected state through the second network, it sends a second identifier to the access network device corresponding to the second network. The second identifier is used to identify the core network device corresponding to the second network, and the second identifier is determined according to the second GUTI.

2. The method as described in claim 1, wherein, The first GUTI and the second GUTI have different formats.

3. The method as described in claim 1, wherein, The method further includes: The terminal sends a first instruction message to the access network device; Wherein, when entering the connected state through the first network, the first indication information is used to indicate that the type of the first identifier is a native type; or... When entering the connected state via the second network, the first indication information is used to indicate that the type of the second identifier is Native.

4. The method according to any one of claims 1-3, wherein, At least one of the first identifier and the second identifier is a globally unique mobility management function identifier (GUAMI).

5. The method according to any one of claims 1-4, wherein, The method further includes: The terminal sends a first message to the core network device corresponding to the target network. The first message is used for registration or mobility registration update MRU of the target network. Wherein, if the target network corresponds to the first network, the first message includes the first GUTI; or... If the target network corresponds to the second network, the first message includes the second GUTI.

6. The method according to any one of claims 1-5, wherein, The method further includes: The terminal sends a second indication message to the first core network device, the second indication message being used to indicate that the terminal supports the first network.

7. The method according to any one of claims 1-6, wherein, The method further includes: The terminal receives a third indication message sent from the first core network device; The third indication information is used to notify the terminal that the first core network device supports the first network.

8. The method according to any one of claims 1-7, wherein, The first network includes a 6G network, and the second network includes one of a 5G network and a 4G network.

9. The method according to any one of claims 1-8, wherein, The first network and the second network share the first core network device, or the first network corresponds to the first core network device.

10. A communication method, comprising: The first core network device sends a second message to the terminal; The second message includes a first globally unique temporary terminal identifier (GUTI) and a second GUTI assigned to the terminal. The first GUTI corresponds to a first network, and the second GUTI corresponds to a second network. The first network is a successor network or a next-generation network of the second network.

11. The method of claim 10, wherein, The first GUTI and the second GUTI have different formats.

12. The method of claim 10, wherein, The method further includes: The first core network device receives a third message from the terminal, the third message being used for the registration or mobility registration update MRU of the first network; The first core network device allocates the first GUTI and the second GUTI to the terminal according to the third message.

13. The method of claim 12, wherein, The first core network device allocates the first GUTI and the second GUTI to the terminal according to the third message, including: When the third message includes fourth indication information and a third GUTI corresponding to the first network, and the fourth indication information is used to indicate that the type of the third GUTI is Mapped, the first core network device allocates the first GUTI and the second GUTI to the terminal according to the fourth indication information.

14. The method of claim 12 or 13, wherein, The method further includes: The first core network device obtains the context of the terminal in the second network from the second core network device corresponding to the second network based on the third message; The first core network device maps the context of the second network to the context of the first network.

15. The method of claim 14, wherein, The first core network device obtains the context of the terminal in the second network from the second core network device corresponding to the second network based on the third message, including: When the third message includes a third GUTI corresponding to the first network, the first core network device maps the third GUTI to a fourth GUTI corresponding to the second network. The first core network device obtains the context of the terminal in the second network from the second core network device based on the fourth GUTI.

16. The method according to any one of claims 10-15, wherein, The method further includes at least one of the following: The first core network device sends a registration message to the third core network device, wherein the registration message includes fifth indication information, which is used to indicate the Radio Access Technology (RAT) type of the first network; The first core network device sends an update message to the fourth core network device, the update message including sixth indication information, the sixth indication information being used for at least one of the following: The update message is indicated to correspond to the first network; The terminal is instructed to perform a registration or mobility registration update MRU on the first network.

17. The method according to any one of claims 10-15, wherein, The method further includes: The first core network device receives a first message from the terminal, wherein the first message is used for registration or mobility registration update MRU of the target network; The first core network device obtains the context of the terminal in the target network from its local storage based on the first message; Wherein, if the target network corresponds to the first network, the first message includes the first GUTI; or... If the target network corresponds to the second network, the first message includes the second GUTI.

18. The method according to any one of claims 10-15, wherein, The method further includes: The first core network device receives a context request message from the fifth core network device corresponding to the second network; The first core network device performs at least one of the following actions based on the context request message: If the context request message includes the seventh indication information, the terminal is sent to the fifth core network device in the context of the first network; If the seventh indication information is not included in the context request message, the context of the terminal in the first network is mapped to the context of the second network, and the context of the second network is sent to the fifth core network device. The seventh indication information is used for at least one of the following: The context request message is indicated to correspond to the first network; The terminal is requested to be in the context of the first network; The terminal is instructed to perform registration or MRU on the first network.

19. The method according to any one of claims 10-18, wherein, The method further includes: The first core network device receives a second indication information from the terminal, the second indication information being used to indicate that the terminal supports the first network.

20. The method according to any one of claims 10-19, wherein, The method further includes: The first core network device sends a third indication message to the terminal, the third indication message being used to notify the terminal that the first core network device supports the first network.

21. The method according to any one of claims 10-20, wherein, The first network includes a 6G network, and the second network includes one of a 5G network and a 4G network.

22. The method according to any one of claims 10-20, wherein, The first network and the second network share the first core network device, or the first network corresponds to the first core network device.

23. A communication method, comprising: The fourth core network device receives update messages from the first core network device; The fourth core network device performs at least one of the following actions based on the update message: If the update message includes a sixth indication information, it is determined that the terminal is in the first network or is in a registered state in the first network. If the sixth indication information is not included in the update message, it is determined that the terminal is in the second network or is in a registered state in the second network; Wherein, the first network is the successor network or next-generation network of the second network, and the sixth indication information is used for at least one of the following: The update message is indicated to correspond to the first network; The terminal is instructed to perform a registration or mobility registration update MRU on the first network.

24. The method of claim 23, wherein, The first network includes a 6G network, and the second network includes one of a 5G network and a 4G network.

25. A communication method, comprising: The fifth core network device receives a first message from the terminal, wherein the first message is used for registration or mobility registration update MRU of the second network; The fifth core network device obtains the context of the terminal in the first network from the first core network device corresponding to the first network according to the context acquisition process corresponding to the second network; The terminal is assigned a first globally unique temporary terminal identifier (GUTI) and a second GUTI by the first core network device. The first GUTI corresponds to a first network, and the second GUTI corresponds to a second network. The first network is the successor network or the next-generation network of the second network.

26. The method of claim 25, wherein, The first GUTI and the second GUTI have different formats.

27. The method of claim 25, wherein, The first network includes a 6G network, and the second network includes one of a 5G network and a 4G network.

28. A communication device, comprising: The receiving module is used to obtain a first globally unique temporary terminal identifier (GUTI) and a second GUTI allocated by the first core network device. The first GUTI corresponds to a first network, and the second GUTI corresponds to a second network. The first network is a successor network or a next-generation network of the second network. The sending module is configured to send a first identifier to the access network device corresponding to the first network when entering a connected state through the first network. The first identifier is used to identify the core network device corresponding to the first network and is determined based on the first GUTI. Alternatively, it is configured to send a second identifier to the access network device corresponding to the second network when entering a connected state through the second network. The second identifier is used to identify the core network device corresponding to the second network and is determined based on the second GUTI.

29. The apparatus of claim 28, wherein, The sending module is further configured to send first indication information to the access network device; wherein, when entering the connected state through the first network, the first indication information is used to indicate that the type of the first identifier is native; or, when entering the connected state through the second network, the first indication information is used to indicate that the type of the second identifier is native.

30. A communication device, comprising: The sending module is used to send a second message to the terminal; The second message includes a first globally unique temporary terminal identifier (GUTI) and a second GUTI assigned to the terminal. The first GUTI corresponds to a first network, and the second GUTI corresponds to a second network. The first network is a successor network or a next-generation network of the second network.

31. The apparatus of claim 30, wherein, The device further includes: A receiving module is configured to receive a third message from the terminal, the third message being used for registration or mobility registration update MRU of the first network; The processing module is configured to allocate the first GUTI and the second GUTI to the terminal according to the third message.

32. A communication device, comprising: The receiving module is used to receive update messages from the first core network device; The processing module is configured to perform at least one of the following based on the update message: If the update message includes a sixth indication information, it is determined that the terminal is in the first network or is in a registered state in the first network. If the sixth indication information is not included in the update message, it is determined that the terminal is in the second network or is in a registered state in the second network; Wherein, the first network is the successor network or next-generation network of the second network, and the sixth indication information is used for at least one of the following: The update message is indicated to correspond to the first network; The terminal is instructed to perform a registration or mobility registration update MRU on the first network.

33. A communication device, comprising: A receiving module is configured to receive a first message from a terminal, wherein the first message is used for registration or mobility registration update MRU of a second network; The processing module is used to obtain the context of the terminal in the first network from the first core network device corresponding to the first network according to the context acquisition process corresponding to the second network; The terminal is assigned a first globally unique temporary terminal identifier (GUTI) and a second GUTI by the first core network device. The first GUTI corresponds to a first network, and the second GUTI corresponds to a second network. The first network is the successor network or the next-generation network of the second network.

34. A terminal comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as claimed in any one of claims 1 to 9.

35. A network-side device, comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as claimed in any one of claims 10 to 28.

36. A readable storage medium storing a program or instructions that, when executed by a processor, implement the steps of the method as claimed in any one of claims 1 to 9, or implement the steps of the method as claimed in any one of claims 10 to 27.

Images