WO2011060630A1 - 一种多智能业务方法、系统及智能网关 - Google Patents

一种多智能业务方法、系统及智能网关 Download PDF

Info

Publication number
WO2011060630A1
WO2011060630A1 PCT/CN2010/071875 CN2010071875W WO2011060630A1 WO 2011060630 A1 WO2011060630 A1 WO 2011060630A1 CN 2010071875 W CN2010071875 W CN 2010071875W WO 2011060630 A1 WO2011060630 A1 WO 2011060630A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
intelligent
intelligent service
user
scp
Prior art date
Application number
PCT/CN2010/071875
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 中兴通讯股份有限公司
Priority to EP10831046.7A priority Critical patent/EP2490455A4/en
Publication of WO2011060630A1 publication Critical patent/WO2011060630A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q3/00—Selecting arrangements
    • H04Q3/0016—Arrangements providing connection between exchanges
    • H04Q3/0029—Provisions for intelligent networking
    • H04Q3/0045—Provisions for intelligent networking involving hybrid, i.e. a mixture of public and private, or multi-vendor systems

Definitions

  • the present invention relates to a multi-intelligent service method, system and intelligent gateway by introducing an intelligent gateway in an intelligent network system.
  • a Mobile Switching Center (MSC) or a Service Switching Point (SSP) detects an intelligent service request and directly communicates with a Service Control Point (SCP). Complete the triggering of the smart business.
  • MSC Mobile Switching Center
  • SSP Service Switching Point
  • the mobile subscriber subscribes to the Home Location Register (HLR), that is, the CAMEL Subscription Information (CSI) of the customized application of the mobile network enhanced service, including the calling CSI (O). -CSI) and called CSI (T-CSI).
  • the CSI includes information such as a service key and a GT (GLOBAL TITLE) address of the SCP.
  • the service key is used to identify the intelligent service, and the GT address of the SCP is used for signaling to the corresponding SCP.
  • the calling intelligent network service is triggered.
  • the called intelligent network service is triggered.
  • the triggering process is as follows: After obtaining the O-CSI or T-CSI, the MSC sends a start DP message (IDP) to the SCP, and the SCP sends the service control information to the MSC: application charging (AC), request reporting BCSM event (RRBE), and The CONNECT message carries the called subscriber number, and the MSC routes to the end office where the called party is located according to the number. If the called user is idle, the call is made. After the call ends, the MSC reports the Application Accounting Report (ACR) and reports the BCSM Event (ERB) and releases the call.
  • IDCP start DP message
  • AC application charging
  • RRBE request reporting BCSM event
  • the CONNECT message carries the called subscriber number, and the MSC routes to the end office where the called party is located according to the number. If the called user is idle, the call is made. After the call ends, the MSC reports the Application Accounting Report (ACR) and reports the BCSM Event (ERB) and releases the call.
  • ACR Application
  • the triggering of the fixed intelligent network service is to dial a specific access code such as 201 by the user, and then the user inputs the card number and password respectively under the voice prompt, and finally inputs the called number to be dialed to complete an intelligent network service call.
  • the process is as follows: The SSP performs a number analysis on the access code dialed by the user to determine whether the fixed network intelligent service needs to be triggered. If yes, the IDP message is sent to the SCP, and the SCP sends the service control information to the SSP: AC, RRBE, and CONNECT messages, and the CONNECT message carries the called number to be connected.
  • the SSP calls the called party according to this number, and the called party is connected to the idle state. After the call is answered, the calling party is called. After the call ends, the SSP reports ACR and ERB, and then releases the call.
  • the technical problem to be solved by the present invention is to provide a method for realizing multi-intelligent service fusion through an intelligent gateway.
  • the present invention provides a multi-intelligent service method, which introduces an intelligent gateway in an intelligent network system, and the method includes:
  • the smart gateway After receiving the primary intelligent service request of the user sent by the mobile switching center (MSC) or the service switching point (SSP), the smart gateway performs processing according to the service logic, for example, if the user finds that the user also subscribes to the auxiliary intelligent service, the smart device is triggered in turn.
  • the intelligent service is sent to the corresponding service control point (SCP), and after the completion, the service control information is returned to the MSC or the SSP.
  • SCP service control point
  • the method further includes:
  • the smart gateway configures an SCP global code (GT) address in the CSI of the primary intelligent service of the home of the smart gateway in the home location register (HLR) as the smart The GT address of the gateway;
  • GT SCP global code
  • the MSC triggers the primary intelligent service to the intelligent gateway according to the CSI of the primary intelligent service acquired from the HLR.
  • the method further includes:
  • the smart gateway is the SCP corresponding to the primary intelligent service of the home user, and the access code of the primary intelligent service of the home node of the smart gateway is the fixed address in the home location register (SHLR) or the user data center (SDC).
  • SHLR home location register
  • SDC user data center
  • the SSP triggers the primary intelligent industry according to the access code of the primary intelligent service acquired from the SHLR or the SDC. Go to the smart gateway.
  • the smart gateway configures the secondary intelligent service information of the home user in the local database;
  • the checking step is: the smart gateway determines whether the user has a secondary intelligent service by querying the local database, and if yes, the triggering secondary intelligence
  • the method further includes: acquiring a CSI or an access code corresponding to the secondary intelligent service, the secondary intelligent service information that is queried by the intelligent gateway, and the secondary intelligent service information of the mobile network for the mobile user, and the fixed network user It is the auxiliary intelligent business information of the fixed network.
  • the application for charging (AC) of the SCP After the smart gateway triggers the secondary intelligent service to the corresponding SCP, the application for charging (AC) of the SCP, requesting to report the basic call state model (BCSM) event (RRBE), the content and parameters of the CONNECT message are legal. Sex check, if it is legal, monitors the checkpoint (DP), converts the triggered smart service into a specific service prefix according to the service requirement, inserts it into the called number, and then triggers the next secondary intelligent service until all After the secondary intelligent service is processed, the AC, RRBE, and CONNECT messages obtained by sorting the AC, RRBE, and CONNECT messages returned by each SCP according to the service logic are sent to the MSC or the SSP; if not, according to the definition on the smart gateway.
  • AC basic call state model
  • RRBE basic call state model
  • the rule determines whether to continue or terminate the call. If the call is continued, the parameters in the AC, RRBE, and CONNECT messages are modified according to the protocol, and are forwarded to the MSC or the SSP. If the call is terminated, the release call ( ReleaseCALL) message is sent to the MSC or the SSP.
  • ReleaseCALL release call
  • the secondary intelligent service of the user includes a mobile intelligent service
  • the method further includes: after the called party answers, the MSC reports a response event to the smart gateway, and the smart gateway forwards the message to the corresponding SCP, and the calling or called party hangs up, and the MSC only removes the user.
  • the line event is reported to the smart gateway, and the smart gateway forwards the disconnection event report to the corresponding SCP, and the corresponding SCP instructs the smart gateway to release the call, and the smart gateway forwards the release message to the MSC to uniformly process the bill generated by each SCP. Information, and release all resources occupied by the call.
  • the secondary intelligent service of the user includes a fixed network intelligent service.
  • the method further includes: after the called party responds, the SSP reports a response event to the smart gateway, and the smart gateway forwards the message to the corresponding SCP.
  • the SSP reports the user to the user.
  • the smart event is reported to the smart gateway, and the smart gateway forwards the disconnection event report to the corresponding SCP, and the corresponding SCP instructs the smart gateway to release the call, and the smart gateway forwards the release message to the
  • the SSP uniformly processes the charging information generated by each SCP and releases all resources occupied by the call.
  • the present invention also provides a multi-intelligence service system, including a mobile switching center (MSC), a home location register (HLR), and at least one service control point (SCP), and an intelligent gateway connected to the MSC.
  • MSC mobile switching center
  • HLR home location register
  • SCP service control point
  • the smart gateway is configured to: after receiving the primary intelligent service request of the user sent by the MSC, perform processing according to the service logic, for example, if the user finds that the user also subscribes to the mobile network auxiliary intelligent service, and then triggers the secondary intelligent service. After the completion of the SCP, the service control information is returned to the MSC after completion, thereby implementing multi-intelligent service convergence.
  • the HLR is set to: the global code (GT) address of the SCP in the CSI of the primary intelligent service of the home user is the GT address of the smart gateway;
  • GT global code
  • the MSC is configured to: trigger a primary intelligent service to the smart gateway according to a CSI of the primary intelligent service acquired from the HLR;
  • the intelligent gateway is further configured to: process the primary intelligent service as the SCP corresponding to the primary intelligent service of the home user, and configure the mobile secondary intelligent service information of the home user in the local database, and determine whether the user is determined by querying the local database.
  • a supplementary intelligent service is also signed, and if so, the CSI corresponding to the secondary intelligent service of the user is obtained.
  • the present invention also provides a multi-intelligence service system, including a service switching point (SSP), a fixed network home location register (SHLR) or a user data center (SDC) and a service control point (SCP), and an intelligent connection with the SSP.
  • SSP service switching point
  • SHLR fixed network home location register
  • SDC user data center
  • SCP service control point
  • the smart gateway is further connected to the SSP, and the smart gateway is configured to: after receiving the primary intelligent service request of the user sent by the SSP, perform processing according to the service logic, for example, checking that the user also subscribes to the fixed network auxiliary intelligent service. Then, the secondary intelligent service is triggered to the corresponding SCP in turn, and the service control information is returned to the SSP after the completion, thereby implementing multi-intelligent service integration.
  • the access code of the primary intelligent service information of the home gateway of the smart gateway in the SHLR or the SDC is an access code corresponding to the smart gateway;
  • the SSP is configured to: trigger the primary intelligent service to the smart gateway according to an access code of the primary intelligent service acquired from the SHLR or the SDC;
  • the smart gateway is further configured to: as an SCP to the home intelligent service corresponding to the home user
  • the service can be processed, and the fixed network auxiliary intelligent service information of the home user is configured in the local database, and the local database is used to determine whether the user also subscribes to the auxiliary intelligent service, and if so, the corresponding auxiliary intelligent service is acquired.
  • CSI CSI.
  • the invention also provides an intelligent gateway, and the smart gateway is set as:
  • the primary intelligent service After receiving the primary intelligent service request from the user sent by the mobile switching center (MSC), the primary intelligent service requests the client to enhance the service by the MSC according to the mobile network of the primary intelligent service acquired from the home location register (HLR)
  • HLR home location register
  • the user subscription information (CSI) of the application is triggered to the smart gateway; processing is performed according to the service logic, for example, it is found that the user also subscribes to the mobile network auxiliary intelligent service, and then triggers the secondary intelligent service to the corresponding service control point (SCP).
  • SCP service control point
  • the service control information is returned to the MSC, thereby implementing multi-intelligent service convergence.
  • the intelligent gateway is further configured to: process the primary intelligent service as the SCP corresponding to the primary intelligent service of the home user, and configure the mobile secondary intelligent service information of the home user in the local database, and determine whether the user is determined by querying the local database.
  • a supplementary intelligent service is also signed, and if so, the CSI corresponding to the secondary intelligent service of the user is obtained.
  • the intelligent gateway is also connected to the SSP.
  • the intelligent gateway is further configured to: after receiving the primary intelligent service request of the user sent by the service switching point (SSP), perform processing according to the service logic, for example, checking that the user also signs a fixed-line secondary intelligent service, and then sequentially The secondary intelligent service is triggered to the corresponding SCP, and the service control information is returned to the SSP after completion.
  • SSP service switching point
  • the smart gateway is further configured to: process the primary intelligent service as the SCP corresponding to the primary intelligent service of the home user, and configure the fixed-line secondary intelligent service information of the home user in the local database, and determine the user by querying the local database. Whether the contracted auxiliary intelligent service is also signed, and if so, the CSI corresponding to the secondary intelligent service is acquired.
  • the foregoing solution implements multi-intelligent service convergence.
  • it also has one or more of the following technical effects: Since the intelligent gateway introduces an intelligent gateway, an interface between the mobile network and the fixed network is provided on the same device. Realizing the convergence of mobile and fixed-line intelligent services; For multi-intelligent services, all the main intelligent services are processed on the intelligent gateway, and the intelligent gateway completes the triggering of the secondary intelligent services. Work, for the mobile switching center, it only triggers an intelligent service once, and does not need to change the existing triggering process, nor does it need to interact with different SCPs, both small changes and reduced mobile switching centers. The load of the multi-intelligent service All the intelligent billing information is centrally managed in the intelligent gateway.
  • the triggering process is easier to control and facilitates the flexible development of intelligent services.
  • FIG. 1 is a schematic diagram of the composition of an intelligent network system according to an embodiment of the present invention.
  • FIG. 2 is a flowchart of signaling processing on the calling side according to an embodiment of the present invention
  • FIG. 3 is a flowchart of signaling processing on the called side according to an embodiment of the present invention.
  • an intelligent gateway is set in the network, and the smart gateway is a service control point corresponding to the primary intelligent service of the user.
  • the GT address of the SCP in the CSI of the primary intelligent service of the home gateway of the smart gateway is configured as the GT address of the smart gateway;
  • the smart gateway in the SHLR or the SDC The access code of the primary intelligent service of the home user is the access code corresponding to the smart gateway, and the SSP can route the signaling to the smart gateway according to the access code.
  • the secondary smart service information of the home users is stored on the smart gateway, and the secondary smart services may be smart services of the mobile network or the fixed network.
  • the calling party is a mobile intelligent user
  • the called party is a fixed network intelligent user
  • the calling party performs an outbound call called by the No. 7 signaling network.
  • the intelligent network includes MSC, SSP, intelligent gateway SCP-1, HLR, SHLR or SDC, and service control points SCP-2 and SCP-3.
  • the MSC is used to query the CSI by the HLR, or locally query the CSI synchronized by the HLR to the MSC, trigger the mobile primary intelligent service, and route the signaling to the intelligent gateway according to the service key in the CSI of the primary intelligent service and the GT code of the SCP.
  • the SSP is used to query the SHLR or SDC for intelligent information subscribed by the user.
  • the SSP is used to trigger the fixed intelligent service of the fixed network, and performs number analysis and routing according to the access code, and the signaling is routed to the intelligent gateway.
  • the intelligent gateway configures the corresponding service prefix for the called number according to the characteristics of the primary intelligent service, and queries whether the user has other CSI or access codes of the secondary intelligent service, and performs CAP or intelligent network application part with the corresponding SCP (Intelligent Network)
  • the application protocol (INAP) triggers the secondary intelligent service in the order of the secondary intelligent service, and the signaling of the secondary intelligent service is routed to the corresponding SCP, and the SCP is sent to apply for the accounting AC, request to report the BCSM event, After the CONNECT message is connected, the service prefix of the secondary intelligent service is added before the called number, and the next secondary intelligent service is triggered, until all the secondary intelligent services are processed, and the applied accounting AC and the requesting report BCSM event are determined according to the rules. And connect the CONNECT message and instruct the MSC or SSP to make calls and billing. Complete the functions of primary intelligent service processing, secondary intelligent service triggering, centralized monitoring, and accounting.
  • the SCP is used for the control of the secondary intelligent service, and authenticates the calling or called user, and instructs the intelligent gateway to perform calling and charging.
  • the HLR is used to manage and maintain the CSI of mobile users and synchronize them to the MSC.
  • SHLR or SDC is used to manage and maintain the intelligent information of fixed network users and provide user information to the SSP.
  • the MSC and the intelligent gateway interact with each other through the Camel Application Part (CAP) signaling, and interact with the SSP through the No. 7 signaling.
  • the SSP interacts with the intelligent gateway through the intelligent network application procedure INAP signaling.
  • the SCP interacts with the intelligent gateway through INAP or CAP signaling.
  • the HLR interacts with the MSC through Mobile Application Party (MAP) signaling.
  • MAP Mobile Application Party
  • the SHLR and the SSP interact through MAP signaling.
  • the signaling between them is not limited to the No. 7 signal.
  • SCP-n corresponding to the secondary intelligent service of the calling party is SCP-2
  • SCP-n corresponding to the secondary intelligent service of the called is SCP-3 as an example.
  • the processing flow is as follows:
  • Step 1 When the mobile user initiates a call as the calling party, the calling MSC calls the local number.
  • the user data 0-CSI signed by the user is obtained from the library or from the HLR, and includes the service key Skey1 of the main intelligent service and the GT code of the smart gateway.
  • the MSC triggers the primary intelligent network service to the intelligent gateway according to the service keys Skey1 and GT code.
  • Step 2 The MSC triggers the primary intelligent network service to organize and send an IDP (Start DP message) to the intelligent gateway SCP-1 using the CAP protocol, carrying the calling number, the called number, the service key Skey1, and the MSC using the smart gateway SCP-1 GT.
  • IDP Start DP message
  • the code carries the No. 7 signaling route and arrives at the intelligent gateway.
  • Step 3 In the intelligent gateway SCP-1, first query the local database, whether the calling user has other intelligent business information. If not, the intelligent gateway SCP-1 acts as a normal SCP, and performs CAP signaling interaction with the MSC according to the service logic, instructing the MSC to perform connection and charging processing. If the user has the intelligent service information CSI-2, the intelligent gateway SCP-1 converts the corresponding service prefix into the called number according to the service characteristics of Skey1, and then uses the CAP protocol to organize and send the IDP message to SCP-2.
  • the service key in the IDP message is Skey2, and carries the calling number and the called number after the changed number.
  • SCP-2 is routed using SCP-2's GT code signaling route in CSI-2.
  • Step 5 SCP-2 interacts with the intelligent gateway SCP-1 for CAP signaling. After receiving the IDP message, SCP-2 delivers the application accounting AC, requests the report BCSM event RRBE, and connects the CONNECT message to the intelligent gateway SCP-1, which carries the called number that needs to be connected.
  • Step 6 After receiving the AC, RRBE, and CONNECT messages sent by SCP-2, SCP-1 checks the content and format of these messages for legality. If it is not legal, it is decided to continue the call or terminate the call according to the rules defined on SCP-1. If it is legal, it monitors the DP point of the call and modifies the AC, RRBE, and CONNECT messages according to the service logic. If it is not legal, it decides whether to continue or terminate the call according to the rules defined on the intelligent gateway. The protocol modifies the parameters in the AC, RRBE, and CONNECT messages and forwards them to the MSC or SSP. If the call is terminated, the ReleaseCALL message is sent to the MSC.
  • Step 7 After receiving the AC, RRBE, and CONNECT messages sent by the smart gateway SCP-1, the MSC connects the called user according to the number carried in the CONNECT, and sends an Initial Address Message (IAM) message to the SSP.
  • IAM Initial Address Message
  • the intelligent gateway After receiving the legal service control information returned by the secondary intelligent service, if the intelligent gateway detects that there are other secondary intelligent services, it triggers the next secondary intelligent service. When there is no other intelligent service, The AC, RRBE, and CONNECT messages sorted according to the service logic are sent back to the MSC. In this embodiment, since the calling party has only one secondary intelligent service of the mobile network, after receiving the service control information sent by the intelligent gateway SCP-1, the called user is connected.
  • Step 8 The SSP receives the IAM message, applies to the SHLR or SDC for the user data subscribed by the user, and the SHLR or SDC returns the primary intelligent service information registered by the user.
  • the SSP triggers the primary intelligent network service to the intelligent gateway SCP-1 according to the access code.
  • Step 9 Smart Gateway SCP-1 first queries the local database, and whether the called user has other intelligent services. If not, the intelligent gateway SCP-1 acts as a normal SCP and performs INAP signaling interaction with the SSP according to the service flow, instructing the SSP to perform connection and accounting processing. If the user has other intelligent service information, the intelligent gateway SCP-1 needs to first convert the corresponding service prefix into the called number according to the service characteristics of the called user's intelligent service key Skey1, and then use the INAP protocol to organize and send the IDP. Message to SCP-3. The IDP message carries the service key, the calling number, and the called number after the changed number. The access code 3 is used for number analysis signaling routing to reach SCP-3.
  • Step 10 SCP-3 interacts with the intelligent gateway SCP-1 for INAP signaling. After receiving the IDP message, SCP-3 sends the application accounting AC, requests the report BCSM event RRBE, and connects the CONNECT message to the intelligent gateway SCP-1, which carries the called number that needs to be connected.
  • Step 11 After receiving the AC, RRBE, and CONNECT messages sent by SCP-3, SCP-1 needs to check the validity of these messages. If it is not legal, according to the rules defined on SCP-1, decide whether to continue the call or terminate the call; if it is legal, it needs to monitor the DP point and decide whether to modify the AC, RRBE, CONNECT message according to the protocol; if it is not legal and SCP- 1 Decide to terminate the call, send a ReleaseCall message to the SSP, instruct the SSP to tear down the call, and release the resources occupied by the call; if it is not legal, but SCP-1 decides to continue the call, it is determined according to the protocol whether the AC, RRBE, CONNECT message needs to be modified. And sent to the SSP. If there is no other intelligent service, the collated AC, RRBE, and CONNECT messages are sent back to the SSP.
  • Step 12 After receiving the AC, RRBE, and CONNECT messages sent by the SCP-1, the SSP connects the called user according to the number carried in the CONNECT.
  • Step 13 When the called party is idle and starts ringing, the SSP sends an Address Complete Message (ACM) to the MSC.
  • Step 14 When the called party answers, the SSP sends an Answer Message (ANM) to the MSC, and simultaneously sends a BCSM Event Report (BCS, ERB) response message to the intelligent gateway SCP-1.
  • the MSC receives the ANM message and sends an ERB response message to the intelligent gateway SCP-1. The two sides started talking.
  • Step 15 The intelligent gateway SCP-1 forwards the ERB response message sent by the MSC to SCP-2, and forwards the ERB response message sent by the SSP to SCP-3.
  • Step 16 The calling or called user hangs up, the MSC reports the charging report ACR and ERB disconnection message of the calling party to the intelligent gateway SCP-1, and the intelligent gateway SCP-1 modifies the charging report ACR and ERB disconnection message of the calling party.
  • the ReleaseCall message is sent to SCP-2 and SCP-2 to instruct the smart gateway SCP-1 to release the call.
  • the intelligent gateway SCP-1 forwards the ReleaseCall message to the MSC, and comprehensively processes the charging duration on SCP-1 and SCP-2, and releases all the resources requested by the calling party.
  • Step 17 The SSP reports the called charging report ACR and ERB disconnection message to the intelligent gateway SCP-1.
  • the intelligent gateway SCP-1 modifies the called charging report.
  • the ACR and ERB disconnection messages are sent to SCP-3.
  • SCP-3 issues a ReleaseCall message to instruct the intelligent gateway SCP-1 to release the call.
  • the intelligent gateway SCP-1 forwards the ReleaseCall message to the SSP, and comprehensively processes the charging duration on SCP-1 and SCP-3, and releases all the resources requested by the called party.
  • the calling party in this embodiment is a mobile subscriber subscription smart service, which is triggered by the MSC; the called subscriber is a fixed network subscriber contracted intelligent service, which is triggered by the SSP.
  • the calling party may be a mobile or fixed network intelligent user, and the called party may also be a mobile or fixed network intelligent user, and the intelligent service triggering process performs similar processing according to the protocol.
  • the difference is only that the outgoing or incoming processing is not performed, and the paging is directly applied to the called party.
  • the route is routed to the corresponding office, and the process is implemented as described above.
  • the calling side first triggers the intelligent service and then sends the IAM message to the outbound.
  • the called side receives the IAM message and triggers the intelligent service to connect to the called party.
  • the interoffice signaling is not the No. 7 signaling, the corresponding protocol is used according to the protocol used by the connection, such as the Bearer Independent Call Control Protocol (BICC). It will not be repeated here.
  • BICC Bearer Independent Call Control Protocol
  • the technical solution of the present invention provides an interface between the mobile network and the fixed network on the same device, and realizes the integration of the mobile and fixed network intelligent services; for multiple intelligent services, all the main intelligent services are processed on the intelligent gateway,
  • the intelligent gateway completes the triggering of the secondary intelligent service.
  • For the mobile switching center only one intelligent service is triggered, and the existing triggering process does not need to be changed, and there is no need to interact with different SCPs. Small, and reduce the load of the mobile switching center; all intelligent charging information of the intelligent service is centrally managed in the intelligent gateway. Even if the service control point SCP in the existing network cannot be monitored, it can be easily completed in the intelligent gateway. Billing and monitoring functions.

