Methods, apparatuses, electronic devices and non-volatile storage media for data interaction

Abstract

This application discloses a method, apparatus, electronic device, and non-volatile storage medium for data interaction. The method includes: an Access and Mobility Management Function (AMF) entity receiving a network handover request message from a Next-Generation Radio Access Network (NG-RAN), wherein the network handover request message instructs a User Equipment (UE) to hand over from a 5G network to a 4G network; the AMF entity determining a target Mobility Management Equipment (MME) entity, wherein the target MME entity is the MME entity in the 4G network area to which the user equipment is handing over; and the AMF entity sending a relocation request to the target MME entity, requesting the target MME entity to establish a new connection for the UE in the 4G network. This application solves the technical problem that the handover from 5G to 4G between the AMF entity and the target MME entity requires numerous interaction steps, resulting in low handover efficiency and a poor user experience.

Description

Technical Field

[0001] This application relates to the field of satellite communications, and more specifically, to a method, apparatus, electronic device, and non-volatile storage medium for data interaction. Background Technology

[0002] 5G communication systems are integrated with 4G communication systems, meaning that their network architectures, physical layer transmission methods, and transmission protocols are all integrated. The integration of 5G and 4G communication systems into a space-ground converged network can provide users with high-quality communication services.

[0003] In a converged space-ground network, the handover from 5G to 4G networks between the Access and Mobility Management Function (AMF) entity and the Mobility Management Entity (MME) involves numerous interactive steps. During the handover process, User Equipment (UE) may need to allocate resources between the 5G and 4G core networks and perform rapid handover between these allocated resources. In related technologies, the handover process between the AMF and MME involves many signaling interaction steps, resulting in lengthy network resource allocation and handover resource allocation times. This leads to increased network resource waiting time during the handover process, ultimately impacting network connectivity performance, reducing handover efficiency, and degrading user experience.

[0004] There is currently no effective solution to the above problems. Summary of the Invention

[0005] This application provides a data interaction method, apparatus, electronic device, and non-volatile storage medium to at least solve the technical problem that the handover from 5G network to 4G network between an AMF entity and a target MME entity requires many interaction steps, resulting in low handover efficiency and poor user experience.

[0006] According to one aspect of the embodiments of this application, a data interaction method is provided, comprising: an Access and Mobility Management Function (AMF) entity receiving a network handover request message from a Next Generation Radio Access Network (NG-RAN), wherein the network handover request message is used to instruct a User Equipment (UE) to hand over from a 5G network to a 4G network; the AMF entity determining a target Mobility Management Entity (MME), wherein the target MME is an MME entity in the 4G network area to which the user equipment has been handed over; and the AMF entity sending a relocation request to the target MME, wherein the relocation request is used to notify the target MME that a User Equipment (UE) will hand over from a 5G network to a 4G network, and to request the target MME to establish a new connection for the UE in the 4G network.

[0007] In some embodiments of this application, after the AMF entity sends a relocation request to the target MME entity, the method further includes: the AMF entity receiving a response message sent by the target MME entity, wherein the response message is a response message to the relocation request; after receiving the response message, the AMF entity sends a session context request to the Session Management Function (SMF) entity / Packet Data Network Gateway Control Plane (PGW-C) entity, wherein the session context request includes tunnel information from the Evolved Universal Terrestrial Radio Access Network (E-UTRAN) core network side of the Serving Gateway (SGW) and bearer information of the Evolved Packet System (EPS).

[0008] In some embodiments of this application, after the AMF entity sends a session context request to the Session Management Function (SMF) entity / Packet Data Network Gateway (PDB) Control Plane PGW-C entity, the method further includes: when the 5G core network has not established a 5G bearer for the UE, instructing the PMF entity / PDB-C entity to allocate tunnel information to the User Plane Function (UPF) entity / PDB-U entity of the PDB, wherein the tunnel information is the tunnel information used by the user plane function during data transmission.

[0009] In some embodiments of this application, the SMF entity and the User Plane Function UPF entity are core network elements for allocating tunnel information in a 5G network, while the PGW-C entity and the PGW-U entity are core network elements for allocating tunnel information in a 4G network.

[0010] In some embodiments of this application, after allocating tunnel information, the method further includes: the AMF entity receiving a notification message sent by the target MME entity, wherein the notification message is used to notify the AMF entity that the handover from the 5G network to the 4G network is complete, and the notification message includes tunnel information mapped from the 5G network to the 4G network.

[0011] In some embodiments of this application, the AMF entity determines the target MME entity based on network load, geographic location, or quality of service parameters.

[0012] In another aspect of the embodiments of this application, a data interaction method is also provided, including: a target mobility management entity (MME) receiving a relocation request sent by an access and mobility management function (AMF) entity; the target MME sending a session creation request to a serving gateway (SGW), wherein the session creation request does not carry tunnel information used by user plane functions during data transmission.

[0013] In some embodiments of this application, the MME entity receives a network handover request message sent by the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), wherein the network handover request message is used to instruct the user equipment to switch from a 5G network to a 4G network; the MME entity sends a relocation completion notification to the AMF entity and the SGW, wherein the relocation completion notification contains tunnel information mapped from the 5G network to the 4G network, wherein the tunnel information is the tunnel information used by the user plane function during data transmission.

[0014] In another aspect of the embodiments of this application, a data interaction apparatus is also provided, comprising: a receiving module, configured to receive a network handover request message from a Next Generation Radio Access Network (NG-RAN), wherein the network handover request message is used to instruct a user equipment (UE) to hand over from a 5G network to a 4G network; a determining module, configured to have the AMF entity determine a target Mobility Management Entity (MME), wherein the target MME is an MME in the 4G network area to which the user equipment (UE) has been handed over; and a sending module, configured to have the AMF entity send a relocation request to the target MME, wherein the relocation request is used to notify the target MME that a UE will hand over from a 5G network to a 4G network, and to request the target MME to establish a new connection for the UE in the 4G network.

[0015] In another aspect of the embodiments of this application, a data interaction system is also provided, including: an Access and Mobility Management Function (AMF) entity and a Target Mobility Management Entity (MME) entity; the AMF entity is used to receive a network handover request message from a Next Generation Radio Access Network (NG-RAN), wherein the network handover request message is used to instruct a User Equipment (UE) to hand over from a 5G network to a 4G network, determine a target MME entity, wherein the target MME entity is an MME entity in the 4G network area to which it is handover is performed, and send a relocation request to the target MME entity, wherein the relocation request is used to notify the target MME entity that a User Equipment (UE) will hand over from a 5G network to a 4G network, and request the target MME entity to establish a new connection for the UE in the 4G network; the target MME entity is used to receive the relocation request sent by the AMF entity and send a session creation request to the Serving Gateway (SGW), wherein the session creation request does not carry tunnel information used by the user plane function during data transmission.

[0016] In another aspect of the embodiments of this application, a non-volatile storage medium is also provided, wherein a program is stored in the non-volatile storage medium, and the program controls the device where the non-volatile storage medium is located to perform the above-mentioned data interaction method when it runs.

[0017] In another aspect of the embodiments of this application, an electronic device includes: a memory and a processor, the processor being configured to run a program stored in the memory, wherein the program, when running, performs the above-described method of data interaction.

[0018] In this embodiment, the Access and Mobility Management Function (AMF) entity receives a network handover request message from the Next Generation Radio Access Network (NG-RAN), whereby the network handover request message instructs a User Equipment (UE) to switch from a 5G network to a 4G network. The AMF entity identifies a target Mobility Management Entity (MME), where the target MME is the MME in the 4G network area to which the user equipment is switching. The AMF entity sends a relocation request to the target MME, which notifies the target MME that a UE will be switching from a 5G network to a 4G network and requests the target MME to establish a new connection for the UE in the 4G network. By simplifying the interaction steps between the AMF entity and the target MME, this solves the technical problem of low handover efficiency and poor user experience caused by the numerous interaction steps required for the handover from 5G to 4G between the AMF entity and the target MME. Attached Figure Description

[0019] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0020] Figure 1 This is a hardware structure block diagram of a computer terminal for implementing a data interaction method according to an embodiment of this application;

[0021] Figure 2 This is a flowchart illustrating a data interaction method provided according to an embodiment of this application;

[0022] Figure 3 This is a flowchart illustrating another data interaction method provided according to an embodiment of this application;

[0023] Figure 4 This is a schematic diagram illustrating the process of a user equipment (UE) switching from a 5G network to a 4G network according to an embodiment of this application.

[0024] Figure 5This is a schematic diagram illustrating an improved process for a user equipment (UE) to switch from a 5G network to a 4G network, according to an embodiment of this application.

[0025] Figure 6 This is a schematic diagram of the structure of a data interaction system provided according to an embodiment of this application;

[0026] Figure 7 This is a schematic diagram of a data interaction device provided according to an embodiment of this application. Detailed Implementation

[0027] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0028] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0029] To better understand the embodiments of this application, the technical terms involved in the embodiments of this application are explained below:

[0030] The Mobility Management Entity (MME) is primarily responsible for mobility management, including user location tracking, paging, and handover control. In the interoperability between 5G (5GS) and 4G (EPS) networks, the MME is a key network element on the 4G side, responsible for interacting with the AMF (Access and Mobility Management Function) in the 5G core network (5GC) to ensure continuity and quality of service when users handover between different networks. In the optimization methods for 5GS to EPS handover in converged space-ground networks, the enhanced functions of the MME play a crucial role in reducing network interactions and improving handover efficiency.

[0031] Next-Generation Radio Access Network (NG-RAN) is a part of the 5G network architecture, comprising 5G base stations and enhanced evolved terrestrial base stations (ETNs). These base stations connect to the 5G core network (5GC) via the NG interface. The main features of NG-RAN are support for higher data rates, lower latency, greater connection density, and more flexible network deployment and management.

[0032] The Session Management Function (SMF) is a key network function in the 5G core network (5GC), responsible for handling tasks related to session management. The SMF is responsible for establishing, modifying, and releasing Protocol Data Unit (PDU) sessions between the User Equipment (UE) and the Data Network (DN). It manages session states, including session policies and charging rules. The SMF selects the User Plane Function (UPF) to handle UE traffic and determines the forwarding path of data packets. In multi-access and mobility scenarios, the SMF is responsible for the handover and optimization of user plane paths. Based on policies and charging rules, the SMF controls the behavior of the User Plane Function (UPF) to ensure that traffic follows the correct policies and charging settings.

[0033] The Evolved Packet System (EPS) is the core network component of the 4G network. EPS primarily consists of the Evolved Packet Core (EPC), including components such as the MME, Serving Gateway (SGW), and Packet Data Network Gateway (PDN Gateway, PGW), providing functions such as data transmission, mobility management, and session management. In a converged space-ground network, EPS, as the core of the 4G network, interacts with the 5GS (5G System) to enable handover and data transmission between different networks.

[0034] The Packet Data Network Gateway Control plane (PGW-C) is responsible for control plane processing, including user and session management, such as the establishment, modification, and release of EPS bearers. In the transition from 5G to 4G, the PGW-C's role primarily involves managing EPS bearer contexts and interacting with the AMF and SMF in the 5G core network (5GC) to ensure user session continuity.

[0035] The Serving Gateway (SGW) is part of the evolved Packet Core (EPC) in Long Term Evolution (LTE) networks. Its primary responsibility is to route and forward data packets between the Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and the Evolved Packet System (EPS) bearer network. During handover and mobility management, the SGW is also responsible for managing user plane sessions, including establishing, modifying, and releasing user plane tunnels to ensure data flow continuity.

[0036] Evolved Universal Terrestrial Radio Access Network (E-UTRAN) is the radio access network component of the LTE (Long Term Evolution) system. It is an air interface defined by 3GPP (3rd Generation Partnership Project) to improve existing UMTS (Universal Mobile Telecommunication System) networks. E-UTRAN consists of eNodeBs (evolved Node Bs), which are interconnected via the X2 interface, while the connection between eNodeBs and EPS (Electronic Resource Sharing) is accomplished through the S1 interface. In E-UTRAN, radio resource management and control functions are centralized in the eNodeBs, which helps simplify the network architecture, reduce latency, and improve spectrum efficiency.

[0037] The Access and Mobility Management Function (AMF) is a key component of the 5G core network, responsible for handling access and mobility events, including user equipment (UE) registration, connection establishment, mobility management (such as handover and reselection), and session management between the UE and the network. In a converged space-ground network, the AMF acts as a bridge, coordinating between the 5G system (5GS) and the 4G system (EPS) to ensure smooth handover of UEs between different networks, providing uninterrupted communication services.

[0038] The Packet Data Network Gateway-User Plane (PGW-U) in 5G network architecture corresponds to a function of the User Plane Function (UPF). However, in 4G network architecture, it is part of the Packet Data Gateway (PGW), specifically handling the forwarding of user plane data. In 5G networks, the UPF is responsible for processing and forwarding Non-Access Stratum (NAS) data, including packet routing and forwarding, packet inspection, QoS (Quality of Service) policy enforcement, and billing data collection. In the scenario of 5GS to EPS handover in a satellite-terrestrial converged network, the PGW-U / UPF is responsible for establishing a user plane tunnel between the 5G System (5GS) and the EPS, ensuring that packets can be seamlessly forwarded from the 5G network to the 4G network, and vice versa. This function is crucial for ensuring continuity and quality of service during handover, especially in satellite communication scenarios, where efficient and stable user plane data transmission is key to maintaining network performance due to satellite link latency and bandwidth limitations.

[0039] In related technologies, the handover process from a 5G network to a 4G network for a User Equipment (UE) may require resource allocation between the 5G core network and the 4G core network, as well as rapid handover between allocated resources. During this handover process, the handover between the AMF and MME requires numerous signaling interaction steps, resulting in lengthy network resource allocation and handover resource allocation times. This leads to increased network resource waiting time during the handover process, ultimately affecting network connection performance, resulting in low handover efficiency and a poor user experience. Therefore, the handover between the AMF entity and the target MME entity requires numerous interaction steps, leading to low handover efficiency and a poor user experience. To address this issue, this application provides a related solution, which is detailed below.

[0040] According to an embodiment of this application, an embodiment of a data interaction method is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0041] The methods and embodiments provided in this application can be executed on mobile terminals, computer terminals, or similar computing devices. Figure 1A hardware block diagram of a computer terminal for implementing a method of data interaction is shown. Figure 1 As shown, the computer terminal 10 may include one or more processors 102 (shown as 102a, 102b, ..., 102n in the figure) 102 (processor 102 may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.), a memory 104 for storing data, and a transmission device 106 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of a BUS bus), a network interface, a power supply, and / or a camera. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the aforementioned electronic device. For example, computer terminal 10 may also include... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.

[0042] It should be noted that the aforementioned one or more processors 102 and / or other data processing circuits are generally referred to herein as "data processing circuits". These data processing circuits may be embodied, in whole or in part, in software, hardware, firmware, or any other combination thereof. Furthermore, the data processing circuits may be a single, independent processing module, or may be integrated, in whole or in part, into any other element within the computer terminal 10. As involved in the embodiments of this application, the data processing circuits serve as a form of processor control (e.g., selection of a variable resistor termination path connected to an interface).

[0043] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the data interaction method in this embodiment. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, thereby realizing the aforementioned data interaction method. The memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to the computer terminal 10 via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0044] The transmission device 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the communication provider of the computer terminal 10. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be a Radio Frequency (RF) module, used for wireless communication with the Internet.

[0045] The display may be, for example, a touchscreen liquid crystal display (LCD) that allows the user to interact with the user interface of the computer terminal 10.

[0046] In the above operating environment, this application embodiment provides a flowchart of a data interaction method, such as... Figure 2 As shown, the method includes the following steps:

[0047] In step S202, the Access and Mobility Management Function (AMF) entity receives a network handover request message from the Next Generation Radio Access Network (NG-RAN), wherein the network handover request message is used to instruct user equipment to switch from the 5G network to the 4G network.

[0048] The following is a specific example:

[0049] The AMF entity receives a handover request message from the source NG-RAN (i.e., the aforementioned NG-RAN). The source NG-RAN refers to the radio access network currently connected to by the mobile device (such as a mobile phone, IoT device, etc.) in the 5G network. The source NG-RAN decides to trigger a handover to EPS (Evolved Packet System, i.e., 4G network) and sends a handover request message to the AMF entity. This is the starting point of the handover process. The handover request message may contain the following: UE identification information (e.g., 5G-GUTI (Global Unique Temporary Identifier) ​​or S-TMSI (Short Term Mobility Subscriber Identity)) to uniquely identify the UE; Handover type (Handover type): explicitly indicating that this is a 5G to 4G handover so that the AMF entity can perform subsequent processing; Handover reason: possibly triggered by UE movement, network load balancing, changes in Quality of Service (QoS) requirements, etc.; Target RAN information: including the type of the target RAN (e.g., EPS or 5GS) and its identifier, such as the target eNB (Evolved Node). B, the ID of the 4G base station (or gNB (5G base station)) and possible N26 interface information, used for subsequent core network node selection; UE capability information: such as supported handover types, whether N26 interface is supported, etc., to help network decision-making. Quality of Service (QoS) requirements: ensuring that the network can provide a quality of service that meets the UE's needs.

[0050] Step S204: The AMF entity determines the target mobility management MME entity, wherein the target MME entity is the MME entity in the 4G network area to which the handover is taking place.

[0051] In the technical solution provided in step S204, the AMF entity determines the target MME entity based on network load, geographical location, or quality of service parameters.

[0052] The following is a specific example:

[0053] Network Load: The AMF entity can monitor the load of the entire network, including the load status of each MME (i.e., the MME entity mentioned above). The AMF entity will analyze the load of MMEs in the target area and select an MME with a relatively low load to avoid switching to an already busy MME, thereby reducing the risk of potential handover failure or service quality degradation.

[0054] Geographical Location: The AMF entity will consider the UE's location information and the geographical area covered by the target MME, and select the MME that is geographically closest to the UE's location. This can reduce transmission latency and improve handover efficiency. It will also refer to the coverage of the satellite network to ensure that the UE still maintains a good satellite signal after handover.

[0055] Quality of Service (QoS) parameters: The AMF entity (i.e., the AMF entity mentioned above) will evaluate the quality of service that the target MME can provide, including parameters such as bandwidth and latency. For UEs with high priority or special needs (such as emergency services, high-definition video streaming, etc.), the AMF entity may prioritize the selection of MMEs that can meet these QoS requirements. In a satellite-ground converged network, the QoS parameters may also consider the stability of the satellite link and the collaborative working capability between the terrestrial network and the satellite network.

[0056] Implementation steps:

[0057] When the AMF entity receives a network handover request message from the source NG-RAN, it evaluates the target MME based on the parameters mentioned above:

[0058] The AMF entity queries or obtains the load and location information of the target MME, as well as its QoS capabilities, from other network functions (such as NRF, Network Repository Function). Based on this information, the AMF entity selects an MME whose load, distance from the UE location, and QoS capabilities are all greater than a preset threshold as the target MME.

[0059] The AMF entity first selects the target MME entity, rather than sending a session context request (e.g., an Nsmf_PDUSessionContext request) to the SMF. The Nsmf_PDUSessionContext request is used to request or update session context information related to the user equipment (UE), including but not limited to tunnel information, QoS parameters, and billing information. During the 5G to 4G handover process, this request is used to ensure the correct establishment and maintenance of user plane data paths between different networks.

[0060] The following is a specific example:

[0061] The AMF entity sends a relocation request to the target MME (i.e., the aforementioned target MME entity). The relocation request is a critical step involving coordination between network nodes to ensure service continuity. When the AMF entity receives a handover request from the NG-RAN, indicating that the UE (User Equipment) is about to switch from the 5G network to the 4G network, it then sends a relocation request to the target MME. The AMF entity informs the target MME entity of the UE's location information and handover requirements through the relocation request message. In this way, the target MME entity can be selected to be responsible for the subsequent connection management of the UE in the EPS network. The UE information and required EPS bearer requirements included in the relocation request enable the MME entity to prepare for the establishment of the EPS bearer in advance, ensuring that the UE can seamlessly continue its data service when switching to the EPS network. This message triggers the reservation and allocation of resources in the EPS network, including but not limited to establishing a tunnel from the SGW to the PGW-U / UPF entity, to prepare for the UE's data transmission in the EPS network.

[0062] In step S206, the AMF entity sends a relocation request to the target MME entity. The relocation request is used to notify the target MME entity that a user equipment (UE) will switch from the 5G network to the 4G network, and to request the target MME entity to establish a new connection for the UE in the 4G network.

[0063] In the technical solution provided in step S206, after the AMF entity sends a relocation request to the target MME entity, the AMF entity receives a response message sent by the target MME entity, wherein the response message is a response message to the relocation request.

[0064] In the response message to the relocation request message, the MME provides user plane configuration information used by the UE in the EPS network (such as tunnel information for the SGW and PGW). This helps establish uplink and downlink data paths from the UE to the EPS network. Through the relocation request and its subsequent response, service continuity for the UE during handover can be ensured, service interruption time can be reduced, and network handover efficiency and user experience can be improved. This optimization is particularly important in satellite-terrestrial converged networks because it can reduce signaling interaction between satellite and terrestrial networks, reduce network latency, and improve handover success rate.

[0065] In the technical solution provided in step S206, after receiving the response message, the AMF entity sends a session context request to the Session Management Function (SMF) / Packet Data Network Gateway Control Plane (PGW-C) entity. The session context request includes tunnel information from the Evolved Universal Terrestrial Radio Access Network (E-UTRAN) core network side of the Serving Gateway (SGW) and bearer information from the Evolved Packet System (EPS).

[0066] After the AMF entity sends a session context request to the Session Management Function (SMF) / Packet Data Network Gateway Control Plane (PGW-C) entity, in the absence of a 5G bearer established for the UE in the 5G core network, it instructs the UPF entity / PGW-U to allocate tunnel information through the SMF / PGW-C entity. The tunnel information is the tunnel information used by the user plane function during data transmission. The SMF and the user plane function UPF entity are the core network elements for allocating tunnel information in the 5G network, while the PGW-C entity and PGW-U are the core network elements for allocating tunnel information in the 4G network.

[0067] The following is a specific example:

[0068] After receiving the response message, the AMF entity sends a session context request (e.g., an Nsmf_PDUSessionContext request) to the Session Management Function (SMF) / Packet Data Network Gateway Control Plane (PGW-C) entity. The session context request contains tunnel information from the Evolved Universal Terrestrial Radio Access Network (E-UTRAN) core network side of the Serving Gateway (SGW) and the Evolved Packet System (EPS) bearer information. EPS bearer information refers to information used to describe data transmission paths and attributes in a 4G network system. In the EPS network architecture, the data transmission channel between each User Equipment (UE) and the network is called a bearer. The EPS bearer is a logical connection established specifically for data services between the UE and the network. It includes QoS parameters, bearer identifiers, and network tunnel information for data transmission. When the SMF entity receives an Nsmf_PDUSessionContext request from the MME entity, if no 5G bearer is currently established (i.e., in the case where no 5G bearer is established for the UE in the 5G core network as described above), the PGW-C entity (equivalent to the SMF entity in the 5G network) instructs the PGW-U entity (equivalent to the UPF entity in the 5G network) to allocate tunnel information (e.g., the UPF entity's tunnel info). This tunnel information will be used to establish a user plane data path from the 5G network to the 4G network, ensuring continuous data transmission. The SMF entity and the UPF entity are the core network elements for allocating tunnel information in the 5G network, while the PGW-C entity and the PGW-U entity are the core network elements for allocating tunnel information in the 4G network. This optimization reduces the interaction steps during handover, especially for high-latency scenarios such as satellite communication, and can significantly improve network handover efficiency.

[0069] This application also provides a flowchart of another data interaction method, such as... Figure 3 As shown, the method includes the following steps:

[0070] Step S302: The target mobility management entity (MME) receives a relocation request sent by the access and mobility management function (AMF) entity.

[0071] In step S304, the target MME entity sends a session creation request to the service gateway SGW. The session creation request does not carry tunnel information used by the user plane function during data transmission.

[0072] In the technical solution provided in step S304, the MME entity receives a network handover request message sent by the evolved Universal Terrestrial Radio Access Network (E-UTRAN), wherein the network handover request message is used to instruct the user equipment to switch from the 5G network to the 4G network.

[0073] When the MME entity receives a relocation request from the source AMF entity, it will also send a session creation request to the SGW. The session creation request is used to ensure that the network can provide continuous network services to the UE, but does not carry tunnel information used by user plane functions during data transmission (e.g., PGW-U entity tunnel info).

[0074] The purpose of sending a session creation request to the SGW without carrying the PGW-U entity tunnel info is to optimize and simplify signaling interactions during the handover process, thereby improving network efficiency. In traditional handover procedures, the PGW-U entity tunnel info is transmitted in multiple steps, each requiring interaction between network nodes, which is particularly inefficient in high-latency environments such as satellite communication. By omitting this information in the initial transmission, the MME entity can more quickly initiate the session creation process, avoiding unnecessary tunnel information interactions before it is certain whether a handover to EPS is needed. This reduces the number of signaling interactions and handover latency. Specifically, omitting the PGW-U entity tunnel info avoids the complex tunnel establishment process in the initial stages of target MME selecting the SGW and establishing a connection with E-UTRAN. This optimization allows the network to establish the PGW-U entity tunnel only in more certain handover scenarios, reducing unnecessary network resource consumption. Especially in satellite-ground converged networks, due to the high latency of satellite links, reducing the number of signaling interactions has a significant positive impact on improving handover success rates and user experience. Finally, when the handover process reaches the point where a tunnel needs to be established between the PGW-U entity and the SGW, relevant information is exchanged. This ensures that each interaction is necessary, thereby optimizing the entire handover process.

[0075] After the UE successfully completes the handover in the target E-UTRAN cell, the MME entity sends a relocation completion notification to the AMF entity and SGW. The relocation completion notification includes tunnel information (e.g., PGW-U entity tunnel info after mapping from the 5G network to the 4G network). The tunnel information is the tunnel information used by user plane functions during data transmission.

[0076] The following is a specific example:

[0077] The MME entity sends a Relocation Complete Notification (e.g., Relocation Complete Notification) to the AMF entity and SGW. This message is used in mobile communication networks to notify the AMF entity that the handover or relocation process is complete. During the handover process between 5G and 4G networks, after the UE successfully connects to the target network (e.g., from 5GS to EPS) and completes all necessary network configurations, the control node of the target network (such as the target MME) sends a "Relocation Complete Notification" to the AMF entity, indicating that the UE has successfully switched to the target network and that all context information (such as tunnel information) has been correctly set.

[0078] After a successful UE handover, the target MME will not only notify the AMF entity that the handover is complete, but will also carry necessary tunnel information (e.g., PGW-U entity tunnel info after mapping from the 5G network to the 4G network) for subsequent network signaling interaction and user plane data transmission optimization.

[0079] This application also provides a schematic diagram of the process for a user equipment (UE) to switch from a 5G network to a 4G network, as shown in the embodiment. Figure 4 As shown, N26 represents the Mobility Management interface between 5GS and EPS, N4 represents the interface between SMF and UPF entities, and Nsmf_PDUSession_ContextRequest represents the SMF interface for requesting PDU session context information.

[0080] 1~2. NG-RAN decides to trigger a handover to EPS (i.e., a handover from 5G network to 4G network) and sends a handover request message to the source AMF (i.e., the aforementioned AMF entity).

[0081] 3-5. Based on the identifier of the target “RAN”, the source AMF (i.e., the AMF entity mentioned above) determines that it is a handover to the target E-UTRAN. Therefore, it requests the PGW-C / SMF (i.e., the PGW-C / SMF entity mentioned above) to provide the EPS connection information required by the target MME (i.e., the target MME entity mentioned above). If the downlink data arriving at the RAN needs to be forwarded to the target E-UTRAN through the PGW-U / UPF, then it needs to obtain the tunnel information (UPF tunnel info) of its node from the PGW-U / UPF in steps 4.1-4.2 and return it in step 5.

[0082] 4.1–4.2. In non-roaming or LBO roaming scenarios, when the PGW-C / SMF receives the Nsmf_PDUSession_ContextRequest interface used by the SMF to request PDU session context information, if the PGW-C / SMF determines that the EPS bearer information can be transmitted to the EPS, and the CN (core network side) tunnel information of the EPS bearer has not been previously assigned to the UE, then the PGW-C / SMF sends an N4 session modification to the PGW-U / UPF, establishes a CN tunnel for each EPS bearer, and provides the EPS bearer information to the source AMF. At this time, the PGW-U / UPF can receive uplink data packets from the E-UTRAN.

[0083] 5. The source AMF receives the PDU session context information in response.

[0084] 6. The source AMF selects a target MME based on the target E-UTRAN information provided by the source NG-RAN.

[0085] 7-8.1. The source AMF sends a relocation request message to the target MME, which then sends it to the SGW. Based on the PGW-U entity tunnel info obtained in step 5, an EPS uplink user plane data path is established from the SGW to the PGW-U / UPF.

[0086] 8.2. The SGW returns a session creation response to the target MME, carrying the tunnel information (tunnel info) allocated by the SGW to the E-UTRAN side (base station side).

[0087] 9.1. The target MME sends a handover request message to the target E-UTRAN, carrying the SGW base station-side tunnel info from step 8.2. This establishes an EPS uplink user plane data path from the target E-UTRAN to the SGW.

[0088] 9.2. The target E-UTRAN returns a handover response message to the target MME, carrying the E-UTRAN tunnel info it has assigned.

[0089] 10.1~10.2. The target MME sends a request to the SGW to establish an indirect tunnel with the UPF, carrying the E-UTRAN tunnel info from step 9.2. At this point, the downlink indirect forwarding path from the SGW to the target E-UTRAN is established.

[0090] 10.2 Return the response information from step 10.1, carrying the SGW CN-side tunnel info assigned by the SGW to the PGW-U / UPF.

[0091] 11. The target MME sends a relocation response message to the source AMF.

[0092] 12. The source AMF sends an Nsmf_PDUSessionContext request to the SMF, carrying the SGW CN-side tunnel info obtained in step 10.2 above.

[0093] 13.1. The SMF sends an N4 session modification request to the PGW-U / UPF to inform the PGW-U / UPF of the tunnel info on the SGW CN side, so as to establish a downlink forwarding tunnel from the PGW-U / UPF to the SGW.

[0094] 13.2-14 Return response information.

[0095] From cell 15 to 17, the source NG-RAN sends a handover command to the UE, and the UE then connects to the target cell.

[0096] 18. The target E-UTRAN sends a handover Notify to the target MME, and the target E-UTRAN considers the handover successful.

[0097] 19.1-19.2 The target MME notification source AMF handover has been completed.

[0098] 20–23. The MME also provides E-UTRAN tunnel information to the SGW and PGW-C / SMF to establish downlink data paths and switch downlink user plane paths to the target E-UTRAN access network.

[0099] 24-26. Finally, the UE initiates the tracking area update procedure (same as the S1-based handover procedure). The S1 interface refers to the interface between the Evolved UTRAN (E-UTRAN) and the Evolved Packet Core (EPC) in a 4G LTE network. Specifically, it connects the eNodeB (base station) with the MME (Mobility Management Entity) and S-GW (Serving Gateway). The S1 interface is divided into two parts: the control plane (S1-MME) and the user plane (S1-U). The S1-MME is used for control plane signaling interaction, and the S1-U is used for user plane data transmission. In the interoperability between 5G and 4G networks, the S1 interface still plays an important role in the 4G network portion.

[0100] If a dedicated bearer establishment request is made during the handover process, PGW-C / SMF will also trigger the establishment of the dedicated bearer. The network will also release any indirect forwarding tunnels that are no longer needed.

[0101] This application also provides an improved flowchart illustrating the process of a user equipment (UE) switching from a 5G network to a 4G network, as shown in the embodiment. Figure 5 As shown, it is for Figure 4 The following is a schematic diagram illustrating the improved 5G network to 4G network switching process using an embodiment of this method.

[0102] 1~2. Same Figure 4 After steps 1-2, the AMF entity first proceeds to step 6 to select the target MME entity, and then proceeds without further steps. Figure 4 In steps 3-5, the AMF entity first selects the target MME entity instead of sending a session context request (e.g., an Nsmf_PDUSessionContext request) to the SMF. This optimization avoids unnecessary signaling interactions before the target MME is determined. Figure 4In the traditional process, the AMF first sends a session context request to the SMF, and then performs MME selection and relocation. The optimized process in this embodiment directly selects the MME, reducing the number of interactions with the core network (5GS) before the target network (EPS) is determined, thereby reducing signaling redundancy and improving network efficiency. In high-latency environments such as satellite communication or in scenarios with dense network interactions, reducing one signaling interaction means reducing network latency. Faster target MME selection can directly accelerate subsequent signaling processes, including EPS bearer information requests and tunnel establishment, thereby improving the overall handover speed of the UE (User Equipment) from the 5GS network to the EPS network. Delaying the sending of the session context request to the SMF until the target MME is determined avoids wasting resources on unnecessary MME entities. For example, processing the target MME too early in the SMF may lead to inefficient resource allocation, while an optimized process can ensure efficient resource utilization. In a space-ground converged network, satellite link resources are precious, and reducing unnecessary signaling interactions can alleviate the transmission burden on the satellite link, especially under high traffic or resource constraints. This optimization is particularly important for ensuring network stability and efficiency.

[0103] Therefore, by first optimizing the target MME through AMF, not only is the signaling process simplified and the interaction efficiency improved, but the network transmission speed and resource optimization capabilities are also indirectly improved, especially for special scenarios such as satellite communication, which has a significant performance improvement effect.

[0104] In steps 7-8, when the source AMF sends the relocation request and session creation request to the target MME, it does not carry the 5GS mapped EPS PGW-U entity tunnel info (PGW-U entity tunnel info). The target MME requests the SGW to allocate the SGW's tunnel info to inform the E-UTRAN in order to establish a data channel from the E-UTRAN to the SGW.

[0105] In traditional handover procedures, tunnel information acquisition and transmission are performed step-by-step, increasing the number of network signaling interactions. In the optimized procedure, the AMF (Active Message Function) does not initially carry PGW-U entity tunnel info, avoiding unnecessary information transmission, reducing the number of signaling interactions, thereby lowering network load and improving handover efficiency. Furthermore, the optimized procedure avoids handover failures due to incorrect tunnel information, improving the handover success rate. In satellite-ground integrated networks, due to the complexity of the satellite network environment, this optimization helps reduce handover failures caused by signaling issues and ensures high-quality user services. Before confirming whether the target network needs and can use this tunnel information, the allocation and transmission of PGW-U entity tunnel info are not performed, which can avoid the pre-occupation of resources and improve the utilization efficiency of network resources. This optimization is especially important in satellite network environments where resource management is more stringent.

[0106] Therefore, the optimization method for EPS PGW-U entity tunnel info without 5GS mapping improves the performance and user experience of 5GS handover to EPS in satellite-ground converged networks by reducing signaling interaction, simplifying processes, enhancing network flexibility, reducing handover failure rate, and improving resource utilization efficiency.

[0107] 9-11 (same) Figure 4 9-11, 12. The source AMF sends an Nsmf_PDUSessionContext request to the SMF, carrying the tunnel info of the SGW CN side (core network side) obtained in step 10.2 above, and requesting the PGW-C / SMF to provide the EPS connection information required by the target MME (i.e. the EPS bearer information mentioned above).

[0108] 13.1 Same Figure 4 Same as 13.1 and 13.2 Figure 4 13.2, and if user plane information has not yet been allocated in the current 5G network, then optional step 4.2 carries UPF Tunnel info (that is, in the case that the 5G core network has not established a 5G bearer for the UE, the UPF / PGW-U is instructed by SMF / PGW-C to allocate tunnel information, where the tunnel information is the tunnel information used by the user plane function in the data transmission process).

[0109] 14. Same Figure 414. Simultaneously, the SMF mapping process adds the mapped PGW-U entity tunnelinfo described in step 13.2 above. Figure 4 4.2~4.3, 15~18. Same as Figure 4 15~18, same as 19.1 Figure 4 Same as 19.1 and 19.2 Figure 4 19.2, and at the same time add the PGW-U entity Tunnel info obtained from step 14.

[0110] 20. Same Figure 4 The 20th generation also carries the PGW-U entity tunnel info obtained from 19.2, thus completing the establishment of the EPS uplink data path from SGW to PGW-U / UPF.

[0111] 21.~26 same Figure 4 21-26.

[0112] This application also provides a schematic diagram of the structure of a data interaction system, such as... Figure 6 As shown, it includes the AMF entity and the target MME entity.

[0113] The AMF entity is used to receive network handover request messages from the Next Generation Radio Access Network (NG-RAN). These messages instruct user equipment (UE) to switch from a 5G network to a 4G network. The AMF entity identifies the target MME entity, which is the MME entity in the 4G network area to which the user equipment is switching. The AMF entity sends a relocation request to the target MME entity, which notifies the target MME entity that a UE will switch from a 5G network to a 4G network and requests the target MME entity to establish a new connection for the UE in the 4G network.

[0114] The target mobility management entity (MME) receives relocation requests from the access and mobility management function (AMF) entity and sends a session creation request to the serving gateway (SGW). The session creation request does not carry tunnel information used by the user plane function during data transmission.

[0115] This application provides a schematic diagram of the structure of a data interaction device, as shown in the embodiment. Figure 7 As shown, it includes a receiving module 702, a determining module 704, and a sending module 706.

[0116] The receiving module 702 is used by the Access and Mobility Management Function (AMF) entity to receive a network handover request message from the Next Generation Radio Access Network (NG-RAN), wherein the network handover request message is used to instruct the user equipment to switch from a 5G network to a 4G network.

[0117] The determination module 704 is used by the AMF entity to determine the target mobility management MME entity, wherein the target MME entity is the MME entity in the 4G network area to which it has been switched.

[0118] The sending module 706 is used by the AMF entity to send a relocation request to the target MME entity. The relocation request is used to notify the target MME entity that a user equipment (UE) will switch from the 5G network to the 4G network, and to request the target MME entity to establish a new connection for the UE in the 4G network.

[0119] It should be noted that the modules in the above-mentioned data interaction device can be program modules (e.g., a set of program instructions to implement a certain function) or hardware modules. For the latter, they can be in the following forms, but are not limited to these: each of the above modules is in the form of a processor, or the functions of each of the above modules are implemented by a processor.

[0120] This application embodiment also provides a non-volatile storage medium, which includes a stored program, wherein the method for controlling the device where the non-volatile storage medium is located to perform the above-mentioned data interaction is provided during program execution. For example, the Access and Mobility Management Function (AMF) entity receives a network handover request message from a Next Generation Radio Access Network (NG-RAN), wherein the network handover request message is used to instruct a user equipment (UE) to hand over from a 5G network to a 4G network; the AMF entity determines a target Mobility Management Mechanism (MME) entity, wherein the target MME entity is the MME entity in the 4G network area to which the user equipment has been handed over; the AMF entity sends a relocation request to the target MME entity, wherein the relocation request is used to notify the target MME entity that a user equipment (UE) will hand over from a 5G network to a 4G network, and requests the target MME entity to establish a new connection for the UE in the 4G network.

[0121] This application also provides an electronic device, which includes a processor for running a program, wherein the above-described data interaction method is executed during program execution. For example, an Access and Mobility Management Function (AMF) entity receives a network handover request message from a Next Generation Radio Access Network (NG-RAN), wherein the network handover request message is used to instruct a User Equipment (UE) to hand over from a 5G network to a 4G network; the AMF entity determines a target Mobility Management Mechanism (MME) entity, wherein the target MME entity is the MME entity in the 4G network area to which the user equipment has been handed over; the AMF entity sends a relocation request to the target MME entity, wherein the relocation request is used to notify the target MME entity that a User Equipment (UE) will hand over from a 5G network to a 4G network, and requests the target MME entity to establish a new connection for the UE in the 4G network.

[0122] According to another aspect of the embodiments of this application, a computer program product is also provided, including a computer program, wherein the computer program, when executed by a processor, implements the above-described data interaction method. For example, the Access and Mobility Management Function (AMF) entity receives a network handover request message from a Next Generation Radio Access Network (NG-RAN), wherein the network handover request message is used to instruct a User Equipment (UE) to hand over from a 5G network to a 4G network; the AMF entity determines a target Mobility Management Mechanism (MME) entity, wherein the target MME entity is the MME entity in the 4G network area to which the user equipment has been handed over; the AMF entity sends a relocation request to the target MME entity, wherein the relocation request is used to notify the target MME entity that a User Equipment (UE) will hand over from a 5G network to a 4G network, and requests the target MME entity to establish a new connection for the UE in the 4G network.

[0123] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

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

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

[0126] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

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

[0128] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A method of data interaction, characterized by, The method comprises the following steps: An access and mobility management function (AMF) entity receives a network switching request message of a next generation radio access network (NG-RAN), wherein the network switching request message is used to indicate that a user equipment (UE) is switched from a 5G network to a 4G network; The AMF entity determines a target mobility management (MME) entity, wherein the target MME entity is an MME entity in a 4G network area to which the UE is switched; The AMF entity sends a relocation request to the target MME entity, wherein the relocation request is used to inform the target MME entity that the UE is switched from the 5G network to the 4G network, and request the target MME entity to establish a new connection for the UE in the 4G network; After the AMF entity sends the relocation request to the target MME entity, the method further comprises the following steps: The AMF entity receives a response message sent by the target MME entity, wherein the response message is a response message of the relocation request; after receiving the response message, the AMF entity sends a session context request to a session management function (SMF) entity / packet data network gateway control plane (PGW-C) entity, wherein the session context request comprises tunnel information of a serving gateway (SGW) core network side obtained from an evolved universal terrestrial radio access network (E-UTRAN) and bearer information of an evolved packet system (EPS); After the AMF entity sends the session context request to the SMF entity / PGW-C entity, the method further comprises the following steps: In a case where no 5G bearer is established for the UE in the 5G core network, tunnel information is allocated by a user plane function (UPF) entity / packet data network gateway user plane (PGW-U) entity of a packet data network gateway indicated by the SMF entity / PGW-C entity, wherein the tunnel information is tunnel information used by the user plane function in a data transmission process.

2. The method of claim 1, wherein, The SMF entity and the UPF entity are core network elements in the 5G network for which the tunnel information is allocated, and the PGW-C entity and the PGW-U entity are core network elements in the 4G network for which the tunnel information is allocated.

3. The method of claim 1, wherein, After the tunnel information is allocated, the method further comprises the following steps: the AMF entity receives a notification message sent by the target MME entity, wherein the notification message is used to inform the AMF entity that the switching from the 5G network to the 4G network is completed, and the notification message comprises tunnel information mapped from the 5G network to the 4G network.

4. The method of claim 1, wherein, The AMF entity determines the target MME entity based on network load, geographical location or quality of service parameters.

5. A method of data interaction, characterized by, The method comprises the following steps: The target mobility management entity MME entity receives a relocation request sent by an access and mobility management function AMF entity, and further comprises: the target mobility management entity MME entity sends a response message to the AMF entity, wherein the response message is a response message of the relocation request; after the AMF entity receives the response message, the AMF entity sends a session context request to a session management function SMF entity / packet data network gateway control plane PGW-C entity, and the session context request contains tunnel information of a serving gateway SGW core network side obtained from an evolved universal terrestrial radio access network E-UTRAN and bearer information of an evolved packet system EPS; after the AMF entity sends the session context request to the SMF entity / PGW-C entity, the method further comprises: in the case that no 5G bearer is established for the UE in the 5G core network, instructing a user plane function UPF entity / packet data network gateway user plane PGW-U entity of a packet data network gateway to allocate tunnel information by the SMF entity / PGW-C entity, wherein the tunnel information is tunnel information used by the user plane function in the data transmission process; The target MME entity sends a create session request to a serving gateway SGW, wherein the create session request does not carry tunnel information used by the user plane function in the data transmission process.

6. The method of claim 5, wherein, The method further comprises: The MME entity receives a network switching request message sent by an evolved universal terrestrial radio access network E-UTRAN, wherein the network switching request message is used to indicate that the user equipment switches from the 5G network to the 4G network.

7. An apparatus for data interaction, characterized by Comprise: A receiving module is configured to receive, by an access and mobility management function AMF entity, a network switching request message of a next generation radio access network NG-RAN, wherein the network switching request message is used to indicate that the user equipment switches from the 5G network to the 4G network; A determining module is configured to determine, by the AMF entity, a target mobility management MME entity, wherein the target MME entity is an MME entity in a 4G network region to which the user equipment switches; The sending module is configured to send, by the AMF entity, a relocation request to the target MME entity, wherein the relocation request is used to inform the target MME entity that a user equipment (UE) will be switched from the 5G network to the 4G network and request the target MME entity to establish a new connection for the UE in the 4G network. After the AMF entity sends the relocation request to the target MME entity, the AMF entity receives a response message sent by the target MME entity, wherein the response message is a response message of the relocation request. After receiving the response message, the AMF entity sends a session context request to a session management function (SMF) entity / packet data network gateway control plane (PGW-C) entity, wherein the session context request comprises tunnel information of a serving gateway (SGW) core network side obtained from an evolved universal terrestrial radio access network (E-UTRAN) and bearer information of an evolved packet system (EPS). After the AMF entity sends the session context request to the SMF entity / PGW-C entity, in a case where no 5G bearer is established for the UE in the 5G core network, tunnel information is allocated by a user plane function (UPF) entity / packet data network gateway user plane (PGW-U) entity indicated by the SMF entity / PGW-C entity, wherein the tunnel information is tunnel information used by the user plane function in a data transmission process.

8. A system for data interaction, characterized by The application relates to a method for switching a user equipment (UE) from a 5G network to a 4G network, and comprises the following steps: An access and mobility management function (AMF) entity and a target mobility management entity (MME) entity are provided. The AMF entity is configured to receive a network switching request message of a next-generation wireless access network (NG-RAN), wherein the network switching request message is used to indicate that a user equipment (UE) is switched from a 5G network to a 4G network, determine a target MME entity, wherein the target MME entity is an MME entity in a 4G network region to which the UE is switched, and send a relocation request to the target MME entity, wherein the relocation request is used to inform the target MME entity that the UE is switched from the 5G network to the 4G network and request the target MME entity to establish a new connection for the UE in the 4G network. After the AMF entity sends the relocation request to the target MME entity, the AMF entity is further configured to receive a response message sent by the target MME entity, wherein the response message is a response message of the relocation request. After receiving the response message, the AMF entity is further configured to send a session context request to a session management function (SMF) entity / packet data network gateway control plane (PGW-C) entity, wherein the session context request includes tunnel information of a serving gateway (SGW) core network side obtained from an evolved universal terrestrial radio access network (E-UTRAN) and bearer information of an evolved packet system (EPS). After the AMF entity sends the session context request to the SMF entity / PGW-C entity: in a case where no 5G bearer is established for the UE in the 5G core network, the SMF entity / PGW-C entity is instructed to allocate tunnel information by a user plane function (UPF) entity / packet data network gateway user plane (PGW-U) entity of a packet data network gateway, wherein the tunnel information is tunnel information used by the UPF in a data transmission process. The target mobility management entity (MME) entity is configured to receive a relocation request sent by an access and mobility management function (AMF) entity, and send a create session request to a serving gateway (SGW), wherein the create session request does not carry tunnel information used by a user plane function (UPF) in a data transmission process.

9. A non-volatile storage medium, characterized by, The non-volatile storage medium stores a program, wherein the program controls a device in which the non-volatile storage medium is located to perform the data interaction method of any one of claims 1 to 4 or the data interaction method of any one of claims 5 to 6 when the program is running.

10. An electronic device, comprising: Comprise: a memory and a processor, wherein the processor is configured to run a program stored in the memory, and the program performs the data interaction method of any one of claims 1 to 4 or the data interaction method of any one of claims 5 to 6 when the program is running.

Images