Abstract:
The present application discloses a method for implementing an intelligent service and a communications system and relates to the communications technology field, so that an intelligent service may be performed in a wireless intelligent network (WIN). The method includes: a home mobile switch center (MSC) receives a call routed by a serving MSC, where the call carries a WIN configuration parameter that a home home location register (HLR) delivers to the serving MSC; after determining, according to the WIN configuration parameter of the serving MSC, that the call is a WIN OVERLAY call, the home MSC obtains an intelligent service parameter through a home first network entity; the home MSC implements WIN intelligent service processing according to the intelligent service parameter. The embodiments of the present invention are mainly applied in a WIN.

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
       [0001]    This application is a continuation of International Application No. PCT/CN2010/072965, filed on May 20, 2010, which claims priority to Chinese Patent Application No. 200910143617.8, filed on May 27, 2009, both of which are hereby incorporated by reference in their entireties. 
     
    
     FIELD OF THE APPLICATION 
       [0002]    The present application relates to the communications technology field, and in particular, to a method for implementing an intelligent service and a communications system. 
       BACKGROUND OF THE APPLICATION 
       [0003]    A wireless intelligent network (WIN) is an intelligent network system based on a code division multiple access (CDMA) mobile communication network and is mainly used to provide users with intelligent services in the CDMA network. A Customized Applications for Mobile Network Enhanced Logic (CAMEL) standard is a mobile intelligent network standard formulated by the European Telecommunications Standards Institute (ETSI), and is mainly used to provide users with intelligent services in a Global System for Mobile Communications (GSM) network. 
         [0004]    Different from the CAMEL standard, a WIN standard defines services, service attributes, and service information flows that are supported at each phase according to urgent market service requirements. In addition, entities such as a service control point (SCP) are introduced in the original CDMA network, and a Mobile Application Part (MAP) protocol is used. 
         [0005]    However, the following problems are known to exist in these systems: 
         [0006]    If an OVERLAY service switching point (OVERLAY SSP) mode is used on the WIN, when an intelligent service is performed, the WIN standard requires that some MAP information should be used as mandatory information elements, however, a relay signaling cannot transfer the MAP information to the OVERLAY SSP. Therefore, the intelligent service may not be performed on the WIN. 
       SUMMARY OF THE APPLICATION 
       [0007]    Embodiments of the present application provide a method for implementing an intelligent service and a communications system, so that an intelligent service can be performed in a wireless intelligent network (WIN). 
         [0008]    The embodiments of the present application adopt the following technical solutions: 
         [0009]    A method for implementing an intelligent service includes: 
         [0010]    receiving, by a home mobile switching center (MSC), a call routed by a serving MSC, where the call carries a WIN configuration parameter that a home home location register (HLR) delivers to the serving MSC; 
         [0011]    after determining that the call is a WIN OVERLAY call according to the WIN configuration parameter of the serving MSC, obtaining, by the home MSC, an intelligent service parameter through a home first network entity; and 
         [0012]    working, by the home MSC and according to the intelligent service parameter, with the serving MSC, the first network entity, and a home second network entity to implement WIN intelligent service processing. 
         [0013]    A communications system includes a home MSC, a home first network entity, and a home second network entity. 
         [0014]    The home MSC is configured to: receive a call routed by a serving MSC, where the call carries a WIN configuration parameter that a home HLR delivers to the serving MSC; after determining that the call is a WIN OVERLAY call, obtain an intelligent service parameter through the home first network entity; and work with the serving MSC, the home first network entity, and the home second network entity to implement WIN intelligent service processing. 
         [0015]    The home first network entity is configured to send the intelligent service parameter to the home MSC. 
         [0016]    The second network entity is configured to work with the home MSC, the home first network entity, and the second network entity to implement the WIN intelligent service processing. 
         [0017]    A method for implementing an intelligent service includes: 
         [0018]    receiving, by a home HLR, a location request message sent by a home MSC, where the message carries a TRANSCAP (namely, system processing capability of a serving MSC) parameter and a mobile switching center identification number (MSCID) of the serving MSC; 
         [0019]    when determining, according to the location request message, that the serving MSC does not have a WIN capability, sending, by the home HLR, a location response message to the home MSC, where the location response message carries an intelligent service parameter and information that is used to indicate that the serving MSC does not have the WIN capability; and 
         [0020]    working, by the home MSC and according to the intelligent service parameter, with the serving MSC, the home HLR, and a service control point (SCP) to implement WIN intelligent service processing. 
         [0021]    A communications system includes a home MSC, a home HLR, and an SCP. 
         [0022]    The home HLR is configured to: receive a location request message sent by the home MSC, where the message carries a TRANSCAP parameter and an MSCID of the serving MSC; when determining, according to the location request message, that the serving MSC does not have a WIN capability, send a location response message to the home MSC, where the location response message carries an intelligent service parameter and information that is used to indicate that the serving MSC does not have the WIN capability. 
         [0023]    The home MSC is configured to: receive the location response message, and work, by using the intelligent service parameter, with the home HLR and the SCP to implement WIN intelligent service processing. 
         [0024]    The SCP is configured to work with the home HLR and the home MSC to implement the WIN intelligent service processing. 
         [0025]    It can be known from the preceding description that by using the method for implementing an intelligent service and the communications system provided in the embodiments of the present application, the home MSC obtains an intelligent service parameter, and communicates with another entity in the network by using the intelligent service parameter. In this way, information elements that comply with the WIN standard may be transmitted between each network entity. Therefore, by using the technical solutions of the present application, in a WIN, when a mobile subscriber roams to a serving MSC that does not support a WIN capability, an intelligent service can still be performed. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0026]      FIG. 1  is a flowchart of a method for implementing an intelligent service according to a first embodiment; 
           [0027]      FIG. 2  is a flowchart of a method for implementing an intelligent service according to a second embodiment; 
           [0028]      FIG. 3  is a schematic network diagram of a method for implementing an intelligent service according to an embodiment; 
           [0029]      FIG. 4  is a location registration flowchart of a method for implementing an intelligent service according to a third embodiment; 
           [0030]      FIG. 5A  and  FIG. 5B  are an origination flowcharts of a method for implementing an intelligent service according to a third embodiment; 
           [0031]      FIG. 6A  and  FIG. 6B  are a termination flowcharts of a method for implementing an intelligent service according to a third embodiment; 
           [0032]      FIG. 7A  and  FIG. 7B  are an origination flowcharts of a method for implementing an intelligent service according to a fourth embodiment; 
           [0033]      FIG. 8  is a schematic diagram of a communications system according to a sixth embodiment; and 
           [0034]      FIG. 9  is a schematic diagram of a communications system according to a seventh embodiment. 
       
    
    
     DETAILED DESCRIPTION OF THE EMBODIMENTS 
       [0035]    The technical solutions in the embodiments are described clearly and completely below with reference to the accompanying drawings. Apparently, the embodiments described below are only part of rather than all of the embodiments. Persons skilled in the art may derive other embodiments from the embodiments without making creative efforts, and all such embodiments shall fall within the protection scope of the claims. 
         [0036]    To enable that an intelligent service m ay be performed in a WIN when a subscriber roams to a serving mobile switch center (MSC) that does not support a WIN capability, a first embodiment provides a method for implementing an intelligent service. As shown in  FIG. 1 , the method provided in the first embodiment includes the following steps: 
         [0037]    Step  11 : An MSC of a home network (home MSC for short) receives a call routed by an MSC of a serving network (serving MSC for short), where the call carries a WIN configuration parameter that a home HLR delivers to the serving MSC. 
         [0038]    The WIN configuration parameter may include a called party number (CPN), a calling party number (CIN), and an original called number (OCN), or the WIN configuration parameter may include a CPN and a CIN. 
         [0039]    Step  12 : After determining, according to the WIN configuration parameter of the serving MSC, that the call is a WIN OVERLAY call, the home MSC obtains an intelligent service parameter through a home first network entity. 
         [0040]    The intelligent service parameter includes but is not limited to an MSCID of the serving MSC, a mobile station identifier (MSID) of a mobile terminal, and a TRIGADDRLIST (namely, intelligent trigger list) parameter. The MSID includes a mobile identity number (MIN) or international mobile subscriber identification number (IMSI). 
         [0041]    Step  13 : The home MSC works, according to the intelligent service parameter, with the serving MSC, the home first network entity, and a home second network entity to implement intelligent service processing. 
         [0042]    The first network entity may be a home HLR, and the second network entity may be an SCP. Alternatively, the first network entity may be an SCP and the second network entity may be a home HLR. 
         [0043]    It can be known from the technical solution provided in the first embodiment that, the home MSC obtains the intelligent service parameter, and communicates with another entity in the network by using the intelligent service parameter. In this way, information elements that comply with the WIN standard may be transmitted between each network entity. Therefore, by using the described technical solution, in a WIN, when a mobile subscriber roams to the serving MSC that does not support the WIN capability, an intelligent service can still be performed. 
         [0044]    As shown in  FIG. 2 , a second embodiment also provides a method for implementing an intelligent service, where the method includes the following steps: 
         [0045]    Step  21 : A home HLR receives a location request message sent by a home MSC, where the message carries a TRANSCAP parameter and an MSCID of the serving MSC. 
         [0046]    Step  22 : When determining, according to the location request message, that the serving MSC does not have a WIN capability, the home HLR sends a location response message to the home MSC, where the location response message carries an intelligent service parameter and information that is used to indicate that the serving MSC does not have the WIN capability. 
         [0047]    The intelligent service parameter is the same as that described in the first embodiment. 
         [0048]    Step  23 : The home MSC works, according to the intelligent service parameter, with the serving MSC, the home HLR, and the SCP to implement WIN intelligent service processing. 
         [0049]    It can be known from the technical solution provided in the second embodiment that, the home MSC obtains an intelligent service parameter, and communicates with another entity in the network by using the intelligent service parameter. In this way, information elements that comply with the WIN standard can be transmitted between each network entity. Therefore, by using the technical solution of the embodiment, in a WIN, when a mobile subscriber roams to the serving MSC that does not support the WIN capability, an intelligent service can still be performed. 
         [0050]    The following describes the technical solutions of the first embodiment and the second embodiment with reference to different embodiments. 
         [0051]    Before a technical solution of each embodiment is described, an application scenario for each embodiment is simply described. In an embodiment, a WIN OVERLAY may be formed by improving a current network system. An overlay schematic network diagram is as shown in  FIG. 3 . As shown in  FIG. 3 , the WIN OVERLAY includes a serving network and a home network. The serving network includes a serving MSC, and the home network includes entities such as a home HLR, a home MSC, and an SCP. In addition, the serving MSC, home HLR, home MSC, and SCP may be improved according to different application scenarios. However, in a specific application, not all the preceding entities are required to be improved concurrently, but only some entities are improved according to different conditions. 
         [0052]    This embodiment provides three application scenarios according to different requirements of the WIN OVERLAY solution for the SCP. Scenario 1: Standard SCP WIN OVERLAY solution. In this scenario, no specific requirement is imposed on the SCP. Scenario 2: Enhanced SCP WIN OVERLAY solution. In this scenario, the SCP needs to be improved accordingly. Scenario 3: WIN OVERLAY solution that fulfills specific conditions. In this scenario, the SCP needs to fulfill specific conditions. 
         [0053]    The following describes the embodiments in detail with reference to different scenarios. In the preceding three scenarios, the embodiments may be described in terms of three aspects, namely, a location registration process, an origination process, and a termination process. In addition, the location registration process and the terminating process are implemented in a same way in the preceding three scenarios. Therefore, these two processes are described in detail in one embodiment only, for example, the third embodiment. Furthermore, in the preceding processes, as an example, a signaling connection between the serving MSC and the home MSC is an Integrated Services Digital Network User Part (ISUP). Other relay modes such as a Session Initiation Protocol (SIP) may also be used in the embodiments. 
       Embodiment 3: Standard SCP WIN OVERLAY Solution 
       [0054]    1. Location Registration Process 
         [0055]    As shown in  FIG. 4 , the location registration process provided in this embodiment may include the following steps: 
         [0056]    Step  41 : When finding that a mobile terminal roams to its serving area, a serving MSC/VLR sends a location registration request (REGNOT) message to a home HLR to obtain a profile (namely, a service item list) and authentication information that are of the mobile terminal. The REGNOT message carries parameters such as an MSCID, an MSID, an ESN (electronic serial number of the mobile terminal), a TRANSCAP (system processing capability of the serving MSC), a WINCAP (WIN processing capability of the serving MSC), and QUALCODE (service qualification information applied by the serving MSC). 
         [0057]    Step  42 : The home HLR authenticates the mobile terminal. After the authentication succeeds and if the mobile terminal subscribes to a WIN trigger, the home HLR determines whether the serving MSC has a WIN capability. 
         [0058]    In an actual application, the home HLR may determine whether the serving MSC has the WIN capability according to the TRANSCAP parameter and the MSCID of the serving MSC. Alternatively, the home HLR may determine whether the serving MSC has the WIN capability according to the TRANSCAP parameter, the MSCID of the serving MSC, and the WINCAP parameter. 
         [0059]    If the home HLR determines that the serving MSC does not have the WIN capability, the home HLR may deduce that WIN capability configuration information includes OriginationIndicator and RestrictionDigits, and generate a WIN configuration parameter. Then, the home HLR sends the WIN configuration parameter to the serving MSC through a location registration response (regnot) message, and the serving MSC stores the WIN configuration parameter. 
         [0060]    In the WIN capability configuration information, both the OriginationIndicator and the RestrictionDigits may be constructed by using the MSCID of the serving MSC and the MSID. In an actual application, it is suggested that a default value of the RestrictionDigits should be 8. 
         [0061]    2. Origination Process 
         [0062]    As shown in  FIG. 5 , the origination process in the scenario provided in the third embodiment may include the following steps: 
         [0063]    Step  51 : The serving MSC receives an MS Origination call from the mobile terminal. 
         [0064]    Step  52 : The serving MSC routes the call to a home MSC. 
         [0065]    In this step, the serving MSC may route the call to the home MSC by using one of the following two routing modes. 
         [0066]    Mode 1: The serving MSC routes the call by using the OriginationIndicator and the RestrictionDigits that are in the WIN capability configuration information. 
         [0067]    The serving MSC detects, according to the regnot message, that the profile of the mobile terminal includes the OriginationIndicator and the RestrictionDigits information. Therefore, the serving MSC sends an initial address message (IAM) to the home MSC. In addition, the WIN configuration parameters carried in the IAM and usage of the WIN configuration parameters are as shown in Table 1. 
         [0000]    
       
         
               
               
               
             
           
               
                 TABLE 1 
               
               
                   
               
               
                 Parameters 
                 Usage 
                 Type 
               
               
                   
               
             
             
               
                 CPN 
                 RestrictionDigits in the profile of 
                 R 
               
               
                 (Called Party Number) 
                 the mobile terminal 
               
               
                 CIN 
                 Mobile directory number (MDN) of 
                 R 
               
               
                 (Calling Party Number) 
                 the mobile terminal 
               
               
                 OCN 
                 Called number dialed by the mobile 
                 R 
               
               
                 (Original Called Number) 
                 terminal 
               
               
                   
               
             
          
         
       
     
         [0068]    Mode 2: The serving MSC routes the call according to a calling number segment. It should be noted that the second mode is generally applicable to a case that the number segments of intelligent users have rules. 
         [0069]    In this mode, the serving MSC sends an IAM to the home MSC, and the WIN configuration parameters carried in the IAM and usage of the WIN configuration parameters are shown in Table 2. 
         [0000]    
       
         
               
               
               
             
           
               
                 TABLE 2 
               
               
                   
               
               
                 Parameters 
                 Usage 
                 Type 
               
               
                   
               
             
             
               
                 CPN 
                 Called number dialed by the mobile 
                 R 
               
               
                 (Called Party Number) 
                 terminal 
               
               
                 CIN 
                 MDN of the mobile terminal 
                 R 
               
               
                 (Calling Party Number) 
               
               
                   
               
             
          
         
       
     
         [0070]    Step  53 : The home MSC determines, according to the IAM, whether the call is a WIN OVERLAY call. In addition, when determining that the call is a WIN OVERLAY call, the home MSC sends a SEARCH message to the home HLR to obtain related intelligent service parameters and mobile data. 
         [0071]    In the first routing mode, the home MSC may determine whether the call is a WIN OVERLAY call according to an OCN parameter and a CPN that are in the IAM. Alternatively, the home MSC may determine whether the call is a WIN OVERLAY call according to the OCN parameter, the CPN, and a CIN parameter. When the CPN or CIN is used, the home MSC may determine, according to configuration of a number segment, whether the call is a WIN OVERLAY call through determining whether the CPN or CIN exists in a locally-configured WIN OVERLAY call origination list and combining the OCN parameter. 
         [0072]    In the second routing mode, the home MSC may determine whether the call is a WIN OVERLAY call by using the CIN parameter. Specifically, the home MSC determines whether the call is a WIN OVERLAY call through determining whether the CIN exists in the locally-configured WIN OVERLAY call origination list. 
         [0073]    When determining that the call is a WIN OVERLAY call, the home MSC sends a SEARCH message to the home HLR to obtain related intelligent service parameters and mobile data. The parameters carried in the SEARCH message and usage of the parameters are as shown in Table 3. 
         [0000]    
       
         
               
               
               
             
           
               
                 TABLE 3 
               
               
                   
               
               
                 Parameters 
                 Usage 
                 Type 
               
               
                   
               
             
             
               
                 DatabaseKey 
                 MDN (calling party number) 
                 R 
               
               
                 SDAEL 
                 MIN identifier 
                 R 
               
               
                 (ServiceDataAccessElementList) 
                 IMSI identifier 
               
               
                   
                 MSCID identifier 
               
               
                   
                 TriggerAddressList Identifier 
               
               
                   
               
             
          
         
       
     
         [0074]    Step  54 : The home HLR sends a search response message to the home MSC. Related parameters carried in the search message and usage of the related parameters are as shown in Table 4. 
         [0000]    
       
         
               
               
               
             
           
               
                 TABLE 4 
               
               
                   
               
               
                 Parameters 
                 Usage 
                 Type 
               
               
                   
               
             
             
               
                 SDAEL 
                 MIN 
                 R 
               
               
                 (ServiceDataAccessElementList) 
                 IMSI 
               
               
                   
                 MSCID: MSCID of the serving 
               
               
                   
                 MSC 
               
               
                   
                 TriggerAddressList: registered 
               
               
                   
                 by the mobile terminal 
               
               
                   
               
             
          
         
       
     
         [0075]    Then, the home MSC, the home HLR, an SCP, and the serving MSC process an intelligent service in the WIN OVERLAY. The specific process includes the following steps: 
         [0076]    Step  55 : The home MSC sends an ORREQ message to the SCP, where the ORREQ message carries information such as the MSCID and the MSID. 
         [0077]    Step  56 : The SCP sends an orreq message to the home MSC. 
         [0078]    Step  57 : The home MSC sends an ANLYZD message to the SCP, where the ANLYZD message carries information such as the MSCID, the TRANSCA, and the MSID. 
         [0079]    Step  58 : The SCP sends an anlyzd response message to the home MSC. 
         [0080]    Steps  59  to  513 : The home MSC, the SCP, the home HLR, and the serving MSC complete the call setup process. 
         [0081]    Steps  514  to  518 : When a user hangs up, the home MSC, the SCP, the home HLR, and the serving MSC complete a disconnection process. Then, the entire call process ends. 
         [0082]    It can be known from the foregoing process that, the specific implementation methods in steps  55  to  518  comply with the WIN standard and an I TU/ANSI ISUP procedure. It should be noted that when communication occurs between the foregoing each entity, the MSCID and the MSID that are used by the home MSC is returned by the home HLR to the home MSC through the search message. 
         [0083]    3. Termination Process 
         [0084]    As shown in  FIG. 6 , the termination process in the scenario provided in the third embodiment may include the following steps: 
         [0085]    Step  61 : The home MSC receives a call from the mobile terminal. 
         [0086]    Step  62 : The home MSC detects a Mobile Termination trigger of the mobile terminal, and sends a location request (LOCREQ) message to the home HLR, where the LOCREQ message carries parameters such as an MSCID, a BILLID (charging ID), DGTSDIAL (original called party number), a TRIGTYPE (triggered trigger type), a TRANSCAP, and a WINCAP. 
         [0087]    Step  63 : The home HLR determines, according to the description in the location registration process, that the serving MSC of the mobile terminal does not have the WIN capability, and sends a location request response (locreq) message to the home MSC. In the locreq response message, the TRIGADDRLIST (an intelligent trigger list) parameter carries an Initial_Termination, a Location, a Called_Routing_Address_Available, a T_Answer, and a T_Disconnect trigger. 
         [0088]    The two intelligent service parameters T_Answer and T_Disconnect are carried to indicate that the serving MSC does not have the WIN capability. 
         [0089]    Step  64 : The home MSC sends an ANLYZD message to the SCP, where the ANLYZD message carries parameters such as an MSCID, a BILLID (charging ID), a DGTSDIAL (original called party number), and a TRIGTYPE. 
         [0090]    Step  65 : The SCP sends an anlyzd response message to the home MSC. 
         [0091]    Step  66 : The home MSC sends a LOCREQ message to the home HLR, where the LOCREQ message carries parameters such as an MSCID, a BILLID (charging ID), a DGTSDIAL (original called party number), a TRIGTYPE, a TRANSCAP, and a WINCAP. 
         [0092]    Steps  64  to  66  comply with procedures in the WIN standard and ISUP. 
         [0093]    Step  67 : The home HLR sends a route request (ROUTREQ) message to the serving MSC after determining, according to the LOCREQ message, that the call process may be continued. It should be noted that the ROUTREQ message does not carry the TRIGADDRLIST parameter because the serving MSC does not have the WIN capability. 
         [0094]    Steps  68  to  614 : The serving MSC, the home MSC, the home HLR, and the SCP perform information interaction. These steps comply with the procedures in the WIN standard and ISUP. 
         [0095]    Step  615 : The home MSC detects the T_Answer trigger, and sends a TANSWER message to the SCP. The TANSWER message carries the MSCID of the serving MSC. 
         [0096]    Step  616 : The mobile terminal releases the call. 
         [0097]    Step  617 : The home MSC detects the T_Disconnect trigger, and sends a TDISCONNECT message to the SCP. The TDISCONNECT message carries the MSCID of the serving MSC. 
         [0098]    Step  618 : The SCP sends a tdisconnect response message to the home MSC. 
         [0099]    Step  619 : The home MSC sends a Release Complete (RLC) message to the serving MSC. 
         [0100]    Steps  618  to  66  comply with procedures in the WIN standard and ISUP. 
         [0101]    It can be known from the technical solution provided in the third embodiment that, the home MSC obtains an intelligent service parameter, and communicates with another network entity by using the intelligent service parameter. In this way, information elements that comply with the WIN standard can be transmitted between each network entity. Therefore, by the technical solution of the embodiment, in a WIN, when a mobile subscriber roams to a serving MSC that does not support a WIN capability, an intelligent service can still be performed. In addition, the SCP in the current network can be used in this embodiment to the greatest extent. 
       Embodiment 4: Enhanced SCP WIN OVERLAY Solution 
       [0102]    As shown in  FIG. 7 , an origination process in a scenario provided in the fourth embodiment may include the following steps: 
         [0103]    Steps  71  to  72  are the same as steps  51  to  52 . 
         [0104]    Step  73 : A home MSC determines, according to the IAM, whether a call is a WIN OVERLAY call. In addition, after determining that the call is a WIN OVERLAY call, the home MSC sends an ORREQ message to an SCP. The trigger type in the ORREQ message is filled as WIN_OVERLAY_Origination_Attempt_Authorized (namely, WIN OVERLAY origination authorization). Related parameters carried in the ORREQ message and usage of the related parameters are as shown in Table 5. 
         [0000]    
       
         
               
               
               
             
           
               
                 TABLE 5 
               
               
                   
               
               
                 Parameters 
                 Usage 
                 Type 
               
               
                   
               
             
             
               
                 MSCID 
                 MSCID of the home MSC 
                 R 
               
               
                 MSID 
                 Set to 0 
                 R 
               
               
                 MDN 
                 Calling party number 
                 R 
               
               
                 DGTSDIAL 
                 Original called party number 
                 R 
               
               
                 TRIGTYPE 
                 WIN_OVERLAY_Origination_Attempt_Authorized. 
                 R 
               
               
                 CPSUB 
                 Address information of the serving MSC: 
                 R 
               
               
                 (CallingPartySubaddress) 
                 (1) Routing mode 1: RestrictionDigits 
               
               
                   
                 (2) Routing mode 2: deduced according to 
               
               
                   
                 an incoming trunk group 
               
               
                   
               
             
          
         
       
     
         [0105]    It can be known from Table 5 that, the home MSC stores location information of the serving MSC by using a CPSUB parameter. In the foregoing first routing mode, the content of the CPSUB is filled as RestrictionDigits; in the foregoing second routing mode, the content of the CPSUB is deduced according to the incoming trunk group. 
         [0106]    Step  74 : If detecting that the trigger type in the ORREQ message is WIN_OVERLAY_Origination_Attempt_Authorized, the SCP determines that the call is a WIN OVERLAY call. The SCP obtains the CPSUB in the ORREQ message, and deduces a location of the serving MSC. In this case, the SCP neglects a WIN parameter, and performs a subsequent service and bill processing logic by using the MDN and deduced location of the serving MSC. 
         [0107]    The SCP sends an orreq response message to the home MSC, and returns a TriggerAddressList parameter subscribed to by a mobile terminal in the orreq response message. Other processing processes are the same as the standard WIN process. 
         [0108]    Step  75 : The home MSC assembles a TriggerAddressList in the orreq. Other processing processes are the same as the processes in the WIN standard. 
         [0109]    Steps  76  to  716 : The home MSC, a home HLR, the SCP, and the serving MSC process the intelligent service in the WIN OVERLAY. Steps  76  to  716  comply with the process in the WIN standard and the procedures in the ITU or ANSI ISUP. It should be noted that the MSCID and the MSID that are used by the home MSC are carried in step  73 . 
         [0110]    It can be known from the technical solution provided in the fourth embodiment that, the home MSC obtains an intelligent service parameter, and communicates with another network entity by using the intelligent service parameter. In this way, information elements that comply with the WIN standard can be transmitted between each network entity. Therefore, by using the described technical solution, in a WIN, when a mobile subscriber roams to a serving MSC that does not support a WIN capability, an intelligent service can still be performed. In addition, in this solution, the improvement on the SCP reduces complexity of improvement on the home MSC. 
         [0111]    Embodiment 5: WIN OVERLAY Solution that Fulfils Specific Conditions 
         [0112]    In a scenario provided in the fifth embodiment, the origination process may include the following steps: 
         [0113]    Steps  81  to  82  are the same as steps  51  to  52 . 
         [0114]    Step  83 : The home MSC determines that the SCP fulfils specific conditions, that is, after a mapping relationship between the MDN and the MSID is stored in the SCP, the following processing is implemented according to different routing methods in step  82 : 
         [0115]    Processing mode 1: In the foregoing first routing mode, the home MSC deduces the MSCID of the serving MSC according to the CPN (RestrictionDigits), and deduces a TriggerAddressList parameter according to the CPN (RestrictionDigits) and the CIN. 
         [0116]    Processing mode 2: In the foregoing second routing mode, the home MSC deduces the MSCID of the serving MSC according to an incoming trunk group, and deduces the TriggerAddressList parameter according to the CPN (RestrictionDigits) and the CIN. 
         [0117]    The home MSC sends an ORREQ message to the SCP. Related parameters carried in the ORREQ message and usage of the related parameters are as shown in Table 6. 
         [0000]    
       
         
               
               
               
               
             
           
               
                   
                 TABLE 6 
               
               
                   
                   
               
               
                   
                 Parameters 
                 Usage 
                 Type 
               
               
                   
                   
               
             
             
               
                   
                 MSCID 
                 MSCID of the serving MSC 
                 R 
               
               
                   
                 MSID 
                 MIN (filled with the MDN) 
                 R 
               
               
                   
                 MDN 
                 Calling party number 
                 R 
               
               
                   
                 DGTSDIAL 
                 Original called party number 
                 R 
               
               
                   
                   
               
             
          
         
       
     
         [0118]    Step  84 : The SCP sends, according to the stored mapping relationship between the MDN and the MSID, an orreq message that carries the MSID to the home MSC. 
         [0119]    Step  85 : The home MSC stores a corresponding MSID, and sends an ANLYZED message to the SCP. 
         [0120]    Steps  86  to  816 : The home MSC, the home HLR, the SCP, and the serving MSC process an intelligent service in the WIN OVERLAY. Steps  86  to  816  comply with the standard WIN process and the ITU/ANSI ISUP procedures. It should be noted that the MSCID parameter used by the home MSC is filled with MSCID of the serving MSC, and the MSID used by the home MSC is filled with the MSID returned by the SCP. 
         [0121]    It can be known from the technical solution provided in the fifth embodiment that, the home MSC obtains an intelligent service parameter, and communicates with another network entity by using the intelligent service parameter. In this way, information elements that comply with the WIN standard can be transmitted between each network entity. Therefore, by using the described technical solution, in a WIN, when a mobile subscriber roams to a serving MSC that does not support a WIN capability, an intelligent service can still be performed. In addition, in this solution, the SCP in the current network can be used to the greatest extent. 
         [0122]    It is understandable to those skilled in the art that all or part of the steps in the preceding embodiments may be implemented by relevant hardware instructed by a program. The program may be stored in a computer readable storage medium. When the program is executed, the processes of the preceding methods are executed. The storage medium may be a magnetic disk, a Compact Disk-Read Only Memory (CD-ROM), a Read-Only Memory (ROM) or a Random Access Memory (RAM). 
         [0123]    As shown in  FIG. 8 , a sixth embodiment also provides a communications system, including a home MSC  91 , a home first network entity  92 , and a home second network entity  93 . 
         [0124]    The home MSC  91  is configured to: receive a call routed by a serving MSC, where the call carries a WIN configuration parameter that a home HLR delivers to the serving MSC; after determining that the call is a WIN OVERLAY call, obtain an intelligent service parameter through a home first network entity; and work with the serving MSC, the home first network entity, and a home second network entity to WIN intelligent service processing. 
         [0125]    The home first network entity  92  is configured to send the intelligent service parameter to the home MSC. 
         [0126]    The home second network entity  93  is configured to work with the home MSC, the home first network entity, and the second network entity to implement the WIN intelligent service processing. 
         [0127]    In an actual application, the home first network entity  92  may be the home HLR, and the home second network entity  93  may be an SCP; or the home first network entity  92  may be the SCP, and the home second network entity  93  may be the home HLR. 
         [0128]    The home HLR is further configured to: receive a location registration request message sent by the serving MSC; when determining that the serving MSC does not have a WIN capability, generate a WIN configuration parameter according to the location registration request message, and send the WIN capability configuration information to the serving MSC through a location registration response message. 
         [0129]    The process of performing location registration by the HLR is the same as that described in the method embodiments, and is not repeatedly described here. 
         [0130]    Moreover, as shown in  FIG. 9 , a seventh embodiment also provides a communications system, including a home MSC  101 , a home HLR  102 , and an SCP  103 . 
         [0131]    The home HLR  102  is configured to: receive a location request message sent by the home MSC, where the location request message carries a TRANSCAP parameter and an MSCID of the serving MSC; when determining, according to the location request message, that the serving MSC does not have a WIN capability, send a location response message to the home MSC, where the location response message carries an intelligent service parameter and information that is used to indicate that the serving MSC does not have the WIN capability. 
         [0132]    The home MSC  101  is configured to: receive the location response message, and work, by using the intelligent service parameter, with the home HLR and the SCP to implement WIN intelligent service processing. 
         [0133]    The SCP  103  is configured to work with the home HLR and the home MSC to implement the WIN intelligent service processing. 
         [0134]    In conclusion, by using the method for implementing an intelligent service and the communications system provided in the embodiments, the home MSC obtains an intelligent service parameter, and communicates with another network entity by using the intelligent service parameter. In this way, information elements that comply with the WIN standard can be transmitted between each network entity. Therefore, by using the technical solution of the embodiment, in a WIN, when a mobile subscriber roams to a serving MSC that does not support a WIN capability, an intelligent service can still be performed. In addition, by using the embodiments, continuous and consistent intelligent service experience can be provided for final users; an intelligent service platform may be uniformly deployed for carriers without limitations of roaming scenarios. 
         [0135]    The preceding descriptions are merely exemplary embodiments, but not intended to limit the protection scope of the claims. Modifications, equivalent replacements, and improvements may be made by those skilled in the art. Such changes are understood to fall within the scope of protection afforded by the claims.