CN116546538A - Core network disaster recovery method, device, equipment and storage medium - Google Patents
Core network disaster recovery method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN116546538A CN116546538A CN202310702181.1A CN202310702181A CN116546538A CN 116546538 A CN116546538 A CN 116546538A CN 202310702181 A CN202310702181 A CN 202310702181A CN 116546538 A CN116546538 A CN 116546538A
- Authority
- CN
- China
- Prior art keywords
- network element
- target
- udm
- amf
- ausf
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/04—Arrangements for maintaining operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/06—Authentication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/60—Context-dependent security
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本申请公开了一种核心网容灾方法、装置、设备及存储介质，涉及通信技术领域，用于提高核心网的容灾效果和用户使用体验。包括：在确定核心网架构中的目标UDM网元和目标AUSF网元同时故障的情况下，触发核心网架构进入旁路状态；当终端设备在目标AMF网元下发起注册流程时，目标AMF网元无需向目标AUSF网元发起执行鉴权过程，通过本地保存的终端设备的上下文信息实现本地鉴权；当检测到主用UDM网元和备用UDM网元中的任一UDM网元恢复正常的情况下，触发核心网架构退出旁路状态，并向任一UDM网元获取签约数据，通过任一UDM网元实现业务流程。本申请应用于核心网容灾的场景中。
The application discloses a core network disaster recovery method, device, equipment and storage medium, which relate to the field of communication technology and are used to improve the core network disaster recovery effect and user experience. Including: when the target UDM network element and the target AUSF network element in the core network architecture are determined to fail at the same time, the core network architecture is triggered to enter the bypass state; when the terminal device initiates the registration process under the target AMF network element, the target AMF network element The element does not need to initiate the authentication process to the target AUSF network element, and realizes local authentication through the locally saved context information of the terminal device; In this case, the core network architecture is triggered to exit the bypass state, and the subscription data is obtained from any UDM network element, and the service process is realized through any UDM network element. This application is applied in the scenario of core network disaster recovery.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method, an apparatus, a device, and a storage medium for disaster recovery of a core network.
Background
The fifth generation mobile communication technology (5th Generation Mobile Communication Technology,5G) is a new generation broadband mobile communication technology with high rate, low latency and large connectivity features. Since 2018 the 3GPP R15 protocol standard freezes, the 5G end-to-end industry chain is becoming mature. Video requirements have penetrated the aspects of the "5G" society, from augmented Reality (Augmented Reality, AR), virtual Reality (VR), mixed Reality (MR) to ultra-high definition video, from remote control to vehicular wireless to X, V2X autopilot. The bandwidth of tens of megabits of the 4G network can not meet the requirement of high-definition video on bandwidth far, and the characteristic of 5G large bandwidth (namely enhanced mobile broadband (Enhanced Mobile Broadband, emmbb)) is perfectly matched with the current application. The requirement on time delay is basically less than 20ms in six vertical industries (namely remote control, intelligent power, intelligent manufacturing, home entertainment, ultra-high definition video and intelligent network connection automobile) corresponding to 5G, the time delay of 50ms in 4G network becomes the bottleneck of industry development, and the problem of time delay requirement can be perfectly solved by the characteristics of Ultra-high speed and Low time delay (namely Low-latency high reliability Low-Latency Communications, urLLC) of 5G network.
In the existing stage, when a primary-backup unified data management function (Unified Data Management, UDM)/authentication service function (Authentication Server Function, AUSF) in a 5G network fails at the same time, or after the primary-backup UDM/AUSF fails due to a transmission failure, user traffic is affected as follows: in terms of data traffic (internet surfing): under the condition that the original online user does not move or does not move across the AMF, the user service can run by inertia, but when the user position moves (including the cross-mode movement and the cross-AMF movement) and service switching is needed, the user service is not available, and the newly started user data service is not available; in terms of voice traffic (telephony): the user service of the original online user calling part is available, the user service of the called part is unavailable, and the user service of the newly started user calling and called is unavailable. Therefore, the current 5G core network has poor disaster recovery effect and poor user experience.
Disclosure of Invention
The application provides a method, a device, equipment and a storage medium for disaster recovery of a core network, which are used for improving disaster recovery effect and user experience of the core network.
In order to achieve the above purpose, the present application adopts the following technical scheme:
In a first aspect, a method for disaster recovery of a core network is provided, where the method includes: under the condition that the simultaneous faults of the target UDM network element and the target AUSF network element in the core network architecture are determined, triggering the core network architecture to enter a bypass state, wherein the target UDM network element comprises: the target AUSF network element comprises a main UDM network element and a standby UDM network element, wherein the target AUSF network element comprises: the bypass state is used for controlling the business process to skip the target UDM network element and the target AUSF network element; when the terminal equipment initiates a registration process under the target AMF network element, the target AMF network element does not need to initiate an authentication executing process to the target AUSF network element, local authentication is realized through the locally stored context information of the terminal equipment, the target AMF network element does not need to register to the target UDM network element, and subscription to subscription data change notification service is not needed; and triggering the core network architecture to exit the bypass state when detecting that any one of the main UDM network element and the standby UDM network element is recovered to be normal, acquiring subscription data from any one UDM network element, and realizing a service flow through any one UDM network element.
In one possible implementation, the method further includes: when determining that the link detection failure and the messages sent to the active UDM network element and the standby UDM network element fail, determining that the target UDM network element and the target AUSF network element in the core network architecture fail simultaneously, the link detection failure includes: the network storage function NRF notifies a failure and detects a link failure between the short-range wireless communications NF.
In one possible implementation manner, in a case that the terminal device does not switch the AMF network element, the target AMF network element is an initial AMF network element; or, in the case that the terminal device is switched from the initial AMF network element to the new AMF network element, the target AMF network element is the new AMF network element.
In one possible implementation, the method further includes: under the condition that the terminal equipment moves across the system, after the MME network element acquires the context information of the terminal equipment from the target AMF network element, authentication to the target UDM network element and the Home Subscriber Server (HSS) network element is not needed; after receiving the signaling including the interface information returned by the serving gateway SGW-C, the MME network element directly executes the interaction flow between the MME network element and the terminal equipment without executing the interaction flow between the MME network element and the target UDM network element and the HSS network element.
In one possible implementation, the method further includes: in the PDU conversation process, configuring the minimum signing data of the SMF network element in the target AMF network element, so that the terminal equipment completes the establishment of the PDU conversation process through the minimum signing data; after the SMF network element receives the signaling which is sent by the target AMF network element and comprises the request for creating the SM context, the SMF network element directly returns the signaling which comprises the confirmation of accepting the process of creating the PDU session to the target AMF network element without acquiring session management subscription data from the target UDM network element.
In a second aspect, a core network disaster recovery device is provided, where the core network disaster recovery device includes: a processing unit and an acquisition unit; a processing unit, configured to trigger the core network architecture to enter a bypass state when it is determined that the target UDM network element and the target AUSF network element in the core network architecture are simultaneously faulty, where the target UDM network element includes: the target AUSF network element comprises a main UDM network element and a standby UDM network element, wherein the target AUSF network element comprises: the bypass state is used for controlling the business process to skip the target UDM network element and the target AUSF network element; the processing unit is used for enabling the target AMF network element to not need to initiate an authentication process to the target AUSF network element when the terminal equipment initiates a registration process under the target AMF network element, realizing local authentication through the locally stored context information of the terminal equipment, enabling the target AMF network element to not need to register to the target UDM network element and not need to subscribe to a subscription data change notification service; the processing unit is used for triggering the core network architecture to exit the bypass state under the condition that any one of the main UDM network element and the standby UDM network element is detected to be recovered to be normal; and the acquisition unit is used for acquiring subscription data from any UDM network element and realizing a service flow through any UDM network element.
In a possible implementation manner, the processing unit is configured to determine that the target UDM network element and the target AUSF network element in the core network architecture simultaneously fail when determining that the link detection fails and when determining that the messages sent to the active UDM network element and the standby UDM network element fail, where the link detection failure includes: the network storage function NRF notifies a failure and detects a link failure between the short-range wireless communications NF.
In one possible implementation manner, in a case that the terminal device does not switch the AMF network element, the target AMF network element is an initial AMF network element; or, in the case that the terminal device is switched from the initial AMF network element to the new AMF network element, the target AMF network element is the new AMF network element.
In a possible implementation manner, the processing unit is configured to, under a situation that the terminal device moves across standards, eliminate the need to authenticate to the target UDM network element and the home subscriber server HSS network element after the MME network element obtains the context information of the terminal device from the target AMF network element; and the processing unit is used for directly executing the interaction flow between the MME network element and the terminal equipment without executing the interaction flow between the MME network element and the target UDM network element and the HSS network element after the MME network element receives the signaling comprising the interface information returned by the serving gateway SGW-C.
In a possible implementation manner, the processing unit is configured to configure minimum subscription data of the SMF network element in the target AMF network element in the PDU session flow, so that the terminal device completes establishment of the PDU session flow through the minimum subscription data; and the processing unit is used for directly returning the signaling including confirming the acceptance of the establishment PDU session flow to the target AMF network element without acquiring session management subscription data from the target UDM network element after the SMF network element receives the signaling including the request for establishing the SM context sent by the target AMF network element.
In a third aspect, an electronic device, comprising: a processor and a memory; the memory is configured to store one or more programs, where the one or more programs include computer-executable instructions, and when the electronic device is running, the processor executes the computer-executable instructions stored in the memory, to cause the electronic device to perform a core network disaster recovery method as in the first aspect.
In a fourth aspect, there is provided a computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by a computer, cause the computer to perform a core network disaster recovery method as in the first aspect.
The application provides a method, a device, equipment and a storage medium for disaster recovery of a core network, which are applied to a scene of disaster recovery of the core network. Under the condition that the target UDM network element and the target AUSF network element in the core network architecture are determined to be simultaneously failed, the core network architecture can be triggered to enter a bypass state so as to control the service flow to skip the target UDM network element and the target AUSF network element and continue to execute. Therefore, when the terminal equipment initiates a registration process under the target AMF network element, the target AMF network element does not need to initiate an authentication process to the target AUSF network element, the local authentication can be realized through the locally stored context information of the terminal equipment, the target AMF network element does not need to register to the target UDM network element, and subscription to subscription data change notification service is not needed. Finally, when any one of the main UDM network element and the standby UDM network element is detected to be recovered to be normal, the core network structure can be triggered to exit the bypass state, subscription data are acquired from any one UDM network element, and a service flow is realized through any one UDM network element. Therefore, under the condition that the target UDM network element and the target AUSF network element in the core network architecture simultaneously fail, the bypass state can be entered through the core network architecture, so that the service flow skips the target UDM network element and the target AUSF network element to continue to execute, and the disaster recovery effect and the user experience of the core network can be improved.
Drawings
FIG. 1 is a schematic diagram of the main components of a 5G-GUTI according to the embodiments of the present application;
FIG. 2 is a schematic diagram of a core network architecture according to an embodiment of the present disclosure;
fig. 3 is a schematic diagram of a UE initial registration flow provided in an embodiment of the present application;
fig. 4 is a schematic diagram of a PDU session flow (surfing) according to an embodiment of the present application;
fig. 5 is a schematic diagram of mobility management context information of a UE stored on an AMF according to an embodiment of the present application;
fig. 6 is a second schematic diagram of mobility management context information of a UE stored on an AMF according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of a disaster recovery system of a core network according to an embodiment of the present application;
fig. 8 is a schematic flow chart of a disaster recovery method of a core network according to an embodiment of the present application;
fig. 9 is a schematic flow chart of a disaster recovery method of a core network according to an embodiment of the present application;
FIG. 10 is a schematic diagram of querying information that an AMF has entered a bypass state according to an embodiment of the present application;
fig. 11 is a second schematic diagram of an initial registration procedure of a UE according to an embodiment of the present application;
fig. 12 is a flowchart of a disaster recovery method for a core network according to an embodiment of the present application;
Fig. 13 is a schematic diagram of a UE cross-mode mobile registration flow provided in an embodiment of the present application;
fig. 14 is a flow chart diagram of a disaster recovery method for a core network according to an embodiment of the present application;
fig. 15 is a second schematic diagram of a PDU session flow (surfing) according to an embodiment of the present application;
fig. 16 is a schematic diagram of exiting a bypass state and initiating deregistration for a UE according to an embodiment of the present application;
fig. 17 is a schematic structural diagram of a disaster recovery device for a core network according to an embodiment of the present application;
fig. 18 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.
In the description of the present application, "/" means "or" unless otherwise indicated, for example, a/B may mean a or B. "and/or" herein is merely an association relationship describing an association object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone. Further, "at least one", "a plurality" means two or more. The terms "first," "second," and the like do not limit the number and order of execution, and the terms "first," "second," and the like do not necessarily differ.
First, the specific terms involved in the embodiments of the present application will be described:
a terminal device (UE) is mainly a mobile phone in a conventional cellular mobile communication network, so the UE is also commonly understood as a mobile phone.
An access and mobility management function (Access and Mobility Management Function, AMF), one of the network elements of the 5G core network, and the base station are logically interconnected. The method directly manages the 5G user to access through the base station, and performs registration management, connection management, accessibility management, mobility management and other functions.
Session management functions (Session Management Function, SMF) are mainly responsible for session management, routing, user plane management, policy control, charging, etc. functions for the user.
An authentication server function (Authentication Server Function, AUSF) serves as an authentication center of the 5G core network, mainly responsible for providing authentication for the user. In actual deployment, the AUSF is typically collocated with the UDM. The Nausf interface is a service interface where AUSF is exposed to other NF (such as AMF).
The home subscriber server (Home Subscriber Server, HSS) is a server for storing subscriber subscription information in the 4G network, and is mainly responsible for managing subscriber subscription data and location information of mobile subscribers.
A unified data management function (Unified Data Management, UDM), similar to the 4G network element HSS function, the UDM is responsible for management of 5G subscriber identities, subscription data, authentication data, service element registration management of the subscriber, etc. The UDM of the current network is compatible with the function of the 4G HSS network element, so the application is applicable to 5G mobile networks and 4G mobile networks, and the 5G mobile networks are taken as an example for description.
The policy control Function (Policy Control Function, PCF) is a core Network element of the 5G policy and charging control architecture, and functions similar to PCRF in the 4G policy and charging control architecture, and can complete formulation and issuing of instructions based on various information acquired from other NFs (Network functions), and issue the instructions to other NF Network elements for execution. In the 5G network architecture, the PCF may be co-located or separate from the PCRF.
An authentication service function (Authentication Server Function, AUSF), supporting a unified authentication service function, supporting access authentication of UE, is a network entity in a 5G network, where the UDM and the AUSF physical layer are usually co-located.
5G user permanent identity (Subscription Permanent Identifier, SUPI).
Subscription hidden identifiers (Subscription Concealed Identifier, sui), including privacy preserving identifiers to hide the SUPI, are all present on the air interface, which SUPI never appears, in order to guarantee the 5G user SUPI security.
The 5G global unique temporary identifier (5G Globally Unique Temporary Identifier,5G-GUTI) is a global unique temporary UE identifier in the 5G system, and aims to provide the UE clear identifier which does not reveal the permanent identity of the UE or the user in the 5G system (5 GS) and improve the safety. It is used in access AMF and network identification, which can be used to establish the identity of the UE during signaling between the 5G network and the UE. The 5G-GUTI is allocated by the AMF, and the AMF may reallocate the 5G-GUTI to the UE under specified conditions.
The 5G-GUTI is mainly composed of two parts, as shown in FIG. 1: the first part, globally unique AMF identifier (Globally Unique AMF Identifier, GUAMI) is the 5G-GUTI assigned by which AMF, and the second part, temporary mobile subscriber identity (Temporary Mobile Subscriber Identity, 5G-TMSI), identifies the UE's unique ID within the AMF. The GUAMI consists of a mobile country number (Mobile Country Code, MCC), a mobile network number (Mobile Network Code, MNC) and an AMF Identifier (AMF Identifier). The AMF identifies the terminal by a 5G-TMSI, which is unique within the AMF. The 5G-S-TMSI is a shortened version of the 5G-GUTI for more efficient wireless signaling procedures (e.g., paging and service requests).
A mobile country number (Mobile Country Code, MCC) consists of 3 digits, uniquely identifying the country to which the mobile subscriber belongs.
Mobile network numbers (Mobile Network Code, MNC) identifying the mobile networks to which the mobile subscriber belongs, e.g. mobile network numbers of chinese communication have 01, 06, 09 and 10.
The 5G based network architecture of the 5G core network is shown in FIG. 2 and includes NEF, NRF, PCF, UDM, AF, AUSF, AMF, SMF, UE, (R) AN-DU, (R) AN-CU, UPF, DN. The role of the UDM/AUSF in the UE initial registration procedure and the PDU session procedure (surfing the Internet) comprises two parts.
The first part is as shown in fig. 3, and the function of UDM/AUSF in the initial registration procedure (5G user registration network) of UE is:
1-3, the UE sends Registration Request (registration request) message to the AMF through the RAN (radio access network, i.e. base station), and the message carries the 5G-GUTI or sui as the identifier.
4. The AMF receives the registration request message and can judge the AMF registered before the UE according to the 5G-GUTI. If the AMF changes, the new AMF sends a Namf_communication_ UEContextTransfer request message to the old AMF to obtain the user context information.
5. The old AMF replies Namf_communication_ UEContextTransfer response message carrying the user's context information.
6. If the UE does not provide SUCI and the new side AMF does not acquire user context from the old side AMF, the new side AMF initiates an Identity Request to the UE and acquires SUCI to the UE.
7. The UE returns Identity Response to the new side AMF.
8. The AMF selects one AUSF as the UE for authentication according to SUPI or SUCI.
9. An authentication procedure (optional flow) is performed.
10. Information is obtained from the old side AMF.
11. The UDM is acquired from the UE.
12. A response message is obtained.
13. Selecting UDM.
14 a-14 c, if the new AMF is an initially registered AMF or the AMF has no UE legal context, the AMF registers with the UDM and obtains subscription data. The AMF subscribes to the subscription data change notification service from the UDM, and when the subscribed subscription data periodically registers the timer to change, the AMF receives the change notification of the UDM.
If the AMF has the legal context information of the UE, the AMF also registers with the UDM, and the UDM registers the identity of the AMF currently registered by the user.
14d, if the UDM stores the association information between the UE access type and the new AMF, the UDM will inform the old AMF to delete the UE context (optional flow).
14e, the old AMF unsubscribes from UDM subscription data (optional flow).
The second part is as shown in fig. 4, after the UE is successfully registered, the PDU session procedure (internet surfing) UDM functions as follows:
1. the UE sends a NAS message to the AMF, where the message includes information such as S-nsai, DNN, PDU session ID, requested PDU Session Type (Request Type), PDU Session Establishment Request, etc.
2. The AMF selects SMF for PDU session establishment according to the information of S-NSSAI, DNN and the like, and obtains SMF selection subscription data (including DNN, slicing and the like) from the UDM to select SMF for PDU session establishment, and please refer to the SMF selection flow for detail.
3. The AMF sends nsmf_pduse_ CreateSMContext Request to the SMF requesting to create the SM context.
4. Optionally: when the session management subscription data corresponding to SUPI, DNN, S-NSSAI is not available, the SMF acquires the session management subscription data through a Nudm_SDM_get (Nudm_ Get UE Session Management Subscription Data Request) message, wherein the session management subscription data comprises a user subscription QoS attribute, a specified APN QoS attribute and the like (optional flow), and acquires notification of subscription data change through a Nudm_SDM_subscience (Nudm_ Subscribe Create Request) message.
5. The SMF returns nsmf_pduse_ CreateSMContext Response to the AMF acknowledging acceptance to create PDU session.
6. The SMF selects the PCF for the PDU session. If dynamic PCC is not deployed, SMF may employ local policy to obtain PCC rules.
7. Optionally: after the SMF selects the PCF, the SMF establishes SM policy association with the PCF.
8. The SMF selects UPF according to the information of UE position, DNN, S-NSSAI and the like, and allocates IP address for the UE according to the IP address determined when the UE signs in the UDM, or allocates the IP address for the UE according to a local address pool by UPF.
9. If the event subscribed by PCF occurs, SMF will report the corresponding information such as time zone change and position change to PCF. The SMF may also report the assigned UE IP address/prefix to the PCF through the procedure.
10. The SMF establishes a connection with the UPF, provides data monitoring for the PDU session, reporting rules, CN tunnel information, etc.
11. The SMF sends Namf_communication_N1N2MessageTransfermessage to AMF, the carried Information comprises N2 SM Information sent to (R) AN, wherein the N2 SM Information comprises QFI, qoS Profile, CN Tunnel Info and the like, the N1 SM content sent to UE comprises PDU Session Establishment Accept, allocated IPv4 Address and the like, and the (R) AN and the UE are informed that PDU session needs to be established.
12. The AMF sends PDU Session Resource Setup Request to the (R) AN, the request contains N2 SM Information, QFI, qoS Profile, CN Tunnel Info, and N1 SM Container to the UE, PDU Session Establishment Accept, assigned IPv4 Address.
13. The (R) AN initiates signaling interaction with the UE, forwards a PDU Session ID and AN N1 SM content message which are required to be sent to the UE by the SMF to the UE, requests the UE to establish a PDU Session, and the message comprises PDU Session Establishment Accept and AN Allocated IPv4 Address.
14. The (R) AN sends PDU Session Resource Setup Response to the AMF, establishes AN Tunnel information, and the response message contains AN Tunnel Info, list of Accepted/Rejected QFI, etc.
15. The AMF sends nsmf_pduse_ UpdateSMContext Request (nsmf_update_ SMContext Request) to the SMF, forwarding the N2 SM Information received from the (R) AN to the SMF.
16. The SMF sends PFCP Session Modification Request to the UPF, sending the AN tunnel information and the corresponding forwarding rules to the UPF.
17. The SMF sends nsmf_pduse_ UpdateSMContext Response (nsmf_update_ SMContext Response) to the AMF.
Further, as shown in fig. 5, after the UE is successfully registered in the 5G network, the AMF stores mobility management context information of the UE, including authentication, encryption algorithm, and the like. As shown in fig. 6, after the UE is de-registered (powered off), the AMF is configured within a certain time frame (the AMF may be configured according to the group specification, and the current network is configured for 24 hours), and the mobility management context information of the UE is still stored.
In the embodiment of the application, when the primary and the secondary UDM/AUSF in the 5G network fail simultaneously or the primary and the secondary UDM/AUSF are totally broken due to transmission failure, the network enters a Bypass state (namely, the state of Bypass UDM), various flows of the user service are skipped over the UDM/AUSF, and the service availability of the user is preferentially ensured. So that in terms of data traffic (surfing the internet): under the condition that the original online user does not move or does not move across the AMF, the user service can run by inertia, when the user position moves (including the cross-mode movement and the cross-AMF movement) and service switching is needed, the user service is still available, and the newly started user data service is available (except the user who is newly connected to the network or is shut down for more than 24 hours); in terms of voice traffic (telephony): the user service of the original online user calling part is available, the user service of the called part is also available, and the user service of the newly started user calling and called is available (except the user who is newly connected to the network or is shut down for more than 24 hours).
And when the AMF and the SMF detect that any one of the docked UDMs is recovered to be normal, the user or the session is identified to exit the bypass state, and user subscription data is acquired from the UDMs again to perform normal business process interaction.
The method and the system are beneficial to further improving the robustness and user perception of the 5G mobile network.
The core network disaster recovery method provided by the embodiment of the application can be applied to a core network disaster recovery system. Fig. 7 shows a schematic structural diagram of the disaster recovery system of the core network. As shown in fig. 7, the core network disaster recovery system 20 includes: a terminal device 21 and a core network 22, the core network 22 comprising: a main UDM network element, a standby UDM network element, an AMF network element, an SMF network element, an ATS network element, an I-CSCF network element, an S-CSCF network element, an SBC network element and the like.
The electronic device 21 is configured to interact with the core network 22 to implement a business process.
The core network 22 is configured to implement a data service flow and a voice service flow of the electronic device 21, and trigger the core network to enter a bypass state to control the service flow to skip the UDM network element and the AUSF network element and continue to execute when determining that the UDM network element and the AUSF network element in the core network are simultaneously failed, where the core network 22 may further include: a primary AUSF network element, a standby AUSF network element.
The following describes a disaster recovery method for a core network provided in an embodiment of the present application with reference to the accompanying drawings. As shown in fig. 8, a disaster recovery method for a core network provided in an embodiment of the present application includes S201 to S203:
s201, under the condition that the simultaneous faults of a target UDM network element and a target AUSF network element in the core network architecture are determined, triggering the core network architecture to enter a bypass state.
Wherein the target UDM network element comprises: the target AUSF network element comprises a main UDM network element and a standby UDM network element, wherein the target AUSF network element comprises: the bypass state is used for controlling the business process to skip the target UDM network element and the target AUSF network element.
Note that the Bypass state is the Bypass UDM state.
In one design, as shown in fig. 9, in a method for disaster recovery of a core network provided in an embodiment of the present application, the method specifically may further include step S301:
s301, when determining that the link detection fails and the messages sent to the active UDM network element and the standby UDM network element fail, determining that a target UDM network element and a target AUSF network element in the core network architecture fail at the same time.
Wherein the link detection failure includes: the network storage function NRF notifies a failure and detects a link failure between the short-range wireless communications NF.
Alternatively, as shown in fig. 10, in the process of testing the network, it is necessary to manually construct a UDM/AUSF external connection fault, and then query whether both the AMF and the SMF have entered a bypass state.
S202, when the terminal equipment initiates a registration process under the target AMF network element, the target AMF network element does not need to initiate an authentication process to the target AUSF network element, and local authentication is realized through locally stored context information of the terminal equipment.
The target AMF network element does not need to register with the target UDM network element and does not need to subscribe to the subscription data change notification service.
Optionally, in the process of UE registration, there are multiple scenarios, where the first scenario is that the UE re-registers after registering (powering off) from the same AMF, in this case, if the UE is powered off for not more than 24 hours, the AMF implements local authentication according to the UE context information stored before the UE is powered off.
Optionally, the second scenario is that the UE moves from the old AMF (i.e. the initial AMF) to the new AMF, initiates a registration procedure (moving across AMFs) under the new AMF, and in conjunction with the illustration in fig. 3, the new AMF initiates a UE context request procedure to the old AMF, the old AMF sends the stored UE context information to the new AMF, and the new AMF implements local authentication according to the UE context information acquired from the old AMF.
Optionally, if the context information of the UE is still stored in the AMF, when the UE starts up to initiate the registration procedure, if the AMF determines that the UDM/AUSF is not available, the interaction procedure between the AMF and the UDM/AUSF is omitted, as shown in fig. 11, and in the registration procedure of the UE, there is no need to execute the procedure between the AMF and the AUSF in the fifth step, and there is no need to execute the procedure between the AMF and the UDM in steps 7a, 7b, and 7 c.
Optionally, in the case that the terminal device does not switch the AMF network element, the target AMF network element is an initial AMF network element;
or, in the case that the terminal device is switched from the initial AMF network element to the new AMF network element, the target AMF network element is the new AMF network element.
And S203, triggering the core network architecture to exit the bypass state and acquiring subscription data from any UDM network element when detecting that any UDM network element in the main UDM network element and the standby UDM network element is recovered to be normal, and realizing a service flow through any UDM network element.
In the embodiment of the application, the integrity verification is carried out by using the security context locally stored in the AMF and the SMF, so that the local authentication is realized; processing a business flow by using locally stored subscription data or locally configured minimum subscription data; the registration data and the subscription data change are not subscribed to the UDM any more, and the registration data and the subscription data change are re-subscribed after the UDM is recovered to be normal, or the UE is de-registered when the UE is in an IDLE state (IDLE state), so that the UE re-initiates registration. When AMF and SMF detect that any one of the docked UDMs is recovered to be normal, the user or session is identified to exit the bypass state, and user subscription data is acquired from the UDMs again to perform normal business process interaction.
In one design, as shown in fig. 12, a method for disaster recovery of a core network provided in the embodiment of the present application may specifically further include S401 to S402:
s401, under the condition that the terminal equipment moves across the system, after the MME network element acquires the context information of the terminal equipment from the target AMF network element, authentication to the target UDM network element and the home subscriber server HSS network element is not needed.
S402, after receiving signaling including interface information returned by the serving gateway SGW-C, the MME network element directly executes the interaction flow between the MME network element and the terminal equipment without executing the interaction flow between the MME network element and the target UDM network element and the HSS network element.
Optionally, in the process of UE registration, the third scenario is UE cross-mode movement (5G movement to 4G or 4G movement to 5G), as shown in fig. 13, taking 5G movement to 4G as an example, specifically including the following procedures:
1. the UE moves from the 5GS coverage area to the EPS coverage area, triggering the TAU procedure.
2. The UE sends TAU Request message, EPS mobile identity IE carries 4G-GUTI mapped by 5G-GUTI, and the access layer signaling also comprises GUMMEI mapped by 5G-GUTI. The TAU Request message uses the security context of 5G for integrity protection. The message also carries a UE status cell, and provides relevant information of the current UE registration state interacted with the EPS to the network, wherein the relevant information is taken as UE is in 5GMM-REGISTERED state.
3. The MME uses EPS mobile identity IE information in the message to judge that the GUTI does not belong to the MME for self allocation, and then performs opposite-end AMF inquiry through DNS according to the MME FQDN (mapped GUMMEI).
4. The MME sends a Context Request message to the opposite terminal AMF to acquire the user Context.
5a-5C, AMF sends Nsmf_PDUSation_ Retrieve SMContext Request to SMF+PGW-C requesting SM context. The smf+pgw-C sends N4 Session modification to the upf+pgw-U, establishes a CN tunnel for each EPS bearer, and provides the EPS bearer context to the AMF.
6. The AMF returns a Context Response message to the MME, carrying the mapped MM Context (including the mapped security Context), SM EPS UE Context (default bearer and proprietary GBR bearer).
7. The MME decides whether to perform an authentication process according to a local policy and the like, and the process is consistent with the authentication process in the TAU flow in 4G.
8. The MME sends Context Acknowledge a message to the AMF, which contains Cause and SGW Change Indication.
9. And the MME preferably selects SGW-C built together with one of the PGW-C according to the PGW-CNode Name information of each PDN Connection in the Context Response message, and sends Create Session Request message to the selected SGW-C. The SGW-C selects a UPF as SGW-U for each PDN Connection based on TAI, DNN, etc., and sends PFCP Session Establishment Request message to the UPF. In the message, establishing an Uplink and Downlink PDR for each EPS beer in the PDN Connection, and allocating different SGW-U S-U interfaces F-TEID for Uplink data forwarding and F-TEID of SGW-U S5/S8-U interfaces for Downlink data forwarding.
10. SGW-C sends Modify Bearer Request message to PGW-C informing S5/S8-C interface F-TEID of SGW-C and F-TEID of SGW-U S/S8-U interface. And the SMF+PGW-C reports events such as RAT change, UE position change and the like to the PCF+PCRF according to Policy Control Request Trigger issued before the PCF+PCRF. And the PCF+PCRF issues the updated strategy. The updated policy is executed in Step 19 if it is required to trigger EPS Bearer operations such as Bearer activation, modification, deletion, etc.
11. The PGW-C informs the serving UPF+PGW-U to switch the Downlink data tunnel to the SGW-U.
12. The PGW-C returns Modify Bearer Response message to the SGW-C, and the message mainly contains the Charging ID information of each EPS beer.
13. The SGW-C returns Create Session Reponse message to the MME, which contains SGW-U S-U interface F-TEID information for each EPS beer.
14. The MME sends Update Location Reqeust a message to the udm+hss, in which the dual registration identity is set to 0 or not carried.
15. The udm+hss calls nudm_uecm_ DeregistrationNotification service operation, where DeregiotionReason of DeregiotionData is "5GS_TO_EPS_mobility".
16. The udm+hss returns a Update Location Ack message to the MME.
17. The MME sends a TAU Accept message to the UE, and if the Active Flag in the TAU Request message is set, the TAU Accept message is carried in a Initial Context Setup Request message of the S1AP-MME interface and sent to the eNodeB. The Initial Context Setup Request message contains E-RAB information to be established.
18. If the 4G-GUTI is newly allocated, the UE returns a TAU Complete message to the MME.
19. Optionally: the pcf+pcrf may initiate proprietary bearer setup/modification/deletion procedures due to RAT changes, by initiating these procedures the relevant modifications are synchronized to the UE.
Optionally, in steps 4-6 in fig. 13, after the MME acquires the UE context information from the AMF, the process of authenticating the MME to the udm+hss in step 7 and the interaction procedure between the MME, the AMF and the udm+hss in steps 14-16 may be omitted.
Optionally, in the test network, a trace message screenshot needs to be implemented to determine that the UE carries 5G-GUTI registration, and sends Registration Request (registration request) message to the AMF, the AMF and the SMF do not interact with the UDM/AUSF, and after the UE is successfully registered, the UE service interacts normally.
In one design, as shown in fig. 14, in a method for disaster recovery of a core network provided in an embodiment of the present application, steps S501 to S502 may specifically further include:
S501, in the PDU conversation process, configuring the minimum signing data of the SMF network element in the target AMF network element, so that the terminal equipment completes the establishment of the PDU conversation process through the minimum signing data.
Optionally, data configuration may be performed in the AMF, and the minimum subscription data after Bypass UDM is added. After the UDM fails completely, the AMF cannot acquire SMF selection subscription data (smfSelData) from the UDM side to establish a PDU session, and therefore the SMF selection subscription data in the Bypass UDM state must be configured on the AMF side.
Optionally, the SMF selects a subscription data format: slice 1 name: DNN1 name |dnn2 name|.
Optionally, the SMF side is configured, and the user signed QoS attribute and the QoS attribute of the appointed APN after the Bypass UDM is added. After the UDM fails completely, the SMF can not acquire PDU session subscription information from the AMF or the UDM, and the UE can complete PDU session establishment by using the local general subscription data. The SMF configured user subscription QoS attribute comprises the information of priority levels of standard 5QI, downstream Session AMBR, upstream Session AMBR and ARP.
S502, after the SMF network element receives the signaling which is sent by the target AMF network element and comprises the SM context request creation, the SMF network element directly returns the signaling which comprises the PDU session confirmation creation process to the target AMF network element without acquiring session management subscription data from the target UDM network element.
Alternatively, when the SMF determines that neither the primary UDM nor the backup UDM is available, referring to fig. 4, as shown in fig. 15, the SMF and UDM interaction flow in step 4 is omitted.
Optionally, after any one of the primary UDM and the standby UDM is restored to normal, as shown in fig. 16, the following command is executed in the AMF to manually exit the bypass state, and the UE is forced to initiate a deregistration flow (to acquire user subscription data from the UDM again to perform normal business flow interaction), the user re-registers, and the AMF interacts with the UDM/AUSF normally, and the registration is successful.
In the embodiment of the application, when all UDMs/AUSF (universal data management/automatic user control) in butt joint with the AMF and the SMF totally fail, the AMF and the SMF perform integrity check by using a locally stored security context to realize local authentication, or finish mobility management and session management processes by using locally stored subscription data or locally configured minimum subscription data, so that the inertial availability of user data service (surfing) is ensured to the greatest extent, the robustness of a network is improved, and user perception is ensured; when AMF and SMF detect that any one of the docked UDMs is recovered to be normal, the user or session is identified to exit the bypass state, and user subscription data is acquired from the UDMs again to perform normal business process interaction.
The application provides a core network disaster recovery method, which can trigger a core network to enter a bypass state under the condition that a target UDM network element and a target AUSF network element in a core network architecture are determined to be simultaneously failed, so as to control a business process to skip the target UDM network element and the target AUSF network element to continue to execute. Therefore, when the terminal equipment initiates a registration process under the target AMF network element, the target AMF network element does not need to initiate an authentication process to the target AUSF network element, the local authentication can be realized through the locally stored context information of the terminal equipment, the target AMF network element does not need to register to the target UDM network element, and subscription to subscription data change notification service is not needed. Finally, when any one of the main UDM network element and the standby UDM network element is detected to be recovered to be normal, the core network structure can be triggered to exit the bypass state, subscription data are acquired from any one UDM network element, and a service flow is realized through any one UDM network element. Therefore, under the condition that the target UDM network element and the target AUSF network element in the core network architecture simultaneously fail, the bypass state can be entered through the core network architecture, so that the service flow skips the target UDM network element and the target AUSF network element to continue to execute, and the disaster recovery effect and the user experience of the core network can be improved.
The foregoing description of the solution provided in the embodiments of the present application has been mainly presented in terms of a method. To achieve the above functions, it includes corresponding hardware structures and/or software modules that perform the respective functions. Those of skill in the art will readily appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
According to the embodiment of the application, the functional modules of the disaster recovery device of the core network can be divided according to the method example, for example, each functional module can be divided corresponding to each function, and two or more functions can be integrated in one processing module. The integrated modules may be implemented in hardware or in software functional modules. Optionally, the division of the modules in the embodiments of the present application is schematic, which is merely a logic function division, and other division manners may be actually implemented.
Fig. 17 is a schematic structural diagram of a core network disaster recovery device provided in an embodiment of the present application, where, as shown in fig. 17, a core network disaster recovery device 100 is configured to improve a disaster recovery effect and a user experience of a core network, for example, to execute a core network disaster recovery method shown in fig. 8. The core network disaster recovery device 100 includes: a processing unit 1001 and an acquisition unit 1002;
a processing unit 1001, configured to trigger, when it is determined that a target UDM network element and a target AUSF network element in a core network architecture are simultaneously failed, the core network architecture to enter a bypass state, where the target UDM network element includes: the target AUSF network element comprises a main UDM network element and a standby UDM network element, wherein the target AUSF network element comprises: the bypass state is used for controlling the business process to skip the target UDM network element and the target AUSF network element;
a processing unit 1001, configured to, when a terminal device initiates a registration procedure under a target AMF network element, perform local authentication by using locally stored context information of the terminal device without initiating an authentication procedure to the target AUSF network element, register the target AMF network element with the target UDM network element, and subscribe to a subscription data change notification service;
a processing unit 1001, configured to trigger the core network architecture to exit the bypass state when detecting that any one of the primary UDM network element and the standby UDM network element is restored to normal;
The obtaining unit 1002 is configured to obtain subscription data from any UDM network element, and implement a service flow through any UDM network element.
In a possible implementation manner, in a core network disaster recovery device 100 provided in the embodiment of the present application, a processing unit 1001 is configured to determine, when determining that a link detection failure fails and a message sent to a primary UDM network element and a backup UDM network element fails, that a target UDM network element and a target AUSF network element in a core network architecture fail simultaneously, where the link detection failure includes: the network storage function NRF notifies a failure and detects a link failure between the short-range wireless communications NF.
In one possible implementation manner, in a case that the terminal device does not switch the AMF network element, the target AMF network element is an initial AMF network element; or, in the case that the terminal device is switched from the initial AMF network element to the new AMF network element, the target AMF network element is the new AMF network element.
In a possible implementation manner, in a core network disaster recovery device 100 provided in the embodiment of the present application, a processing unit 1001 is configured to, in a case that a terminal device moves across standards, eliminate the need to authenticate to a target UDM network element and a home subscriber server HSS network element after an MME network element obtains context information of the terminal device from the target AMF network element; and the processing unit 1001 is configured to directly execute an interaction flow between the MME network element and the terminal device without executing an interaction flow between the MME network element and the target UDM network element and the HSS network element after the MME network element receives the signaling including the interface information returned by the serving gateway SGW-C.
In a possible implementation manner, in a core network disaster recovery device 100 provided in the embodiment of the present application, a processing unit 1001 is configured to configure, in a PDU session flow, minimum subscription data of an SMF network element in a target AMF network element, so that a terminal device completes establishment of the PDU session flow through the minimum subscription data;
the processing unit 1001 is configured to, after the SMF network element receives the signaling sent by the target AMF network element and including the request to create the SM context, directly return, to the target AMF network element, the signaling including the confirmation of accepting to create the PDU session flow without acquiring session management subscription data from the target UDM network element.
In the case of implementing the functions of the integrated modules in the form of hardware, another possible structural schematic diagram of the electronic device involved in the foregoing embodiment is provided in the embodiments of the present application. As shown in fig. 18, an electronic device 90 is configured to improve a disaster recovery effect and a user experience of a core network, for example, to perform a disaster recovery method of the core network shown in fig. 8. The electronic device 90 comprises a processor 901, a memory 902 and a bus 903. The processor 901 and the memory 902 may be connected by a bus 903.
The processor 901 is a control center of the communication device, and may be one processor or a collective term of a plurality of processing elements. For example, the processor 901 may be a general-purpose central processing unit (central processing unit, CPU), or may be another general-purpose processor. Wherein the general purpose processor may be a microprocessor or any conventional processor or the like.
As one example, processor 901 may include one or more CPUs, such as CPU 0 and CPU 1 shown in fig. 18.
The memory 902 may be, but is not limited to, read-only memory (ROM) or other type of static storage device that can store static information and instructions, random access memory (random access memory, RAM) or other type of dynamic storage device that can store information and instructions, as well as electrically erasable programmable read-only memory (EEPROM), magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.
As a possible implementation, the memory 902 may exist separately from the processor 901, and the memory 902 may be connected to the processor 901 by a bus 903 for storing instructions or program code. When the processor 901 invokes and executes the instructions or the program codes stored in the memory 902, the method for disaster recovery of the core network provided in the embodiment of the present application can be implemented.
In another possible implementation, the memory 902 may also be integrated with the processor 901.
Bus 903 may be an industry standard architecture (Industry Standard Architecture, ISA) bus, a peripheral component interconnect (Peripheral Component Interconnect, PCI) bus, or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, among others. The bus may be classified as an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in fig. 18, but not only one bus or one type of bus.
It should be noted that the structure shown in fig. 18 does not constitute a limitation of the electronic apparatus 90. The electronic device 90 may include more or fewer components than shown in fig. 18, or may combine certain components or a different arrangement of components.
As an example, in connection with fig. 17, the processing unit 1001 and the acquisition unit 1002 in the core network disaster recovery device 100 realize the same functions as those of the processor 901 in fig. 18.
Optionally, as shown in fig. 18, the electronic device 90 provided in the embodiment of the present application may further include a communication interface 904.
A communication interface 904 for connecting with other devices via a communication network. The communication network may be an ethernet, a radio access network, a wireless local area network (wireless local area networks, WLAN), etc. The communication interface 904 may include a receiving unit for receiving data and a transmitting unit for transmitting data.
In one design, the electronic device provided in the embodiments of the present application may further include a communication interface integrated into the processor.
From the above description of embodiments, it will be apparent to those skilled in the art that the foregoing functional unit divisions are merely illustrative for convenience and brevity of description. In practical applications, the above-mentioned function allocation may be performed by different functional units, i.e. the internal structure of the device is divided into different functional units, as needed, to perform all or part of the functions described above. The specific working processes of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, which are not described herein.
The embodiment of the application further provides a computer readable storage medium, in which instructions are stored, and when the computer executes the instructions, the computer executes each step in the method flow shown in the method embodiment.
Embodiments of the present application provide a computer program product comprising instructions which, when executed on a computer, cause the computer to perform a core network disaster recovery method of the above method embodiments.
The computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium would include the following: electrical connections having one or more wires, portable computer diskette, hard disk. Random access Memory (Random Access Memory, RAM), read-Only Memory (ROM), erasable programmable Read-Only Memory (Erasable Programmable Read Only Memory, EPROM), registers, hard disk, optical fiber, portable compact disc Read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any other form of computer-readable storage medium suitable for use by a person or persons of skill in the art.
An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an application specific integrated circuit (Application Specific Integrated Circuit, ASIC).
In the context of the present application, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
Since the electronic device, the computer readable storage medium, and the computer program product in the embodiments of the present application may be applied to the above-mentioned method, the technical effects that can be obtained by the electronic device, the computer readable storage medium, and the computer program product may also refer to the above-mentioned method embodiments, and the embodiments of the present application are not repeated herein.
The foregoing is merely a specific embodiment of the present application, but the protection scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered in the protection scope of the present application.
Claims (12)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310702181.1A CN116546538A (en) | 2023-06-13 | 2023-06-13 | Core network disaster recovery method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310702181.1A CN116546538A (en) | 2023-06-13 | 2023-06-13 | Core network disaster recovery method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116546538A true CN116546538A (en) | 2023-08-04 |
Family
ID=87445460
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310702181.1A Pending CN116546538A (en) | 2023-06-13 | 2023-06-13 | Core network disaster recovery method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116546538A (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090279425A1 (en) * | 2006-12-29 | 2009-11-12 | Huawei Technologies Co., Ltd. | Method, system, and network element for service processing after data of network element is invalid or network element fails |
| WO2020038236A1 (en) * | 2018-08-23 | 2020-02-27 | 华为技术有限公司 | Routing method, apparatus and system |
| WO2022172858A1 (en) * | 2021-02-10 | 2022-08-18 | Nec Corporation | Method of core network apparatus, method of radio access network, core network apparatus and radio access network |
| CN115696409A (en) * | 2022-10-12 | 2023-02-03 | 中国电信股份有限公司 | Core network data disaster tolerance method and device and electronic equipment |
| CN115776717A (en) * | 2021-09-07 | 2023-03-10 | 中国移动通信集团设计院有限公司 | Terminal pre-registration method, device and equipment |
| WO2023050948A1 (en) * | 2021-09-30 | 2023-04-06 | 中兴通讯股份有限公司 | Disaster tolerance method, apparatus and system, and readable storage medium |
| CN116133018A (en) * | 2022-12-29 | 2023-05-16 | 中国电信股份有限公司 | User state control method and device, readable storage medium and electronic equipment |
-
2023
- 2023-06-13 CN CN202310702181.1A patent/CN116546538A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090279425A1 (en) * | 2006-12-29 | 2009-11-12 | Huawei Technologies Co., Ltd. | Method, system, and network element for service processing after data of network element is invalid or network element fails |
| WO2020038236A1 (en) * | 2018-08-23 | 2020-02-27 | 华为技术有限公司 | Routing method, apparatus and system |
| WO2022172858A1 (en) * | 2021-02-10 | 2022-08-18 | Nec Corporation | Method of core network apparatus, method of radio access network, core network apparatus and radio access network |
| CN115776717A (en) * | 2021-09-07 | 2023-03-10 | 中国移动通信集团设计院有限公司 | Terminal pre-registration method, device and equipment |
| WO2023050948A1 (en) * | 2021-09-30 | 2023-04-06 | 中兴通讯股份有限公司 | Disaster tolerance method, apparatus and system, and readable storage medium |
| CN115696409A (en) * | 2022-10-12 | 2023-02-03 | 中国电信股份有限公司 | Core network data disaster tolerance method and device and electronic equipment |
| CN116133018A (en) * | 2022-12-29 | 2023-05-16 | 中国电信股份有限公司 | User state control method and device, readable storage medium and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110167082B (en) | Network switching method, device and system, and switching determination method and device | |
| JP7240689B2 (en) | Control plane based configuration for time sensitive networking | |
| KR102365459B1 (en) | Communication method and communication device in centralized unit-decentralized unit architecture | |
| CN108632915B (en) | Method, device and equipment for moving terminal between 4G network and 5G network | |
| CN109548093B (en) | Network switching method, device and system | |
| US9532331B2 (en) | System and method for reducing paging in UTRAN/GERAN/E-UTRAN networks when idle signaling reduction is active | |
| CN113098822B (en) | A method and device for restoring IMS services | |
| EP4171089B1 (en) | Communication method and apparatus | |
| WO2018059401A1 (en) | Network switching method, device and system, and network access method and device | |
| EP3297333A1 (en) | Access method and corresponding access node, terminal and communication network | |
| US20210168585A1 (en) | Indication information sending method, apparatus and system, and storage medium | |
| CN103841545A (en) | Capability information reporting method and device in MME pool scene | |
| CN112788682A (en) | Communication method and device thereof | |
| EP2487937A1 (en) | Method, device and communication system for group call | |
| US20220225459A1 (en) | Communication network component and method for handling a service request | |
| CN106304160B (en) | Bearer creation and base station switching processing method and device | |
| CN102378208A (en) | Processing method for VLR fault and system thereof | |
| CN114339948B (en) | Communication method and communication device | |
| CN101277470B (en) | A method and system for obtaining IP-CAN bearer | |
| CN113242585A (en) | Network switching method, device, equipment and medium | |
| CN108307401A (en) | Establish the method, apparatus and communication equipment of communication connection | |
| CN116546538A (en) | Core network disaster recovery method, device, equipment and storage medium | |
| CN112118606B (en) | Method, related device and system for realizing service continuity | |
| US8983456B2 (en) | Method and system for implementing single radio voice call continuity | |
| CN112449317A (en) | Charging information reporting method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |