A communication method and apparatus

By replacing the CSCF network element with the SBC in the IMS network, self-switching or fake registration is achieved, which solves the problem of user service unavailability caused by a complete failure of CSCF, ensures successful terminal registration, and improves user experience.

CN123124083APending Publication Date: 2026-11-17HUAWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202510633878.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-05-15
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

When the IMS network fails, especially in the case of a complete CSCF failure, users' voice and data services become unavailable, resulting in a poor user experience and frequent terminal registration failures.

Method used

By replacing the CSCF network element with network devices such as SBC in the IMS network, the user registration process is terminated, enabling self-switching registration or fake registration, avoiding frequent re-registration, and ensuring successful terminal registration.

Benefits of technology

In a CSCF network element full-fault scenario, successful terminal registration is achieved, improving the availability of user voice and data services and enhancing user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123124083A_ABST
    Figure CN123124083A_ABST
Patent Text Reader

Abstract

This application provides a communication method and apparatus to address the problem of unavailable voice and data services for users in a CSCF (Call Session Control Network) scenario of complete network element failure, thereby improving user experience. The method includes: receiving a first message from a first terminal, the first message being used to request initial registration or re-registration; if it is determined that the call session control network element is completely faulty, setting the user of the first terminal as a self-registered user or a fake registered user; and sending a second message to the first terminal to indicate that the first terminal has successfully registered.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0002] With the development of mobile communication technology, Internet Protocol Multimedia Subsystem (IMS) technology has emerged, gradually replacing traditional circuit-switched (CS) voice communication technology in second-generation (2G) or third-generation (3G) networks. IMS can be carried on fourth-generation (4G) or fifth-generation (5G) communication networks to implement voice control, referred to as Voice over Long Term Evolution (VoLTE) and Voice over New Radio (VoNR) respectively. VoLTE or VoNR can provide high-definition and low-latency voice calls to user equipment (UE).

[0003] Currently, in scenarios where CS and IMS networks are deployed together, when the IMS network fails, such as the upper-layer network element's call session control function (CSCF) failing completely, circuit-switched fallback (CSFB) can be used, allowing the UE to access the 2G or 3G network and make voice calls through the CS network, thus making both voice and data services available.

[0004] However, facing the issue of CS network shutdown or withdrawal, without CS network, the terminal cannot use voice services normally in the event of IMS network failure, and the UE side fails to register with IMS network again, data services are also unavailable, resulting in a poor user experience. Summary of the Invention

[0005] This application provides a communication method and apparatus to solve the problem of unavailable voice and data services for users in the event of a complete failure of the CSCF network element, thereby improving the user experience.

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

[0007] Firstly, a communication method is provided, which can be executed by a communication device. The communication device can be a network device, a module (such as a chip, chip system, or circuit) within the network device, or a module or software capable of implementing all or part of the functions of the network device. For example, the network device can be a session border controller (SBC). The method includes: receiving a first message from a first terminal, the first message being used to request initial registration or re-registration; if it is determined that the call session control network element is completely faulty, setting the user of the first terminal as a self-registered user or a fake registered user; and sending a second message to the first terminal to indicate that the first terminal has successfully registered.

[0008] In the above implementation, network devices such as SBCs in the IMS network can replace CSCF network elements to terminate the user registration process, thereby enabling successful registration of terminal users. Specifically, it can be customized as self-switching registration or fake registration, thereby avoiding frequent re-registration triggered by terminal registration failure, solving the problem of unavailable terminal voice and data services in the case of full failure of CSCF network elements, and improving user experience.

[0009] In one implementation, if it is determined that the call session control network element is completely faulty, the method further includes: sending a third message to the first network element, wherein the third message includes information of the first terminal, and the third message is used to request to obtain the user registration information of the first terminal.

[0010] In the above implementation, under the scenario of a complete failure of the CSCF network element, by requesting the user registration information of the first terminal from other network elements, the terminal user registration process within a certain area can be realized, enabling the terminal to register successfully. This avoids the frequent triggering of re-registration due to terminal registration failure, solves the problem of unavailable terminal voice and data services under the scenario of a complete failure of the CSCF network element, and improves the user experience.

[0011] In one embodiment, the method further includes: receiving a fourth message from the first network element; if the fourth message includes user registration information of the first terminal, then setting the user as a self-registered user, and the second message including the user registration information; if the fourth message is used to indicate a failure response, then setting the user as a fake registered user and constructing fake user registration information, and the second message including the fake user registration information.

[0012] In the above embodiments, by requesting the user registration information of the first terminal from other network elements, the terminal user registration process within a certain area can be realized, enabling the terminal to register successfully. This avoids frequent re-registration triggered by terminal registration failure, solves the problem of unavailable terminal voice and data services in the scenario of full failure of CSCF network elements, and improves user experience.

[0013] In one embodiment, the method further includes: sending a probe message to at least one session boundary controller, the probe message being used to obtain the status of a call session control network element corresponding to the session boundary controller; wherein the at least one session boundary controller includes a first network element; and receiving a probe response message from the at least one session boundary controller, the probe response message being used to indicate that the call session control network element is in a fault state or a reachable state.

[0014] In the above implementation, by sending a probe message to the session boundary controller, the status of the call session control network element in a certain area can be obtained and recorded, thereby maintaining the status of the call session control network element in the area and flexibly handling services such as user registration or calls. This solves the problem of frequent terminal registration failures in the case of full failure of CSCF network element and improves user experience.

[0015] In one embodiment, the method further includes: saving the status information of the call session control network element corresponding to the at least one session boundary controller.

[0016] In one embodiment, the method further includes: receiving a call request message from a first terminal; confirming, based on the calling information in the call request message, whether the first terminal is a self-registered user or a fake registered user, and determining that all call session control network elements are faulty; obtaining user registration information of a second terminal based on the called information in the call request message, the user registration information including the access information of the second terminal; and forwarding the call request message to the second terminal based on the access information to establish a call.

[0017] In the above embodiments, by marking self-switched registered users or fake registered users, in the event of a complete CSCF failure in the IMS network, the user registration information of the called user is obtained and the call request message is forwarded to the second terminal to establish a call, thereby realizing a self-switched call process and improving communication efficiency.

[0018] In one embodiment, the method further includes: performing global format normalization on the called number in the called information of the call request message to obtain the global number of the second terminal; querying the number information of the registered user based on the global number to obtain the user registration information of the second terminal.

[0019] In one embodiment, the method further includes: receiving a call request message from a first terminal; confirming, based on the calling information in the call request message, whether the first terminal is a self-registered user or a fake registered user, and determining that the call session control network element is completely faulty; if, based on the called information in the call request message, no user registration information for a second terminal is found, sending a probe message, the probe message including information about the second terminal, the probe message being used to request the acquisition of the session boundary controller corresponding to the second terminal; receiving a probe response message, the probe response message being used to indicate that the first network element is the session boundary controller corresponding to the second terminal; and forwarding the call request message to the first network element to establish a call.

[0020] In the above embodiments, by marking self-registered users or fake registered users, in the event of a complete CSCF failure in the IMS network, the system requests information from other network elements to obtain the Session Border Controller (SBC) information corresponding to the second terminal. This allows the SBC to forward call request messages to the SBC corresponding to the second terminal, enabling the SBC to query and obtain the user registration information of the second terminal and forward the call request message, thus successfully establishing a call and improving communication efficiency. For example, if the first network element is an SBC network element, the interaction of call request messages is implemented at the SBC level, allowing calling and called users within the same operator but in different SBC management areas to successfully make calls, further improving communication efficiency.

[0021] In one implementation, the method further includes: confirming that the second terminal is a user within a first area based on the called party information in the call request message.

[0022] In one embodiment, the method further includes: receiving a call request message from a first terminal; confirming, based on the calling information in the call request message, whether the first terminal is a self-registered user or a fake registered user, and determining that the call session control network element is completely faulty; if, based on the called information in the call request message, it is confirmed that the second terminal is not a user within the first area, then sending a call failure message to the first terminal.

[0023] In one embodiment, the method further includes: receiving a call request message from a first terminal; detecting that at least one call session control network element is in a reachable state; confirming that the first terminal is a self-registered user or a fake registered user based on the calling information in the call request message; and sending a call failure response message to the first terminal, wherein the call failure response message is further used to instruct a re-registration request.

[0024] In one implementation, after the CSCF fault in the IMS network is resolved, end users can register normally with the IMS network and resume normal call services. For example, if the first network element detects that the state of the call session control network element has returned to normal, it can re-mark or set self-registered users or fake registered users as normal users to execute subsequent user registration or call processes, thereby improving the user experience.

[0025] In one embodiment, the method further includes: receiving a registration request message from the first terminal; if the state of the call session control network element is detected to be reachable; interacting with the call session control network element to complete user registration; and setting the user of the first terminal as a normal registered user.

[0026] In the above embodiments, if the CSCF status in the IMS network is detected to have returned to normal, the user registration process can improve the flexibility and efficiency of user registration in the IMS network and enhance the user experience by successfully registering the first terminal and updating the settings of the first terminal to those of a normal registered user.

[0027] In one embodiment, the method further includes: receiving a registration request message from the first terminal; if the status of the call session control network element corresponding to the first network element in the first area is detected to be reachable, sending a response message to the first terminal, the response message being used to indicate registration migration to the first network element.

[0028] In a second aspect, a communication device is provided for implementing the above-described method. This communication device may be a network device as described in the first aspect, or a node or device comprising the network device, or a module within the network device, such as a chip, chip system, or circuit, or a logic node, logic module, or software capable of performing some or all of the functions.

[0029] The communication device includes modules, units, or means that implement the methods described above. These modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.

[0030] In conjunction with the second aspect described above, in one possible implementation, the communication device may include a processing module and a transceiver module. The processing module can be used to implement the processing functions in any of the above aspects and any of their possible implementations. The processing module may be, for example, a processor. The transceiver module, also referred to as a transceiver unit, is used to implement the sending and / or receiving functions in any of the above aspects and any of their possible implementations. The transceiver module may consist of a transceiver circuit, a transceiver, a transceiver unit, or a communication interface.

[0031] In conjunction with the second aspect above, in one possible implementation, the transceiver module includes a sending module and a receiving module, which are used to implement the sending and receiving functions in any of the above aspects and any possible implementations.

[0032] Thirdly, a communication device is provided, comprising: a processor; the processor being coupled to a memory and, after reading instructions from the memory, executing the method as described in any of the preceding aspects according to the instructions. The communication device may be a network device as described in the first aspect, or a node or device comprising the network device, or a module in the network device, such as a chip, chip system, or circuit, or a logic node, logic module, or software capable of implementing some or all of the functions.

[0033] In conjunction with the third aspect described above, in one possible implementation, the communication device further includes a memory for storing necessary program instructions and data.

[0034] In conjunction with the third aspect described above, in one possible implementation, the communication device is a chip or a chip system. Optionally, when the communication device is a chip system, it can be composed of chips or may include chips and other discrete components.

[0035] Fourthly, a communication device is provided, comprising: a processor and an interface circuit; the interface circuit is configured to receive a computer program or instructions and transmit them to the processor; the processor is configured to execute the computer program or instructions to cause the communication device to perform the method described in any of the preceding aspects. The communication device may be a network device as described in the first aspect, or a node or device comprising the network device, or a module in the network device, such as a chip, chip system, or circuit, or a logic node, logic module, or software capable of implementing some or all of the functions.

[0036] In conjunction with the fourth aspect above, in one possible implementation, the communication device is a chip or a chip system. Optionally, when the communication device is a chip system, it can be composed of chips or may include chips and other discrete components.

[0037] Fifthly, a computer-readable storage medium is provided that stores instructions which, when executed on a computer, enable the computer to perform the methods described in any of the preceding aspects.

[0038] In a sixth aspect, a computer program product containing instructions is provided, which, when run on a computer, enables the computer to perform the methods described in any of the preceding aspects.

[0039] The technical effects of any of the possible implementations of aspects two through six can be found in the technical effects of the different possible implementations of aspect one above, and will not be repeated here.

[0040] Understandably, provided that the solutions do not contradict each other, the solutions in the above aspects can be combined. Attached Figure Description

[0041] Figure 1 This application provides a schematic diagram of the architecture of a communication system.

[0042] Figure 2 This is a schematic diagram of the architecture of another communication system provided in an embodiment of this application;

[0043] Figure 3 A schematic diagram of the architecture of a communication device provided in an embodiment of this application;

[0044] Figure 4 This is a schematic diagram of the architecture of another communication system provided in an embodiment of this application;

[0045] Figures 5-10 Flowchart of the communication method provided in the embodiments of this application Figures 1 to 6 ;

[0046] Figure 11 This is a schematic diagram of the architecture of a communication device provided in an embodiment of this application. Detailed Implementation

[0047] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this embodiment, unless otherwise stated, "a plurality of" means two or more.

[0048] It should be noted that, in this application, the terms "exemplary" or "for example" are used to indicate that something is being described as an example, illustration, or illustration. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design solutions. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0049] In this application, "sending information" can be understood as one device sending information to another device, or it can also be understood as one logical module within a device sending information to another logical module. For example, "access network device sending information" can be understood as the access network device sending information to another device (such as a terminal), or it can be understood as logical module 1 in the access network device sending information to logical module 2 in the access network device.

[0050] In this application, "receiving information" can be understood as one device receiving information from another device, or it can also be understood as a logical module within a device receiving information from another logical module. For example, "access network device receiving information" can be understood as the access network device receiving information from another device (such as a terminal), or it can be understood as logical module 1 in the access network device receiving information from logical module 2 in the access network device.

[0051] In this application, phrases such as "sending information to... (e.g., a terminal)" or related illustrations in the accompanying drawings can be understood as indicating that the destination of the information is a terminal. This can include sending information directly or indirectly to a terminal. Similarly, phrases such as "receiving information from... (e.g., a terminal)," "receiving information from... (e.g., a terminal)," or "receiving information sent by (e.g., a terminal)," or related illustrations in the accompanying drawings, can be understood as indicating that the source of the information is a terminal. This can include receiving information directly or indirectly from a terminal. Information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be interpreted similarly and will not be elaborated further here.

[0052] 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.

[0053] First, a brief introduction will be given to the implementation environment and application scenarios of the embodiments of this application.

[0054] The communication method provided in this application can be applied to fourth-generation (4G) communication systems, such as long-term evolution (LTE) communication systems or evolved packet system (EPS) networks, as well as fifth-generation (5G) communication systems, such as 5G new radio (NR) communication systems, or various communication systems evolving after 5G, and future communication systems. The 4G core network is called the evolved packet core (EPC), and the 5G core network is called the 5G core network (5GC).

[0055] For example, Figure 1 This application illustrates a network architecture to which this application applies, wherein, Figure 1Taking the network service architecture of a 5G system as an example, this paper illustrates the interaction relationships between network functions (NFs) and entities, as well as their corresponding interfaces. The service-based architecture (SBA) of the 3rd generation partnership project (3GPP) for 5G systems includes the following network functions and entities: user equipment (UE), at least one access network (AN) or radio access network (RAN) node, user plane function (UPF), data network (DN), access and mobility management function (AMF), session management function (SMF), policy control function (PCF), application function (AF), unified data management (UDM), network exposure function (NEF), unified data repository (UDR), authentication server function (AUSF), network storage function (NRF), and network slice selection function (NSSF), etc.

[0056] In this context, the UE, radio access network (RAN) node, UPF, and DN are generally referred to as user plane network functions and entities (or user plane network elements), while the others are generally referred to as control plane network functions and entities (or control plane network elements). Control plane network elements, defined by 3GPP, define the processing functions within a network. They possess 3GPP-defined functional behaviors and interfaces. An NF can function as a network element running on proprietary hardware, a software instance running on proprietary hardware, or a virtual function instantiated on a suitable platform, such as a cloud infrastructure.

[0057] The main functions of each network function are described in detail below.

[0058] The user plane network functions in the communication system include:

[0059] (R)AN Node: A (R)AN can be an AN, a RAN, or an access network device, RAN entity, or access node, etc., forming part of the communication system to help terminal devices access the communication network. For example, a (R)AN can be various types of base stations, such as macro base stations, micro base stations, radio controllers, relay stations, access points, or network equipment in vehicle-mounted devices, wearable devices, or future public land mobile networks (PLMNs). The (R)AN is primarily responsible for air interface-side radio resource management, quality of service management, data compression, and encryption.

[0060] In addition, (R)AN nodes can also be access nodes in open RAN (O-RAN or ORAN), cloud radio access network (CRAN), or wireless fidelity (Wi-Fi) systems, or access nodes in communication systems that integrate two or more of the above systems.

[0061] In one possible scenario, a RAN node can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB) in a future mobile communication system, or an access node in a Wi-Fi system. A RAN node can be a macro base station, a micro base station, an indoor station, a relay node, a donor node, or a radio controller in a CRAN scenario. Optionally, a RAN node can also be a server, a wearable device, a vehicle, or in-vehicle equipment. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). All or part of the functions of the RAN node in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The RAN node in this application can also be a logical node, logical module, or software capable of implementing all or part of the RAN node functions.

[0062] In another possible scenario, multiple RAN nodes collaborate to assist terminal devices in achieving wireless access, with different RAN nodes each implementing some of the base station's functions. For example, RAN nodes can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs), etc. CUs and DUs can be set up separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

[0063] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0064] UE: Also known as a terminal, terminal device, mobile station (MS), mobile terminal (MT), etc., it is a device used to provide voice or data connectivity to users, or an Internet of Things (IoT) device. For example, terminal devices include handheld devices with wireless connectivity, in-vehicle devices, etc. Currently, terminal devices can include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices (such as smartwatches, smart bracelets, pedometers, smart glasses, etc.), in-vehicle devices (such as cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.), satellite terminals, virtual reality (VR) devices, augmented reality (AR) devices, point-of-sale (POS) machines, customer-premises equipment (CPE), light user equipment (UE), reduced capability user equipment (REDCAP UE), wireless terminals in industrial control, smart home devices (such as refrigerators, televisions, air conditioners, electricity meters, etc.), intelligent robots, robotic arms, workshop equipment, wireless terminals in autonomous driving, wireless terminals in telemedicine, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, or wireless terminals in smart homes, and flying equipment (such as intelligent robots, hot air balloons, drones, airplanes), etc. Terminal devices can also be vehicle devices, such as vehicle units, vehicle modules, vehicle chips, onboard units (OBU), or telematics boxes (T-BOX). Terminal devices can also be other devices with terminal functions. For example, a terminal device can also be a device that plays a terminal function in device-to-device (D2D) communication.

[0065] The embodiments of this application do not limit the form of the terminal device. The device used to implement the functions of the terminal device can be the terminal device itself, or it can be a device that supports the terminal device in implementing the functions, such as a chip system. The device can be installed in the terminal device or used in conjunction with the terminal device. In the embodiments of this application, the chip system can be composed of chips, or it can include chips and other discrete devices. All or part of the functions of the terminal device in this application can also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (such as a cloud platform).

[0066] UPF: Primarily responsible for forwarding and receiving user plane data. The UPF can receive downlink data from the DN and then transmit that downlink data to the UE via (R)AN. The UPF can also receive uplink data from the UE via (R)AN and then forward that uplink data to the DN.

[0067] DN: For example, a DN can be an operator service network, an internet access network, or a third-party service network. A DN can exchange information with the UE through a PDU session. PDU sessions can be of various types, such as Internet Protocol version 4 (IPv4) and IPv6. For a 5GC network, the IMS network is a type of DN.

[0068] In addition, the control plane network functions in the communication system include:

[0069] AMF (Automatic Management Function): Primarily responsible for processing control plane messages and managing the mobility of terminal devices, including mobility state management, assigning temporary user identities, and authenticating and authorizing users. Examples include access control, mobility management, registration and deregistration, and network element selection.

[0070] SMF: Primarily used for session management, session establishment, allocation and management of UE's (private) IP address, responsible for session establishment, modification and release, and quality of service (QoS) control, etc.

[0071] UDM (User Authentication and Authorization Manager): Primarily used for authentication and credit processing, it manages subscription data, user identification, access authorization, registration / mobility management, subscription management, and SMS management. For example, when a user's subscription data is modified, the UDM is responsible for notifying the relevant network elements.

[0072] NEF: Primarily used to provide corresponding security guarantees to ensure the security of external applications to the communication network, providing functions such as opening up QoS customization capabilities for external applications, subscription to mobility state events, and distribution of AF requests.

[0073] NRF: Primarily used to provide internal / external addressing functions, etc.

[0074] AUSF: Primarily used for authentication processing functions, enabling two-way authentication between terminals and networks.

[0075] AF: Primarily used to send data routing information affecting applications to the network side, and to perform policy control through interaction between network open function elements and the policy framework.

[0076] PCF: Its main function is as a policy decision point, providing rules for detection, QoS, and flow-based charging control based on service data flows or applications. It can also provide policies to AMF and SMF, such as QoS policies and slice selection policies.

[0077] Furthermore, the IMS network can be carried on 4G or 5G networks to provide voice call services based on the Internet Protocol (IP).

[0078] like Figure 1 As shown, an IMS network may include at least one call session control function (CSCF) network element, which is mainly responsible for handling signaling control during multimedia call sessions. For example, it can be used to manage user authentication in the IMS network, IMS bearer plane QoS, control of session initiation protocol (SIP) sessions in cooperation with other network entities, as well as service negotiation and resource allocation.

[0079] For example, based on their different functions, CSCFs can be divided into proxy CSCFs (P-CSCF), interrogating CSCFs (I-CSCF), and perving CSCFs (S-CSCF). Essentially, they are all SIP servers used to process SIP signaling. For instance, the main functions of a P-CSCF include: forwarding SIP registration requests sent by terminals to the I-CSCF; and forwarding SIP messages sent by terminals to the S-CSCF. The P-CSCF determines the S-CSCF when the terminal initiates the registration process. Optionally, the P-CSCF can serve as a user access node in an IMS network.

[0080] in addition, Figure 2 This illustrates another network architecture to which this application applies. Figure 2Taking the network service architecture of a 4G system as an example, the network functions and entities included in a 4G system mainly include: UE, eNodeB, Mobility Management Entity (MME), Serving Gateway (SGW or S-GW), Packet Data Network Gateway (PGW or P-GW), Home Subscription Server (HSS), Policy and Charging Rule Function (PCRF), and Service Capability Exposure Function (SCEF), etc.

[0081] MME: The key control node of the LTE access network, which is responsible for the location of UEs in idle mode, the paging process, including relaying.

[0082] SGW: User plane access service gateway in EPC network, responsible for forwarding user data. For example, it can include control plane service gateway (SGW-controlplane, SGW-C) and user plane service gateway (SGW-user plane, SGW-U).

[0083] PGW (Power Gateway): Used to provide user session management and bearer control, data forwarding, IP address allocation, and access for non-3GPP users. It is the anchor point for users accessing the packet data network (PDN). For example, it can include a user plane PDN gateway (PGW-U) and a control plane PDN gateway (PGW-C).

[0084] HSS: The information processed includes: user identification, numbering and address information; user security information; user location information; user list information.

[0085] PCRF: It can control the QoS of users and services, thereby providing users with differentiated services, as well as guaranteeing service flow carrying resources and traffic billing policies, such as policy charging control (PCC) rules.

[0086] SCEF exposes the services and capabilities of 3GPP network functions to third-party applications, and also allows third-party applications to provide information to 3GPP network functions.

[0087] It should be noted that, Figure 1 or Figure 2 The functions of other network elements included can be found in the relevant descriptions in conventional technologies, and will not be repeated here. Figure 1 or Figure 2 The network architecture shown is for illustrative purposes only and is not intended to limit the technical solutions of this application. Those skilled in the art should understand that other network elements or devices may be included in the specific implementation, and the number of access network devices, terminal devices, and / or core network devices may be determined according to specific needs.

[0088] Optional, Figure 1 or Figure 2 Each network element shown can be a device, a functional module within a device, or a logical functional unit. It is understood that the aforementioned functions can be network components in hardware devices, such as communication chips in mobile phones, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (e.g., a cloud platform).

[0089] Understandably, the above Figure 1 or Figure 2 In a communication system, devices or network elements can communicate directly or through forwarding from other devices. This application does not specifically limit this.

[0090] Understandably, the above Figure 1 or Figure 2 This is merely an illustrative diagram and does not constitute a limitation on the applicable scenarios of the technical solutions provided in this application. Those skilled in the art should understand that, in specific implementation processes, the communication system may include, for example, […]. Figure 1 or Figure 2 The number of devices or network elements shown may be fewer, or the communication system may include other devices or other network elements, and the number of devices or network elements in the communication system may be determined according to specific needs.

[0091] For example, Figure 1 or Figure 2 Each network element in the network can be accessed through Figure 3 This is achieved through the communication device 300. Figure 3 The diagram shows a hardware structure of a communication device applicable to embodiments of this application. The communication device 300 includes at least one processor 301, a communication line 302, and at least one communication interface 304. Optionally, the communication device 300 may further include a memory 303.

[0092] Processor 301 can be one or more central processing units (CPUs). If the processor is a CPU, it can be a single-core CPU or a multi-core CPU. The processor can be a general-purpose processor, digital signal processor, application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, capable of implementing or executing the methods, steps, and logic block diagrams disclosed in the embodiments of this application. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or executed by a combination of hardware and software modules within the processor.

[0093] Optionally, the processor may include one or more of the following: a central processing unit (CPU), an application-specific integrated circuit (ASIC), a digital signal processor (DSP), a microprocessor unit (MPU), a microcontroller unit (MCU), a graphics processing unit (GPU), a field-programmable gate array (FPGA), an artificial intelligence processor (AI processor), or a neural processing unit (NPU).

[0094] Communication line 302 may include a path for transmitting information between the aforementioned components, such as a bus.

[0095] Communication interface 304 uses any transceiver-like device for communicating with other devices or communication networks, such as Ethernet interface, RAN interface, wireless local area network (WLAN) interface, etc.

[0096] The memory 303 may include, but is not limited to, a cache, read-only memory (ROM), random access memory (RAM), synchronous dynamic random access memory (SDRAM), hard disk drive (HDD) or solid-state drive (SSD), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM), etc. Memory is any other medium capable of carrying or storing desired program code in the form of instructions or data structures that can be accessed by a computer, but is not limited to this. The memory in this embodiment may also be a circuit or any other device capable of implementing storage functions for storing computer programs or instructions, and / or data. Optionally, the memory may exist independently and be connected to the processor via communication line 302. Optionally, the memory may also be integrated with the processor. The memory provided in this embodiment typically has non-volatile properties. The memory 303 stores computer execution instructions involved in the present application, and the processor 301 controls the execution of these instructions. The processor 301 executes the computer execution instructions stored in the memory 303 to implement the method provided in the embodiments of the present application.

[0097] Optionally, the computer execution instructions in the embodiments of this application may also be referred to as application code, and the embodiments of this application do not specifically limit this.

[0098] In a specific implementation, as one example, processor 301 may include one or more CPUs, for example... Figure 3 CPU0 and CPU1 in the CPU.

[0099] In a specific implementation, as one example, the communication device 300 may include multiple processors, such as... Figure 3 Processors 301 and 307 are described herein. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor here may refer to one or more devices, circuits, and / or processing cores used to process data (e.g., computer program instructions).

[0100] In a specific implementation, as one embodiment, the communication device 300 may further include an output device 305 and an input device 306. The output device 305 communicates with the processor 301 and can display information in various ways. For example, the output device 305 may be a liquid crystal display (LCD), a light-emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector, etc. The input device 306 communicates with the processor 301 and can receive user input in various ways. For example, the input device 306 may be a mouse, keyboard, touchscreen device, or sensing device, etc.

[0101] The aforementioned communication device 300 can be a general-purpose device or a dedicated device. In specific implementations, the communication device 300 can be a portable computer, a network server, a handheld digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, an embedded device, or something similar. Figure 3 Devices with similar structures. This application does not limit the type of communication device 300 to any particular embodiment.

[0102] The communication method provided in the embodiments of this application will be described in detail below.

[0103] It should be noted that the message names between network elements or the names of parameters in the messages in the following embodiments of this application are just examples. Other names may be used in the specific implementation. This application does not limit them in this respect.

[0104] It is understood that some or all of the steps in the embodiments of this application are merely examples, and other steps or variations thereof may also be performed in the embodiments of this application. Furthermore, the steps may be performed in different orders as presented in the embodiments of this application, and it is not necessary to perform all the steps in the embodiments of this application.

[0105] Currently, in scenarios where 2G / 3G and 4G / 5G networks converge, if the IMS network fails, such as a complete failure of the upper-layer network element CSCF, VoNR and VoLTE can fall back to CS for voice calls via CSFB, thus ensuring the availability of both voice and data services. However, with the decommissioning of 2G and 3G networks and the absence of a CS network, in the event of an IMS network failure, terminals cannot use voice services normally; furthermore, user registration failures trigger continuous registration requests on the terminal side, making data services unavailable as well.

[0106] This application proposes a communication method applicable to 4G, 5G, or future communication networks. In an IMS network where the CSCF (CStriel Functional Communication Center) element is completely faulty, a first network element replaces the CSCF element to terminate the registration process, completing user registration and some call services. This solves the problem of unavailable voice and data services on user terminals, improving user experience. For example, in the user registration scenario, successful registration can be achieved through user self-switching registration or sham registration, avoiding repeated registration requests from the terminal. For call services, successful calls can be completed for terminal users within a certain area.

[0107] For example, the first network element may be a session border controller (SBC) or other network elements, and this application does not limit this.

[0108] In one embodiment, the communication method provided in this application can be applied to, for example... Figure 4 The network architecture shown includes terminals, access nodes, a core network, and an IMS network. For example, in a 4G network, the core network may include network elements such as MME, SGW-C or PGW-C, SGW-U or PGW-U. In a 5G network, the core network may include network elements such as AMF, SMF, and UPF. The IMS network may include network elements such as CSCF and SBC. For example, one or more CSCFs in the IMS network may fail or become unreachable.

[0109] Among them, the SBC network element is a network element in the IMS network used to realize IP access, interconnection and security protection. It exists between the access network and the IMS network or between different IMS networks and can serve as the entry point for users to access the IMS network.

[0110] For example, SBCs can be deployed in a distributed manner across different locations to effectively manage and optimize network performance, enhance network security, and meet specific business needs. For instance, SBC deployment areas can be divided based on network size, service requirements, geographical location, and security requirements. For example, operators can plan SBC deployments by province or city; for instance, one or more SBCs can be deployed in a city to manage IP access or interoperability of end users within the IMS network of that city.

[0111] Example 1: Terminal Registration Process

[0112] like Figure 5 As shown, the method may include the following steps.

[0113] 501: The first terminal sends a first message to the first network element, the first message being used to request initial registration or re-registration. Correspondingly, the first network element receives the first message from the first terminal.

[0114] Before communicating with the IMS network, the terminal can trigger a registration process. Through the registration process, the terminal can obtain the necessary parameters and configurations for communicating with the IMS network. For example, the registration process can be triggered after the terminal is powered on or started; or, the registration process can be triggered after the terminal is disconnected from the network and then restored. For example, this embodiment uses the terminal as the first terminal as an example.

[0115] It should be understood that in this application, when a terminal sends a message to a first network element, it may include the terminal sending the message to the first network element through the access network, or the terminal sending the message to the first network element through network elements of the access network and the core network. That is, the sender of the message is the terminal and the destination is the first network element, which may include the terminal sending the message directly or indirectly to the first network element.

[0116] The registration process triggered by the terminal can be an initial registration or a re-registration after a registration failure. For example, the first message can be an initial registration request message or a re-registration request message. This application does not limit this.

[0117] For example, when the first terminal triggers the initial registration process, the first message sent by the first terminal to the first network element can be an initial registration request message, such as a Register message, carrying the identifier of the first terminal.

[0118] In one implementation, the first network element may be an SBC (Session Management Controller) or other management network element, such as a session management network element, used to manage the registration or access of terminal users in the IMS network. This application does not limit this; the following embodiments use an SBC as an example.

[0119] In this application, the first network element can be used to record the status of call session control function network elements in the IMS network. For example, the first network element can record the status of call session control network elements in a first area corresponding to the first network element as either normal or faulty. Optionally, the first network element can record the status of call session control network elements in other areas as either normal or faulty.

[0120] For example, the region where the SBC is deployed in the IMS network is not limited in this embodiment of the application. For example, the first region or the second region can be used as an example. Optionally, the first region can be a province, city, administrative region, county or other custom-defined area. This application does not limit this.

[0121] For example, the first network element is the first SBC. The first SBC can record and maintain the status of the CSCF network elements in the first area corresponding to the first SBC. Furthermore, the first SBC also records and maintains the status of the CSCF network elements in the second area corresponding to the second SBC, etc.

[0122] For example, the first SBC can detect and obtain the status of CSCF network elements. Optionally, the first SBC can interact with the second SBC to obtain the status of CSCF network elements in the second area corresponding to the second SBC.

[0123] The following describes a method for the first network element to obtain the status of the call session control network element. For example, in one implementation, steps 500a and / or steps 500b-500c may be performed.

[0124] 500a: The first network element sends a probe message to obtain the status of the call session control network element.

[0125] For example, the first network element is SBC1, which can send probe messages (such as OPTIONS) to probe the status of the CSCF. Optionally, the first network element can send probe messages via broadcast, multicast, or unicast.

[0126] For example, if CSCF-1 does not respond, or returns a failure response, it indicates that CSCF-1 is unreachable or faulty. SBC1 can save the fault status to the corresponding CSCF status list of SBC1, recording the status of CSCF-1 as faulty. As another example, if CSCF-2 returns a probe response, indicating that CSCF-2 is normal or reachable, SBC1 can save the normal status to the corresponding CSCF status list of SBC1, recording the status of CSCF-2 as normal / reachable.

[0127] In one implementation, an SBC list can be set on the SBC, which includes multiple SBCs. These SBCs may be located in the same area or in different areas. The SBC can record and maintain the status information of the call session control network element corresponding to each SBC in the SBC list.

[0128] 500b: The first network element sends a probe message to the second network element to obtain the status of the call session control network element corresponding to the second network element. Correspondingly, the second network element receives the probe message.

[0129] For example, the first network element is SBC1, and the second network element is SBC2. SBC1 can trigger device-level probing based on the configured SBC list. For instance, SBC1 can send probe messages (e.g., OPTIONS messages) to other SBCs in the SBC list to request the CSCF status corresponding to those SBCs. Optionally, the first network element can send probe messages via broadcast, multicast, or unicast.

[0130] 500c: The second network element sends a probe response message to the first network element. Correspondingly, the first network element receives the probe response message.

[0131] For example, the second network element receives a probe message, obtains the recorded CSCF status, and sends a probe response message to the first network element according to the CSCF status, which is used to indicate that the call session control network element corresponding to the second network element is in a fault state, or a normal / reachable state.

[0132] For example, if SBC2 records one or more local CSCF states as normal / reachable, it can send a 200 response message to the first network element to indicate an acknowledgment response, that is, to indicate that the CSCF state is normal / reachable.

[0133] For example, if SBC2 records one or more local CSCF states as faulty, it can send a rejection response message, such as an OXX message, to the first network element to indicate that the CSCF state of SBC2 is faulty. For instance, the OXX message could be a 404 message or other response message indicating failure or rejection; this application does not limit this.

[0134] After receiving the probe response message, SBC1 saves the status information to the CSCF status of SBC2 in the SBC list.

[0135] Therefore, after receiving the registration request from the terminal, the first network element can determine the subsequent registration process of the terminal based on the recorded status of the call session control network element.

[0136] 502: If the first network element determines that the call session control network element is completely faulty, set the user of the first terminal to a self-registered user or a fake registered user.

[0137] The first network element queries the status record of the call session control network element. If all call session control network elements in the record are in a fault state, the user of the first terminal is set to a self-registered user or a fake registered user.

[0138] For example, the first network element is SBC1. In the SBC list recorded by SBC1, all CSCF states corresponding to any SBC are in a fault state. The user of the first terminal is set to a self-registered user or a fake registered user.

[0139] In this application, self-exchange registration means that the user registration information is available locally, or the SBC does not have the user registration information locally, but can obtain the terminal's user registration information by interacting with other SBCs. In other words, the user registration information is obtained through exchange between SBCs, thereby completing the terminal's registration and enabling the terminal to successfully register, thus avoiding the terminal frequently requesting registration repeatedly.

[0140] For example, the first network element is SBC1. The first terminal is requesting registration from SBC1 for the first time. SBC1 does not store the user registration information of the first terminal, but other SBCs may store the user registration information of the first terminal. Therefore, SBC1 can request to obtain the user registration information of the first terminal from other SBCs. For example, SBC1 can obtain the user registration information of the first terminal from SBC2.

[0141] In this application, "fake registration" refers to the ability of a first network element to generate fake user registration information, thereby terminating the terminal's registration process and enabling the terminal to successfully register. For example, the first network element can generate fake user registration information and record the user of the first terminal as a fake registered user.

[0142] 503: The first network element sends a second message to the first terminal to indicate that the first terminal has successfully registered. Correspondingly, the first terminal receives the second message.

[0143] In other words, in this application, the registration process is terminated by replacing the CSCF network element with the first network element, thereby realizing the registration of terminal users, thus avoiding the frequent triggering of re-registration due to terminal registration failure, solving the problem of unavailable terminal data services, and improving user experience.

[0144] In another implementation, the first network element queries the records. If a CSCF in a normal / reachable state exists, for example, the CSCF corresponding to SBC2 in the record is in a normal state, then the registration of the first terminal fails. The first network element can send a response message to the first terminal to indicate the registration failure. Optionally, the response message can indicate that the first terminal can migrate to another SBC to request registration (optionally indicating SBC2), such as sending an OXX message (e.g., a 404 message).

[0145] Optionally, in one implementation, for a re-registration scenario, the first message sent by the first terminal to the first network element is a re-registration message. Upon receiving the re-registration message from the first terminal, for example, if the first network element stores user registration information corresponding to the first terminal, then the first network element makes the following judgment:

[0146] (1) The first network element queries the status record of the call session control network element. If all call session control network elements in the record are in a fault state, the user of the first terminal is set to a self-registered user or a fake registered user. Step 503 is executed, and the first network element sends a first message to the first terminal to indicate successful registration. For example, the second message can be a 200 message with a P-Associated-URI header field added, carrying the user registration information of the first terminal.

[0147] (2) The first network element queries the status record of the call session control network element. If the status of a certain call session control network element in the record is normal, such as the first network element being SBC1, and the CSCF status of SBC2 is found to be normal, then SBC1 sends a failure response message (such as a 404 message) to the first terminal to indicate that the first terminal's registration has failed and it can migrate to other SBCs for registration, such as SBC2.

[0148] In one implementation, when the first network element determines that the call session control network element is completely faulty in step 502, the following steps may also be performed:

[0149] Step a: The first network element sends a third message to the second network element, including information about the first terminal. The third message is used to request the user registration information of the first terminal. Correspondingly, the second network element receives the third message.

[0150] In other words, when the first network element determines that the call session control network element is completely faulty, it can request the user registration information of the first terminal from other network elements such as the second network element.

[0151] Step b: The second network element sends a fourth message to the first network element. Correspondingly, the first network element receives the fourth message.

[0152] Scenario 1: If the second network element stores the user registration information of the first terminal, then the second network element sends a fourth message to the first network element. The fourth message may include the user registration information of the first terminal.

[0153] For example, the fourth message sent by the second network element to the first terminal can be a 200 message with a P-Associated-URI header field added, carrying the implicit registration information of the user of the first terminal.

[0154] In this scenario, the first network element receives the fourth message and obtains the user registration information carried in the fourth message. It can then set the user of the first terminal as a self-registered user. The second message in subsequent step 503 may include this user registration information.

[0155] Scenario 2: If the second network element does not store the user registration information of the first terminal, then the second network element sends a fourth message to the first network element. This fourth message can be used to indicate a failure response.

[0156] For example, the fourth message sent by the second network element to the first terminal can be an OXX message (such as a 404 message), which indicates that the user registration information of the first terminal does not exist on the second network element.

[0157] In this scenario, the first network element, upon receiving the fourth message, can set the user of the first terminal as a fake registered user and construct fake user registration information, for example, by generating a fake P-Associated-URI header. The fake user registration information may be included in the second message of subsequent step 503.

[0158] In summary, in one implementation, the first network element is SBC1. After receiving the first message, SBC1 can perform the following processing:

[0159] 1. If all the CSCFs corresponding to SBCs in the SBC list recorded by SBC1 are in a fault state, a probe message can be sent to other SBCs in the SBC list to obtain the user registration information corresponding to the first terminal.

[0160] (1) If the user registration information corresponding to the first terminal is obtained from other SBCs such as SBC2, a registration success response message is sent to the first terminal, carrying the user registration information of the first terminal obtained from SBC2.

[0161] (2) If the user registration information corresponding to the first terminal is not obtained from other SBCs, fake user registration information is generated and a registration success response message is sent to the first terminal, carrying the fake user registration information.

[0162] 2. If the CSCF status of SBC2 in the recorded SBC list is normal, a registration failure response message, such as an OXX message, is sent to the first terminal, instructing it to request registration from other SBCs.

[0163] The above implementation method describes the terminal registration process in the case of a complete CSCF failure in an IMS network. Below, in conjunction with... Figure 6 Example 2 illustrates the call flow between end users in a CSCF full-fault scenario.

[0164] Example 2: Terminal call process. The following example uses the case of a first terminal initiating a call request to a second terminal.

[0165] like Figure 6 As shown, the communication method includes the following steps.

[0166] 601: The first terminal sends a call request message to the first network element. Correspondingly, the first network element receives the call request message.

[0167] For example, if the first terminal triggers a voice call service and initiates a call request to the second terminal, the first terminal sends a call request message, such as an INVITE message, to the first network element.

[0168] The call request message may include calling information and called information, where the calling information is the information of the first terminal and the called terminal is the information of the second terminal.

[0169] 602: The first network element confirms whether the first terminal is a self-registered user or a fake registered user based on the calling information in the call request message, and determines that the call session control network element is completely faulty.

[0170] In one implementation, the first network element can query the user registration information of the first terminal based on the calling party information, i.e., the information of the first terminal, in the call request message. According to the aforementioned... Figure 5 In the embodiment shown, the first network element can determine whether the first terminal is a self-registered user or a fake registered user based on local records. In addition, the first network element can determine that all call session control network elements are faulty based on the recorded status of the call session control network element.

[0171] 603: The first network element obtains the user registration information of the second terminal based on the called party information in the call request message. The user registration information includes the access information of the second terminal.

[0172] Specifically, the first network element can query the user registration information of the second terminal based on the called party information in the call request message, such as the information of the second terminal.

[0173] For example, the first network element can query a matching registration number based on the information from the second terminal. The registration number can originate from the P-Associated-URI header field stored by the first network element.

[0174] Optionally, the first network element can perform global format normalization on the called number in the called information of the call request message, and then the first network element can query the number information of the registered user based on the global number to obtain the user registration information of the second terminal.

[0175] For example, the first network element is the SBC (Service Controller). The SBC can identify and modify the format of the called number, such as adding / deleting country codes, area codes, or special symbols, to make it conform to the specifications of the target network. For instance, the SBC can convert internal short numbers to the standard E.164 format or be compatible with the numbering rules of different operators.

[0176] For example, if the called number in the call request message is the number of the second terminal, the first network element can perform global format normalization on the number of the second terminal to obtain the global number of the second terminal.

[0177] For example, when a user terminal registers with the IMS network, the user registration number stored by the network can be a global number, such as an 86+11 digit mobile phone number. When a user makes a call, they may dial a secondary number or not include the country code, such as the country code for China being 86. Therefore, the first network element can perform global format normalization on the called number, i.e., the number of the second terminal, such as converting the secondary number into the corresponding global number, or supplementing it with 86 to generate a global number, and then matching and querying the registration number based on this global number to obtain the corresponding user registration information of the second terminal.

[0178] Similar to the aforementioned embodiments, the first network element can obtain the user registration information of the second terminal from its local query. If the information is not found locally, the first network element can request the user registration information of the second terminal from other network elements, as shown in Embodiment 3 below. Figure 7 Related descriptions.

[0179] For example, the first network element obtains the user registration information of the second terminal by querying. The user registration information includes the access information of the second terminal. For instance, the access information may include the IP address and port number of the second terminal.

[0180] For example, the first network element is an SBC network element. The SBC network element can locally query and obtain the user registration information of the called user who is in the same SBC management area as the calling user. That is, if the first terminal calls a user of the second terminal, and the location of the second terminal is in the same SBC network element as the first terminal, then the SBC network element can query and obtain the user registration information of the second terminal, thereby enabling subsequent processes and successfully establishing a call. Otherwise, if the first terminal calls a user of the second terminal, and the location of the second terminal corresponds to the second SBC network element, while the first terminal corresponds to the first SBC network element, then the first SBC network element cannot obtain the user registration information of the second terminal through local query.

[0181] 604: The first network element forwards a call request message to the second terminal based on the access information to establish a call. Correspondingly, the second terminal receives the call request message.

[0182] The first network element can forward the call request message triggered by the calling party to the second terminal based on the access information obtained from the second terminal. For example, the first network element sends an INVITE message to the second terminal.

[0183] 605: Perform additional procedures for call setup.

[0184] Subsequently, the first terminal, the second terminal, and the first network element interact to complete other procedures for call establishment. For details, please refer to relevant technical content. This application will not elaborate on these procedures.

[0185] Optionally, if the IMS network needs to perform offline call detail record (CDR) billing for the self-switching call service provided in this application, the following steps can also be performed:

[0186] 606: The first network element interacts with the billing function network element to realize billing.

[0187] For example, the billing function network element can be a counting collection function (CCF) network element, which can be used to bill users' call services.

[0188] For example, SBC1 can trigger a billing event by sending an accounting request (ACR) message to the CCF network element, carrying the session identifier and calling information. Correspondingly, the CCF receives the ACR message from SBC1, completes billing data collection and preprocessing (such as call detail record generation), and sends an accounting answer (ACA) message to SBC1.

[0189] In the above embodiments, by marking self-switched registered users or fake registered users, in the event of a complete CSCF failure in the IMS network, the first network element obtains the called user's registration information and forwards the call request message to the second terminal to establish a call. This enables a self-switching call process based on the first network element, improving communication efficiency. For example, if the first network element is an SBC network element, the interaction of the call request message is implemented at the SBC layer, allowing users within the same area of ​​the same operator to successfully make calls, further improving communication efficiency.

[0190] In the above embodiments, in step 603, the first network element can query and obtain the user registration information of the second terminal based on the called party information in the call request message. In another embodiment, if the first network element does not find the user registration information of the second terminal locally, it can request other network elements (such as other SBCs) in the same area to query the user registration information of the second terminal in order to successfully establish a call. See the description of Embodiment 3 below for details.

[0191] Example 3: Terminal call process. The following example uses the first terminal initiating a call request to the second terminal as an example, and the first network element is the SBC network element.

[0192] like Figure 7 As shown, the communication method includes the following steps.

[0193] 701: The first terminal sends a call request message to the first SBC. Correspondingly, the first SBC receives the call request message.

[0194] 702: The first SBC confirms whether the first terminal is a self-registered user or a fake registered user based on the calling information in the call request message, and determines that the call session control network element is completely faulty.

[0195] 703: The first SBC sends a probe message carrying the information of the second terminal based on the called party information in the call request message, in order to request the SBC information corresponding to the second terminal.

[0196] For example, if the first SBC cannot find the user registration information of the second terminal based on the called party information in the call request message, it can send a probe message to request other network elements, such as other SBC network elements, to obtain the session boundary controller information corresponding to the second terminal.

[0197] In one implementation, the first SBC can determine whether the second terminal is a user within a first area based on the called party information in the call request message. Here, the first terminal is a user within the first area. That is, the first SBC can determine whether the calling and called users are in the same area. If the second terminal and the first terminal are in the same area (e.g., within the first area), the first SBC corresponding to the first terminal can interact with the second SBC corresponding to the second terminal, and a call can be successfully established through SBC-level interaction. If the second terminal and the first terminal are in different areas, a call cannot be successfully established, meaning the call may fail.

[0198] 704: The second SBC receives the probe message and queries the user registration information of the second terminal based on the information of the second terminal carried in the probe message.

[0199] For example, the second SBC performs this query based on the information from the second terminal to obtain the user registration information of the second terminal. For instance, the user registration information may include the access information of the second terminal.

[0200] 705: The second SBC queries the user registration information of the second terminal and sends a probe response message to the first SBC. Correspondingly, the first SBC receives the probe response message.

[0201] For example, after the second SBC queries the user registration information of the second terminal, it can send a probe response message to the first SBC to indicate that the second SBC is the session boundary controller corresponding to the second terminal. For example, this probe response message can be a 200 acknowledgment message.

[0202] In another example, if the second SBC does not find the user registration information of the second terminal, it may not reply with a response message, or it may send a failure response message to the first SBC, indicating that the second SBC did not find the user registration information of the second terminal, and / or the second terminal is not registered on the second SBC.

[0203] 706: The first SBC sends a call request message to the second SBC. Correspondingly, the second SBC receives the call request message.

[0204] 707: The second SBC obtains the user registration information of the second terminal, including the access information of the second terminal, based on the called party information in the call request message. The second SBC sends a call request message to the second terminal based on the access information to establish a call.

[0205] The call request message is forwarded to the first network element to establish a call.

[0206] 708: Perform other procedures for call setup.

[0207] Optionally, step 709 may also be included: the first network element interacts with the billing function network element to realize billing.

[0208] In the above embodiments, by marking self-registered users or fake registered users, in the event of a complete CSCF failure in the IMS network, the first network element requests information from other network elements to obtain the session boundary controller (SBC) information corresponding to the second terminal. This allows the first network element to forward a call request message to the SBC corresponding to the second terminal. The SBC then queries and obtains the user registration information of the second terminal, and forwards the call request message to the second terminal, successfully establishing a call and improving communication efficiency. For example, if the first network element is an SBC network element, the interaction of call request messages is implemented at the SBC level, enabling calling and called users within the same operator but in different SBC management areas to successfully make calls, further improving communication efficiency.

[0209] In addition, if the called user is not registered, or if the called user is not a user in this area, the call cannot be successfully established in the event of a complete failure of the CSCF in the IMS network.

[0210] Example 4: Terminal call process. The following example uses the first terminal initiating a call request to the second terminal as an example, and the first network element is the SBC network element.

[0211] like Figure 8 As shown, the communication method includes the following steps.

[0212] 801: The first terminal sends a call request message to the first SBC. Correspondingly, the first SBC receives the call request message.

[0213] 802: The first SBC confirms whether the first terminal is a self-registered user or a fake registered user based on the calling information in the call request message, and determines that the call session control network element is completely faulty.

[0214] In one implementation, if the first SBC determines, based on the called party information in the call request message, that the second terminal is not a user within the first area, then step 803 can be executed: the first SBC sends a call failure message to the first terminal. Correspondingly, the first terminal receives the call failure message.

[0215] In another implementation, if the first SBC confirms that the second terminal is a user in the first area based on the called party information in the call request message, then step 804 can be executed: the first SBC sends a probe message carrying the information of the second terminal to request the acquisition of the SBC information corresponding to the second terminal.

[0216] Correspondingly, the second SBC receives the probe message and queries the user registration information of the second terminal based on the information of the second terminal carried in the probe message.

[0217] 805: The second SBC failed to find the user registration information of the second terminal and sent a probe response message to the first SBC. Correspondingly, the first SBC received the probe response message.

[0218] For example, the probe response message can be a 404 message, indicating that the second SBC cannot find the user registration information of the called user.

[0219] 806: The first SBC sends a call failure message to the first terminal. Correspondingly, the first terminal receives the call failure message.

[0220] For example, the first SBC can send a call failure message, such as an OXX message, to the first terminal to indicate that the call has failed and the call is terminated. Optionally, this call failure message is not used to trigger user re-registration; for example, the call failure message can be a 487 message.

[0221] In one implementation, after the CSCF fault in the IMS network is resolved, terminal users can register normally with the IMS network and resume normal call services. For example, if the first network element detects that the state of the call session control network element has returned to normal, it can re-mark or set self-registered users or fake registered users as normal users to execute subsequent user registration or call procedures. The following describes the terminal registration recovery process and the call service recovery process after the CSCF fault is resolved, with reference to specific embodiments.

[0222] Example 5: The CSCF network element returns to normal during the terminal registration process. The following example uses the first terminal requesting registration from the first network element as an example. Figure 9 As shown.

[0223] 901: The first terminal sends a registration request message to the first network element. Correspondingly, the first network element receives the registration request message from the first terminal.

[0224] 902: The first network element detects that at least one call session control network element is in a reachable state.

[0225] The execution of steps 901 and 902 is not sequential.

[0226] In one implementation, if the first network element detects that at least one CSCF fault has been recovered, or that the CSCF state has been restored to a reachable state, then steps 903-905 can be executed.

[0227] Optionally, the first network element can detect the status of the local CSCF, which can be done by referring to the aforementioned step 500a, and will not be repeated here.

[0228] 903: The first network element sends a registration request message to the CSCF. Correspondingly, the CSCF receives the registration request message.

[0229] 904: The CSCF sends a registration response message to the first network element. Correspondingly, the first network element receives the registration response message.

[0230] The first network element interacts with the CSCF to complete the user registration process. The CSCF sends a registration response message, such as a 401 or 200 response message, to the first terminal through the first network element. The first network element then processes the subsequent registration information normally, completes the IMS registration, and sets the user as a regular registered user.

[0231] 905: The first network element sets the user of the first terminal as a normal registered user.

[0232] In another implementation, if the first network element detects that the fault of the local CSCF has not been recovered, while the CSCF corresponding to the second network element has recovered or the CSCF status has been restored to a reachable state, then step 906 can be executed.

[0233] Optionally, the first network element can detect the status of the CSCF of other SBCs in the same area, which can be referred to in the aforementioned steps 500b-500c, and will not be repeated here.

[0234] 906: The first network element sends a response message to the first terminal, indicating that the registration has been migrated to the second network element. Correspondingly, the first terminal receives the response message.

[0235] If the first network element detects that the call session control network element corresponding to the second network element in the first area is in a reachable state, the first network element sends a response message to the first terminal to instruct the first terminal to register and migrate. For example, the response message can be an OXX message, such as a 503 message, to trigger the first terminal's registration and migration, or it can instruct the first terminal to migrate to the second SBC to request registration.

[0236] In the above embodiments, if the first network element detects that the CSCF status in the IMS network has returned to normal, in the user registration process, the first network element enables the first terminal to successfully register and updates the settings of the first terminal to normal registered user, thereby improving the flexibility and efficiency of user registration in the IMS network.

[0237] Example 6: The CSCF network element returns to normal during the terminal call process. The following example uses the first terminal initiating a call request.

[0238] like Figure 10 As shown, the communication method includes the following steps.

[0239] 1001: The first terminal sends a call request message to the first network element. Correspondingly, the first SBC receives the call request message.

[0240] 1002: The first network element detects that at least one call session control network element is in a reachable state.

[0241] Steps 1002 and 1001 are executed in any order.

[0242] In one implementation, the first network element can detect local CSCF fault recovery or CSCF status recovery to a reachable state.

[0243] Optionally, the first network element can detect the status of the local CSCF, which can be done by referring to the aforementioned step 500a, and will not be repeated here.

[0244] In another implementation, the first network element detects that the fault of the local CSCF has not been recovered, while it detects that the fault of the CSCF corresponding to the second network element has been recovered, or the CSCF status has been restored to a reachable state.

[0245] Optionally, the first network element can detect the status of the CSCF of other SBCs in the same area, which can be referred to in the aforementioned steps 500b-500c, and will not be repeated here.

[0246] 1003: The first network element sends a call failure response message to the first terminal. The call failure response message also instructs the first terminal to re-request registration. Correspondingly, the first terminal receives the call failure response message.

[0247] For example, the first network element determines whether the first terminal is a self-registered user or a fake registered user based on the calling information in the call request message. The calling information carried in the call request message is the information of the first terminal.

[0248] For example, the first network element can determine whether the first terminal is a self-registered user or a fake registered user based on previously saved settings.

[0249] In other words, once the first network element determines that the current CSCF status has returned to normal, it can instruct the first terminal to re-register so that the user registration process can be executed normally before the call process can be executed, thereby improving communication efficiency.

[0250] For example, the call failure response message can be an OXX message, such as a 503 message, used to trigger the first terminal to re-request registration.

[0251] In the above embodiments, if the first network element detects that the CSCF status in the IMS network has returned to normal, during the user call process, the first network element can indicate the call failure to the first terminal and instruct it to re-register, thereby improving the flexibility and communication efficiency of user registration in the IMS network and enhancing the user experience.

[0252] The above mainly describes the solution provided in this application from the perspective of interaction between various devices. Accordingly, this application also provides a communication device, which can be one of the communication devices or nodes in the above method embodiments, or a component such as a chip that can be used in the above communication devices or nodes.

[0253] It is understood that, in order to achieve the aforementioned functions, the communication device includes corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, based on the unit and algorithm operations of the examples described in conjunction with the embodiments disclosed 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 specific applications, but such implementation should not be considered beyond the scope of this application.

[0254] It should be understood that the above description is merely an example illustrating the interaction between the various devices. In reality, the processing performed by the aforementioned communication devices or nodes is not limited to being performed by a single network element.

[0255] This application can divide the communication device into functional modules based on the above method examples. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one module or unit. These modules or units can be implemented in hardware or as software functional modules. It is understood that the module or unit division in this application is illustrative and represents only one logical functional division; in actual implementation, other division methods may be used.

[0256] In addition, this application also provides a communication device for implementing the above-described communication method. For example... Figure 11As shown, the communication device includes a communication module 1101 and a processing module 1102, used to implement the method executed by the first network element or the second network element in the above embodiments. Optionally, the communication device 1100 may further include a storage module 1103 for storing device program code and / or data.

[0257] The communication module 1101 can be used to receive a first message from the first terminal, which is used to request initial registration or re-registration.

[0258] The processing module 1102 can be used to set the user of the first terminal to a self-registered user or a fake registered user if it is determined that the call session control network element is completely faulty.

[0259] The communication module 1101 can also be used to send a second message to the first terminal to indicate that the first terminal has successfully registered.

[0260] In one implementation, if it is determined that the call session control network element is completely faulty, the communication module 1101 can also be used to send a third message to the first network element, the third message including information of the first terminal, the third message being used to request the user registration information of the first terminal.

[0261] In one embodiment, the communication module 1101 can also be used to receive a fourth message from the first network element. If the fourth message includes user registration information of the first terminal, the processing module 1102 can be used to set the user as a self-switching registered user, and the second message includes the user registration information. If the fourth message is used to indicate a failure response, the user is set as a fake registered user and fake user registration information is constructed, and the second message includes the fake user registration information.

[0262] In one embodiment, the communication module 1101 can also be used to send a probe message to at least one session boundary controller, the probe message being used to obtain the status of the call session control network element corresponding to the session boundary controller; wherein, the at least one session boundary controller includes a first network element; and receive a probe response message from the at least one session boundary controller, the probe response message being used to indicate that the call session control network element is in a fault state or a reachable state.

[0263] In one embodiment, the processing module 1102 can be used to save the status information of the call session control network element corresponding to the at least one session boundary controller.

[0264] In one embodiment, the communication module 1101 can also be used to receive a call request message from a first terminal; the processing module 1102 can be used to confirm, based on the calling information in the call request message, whether the first terminal is a self-registered user or a fake registered user, and to determine that all call session control network elements are faulty; the processing module 1102 can be used to obtain the user registration information of a second terminal based on the called information in the call request message, the user registration information including the access information of the second terminal; the communication module 1101 can also be used to forward the call request message to the second terminal based on the access information to establish a call.

[0265] In one embodiment, the processing module 1102 can be used to perform global format normalization on the called number in the called information of the call request message to obtain the global number of the second terminal; and query the number information of the registered user based on the global number to obtain the user registration information of the second terminal.

[0266] In one embodiment, the communication module 1101 can also be used to receive a call request message from a first terminal; the processing module 1102 can be used to confirm, based on the calling information in the call request message, whether the first terminal is a self-registered user or a fake registered user, and to determine that the call session control network element is completely faulty; if, based on the called information in the call request message, no user registration information for the second terminal is found, the communication module 1101 can also be used to send a probe message, the probe message including information about the second terminal, the probe message being used to request the acquisition of the session boundary controller corresponding to the second terminal; the communication module 1101 can also be used to receive a probe response message, the probe response message being used to indicate that the first network element is the session boundary controller corresponding to the second terminal; the communication module 1101 can also be used to forward the call request message to the first network element to establish a call.

[0267] In one implementation, the processing module 1102 can be used to confirm that the second terminal is a user in the first area based on the called party information in the call request message.

[0268] In one embodiment, the communication module 1101 can also be used to receive a call request message from the first terminal; the processing module 1102 can be used to confirm whether the first terminal is a self-registered user or a fake registered user based on the calling information in the call request message, and to determine that the call session control network element is completely faulty; if the called information in the call request message confirms that the second terminal is not a user in the first area, then a call failure message is sent to the first terminal.

[0269] In one embodiment, the communication module 1101 can also be used to receive a call request message from the first terminal; detect that at least one call session control network element is in a reachable state; the processing module 1102 can be used to confirm that the first terminal is a self-registered user or a fake registered user based on the calling information in the call request message; the communication module 1101 can also be used to send a call failure response message to the first terminal, the call failure response message being used to instruct a re-registration request.

[0270] In one embodiment, the communication module 1101 can also be used to receive the registration request message of the first terminal, and if the status of the call session control network element is detected to be reachable, interact with the call session control network element to complete the user registration, and set the user of the first terminal as a normal registered user.

[0271] In one embodiment, the communication module 1101 can also be used to receive the registration request message of the first terminal; if the status of the call session control network element corresponding to the first network element in the first area is detected to be reachable, a response message is sent to the first terminal, the response message being used to indicate registration migration to the first network element.

[0272] In summary, when the communication device 1100 is used to implement the functions performed by the network device or node in the above embodiments, other functions that the communication device 1100 can implement can be referred to the relevant descriptions of any of the embodiments shown above, and will not be elaborated further.

[0273] In a simplified embodiment, those skilled in the art will recognize that the communication device 1100 can employ... Figure 3 The form shown. For example, Figure 3 The processor 301 can call computer execution instructions stored in the memory 303 to cause the communication device 300 to execute the method described in the above method embodiment.

[0274] For example, Figure 11 The function / implementation process of the processing module 1102 can be achieved through... Figure 3 It is implemented by processor 301 in the system.

[0275] For example, Figure 11 The function / implementation process of the communication module 1101 can be obtained through Figure 3 It is implemented using the communication interface 304.

[0276] It is understood that one or more of the above modules or units can be implemented by software, hardware, or a combination of both. When any of the above modules or units are implemented by software, the software exists as computer program instructions and is stored in memory. The processor can be used to execute the program instructions and implement the above method flow. The processor can be built into a SoC (System-on-a-Chip) or ASIC, or it can be a separate semiconductor chip. In addition to the core that executes software instructions for computation or processing, the processor may further include necessary hardware accelerators, such as field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), or logic circuits that implement dedicated logic operations.

[0277] When the above modules or units are implemented in hardware, the hardware can be any one or any combination of a CPU, microprocessor, digital signal processing (DSP) chip, microcontroller unit (MCU), artificial intelligence processor, ASIC, SoC, FPGA, PLD, application-specific digital circuit, hardware accelerator, or non-integrated discrete device, which can run the necessary software or perform the above method flow independently of software.

[0278] In one possible implementation, this application also provides a chip system, including: at least one processor and an interface, wherein the at least one processor is coupled to a memory via the interface, and when the at least one processor executes a computer program or instructions in the memory, the method in any of the above method embodiments is executed. In one possible implementation, the chip system further includes a memory. Optionally, the chip system may be composed of chips or may include chips and other discrete devices; this application does not specifically limit this.

[0279] Optionally, this application also provides a computer-readable storage medium. All or part of the processes in the above method embodiments can be implemented by a computer program instructing related hardware. This program can be stored in the aforementioned computer-readable storage medium. When executed, the program can include the processes described in the above method embodiments. The computer-readable storage medium can be an internal storage unit of the communication device in any of the foregoing embodiments, such as the hard disk or memory of the communication device. The aforementioned computer-readable storage medium can also be an external storage device of the communication device, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the communication device. Further, the aforementioned computer-readable storage medium can include both internal storage units and external storage devices of the communication device. The aforementioned computer-readable storage medium is used to store the aforementioned computer program and other programs and data required by the communication device. The aforementioned computer-readable storage medium can also be used to temporarily store data that has been output or will be output.

[0280] In one possible implementation, this application also provides a computer program product. All or part of the processes in the above method embodiments can be executed by a computer program instructing related hardware. This program can be stored in the above computer program product, and when executed, it can include the processes of the above method embodiments.

[0281] In one possible implementation, this application also provides computer instructions. All or part of the processes in the above method embodiments can be executed by computer instructions instructing related hardware (such as a computer, processor, network device, or terminal device). The program can be stored in the aforementioned computer-readable storage medium or the aforementioned computer program product.

[0282] In one possible implementation, this application also provides a communication system, which may include network devices such as the first network element and the second network element in the above embodiments.

[0283] 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.

[0284] 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 in actual implementation, there may be other division methods. 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 mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0285] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

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

[0287] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions 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 communication method, characterized in that, The method includes: Receive a first message from the first terminal, the first message being used to request initial registration or re-registration; If it is determined that the entire call session control network element is faulty, the user of the first terminal is set to a self-registered user or a fake registered user. A second message is sent to the first terminal to indicate that the first terminal has successfully registered.

2. The method according to claim 1, characterized in that, If it is determined that the entire call session control network element is faulty, the method further includes: A third message is sent to the first network element. The third message includes information about the first terminal and is used to request the user registration information of the first terminal.

3. The method according to claim 2, characterized in that, The method further includes: Receive a fourth message from the first network element; if the fourth message includes user registration information of the first terminal, then set the user as a self-registered user, and the second message includes the user registration information. If the fourth message is used to indicate a failure response, then the user is set as a fake registered user and fake user registration information is constructed, and the second message includes the fake user registration information.

4. The method according to any one of claims 1-3, characterized in that, The method further includes: Send a probe message to at least one session boundary controller, the probe message being used to obtain the status of the call session control network element corresponding to the session boundary controller; wherein, the at least one session boundary controller includes a first network element; Receive a probe response message from the at least one session boundary controller, the probe response message being used to indicate that the call session control network element is in a fault state or a reachable state.

5. The method according to claim 4, characterized in that, The method further includes: Save the status information of the call session control network element corresponding to the at least one session boundary controller.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: Receive a call request message from the first terminal; Based on the calling information in the call request message, it is confirmed that the first terminal is a self-registered user or a fake registered user, and it is determined that all call session control network elements are faulty. Based on the called party information in the call request message, obtain the user registration information of the second terminal, wherein the user registration information includes the access information of the second terminal; The call request message is forwarded to the second terminal based on the access information to establish a call.

7. The method according to claim 6, characterized in that, The method further includes: The called number in the called information of the call request message is globally formatted to obtain the global number of the second terminal; Based on the global number, query the registered user's number information to obtain the user registration information of the second terminal.

8. The method according to any one of claims 1-5, characterized in that, The method further includes: Receive a call request message from the first terminal; Based on the calling information in the call request message, it is confirmed that the first terminal is a self-registered user or a fake registered user, and it is determined that the call session control network element is completely faulty. If the user registration information of the second terminal is not found based on the called party information in the call request message, a probe message is sent. The probe message includes information about the second terminal and is used to request the acquisition of the session boundary controller corresponding to the second terminal. Receive a probe response message, the probe response message being used to indicate that the first network element is the session boundary controller corresponding to the second terminal; The call request message is forwarded to the first network element to establish a call.

9. The method according to claim 8, characterized in that, The method further includes: Based on the called party information in the call request message, the second terminal is confirmed to be a user within the first area.

10. The method according to any one of claims 1-5, characterized in that, The method further includes: Receive a call request message from the first terminal; Based on the calling information in the call request message, it is confirmed that the first terminal is a self-registered user or a fake registered user, and it is determined that the call session control network element is completely faulty. If, based on the called party information in the call request message, it is confirmed that the second terminal is not a user within the first area, then a call failure message is sent to the first terminal.

11. The method according to any one of claims 1-10, characterized in that, The method further includes: Receive a call request message from the first terminal; At least one call session control network element is detected to be in a reachable state. Based on the calling information in the call request message, the first terminal is confirmed to be a self-registered user or a fake registered user. A call failure response message is sent to the first terminal, and the call failure response message is also used to instruct a re-registration request.

12. The method according to any one of claims 1-11, characterized in that, The method further includes: Receive the registration request message from the first terminal, and if the status of the call session control network element is detected to be reachable; The user registration is completed by interacting with the call session control network element, and the user of the first terminal is set as a normal registered user.

13. The method according to any one of claims 1-11, characterized in that, The method further includes: Receive the registration request message from the first terminal; If the status of the call session control network element corresponding to the first network element in the first area is detected to be reachable, a response message is sent to the first terminal. The response message is used to indicate registration migration to the first network element.

14. A communication device, characterized in that, The apparatus is used to implement the method as described in any one of claims 1-13.

15. A communication device, characterized in that, include: A processor, when a computer program or instructions are executed by the processor, causes the method as described in any one of claims 1-13 to be performed.

16. The communication device according to claim 15, characterized in that, It also includes a memory for storing the computer program or instructions.

17. A computer-readable storage medium having a computer program or instructions stored thereon, characterized in that, When the computer program or instructions are executed, the method as described in any one of claims 1-13 is performed.

18. A computer program product, said computer program product comprising computer program code, characterized in that, When the computer program code is run on a computer, the method as described in any one of claims 1-13 is performed.