WO2009092255A1 - 一种为ims用户提供智能业务的方法、系统和装置 - Google Patents

一种为ims用户提供智能业务的方法、系统和装置 Download PDF

Info

Publication number
WO2009092255A1
WO2009092255A1 PCT/CN2008/073658 CN2008073658W WO2009092255A1 WO 2009092255 A1 WO2009092255 A1 WO 2009092255A1 CN 2008073658 W CN2008073658 W CN 2008073658W WO 2009092255 A1 WO2009092255 A1 WO 2009092255A1
Authority
WO
WIPO (PCT)
Prior art keywords
call request
user
called
ims
entity
Prior art date
Application number
PCT/CN2008/073658
Other languages
English (en)
French (fr)
Inventor
Kai Wen
Nengwu Yang
Original Assignee
Huawei Technologies Co., Ltd.
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 Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2009092255A1 publication Critical patent/WO2009092255A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment

Definitions

  • the present invention relates to the field of mobile communication technologies, and in particular, to a method, system and apparatus for providing intelligent services for IMS users. Background technique
  • IMS IP Multimedia Subsystem, IP Multimedia Subsystem
  • 3GPP Third Generation Partnership Project
  • IMS Under the leadership of Next Generation Network, IMS should support both fixed and mobile access.
  • the terminal and access network are various, and the core network has only one IMS. Its core feature is SIP.
  • IMS IP-based, service-open, access-independent network environment that provides user identity authentication, QoS (Quality of Service) assurance, security assurance, and NAT (Network Address Translator) at the core network layer. , network address translation) traversal and other basic capabilities, to provide a strong support for various businesses.
  • the IMS provides a form of service, generally introducing an AS (Application Server), and each AS can host one or more services. The processes of each service may be very different, and the usages are different. Many services also need to introduce corresponding client software on the User Equipment (User Terminal) to provide specific services to the user, such as PoC. (Push to Talk Over Cellular) service, the PoC server (PoC server) needs to be deployed on the network side, and the PoC client (PoC client) needs to be deployed on the terminal side.
  • PoC Push to Talk Over Cellular
  • the PSTN (Public Switched Telephone Network) side has realized network intelligence, and the intelligent services of end-office users are concentrated on the tandem office.
  • the intelligent service of all users is subscribed to the SHLR (Smart Home Location Register), and all the user's office calls are moved up to the tandem office.
  • the gateway obtains the prefix corresponding to the user's subscription smart service by querying the SHLR. And insert the smart service prefix in front of the called number in the order of the service, and trigger the corresponding intelligent service. After the smart service is triggered, the callee is finally connected according to the called number.
  • IMS The advantage of IMS is that it is easy to provide rich multimedia services, at the same time, it needs to be considered.
  • New IMS networks need to have inheritance to existing PSTN services.
  • the telephone service AS the IMS network can provide the telephone supplementary service of the existing PSTN/PLMN (Public Land Mobile Network).
  • an IMS-SSF IMS Service Switching Function
  • IMS-SSF IMS Service Switching Function
  • IMS-SSF has a large amount of development work. It may not be supported in the early deployment of IMS. It is necessary to consider the method of providing IMS users with live network intelligent services without IMS-SSF entities in the networking. There is no such solution yet.
  • the new IMS network needs to have the inheritance requirement for the existing network number. Take Figure 3 as an example to illustrate the need to inherit the existing network number.
  • the original two PSTN phones in the user's home are placed in the living room and the study room.
  • the PSTN phone in the living room is replaced with a SIP phone (access to the IMS network).
  • the user wants the SIP phone to still use the original one.
  • a method for allocating a telephone number to a user of an IMS network As shown in FIG. 1, a schematic diagram of an independent number resource is used for an IMS network.
  • an operator separately allocates a number resource for a newly created IMS network.
  • the IMS network subscriber number uses a separate number segment. For example, the current network has a number segment beginning with "876" that is not used. This segment is assigned to the IMS network.
  • the original gateway adds routing data to the IMS network according to the called "876". In this way, the IMS user's number is independent of the original PSTN number number segment resources.
  • the inventors have found that the prior art has at least the following problems: the prior art needs to develop an IMS-SSF for providing intelligent services for IMS users, but the development workload of the IMS-SSF is large, and the network is complex. Moreover, the early deployment of IMS may not support this function. It is necessary to consider the method of providing the IMS user with the existing network intelligent service without the IMS-SSF entity in the networking, but there is no such solution at present. Summary of the invention
  • the embodiments of the present invention provide a method, a system, and a device for providing an IMS user with an intelligent service, so that an IMS user can be provided with an existing network intelligent service without an IMS-SSF entity in the networking. Further, in the embodiment of the present invention, the IMS newly added user can inherit the use of the existing network number, so that the newly added IMS user can make a call on the basis of inheriting the existing network number resource, and does not bring data maintenance difficulty to the existing network device. problem.
  • An embodiment of the present invention provides a method for providing an IMS user with an intelligent service, which specifically includes: receiving a call request; and identifying an IMS user in the call request and the signed intelligent service information and a database, a service control point SCP Interacting to provide intelligent service for the IMS user; routing the call request according to the called number in the call request.
  • the embodiment of the present invention further provides a system for providing an intelligent service to an IMS user, including: a first CSCF entity, a number change AS entity, and a first softswitch entity, where the first CSCF entity is used to a call request is triggered to the AS entity, and the call request is routed to the first softswitch entity according to the indication of the AS entity; the AS entity is configured to be in the call request according to configuration data.
  • a system for providing an intelligent service to an IMS user including: a first CSCF entity, a number change AS entity, and a first softswitch entity, where the first CSCF entity is used to a call request is triggered to the AS entity, and the call request is routed to the first softswitch entity according to the indication of the AS entity; the AS entity is configured to be in the call request according to configuration data.
  • the first softswitch entity configured to receive a call request sent by the first CSCF entity, and delete a prefix of the called number in the call request, according to the call request.
  • the IMS user's identity and its subscribed intelligent service information interact with the database and the SCP to provide the IMS user with intelligent services, and route the call request according to the called number in the call request.
  • the embodiment of the present invention further provides another system for providing an IMS user with an intelligent service, including: a second softswitch entity and a second CSCF entity, where the second softswitch entity is configured to receive a call request, And interacting with the database and the SCP according to the identifier of the IMS user in the call request and the signed intelligent service information, providing the IMS user with an intelligent service, and routing the call request according to the called number in the call request.
  • the second CSCF entity is configured to receive a call request sent by the second softswitch entity, and continue the call request.
  • the embodiment of the present invention further provides a first softswitch entity, including: a first receiving module, configured to receive a call request sent by a first CSCF entity; and a prefix deletion module, configured to delete the first receiving a prefix of the called number in the call request received by the module; the first triggering module, configured to interact with the database and the SCP according to the identifier of the IMS user in the call request and the signed intelligent service information, where the IMS user is Providing an intelligent service; a first sending module, configured to route the call request according to the indication of the first triggering module and the called number in the call request.
  • a first receiving module configured to receive a call request sent by a first CSCF entity
  • a prefix deletion module configured to delete the first receiving a prefix of the called number in the call request received by the module
  • the first triggering module configured to interact with the database and the SCP according to the identifier of the IMS user in the call request and the signed intelligent service information, where the IMS user is Providing
  • the embodiment of the present invention further provides a second softswitch entity, including: a second receiving module, configured to receive a call request, and a second triggering module, configured to receive, according to the call request received by the second receiving module
  • the identifier of the IMS user and the signed intelligent service information interact with the database and the SCP to provide the IMS user with the intelligent service;
  • the second sending module is configured to use the indication of the second trigger module and the call request The called number in the route routes the call request.
  • the embodiment of the present invention further provides a first CSCF entity, including: a triggering module, configured to trigger a call request to an AS entity; and a sending module, configured to send the call request according to the indication of the AS entity Route to the first softswitch.
  • a second CSCF entity including: a receiving module, configured to receive a call request sent by a second softswitch entity; and a connection module, configured to connect to the call request received by the receiving module .
  • the embodiment of the present invention further provides a number change AS entity, including: a configuration data module, configured to record a routing number of a first softswitch entity that provides an intelligent service for an IMS user; and a call receiving module, configured to receive a call requesting module, configured to determine, according to the call request received by the call receiving module, whether the currently served IMS user is a called user or a called user; a number conversion module, configured to determine a result according to the call determining module And the IMS user is configured to record the data module, convert the called number in the call request, and insert a routing number as a prefix before the called number.
  • a configuration data module configured to record a routing number of a first softswitch entity that provides an intelligent service for an IMS user
  • a call receiving module configured to receive a call requesting module, configured to determine, according to the call request received by the call receiving module, whether the currently served IMS user is a called user or a called user
  • a number conversion module configured to determine a result
  • the technical solution of the embodiment of the present invention has the following advantages:
  • the softswitch is used to provide the IMS user with the live network intelligent service, which saves the cost of developing the IMS-SSF entity and improves the cost.
  • the utilization of the softswitch, and the embodiment of the present invention enables the IMS user to inherit the existing network number, so that the newly added IMS user can make a call on the basis of inheriting the existing network number resource, and does not bring data maintenance to the existing network device. Difficult problem. DRAWINGS
  • FIG. 1 is a schematic diagram of a IMS network using an independent number resource
  • FIG. 2 is a network architecture diagram of an IMS user using a PSTN side calling smart service according to an embodiment of the present invention
  • FIG. 4 is a flowchart of an IMS user using an existing network softswitch called smart service according to an embodiment of the present invention
  • FIG. 5 is a schematic structural diagram of an IMS user using an existing network softswitch called intelligent service according to an embodiment of the present invention
  • FIG. 6 is a schematic diagram of another architecture of an IMS user using a PSTN side called smart service according to an embodiment of the present invention
  • FIG. 7 is a flowchart of a called smart service of an IMS user using an existing network soft switch according to an embodiment of the present invention
  • FIG. 8 is a flowchart of registering an IMS user terminal according to an embodiment of the present invention.
  • FIG. 9 is a flowchart of a scenario for simultaneously using multiple services of an IMS user according to an embodiment of the present invention.
  • FIG. 10 is a schematic diagram of a scenario architecture for simultaneously using multiple services of an IMS user according to an embodiment of the present invention.
  • FIG. 11 is a structural diagram of a system for providing an intelligent service to an IMS user according to an embodiment of the present invention.
  • FIG. 12 is a schematic structural diagram of another system for providing an intelligent service to an IMS user according to an embodiment of the present invention. detailed description
  • the network architecture diagram of the IMS is introduced on the PSTN network in the embodiment of the present invention.
  • the left side of the architecture is the PSTN existing network architecture, and the terminal belongs to the softswitch (or the switch under the soft switch), and the PSTN intelligent service is composed of The SCP (Service Control Point) provides the intelligent service subscription of each user on the SHLR.
  • SCP Service Control Point
  • On the right side of the architecture is the architecture of the new IMS network.
  • the IMS network service is provided by the SIP AS, and the service is contracted on the HSS (Home Subscriber Server).
  • the softswitch interfaces with the IMS network through the SIP trunk. Because the 3GPP IMS specification extends the SIP protocol, the existing network softswitch usually does not support these extensions.
  • the new IMS network needs to be adapted to the SIP specification supported by the existing network softswitch.
  • the S-CSCF in the IMS network has the ability to directly interwork with the softswitch of the existing network
  • the S-CSCF Serving CSCF
  • the interworking boundary control function unit completes the softswitch SIP Profile and IMS SIP Conversion between profiles.
  • the manner in which the S-CSCF directly communicates with the softswitch is taken as an example.
  • the CSCF represents the S-CSCF unless otherwise specified.
  • the IMS network is deployed by the operator.
  • the number of resources of the newly deployed IMS domain is "876", and the number of resources of the original softswitch domain is "976".
  • the IMS user While enjoying the multimedia service, the IMS user also wants to use the traditional intelligent service.
  • the traditional intelligent service is provided to the IMS user by the softswitch domain by routing the call to the softswitch domain.
  • an IMS user uses a PSTN side calling intelligent service flow chart, such as a calling prepaid service, according to an embodiment of the present invention.
  • the SIP terminal D in FIG. 2 is used as an example to describe the calling prepaid service flow of the IMS calling terminal D using the softswitch, which specifically includes the following steps:
  • Step S301 the calling terminal D initiates a session request to the called terminal C at the IMS.
  • Step S302 the CSCF receives the call request of the calling terminal D, triggers the number change AS according to the subscription data signed on the calling number, and routes the call request to the number change AS.
  • Step S303 The number change AS inserts the routing number of the softswitch before the called number, and sends the converted called number to the CSCF.
  • Step S304 the CSCF routes the call request to the softswitch according to the converted called number.
  • Step S305 The softswitch configures the routing number before the called number according to the trunk group data, and queries the SHLR for the smart service information signed on the calling number according to the calling number.
  • Step S306 the SHLR returns the smart service information signed on the calling number to the softswitch.
  • Step S307 the softswitch triggers the calling smart service to the SCP.
  • the softswitch inserts the smart prefix corresponding to the smart service in front of the called number according to the intelligent service information signed by the SHLR, and routes the call to the SCP to trigger the corresponding intelligent service.
  • the softswitch triggers the call to complete the service on the SCP.
  • Step S308, the softswitch routes the call to the CSCF.
  • the softswitch continues to query whether the called number of the call is subscribed to the smart service. In this example, the called number does not sign the smart service, so the soft switch routes the call to the IMS domain according to the called number.
  • CSCF the softswitch triggers the calling smart service to the SCP.
  • Step S309 the CSCF performs the called process, and connects the called terminal C according to the called number.
  • Step S310 the called terminal C responds to the call, and the 180 response returns to the calling terminal D along the INVITE path.
  • the IMS user uses the smart service provided by the softswitch to perform corresponding configuration on the user subscription data, and the CSDC triggers the softswitch intelligent service by triggering the number change service first. Then, according to the converted called number, the method of routing the call to the softswitch is implemented.
  • the S-CSCF In order to trigger the calling intelligent service for the user of the IMS domain, and sign a calling service for the corresponding user number (for example, the service is called "softswitch intelligent service"), when the calling service is triggered, the S-CSCF The INVITE request is routed to the number change AS, which is responsible for inserting a route prefix (for example, 127) before the called number, and then routing the INVITE request back to the S-CSCF, and the S-CSCF according to the prefix of the converted number 127 Route the call request INVITE to the softswitch.
  • the IMS multimedia service needs to be triggered first through reasonable subscription data configuration.
  • the number change AS changes the called number, and the subsequent CSCF processes. All are directed to the processing of the called party. If the softswitch intelligent service is triggered first, the multimedia service that is ranked next will have no chance to be triggered.
  • FIG. 4 it is a flowchart of an IMS user using an existing network softswitch called intelligent service according to an embodiment of the present invention, for example, a called simultaneous vibration service.
  • terminal B and terminal C belong to the same user.
  • SIP terminal D dials SIP terminal C number 876001, called terminal C.
  • the service trigger data needs to be configured for the calling user, and the call number is converted by the number change AS to route the call to the softswitch.
  • the S-CSCF in order to trigger the called intelligent service to the user 876001 of the IMS domain, it is required to sign the called service for 876001.
  • the service for example, the service is called "softswitch intelligent service"
  • the S-CSCF routes the INVITE request to the number change AS, and the AS is responsible for inserting a route prefix before the called number ( For example, 127), the INVITE request is then routed back to the S-CSCF, and the S-CSCF can route the call request INVITE to the softswitch according to the prefix 127 of the transformed number.
  • the following steps are included:
  • Step S401 after completing the processing on the calling side, the calling side routes the call to the CSCF according to the called number 876001.
  • the calling user can be an IMS domain user such as terminal D or a softswitch domain user.
  • the calling side processing flow is omitted here.
  • Step S402 the CSCF receives the call request, and the CSCF routes the call request INVITE to the number change AS according to the subscription data signed by the called number.
  • Step S403 The number change AS inserts the routing number 127 of the PSTN before the called number, and sends the converted called number to the CSCF.
  • Step S404 the CSCF routes the call to the softswitch according to the routing number 127.
  • Step S405 The softswitch configures the routing number before the called number according to the configuration of the relay data, and first processes the calling intelligent service (in this example, there is no calling intelligent service) to process the called intelligent service.
  • the softswitch queries the SHLR to query the smart service information signed on the called number.
  • Step S406 The SHLR returns the smart service information signed on the called number to the softswitch.
  • step S407 the softswitch inserts the smart prefix corresponding to the smart service in front of the called number according to the subscribed different smart service information, and triggers the call to the corresponding smart service on the SCP.
  • the SCP is configured with the correspondence between the logical number 876001 and the physical number 126876001 and the PSTN terminal B number 976002.
  • Step S408 The SCP sends a new session request to the physical numbers of the POTS terminal B and the SIP terminal C, respectively.
  • the softswitch is routed to the IMS according to the physical number, and the CSCF performs the called party processing. Since the physical number does not sign the "softswitch intelligent service", the number change AS is not triggered again.
  • Step S409 the CSCF routes the call request to the called party according to the physical number.
  • SIP terminal c the CSCF routes the call request to the called party according to the physical number.
  • Step S410 the called party responds to the call, and the 180 response returns to the calling terminal D along the INVITE path.
  • the IMS network assigns the number 876001 to the SIP terminal C, which is called a logical number. It is recommended to allocate another number to the terminal C, which is called a physical number, such as 126876001. If you do not assign a physical number, the following problems occur.
  • the CSCF routes the call to the softswitch to trigger the called intelligent service. After the called intelligent service is processed, the softswitch makes the called route, and the called number 876001 belongs to the IMS domain, and the softswitch The call is routed back to the IMS domain.
  • the IMS domain CSCF receives the INVITE, and performs the called process according to the called number 876001. According to the 876001 service subscription data, it continues to trigger the number change AS and inserts the routing number before the called number to route the call. Go back to the PSTN side and get into the loop. Unless the softswitch adds a signaling indication to the call back to the IMS domain, this requires the existing network softswitch to be modified. Therefore, in the case that the existing network softswitch is not modified, it is recommended to assign a physical number to the IMS domain terminal C. After completing the called intelligent service processing, the softswitch changes the called number to a physical number, and routes the call back to the IMS according to the physical number. .
  • the called service subscription data of the logical number can also sign the IMS multimedia service before the "softswitch intelligent service”, and can also sign the IMS multimedia service based on the physical number.
  • Another IMS user uses the PSTN side called intelligent service scenario, and the number change AS is not needed in this scenario.
  • the user's phone number is 976002.
  • the original two PSTN phones in the home are placed in the living room and the study room.
  • the user replaces the PSTN phone in the living room with a SIP phone (access to the IMS network). )
  • the user wants the SIP phone to still use the previously existing phone number 976002, and when there is a call, the SIP phone and the PSTN phone can ring at the same time.
  • the number 976002 of the new SIP terminal C is the number resource of the softswitch. This number is a logical number.
  • FIG. 7 the flow of the called intelligent service of the IMS user using the softswitch of the existing network is as shown in FIG. 7, which specifically includes the following steps:
  • Step S701 The calling side routes the call to the softswitch according to the called logical number.
  • the calling party calls the called number 976002. Since this number is a number resource of the softswitch, the call request is routed to the softswitch regardless of whether the calling user is the softswitch user terminal A or the IMS user terminal D.
  • Step S702 The softswitch queries the SHLR for the smart service information subscribed to the called logical number according to the called logical number query.
  • the calling party does not sign the smart service information.
  • Step S703 The SHLR returns the smart service information of the called subscription to the softswitch.
  • Step S704 The softswitch inserts the smart prefix corresponding to the smart service in front of the called number according to the subscribed different intelligent service information, and triggers the call to the corresponding SCP according to the smart prefix to complete the corresponding intelligent service.
  • the logical number 976002 subscribes to the "called simultaneous vibration" service, and the SCP stores the correspondence between the logical number 976002 and the IMS domain terminal C physical number 126976002 and the PSTN POTS terminal B number.
  • Step S705 The SCP sends a new session request to the physical number corresponding to the POTS B and the SIP terminal C, respectively.
  • Step S706 the softswitch routes the call to the called terminal C.
  • the softswitch easily routes the call request message INVITE to the IMS based on the "126" contained in the physical number. Since the physical number is already registered with the CSCF, the CSCF can route the call request INVITE to the called terminal C.
  • Step S707 the called party rings.
  • Step S708 the called party responds to the call, and the 180 response returns to the calling terminal D along the INVITE path.
  • the SIP terminal C uses the called intelligent service provided by the softswitch, and can also use the called multimedia service of the IMS at the same time.
  • the operator signs the called multimedia service on the user's physical number, so when 976002 is called, the caller The call is first routed to the softswitch to provide the called intelligent service, and then routed to the CSCF of the IMS.
  • the CSCF can continue to trigger the called service on the physical number according to the called physical number to provide the IMS multimedia service for the user.
  • the CSCF determines the IP address of the called terminal C based on the physical number of the call request, and routes the call request to the called terminal C.
  • the IMS user is assigned a logical number and a physical number.
  • the user number published in the opposite direction is the “logical number”, that is, the telephone number that the user provides to others in his business card, such as 876001/976002.
  • the user number that is not publicly announced is a physical number, and the physical number is assigned to the user for a specific purpose, such as 126876001 in the second embodiment, which is allocated to the user in order to prevent loop processing.
  • the 126976002 in the third embodiment it is allocated for the user to enable the network side to route the call request to the terminal C.
  • the number resource of the physical number assigned to the IMS user belongs to the IMS network, and the network side can route the call to the corresponding IMS network according to the physical number. Since the physical number is not directly used by the user (for example, the calling user does not directly call the called physical number when making a call), it has strong scalability and can be flexibly set. This is different from the logical number. For example, the current network logical number is currently 8 bits long and needs to be divided according to the area. A certain area needs to adopt the similar restrictions of 8740000 - 8741000. For the physical number, any length can be used, and the number segment can also be set arbitrarily.
  • a physical number of 9 digits is considered to belong to the IMS network.
  • the physical number has very strong scalability, and there are also many variations on the way the physical number is set. Specifically, how to set the physical number, including the number segment of the physical number, the length, and the like are based on the foregoing method proposed by the embodiment of the present invention, so any method for setting the physical number and corresponding changes should be The scope of the invention is covered by the scope of protection.
  • the physical number and logical number of the user can be configured in the same implicit registration set on the HSS to ensure that the terminal can successfully use the physical number and logical number.
  • the CSCF downloads the service subscription information corresponding to each of the two numbers from the HSS.
  • the flow chart for registering the IMS user terminal includes the following steps:
  • Step S801 The newly added IMS user sends a registration message REGISTER to the S-CSCF, where the calling user identifier in the registration message may be a logical number or a physical number.
  • Step S802 After the S-CSCF authentication registration request is successful, the S-CSCF requests the HSS to download the user subscription data through the SAR request.
  • Step S803 The physical number and the logical number are configured in the same implicit registration set in the HSS, and the physical number and the logical number can be signed to have different services.
  • the HSS sends the user subscription data corresponding to the two numbers to the S-CSCF through the S AA response.
  • Step S804 the S-CSCF returns a 200 OK to the IMS terminal.
  • the foregoing embodiments respectively describe a method in which an IMS user uses a called intelligent service and an IMS user to use a called intelligent service.
  • the scenario in which multiple services are used simultaneously is described below.
  • Step S901 The IMS processes the multimedia service of the calling 876001. The call is routed to the softswitch by the number change AS.
  • Step S902 the softswitch deletes the routing number 127 in the called number, queries the subscription data signed by the calling party 876001, processes the calling intelligent service, queries the contracted data of the called 876002, processes the called intelligent service, and then routes the call to IMS.
  • Step S903 The IMS processes the multimedia service of the called 126876002.
  • the embodiment of the present invention takes an intelligent service provided by an IMS user using a PSTN side softswitch as an example.
  • the method using the embodiment of the present invention is also applicable to the IMS user using the PLMN side intelligent service.
  • Related equipment such as mobile softswitch, HLR, SCP, etc., the signaling interaction between the mobile softswitch and the HLR, the SCP, and the signaling interaction between the softswitch and the SHLR and the SCP in the fixed PSTN will be different. However, it does not affect the application of the method of the invention.
  • a system structure diagram for providing an intelligent service for an IMS user includes: a first CSCF entity 1, a number change AS entity 2, and a first softswitch entity 3; a first CSCF entity 1 .
  • the AS entity 2 For triggering a call request to the AS entity 2, and routing the call request to the first softswitch entity 3 according to the indication of the AS entity 2; the AS entity 2, for using the called number in the call request according to the configuration data Inserting a prefix; the first softswitch entity 3 is configured to receive a call request sent by the first CSCF entity 1, delete the prefix of the called number in the call request, according to the identifier of the IMS user in the call request and the signed intelligent service information Interact with the database, SCP, provide intelligent services for IMS users, and route call requests according to the called number in the call request.
  • the first CSCF entity 1 further includes: a triggering module 11 for triggering a call request to the AS entity 2; and a sending module 12, configured to route the call request to the first softswitch entity according to the indication of the AS entity 2 3.
  • the AS entity 2 further includes: a configuration data module 21, configured to record a routing number of a first softswitch entity that provides an intelligent service for the IMS user; a call receiving module 22, configured to receive a call request; and a call determining module 23, Determining, according to the call request received by the call receiving module 22, whether the currently served IMS user is a called user or a called user; the number conversion module 24 is configured to use the judgment result of the call determining module 23 and the IMS user in the configuration data module.
  • the record of 21 converts the called number in the call request, and inserts a routing number as a prefix before the called number.
  • the first softswitch entity 3 further includes: a first receiving module 31, configured to receive a call request sent by the first CSCF entity 1, and a prefix deletion module 32, configured to delete the call request received by the first receiving module 31. a prefix of the called number; the first triggering module 33 is configured to interact with the database and the SCP according to the identifier of the IMS user in the call request and the signed intelligent service information, and provide an intelligent service for the IMS user; 34. For routing a call request according to the indication of the first trigger module 33 and the called number in the call request. As shown in FIG.
  • another system structure diagram for providing an IMS user with an intelligent service includes: a second softswitch entity 4 and a second CSCF entity 5; and a second softswitch entity 4, Receiving a call request, interacting with the database and the SCP according to the identifier of the IMS user in the call request and the signed intelligent service information, providing an intelligent service for the IMS user, and routing the call request according to the called number in the call request; the second CSCF The entity 5 is configured to receive a call request sent by the second softswitch entity 4.
  • the second softswitch entity 4 further includes: a second receiving module 41, configured to receive a call request, and a second triggering module 42, configured to: according to the identifier of the IMS user in the call request received by the second receiving module 41, The subscribed intelligent service information interacts with the database and the SCP to provide an intelligent service for the IMS user.
  • the second sending module 43 is configured to route the call request according to the indication of the second trigger module 42 and the called number in the call request.
  • the second CSCF entity 5 further includes: a receiving module 51, configured to receive a call request sent by the second softswitch entity 4, and a connection module 52, configured to connect to the call request received by the module 51.
  • the IMS user when the IMS-SSF entity is not in the networking, the IMS user is provided with the live network intelligent service by using the softswitch, which saves the cost of developing the IMS-SSF entity, and the embodiment of the present invention enables the IMS user to Inheriting the existing network number enables new IMS users to make calls based on the 7 live network number resources, and does not bring data maintenance difficulties to the existing network devices.
  • the present invention can be implemented by hardware or by software plus necessary general hardware platform.
  • the technical solution of the present invention may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a USB flash drive, a mobile hard disk, etc.), including several The instructions are for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present invention.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)

