WO2016050033A1 - 终呼处理方法、装置及系统 - Google Patents

终呼处理方法、装置及系统 Download PDF

Info

Publication number
WO2016050033A1
WO2016050033A1 PCT/CN2015/073805 CN2015073805W WO2016050033A1 WO 2016050033 A1 WO2016050033 A1 WO 2016050033A1 CN 2015073805 W CN2015073805 W CN 2015073805W WO 2016050033 A1 WO2016050033 A1 WO 2016050033A1
Authority
WO
WIPO (PCT)
Prior art keywords
registration information
user
cscf
call
user registration
Prior art date
Application number
PCT/CN2015/073805
Other languages
English (en)
French (fr)
Inventor
李振东
张强
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2016050033A1 publication Critical patent/WO2016050033A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40Network security protocols

Definitions

  • the present invention relates to the field of communications, and in particular to a method, device and system for terminating call processing.
  • the IP Multimedia Core Subsystem is an IP-based network architecture proposed by the 3rd Generation Partnership Project (3GPP) to build an open and flexible network.
  • 3GPP 3rd Generation Partnership Project
  • the business environment supports multimedia applications and provides users with rich multimedia services.
  • control layer In the IMS service system, the control layer and the service layer are separated.
  • the control layer does not provide specific services, and only provides necessary triggering, routing, and accounting functions to the service layer.
  • FIG. 1 is a schematic diagram of a basic IMS architecture defined by the 3GPP in the related art.
  • the service triggering and control function in the control layer is implemented by a Call Session Control Function (CSCF).
  • CSCF Call Session Control Function
  • the call session control functions are divided into: proxy call session control function (Proxy-CSCF, referred to as P-CSCF), query call session control function (Interrogating-CSCF, referred to as I-CSCF), and service call session control function (Serving-CSCF). , referred to as S-CSCF for three types.
  • the business layer is composed of a series of application servers (Application Servers, referred to as ASs), which can provide specific business services.
  • the control layer controls the service trigger according to the subscription information of the user, and invokes the service on the AS to implement the service function.
  • the user's subscription data is stored in the home subscription server (HSS).
  • HSS home subscription server
  • the subscription data is downloaded from the HSS to the S-CSCF to which the user is registered.
  • the end-to-end device in the session is called a user equipment (User Equipment, UE for short) and is responsible for the interaction with the user.
  • Some UEs have multiple access networks, including packet switching through 3GPP (Packet Switch, referred to as For the PS) domain access network, access the network through other non-3GPP PS domains.
  • 3GPP Packet Switch, referred to as For the PS domain access network
  • PS Packet Switch
  • PS Packet Switch
  • Each user is assigned at least one SIP URI, called IMS public user identity (IMPU).
  • IMPU IMS public user identity
  • the format is as follows sip:xyz@abc.com. When an IMS user accesses the IMS, it must first register with the IMS.
  • IP-PBX can register all users of the enterprise network to the IMS at one time with an IMPU containing a wildcard, such as sip:mxcorp@ddx.com.
  • Each user of the subsequent enterprise network can call directly without having to register separately.
  • each user's data must be configured in the HSS.
  • the S-CSCF currently registered by the user is saved in the HSS, and the IMS subscription data of the user is also present on the S-CSCF.
  • FIG. 2 is a flow chart of a process of terminating a call to an IMS user in the related art. As shown in FIG. 2, the process includes the following steps:
  • Step 201 The call request arrives at the I-CSCF of the UE home IMS network;
  • Step 202 After receiving the call request, the I-CSCF initiates a location query to the HSS.
  • Step 203 After receiving the query request, the HSS queries the registration status of the user. If the user has already registered, the registered S-CSCF is returned. If not registered, return a list of S-CSCFs;
  • Step 204 After receiving the response, the I-CSCF sends a call request to the S-CSCF.
  • the I-CSCF needs to select an S-CSCF to send a call request;
  • Step 204a After the S-CSCF receives the call request, if the user has not registered in the S-CSCF, the S-CSCF obtains the user subscription data from the HSS.
  • Step 205 After receiving the call request, the S-CSCF performs the service related to the called party.
  • Step 206 The S-CSCF forwards the call request to the P-CSCF/IBCF. (When the UE registers itself, the call is sent to the P-CSCF, and when the user registers in the enterprise network, it is sent to the IBCF);
  • Step 207 The P-CSCF/IBCF forwards the call request to the UE/IP-PBX.
  • the P-CSCF forwards the call to the UE, the IBCF forwards it to the IP-PBX, and the IP-PBX forwards it to the UE in the enterprise network);
  • Step 208 After the call request finally arrives at the UE, the establishment of the call is completed according to the prior art.
  • Each user needs to access a fixed P-CSCF when registering, and the network will assign an S-CSCF.
  • the IP-PBX accesses the IMS network through the IBCF/P-CSCF.
  • the network often allocates an S-CSCF to serve a specific enterprise network user.
  • the S-CSCF also knows which IBCF to pass.
  • /P-CSCF is connected to the enterprise network.
  • third parties such as websites, there are many users.
  • the performance of assigning a fixed S-CSCF cannot meet the requirements; at the same time, it is used to be scattered everywhere, there is no unified portal like IP-PBX, and access to P-CSCF is different.
  • the existing enterprise network approach cannot meet the demand.
  • the HSS cannot record the S-CSCF currently registered by the unconfigured user. Then at step 204 of Figure 2, the HSS cannot return the address of the S-CSCF.
  • a unified S-CSCF is allocated to a third-party registered user for call processing performance, and due to user dispersion, a unified S-CSCF cannot be implemented.
  • the present invention provides a method, an apparatus and a system for terminating call processing, so as to at least solve the related art, a third-party registered user is assigned a unified S-CSCF, and the call processing performance cannot meet the requirements, and due to user dispersion, Problems that cannot be achieved with a unified S-CSCF.
  • a method for processing a terminal call includes: a third-party database TPUD storing user registration information after registration by a third party, wherein the user registration information includes: a registered user, and the registered user corresponds to Service call session control function S-CSCF; the TPUD receives a query request for querying user registration information corresponding to the called user; the TPUD will query the corresponding user of the called user according to the query request
  • the registration information is sent to the requesting party that sent the query request, wherein the user registration information is used by the requesting party to perform a terminal call process.
  • the requester that sends the query request includes at least one of the following: an application server AS, an inquiry call session control function I-CSCF, and an interconnection boundary control function IBCF.
  • a method for terminating call processing comprising: an application server AS receiving a call request; the AS querying a called party in the call request to a third party database TPUD for storing user registration information User registration information corresponding to the user, wherein the user registration information includes: a registered user, and a service call session control function S-CSCF corresponding to the registered user; the AS receives the TPUD query to the called user The user registration information; the AS forwards the call request to the S-CSCF to perform a terminal call process according to the received user registration information.
  • the AS receives the call request by at least one of: the AS passes, and the inquiry call session control function I-CSCF places the call by treating the called user as a public service identifier PSI.
  • Sending to the AS the call request is received; the AS sends the call request to the TRF by the inquiry call session control function I-CSCF, and the TRF receives the call by means of service triggering.
  • the request is received by the AS by means of a service call session control function S-CSCF service triggering.
  • a terminal call processing method including: an inquiry call session control function I-CSCF receives a call request; and the I-CSCF registers with a third party according to the call request
  • the third party database TPUD of the subsequent user registration information queries the user registration information of the called user in the call request; wherein the user registration information includes: a registered user, and a service call session control function corresponding to the registered user S- CSCF; the I-CSCF receives user registration information of the called user that is queried by the TPUD; and the I-CSCF forwards the call request to the S- according to the received user registration information.
  • the CSCF performs terminal call processing.
  • the I-CSCF queries the user registration information of the TPUD for storing the third-party registered user registration information according to the call request, and includes at least one of the following: the I-CSCF directly from the location
  • the TPUD queries the user registration information of the user; the I-CSCF sends the call request to the application server AS by using the identifier of the called user as a public service identifier PSI, by the AS
  • the TPUD queries the user registration information
  • the user registration information is received by the TPUD, and the user registration information is queried;
  • the I-CSCF sends the information to the AS in a manner triggered by the TRF service.
  • the call request after the AS queries the TPUD for the user registration information, receives the feedback of the user registration information fed back by the TPUD, and queries the user registration information.
  • a terminal call processing apparatus which is applied to a third-party database TPUD, and includes: a storage module configured to store third-party registered user registration information, wherein the user registration letter The information includes: a registered user, and a service call session control function S-CSCF corresponding to the registered user; the first receiving module is configured to receive a query request for querying user registration information corresponding to the called user; the first sending module And sending, according to the query request, the queried user registration information corresponding to the called user to the requesting party that sends the query request, where the user registration information is used by the requesting party to perform terminal call processing. .
  • the requester that sends the query request includes at least one of the following: an application server AS, an inquiry call session control function I-CSCF, and an interconnection boundary control function IBCF.
  • a terminal call processing apparatus which is applied to an application server AS, comprising: a second receiving module configured to receive a call request; and a first query module configured to register with a user for storage
  • the third-party database TPUD of the information queries the user registration information corresponding to the called user in the call request, where the user registration information includes: a registered user, and a service call session control function S-CSC corresponding to the registered user; a receiving module, configured to receive the user registration information of the TPUD to the called user; the first processing module is configured to forward the call request to the user according to the received user registration information
  • the S-CSCF performs termination call processing.
  • the second receiving module is further configured to receive the call request by at least one of: the AS passes, and the query call session control function I-CSCF treats the called user as a public
  • the service identifier PSI sends a call to the AS to receive the call request; the AS passes the inquiry call session control function I-CSCF to send the call request to the TRF, and the TRF is triggered by the service.
  • a call processing apparatus which is applied to an inquiry call session control function I-CSCF, and includes: a fourth receiving module configured to receive a call request; and a second query module configured to Determining, according to the call request, the third party database TPUD for storing the third party registered user registration information, the user registration information of the called user in the call request, wherein the user registration information includes: a registered user, and The service call session control function S-CSCF corresponding to the registered user; the fifth receiving module is configured to receive the user registration information of the TPUD query to the called user; and the second processing module is configured to receive according to the The obtained user registration information forwards the call request to the S-CSCF to perform a terminal call process.
  • the second query module is further configured to query the user registration information by at least one of: directly querying the user registration information of the user from the TPUD; by using the identifier of the called user Sending the call request to the application server AS in a manner that the public service identifier PSI treats, after the AS queries the TPUD for the user registration information, the user registration information received by the TPUD is received.
  • the manner in which the user registration information is fed back is queried to the user registration information.
  • a call processing system comprising: the third party database TPUD according to any one of the above, the application server AS according to any one of the above, and the query according to any one of the above a call session control function I-CSCF, wherein the connection manner between the AS and the TPUD includes at least one of the following: the AS is associated with the TPUD; the AS is separated from the TPUD; and the TPUD is One of the ASs is associated with the other ASs of the plurality of ASs except the ASs that are combined.
  • the third party database TPUD is used to store the third party registered user registration information, wherein the user registration information includes: a registered user, and a service call session control function S-CSCF corresponding to the registered user; the TPUD Receiving a query request for querying user registration information corresponding to the called user; the TPUD sends the queried user registration information corresponding to the called user to the requesting party that sends the query request according to the query request,
  • the user registration information is used by the requesting party to perform the terminating call processing, and the related technology is configured to allocate a unified S-CSCF for the third-party registered user, and the call processing performance cannot meet the requirements, and the user is dispersed.
  • the problem that can not be achieved by using the unified S-CSCF can achieve the effect of improving the efficiency of the user's final call.
  • FIG. 1 is a schematic diagram of a basic IMS architecture defined by the 3GPP in the related art
  • FIG. 2 is a flow chart of a process of terminating a call to an IMS user in the related art
  • FIG. 3 is a flowchart 1 of a method for processing a terminal call according to an embodiment of the present invention
  • FIG. 4 is a second flowchart of a method for processing a terminal call according to an embodiment of the present invention.
  • FIG. 5 is a third flowchart of a method for processing a terminal call according to an embodiment of the present invention.
  • FIG. 6 is a structural block diagram of a terminal call processing apparatus 1 according to an embodiment of the present invention.
  • FIG. 7 is a structural block diagram of a terminal call processing apparatus 2 according to an embodiment of the present invention.
  • FIG. 8 is a structural block diagram of a terminal call processing apparatus 3 according to an embodiment of the present invention.
  • FIG. 9 is a structural block diagram of a terminal call processing system according to an embodiment of the present invention.
  • FIG. 10 is a schematic diagram of a terminal call architecture of an IMS user according to an embodiment of the present invention.
  • 11-1 is a TPUD deployment diagram 1 of a terminal call architecture of an IMS user according to an embodiment of the present invention
  • 11-2 is a TPUD deployment diagram 2 of a terminal call architecture of an IMS user according to an embodiment of the present invention
  • FIG. 11-3 is a TPUD deployment diagram 3 of a terminal call architecture of an IMS user according to an embodiment of the present invention.
  • Figure 13 is a flow chart 2 of a final call according to a preferred embodiment of the present invention.
  • Figure 14 is a flow chart 3 of a terminal call in accordance with a preferred embodiment of the present invention.
  • Figure 15 is a fourth flow diagram of a terminal call in accordance with a preferred embodiment of the present invention.
  • FIG. 3 is a flowchart 1 of a method for processing a terminal call according to an embodiment of the present invention. As shown in FIG. 3, the process includes the following steps:
  • the third-party database TPUD stores the third-party registered user registration information, wherein the user registration information includes: a registered user, and a service call session control function S-CSCF corresponding to the registered user;
  • Step S304 the TPUD receives a query request for querying user registration information corresponding to the called user.
  • Step S306 the TPUD sends the queried user registration information corresponding to the called user to the requesting party that sends the query request according to the query request, where the user registration information is used by the requesting party to perform the terminal call processing.
  • the user terminal call processing is performed according to the third-party registered user registration information stored in the TPUD, which not only solves the problem that the third-party user is assigned a unified S-CSCF in the related art, and the call processing performance cannot meet the requirements, and Due to the dispersion of users, the problem that cannot be realized by using the unified S-CSCF can achieve the effect of improving the efficiency of the user's final call.
  • the requesting party that sends the query request may be multiple, for example, may include at least one of the following: an application server AS, an inquiry call session control function I-CSCF, and an interconnection boundary control function IBCF.
  • FIG. 4 is a second flowchart of a method for processing a terminal call according to an embodiment of the present invention. As shown in FIG. 4, the process includes the following steps:
  • Step S402 the application server AS receives the call request.
  • step S404 the AS queries the third-party database TPUD for storing the user registration information to query the user registration information corresponding to the called user in the call request, where the user registration information includes: the registered user, and the service call session control function corresponding to the registered user.
  • the user registration information includes: the registered user, and the service call session control function corresponding to the registered user.
  • Step S406 the AS receives the TPUD query to the user registration information of the called user.
  • Step S408 the AS forwards the call request to the S-CSCF to perform the terminal call processing according to the received user registration information.
  • the AS performs the user terminal call processing according to the third-party registered user registration information stored in the TPUD, which not only solves the problem that the third-party user is assigned a unified S-CSCF in the related art, and the call processing performance cannot meet the requirements. Moreover, due to the dispersion of users, the problem that cannot be realized by using the unified S-CSCF can achieve the effect of improving the efficiency of the user's final call.
  • the AS may receive the call request in multiple manners.
  • the AS may receive the call request by using at least one of the following methods: the AS passes, and the query call session control function I-CSCF identifies the called user as a public service identifier.
  • the PSI treats the call to the AS and receives the call request; the AS passes the inquiry call session control function I-CSCF to send the call request to the TRF, and the TRF receives the call request by means of service triggering; the AS passes, the service
  • the call session control function triggers the S-CSCF service and receives the call request.
  • FIG. 5 is a third flowchart of a method for processing a terminal call according to an embodiment of the present invention. As shown in FIG. 5, the process includes the following steps:
  • Step S502 the query call session control function I-CSCF receives the call request
  • Step S504 the I-CSCF queries, according to the call request, the user registration information of the called user in the call request to the third-party database TPUD for storing the third-party registered user registration information; wherein the user registration information includes: a registered user, and The service call session control function S-CSCF corresponding to the registered user;
  • Step S506 the I-CSCF receives the user registration information of the called user that is queried by the TPUD;
  • Step S508 the I-CSCF forwards the call request to the S-CSCF to perform the terminal call processing according to the received user registration information.
  • the query call session control function I-CSCF performs the user terminal call processing according to the third-party registered user registration information stored by the TPUD, and not only solves the related art, but also assigns a unified S-CSCF to the third-party user to make a call.
  • the processing performance cannot meet the requirements, and due to the dispersion of users, the problem that cannot be realized by using the unified S-CSCF can achieve the effect of improving the efficiency of the user's final call.
  • the I-CSCF may query the user registration information of the TPUD for storing the third-party registered user registration information according to the call request in multiple manners. For example, at least one of the following may be adopted: the I-CSCF directly queries the user from the TPUD. User registration information; the I-CSCF sends a call request to the application server AS by treating the identity of the called user as a public service identifier PSI, and the user registration of the TPUD feedback is received after the AS queries the TPUD for the user registration information. The information is queried to the user registration information. The I-CSCF sends a call request to the AS in the manner triggered by the TRF service. After the AS queries the TPUD for the user registration information, it receives the TPUD feedback user registration information feedback method and queries the user. registration message.
  • the I-CSCF directly queries the user from the TPUD. User registration information
  • the I-CSCF sends a call request to the application server AS by treating the identity of the called user as a public service identifie
  • a terminal call processing device is also provided, which is used to implement the foregoing embodiments and preferred embodiments, and has not been described again.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 6 is a structural block diagram of a call processing apparatus 1 according to an embodiment of the present invention. As shown in FIG. 6, the apparatus is applied to a third-party database TPUD, and includes: a storage module 62, a first receiving module 64, and a first sending module 66. The device will be described below.
  • the storage module 62 is configured to store third-party registered user registration information, where the user registration information includes: a registered user, and a service call session control function S-CSCF corresponding to the registered user; and a first receiving module 64 connected to the foregoing storage
  • the module 62 is configured to receive a query request for querying user registration information corresponding to the called user.
  • the first sending module 66 is connected to the first receiving module 64, and is configured to respond to the called user according to the query request.
  • the user registration information is sent to the requesting party that sends the query request, wherein the user registration information is used by the requesting party to perform the terminal call processing.
  • the requester that sends the query request includes at least one of the following: an application server AS, an inquiry call session control function I-CSCF, and an interconnection boundary control function IBCF.
  • FIG. 7 is a structural block diagram of a call processing apparatus 2 according to an embodiment of the present invention. As shown in FIG. 7, the apparatus is applied to an application server AS, and includes: a second receiving module 72, a first query module 74, and a third receiving module. 76 and the first processing module 78, the apparatus will be described below.
  • the second receiving module 72 is configured to receive the call request.
  • the first query module 74 is connected to the second receiving module 72, and is configured to query the called user in the call request to the third-party database TPUD for storing the user registration information.
  • User registration information wherein the user registration information includes: a registered user, and a service call session control function S-CSC corresponding to the registered user;
  • the third receiving module 76 is connected to the first query module 74, and is configured to receive the TPUD query.
  • the first processing module 78 is connected to the third receiving module 76, and configured to forward the call request to the S-CSCF to perform the terminal call processing according to the received user registration information.
  • the foregoing second receiving module 72 is further configured to receive a call request by using at least one of the following manners: the AS passes, and the manner in which the call session control function I-CSCF treats the called user as a public service identifier PSI is processed.
  • the call is sent to the AS, and the call request is received; the AS passes the inquiry call session control function I-CSCF to send the call request to the TRF, and the TRF receives the user call request by means of service triggering; the AS passes, the service call session controls
  • the function S-CSCF service triggers the method of receiving a call request.
  • FIG. 8 is a structural block diagram of a call processing apparatus 3 according to an embodiment of the present invention. As shown in FIG. 8, the apparatus is applied to an inquiry call session control function I-CSCF, and includes: a fourth receiving module 82 and a second query module. 84. The fifth receiving module 86 and the second processing module 88 are described below.
  • the fourth receiving module 82 is configured to receive the call request
  • the second query module 84 is connected to the fourth receiving module 82, and is configured to send a third-party database for storing the third-party registered user registration information according to the call request.
  • the TPUD queries the user registration information of the called user in the call request.
  • the user registration information includes: a registered user, and a service call session control function S-CSCF corresponding to the registered user; and a fifth receiving module 86 connected to the second query module.
  • 84 configured to receive the TPUD query to the user registration information of the called user
  • the second processing module 88 is connected to the fifth receiving module 86, and is configured to forward the call request to the S-CSCF according to the received user registration information. End call processing.
  • the foregoing second query module 84 is further configured to query user registration information by at least one of: directly querying user registration information of the user from the TPUD; treating the identifier of the called user as a public service identifier PSI
  • the method sends a call request to the application server AS.
  • the AS queries the TPUD for the user registration information
  • the AS receives the user registration information fed back by the TPUD, and queries the user registration information.
  • the TRF service triggers the method to send a call request to the AS.
  • the user registration information of the TPUD feedback is received, and the user registration information is queried.
  • FIG. 9 is a structural block diagram of a terminal call processing system according to an embodiment of the present invention.
  • the terminating call processing system 90 includes: any one of the foregoing third party databases TPUD92, the application server AS94 of any of the above, and the foregoing The inquiry call session control function I-CSCF96 of any one of the following, wherein the connection manner between the AS and the TPUD includes at least one of the following: AS and TPUD are combined; AS and TPUD are separated; TPUD is combined with one of the plurality of ASs, TPUD It is divided with other ASs other than the ASs in the AS.
  • a terminating call scheme of an IMS user in an IP multimedia subsystem is provided, so that an IMS network operator can provide a better service to a third party service (for example, Voice service) greatly simplifies the configuration of user data in the network.
  • a third party service for example, Voice service
  • FIG. 10 is a schematic diagram of a terminal call architecture of an IMS user according to an embodiment of the present invention.
  • the third party user database TPUD
  • the AS Store registration information for third-party users.
  • the call is first routed to the AS, and the AS queries the TPUD. After the S-CSCF is queried, the call is forwarded to the corresponding S-CSCF.
  • the TPUD may be part of the AS, and the interaction between the AS and the TPUD is an internal process at this time; or it may be an independent entity;
  • FIG. 11-1 is a TPUD deployment diagram of an IMS user's terminal call architecture according to an embodiment of the present invention. As shown in FIG. 11-1, at this time, the AS and the TPUD are combined, and only one such network element exists in the network. This scenario is for scenes with a small number of users.
  • FIG. 11-2 is a TPUD deployment diagram of an IMS user's terminal call architecture according to an embodiment of the present invention. As shown in FIG. 11-2, TPUD is independently set, and multiple ASs of the same type can access TPUD. Load balancing, can handle a large number of users.
  • FIG. 11-3 is a TPUD deployment diagram of an IMS user's terminal call architecture according to an embodiment of the present invention. As shown in FIG. 11-3, there are multiple ASs of the same type, but one of them has a TPUD, and other ASs need to TPUD interaction within the AS.
  • FIG. 12 is a flow chart of an intuitive terminal call according to a preferred embodiment of the present invention. As shown in FIG. 12, the process includes the following steps:
  • Step 501 The call request arrives at the I-CSCF/IBCF of the UE home IMS network;
  • Step 1202 After receiving the call request, the I-CSCF/IBCF initiates a location query to the TPUD; after receiving the query request, the TPUD queries the registration status of the user. If the registration information is not found, the TPUD will return unqueried, and the I-CSCF continues to execute from step 202 as in the background art shown in FIG. If the registration information is found, the S-CSCF registered by the user is returned;
  • Step 1203 The I-CSCF sends a call request to the S-CSCF according to the received S-CSCF.
  • Step 1204 After receiving the call request, the S-CSCF performs the service related to the called party.
  • Step 1205 The S-CSCF forwards the call request to the P-CSCF.
  • Step 1206 The P-CSCF forwards the call request to the UE.
  • Step 1207 After the call request finally arrives at the UE, the establishment of the call is completed according to the prior art.
  • the preferred embodiment belongs to one of the most intuitive implementations, however this requires the I-CSCF to support this function.
  • the corresponding configuration can be performed on the I-CSCF, and the configuration can identify which called users are the above-mentioned third-party users that require special processing. If it is a normal user, the I-CSCF no longer queries the TPUD, but executes the existing process.
  • the terminal call of the above IMS user can also be performed when the I-CSCF is not upgraded.
  • FIG. 13 is a flow chart 2 of a terminal call according to a preferred embodiment of the present invention. As shown in FIG. 13, the process includes the following steps:
  • Step 601 The call request arrives at the I-CSCF/IBCF of the UE home IMS network;
  • Step 1302 Optionally, after receiving the call request, the I-CSCF/IBCF may query the HSS, and the HSS returns an AS address.
  • Step 1303 If the I-CSCF does not perform step 1302, the I-CSCF is configured locally, and the IMPU of the third-party user that needs special treatment in this patent is treated as a (Public Service Identity, PSI).
  • PSI is a special type of SIP URI whose host is AS. Whether the I-CSCF queries the AS address from the HSS or treats the IMPU as a PSI, the SIP URI points to an AS. The I-CSCF sends the call to the AS;
  • Step 1304 After receiving the call request, the AS queries the TPUD to obtain the current S-CSCF address of the user.
  • Step 1305 The AS forwards the call request to the corresponding S-CSCF.
  • Step 1306 After receiving the call request, the S-CSCF performs the service related to the called party.
  • Step 1307 The S-CSCF forwards the call request to the P-CSCF.
  • Step 1308 The P-CSCF forwards the call request to the UE.
  • Step 1309 After the call request finally arrives at the UE, the establishment of the call is completed according to the prior art.
  • FIG. 14 is a flowchart 3 of a terminal call according to a preferred embodiment of the present invention. As shown in FIG. 14, the process includes the following steps:
  • Step 1401 The call request arrives at the I-CSCF/IBCF of the UE home IMS network;
  • Step 1402 the I-CSCF/IBCF may query the HSS, and the HSS returns a Transit function (TRF) address;
  • TRF Transit function
  • Step 1403 If the I-CSCF does not perform step 1402, the I-CSCF is locally configured.
  • the network When receiving the IMPU of the third-party user that needs special handling in this patent, the network is considered to be an IMS relay network. In this case, the call is required.
  • the TRF sent to this network. Whether the I-CSCF queries from the HSS or the network as a relay network, the SIP URI points to the TRF. The I-CSCF sends the call to the TRF;
  • Step 1404 After receiving the call request, the TRF performs a service trigger.
  • the service trigger of the TRF is similar to the service trigger mechanism of the S-CSCF. Only TRF does not need to download each user's business data (such as iFC) from HSS, and iFC is configured on TRF, which is based on iFC of a certain type of user, or iFC based on a certain network;
  • Step 1405 The TRF sends the call to the AS according to the local iFC.
  • Step 1406 After receiving the call request, the AS queries the TPUD to obtain the current S-CSCF address of the user.
  • Step 1407 The AS forwards the call request to the corresponding S-CSCF.
  • Step 1408 After receiving the call request, the S-CSCF performs the service related to the called party.
  • Step 1409 The S-CSCF forwards the call request to the P-CSCF.
  • Step 1410 The P-CSCF forwards the call request to the UE.
  • Step 1411 After the call request finally arrives at the UE, the establishment of the call is completed according to the prior art.
  • FIG. 15 is a flow chart 4 of a terminal call according to a preferred embodiment of the present invention. As shown in FIG. 15, the process includes the following steps:
  • Step 1501 The call request arrives at the I-CSCF/IBCF of the UE home IMS network;
  • Step 1502 After receiving the call request, the I-CSCF/IBCF queries the HSS. Since the HSS does not have registration information for the user, it is not found. According to the prior art, the HSS returns a list of S-CSCFs;
  • Step 1503 The I-CSCF selects an S-CSCF, and sends a call to the S-CSCF.
  • Step 1504 After receiving the call request, the S-CSCF obtains the user subscription data from the HSS, and performs a service trigger.
  • Step 1505 The S-CSCF sends the call route to the AS according to the iFC in the subscription;
  • Step 1506 After receiving the call request, the AS queries the TPUD to obtain the current S-CSCF address of the user.
  • Step 1507 The AS forwards the call request to the corresponding S-CSCF.
  • Step 1508 After receiving the call request, the S-CSCF performs the service related to the called party.
  • Step 1509 The S-CSCF forwards the call request to the P-CSCF.
  • Step 1510 The P-CSCF forwards the call request to the UE.
  • Step 1511 After the call request finally arrives at the UE, the establishment of the call is completed according to the prior art.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the foregoing embodiments and preferred embodiments solve the problem that the third-party registered users are allocated a unified S-CSCF in the related art, and the call processing performance cannot meet the requirements, and the unified S is adopted due to user dispersion.
  • CSCF can't achieve, and thus achieves the effect of improving the efficiency of the user's final call.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本发明公开了一种终呼处理方法、装置及系统,其中,该方法包括:第三方数据库TPUD存储第三方注册后的用户注册信息,其中,用户注册信息包括:注册用户,以及注册用户对应的服务呼叫会话控制功能S-CSCF;TPUD接收到用于查询被叫用户对应的用户注册信息的查询请求;TPUD依据查询请求将查询到的被叫用户对应的用户注册信息发送给发送查询请求的请求方,其中,用户注册信息用于请求方执行终呼处理,通过本发明,解决了相关技术中为第三方注册的用户分配一个统一的S-CSCF进行呼叫处理性能上无法满足要求,并且由于用户的分散,采用统一的S-CSCF也无法实现的问题,进而达到了提高用户终呼效率的效果。

Description

终呼处理方法、装置及系统 技术领域
本发明涉及通信领域,具体而言,涉及一种终呼处理方法、装置及系统。
背景技术
IP多媒体子系统(IP Multimedia Core Network Subsystem,简称为IMS)是由第三代合作伙伴计划(3rd Generation Partnership Project,简称为3GPP)提出的一种基于IP的网络架构,构建了一个的开放而灵活的业务环境,支持多媒体应用,能够为用户提供丰富的多媒体业务。
在IMS业务体系中,控制层和业务层是分离的,控制层不提供具体业务,只向业务层提供必要的触发、路由、计费等功能。
图1是相关技术中3GPP定义的IMS基本架构示意图,如图1所示,控制层中业务触发和控制功能是呼叫会话控制功能(Call Session Control Function,简称为CSCF)完成的。呼叫会话控制功能分为:代理呼叫会话控制功能(Proxy-CSCF,简称为P-CSCF)、查询呼叫会话控制功能(Interrogating-CSCF,简称为I-CSCF)和服务呼叫会话控制功能(Serving-CSCF,简称为S-CSCF)三种类型。
业务层是由一系列应用服务器(Application Server,简称为AS)组成,能提供具体业务服务。控制层(S-CSCF)根据用户的签约信息控制业务触发,调用AS上的业务,实现业务功能。
用户的签约数据存储在归属签约服务器中(Home Subscription Server,简称为HSS),用户在IMS注册时,签约数据会从HSS下载到用户注册到的S-CSCF中。
会话中的端到端设备称为用户设备(User Equipment,简称为UE),负责与使用者的交互,有的UE具有多种接入网络的方式,包括通过3GPP的分组交换(Packet Switch,简称为PS)域接入网络,通过其他非3GPP的PS域接入网络。每个用户都会分配至少一个SIP URI,称为IMS用户公有标识(IMS public user identity,简称为IMPU)。格式如下sip:xyz@abc.com。IMS用户在接入IMS时,首先要在IMS注册。
企业网的出现,出现了通配注册技术。企业网用户,通常其IMPU的用户部分都有相同的前缀,如mx公司在运营商ddx开户的IMPU,用户部分都是以mxcorp开头, 如sip:mxcorp.John@ddx.com,sip:mxcorp.ms@ddx.com。企业网在通过IP-PBX连接到IMS网络时,IP-PBX可以用一个含通配符的IMPU,如sip:mxcorp@ddx.com一次性把企业网所有用户注册到IMS中。后续企业网的每个用户,可以直接呼叫,而无需单独注册一次。
不管何种方式,在相关技术中都要求每个用户的数据必须在HSS中配置。在注册后,HSS中保存了用户当前注册的S-CSCF,S-CSCF上也会有用户的IMS签约数据。
图2是相关技术中向IMS用户终呼过程的流程图,如图2所示,该流程包括如下步骤:
步骤201:呼叫请求到达UE归属IMS网络的I-CSCF;
步骤202:I-CSCF收到呼叫请求后,向HSS发起位置查询;
步骤203:HSS收到查询请求后,查询该用户的注册状态。如果用户已经注册,则返回注册的S-CSCF。如果没有注册,则返回一个S-CSCF的列表;
步骤204:I-CSCF收到应答后,向S-CSCF发送呼叫请求。当收到的是一个S-CSCF列表时,I-CSCF需要从中选出一个S-CSCF来发送呼叫请求;
步骤204a:S-CSCF收到呼叫请求后,如果用户尚未在该S-CSCF注册,则S-CSCF从HSS获取用户签约数据;
步骤205:S-CSCF收到呼叫请求后,执行被叫相关的业务;
步骤206:S-CSCF向P-CSCF/IBCF转发呼叫请求。(当UE是自己注册,呼叫发给P-CSCF,当用户在企业网内注册,则发给IBCF);
步骤207:P-CSCF/IBCF向UE/IP-PBX转发呼叫请求。(P-CSCF把呼叫转发给UE,IBCF则转发给IP-PBX,IP-PBX在转发给企业网内的UE);
步骤208:呼叫请求最终到达UE后,按现有技术完成呼叫的建立。
然而,随着第三方(如一个企业,一个网站等业务的发展,特别是WebRTC技术的出现,上述的技术无法满足需求。
1)如运营商可以将一个或数个号段分配给第三方,如1895000xxxx分配给某第三方;或第三方的IMPU有一个共同的前缀,如上述的sip:mxcorp。但是在IMS网络 HSS中,不能配置每个用户数据。第三方用户数据的维护,是第三方自己完成的。这种需求在现实中非常普遍,如,运营商A给某网站xyz的用户接入IMS,其用户的IMPU,拥有共同的前缀sip:xyz。但是由于各种原因,具体有多少个用户,每个用户的完整IMPU,运营商网络的HSS中没有,或者不完整。
2)每个用户在注册时,都需要接入一个固定的P-CSCF,网络会分配一个S-CSCF。对于企业网,其IP-PBX通过IBCF/P-CSCF接入IMS网络,网络往往固定分配一个S-CSCF为某个具体企业网用户服务,在统配注册后,S-CSCF也知道通过哪个IBCF/P-CSCF连向该企业网。然后,对于上述的第三方,如网站,其用户非常之多。分配一个固定的S-CSCF性能上无法满足要求;同时用于分散在各地,没有一个类似IP-PBX的统一入口,接入P-CSCF各不一样。现有的企业网方式无法满足需求。
当HSS中不能配置每个用户的数据时,HSS就无法记录未能配置的用户当前注册的S-CSCF。那么在图2的步骤204,HSS无法返回S-CSCF的地址。
如果采用企业网式的统配注册,那么要求所有的用户都要在同一个IP-PBX范围内部,并且分配相同的S-CSCF。然而,对于Web网站这类第三方用户,用户是在全球各地上网,无法做到在IP-PBX内部。并且相同的S-CSCF性能上根本无法负担这么大的用户群。
因此,在相关技术中,为第三方注册的用户分配一个统一的S-CSCF进行呼叫处理性能上无法满足要求,并且由于用户的分散,采用统一的S-CSCF也无法实现。
发明内容
本发明提供了一种终呼处理方法、装置及系统,以至少解决相关技术中,为第三方注册的用户分配一个统一的S-CSCF进行呼叫处理性能上无法满足要求,并且由于用户的分散,采用统一的S-CSCF也无法实现的问题。
根据本发明的一个方面,提供了一种终呼处理方法,包括:第三方数据库TPUD存储第三方注册后的用户注册信息,其中,所述用户注册信息包括:注册用户,以及所述注册用户对应的服务呼叫会话控制功能S-CSCF;所述TPUD接收到用于查询被叫用户对应的用户注册信息的查询请求;所述TPUD依据所述查询请求将查询到的所述被叫用户对应的用户注册信息发送给发送所述查询请求的请求方,其中,所述用户注册信息用于所述请求方执行终呼处理。
优选地,发送所述查询请求的所述请求方包括以下至少之一:应用服务器AS、查询呼叫会话控制功能I-CSCF、互联边界控制功能IBCF。
根据本发明的另一方面,提供了一种终呼处理方法,包括:应用服务器AS接收到呼叫请求;所述AS向用于存储用户注册信息的第三方数据库TPUD查询所述呼叫请求中被叫用户对应的用户注册信息,其中,所述用户注册信息包括:注册用户,以及所述注册用户对应的服务呼叫会话控制功能S-CSCF;所述AS接收到所述TPUD查询到所述被叫用户的所述用户注册信息;所述AS依据接收到的所述用户注册信息将所述呼叫请求转发给所述S-CSCF执行终呼处理。
优选地,所述AS通过以下方式至少之一接收到所述呼叫请求:所述AS通过,查询呼叫会话控制功能I-CSCF通过将所述被叫用户当作公共服务标识PSI对待的方式把呼叫发送给所述AS,接收到所述呼叫请求;所述AS通过,查询呼叫会话控制功能I-CSCF将所述呼叫请求发送给TRF,由所述TRF通过业务触发的方式,接收到所述呼叫请求;所述AS通过,服务呼叫会话控制功能S-CSCF业务触发的方式,接收到所述呼叫请求。
根据本发明的又一方面,提供了一种终呼处理方法,包括:查询呼叫会话控制功能I-CSCF接收到呼叫请求;所述I-CSCF依据所述呼叫请求,向用于存储第三方注册后的用户注册信息的第三方数据库TPUD查询所述呼叫请求中被叫用户的用户注册信息;其中,所述用户注册信息包括:注册用户,以及所述注册用户对应的服务呼叫会话控制功能S-CSCF;所述I-CSCF接收到所述TPUD查询到的所述被叫用户的用户注册信息;所述I-CSCF依据接收到的所述用户注册信息将所述呼叫请求转发给所述S-CSCF执行终呼处理。
优选地,所述I-CSCF依据所述呼叫请求,向用于存储第三方注册后的用户注册信息的所述TPUD查询用户的用户注册信息包括以下至少之一:所述I-CSCF直接从所述TPUD查询用户的所述用户注册信息;所述I-CSCF通过,将所述被叫用户的标识当作公共服务标识PSI对待的方式向应用服务器AS发送所述呼叫请求,由所述AS向所述TPUD查询所述用户注册信息后,接收到所述TPUD反馈的所述用户注册信息的方式,查询到所述用户注册信息;所述I-CSCF通过TRF业务触发的方式向所述AS发送所述呼叫请求,由所述AS向所述TPUD查询所述用户注册信息后,接收到所述TPUD反馈的所述用户注册信息反馈的方式,查询到所述用户注册信息。
根据本发明的一方面,提供了一种终呼处理装置,应用于第三方数据库TPUD,包括:存储模块,设置为存储第三方注册后的用户注册信息,其中,所述用户注册信 息包括:注册用户,以及所述注册用户对应的服务呼叫会话控制功能S-CSCF;第一接收模块,设置为接收到用于查询被叫用户对应的用户注册信息的查询请求;第一发送模块,设置为依据所述查询请求将查询到的所述被叫用户对应的用户注册信息发送给发送所述查询请求的请求方,其中,所述用户注册信息用于所述请求方执行终呼处理。
优选地,发送所述查询请求的所述请求方包括以下至少之一:应用服务器AS、查询呼叫会话控制功能I-CSCF、互联边界控制功能IBCF。
根据本发明的另一方面,提供了一种终呼处理装置,应用于应用服务器AS,包括:第二接收模块,设置为接收到呼叫请求;第一查询模块,设置为向用于存储用户注册信息的第三方数据库TPUD查询所述呼叫请求中被叫用户对应的用户注册信息,其中,所述用户注册信息包括:注册用户,以及所述注册用户对应的服务呼叫会话控制功能S-CSC;第三接收模块,设置为接收到所述TPUD查询到所述被叫用户的所述用户注册信息;第一处理模块,设置为依据接收到的所述用户注册信息将所述呼叫请求转发给所述S-CSCF执行终呼处理。
优选地,所述第二接收模块,还设置为通过以下方式至少之一,接收到所述呼叫请求:所述AS通过,查询呼叫会话控制功能I-CSCF通过将所述被叫用户当作公共服务标识PSI对待的方式把呼叫发送给所述AS,接收到所述呼叫请求;所述AS通过,查询呼叫会话控制功能I-CSCF将所述呼叫请求发送给TRF,由所述TRF通过业务触发的方式,接收到所述用户呼叫请求;所述AS通过,服务呼叫会话控制功能S-CSCF业务触发的方式,接收到所述呼叫请求。
根据本发明的又一方面,提供了一种终呼处理装置,应用于查询呼叫会话控制功能I-CSCF中,包括:第四接收模块,设置为接收到呼叫请求;第二查询模块,设置为依据所述呼叫请求,向用于存储第三方注册后的用户注册信息的第三方数据库TPUD查询所述呼叫请求中被叫用户的用户注册信息;其中,所述用户注册信息包括:注册用户,以及所述注册用户对应的服务呼叫会话控制功能S-CSCF;第五接收模块,设置为接收到所述TPUD查询到所述被叫用户的所述用户注册信息;第二处理模块,设置为依据接收到的所述用户注册信息将所述呼叫请求转发给所述S-CSCF执行终呼处理。
优选地,所述第二查询模块,还设置为通过以下方式至少之一查询到所述用户注册信息:直接从所述TPUD查询用户的所述用户注册信息;通过将所述被叫用户的标识当作公共服务标识PSI对待的方式向应用服务器AS发送所述呼叫请求,由所述AS向所述TPUD查询所述用户注册信息后,接收到所述TPUD反馈的所述用户注册信息 的方式,查询到所述用户注册信息;通过TRF业务触发的方式向所述AS发送所述呼叫请求,由所述AS向所述TPUD查询所述用户注册信息后,接收到所述TPUD反馈的所述用户注册信息反馈的方式,查询到所述用户注册信息。
根据本发明的再一方面,还提供了一种终呼处理系统,包括:上述任一项所述第三方数据库TPUD、上述任一项所述的应用服务器AS和上述任一项所述的查询呼叫会话控制功能I-CSCF,其中,所述AS与所述TPUD的连接方式包括以下至少之一:所述AS与所述TPUD合设;所述AS与所述TPUD分设;所述TPUD与多个AS中的一个合设,所述TPUD与所述多个AS中除合设的AS之外的其它AS分设。
通过本发明,采用第三方数据库TPUD存储第三方注册后的用户注册信息,其中,所述用户注册信息包括:注册用户,以及所述注册用户对应的服务呼叫会话控制功能S-CSCF;所述TPUD接收到用于查询被叫用户对应的用户注册信息的查询请求;所述TPUD依据所述查询请求将查询到的所述被叫用户对应的用户注册信息发送给发送所述查询请求的请求方,其中,所述用户注册信息用于所述请求方执行终呼处理,解决了相关技术中为第三方注册的用户分配一个统一的S-CSCF进行呼叫处理性能上无法满足要求,并且由于用户的分散,采用统一的S-CSCF也无法实现的问题,进而达到了提高用户终呼效率的效果。
附图说明
此处所说明的附图用来提供对本发明的进一步理解,构成本申请的一部分,本发明的示意性实施例及其说明用于解释本发明,并不构成对本发明的不当限定。在附图中:
图1是相关技术中3GPP定义的IMS基本架构示意图;
图2是相关技术中向IMS用户终呼过程的流程图;
图3是根据本发明实施例的终呼处理方法的流程图一;
图4是根据本发明实施例的终呼处理方法的流程图二;
图5是根据本发明实施例的终呼处理方法的流程图三;
图6是根据本发明实施例的终呼处理装置一的结构框图;
图7是根据本发明实施例的终呼处理装置二的结构框图;
图8是根据本发明实施例的终呼处理装置三的结构框图;
图9是根据本发明实施例的终呼处理系统的结构框图;
图10是根据本发明实施例的IMS用户的终呼架构的示意图;
图11-1是根据本发明实施例的IMS用户的终呼架构的TPUD部署图一;
图11-2是根据本发明实施例的IMS用户的终呼架构的TPUD部署图二;
图11-3是根据本发明实施例的IMS用户的终呼架构的TPUD部署图三;
图12是根据本发明优选实施方式的直观的终呼流程图一;
图13是根据本发明优选实施方式的终呼流程图二;
图14是根据本发明优选实施例的终呼流程图三;
图15是根据本发明优选实施方式的终呼流程图四。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是,在不冲突的情况下,本申请中的实施例及实施例中的特征可以相互组合。
在本实施例中提供了一种终呼处理方法,图3是根据本发明实施例的终呼处理方法的流程图一,如图3所示,该流程包括如下步骤:
步骤S302,第三方数据库TPUD存储第三方注册后的用户注册信息,其中,用户注册信息包括:注册用户,以及注册用户对应的服务呼叫会话控制功能S-CSCF;
步骤S304,TPUD接收到用于查询被叫用户对应的用户注册信息的查询请求;
步骤S306,TPUD依据查询请求将查询到的被叫用户对应的用户注册信息发送给发送查询请求的请求方,其中,用户注册信息用于请求方执行终呼处理。
通过上述步骤,依据TPUD存储的第三方注册后的用户注册信息来执行用户终呼处理,不仅解决了相关技术中为第三方用户分配一个统一的S-CSCF进行呼叫处理性能上无法满足要求,并且由于用户的分散,采用统一的S-CSCF也无法实现的问题,进而达到了提高用户终呼效率的效果。
其中,发送查询请求的请求方可以为多种,例如,可以包括以下至少之一:应用服务器AS、查询呼叫会话控制功能I-CSCF、互联边界控制功能IBCF。
图4是根据本发明实施例的终呼处理方法的流程图二,如图4所示,该流程包括如下步骤:
步骤S402,应用服务器AS接收到呼叫请求;
步骤S404,AS向用于存储用户注册信息的第三方数据库TPUD查询呼叫请求中被叫用户对应的用户注册信息,其中,用户注册信息包括:注册用户,以及注册用户对应的服务呼叫会话控制功能S-CSCF;
步骤S406,AS接收到TPUD查询到被叫用户的用户注册信息;
步骤S408,AS依据接收到的用户注册信息将呼叫请求转发给S-CSCF执行终呼处理。
通过上述步骤,AS依据TPUD存储的第三方注册后的用户注册信息来执行用户终呼处理,不仅解决了相关技术中为第三方用户分配一个统一的S-CSCF进行呼叫处理性能上无法满足要求,并且由于用户的分散,采用统一的S-CSCF也无法实现的问题,进而达到了提高用户终呼效率的效果。
其中,AS接收到上述呼叫请求可以采用多种方式,例如,AS可以通过以下方式至少之一接收到呼叫请求:AS通过,查询呼叫会话控制功能I-CSCF通过将被叫用户当作公共服务标识PSI对待的方式把呼叫发送给AS,接收到呼叫请求;AS通过,查询呼叫会话控制功能I-CSCF将呼叫请求发送给TRF,由TRF通过业务触发的方式,接收到呼叫请求;AS通过,服务呼叫会话控制功能S-CSCF业务触发的方式,接收到呼叫请求。
图5是根据本发明实施例的终呼处理方法的流程图三,如图5所示,该流程包括如下步骤:
步骤S502,查询呼叫会话控制功能I-CSCF接收到呼叫请求;
步骤S504,I-CSCF依据呼叫请求,向用于存储第三方注册后的用户注册信息的第三方数据库TPUD查询呼叫请求中被叫用户的用户注册信息;其中,用户注册信息包括:注册用户,以及注册用户对应的服务呼叫会话控制功能S-CSCF;
步骤S506,I-CSCF接收到TPUD查询到的被叫用户的用户注册信息;
步骤S508,I-CSCF依据接收到的用户注册信息将呼叫请求转发给S-CSCF执行终呼处理。
通过上述步骤,查询呼叫会话控制功能I-CSCF依据TPUD存储的第三方注册后的用户注册信息来执行用户终呼处理,不仅解决了相关技术中为第三方用户分配一个统一的S-CSCF进行呼叫处理性能上无法满足要求,并且由于用户的分散,采用统一的S-CSCF也无法实现的问题,进而达到了提高用户终呼效率的效果。
I-CSCF依据呼叫请求,向用于存储第三方注册后的用户注册信息的TPUD查询用户的用户注册信息可以采用多种方式,例如,可以采用以下至少之一:I-CSCF直接从TPUD查询用户的用户注册信息;I-CSCF通过,将被叫用户的标识当作公共服务标识PSI对待的方式向应用服务器AS发送呼叫请求,由AS向TPUD查询用户注册信息后,接收到TPUD反馈的用户注册信息的方式,查询到用户注册信息;I-CSCF通过TRF业务触发的方式向AS发送呼叫请求,由AS向TPUD查询用户注册信息后,接收到TPUD反馈的用户注册信息反馈的方式,查询到用户注册信息。
在本实施例中还提供了一种终呼处理装置,该装置用于实现上述实施例及优选实施方式,已经进行过说明的不再赘述。如以下所使用的,术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现,但是硬件,或者软件和硬件的组合的实现也是可能并被构想的。
图6是根据本发明实施例的终呼处理装置一的结构框图,如图6所示,该装置应用于第三方数据库TPUD,包括:存储模块62、第一接收模块64和第一发送模块66,下面对该装置进行说明。
存储模块62,设置为存储第三方注册后的用户注册信息,其中,用户注册信息包括:注册用户,以及注册用户对应的服务呼叫会话控制功能S-CSCF;第一接收模块64,连接至上述存储模块62,设置为接收到用于查询被叫用户对应的用户注册信息的查询请求;第一发送模块66,连接至上述第一接收模块64,设置为依据查询请求将查询到的被叫用户对应的用户注册信息发送给发送查询请求的请求方,其中,用户注册信息用于请求方执行终呼处理。
其中,上述发送查询请求的请求方包括以下至少之一:应用服务器AS、查询呼叫会话控制功能I-CSCF、互联边界控制功能IBCF。
图7是根据本发明实施例的终呼处理装置二的结构框图,如图7所示,该装置应用于应用服务器AS,包括:第二接收模块72、第一查询模块74、第三接收模块76和第一处理模块78,下面对该装置进行说明。
第二接收模块72,设置为接收到呼叫请求;第一查询模块74,连接至上述第二接收模块72,设置为向用于存储用户注册信息的第三方数据库TPUD查询呼叫请求中被叫用户对应的用户注册信息,其中,用户注册信息包括:注册用户,以及注册用户对应的服务呼叫会话控制功能S-CSC;第三接收模块76,连接至上述第一查询模块74,设置为接收到TPUD查询到被叫用户的用户注册信息;第一处理模块78,连接至上述第三接收模块76,设置为依据接收到的用户注册信息将呼叫请求转发给S-CSCF执行终呼处理。
优选地,上述第二接收模块72,还设置为通过以下方式至少之一,接收到呼叫请求:AS通过,查询呼叫会话控制功能I-CSCF通过将被叫用户当作公共服务标识PSI对待的方式把呼叫发送给AS,接收到呼叫请求;AS通过,查询呼叫会话控制功能I-CSCF将呼叫请求发送给TRF,由TRF通过业务触发的方式,接收到用户呼叫请求;AS通过,服务呼叫会话控制功能S-CSCF业务触发的方式,接收到呼叫请求。
图8是根据本发明实施例的终呼处理装置三的结构框图,如图8所示,该装置应用于查询呼叫会话控制功能I-CSCF中,包括:第四接收模块82、第二查询模块84、第五接收模块86和第二处理模块88,下面对该装置进行说明。
第四接收模块82,设置为接收到呼叫请求;第二查询模块84,连接至上述第四接收模块82,设置为依据呼叫请求,向用于存储第三方注册后的用户注册信息的第三方数据库TPUD查询呼叫请求中被叫用户的用户注册信息;其中,用户注册信息包括:注册用户,以及注册用户对应的服务呼叫会话控制功能S-CSCF;第五接收模块86,连接至上述第二查询模块84,设置为接收到TPUD查询到被叫用户的用户注册信息;第二处理模块88,连接至上述第五接收模块86,设置为依据接收到的用户注册信息将呼叫请求转发给S-CSCF执行终呼处理。
优选地,上述第二查询模块84,还设置为通过以下方式至少之一查询到用户注册信息:直接从TPUD查询用户的用户注册信息;通过将被叫用户的标识当作公共服务标识PSI对待的方式向应用服务器AS发送呼叫请求,由AS向TPUD查询用户注册信息后,接收到TPUD反馈的用户注册信息的方式,查询到用户注册信息;通过TRF业务触发的方式向AS发送呼叫请求,由AS向TPUD查询用户注册信息后,接收到TPUD反馈的用户注册信息反馈的方式,查询到用户注册信息。
图9是根据本发明实施例的终呼处理系统的结构框图,如图9所示,终呼处理系统90,包括:上述任一项第三方数据库TPUD92、上述任一项的应用服务器AS94和上述任一项的查询呼叫会话控制功能I-CSCF96,其中,AS与TPUD的连接方式包括以下至少之一:AS与TPUD合设;AS与TPUD分设;TPUD与多个AS中的一个合设,TPUD与多个AS中除合设的AS之外的其它AS分设。
针对相关技术中的上述问题,在本实施例中提供了一种在IP多媒体子系统中一种IMS用户的终呼方案,使得IMS网络运营商能够向第三方业务提供更好的服务(例如,语音服务),极大的简化网络中用户数据的配置工作。
图10是根据本发明实施例的IMS用户的终呼架构的示意图,如图10所示,包括新的网元第三方数据库(The Third Party User Database,简称为TPUD),该数据库和AS相连,存储第三方用户的注册信息。终呼时,首先把呼叫路由到AS,AS查询TPUD,查询出用户的S-CSCF后,将呼叫转发给对应的S-CSCF。
需要说明的是,TPUD可以是AS的一部分,此时AS和TPUD之间的交互是内部过程;也可以是一个独立的实体;下面分别说明。
图11-1是根据本发明实施例的IMS用户的终呼架构的TPUD部署图一,如图11-1所示,此时AS和TPUD合设,网络中只有一个这样的网元。此场景适用于用户数量较少的场景。
图11-2是根据本发明实施例的IMS用户的终呼架构的TPUD部署图二,如图11-2所示,TPUD独立设置,多个同类AS均可以访问TPUD,此时AS之间能够负载均衡,能处理数量很大的用户。
图11-3是根据本发明实施例的IMS用户的终呼架构的TPUD部署图三,如图11-3所示,有多个同类AS,但是其中一个内涵了TPUD,其他AS均需要和该AS内的TPUD交互。
无论采用上述何种方式,都是相关技术对于图10架构的实现方式之一。
下面对本发明优选实施方式进行说明。
图12是根据本发明优选实施方式的直观的终呼流程图一,如图12所示,该流程包括如下步骤:
步骤501:呼叫请求到达UE归属IMS网络的I-CSCF/IBCF;
步骤1202:I-CSCF/IBCF收到呼叫请求后,向TPUD发起位置查询;TPUD收到查询请求后,查询该用户的注册状态。如果未查到注册信息,TPUD会返回未查询到,则I-CSCF如图2所示的背景技术一样,继续从步骤202开始执行。如果查到注册信息,则返回用户注册的S-CSCF;
步骤1203:I-CSCF根据收到的S-CSCF,向S-CSCF发送呼叫请求;
步骤1204:S-CSCF收到呼叫请求后,执行被叫相关的业务;
步骤1205:S-CSCF向P-CSCF转发呼叫请求;
步骤1206:P-CSCF向UE转发呼叫请求;
步骤1207:呼叫请求最终到达UE后,按现有技术完成呼叫的建立。
需要说明的是,本优选实施方式属于一种最为直观的实现方式,然而这要求I-CSCF能支持这个功能。优选地,可以在I-CSCF上进行相应配置,通过配置可以识别出哪些被叫用户是上述需要特殊处理的第三方用户。如果是普通用户,I-CSCF不再查询TPUD,而是执行现有流程。另外,在不对I-CSCF升级时,也可以执行上述IMS用户的终呼。
图13是根据本发明优选实施方式的终呼流程图二,如图13所示,该流程包括如下步骤:
步骤601:呼叫请求到达UE归属IMS网络的I-CSCF/IBCF;
步骤1302:可选的,I-CSCF/IBCF收到呼叫请求后,可以向HSS查询,HSS返回的是AS地址;
步骤1303:如果I-CSCF不执行步骤1302,则I-CSCF本地配置,将本专利的需要特殊处理的第三方用户的IMPU,当做(Public Service Identity,PSI)对待。PSI是一类特殊的SIP URI,其宿主为AS。无论I-CSCF从HSS查询到AS地址,还是将IMPU当做PSI处理,该SIP URI都指向某个AS。I-CSCF将呼叫发送给AS;
步骤1304:AS收到呼叫请求后,向TPUD查询,获得用户当前S-CSCF地址;
步骤1305:AS将呼叫请求后转发给对应的S-CSCF;
步骤1306:S-CSCF收到呼叫请求后,执行被叫相关的业务;
步骤1307:S-CSCF向P-CSCF转发呼叫请求;
步骤1308:P-CSCF向UE转发呼叫请求;
步骤1309:呼叫请求最终到达UE后,按现有技术完成呼叫的建立。
图14是根据本发明优选实施例的终呼流程图三,如图14所示,该流程包括如下步骤:
步骤1401:呼叫请求到达UE归属IMS网络的I-CSCF/IBCF;
步骤1402:可选的,I-CSCF/IBCF收到呼叫请求后,可以向HSS查询,HSS返回的是(Transit function,简称为TRF)地址;
步骤1403:如果I-CSCF不执行步骤1402,则I-CSCF本地配置,收到本专利的需要特殊处理的第三方用户的IMPU时,认为本网络是IMS中继网络,此时,需要将呼叫发给本网络的TRF。无论I-CSCF从HSS查询,还是将本网络当做中继网络,该SIP URI都指向TRF。I-CSCF将呼叫发送给TRF;
步骤1404:TRF收到呼叫请求后,执行业务触发。TRF的业务触发,类似由于S-CSCF的业务触发机制。只是TRF不需要从HSS下载每个用户的业务数据(如iFC),TRF上配置了iFC,这是基于某一类用户的iFC,或者是基于某个网络的iFC;
步骤1405:TRF根据本地的iFC,将呼叫发送给AS;
步骤1406:AS收到呼叫请求后,向TPUD查询,获得用户当前S-CSCF地址;
步骤1407:AS将呼叫请求后转发给对应的S-CSCF;
步骤1408:S-CSCF收到呼叫请求后,执行被叫相关的业务;
步骤1409:S-CSCF向P-CSCF转发呼叫请求;
步骤1410:P-CSCF向UE转发呼叫请求;
步骤1411:呼叫请求最终到达UE后,按现有技术完成呼叫的建立。
图15是根据本发明优选实施方式的终呼流程图四,如图15所示,该流程包括如下步骤:
步骤1501:呼叫请求到达UE归属IMS网络的I-CSCF/IBCF;
步骤1502:I-CSCF/IBCF收到呼叫请求后,向HSS查询。由于HSS没有该用户的注册信息,所以没有查到。按照现有技术,HSS返回一个S-CSCF的列表;
步骤1503:I-CSCF选择一个S-CSCF,将呼叫发送给该S-CSCF;
步骤1504:S-CSCF收到呼叫请求后,S-CSCF从HSS获取用户签约数据,执行业务触发;
步骤1505:S-CSCF根据签约中的iFC,将呼叫路由发送至AS;
步骤1506:AS收到呼叫请求后,向TPUD查询,获得用户当前S-CSCF地址;
步骤1507:AS将呼叫请求后转发给对应的S-CSCF;
步骤1508:S-CSCF收到呼叫请求后,执行被叫相关的业务;
步骤1509:S-CSCF向P-CSCF转发呼叫请求;
步骤1510:P-CSCF向UE转发呼叫请求;
步骤1511:呼叫请求最终到达UE后,按现有技术完成呼叫的建立。
显然,本领域的技术人员应该明白,上述的本发明的各模块或各步骤可以用通用的计算装置来实现,它们可以集中在单个的计算装置上,或者分布在多个计算装置所组成的网络上,可选地,它们可以用计算装置可执行的程序代码来实现,从而,可以将它们存储在存储装置中由计算装置来执行,并且在某些情况下,可以以不同于此处的顺序执行所示出或描述的步骤,或者将它们分别制作成各个集成电路模块,或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样,本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已,并不用于限制本发明,对于本领域的技术人员来说,本发明可以有各种更改和变化。凡在本发明的精神和原则之内,所作的任何修改、等同替换、改进等,均应包含在本发明的保护范围之内。
工业实用性
如上所述,通过上述实施例及优选实施方式,解决了相关技术中为第三方注册的用户分配一个统一的S-CSCF进行呼叫处理性能上无法满足要求,并且由于用户的分散,采用统一的S-CSCF也无法实现的问题,进而达到了提高用户终呼效率的效果。

Claims (13)

  1. 一种终呼处理方法,包括:
    第三方数据库TPUD存储第三方注册后的用户注册信息,其中,所述用户注册信息包括:注册用户,以及所述注册用户对应的服务呼叫会话控制功能S-CSCF;
    所述TPUD接收到用于查询被叫用户对应的用户注册信息的查询请求;
    所述TPUD依据所述查询请求将查询到的所述被叫用户对应的用户注册信息发送给发送所述查询请求的请求方,其中,所述用户注册信息用于所述请求方执行终呼处理。
  2. 根据权利要求1所述的方法,其中,发送所述查询请求的所述请求方包括以下至少之一:
    应用服务器AS、查询呼叫会话控制功能I-CSCF、互联边界控制功能IBCF。
  3. 一种终呼处理方法,包括:
    应用服务器AS接收到呼叫请求;
    所述AS向用于存储用户注册信息的第三方数据库TPUD查询所述呼叫请求中被叫用户对应的用户注册信息,其中,所述用户注册信息包括:注册用户,以及所述注册用户对应的服务呼叫会话控制功能S-CSCF;
    所述AS接收到所述TPUD查询到所述被叫用户的所述用户注册信息;
    所述AS依据接收到的所述用户注册信息将所述呼叫请求转发给所述S-CSCF执行终呼处理。
  4. 根据权利要求3所述的方法,其中,所述AS通过以下方式至少之一接收到所述呼叫请求:
    所述AS通过,查询呼叫会话控制功能I-CSCF通过将所述被叫用户当作公共服务标识PSI对待的方式把呼叫发送给所述AS,接收到所述呼叫请求;
    所述AS通过,查询呼叫会话控制功能I-CSCF将所述呼叫请求发送给TRF,由所述TRF通过业务触发的方式,接收到所述呼叫请求;
    所述AS通过,服务呼叫会话控制功能S-CSCF业务触发的方式,接收到所述呼叫请求。
  5. 一种终呼处理方法,包括:
    查询呼叫会话控制功能I-CSCF接收到呼叫请求;
    所述I-CSCF依据所述呼叫请求,向用于存储第三方注册后的用户注册信息的第三方数据库TPUD查询所述呼叫请求中被叫用户的用户注册信息;其中,所述用户注册信息包括:注册用户,以及所述注册用户对应的服务呼叫会话控制功能S-CSCF;
    所述I-CSCF接收到所述TPUD查询到的所述被叫用户的用户注册信息;
    所述I-CSCF依据接收到的所述用户注册信息将所述呼叫请求转发给所述S-CSCF执行终呼处理。
  6. 根据权利要求5所述的方法,其中,所述I-CSCF依据所述呼叫请求,向用于存储第三方注册后的用户注册信息的所述TPUD查询用户的用户注册信息包括以下至少之一:
    所述I-CSCF直接从所述TPUD查询用户的所述用户注册信息;
    所述I-CSCF通过,将所述被叫用户的标识当作公共服务标识PSI对待的方式向应用服务器AS发送所述呼叫请求,由所述AS向所述TPUD查询所述用户注册信息后,接收到所述TPUD反馈的所述用户注册信息的方式,查询到所述用户注册信息;
    所述I-CSCF通过TRF业务触发的方式向所述AS发送所述呼叫请求,由所述AS向所述TPUD查询所述用户注册信息后,接收到所述TPUD反馈的所述用户注册信息反馈的方式,查询到所述用户注册信息。
  7. 一种终呼处理装置,应用于第三方数据库TPUD,包括:
    存储模块,设置为存储第三方注册后的用户注册信息,其中,所述用户注册信息包括:注册用户,以及所述注册用户对应的服务呼叫会话控制功能S-CSCF;
    第一接收模块,设置为接收到用于查询被叫用户对应的用户注册信息的查询请求;
    第一发送模块,依据所述查询请求将查询到的所述被叫用户对应的用户注册信息发送给发送所述查询请求的请求方,其中,所述用户注册信息用于所述请求方执行终呼处理。
  8. 根据权利要求7所述的装置,其中,发送所述查询请求的所述请求方包括以下至少之一:
    应用服务器AS、查询呼叫会话控制功能I-CSCF、互联边界控制功能IBCF。
  9. 一种终呼处理装置,应用于应用服务器AS,包括:
    第二接收模块,设置为接收到呼叫请求;
    第一查询模块,设置为向用于存储用户注册信息的第三方数据库TPUD查询所述呼叫请求中被叫用户对应的用户注册信息,其中,所述用户注册信息包括:注册用户,以及所述注册用户对应的服务呼叫会话控制功能S-CSC;
    第三接收模块,设置为接收到所述TPUD查询到所述被叫用户的所述用户注册信息;
    第一处理模块,设置为依据接收到的所述用户注册信息将所述呼叫请求转发给所述S-CSCF执行终呼处理。
  10. 根据权利要求9所述的装置,其中,所述第二接收模块,还设置为通过以下方式至少之一,接收到所述呼叫请求:
    所述AS通过,查询呼叫会话控制功能I-CSCF通过将所述被叫用户当作公共服务标识PSI对待的方式把呼叫发送给所述AS,接收到所述呼叫请求;
    所述AS通过,查询呼叫会话控制功能I-CSCF将所述呼叫请求发送给TRF,由所述TRF通过业务触发的方式,接收到所述用户呼叫请求;
    所述AS通过,服务呼叫会话控制功能S-CSCF业务触发的方式,接收到所述呼叫请求。
  11. 一种终呼处理装置,应用于查询呼叫会话控制功能I-CSCF中,包括:
    第四接收模块,设置为接收到呼叫请求;
    第二查询模块,设置为依据所述呼叫请求,向用于存储第三方注册后的用户注册信息的第三方数据库TPUD查询所述呼叫请求中被叫用户的用户注册信息;其中,所述用户注册信息包括:注册用户,以及所述注册用户对应的服务呼叫会话控制功能S-CSCF;
    第五接收模块,设置为接收到所述TPUD查询到所述被叫用户的所述用户注册信息;
    第二处理模块,设置为依据接收到的所述用户注册信息将所述呼叫请求转发给所述S-CSCF执行终呼处理。
  12. 根据权利要求11所述的装置,其中,所述第二查询模块,还设置为通过以下方式至少之一查询到所述用户注册信息:
    直接从所述TPUD查询用户的所述用户注册信息;
    通过将所述被叫用户的标识当作公共服务标识PSI对待的方式向应用服务器AS发送所述呼叫请求,由所述AS向所述TPUD查询所述用户注册信息后,接收到所述TPUD反馈的所述用户注册信息的方式,查询到所述用户注册信息;
    通过TRF业务触发的方式向所述AS发送所述呼叫请求,由所述AS向所述TPUD查询所述用户注册信息后,接收到所述TPUD反馈的所述用户注册信息反馈的方式,查询到所述用户注册信息。
  13. 一种终呼处理系统,包括:权利要求7至8中任一项所述第三方数据库TPUD、权利要求9至10中任一项所述的应用服务器AS和权利要求11至12中任一项所述的查询呼叫会话控制功能I-CSCF,其中,所述AS与所述TPUD的连接方式包括以下至少之一:
    所述AS与所述TPUD合设;所述AS与所述TPUD分设;所述TPUD与多个AS中的一个合设,所述TPUD与所述多个AS中除合设的AS之外的其它AS分设。
PCT/CN2015/073805 2014-09-30 2015-03-06 终呼处理方法、装置及系统 WO2016050033A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410526580.8A CN105450621A (zh) 2014-09-30 2014-09-30 终呼处理方法、装置及系统
CN201410526580.8 2014-09-30

Publications (1)

Publication Number Publication Date
WO2016050033A1 true WO2016050033A1 (zh) 2016-04-07

Family

ID=55560400

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/073805 WO2016050033A1 (zh) 2014-09-30 2015-03-06 终呼处理方法、装置及系统

Country Status (2)

Country Link
CN (1) CN105450621A (zh)
WO (1) WO2016050033A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115499415B (zh) * 2022-11-17 2023-03-28 中兴通讯股份有限公司 一种呼叫请求处理方法、网络节点及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1968138A (zh) * 2006-06-07 2007-05-23 华为技术有限公司 Ims网络用户注册信息的管理方法和装置
WO2008101838A2 (en) * 2007-02-22 2008-08-28 Telefonaktiebolaget Lm Ericsson (Publ) Group access to ip multimedia subsystem service
CN102265565A (zh) * 2008-12-26 2011-11-30 爱立信电话股份有限公司 用于企业网络接入点确定的方法和系统
CN102273238A (zh) * 2008-12-31 2011-12-07 北方电讯网络有限公司 创建订户装置的全局唯一标识符
CN102577281A (zh) * 2011-12-30 2012-07-11 华为技术有限公司 Ip pbx的呼叫路由方法及设备

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100395976C (zh) * 2005-07-05 2008-06-18 华为技术有限公司 一种因特网协议多媒体子系统的鉴权方法
CN101001145B (zh) * 2006-01-11 2011-04-20 华为技术有限公司 支持非ip多媒体业务子系统终端漫游的认证方法
CN101212323B (zh) * 2006-12-25 2010-08-25 华为技术有限公司 Ims网络为群用户提供服务的方法和系统
US20130315138A1 (en) * 2012-05-23 2013-11-28 Nokia Siemens Networks Oy Configurable services in internet protocol (ip)-based multimedia subsystem (ims)

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1968138A (zh) * 2006-06-07 2007-05-23 华为技术有限公司 Ims网络用户注册信息的管理方法和装置
WO2008101838A2 (en) * 2007-02-22 2008-08-28 Telefonaktiebolaget Lm Ericsson (Publ) Group access to ip multimedia subsystem service
CN102265565A (zh) * 2008-12-26 2011-11-30 爱立信电话股份有限公司 用于企业网络接入点确定的方法和系统
CN102273238A (zh) * 2008-12-31 2011-12-07 北方电讯网络有限公司 创建订户装置的全局唯一标识符
CN102577281A (zh) * 2011-12-30 2012-07-11 华为技术有限公司 Ip pbx的呼叫路由方法及设备

Also Published As

Publication number Publication date
CN105450621A (zh) 2016-03-30

Similar Documents

Publication Publication Date Title
JP4856179B2 (ja) Imsにおけるアプリケーションサーバの割当方法および装置
US10893109B2 (en) Method, device, network entity and computer program product for providing an IP service application
EP2371154B1 (en) Creating a globally unique indentifier of a subscriber device
US7715370B2 (en) Method and system for subscribing a user to a service
CN100551146C (zh) 一种实现用户身份关联的方法、系统及装置
KR100755984B1 (ko) 이동 통신 시스템에서의 가입자의 복수 등록
US8457046B2 (en) Method for multiple registration of a multimodal communication terminal
CN101326493B (zh) 用于多处理器服务器中的负载分配的方法和装置
JP2006522501A5 (zh)
US8600031B2 (en) Method for connecting calls between an IP multimedia subsystem (IMS) domain and a circuit switched (CS) domain
US9609059B2 (en) Synchronization of shared identifiers across servers in an IMS network
CN102148739B (zh) 一种ims会话路由控制方法及系统
CN100512495C (zh) 一种实现被叫服务的方法和系统
US9160708B2 (en) Methods and apparatuses for handling public identities in an internet protocol multimedia subsystem network
US20150117423A1 (en) Call routing for ip multimedia subsystem users
US8649496B2 (en) Call classification and forwarding
WO2016050033A1 (zh) 终呼处理方法、装置及系统
JP5467138B2 (ja) Ipマルチメディア・サブシステム・サービスへのグループ・アクセス
WO2016050032A1 (zh) 用户注册处理方法、装置及系统
KR101075614B1 (ko) 아이피 기반 멀티미디어 서브시스템에서 가입자 정보유실시 착신호를 가능하게 하는 방법
US20130212284A1 (en) Method and apparatus for maintaining information about subscription servers
CN1941774B (zh) 在网络中实现公共用户标识携带的方法及系统
Lundqvist et al. Service program mobility—Dynamic service roaming
CN105049230A (zh) 一种基于域名系统的分布式多媒体子系统的车辆容灾方法及其车辆容灾系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15846578

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15846578

Country of ref document: EP

Kind code of ref document: A1