Information interaction method, device and equipment

Abstract

The invention discloses an information interaction method, device and equipment, and belongs to the technical field of communication, and the information interaction method comprises the steps that a first network function receives first information, and the first information comprises a first identifier and a second identifier; the first network function performs a first operation based on first context information and second context information; wherein the first operation comprises at least one of the following items: generating, determining or judging third context information, sending the third context information to a seventh network function, executing a third operation, sending second information to a fourth network function, sending third information and fourth information to the fourth network function and the like.

Description

Technical Field

[0001] This application belongs to the field of communication technologies, and particularly relates to a method, apparatus, and device for information interaction. Background Art

[0002] Some terminals can access multiple networks simultaneously through different identifiers. For example, a user equipment (UE) supporting multi-universal subscriber identity module (Multi-SIM or MUSIM) has multiple card slots and can be connected to multiple networks simultaneously through different SIM cards. Another example is that a dual-steer device can use two subscription permanent identifiers (SUPI) to register different networks respectively.

[0003] However, for services or sessions of such terminals under different networks, due to mobility, a connection under one network needs to be switched to another network, resulting in two connections under the same network, thus reducing the communication efficiency of the terminal. Summary of the Invention

[0004] Embodiments of this application provide a mobility management, information interaction method, apparatus, and device to solve the problem that when a connection of a terminal device is updated or switched to another network under one network, there are two connections under the same network, thus reducing the communication efficiency of the terminal.

[0005] In a first aspect, an information interaction method is provided. The method includes:

[0006] A first network function receives first information, where the first information includes a first identifier and a second identifier;

[0007] The first network function performs a first operation based on first context information and second context information;

[0008] Wherein, the first operation includes at least one of the following:

[0009] Generate, determine, or judge third context information;

[0010] Send the third context information to a seventh network function;

[0011] Perform a third operation;

[0012] Send at least one of the following to a fourth network function:

[0013] Second information;

[0014] The third information and the fourth information;

[0015] Wherein, the first context information is related to the first identifier; the second context information is related to the second identifier;

[0016] Wherein, the second information includes any one of the following:

[0017] A third identifier;

[0018] A third identifier and at least one of the following: first session information, first identifier association information, a fourth identifier, second session information, a registration indication or a location update indication, a deregistration indication or a location cancellation indication;

[0019] Wherein, the third information includes a third identifier and a deregistration indication or a location cancellation indication;

[0020] Wherein, the fourth information includes a fourth identifier and a registration indication or a location update indication;

[0021] Wherein, the third operation includes at least one of the following:

[0022] Instructing a fifth network function to create, update, or release a session or a session context;

[0023] Instructing a fifth network function to indicate the eighth information;

[0024] Instructing a terminal device to indicate the eighth session information;

[0025] Instructing a terminal device to indicate the third session information;

[0026] Wherein, the eighth information is used to indicate at least one of the following:

[0027] Session transfer, session handover, session merging, cancellation of traffic splitting, release of associated session, preparation for session transfer, preparation for session handover, preparation for session merging, preparation for cancellation of traffic splitting, preparation for release of associated session;

[0028] Wherein, the eighth session information is used for at least one of the following:

[0029] Establishing a session based on the eighth session information;

[0030] Indicating an unaccepted session;

[0031] Indicating a released session;

[0032] Wherein, the third session information is used for at least one of the following:

[0033] Indicating an accepted session;

[0034] Indicating a held session.

[0035] Second aspect, there is provided an information interaction method, the method comprising:

[0036] A terminal device sends first information to a first network function, the first information including a first identifier and a second identifier;

[0037] Wherein, the first identifier is related to a third identifier, and the second identifier is related to a fourth identifier.

[0038] Third aspect, there is provided an information interaction method, the method comprising:

[0039] A second network function receives second indication information from the first network function;

[0040] The second network function sends first context information to the first network function based on the second indication information, and deletes or invalidates first session information, wherein the first session information is included in the first context information.

[0041] Fourth aspect, there is provided an information interaction method, the method comprising:

[0042] A fifth network function receives eighth information indicated by the first network function;

[0043] The fifth network function instructs an eighth network function to forward data based on the eighth information;

[0044] Wherein, the eighth information is used to indicate at least one of the following:

[0045] Session transfer, session handover, session merging, cancellation of traffic splitting, associated session release, preparation for session transfer, preparation for session handover, preparation for session merging, preparation for cancellation of traffic splitting, associated session preparation for release.

[0046] Fifth aspect, there is provided an information interaction method, the method comprising:

[0047] A ninth network function performs any one of the following:

[0048] Broadcast fourth indication information, send fourth indication information to a terminal device;

[0049] Wherein, the fourth indication information indicates at least one of the following:

[0050] Support context merging, support session merging, support registration mode conversion, support switchover, support steering, support splitting.

[0051] Sixth aspect, there is provided an information interaction apparatus, the apparatus comprising:

[0052] A first functional module, configured to register with a first network based on a third identifier;

[0053] A second functional module, configured to register a second network based on a fourth identifier.

[0054] Wherein, the third identifier is different from the fourth identifier.

[0055] In a seventh aspect, a communication system is provided, including:

[0056] A terminal device, configured to send first information to a first network function, where the first information includes a first identifier and a second identifier;

[0057] The first network function, configured to receive the first information and perform a first operation based on first context information and second context information;

[0058] Wherein, the first operation includes at least one of the following:

[0059] Generating third context information;

[0060] Sending the third context information to a seventh network function;

[0061] Wherein, the first context information is related to the first identifier, and the first context information includes at least one of the following: first session information and a third identifier; the second context information is related to the second identifier, and the second context information includes at least one of the following: second session information and a fourth identifier.

[0062] In a ninth aspect, a terminal is provided, where the terminal includes a processor and a memory, and the memory stores a program or instruction that can run on the processor. When the program or instruction is executed by the processor, the steps of the method described in the second aspect are implemented.

[0063] In a tenth aspect, a network-side device is provided, where the network-side device includes a processor and a memory, and the memory stores a program or instruction that can run on the processor. When the program or instruction is executed by the processor, the steps of the method described in any one of the first aspect, the third aspect, the fourth aspect, and the fifth aspect are implemented.

[0064] In an eleventh aspect, a readable storage medium is provided, where the readable storage medium stores a program or instruction. When the program or instruction is executed by a processor, the steps of the method described in any one of the first aspect, the third aspect, the fourth aspect, and the fifth aspect are implemented, or the steps of the method described in the second aspect are implemented.

[0065] In an eleventh aspect, a chip is provided. The chip includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is configured to run programs or instructions to implement the method described in any one of the first, third, fourth, and fifth aspects, or to implement the method described in the second aspect.

[0066] In a twelfth aspect, a computer program / program product is provided. The computer program / program product is stored in a storage medium and is executed by at least one processor to implement the steps of the method described in any one of the first, second, third, fourth, and fifth aspects.

[0067] In an embodiment of the present application, since the first network function can generate third context information based on the first context information and the second context information and / or send the third context information to the seventh network function after receiving the first information including the first identifier and the second identifier, where the first context information is related to the first identifier and the first context information includes at least one of the following: first session information and a third identifier; the second context information is related to the second identifier and the second context information includes at least one of the following: second session information and a fourth identifier. This can reduce the number of connections under the same network after the connection of the terminal device is updated or switched to another network under one network, thereby improving the communication efficiency of the terminal device. BRIEF DESCRIPTION OF THE DRAWINGS

[0068] Figure 1 is a block diagram of a wireless communication system provided by an embodiment of the present application.

[0069] Figure 2 is a schematic flowchart of an information interaction method provided by an embodiment of the present application.

[0070] Figure 3 is a schematic flowchart of an information interaction method provided by another embodiment of the present application.

[0071] Figure 4 is a schematic flowchart of an information interaction method provided by another embodiment of the present application.

[0072] Figure 5 is a schematic flowchart of an information interaction method provided by another embodiment of the present application.

[0073] Figure 6 is a schematic flowchart of an information interaction method provided by another embodiment of the present application.

[0074] Figure 7 is a schematic flowchart of an information interaction method provided by another embodiment of the present application.

[0075] Figure 8 It is a schematic structural diagram of an information interaction device provided by an embodiment of the present application.

[0076] Figure 9A It is a schematic flowchart of an information interaction method provided by a specific embodiment 1 of the present application.

[0077] Figure 9B It is a schematic flowchart of an information interaction method provided by a specific embodiment 2 of the present application.

[0078] Figure 9C It is a schematic flowchart of an information interaction method provided by a specific embodiment 3 of the present application.

[0079] Figure 9D It is a schematic flowchart of an information interaction method provided by a specific embodiment 4 of the present application.

[0080] Figure 9E It is a schematic flowchart of an information interaction method provided by a specific embodiment 5 of the present application.

[0081] Figure 9F It is a schematic flowchart of an information interaction method provided by a specific embodiment 6 of the present application.

[0082] Figure 9G It is a schematic flowchart of an information interaction method provided by a specific embodiment 7 of the present application.

[0083] Figure 9H It is a schematic flowchart of an information interaction method provided by a specific embodiment 8 of the present application.

[0084] Figure 9I It is a schematic flowchart of an information interaction method provided by a specific embodiment 9 of the present application.

[0085] Figure 9J It is a schematic flowchart of an information interaction method provided by a specific embodiment 10 of the present application.

[0086] Figure 10 It is a schematic structural diagram of an information interaction device provided by an embodiment of the present application.

[0087] Figure 11 It is a schematic structural diagram of an information interaction device provided by another embodiment of the present application.

[0088] Figure 12 It is a schematic structural diagram of an information interaction device provided by another embodiment of the present application.

[0089] Figure 13 It is a schematic structural diagram of an information interaction device provided by another embodiment of the present application.

[0090] Figure 14 It is a schematic structural diagram of an information interaction device provided by another embodiment of the present application.

[0091] Figure 15 It is a schematic structural diagram of an information interaction device provided by another embodiment of the present application.

[0092] Figure 16 It is a schematic structural diagram of a communication device of the present application.

[0093] Figure 17 Schematic hardware structure diagram of the terminal in the embodiment of the present application.

[0094] Figure 18 Schematic hardware structure diagram of the network-side device in the embodiment of the present application. Specific implementation manners

[0095] Next, the technical solutions in the embodiments of the present application will be clearly described with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are some, but not all, of the embodiments of the present application. According to the embodiments in the present application, every other embodiment obtained by those of ordinary skill in the art shall fall within the protection scope of the present application.

[0096] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, rather than to describe a specific order or sequence. It should be understood that such terms can be interchanged under appropriate circumstances so that the embodiments of the present application can be implemented in an order different from those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same category, and the number of objects is not limited. For example, the first access object can be one or more. In addition, "and / or" in the specification and claims means at least one of the connected objects, and the character " / " generally means an "or" relationship between the associated objects before and after.

[0097] It should be noted that the technology described in the embodiments of this application is 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), and other systems. The terms "system" and "network" in the embodiments of this application are often used interchangeably, and the described technology can be used in the above-mentioned systems and radio technologies, as well as in other systems and radio technologies. The following description describes the New Radio (NR) system for illustrative purposes and uses NR terms in most of the following descriptions, but these technologies can also be applied to applications other than NR system applications, such as the 6th Generation (6G) communication system. th Generation, 6G) communication system.

[0098] Figure 1The block diagram of a wireless communication system to which the embodiments of the present application can be applied is shown. The wireless communication system includes a terminal 01 and a network-side device 02. Among them, the terminal 01 can be a mobile phone, a tablet personal computer, a laptop computer or a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile Internet device (MID), an augmented reality (AR) / virtual reality (VR) device, a robot, a wearable device, a vehicle-mounted device (VUE), a pedestrian terminal (PUE), a smart home (home devices with wireless communication functions, such as refrigerators, TVs, washing machines or furniture, etc.), a game console, a personal computer (PC), a teller machine or a self-service machine, etc. The wearable device includes: a smart watch, a smart bracelet, a smart earphone, a smart glasses, smart jewelry (smart bracelet, smart bracelet, smart ring, smart necklace, smart anklet, smart ankle chain, etc.), a smart wristband, a smart clothing, etc. It should be noted that the specific type of the terminal 01 is not limited in the embodiments of the present application. The network-side device 02 can include an access network device or a core network device. Among them, the access network device 12 can also be called a radio access network device, a radio access network (RAN), a radio access network function or a radio access network unit. The access network device 12 can include a base station, a WLAN access point or a WiFi node, etc. The base station can be called a Node B, an evolved Node B (eNB), an access point, a base transceiver station (BTS), a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a home Node B, a home evolved Node B, a transmitting and receiving point (TRP) or some other suitable term in the art. As long as the same technical effect is achieved, the base station is not limited to a specific technical term. It should be noted that in the embodiments of the present application, only the base station in the NR system is taken as an example for introduction, and the specific type of the base station is not limited.

[0099] In order to solve the problem that a connection update or switching from one network to another results in two connections existing in the same network, thereby causing low communication efficiency of the terminal, the embodiments of the present application propose an information interaction method, device and equipment, which are described in detail below in conjunction with the accompanying drawings.

[0100] The terminal equipment (User Equipment, UE) involved in the embodiments of the present application refers to a terminal equipment having at least one of dual registration, dual connection, dual access, multi-access, multi-registration and multi-connection capabilities. For example, the terminal equipment involved in the embodiments of the present application may be a dual-boot device (DualSteer Device). A dual-boot device is a device with capabilities such as dual registration and dual-path transmission. The dual-boot device may include two terminal equipment (Terminal Equipment, TE): TE1 and TE2. TE has similar functions to UE and can also be regarded as a UE, specifically as a modem (Modem) of the UE. Alternatively, the dual-boot device can also be regarded as a UE, which includes at least an independent modem and an independent SIM card.

[0101] The network elements involved in the embodiments of the present application include a first network function, a second network function, a third network function, a fourth network function, a fifth network function, a sixth network function, a seventh network function, an eighth network function and a ninth network function.

[0102] In the case where the network access situation of the terminal device includes any one of 4G network and 5G network dual access, 5G network dual access, 4G network and 5G network dual registration, 5G network dual registration, 4G network and 5G network dual connection, 5G network dual connection, etc., exemplary:

[0103] The first network function may include: a first access and mobility management function (Access and Mobility Management Function, AMF) or a first mobility management entity (Mobile Management Entity, MME).

[0104] The second network function may include: a second AMF or a second MME.

[0105] The third network function may include: a second AMF or a second MME.

[0106] The fourth network function may include: a unified data management function (Unified Data Management, UDM) or a home subscriber server (Home Subscriber Server, HSS).

[0107] The fifth network function may include: Session Management Function (SMF) or Packet Data Network Gateway (PGW).

[0108] The sixth network function may include: PGW or SMF.

[0109] The seventh network function may include: the first MME or the first AMF.

[0110] The eighth network function may include: User Plane Function (UPF) or Packet Data Network Gateway - User Plane (PGW-U).

[0111] The ninth network function may include at least one of an access network node and a core network function. Among them, the access network node may be, for example, the Next Generation Radio Access Network (NG-RAN) of 5G, and the core network function may be AMF.

[0112] It should be noted that the above descriptions of the first to ninth network functions are merely examples. In some cases, the specific names of these network functions may change, and the specific situation shall be subject to the relevant embodiments in the following text.

[0113] First, an information interaction method proposed in an embodiment of the present application will be described below.

[0114] As Figure 2 shown, an information interaction method proposed in an embodiment of the present application may include:

[0115] Step 201, the first network function receives the first information, and the first information includes a first identifier and a second identifier.

[0116] In the first example, the first network function may receive the first information from the seventh network function. For example, it receives a Context Transfor Request message sent by the seventh network function, and the first information is carried in this message. Assume that the first network function is the second AMF (old AMF) in the 5G network. Then the seventh network function may be the first MME in the 4G network. The first information sent by the first MME to the first network function may come from the terminal device, and the first MME may be the target MME for the terminal device to perform mobility update or handover.

[0117] In the second example, the first network function may receive the first information from the terminal device. For example, the first information may be included in a first message sent by the terminal device to the first network function, where the first message is one of messages such as a mobility update message, a registration update message, a registration request message (Registration Request), a tracking area update message (Tracking Area Update, TAU), and a routing area update message (Routing Area Update, RAU). At this time, the first network function may be the first AMF in the 5G network, and the first AMF is the target AMF for the terminal device to perform a mobility update or handover.

[0118] Wherein, the first identifier may include at least one of the following:

[0119] The first globally unique temporary identifier (Globally Unique Temporary UE Identity, GUTI), such as GUTI1;

[0120] The first mapped GUTI obtained from the first GUTI, such as additional GUTI.

[0121] Wherein, the second identifier may include at least one of the following:

[0122] The second GUTI, such as GUTI2;

[0123] The second mapped GUTI obtained from the second GUTI, such as mapped GUTI.

[0124] Step 202, the first network function performs a first operation based on the first context information and the second context information.

[0125] Wherein, the first operation includes at least one of the following:

[0126] 1) Generate, determine, or decide the third context information;

[0127] For example, in the case where the first network function receives the first information from the seventh network function (i.e., the first example above), the first operation includes: generating third context information and sending the third context information to the seventh network function, such as sending a Context Transfor Response to the seventh network function. In the case where the first network function receives the first information from the terminal device (i.e., the second example above), the first operation includes: generating third context information. Among them, the generation of the third context information specifically includes: combining the first context information and the second context information (Combine session context).

[0128] 2) Send the third context information to the seventh network function.

[0129] 3) Execute the third operation;

[0130] 4) Send at least one of the following to the fourth network function:

[0131] The second information;

[0132] The third information and the fourth information.

[0133] Among them, the first context information is related to the first identifier, and the first context information includes at least one of the following: first session information and a third identifier; the second context information is related to the second identifier, and the second context information includes at least one of the following: second session information and a fourth identifier.

[0134] Among them, the third identifier may include at least one of the following:

[0135] The first Subscription Permanent Identifier (SUPI), such as SUPI1;

[0136] The first International Mobile Subscriber Identity (IMSI), such as IMSI1.

[0137] Among them, the fourth identifier may include at least one of the following:

[0138] The second SUPI, such as SUPI2;

[0139] The second IMSI, such as IMSI2.

[0140] Among them, the second information may include any one of the following:

[0141] The third identifier;

[0142] The third identifier and at least one of the following: the first session information, the first identifier association information, the fourth identifier, the second session information, a registration indication or a location update indication, a deregistration indication or a location cancellation indication.

[0143] Wherein, the third information includes the third identifier and a deregistration indication or a location cancellation indication.

[0144] Wherein, the fourth information includes the fourth identifier and a registration indication or a location update indication.

[0145] For example, in the case where a first network function receives the first information from a terminal device (i.e., the second example in the above text), if the first network function is the first AMF in a 5G network and the first AMF is the target AMF for the terminal device to perform mobility update or handover, the fourth network function may be a UDM or an Authentication Server Function (AUSF). At this time, if the first AMF and the second AMF are different AMFs, the first AMF indicates the registered AMF to the UDM for the fourth identifier (SUPI2) registered for 5G, that is, records the serving AMF information of SUPI2 in the UDM.

[0146] Wherein, the third operation includes at least one of the following:

[0147] 1) Instruct a fifth network function to create, update, or release a session or session context;

[0148] 2) Instruct a fifth network function to indicate the eighth information;

[0149] 3) Instruct a terminal device to indicate the eighth session information;

[0150] 4) Instruct a terminal device to indicate part or all of the third session information, and the third session information is included in the third context information.

[0151] Wherein, the eighth information can be used to indicate at least one of the following:

[0152] Session transfer, session handover, session merge, cancellation of traffic splitting, release of associated session, preparation for session transfer, preparation for session handover, preparation for session merge, preparation for cancellation of traffic splitting, preparation for release of associated session.

[0153] Wherein, the eighth session information can be used for at least one of the following:

[0154] Establish a session based on the eighth session information;

[0155] Indicate an unaccepted session;

[0156] Indicate a released session.

[0157] For example, the eighth session information may include at least one of the following: Data Network Name (DNN), Single Network Slice Selection Assistance Information (S-NSSAI), Access Point Name (APN), Protocol Data Unit (PDU) session ID, Evolved Packet System (EPS) bearer ID - at least one of the session IDs.

[0158] Generally speaking, in the embodiments of the present application, the first session information is included in the first context information, the second session information is included in the second context information, the third session information is used to indicate to the terminal device the sessions that have not been accepted and / or the sessions that have been released, the fourth session information and the fifth session information are used to determine whether the sessions are associated and / or whether the associated sessions are allowed, and the seventh session information and the eighth session information identify a pair of session information. For example, if the session indicated by the fourth session information is a session in the first session information or the second session information but does not belong to the session in the third session information, at this time, the first network function may notify the terminal device that these sessions have not been accepted or notify the terminal to re - establish these sessions.

[0159] Specifically, the eighth session information may be used for at least one of the following:

[0160] Establish a session based on the eighth session information;

[0161] Indicate the sessions that have not been accepted;

[0162] Indicate the sessions that have been released.

[0163] Specifically, the third session information may be used for at least one of the following:

[0164] Indicate the sessions that have been accepted;

[0165] Indicate the sessions that have been held.

[0166] For example, the third session information may include the accepted or reserved session DNN / S-NSSAI, PDU session ID, EPS bearer ID, APN, etc.

[0167] It should be noted that in the embodiments of the present application, the session information in the first session information, the second session information, the third session information, the fourth session information, the fifth session information, the sixth session information, the seventh session information, and the eighth session information may all include at least one of the following: DNN, S-NSSAI, APN, PDU session ID, EPS bearer ID, and session ID. However, these information in different session information may be different. That is to say, the first session information, the second session information, the third session information, the fourth session information, the fifth session information, the sixth session information, the seventh session information, and the eighth session information may be session information containing different DNNs, different S-NSSAIs, different EPS bearer IDs, etc., respectively, corresponding to indicating multiple sessions.

[0168] It should also be noted that any one of the above-mentioned first session information, second session information, third session information, fourth session information, fifth session information, sixth session information, seventh session information, and eighth session information may include a session information list, that is, any one of the above-mentioned session information may contain relevant information of multiple sessions.

[0169] Optionally, in some embodiments, the first information may further include first indication information, and the first indication information may be used to indicate at least one of the following:

[0170] At least one of session merging, context merging, stopping switching, stopping steering, stopping splitting, stopping dual transmission, stopping multi-transmission, stopping concurrent transmission;

[0171] Any one of stopping dual registration, maintaining dual registration, stopping multi-registration, maintaining multi-registration, stopping dual connection, stopping multi-connection, stopping dual access, stopping multi-access, maintaining dual connection, maintaining multi-connection, maintaining dual access, and maintaining multi-access.

[0172] It can be understood that when the first indication information is used to indicate at least one of session merging, context merging, stopping switching, stopping steering, stopping splitting, stopping dual transmission, stopping multi-transmission, stopping concurrent transmission, stopping dual registration, stopping multi-registration, stopping dual connection, stopping multi-connection, stopping dual access, and stopping multi-access, the network side can be triggered to reduce the number of connections of the terminal device under the same network, thereby improving communication efficiency.

[0173] Optionally, Figure 2 The method shown may further include at least one of the following:

[0174] The first network function obtains the first context information from the second network function based on the first identifier;

[0175] The first network function receives the first context information from the second network function;

[0176] The first network function obtains the second context information from the third network function based on the second identifier;

[0177] The first network function receives the second context information from the third network function.

[0178] For example, in the case where the first network function receives the first information from the seventh network function (i.e., the first example in the above text), assuming that the first network function is the second AMF (old AMF) in the 5G network, then the third network function can be the second MME (old MME) in the 4G network. The second MME can be the source MME for the terminal device to perform mobility update or handover. The first context information can be 5G context information, and the 5G context information is stored locally in the second AMF; the second context information can be 4G context information.

[0179] For another example, in the case where the first network function receives the first information from the terminal device (i.e., the second example in the above text), if the first network function is the first AMF in the 5G network and the first AMF is the target AMF for the terminal device to perform mobility update or handover, then the second network function can be the second AMF (old AMF) in the 5G network. The second AMF is the source AMF for the terminal device to perform mobility update or handover. The first context information can be 5G context information; the third network function can be the second MME (old MME) in the 4G network. The second MME can be the source MME for the terminal device to perform mobility update or handover. The first context information can be 4G context information.

[0180] Optionally, Figure 2 The method shown may further include: The first network function sends second indication information to the second network function or the third network function based on the first information.

[0181] Wherein, the second indication information is used to indicate at least one of the following:

[0182] Maintain registration, transfer session.

[0183] Optionally, in some embodiments, the first identifier, the third identifier, the second identifier, and the fourth identifier are related to at least one of the following: user equipment, end user, subscribed user, and terminal device.

[0184] Optionally, in some embodiments, the third identifier is different from the fourth identifier; alternatively, the third identifier is different from the fourth identifier, and the third context information includes any one of the third identifier and the fourth identifier, that is, the third context information is associated with the third identifier or the fourth identifier. Finally, there is only one context between the terminal device and the network side based on the third identifier or the fourth identifier. Therefore, the number of connections of the terminal device under the same network can be reduced, thereby improving the communication efficiency of the terminal device.

[0185] Optionally, in some embodiments, the execution of the first operation is further based on third indication information, where the third indication information is received by the first network function from at least one of the fourth network function and the fifth network function, or the third indication information is included in at least one of the following:

[0186] The first information;

[0187] The first context information;

[0188] The second context information.

[0189] Wherein, the third indication information is used to indicate that there is an associated identifier, which can be an indication information, or the associated identifier can be indicated by the fourth identifier. For example, if the third indication information includes a fifth identifier but is different from the fourth identifier, the first operation is not executed, or if the third indication information does not include a dual / multi-registration indication, the first operation is not executed.

[0190] Specifically, the third indication information may include at least one of the following:

[0191] Second identifier association information;

[0192] Dual registration indication or multi-registration indication;

[0193] The fourth identifier or the third identifier.

[0194] Optionally, the third identifier is different from the fifth identifier.

[0195] Optionally, the fifth identifier includes at least one of the following:

[0196] Third SUPI;

[0197] Third IMSI.

[0198] Wherein, the second identifier association information is used to indicate that there is an associated identifier, which can be an indication information or an identifier. For example, the second identifier association information includes the fourth identifier, which is used to indicate that the associated identifier is the fourth identifier.

[0199] Optionally, the first context information includes the first session information, and the second context information includes the second session information. Figure 2 An information interaction method provided by the illustrated embodiment may further include:

[0200] The first network function performs a second operation based on any one of the following:

[0201] 1) The first session information;

[0202] 2) The second session information;

[0203] 3) The first session information and the second session information;

[0204] 4) The first context information and the second session information;

[0205] 5) The first session information and the second context information.

[0206] Wherein, the second operation includes at least one of the following:

[0207] Generate, determine or judge third session information;

[0208] Include the third session information in the third context information.

[0209] Optionally, the first network function further performs the second operation based on the seventh information, wherein the seventh information is received by the first network function from at least one of the fourth network function and the fifth network function, or the seventh information is included in at least one of the following: the first context information, the second context information;

[0210] Wherein, the seventh information includes at least one of the following:

[0211] Fourth session information;

[0212] Fifth session information;

[0213] Sixth session information;

[0214] Session association information;

[0215] Wherein, the fifth session information indicates at least one of the session information of permission, acceptance, and signing;

[0216] Wherein, the sixth session information indicates the session information of non - permission or rejection.

[0217] Wherein, the session association information may include at least one of the following:

[0218] IP address information;

[0219] Transport address information;

[0220] Associated ID;

[0221] A pair of session information including seventh session information and eighth session information.

[0222] For example, the first network function can directly obtain the associated session information from the fourth session information. The first network function determines that a certain session information in the first session information or a certain session information in the second session information is in the fifth session information but not in the third session information through the fifth session information - that is, some session information does not enter the third session information during the merging process. For example, it is not in the seventh session information or the eighth session information, not in the fourth session information, and has nothing to do with the associated ID. The corresponding IP address or transmission address cannot establish a session, etc. The first network function can notify the terminal that these sessions are not accepted or notify the terminal to reconstruct these sessions.

[0223] Optionally, the first network function performs a third operation based on the first context information and the second context information, which may include: the first network function performs the third operation based on at least one of the following:

[0224] The third session information and the first session information;

[0225] The third session information and the second session information;

[0226] The third session information.

[0227] In some embodiments, the first context information includes any one of the following: the third identifier and the first identifier, the third identifier, and the fifth identifier related to the first identifier; and / or, the second context information includes any one of the following: the fourth identifier and the second identifier, the fourth identifier, and the sixth identifier related to the second identifier. For example, assume that the first context information is TE1, and the first identifier, the third identifier, and the fifth identifier indicate TE1; the second context information is TE2, and the second identifier, the fourth identifier, and the sixth identifier indicate TE2. TE1 and TE2 can be collectively referred to as a terminal device, that is, a terminal device with 2 identifiers at the same time. Specifically, when the first identifier is the first mapped GUTI (mappedGUTI), the fifth identifier can be the first GUTI, and when the second identifier is the second mapped GUTI (mapped GUTI), the fifth identifier can be the second GUTI.

[0228] In some embodiments, Figure 2 The method shown may further include at least one of the following:

[0229] The first network function obtains the first session information from the fifth network function;

[0230] The first network function obtains the second session information from the sixth network function.

[0231] Exemplarily, the fifth network function may be an SMF or a PGW, and the sixth network function may be a PGW or an SMF.

[0232] Figure 2 For an information interaction method provided by the illustrated embodiment, since after the first network function receives the first information including the first identifier and the second identifier, it can perform first operations such as generating third context information based on the first context information and the second context information and / or sending the third context information to the seventh network function. Among them, the first context information is related to the first identifier, and the first context information includes at least one of the following: first session information and a third identifier; the second context information is related to the second identifier, and the second context information includes at least one of the following: second session information and a fourth identifier. This can reduce the number of connections under the same network after the connection of the terminal device is updated under one network or switched to another network, thereby improving the communication efficiency of the terminal device.

[0233] As Figure 3 As shown, an information interaction method provided by another embodiment of the present application may include:

[0234] Step 301, the terminal device sends the first information to the first network function, and the first information includes a first identifier and a second identifier.

[0235] Among them, the first identifier is related to a third identifier, and the second identifier is related to a fourth identifier.

[0236] Optionally, the first information further includes first indication information, and the first indication information is used to indicate at least one of the following:

[0237] At least one of session merging, context merging, stopping handover, stopping steering, stopping splitting, stopping dual transmission, stopping multi-transmission, and stopping concurrent transmission;

[0238] Any one of stopping dual registration, maintaining dual registration, stopping multi-registration, maintaining multi-registration, stopping dual connection, stopping multi-connection, stopping dual access, stopping multi-access, maintaining dual connection, maintaining multi-connection, maintaining dual access, and maintaining multi-access.

[0239] Optionally, the first identifier, the third identifier, the second identifier, and the fourth identifier are related to at least one of the following: user equipment, end user, subscribed user, and the terminal device.

[0240] Optionally, the third identifier is different from the fourth identifier.

[0241] Optionally, the first information is included in the first message sent by the terminal device, where the first message is one of messages such as a mobility update message, a registration update message, a registration request message, a TAU, and a RAU.

[0242] Optionally, the first identifier includes at least one of the following:

[0243] The first GUTI;

[0244] The first mapped GUTI obtained from the first GUTI.

[0245] Optionally, the second identifier includes at least one of the following:

[0246] The second GUTI;

[0247] The second mapped GUTI obtained from the second GUTI.

[0248] Optionally, the third identifier includes at least one of the following:

[0249] The first SUPI;

[0250] The first IMSI.

[0251] Optionally, the fourth identifier includes at least one of the following:

[0252] The second SUPI;

[0253] The second IMSI.

[0254] In some embodiments, the first identifier is the first mapped GUTI, and the second identifier is the second GUTI, or the first identifier is the first GUTI, and the second identifier is the second mapped GUTI.

[0255] Optionally, Figure 3 The method shown may further include:

[0256] The terminal device receives at least one of the following indicated by the first network function:

[0257] The eighth session information;

[0258] The third session information.

[0259] Wherein, the eighth session information is used for at least one of the following:

[0260] Establish a session based on the eighth session information;

[0261] Indicate an unaccepted session;

[0262] Indicates a released session.

[0263] Wherein, the third session information is used for at least one of the following:

[0264] Indicates an accepted session;

[0265] Indicates a held session.

[0266] Optionally, step 301 may specifically include: when the terminal device decides to perform any one of the following, sending the first information to the first network function:

[0267] 1) Stopping at least one of dual connection, multi-connection, dual access, multi-access, dual transmission, multi-transmission, concurrent transmission, dual registration, multi-registration, session merging, context merging, stopping switch, stopping steer, and stopping split;

[0268] 2) Starting at least one of single connection, single access, single transmission, and single registration.

[0269] It can be understood that, in the case where the terminal device decides to stop the dual connection and sends the first information to the first network function, if it receives the eighth session information returned by the first network function, and the eighth session information is used to indicate a released session, it can cancel or release the corresponding local session, thereby stopping the dual connection and switching to a single connection. The same applies to other cases.

[0270] Optionally, Figure 3 The method shown may further include:

[0271] The terminal device receives fourth indication information from the ninth network function.

[0272] Correspondingly, step 301 may specifically include: the terminal device sending the first information to the first network function based on the fourth indication information.

[0273] Wherein, the fourth indication information may indicate at least one of the following:

[0274] Supporting context merging, supporting session merging, supporting registration mode conversion.

[0275] Wherein, the registration mode conversion includes: converting from a single registration mode to a dual registration mode, converting from a dual registration mode to a single registration mode, and so on.

[0276] Wherein, the ninth network function may access at least one of an access network function and a core network function. For example, when the access network of the terminal device is a 5G network, the ninth network function may be the 5G NG-RAN, and the fourth indication information may be broadcast by the 5G NG-RAN; or, the ninth network function may be the AMF, and correspondingly, the fourth indication information may be sent by the AMF to the terminal device.

[0277] As Figure 4 shown, an information interaction method provided in another embodiment of the present application may include:

[0278] Step 401, a second network function receives second indication information from a first network function.

[0279] Step 402, the second network function sends first context information to the first network function based on the second indication information, and deletes or invalidates first session information, where the first session information is included in the first context information.

[0280] For example, if the first network function is the first AMF in a 5G network, and the first AMF is the target AMF for the terminal device to perform mobility update or handover, then the second network function may be the second AMF (old AMF) in the 5G network, and the second AMF is the source AMF for the terminal device to perform mobility update or handover. The first context information may be 5G context information. The first AMF may request 5G context information from the second AMF based on the 5G-GUTI. Specifically, the first AMF may send a Namf_Communication_UEContextTransfer Request (second indication information) carrying the 5G-GUTI (first identifier) to the second AMF to request 5G context information. The second AMF returns the 5G context information, and the 5G context information includes SUPI1 (third identifier). The 5G context information may further include session information, such as a PDU session ID, related DNN, S-NSSAI, and SMF information. The 5G context information may further include identification association information for indicating that the terminal device has an associated SUPI, such as by carrying SUPI2. The 5G context information may further include session association information, such as the mapping relationship between (DNN, S-NSSAI) and APN, and the EPS bearer ID corresponding to the PDU session. It can be understood that when the second AMF and the first AMF are the same AMF, steps 401 and 402 are internal operations.

[0281] It can also be understood that the second network function deletes or invalidates the first session information, that is, deletes or invalidates redundant session information, which can improve communication efficiency.

[0282] Optionally, Figure 4 The method shown may further include: the second network function retains the part of the first context information other than the first session information to ensure normal communication of other context information.

[0283] Such as Figure 5 As shown, an information interaction method provided by another embodiment of the present application may include:

[0284] Step 501, a third network function receives second indication information from a first network function.

[0285] Step 502, the third network function sends second context information to the first network function based on the second indication information, and deletes or invalidates the second session information, where the second session information is included in the second context information.

[0286] For example, if the first network function is the first AMF in a 5G network, and the first AMF is the target AMF for the terminal device to perform mobility update or handover, then the second network function may be the second MME (old MME) in a 4G network, and the second MME may be the source MME for the terminal device to perform mobility update or handover. The second context information may be 4G context information; the first AMF may send second indication information to the second MME to request 4G context information. Specifically, the first AMF may send a UE Context Transfer Request message carrying the second mapped GUTI (second identifier) to the second MME, and the second MME returns the 4G context information of the UE, and the 4G context information may include SUPI2 (fourth identifier).

[0287] It can also be understood that the third network function deletes or invalidates the second session information, that is, deletes or invalidates redundant session information, which can improve communication efficiency.

[0288] Optionally, Figure 5 The method shown may further include: the third network function retains the part of the second context information other than the second session information to ensure normal communication of other context information.

[0289] Such as Figure 6 As shown, an information interaction method provided by another embodiment of the present application may include:

[0290] Step 601, a fifth network function receives eighth information indicated by a first network function.

[0291] Step 602, the fifth network function instructs an eighth network function to forward data based on the eighth information.

[0292] Among them, the eighth piece of information is used to indicate at least one of the following:

[0293] Session transfer, session handover, session merger, cancellation of traffic splitting, release of associated session, preparation for session transfer, preparation for session handover, preparation for session merger, preparation for cancellation of traffic splitting, preparation for release of associated session.

[0294] As an example, assume that the first network function is the first AMF, the fifth network function is the SMF or PGW, and the eighth network function is the UPF or PGW-U. Then the first AMF can determine whether it is necessary to create a new PDU session for SUPI1 in the 5G network based on the third context information (for example, based on the session association information to determine that a certain 4G session has no associated 5G session). If necessary, it can indicate to the SMF to create a PDU session for SUPI1 based on the 4G context information (the second context information), such as invoking the Nsmf_PDUSession_CreateSMContext operation, and the parameters can include indication information 1 (i.e., the eighth piece of information), indicating preparation for transfer / handoff. After the creation of the PDU session is completed, the SMF notifies the PGW-U or UPF to transmit the downlink data packets for the corresponding 4G session through the PDU session path of SUPI1, and the corresponding 4G session no longer transmits downlink data. This operation can be based on indication information 1.

[0295] As another example, assume that the first network function is the first AMF, the fifth network function is the SMF or PGW, and the eighth network function is the UPF or PGW-U. Then the first AMF can also determine that a certain 4G session has an associated 5G session based on the third context information (such as based on the session association information), and then indicate to the SMF to update the PDU session of SUPI1, such as invoking the Nsmf_PDUSession_UpdateSMContext operation for update. The parameters can include indication information 1 or indication information 2. Indication information 2 (i.e., the eighth piece of information) indicates transfer / handoff. The SMF notifies the PGW-U or UPF to transmit the downlink data packets for the corresponding 4G session through the PDU session path of SUPI1, and the corresponding 4G session no longer transmits downlink data. This operation can be based on indication information 1 or indication information 2.

[0296] Alternatively, assume that the first network function is the first AMF, the fifth network function is the SMF or the PGW, and the eighth network function is the UPF or the PGW-U. Then, based on all the 4G session information (the second session information) in the 4G context information, the first AMF can establish a new PDU session for SUPI1 in 5G, which can carry identification association information. For example, by carrying SUPI2 or indication information, the SMF can determine whether to create a PDU session based on the identification association information and the local session association information, and return the result to the first AMF. The first AMF merges the first context information and the second context information based on the returned result, that is, when there are the same sessions (with an association relationship, or the returned result indicates an existing associated session, failure, etc.), the 5G PDU session is retained while the 4G PDN connection or EPS bearer is invalidated.

[0297] As Figure 7 shown, an information interaction method provided by another embodiment of the present application may include:

[0298] Step 701, the ninth network function performs any one of the following:

[0299] Broadcasting the fourth indication information, sending the fourth indication information to the terminal device.

[0300] Wherein, the fourth indication information indicates at least one of the following:

[0301] Supporting context merging, supporting session merging, supporting registration mode conversion, supporting switching, supporting steering, supporting splitting.

[0302] Wherein, the ninth network function includes any one of the following:

[0303] Access network node, core network function.

[0304] Wherein, the registration mode conversion includes: converting from a single registration mode to a dual registration mode, converting from a dual registration mode to a single registration mode, and so on.

[0305] Wherein, the ninth network function can be at least one of an access network function and a core network function. For example, when the access network of the terminal device is a 5G network, the ninth network function can be the 5G NG-RAN, and the fourth indication information can be broadcast by the 5G NG-RAN; or, the ninth network function can be the AMF, and correspondingly, the fourth indication information can be sent by the AMF to the terminal device.

[0306] Based on the Figure 7 embodiment shown, the terminal device can initiate a Registration Request / TAU Request message in the embodiment based on the fourth indication information. In addition:

[0307] 1) During the process of the terminal device establishing a PDU session in 5G, the UDM can, based on the subscription information, send identification association information (such as the associated SUPI) and / or session association information (such as the PDU session ID, and / or at least one of the EPS bearer ID corresponding to (DNN, S-NSSAI) and the APN; or, the PDU session ID / DNN / S-NSSAI corresponding to the EPS bearer ID / APN) to the SMF;

[0308] 2) During the process of the terminal device establishing a PDU session in 5G, the terminal device sends identification association information and / or session association information to the SMF.

[0309] 3) During the process of the terminal device establishing a PDU session in 5G, the SMF can send the above session association information to the AMF.

[0310] As Figure 8 shown, another embodiment of the present application further proposes an information interaction device, which can be applied to a terminal device. The device 800 may include: a first functional module 801 and a second functional module 802.

[0311] The first functional module 801 is used to register with the first network based on the third identifier.

[0312] The second functional module 802 is used to register with the second network based on the fourth identifier.

[0313] When the device is applied to a dual-boot device, the first functional module 801 and the second functional module 802 can be TE1 and TE2 in the dual-boot device respectively. That is, TE1 can be used to register with the first network based on the third identifier, and TE2 can be used to register with the second network based on the third identifier.

[0314] Wherein, the third identifier includes at least one of the following:

[0315] The first SUPI;

[0316] The first IMSI;

[0317] Wherein, the fourth identifier includes at least one of the following.

[0318] The second SUPI;

[0319] The second IMSI.

[0320] Optionally, the first functional module 801 is further used to perform any one of the following:

[0321] Obtain second context information from the second functional module, where the second context information includes a second identifier;

[0322] Send first context information to the second functional module, where the first context information includes a first identifier;

[0323] Obtain second context information from the second functional module, where the second context information includes a seventh identifier, and the first functional module generates a second identifier based on the seventh identifier;

[0324] Send first context information to the second functional module, where the second context information includes an eighth identifier, and the second functional module generates a first identifier based on the eighth identifier.

[0325] Wherein, the first identifier includes at least one of the following:

[0326] First globally unique temporary identifier GUTI;

[0327] Second mapped GUTI obtained from the first GUTI.

[0328] Wherein, the second identifier includes at least one of the following:

[0329] Second GUTI;

[0330] Second mapped GUTI obtained from the second GUTI;

[0331] Wherein, the seventh identifier includes a second GUTI.

[0332] Wherein, the eighth identifier includes a first GUTI.

[0333] Wherein, the first identifier is related to the third identifier.

[0334] Wherein, the second identifier is related to the fourth identifier.

[0335] Optionally, the first functional module 801 is further configured to: send first information to a first network function.

[0336] Wherein, the first information includes a first identifier and a second identifier.

[0337] As an example, the first identifier is the first mapped GUTI, and the second identifier is the second GUTI, or the first identifier is the first GUTI, and the second identifier is the second mapped GUTI.

[0338] Optionally, the first information further includes first indication information; wherein, the first indication information is used to indicate at least one of the following:

[0339] At least one of session merging, context merging, stopping the handover switch, stopping the steering, stopping the splitting, stopping the dual transmission, stopping the multi-transmission, and stopping the concurrent transmission;

[0340] Any one of stopping dual registration, maintaining dual registration, stopping multi-registration, maintaining multi-registration, stopping dual connection, stopping multi-connection, stopping dual access, stopping multi-access, maintaining dual connection, maintaining multi-connection, maintaining dual access, and maintaining multi-access.

[0341] Optionally, the first functional module 801 is further configured to: send at least one of the following to the second functional module:

[0342] Deregistration, local deregistration, maintaining registration, session release, local session release, session information.

[0343] Optionally, the first functional module 801 is further configured to: receive at least one of the following from the second functional module:

[0344] Deregistration, local deregistration, maintaining registration, session release, local session release, session information.

[0345] In addition, the first functional module is further configured to: perform at least one of the following:

[0346] Deregistration, local deregistration, releasing the session, locally releasing the session, maintaining registration.

[0347] Optionally, the first functional module 801 is further configured to: receive fourth indication information from the ninth network function.

[0348] Wherein, the sending of the first information to the first network function includes: sending the first information to the first network function based on the fourth indication information.

[0349] Wherein, the fourth indication information indicates at least one of the following:

[0350] Supporting context merging, supporting session merging, supporting registration mode conversion.

[0351] Since Figure 8 The device shown can register different networks through the first functional module 801 and the second functional module 802 respectively, exchange context information under the networks it has registered internally, and can perform operations such as deregistration, local deregistration, releasing the session, locally releasing the session, and maintaining registration. Therefore, when the connection under one network is updated or switched to another network, the number of connections under the same network can be reduced, thereby improving the communication efficiency of the terminal device applying the device.

[0352] The above introduced an information interaction method proposed in this application from the perspectives of the terminal device, the first network function, the second network function, the third network function, the fifth network function, and the ninth network function. Next, an information interaction method proposed in this application will be described from the perspectives of the terminal device and the interaction of each network function.

[0353] In one embodiment, an information interaction method provided in this application may include:

[0354] Step 1, the terminal device or the seventh network function sends first information to the first network function, where the first information includes a first identifier and a second identifier;

[0355] Step 2, the first network function receives the first information and performs a first operation based on the first context information and the second context information.

[0356] Wherein, the first operation includes at least one of the following:

[0357] 1) Generate, determine, or judge third context information;

[0358] 2) Send the third context information to the seventh network function;

[0359] 3) Perform a third operation;

[0360] 4) Send at least one of the following to the fourth network function:

[0361] Second information;

[0362] Third information and fourth information.

[0363] Wherein, the first context information is related to the first identifier; the second context information is related to the second identifier.

[0364] Wherein, the second information is used to indicate a third identifier or information associated with the third identifier.

[0365] Wherein, the third information includes a third identifier and a cancellation indication or a location cancellation indication.

[0366] Wherein, the fourth information includes a fourth identifier and a registration indication or a location update indication.

[0367] Wherein, the third identifier is related to the first identifier, and the fourth identifier is related to the second identifier.

[0368] Wherein, the third operation includes at least one of the following:

[0369] Instruct the fifth network function to create, update, or release a session or session context;

[0370] Indicate the eighth information to the fifth network function;

[0371] Indicate the eighth session information to the terminal device;

[0372] Indicate the third session information to the terminal device.

[0373] Wherein, the eighth information is used to indicate at least one of the following:

[0374] Session transfer, session handover, session merge, cancellation of traffic splitting, release of associated session, preparation for session transfer, preparation for session handover, preparation for session merge, preparation for cancellation of traffic splitting, preparation for release of associated session.

[0375] Wherein, the eighth session information is used for at least one of the following:

[0376] Establish a session based on the eighth session information;

[0377] Indicate an unaccepted session;

[0378] Indicate a released session.

[0379] Wherein, the third session information is used for at least one of the following:

[0380] Indicate an accepted session;

[0381] Indicate a held session.

[0382] Optionally, the above information interaction method may further include:

[0383] Step 3, the first network function sends second indication information to the second network function based on the first identifier, the second network function sends the first context information to the first network function based on the second indication information, and deletes or invalidates the first session information;

[0384] Step 4, the first network function sends second indication information to the third network function based on the second identifier, the third network function sends the second context information to the first network function based on the second indication information, and deletes or invalidates the second session information.

[0385] Wherein, the first session information is included in the first context information.

[0386] Wherein, the second session information is included in the second context information.

[0387] Optionally, the above information interaction method may further include:

[0388] Step 5, the fifth network function receives the eighth information indicated by the first network function.

[0389] Step 6, based on the eighth piece of information, the fifth network function instructs the eighth network function to forward data.

[0390] Wherein, the eighth piece of information is used to indicate at least one of the following:

[0391] Session transfer, session handover, session merging, cancellation of traffic splitting, release of associated session, preparation for session transfer, preparation for session handover, preparation for session merging, preparation for cancellation of traffic splitting, preparation for release of associated session.

[0392] Optionally, the above information interaction method may further include:

[0393] Step 7, the ninth network function performs any one of the following: broadcasting the fourth indication information, sending the fourth indication information to the terminal device.

[0394] Wherein, the fourth indication information indicates at least one of the following:

[0395] Support for context merging, support for session merging, support for registration mode conversion.

[0396] Correspondingly, the terminal device receives the fourth indication information and sends the first piece of information to the first network function based on the fourth indication information.

[0397] It should be noted that the information interaction method involving multi-party interaction corresponds to the information interaction method introduced from a single-sided perspective in the above text, and can achieve the same corresponding technical effects, so the description is relatively simple, and they can refer to each other.

[0398] In summary, by applying an information interaction method provided in an embodiment of the present application, when the terminal device is in a dual registration situation, if the connection under one network is switched, such that both connections are in the same network, or the device decides to enter a single transmission, the original service can be transmitted by one connection while maintaining continuity, improving the wireless efficiency and also saving power.

[0399] Next, a specific embodiment is used to illustrate an information interaction method provided by the present application.

[0400] It should be noted that in the following embodiments, the terminal device is a DualSteerDevice, which is a device with capabilities such as dual registration and dual-path transmission. The DualSteerDevice may include two Terminal Equipments (TEs): TE1 and TE2. The TE is similar to the UE in function and can also be regarded as a UE, specifically as a Modem of the UE. Alternatively, the DualSteerDevice can also be regarded as a UE, which at least includes an independent Modem and an independent SIM card.

[0401] It should also be noted that in the following embodiments, the first identifier may be a GUTI 1 / 5G-GUTI or a first mapped GUTI (additional GUTI / mapped GUTI) mapped from the GUTI 1 / 5G-GUTI; the second identifier may be a GUTI 2 / 4G-GUTI or a second mapped GUTI (additional GUTI / mapped GUTI) mapped from the GUTI 2 / 4G-GUTI; the third identifier may be SUPI1 or IMSI1, and the fourth identifier may be SUPI2 or IMSI2. The first context information is 5G context information, and the second context information is 4G context information.

[0402] Specific Embodiment 1 (Mobility Update from 4G (TE2) to 5G, becoming single access of TE1)

[0403] In Specific Embodiment 1, as Figure 9A shown, TE1 of the DualSteerDevice 8 has been registered in the 5G network based on SUPI1, and TE2 of the DualSteerDevice 8 has been registered in the 4G network based on SUPI2; the first network function is the first AMF11, the second network function is the second AMF 21, the third network function is the second MME 31, the fourth network function is the UDM 4, and the fifth network function or the sixth network function is the SMF 5.

[0404] As Figure 9A shown, in Specific Embodiment 1, an information interaction method provided in this application includes:

[0405] Step 1, TE1 in the DualSteerDevice 8 has been registered in the 5G network based on SUPI1, TE2 in the DualSteerDevice has been registered in the 4G network based on SUPI2, and TE2 may have established a session (PDN connection) in 4G.

[0406] Among them, TE1 accesses the 5G network through the 5G base station 9.

[0407] Among them, SUPI1 and SUPI2 can be different or the same.

[0408] Step 2, TE2 sends 4G context information to TE1.

[0409] Specifically, assume that the dual-boot device 8 needs to perform an inter-system mobility update from a 4G network to a 5G network. For example, the 4G network signal can no longer be used, and at the same time, it is desired to use only a single connection mode after moving to the 5G network, that is, there will be no complex situations such as two registrations and two connections in the 5G network. For this reason, TE2 sends 4G context information to TE1. The 4G context information may include: 4G GUTI or a mapped GUTI mapped from the 4G GUTI; optionally, the 4G context information may further include a security context; optionally, the 4G context information may further include 4G session or connection context, etc.

[0410] Step 3, TE1 in the dual-boot device 8 sends an inter-system mobility registration message (i.e., sends the first information) to the first AMF 11 in the 5G network, such as sending a Registration Request message. Among them, the Registration Request carries 5G-GUTI and / or a first mapped GUTI (additional GUTI), where 5G-GUTI is the GUTI obtained by the dual-boot device 8 during 5G registration, and additional GUTI is a mapped GUTI (obtained from TE2 or calculated from the information obtained from TE2); the Registration Request may also carry an inter-system mobility update indication (i.e., the first indication information), such as carrying an indication of "moving from EPC".

[0411] Step 4, optionally, the first AMF 11 may request the 5G context information (i.e., the first context information) of the dual-boot device 8 from the second AMF 21 based on the 5G-GUTI.

[0412] Specifically, the first AMF 11 may send a Namf_Communication_UEContextTransfer Request (i.e., the second indication information) carrying the 5G-GUTI (the first identifier) to the second AMF 21 to request the 5G context information.

[0413] Step 5, optionally, the second AMF 21 returns the 5G context information.

[0414] Among them, the 5G context information may include SUPI1 (the third identifier).

[0415] Optionally, the 5G context information may further include first session information (such as PDU session ID, related DNN, S-NSSAI, SMF information).

[0416] Optionally, the 5G context information may further include identification association information for indicating that the terminal device has an associated SUPI, for example, it may be indicated by carrying SUPI2.

[0417] Optionally, the 5G context information may further include session association information, such as the mapping relationship between (DNN, S-NSSAI) and APN, and the EPS bearer ID corresponding to the PDU session.

[0418] It can be understood that when the second AMF 21 and the first AMF 11 are the same AMF, steps 4 and 5 are internal operations.

[0419] Step 6, after step 3, the first AMF 11 obtains the 4G context information (i.e., the second context information) of the dual-boot device 8 in the 4G network from the second MME 31 based on the second mapped GUTI.

[0420] Specifically, the first AMF 11 may query the UE context corresponding to the second mapped GUTI in the second MME, for example, by sending a UEContext Transfer Request message for querying.

[0421] Among them, the 4G context information includes SUPI2 (the fourth identifier).

[0422] Optionally, the 4G context information may further include: second session information (such as PDU session ID, related DNN, S-NSSAI, SMF information).

[0423] Optionally, the 4G context information may further include identification association information for indicating that the terminal device has an associated SUPI, for example, it may be indicated by carrying SUPI2.

[0424] Optionally, the 4G context information may further include session association information, such as the mapping relationship between (DNN, S-NSSAI) and APN, and the EPS bearer ID corresponding to the PDU session.

[0425] Step 7, optionally, the first AMF 11 may request subscription information from the UDM 4 based on SUPI1 and / or SUPI2 obtained in steps 4 and 6, or at least one of the second session information, identification association information, and session association information obtained in step 6, or request subscription information based on the SUPI1 registered in 5G or the SUPI2 registered in 4G.

[0426] For example, call the Nudm_SDM_Get operation to request subscription information.

[0427] The UDM 4 returns the subscription information of SUPI1, which may include session association relationships, such as the mapping relationship between (DNN, S-NSSAI) and APN. The subscription information may also include identity association information.

[0428] Step 8: The first AMF 11 combines the 5G context information and the 4G context information into the third context information.

[0429] Optionally, the first AMF 11 associates the third context information with a SUPI, such as associating it with SUPI1 or SUPI2.

[0430] Specifically, the first AMF 11 can determine whether to combine the 5G context information and the 4G context information based on the identity association information and / or session association information in Step 5 or Step 7. If the associated SUPI for 5G registration is the SUPI for 4G registration, or the associated SUPI for 4G registration is the SUPI for 5G registration, or there is identity association information, then the first AMF 11 combines the 5G context information and the 4G context information. Conversely, if the associated SUPI for 5G registration is not the SUPI for 4G registration, or the associated SUPI for 4G registration is not the SUPI for 5G registration, or there is no identity association information, then the first AMF 11 can indicate registration rejection to the dual-boot device 8, or does not perform context combination, and indicates through Step 11 that the dual-boot device 8 has not combined the context.

[0431] Step 9a: Based on the third context information, the first AMF 11 determines whether it is necessary to create a new PDU session for SUPI1 in the 5G network (for example, based on the session association information, it is determined that a certain 4G session has no associated 5G session).

[0432] If necessary, the SMF 5 creates a PDU session for SUPI1 based on the 4G context information.

[0433] Specifically, for example, the first AMF 11 calls the NSMF 5_PDUSession_CreateSMContext operation, and the parameters may include indication information 1, indicating preparation for transfer / handover. After the creation of the PDU session is completed, the SMF 5 notifies (the specific notification information is the eighth information) the PGW-U or UPF to transmit the downlink data packets for the corresponding 4G session through the PDU session path of SUPI1, and the corresponding 4G session no longer transmits downlink data. This operation can be based on the indication information 1.

[0434] Step 9b, the first AMF 11 may also determine, based on the third context information (such as the session association information in the third context information), that a certain 4G session has a 5G session associated therewith, and then instruct the SMF 5 to update the PDU session of SUPI1. For example, it calls the NSMF 5_PDUSession_UpdateSMContext operation, and the parameters may include indication information 1 or 2. Indication information 2 indicates transfer / handoff. The SMF 5 notifies (the specific notification information is the eighth information) the PGW-U or UPF to transmit the downlink data packets for the corresponding 4G session from the PDU session path of SUPI1, and the corresponding 4G session no longer transmits downlink data. This operation may be based on indication information 1 or 2.

[0435] Another embodiment of steps 8 and 9 is that step 9 is executed first and then step 8 is executed, specifically as follows:

[0436] Step 9, the first AMF 11 creates a new PDU session for SUPI1 in 5G based on all 4G session information in the 4G context information. The session creation request may carry identification association information. For example, by carrying SUPI2 or carrying indication information, the SMF 5 may decide whether to create a PDU session based on the identification association information and the local session association information, and return the result to the first AMF 11.

[0437] Step 8, the first AMF 11 merges the 5G context information and the 4G context information based on the returned result, that is, when there are the same sessions (with an association relationship, or the returned result during creation indicates an existing associated session, failure, etc.), the 5G PDU session is retained while the 4G PDN connection or EPS bearer is invalidated.

[0438] Step 10, when the first AMF 11 is not the second AMF 21, the first AMF 11 indicates the registered AMF to the UDM 4 for the SUPI1 registered in 5G.

[0439] The purpose of step 10 is to record the serving AMF information of SUPI1 in the UDM 4.

[0440] Step 11, the first AMF 11 sends a registration acceptance message to the dual-boot device 8, such as sending a RegistrationAccept message. Among them, the registration acceptance message may carry indication information for instructing the dual-boot device 8 to perform at least one of the following: merging the 5G context information and the 4G context information, 5G or 4G related information (such as indicating registration using 5G, 5G RAT type indicating registration using 5G, PLMN ID of the 5G network indicating registration using 5G, etc.). Among them, PLMN refers to the Public Land Mobile Network.

[0441] Step 12, TE1 in the dual-boot device 8 combines the original 5G context information and 4G context information into 5G context information. Optionally, TE1 sends a deregistration indication to TE2 to indicate at least one of local deregistration of the 4G context and exiting the 4G registration state, or TE1 sends 5G context information without session content to TE2, and TE2 maintains 5G registration but has no session.

[0442] In the combined 5G context information, only one associated session is retained. For example, if two sessions have the same PDU session ID or EPS bearer ID, they are associated sessions. Optionally, the 4G security context may not be included in the combination, that is, only the 5G security context is retained. In one embodiment, single registration is not entered, so there are two 5G context information, one of which has no session context; in another embodiment, single registration is entered, so there is only one 5G context information, the device enters the 5G single registration (SUPI1 registration) state, and the dual-boot device 8 deregisters the 4G context information and exits the 4G registration state locally for at least one of them.

[0443] Step 13, optionally (for example, when dual registration is no longer required), after step 10, the first AMF 11 also instructs the UDM 4 to deregister the SUPI2 for 4G registration.

[0444] Step 14, optionally, link two registrations.

[0445] Specifically, after step 10, the UDM 4 learns about the service network element registration situation of the dual-boot device 8 based on the indication information in step 10, or after step 13, the UDM 4 learns about the service network element registration situation of the dual-boot device 8.

[0446] Among them, the service network element registration situation of the dual-boot device 8 may include at least one of the following:

[0447] Register MME / AMF;

[0448] Register MME / AMF associated with SUPI.

[0449] It can be understood that in the case where SUPI1 and SUPI2 are the same, there is one registration of MME and one registration of AMF for SUPI.

[0450] Optionally, when the dual-boot device 8 establishes two registrations using two different SUPIs, after step 10, step 16 is executed to notify the second AMF 21 of deregistration, and after step 13, step 15 is executed to notify the second MME 31 of deregistration. When the two registrations of the dual-boot device 8 on the network side are based on the same SUPI, step 13 is not executed, step 10 carries a single-registration indication, the UDM 4 deregisters the second MME 31, and if the first AMF 11 registered in step 10 is not an existing registration in the UDM 4 (the first AMF 11 is not the second AMF 21), then step 16 is executed to deregister the second AMF 21.

[0451] In step 15, the UDM 4 may perform a deregistration operation based on the association result of step 14 to deregister the registration of the dual-boot device 8 on the second MME 31 based on SUPI2.

[0452] In step 16, the UDM 4 notifies the second AMF 21 of deregistration to deregister the registration of the dual-boot device 8 on the second AMF based on SUPI1.

[0453] Specific Embodiment 2 (Mobility Update from 4G (TE2) to 5G, Becoming TE2 Single-Access)

[0454] In Specific Embodiment 2, as Figure 9B shown, the TE1 of the dual-boot device 8 has been registered in the 5G network based on SUPI1, and the TE2 of the dual-boot device 8 has been registered in the 4G network based on SUPI2; the first network function is the first AMF11, the second network function is the second AMF 21, the third network function is the second MME 31, the fourth network function is the UDM 4, and the fifth network function or the sixth network function is the SMF 5.

[0455] As Figure 9B shown, in Specific Embodiment 2, an information interaction method provided by the present application may include:

[0456] In step 1, the TE1 in the dual-boot device 8 has been registered in the 5G network based on SUPI1, the TE2 in the dual-boot device has been registered in the 4G network based on SUPI2, and the TE2 may have established a session (PDN connection) in 4G.

[0457] Among them, the TE1 accesses the 5G network through the 5G base station 9.

[0458] Among them, SUPI1 and SUPI2 may be different or the same.

[0459] In step 2, the TE2 requests 5G context information from the TE1.

[0460] Specifically, assume that the dual-boot device 8 needs to perform an inter-system mobility update from a 4G network to a 5G network. For example, the 5G network signal can no longer be used, and it is desired to use only a single connection mode after moving to the 4G network, that is, there will be no complex situations such as two registrations and two connections in the 4G network. For this purpose, TE2 requests 5G context information from TE1. The 5G context information may include: 5G GUTI or a mapped GUTI obtained by mapping the 5G GUTI; optionally, the 5G context information may further include a security context; optionally, the 5G context information may further include 5G session or connection context, etc.

[0461] Step 3, TE2 in the dual-boot device 8 sends an inter-system mobility registration message (i.e., sends the first information) to the first AMF 11 in the 4G network, such as sending a Registration Request message. Among them, the Registration Request carries 5G-GUTI and / or the first mapped GUTI (additional GUTI), where 5G-GUTI is the GUTI obtained by the dual-boot device 8 during 5G registration, and additional GUTI is the mapped GUTI (obtained from TE2 or calculated from the information obtained from TE2); the Registration Request may also carry an inter-system mobility update indication (i.e., the first indication information), such as carrying an indication of "moving from EPC".

[0462] Step 4, after step 3, the first AMF 11 obtains the 4G context information (i.e., the second context information) of the dual-boot device 8 in the 4G network based on the second mapped GUTI from the second MME 31.

[0463] Specifically, the first AMF 11 may query the UE context corresponding to the second mapped GUTI in the second MME, such as sending a UEContext Transfer Request message for querying.

[0464] Among them, the 4G context information includes SUPI2 (the fourth identifier).

[0465] Optionally, the 4G context information may further include: second session information (such as PDU session ID, related DNN, S-NSSAI, SMF information).

[0466] Optionally, the 4G context information may further include identification association information for indicating that the terminal device has an associated SUPI, such as it may be indicated by carrying SUPI2.

[0467] Optionally, the 4G context information may further include session association information, such as the mapping relationship between (DNN, S-NSSAI) and APN, and the EPS bearer ID corresponding to the PDU session.

[0468] Step 5. Optionally, the first AMF 11 may request the 5G context information (i.e., the first context information) of the dual-boot device 8 from the second AMF 21 based on the 5G-GUTI.

[0469] Specifically, the first AMF 11 may send a Namf_Communication_UEContextTransfer Request (i.e., the second indication information) carrying the 5G-GUTI (the first identifier) to the second AMF 21 to request the 5G context information.

[0470] Step 6. Optionally, the second AMF 21 returns the 5G context information.

[0471] Among them, the 5G context information may include SUPI1 (the third identifier).

[0472] Optionally, the 5G context information may further include the first session information (such as the PDU session ID, related DNN, S-NSSAI, SMF information).

[0473] Optionally, the 5G context information may further include identification association information for indicating that the terminal device has an associated SUPI, such as by carrying SUPI2 for indication.

[0474] Optionally, the 5G context information may further include session association information, such as the mapping relationship between (DNN, S-NSSAI) and APN, and the EPS bearer ID corresponding to the PDU session.

[0475] It can be understood that when the second AMF 21 and the first AMF 11 are the same AMF, steps 4 and 5 are internal operations.

[0476] Step 7. Optionally, the first AMF 11 may request the subscription information from the UDM 4 based on SUPI1 and / or SUPI2 obtained in steps 4 and 6, or at least one of the second session information, identification association information, and session association information obtained in step 6, or request the subscription information based on the SUPI1 registered in 5G or the SUPI2 registered in 4G.

[0477] For example, call the Nudm_SDM_Get operation to request the subscription information.

[0478] The UDM 4 returns the subscription information of SUPI1, which may include session association relationships, such as the mapping relationship between (DNN, S-NSSAI) and APN. The subscription information may also include identification association information.

[0479] Step 8: The first AMF 11 combines the 5G context information and the 4G context information into the third context information.

[0480] Optionally, the first AMF 11 associates the third context information with a SUPI, such as associating it with SUPI1 or SUPI2.

[0481] Specifically, the first AMF 11 may determine whether to combine the 5G context information and the 4G context information based on the identification association information and / or the session association information in Step 5 or Step 7. If the associated SUPI of the 5G registration is the SUPI of the 4G registration, or the associated SUPI of the 4G registration is the SUPI of the 5G registration, or there is identification association information, then the first AMF 11 combines the 5G context information and the 4G context information. Conversely, if the associated SUPI of the 5G registration is not the SUPI of the 4G registration, or the associated SUPI of the 4G registration is not the SUPI of the 5G registration, or there is no identification association information, then the first AMF 11 may indicate registration rejection to the dual-boot device 8, or not perform context combination, and indicate through Step 11 that the dual-boot device 8 has not combined the context.