Description

一种为 IMS用户提供智能业务的方法、 系统和装置 本申请要求于 2007年 12 月 29 日提交中国专利局、 申请号为 200710306082.2、 发明名称为"一种呼叫建立和业务应用方法、 系统 和装置 "的中国专利申请，以及于 2008年 1月 14日提交中国专利局、 申请号为 200810003683.0, 发明名称为 "一种为 IMS用户提供智能 业务的方法、 系统和装置" 的中国专利申请的优先权， 其全部内容通 过引用结合在本申请中。 技术领域
本发明涉及移动通信技术领域， 特别是涉及一种为 IMS用户提 供智能业务的方法、 系统和装置。 背景技术
IMS ( IP Multimedia Subsystem, IP多媒体子系统）是一种网络 结构， 该技术植根于移动通信领域， 最初是 3GPP ( Third Generation Partnership Project, 第三代合作项目）为移动网络定义的， 而在 NGN
( Next Generation Network, 下一代网络 ) 的才匡架下， IMS应同时支 持固定接入和移动接入。 在 NGN的框架中， 终端和接入网络是各种 各样的， 而其核心网络只有一个 IMS , 它的核心特点是采用 SIP
( Session Initiated Protocol, 会话发起协议）协议和与接入的无关性。
IMS是一个基于 IP的、 业务开放的、 与接入方式无关的网络环 境， 通过在核心网络层提供用户标识鉴权、 QoS ( Quality of Service, 服务质量）保证、 安全保证、 NAT ( Network Address Translator, 网 络地址转换）穿越等基础能力， 给各种业务以有力的支撑。 IMS提供 业务的形式， 一般是引入一个 AS ( Application Server, 应用服务器）， 每个 AS上可以驻留一个或多个业务。各业务的流程间可能相差悬殊， 用途各异， 很多业务量也需要 UE ( User Equipment, 用户终端）上引 入对应的客户端软件， 与 AS —起向用户提供具体的业务； 如 PoC ( Push to Talk Over Cellular,无线一键通 )业务，网络侧需要部署 PoC Server ( PoC服务端 ), 终端侧需要部署 PoC Client ( PoC客户端）。
目前 PSTN ( Public Switched Telephone Network, 公共电话交换 网）侧已经实现网络智能化， 端局用户的智能业务在汇接局上集中触 发。所有用户的智能业务签约在 SHLR( Smart Home Location Register, 智能归属位置寄存器）上， 用户端局呼叫全部上移到汇接局上， 汇接 局通过查询 SHLR得到用户签约智能业务对应的字冠，并按照业务的 顺序顺次在被叫号码前插智能业务字冠， 并触发对应的智能业务。 当 智能业务触发完毕后， 最后根据被叫号码接续被叫。
IMS的优势是易于提供丰富的多媒体业务， 与此同时， 还需考虑
IMS网络对现网业务的继 7 性。
新建 IMS 网络需要具备对现有 PSTN业务的继承性。 一方面利 用电话业务 AS, IMS网络可以提供现有 PSTN/PLMN ( Public Land Mobile Network, 公用陆地移动通信网）的电话补充业务。 另一方面， 依据 3GPP IMS标准， 可以利用 IMS - SSF ( IMS Service Switching Function, IMS服务交换功能）实体与现有智能网互通， 向 IMS用户 提供除补充业务之外的智能业务。 但 IMS-SSF的开发工作量大， 在 IMS 早期部署时可能还不支持此功能， 需要考虑在组网中没有 IMS-SSF实体的情况下， 为 IMS用户提供现网智能业务的方法， 但 目前还没有这样的解决方案。
进一步的， 新建 IMS网络需要具备对现网号码的继承性的需求。 以图三为例说明继承现网号码的需求。 用户家中原有两部 PSTN话 机， 分别放置在客厅和书房， 为了使用丰富的多媒体业务， 将其客厅 的 PSTN话机更换为 SIP话机（接入 IMS网络），显然，用户希望 SIP 话机仍然沿用原先已有的电话号码。 因此新建的 IMS 网络仍然需要 支持使用原有 PSTN电话号码作为用户终端的标识。
通常为 IMS网络的用户分配电话号码的方法， 如图 1所示， 为 IMS网络使用独立号码资源示意图，该实施例由运营商为新建的 IMS 网络单独分配号码资源。 为方便与现有网络互通时数据的规划， 新建 IMS 网络用户号码使用单独的号段。 比如现网还有以 "876"开头的 号段没有使用， 将此号段分配给 IMS 网络， 原有汇接局增加根据被 叫 "876"路由到 IMS网络的路由数据。 采用这种方式， IMS用户的 号码与原先 PSTN号码号段资源是相互独立的。
在实现本发明的过程中， 发明人发现现有技术至少存在以下 问题：现有技术要实现为 IMS用户提供智能业务需开发 IMS-SSF, 但 IMS-SSF的开发工作量大， 部网复杂， 而且早期部署 IMS的可 能还不支持此功能， 需要考虑在组网中没有 IMS-SSF实体的情况 下， 为 IMS用户提供现网智能业务的方法， 但目前还没有这样的 解决方案。 发明内容
本发明实施例提供一种为 IMS用户提供智能业务的方法、 系 统和装置，使得在组网中没有 IMS-SSF实体的情况下，能够为 IMS 用户提供现网智能业务。 进一步的， 本发明实施例中 IMS新增用 户能够继承使用现网号码， 使新增 IMS用户能够在继承现网号码 资源的基础上进行呼叫， 并且不会给现网设备带来数据维护困难 的问题。
本发明实施例一方面提出一种为 IMS用户提供智能业务的方 法， 具体包括： 接收呼叫请求； 依据所述呼叫请求中的 IMS用户 的标识及其签约的智能业务信息与数据库、 业务控制点 SCP进行 交互， 为所述 IMS用户提供智能业务； 依据所述呼叫请求中的被 叫号码路由所述呼叫请求。
另一方面， 本发明实施例还提供了一种为 IMS用户提供智能 业务的系统， 包括： 第一 CSCF实体、 号码变换 AS实体和第一软 交换实体， 所述第一 CSCF实体， 用于将呼叫请求触发到所述 AS 实体，并根据所述 AS实体的指示将所述呼叫请求路由到所述第一 软交换实体； 所述 AS实体， 用于根据配置数据在所述呼叫请求中 的被叫号码前插入前缀； 所述第一软交换实体， 用于接收所述第 一 CSCF实体发送的呼叫请求，删除所述呼叫请求中的被叫号码的 前缀， 依据所述呼叫请求中的 IMS用户的标识及其签约的智能业 务信息与数据库、 SCP进行交互， 为所述 IMS用户提供智能业务， 并依据所述呼叫请求中的被叫号码路由所述呼叫请求。
再一方面， 本发明实施例还提供了另一种为 IMS用户提供智 能业务的系统， 包括： 第二软交换实体和第二 CSCF实体， 所述第 二软交换实体， 用于接收呼叫请求， 依据所述呼叫请求中的 IMS 用户的标识及其签约的智能业务信息与数据库、 SCP 进行交互， 为所述 IMS用户提供智能业务， 并依据所述呼叫请求中的被叫号 码路由所述呼叫请求。所述第二 CSCF实体，用于接收所述第二软 交换实体发送的呼叫请求， 接续所述呼叫请求。
再一方面， 本发明实施例还提供了一种第一软交换实体， 包 括： 第一接收模块， 用于接收第一 CSCF实体发送的呼叫请求； 前 缀删除模块， 用于删除所述第一接收模块接收的呼叫请求中的被 叫号码的前缀； 第一触发模块， 用于依据所述呼叫请求中的 IMS 用户的标识及其签约的智能业务信息与数据库、 SCP 进行交互， 为所述 IMS用户提供智能业务； 第一发送模块， 用于依据所述第 一触发模块的指示和所述呼叫请求中的被叫号码路由所述呼叫请 求。
再一方面， 本发明实施例还提供了一种第二软交换实体， 包 括： 第二接收模块， 用于接收呼叫请求； 第二触发模块， 用于依 据所述第二接收模块接收的呼叫请求中的 IMS用户的标识及其签 约的智能业务信息与数据库、 SCP进行交互， 为所述 IMS用户提 供智能业务； 第二发送模块， 用于依据所述第二触发模块的指示 和所述呼叫请求中的被叫号码路由所述呼叫请求。
再一方面，本发明实施例还提供了一种第一 CSCF实体，包括： 触发模块， 用于将呼叫请求触发到 AS实体； 发送模块， 用于根据 所述 A S实体的指示将所述呼叫请求路由到第一软交换。 再一方面，本发明实施例还提供了一种第二 CSCF实体，包括： 接收模块， 用于接收第二软交换实体发送的呼叫请求； 接续模块， 用于接续所述接收模块接收的呼叫请求。
再一方面， 本发明实施例还提供了一种号码变换 AS实体， 包 括： 配置数据模块， 用于记录为 IMS用户提供智能业务的第一软 交换实体的路由号； 呼叫接收模块， 用于接收呼叫请求； 呼叫判 断模块， 用于依据所述呼叫接收模块接收的呼叫请求判断当前所 服务的 IMS用户为主叫用户还是被叫用户； 号码变换模块， 用于 依据所述呼叫判断模块的判断结果和所述 IMS用户在配置数据模 块的记录， 将所述呼叫请求中的被叫号码进行变换， 在所述被叫 号码前插入路由号作为前缀。
本发明实施例的技术方案具有以下优点： 实现了在组网中没 有 IMS-SSF实体的情况下， 采用软交换为 IMS用户提供现网智能 业务， 节省了开发 IMS-SSF实体的成本， 提高了软交换的利用率， 而且本发明实施例使 IMS用户能够继承使用现网号码，使新增 IMS 用户能够在继承现网号码资源的基础上进行呼叫， 并且不会给现 网设备带来数据维护困难的问题。 附图说明
图 1为现有技术 IMS网络使用独立号码资源示意图； 图 2为本发明实施例 PSTN现网引入 IMS的网络架构图； 图 3为本发明实施例 IMS用户使用 PSTN侧主叫智能业务流 程图；
图 4为本发明实施例 IMS用户使用现网软交换被叫智能业务 的流程图；
图 5为本发明实施例 IMS用户使用现网软交换被叫智能业务 的架构示意图；
图 6为本发明实施例 IMS用户使用 PSTN侧被叫智能业务的 另一架构示意图； 图 7为本发明实施例 IMS用户使用现网软交换的被叫智能业 务的流程；
图 8为本发明实施例 IMS用户终端注册流程图；
图 9为本发明实施例为 IMS用户多种业务同时使用的场景流 程图；
图 10为本发明实施例为 IMS用户多种业务同时使用的场景架 构示意图；
图 11为本发明实施例的一种为 IMS用户提供智能业务的系统 结构图；
图 12为本发明实施例的另一种为 IMS用户提供智能业务的系 统结构图。 具体实施方式
下面结合附图和实施例，对本发明的具体实施方式作进一步详 细描述。
如图 2所示， 为本发明实施例在 PSTN现网引入 IMS的网络 架构图， 架构左侧为 PSTN现有网络架构， 终端归属于软交换（或 软交换下的交换机 ) , PSTN智能业务由 SCP( Service Control Point, 业务控制点）提供， 各用户的智能业务签约在 SHLR 上。 架构右 侧为新增 IMS网络的架构， IMS网络业务由 SIP AS提供， 业务签 约在 HSS ( Home Subscriber Server, 归属用户服务器）上。 软交换 通过 SIP中继与 IMS网络对接。 由于 3GPP IMS规范对 SIP协议 做了一定扩展， 而现网软交换通常不支持这些扩展， 为保证 IMS 网络与 PSTN网络的互通， 新增 IMS网络需要适配现网软交换支 持的 SIP规范， 具体有两种方式， 一种是 IMS 网络中的 S-CSCF 具备与现网软交换直接互通的能力， 另一种是 S-CSCF ( Serving CSCF, 服务 CSCF ) 通过互通边界控制功能单元与现网软交换互 通， 其中互通边界控制功能单元完成软交换 SIP Profile与 IMS SIP Profile之间的转换。 本发明实施例流程中， 为了筒洁采用 S-CSCF 直接与软交换互通的方式为例。 本发明实施例中， 在未特别说明 的情况下， CSCF即代表 S-CSCF。
为了向用户提供丰富的多媒体业务， 运营商部署了 IMS 网络， 新部署的 IMS域的号段资源为 "876" , 原有软交换域的号段资源为 "976"。 IMS用户在享用多媒体业务的同时， 也希望使用传统的智能 业务， 本发明的实施例中， 通过将呼叫路由到软交换域， 由软交换 域为 IMS用户提供传统智能业务。
如图 3所示， 为本发明实施例 IMS用户使用 PSTN侧主叫智 能业务流程图， 例如主叫预付费业务。 以图 2中 SIP终端 D拨叫 SIP终端 C为例， 描述 IMS主叫终端 D使用软交换的主叫预付费 业务流程， 具体包括以下步骤：
步骤 S301 , 主叫终端 D在 IMS向被叫终端 C发起会话请求。 步骤 S302, CSCF接收主叫终端 D的呼叫请求， 根据主叫号 码上签约的签约数据触发号码变换 AS , 将呼叫请求路由到号码变 换 AS上。
步骤 S303 , 号码变换 AS在被叫号码前插入软交换的路由号， 并将变换后的被叫号码发送给 CSCF。
步骤 S304, CSCF依据变换后的被叫号码， 将呼叫请求路由 到软交换。
步骤 S305 , 软交换依据中继群数据配置， 删除被叫号码前的 路由号， 并根据主叫号码向 SHLR 查询主叫号码上签约的智能业 务信息。
步骤 S306, SHLR 向软交换返回主叫号码上签约的智能业务 信息。
步骤 S307 , 软交换触发主叫智能业务到 SCP。 软交换根据 SHLR 上签约的智能业务信息顺次在被叫号码前插入该智能业务 对应的智能字冠， 把呼叫路由到 SCP上触发对应的智能业务。 以 主叫预付费业务为例， 软交换将呼叫触发到 SCP上完成业务。 步骤 S308 , 软交换将呼叫路由到 CSCF。 在触发主叫智能业 务到 SCP后， 软交换继续查询本次呼叫的被叫号码是否签约智能 业务， 本例中被叫号码未签约智能业务， 因此软交换依据被叫号 码将呼叫路由到 IMS域的 CSCF。
步骤 S309, CSCF做被叫处理，根据被叫号码接续被叫终端 C。 步骤 S310, 被叫终端 C响应呼叫， 180响应沿 INVITE路径返 回到主叫终端 D。
本发明实施例中， IMS 用户使用由软交换提供的智能业务需 要在用户签约数据做相应配置， 考虑到现网软交换不支持 ISC接 口， CSCF触发软交换智能业务是通过先触发号码变换业务， 再依 据变换后的被叫号码将呼叫路由到软交换的方法来实现的。 具体 说， 为了对 IMS域的用户触发主叫智能业务， 为相应用户号码签 约一个主叫业务 （例如称此业务为 "软交换智能业务"）， 当此主 叫业务被触发时， S-CSCF将 INVITE请求路由到号码变换 AS , 该 AS负责在被叫号码前插一个路由字冠（例如 127 ),然后将 INVITE 请求路由回 S-CSCF, S-CSCF依据此变换后的号码的字冠 127将 呼叫请求 INVITE路由到软交换。 当用户同时签约 IMS多媒体业 务和软交换智能业务，需要通过合理的签约数据配置，先触发 IMS 多媒体业务， 因为触发了软交换智能业务之后， 号码变换 AS变换 了被叫号码后，后续 CSCF的处理都是针对被叫的处理，如果先触 发软交换智能业务， 则排在其后的多媒体业务将没有机会被触发。
如图 4所示， 为本发明实施例 IMS用户使用现网软交换被叫 智能业务的流程图， 例如被叫同振业务。 以图 5为例， 终端 B和 终端 C属于同一个用户， 用户希望有入呼叫时终端 B和终端 C能 够同时振铃， 例如图中 SIP终端 D拨叫 SIP终端 C号码 876001 , 被叫终端 C使用软交换提供的同振智能业务。 本发明实施例类似 前述实施例中需要为主叫用户配置业务触发数据， 并通过号码变 换 AS 变换被叫号码将呼叫路由到软交换。 本实施例为了对 IMS 域的用户 876001触发被叫智能业务， 需要为 876001签约被叫业 务（例如称此业务为 "软交换智能业务"）， 当此被叫业务被触发 时， S-CSCF将 INVITE请求路由到号码变换 AS , 该 AS负责在被 叫号码前插一个路由字冠 （例如 127 ), 然后将 INVITE请求路由 回 S-CSCF, S-CSCF可以依据此变换后的号码的字冠 127将呼叫 请求 INVITE路由到软交换。 具体包括以下步骤：
步骤 S401，在完成主叫侧处理后，主叫侧根据被叫号码 876001 将呼叫路由到 CSCF。 主叫用户可以是 IMS域用户如终端 D,也可 以是软交换域的用户。 此处省略主叫侧处理流程。
步骤 S402, CSCF收到呼叫请求， CSCF根据被叫号码签约的 签约数据， 将呼叫请求 INVITE路由到号码变换 AS。
步骤 S403 , 号码变换 AS在被叫号码前插入 PSTN的路由号 127 , 并将变换后的被叫号码发送给 CSCF。
步骤 S404, CSCF依据路由号 127将呼叫路由到软交换。
步骤 S405 , 软交换依据中继数据配置， 删除被叫号码前的路 由号， 先处理主叫智能业务 （本例中没有主叫智能业务） 再处理 被叫智能业务。 软交换根据被叫号码查询 SHLR 查询被叫号码上 签约的智能业务信息。
步骤 S406, SHLR 向软交换返回被叫号码上签约的智能业务 信息。
步骤 S407, 软交换根据签约的不同智能业务信息顺次在被叫 号码前插入该智能业务对应的智能字冠， 并把呼叫触发到 SCP上 对应的智能业务。 以被叫同振业务为例， SCP 配置有逻辑号码 876001与物理号码 126876001和 PSTN终端 B号码 976002的对应 关系，
步骤 S408, SCP分别对 POTS终端 B及 SIP终端 C的物理号 码下发新的会话请求。 对被叫 SIP C物理号码那一路呼叫， 软交换 根据物理号码路由到 IMS, CSCF做被叫处理， 由于物理号码上未 签约 "软交换智能业务"， 因此不会又触发号码变换 AS。
步骤 S409, CSCF根据物理号码， 将呼叫请求路由至被叫方 SIP终端 c。
步骤 S410, 被叫响应呼叫， 180响应沿 INVITE路径返回到主 叫终端 D。
本发明实施例， IMS网络为 SIP终端 C分配号码 876001 , 称 逻辑号码， 建议为终端 C再分配另一个号码， 称为物理号码， 如 126876001。 如果不分配物理号码， 则会出现以下问题。 当 876001 作为被叫时， 依据前述方法， CSCF将呼叫路由到软交换触发被叫 智能业务， 当被叫智能业务处理完毕后， 软交换做被叫路由， 被 叫号码 876001属于 IMS域， 软交换将呼叫路由回 IMS域， 此时 IMS域 CSCF收到 INVITE, 根据被叫号码 876001做被叫处理， 依据 876001业务签约数据， 继续触发到号码变换 AS并在被叫号 码前插路由号将呼叫路由回 PSTN侧， 陷入循环。 除非软交换在路 由回 IMS域的呼叫中增加信令指示， 但这样需要现网软交换配合 修改。 因此在现网软交换不修改的情况下， 建议为 IMS域终端 C 分配物理号码， 软交换在完成被叫智能业务处理后， 将被叫号码 变为物理号码， 依据物理号码将呼叫路由回 IMS。 针对逻辑号码 签约有被叫 "软交换智能业务"， 针对物理号码则不签约此业务。 逻辑号码的被叫业务签约数据， 在 "软交换智能业务" 之前还可 以签约 IMS多媒体业务， 基于物理号码也可以签约 IMS多媒体业 务。
下面描述另一种 IMS用户使用 PSTN侧被叫智能业务场景， 此场景中不需要号码变换 AS。如图 6所示，用户电话号码为 976002, 家中原有两部 PSTN话机， 分别放置在客厅和书房， 为使用丰富的多 媒体业务， 用户将其客厅的 PSTN话机更换为 SIP话机（接入 IMS 网络）， 用户希望 SIP话机仍然沿用原先已有的电话号码 976002, 并 且有电话呼入时， SIP话机和 PSTN话机能同时振铃。 新增 SIP终端 C的号码 976002属软交换的号码资源， 此号码为逻辑号码。 为了 使网络侧能够将呼叫最终路由到终端 C, 需要为 SIP终端 C另外 分配一个属于 IMS 网络的号码， 比如 126976002。 称此号码为物 理号码。
以 SIP终端 C为例， IMS用户使用现网软交换的被叫智能业 务的流程如图 7所示， 具体包括以下步骤：
步骤 S701 , 主叫侧根据被叫逻辑号码将呼叫路由到软交换。 主叫呼叫被叫号码 976002, 由于此号码属软交换的号码资源， 因 此无论主叫用户是软交换用户终端 A或者是 IMS用户终端 D, 呼 叫请求都会被路由到软交换。
步骤 S702, 软交换根据被叫逻辑号码查询向 SHLR查询被叫 逻辑号码上签约的智能业务信息。 本实施例中主叫未签约智能业 务信息。
步骤 S703 , SHLR向软交换返回被叫签约的智能业务信息。 步骤 S704, 软交换根据签约的不同智能业务信息顺次在被叫 号码前插入该智能业务对应的智能字冠， 并依据智能字冠， 将呼 叫触发到相应 SCP上以完成相应的智能业务。 本实施例中， 逻辑 号码 976002签约了 "被叫同振"业务， SCP保存有逻辑号码 976002 与 IMS域终端 C物理号码 126976002和 PSTN POTS终端 B的号 码的对应关系。
步骤 S705 , SCP分别对 POTS B、 SIP终端 C对应的物理号码 下发新的会话请求。
步骤 S706, 软交换将呼叫路由到被叫终端 C。 软交换根据物 理号码中包含的 " 126" , 很容易将呼叫请求消息 INVITE路由到 IMS , 因物理号码已在 CSCF 注册， 因此 CSCF可以将呼叫请求 INVITE路由到被叫终端 C。
步骤 S707, 被叫振铃。
步骤 S708 , 被叫响应呼叫， 180响应沿 INVITE路径返回到主 叫终端 D。
本发明实施例中， SIP终端 C使用由软交换提供的被叫智能业 务， 还可以同时使用 IMS的被叫多媒体业务。 本例运营商在用户 物理号码上签约被叫多媒体业务， 因此当 976002做为被叫时， 呼 叫先被路由到软交换， 提供被叫智能业务， 之后路由到 IMS 的 CSCF, CSCF 可以根据该被叫物理号码继续触发该物理号码上签 约的被叫业务， 为用户提供 IMS的多媒体业务。 之后 CSCF根据 呼叫请求的物理号码确定被叫终端 C的 IP地址， 将呼叫请求路由 至被叫终端 C。
本实施例中， 为 IMS用户分配有逻辑号码和物理号码。 称对 外公布的用户号码为 "逻辑号码"， 即用户在自己的名片中提供给 他人的电话号码， 如 876001/976002。 称不对外公布的用户号码为 物理号码， 物理号码是为了特定目的而为用户分配的， 如第二实 施例中的 126876001 , 是为了防止循环处理而为用户分配的。 如第 三实施例中的 126976002,是为了使网络侧能够将呼叫请求路由到 终端 C而为用户分配的。
为 IMS用户分配的物理号码的号码资源属于 IMS网络， 网络 侧依据物理号码能够将呼叫路由到相应 IMS 网络。 因物理号码不 被用户直接使用（例如主叫用户发起呼叫时不会直接呼叫被叫的物理 号码）， 因此有较强的可扩展性， 可以灵活设置。 这点不同于逻辑号 码。例如，现网逻辑号码目前长度为 8位，且需要根据区域进行划分， 某区域需要采用 8740000 - 8741000号段等类似的限制。 而对于物理 号码来说可以采用任意长度， 号段也可以任意设置， 只要设置合理只 需 4艮少的配置数据即可实现将呼叫路由到相应 IMS 网络的判断。 如 将长度为 9位的物理号码认为被叫方属于 IMS网络。 或者在被叫方 的逻辑号码之前添加一个路由号码得到对应的物理号码，由于逻辑号 码是唯一的， 因此添加路由号码后的物理号码也是唯一的， 如将路由 号码设置为 126 (属于 IMS网络， 使用现网不用的一个单独号段）， 因此转换后为 "126 +逻辑号码" 的所有物理号码都属于 IMS网络。
通过上述描述可以看出， 物理号码有非常强的可扩展性， 并且对 于物理号码的设置方式也存在多种变化。 具体如何设置物理号码， 包 括设置物理号码的号段，长度等均以本发明实施例提出的上述方法为 基础， 因此任何关于如何设置物理号码， 及相应的变化方式均应为本 发明实施例保护范围所涵盖。
当终端同时具备逻辑号码和物理号码时， 为保证终端注册成 功后可以使用物理号码和逻辑号码， 在 HSS上将用户的物理号码 和逻辑号码配置在同一个隐式注册集中。 终端注册成功后， CSCF 从 HSS下载两个号码各自对应的业务签约信息。
如图 8所示， 为 IMS用户终端注册流程图 （省略了对注册的 认证过程）， 包括以下步骤：
步骤 S801 , 新增 IMS 用户向 S-CSCF 发送注册报文 REGISTER，该注册报文中的主叫用户标识可以是逻辑号码或者物 理号码。
步骤 S802, S-CSCF认证注册请求成功后， S-CSCF通过 SAR 请求， 向 HSS请求下载用户签约数据。
步骤 S803 , 在 HSS已将物理号码、 逻辑号码配置在同一个隐 式注册集中， 并且物理号码和逻辑号码可签约有不同的业务。 HSS 将两个号码对应的用户签约数据通过 S AA响应下发给 S-CSCF。
步骤 S804, S-CSCF返回 200 OK给 IMS终端。
前述实施例分别描述 IMS用户使用主叫智能业务和 IMS用户 使用被叫智能业务的方法。 如下筒述多种业务同时使用的场景。
如图 9所示， 为 IMS用户多种业务同时使用的场景流程图， 以图 10中 IMS终端 C呼叫 IMS终端 D为例，具体包括以下步骤： 步骤 S901 , IMS处理主叫 876001的多媒体业务， 通过号码变 换 AS将呼叫路由到软交换。
步骤 S902, 软交换删除被叫号码中的路由号 127, 查询主叫 876001签约的签约数据， 处理主叫智能业务， 查询被叫 876002签 约的签约数据， 处理被叫智能业务， 然后将呼叫路由到 IMS。
步骤 S903 , IMS处理被叫 126876002的多媒体业务。
本发明实施例以 IMS用户使用 PSTN侧软交换提供的智能业 务为例。 当然， 采用本发明实施例的方法同样适用于 IMS用户使 用 PLMN侧智能业务。 此时需要将 PSTN侧的设备变为 PLMN的 相关设备， 如移动软交换， HLR、 SCP 等， 此时在移动软交换和 HLR、 SCP间的信令交互与固定 PSTN中的软交换与 SHLR、 SCP 间的信令交互细节上会有所差异， 但并不影响本发明方法的应用。
如图 11所示， 为本发明实施例的一种为 IMS用户提供智能业 务的系统结构图， 包括： 第一 CSCF实体 1、 号码变换 AS实体 2和 第一软交换实体 3; 第一 CSCF实体 1 , 用于将呼叫请求触发到 AS 实体 2, 并根据 AS实体 2的指示将呼叫请求路由到第一软交换实体 3; AS实体 2, 用于根据配置数据在呼叫请求中的被叫号码前插入前 缀； 第一软交换实体 3,用于接收第一 CSCF实体 1发送的呼叫请求， 删除呼叫请求中的被叫号码的前缀， 依据呼叫请求中的 IMS用户的 标识及其签约的智能业务信息与数据库、 SCP进行交互， 为 IMS用 户提供智能业务， 并依据呼叫请求中的被叫号码路由呼叫请求。
其中， 第一 CSCF实体 1 , 进一步包括： 触发模块 11 , 用于将呼 叫请求触发到 AS实体 2; 发送模块 12, 用于根据 AS实体 2的指示 将所述呼叫请求路由到第一软交换实体 3。
其中， AS实体 2, 进一步包括： 配置数据模块 21 , 用于记录为 IMS 用户提供智能业务的第一软交换实体的路由号； 呼叫接收模块 22, 用于接收呼叫请求； 呼叫判断模块 23, 用于依据呼叫接收模块 22接收的呼叫请求判断当前所服务的 IMS用户为主叫用户还是被叫 用户； 号码变换模块 24, 用于依据呼叫判断模块 23的判断结果和所 述 IMS用户在配置数据模块 21的记录， 将呼叫请求中的被叫号码进 行变换， 在被叫号码前插入路由号作为前缀。
其中， 第一软交换实体 3, 进一步包括： 第一接收模块 31 , 用于 接收第一 CSCF实体 1发送的呼叫请求； 前缀删除模块 32, 用于删 除第一接收模块 31接收的呼叫请求中的被叫号码的前缀； 第一触发 模块 33 , 用于依据所述呼叫请求中的 IMS用户的标识及其签约的智 能业务信息与数据库、 SCP进行交互， 为 IMS用户提供智能业务； 第一发送模块 34, 用于依据第一触发模块 33的指示和呼叫请求中的 被叫号码路由呼叫请求。 如图 12所示， 为本发明实施例的另一种为 IMS用户提供智能 业务的系统结构图， 包括： 第二软交换实体 4和第二 CSCF实体 5; 第二软交换实体 4, 用于接收呼叫请求，依据呼叫请求中的 IMS用户 的标识及其签约的智能业务信息与数据库、 SCP 进行交互， 为 IMS 用户提供智能业务， 并依据呼叫请求中的被叫号码路由呼叫请求； 第 二 CSCF实体 5, 用于接收第二软交换实体 4发送的呼叫请求。
其中， 第二软交换实体 4, 进一步包括： 第二接收模块 41 , 用于 接收呼叫请求； 第二触发模块 42, 用于依据第二接收模块 41接收的 呼叫请求中的 IMS用户的标识及其签约的智能业务信息与数据库、 SCP进行交互， 为 IMS用户提供智能业务； 第二发送模块 43, 用于 依据第二触发模块 42 的指示和呼叫请求中的被叫号码路由呼叫请 求。
其中， 第二 CSCF实体 5, 进一步包括： 接收模块 51 , 用于接收 第二软交换实体 4发送的呼叫请求； 接续模块 52, 用于接续接收模 块 51接收的呼叫请求。
本发明实施例实现了在组网中没有 IMS-SSF 实体的情况下， 采 用软交换为 IMS用户提供现网智能业务， 节省了开发 IMS-SSF实体 的成本， 而且本发明实施例使 IMS 用户能够继承使用现网号码， 使 新增 IMS用户能够在继 7 现网号码资源的基础上进行呼叫， 并且不 会给现网设备带来数据维护困难的问题。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解 到本发明可以通过硬件实现，也可以借助软件加必要的通用硬件平台 的方式来实现。基于这样的理解， 本发明的技术方案可以以软件产品 的形式体现出来， 该软件产品可以存储在一个非易失性存储介质（可 以是 CD-ROM, U盘， 移动硬盘等） 中， 包括若干指令用以使得一 台计算机设备（可以是个人计算机， 服务器， 或者网络设备等）执行 本发明各个实施例所述的方法。
总之， 以上所述仅为本发明的较佳实施例而已， 并非用于限定本 发明的保护范围。 凡在本发明的精神和原则之内， 所作的任何修改、 等同替换、 改进等， 均应包含在本发明的保护范围之内。

Claims

权利要求
1、 一种为多媒体子系统 IMS用户提供智能业务的方法， 其特征 在于， 包括：
接收呼叫请求；
依据所述呼叫请求中的 IMS用户的标识及其签约的智能业务信 息与数据库、 业务控制点 SCP进行交互， 为所述 IMS用户提供智能 业务；
依据所述呼叫请求中的被叫号码路由所述呼叫请求。
2、 如权利要求 1所述为 IMS用户提供智能业务的方法， 其特征 在于， 当为所述 IMS用户提供主叫智能业务时， 具体包括：
在呼叫会话控制功能 CSCF依据呼叫请求中的主叫用户的签约 数据将所述呼叫请求中的被叫号码进行变换后，接收所述 CSCF发送 的呼叫请求；
删除所述呼叫请求中的被叫号码的前缀，并依所述主叫用户签约 的智能业务信息与数据库、 SCP进行交互， 为所述主叫用户提供主叫 智能业务；
依据所述呼叫请求中的被叫号码路由所述呼叫请求。
3、 如权利要求 1所述为 IMS用户提供智能业务的方法， 其特征 在于， 当为所述 IMS用户提供被叫智能业务， 且所述 IMS用户号码 资源属于 IMS时， 具体包括：
在 CSCF依据呼叫请求中的被叫用户的签约数据将所述呼叫请 求中的被叫号码进行变换后， 接收所述 CSCF发送的呼叫请求； 删除所述呼叫请求中的被叫号码的前缀，并依据所述被叫用户签 约的智能业务信息与数据库、 SCP进行交互， 为所述被叫用户提供被 叫智能业务；
依据所述呼叫请求中的被叫号码路由所述呼叫请求。
4、 如权利要求 2或 3所述为 IMS用户提供智能业务的方法， 其 特征在于， 所述将呼叫请求中的被叫号码进行号码变换， 具体包括： 所述 CSCF将所述呼叫请求触发到号码变换 AS, 所述 AS依据 配置数据在所述被叫号码前插入前缀。
5、 如权利要求 1所述为 IMS用户提供智能业务的方法， 其特征 在于， 当为所述 IMS用户提供被叫智能业务， 且所述 IMS用户号码 资源属于本地软交换时， 具体包括如下步骤：
接收呼叫请求中的主叫侧依据所述呼叫请求中的被叫号码发送 的呼叫请求， 所述主叫侧包括所述 IMS域的用户或共用电话交换网 PSTN域的用户；
依据所述被叫用户签约的智能业务信息与所述数据库、 SCP进行 交互， 为所述被叫用户提供被叫智能业务；
依据所述呼叫请求中的被叫号码路由所述呼叫请求。
6、 如权利要求 3或 5所述为 IMS用户提供智能业务的方法， 其 特征在于， 还包括：
在 IMS域为所述被叫用户分配两个号码， 第一号码和第二号码， 所述第一号码为所述被叫用户对外公布的号码，在所述呼叫中作为初 始被叫号码， 所述第二号码为所述被叫用户不对外公开的号码， 所述 两个号码属于同一隐式注册集；
本地软交换的智能业务信息基于所述被叫用户的第一号码； 在基于所述第一号码签约的智能业务信息完成被叫智能业务后， 将所述第一号码变为所述第二号码，并依据所述第二号码路由所述呼 叫请求。
7、 如权利要求 6所述为 IMS用户提供智能业务的方法， 其特征 在于， 还包括：
所述第二号码的分配原则为， 基于所述第一号码增加一个前缀； 依据所述第二号码的前缀将所述呼叫请求路由到所述 IMS域。
8、 一种为多媒体子系统 IMS用户提供智能业务的系统， 其特征 在于， 包括： 第一 CSCF实体、号码变换 AS实体和第一软交换实体， 所述第一 CSCF实体， 用于将呼叫请求触发到所述 AS实体， 并 根据所述 AS 实体的指示将所述呼叫请求路由到所述第一软交换实 体；
所述 AS实体， 用于根据配置数据在所述呼叫请求中的被叫号码 前插入前缀；
所述第一软交换实体，用于接收所述第一 CSCF实体发送的呼叫 请求， 删除所述呼叫请求中的被叫号码的前缀，依据所述呼叫请求中 的 IMS用户的标识及其签约的智能业务信息与数据库、 SCP进行交 互， 为所述 IMS用户提供智能业务， 并依据所述呼叫请求中的被叫 号码路由所述呼叫请求。
9、 一种为多媒体子系统 IMS用户提供智能业务的系统， 其特征 在于， 包括： 第二软交换实体和第二 CSCF实体，
所述第二软交换实体， 用于接收呼叫请求，依据所述呼叫请求中 的 IMS用户的标识及其签约的智能业务信息与数据库、 SCP进行交 互， 为所述 IMS用户提供智能业务， 并依据所述呼叫请求中的被叫 号码路由所述呼叫请求；
所述第二 CSCF实体，用于接收所述第二软交换实体发送的呼叫 请求， 接续所述呼叫请求。
10、 一种第一软交换实体， 其特征在于， 包括：
第一接收模块， 用于接收第一 CSCF实体发送的呼叫请求； 前缀删除模块，用于删除所述第一接收模块接收的呼叫请求中的 被叫号码的前缀；
第一触发模块， 用于依据所述呼叫请求中的 IMS用户的标识及 其签约的智能业务信息与数据库、 SCP进行交互， 为所述 IMS用户 提供智能业务；
第一发送模块，用于依据所述第一触发模块的指示和所述呼叫请 求中的被叫号码路由所述呼叫请求。
11、 一种第二软交换实体， 其特征在于， 包括：
第二接收模块， 用于接收呼叫请求；
第二触发模块，用于依据所述第二接收模块接收的呼叫请求中的 IMS用户的标识及其签约的智能业务信息与数据库、 SCP进行交互， 为所述 IMS用户提供智能业务；
第二发送模块，用于依据所述第二触发模块的指示和所述呼叫请 求中的被叫号码路由所述呼叫请求。
12、 一种第一 CSCF实体， 其特征在于， 包括：
触发模块， 用于将呼叫请求触发到 AS实体；
发送模块， 用于根据所述 AS实体的指示将所述呼叫请求路由到 第一软交换。
13、 一种第二 CSCF实体， 其特征在于， 包括：
接收模块， 用于接收第二软交换实体发送的呼叫请求； 接续模块， 用于接续所述接收模块接收的呼叫请求。
14、 一种号码变换 AS实体， 其特征在于， 包括：
配置数据模块， 用于记录为 IMS用户提供智能业务的第一软交 换实体的路由号；
呼叫接收模块， 用于接收呼叫请求；
呼叫判断模块，用于依据所述呼叫接收模块接收的呼叫请求判断 当前所服务的 IMS用户为主叫用户还是被叫用户； 号码变换模块， 用于依据所述呼叫判断模块的判断结果和所述 IMS用户在配置数据 模块的记录， 将所述呼叫请求中的被叫号码进行变换， 在所述被叫号 码前插入路由号作为前缀。
PCT/CN2008/073658 2007-12-29 2008-12-22 一种为ims用户提供智能业务的方法、系统和装置 WO2009092255A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN200710306082 2007-12-29
CN200710306082.2 2007-12-29
CN200810003683.0 2008-01-14
CN200810003683.0A CN101330652A (zh) 2007-12-29 2008-01-14 一种为ims用户提供智能业务的方法、系统和装置

Publications (1)

Publication Number Publication Date
WO2009092255A1 true WO2009092255A1 (zh) 2009-07-30

Family

ID=40206200

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/073658 WO2009092255A1 (zh) 2007-12-29 2008-12-22 一种为ims用户提供智能业务的方法、系统和装置

Country Status (2)

Country Link
CN (1) CN101330652A (zh)
WO (1) WO2009092255A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101505509B (zh) * 2009-03-19 2011-09-21 中兴通讯股份有限公司 资源预留的实现方法以及互通网元

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1816022A (zh) * 2005-02-05 2006-08-09 华为技术有限公司 实现电路域和分组域双向互操作的方法及系统
CN1848793A (zh) * 2005-04-15 2006-10-18 华为技术有限公司 一种分组网络互通的方法及其网络系统
CN1913503A (zh) * 2005-08-08 2007-02-14 华为技术有限公司 一种会话路由路径控制方法和系统
CN101083520A (zh) * 2007-07-20 2007-12-05 中兴通讯股份有限公司 一种ngn网络下接入网关容灾方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1816022A (zh) * 2005-02-05 2006-08-09 华为技术有限公司 实现电路域和分组域双向互操作的方法及系统
CN1848793A (zh) * 2005-04-15 2006-10-18 华为技术有限公司 一种分组网络互通的方法及其网络系统
CN1913503A (zh) * 2005-08-08 2007-02-14 华为技术有限公司 一种会话路由路径控制方法和系统
CN101083520A (zh) * 2007-07-20 2007-12-05 中兴通讯股份有限公司 一种ngn网络下接入网关容灾方法

Also Published As

Publication number Publication date
CN101330652A (zh) 2008-12-24

Similar Documents

Publication Publication Date Title
US8392582B2 (en) Method and apparatuses for making use of virtual IMS subscriptions coupled with the identity of a non SIP compliant terminal for non-registered subscribers
US7512090B2 (en) System and method for routing calls in a wireless network using a single point of contact
US8351461B2 (en) Method and apparatus for network based fixed mobile convergence
CN109639717B (zh) 携号转网的通信方法、主叫侧/被叫侧业务控制点服务器
EP2247031B1 (en) Implementation method, system and device for ims monitoring
JP6168572B2 (ja) ナンバー・ポータビリティ・サービスに基づくオンライン課金方法、装置、およびシステム
WO2007036123A1 (fr) Procede et systeme de communication pour un utilisateur du domaine cs accedant au domaine ims
CN1941739B (zh) 分配和使用用户标识的方法及其系统
WO2010017730A1 (zh) Ip多媒体子系统注册机制的实现方法、系统及装置
US8320363B2 (en) Implementation method, system and device of IMS interception
US8908665B2 (en) Methods for routing of calls in internet protocol multimedia subsystem centralized services networks and related gateway mobile switching centres (GMSC) and home location registers (HLR)
CN101212386A (zh) 一种电路交换网络与ip多媒体子系统的互通系统
CN1848793A (zh) 一种分组网络互通的方法及其网络系统
WO2009092255A1 (zh) 一种为ims用户提供智能业务的方法、系统和装置
KR20030055417A (ko) Ｉｐ 멀티미디어 서비스 가입자의 이동성 관리를 위한가입자 데이터 관리 장치 및 방법
CN101212387B (zh) 一种电路交换网络与ip多媒体子系统的互通方法
CN101325564B (zh) 一种虚拟媒体网关选择方法、装置及系统
US8804928B2 (en) System and method for allowing virtual private network users to obtain presence status and/or location of others on demand
WO2010075688A1 (zh) Ims集群会议的创建和加入方法、装置及系统
CN109981524B (zh) 用户号码分区接入方法、装置、设备及介质
CN103139745A (zh) 紧急呼叫实现方法、系统及归属网络、拜访网络服务装置
WO2008119302A1 (fr) Système, dispositif et procédé pour traiter un service dans un réseau de domaine de groupe
WO2015070556A1 (zh) 一种利用服务代理器传输信息的方法及服务代理器
WO2001080526A1 (en) Method and system for establishing a communication between a first and a second communication entity
WO2011140712A1 (zh) 一种为非ims终端实现ims共享公共用户标识服务的方法及装置

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: 08871195

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: 08871195

Country of ref document: EP

Kind code of ref document: A1