Request response method, apparatus, and storage medium

Abstract

The application provides a request response method and device and a storage medium, relates to the technical field of communication, and is used for improving the problem that the invalidation of a subscription network easily leads to the failure of network service. The method is applied to a first network element and includes the following steps: receiving a session request message used for requesting to establish a session for a UE; the session request message comprises session establishment information corresponding to the session; and the session request message is responded to based on the session establishment information and historical session information of the UE in a historical session process.

Description

Technical Field

[0001] This application belongs to the field of communication technology, and in particular relates to a request-response method, apparatus and storage medium. Background Technology

[0002] Currently, the registration and session establishment processes of user equipment (UE) in 5G networks generally rely on the authentication server function (AUSF) and unified data management (UDM) functions on the contracted network side. As core functions of 5G networks, AUSF and UDM are typically deployed in a primary / backup configuration to enhance network disaster recovery capabilities.

[0003] However, in abnormal situations such as bearer network failure, power failure, equipment failure, or disaster recovery failure, the AUSF and UDM functions on the contracted network side may fail, causing network elements in the 5G core network to be unable to respond to service requests, resulting in network services being unable to be implemented. Summary of the Invention

[0004] This application provides a request-response method, apparatus, and storage medium to improve the problem that network service failures can easily lead to network service unavailability due to contract network failures.

[0005] To achieve the above objectives, this application adopts the following technical solution:

[0006] In a first aspect, a request-response method is provided, applied to a first network element, comprising: receiving a session request message for requesting to establish a session for a UE; the session request message including session establishment information corresponding to the session; and responding to the session request message based on the session establishment information and historical session information of the UE in historical session processes.

[0007] Optionally, when the first network element is an access and mobility management function (AMF) network element, before receiving the session request message for requesting to establish a session for the UE, the request response method further includes:

[0008] Receive a registration request message sent by the UE; the registration request message includes temporary identification information; the temporary identification information is used to identify the historical AMF network element that provides network services to the UE; the historical AMF network element stores the historical usage information corresponding to the UE; the historical usage information includes security context information and historical session information;

[0009] When the user data management network element is in working condition, the UE is registered on the user data management network element, and the secure uplink message information of the UE during the registration process is stored.

[0010] When the user data management network element is in a failed state and matches the temporary identifier information, it reads the security context information corresponding to the UE and responds to the registration request message based on the security context information;

[0011] When the user data management network element is in a failed state and does not match the temporary identification information, historical usage information is obtained from the historical AMF network element based on the temporary identification information, and the registration request message is responded to based on the security context information in the historical usage information.

[0012] Optionally, the session establishment information includes the data network name and network area information; the historical session information includes the first subscription information used for service area management; and the method for responding to the session request message based on the session establishment information and the UE's historical session information during historical sessions specifically includes:

[0013] Retrieve historical session information;

[0014] The session management function (SMF) network element that matches the data network name, network area information, and first subscription information is identified as the target SMF network element.

[0015] Send a session request message to the target SMF network element to establish a session for the UE.

[0016] Optionally, the session establishment information includes UE identification information and data network name; the historical session information includes the correspondence between at least one historical session and at least one SMF network element; the method for responding to the session request message based on the session establishment information and the UE's historical session information during the historical session process specifically includes:

[0017] Retrieve historical session information;

[0018] The SMF network element that corresponds to the target historical session is identified as the target SMF network element; the target historical session is used to represent the historical session that corresponds to the UE identification information and the data network name.

[0019] Send a session request message to the target SMF network element to establish a session for the UE.

[0020] Optionally, after sending a session request message to the target SMF network element to establish a session for the UE, the request response method further includes:

[0021] Update the mapping between sessions and target SMF network elements in the historical usage information;

[0022] Send updated historical usage information to other AMF network elements belonging to the same pool group.

[0023] Optionally, the session establishment information includes the data network name and network area information; when the first network element is an SMF network element, the historical session information includes second subscription information used for session management; the method for responding to the session request message based on the session establishment information and the UE's historical session information during the historical session process specifically includes:

[0024] Retrieve historical session information;

[0025] User plane function (UPF) network elements that match the data network name, network area information, and second contract information are identified as target UPF network elements.

[0026] Send the configuration information corresponding to the session to both the UE and the target UPF network element.

[0027] Optionally, the session establishment information includes UE identification information and data network name; when the first network element is an SMF network element, the historical session information includes the correspondence between at least one historical session and at least one UPF network element; the method for responding to a request to establish a session based on the session establishment information and historical session information includes:

[0028] Retrieve historical session information;

[0029] The UPF network element that corresponds to the target historical session is identified as the target UPF network element; the target historical session is used to represent the historical session that corresponds to the UE identification information and the data network name;

[0030] Send the configuration information corresponding to the session to both the UE and the target UPF network element.

[0031] Optionally, after sending the session-related configuration information to the UE and the target UPF network element respectively, the method further includes:

[0032] Update the mapping between sessions and target UPF network elements in the historical session information;

[0033] Send updated historical session information to other UPF network elements belonging to the same pool group.

[0034] Optionally, the session establishment information includes temporary identification information, data network name, network area information, and UE identification information; the temporary identification information is used to identify the historical AMF network element that provides network services to the UE; the historical AMF network element stores the historical session information corresponding to the UE; the historical session information includes the correspondence between at least one historical session and at least one SMF network element; when the first network element is a mobility management entity (MME), the method for responding to the request to establish a session based on the session establishment information and the historical session information includes:

[0035] Historical session information is obtained from historical AMF network elements based on temporary identification information;

[0036] Based on the data network name, UE identification information and historical session information, the target SMF network element is determined, and the first configuration information corresponding to the session is sent to the UE and the target SMF network element respectively.

[0037] The serving gateway (SGW) corresponding to the network area information is determined, and the second configuration information corresponding to the session is sent to the UE and the SGW respectively.

[0038] Secondly, a request-response device is provided, applied to a first network element, comprising: a receiving unit and a response unit;

[0039] The receiving unit is used to receive a session request message that requests the establishment of a session for the UE; the session request message includes session establishment information corresponding to the session;

[0040] The response unit is used to respond to the session request message based on the session establishment information and the UE's historical session information during the historical session process.

[0041] Optionally, when the first network element is an AMF network element, the receiving unit is further configured to receive a registration request message sent by the UE; the registration request message includes temporary identification information; the temporary identification information is used to identify the historical AMF network element that provides network services to the UE; the historical AMF network element stores the historical usage information corresponding to the UE; the historical usage information includes security context information and historical session information;

[0042] The response unit is also used to register the UE on the user data management network element when the user data management network element is in working state, and to store the UE's secure uplink message information during the registration process;

[0043] The response unit is also used to read the security context information corresponding to the UE when the user data management network element is in a failed state and matches the temporary identification information, and to respond to the registration request message based on the security context information;

[0044] The response unit is also used to obtain historical usage information from historical AMF network elements based on temporary identification information when the user data management network element is in a failed state and does not match the temporary identification information, and to respond to the registration request message based on the security context information in the historical usage information.

[0045] Optionally, the session establishment information includes the data network name and network area information; the historical session information includes the first subscription information used for service area management; and the response unit is specifically used for:

[0046] Retrieve historical session information;

[0047] SMF network elements that match the data network name, network area information, and first contract information are identified as target SMF network elements;

[0048] Send a session request message to the target SMF network element to establish a session for the UE.

[0049] Optionally, the session establishment information includes UE identification information and data network name; the historical session information includes the correspondence between at least one historical session and at least one SMF network element; the response unit is specifically used for:

[0050] Retrieve historical session information;

[0051] The SMF network element that corresponds to the target historical session is identified as the target SMF network element; the target historical session is used to represent the historical session that corresponds to the UE identification information and the data network name.

[0052] Send a session request message to the target SMF network element to establish a session for the UE.

[0053] Optionally, the request response apparatus further includes: an update unit and a send unit;

[0054] The update unit is used to update the correspondence between sessions and target SMF network elements in the historical usage information;

[0055] The sending unit is used to send updated historical usage information to other AMF network elements belonging to the same pool group.

[0056] Optionally, the session establishment information includes the data network name and network area information; when the first network element is an SMF network element, the historical session information includes second subscription information used for session management; the response unit is specifically used for:

[0057] Retrieve historical session information;

[0058] UPF network elements that match the data network name, network area information, and second contract information are identified as target UPF network elements;

[0059] Send the configuration information corresponding to the session to both the UE and the target UPF network element.

[0060] Optionally, the session establishment information includes UE identification information and data network name; when the first network element is an SMF network element, the historical session information includes the correspondence between at least one historical session and at least one UPF network element; the response unit is specifically used for:

[0061] Retrieve historical session information;

[0062] The UPF network element that corresponds to the target historical session is identified as the target UPF network element; the target historical session is used to represent the historical session that corresponds to the UE identification information and the data network name;

[0063] Send the configuration information corresponding to the session to both the UE and the target UPF network element.

[0064] Optionally, the update unit is also used to update the correspondence between the session and the target UPF network element in the historical session information;

[0065] The sending unit is also used to send updated historical session information to other UPF network elements belonging to the same pool group.

[0066] Optionally, the session establishment information includes temporary identification information, data network name, network area information, and UE identification information; the temporary identification information is used to identify the historical AMF network element that provides network services to the UE; the historical AMF network element stores the historical session information corresponding to the UE; the historical session information includes the correspondence between at least one historical session and at least one SMF network element; when the first network element is an MME, the response unit is specifically used for:

[0067] Historical session information is obtained from historical AMF network elements based on temporary identification information;

[0068] Based on the data network name, UE identification information and historical session information, the target SMF network element is determined, and the first configuration information corresponding to the session is sent to the UE and the target SMF network element respectively.

[0069] The SGW corresponding to the network area information is determined, and the second configuration information corresponding to the session is sent to the UE and the SGW respectively.

[0070] Thirdly, a request response apparatus is provided, including a memory and a processor; the memory is used to store computer execution instructions, and the processor is connected to the memory via a bus; when the request response apparatus is running, the processor executes the computer execution instructions stored in the memory to cause the request response apparatus to perform a request response method as described in the first aspect and any of its optional methods.

[0071] The request-response device may be a network device or a part of a network device, such as a chip system within the network device. The chip system supports the network device in implementing the functions involved in the first aspect and any of its optional implementations, such as receiving, determining, and routing the data and / or information involved in the aforementioned request-response method. The chip system includes a chip and may also include other discrete devices or circuit structures.

[0072] Fourthly, a computer-readable storage medium is provided, including computer-executable instructions that, when executed on a computer, cause the computer to perform a request-response method as described in the first aspect and any of its optional methods.

[0073] It should be noted that the aforementioned computer instructions may be stored, in whole or in part, on the first computer-readable storage medium. The first computer-readable storage medium may be packaged together with the processor of the request-response device, or it may be packaged separately from the processor of the request-response device; this application does not impose any limitations on this.

[0074] In this application, the names of the aforementioned request response devices do not limit the devices or functional modules themselves. In actual implementation, these devices or functional modules may appear under other names. As long as the functions of each device or functional module are similar to those in this application, they fall within the scope of the claims of this application and their equivalents.

[0075] These or other aspects of this application will become more readily apparent in the following description.

[0076] The technical solution provided in this application brings at least the following beneficial effects:

[0077] Based on any of the above aspects, in this application, the first network element can receive a session request message for requesting to establish a session for the UE, and respond to the session request message based on session establishment information and the UE's historical session information during historical sessions. Therefore, this application can directly respond to the session request message using the UE's historical session information during historical sessions when the AUSF and UDM functions on the subscribed network side fail, thereby realizing the network service of establishing a session and avoiding the problem of being unable to respond to service requests due to subscribed network failure. Therefore, this application can be used to improve the problem that subscribed network failure easily leads to the inability to realize network services. Attached Figure Description

[0078] Figure 1 A schematic diagram of a network architecture provided in an embodiment of this application;

[0079] Figure 2 A schematic diagram of yet another network architecture provided in an embodiment of this application;

[0080] Figure 3 A schematic diagram of a request-response system provided in an embodiment of this application;

[0081] Figure 4 A schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application;

[0082] Figure 5 A flowchart illustrating a request-response method provided in an embodiment of this application;

[0083] Figure 6 A flowchart illustrating yet another request-response method provided in an embodiment of this application;

[0084] Figure 7 A flowchart illustrating yet another request-response method provided in an embodiment of this application;

[0085] Figure 8 A flowchart illustrating yet another request-response method provided in an embodiment of this application;

[0086] Figure 9 A flowchart illustrating yet another request-response method provided in an embodiment of this application;

[0087] Figure 10 A flowchart illustrating yet another request-response method provided in an embodiment of this application;

[0088] Figure 11 This is a schematic diagram of a request response device provided in an embodiment of this application. Detailed Implementation

[0089] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0090] It should be noted that in the embodiments of this application, the words "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the words "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0091] To facilitate a clear description of the technical solutions of the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish the same or similar items with essentially the same function and effect. Those skilled in the art can understand that the terms "first" and "second" are not intended to limit the quantity or execution order.

[0092] Furthermore, the terms "comprising" and "having" in the embodiments, claims, and drawings of this application are not exclusive. For example, a process, method, system, product, or device that includes a series of steps or modules is not limited to the listed steps or modules, but may also include steps or modules not listed.

[0093] To facilitate understanding of this application, the relevant elements involved in this application are described below.

[0094] Currently, 5G, with its superior characteristics of high bandwidth, low latency, wide connectivity, and high security, has been integrated into multiple industries such as manufacturing, healthcare, education, and transportation, playing an enabling role. In 5G networks, data transmission depends on data pathways.

[0095] like Figure 1 The diagram illustrates an architecture for establishing a data path in a 5G network. The UE can initiate a registration request to the AMF network element. Registration is the process by which the UE requests authorization from the subscribed network to use services. After registration, the UE can enjoy the services provided by the network.

[0096] AMF network elements can obtain authentication and subscription information from network elements jointly deployed with AUSF and UDM functions to complete two-way authentication between the UE and the network, and perform encryption and integrity protection procedures. After successful authentication, the AMF network element can perform operations such as UE registration on network elements with UDM functions, retrieving subscription information, and subscribing to data change notifications. After successful registration, the AMF network element can assign a globally unique temporary identifier (5G-GUTI) to the UE.

[0097] The UE can send a session establishment request to the AMF network element carrying information such as the 5G-GUTI and data network name (DNN) to establish a data path to the data network corresponding to the DNN. The AMF network element can select the SMF network element based on the single network slice selection assistance information (S-NSSAI), DNN information, and tracking area code (TAC) information, and forward the session establishment request.

[0098] Upon receiving a session establishment request forwarded by an AMF network element, the SMF can perform operations such as registering the session with the network element deploying UDM functionality, retrieving subscription information, and subscribing to data change notifications. Furthermore, the SMF network element can select a UPF network element based on S-NSSAI, DNN information, and TAC information, and notify the selected UPF network element and the radio side to establish a data path from the UE to the UPF network element. Specifically, the DNN can be used to identify external DNs, and the UPF network element can serve as a user plane data anchor point, transmitting user data streams to different external DNs based on the DNN. In other words, within the UPF network element, different DNNs are bound to different external data exits such as virtual local area networks (VLANs), virtual private networks (VPNs), and leased lines, thereby enabling data streams from different DNNs to enter different data exits and reach different data networks.

[0099] Based on this, the UE can successfully register in the 5G network and smoothly transmit data based on the established data path.

[0100] Combination Figure 1 ,like Figure 2 As shown, network elements jointly deployed with AUSF and UDM functions serve as user databases in 5G networks. They are essential core devices in 5G networks, carrying out important functions such as providing user and service data storage and management, registration and authentication. They are usually deployed in a primary and backup manner to enhance network disaster recovery capabilities.

[0101] However, in abnormal situations such as network failure, power failure, equipment failure, or disaster recovery failure, both the AUSF and UDM functions deployed on the contracted network side may be in a faulty state. In this case, users on the network can continue to operate according to the current 5G service process. However, in scenarios such as cross-AMF network element movement, cross-network standard switching, and new user startup, network elements located in the 5G core network may be unable to respond to service requests, resulting in service interruption and severely impacting user service experience.

[0102] To address the aforementioned issues, this application provides a request-response method. In this method, a first network element can receive a session request message requesting the establishment of a session for a UE, and respond to the session request message based on session establishment information and the UE's historical session information during historical sessions. Therefore, this application can directly respond to the session request message using the UE's historical session information when the AUSF and UDM functions on the subscribed network side fail, thereby enabling network services for establishing sessions and avoiding the problem of being unable to respond to service requests due to subscribed network failure. Thus, this application can improve the problem that subscribed network failure easily leads to the inability to realize network services.

[0103] This request-response method is applicable to request-response systems. Figure 3 One structure of the request-response system 100 is shown. For example... Figure 3 As shown, the request-response system 100 may include a session request device 101 and a first network element 102. The session request device 101 and the first network element 102 may establish a communication connection through a wired network or a wireless network.

[0104] It should be noted that, Figure 3 The session requesting device 101 can be a UE or an AMF network element. When the session requesting device 101 is a UE, the first network element 102 can be an AMF network element. When the session requesting device 101 is a UE, the first network element 102 can also be an MME. When the session requesting device 101 is an AMF network element, the first network element 102 can be an SMF network element. Figure 3 This is an example of one device configuration of the session request device 101 and the first network element 102 provided in the embodiments of this application, and does not constitute a limitation on the specific device configuration of the session request device 101 and the first network element 102.

[0105] In one possible approach, when the first network element 102 is an AMF network element or an MME, the first network element 102 can communicate with one or more session requesting devices 101 (i.e., multiple UEs). For ease of understanding, this application uses the communication connection between the first network element 102 and one session requesting device 101 as an example for illustration.

[0106] In one possible approach, when the session request device 101 is an AMF network element, the session request device 101 can communicate with one or more first network elements 102 (i.e., multiple SMF network elements). For ease of understanding, this application uses the communication connection between the session request device 101 and a first network element 102 as an example for illustration.

[0107] Optionally, when the session requesting device 101 is a UE, the UE can be a device providing voice and / or data connectivity to a user, a handheld device with wireless connectivity, or other processing devices connected to a wireless modem. The UE can communicate with one or more core networks via a radio access network (RAN). The UE can be a mobile terminal, such as a computer with a mobile terminal, or a portable, pocket-sized, handheld, or computer-embedded mobile device that exchanges voice and / or data with the radio access network. Examples include mobile phones, tablets, laptops, netbooks, and personal digital assistants (PDAs).

[0108] Optionally, when the session request device 101 or the first network element is an AMF network element, the AMF network element may have access and mobility management functions, which can be used to provide UE with registration services, mobility management services and service process monitoring services, etc.

[0109] Optionally, when the first network element is an MME, the MME can be used to provide access control, mobility management, attach and detach, session management, and selection of SGW and packet data network gateway (PGW).

[0110] Optionally, when the first network element is an SMF network element, the SMF network element may have session management functions to provide tunnel maintenance services, Internet Protocol (IP) address allocation and management services, policy enforcement services, and QoS control, billing data collection and roaming services.

[0111] This SMF network element can also have packet data network gateway control plane (PGWC) functionality, and can operate simultaneously on both 4G and 5G networks.

[0112] Optionally, when session request device 101 is an AMF network element and the first network element 102 is an SMF network element, Figure 3 The session request device 101 and the first network element 102 can be independently configured devices or functional modules integrated within the same device. This application embodiment does not impose such limitations.

[0113] It is easy to understand that when the session request device 101 and the first network element 102 are functional modules integrated within the same device, the communication method between the session request device 101 and the first network element 102 is the communication between modules within the device. In this case, the communication process between the two is the same as that between the session request device 101 and the first network element 102 when they are set up independently.

[0114] For ease of understanding, this application mainly uses the example of the session request device 101 and the first network element 102 being configured independently of each other.

[0115] Optionally, when session request device 101 is an AMF network element and first network element 102 is an SMF network element, session request device 101 and first network element 102 can be servers. The server can be a single server, or it can be a server cluster consisting of multiple servers. In some embodiments, the server cluster can also be a distributed cluster.

[0116] like Figure 4 The diagram shown is a hardware structure schematic of an electronic device provided in an embodiment of this application. The electronic device can be a session request device 101 or a first network element 102. The electronic device may include a processor 21, a memory 22, a communication interface 23, and a bus 24. The processor 21, memory 22, and communication interface 23 can be connected via the bus 24.

[0117] Processor 21 is the control center of the electronic device. It can be a single processor or a collective term for multiple processing elements. For example, processor 21 can be a CPU or other general-purpose processors. Among them, general-purpose processors can be microprocessors or any conventional processors.

[0118] As one embodiment, processor 21 may include one or more CPUs, for example Figure 4 CPU0 and CPU1 are shown in the diagram.

[0119] The memory 22 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto.

[0120] In one possible implementation, the memory 22 can exist independently of the processor 21. The memory 22 can be connected to the processor 21 via a bus 24 and is used to store instructions or program code. When the processor 21 calls and executes the instructions or program code stored in the memory 22, it can implement the request-response method provided in the following embodiments of this application.

[0121] In another possible implementation, the memory 22 can also be integrated with the processor 21.

[0122] Communication interface 23 is used for connecting electronic devices to other devices via a communication network, which may be Ethernet, wireless access network, wireless local area network (WLAN), etc. Communication interface 23 may include a receiving unit for receiving data and a transmitting unit for sending data.

[0123] Bus 24 can be an industry standard architecture (ISA) bus, a peripheral component interconnect (PCI) bus, or an extended industry standard architecture (EISA) bus, etc. This bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 4 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0124] It should be pointed out that, Figure 4 The structures shown do not constitute a limitation on electronic devices, except... Figure 4 In addition to the components shown, electronic devices may include more or fewer components than illustrated, or combine certain components, or have different component arrangements.

[0125] Combination Figure 3 When the session requesting device 101 is a UE and the first network element 102 is an AMF network element, such as Figure 5 The diagram shown is a flowchart illustrating a request-response method provided in an embodiment of this application. This request-response method can be applied to... Figure 3 The first network element 102 in the request-response system 100 shown is, i.e. Figure 5 The AMF network element in the request. The response methods for this request include: S501-S502.

[0126] S501, the AMF network element receives a session request message used to request the establishment of a session for the UE.

[0127] The session request message may include session establishment information corresponding to the session.

[0128] In one possible approach, the session requested to be established for the UE could be a protocol data unit (PDU) session.

[0129] In one possible approach, the session establishment information may include UE identification information, the data network name corresponding to the session, and the network area information where the UE is located.

[0130] UE identification information can be either the International Mobile Subscriber Identity (IMSI) or the Mobile Subscriber International ISDN Number (MSISDN).

[0131] The data network name can be used to identify the data network corresponding to the session requested by the UE. After the session is established, a data path can be established between the UE and the data network to meet the UE's service requirements.

[0132] Network area information can include TAC information and cell identifier codes, etc.

[0133] In one possible approach, the UE can send a session request message to the AMF network element when it needs to transmit data with the data network. Correspondingly, the AMF network element can receive the session request message from the UE.

[0134] The S502 and AMF network elements respond to session request messages based on session establishment information and the UE's historical session information during historical sessions.

[0135] It should be noted that AMF network elements can record historical usage information corresponding to the UE identification information during the process of providing network services such as registration and session establishment services to the UE. Historical usage information may include security context information and historical session information. Historical session information may include subscription information obtained by the AMF network element from network elements deploying UDM functionality during the process of providing network services such as registration and session establishment services to the UE.

[0136] In one possible approach, after receiving a session request message requesting the establishment of a session for the UE, the AMF network element can read stored historical session information to further respond to the session request message based on the session establishment information and the UE's historical session information during the historical session process. Specifically, the AMF network element can determine the target SMF network element for providing session establishment services based on the session establishment information and the UE's historical session information during the historical session process, and instruct the target SMF network element to establish the session corresponding to the session request message.

[0137] In one embodiment, before S501 above, that is, before the AMF network element receives the session request message for requesting to establish a session for the UE, the request response method provided in this application embodiment further includes: S601-S604.

[0138] S601, the AMF network element receives the registration request message sent by the UE.

[0139] The registration request message may include temporary identification information. This temporary identification information can be used to identify historical AMF (Application Function Provider) network elements that provided network services to the UE. These historical AMF network elements may store historical usage information corresponding to the UE. Historical usage information may include security context information and historical session information.

[0140] In one possible approach, the temporary identification information can be 5G-GUTI. 5G-GUTI can consist of a globally unique AMF identifier (GUAMI) of the historical AMF network element and the UE's 5G-temporary mobile subscriber identity (5G-TMSI).

[0141] It should be noted that for UEs that have undergone the registration process in the 5G network, these UEs can store the temporary identifier information assigned to them by the AMF network element when the registration is completed.

[0142] In scenarios involving UE reboot (also known as power-on) and UE movement across AMF network elements, the UE needs to re-register to establish a session. In this case, the UE can send a registration request message carrying its stored temporary identifier information to the AMF network element. Correspondingly, the AMF network element can receive the registration request message sent by the UE. UE movement across AMF network elements refers to the UE moving from the service area of ​​the AMF network element that assigned it temporary identifier information (i.e., the historical AMF network element) to the service area of ​​another AMF network element.

[0143] S602, AMF network element: When the user data management network element is in working state, it registers the UE on the user data management network element and stores the UE's secure uplink message information during the registration process.

[0144] In one possible approach, within a 5G network, the user data management network element can be deployed on the contracted network side, and can be a network element with UDM functionality. The user data management network element can also be equipped with AUSF.

[0145] In one possible approach, the AMF network element can monitor the operational status of user data management network elements that do not belong to the contracted network side through mechanisms such as heartbeat communication.

[0146] In one possible implementation, if the AFS and UDM functions on the contracted network side are working normally, i.e., the user data management network element is in a working state, then after the AMF network element receives the registration request message from the UE, it can proceed as follows: Figure 1 The registration process shown completes the UE's registration.

[0147] The AMF network element can store the security context information corresponding to the encryption and integrity protection process during the UE registration process, as well as the first subscription information obtained from the UDM network element for service area management, as historical usage information (also known as disaster recovery backup information) and corresponding to the UE identification information. This historical usage information can be used when the user data management network element is in a failed state, but not in the normal registration process and session establishment process.

[0148] In one possible approach, security context information may include data encryption algorithms and data integrity protection algorithms, etc.

[0149] When the user data management network element is in a failed state and matches the temporary identification information, the S603 and AMF network elements read the security context information corresponding to the UE and respond to the registration request message based on the security context information.

[0150] In one possible approach, the AMF network element can be configured with a disaster recovery bypass function. Under the disaster recovery bypass function, the AMF network element can avoid executing the UE registration process on the UDM network element, the process of obtaining the first subscription information from the UDM network element, and the subscription change process for the UE's first subscription information on the UDM network element.

[0151] If the AUSF and UDM functions on the contracted network side fail, meaning the user data management network element is in a disabled state, the AMF network element, upon receiving the UE's registration request message, can activate the disaster recovery bypass function and parse the registration request message to obtain temporary identification information. The AMF network element can then determine whether it matches this temporary identification information, i.e., whether this temporary identification information was generated and assigned to the UE.

[0152] If the AMF network element is determined to match the temporary identifier information, it indicates that the AMF network element was a historical AMF network element that provided network services to the UE before the User Data Management Network element became inactive, and it stores the UE's historical usage information. Therefore, when the User Data Management Network element is inactive and matches the temporary identifier information, the AMF network element can read the security context information corresponding to the UE from the stored historical usage information and respond to the registration request message based on the security context information.

[0153] Specifically, the AMF network element can parse security context information to obtain data encryption algorithms and data integrity protection algorithms, and send these algorithms to the UE. Correspondingly, the UE can receive the data encryption algorithms and data integrity protection algorithms from the AMF network element, facilitating secure data transmission. Based on this, this application can support responding to UE service requests and ensure the security of UE data transmission even when the user data management network element is in a failed state.

[0154] S604. When the user data management network element is in a failed state and does not match the temporary identification information, the AMF network element obtains historical usage information from the historical AMF network element based on the temporary identification information, and responds to the registration request message based on the security context information in the historical usage information.

[0155] In one possible approach, within a 5G network, the network repository function (NRF) element can be used to manage the registration and status detection of various functional network elements (such as AMF and SMF elements). The registration information can include function type, network address, and service list.

[0156] In one possible approach, if the AMF network element is determined to be inconsistent with the temporary identification information, it indicates that the AMF network element is not a historical AMF network element that provided network services to the UE before the user data management network element was in a failed state, and it did not store the historical usage information corresponding to the UE.

[0157] If the user data management network element is in a failed state and does not match the temporary identification information, the AMF network element can send temporary identification information to the NRF network element. Correspondingly, the NRF network element can receive the temporary identification information from the AMF network element, parse the temporary identification information to determine the identification information of the historical AMF network element, read the network address of the historical AMF network element corresponding to its identification information, and send the network address of the historical AMF network element to the AMF network element.

[0158] Correspondingly, the AMF network element can receive the network address of a historical AMF network element from the NRF network element and send an information retrieval request carrying UE identification information to that network address. In response to this information retrieval request, the historical AMF network element can read the historical usage information corresponding to the UE identification information and send this historical usage information to the AMF network element. Correspondingly, the AMF network element can receive the historical usage information corresponding to the UE identification information from the historical AMF network element and respond to the registration request message based on the security context information in the historical usage information.

[0159] In one possible approach, the AMF network element can store historical usage information corresponding to the UE identification information, and after responding to the registration request message based on the security context information in the historical usage information, send a response success message to the historical AMF network element. Correspondingly, the historical AMF network element can receive this response success message and delete the stored historical usage information corresponding to the UE identification information.

[0160] In one possible approach, the AMF network element can assign new temporary identification information to the UE and notify the UE to replace the temporary identification information previously assigned by the AMF network element with the new temporary identification information. Based on this, when the UE moves across AMF network elements again, the AMF network element in the area where the UE is located after the move can easily obtain the historical usage information corresponding to the UE based on the new temporary identification information to support the response to the UE's service requests.

[0161] In one embodiment, when the AMF network element responds to the session request message based on the session establishment information and the UE's historical session information in the historical session process in the above S502, this application embodiment provides an optional implementation method, including: S701-S703.

[0162] S701 and AMF network elements obtain historical session information.

[0163] In one possible approach, when the user data management network element is in a failed state, the AMF network element, upon receiving a session request message from the UE, can read the historical session information corresponding to the UE identification information from the stored historical usage information corresponding to the UE identification information, that is, the historical session information of the UE during the historical session process.

[0164] In one possible approach, the historical usage information corresponding to the UE identification information stored in the AMF network element can be recorded by the AMF network element when the user data management network element is in a working state, or it can be obtained by the AMF network element from historical AMF network elements after the user data management network element is in a failed state.

[0165] S702, the AMF network element will identify the SMF network element that matches the data network name, network area information and first contract information as the target SMF network element.

[0166] In one possible approach, if the historical session information includes first subscription information for service area management, the AMF network element can identify the target SMF network element from among the multiple SMF network elements belonging to the service area corresponding to the first subscription information that supports access to the data network corresponding to the data network name and supports providing network services to the network area corresponding to the network area information. That is, the SMF network element that meets the data network name, network area information and first subscription information is identified as the target SMF network element.

[0167] S703, the AMF network element sends a session request message to the target SMF network element to establish a session for the UE.

[0168] It should be noted that the historical session information corresponding to the UE identification information stored on historical AMF network elements may also include a mapping relationship between at least one historical session and at least one SMF network element. This mapping relationship may include information such as the network address and domain name of the SMF network element. The SMF network element may store secondary subscription information for session management corresponding to the historical sessions. Different historical sessions may have a mapping relationship with the same SMF network element. Each historical session may also have a mapping relationship with both UE identification information and data network name. The secondary subscription information may include parameters used to establish a session, such as session type and session and service continuity (SSC) mode.

[0169] To facilitate the session establishment process, in S604 above, when the AMF network element obtains historical usage information from the historical AMF network element based on temporary identification information, it can also obtain second subscription information corresponding to the UE identification information. Specifically, when the historical AMF network element reads the historical usage information corresponding to the UE identification information, it can also obtain second subscription information for session management from the SMF network element that has a corresponding relationship with the historical session corresponding to the UE identification information, and send the second subscription information to the AMF network element. Furthermore, when the historical AMF network element deletes the stored historical usage information corresponding to the UE identification information, it can also notify the SMF network element that has a corresponding relationship with the historical session corresponding to the UE identification information to delete the stored second subscription information, etc.

[0170] Therefore, if the AMF network element and the temporary identifier information do not match, the AMF network element can send a session request message carrying the second subscription information to the target SMF network element. Correspondingly, the target SMF network element can receive the session request message from the AMF network element, parse the message to obtain the second subscription information, and establish a session corresponding to the UE.

[0171] In one possible approach, if the AMF network element matches the temporary identification information and there is no corresponding relationship between the historical session corresponding to the UE identification information and the data network name and the target SMF network element, then the AMF network element can obtain the second subscription information from the SMF network element that corresponds to the historical session corresponding to the UE identification information and the data network name, and send a session request message carrying the second subscription information to the target SMF network element.

[0172] If the AMF network element matches the temporary identifier information, and there is a correspondence between the historical sessions corresponding to the UE identifier information and the data network name and the target SMF network element, then the AMF network element can directly send a session request message to the target SMF network element.

[0173] In one embodiment, when the AMF network element responds to the session request message based on the session establishment information and the UE's historical session information in the historical session process in the above S502, this application embodiment provides another optional implementation method, including: S801-S803.

[0174] S801 and AMF network elements obtain historical session information.

[0175] It should be understood that the implementation of S801 can be found in the specific description in S802, and will not be repeated here.

[0176] S802, the AMF network element identifies at least one SMF network element that has a corresponding relationship with the target historical session as the target SMF network element.

[0177] The target historical session can be used to represent a historical session that corresponds to the UE identification information and the data network name.

[0178] In one possible approach, where the historical session information includes a correspondence between at least one historical session and at least one SMF network element, if an AMF network element identifies a historical session that corresponds to the UE identification information and the data network name within at least one historical session—that is, identifies a target historical session—it indicates the existence of an SMF network element storing second subscription information corresponding to the target historical session. In this case, the AMF network element can identify the SMF network element among the at least one SMF network elements that corresponds to the target historical session as the target SMF network element, and provide session establishment services to the UE through the target SMF network element.

[0179] S803, the AMF network element sends a session request message to the target SMF network element to establish a session for the UE.

[0180] In one possible approach, combining Figure 5 ,like Figure 6 As shown, the AMF network element can respond to a session request message from the UE and, according to the implementation methods described in S701-S702 or S801-S802 above, determine the target SMF network element based on the session establishment information and the UE's historical session information in the historical session process, and send a session request message to the target SMF network element to establish a session for the UE, so that the target SMF network element provides session establishment services for the UE.

[0181] In one embodiment, after the AMF network element sends a session request message for establishing a session for the UE to the target SMF network element, the request response method provided in this application embodiment further includes: S901-S902.

[0182] S901 and AMF network elements update the correspondence between sessions and target SMF network elements in the historical usage information.

[0183] In one possible approach, if the session currently requested by the UE and a historical session included in the historical usage information have a correspondence with the same data network name, the AMF network element can delete the correspondence between the historical session information and the SMF network element in the historical usage information, and store the correspondence between the session currently requested by the UE and the target SMF network element in the historical usage information.

[0184] S902, the AMF network element sends updated historical usage information to other AMF network elements belonging to the same pool group.

[0185] In one possible approach, the AMF network element can send updated historical usage information to other AMF network elements belonging to the same pool group, so that when the UE moves to the service area of ​​other AMF network elements in the same pool group, it can efficiently provide service response services to the UE.

[0186] Combination Figure 3 When the session requesting device 101 is an AMF network element and the first network element 102 is an SMF network element, such as Figure 7 The diagram shown is a flowchart illustrating a request-response method provided in an embodiment of this application. This request-response method can be applied to... Figure 3 The first network element 102 in the request-response system 100 shown is, i.e. Figure 7 The SMF network element in the request. The request-response method includes: S1001-S1002.

[0187] S1001, the SMF network element receives a session request message used to request the establishment of a session for the UE.

[0188] The session request message may include session establishment information corresponding to the session.

[0189] In one possible approach, the session requested to be established for the UE could be a PDU session.

[0190] In one possible approach, the session establishment information may include UE identification information, the data network name corresponding to the session, and the network area information where the UE is located.

[0191] UE identification information can be either the International Mobile Subscriber Identity (IMSI) or the Mobile Subscriber International ISDN Number (MSISDN).

[0192] The data network name can be used to identify the data network corresponding to the session requested by the UE. After the session is established, a data path can be established between the UE and the data network to meet the UE's service requirements.

[0193] Network area information can include TAC information and cell identifier codes, etc.

[0194] In one possible approach, after receiving a session request message from the UE, the AMF network element can select an SMF network element based on the method described in S502 above, and send a session request message to the selected SMF network element (i.e., the target SMF network element). Correspondingly, the SMF network element can receive the session request message from the AMF network element.

[0195] S1002 and SMF network elements respond to session request messages based on session establishment information and the UE's historical session information during historical sessions.

[0196] In one possible approach, the SMF network element can also record historical session information corresponding to the UE identification information during the process of providing network services such as session establishment to the UE. The historical session information may include second subscription information used for session management. This second subscription information may simultaneously correspond to both the UE identification information in the session establishment information and the data network name in the session establishment information.

[0197] Alternatively, the session request message received by the SMF network element from the AMF network element may include historical session information of the UE during historical sessions. This historical session information may include second subscription information used for session management.

[0198] SMF network elements can determine the UPF network element used to provide data transmission services to the UE based on session establishment information and second subscription information included in historical session information, and send session configuration information to both the UE and the determined UPF network element to respond to session request messages. The session configuration information may include information such as session identifier and session type.

[0199] In one possible approach, the historical session information recorded by the SMF network element corresponding to the UE identification information may also include at least one historical session and at least one network element correspondence.

[0200] Upon receiving a session request message from an AMF network element, the SMF network element can read stored historical session information and further determine whether at least one historical session contains a target historical session that corresponds to the UE identification information and the data network name. If a target historical session exists, the SMF network element can send session configuration information to both the UE and the UPF network element corresponding to the target historical session in response to the session request message.

[0201] In one embodiment, when the SMF network element responds to the session request message based on the session establishment information and the UE's historical session information in the historical session process in the above S1002, this application embodiment provides an optional implementation method, including: S1101-S1103.

[0202] S1101 and SMF network elements obtain historical session information.

[0203] In one possible approach, if the SMF network element does not store historical session information corresponding to the UE, the SMF network element can parse the session request message from the AMF network element to obtain the historical session information corresponding to the UE.

[0204] In one possible approach, if the SMF network element stores historical session information corresponding to the UE, the SMF network element can read the stored historical session information corresponding to the UE after receiving a session request message from the AMF network element.

[0205] S1102, SMF network elements will identify UPF network elements that conform to the data network name, network area information, and second contract information as target UPF network elements.

[0206] In one possible approach, the SMF network element can identify the UPF network element that supports the relevant parameter configuration in the second contract information, supports access to the data network corresponding to the data network name, and supports providing network services to the network area corresponding to the network area information. In other words, the UPF network element that meets the data network name, network area information, and second contract information can be identified as the target UPF network element.

[0207] S1103, the SMF network element sends configuration information corresponding to the session to the UE and the target UPF network element respectively.

[0208] The configuration information corresponding to the session may include information such as session identifier, session type, and SCC mode.

[0209] In one embodiment, when the SMF network element responds to the session request message based on the session establishment information and the UE's historical session information in the historical session process in the above S1002, this application embodiment provides an optional implementation method, including: S1201-S1203.

[0210] S1201 and SMF network elements obtain historical session information.

[0211] S1202, the SMF network element identifies at least one UPF network element that has a corresponding relationship with the target historical session as the target UPF network element.

[0212] The target historical session can be used to represent a historical session that corresponds to the UE identification information and the data network name.

[0213] In one possible approach, where the historical session information includes a correspondence between at least one historical session and at least one UPF network element, if the SMF network element identifies a historical session that corresponds to the UE identification information and the data network name within at least one historical session—that is, identifies a target historical session—it indicates the existence of a UPF network element that supports establishing that session. In this case, the SMF network element can identify the UPF network element among the at least one UPF network elements that corresponds to the target historical session as the target UPF network element, and provide session establishment services to the UE through the target UPF network element.

[0214] S1203, the SMF network element sends configuration information corresponding to the session to the UE and the target UPF network element respectively.

[0215] In one possible approach, combining Figure 7 ,like Figure 8 As shown, the SMF network element can respond to the session request message from the AMF network element and, according to the implementation methods described in S1101-S1102 or S1201-S1202 above, determine the target UPF network element based on the session establishment information and the UE's historical session information in the historical session process, and send the configuration information corresponding to the session to the UE and the target UPF network element respectively, so as to establish a session corresponding to the UE.

[0216] In one embodiment, after the SMF network element sends configuration information corresponding to the session to the UE and the target UPF network element respectively, the request-response method provided in this application embodiment further includes: S1301-S1302.

[0217] S1301, the SMF network element updates the correspondence between the session and the target UPF network element in the historical session information.

[0218] In one possible approach, if the session currently requested by the UE and a historical session included in the historical session information have a correspondence with the same data network name, the SMF network element can delete the correspondence between the historical session information and the UPF network element in the historical session information, and store the correspondence between the session currently requested by the UE and the target UPF network element in the historical session information.

[0219] S1302, the SMF network element sends updated historical session information to other UPF network elements belonging to the same pool group.

[0220] In one possible approach, the SMF network element can send updated historical session information to other SMF network elements belonging to the same pool group, so that the AMF network element can assign the UE to other SMF network elements in the same pool group, thereby efficiently providing service response services to the UE.

[0221] Combination Figure 3 When the session requesting device 101 is a UE and the first network element 102 is an MME, such as Figure 9 The diagram shown is a flowchart illustrating a request-response method provided in an embodiment of this application. This request-response method can be applied to... Figure 3 The first network element 102 in the request-response system 100 shown is, i.e. Figure 9 The MME in the request-response method includes: S1401-S1402.

[0222] S1401, the MME receives a session request message used to request the establishment of a session for the UE.

[0223] The session request message may include session establishment information corresponding to the session.

[0224] In one possible approach, the session requested to be established for the UE could be a packet data network (PDN) session.

[0225] In one possible approach, the session establishment information may include temporary identification information, UE identification information, the data network name corresponding to the session, and the network area information where the UE is located.

[0226] Temporary identification information can be used to identify historical AMF (Application Function) network elements that provided network services to the UE. Historical AMF network elements can store historical session information corresponding to the UE. Historical session information includes a mapping between at least one historical session and at least one SMF network element. This mapping may include information such as the network address and domain name of the SMF network element. Temporary identification information can be a 5G-GUTI (Guided UTI). For UEs that have undergone registration in a 5G network, these UEs can store temporary identification information assigned to them by the AMF network element upon completion of registration.

[0227] The UE identification information can be either IMSI or MSISDN.

[0228] The data network name can be used to identify the data network corresponding to the session requested by the UE. After the session is established, a data path can be established between the UE and the data network to meet the UE's service requirements.

[0229] Network area information can include TAC information and cell identifier codes, etc.

[0230] In one possible scenario, if the user data management network element on the contracted network side is in a failed state and the UE switches from a 5G network to a 4G network, the UE can send a session request message to the MME in the 4G network. Correspondingly, the MME can receive the session request message from the UE and parse it to obtain temporary identification information, UE identification information, the data network name corresponding to the session, and the network area information where the UE is located.

[0231] S1402, the MME responds to the session request message based on the session establishment information and the UE's historical session information during the historical session process.

[0232] In one possible approach, combining Figure 9 ,like Figure 10 As shown, the MME can respond to a session request message from the UE, obtain historical session information from historical AMF network elements based on temporary identification information, determine the target SMF network element according to the data network name, UE identification information, and historical session information, and send first configuration information corresponding to the session to both the UE and the target SMF network element. Furthermore, the MME can determine the SGW corresponding to the network area information and send second configuration information corresponding to the session to both the UE and the SGW.

[0233] Specifically, when the MME retrieves historical session information from historical AMF network elements based on temporary identification information, it can send the temporary identification information from the session establishment information to the domain name server (DNS). Correspondingly, the DNS can receive this temporary identification information, parse it to determine the identification information of the historical AMF network element, read the network address of the historical AMF network element corresponding to its identification information, and send the network address of the historical AMF network element to the MME.

[0234] Accordingly, the MME can receive the network address of a historical AMF network element from the DNS and send an information retrieval request carrying UE identification information to that network address. In response to this information retrieval request, the historical AMF network element can read the historical session information corresponding to the UE identification information and send it to the MME. Consequently, the MME can receive the historical session information corresponding to the UE identification information from the historical AMF network element.

[0235] When determining the target SMF network element based on the data network name, UE identification information, and historical session information, the MME can identify the target historical session corresponding to the data network name and the UE identification information, and then determine the SMF network element corresponding to the historical session as the target SMF network element. Further, the MME can send first configuration information corresponding to the session to both the UE and the target SMF network element. This first configuration information may include information such as the IP address and access point name (APN) assigned to the UE under this session. In this case, the target SMF network element functions similarly to the PGWC, used for processing and controlling packet data communication services in the 4G network.

[0236] The MME can select the SGW corresponding to the network area information in the session establishment information and send the second configuration information corresponding to the session to both the UE and the SGW. The second configuration information may include information such as the session identifier corresponding to the session.

[0237] Based on this, this application can support the response to service requests during the process of UE switching from 5G network standard to 4G network standard when the user data management network element on the contracted network side is in a failed state, thereby realizing communication services for UE in cross-network standard scenarios.

[0238] This application enhances the disaster recovery capabilities of AMF and SMF network elements in 5G networks by caching security context, subscription data, and session information through AMF and SMF network elements, thereby achieving a disaster recovery bypass function. When the AMF and SMF functions on the subscription network side fail, it can effectively smooth out services, improve the reliability of 5G networks, optimize network resources, and enhance the network's ability to resist risks, which helps to build a secure, agile, and intelligent 5G network.

[0239] The foregoing mainly describes the solutions provided by the embodiments of this application from a methodological perspective. To achieve the above functions, it includes corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, in conjunction with the units and algorithm steps of the various examples described in the embodiments herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0240] This application embodiment can divide the first network element into functional modules according to the above method example. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. Optionally, the module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0241] like Figure 11 The diagram shown is a structural schematic of a request-response device provided in an embodiment of this application. This request-response device can be applied to a first network element and can be used to perform actions such as... Figures 5-10 The request-response method is shown. The request-response apparatus includes: applied to a first network element, comprising: a receiving unit 1501 and a response unit 1502;

[0242] Receiving unit 1501 is configured to receive a session request message for requesting the establishment of a session for the UE; the session request message includes session establishment information corresponding to the session; for example, combined with Figure 5 The receiving unit 1501 can be used to execute S501.

[0243] Response unit 1502 is used to respond to the session request message based on session establishment information and historical session information of the UE during historical sessions. For example, combined with Figure 5 The response unit 1502 can be used to execute S502.

[0244] Optionally, when the first network element is an AMF network element, the receiving unit 1501 is further configured to receive a registration request message sent by the UE; the registration request message includes temporary identification information; the temporary identification information is used to identify the historical AMF network element that provides network services to the UE; the historical AMF network element stores the historical usage information corresponding to the UE; the historical usage information includes security context information and historical session information; for example, the receiving unit 1501 can be used to execute S601.

[0245] The response unit 1502 is also used to register the UE on the user data management network element when the user data management network element is in working state, and to store the UE's secure uplink message information during the registration process; for example, the response unit 1502 can be used to execute S602.

[0246] The response unit 1502 is also used to read the security context information corresponding to the UE when the user data management network element is in a failed state and matches the temporary identification information, and respond to the registration request message based on the security context information; for example, the response unit 1502 can be used to execute S603.

[0247] The response unit 1502 is further configured to, when the user data management network element is in a failed state and does not match the temporary identification information, obtain historical usage information from the historical AMF network element based on the temporary identification information, and respond to the registration request message based on the security context information in the historical usage information. For example, the response unit 1502 can be used to execute S604.

[0248] Optionally, the session establishment information includes the data network name and network area information; the historical session information includes the first subscription information used for service area management; the response unit 1502 is specifically used for:

[0249] Obtain historical session information; for example, response unit 1502 can be used to execute S701.

[0250] The SMF network element that matches the data network name, network area information and first contract information is identified as the target SMF network element; for example, response unit 1502 can be used to execute S702.

[0251] Send a session request message to the target SMF network element to establish a session for the UE. For example, response unit 1502 can be used to execute S703.

[0252] Optionally, the session establishment information includes UE identification information and data network name; the historical session information includes the correspondence between at least one historical session and at least one SMF network element; the response unit 1502 is specifically used for:

[0253] Obtain historical session information; for example, response unit 1502 can be used to execute S801.

[0254] At least one SMF network element that corresponds to the target historical session is identified as the target SMF network element; the target historical session is used to represent the historical session that corresponds to the UE identification information and the data network name; for example, the response unit 1502 can be used to execute S802.

[0255] Send a session request message to the target SMF network element to establish a session for the UE. For example, response unit 1502 can be used to execute S803.

[0256] Optionally, the request response device further includes: an update unit 1503 and a sending unit 1504;

[0257] The update unit 1503 is used to update the correspondence between the session and the target SMF network element in the historical usage information; for example, the update unit 1503 can be used to execute S901.

[0258] The sending unit 1504 is used to send updated historical usage information to other AMF network elements belonging to the same pool group. For example, the sending unit 1504 can be used to execute S902.

[0259] Optionally, the session establishment information includes data network name and network area information; when the first network element is an SMF network element, the historical session information includes second subscription information used for session management; the response unit 1502 is specifically used for:

[0260] Obtain historical session information; for example, response unit 1502 can be used to execute S1101.

[0261] The UPF network element that matches the data network name, network area information, and second contract information is identified as the target UPF network element; for example, the response unit 1502 can be used to execute S1102.

[0262] Configuration information corresponding to the session is sent to both the UE and the target UPF network element. For example, response unit 1502 can be used to execute S1103.

[0263] Optionally, the session establishment information includes UE identification information and data network name; when the first network element is an SMF network element, the historical session information includes the correspondence between at least one historical session and at least one UPF network element; the response unit 1502 is specifically used for:

[0264] Obtain historical session information; for example, response unit 1502 can be used to execute S1201.

[0265] At least one UPF network element that corresponds to the target historical session is identified as the target UPF network element; the target historical session is used to represent the historical session that corresponds to the UE identification information and the data network name; for example, the response unit 1502 can be used to execute S1202.

[0266] Configuration information corresponding to the session is sent to both the UE and the target UPF network element. For example, response unit 1502 can be used to execute S1203.

[0267] Optionally, the update unit 1503 is also used to update the correspondence between the session and the target UPF network element in the historical session information; for example, the update unit 1503 can be used to execute S1301.

[0268] The sending unit 1504 is also used to send updated historical session information to other UPF network elements belonging to the same pool group. For example, the sending unit 1504 can be used to execute S1302.

[0269] Optionally, the session establishment information includes temporary identification information, data network name, network area information, and UE identification information; the temporary identification information is used to identify the historical AMF network element that provides network services to the UE; the historical AMF network element stores the historical session information corresponding to the UE; the historical session information includes the correspondence between at least one historical session and at least one SMF network element; when the first network element is an MME, the response unit 1502 is specifically used for:

[0270] Historical session information is obtained from historical AMF network elements based on temporary identification information;

[0271] Based on the data network name, UE identification information and historical session information, the target SMF network element is determined, and the first configuration information corresponding to the session is sent to the UE and the target SMF network element respectively.

[0272] The SGW corresponding to the network area information is determined, and the second configuration information corresponding to the session is sent to the UE and the SGW respectively.

[0273] Those skilled in the art will recognize that, in one or more of the examples above, the functions described in this application can be implemented using hardware, software, firmware, or any combination thereof. When implemented in software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer-readable storage media and communication media, wherein communication media include any medium that facilitates the transmission of a computer program from one place to another. Storage media can be any available medium accessible to a general-purpose or special-purpose computer.

[0274] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0275] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and other division methods may exist in actual implementation. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the shown or discussed mutual couplings, direct couplings, or communication connections may be through some interfaces; indirect couplings or communication connections between devices or units may be electrical, mechanical, or other forms. Units described as separate components may or may not be physically separate; components shown as units may be one physical unit or multiple physical units, i.e., they may be located in one place or distributed in multiple different places. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

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

Claims

1. A request-response method, characterized in that, Applied to the first network element, including: When the first network element is an Access and Mobility Management Function (AMF) network element, it receives a registration request message sent by a User Equipment (UE); the registration request message includes temporary identification information; the temporary identification information is used to identify the historical AMF network element that provides network services to the UE; the historical AMF network element stores the historical usage information corresponding to the UE; the historical usage information includes security context information and the historical session information; When the user data management network element is in working condition, the UE is registered on the user data management network element, and the secure uplink and downlink message information of the UE during the registration process is stored. When the user data management network element is in a failed state and matches the temporary identifier information, the security context information corresponding to the UE is read, and the registration request message is responded to based on the security context information; When the user data management network element is in a failed state and does not match the temporary identification information, the historical usage information is obtained from the historical AMF network element based on the temporary identification information, and the registration request message is responded to based on the security context information in the historical usage information; Receive a session request message for requesting the establishment of a session for the UE; the session request message includes session establishment information corresponding to the session; The UE responds to the session request message based on the session establishment information and the UE's historical session information during the historical session process.

2. The request-response method according to claim 1, characterized in that, The session establishment information includes the data network name and network area information; the historical session information includes the first subscription information used for service area management. The step of responding to the session request message based on the session establishment information and the UE's historical session information during historical sessions includes: Obtain the historical session information; The SMF network element that matches the data network name, the network area information, and the first subscription information is identified as the target SMF network element. Send a session request message to the target SMF network element to establish the session for the UE.

3. The request-response method according to claim 1, characterized in that, The session establishment information includes UE identification information and data network name; the historical session information includes the correspondence between at least one historical session and at least one SMF network element; The step of responding to the session request message based on the session establishment information and the UE's historical session information during historical sessions includes: Obtain the historical session information; The SMF network element that corresponds to the target historical session among the at least one SMF network element is determined as the target SMF network element; the target historical session is used to represent the historical session that corresponds to the UE identification information and the data network name; Send a session request message to the target SMF network element to establish the session for the UE.

4. The request-response method according to claim 2 or 3, characterized in that, After sending a session request message to the target SMF network element to establish the session for the UE, the method further includes: The correspondence between the session and the target SMF network element is updated in the historical usage information; The updated historical usage information is sent to other AMF network elements belonging to the same pool group.

5. The request-response method according to claim 1, characterized in that, The session establishment information includes the data network name and network area information; when the first network element is an SMF network element, the historical session information includes second subscription information used for session management; The step of responding to the session request message based on the session establishment information and the UE's historical session information during historical sessions includes: Obtain the historical session information; User plane function UPF network elements that match the data network name, the network area information, and the second subscription information are identified as target UPF network elements; The configuration information corresponding to the session is sent to the UE and the target UPF network element respectively.

6. The request-response method according to claim 1, characterized in that, The session establishment information includes UE identification information and data network name; when the first network element is an SMF network element, the historical session information includes the correspondence between at least one historical session and at least one UPF network element; The step of responding to the request to establish the session based on the session establishment information and the historical session information includes: Obtain the historical session information; The UPF network element that corresponds to the target historical session among the at least one UPF network element is determined as the target UPF network element; the target historical session is used to represent the historical session that corresponds to the UE identification information and the data network name; The configuration information corresponding to the session is sent to the UE and the target UPF network element respectively.

7. The request-response method according to claim 5 or 6, characterized in that, After sending the configuration information corresponding to the session to the UE and the target UPF network element respectively, the method further includes: The correspondence between the session and the target UPF network element is updated in the historical session information; The updated historical session information is sent to other UPF network elements belonging to the same pool group.

8. The request-response method according to claim 1, characterized in that, The session establishment information includes temporary identification information, data network name, network area information, and UE identification information; the temporary identification information is used to identify the historical AMF network element that provided network services to the UE; the historical AMF network element stores the historical session information corresponding to the UE; the historical session information includes the correspondence between at least one historical session and at least one SMF network element; When the first network element is a Mobility Management Entity (MME), the step of responding to the request to establish the session based on the session establishment information and the historical session information includes: The historical session information is obtained from the historical AMF network element based on the temporary identifier information; Based on the data network name, the UE identification information, and historical session information, the target SMF network element is determined, and first configuration information corresponding to the session is sent to the UE and the target SMF network element respectively. The Serving Gateway (SGW) corresponding to the network area information is determined, and the second configuration information corresponding to the session is sent to the UE and the SGW respectively.

9. A request-response device, characterized in that, Applied to the first network element, including: a receiving unit and a response unit; When the first network element is an Access and Mobility Management Function (AMF) network element, the receiving unit is configured to receive a registration request message sent by a User Equipment (UE); the registration request message includes temporary identification information; the temporary identification information is used to identify the historical AMF network element that provides network services to the UE; the historical AMF network element stores the historical usage information corresponding to the UE; the historical usage information includes security context information and the historical session information; The response unit is used to register the UE on the user data management network element when the user data management network element is in working state, and to store the secure uplink and downlink message information of the UE during the registration process; The response unit is further configured to read the security context information corresponding to the UE when the user data management network element is in a failed state and matches the temporary identifier information, and respond to the registration request message based on the security context information; The response unit is further configured to, when the user data management network element is in a failed state and does not match the temporary identification information, obtain the historical usage information from the historical AMF network element based on the temporary identification information, and respond to the registration request message based on the security context information in the historical usage information; The receiving unit is further configured to receive a session request message for requesting the establishment of a session for the UE; the session request message includes session establishment information corresponding to the session; The response unit is further configured to respond to the session request message based on the session establishment information and the UE's historical session information during the historical session process.

10. A request-response device, characterized in that, It includes a memory and a processor; the memory is used to store computer execution instructions, and the processor is connected to the memory via a bus; when the request response device is running, the processor executes the computer execution instructions stored in the memory to cause the request response device to perform the request response method as described in any one of claims 1-8.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes computer-executable instructions that, when executed on a computer, cause the computer to perform the request-response method as described in any one of claims 1-8.

Images