[0482] Step 9: The first AMF 11 creates a new PDU session in 5G for all 4G sessions of SUPI2, and then based on the combined context, determines whether an additional PDU session needs to be created in 5G for SUPI2 (such as determining that a certain 5G session has no associated 4G session based on the session association information). If so, it instructs the SMF5 to create a PDU session for SUPI2, such as invoking the Nsmf_PDUSession_CreateSMContext operation, and the parameters may include indication information 1 indicating preparation for handover / switching. After the creation of this PDU session is completed, the SMF5 notifies the PGW-U (UPF) to transmit the downlink data packets for the corresponding 4G session through the PDU session path of SUPI2, and the corresponding 4G session no longer transmits downlink data. This operation may be based on the indication information 1.

[0483] Another embodiment of Steps 8 and 9 is that Step 9 is executed first and then Step 8, specifically as follows:

[0484] Step 9: The first AMF 11 creates a PDU session for SUPI2 in 5G for all 5G sessions of SUPI1, which can carry identification association information. For example, by carrying the SUPI1 indication, the SMF5 can decide whether to create a PDU session based on the identification association information and the local session association information, and return the result to the first AMF 11.

[0485] Step 8: The first AMF 11 merges the two contexts based on the returned result, that is, when there are the same sessions (with an association relationship, or the returned result at creation indicates an existing associated session, failure, etc.), the 5G PDU session is retained while the 4G PDN connection or EPS bearer is invalidated.

[0486] Step 10: When the first AMF 11 is not the second AMF 21, the first AMF 11 indicates the registered AMF to the UDM 4 for the SUPI2 registered in 5G.

[0487] The purpose of Step 10 is to record the serving AMF information of SUPI1 in the UDM 4.

[0488] Step 11: The first AMF 11 sends a registration acceptance message to the dual-boot device 8, such as sending a RegistrationAccept message. Among them, the registration acceptance message can carry indication information for instructing the dual-boot device 8 to perform at least one of the following: merging 5G context information and 4G context information, 5G or 4G related information (such as indicating registration using 5G, 5G RAT type indicating registration using 5G, PLMN ID of the 5G network indicating registration using 5G, etc.).

[0489] Step 12: The TE2 in the dual-boot device 8 merges the original 5G context information and 4G context information into 5G context information. Optionally, the TE2 sends a deregistration indication to the TE1 for instructing at least one of the following: locally deregistering the 5G context, exiting the 5G registration state, or the TE2 sends 5G context information without session content to the TE1, and the TE1 maintains 5G registration but has no session.

[0490] In the merged 5G context information, only one associated session is retained. For example, if two sessions have the same PDU session ID or EPS bearer ID, they are associated sessions. Optionally, the 4G security context may not be included in the merge, that is, only the 5G security context is retained. One embodiment is not to enter single registration, then there are two 5G context information, one of which has no session context; another embodiment is to enter single registration, then there is only one 5G context information, the device enters the 5G single registration (SUPI2 registration) state, and the dual-boot device 8 deregisters the 4G context information and exits the 4G registration state locally for at least one of them.

[0491] Step 13, optionally (for example, when dual registration is not required), after step 10, the first AMF 11 also instructs the UDM 4 to cancel the registration for the 5G registered SUPI1.

[0492] Step 14, optionally, link two registrations.

[0493] Specifically, after step 10, based on the indication information in step 10, the UDM 4 learns about the service network element registration status of the dual-boot device 8, or after step 13, the UDM 4 learns about the service network element registration status of the dual-boot device 8.

[0494] Among them, the service network element registration status of the dual-boot device 8 may include at least one of the following:

[0495] Register with MME / AMF;

[0496] Register with MME / AMF associated with SUPI.

[0497] It can be understood that when SUPI1 and SUPI2 are the same, there is a registration with one MME and one AMF for SUPI.

[0498] Optionally, when the dual-boot device 8 establishes two registrations using two different SUPIs, after step 10, step 16 is executed to notify the second AMF 21 to cancel the registration, and after step 13, step 15 is executed to notify the second MME 31 to cancel the registration. When the two registrations of the dual-boot device 8 on the network side are based on the same SUPI, step 13 is not executed, and step 10 carries a single registration indication. The UDM 4 cancels the second MME 31. If the first AMF 11 registered in step 10 is not the existing registration in the UDM 4 (the first AMF 11 is not the second AMF 21), then step 16 is executed to cancel the second AMF 21.

[0499] Step 15, the UDM 4 can perform a cancellation operation based on the association result of step 14 to cancel the registration of the dual-boot device 8 with the second MME 31 based on SUPI2.

[0500] Step 16, the UDM 4 notifies the second AMF 21 to cancel the registration to cancel the registration of the dual-boot device 8 with the second AMF based on SUPI1.

[0501] Specific Embodiment 3 (5G (TE1) to 4G mobility update, changing to TE2 or TE2 single access)

[0502] In Specific Embodiment 3, as Figure 9CAs shown, TE1 of the dual-boot device 8 has been registered in the 5G network based on SUPI1, and TE2 of the dual-boot device 8 has been registered in the 4G network based on SUPI2; the first network function is the first MME 12, the second network function is the second AMF 21, the third network function is the second MME 31, the fourth network function is the UDM 4, and the fifth network function or the sixth network function is the SMF 5.

[0503] As Figure 9C shown, in the third specific embodiment, an information interaction method provided by the present application may include:

[0504] Step 1, the dual-boot device 8 has been registered in the 4G network based on SUPI2 (it may be that TE2 of the dual-boot device 8 is registered in the 4G network), and the dual-boot device 8 has also been registered in the 5G network based on SUPI1 and may have established a session (PDU session) in the 5G network (it may be that TE1 is registered and has established a session in the 5G network). SUPI1 and SUPI2 may be different or the same.

[0505] Among them, TE2 accesses the 4G network through the 4G base station 10.

[0506] Step 2, the dual-boot device 8 first performs an inter-system mobility update from 5G to 4G.

[0507] For example, if the 5G signal can no longer be used and it is desired to use only a single connection mode after moving to the 4G network, that is, there will not be a complex situation of two registrations and two connections in the 4G network. The dual-boot device 8 first performs a 4G to 5G mobility update in the manner of the first specific embodiment described above and becomes a single 5G registration of (TE1), or first performs a 4G to 5G mobility update in the manner of the second specific embodiment described above and becomes a single 5G registration of (TE2). Different from the first specific embodiment, TE1 requests 4G context information from TE2. Different from the second specific embodiment, TE1 sends 5G context information to TE2. Assume that after the mobility update is completed, the context of the dual-boot device 8 is in Figure 9C the second AMF 21.

[0508] Step 3, after step 2, there is only one copy of the context in the network (not stored in two places - the second MME 31 and the second AMF 21), and there is only one connection from the dual-boot device 8 to the network. It then performs an inter-system mobility update process from 5G to 4G according to the existing calculation, that is, the mobility update from 5G (TE1) to 4G can be achieved and it becomes a single access of TE2 or TE2.

[0509] Specific embodiment four (mobility update from 5G (TE1) to 4G, becoming a single access of TE1)

[0510] In the fourth specific embodiment, as Figure 9D shown, the TE1 of the dual-boot device 8 has been registered in the 5G network based on SUPI1, and the TE2 of the dual-boot device 8 has been registered in the 4G network based on SUPI2; the seventh network function is the first MME 12, the first network function is the second AMF 21, the third network function is the second MME 31, the fourth network function is the UDM 4, and the fifth network function or the sixth network function is the SMF 5.

[0511] As Figure 9D shown, in the fourth specific embodiment, an information interaction method provided by the present application includes:

[0512] Step 1, the TE1 in the dual-boot device 8 has been registered in the 5G network based on SUPI1, the TE2 in the dual-boot device has been registered in the 4G network based on SUPI2, and the TE1 may have established a session (PDU session) in 5G.

[0513] Among them, the TE2 accesses the 4G network through the 4G base station 10.

[0514] Among them, SUPI1 and SUPI2 may be different or the same.

[0515] Step 2, the TE1 requests 4G context information from the TE2.

[0516] Specifically, assume that the dual-boot device 8 needs to perform an inter-system mobility update from the 5G network to the 4G network, for example, the 5G network signal can no longer be used, and at the same time, it is desired to use only a single connection method after moving to the 4G network, that is, there will be no complex situation of two registrations and two connections in the 4G network. For this reason, the TE1 requests 4G context information from the TE2, and the 4G context information may include: 4G GUTI or mapped GUTI mapped from the 4G GUTI; optionally, the 4G context information may further include a security context; optionally, the 4G context information may further include 4G session or connection context, etc.

[0517] Step 3, TE1 in the dual-boot device 8 sends a cross-system mobility registration message (i.e., sends the first information) to the first MME 12 in the 5G network. For example, it sends a Tracking Area Update Request (TAU Request) message. Among them, at least one of 5G-GUTI (from TE1), the second mapped GUTI (4G-GUTI, from TE2), and additional GUTI is carried in the TAU Request. Among them, 4G-GUTI is the mapped GUTI (calculated from the 5G-GUTI obtained by TE1 in 5G), and additional GUTI is the GUTI obtained when the dual-boot device 8 is registered in 4G (4G context information from TE2) or the mapped 5G-GUTI mapped from this 4G-GUTI. Optionally, the TAU Request may also carry a cross-system mobility update indication, such as an indication of "moving from 5GC". The dual-boot device 8 sends a TAU message based on the 5G security context information.

[0518] Step 4, optionally, the first MME 12 may request the 4G context information (i.e., the second context information) of the dual-boot device 8 from the second AMF 21 based on the 4G-GUTI or the second mapped GUTI. That is, the first network function receives the first information from the seventh network function.

[0519] Specifically, the first MME 12 may send a ContextTransfer Request carrying 4G-GUTI (the second identifier) to the second AMF 21 to request 4G context information.

[0520] Step 5, after receiving the first information, the second AMF 21 requests the 4G context information (i.e., the second context information) of the dual-boot device 8 from the second MME 31 based on the 4G-GUTI. Optionally, the second MME 31 returns the 4G context information.

[0521] Among them, the 4G context information may include SUPI2 (the third identifier).

[0522] Optionally, the 4G context information may also include the first session information (such as PDU session ID, related DNN, S-NSSAI, SMF information).

[0523] Optionally, the 4G context information may also include identification association information for indicating that the terminal device has an associated SUPI, such as by carrying SUPI1 for indication.

[0524] Optionally, the 4G context information may further include session association information, such as the mapping relationship between (DNN, S-NSSAI) and APN, and the EPS bearer ID corresponding to the PDU session.

[0525] It should be noted that the 5G context information (i.e., the first context information) of the dual-boot device 8 is stored locally in the second AMF 21.

[0526] Step 6, optionally, the second AMF 21 requests subscription information from the UDM 4.

[0527] Specifically, if the SUPI in the 4G context information obtained in step 5 is different from the SUPI in the locally saved 5G context information, or the locally saved 5G context information includes at least one of session information, identity association information, and session association information, the second AMF 21 requests subscription information from the UDM 4. For example, it requests subscription information from the UDM 4 based on the SUPI1 for 5G registration, such as invoking the Nudm_SDM_Get operation. Of course, it can also request subscription information based on the SUPI2 for 4G registration. The UDM 4 returns the subscription information for SUPI1, and the subscription information may include session association relationships, such as the mapping relationship between (DNN, S-NSSAI) and APN, and the subscription information may also include identity association information.

[0528] Step 7, optionally, the second AMF 21 requests the first session information from the SMF 5 based on the 5G context information.

[0529] For example, the second AMF 21 invokes Nsmf_PDUSession_ContextRequest and carries SUPI1 in the request; the request may also carry indication information 1 for indicating preparation for handover / transfer; the request may also carry identity association information, such as SUPI2 or information indicating identity association. The SMF 5 may return an association result to the second AMF based on the identity association information (local or received) and the local session association information. For example, for a PDU session with a 4G associated session, it returns the PDU session information and session association information, or it may not return the PDU session information.

[0530] Step 8, the second AMF 21 merges the 5G context information and the 4G context information into the third context information.

[0531] Optionally, the second AMF 21 associates the third context information with a SUPI, such as associating it with SUPI1 or SUPI2.

[0532] Specifically, based on the local 5G context information and the 4G context information obtained in step 5, the second AMF 21 merges the 4G and 5G context information into a UE context, and associates the merged UE context with a SUPI (such as the SUPI1 registered for 5G). The second AMF 21 can determine whether to merge the two contexts based on the 4G context information in step 5 and the identification association information and / or session association information in step 7 (if step 7 does not return PDU session information due to the association of a 4G session with a PDU session, the merge operation has no information related to the PDU session information). Optionally, if the associated SUPI registered for 5G is not the SUPI registered for 4G, or the associated SUPI registered for 4G is not the SUPI registered for 5G, or there is no identification association information, the second AMF 21 can return an error indication to the first MME 12, ultimately resulting in the rejection of the registration.

[0533] Step 9, the second AMF 21 returns the merged context information to the first MME 12, and the context information may include SUPI1.

[0534] Step 10, the first MME 12 indicates to the UDM 4 to register the first MME for the SUPI1 registered for 4G.

[0535] The purpose of step 10 is to record the serving MME information of SUPI1 in the UDM 4.

[0536] Step 11, the first MME 12 sends a TAU acceptance message to the dual-boot device 8, such as sending a TAU Accept message.

[0537] Among them, the TAU acceptance message can carry indication information for instructing the dual-boot device 8 to perform at least one of the merging of 5G context information and 4G context information, 5G- or 4G-related information (such as indicating registration for 5G, 5G RAT type indicating registration for 5G, PLMN ID of the 5G network indicating registration for 5G, etc.). Among them, PLMN refers to the Public Land Mobile Network.

[0538] Step 12, the TE1 in the dual-boot device 8 merges the original 5G context information and 4G context information into 4G context information.

[0539] Optionally, the TE1 sends a deregistration indication to the TE2 for instructing at least one of local deregistration of the 5G context and exiting the 5G registration state. The TE1 maintains 4G single registration, or the TE1 sends 4G context information without session content to the TE2, and the TE2 maintains 4G registration but has no session.

[0540] In the merged 5G context information, only one associated session is retained. For example, if two sessions have the same PDU session ID or EPS bearer ID, they are associated sessions. Optionally, the 5G security context is not merged, that is, only the 4G security context is retained. Optionally, in one embodiment, single registration is not entered, so there are two 4G context information, one of which has no session context; in another embodiment, single registration is entered, so there is only one 4G context information, and the device enters the 4G single registration (SUPI1 registration) state, and the dual-boot device 8 deregisters at least one of the 5G context information and locally exits the 5G registration state.

[0541] Step 13, optionally, after step 10, the first MME 12 also instructs the UDM 4 to deregister the SUPI2 for 4G registration.

[0542] Step 14, optionally, link two registrations.

[0543] Specifically, after step 10, the UDM 4 learns about the service network element registration status of the dual-boot device 8 based on the indication information in step 10, or after step 13, the UDM 4 learns about the service network element registration status of the dual-boot device 8.

[0544] Among them, the service network element registration status of the dual-boot device 8 may include at least one of the following:

[0545] Registered MME / AMF;

[0546] Registered MME / AMF associated with SUPI.

[0547] It can be understood that in the case where SUPI1 and SUPI2 are the same, there is one registration of MME and one registration of AMF for SUPI.

[0548] Optionally, when the dual-boot device 8 establishes two registrations using two different SUPIs, step 16 is executed after step 10 to notify the second AMF 21 to deregister, and step 15 is executed after step 13 to notify the second MME 31 to deregister. In the case where the two registrations of the dual-boot device 8 on the network side are based on the same SUPI, step 13 is not executed, step 10 carries a single registration indication, the UDM 4 deregisters the second MME 31, and if the first MME 12 registered in step 10 is not the existing registration in the UDM 4 (the first MME 12 is not the second AMF 21), then step 16 is executed to deregister the second AMF 21.

[0549] Step 15, the UDM 4 can perform a deregistration operation based on the association result of step 14 to deregister the registration of the dual-boot device 8 on the second MME 31 based on SUPI2.

[0550] Step 16, the UDM 4 notifies the second AMF 21 of deregistration to deregister the dual-boot device 8's registration with the second AMF based on SUPI1.

[0551] Specific Embodiment Five (5G (TE1) to 4G Mobility Update, Becoming TE2 Single-Access)

[0552] In Specific Embodiment Five, as Figure 9E shown, the TE1 of the dual-boot device 8 has been registered in the 5G network based on SUPI1, and the TE2 of the dual-boot device 8 has been registered in the 4G network based on SUPI2; the seventh network function is the first MME 12, the first network function is the second AMF 21, the third network function is the second MME 31, the fourth network function is the UDM 4, and the fifth network function or the sixth network function is the SMF 5.

[0553] As Figure 9E shown, in Specific Embodiment Five, an information interaction method provided by the present application includes:

[0554] Step 1, the TE1 in the dual-boot device 8 has been registered in the 5G network based on SUPI1, the TE2 in the dual-boot device has been registered in the 4G network based on SUPI2, and the TE1 may have established a session (PDU session) in 5G.

[0555] Among them, the TE2 accesses the 4G network through the 4G base station 10.

[0556] Among them, SUPI1 and SUPI2 may be different or the same.

[0557] Step 2, the TE1 sends 5G context information to the TE2.

[0558] Specifically, assume that the dual-boot device 8 needs to perform an inter-system mobility update from the 5G network to the 4G network, for example, the 5G network signal can no longer be used, and at the same time, it is desired to use only a single connection mode after moving to the 4G network, that is, there will be no complex situation of two registrations and two connections in the 4G network. For this reason, the TE1 sends 5G context information to the TE2, and the 5G context information may include: 5G GUTI or the mapped GUTI mapped from the 5G GUTI; optionally, the 5G context information may further include a security context; optionally, the 5G context information may further include a 5G session or connection context, etc.

[0559] Step 3, TE2 in the dual-boot device 8 sends a cross-system mobility registration message (i.e., sends the first information) to the first MME 12 over the 4G network, such as sending a Tracking Area Update Request (TAU Request) message. Among them, the Tracking Area Update Request carries at least one of the first mapped GUTI (from TE1), 4G-GUTI (4G-GUTI, from TE2), and additional GUTI. Among them, 4G-GUTI is a mapped GUTI (calculated from the 5G-GUTI obtained by TE1 in 5G), and additional GUTI is the GUTI obtained when the dual-boot device 8 is registered in 4G (4G context information from TE2) or the mapped 5G-GUTI mapped from this 4G-GUTI.

[0560] Optionally, the Tracking Area Update Request may also carry a cross-system mobility update indication, such as carrying an indication of "moving from 5GC". The dual-boot device 8 sends a TAU message based on the 5G security context information.

[0561] Step 4, optionally, the first MME 12 may request the 4G context information (i.e., the second context information) of the dual-boot device 8 from the second AMF 21 based on the 4G-GUTI or the second mapped GUTI. That is, the first network function receives the first information from the seventh network function.

[0562] Specifically, the first MME 12 may send a ContextTransfer Request carrying the 4G-GUTI (the second identifier) to the second AMF 21 to request 4G context information.

[0563] Step 5, after receiving the first information, the second AMF 21 requests the 4G context information (i.e., the second context information) of the dual-boot device 8 from the second MME 31 based on the 4G-GUTI. Optionally, the second MME 31 returns the 4G context information.

[0564] Among them, the 4G context information may include SUPI2 (the third identifier).

[0565] Optionally, the 4G context information may also include the first session information (such as PDU session ID, related DNN, S-NSSAI, SMF information).

[0566] Optionally, the 4G context information may also include identification association information for indicating that the terminal device has an associated SUPI, such as by carrying SUPI1 for indication.

[0567] Optionally, the 4G context information may further include session association information, such as the mapping relationship between (DNN, S-NSSAI) and APN, and the EPS bearer ID corresponding to the PDU session.

[0568] It should be noted that the 5G context information (i.e., the first context information) of the dual-boot device 8 is stored locally in the second AMF 21.

[0569] Step 6, optionally, the second AMF 21 requests subscription information from the UDM 4.

[0570] Specifically, when the SUPI in the 4G context information obtained in step 5 is different from the SUPI in the locally stored 5G context information, or the locally stored 5G context information includes at least one of session information, identity association information, and session association information, the second AMF 21 requests subscription information from the UDM 4. For example, it requests subscription information from the UDM 4 based on the SUPI2 in the 4G context information, such as invoking the Nudm_SDM_Get operation. Of course, it can also request subscription information based on the SUPI1 registered in 5G. The UDM 4 returns the subscription information of SUPI2, which may include session association relationships, such as the mapping relationship between (DNN, S-NSSAI) and APN, and the subscription information may also include identity association information.

[0571] Step 7, optionally, the second AMF 21 requests the first session information from the SMF 5 based on the 5G context information.

[0572] For example, the second AMF 21 invokes Nsmf_PDUSession_ContextRequest and carries SUPI1 in this request; the request may also carry indication information 1 for indicating preparation for handover / transfer; the request may also carry identity association information, such as SUPI2 or information indicating identity association. The SMF 5 can return an association result to the second AMF based on the identity association information (local or received) and the local session association information. For example, for a PDU session with a 4G associated session, it returns the information of the PDU session and session association information, or it may not return the PDU session information.

[0573] Step 8, the second AMF 21 merges the 5G context information and the 4G context information into the third context information.

[0574] Optionally, the second AMF 21 associates the third context information with a SUPI, such as associating it with SUPI1 or SUPI2.

[0575] Specifically, based on the local 5G context information and the 4G context information obtained in step 5, the second AMF 21 merges the 4G and 5G context information into a UE context and associates the merged UE context with a SUPI (such as the 5G-registered SUPI1). The second AMF 21 can determine whether to merge the two contexts based on the 4G context information in step 5 and the identification association information and / or session association information in step 7 (if step 7 does not return PDU session information because there is an associated 4G session for the PDU session, the merge operation has no information related to the PDU session information). Optionally, if the associated SUPI registered for 5G is not the SUPI registered for 4G, or the associated SUPI registered for 4G is not the SUPI registered for 5G, or there is no identification association information, the second AMF 21 can return an error indication to the first MME 12, ultimately resulting in the rejection of the registration.

[0576] Step 9, the second AMF 21 returns the merged context information to the first MME 12, and the context information may include SUPI1.

[0577] Step 10, in the case where the first MME 12 is different from the second MME 31, the first MME 12 indicates to the UDM 4 to register the first MME for the 4G-registered SUPI1.

