Call service implementation method and device, electronic equipment, readable medium

Abstract

The application discloses a call service implementation method and device, electronic equipment and readable medium. The method comprises the following steps: judging whether the first state of a terminal in an enhanced mobile switching center and the second state of the terminal in an IMS (Internet Protocol Multimedia Subsystem) are consistent; if not, sending a registration request to the IMS to make the terminal complete an initial call service; wherein the enhanced mobile switching center does not subscribe to registration state information in the IMS. By judging whether the first state and the second state are consistent, when the first state and the second state are inconsistent, a registration request is sent to the IMS, the terminal communicates with the equipment in the IMS and completes the initial call service, and relevant service information in the IMS is obtained, so that the equipment in the enhanced mobile switching center and the IMS does not need to consume memory resources to subscribe to and notify the registration state information, CPU consumption of the equipment in the enhanced mobile switching center and the IMS is reduced, network signaling traffic is reduced, and the performance of network elements is improved.

Description

Technical Field

[0001] The embodiments of the present disclosure relate to the field of communication technologies, and in particular to a method and device for implementing a call service, an electronic device, and a readable medium. Background Art

[0002] The Internet Protocol (IP) Multimedia Subsystem (IMS) is an IP-based network architecture proposed by the 3rd Generation Partnership Project (3GPP). It creates an open and flexible service environment, supports multimedia applications, and provides users with a rich set of multimedia services. IMS is access technology-independent and can provide services for access networks such as General Packet Radio Service (GPRS), Wireless Local Area Network (WLAN), Packet Switched (PS), and Evolved Packet System (EPS). It can also provide services for mobile cellular networks such as the Global System for Mobile Communications (GSM) and the Universal Mobile Telecommunications System (UMTS). Mobile cellular networks such as GSM and UMTS use circuit switching technology, known as the Circuit Switched (CS) domain. When end users in the CS domain access the IMS domain, the CS domain evolves into an access method where services are completely provided by the IMS domain. This technology is called IMS Centralized Service (ICS).

[0003] However, when an end user conducts ICS communications, subscription notification technology is required to ensure that the user status on the enhanced Mobile Switch Center for ICS (eMSC), the Call Session Control Function (CSCF) in the IMS domain, and the Home Subscriber Server (HSS) is consistent, ensuring that the end user's calling and called services proceed normally. If there is no registration status subscription between the eMSC and CSCF, when the end user is deregistered from the IMS network, the SCSCF cannot notify the eMSC of the end user's current status through a notification message (NOTIFY). This will cause the eMSC to display the end user as registered, while the SCSCF will display the end user as deregistered, resulting in inconsistent end user status. If the terminal user initiates a call request to the eMSC at this time, since the eMSC stores the terminal user's registration information and SCSCF name, the eMSC believes that the terminal user is in the registered state. Therefore, the eMSC will forward the terminal user's call request to the SCSCF. However, since the SCSCF finds that the terminal user is in the deregistered state, it will directly reject the call request, resulting in the terminal user being unable to complete normal communication.

[0004] Because the existing technology requires that the eMSC and SCSCF must maintain the relevant information of the status subscription, the eMSC and SCSCF must consume memory resources to save the relevant information of the status subscription, and also maintain related messages such as initial subscription, refresh subscription, notification messages, etc., which increases the signaling traffic in the communication network and the CPU consumption of the network element, and reduces the performance of the network element. Summary of the Invention

[0005] The present disclosure provides a method and apparatus for implementing a call service, an electronic device, and a readable medium to solve the problem of a terminal user being unable to access the IMS normally due to the terminal user not subscribing to registration status information during ICS communication.

[0006] In a first aspect, an embodiment of the present disclosure provides a method for implementing a call service, the method comprising: determining whether a first state of a terminal in an enhanced mobile switching center is consistent with a second state of the terminal in an Internet Protocol Multimedia Subsystem (IMS); if not, sending a registration request to the IMS to enable the terminal to complete an initial call service; wherein the enhanced mobile switching center does not subscribe to registration status information in the IMS.

[0007] In a second aspect, an embodiment of the present disclosure provides a method for implementing a call service, the method comprising: receiving a registration request sent by an enhanced mobile switching center, wherein the registration request is a request sent by the enhanced mobile switching center when the enhanced mobile switching center determines that a first state of a terminal within the enhanced mobile switching center and a second state of the terminal in an Internet Protocol Multimedia Subsystem (IMS) are inconsistent, and the enhanced mobile switching center has not subscribed to registration status information in the IMS, and the registration request includes an identifier of the terminal; registering the terminal in the IMS based on the identifier of the terminal; and providing service data for the terminal in response to the call request of the terminal forwarded by the enhanced mobile switching center, thereby completing the initial call service.

[0008] In a third aspect, an embodiment of the present disclosure provides a device for implementing a call service, the device comprising: a judgment module for judging whether a first state of a terminal in an enhanced mobile switching center and a second state of a terminal in an Internet Protocol Multimedia Subsystem (IMS) are consistent; a sending module for sending a registration request to the IMS when it is determined that the first state and the second state are inconsistent, so that the terminal completes the initial call service, wherein the enhanced mobile switching center has not subscribed to registration status information in the IMS.

[0009] In a fourth aspect, an embodiment of the present disclosure provides a call session control functional entity, including: a receiving module for receiving a registration request sent by an enhanced mobile switching center, wherein the registration request is a request issued by the enhanced mobile switching center when it determines that a first state of a terminal in the enhanced mobile switching center and a second state of the terminal in the Internet Protocol Multimedia Subsystem IMS are inconsistent, and the enhanced mobile switching center has not subscribed to registration status information in the IMS, and the registration request includes an identifier of the terminal; a registration module for registering the terminal in the IMS based on the identifier of the terminal; and a service module for responding to the call request of the terminal forwarded by the enhanced mobile switching center, providing service data for the terminal, and completing the initial call service.

[0010] In a fifth aspect, an embodiment of the present disclosure provides an electronic device comprising: one or more processors; a storage device on which one or more programs are stored, and when the one or more programs are executed by one or more processors, the one or more processors implement the method described in the first aspect or the second aspect.

[0011] In a sixth aspect, an embodiment of the present disclosure provides a computer-readable medium having a computer program stored thereon, which implements the method described in the first aspect or the second aspect when the program is executed by a processor.

[0012] The method provided by the embodiment of the present disclosure determines whether a first state of a terminal in an enhanced mobile switching center is consistent with a second state of the terminal in an IMS. When the state is inconsistent, a registration request is sent to the IMS, so that the terminal can communicate with a device in an Internet protocol multimedia subsystem, thereby enabling the terminal to complete an initial call service and obtain relevant service information in the Internet protocol multimedia subsystem. This eliminates the need for the devices in the enhanced mobile switching center and the Internet protocol multimedia subsystem to consume memory resources to store registration status information and related signaling information, thereby reducing CPU consumption of the devices in the enhanced mobile switching center and the Internet protocol multimedia subsystem, reducing network signaling traffic, and improving network element performance. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The accompanying drawings are used to provide a further understanding of the embodiments of the present disclosure and constitute a part of the specification. Together with the embodiments of the present disclosure, they are used to explain the present disclosure and do not constitute a limitation of the present disclosure. The above and other features and advantages will become more apparent to those skilled in the art by describing the detailed exemplary embodiments with reference to the accompanying drawings, in which:

[0014] Figure 1 This is an ICS network architecture diagram for user equipment accessing IMS through GSM and UMTS networks.

[0015] Figure 2 This is a flow chart of ICS user registration and subscription signaling.

[0016] Figure 3 This is the signaling flow chart for the S-CSCF in the IMS network to proactively initiate deregistration of an ICS user.

[0017] Figure 4 This is the signaling flow chart for the IMS-HSS in the IMS network to proactively initiate ICS user deregistration.

[0018] Figure 5 This is a method flow chart of the implementation method of the call service in Example 1 of the present application.

[0019] Figure 6 This is a flow chart of a method for implementing the call service in Example 2 of the present application.

[0020] Figure 7 This is a flow chart of the working method of the enhanced mobile switching center in embodiment 3 of the present application when performing the initial call service of the terminal.

[0021] Figure 8 This is a method flow chart of the method for implementing the call service in Example 4 of the present application.

[0022] Figure 9This is a method flow chart of the method for implementing the call service in Example 5 of the present application.

[0023] Figure 10 This is a flow chart of the working method of the user terminal in Example 6 of the present application when performing a call service.

[0024] Figure 11 This is a block diagram of a device for implementing a call service in Example 7 of the present application.

[0025] Figure 12 This is a block diagram of the composition of a call session control function entity in Example 8 of the present application.

[0026] Figure 13 This is a block diagram of a device for implementing a call service in Example 9 of the present application.

[0027] Figure 14 This is a structural diagram of an exemplary hardware architecture of an electronic device that can implement the method and apparatus for implementing the call service according to the embodiment of the present application in the tenth embodiment of the present application. DETAILED DESCRIPTION

[0028] To enable those skilled in the art to better understand the technical solutions of the present invention, the method and apparatus, electronic device, and computer-readable medium provided by the present invention are described in detail below with reference to the accompanying drawings.

[0029] Example embodiments will be described more fully hereinafter with reference to the accompanying drawings, but the example embodiments may be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete and will fully convey the scope of this disclosure to those skilled in the art.

[0030] The terms "first" and "second" in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that the numbers used in this way can be interchanged where appropriate so that the embodiments described herein can be implemented in an order other than that shown or described herein. In addition, the terms "including" or "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0031] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art. It will also be understood that terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant art and the present disclosure, and will not be interpreted as having an idealized or overly formal meaning unless expressly defined as such herein.

[0032] ICS networks have the following advantages: 1) IMS provides unified services for circuit switching domains, packet switching domains, and other access methods, supporting network convergence; 2) It supports the evolution of CS networks to IMS networks; 3) It supports not only user terminals with ICS capabilities, but also existing user terminals without ICS capabilities. Among them, user terminals without ICS capabilities are also called traditional user terminals. Figure 1 This is an ICS network architecture diagram for user equipment (UE) accessing the IMS via the GSM or UMTS network. The ICS network architecture diagram primarily includes the following network elements: UE 110, eMSC 120, CSCF 130, Telecom Application Server (TAS) 140, and Home Server 150.

[0033] UE 110 is used to attach to a CS cellular network and then perform a call service (for example, UE 110 initiates a call request as a calling party; or UE 110 receives a call request sent by a calling terminal as a called party). UE 110 may or may not support ICS capabilities.

[0034] The ICS-enabled eMSC 120 connects UE 110 to 2nd Generation Mobile Networks (2G) or 3rd Generation Mobile Networks (3G), and also registers with the IMS network on behalf of traditional terminals. When UE 110 initiates a call, eMSC 120 forwards the call request to the IMS domain, where relevant equipment executes the user service. The interface between UE 110 and eMSC 120 is the A / Iu interface.

[0035] CSCF 130 is responsible for IMS domain registration authentication, call routing, and service triggering. It includes an interrogating call session control function (I-CSCF) 131 and a serving call session control function (S-CSCF) 132. The I2 interface between eMSC 120 and CSCF 130 is based on the Session Initiation Protocol (SIP).

[0036] The TAS 140 is responsible for executing user-subscribed services. The standard ISC interface based on the SIP protocol is used between the S-CSCF 132 and the TAS 140. The Sh interface based on the Diameter protocol is used between the IMS-HSS 151 and the TAS 140. The Diameter protocol is not a single protocol, but a protocol suite consisting of the Diameter Base Protocol and various application protocols derived from it.

[0037] Home server 150 stores UE information and may include an IMS-HSS 151 and a Home Location Register (HLR) 152 in the CS domain. The IMS-HSS 151 serves users in the IMS domain, while the HLR 152 serves users in the CS domain. The interface between the IMS-HSS 151 and the S-CSCF 132 is a Cx interface based on the Diameter protocol, while the interface between the HLR 152 and the eMSC 120 is a C interface based on the Mobile Application Part (MAP) protocol.

[0038] Figure 2 This is a flowchart of ICS user registration and subscription signaling, which specifically includes the following steps.

[0039] S201, UE 110 initiates a Location-Update request to eMSC 120;

[0040] S202 : The eMSC 120 completes downloading of service data required by the terminal through signaling interaction with the home server 150 , and enables the home server 150 to update the address of the eMSC 120 stored therein.

[0041] S203, the eMSC 120 returns a Location-Update response to the UE 110, wherein the Location-Update response includes an attach identity indicating that the UE 110 is successfully attached in the CS domain.

[0042] S204, the eMSC 120 prepares to initiate IMS registration on behalf of the UE 110 to the IMS domain according to the ICS user attribute of the subscription returned by the HLR 152 in the home server 150, or according to the ICS user attribute configured according to the number segment of the International Mobile Subscriber Identity (IMSI) of the ICS user terminal of the subscription.

[0043] S205, the eMSC 120 sends a registration request to the CSCF 130, wherein the registration request is used to register the UE 110 to the IMS domain.

[0044] S206, after receiving the registration request sent by the eMSC 120, the CSCF 130 performs signaling interaction with the IMS-HSS 151 in the home server 150, and downloads the subscription data to the CSCF 130.

[0045] S207, the CSCF 130 returns a registration success response message to the eMSC 120.

[0046] S208, after receiving the registration success response, the eMSC 120 initiatively initiates a registration state subscription request to the CSCF 130.

[0047] S209, after receiving the registration state subscription request sent by the eMSC 120, the S-CSCF 132 in the CSCF 130 processes the subscription request, and returns a subscription success response to the eMSC 120.

[0048] S210, the S-CSCF 132 in the CSCF 130 sends a notification message (NOTIFY) to the eMSC 120 based on the subscription session, wherein the notification message is used to inform the eMSC 120 of the registration state of the UE 110 in the IMS.

[0049] S211, after obtaining the registration state of the UE 110 in the IMS, the eMSC 120 returns a success response to the S-CSCF 132 in the CSCF 130, so that the S-CSCF 132 determines that the eMSC 120 is aware of the registration state of the UE 110 in the IMS.

[0050] It should be noted that when the ICS user (e.g., UE 110) is successfully registered in the IMS domain and successfully subscribes to the registration status information, if the state of the ICS user in the IMS network changes, the IMS network can actively trigger a network logout, so that the eMSC 120 can learn the state of the ICS user in the IMS domain. The network logout includes a network logout in the CSCF 130 and an IMS network logout. In the prior art, the S-CSCF 132 sends a NOTIFY message to the eMSC 120 (e.g., step S210 described above) through an existing subscription session, so that the eMSC 120 can synchronize the logout of the ICS user, thereby ensuring that the registration status of the ICS user on the S-CSCF 132, the IMS-HSS 151 and the eMSC 120 can be kept consistent.

[0051] Figure 3 is a signaling flowchart in which the S-CSCF 132 in the IMS network initiatively initiates the logout of the ICS user, and can include the following steps.

[0052] S301, the user terminal (UE) 110 successfully completes registration in the CS domain and in the IMS domain, and the state of the UE 110 in the CS domain and the state of the UE 110 in the IMS domain are both registered states.

[0053] S302, the call session control function entity 130 triggers the logout of the UE 110 due to the needs of operator management.

[0054] For example, the operator upgrades and removes the UE 110, or requires the UE 110 to re-register, etc.

[0055] S303, the call session control function entity 130 sends a notification message (NOTIFY) to the eMSC 120 after logging out the UE 110 from the IMS based on the state message subscribed by the eMSC 120, wherein the notification message includes the state of the UE 110 in the IMS as a logout state.

[0056] S304, after the eMSC 120 learns that the state of the UE 110 in the IMS is a logout state, the eMSC 120 also logs out the UE 110 from the CS domain and changes the state of the UE 110 in the CS domain to a logout state.

[0057] S305, the eMSC 120 sends a successful response to the call session control function entity 130, so that the call session control function entity 130 learns that the state of the UE 110 in the CS domain is a logout state.

[0058] S306 , the call session control function 130 sends a service assignment request (Server-Assignment-Request) to the home server 150 , instructing the HSS 151 in the home server 150 to deregister the UE 110 .

[0059] S307 , after deregistering UE 110 , HSS 151 in home server 150 feeds back a service assignment answer message (Server-Assignment-Answer) to call session control function 130 , so that call session control function 130 knows that UE 110 has been successfully deregistered.

[0060] At this point, after the SCSCF initiates the deregistration of UE 110 in the IMS, the status of UE 110 on the eMSC and the status of UE 110 on the call session control function entity 130 are both deregistered based on the status of UE 110 on the home server 150, so that the status of UE 110 in the CS domain remains consistent with that in the IMS.

[0061] Figure 4 This is a signaling flow chart of the IMS-HSS 151 in the IMS network proactively initiating deregistration of an ICS user, which may specifically include the following steps.

[0062] S401: User terminal (UE) 110 successfully completes registration in both the CS domain and the IMS domain. The status of UE 110 in the CS domain and the status in the IMS domain are both registered.

[0063] S402 : Due to operator management requirements, the IMS-HSS 151 in the home server 150 triggers deregistration of the UE 110 .

[0064] For example, the operator removes UE 110 before upgrading, or deregisters UE 110 due to the need to release a number.

[0065] S403 , the IMS-HSS 151 constructs and sends a Registration-Termination-Request (RTR request) to notify the call session control function 130 to deregister the UE 110 .

[0066] S404 , after receiving the RTR request, the call session control function entity 130 deregisters the UE 110 and returns a Registration-Termination-Answer (RTA response) to the IMS-HSS 151 .

[0067] S405 : The call session control function 130 sends a NOTIFY message to the eMSC 120 based on the status message to which the eMSC 120 has subscribed. The NOTIFY message includes information that the UE 110 is in the deregistered state in the IMS.

[0068] S406 , the eMSC 120 deregisters the UE 110 according to the relevant information in the received NOTIFY message indicating that the UE 110 is in the deregistered state in the IMS, and updates the state of the UE 110 in the CS domain to the deregistered state.

[0069] S407 , the eMSC 120 sends a success response (eg, a response message including a 200 OK) to the call session control function 130 .

[0070] At this point, after the IMS-HSS initiates the deregistration of UE 110 in the IMS, the status of UE 110 on the eMSC and the status of UE 110 on the call session control function entity 130 are both deregistered based on the status of UE 110 on the IMS-HSS 151, so that the status of UE 110 in the CS domain remains consistent with that in the IMS.

[0071] In the prior art described above, deregistration operations for user terminals rely on subscription notification technology to ensure consistent user terminal status across the eMSC, the IMS domain's call session control function, and the IMS-HSS, thereby ensuring the normal operation of calling and receiving services initiated by the user terminal. If the eMSC and the call session control function do not subscribe to registration status information, the call session control function cannot notify the eMSC via a NOTIFY message during network deregistration. This results in the user terminal being registered on the eMSC while deregistered on the call session control function. If the user terminal initiates a call, the eMSC, having locally stored the user terminal's registration information and the name of the SCSCF in the call session control function, assumes the user is registered and sends the call request to the SCSCF. However, since the user terminal is deregistered from the SCSCF, the SCSCF directly rejects the call request, causing the originating call to fail. Since the subscription session must be maintained between the eMSC and SCSCF, on the one hand, the memory resources of the eMSC and SCSCF are consumed to save the relevant information of the subscription session. On the other hand, the interactive messages in the subscription session (for example, initial subscription, refresh subscription, notification messages) increase the network signaling traffic and the CPU consumption of the network element, thereby reducing the performance of the network element.

[0072] Example 1

[0073] This embodiment relates to a method for implementing a call service, which is used to solve the above problems, thereby reducing the consumption of buffer resources of an enhanced mobile switching center, reducing network signaling traffic, and ensuring that the call service of a user terminal can be completed normally and quickly.

[0074] The following is a detailed description of the implementation details of the method in this embodiment. The following content is only for the convenience of understanding the implementation details of this solution and is not necessary for implementing this solution.

[0075] Figure 5 FIG. 1 is a flow chart of a method for implementing a call service in this embodiment, which can be applied to a device for implementing a call service, and the device can run on an eMSC. The method can include the following steps.

[0076] S510: Determine whether a first state of the terminal in the enhanced mobile switching center is consistent with a second state of the terminal in the Internet Protocol Multimedia Subsystem IMS.

[0077] It should be noted that the enhanced mobile switching center does not subscribe to registration status information in the IMS. The first status can be a registered state or a deregistered state, and the second status can also be a registered state or a deregistered state. If the first status and the second status are inconsistent, step 520 is executed; otherwise, the process ends.

[0078] S520: Send a registration request to the IMS.

[0079] Specifically, when the device in the IMS receives the registration request of the terminal, if it is determined through query that the second state of the terminal in the IMS is the registered state, the terminal is allowed to successfully access the device in the IMS, thereby completing the initial call service.

[0080] In some specific implementations, if the first state is a registered state and the second state is a deregistered state, a registration request is sent to the IMS so that the terminal completes the initial call service.

[0081] It should be noted that because the first state is inconsistent with the second state, and the first state is the registered state, the call service implementation device will believe that the terminal is a user that has successfully registered in the CS domain, but has not registered in the IMS domain. Therefore, it is necessary to send a registration request to the IMS to enable the device in the IMS to complete the registration of the terminal. When the second state of the terminal in the IMS is updated to the registered state, the call service implementation device will send a call request of the terminal to the device in the IMS, thereby enabling the terminal to successfully complete the initial call service and obtain relevant service data in the IMS. This ensures that even if the terminal has not subscribed to the registration status information in the IMS, the initial call service of the terminal can still be completed quickly and smoothly, thereby improving the efficiency of service processing.

[0082] In some specific implementations, after the terminal completes the initial call service steps, the method further includes: deregistering the terminal in response to a deregistration message sent by a home location register HLR in the IMS; and changing the first state to a deregistered state.

[0083] It should be noted that if the home location register (HLR) in the IMS initiates deregistration of the terminal, the signaling interaction between the service call session control function entity and the home server in the IMS enables all devices in the IMS to know that the second state of the terminal is the deregistered state. However, since the terminal has not subscribed to the registration state information in the IMS, the HLR proactively sends a deregistration message to the call service implementation device, informing the call service implementation device that the terminal will be deregistered, and changes the first state of the terminal to the deregistered state, so that the first state of the terminal in the CS domain and the second state in the IMS are both deregistered states. This synchronizes the states in advance for the subsequent call service of the terminal, ensures that the subsequent service processes of the terminal can be completed smoothly, improves service processing efficiency, and improves user experience.

[0084] In this embodiment, by determining whether the first state of the terminal in the enhanced mobile switching center is consistent with the second state of the terminal in the IMS, if they are inconsistent, a registration request is sent to the IMS, so that the terminal can communicate with the device in the Internet protocol multimedia subsystem, thereby enabling the terminal to complete the initial call service and obtain relevant service information in the Internet protocol multimedia subsystem. This eliminates the need for the devices in the enhanced mobile switching center and the Internet protocol multimedia subsystem to consume memory resources to store registration state information and related signaling information, thereby reducing CPU consumption of the devices in the enhanced mobile switching center and the Internet protocol multimedia subsystem, reducing network signaling traffic, and improving network element performance.

[0085] Example 2

[0086] Figure 6 This is a flowchart of a method for implementing a call service in this embodiment. This method can be applied to a device for implementing a call service, which can run on an eMSC. Embodiment 2 is substantially the same as the first embodiment, with the primary difference being that, upon determining that the first and second states of the terminal are inconsistent, a registration request is sent to a querying call session control function entity in the IMS, enabling the querying call session control function entity to reselect a serving call session control function entity for the terminal, namely, a second serving call session control function entity, to complete the relevant services for the terminal in the IMS domain.

[0087] The method for implementing the call service in this embodiment may include the following steps.

[0088] S610: Receive an initial call request sent by a terminal, and obtain a first state of the terminal in the enhanced mobile switching center.

[0089] Among them, the initial call request includes the terminal identification. The call service implementation device searches the local database or cache based on the terminal identification to find out whether the terminal has been successfully registered with the call service implementation device, that is, whether the first state of the terminal in the enhanced mobile switching center is a registered state or a deregistered state.

[0090] In some specific implementations, after step 610, the method further includes: if it is determined that the first state is a deregistered state, sending a registration request to the IMS.

[0091] Specifically, when it is determined that the first state is the deregistered state, it indicates that the terminal is not registered with the call service implementation device, and it is necessary to first complete the terminal's registration process with the enhanced mobile switching center and update the terminal's first state with the enhanced mobile switching center to the registered state. Since the terminal's second state in the IMS domain may also be the deregistered state, it is necessary to send a registration request to the IMS to ensure that the terminal can complete registration with the IMS domain, so that the terminal's second state in the IMS domain is also the registered state, thereby achieving synchronization between the first state and the second state.

[0092] S620: Acquire a second state of the terminal in the Internet Multimedia Subsystem IMS.

[0093] Specifically, a query request may be sent to a device in the IMS, and the second state of the terminal in the IMS may be obtained through a query result fed back by the device in the IMS. The second state may be a registered state or a deregistered state.

[0094] In some specific implementations, the initial call request is forwarded to a first serving call session control function entity in the IMS; and in response to a call rejection response fed back by the first serving call session control function entity, the second state of the terminal is obtained as a deregistered state.

[0095] It should be noted that, because the terminal's first state in the enhanced mobile switching center is registered, the call service implementation device determines that the terminal has successfully registered with the IMS and therefore sends an initial call request to the first serving call session control function entity in the IMS. However, since the first serving call session control function entity determines, by querying the terminal's identifier, that the terminal is not registered with the IMS, i.e., the terminal's second state is deregistered, the first serving call session control function entity rejects the terminal's call request and sends a call rejection response back to the call service implementation device, informing the call service implementation device that the terminal is not registered with the IMS.

[0096] In some specific implementations, after step S610 and before forwarding the initial call request to the first serving call session control function entity in the IMS, the method further includes: caching the initial call request in an enhanced mobile switching center.

[0097] It should be noted that if the terminal is not registered in the IMS, and the first service call session control function entity in the IMS feeds back a call rejection response, that is, the terminal is rejected from completing the call service in the IMS domain, then the call service implementation device or the eMSC including the call service implementation device will cache the call request sent by the terminal and cannot immediately return a call success response or a call failure response to the terminal. After the eMSC assists the terminal in completing the registration of the terminal in the IMS domain and determines whether the terminal can complete the call service in the IMS domain, the call success response or the call failure response will be fed back to the terminal.

[0098] If it is determined that the first serving call session control function entity in the IMS is not because the terminal is not registered with the IMS (it may be due to a failure of related equipment in the IMS, etc.), but the first serving call session control function entity still feeds back a call rejection response to the eMSC, the eMSC can directly return a call failure response to the terminal and reject the current call service of the terminal.

[0099] S630: Determine whether the first state of the terminal in the enhanced mobile switching center is consistent with the second state of the terminal in the Internet Protocol Multimedia Subsystem IMS.

[0100] It should be noted that the enhanced mobile switching center does not subscribe to registration status information in the IMS. If the first and second states are inconsistent, step 640 is executed; otherwise, the process ends. Step S630 in this embodiment is the same as step S510 in the first embodiment and will not be repeated here.

[0101] S640: Send a registration request to the I-CSCF in the IMS.

[0102] The registration request includes the terminal identifier, and the I-CSCF is used to query the Home Subscriber Server HSS according to the terminal identifier, select a second serving call session control function entity for the terminal, and forward the registration request to the second serving call session control function entity.

[0103] It should be noted that the I-CSCF is the entry point of the IMS network. Its main function is to specify a service call session control function entity for the user terminal to perform the terminal's registration service. For example, it queries the home subscriber server HSS based on the terminal's identifier, obtains the address of the second service call session control function entity, and then selects the second service call session control function entity for the terminal to perform the terminal's registration service.

[0104] Specifically, the I-CSCF uses the address of the second serving call session control function entity as the destination address and forwards the terminal's registration request to the second serving call session control function entity, so that the terminal can successfully register with the second serving call session control function entity.

[0105] S650: In response to the registration success response fed back by the I-CSCF, the initial call request of the terminal is sent to the second serving call session control function entity.

[0106] The successful registration response includes the address of the second serving call session control function entity, enabling the enhanced mobile switching center to obtain the address of the second serving call session control function entity. The enhanced mobile switching center then uses the address of the second serving call session control function entity as the destination address and sends the terminal's initial call request to the second serving call session control function entity, allowing the terminal to complete its initial call service through the second serving call session control function entity.

[0107] It should be noted that, because the terminal was originally registered with the first service call session control function entity, but due to a device failure or other reasons in the IMS domain, the first service call session control function entity restarts or performs disaster recovery, causing the first service call session control function entity to deregister the terminal, and the terminal has not subscribed to registration status information, resulting in inconsistency between the first and second states of the terminal. When the terminal initiates a call request, the terminal needs to re-register with the IMS domain. That is, the enhanced mobile switching center re-registers the terminal with the second service call session control function entity, so that the second service call session control function entity provides the terminal with the corresponding IMS domain service data.

[0108] In this embodiment, when determining that the first and second states of the terminal are inconsistent, a registration request is sent to the query call session control function entity in the IMS, allowing the query call session control function entity to reselect a serving call session control function entity for the terminal, namely, the second serving call session control function entity, thereby ensuring that the terminal can re-register with the IMS and, in turn, successfully complete its call service in the IMS domain. Even if the terminal has not subscribed to registration status information, registration and call services in the IMS domain can still be quickly completed, reducing the amount of registration status subscription information maintained between network element devices, simplifying signaling processes, improving service processing efficiency, and enhancing user experience.

[0109] Example 3

[0110] Figure 7 This is a flowchart of the working method of the eMSC in this embodiment when performing initial call services for a terminal. This method, independent of the registration status subscription notification mechanism, resolves the inconsistency between the first status of an ICS user on the eMSC and the second status on the IMS domain, ensuring that the initial call service process for the terminal can proceed normally. The method specifically includes the following steps.

[0111] S701, user terminal 7001 sends a local update request to enhanced mobile switching terminal eMSC7002.

[0112] S702, eMSC7002 completes the update of local information (for example, making the home server 7004 update the address of eMSC7002 stored therein, etc.) by performing signaling interaction with the device in the IMS (for example, the home server 7004 in the IMS).

[0113] S703, eMSC7002 feeds back a local update success response to the user terminal 7001.

[0114] S704, the eMSC 7002 sends a registration request to the first serving call session control function entity 7003. The registration request is used to enable the user terminal 7001 to register with the first serving call session control function entity 7003 in the IMS.

[0115] S705: After receiving the registration request from the eMSC 7002, the first serving call session control function entity 7003 sends a subscription data request (for example, a Diameter_SAR message based on the Diameter protocol) to the home server 7004 in the IMS.

[0116] S706 , after confirming that the subscription with the user terminal 7001 is successful, the home server 7004 feeds back a subscription data success response (for example, a Diameter_SAA message based on the Diameter protocol) to the first serving call session control function entity 7003 .

[0117] S707 , the first serving call session control function entity 7003 returns a registration success response message to the eMSC 7002 , so that the eMSC 7002 confirms that the user terminal 7001 has been successfully registered with the first serving call session control function entity 7003 in the IMS.

[0118] It should be noted that since eMSC7002 did not initiate registration status subscription, the first status of the user terminal 7001 on eMSC7002 (i.e., the registration status of the user terminal 7001 in the CS domain) and its second status on the device in the IMS (i.e., the registration status of the user terminal 7001 in the IMS domain) may be inconsistent.

[0119] S708: The IMS domain initiates deregistration of user terminal 7001. Through signaling interaction between first serving call session control function entity 7003 and home server 7004, all devices in the IMS are aware that the second state of user terminal 7001 is deregistered. However, because eMSC 7002 has not initiated a registration state subscription, first serving call session control function entity 7003 is unable to send a notification message (NOTIFY) to eMSC 7002. As a result, the first state of user terminal 7001 on eMSC 7002 remains registered.

[0120] S709, user terminal 7001 sends a call request to eMSC 7002 in the CS domain.

[0121] S710 , the eMSC 7002 learns through query that the first state is the registered state, and then forwards the call request of the user terminal 7001 to the first serving call session control function entity 7003 .

[0122] S711, after the first service call session control function entity 7003 receives the call request (for example, SIP_INVITE based on the SIP protocol) from the user terminal 7001, it finds out through query that the user terminal 7001 has been deregistered and will reject the call service of the user terminal 7001, so it feeds back a call failure response message (for example, a call failure response message based on the SIP protocol) to the eMSC7002.

[0123] It should be noted that the call failure response message carries a user unregistered indication, which indicates that the second state of user terminal 7001 in the IMS is a deregistered state. The SIP protocol is used for transmission between first serving call session control function entity 7003 and eMSC 7002, but other communication protocols may also be used. These protocols can be set based on actual circumstances. Other communication protocols not exemplified are also within the scope of protection of this application and will not be described in detail here.

[0124] S712, eMSC7002 obtains the user unregistered indication by parsing the received call failure response message, and learns that the second state of the user terminal 7001 in the IMS is the deregistered state. It then caches the call request message of the user terminal 7001 to the enhanced mobile switching center, and at the same time sends a new registration request to the query call session control function entity (I-CSCF) 7005 in the IMS.

[0125] S713 , the I-CSCF 7005 assigns the user terminal 7001 to register with the second serving call session control function entity 7006 through query, and then forwards the new registration request to the second serving call session control function entity 7006 .

[0126] S714, after receiving the new registration request sent by the I-CSCF 7005, the second serving call session control function entity 7006 sends a re-subscription data request (for example, sending a Diameter_SAR message based on the Diameter protocol) to the home server 7004 in the IMS.

[0127] S715 , after confirming that the re-subscription of the user terminal 7001 is successful, the home server 7004 feeds back a re-subscription data success response (for example, a Diameter_SAA message based on the Diameter protocol) to the second serving call session control function entity 7006 .

[0128] S716 , the second serving call session control function entity 7006 returns a new registration success response message to the I-CSCF 7005 .

[0129] The registration success response message includes the address of the second service call session control function entity 7006.

[0130] S717 , the I-CSCF 7005 confirms that the user terminal 7001 has been successfully registered with the second serving call session control function entity 7006 in the IMS, and feeds back a registration success response to the eMSC 7002 .

[0131] It should be noted that after confirming that the user terminal 7001 is registered with the second service call session control function entity 7006 in the IMS, the first state of the user terminal 7001 in the eMSC7002 and its second state in the IMS are both registered states, ensuring that the state of the user terminal 7001 in the CS domain is consistent with its state in the IMS domain.

[0132] S718, eMSC7002 sends the cached call request of the user terminal 7001 to the newly registered second service call session control function entity 7006 according to the address of the second service call session control function entity 7006 in the registration success response message to complete the call service and ensure the normal progress of the call service process.

[0133] In this embodiment, by forwarding a call request of a user terminal to a first serving call session control function entity in the IMS and obtaining a call failure response message fed back by the first serving call session control function entity, it is learned that the first state of the user terminal in the eMSC is inconsistent with the second state in the IMS. Then, a re-registration request is sent to the IMS domain to re-register the user terminal with the second serving call session control function entity in the IMS. This ensures that the first state of the user terminal in the CS domain and the second state in the IMS domain are consistent, that is, both are registered states. The initial call service is then completed, and relevant service information in the IMS is obtained. This eliminates the need for devices in the eMSC and IMS to consume memory resources to store registration state information and related signaling information, thereby reducing CPU consumption of devices in the eMSC and IMS, reducing network signaling traffic, and improving network element performance.

[0134] Example 4

[0135] This embodiment relates to a method for implementing a call service. The following describes the implementation details of the method in this embodiment. The following content is only for the convenience of understanding the implementation details of this solution and is not necessary for implementing this solution.

[0136] Figure 8 This is a flow chart of a method for implementing a call service in this embodiment. The method can be applied to a call session control function entity and specifically includes the following steps.

[0137] S801: Receive a registration request sent by an enhanced mobile switching center.

[0138] The registration request is a request sent by the enhanced mobile switching center when it determines that a first state of the terminal in the enhanced mobile switching center is inconsistent with a second state of the terminal in the Internet Protocol Multimedia Subsystem (IMS), and the enhanced mobile switching center has not subscribed to registration state information in the IMS. The registration request includes an identifier of the terminal.

[0139] It should be noted that the call session control function entity may include: a query call session control function entity, a first serving call session control function entity, and a second serving call session control function entity. A terminal is initially registered with the first serving call session control function entity, but due to network adjustments or equipment maintenance, the second state of the terminal in the first serving call session control function entity becomes inconsistent with its first state in the enhanced mobile switching center (for example, the first state is a registered state, while the second state is a deregistered state). In this case, the terminal needs to resend a registration request to the IMS through the enhanced mobile switching center so that the terminal can re-register with the IMS.

[0140] S802: Register the terminal in the IMS according to the terminal identifier.

[0141] Specifically, the home user server is searched based on the identifier of the terminal, a second service call session control function entity in the IMS is selected for the terminal, and the terminal is registered with the second service call session control function entity. When the registration is completed, the second service call session control function entity returns a registration success response message to the enhanced mobile switching center, where the registration success response message includes the address of the second service call session control function entity.

[0142] When the enhanced mobile switching center receives the registration success response message returned by the second serving call session control function entity, it can determine that the second state of the terminal has been updated to the registered state. When the first state and the second state of the terminal are both registered states, the first state and the second state of the terminal are kept consistent. At the same time, by parsing the registration success response message, the address of the second serving call session control function entity is obtained, so that the enhanced mobile switching center can send the cached call request of the terminal to the newly registered second serving call session control function entity based on the address.

[0143] S803: In response to the call request of the terminal forwarded by the enhanced mobile switching center, the terminal is provided with service data to complete the initial call service.

[0144] Specifically, when the second service call session control function entity receives a call request from a terminal forwarded by the enhanced mobile switching center, it will provide the terminal with corresponding service data based on the relevant service requirement information carried in the call request to complete the call service and ensure the normal progress of the call service process.

[0145] In this embodiment, by receiving a registration request sent by an enhanced mobile switching center, obtaining an identifier, and registering the terminal in the IMS based on the terminal identifier, the terminal is ensured to maintain consistency between the first and second states of the terminal. After receiving a call request from the terminal forwarded by the enhanced mobile switching center, service data is provided to the terminal, ensuring that the call service for the terminal can be successfully completed. This eliminates the need for devices in the enhanced mobile switching center and the IMS to consume memory resources to store registration status information and related signaling information, thereby reducing CPU consumption in the devices in the enhanced mobile switching center and the IMS, reducing network signaling traffic, and improving network element performance.

[0146] Example 5

[0147] This embodiment relates to a method for implementing a call service. The following describes the implementation details of the method in this embodiment. The following content is only for the convenience of understanding the implementation details of this solution and is not necessary for implementing this solution.

[0148] Figure 9 This is a flow chart of a method for implementing a call service in this embodiment. The method can be applied to a device for implementing a call service, which can run on a home server in an IMS or on an HLR. The method can include the following steps.

[0149] S901: Acquire a first state of a terminal in an enhanced mobile switching center (eMSC) and a second state of the terminal in an Internet protocol multimedia subsystem (IMS).

[0150] Specifically, when the terminal sends a call request message to the eMSC, the terminal will carry the terminal's identifier, and the first state and the second state of the terminal will be specifically determined according to the terminal's identifier.

[0151] In some specific implementations, based on the terminal identifier, a first state stored in the enhanced mobile switching center is obtained; if it is determined that the terminal is integrated with the home subscriber server HSS in the IMS in the same device, a notification message sent by the HSS is received through the internal interface to obtain the second state; otherwise, a notification message sent by the HSS is received through the external interface of the device to obtain the second state.

[0152] For example, when the HLR and HSS are integrated and implemented on the same device, the HLR receives a notification message sent by the HSS through the device's internal interface (e.g., a customized interface between modules). The notification message includes the second state of the terminal in the IMS, allowing the HLR to learn the second state of the terminal by parsing the notification message. When the HLR and HSS are implemented using two independent devices, the HLR receives a notification message sent by the HSS through the device's external interface (e.g., an interface connected by a network cable between devices, or a wireless interface, etc.), allowing the HLR to learn the second state of the terminal by parsing the notification message.

[0153] S902: If it is determined that the first state is inconsistent with the second state, a deregistration instruction is sent to the eMSC.

[0154] Specifically, upon receiving the deregistration instruction, the eMSC deregisters the terminal from the CS domain and synchronizes the terminal's first state (i.e., the terminal's state in the CS domain) with its second state, updating the first state to the deregistered state. Upon receiving a call request from the terminal, the eMSC re-registers the terminal with the IMS and completes the terminal's call service.

[0155] In some specific implementations, if it is determined that the first state is the registered state and the second state is the deregistered state, a deregistration instruction is generated based on the second state; the deregistration instruction is sent to the eMSC so that the eMSC deregisters the terminal and updates the first state to the deregistered state.

[0156] Specifically, due to service needs or device failure, a device in the IMS may deregister a terminal and update the terminal's second status in the IMS to the deregistered state. However, because the terminal has not subscribed to the corresponding registration status information, its first status in the eMSC remains unchanged and remains registered. In this case, the HLR proactively generates a deregistration instruction and sends it to the eMSC, enabling the eMSC to simultaneously deregister the terminal and update its first status to the deregistered state. This ensures that the terminal's first and second statuses remain consistent, facilitating subsequent reconnection of the terminal, reducing signaling interactions, and improving service processing efficiency.

[0157] In this embodiment, by obtaining the terminal's first state in the eMSC and its second state in the IMS, if it is determined that the first and second states are inconsistent, a deregistration instruction is sent to the eMSC, causing the eMSC to deregister the terminal from the CS domain and update the terminal's first state to the deregistered state. This ensures that the terminal's first and second states can be quickly synchronized even when no subscription registration state information is available. This eliminates the need for devices in the eMSC and IMS to consume memory resources to store registration state information and related signaling information, reducing CPU consumption in the eMSC and IMS devices. Furthermore, this allows the terminal to be prepared for subsequent call services, improving service processing efficiency and enhancing user experience.

[0158] Example 6

[0159] Figure 10 FIG. 1 is a flow chart of a working method of a user terminal in this embodiment when performing a call service. The method may include the following steps.

[0160] S1001, user terminal 10001 sends a local update request to enhanced mobile switching terminal eMSC10002.

[0161] S1002, eMSC10002 completes the update of local information (for example, causing the home subscriber server 10004 to update the address of eMSC10002 stored therein, etc.) by performing signaling interaction with a device in the IMS (for example, the home subscriber server HSS10004 in the IMS).

[0162] S1003 , eMSC 10002 feeds back a local update success response to the user terminal 10001 .

[0163] S1004, the eMSC 10002 sends a registration request to the first serving call session control function entity 10003, where the registration request is used to enable the user terminal 10001 to register with the first serving call session control function entity 10003 in the IMS.

[0164] S1005, after receiving the registration request sent by the eMSC 10002, the first serving call session control function entity 10003 sends a subscription data request (for example, sends a Diameter_SAR message based on the Diameter protocol) to the home subscriber server 10004 in the IMS.

[0165] S1006 , after confirming that the subscription with the user terminal 10001 is successful, the home subscriber server 10004 feeds back a subscription data success response (for example, a Diameter_SAA message based on the Diameter protocol) to the first serving call session control function entity 10003 .

[0166] S1007 , the first serving call session control function entity 10003 returns a registration success response message to the eMSC 10002 , so that the eMSC 10002 confirms that the user terminal 10001 has been successfully registered with the first serving call session control function entity 10003 in the IMS.

[0167] It should be noted that since eMSC10002 does not initiate registration status subscription, the first status of the user terminal 10001 on eMSC10002 (i.e., the registration status of the user terminal 10001 in the CS domain) and its second status on the device in the IMS (i.e., the registration status of the user terminal 10001 in the IMS domain) may be inconsistent.

[0168] S1008. When the first service call session control function entity 10003 in the IMS actively deregisters the user (for example, the first service call session control function entity 10003 is restarted or in a disaster recovery scenario due to equipment failure or other reasons), or the home subscriber server 10004 in the IMS actively deregisters the user terminal 10001, through the signaling interaction between the first service call session control function entity 10003 and the home subscriber server 10004, all devices in the IMS know that the second state of the user terminal 10001 is the deregistered state. However, because the eMSC 10002 does not initiate a registration state subscription, the first service call session control function entity 10003 cannot send a notification message (NOTIFY) to the eMSC 10002, resulting in the first state of the user terminal 10001 on the eMSC 10002 still being the registered state.

[0169] S1009 , the home subscriber server 10004 in the IMS sends a cancellation message (eg, MAP_CANCEL_LOCATION message) to the home location server 10005 , where the cancellation message includes the identifier of the user terminal 10001 .

[0170] S1010, the home location server 10005 forwards the MAP_CANCEL_LOCATION message to eMSC10002, informing the IMS domain that the user terminal 10001 has been deregistered, and that eMSC10002 needs to synchronously change the first state of the user terminal 10001 to the deregistered state, so that eMSC10002 deregisters the user terminal 10001 and simultaneously changes the first state of the user terminal 10001 on eMSC10002 to the deregistered state, so that the first state is consistent with its second state on the IMS domain, which facilitates subsequent access by the user terminal 10001.

[0171] It should be noted that when the home user server 10004 and the home location server 10005 are integrated into the same device, the deregistration message sent in step 1009 is transmitted through the internal message interface; otherwise, when the home user server 10004 and the home location server 10005 are two independent devices, the deregistration message sent in step 1009 is transmitted through the device external message interface.

[0172] S1011, user terminal 10001 sends a call request to eMSC 10002 in the CS domain.

[0173] S1012, the eMSC 10002 learns through query that the user terminal 10001 is currently in the deregistered state, and then initiates a new registration process, ie, sends a new registration request to the interrogating call session control function (I-CSCF) 10006.

[0174] S1013 , the I-CSCF 10006 assigns the user terminal 10001 to register with the second serving call session control function entity 10007 through query, and then forwards the new registration request to the second serving call session control function entity 10007 .

[0175] S1014, after receiving the new registration request sent by I-CSCF 10006, the second serving call session control function entity 10007 sends a re-subscription data request (for example, sending a Diameter_SAR message based on the Diameter protocol) to the home subscriber server 10004 in the IMS.

[0176] S1015 , after confirming that the re-subscription of the user terminal 10001 is successful, the home subscriber server 10004 feeds back a re-subscription data success response (for example, a Diameter_SAA message based on the Diameter protocol) to the second serving call session control function entity 10007 .

[0177] S1016 , the second serving call session control function entity 10007 returns a new registration success response message to the I-CSCF 10006 .

[0178] The registration success response message includes the address of the second serving call session control function entity 10007 .

[0179] S1017 , the I-CSCF 10006 confirms that the user terminal 10001 has been successfully registered with the second serving call session control function entity 10007 in the IMS, and feeds back a registration success response to the eMSC 10002 .

[0180] It should be noted that after confirming that the user terminal 10001 is registered with the second service call session control function entity 10007 in the IMS, the first state of the user terminal 10001 in the eMSC10002 and its second state in the IMS are both registered states, ensuring that the state of the user terminal 10001 in the CS domain is consistent with its state in the IMS domain.

[0181] S1018, eMSC10002 sends the cached call request of user terminal 10001 to the newly registered second service call session control function entity 10007 according to the address of the second service call session control function entity 10007 in the registration success response message to complete the call and ensure the normal progress of the call service process.

[0182] In this embodiment, when the first state of a user terminal in the CS domain is inconsistent with its second state in the IMS, and the user terminal is not subscribed, the home location server interacts with the home subscriber server in the IMS, so that the home location server learns that the second state in the IMS is a deregistered state. The deregistered state is then notified to the eMSC, enabling the eMSC to synchronously deregister the user terminal, thereby ensuring synchronization between the first and second states of the user terminal. This eliminates the need for each device to process messages such as subscription requests and notification requests, or maintain subscription session-related processes. This reduces the memory usage of devices in the eMSC and IMS by registration state information, reduces CPU consumption on each device, reduces network signaling traffic, and improves network element performance.

[0183] The steps of the various methods above are divided only for the purpose of clear description. During implementation, they can be combined into one step or some steps can be split and decomposed into multiple steps. As long as they include the same logical relationship, they are all within the scope of protection of this patent. Adding insignificant modifications or introducing insignificant designs to the algorithm or process without changing the core design of the algorithm and process are all within the scope of protection of this patent.

[0184] Example 7

[0185] This embodiment relates to a device for implementing a call service. The specific implementation of the device can be found in the relevant description of the first embodiment, and any repetitions will not be repeated. It is worth noting that the specific implementation of the device in this embodiment can also be found in the relevant description of the second embodiment, but is not limited to the above two embodiments. Other embodiments not described are also within the scope of protection of this device.

[0186] Figure 11is a component block diagram of an implementation device of a call service in the embodiment, and the device mainly comprises: a judging module 1101 configured to judge whether a first state of a terminal in an enhanced mobile switching center and a second state of the terminal in an Internet Protocol Multimedia Subsystem (IMS) are consistent; and a sending module 1102 configured to send a registration request to the IMS to make the terminal complete an initial call service when it is determined that the first state and the second state are inconsistent, wherein the terminal does not subscribe to registration state information in the IMS.

[0187] In the embodiment, the judging module is configured to judge whether the first state of the terminal in the enhanced mobile switching center and the second state of the terminal in the IMS are consistent, and the sending module is configured to send a registration request to the IMS when the first state and the second state are inconsistent, so that the terminal can communicate with a device in the IMS, and then the terminal can complete an initial call service and obtain related service information in the IMS, so that the enhanced mobile switching center and the device in the IMS do not have to consume memory resources to save registration state information and related signaling information, the CPU consumption of the enhanced mobile switching center and the device in the IMS is reduced, the network signaling traffic is reduced, and the performance of the network element is improved.

[0188] It can be found that the embodiment is a device embodiment corresponding to the first embodiment or the second embodiment, and the embodiment can be implemented in cooperation with the first embodiment or the second embodiment. The related technical details mentioned in the first embodiment or the second embodiment are still valid in the embodiment, and are not described herein again to avoid repetition. Correspondingly, the related technical details mentioned in the embodiment can also be applied to the first embodiment or the second embodiment.

[0189] Embodiment Eight

[0190] The embodiment relates to a call session control function entity, and specific implementation of the entity can be referred to related description in the fourth embodiment, and repeated parts are not described herein again. It should be explained that the specific implementation of the call session control function entity in the embodiment is not limited to the above embodiment, and other unexplained embodiments are also within the protection scope of the entity.

[0191] Figure 12This is a block diagram of a call session control function entity in this embodiment. The call session control function entity mainly includes: a receiving module 1201 for receiving a registration request sent by an enhanced mobile switching center. The registration request is a request sent by the enhanced mobile switching center when it determines that a first state of a terminal in the enhanced mobile switching center is inconsistent with a second state of the terminal in the Internet Protocol Multimedia Subsystem (IMS), and the enhanced mobile switching center has not subscribed to registration state information in the IMS. The registration request includes a terminal identifier; a registration module 1202 for registering the terminal in the IMS based on the terminal identifier; and a service module 1203 for responding to the call request from the terminal forwarded by the enhanced mobile switching center, providing service data to the terminal, and completing the initial call service.

[0192] In this embodiment, a receiving module receives a registration request sent by an enhanced mobile switching center, obtains an identifier, and uses a registration module to register the terminal in the IMS based on the terminal identifier, ensuring that the first and second states of the terminal remain consistent. After receiving a call request from the terminal forwarded by the enhanced mobile switching center, the service module can provide service data to the terminal, ensuring that the call service for the terminal can be successfully completed. This eliminates the need for devices in the enhanced mobile switching center and the IMS to consume memory resources to store registration status information and related signaling information, thereby reducing CPU consumption in the devices in the enhanced mobile switching center and the IMS, reducing network signaling traffic, and improving network element performance.

[0193] It is not difficult to find that this embodiment is a device embodiment corresponding to Example 4, and this embodiment can be implemented in conjunction with Example 4. The relevant technical details mentioned in Example 4 are still valid in this embodiment, and to reduce repetition, they are not repeated here. Accordingly, the relevant technical details mentioned in this embodiment can also be applied in Example 4.

[0194] Embodiment 9

[0195] This embodiment relates to a device for implementing a call service. The specific implementation of the device can be found in the relevant description of Example 5, and the repeated parts will not be repeated. It is worth noting that the specific implementation of the device in this embodiment is not limited to the above embodiment, and other embodiments not described are also within the scope of protection of this device.

[0196] Figure 13is a constituent block diagram of an implementation device of the call service in the embodiment, and the device mainly comprises: an acquisition module 1301 configured to acquire a first state of a terminal in an enhanced mobile switching center eMSC and a second state of the terminal in a network protocol multimedia subsystem IMS, wherein the eMSC does not subscribe to register state information in the IMS; and a synchronization module 1302 configured to send a logout instruction to the eMSC to synchronize the first state and the second state when it is determined that the first state is inconsistent with the second state, and to make the terminal complete the call service when receiving a call request sent by the terminal.

[0197] In the embodiment, the acquisition module is configured to acquire a first state of a terminal in an enhanced mobile switching center eMSC and a second state of the terminal in a network protocol multimedia subsystem IMS, and since the terminal does not subscribe to register state information in the IMS, devices in the IMS cannot synchronize the second state of the terminal in the IMS to the eMSC, so that the first state of the terminal in the eMSC and the second state of the terminal in the IMS can be inconsistent. When the first state is inconsistent with the second state, the implementation device of the call service sends a logout instruction to the eMSC to synchronize the first state and the second state, and makes the terminal complete the call service when receiving a call request sent by the terminal. The terminal can successfully call the service, and user experience is improved.

[0198] It can be found that the present embodiment is a device embodiment corresponding to embodiment five, and the present embodiment can be implemented in cooperation with embodiment five. The related technical details mentioned in embodiment five are still valid in the present embodiment. In order to reduce repetition, the detailed description is omitted here. Correspondingly, the related technical details mentioned in the present embodiment can also be applied in embodiment five.

[0199] It should be clear that the present application is not limited to the specific configurations and processes described in the above embodiments and shown in the drawings. For the convenience and brevity of description, the detailed description of known methods is omitted, and the specific working processes of the above-described systems, modules and units can refer to the corresponding processes in the foregoing method embodiments, which will not be described here.

[0200] Embodiment ten

[0201] Figure 14 is a structural diagram of an exemplary hardware architecture of an electronic device that can implement the call service implementation method and device according to the embodiments of the present application in the embodiment.

[0202] As Figure 14As shown, the computing device 1400 includes an input device 1401, an input interface 1402, a central processing unit 1403, a memory 1404, an output interface 1405, and an output device 1406. Among them, the input interface 1402, the central processing unit 1403, the memory 1404, and the output interface 1405 are connected to each other through the bus 1407, and the input device 1401 and the output device 1406 are connected to the bus 1407 through the input interface 1402 and the output interface 1405 respectively, and then connected to other components of the computing device 1400.

[0203] Specifically, the input device 1401 receives input information from the outside, and transmits the input information to the central processing unit 1403 through the input interface 1402; the central processing unit 1403 processes the input information based on the computer executable instructions stored in the memory 1404 to generate output information, temporarily or permanently stores the output information in the memory 1404, and then transmits the output information to the output device 1406 through the output interface 1405; the output device 1406 outputs the output information to the outside of the computing device 1400 for the user to use.

[0204] In one embodiment, Figure 14 The computing device 1400 shown can be implemented as a call service implementation system, which can include a memory configured to store a program, and a processor configured to run the program stored in the memory to execute the method described in any of the above embodiments of the application.

[0205] According to the embodiments of the application, the processes described above with reference to the flowcharts can be implemented as a computer software program. For example, the embodiments of the application include a computer program product including a computer program tangibly embodied on a machine-readable medium, the computer program containing program code for executing the method shown in the flowchart. In such embodiments, the computer program can be downloaded and installed from the network, and / or installed from a removable storage medium.

[0206] It will be appreciated by those skilled in the art that all or some of the steps, systems, and functional modules / units in the methods disclosed above may be implemented as software, firmware, hardware, and appropriate combinations thereof. In hardware implementations, the division between the functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed by several physical components in cooperation. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include a computer storage medium (or non-transitory medium) and a communication medium (or temporary medium). As is well known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable, and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by a computer. In addition, it is well known to those skilled in the art that communication media generally embodies computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0207] It will be understood that the above embodiments are merely exemplary embodiments for illustrating the principles of the present invention, and the present invention is not limited thereto. Those skilled in the art will appreciate that various modifications and improvements can be made without departing from the spirit and substance of the present invention, and such modifications and improvements are also considered to be within the scope of protection of the present invention.

Claims

1. A method for implementing a call service, comprising: determining whether a first state of the terminal in the enhanced mobile switching center is consistent with a second state of the terminal in the Internet Protocol Multimedia Subsystem (IMS); and if not, sending a registration request to the IMS to enable the terminal to complete an initial call service; wherein the enhanced mobile switching center does not subscribe to registration status information in the IMS; If it is determined that the first state and the second state are inconsistent, sending a registration request to the IMS so that the terminal completes the initial call service, including: If the first state is a registered state and the second state is a deregistered state, a registration request is sent to the IMS so that the terminal completes an initial call service.

2. The method according to claim 1, wherein After the terminal completes the initial call service step, the method further includes: deregistering the terminal in response to a deregistration message sent by a home location register HLR in the IMS; The first state is changed to a logged-out state.

3. The method according to claim 1, wherein Before the step of determining whether the first state of the terminal in the enhanced mobile switching center is consistent with the second state of the terminal in the Internet Protocol Multimedia Subsystem IMS, the method further includes: receiving an initial call request sent by a terminal, and acquiring a first state of the terminal in the enhanced mobile switching center; A second state of the terminal in the Internet Protocol Multimedia Subsystem IMS is obtained.

4. The method according to claim 3, wherein: The acquiring the second state of the terminal in the Internet Protocol Multimedia Subsystem IMS includes: forwarding the initial call request to a first serving call session control function entity in the IMS; In response to the call rejection response fed back by the first serving call session control function entity, the second state of the terminal is obtained as a deregistered state.

5. The method according to claim 4, wherein After receiving the initial call request sent by the terminal and before forwarding the initial call request to the first serving call session control function entity in the IMS, the method further includes: The initial call request is cached in the enhanced mobile switching center.

6. The method according to claim 1, wherein The sending of a registration request to the IMS so that the terminal completes the initial call service includes: Sending the registration request to an I-CSCF in the IMS, so that the I-CSCF queries a home subscriber server HSS, selects a second serving call session control function entity for the terminal, and registers with the second serving call session control function entity; wherein the registration request includes an identifier of the terminal; In response to the successful registration response fed back by the I-CSCF, the initial call request of the terminal is sent to the second service call session control function entity, so that the terminal completes the initial call service, wherein the successful registration response includes the address of the second service call session control function entity.

7. A method for implementing a call service, comprising: receiving a registration request sent by an enhanced mobile switching center, wherein the registration request is sent by the enhanced mobile switching center when the enhanced mobile switching center determines that a first state of the terminal in the enhanced mobile switching center is a registered state and a second state of the terminal in an Internet Protocol Multimedia Subsystem (IMS) is a deregistered state, and the enhanced mobile switching center has not subscribed to registration state information in the IMS, and the registration request includes an identifier of the terminal; registering the terminal in the IMS according to the identifier of the terminal; In response to the call request of the terminal forwarded by the enhanced mobile switching center, service data is provided to the terminal to complete the initial call service.

8. A device for implementing a call service, comprising: a determination module, configured to determine whether a first state of the terminal in the enhanced mobile switching center is consistent with a second state of the terminal in the Internet protocol multimedia subsystem IMS; A sending module is configured to send a registration request to the IMS when it is determined that the first state is a registered state and the second state is a deregistered state, so that the terminal completes an initial call service, wherein the enhanced mobile switching center has not subscribed to registration state information in the IMS.

9. A call session control function entity, comprising: a receiving module, configured to receive a registration request sent by an enhanced mobile switching center, wherein the registration request is sent by the enhanced mobile switching center when the enhanced mobile switching center determines that a first state of a terminal in the enhanced mobile switching center is a registered state and a second state of the terminal in an Internet Protocol Multimedia Subsystem (IMS) is a deregistered state, and the enhanced mobile switching center has not subscribed to registration state information in the IMS, and the registration request includes an identifier of the terminal; a registration module, configured to register the terminal in the IMS based on the identification of the terminal; The service module is used to respond to the call request of the terminal forwarded by the enhanced mobile switching center, provide service data for the terminal, and complete the initial call service.

10. An electronic device comprising: one or more processors; A storage device having one or more programs stored thereon, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 6, or the method according to claim 7.

11. A computer-readable medium having a computer program stored thereon, wherein when the program is executed by a processor, the method according to any one of claims 1 to 6 or the method according to claim 7 is implemented.

Images