Abstract

本发明公开了一种多智能业务方法，在智能网系统中引入智能网关，智能网关收到移动交换中心（MSC）或业务交换点（SSP）发来的用户的主智能业务请求后根据业务逻辑进行处理，如检查发现该用户还签约有辅智能业务，依次触发辅智能业务到对应的业务控制点（SCP），完成后向所述MSC或SSP返回业务控制信息，从而实现多智能业务融合。本发明还公开了相应系统和智能网关。本发明实现了多智能业务融合，触发流程更易控制，方便智能业务的灵活发展。

Description

一种多智能业务方法、 系统及智能网关
技术领域
本发明涉及一种在智能网系统中通过引入智能网关来实现多智能业务方 法、 系统及智能网关。
背景技术
对于传统的智能网系统， 移动交换中心 (Mobile Switching Center, MSC)或 者业务交换点 (Service Switching Point, SSP)检测出智能业务请求， 就直接和业 务控制点 (Service Control Point, SCP)进行通信， 完成智能业务的触发。
在移动智能网系统中， 移动用户在归属位置寄存器 (Home Location Register, HLR)上签约， 即移动网络增强业务的客户化应用的用户签约信息 (CAMEL Subscription Information , CSI) , 包括主叫 CSI(O-CSI)和被叫 CSI(T-CSI)。 其中， CSI中包括业务键和 SCP的 GT(GLOBAL TITLE)地址等 信息，业务键用来标识智能业务， SCP的 GT地址用于信令路由到对应的 SCP。 当用户签约 0-CSI并作为主叫用户拨打其他被叫用户， 就会触发主叫智能网 业务； 当用户签约 T-CSI并作为被叫用户时， 就会触发被叫智能网业务。 触 发的流程如下： MSC获取到 O-CSI或者 T-CSI后， 发送启动 DP消息 (IDP) 给 SCP, SCP给 MSC回送业务控制信息： 申请计费 (AC)、 请求报告 BCSM 事件 (RRBE)和连接 (CONNECT)消息， CONNECT 消息中携带了被叫用户号 码， MSC会按照这个号码路由到被叫所在的端局。如果被叫用户空闲就接续， 主被叫通话。 通话结束后 MSC上报申请计费报告 (ACR)和报告 BCSM事件 (ERB)并释放呼叫。
固定智能网业务的触发是通过用户拨打特定的接入码比如 201 , 然后用 户在语音提示下分别输入卡号、 密码， 最后输入所需拨打的被叫号码完成一 次智能网业务呼叫。 其流程如下： SSP通过对用户拨打的接入码进行号码分 析， 判断是否需要触发固网智能业务。 是， 则发送 IDP消息到 SCP, SCP给 SSP下发业务控制信息： AC、 RRBE和 CONNECT消息， CONNECT消息中 携带需接续的被叫号码。 SSP按照此号码呼叫被叫， 被叫空闲状态下接续成 功， 被叫应答后， 主被叫通话。 通话结束后 SSP上报 ACR和 ERB, 然后释 放呼叫。
随着智能业务的发展，固网和移动网多智能业务的融合需求越来越普遍。 但 MSC和传统的 SSP均无法提供移动多智能业务和固定多智能业务的融合 处理， 并且由于目前现网中的 SCP设备很多比较陈旧， 无法满足集中计费和 监控的要求， 不利于业务的灵活处理和发展。 发明内容
本发明要解决的技术问题是提供一种通过智能网关实现多智能业务融合 的方法。
为了解决上述问题， 本发明提供了一种多智能业务方法， 在智能网系统 中引入智能网关， 该方法包括：
所述智能网关收到移动交换中心 (MSC)或业务交换点 (SSP)发来的用户的 主智能业务请求后根据业务逻辑进行处理， 如检查发现该用户还签约有辅智 能业务，依次触发辅智能业务到对应的业务控制点 (SCP),完成后向所述 MSC 或 SSP返回业务控制信息，
从而实现多智能业务融合。
接收所述主智能业务请求前， 该方法还包括：
所述智能网关作为其归属用户主智能业务对应的 SCP, 在归属位置寄存 器 (HLR)中将所述智能网关归属用户的主智能业务的 CSI 中的 SCP全局码 (GT)地址配置为所述智能网关的 GT地址；
所述的 MSC根据从 HLR获取的主智能业务的 CSI, 触发主智能业务到 所述智能网关。
接收所述主智能业务请求前， 该方法还包括：
所述智能网关作为其归属用户主智能业务对应的 SCP, 在固网位置归属 寄存器 (SHLR)或用户数据中心 (SDC)中， 所述智能网关归属用户的主智能业 务的接入码为所述智能网关对应的接入码；
所述 SSP根据从 SHLR或 SDC获取的主智能业务的接入码触发主智能业 务到所述智能网关。
所述智能网关在本地数据库中配置有归属用户的辅智能业务信息； 所述检查步骤为： 所述智能网关通过查询本地数据库判断所述用户是否 有辅智能业务， 如果有， 所述触发辅智能业务步骤前， 该方法还包括： 获取 所述辅智能业务对应的 CSI或者接入码， 所述智能网关查询的辅智能业务信 息， 对于移动用户是移动网的辅智能业务信息， 对于固网用户是固网的辅智 能业务信息。
所述智能网关触发辅智能业务到对应的 SCP后，对 SCP返回的申请计费 (AC), 请求报告基本呼叫状态模型 (BCSM)事件 (RRBE)、 连接 (CONNECT)消 息的内容和参数进行合法性检查， 如果合法， 则监控检出点 (DP), 将已经触 发过的智能业务根据业务要求转化成特定的业务前缀， 插到被叫号码前， 再 触发下一个辅智能业务， 直至所有的辅智能业务都处理完， 将根据业务逻辑 对各 SCP返回的 AC、 RRBE、 CONNECT消息进行整理后得到的 AC、 RRBE、 CONNECT消息发送给 MSC或 SSP; 如果不合法， 则根据智能网关上定义的 规则决定继续呼叫还是终止呼叫， 若继续呼叫则根据协议修改 AC、 RRBE、 CONNECT消息中的参数， 转发给 MSC或 SSP, 若终止呼叫， 则下发释放呼 叫 ( ReleaseCALL ) 消息给 MSC或 SSP。
所述用户的辅智能业务包括移动智能业务，
该方法还包括： 所述被叫应答后， 所述 MSC上报应答事件给所述智能网 关， 所述智能网关转发此消息给对应的 SCP, 主叫或被叫挂机后， MSC上才艮 用户拆线事件报告给智能网关， 所述智能网关转发该拆线事件报告给对应的 SCP, 相应 SCP指示所述智能网关释放呼叫， 所述智能网关转发释放消息给 MSC, 统一处理各 SCP产生的计费信息， 并释放该呼叫占用的所有资源。
所述用户的辅智能业务包括固网智能业务，
该方法还包括： 所述被叫应答后， 所述 SSP上报应答事件给所述智能网 关， 所述智能网关转发此消息给对应的 SCP, 主叫或被叫挂机后， 所述 SSP 上报用户拆线事件报告给所述智能网关， 所述智能网关转发该拆线事件报告 给对应的 SCP, 相应 SCP指示智能网关释放呼叫， 智能网关转发释放消息给 所述 SSP,统一处理各 SCP产生的计费信息，并释放该呼叫占用的所有资源。 本发明还提供了一种实现多智能业务系统， 包括移动交换中心 (MSC)、 归属位置寄存器 (HLR)和至少一个业务控制点 (SCP),以及与 MSC连接的智能 网关，
所述智能网关设置为： 在收到所述 MSC发来的用户的主智能业务请求 后， 根据业务逻辑进行处理， 如检查发现该用户还签约有移动网辅智能业务， 再依次触发辅智能业务到对应的 SCP, 完成后向所述 MSC返回业务控制信 息， 从而实现多智能业务融合。
所述 HLR设置为：其归属用户的主智能业务的 CSI中 SCP的全局码 (GT) 地址为所述智能网关的 GT地址；
所述 MSC设置为： 根据从 HLR获取的主智能业务的 CSI, 触发主智能 业务到所述智能网关；
所述智能网关还设置为： 作为其归属用户主智能业务对应的 SCP对主智 能业务进行处理，且在本地数据库中配置有归属用户的移动辅智能业务信息， 通过查询本地数据库判断所述用户是否还签约有辅智能业务， 如果有， 再获 取所述用户的辅智能业务对应的 CSI。
本发明还提供了一种实现多智能业务系统， 包括业务交换点 (SSP), 固网 归属位置寄存器 (SHLR)或用户数据中心 (SDC)和业务控制点 (SCP), 以及与 SSP连接的智能网关，
所述智能网关还与 SSP相连， 所述智能网关设置为： 在收到 SSP发来的 用户的主智能业务请求后， 根据业务逻辑进行处理， 如检查发现该用户还签 约有固网辅智能业务， 再依次触发辅智能业务到对应的 SCP, 完成后向所述 SSP返回业务控制信息， 从而实现多智能业务融合。
所述 SHLR或 SDC中所述智能网关归属用户的主智能业务信息的接入码 为智能网关对应的接入码；
所述 SSP设置为：根据从 SHLR或 SDC获取的主智能业务的接入码触发 主智能业务到所述智能网关；
所述智能网关还设置为： 作为其归属用户主智能业务对应的 SCP对主智 能业务进行处理，且在本地数据库中配置有归属用户的固网辅智能业务信息， 通过查询本地数据库判断所述用户是否还签约有辅智能业务， 如果有， 再获 取所述辅智能业务对应的 CSI。 本发明还提供了一种智能网关， 所述智能网关设置为：
在收到移动交换中心 (MSC)发来的用户的主智能业务请求后， 所述主智 能业务请求由所述 MSC根据从归属位置寄存器 (HLR)获取的主智能业务的移 动网络增强业务的客户化应用的用户签约信息 （CSI )触发到所述智能网关； 根据业务逻辑进行处理，如检查发现该用户还签约有移动网辅智能业务， 再依次触发辅智能业务到对应的业务控制点 (SCP), 完成后向所述 MSC返回 业务控制信息， 从而实现多智能业务融合。
所述智能网关还设置为： 作为其归属用户主智能业务对应的 SCP对主智 能业务进行处理，且在本地数据库中配置有归属用户的移动辅智能业务信息， 通过查询本地数据库判断所述用户是否还签约有辅智能业务， 如果有， 再获 取所述用户的辅智能业务对应的 CSI。
所述智能网关还与 SSP相连，
所述智能网关还设置为： 在收到业务交换点 (SSP)发来的用户的主智能业 务请求后， 根据业务逻辑进行处理， 如检查发现该用户还签约有固网辅智能 业务， 再依次触发辅智能业务到对应的 SCP, 完成后向所述 SSP返回业务控 制信息。
所述智能网关还设置为： 作为其归属用户主智能业务对应的 SCP对主智 能业务进行处理 ,且在本地数据库中配置有归属用户的固网辅智能业务信息 , 通过查询本地数据库判断所述用户是否还签约有辅智能业务， 如果有， 再获 取所述辅智能业务对应的 CSI。
上述方案实现了多智能业务融合， 在一些实施例中， 还具有以下的一个 或多个技术效果： 由于该智能网中引入了智能网关， 在同一设备上提供了对 移动网和固网的接口， 实现了移动和固网智能业务的融合； 对多智能业务， 所有的主智能业务均在智能网关上处理， 由智能网关完成辅智能业务的触发 工作， 对移动交换中心来说， 实际上只触发了一次智能业务， 并且不需要改 变现有的触发流程， 也不需要跟不同的 SCP进行交互， 既做到改动小， 又减 轻了移动交换中心的负荷； 多智能业务所有的智能计费信息都在智能网关进 行集中管理， 即使现网中业务控制点 SCP陈旧无法实现监控， 也可以轻松的 在智能网关统一完成计费和监控功能。 因此对多智能业务融合的情况， 触发 流程更易控制， 方便智能业务的灵活发展。
附图概述
图 1是本发明实施例的智能网系统组成示意图；
图 2是本发明实施例主叫侧的信令处理流程图；
图 3是本发明实施例被叫侧的信令处理流程图。
本发明的较佳实施方式
下面通过具体的实施例并结合附图对本发明作进一步详细的描述。
相对现有技术， 本实施例在网络中设置智能网关， 该智能网关为其归属 用户主智能业务对应的业务控制点。 具体地， 对移动网智能业务， 将 HLR中 该智能网关归属用户的主智能业务的 CSI中 SCP的 GT地址配置为该智能网 关的 GT地址； 对固网智能业务， SHLR或 SDC中该智能网关归属用户的主 智能业务的接入码为该智能网关对应的接入码， SSP可以根据该接入码将信 令路由到智能网关。 另外， 在智能网关上存储了归属用户的辅智能业务信息， 这些辅智能业务可以是移动网和或固网的智能业务。
本实施例是以主叫是移动智能用户， 被叫是固网智能用户， 主叫通过 7 号信令网进行出局呼叫被叫的情况加以说明的。
如图 1所示， 智能网包括 MSC、 SSP, 智能网关 SCP-1、 HLR, SHLR或 SDC、 以及业务控制点 SCP-2、 SCP-3。
其中， MSC用于到 HLR查询 CSI, 或者本地查询由 HLR同步到 MSC 的 CSI, 触发移动主智能业务， 根据主智能业务的 CSI中的业务键和 SCP的 GT码将信令路由到智能网关。 SSP用于到 SHLR或 SDC查询用户签约的智能信息。 SSP用于触发固网 主智能业务， 根据接入码进行号码分析选路， 信令路由到智能网关。
智能网关根据主智能业务特性为被叫号码配置相应的业务前缀， 同时查 询用户是否还有其他辅智能业务的 CSI或者接入码， 与对应的 SCP之间进行 CAP或智能网络应用部分（ Intelligent Network Application Protocol , INAP ) 信令交互， 按辅智能业务的顺序依次触发辅智能业务， 将辅智能业务的信令 路由到对应的 SCP, 收到该 SCP下发申请计费 AC、 请求报告 BCSM事件、 连接 CONNECT消息后， 在被叫号码前添加该辅智能业务的业务前缀， 再触 发下一个辅智能业务， 直到所有辅智能业务处理完成， 根据规则决定修改得 到的申请计费 AC、 请求报告 BCSM事件， 以及连接 CONNECT消息， 并指 示 MSC或 SSP进行呼叫和计费。 完成主智能业务处理、 辅智能业务触发、 集中监控和计费的功能。
SCP用于辅智能业务的控制， 对主叫或者被叫用户进行鉴权， 指示智能 网关进行呼叫和计费。
HLR用于管理和维护移动用户的 CSI, 并将其同步到 MSC。
SHLR或 SDC用于管理和维护固网用户的智能信息， 并向 SSP提供用户 信息。
上述各个设备之间交互时， MSC与智能网关之间通过 Camel应用部分 ( CAP )信令交互， 与 SSP之间通过 7号信令交互。 SSP与智能网关之间通 过智能网应用规程 INAP信令交互。 SCP与智能网关之间通过 INAP或者 CAP 信令交互。 HLR与 MSC之间通过移动应用部分 (Mobile Application Party, MAP) 信令交互。 SHLR与 SSP之间通过 MAP信令交互。 不过对于 MSC和 SSP之 间通过 IP网络连接或经过他局转接的情况， 其间的信令不仅仅局限于 7号信 令。
如图 2和图 3所示， 以主叫的辅智能业务对应的 SCP-n为 SCP-2, 被叫 的辅智能业务对应的 SCP-n为 SCP-3为例， 对多智能业务融合触发的处理流 程如下：
步骤 1 : 当移动用户作为主叫发起呼叫时， 主叫所在的 MSC调用本地数 据库或从 HLR获取该用户签约的用户数据 0-CSI, 包含主智能业务的业务键 Skeyl和智能网关的 GT码。 MSC根据业务键 Skeyl和 GT码触发主智能网业 务到智能网关。
步骤 2: MSC触发主智能网业务使用 CAP协议组织并发送 IDP (启动 DP 消息)给智能网关 SCP-1 , 携带主叫号码、 被叫号码、 业务键 Skeyl , MSC使 用智能网关 SCP-1的 GT码进行 7号信令路由， 到达智能网关。
步骤 3: 在智能网关 SCP-1 中， 先查询本地数据库， 是否主叫用户还有 其他的智能业务信息。 如果没有， 则智能网关 SCP-1就作为普通的 SCP, 根 据业务逻辑与 MSC进行 CAP信令交互， 指示 MSC进行连接和计费等处理。 如果用户还有智能业务信息 CSI-2,则智能网关 SCP-1根据 Skeyl的业务特性 转化为相应的业务前缀插入到被叫号码前， 再使用 CAP协议组织并发送 IDP 消息给 SCP-2。 IDP消息中的业务键为 Skey2, 同时携带主叫号码和改号后的 被叫号码。 使用 CSI-2中的 SCP-2的 GT码信令路由到达 SCP-2。
步骤 5: SCP-2与智能网关 SCP-1进行 CAP信令交互。 SCP-2收到 IDP 消息后，下发申请计费 AC、请求报告 BCSM事件 RRBE,以及连接 CONNECT 消息给智能网关 SCP-1 , CONNECT中携带需要接续的被叫号码。
步骤 6: 智能网关 SCP-1收到 SCP-2发送过来的 AC、 RRBE, CONNECT 消息后，对这些消息的内容和格式进行合法性检查。如果不合法，根据 SCP-1 上定义的规则， 决定是继续呼叫， 还是终止呼叫。 如果合法， 则对呼叫的 DP 点进行监控， 同时根据业务逻辑对 AC、 RRBE, CONNECT消息进行修改； 如果不合法，则根据智能网关上定义的规则决定继续呼叫还是终止呼叫， 若继续呼叫则根据协议修改 AC、 RRBE, CONNECT消息中的参数， 转发给 MSC或 SSP, 若终止呼叫， 则下发 ReleaseCALL消息给 MSC。
步骤 7: MSC在收到智能网关 SCP-1发过来的 AC、 RRBE, CONNECT 消息后， 根据 CONNECT 中携带的号码接续被叫用户， 发送初始地址消息 ( Initial Address Message, IAM ) 消息给 SSP。
智能网关收到一个辅智能业务返回的合法业务控制信息后， 如检查发现 还有其他辅智能业务， 则触发下一辅智能业务， 当没有其他智能业务时， 将 根据业务逻辑整理后的 AC、 RRBE、 CONNECT消息回送给 MSC。 本实施例 因为主叫只有一项移动网的辅智能业务， 因此收到智能网关 SCP-1发过来的 业务控制信息后， 即接续被叫用户。
步骤 8: SSP收到 IAM消息， 向 SHLR或 SDC申请该用户签约的用户 数据， SHLR或 SDC返回用户注册的主智能业务信息。 SSP根据接入码触发 主智能网业务到智能网关 SCP-1。
步骤 9: 智能网关 SCP-1先查询本地数据库， 是否被叫用户还有其他的 智能业务。 如果没有， 则智能网关 SCP-1就作为普通的 SCP, 按照业务流程 与 SSP进行 INAP信令交互， 指示 SSP进行连接和计费等处理。 如果用户还 有其他智能业务信息， 则智能网关 SCP-1 需要先根据被叫用户智能业务键 Skeyl的业务特性， 转化为相应的业务前缀插到被叫号码前， 再使用 INAP协 议组织并发送 IDP消息给 SCP-3。 IDP消息中携带业务键、 主叫号码和改号 后的被叫号码。 使用接入码 3进行号码分析信令路由到达 SCP-3。
步骤 10: SCP-3与智能网关 SCP-1进行 INAP信令交互。 SCP-3收到 IDP 消息后，下发申请计费 AC、请求报告 BCSM事件 RRBE,以及连接 CONNECT 消息给智能网关 SCP-1 , CONNECT中携带需要接续的被叫号码。
步骤 11 :智能网关 SCP-1收到 SCP-3发送过来的 AC、 RRBE, CONNECT 消息后， 需要对这些消息进行合法性检查。 如果不合法， 根据 SCP-1上定义 的规则， 决定是继续呼叫， 还是终止呼叫； 如果合法， 需要监控 DP点， 同 时根据协议决定是否需要修改 AC、 RRBE, CONNECT消息； 如果不合法且 SCP-1决定终止呼叫， 向 SSP发送 ReleaseCall消息， 指示 SSP拆除呼叫， 并 释放该呼叫占用的资源； 如果不合法， 但 SCP-1决定继续呼叫， 则根据协议 决定是否需要修改 AC、 RRBE, CONNECT消息， 并发送给 SSP。 如果没有 其他智能业务， 将整理后的 AC、 RRBE, CONNECT消息回送给 SSP。
步骤 12: SSP在收到智能网关 SCP-1发过来的 AC、 RRBE, CONNECT 消息后， 根据 CONNECT中携带的号码接续被叫用户。
步骤 13：当被叫空闲并开始振铃时， SSP向 MSC发送地址全消息 (Address Complete Message, ACM)。 步骤 14: 当被叫应答时 SSP向 MSC发送应答消息 (Answer Message, ANM), 同时向智能网关 SCP-1发送 BCSM事件报告 ( Event Report BCSM, ERB )应答消息。 MSC收到 ANM消息，发送 ERB应答消息给智能网关 SCP-1。 双方开始通话。
步骤 15: 智能网关 SCP-1转发 MSC发送来的 ERB应答消息给 SCP-2, 转发 SSP发送来的 ERB应答消息给 SCP-3。
步骤 16: 主叫或者被叫用户挂机， MSC上报主叫的计费报告 ACR、 ERB 拆线消息给智能网关 SCP-1 ,智能网关 SCP-1修改主叫的计费报告 ACR、 ERB 拆线消息给 SCP-2, SCP-2下发 ReleaseCall消息指示智能网关 SCP-1释放呼 叫。智能网关 SCP-1转发 ReleaseCall消息给 MSC, 综合处理 SCP-1和 SCP-2 上的计费时长， 并释放本次呼叫为主叫侧申请的所有资源。
步骤 17: SSP 上报被叫的计费报告 ACR、 ERB 拆线消息给智能网关 SCP-1。 智能网关 SCP-1修改被叫的计费报告 ACR、 ERB拆线消息给 SCP-3 , SCP-3下发 ReleaseCall消息指示智能网关 SCP-1释放呼叫。 智能网关 SCP-1 转发 ReleaseCall消息给 SSP, 综合处理 SCP-1和 SCP-3上的计费时长， 并释 放本次呼叫为被叫侧申请的所有资源。
以上所述的步骤 16和步骤 17之间不局限于某种固定的先后顺序。
本实施例的主叫为移动用户签约智能业务， 以 MSC来触发； 被叫为固网 用户签约智能业务， 以 SSP来触发。 在其他的实施例中， 主叫可以是移动或 固网智能用户， 被叫也可以是移动或固网智能用户， 智能业务触发流程依据 协议进行类似处理。 对于局内呼叫， 差别仅在于不进行出局或入局处理， 直 接对被叫下寻呼 (Paging); 对于网内和网外呼叫依据号码分析， 路由到相应的 局点， 其流程与上面所述实施例类似， 主叫侧先触发智能业务再发送 IAM消 息出局， 被叫侧收到 IAM消息触发智能业务再接续被叫。 若局间信令不是 7 号信令， 则依据连接所釆用的协议如与承载无关的呼叫控制协议 （Bearer Independent Call Control protocol, BICC )进行相应的处理。 在此不再加以累 述。 这些相应的改变和变形都应该属于本发明所附的权利要求的保护范围。 工业实用性
本发明的技术方案， 在同一设备上提供了对移动网和固网的接口， 实现 了移动和固网智能业务的融合； 对多智能业务， 所有的主智能业务均在智能 网关上处理， 由智能网关完成辅智能业务的触发工作， 对移动交换中心来说， 实际上只触发了一次智能业务， 并且不需要改变现有的触发流程， 也不需要 跟不同的 SCP进行交互， 既做到改动小， 又减轻了移动交换中心的负荷； 多 智能业务所有的智能计费信息都在智能网关进行集中管理， 即使现网中业务 控制点 SCP陈旧无法实现监控， 也可以轻松的在智能网关统一完成计费和监 控功能。