[0578] The purpose of step 10 is to record the serving MME information of SUPI2 in the UDM 4.

[0579] Step 11, the first MME 12 sends a TAU acceptance message to the dual-boot device 8, such as sending a TAU Accept message.

[0580] Among them, the TAU acceptance message can carry indication information for instructing the dual-boot device 8 to perform at least one of the merging of 5G context information and 4G context information, 5G- or 4G-related information (such as indicating to use 5G registration, 5G RAT type indicating to use 5G registration, PLMN ID of the 5G network indicating to use 5G registration, etc.). Among them, PLMN refers to the Public Land Mobile Network.

[0581] Step 12, the TE1 in the dual-boot device 8 merges the original 5G context information and 4G context information into 4G context information.

[0582] Optionally, TE2 sends a deregistration indication to TE1 to indicate at least one of local deregistration of the 5G context and exiting the 5G registration state. TE1 maintains 4G single registration, or TE1 sends 4G context information without session content to TE2, and TE2 maintains 4G registration but has no session.

[0583] In the merged 5G context information, only one associated session is retained. For example, if two sessions have the same PDU session ID or EPS bearer ID, they are associated sessions. Optionally, the 5G security context is not included in the merge, that is, only the 4G security context is retained. Optionally, in one embodiment, single registration is not entered, so there are two 4G context information, one of which has no session context; in another embodiment, single registration is entered, so there is only one 4G context information, the device enters the 4G single registration (SUPI2 registration) state, and the dual-boot device 8 deregisters at least one of the 5G context information and local exits from the 5G registration state.

[0584] Step 13, optionally, after step 10, the second AMF 12 also indicates deregistration to the UDM 4 for the SUPI1 registered for 5G.

[0585] Step 14, optionally, link two registrations.

[0586] Specifically, after step 10, the UDM 4 learns about the service network element registration situation of the dual-boot device 8 based on the indication information in step 10, or after step 13, the UDM 4 learns about the service network element registration situation of the dual-boot device 8.

[0587] Among them, the service network element registration situation of the dual-boot device 8 may include at least one of the following:

[0588] Register with MME / AMF;

[0589] The MME / AMF associated with the SUPI registration.

[0590] Step 15, when the dual-boot device 8 establishes two registrations using two different SUPIs, step 15 is executed after step 10 to notify deregistration to the second MME 31 to deregister the registration of the dual-boot device 8 with the second MME 31 based on SUPI2.

[0591] Specific Embodiment Six (Handover from 4G (TE2) to 5G, becoming TE1 single access)

[0592] In Specific Embodiment Six, as Figure 9FAs shown, the TE1 of the dual-boot device 8 has been registered in the 5G network based on SUPI1, and the TE2 of the dual-boot device 8 has been registered in the 4G network based on SUPI2; the first network function is the first AMF11, the second network function is the second AMF 21, the third network function is the second MME 31, the fourth network function is the UDM 4, and the fifth network function or the sixth network function is the SMF 5.

[0593] As Figure 9F shown, in the sixth specific embodiment, an information interaction method provided by the present application includes:

[0594] Step 1a, the TE1 in the dual-boot device 8 has been registered in the 5G network based on SUPI1, the TE2 in the dual-boot device has been registered in the 4G network based on SUPI2, and the TE2 may have established a session (PDN connection) in the 4G network.

[0595] Among them, the TE1 accesses the 5G network through the 5G base station 9, and the TE1 accesses the 5G network through the 4G base station 10.

[0596] Among them, SUPI1 and SUPI2 may be different or the same.

[0597] Step 1b, perform a handover required (for TE2) for the TE2

[0598] Step 1c, first initiate a cross-system handover process from 4G to 5G for the TE2, and the first AMF is the target AMF.

[0599] Specifically, the original 4G base station 10 performs a handover of the 4G connection of the dual-boot device 8 and sends a handover request to the second MME31. The dual-boot device 8 performs a cross-system handover process and specifically completes the relevant process for the TE2. At this time, the dual-boot device 8 is in a temporary state with two registrations and two connections in 5G, and the 4G context information is transferred to the first AMF11.

[0600] Step 2, the TE2 sends the 4G context information to the TE1.

[0601] Specifically, assume that the dual-boot device 8 needs to perform an inter-system mobility update from a 4G network to a 5G network. For example, the 4G network signal can no longer be used, and it is desired to use only a single connection mode after moving to the 5G network, that is, there will be no complex situations such as two registrations and two connections in the 5G network. For this purpose, TE2 sends 4G context information to TE1. The 4G context information may include: 4G GUTI or a mapped GUTI mapped from the 4G GUTI; optionally, the 4G context information may further include a security context; optionally, the 4G context information may further include 4G session or connection context, etc.

[0602] Step 3, TE1 in the dual-boot device 8 sends an inter-system mobility registration message (i.e., sends the first information) to the first AMF 11 in the 5G network. For example, it sends a Registration Request message. Among them, the registration request carries 5G-GUTI and / or the first mapped GUTI (additional GUTI), where 5G-GUTI is the GUTI obtained by the dual-boot device 8 during 5G registration, and additional GUTI is the mapped GUTI (obtained from TE2 or calculated from the information obtained from TE2); the registration request may also carry an inter-system mobility update indication (i.e., the first indication information), such as carrying an indication of "moving from EPC".

[0603] Compared with Figure 9E In the specific embodiment five shown, in the specific embodiment six, the process of obtaining 4G context information from the second MME 31 in step 6 is not executed because the 4G context information has been transferred to the first AMF 11.

[0604] Step 4, optionally, the first AMF 11 may request the 5G context information (i.e., the first context information) of the dual-boot device 8 from the second AMF 21 based on the 5G-GUTI.

[0605] Specifically, the first AMF 11 may send a Namf_Communication_UEContextTransfer Request (i.e., the second indication information) carrying 5G-GUTI (the first identifier) to the second AMF 21 to request 5G context information.

[0606] Step 5, optionally, the second AMF 21 returns the 5G context information.

[0607] Among them, the 5G context information may include SUPI1 (the third identifier).

[0608] Optionally, the 5G context information may further include first session information (such as PDU session ID, related DNN, S-NSSAI, SMF information).

[0609] Optionally, the 5G context information may further include identification association information for indicating that the terminal device has an associated SUPI, for example, it may be indicated by carrying SUPI2.

[0610] Optionally, the 5G context information may further include session association information, such as the mapping relationship between (DNN, S-NSSAI) and APN, and the EPS bearer ID corresponding to the PDU session.

[0611] It can be understood that when the second AMF 21 and the first AMF 11 are the same AMF, steps 4 and 5 are internal operations.

[0612] Step 7, optionally, the first AMF 11 may request subscription information from the UDM 4 based on SUPI1 and / or SUPI2, or at least one of the second session information, identification association information, and session association information obtained in step 4, or request subscription information based on the SUPI2 registered in 4G.

[0613] For example, call the Nudm_SDM_Get operation to request subscription information.

[0614] The UDM 4 returns the subscription information of SUPI2, and the subscription information may include session association relationships, such as the mapping relationship between (DNN, S-NSSAI) and APN. The subscription information may further include identification association information.

[0615] Step 8, the first AMF 11 combines the 5G context information and the 4G context information into third context information.

[0616] Optionally, the first AMF 11 associates the third context information with a SUPI, such as associating it with SUPI1 or SUPI2.

[0617] Specifically, the first AMF 11 can determine whether to merge the 5G context information and the 4G context information based on the identification association information and / or session association information in step 5 or step 7. If the associated SUPI of 5G registration is the SUPI of 4G registration, or the associated SUPI of 4G registration is the SUPI of 5G registration, or there is identification association information, the first AMF 11 performs the merging of the 5G context information and the 4G context information. Conversely, if the associated SUPI of 5G registration is not the SUPI of 4G registration, or the associated SUPI of 4G registration is not the SUPI of 5G registration, or there is no identification association information, the first AMF 11 can indicate registration rejection to the dual-boot device 8, or does not perform context merging, and indicates to the dual-boot device 8 through step 11 that there is no merged context.

[0618] Step 9a: Based on the third context information, the first AMF 11 determines whether it is necessary to create a new PDU session for SUPI1 in the 5G network (for example, based on the session association information, it is determined that a certain 4G session has no associated 5G session).

[0619] If necessary, the SMF 5 creates a PDU session for SUPI1 based on the 4G context information.

[0620] Specifically, for example, the first AMF 11 invokes the NSMF 5_PDUSession_CreateSMContext operation, and the parameters can include indication information 1, indicating preparation for transfer / handover. After the creation of the PDU session is completed, the SMF 5 notifies (the specific notification information is the eighth information) the PGW-U or UPF to transmit the downlink data packets of the corresponding 4G session from the PDU session path of SUPI1, and the corresponding 4G session no longer transmits downlink data. This operation can be based on indication information 1.

[0621] Step 9b: The first AMF 11 can also determine based on the third context information (such as the session association information in the third context information) that a certain 4G session has an associated 5G session, and then instruct the SMF 5 to update the PDU session of SUPI1. For example, it invokes the NSMF 5_PDUSession_UpdateSMContext operation, and the parameters can include indication information 1 or 2. Indication information 2 indicates transfer / handover. The SMF 5 notifies (the specific notification information is the eighth information) the PGW-U or UPF to transmit the downlink data packets of the corresponding 4G session from the PDU session path of SUPI1, and the corresponding 4G session no longer transmits downlink data. This operation can be based on indication information 1 or 2.

[0622] Another embodiment of steps 8 and 9 is that step 9 is executed first and then step 8, specifically as follows:

[0623] Step 9: Based on all 4G session information in the 4G context information, the first AMF 11 creates a PDU session for SUPI1 in 5G. The session creation request may carry identification association information. For example, by carrying SUPI2 or indication information, the SMF 5 can decide whether to create a PDU session based on the identification association information and local session association information, and return the result to the first AMF 11.

[0624] Step 8: The first AMF 11 merges the 5G context information and 4G context information based on the returned result. That is, when there are identical sessions (with an association relationship, or the returned result during creation indicates an existing associated session, failure, etc.), the PDU session in 5G is retained while the PDN connection or EPS bearer in 4G is invalidated.

[0625] Step 10: When the first AMF 11 is not the second AMF 21, the first AMF 11 indicates the registered AMF to the UDM 4 for the SUPI1 registered in 5G.

[0626] The purpose of Step 10 is to record the serving AMF information of SUPI1 in the UDM 4.

[0627] Step 11: The first AMF 11 sends a registration acceptance message to the dual-boot device 8, such as sending a RegistrationAccept message. The registration acceptance message may carry indication information for instructing the dual-boot device 8 to perform at least one of the following: merging the 5G context information and 4G context information, 5G- or 4G-related information (such as indicating registration using 5G, indicating registration using 5G RAT type, indicating registration using the PLMN ID of the 5G network, etc.). Here, PLMN refers to Public Land Mobile Network.

[0628] Step 12: The TE1 in the dual-boot device 8 merges the original 5G context information and 4G context information into 5G context information. Optionally, the TE1 sends a deregistration indication to the TE2 for instructing at least one of local deregistration of the 4G context and exiting the 4G registration state, or the TE1 sends 5G context information without session content to the TE2, and the TE2 maintains 5G registration but has no session.

[0629] In the merged 5G context information, only one associated session is retained. For example, if two sessions have the same PDU session ID or EPS bearer ID, they are associated sessions. Optionally, the 4G security context may not be included in the merge, that is, only the 5G security context is retained. In one embodiment, if single registration is not entered, there are two 5G context information, one of which has no session context; in another embodiment, if single registration is entered, there is only one 5G context information, and the device enters the 5G single registration (SUPI1 registration) state, and the dual-boot device 8 deregisters at least one of the 4G context information and locally exits the 4G registration state.

[0630] Step 13, optionally (for example, when dual registration is no longer required), after step 10, the first AMF 11 also instructs the UDM 4 to deregister the SUPI2 for 4G registration.

[0631] Step 14, optionally, link two registrations.

[0632] Specifically, after step 10, based on the indication information in step 10, the UDM 4 learns about the service network element registration status of the dual-boot device 8, or after step 13, the UDM 4 learns about the service network element registration status of the dual-boot device 8.

[0633] Among them, the service network element registration status of the dual-boot device 8 may include at least one of the following:

[0634] Register with MME / AMF;

[0635] Register with MME / AMF associated with SUPI.

[0636] It can be understood that in the case where SUPI1 and SUPI2 are the same, there is one registration of SUPI with one MME and one AMF.

[0637] Optionally, when the dual-boot device 8 establishes two registrations using two different SUPIs, after step 10, step 16 is executed to notify the second AMF 21 to deregister, and after step 13, step 15 is executed to notify the second MME 31 to deregister. In the case where the two registrations of the dual-boot device 8 on the network side are based on the same SUPI, step 13 is not executed, step 10 carries a single registration indication, and the UDM 4 deregisters the second MME 31. If the first AMF 11 registered in step 10 is not an existing registration in the UDM 4 (the first AMF 11 is not the second AMF 21), then step 16 is executed to deregister the second AMF 21.

[0638] Step 15, the UDM 4 may perform a deregistration operation based on the association result of step 14 to deregister the registration of the dual-boot device 8 with the second MME 31 based on SUPI2.

[0639] Step 16: UDM 4 notifies the second AMF 21 of deregistration to deregister the dual-boot device 8's registration with the second AMF based on SUPI1.

[0640] Specific Embodiment Seven (4G (TE2) to 5G handover, becoming TE2 single access)

[0641] In Specific Embodiment Seven, as Figure 9G shown, TE1 of the dual-boot device 8 has been registered in the 5G network based on SUPI1, and TE2 of the dual-boot device 8 has been registered in the 4G network based on SUPI2; the first network function is the first AMF11, the second network function is the second AMF 21, the third network function is the second MME 31, the fourth network function is UDM 4, and the fifth network function or the sixth network function is SMF 5.

[0642] As Figure 9G shown, in Specific Embodiment Seven, an information interaction method provided by the present application may include:

[0643] Step 1a: TE1 in the dual-boot device 8 has been registered in the 5G network based on SUPI1, TE2 in the dual-boot device has been registered in the 4G network based on SUPI2, and TE2 may have established a session (PDN connection) in the 4G network.

[0644] Among them, TE1 accesses the 5G network through the 5G base station 9, and TE1 accesses the 5G network through the 4G base station 10.

[0645] Among them, SUPI1 and SUPI2 may be different or the same.

[0646] Step 1b: Perform handover requirement handover for TE2 (Handover required (for TE2))

[0647] Step 1c: First initiate the inter-system handover process from 4G to 5G for TE2, with the first AMF as the target AMF.

[0648] Specifically, the original base station 10 of 4G performs the handover of the 4G connection of the dual-boot device 8 and sends a handover request to the second MME31. The dual-boot device 8 performs the inter-system handover process, specifically completing the relevant process for TE2. At this time, the dual-boot device 8 is in a temporary state of having two registrations and two connections in 5G, and the 4G context information is transferred to the first AMF11.

[0649] Step 2: TE2 requests 5G context information from TE1.

[0650] Specifically, assume that the dual-boot device 8 needs to perform an inter-system mobility update from the 5G network to the 4G network. For example, the 5G network signal can no longer be used, and it is desired to use only a single connection mode after moving to the 4G network, that is, there will be no complex situations such as two registrations and two connections in the 4G network. For this purpose, TE2 requests 5G context information from TE1. The 5G context information may include: 5G GUTI or the mapped GUTI obtained by mapping the 5G GUTI; optionally, the 5G context information may further include a security context; optionally, the 5G context information may further include 5G session or connection context, etc.

[0651] Step 3, TE2 in the dual-boot device 8 sends an inter-system mobility registration message (i.e., sends the first information) to the first AMF 11 in the 4G network, such as sending a Registration Request message. Among them, the 5G-GUTI and / or the first mapped GUTI (additional GUTI) are carried in the registration request. The 5G-GUTI is the GUTI obtained by the dual-boot device 8 during 5G registration, and the additional GUTI is the mapped GUTI (obtained from TE2 or calculated from the information obtained from TE2); the registration request may also carry an inter-system mobility update indication (i.e., the first indication information), such as carrying an indication of "moving from EPC".

[0652] Compared with Figure 9B In the specific embodiment seven shown, in this specific embodiment seven, the process of obtaining the 4G context information from the second MME 31 in step 4 is not executed because the 4G context information has been transferred to the first AMF 11.

[0653] Among them, the 4G context information includes SUPI2 (the fourth identifier).

[0654] Optionally, the 4G context information may further include: the second session information (such as PDU session ID, related DNN, S-NSSAI, SMF information).

[0655] Optionally, the 4G context information may further include identification association information for indicating that the terminal device has an associated SUPI, such as it may be indicated by carrying SUPI2.

[0656] Optionally, the 4G context information may further include session association information, such as the mapping relationship between (DNN, S-NSSAI) and APN, and the EPS bearer ID corresponding to the PDU session.

[0657] Step 5. Optionally, the first AMF 11 may request the 5G context information (i.e., the first context information) of the dual-boot device 8 from the second AMF 21 based on the 5G-GUTI.

[0658] Specifically, the first AMF 11 may send a Namf_Communication_UEContextTransfer Request (i.e., the second indication information) carrying the 5G-GUTI (the first identifier) to the second AMF 21 to request the 5G context information.

[0659] Step 6. Optionally, the second AMF 21 returns the 5G context information.

[0660] Among them, the 5G context information may include the SUPI1 (the third identifier).

[0661] Optionally, the 5G context information may further include the first session information (such as the PDU session ID, the related DNN, S-NSSAI, SMF information).

[0662] Optionally, the 5G context information may further include the identification association information for indicating that the terminal device has an associated SUPI, for example, it may be indicated by carrying the SUPI2.

[0663] Optionally, the 5G context information may further include the session association information, such as the mapping relationship between (DNN, S-NSSAI) and the APN, and the EPS bearer ID corresponding to the PDU session.

[0664] It can be understood that when the second AMF 21 and the first AMF 11 are the same AMF, Steps 4 and 5 are internal operations.

[0665] Step 7. Optionally, the first AMF 11 may request the subscription information from the UDM 4 based on the SUPI1 and / or SUPI2, or at least one of the second session information, identification association information, and session association information obtained in Step 6, or request the subscription information based on the SUPI1 registered for 5G or the SUPI2 registered for 4G.

[0666] For example, call the Nudm_SDM_Get operation to request the subscription information.

[0667] The UDM 4 returns the subscription information of the SUPI1, and the subscription information may include the session association relationship, such as the mapping relationship between (DNN, S-NSSAI) and the APN. The subscription information may further include the identification association information.

[0668] Step 8. The first AMF 11 combines the 5G context information and the 4G context information into the third context information.

[0669] Optionally, the first AMF 11 associates the third context information with a SUPI, such as associating it with SUPI1 or SUPI2.

[0670] Specifically, the first AMF 11 can determine whether to merge 5G context information and 4G context information based on the identification association information and / or session association information in step 5 or step 7. If the associated SUPI for 5G registration is the SUPI for 4G registration, or the associated SUPI for 4G registration is the SUPI for 5G registration, or there is identification association information, the first AMF 11 performs the merge of 5G context information and 4G context information. Conversely, if the associated SUPI for 5G registration is not the SUPI for 4G registration, or the associated SUPI for 4G registration is not the SUPI for 5G registration, or there is no identification association information, the first AMF 11 can indicate registration rejection to the dual-boot device 8, or does not perform context merging, and indicates to the dual-boot device 8 through step 11 that there is no merged context.

[0671] Step 9: The first AMF 11 creates new PDU sessions for all 4G sessions of SUPI2 in 5G, and then, based on the merged context, determines whether an additional PDU session needs to be created for SUPI2 in 5G (for example, determines that a certain 5G session has no associated 4G session based on session association information). If necessary, it instructs SMF5 to create a PDU session for SUPI2, such as by invoking the Nsmf_PDUSession_CreateSMContext operation. The parameters can include indication information 1 indicating preparation for transfer / handover. After the creation of this PDU session is completed, SMF5 notifies PGW-U (UPF) to transmit the downlink data packets for the corresponding 4G session through the PDU session path of SUPI2, and the corresponding 4G session no longer transmits downlink data. This operation can be based on indication information 1.

[0672] Another embodiment of steps 8 and 9 is that step 9 is executed first and then step 8, specifically as follows:

[0673] Step 9: The first AMF 11 creates new PDU sessions for all 5G sessions of SUPI1 in 5G for SUPI2, which can carry identification association information, such as by carrying SUPI1 indication. SMF5 can decide whether to create a PDU session based on the identification association information and local session association information, and return the result to the first AMF 11.

[0674] Step 8: The first AMF 11 merges the two contexts based on the returned result, that is, when there are the same sessions (with an associated relationship, or the returned result during creation indicates an existing associated session, failure, etc.), the 5G PDU session is retained while the 4G PDN connection or EPS bearer is invalidated.

[0675] Step 10: When the first AMF 11 is not the second AMF 21, the first AMF 11 indicates the registered AMF for the 4G-registered SUPI2 to the UDM 4.

[0676] The purpose of step 10 is to record the serving AMF information of the SUPI2 in the UDM 4.

[0677] Step 11: The first AMF 11 sends a registration acceptance message to the dual-boot device 8, such as sending a RegistrationAccept message. The registration acceptance message may carry indication information for instructing the dual-boot device 8 to perform at least one of the following: merging 5G context information and 4G context information, and 5G- or 4G-related information (such as indicating registration using 5G, indicating registration using 5G RAT type, indicating registration using the PLMN ID of the 5G network, etc.).

[0678] Step 12: The TE2 in the dual-boot device 8 merges the original 5G context information and 4G context information into 5G context information. Optionally, the TE2 sends a deregistration indication to the TE1 for instructing at least one of the following: locally deregistering the 5G context and exiting the 5G registration state, or the TE2 sends 5G context information without session content to the TE1, and the TE1 maintains 5G registration but has no session.

[0679] In the merged 5G context information, only one associated session is retained. For example, if two sessions have the same PDU session ID or EPS bearer ID, they are associated sessions. Optionally, the 4G security context may not be included in the merge, that is, only the 5G security context is retained. In one embodiment, single registration is not entered, so there are two 5G context information, one of which has no session context; in another embodiment, single registration is entered, so there is only one 5G context information, the device enters the 5G single registration (SUPI2 registration) state, and the dual-boot device 8 deregisters the 4G context information and exits the 4G registration state locally for at least one of the above.

[0680] Step 13: Optionally (such as when dual registration is no longer required), after step 10, the first AMF 11 also indicates deregistration for the 5G-registered SUPI1 to the UDM 4.

[0681] Step 14: Optionally, link two registrations.

[0682] Specifically, after step 10, the UDM 4 learns about the service network element registration situation of the dual-boot device 8 based on the indication information in step 10, or after step 13, the UDM 4 learns about the service network element registration situation of the dual-boot device 8.

[0683] Among them, the service network element registration status of the dual-boot device 8 may include at least one of the following:

[0684] Register with MME / AMF;

[0685] Register with MME / AMF associated with the SUPI.

[0686] It can be understood that when SUPI1 and SUPI2 are the same, there is one registration of MME and one registration of AMF for the SUPI.

[0687] Optionally, when the dual-boot device 8 establishes two registrations using two different SUPIs, after step 10, step 16 is executed to notify the second AMF 21 of deregistration, and after step 13, step 15 is executed to notify the second MME 31 of deregistration. When the two registrations of the dual-boot device 8 on the network side are based on the same SUPI, step 13 is not executed, step 10 carries a single-registration indication, and the UDM 4 deregisters the second MME 31. If the first AMF 11 registered in step 10 is not the existing registration in the UDM 4 (the first AMF 11 is not the second AMF 21), then step 16 is executed to deregister the second AMF 21.

[0688] Step 15, the UDM 4 can perform a deregistration operation based on the association result of step 14 to deregister the registration of the dual-boot device 8 on the second MME 31 based on SUPI2.

[0689] Step 16, the UDM 4 notifies the second AMF 21 of deregistration to deregister the registration of the dual-boot device 8 on the second AMF based on SUPI1.

[0690] Specific Embodiment Eight (Mobility Update from 5G (TE1) to 4G, Becoming TE1 Single-Access)

[0691] In Specific Embodiment Eight, as Figure 9H shown, the TE1 of the dual-boot device 8 has been registered in the 5G network based on SUPI1, and the TE2 of the dual-boot device 8 has been registered in the 4G network based on SUPI2; the seventh network function is the first MME 12, the first network function is the second AMF 21, the third network function is the second MME 31, the fourth network function is the UDM 4, and the fifth network function or the sixth network function is the SMF 5.

[0692] As Figure 9H shown, in Specific Embodiment Eight, an information interaction method provided by the present application includes:

[0693] Step 1a, TE1 in the dual-boot device 8 has been registered in the 5G network based on SUPI1, TE2 in the dual-boot device has been registered in the 4G network based on SUPI2, and TE1 may have established a session (PDU session) in 5G.

[0694] Among them, TE2 accesses the 4G network through the 4G base station 10.

[0695] Among them, SUPI1 and SUPI2 can be different or the same.

[0696] Step 1b, perform handover required (for TE1) for TE1.

[0697] Step 1c, first initiate the cross-system handover process from 4G to 5G for TE1, with the first MME12 as the target AMF.

[0698] Specifically, the original 5G base station 9 performs the handover of the 5G connection of the dual-boot device 8 and sends a handover request to the second AMF21. The dual-boot device 8 performs the cross-system handover process and specifically completes the relevant process for TE1. At this time, the dual-boot device 8 is in a temporary state with two registrations and two connections in 4G, and the 5G context information is transferred to the first MME12.

[0699] Step 2, TE1 requests 4G context information from TE2.

[0700] Specifically, assume that the dual-boot device 8 needs to perform inter-system mobility update from the 5G network to the 4G network, for example, the 5G network signal can no longer be used, and at the same time, it is hoped that only a single connection mode will be used after moving to the 4G network, that is, there will be no complex situation of two registrations and two connections in the 4G network. For this reason, TE1 requests 4G context information from TE2. The 4G context information may include: 4G GUTI or the mapped GUTI obtained by mapping from the 4G GUTI; optionally, the 4G context information may further include a security context; optionally, the 4G context information may further include 4G session or connection context, etc.

[0701] Step 3, TE1 in the dual-boot device 8 sends a cross-system mobility registration message (i.e., sends the first information) to the first MME 12 in the 5G network, such as sending a Tracking Area Update Request (TAU Request) message. Among them, at least one of 5G-GUTI (from TE1), the second mapped GUTI (4G-GUTI, from TE2), and additional GUTI is carried in the tracking area update request. Among them, 4G-GUTI is a mapped GUTI (calculated from the 5G-GUTI obtained by TE1 in 5G), and additional GUTI is the GUTI obtained when the dual-boot device 8 is registered in 4G (4G context information from TE2) or the mapped 5G-GUTI mapped from this 4G-GUTI. Optionally, a cross-system mobility update indication may also be carried in the tracking area update request, such as carrying an indication of "moving from 5GC". The dual-boot device 8 sends a TAU message based on the 5G security context information.

[0702] Step 4, optionally, the first MME 12 may request the 4G context information (i.e., the second context information) of the dual-boot device 8 from the second AMF 21 based on the 4G-GUTI or the second mapped GUTI. That is, the first network function receives the first information from the seventh network function.

[0703] Specifically, the first MME 12 may send a ContextTransfer Request carrying the 4G-GUTI (the second identifier) to the second AMF 21 to request the 4G context information.

[0704] Step 5, after receiving the first information, the second AMF 21 requests the 4G context information (i.e., the second context information) of the dual-boot device 8 from the second MME 31 based on the 4G-GUTI. Optionally, the second MME 31 returns the 4G context information.

[0705] Among them, the 4G context information may include SUPI2 (the third identifier).

[0706] Optionally, the 4G context information may also include the first session information (such as PDU session ID, related DNN, S-NSSAI, SMF information).

[0707] Optionally, the 4G context information may also include identification association information for indicating that the terminal device has an associated SUPI, such as it may be indicated by carrying SUPI1.

[0708] Optionally, the 4G context information may further include session association information, such as the mapping relationship between (DNN, S-NSSAI) and APN, and the EPS bearer ID corresponding to the PDU session.

[0709] It should be noted that the 5G context information (i.e., the first context information) of the dual-boot device 8 is stored locally in the second AMF 21.

[0710] Step 6, optionally, the second AMF 21 requests subscription information from the UDM 4.

[0711] Specifically, if the SUPI in the 4G context information obtained in step 5 is different from the SUPI in the locally stored 5G context information, or the local 5G context information includes at least one of session information, identity association information, and session association information, the second AMF 21 requests subscription information from the UDM 4. For example, it requests subscription information from the UDM 4 based on the SUPI1 registered for 5G, such as by invoking the Nudm_SDM_Get operation. Of course, it can also request subscription information based on the SUPI2 registered for 4G. The UDM 4 returns the subscription information for SUPI1, which may include session association relationships, such as the mapping relationship between (DNN, S-NSSAI) and APN, and the subscription information may also include identity association information.

[0712] Step 7, optionally, the second AMF 21 requests the first session information from the SMF 5 based on the 5G context information.

[0713] For example, the second AMF 21 invokes Nsmf_PDUSession_ContextRequest and carries SUPI1 in this request; the request may also carry indication information 1 for indicating preparation for handover / transfer; the request may also carry identity association information, such as SUPI2 or information indicating identity association. The SMF 5 may return an association result to the second AMF based on the identity association information (local or received) and the local session association information. For example, for a PDU session with a 4G associated session, it returns the information of the PDU session and session association information, or it may not return the PDU session information.

[0714] Step 8, the second AMF 21 merges the 5G context information and the 4G context information into the third context information.

[0715] Optionally, the second AMF 21 associates the third context information with a SUPI, such as associating it with SUPI1 or SUPI2.

[0716] Specifically, based on the local 5G context information and the 4G context information obtained in step 5, the second AMF 21 merges the 4G and 5G context information into a UE context and associates the merged UE context with a SUPI (such as the SUPI1 registered for 5G). The second AMF 21 can determine whether to merge the two contexts based on the 4G context information in step 5 and the identification association information and / or session association information in step 7 (if step 7 does not return PDU session information due to the association of a 4G session with the PDU session, then the merge operation has no information related to the PDU session information). Optionally, if the SUPI associated with 5G registration is not the SUPI registered for 4G, or the SUPI associated with 4G registration is not the SUPI registered for 5G, or there is no identification association information, the second AMF 21 can return an error indication to the first MME 12, ultimately resulting in the rejection of the registration.

[0717] Step 9, the second AMF 21 returns the merged context information to the first MME 12, and the context information may include SUPI1.

[0718] Step 10, the first MME 12 instructs the UDM 4 to register the first MME for the SUPI1 registered for 4G.

[0719] The purpose of step 10 is to record the serving MME information of SUPI1 in the UDM 4.

[0720] Step 11, the first MME 12 sends a TAU acceptance message to the dual-boot device 8, such as sending a TAU Accept message.

[0721] Among them, the TAU acceptance message can carry indication information for instructing the dual-boot device 8 to perform at least one of the following operations: merging 5G context information and 4G context information, 5G- or 4G-related information (such as indicating 5G registration, 5G RAT type indicating 5G registration, PLMN ID of the 5G network indicating 5G registration, etc.). Among them, PLMN refers to the Public Land Mobile Network.

[0722] Step 12, the TE1 in the dual-boot device 8 merges the original 5G context information and 4G context information into 4G context information.

[0723] Optionally, the TE1 sends a deregistration indication to the TE2 for instructing at least one of local deregistration of the 5G context and exiting the 5G registration state. The TE1 maintains 4G single registration, or the TE1 sends 4G context information without session content to the TE2, and the TE2 maintains 4G registration but has no session.

[0724] In the merged 5G context information, only one associated session is retained. For example, if two sessions have the same PDU session ID or EPS bearer ID, they are associated sessions. Optionally, the 5G security context is not merged, that is, only the 4G security context is retained. Optionally, in one embodiment, single registration is not entered, so there are two 4G context information, one of which has no session context; in another embodiment, single registration is entered, so there is only one 4G context information, and the device enters the 4G single registration (SUPI1 registration) state, and the dual-boot device 8 logs off at least one of the 5G context information and the local 5G registration state exit.

[0725] Step 13, optionally, after step 10, the first MME 12 also instructs the UDM 4 to log off the SUPI2 registered for 4G.

[0726] Step 14, optionally, link two registrations.

[0727] Specifically, after step 10, the UDM 4 learns about the service network element registration status of the dual-boot device 8 based on the indication information in step 10, or after step 13, the UDM 4 learns about the service network element registration status of the dual-boot device 8.

[0728] Among them, the service network element registration status of the dual-boot device 8 may include at least one of the following:

[0729] Registered MME / AMF;

[0730] Registered MME / AMF associated with the SUPI.

[0731] It can be understood that when SUPI1 and SUPI2 are the same, the SUPI has one registration for the MME and one for the AMF.

[0732] Optionally, when the dual-boot device 8 establishes two registrations using two different SUPIs, step 16 is executed after step 10 to notify the second AMF 21 to log off, and step 15 is executed after step 13 to notify the second MME 31 to log off. When the two registrations of the dual-boot device 8 on the network side are based on the same SUPI, step 13 is not executed, step 10 carries a single registration indication, the UDM 4 logs off the second MME 31, and if the first MME 12 registered in step 10 is not the existing registration in the UDM 4 (the first MME 12 is not the second AMF 21), then step 16 is executed to log off the second AMF 21.

[0733] Step 15, the UDM 4 may perform a logoff operation based on the association result of step 14 to log off the registration of the dual-boot device 8 on the second MME 31 based on SUPI2.

[0734] Step 16, UDM 4 notifies the second AMF 21 of deregistration to deregister the dual-boot device 8's registration based on SUPI1 at the second AMF.

[0735] Specific Embodiment Nine (5G (TE1) to 4G handover, becoming TE2 single access)

[0736] In Specific Embodiment Nine, as Figure 9I shown, TE1 of the dual-boot device 8 has been registered in the 5G network based on SUPI1, and TE2 of the dual-boot device 8 has been registered in the 4G network based on SUPI2; the seventh network function is the first MME 12, the first network function is the second AMF 21, the third network function is the second MME 31, the fourth network function is the UDM 4, and the fifth network function or the sixth network function is the SMF 5.

[0737] As Figure 9I shown, in Specific Embodiment Nine, an information interaction method provided by this application includes:

[0738] Step 1a, TE1 in the dual-boot device 8 has been registered in the 5G network based on SUPI1, TE2 in the dual-boot device has been registered in the 4G network based on SUPI2, and TE1 may have established a session (PDU session) in 5G.

[0739] Among them, TE2 accesses the 4G network through the 4G base station 10.

[0740] Among them, SUPI1 and SUPI2 may be different or the same.

[0741] Step 1b, perform handover required for TE1.

[0742] Step 1c, first initiate the cross-system handover process from 4G to 5G for TE1, with the first MME12 as the target AMF.

[0743] Specifically, the original 5G base station 9 performs the handover of the 5G connection of the dual-boot device 8 and sends a handover request to the second AMF21. The dual-boot device 8 performs the cross-system handover process, specifically completing the relevant process for TE1. At this time, the dual-boot device 8 is in a temporary state of having two registrations and two connections in 4G, and the 5G context information is transferred to the first MME12.

[0744] Step 2, TE1 sends 5G context information to TE2.

[0745] Specifically, assume that the dual-boot device 8 needs to perform an inter-system mobility update from a 5G network to a 4G network. For example, when the 5G network signal can no longer be used, and it is desired to use only a single connection mode after moving to the 4G network, that is, there will be no complex situations such as two registrations and two connections in the 4G network. For this purpose, TE1 sends 5G context information to TE2. The 5G context information may include: 5G GUTI or a mapped GUTI obtained by mapping the 5G GUTI; optionally, the 5G context information may further include a security context; optionally, the 5G context information may further include 5G session or connection context, etc.

[0746] Step 3, TE2 in the dual-boot device 8 sends an inter-system mobility registration message (i.e., sends the first information) to the first MME 12 in the 4G network. For example, it sends a Tracking Area Update Request (TAU Request) message. Among them, the tracking area update request carries at least one of a first mapped GUTI (from TE1), a 4G-GUTI (4G-GUTI, from TE2), and an additional GUTI. Among them, the 4G-GUTI is a mapped GUTI (calculated from the 5G-GUTI obtained by TE1 in 5G), and the additional GUTI is a GUTI obtained when the dual-boot device 8 is registered in 4G (from the 4G context information of TE2) or a mapped 5G-GUTI mapped from the 4G-GUTI.

[0747] Optionally, the tracking area update request may further carry an inter-system mobility update indication, such as an indication of "moving from 5GC". The dual-boot device 8 sends a TAU message based on the 5G security context information.

[0748] Step 4, optionally, the first MME 12 may request the 4G context information (i.e., the second context information) of the dual-boot device 8 from the second AMF 21 based on the 4G-GUTI or the second mapped GUTI. That is, the first network function receives the first information from the seventh network function.

[0749] Specifically, the first MME 12 may send a ContextTransfer Request carrying the 4G-GUTI (the second identifier) to the second AMF 21 to request the 4G context information.

[0750] Step 5, after receiving the first information, the second AMF 21 requests the 4G context information (i.e., the second context information) of the dual-boot device 8 from the second MME 31 based on the 4G-GUTI. Optionally, the second MME 31 returns the 4G context information.

[0751] Among them, the 4G context information may include SUPI2 (the third identifier).

[0752] Optionally, the 4G context information may further include first session information (such as PDU session ID, related DNN, S-NSSAI, SMF information).

[0753] Optionally, the 4G context information may further include identification association information for indicating that the terminal device has an associated SUPI, for example, it may be indicated by carrying SUPI1.

[0754] Optionally, the 4G context information may further include session association information, such as the mapping relationship between (DNN, S-NSSAI) and APN, and the EPS bearer ID corresponding to the PDU session.

[0755] It should be noted that the 5G context information (i.e., the first context information) of the dual-boot device 8 is saved locally in the second AMF 21.

[0756] Step 6, optionally, the second AMF 21 requests subscription information from the UDM 4.

[0757] Specifically, when the SUPI in the 4G context information obtained in step 5 is different from the SUPI in the locally saved 5G context information, or the locally saved 5G context information includes at least one of session information, identification association information, and session association information, the second AMF 21 requests subscription information from the UDM 4. For example, it requests subscription information from the UDM 4 based on SUPI2 in the 4G context information, such as invoking the Nudm_SDM_Get operation. Of course, it can also request subscription information based on the SUPI1 registered for 5G. The UDM 4 returns the subscription information of SUPI2, and the subscription information may include session association relationships, such as the mapping relationship between (DNN, S-NSSAI) and APN, and the subscription information may further include identification association information.

[0758] Step 7, optionally, the second AMF 21 requests first session information from the SMF 5 based on the 5G context information.

[0759] For example, the second AMF 21 invokes Nsmf_PDUSession_ContextRequest and carries SUPI1 in this request; indication information 1 can also be carried in this request to indicate preparation for handover / transfer; identification association information such as SUPI2 or information indicating identification association can also be carried in this request. The SMF 5 can return an association result to the second AMF based on the identification association information (local or received) and local session association information. For example, for a PDU session with a 4G associated session, the PDU session information and session association information are returned, or the PDU session information may not be returned.

[0760] Step 8: The second AMF 21 merges the 5G context information and 4G context information into third context information.

[0761] Optionally, the second AMF 21 associates the third context information with a SUPI, such as associating it with SUPI1 or SUPI2.

[0762] Specifically, the second AMF 21 merges the 4G and 5G context information into a UE context based on the local 5G context information and the 4G context information obtained in step 5, and associates the merged UE context with a SUPI (such as the 5G registered SUPI1). The second AMF 21 can determine whether to merge the two contexts based on the 4G context information in step 5 and the identification association information and / or session association information in step 7 (if the PDU session information is not returned in step 7 because there is an associated 4G session for the PDU session, then the merge operation has no information related to the PDU session information). Optionally, if the associated SUPI registered for 5G is not the SUPI registered for 4G, or the associated SUPI registered for 4G is not the SUPI registered for 5G, or there is no identification association information, the second AMF 21 can return an error indication to the first MME 12, ultimately resulting in the rejection of the registration.

[0763] Step 9: The second AMF 21 returns the merged context information to the first MME 12, and this context information may include SUPI1.

[0764] Step 10: In the case where the first MME 12 is different from the second MME 31, the first MME 12 indicates to the UDM 4 to register the first MME for the 4G registered SUPI1.

[0765] The purpose of step 10 is to record the serving MME information of SUPI2 in the UDM 4.

[0766] Step 11: The first MME 12 sends a TAU acceptance message to the dual-boot device 8, such as sending a TAU Accept message.

[0767] Among them, the TAU acceptance message can carry indication information for indicating at least one of the following: merging 5G context information and 4G context information by the dual-boot device 8, 5G or 4G related information (such as indicating 5G registration, 5G RAT type indicating 5G registration, PLMN ID of the 5G network indicating 5G registration, etc.). Herein, PLMN refers to Public Land Mobile Network.

[0768] Step 12, the TE1 in the dual-boot device 8 merges the original 5G context information and 4G context information into 4G context information.

[0769] Optionally, the TE2 sends a deregistration indication to the TE1 for indicating at least one of locally deregistering the 5G context and exiting the 5G registration state. The TE1 maintains 4G single registration, or the TE1 sends 4G context information without session content to the TE2, and the TE2 maintains 4G registration but has no session.

[0770] In the merged 5G context information, only one associated session is retained. For example, if two sessions have the same PDU session ID or EPS bearer ID, they are associated sessions. Optionally, the 5G security context is not included in the merge, that is, only the 4G security context is retained. Optionally, in one embodiment, single registration is not entered, so there are two 4G context information, one of which has no session context; in another embodiment, single registration is entered, so there is only one 4G context information, the device enters the 4G single registration (SUPI2 registration) state, and the dual-boot device 8 deregisters at least one of the 5G context information and locally exits the 5G registration state.

[0771] Step 13, optionally, after step 10, the second AMF 12 also indicates deregistration to the UDM 4 for the SUPI1 of the 5G registration.

[0772] Step 14, optionally, link two registrations.

[0773] Specifically, after step 10, the UDM 4 learns about the service network element registration situation of the dual-boot device 8 based on the indication information in step 10, or after step 13, the UDM 4 learns about the service network element registration situation of the dual-boot device 8.

[0774] Among them, the service network element registration situation of the dual-boot device 8 may include at least one of the following:

[0775] Register MME / AMF;

[0776] Register MME / AMF associated with the SUPI.

[0777] Step 15: When the dual-boot device 8 establishes two registrations using two different SUPIs, after Step 10, Step 15 is executed to notify the second MME 31 of deregistration, so as to deregister the dual-boot device 8's registration with the second MME 31 based on SUPI2.

[0778] Specific Embodiment Ten (5G-to-5G Mobility Update)

[0779] In Specific Embodiment Ten, as Figure 9J shown, the TE1 of the dual-boot device 8 has been registered in the 5G network based on SUPI1, and the TE2 of the dual-boot device 8 has been registered in the 4G network based on SUPI2; the first network function is the first AMF 11, the second network function is the second AMF 21, the third network function is the third AMF 32, the fourth network function is the UDM 4, and the fifth network function or the sixth network function is the SMF 5.

[0780] It should be noted that in Specific Embodiment Ten, after swapping TE1 and TE2, or swapping SUPI1 and SUPI2, the handover process is similar.

[0781] As Figure 9J shown, in Specific Embodiment Ten, an information interaction method provided by the present application includes:

[0782] Step 1: The TE1 in the dual-boot device 8 has been registered in the 5G network based on SUPI1, the TE2 in the dual-boot device has been registered in the 5G network based on SUPI2, and TE2 may have established a session (PDN connection) in 5G.

[0783] Wherein, SUPI1 and SUPI2 may be different or the same.

[0784] Step 2: TE2 and TE1 exchange 5G context information.

[0785] The exchanged 5G context information may include: 5G GUTI or the mapped GUTI mapped from 5G GUTI; optionally, the 5G context information may further include a security context; optionally, the 5G context information may further include 5G session or connection context, etc.

[0786] Step 3, TE1 in the dual-boot device 8 sends a cross-system mobility registration message (i.e., sends the first piece of information) to the first AMF 11 in the 5G network, such as sending a Registration Request message. Among them, the Registration Request carries a 5G-GUTI and / or a first mapped GUTI (additional GUTI). The 5G-GUTI is the GUTI obtained by the dual-boot device 8 during 5G registration, and the additional GUTI is the mapped GUTI (obtained from TE2 or calculated from the information obtained from TE2); the Registration Request may also carry a cross-system mobility update indication (i.e., the first indication information), such as carrying an indication of "moving from TE2".

[0787] Steps 4 - 5, optionally, the first AMF 11 may request the first 5G context information (i.e., the first context information) of the dual-boot device 8 from the second AMF 21 based on the 5G-GUTI. The second AMF 21 returns the first 5G context information.

[0788] Specifically, the first AMF 11 may send a Namf_Communication_UEContextTransfer Request (i.e., the second indication information) carrying the 5G-GUTI (the first identifier) to the second AMF 21 to request the first 5G context information. Among them, the 5G context information may include SUPI1 (the third identifier). Optionally, the 5G context information may also include the first session information (such as PDU session ID, related DNN, S-NSSAI, SMF information).

[0789] Step 6( Figure 9J (not shown), optionally, the first AMF 11 may request the second 5G context information (i.e., the second context information) of the dual-boot device 8 from the third AMF 32 based on the 5G-GUTI. The third AMF 32 returns the second 5G context information.

[0790] Among them, the second 5G context information includes SUPI2 (the fourth identifier).

[0791] Optionally, the second 5G context information may also include: the second session information (such as PDU session ID, related DNN, S-NSSAI, SMF information).

[0792] Optionally, the second 5G context information may also include identification association information for indicating that the terminal device has an associated SUPI, such as by carrying an indication of SUPI2.

[0793] Optionally, the second 5G context information may further include session association information, such as the mapping relationship between (DNN, S-NSSAI) and APN, and the EPS bearer ID corresponding to the PDU session.

[0794] Step 7. Optionally, the first AMF 11 may request subscription information from the UDM 4 based on the SUPI1 and / or SUPI2 obtained in Steps 4 and 6, or at least one of the second session information, identity association information, and session association information obtained in Step 6, or request subscription information based on the SUPI1 registered in 5G or the SUPI2 registered in 4G.

[0795] For example, call the Nudm_SDM_Get operation to request subscription information.

[0796] The UDM 4 returns the subscription information of SUPI1, which may include session association relationships, such as the mapping relationship between (DNN, S-NSSAI) and APN. The subscription information may also include identity association information.

[0797] Step 8. The first AMF 11 merges the first 5G context information and the second 5G context information into the third context information.

[0798] Optionally, the first AMF 11 associates the third context information with a SUPI, such as associating it with SUPI1 or SUPI2.

[0799] Specifically, the first AMF 11 may determine whether to merge the first 5G context information and the second 5G context information based on the identity association information and / or session association information in Step 5 or Step 7. If the two SUPIs are associated SUPIs, the first AMF 11 merges the first 5G context information and the second 5G context information; otherwise, the first AMF 11 may indicate registration rejection to the dual-boot device 8, or not perform context merging, and indicate to the dual-boot device 8 through Step 11 that there is no context merging.

[0800] Step 9a. Based on the third context information, the first AMF 11 determines whether a new PDU session needs to be established for SUPI1 in the 5G network.

[0801] If needed, the SMF 5 creates a PDU session for SUPI1 based on the second 5G context information.

[0802] Specifically, for example, the first AMF 11 invokes the NSMF 5_PDUSession_CreateSMContext operation, and the parameters may include indication information 1 indicating preparation for transfer / handover. After the creation of the PDU session is completed, the SMF 5 notifies (specific notification information is the eighth information) the PGW-U or the UPF to transmit the downlink data packets for the second 5G session through the PDU session path of SUPI1, and the second 5G session no longer transmits downlink data. This operation may be based on the indication information 1.

[0803] In step 9b, the first AMF 11 may also determine, based on the third context information (such as the session association information in the third context information), that a certain 5G session has an associated 5G session, and then instruct the SMF 5 to update the PDU session of SUPI1. For example, it invokes the NSMF 5_PDUSession_UpdateSMContext operation, and the parameters may include indication information 1 or 2. The indication information 2 indicates transfer / handover. The SMF 5 notifies (specific notification information is the eighth information) the PGW-U or the UPF to transmit the downlink data packets for the corresponding 5G session through the PDU session path of SUPI1, and the corresponding 5G session no longer transmits downlink data. This operation may be based on the indication information 1 or 2.

[0804] Another embodiment of steps 8 and 9 is that step 9 is executed first and then step 8, specifically as follows:

[0805] In step 9, based on all 5G session information in the second 5G context information, the first AMF 11 creates a PDU session for SUPI1 in 5G. The session creation request may carry identification association information, such as by carrying SUPI2 or indication information. The SMF 5 may decide whether to create a PDU session based on the identification association information and the local session association information, and return the result to the first AMF 11.

[0806] In step 8, the first AMF 11 merges the first 5G context information and the second 5G context information based on the returned result, that is, when there are the same sessions (with an association relationship, or the returned result during creation indicates an existing associated session, failure, etc.), the PDU session of the first 5G is retained and the PDU session of the second 5G is invalidated.

[0807] In step 10, when the first AMF 11 is not the second AMF 21, the first AMF 11 indicates the registered AMF to the UDM 4 for the 5G-registered SUPI1.

[0808] The purpose of step 10 is to record the serving AMF information of SUPI1 in the UDM 4.

[0809] Step 11: The first AMF 11 sends a registration acceptance message to the dual-boot device 8, such as sending a RegistrationAccept message. The registration acceptance message may carry indication information for instructing the dual-boot device 8 to perform at least one of the following: merging 5G context information and 4G context information, and 5G- or 4G-related information (such as indicating registration using 5G, indicating registration using 5G for the 5G RAT type, indicating registration using 5G for the PLMN ID of the 5G network, etc.). Here, PLMN refers to the Public Land Mobile Network.

[0810] Step 12: The TE1 in the dual-boot device 8 merges the original first 5G context information and the second 5G context information into one 5G context information. Optionally, the TE1 sends a deregistration indication to the TE2 for instructing at least one of local deregistration of the 5G context and exiting the 5G registration state, or the TE1 sends the 5G context information without session content to the TE2, and the TE2 maintains 5G registration but has no session.

[0811] In the merged 5G context information, only one associated session is retained. For example, if two sessions have the same PDU session ID, they are associated sessions. Optionally, the security context in the second 5G context information may not be merged, that is, only the security context in the first 5G context information is retained. In one embodiment, if single registration is not entered, there are two 5G context information, one of which has no session context; in another embodiment, if single registration is entered, there is only one 5G context information, the device enters the 5G single registration (SUPI1 registration) state, and the dual-boot device 8 deregisters at least one of the second 5G context information and locally exits the second 5G registration state.

[0812] Step 13: Optionally (such as when dual registration is no longer required), after step 10, the first AMF 11 also instructs the UDM 4 to deregister the SUPI2 for 5G registration.

[0813] Step 14: Optionally, link two registrations.

[0814] Specifically, after step 10, based on the indication information in step 10, the UDM 4 learns about the service network element registration status of the dual-boot device 8, or after step 13, the UDM 4 learns about the service network element registration status of the dual-boot device 8.

[0815] The service network element registration status of the dual-boot device 8 may include at least one of the following:

[0816] Registered AMF;

[0817] Registered AMF associated with SUPI.

[0818] It can be understood that when SUPI1 and SUPI2 are the same, there is only one registration of SUPI with an AMF.

[0819] Optionally, when the dual-boot device 8 establishes two registrations using two different SUPIs, after step 10, step 16 is executed to notify the second AMF 21 of deregistration, and after step 13, step 15 is executed to notify the second MME 31 of deregistration. When the two registrations of the dual-boot device 8 on the network side are based on the same SUPI, step 13 is not executed, and step 10 carries a single-registration indication. The UDM 4 deregisters the second MME 31. If the first AMF 11 registered in step 10 is not an existing registration in the UDM 4 (the first AMF 11 is not the second AMF 21), then step 16 is executed to deregister the second AMF 21.

[0820] In step 15, the UDM 4 can perform a deregistration operation based on the association result of step 14 to deregister the registration of the dual-boot device 8 with the second AMF 21 based on SUPI2.

[0821] In step 16, the UDM 4 notifies the third AMF 32 of deregistration to deregister the registration of the dual-boot device 8 with the third AMF 32 based on SUPI1.

[0822] It should be noted that in addition to 4G and 5G networks, the information interaction method provided in the embodiments of the present application can also be applied to the interaction (interworking) aspect when 6G and 5G networks coexist.

[0823] It should be noted that for the information interaction method provided in the embodiments of the present application, the execution subject can be an information interaction device. In the embodiments of the present application, taking the information interaction device executing the information interaction method as an example, the information interaction device provided in the embodiments of the present application is described.

[0824] The following describes an information interaction device provided in the embodiments of the present application with reference to the accompanying drawings. Since the information interaction device provided in the embodiments of the present application corresponds to the information interaction method provided in the embodiments of the present application, the description of the information interaction device provided in the embodiments of the present application is relatively brief, and for detailed content, reference can be made to the introduction in the method embodiment part above.

[0825] As Figure 10 shown, an embodiment of the present application provides an information interaction device 1000, which can be applied to a first network function. The device 1000 may include: a first receiving module 1001 and a first execution module 1002.

[0826] The first receiving module 1001 is configured to receive a first piece of information, where the first piece of information includes a first identifier and a second identifier.

[0827] Wherein, the first identifier may include at least one of the following:

[0828] A first globally unique temporary identifier (Globally Unique Temporary UE Identity, GUTI), such as GUTI1;

[0829] A first mapped GUTI obtained from the first GUTI, such as additional GUTI.

[0830] Wherein, the second identifier may include at least one of the following:

[0831] A second GUTI, such as GUTI2;

[0832] A second mapped GUTI obtained from the second GUTI, such as mapped GUTI.

[0833] The first execution module 1002 is configured to perform a first operation based on the first context information and the second context information.

[0834] Wherein, the first operation includes at least one of the following:

[0835] 1) Generate, determine or judge third context information;

[0836] 2) Send the third context information to a seventh network function.

[0837] 3) Perform a third operation;

[0838] 4) Send at least one of the following to a fourth network function:

[0839] A second piece of information;

[0840] A third piece of information and a fourth piece of information.

[0841] Wherein, the first context information is related to the first identifier, and the first context information includes at least one of the following: first session information and a third identifier; the second context information is related to the second identifier, and the second context information includes at least one of the following: second session information and a fourth identifier.

[0842] Wherein, the third identifier may include at least one of the following:

[0843] A first subscribed user permanent identifier (SUbs cription Permanent Identifier, SUPI), such as SUPI1;

[0844] The first International Mobile Subscriber Identity (IMSI), such as IMSI1;

[0845] Wherein, the fourth identifier may include at least one of the following:

[0846] The second SUPI, such as SUPI2;

[0847] The second IMSI, such as IMSI2.

[0848] Wherein, the second information may include any one of the following:

[0849] The third identifier;

[0850] The third identifier and at least one of the following: the first session information, the first identifier association information, the fourth identifier, the second session information, the registration indication or the location update indication, the deregistration indication or the location cancellation indication.

[0851] Wherein, the third information includes the third identifier and the deregistration indication or the location cancellation indication.

[0852] Wherein, the fourth information includes the fourth identifier and the registration indication or the location update indication.

[0853] Wherein, the third operation includes at least one of the following:

[0854] 1) Instruct the fifth network function to create, update, or release a session or session context;

[0855] 2) Instruct the fifth network function to indicate the eighth information;

[0856] 3) Instruct the terminal device to indicate the eighth session information;

[0857] 4) Instruct the terminal device to indicate part or all of the third session information, and the third session information is included in the third context information.

[0858] Wherein, the eighth information may be used to indicate at least one of the following:

[0859] Session transfer, session handover, session merger, cancellation of traffic splitting, release of associated session, preparation for session transfer, preparation for session handover, preparation for session merger, preparation for cancellation of traffic splitting, preparation for release of associated session.

[0860] Wherein, the eighth session information may be used for at least one of the following:

[0861] Establish a session based on the eighth session information;

[0862] Indicate an unaccepted session;

[0863] Indicate a released session.

[0864] Specifically, the eighth session information can be used for at least one of the following:

[0865] Establish a session based on the eighth session information;

[0866] Indicate an unaccepted session;

[0867] Indicate a released session.

[0868] Specifically, the third session information can be used for at least one of the following:

[0869] Indicate an accepted session;

[0870] Indicate a held session.

[0871] It should be noted that in the embodiments of the present application, the session information in the first session information, the second session information, the third session information, the fourth session information, the fifth session information, the sixth session information, the seventh session information, and the eighth session information can all include at least one of the following: DNN, S-NSSAI, APN, PDU session ID, EPS bearer ID, and session ID. However, these information in different session information may be different. That is to say, the first session information, the second session information, the third session information, the fourth session information, the fifth session information, the sixth session information, the seventh session information, and the eighth session information can be session information including different DNNs, different S-NSSAIs, different EPS bearer IDs, etc., respectively, corresponding to indicating multiple sessions.

[0872] It should also be noted that any of the above first session information, second session information, third session information, fourth session information, fifth session information, sixth session information, seventh session information, and eighth session information can include a session information list, that is, the above any session information can include the relevant information of multiple sessions.

[0873] Optionally, in some embodiments, the first information may further include first indication information, and the first indication information can be used to indicate at least one of the following:

[0874] At least one of session merge, context merge, stop switching (Switch), stop steering (Steer), stop splitting (Split), stop dual transmission, stop multi-transmission, and stop concurrent transmission;

[0875] Any one of stopping dual registration, maintaining dual registration, stopping multi-registration, maintaining multi-registration, stopping dual connection, stopping multi-connection, stopping dual access, stopping multi-access, maintaining dual connection, maintaining multi-connection, maintaining dual access, and maintaining multi-access.

[0876] It can be understood that when the first indication information is used to indicate at least one of session merging, context merging, stopping handover, stopping diversion, stopping splitting, stopping dual transmission, stopping multi-transmission, stopping concurrent transmission, stopping dual registration, stopping multi-registration, stopping dual connection, stopping multi-connection, stopping dual access, and stopping multi-access, the network side can be triggered to reduce the number of connections of the terminal device under the same network, thereby improving communication efficiency.

[0877] It should be noted that Figure 10 The device shown can implement Figure 2 the method shown and can achieve the same technical effect. Therefore, the description is relatively simple, and for related parts, reference can be made to the description of the Figure 2 embodiment shown above.

[0878] As Figure 11 shown, an embodiment of the present application provides an information interaction device 1100, which can be applied to a terminal device. The device 1100 may include: an information sending module 1101.

[0879] The information sending module 1101 is configured to send first information to a first network function, where the first information includes a first identifier and a second identifier.

[0880] Wherein, the first identifier is related to a third identifier, and the second identifier is related to a fourth identifier.

[0881] Optionally, the first information further includes first indication information, where the first indication information is used to indicate at least one of the following:

[0882] at least one of session merging, context merging, stopping handover Switch, stopping diversion Steer, stopping splitting Split, stopping dual transmission, stopping multi-transmission, and stopping concurrent transmission;

[0883] Any one of stopping dual registration, maintaining dual registration, stopping multi-registration, maintaining multi-registration, stopping dual connection, stopping multi-connection, stopping dual access, stopping multi-access, maintaining dual connection, maintaining multi-connection, maintaining dual access, and maintaining multi-access.

[0884] Optionally, the first identifier, the third identifier, the second identifier, and the fourth identifier are related to at least one of the following: user equipment, end user, subscribed user, and the terminal device.

[0885] Optionally, the third identifier is different from the fourth identifier.

[0886] Optionally, the first information is included in a first message sent by the terminal device, where the first message is one of messages such as a mobility update message, a registration update message, a registration request message, a TAU, and a RAU.

[0887] Optionally, the first identifier includes at least one of the following:

[0888] The first GUTI;

[0889] The first mapped GUTI obtained from the first GUTI.

[0890] Optionally, the second identifier includes at least one of the following:

[0891] The second GUTI;

[0892] The second mapped GUTI obtained from the second GUTI.

[0893] Optionally, the third identifier includes at least one of the following:

[0894] The first SUPI;

[0895] The first IMSI.

[0896] Optionally, the fourth identifier includes at least one of the following:

[0897] The second SUPI;

[0898] The second IMSI.

[0899] In some embodiments, the first identifier is the first mapped GUTI, and the second identifier is the second GUTI, or the first identifier is the first GUTI, and the second identifier is the second mapped GUTI.

[0900] Optionally, Figure 3 The method shown may further include:

[0901] The terminal device receives at least one of the following indicated by the first network function:

[0902] The eighth session information;

[0903] The third session information.

[0904] Wherein, the eighth session information is used for at least one of the following:

[0905] Establish a session based on the eighth session information;

[0906] Indicate an unaccepted session;

[0907] Indicates the released session.

[0908] Wherein, the third session information is used for at least one of the following:

[0909] Indicates the accepted session;

[0910] Indicates the held session.

[0911] Optionally, the information sending module can be specifically used for: when the terminal device decides to execute any one of the following, sending the first information to the first network function:

[0912] 1) Stopping at least one of dual connection, multi-connection, dual access, multi-access, dual transmission, multi-transmission, concurrent transmission, dual registration, multi-registration, session merging, context merging, stopping switching (Switch), stopping steering (Steer), and stopping splitting (Split);

[0913] 2) Starting at least one of single connection, single access, single transmission, and single registration.

[0914] It can be understood that when the terminal device decides to stop the dual connection and sends the first information to the first network function, if it receives the eighth session information returned by the first network function, and the eighth session information is used to indicate the released session, it can cancel or release the corresponding local session, thereby stopping the dual connection and switching to a single connection. The same applies to other cases.

[0915] It should be noted that Figure 11 The shown device can implement Figure 3 The shown method and can achieve the same technical effects. Therefore, the description is relatively simple, and for related parts, reference can be made to the description of the Figure 3 Shown embodiment above.

[0916] As Figure 12 Shown, an embodiment of the present application provides an information interaction device 1200, which can be applied to the second network function. The device 1200 may include: an information receiving module 1201 and an information sending module 1202.

[0917] The information receiving module 1201 is used to receive the second indication information from the first network function.

[0918] The information sending module 1202 is used to send the first context information to the first network function based on the second indication information, and delete or invalidate the first session information, wherein the first session information is included in the first context information.

[0919] It should be noted that Figure 12 The shown device can implementFigure 4 The method shown, and can achieve the same technical effects, so the description is relatively simple. For related parts, reference can be made to the description of the Figure 4 embodiment shown above.

[0920] As Figure 13 shown, an embodiment of the present application provides an information interaction device 1300, which can be applied to the third network function. The device 1300 may include: an information receiving module 1301 and an information sending module 1302.

[0921] The information receiving module 1301 is configured to receive second indication information from the first network function.

[0922] The information sending module 1302 is configured to send second context information to the first network function based on the second indication information, and delete or invalidate second session information, where the second session information is included in the second context information.

[0923] It should be noted that Figure 13 the device shown can implement Figure 5 the method shown, and can achieve the same technical effects, so the description is relatively simple. For related parts, reference can be made to the description of the Figure 5 embodiment shown above.

[0924] As Figure 14 shown, an embodiment of the present application provides an information interaction device 1400, which can be applied to the fifth network function. The device 1400 may include: an information receiving module 1401 and an information indicating module 1402.

[0925] The information receiving module 1401 is configured to receive eighth information indicated by the first network function.

[0926] The information indicating module 1402 is configured to, based on the eighth information, instruct the eighth network function to forward data.

[0927] Wherein, the eighth information is used to indicate at least one of the following:

[0928] session transfer, session handover, session merge, cancel traffic splitting, associated session release, prepare session transfer, prepare session handover, prepare session merge, prepare cancel traffic splitting, associated session prepare release.

[0929] It should be noted that Figure 14 the device shown can implement Figure 6 the method shown, and can achieve the same technical effects, so the description is relatively simple. For related parts, reference can be made to the description of the Figure 6 embodiment shown above.

[0930] AsFigure 15 As shown in Figure 15 , an embodiment of the present application provides an information interaction device 1500, which can be applied to the ninth network function. The device 1500 may include: an information sending module 1501.

[0931] The information sending module 1501 is configured to perform any one of the following:

[0932] Broadcasting the fourth indication information or sending the fourth indication information to a terminal device.

[0933] Wherein, the fourth indication information indicates at least one of the following:

[0934] Supporting context merging, supporting session merging, supporting registration mode conversion, supporting Switching, supporting Steering, and supporting Splitting.

[0935] Wherein, the registration mode conversion includes: converting from a single registration mode to a dual registration mode, converting from a dual registration mode to a single registration mode, and so on.

[0936] It should be noted that Figure 15 the device shown in Figure 15 can implement Figure 7 the method shown in Figure 7 and can achieve the same technical effects. Therefore, the description is relatively simple, and for related parts, reference can be made to the description of the Figure 7 embodiment shown in Figure 7 .

[0937] It should be noted that the information interaction device in the embodiment of the present application may be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device may be a terminal or other devices other than a terminal. Exemplarily, the terminal may include, but is not limited to, the types of terminal 01 listed above, and other devices may be a server, a Network Attached Storage (NAS), etc. The embodiment of the present application does not make specific limitations.

[0938] Optionally, as Figure 16 shown in Figure 16 , the embodiment of the present application further provides a communication device 1600, including a processor 1601 and a memory 1602. A program or instruction that can run on the processor 1601 is stored on the memory 1602. For example, when the communication device 1600 is a terminal, when the program or instruction is executed by the processor 1601, it implements each step of the above information interaction method embodiment and can achieve the same technical effects.

[0939] The embodiment of the present application further provides a terminal, including a processor and a communication interface. The communication interface is used to send the first information to the first network function. This terminal embodiment is the same as the above Figure 3Corresponding to the method embodiments on the terminal side, each implementation process and realization manner of the above method embodiments can be applied to this terminal embodiment, and the same technical effects can be achieved. Specifically, Figure 17 It is a schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.

[0940] The terminal 1700 includes, but is not limited to, at least some components such as a radio frequency unit 1701, a network module 1702, an audio output unit 1703, an input unit 1704, a sensor 1705, a display unit 1706, a user input unit 1707, an interface unit 1708, a memory 1709, and a processor 1710.

[0941] Those skilled in the art can understand that the terminal 1700 may further include a power source (such as a battery) for supplying power to each component. The power source can be logically connected to the processor 1710 through a power management system, so as to realize functions such as management of charging, discharging, and power consumption management through the power management system. Figure 17 The terminal structure shown in does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0942] It should be understood that in the embodiments of the present application, the input unit 1704 may include a graphics processing unit (GPU) 17041 and a microphone 17042. The graphics processor 17041 processes the image data of static pictures or videos obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 1706 may include a display panel 17061, and the display panel 17061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1707 includes at least one of a touch panel 17071 and other input devices 17072. The touch panel 17071 is also called a touch screen. The touch panel 17071 may include a touch detection device and a touch controller. The other input devices 17072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be elaborated here.

[0943] In the embodiments of the present application, after the radio frequency unit 1701 receives downlink data from the network side device, it can be transmitted to the processor 1710 for processing; in addition, the radio frequency unit 1701 can send uplink data to the network side device. Generally, the radio frequency unit 1701 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0944] The memory 1709 can be used to store software programs or instructions and various data. The memory 1709 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data. Among them, the first storage area may store an operating system, application programs or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 1709 may include volatile memory or non-volatile memory, or the memory 1709 may include both volatile and non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (Synchronous DRAM, SDRAM), a double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), an enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), a synchronous link dynamic random access memory (Synch link DRAM, SLDRAM), and a direct rambus random access memory (Direct Rambus RAM, DRRAM). The memory 1709 in the embodiments of the present application includes, but is not limited to, these and any other suitable types of memory.

[0945] The processor 1710 may include one or more processing units; optionally, the processor 1710 integrates an application processor and a modem processor. Among them, the application processor mainly processes operations related to the operating system, user interface, and application programs, etc., and the modem processor mainly processes wireless communication signals, such as a baseband processor. It can be understood that the above modem processor may not be integrated into the processor 1710 either.

[0946] Among them, the radio frequency unit 1701 can be used to send a first message to a first network function, and the first message includes a first identifier and a second identifier; among them, the first identifier is related to a third identifier, and the second identifier is related to a fourth identifier.

[0947] In an embodiment of the present application, since the terminal 1700 can send first information including a first identifier and a second identifier to a first network function, and the first identifier is related to a third identifier, and the second identifier is related to a fourth identifier, operations such as context merging and session invalidation can be triggered on the network side, so that after the connection of the terminal device under one network is updated or switched to another network, the number of connections under the same network is reduced, thereby improving the communication efficiency of the terminal device.

[0948] An embodiment of the present application also provides a network-side device, including a processor and a communication interface, and the communication interface is used for. This embodiment of the network-side device corresponds to the above-mentioned method embodiment of the network-side device. Each implementation process and implementation manner of the above-mentioned method embodiment can be applied to this embodiment of the network-side device, and the same technical effect can be achieved.

[0949] Specifically, an embodiment of the present application also provides a network-side device. As Figure 18 shown, the network-side device 1800 includes: an antenna 1801, a radio frequency device 1802, a baseband device 1803, a processor 1804, and a memory 1805. The antenna 1801 is connected to the radio frequency device 1802. In the uplink direction, the radio frequency device 1802 receives information through the antenna 1801 and sends the received information to the baseband device 1803 for processing. In the downlink direction, the baseband device 1803 processes the information to be sent and sends it to the radio frequency device 1802. The radio frequency device 1802 processes the received information and then sends it out through the antenna 1801.

[0950] In the above embodiments, the method executed by the network-side device can be implemented in the baseband device 1803, and the baseband device 1803 includes a baseband processor.

[0951] The baseband device 1803 may include, for example, at least one baseband board, and multiple chips are arranged on the baseband board. As Figure 18 shown, one of the chips is, for example, a baseband processor, which is connected to the memory 1805 through a bus interface to call the program in the memory 1805 and execute the network device operations shown in the above method embodiments.

[0952] The network-side device may further include a network interface 1806, and this interface is, for example, a common public radio interface (CPRI).

[0953] Specifically, the network-side device 18000 in the embodiment of the present invention further includes: instructions or programs stored on the memory 1805 and executable on the processor 1804. The processor 1804 calls the instructions or programs in the memory 1805 to execute Figure 10 、 Figure 12 、Figure 13 , Figure 14 and Figure 15 The methods executed by each module shown in any of the accompanying drawings in Figure 13 , Figure 14 , and Figure 15 achieve the same technical effects. To avoid repetition, they will not be elaborated here.

[0954] The embodiments of the present application further provide a readable storage medium. Programs or instructions are stored on the readable storage medium. When the programs or instructions are executed by a processor, each process of the above information interaction method embodiment is implemented, and the same technical effects can be achieved. To avoid repetition, they will not be elaborated here.

[0955] Wherein, the processor 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 disks, or optical discs, etc.

[0956] The embodiments of the present application further provide a chip. The chip 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 each process of the above information interaction method embodiment, and the same technical effects can be achieved. To avoid repetition, they will not be elaborated here.

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

[0958] The embodiments of the present application further provide a computer program / program product. The computer program / program product is stored in a non-volatile storage medium. The computer program / program product is executed by at least one processor to implement each process of the above information interaction method embodiment, and the same technical effects can be achieved. To avoid repetition, they will not be elaborated here.

[0959] The embodiments of the present application further provide a communication system, including: a terminal and a network-side device. The terminal can be used to execute the steps of the information interaction method as described in Figure 3 The network-side device can be used to execute the steps of the information interaction method as described in Figure 2 , Figure 4 , Figure 5 , Figure 6 and Figure 7 shown in any of the accompanying drawings.

[0960] It should be noted that, in this document, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, such that a process, method, article or device comprising a series of elements not only includes those elements but also other elements not expressly listed, or further includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "comprising one..." does not exclude the existence of additional identical elements in the process, method, article or device comprising that element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the reverse order according to the functions involved. For example, the described methods may be performed in an order different from that described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0961] Through the description of the above embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus a necessary general hardware platform. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation. Based on such understanding, the technical solution of the present application, in essence or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disc) and includes several instructions for causing a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of the present application.

[0962] The embodiments of the present application have been described above in conjunction with the accompanying drawings. However, the present application is not limited to the above specific embodiments. The above specific embodiments are merely illustrative and not restrictive. Under the inspiration of the present application, those of ordinary skill in the art can also make many forms without departing from the purpose of the present application and the scope protected by the claims, and all of them fall within the protection scope of the present application.

Claims

1. An information interaction method, characterized in that, The method includes: A first network function receives first information, where the first information includes a first identifier and a second identifier; The first network function performs a first operation based on first context information and second context information; Wherein, the first operation includes at least one of the following: Generating, determining, or judging third context information; Sending the third context information to a seventh network function; Performing a third operation; Sending at least one of the following to a fourth network function: Second information; Third information and fourth information; Wherein, the first context information is related to the first identifier; the second context information is related to the second identifier; Wherein, the second information includes any one of the following: A third identifier; A third identifier and at least one of the following: first session information, first identifier association information, a fourth identifier, second session information, a registration indication or a location update indication, a deregistration indication or a location cancellation indication; Wherein, the third information includes a third identifier and a deregistration indication or a location cancellation indication; Wherein, the fourth information includes a fourth identifier and a registration indication or a location update indication; Wherein, the third operation includes at least one of the following: Instructing a fifth network function to create, update, or release a session or session context; Instructing an eighth information to the fifth network function; Instructing an eighth session information to a terminal device; Instructing a third session information to a terminal device; Wherein, the eighth information is used to indicate at least one of the following: Session transfer, session handover, session merger, cancellation of traffic splitting, release of associated session, preparation for session transfer, preparation for session handover, preparation for session merger, preparation for cancellation of traffic splitting, preparation for release of associated session; Wherein, the eighth session information is used for at least one of the following: Establishing a session based on the eighth session information; Indicating an unaccepted session; Indicating a released session; Wherein, the third session information is used for at least one of the following: Indicating an accepted session; Indicating a held session.

2. The method according to claim 1, wherein The first information further includes first indication information, where the first indication information is used to indicate at least one of the following: At least one of session merger, context merger, stop of switching, stop of steering, stop of splitting, stop of dual transmission, stop of multi-transmission, stop of concurrent transmission; Any one of stop of dual registration, maintaining dual registration, stop of multi-registration, maintaining multi-registration, stop of dual connection, stop of multi-connection, stop of dual access, stop of multi-access, maintaining dual connection, maintaining multi-connection, maintaining dual access, maintaining multi-access.

3. The method according to claim 1 or 2, characterized in that, The method further includes at least one of the following: The first network function obtains the first context information from a second network function based on the first identifier; The first network function receives the first context information from a second network function; The first network function obtains the second context information from a third network function based on the second identifier; The first network function receives the second context information from a third network function.

4. The method according to claim 3, characterized in that The method further includes: The first network function sends second indication information to the second network function or the third network function based on the first information; Wherein, the second indication information is used to indicate at least one of the following: Maintain registration and transfer the session.

5. The method according to any one of claims 1 to 4, characterized in that The first context information is related to a third identifier, the second context information is related to a fourth identifier, the third identifier is different from the fourth identifier, or, the third identifier is different from the fourth identifier, and the third context information includes any one of the third identifier and the fourth identifier.

6. The method according to any one of claims 1 to 5, characterized in that, The first identifier, and / or the third identifier, and / or the second identifier, and / or the fourth identifier are related to at least one of the following: User equipment; End user; Subscribed user; Terminal device.

7. The method according to any one of claims 1 to 6, characterized in that The execution of the first operation is further based on third indication information, where the third indication information is received by the first network function from at least one of a fourth network function and a fifth network function, or, the third indication information is included in at least one of the following: The first information; The first context information; The second context information.

8. The method according to claim 7, characterized in that, The third indication information includes at least one of the following: Second identifier association information; Dual registration indication or multi-registration indication; Fifth identifier.

9. The method according to claim 8, wherein The third identifier is different from the fifth identifier; and / or, the fifth identifier includes at least one of the following: Third Subscribed User Permanent Identifier (SUPI); Third International Mobile Subscriber Identity (IMSI).

10. The method according to any one of claims 1 to 9, characterized in that, The first context information includes the first session information, the second context information includes the second session information, and the method further includes: The first network function performs a second operation based on any one of the following: The first session information; The second session information; The first session information and the second session information; The first context information and the second session information; The first session information and the second context information; where the second operation includes at least one of the following: Generate, determine, or decide third session information; Include the third session information in the third context information.

11. The method according to claim 10, characterized in that, The method includes: The first network function further performs the second operation based on seventh information; where the seventh information is received by the first network function from at least one of a fourth network function and a fifth network function, or the seventh information is included in at least one of the following: first context information, second context information; where the seventh information includes at least one of the following: Fourth session information; Fifth session information; Sixth session information; Session association information; where the fifth session information indicates at least one of allowed, accepted, subscribed session information; where the sixth session information indicates disallowed or rejected session information.

12. The method according to claim 11, wherein The session association information includes at least one of the following: IP address information; Transport address information; Association ID; A pair of session information including seventh session information and eighth session information.

13. The method according to any one of claims 1 to 12, characterized in that, The session information includes at least one of the following: Data Network Name (DNN); Single Network Slice Selection Assistance Information (S-NSSAI); Access Point Name (APN); Protocol Data Unit (PDU) session ID; Evolved Packet System (EPS) bearer ID; Session ID.

14. The method according to any one of claims 10 to 13, characterized in that, The first network function performs a third operation based on the first context information and the second context information, including: The first network function performs the third operation based on at least one of the following: The third session information and the first session information; The third session information and the second session information; The third session information.

15. The method according to any one of claims 1 to 14, characterized in that The first network function receives first information, including at least one of the following: The first network function receives the first information from the seventh network function; The first network function receives the first information from the terminal device.

16. The method according to claim 15, characterized in that The first information is included in a first message sent by the terminal device, where the first message is one of a mobility update message, a registration update message, a registration request message, a tracking area update message TAU, and a routing area update message RAU.

17. The method according to any one of claims 1 to 16, characterized in that The first identifier includes at least one of the following: A first globally unique temporary identifier GUTI; A first mapped GUTI obtained from the first GUTI; The second identifier includes at least one of the following: A second GUTI; A second mapped GUTI obtained from the second GUTI; And / or, the third identifier includes at least one of the following: A first subscribed user permanent identifier SUPI; A first international mobile subscriber identity IMSI; And / or, the fourth identifier includes at least one of the following: A second SUPI; A second IMSI.

18. An information interaction method, characterized in that, The method includes: The terminal device sends first information to the first network function, where the first information includes a first identifier and a second identifier; Wherein, the first identifier is related to a third identifier, and the second identifier is related to a fourth identifier.

19. The method according to claim 18, wherein The first information further includes first indication information, where the first indication information is used to indicate at least one of the following: At least one of session merging, context merging, stopping switching, stopping steering, stopping splitting, stopping dual transmission, stopping multi-transmission, and stopping concurrent transmission; Any one of stopping dual registration, maintaining dual registration, stopping multi-registration, maintaining multi-registration, stopping dual connection, stopping multi-connection, stopping dual access, stopping multi-access, maintaining dual connection, maintaining multi-connection, maintaining dual access, and maintaining multi-access.

20. The method according to claim 18 or 19, characterized in that, The first identifier, and / or the third identifier, and / or the second identifier, and / or the fourth identifier is related to at least one of the following: A user equipment; An end user; A subscribed user; The terminal device.

21. The method according to any one of claims 18 to 20, characterized in that, The third identifier is different from the fourth identifier.

22. The method according to any one of claims 18 to 21, characterized in that, The first information is included in a first message sent by the terminal device, where the first message is one of a mobility update message, a registration update message, a registration request message, a tracking area update message TAU, and a routing area update message RAU.

23. The method according to any one of claims 18 to 22, characterized in that, The first identifier includes at least one of the following: A first globally unique temporary identifier GUTI; A first mapped GUTI obtained from the first GUTI; And / or, the second identifier includes at least one of the following: A second GUTI; A second mapped GUTI obtained from the second GUTI; And / or, the third identifier includes at least one of the following: A first subscribed user permanent identifier SUPI; A first international mobile subscriber identity IMSI; And / or, the fourth identifier includes at least one of the following: A second SUPI; A second IMSI.

24. The method according to claim 23, wherein The first identifier is the first mapped GUTI, and the second identifier is the second GUTI, or the first identifier is the first GUTI, and the second identifier is the second mapped GUTI.

25. The method according to any one of claims 18 to 24, characterized in that, It further includes: The terminal device receives at least one of the following indicated by the first network function: Eighth session information; Third session information; Wherein, the eighth session information is used for at least one of the following: Establishing a session based on the eighth session information; Indicating an unaccepted session; Indicating a released session; Wherein, the third session information is used for at least one of the following: Indicating an accepted session; Indicating a held session.

26. The method according to any one of claims 18 to 25, characterized in that, The terminal device sends first information to the first network function, including: When the terminal device decides to perform any one of the following, it sends the first information to the first network function: Stopping at least one of dual connection, multi-connection, dual access, multi-access, dual transmission, multi-transmission, concurrent transmission, dual registration, multi-registration, session merging, context merging, stopping switching (Switch), stopping steering (Steer), and stopping splitting (Split); Starting at least one of single connection, single access, single transmission, and single registration.

27. The method according to any one of claims 18 to 26, characterized in that The method further includes: The terminal device receives fourth indication information from the ninth network function; Wherein, the terminal device sends first information to the first network function, including: The terminal device sends the first information to the first network function based on the fourth indication information.

28. The method according to claim 27, wherein The fourth indication information indicates at least one of the following: Supporting context merging, supporting session merging, supporting registration mode conversion.

29. An information interaction method, characterized in that, The method includes: The second network function receives second indication information from the first network function; The second network function sends first context information to the first network function based on the second indication information, and deletes or invalidates the first session information, wherein the first session information is included in the first context information.

30. The method according to claim 29, wherein The method further includes: The second network function retains the part of the first context information other than the first session information.

31. An information interaction method, characterized in that The method includes: The fifth network function receives eighth information indicated by the first network function; The fifth network function, based on the eighth information, instructs the eighth network function to forward data; Wherein, the eighth information is used to indicate at least one of the following: Session transfer, session handover, session merging, cancellation of splitting, associated session release, preparation for session transfer, preparation for session handover, preparation for session merging, preparation for cancellation of splitting, associated session preparation for release.

32. An information interaction method, characterized in that, The method includes: The ninth network function performs any one of the following: Broadcasting the fourth indication information, sending the fourth indication information to the terminal device; Wherein, the fourth indication information indicates at least one of the following: Supporting context merging, supporting session merging, supporting registration mode conversion, supporting switching (Switch), supporting steering (Steer), supporting splitting (Split).

33. The method according to claim 32, wherein The ninth network function includes any one of the following: Access network node, core network function.

34. An information interaction device, characterized in that, The device includes: The first functional module is used to register the first network based on the third identifier; The second functional module is used to register the second network based on the fourth identifier.

35. The apparatus according to claim 34, wherein the third identifier comprises at least one of the following: The first Subscriber Permanent Identifier (SUPI); The first International Mobile Subscriber Identity (IMSI); And / or, the fourth identifier comprises at least one of the following: The second SUPI; The second IMSI.

36. The device according to claim 34 or 35, characterized in that, The first functional module is further used to perform any one of the following: Obtain second context information from the second functional module, where the second context information includes a second identifier; Send first context information to the second functional module, where the first context information includes a first identifier; Obtain second context information from the second functional module, where the second context information includes a seventh identifier, and the first functional module generates a second identifier based on the seventh identifier; Send first context information to the second functional module, where the second context information includes an eighth identifier, and the second functional module generates a first identifier based on the eighth identifier; Wherein, the first identifier comprises at least one of the following: The first Globally Unique Temporary Identifier (GUTI); The second mapped GUTI obtained from the first GUTI; Wherein, the second identifier comprises at least one of the following: The second GUTI; The second mapped GUTI obtained from the second GUTI; Wherein, the seventh identifier includes the second GUTI; Wherein, the eighth identifier includes the first GUTI; Wherein, the first identifier is related to the third identifier; Wherein, the second identifier is related to the fourth identifier.

37. The device according to any one of claims 34 to 36, characterized in that, The first functional module is further used to: send first information to a first network function; Wherein, the first information includes the first identifier and the second identifier; Wherein, the first identifier comprises at least one of the following: The first GUTI; The first mapped GUTI obtained from the first GUTI.

38. The apparatus according to claim 37, wherein The first identifier is the first mapped GUTI and the second identifier is the second GUTI, or the first identifier is the first GUTI and the second identifier is the second mapped GUTI.

39. The device according to claim 37 or 38, characterized in that, The first information further includes first indication information; Wherein, the first indication information is used to indicate at least one of the following: At least one of session merge, context merge, stop switch, stop steer, stop split, stop dual transmission, stop multi - transmission, stop concurrent transmission; Any one of stop dual registration, maintain dual registration, stop multi - registration, maintain multi - registration, stop dual connection, stop multi - connection, stop dual access, stop multi - access, maintain dual connection, maintain multi - connection, maintain dual access, maintain multi - access.

40. The device according to any one of claims 34 to 39, characterized in that The first functional module is further used to: Send at least one of the following to the second functional module: Deregistration, local deregistration, maintain registration, session release, session local release, session information.

41. The apparatus according to any one of claims 34 to 39, wherein The first functional module is further used to: receive at least one of the following from the second functional module: Deregistration, local deregistration, registration retention, session release, local session release, session information; The first functional module is further configured to: perform at least one of the following: Deregistration, local deregistration, session release, local session release, registration retention.

42. The apparatus according to claim 37 or 41, wherein The first functional module is further configured to: receive fourth indication information from a ninth network function; Wherein, the sending of the first information to the first network function includes: Sending the first information to the first network function based on the fourth indication information; Wherein, the fourth indication information indicates at least one of the following: Support for context merging, support for session merging, support for registration mode conversion.

43. An information interaction method, characterized in that, Including: A terminal device or a seventh network function sends first information to a first network function, where the first information includes a first identifier and a second identifier; The first network function receives the first information and performs a first operation based on first context information and second context information; Wherein, the first operation includes at least one of the following: Generating, determining, or judging third context information; Sending the third context information to the seventh network function; Performing a third operation; Sending at least one of the following to a fourth network function: Second information; Third information and fourth information; Wherein, the first context information is related to the first identifier; the second context information is related to the second identifier; Wherein, the second information is used to indicate a third identifier or information associated with the third identifier; Wherein, the third information includes a third identifier and a deregistration indication or a location cancellation indication; Wherein, the fourth information includes a fourth identifier and a registration indication or a location update indication; Wherein, the third identifier is related to the first identifier, and the fourth identifier is related to the second identifier; Wherein, the third operation includes at least one of the following: Instructing a fifth network function to create, update, or release a session or session context; Instructing an eighth information to the fifth network function; Instructing an eighth session information to the terminal device; Instructing a third session information to the terminal device; Wherein, the eighth information is used to indicate at least one of the following: Session transfer, session handover, session merging, cancellation of traffic splitting, associated session release, preparation for session transfer, preparation for session handover, preparation for session merging, preparation for cancellation of traffic splitting, associated session preparation for release; Wherein, the eighth session information is used for at least one of the following: Establishing a session based on the eighth session information; Indicating an unaccepted session; Indicating a released session; Wherein, the third session information is used for at least one of the following: Indicating an accepted session; Indicating a retained session.

44. The method according to claim 43, wherein Further includes at least one of the following: The first network function sends second indication information to a second network function based on the first identifier, the second network function sends the first context information to the first network function based on the second indication information, and deletes or invalidates the first session information; The first network function sends second indication information to a third network function based on the second identifier. The third network function sends the second context information to the first network function based on the second indication information, and deletes or invalidates the second session information; Wherein, the first session information is included in the first context information; Wherein, the second session information is included in the second context information.

45. The method according to claim 43 or 44, characterized in that, Further included: A ninth network function performs any one of the following: broadcasting fourth indication information, sending fourth indication information to a terminal device; Wherein, the fourth indication information indicates at least one of the following: Supporting context merging, supporting session merging, supporting registration mode conversion; The terminal device receives the fourth indication information and sends first information to the first network function based on the fourth indication information.

46. A network-side device, characterized in that, Comprising a processor and a memory, the memory stores a program or instructions that can run on the processor. When the program or instructions are executed by the processor, the steps of the information interaction method according to any one of claims 1 to 17 are implemented, or when the program or instructions are executed by the processor, the steps of the information interaction method according to any one of claims 29 to 35 are implemented.

47. A terminal, characterized in that, Comprising a processor and a memory, the memory stores a program or instructions that can run on the processor. When the program or instructions are executed by the processor, the steps of the information interaction method according to any one of claims 18 to 28 are implemented.

48. A readable storage medium, characterized in that, The program or instructions are stored on the readable storage medium. When the program or instructions are executed by the processor, the steps of the information interaction method according to any one of claims 1 to 17, 29 to 33 are implemented, or when the program or instructions are executed by the processor, the steps of the information interaction method according to any one of claims 18 to 28 are implemented.

Images