Claims

权 利 要 求 书
1、 一种多智能业务方法， 其特征在于， 在智能网系统中引入智能网关， 该方法包括：
所述智能网关收到移动交换中心 (MSC)或业务交换点 (SSP)发来的用户的 主智能业务请求后根据业务逻辑进行处理， 如检查发现该用户还签约有辅智 能业务，依次触发辅智能业务到对应的业务控制点 (SCP),完成后向所述 MSC 或 SSP返回业务控制信息，
从而实现多智能业务融合。
2、 如权利要求 1所述的多智能业务方法， 其中， 接收所述主智能业务请 求前， 该方法还包括：
所述智能网关作为其归属用户主智能业务对应的 SCP, 在归属位置寄存 器 (HLR)中将所述智能网关归属用户的主智能业务的移动网络增强业务的客 户化应用的用户签约信息 (CSI)中的 SCP全局码 (GT)地址配置为所述智能网 关的 GT地址；
所述的 MSC根据从 HLR获取的主智能业务的 CSI, 触发主智能业务到 所述智能网关。
3、 如权利要求 1或 2所述的多智能业务方法， 其中， 接收所述主智能业 务请求前， 该方法还包括：
所述智能网关作为其归属用户主智能业务对应的 SCP, 在固网位置归属 寄存器 (SHLR)或用户数据中心 (SDC)中， 所述智能网关归属用户的主智能业 务的接入码为所述智能网关对应的接入码；
所述 SSP根据从 SHLR或 SDC获取的主智能业务的接入码触发主智能业 务到所述智能网关。
4、 如权利要求 2所述的多智能业务方法， 其中，
所述智能网关在本地数据库中配置有归属用户的辅智能业务信息； 所述检查步骤为： 所述智能网关通过查询本地数据库判断所述用户是否 还签约有辅智能业务，
如果有， 所述触发辅智能业务步骤前， 该方法还包括： 获取所述辅智能 业务对应的 CSI或者接入码， 所述智能网关查询的辅智能业务信息， 对于移 动用户是移动网的辅智能业务信息，对于固网用户是固网的辅智能业务信息。
5、 如权利要求 1所述的多智能业务方法， 其还包括，
所述智能网关触发辅智能业务到对应的 SCP后，对 SCP返回的申请计费 (AC), 请求报告基本呼叫状态模型 (BCSM)事件 (RRBE)、 连接 (CONNECT)消 息的内容和参数进行合法性检查， 如果合法， 则监控检出点 (DP), 将已经触 发过的智能业务根据业务要求转化成特定的业务前缀， 插到被叫号码前， 再 触发下一个辅智能业务， 直至所有的辅智能业务都处理完， 将根据业务逻辑 对各 SCP返回的 AC、 RRBE、 CONNECT消息进行整理后得到的 AC、 RRBE、 CONNECT消息发送给 MSC或 SSP; 如果不合法， 则根据智能网关上定义的 规则决定继续呼叫还是终止呼叫， 若继续呼叫则根据协议修改 AC、 RRBE、 CONNECT消息中的参数， 转发给 MSC或 SSP, 若终止呼叫， 则下发释放呼 叫 ( ReleaseCALL ) 消息给 MSC或 SSP。
6、 如权利要求 1所述的多智能业务方法， 其中，
所述用户的辅智能业务包括移动智能业务，
该方法还包括： 所述被叫应答后， 所述 MSC上报应答事件给所述智能网 关， 所述智能网关转发此消息给对应的 SCP, 主叫或被叫挂机后， MSC上才艮 用户拆线事件报告给智能网关， 所述智能网关转发该拆线事件报告给对应的 SCP, 相应 SCP指示所述智能网关释放呼叫， 所述智能网关转发释放消息给 MSC, 统一处理各 SCP产生的计费信息， 并释放该呼叫占用的所有资源。
7、 如权利要求 1或 6所述的多智能业务方法， 其中，
所述用户的辅智能业务包括固网智能业务，
该方法还包括： 所述被叫应答后， 所述 SSP上报应答事件给所述智能网 关， 所述智能网关转发此消息给对应的 SCP, 主叫或被叫挂机后， 所述 SSP 上报用户拆线事件报告给所述智能网关， 所述智能网关转发该拆线事件报告 给对应的 SCP, 相应 SCP指示智能网关释放呼叫， 智能网关转发释放消息给 所述 SSP,统一处理各 SCP产生的计费信息，并释放该呼叫占用的所有资源。
8、 一种实现多智能业务系统， 包括移动交换中心 (MSC)、 归属位置寄存 器 (HLR)和至少一个业务控制点 (SCP), 以及与 MSC连接的智能网关： 所述智能网关设置为： 在收到所述 MSC发来的用户的主智能业务请求 后， 根据业务逻辑进行处理， 如检查发现该用户还签约有移动网辅智能业务， 再依次触发辅智能业务到对应的 SCP, 完成后向所述 MSC返回业务控制信 息， 从而实现多智能业务融合。
9、 如权利要求 8所述的实现多智能业务系统， 其中，
所述 HLR设置为：其归属用户的主智能业务的移动网络增强业务的客户 化应用的用户签约信息 (CSI)中 SCP的全局码 (GT)地址为所述智能网关的 GT 地址；
所述 MSC设置为： 根据从 HLR获取的主智能业务的 CSI, 触发主智能 业务到所述智能网关；
所述智能网关还设置为： 作为其归属用户主智能业务对应的 SCP对主智 能业务进行处理，且在本地数据库中配置有归属用户的移动辅智能业务信息， 通过查询本地数据库判断所述用户是否还签约有辅智能业务， 如果有， 再获 取所述用户的辅智能业务对应的 CSI。
10、 一种实现多智能业务系统， 包括业务交换点 (SSP), 固网归属位置寄 存器 (SHLR)或用户数据中心 (SDC)和业务控制点 (SCP), 以及与 SSP连接的智 能网关，
所述智能网关还与 SSP相连， 所述智能网关设置为： 在收到 SSP发来的 用户的主智能业务请求后， 根据业务逻辑进行处理， 如检查发现该用户还签 约有固网辅智能业务， 再依次触发辅智能业务到对应的 SCP, 完成后向所述 SSP返回业务控制信息， 从而实现多智能业务融合。
11、 如权利要求 10所述的实现多智能业务系统， 其中，
所述 SHLR或 SDC中所述智能网关归属用户的主智能业务信息的接入码 为智能网关对应的接入码；
所述 SSP设置为：根据从 SHLR或 SDC获取的主智能业务的接入码触发 主智能业务到所述智能网关；
所述智能网关还设置为： 作为其归属用户主智能业务对应的 SCP对主智 能业务进行处理 ,且在本地数据库中配置有归属用户的固网辅智能业务信息 , 通过查询本地数据库判断所述用户是否还签约有辅智能业务， 如果有， 再获 取所述辅智能业务对应的移动网络增强业务的客户化应用的用户签约信息
( CSI ) 。
12、 一种智能网关， 所述智能网关设置为：
在收到移动交换中心 (MSC)发来的用户的主智能业务请求后， 所述主智 能业务请求由所述 MSC根据从归属位置寄存器 (HLR)获取的主智能业务的移 动网络增强业务的客户化应用的用户签约信息 （CSI )触发到所述智能网关； 根据业务逻辑进行处理，如检查发现该用户还签约有移动网辅智能业务， 再依次触发辅智能业务到对应的业务控制点 (SCP), 完成后向所述 MSC返回 业务控制信息， 从而实现多智能业务融合。
13、 如权利要求 12所述的智能网关， 所述智能网关还设置为： 作为其归 属用户主智能业务对应的 SCP对主智能业务进行处理， 且在本地数据库中配 置有归属用户的移动辅智能业务信息， 通过查询本地数据库判断所述用户是 否还签约有辅智能业务， 如果有， 再获取所述用户的辅智能业务对应的 CSI。
14、 如权利要求 12所述的智能网关， 所述智能网关还与 SSP相连， 所述智能网关还设置为： 在收到业务交换点 (SSP)发来的用户的主智能业 务请求后， 根据业务逻辑进行处理， 如检查发现该用户还签约有固网辅智能 业务， 再依次触发辅智能业务到对应的 SCP, 完成后向所述 SSP返回业务控 制信息。
15、 如权利要求 14所述的智能网关， 所述智能网关还设置为： 作为其归 属用户主智能业务对应的 SCP对主智能业务进行处理， 且在本地数据库中配 置有归属用户的固网辅智能业务信息， 通过查询本地数据库判断所述用户是 否还签约有辅智能业务， 如果有， 再获取所述辅智能业务对应的 CSI。
PCT/CN2010/071875 2009-11-17 2010-04-19 一种多智能业务方法、系统及智能网关 WO2011060630A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP10831046.7A EP2490455A4 (en) 2009-11-17 2010-04-19 PROCESS, SYSTEM AND INTELLIGENT GATEWAY FOR MULTIPLE INTELLIGENT SERVICES

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200910224323.8 2009-11-17
CN2009102243238A CN101729930B (zh) 2009-11-17 2009-11-17 一种通过智能网网关来实现多智能业务融合的方法

Publications (1)

Publication Number Publication Date
WO2011060630A1 true WO2011060630A1 (zh) 2011-05-26

Family

ID=42449989

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/071875 WO2011060630A1 (zh) 2009-11-17 2010-04-19 一种多智能业务方法、系统及智能网关

Country Status (3)

Country Link
EP (1) EP2490455A4 (zh)
CN (1) CN101729930B (zh)
WO (1) WO2011060630A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20150056847A (ko) * 2012-09-17 2015-05-27 질랜드 파마 에이/에스 글루카곤 유사체

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101924789B (zh) * 2010-07-27 2014-03-19 中兴通讯股份有限公司 一种实现不同类型业务嵌套的方法和系统
CN102547484A (zh) * 2010-12-31 2012-07-04 中国移动通信集团浙江有限公司 一种智能网业务嵌套的方法、系统及业务代理装置
CN102082975B (zh) * 2011-03-04 2013-08-28 创博亚太科技（山东）有限公司 一种支持多智能网业务的业务控制点scp网关方法
CN110941220A (zh) * 2019-12-19 2020-03-31 重庆壹城桥慧科技有限公司 一种基于集中网关的中心管理系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1558694A (zh) * 2004-01-14 2004-12-29 得实信息科技(北京)有限公司 预付费用户在两种异构网络之间的国际漫游的实现方法
EP1111945B1 (en) * 1999-12-22 2005-10-19 Star Home GmbH System and methods for global access to services for mobile telephone subscribers
CN1956424A (zh) * 2005-10-26 2007-05-02 德赛电子(惠州)有限公司 基于分布式网关的通信方法及应用
CN1996971A (zh) * 2006-12-14 2007-07-11 华为技术有限公司 虚拟媒体网关优化接网的方法及系统
CN101227729A (zh) * 2008-01-29 2008-07-23 侯万春 实现移动电话自动租用漫游地电话号码的方法

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR2773656B1 (fr) * 1998-01-15 2000-02-11 Alsthom Cge Alcatel Passerelle intelligente entre un point de controle de service, et un reseau de signalisation
RU2311741C2 (ru) * 2001-12-21 2007-11-27 Ориндж Персонал Коммьюникейшнз Сервисиз Лимитед Обработка вызова в мобильных телекоммуникационных сетях
WO2004103012A1 (en) * 2003-05-19 2004-11-25 Siemens Aktiengesellschaft Method and means for handling multiple services of an intelligent network within a mobile communication network
CN1882108A (zh) * 2005-07-29 2006-12-20 华为技术有限公司 一种触发智能业务的方法及通信系统
CN101341764B (zh) * 2005-12-16 2012-09-05 艾利森电话股份有限公司 智能网服务
CN101370309B (zh) * 2008-09-24 2012-09-05 中兴通讯股份有限公司 智能网及其触发移动智能网业务应用的方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1111945B1 (en) * 1999-12-22 2005-10-19 Star Home GmbH System and methods for global access to services for mobile telephone subscribers
CN1558694A (zh) * 2004-01-14 2004-12-29 得实信息科技(北京)有限公司 预付费用户在两种异构网络之间的国际漫游的实现方法
CN1956424A (zh) * 2005-10-26 2007-05-02 德赛电子(惠州)有限公司 基于分布式网关的通信方法及应用
CN1996971A (zh) * 2006-12-14 2007-07-11 华为技术有限公司 虚拟媒体网关优化接网的方法及系统
CN101227729A (zh) * 2008-01-29 2008-07-23 侯万春 实现移动电话自动租用漫游地电话号码的方法

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20150056847A (ko) * 2012-09-17 2015-05-27 질랜드 파마 에이/에스 글루카곤 유사체
KR101667948B1 (ko) 2012-09-17 2016-10-20 베링거 인겔하임 인터내셔날 게엠베하 글루카곤 유사체

Also Published As

Publication number Publication date
EP2490455A4 (en) 2013-07-03
CN101729930B (zh) 2012-07-04
EP2490455A1 (en) 2012-08-22
CN101729930A (zh) 2010-06-09

Similar Documents

Publication Publication Date Title
US8670549B2 (en) Method and system for improved routing of repair calls to a call center
JP5611037B2 (ja) 異なるネットワーク間における相互接続を通じた接続の設定
EP2011347A2 (en) Methods, systems, and computer program products for providing internet protocol multimedia subsystem(ims) registration services for non-ims devices
CN1863252B (zh) 为用户增加特殊用途号码的方法及系统
CN101534492B (zh) 综合虚拟专用网业务系统及实现虚拟专用网业务的方法
CN101146266A (zh) 为用户增加特殊用途号码的方法及系统
WO2008104115A1 (fr) Procédé de facturation de service par groupe de central téléphonique et dispositif de commande de service
US7929674B1 (en) Method and system for providing billing capability for a service node in an advanced intelligent network environment
EP2109299B1 (en) A method, system and device for playing group color ring
WO2011060630A1 (zh) 一种多智能业务方法、系统及智能网关
US20100067681A1 (en) Systems and methods for providing a telecommunications extension service for multiple telecommunications units
WO2008019623A1 (fr) Procédé appareil et système de réalisation de service de rappel d'occupation
US20010053218A1 (en) Transaction bridging/forwarding in signaling system of telecommunications network
EP2060128B1 (en) System and method for providing high reliability network
EP1131918A1 (en) Triggering of intelligent network service
US20070140158A1 (en) Method, apparatus and network arrangement for establishing calls in a communications network
US7957523B2 (en) Method and system for implementing a ring back tone based on group mobile switchboard service
CN100496072C (zh) 一种总机实现方法
US7149300B1 (en) Transfer function for messaging platform in public telephone system
US6771762B1 (en) System and method for call merge to an AIN SSP from an intelligent peripheral
US6707898B1 (en) Elapsed time reminder for telecommunication network
WO2005039207A1 (fr) Procede de mise en oeuvre de gestion de mobilite de terminaux fixes dans un reseau de communication
O'Reilly-Roche Call party handling using the connection view state approach: a foundation for intelligent control of multiparty calls
KR100630623B1 (ko) 링백톤 대체음을 제공하는 방법 및 장치
KR100278740B1 (ko) 전자교환시스템에서의차세대지능망착신과금호처리방법

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

Country of ref document: EP

Kind code of ref document: A1

REEP Request for entry into the european phase

Ref document number: 2010831046

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2010831046

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE