WO2010135877A1 - 移动虚拟专用网集团智能业务实现方法和装置 - Google Patents
移动虚拟专用网集团智能业务实现方法和装置 Download PDFInfo
- Publication number
- WO2010135877A1 WO2010135877A1 PCT/CN2009/073754 CN2009073754W WO2010135877A1 WO 2010135877 A1 WO2010135877 A1 WO 2010135877A1 CN 2009073754 W CN2009073754 W CN 2009073754W WO 2010135877 A1 WO2010135877 A1 WO 2010135877A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- group
- call
- scp
- user
- calling
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 80
- 230000008569 process Effects 0.000 claims description 57
- 238000012545 processing Methods 0.000 claims description 28
- 238000012546 transfer Methods 0.000 claims description 10
- 238000012217 deletion Methods 0.000 claims description 8
- 230000037430 deletion Effects 0.000 claims description 8
- 102100027668 Carboxy-terminal domain RNA polymerase II polypeptide A small phosphatase 1 Human genes 0.000 description 9
- 101710134395 Carboxy-terminal domain RNA polymerase II polypeptide A small phosphatase 1 Proteins 0.000 description 9
- PUPNJSIFIXXJCH-UHFFFAOYSA-N n-(4-hydroxyphenyl)-2-(1,1,3-trioxo-1,2-benzothiazol-2-yl)acetamide Chemical compound C1=CC(O)=CC=C1NC(=O)CN1S(=O)(=O)C2=CC=CC=C2C1=O PUPNJSIFIXXJCH-UHFFFAOYSA-N 0.000 description 9
- 102100027667 Carboxy-terminal domain RNA polymerase II polypeptide A small phosphatase 2 Human genes 0.000 description 8
- 101710134389 Carboxy-terminal domain RNA polymerase II polypeptide A small phosphatase 2 Proteins 0.000 description 8
- 238000010586 diagram Methods 0.000 description 6
- 238000012986 modification Methods 0.000 description 6
- 230000004048 modification Effects 0.000 description 6
- 238000011161 development Methods 0.000 description 5
- 230000008859 change Effects 0.000 description 3
- 238000010295 mobile communication Methods 0.000 description 3
- 230000001960 triggered effect Effects 0.000 description 3
- 101000615382 Homo sapiens Stromal membrane-associated protein 1 Proteins 0.000 description 2
- 102100021037 Protein unc-45 homolog A Human genes 0.000 description 2
- 230000008901 benefit Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/44—Augmented, consolidated or itemized billing statement or bill presentation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/70—Administration or customization aspects; Counter-checking correct charges
- H04M15/745—Customizing according to wishes of subscriber, e.g. friends or family
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/70—Administration or customization aspects; Counter-checking correct charges
- H04M15/765—Linked or grouped accounts, e.g. of users or devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/70—Administration or customization aspects; Counter-checking correct charges
- H04M15/765—Linked or grouped accounts, e.g. of users or devices
- H04M15/7652—Linked or grouped accounts, e.g. of users or devices shared by users
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/80—Rating or billing plans; Tariff determination aspects
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/90—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP using Intelligent Networks [IN] or Advanced Intelligent Networks [AIN]
-
- 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
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
- H04W4/08—User group management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2203/00—Aspects of automatic or semi-automatic exchanges
- H04M2203/20—Aspects of automatic or semi-automatic exchanges related to features of supplementary services
- H04M2203/2044—Group features, e.g. closed user group
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2207/00—Type of exchange or network, i.e. telephonic medium, in which the telephonic communication takes place
- H04M2207/12—Type of exchange or network, i.e. telephonic medium, in which the telephonic communication takes place intelligent networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
- H04M2215/01—Details of billing arrangements
- H04M2215/0104—Augmented, consolidated or itemised billing statement, e.g. additional billing information, bill presentation, layout, format, e-mail, fax, printout, itemised bill per service or per account, cumulative billing, consolidated billing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
- H04M2215/01—Details of billing arrangements
- H04M2215/0108—Customization according to wishes of subscriber, e.g. customer preferences, friends and family, selecting services or billing options, Personal Communication Systems [PCS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
- H04M2215/01—Details of billing arrangements
- H04M2215/0152—General billing plans, rate plans, e.g. charge rates, numbering plans, rate centers, customer accounts
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
- H04M2215/01—Details of billing arrangements
- H04M2215/016—Billing using Intelligent Networks [IN] or Advanced Intelligent Networks [AIN]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
- H04M2215/72—Account specifications
- H04M2215/724—Linked accounts
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
- H04M2215/72—Account specifications
- H04M2215/724—Linked accounts
- H04M2215/7245—Shared by users, e.g. group accounts or one account for different users
Definitions
- the present invention relates to the field of mobile intelligent network technologies, and in particular, to a mobile virtual private network group intelligent service implementation method and apparatus.
- a mobile intelligent network system is one of the main business growth points of a telecom operator, and it can provide various value-added services conveniently, flexibly, economically, and effectively, and through the business system,
- the integration of customer service centers, short message centers and banking systems provides users with better, timely and user-friendly services.
- the mobile virtual private network group business is an intelligent network service with a wide range of applications.
- the internal short numbering plan can be developed according to the characteristics of the group for memorization and management.
- a short number can uniquely identify a group member. Taking a group customer as an example, a short number can include information such as position, job number, etc., and when the group member's real number changes, the group member can be deleted and re-added.
- the real number of the repairer does not affect the numbering scheme of the short number. In this way, the employees inside the group will not affect the working contact due to the change of the real number of the mobile communication terminal.
- the users in the group can only find the hope by remembering the short number inside the group. The user found.
- the mobile virtual private network group service can classify the call according to the information of the call: for example, a call within a group, called an intra-network call; a group of one or more small units can also be established within a group to form a closed user. Groups, calls that occur within a closed user group are called closed user groups in the network; a group can also set up some important extranet customers to form an out-of-network number group, when users in the group call the users outside the network number group Call for an out-of-network number group.
- the service can be different in the type of call, and different degrees of preferential offers are given to intra-network calls, closed-closed user group calls, extra-network number group calls, and ordinary off-net calls, so that the communication costs of the group using the service are reduced.
- this business attracts large group customers and can achieve better profits. Therefore, the business can reduce the communication cost of the group to the employees of the group, and enable the operators to attract a large number of group customers and better realize their profits.
- SCP Service Control Point
- the group users of this business have developed rapidly, and there have been a large number of cross-provincial and even multinational groups.
- the expansion of group users has become an inevitable trend. Therefore, a group of users is only distributed in one SCP ⁇ ! Dog conditions can not meet the actual needs.
- many of the original intelligent network devices have been unable to meet the business development needs, and there is an urgent need for capacity expansion. This has led to the problem of how to make full use of the existing smart devices, which is currently urgently needed in the field. of. SUMMARY OF THE INVENTION
- the technical problem to be solved by the present invention is that the mobile virtual private network group can only belong to one service control point in the related art, which causes the problem that the virtual group business development demand cannot be satisfied.
- a mobile virtual private network group intelligent service implementation solution which provides all the business attributes of the non-cross-SCP virtual private network group users for the users of the SCP virtual private network group.
- the technical solution adopted by the present invention is that the mobile virtual private network group intelligent service implementation method includes: configuring a group number and an SCP module number distributed by the group on a service management point (SMP) Corresponding relationship, the relevant data information of the group is configured in the business database of each SCP distributed by the group; the related data information of the group distributed on different SCPs is uniformly managed; when the user triggers a certain service, the call is judged, Control and billing.
- SMP service management point
- the unified management manages related data information of the group distributed on different SCPs, including updating and synchronizing related data information of the group on the SCP distributed by the group when the related data information of the group changes.
- the relevant data information of the group includes: group information and group member information.
- the updating and synchronizing the related data information of the group on the SCP distributed by the group includes: the SMP sequentially sends an instruction to the relevant SCP according to the SCP module number distributed by the group or through the interface machine, and the related SCP receives the instruction.
- the group related data information is updated in the local database.
- the updating of the related data information of the group includes at least one of the following: group creation and deletion, group member addition and deletion, group member short number setting and 4 tampering, group member call authority setting and 4 ⁇ change.
- the call judgment, control, and billing are performed throughout the calling process, the called process, and the forwarding process.
- the calling process in the mobile virtual private network group intelligent service implementation method includes:
- the SCP When the SCP receives the call, it determines whether the calling user belongs to the SCP. If the calling user belongs to the SCP, it further determines whether the called user and the calling user belong to the same group. If yes, according to the balance of the calling user account And the call type for charging control and preferential charging, otherwise charging control and non-concessional charging according to the calling user account balance and call type; if the calling user is not attributed to the SCP, the call is directly forwarded to the MSC for processing , call control and call billing are no longer performed; the called process includes:
- the SCP When the SCP receives the call, it determines whether the called user belongs to the SCP. If the called user belongs to the SCP, it further determines whether the called user and the calling user belong to the same group. If yes, according to the balance of the called user account And the call type for charging control and preferential charging, otherwise charging control and non-concessional charging according to the called user account balance and call type; if the called user does not belong to the SCP, the call is directly forwarded to the MSC for processing , no call control and call billing are performed; the forwarding process includes:
- the SCP receives the call, determines whether the forwarded user belongs to the SCP, and if the forwarded user belongs to the SCP, further determines whether the forwarded user and the forwarded user belong to the same group, and if so, The charging control and the preferential charging are performed according to the user account balance and the call type in which the forwarding occurs, otherwise the charging control and the non-concessional charging are performed according to the user account balance and the call type in which the forwarding occurs; If the user does not belong to the SCP, the call is directly forwarded to the MSC for processing, and call control and call charging are no longer performed.
- the mobile virtual private network group intelligent service implementation method adds a field including the network external number group information corresponding to the group to the group information, where the calling process includes the following Steps:
- the SCP When the SCP receives the call, it determines whether the calling user belongs to the SCP. If the calling user belongs to the SCP, it further determines whether the called user and the calling user belong to the same group. If yes, according to the balance of the calling user account And the first type of preferential billing for the call type, otherwise further judgment Whether the called user belongs to the out-of-network number group of the group where the calling user is located, and if so, performs the second-level preferential charging according to the calling user account balance and the call type, otherwise, the calling user account balance and the calling type are determined.
- the third-level preferential charging is performed; if the calling user is not at the present SCP, the call is directly forwarded to the MSC for processing, and call control and call charging are no longer performed; the called process includes the following steps:
- the SCP When the SCP receives the call, it determines whether the called user belongs to the SCP. If the called user belongs to the SCP, it further determines whether the called user and the calling user belong to the same group. If yes, according to the balance of the called user account And the call type performs the first-level preferential charging, otherwise it further determines whether the calling user belongs to the network external number group of the group where the called user is located, and if so, performs the second-level preferential charging according to the called user account balance and the call type.
- the third-level preferential charging is performed according to the called user account balance and the call type; if the called user does not belong to the SCP, the call is directly forwarded to the MSC for processing, and call control and call charging are no longer performed;
- the forward process includes:
- the SCP receives the call and determines whether the forwarded user belongs to the SCP. If the forwarded user belongs to the SCP, it further determines whether the forwarded user and the forwarded user belong to the same group, and if so, The first-level preferential billing is performed according to the balance of the user account and the call type in which the transfer occurs, otherwise it is further determined whether the forwarded user belongs to the external network number group, and if so, the balance of the user account that occurs before the transfer occurs. The second-level preferential charging is performed with the call type. Otherwise, the third-level preferential charging is performed according to the user account balance and the call type in which the forwarding occurs; if the forwarded user does not belong to the SCP, the call is directly forwarded.
- the MSC processes, no call control and call billing.
- the mobile virtual private network group intelligent service implementation method adds a field including the closed subscriber group information in the network corresponding to the group to the group information, where the calling process includes The following steps:
- the SCP When the SCP receives the call, it determines whether the calling user belongs to the SCP. If the calling user belongs to the SCP, it further determines whether the called user and the calling user belong to the same group. If yes, further determines the calling user. Whether the called user belongs to the closed user group in the same network, and if so, performs the first-level preferential charging according to the calling user account balance and the call type, otherwise the second-level preferential charging is performed according to the calling user account balance and the call type. ; otherwise, according to the calling user account balance and The call type performs the third-level preferential charging; if the calling user does not belong to the SCP, the call is directly forwarded to the MSC for processing, and the call control and call charging are not performed; the called process includes:
- the SCP When the SCP receives the call, it determines whether the called user belongs to the SCP. If the called user belongs to the SCP, it further determines whether the called user and the calling user belong to the same group. If yes, further determines the calling user. Whether the called user belongs to the closed user group in the same network, and if so, the first-level preferential charging is performed according to the called user account balance and the call type, otherwise the second is based on the called user account balance and the call type. Level-based preferential billing; otherwise, the third-level preferential billing is performed according to the called user account balance and call type; if the called user does not belong to the SCP, the call is directly forwarded to the MSC for processing, and call control is no longer performed.
- Call billing the forwarding process includes:
- the SCP receives the call, determines whether the forwarded user belongs to the SCP, and if the forwarded user belongs to the SCP, further determines whether the forwarded user and the forwarded user belong to the same group, and if so, Further determining whether the forwarded user and the forwarded user belong to the closed network user group in the same network, and if so, the first level preferential charging is performed according to the user account balance and the call type in which the forwarding occurs, otherwise, The second-level preferential billing is performed according to the balance of the user account and the call type that occurs before the transfer; otherwise, the third-level preferential billing is performed according to the balance of the user account and the call type in which the transfer occurs; In the present SCP, the call is directly forwarded to the MSC for processing, and call control and call charging are no longer performed.
- the invention also provides a mobile virtual private network group intelligent service implementation device, comprising: a configuration module, configured to configure, on an SMP, a correspondence between a group number and an SCP module number distributed by the group, and each SCP distributed in the group
- the service database is configured to configure related data information of the group
- the management module is configured to uniformly manage related data information of the group distributed on different SCPs
- the service execution module is configured to judge the call when the user triggers an intelligent service , control and billing.
- the unified management manages related data information of the group distributed on different SCPs, including updating and synchronizing related data information of the group on the SCP distributed by the group when the related data information of the group changes.
- the relevant data information of the group includes: group information, long number and short number of the group members The code, the call rights of the group members, and the attribution information of the group members to the SCP.
- the service execution module includes a calling execution module, a called execution module, and a forwarding module. According to the above technical solution, the present invention has at least the following advantages:
- the mobile virtual private network group intelligent service implementation method and apparatus of the present invention the correspondence between the group number and the SCP module number distributed by the group is configured on the SMP, in the group office
- the distribution of each SCP's business database configures the relevant data information of the group, and uniformly manages the relevant data information of the group distributed on different SCPs. Once the relevant data information of the group changes, the group distributes all the groups on the SCP.
- FIG. 1 is a schematic diagram of a mobile virtual private network networking according to a first embodiment of the present invention
- FIG. 2 is a corresponding relationship diagram of a group number and an SCP module number configured on an SMP according to an embodiment of the present invention
- FIG. 4 is a flow chart of the called party in the first embodiment of the present invention
- FIG. 5 is a flow chart of the forward rotation in the first embodiment of the present invention
- FIG. 7 is a flowchart of a called party in a second embodiment of the present invention
- FIG. 8 is a flowchart of a forward rotation in a second embodiment of the present invention
- FIG. 9 is a third embodiment of the present invention
- FIG. 10 is a flowchart of a called party in a third embodiment of the present invention
- FIG. 11 is a flowchart of a forward rotation in a third embodiment of the present invention
- FIG. 12 is a schematic diagram of an apparatus for implementing an intelligent service of a mobile virtual private network group according to a fourth embodiment of the present invention.
- the present invention provides a mobile virtual private network group intelligent service. Considering the problem that the mobile virtual private network group can only belong to one service control point in the related art, which may not satisfy the virtual group service development requirement.
- the implementation principle of the solution is as follows: The correspondence between the group number and the SCP module number distributed by the group is configured on the SMP, and the related data information of the group is configured in the business database of each SCP distributed by the group; The relevant data information of the group distributed on different SCPs; when the user triggers an intelligent service, the call is judged, controlled and charged. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.
- . 1 is a schematic diagram of a network of a mobile virtual private network according to a first embodiment of the present invention, as shown in FIG.
- the SMP communicates with the service management access point (SMAP) and between the SMP and the SCP through the TCP/IP protocol.
- SCP Mobile Switching Center (Mobile Switching Center) or Visitor Location Register (VLR) or Service Switching Point (SSP), Home Location Register (Home Location)
- HLR Home Location Register
- the registers which are called HLRs, are connected to each other through the SS7 network.
- the first service control point SCP1 and the second service control point SCP2 are connected through the SS7 network and the TCP/IP network.
- a unique group number is assigned to each group in the mobile virtual private network, and each service of the mobile communication is implemented on each SCP distributed across the group of the SCP mobile virtual private network.
- group 11 is distributed on the first service control point SCP1 and the second service control point SCP2, and the services are respectively loaded on the two service control points.
- the number of Group 11 is the same on the SCPs distributed by the group.
- the SMP manages the services running on the first service control point SCP1 and the second service control point SCP2 through SMAP.
- the MSC or VLR implements a service switching function, and the HLR stores and manages subscription information of mobile users or group members.
- the user can be referred to as a group member of the group when it is determined that a certain user belongs to a group belonging to the SCP.
- the method for implementing the mobile virtual private network group intelligent service in the embodiment includes the following steps: Step 1: Configuring a correspondence between the group number and the SCP module number distributed by the group on the SMP, each SCP distributed in the group
- the relevant data information of the group is configured in the business database.
- FIG. 2 is a corresponding relationship diagram of a group number and an SCP module number configured on an SMP according to an embodiment of the present invention. As shown in FIG. 2, a correspondence relationship between a group number and an SCP module number is configured on the SMP.
- Each SCP has a unique SCP module number, and the SCP module number corresponds to the IP address of the SCP.
- the module number of the first service control point SCP1 is 135, and the module number of the second service control point SCP2 is 136.
- SMP can distinguish the unused SCP by the SCP module number, and use the TCP/IP protocol to operate the data on the SCP to realize unified management of the relevant data of the group in each SCP.
- Filling in the business database of each SCP distributed by the group, the relevant data information of the group on all SCPs of the group is filled in.
- the related data information of the group includes: group information and user information, and the user information includes: The long and short numbers of the members, the call rights of the group members, and the attribution information of the group members to the SCP.
- the first group member belongs to this SCP, that is, the group member signs the virtual private network intelligent service, which will trigger the virtual private network intelligent service of the SCP
- the second type The members of the group do not belong to this SCP, and will not trigger the virtual private network intelligent service to the SCP. Therefore, it is necessary to identify the ownership information of the group members to the SCP in the user information table of the SCP service database, and distinguish the two group members.
- Step 2 The SMP uniformly manages the relevant data information of the group on the SCP distributed by the group.
- the SMP needs to update and synchronize the related data information of the group on the SCP distributed by the group, and the group member information includes the set.
- the updating and synchronizing the related data information of the group on the SCP distributed by the group includes: SMP sending an instruction to the SCP distributed by the group according to the SCP module number distributed by the group, and the SCP receives the instruction in the local database. Update the relevant data information of the group.
- the updating of the related data information of the group includes at least one of the following: group creation and deletion, group member addition and deletion, group member short number setting and modification, group member call authority setting and modification. It should be noted that since each group member has a unique long number, if the long number of the group member needs to be set and modified, it is equivalent to adding and deleting the group members. To this end, SMP needs to define the following interfaces to the SCP through the TCP/IP protocol:
- the interface used by the group is called to add the group interface.
- the basic fields that are sent through the interface are as follows: Group number, the SCP module number distributed by the group; 2.
- the interface used to delete the group, the cartridge is called delete.
- the group interface, the basic fields that are sent by the interface are as follows: Group number, the module number of the SCP distributed by the group;
- the cylinder is said to add the group member interface.
- the basic fields that are sent through the interface are as follows: Group number, group member number, group member short number, group member call authority, group member ownership SCP module number, The module number of the SCP distributed by the group;
- the interface used to delete the group members the cartridge is called to delete the group member interface.
- the basic fields that the command sends through the interface are as follows: Group number, member user long number, SCP module number distributed by the group;
- Set or modify the group member short number is the interface used.
- the cartridge is called to modify the short number interface.
- the basic fields that are sent through the interface are as follows: Group number, group member long number, group member new short number, group distribution SCP module number;
- the cartridge is called "change the call permission interface.
- the basic fields that are sent through the interface are as follows: Group number, group member number, group member new call Permission, the SCP module number distributed by the group. Taking the group members as an example, describe the process of SMP unified management of the SCP distributed by the group.
- the group management operator initiates the addition of a long number through the first service management access point SMAP1. For the operation of the group member of 8613905190600 to the group 11, the short number is 61001, the call right is the intra-network call, and the group member belongs to the first service control point SCP1 with the module number 135.
- the SMP queries the configuration information in the local database, and learns that the group 11 is distributed on the first service control point SCP1 with the module number 135 and the second service control point SCP2 with the module number 137.
- SMP After receiving the group number sent by the first service management access point SMAP1, the group member number and short number, the call authority, the group member's attribution information to the SCP, and the SCP information distributed by the group, the SCP is distributed according to the group.
- the information is sent to the first service control in sequence, including the group number, the group member long number, the group member short number, the group member call authority, the SCP module number to which the group member belongs, and the block number of the SCP module number distributed by the group.
- Point SCP1 and the second service control point SCP2 add group member interface. Then, the first service control point SCP1 and the second service control point SCP2 add the group number, the group member long number and the short number, and the call right information in the local service database, and set the group member attribution on the first service control point SCP1. In this SCP, the group member is not attributed to the SCP at the second service control point SCP2.
- an interface machine can be connected between the SMP and the SCP, and the SMP and the interface machine, the interface machine and the SCP communicate with each other through the TCP/IP protocol.
- SMP can define six interfaces such as adding group interface, deleting group interface, adding group member interface, deleting group member interface, modifying short number interface and modifying call permission interface on the interface machine through TCP/IP protocol.
- Basic field The relevant information of the changed group is packaged and sent to the interface machine, and the interface machine distributes the instructions to the SCP distributed by the group. At this time, due to the addition of the interface machine, it is specifically used to help the SMP distribute various instructions to the SCP to manage it in a unified manner, so that the resource consumption burden of the SMP is reduced, and the efficiency of the system is improved.
- Step 3 When the user triggers an intelligent service through the SCP to which the user belongs, the SCP judges, controls, and charges the out-of-network call in the network.
- FIG. 3 is a flow chart of the calling party in the first embodiment of the present invention.
- the calling process is as shown in FIG. 3, and includes the following steps: Step 1 a.
- Step 1 a When the SCP receives the call, it searches for the judgment in the service database of the SCP.
- step 2a Whether the calling user belongs to the SCP, if yes, after obtaining the group number of the calling user, further determining whether the calling user dials a long number or a short number, and if it is a long number, performing step 2a, if it is a short number, Then, step 3a is performed; otherwise, step 4a is performed; step 2a, according to the long number and the group number of the calling user, the calling user returns Look up the called user in the service database of the SCP, and determine whether the called user and the calling user belong to the same group.
- Step 3a according to the short number and the main The group number of the user is called, and the called user is searched in the service database of the SCP to which the calling user belongs, and it is determined whether the called user and the calling user belong to the same group. If yes, step 5a is performed, otherwise step 6a is performed; 4a, the SCP forwards the call directly to the MSC for processing, no longer performs call control and call billing; Step 5a, performs billing control and preferential billing according to the calling user account balance and call type; Step 6a, according to the calling party User account balances and call types are used for billing control and non-concession billing.
- Step lb When receiving a call, the SCP searches for a judgment in the service database of the SCP. If the user is the short number, then Step 3b is performed; otherwise, step 4b is performed; Step 2b, according to the long number of the calling user and the group number of the called party, the calling user is searched in the service database of the SCP to which the called user belongs, and the called party is judged.
- step 5b Whether the user and the calling user belong to the same group, if yes, step 5b is performed, otherwise step 6b is performed; step 3b, according to the short number of the calling user and the group number of the called party, the called user belongs to In the service database of the SCP, the calling user is searched to determine whether the called user and the calling user belong to the same group. If yes, step 5b is performed; otherwise, step 6b is performed; step 4b, The SCP forwards the call directly to the MSC for processing, and no longer performs call control and call charging; Step 5b, performs charging control and preferential charging according to the called user account balance and call type; Step 6b, according to the called user account balance and Call type for billing control and non-concession Fee.
- Step 1 c When the SCP receives the call, it searches for the judgment in the service database of the SCP.
- step 2c the group of the user who has transferred forward occurs
- the number and the number of the forwarded user are searched for the forwarded user in the service database of the SCP to which the forwarded user belongs, and it is determined whether the forwarded user and the forwarded user belong to the same group, and if so, Then step 4c is performed, otherwise step 5c is performed; it should be noted that the forwarding service is triggered as an intelligent service by the group member in the HLR. If a user needs to call forward, then the contract information is in the HLR.
- Step 3c The SCP directly forwards the call to the MSC for processing, and no longer performs call control and call charging; Step 4c, performs charging control and preferential charging according to the account balance and call type of the user who has forwarded; Step 5c The charging control and non-concessional charging are performed according to the account balance and call type of the user who has transferred.
- the mobile virtual private network group intelligent service implementation method in this embodiment is different from the first embodiment in that the group information is created in the group information.
- step 3 when the group member triggers an intelligent service through its belonging SCP, the calling process determines the calling party and the called party. After not belonging to the same group, it is necessary to further determine whether the called user belongs to the out-of-network number group of the group in which the calling user is located, so as to win the call between the users in the network, the users in the network and the users outside the network. Differentiating between the call and the call between the user in the network and the user outside the ordinary network, respectively, call control and charging are performed to realize different preferential billing.
- FIG. 6 is a flowchart of a calling party according to a second embodiment of the present invention.
- the calling process is as shown in FIG. 6 and includes the following steps: Step 1 a.
- the SCP When the SCP receives the call, it searches in the service database of the SCP to determine whether the calling user belongs to the SCP. If yes, after obtaining the group number of the calling user, it further determines the calling of the calling user. Is the long number or short number of the called user, if it is a long number, step 2a is performed; if it is a short number, step 3 is performed; otherwise, step 4a is performed; step 2a, according to the long number and the calling user's location
- the group number is used to find the called user in the service database of the SCP to which the calling user belongs, and determine whether the called user and the calling user belong to the same group.
- step 5a If yes, step 5a is performed; otherwise, step 6a is performed; step 3a, According to the short number and the group number of the calling user, the called user is searched in the service database of the SCP to which the calling user belongs, and it is determined whether the called user and the calling user belong to the same group. If yes, step 5a is performed.
- step 6a is performed;
- Step 4a the SCP forwards the call directly to the MSC for processing, and no longer performs call control and call charging;
- Step 5a according to the calling user
- the account balance and the call type are subject to the first level of preferential billing;
- Step 6a determining whether the called user belongs to the out-of-network number group of the group in which the calling user is located, and if so, proceeding according to the balance of the calling user account and the call type.
- the second-level preferential billing otherwise, the third-level preferential billing is performed according to the balance of the calling user account and the type of the call.
- FIG. 7 is a flow chart of a called party according to a second embodiment of the present invention.
- the called process is as shown in FIG. 7 and includes the following steps: Step 1 a.
- the SCP receives a call, it searches for a judgment in the service database of the SCP.
- step 2a is performed, if it is a short number Then, step 3 is performed; otherwise, step 4a is performed; step 2a, according to the long number and the group number of the called user, the called user is searched in the service database of the SCP to which the called user belongs, and the called user is judged.
- step 5a determines whether it is the same group as the calling user, if yes, step 5a is performed, otherwise step 6a is performed; step 3a, according to the short number and the group number of the called user, the service of the SCP to which the called user belongs Find the called user in the database to determine whether the called user and the calling user belong to The same group, if yes, go to step 5a, otherwise go to step 6a; Step 4a, SCP forward the call directly to the MSC for processing, no longer call control and call billing; Step 5a, according to the account balance and call of the called user The type carries the first-level preferential billing; Step 6a, determines whether the calling user belongs to the extranet number group of the group where the called user is located, and if so, performs the second-level preferential charging according to the called user account balance and the call type, otherwise According to the called user account balance and call type, the third level of preferential billing is performed.
- how to perform charging control and preferential according to the balance of the calling user account and the type of the call may be set by the mobile operator, but is not limited thereto.
- the forward flow process after determining that the forwarded user and the forwarded user do not belong to the same group, it is further determined whether the forwarded user belongs to the out-of-network number of the group in which the forwarded user belongs. Group, in order to distinguish between the forward call of the users in the network, the forward call of the user in the network to the outgoing user of the ordinary network, and the forward call of the user in the network to the external number group user in the forwarding process. , respectively, call control and billing to achieve different preferential billing.
- Step 1 c When receiving a call, the SCP searches for the judgment in the service database of the SCP.
- step 2c Whether the user who has transferred forward belongs to the SCP, and if yes, after obtaining the group number of the user who has transferred forward, step 2c is performed; otherwise, step 3c is performed; step 2c, the group of the user who has transferred forward occurs Number and forwarded user number, look up the forwarded user in the SCP business database to which the forwarded group member belongs, and determine whether the forwarded user and the forwarded user belong to the same group, if Step 4c is performed, otherwise step 5c is performed; Step 3c, the SCP forwards the call directly to the MSC for processing, no longer performs call control and call billing; Step 4c, based on the user account balance and call type in which the forwarding occurs The first level of preferential billing; Step 5c, judging whether the forwarded user belongs to the group outside the group where the user who is forwarding occurs The number group, if it is, will be subject to the second-level preferential billing according to the group member account balance and call type of the forwarded group.
- the mobile virtual private network group intelligent service implementation method in this embodiment is different from the first embodiment in that, when the group is created, in the group Adding a field containing information about the closed user group in the network corresponding to the group, in addition, in step 3, when the user triggers an intelligent service through the SCP to which the user belongs, the calling process and the called process are After judging that the main user belongs to the same group, it is further determined whether the main called user belongs to the closed user group in the same network, so as to close the call between the users in the network, the call between ordinary users in the network, and the users in the network.
- FIG. 9 is a flowchart of a calling party according to a third embodiment of the present invention.
- the calling process is as shown in FIG. 9 and includes the following steps: Step 1 a.
- the SCP receives a call, it searches for a judgment in the service database of the SCP.
- step 2a Whether the calling user belongs to the SCP, and if yes, after obtaining the group number of the calling user, further determining whether the calling user dials a long number or a short number, and if it is a long number, performing step 2a, if it is a short number, Then, step 3 is performed; otherwise, step 4a is performed; step 2a, according to the long number and the group number of the calling user, the called user is searched in the service database of the SCP to which the calling user belongs, and the called user is determined.
- step 5a Whether the calling user belongs to the same group, if yes, step 5a is performed, otherwise step 6a is performed; step 3a, according to the short number and the group number where the calling user is located, the service database of the SCP to which the calling user belongs Find the called user, determine whether the called user and the calling user belong to the same group, if yes, go to step 5a, otherwise go to step 6a; Step 4a, SCP will call Directly handed over to the MSC for processing, no more call control and call billing; Step 5a, determining whether the calling user and the called user belong to the closed network user group in the same network, and if so, according to the calling user account balance and call type The first level of preferential billing, otherwise the second level of preferential billing is performed according to the calling user account balance and the call type; Step 6a, the third level of preferential billing is performed according to the calling user account balance and the call type.
- Step lb When receiving a call, the SCP searches for a judgment in the service database of the SCP. If the user is the shortest number, go to step Sb. 3b; Otherwise, step 4b is performed; step 2b, according to the long number and the group number of the called user, look up the calling user in the service database of the SCP to which the called user belongs, and determine the called user and the calling user.
- step 5b Whether it belongs to the same group, if yes, step 5b is performed, otherwise step 6b is performed; step 3b, according to the short number and the group number of the called user, find the main in the service database of the SCP to which the called user belongs. Call the user to determine whether the called user and the calling user belong to the same group. If yes, go to step 5b, otherwise go to step 6b; Step 4b, SCP will directly transfer the call. After the MSC process, no call control and call billing are performed; Step 5b, determining whether the calling user and the called user belong to the closed network group in the same network, and if so, performing the first level according to the called user account balance and the call type.
- the preferential billing is performed, otherwise the second-level preferential billing is performed according to the called user account balance and the call type; Step 6a, the third-level preferential billing is performed according to the called user account balance and the call type.
- the forward flow process after determining whether the forwarded user and the forwarded user belong to the same group, it is further determined whether the forwarded user belongs to the closed network user group in the same network, so as to be forwarded.
- the forward call between the users in the closed user group in the network, the forward call between the ordinary users in the network, and the forward call from the users in the network to the users outside the network are distinguished, respectively. Call control and billing to achieve different preferential billing.
- Step 1 c When the SCP receives a call, it searches for a judgment in the service database of the SCP. Before the occurrence Whether the transferred user belongs to the SCP, if yes, obtain the group number of the user who has forwarded, go to step 2c, otherwise go to step 3c; Step 2c, according to the group number and forwarding of the user who has forwarded the transfer The number of the user to be accessed is searched for the forwarded user in the service database of the SCP to which the forwarded user belongs, and it is determined whether the forwarded user and the forwarded user belong to the same group.
- step 4c determines the user who has forwarded the call and the former Whether the transferred user belongs to the closed user group in the same network, and if so, the first-level preferential charging is performed according to the user account balance and the call type in which the forwarding occurs, otherwise, the user account balance of the forwarded account is The call type performs the second-level preferential charging; in step 5c, the third-level preferential charging is performed according to the user account balance and the call type in which the forwarding occurs.
- the method includes: a configuration module, configured to configure a group number and an SCP distributed by the group on the SMP.
- the correspondence relationship of the module numbers is configured with the related data information of the group in the business database of each SCP distributed by the group.
- the configuration of the related data information of the group refers to filling in the business database of each SCP distributed by the group with relevant data information of the group on all SCPs of the group, and the related data information of the group includes : Group information and group member information, the group member information includes long and short numbers of the group members, call rights of the group members, and attribution information of the group members to the SCP, optionally, the related data information of the group is further Including the group's extranet number group and closed user group information.
- the management module is used to uniformly manage related data information of the group distributed on different SCPs.
- the instructions are sent to the SCP distributed by the group, and then the SCP Group creation and deletion, group member addition and deletion, group member short number setting and modification, group member call permission setting and modification in the local database.
- the management module can also use the group's extranet number group and closure.
- the group information is set and modified.
- the management module can be part of the SMP when it is implemented.
- the service execution module is configured to judge, control, and charge a call outside the network when the user triggers a virtual private network intelligent service.
- the service execution module includes a calling execution module, a called execution module, and a forward execution module.
- the business execution module can be one of the components of the SCP.
- the calling execution module is configured to determine whether the calling user belongs to the SCP, and if the calling user belongs to the SCP, further determine whether the called user and the calling user belong to the same group, and if so, The calling user account balance and the call type are used for charging control and preferential charging, otherwise charging control and non-concessional charging are performed according to the calling user account balance and the call type; if the calling user is not attributable to the SCP, The call is directly forwarded to the MSC for processing, and call control and call accounting are no longer performed.
- the called execution module is configured to determine whether the called user belongs to the SCP, and if the called user belongs to the SCP, further determine whether the called user and the calling user belong to the same group, and if so, according to the called party
- the user account balance and the call type are used for charging control and preferential charging, otherwise the charging control and non-concessional charging are performed according to the called user account balance and the call type; if the called user does not belong to the SCP, the The call is directly forwarded to the MSC for processing, and call control and call accounting are no longer performed.
- the forward execution module is configured to determine whether the user who is forwarded belongs to the current SCP, and if the user who is forwarded belongs to the SCP, further determines whether the forwarded user and the forwarded user belong to the same group. If yes, the charging control and the preferential charging are performed according to the user account balance and the call type in which the forwarding occurs; otherwise, the charging control and the non-concessional charging are performed according to the user account balance and the call type in which the forwarding occurs; If the forwarded user does not belong to the SCP, the call is directly forwarded to the MSC for processing, and call control and call accounting are no longer performed.
- the functions performed by the calling execution module, the called execution module, and the forward execution module described in this embodiment are all related to the calling process, the called process, and the called process in the first embodiment of the present invention.
- the forwarding process corresponds to the first embodiment, and the functions performed by the calling execution module, the called execution module, and the forward execution module are not limited to the first embodiment.
- the calling process, the called process, and the forwarding process in the third embodiment correspond to each other.
- the embodiment of the invention uses SMP to manage multiple SCPs to ensure data synchronization between SCPs. Business Implemented on each SCP distributed across the SCP Mobile Virtual Private Network Group. Each group is assigned a group number in the whole network, which uniquely identifies the group.
- the group number is unique on each SCP, but it can exist simultaneously on multiple SCPs in the whole network.
- the SMP uniformly manages various transactions of the group distributed on different SCPs, and ensures that the related data information of the group of the SCPs distributed by the group is synchronized.
- the mobile virtual private network group intelligent service implementation method according to the embodiment of the present invention is powerful. Achieving a single order, the technical solution of the present invention can realize all the business attributes of the mobile virtual private network group, and is a very good method for solving the mobile virtual private network group across the SCP, and has high economic benefits.
- the technical means and functions of the present invention for achieving the intended purpose can be more deeply and specifically understood by the description of the specific embodiments.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
- Meter Arrangements (AREA)
Description
移动虚拟专用网集团智能业务实现方法和装置 技术领域 本发明涉及移动智能网络技术领域,尤其涉及一种移动虚拟专用网集团 智能业务实现方法和装置。 背景技术 移动智能网系统作为移动通信行业新兴的业务服务网络,是电信运营商 的主要业务增长点之一, 它能够方便、 灵活、 经济、 有效地提供各种增值业 务, 并通过与营业系统、 客户服务中心、 短消息中心以及银行系统的集成, 为用户提供更优质、 及时、 人性化的服务。 移动虚拟专用网集团业务是一项应用十分广泛的智能网业务。该业务以 集团客户为目标, 例如, 企业、 团体、 学校、 医院、 政府机关等。 集团客户 申请了该业务后, 可以才艮据该集团的特点制定其内部的短号码编号方案, 以 便记忆和管理。 在一个集团内部, 短号码可以唯一标识一个集团成员, 以企 业集团客户为例, 短号码可以包括职位、 工号等信息, 当集团成员的真实号 码改变时可以通过删除和重新添加集团成员的方式修 丈真实号码, 不影响其 短号码的编号方案, 这样, 集团内部的员工不会因移动通信终端真实号码的 变更而影响工作联系 , 集团内用户只要记住集团内部短号码就可以找到他希 望找到的用户。 移动虚拟专用网集团业务可以根据呼叫的信息将呼叫加以详细分类:比 如在一个集团内部的呼叫, 称为网内呼叫; 一个集团内还可以再成立一个或 多个小单位的群体, 组成闭合用户群, 闭合用户群里面发生的呼叫叫做网内 闭合用户群呼叫; 一个集团还可以设置一些重要的网外客户, 组成网外号码 组, 当该集团内的用户向网外号码组的用户呼叫称为网外号码组呼叫。 业务 可以 居呼叫类型的不同, 对网内呼叫、 网内闭合用户群呼叫、 网外号码组 呼叫和普通网外呼叫给予不同程度的优惠, 使得使用该业务的集团的通讯费 用降低。 而对于运营商来说, 该业务吸引了大的集团客户, 可以实现其较好 的利润。 因此该业务即可使集团通讯费用降 方便集团内部员工使用, 又 可使运营商吸引大量的集团客户, 较好的实现其利润。 这些特性使得该业务 得到广泛应用。
目前在实现移动虚拟专用网集团业务时,一个移动虚拟专用网集团只能 归属于一个业务控制点(Service Control Point, 筒称为 SCP ), 但随着经济的 发展, 社会企业和团体等大量需要该业务的集团用户发展迅速, 跨省乃至跨 国集团大量出现, 集团用户在空间上的扩展已经成为必然的趋势。 因此, 一 个集团用户只分布在一个 SCP的^!犬况不能满足实际的需要。 另外, 随着虚拟集团业务的发展, 很多原来的智能网设备已经不能满足 业务发展需求, 急需扩容, 这样就出现了如何充分利用现有的智能设备的问 题, 这一问题是目前本领域亟待解决的。 发明内容 本发明要解决的技术问题是相关技术中移动虚拟专用网集团只能归属 于一个业务控制点而导致已经不能满足虚拟集团业务发展需求的问题。为此, 提供一种移动虚拟专用网集团智能业务实现方案,为跨 SCP虚拟专用网集团 用户提供非跨 SCP虚拟专用网集团用户所具有的所有业务属性。 本发明采用的技术方案是, 所述移动虚拟专用网集团智能业务实现方 法, 包括: 在业务管理点 ( service management point, 筒称为 SMP )上配置 集团编号与该集团所分布的 SCP 模块号的对应关系, 在集团所分布的每个 SCP的业务数据库中配置该集团的相关数据信息; 统一管理分布在不同的 SCP上集团的相关数据信息; 当用户触发某项业务时, 对呼叫进行判断、 控制及计费。 所述统一管理分布在不同的 SCP上集团的相关数据信息 , 包括当集团 的相关数据信息变化时,更新并同步该集团分布的 SCP上的集团的相关数据 信息。 所述集团的相关数据信息包括: 集团信息和集团成员信息。 所述更新并同步该集团分布的 SCP上的集团的相关数据信息包括: SMP 根据集团所分布的 SCP模块号或者通过接口机, 依次向相关的 SCP发送指 令,所述相关的 SCP收到指令后在本地数据库中对集团相关数据信息进行更 新。 所述对集团的相关数据信息进行更新至少包括以下其中之一: 集团的创 建和删除、 集团成员的增加和删除、 集团成员短号码的设置和 4爹改、 集团成 员呼叫权限的设置和 4爹改。
所述对呼叫判断、 控制及计费贯穿于主叫流程、 被叫流程和前转流程。 作为一种优选的技术方案,所述移动虚拟专用网集团智能业务实现方法 中的所述主叫流程包括:
SCP收到呼叫时, 判断主叫用户是否归属于本 SCP, 如果主叫用户归属 于本 SCP, 则进一步判断被叫用户与主叫用户是否归属于同一集团, 若是, 则根据主叫用户账户余额和呼叫类型进行计费控制和优惠计费 , 否则根据主 叫用户账户余额和呼叫类型进行计费控制和非优惠计费; 如果主叫用户不归 属于本 SCP, 则将该呼叫直接转交 MSC处理, 不再进行呼叫控制及呼叫计 费; 所述被叫流程包括:
SCP收到呼叫时, 判断被叫用户是否归属于本 SCP, 如果被叫用户归属 于本 SCP, 则进一步判断被叫用户与主叫用户是否归属于同一集团, 若是, 则根据被叫用户账户余额和呼叫类型进行计费控制和优惠计费 , 否则根据被 叫用户账户余额和呼叫类型进行计费控制和非优惠计费; 如果被叫用户不归 属于本 SCP, 则将该呼叫直接转交 MSC处理, 不再进行呼叫控制及呼叫计 费; 所述前转流程包括:
SCP收到呼叫, 判断发生前转的用户是否归属于本 SCP, 如果发生前转 的用户归属于本 SCP , 则进一步判断发生前转的用户与前转到的用户是否属 于同一集团, 若是, 则才艮据发生前转的用户账户余额和呼叫类型进行计费控 制和优惠计费, 否则才艮据发生前转的用户账户余额和呼叫类型进行计费控制 和非优惠计费; 如果发生前转的用户不归属于本 SCP, 则将该呼叫直接转交 MSC处理, 不再进行呼叫控制及呼叫计费。 作为另一种优选的技术方案,所述移动虚拟专用网集团智能业务实现方 法,在所述集团信息中增加一个包含该集团所对应的网外号码组信息的字段, 所述主叫流程包括如下步骤:
SCP收到呼叫时, 判断主叫用户是否归属于本 SCP, 如果主叫用户归属 于本 SCP, 则进一步判断被叫用户与主叫用户是否归属于同一集团, 若是, 则根据主叫用户账户余额和呼叫类型进行第一级优惠计费, 否则再进一步判
断被叫用户是否属于主叫用户所在集团的网外号码组, 若是, 则根据主叫用 户账户余额和呼叫类型进行第二级优惠计费, 否则, 才艮据主叫用户账户余额 和呼叫类型进行第三级优惠计费; 如果主叫用户不归属于本 SCP, 则将该呼 叫直接转交 MSC处理, 不再进行呼叫控制及呼叫计费; 所述被叫流程包括如下步骤:
SCP收到呼叫时, 判断被叫用户是否归属于本 SCP, 如果被叫用户归属 于本 SCP, 则进一步判断被叫用户与主叫用户是否归属于同一集团, 若是, 则根据被叫用户账户余额和呼叫类型进行第一级优惠计费, 否则再进一步判 断主叫用户是否属于被叫用户所在集团的网外号码组, 若是, 则根据被叫用 户账户余额和呼叫类型进行第二级优惠计费, 否则, 根据被叫用户账户余额 和呼叫类型进行第三级优惠计费; 如果被叫用户不归属于本 SCP, 则将该呼 叫直接转交 MSC处理, 不再进行呼叫控制及呼叫计费; 所述前转流程包括:
SCP收到呼叫, 判断发生前转的用户是否归属于本 SCP, 如果发生前转 的用户归属于本 SCP, 则进一步判断发生前转的用户与前转到的用户是否属 于同一集团, 若是 , 则才艮据发生前转的用户账户余额和呼叫类型进行第一级 优惠计费, 否则再进一步判断前转到的用户是否属于网外号码组, 若是, 则 才艮据发生前转的用户账户余额和呼叫类型进行第二级优惠计费, 否则, 根据 发生前转的用户账户余额和呼叫类型进行第三级优惠计费; 如果发生前转的 用户不归属于本 SCP, 则将该呼叫直接转交 MSC处理, 不再进行呼叫控制 及呼叫计费。 作为另一种优选的技术方案,所述移动虚拟专用网集团智能业务实现方 法, 在所述集团信息中增加一个包含该集团所对应的网内闭合用户群信息的 字段, 所述主叫流程包括如下步骤:
SCP收到呼叫时, 判断主叫用户是否归属于本 SCP, 如果主叫用户归属 于本 SCP, 则进一步判断被叫用户与主叫用户是否归属于同一集团, 若是, 则再进一步判断主叫用户和被叫用户是否属于同一网内闭合用户群, 若是, 则根据主叫用户账户余额和呼叫类型进行第一级优惠计费 , 否则根据主叫用 户账户余额和呼叫类型进行第二级优惠计费; 否则才艮据主叫用户账户余额和
呼叫类型进行第三级优惠计费; 如果主叫用户不归属于本 SCP, 则将该呼叫 直接转交 MSC处理 , 不再进行呼叫控制及呼叫计费; 所述被叫流程包括:
SCP收到呼叫时, 判断被叫用户是否归属于本 SCP, 如果被叫用户归属 于本 SCP, 则进一步判断被叫用户与主叫用户是否归属于同一集团, 若是, 则再进一步判断主叫用户和被叫用户是否属于同一网内闭合用户群, 若是, 则才艮据被叫用户账户余额和呼叫类型进行第一级优惠计费, 否则才艮据被叫用 户账户余额和呼叫类型进行第二级优惠计费; 否则才艮据被叫用户账户余额和 呼叫类型进行第三级优惠计费; 如果被叫用户不归属于本 SCP, 则将该呼叫 直接转交 MSC处理, 不再进行呼叫控制及呼叫计费; 所述前转流程包括:
SCP收到呼叫, 判断发生前转的用户是否归属于本 SCP, 如果发生前转 的用户归属于本 SCP , 则进一步判断发生前转的用户与前转到的用户是否属 于同一集团, 若是, 则再进一步判断发生前转的用户和前转到的用户是否属 于同一网内闭合用户群, 若是, 则才艮据发生前转的用户账户余额和呼叫类型 进行第一级优惠计费, 否则, 才艮据发生前转的用户账户余额和呼叫类型进行 第二级优惠计费; 否则才艮据发生前转的用户账户余额和呼叫类型进行第三级 优惠计费; 如果发生前转的用户不归属于本 SCP, 则将该呼叫直接转交 MSC 处理, 不再进行呼叫控制及呼叫计费。 本发明还提供一种移动虚拟专用网集团智能业务实现装置, 包括: 配置模块, 用于在 SMP上配置集团编号与该集团所分布的 SCP模块号 的对应关系 ,在集团所分布的每个 SCP的业务数据库中配置该集团的相关数 据信息; 管理模块, 用于统一管理分布在不同的 SCP上集团的相关数据信息; 业务执行模块, 用于当用户触发某项智能业务时, 对呼叫进行判断、 控 制及计费。 所述统一管理分布在不同的 SCP上集团的相关数据信息 , 包括当集团 的相关数据信息变化时,更新并同步该集团分布的 SCP上的集团的相关数据 信息。 所述集团的相关数据信息包括: 集团信息、 集团成员的长号码和短号
码、 集团成员的呼叫权限以及集团成员对 SCP的归属信息。 所述业务执行模块包括主叫执行模块、 被叫执行模块和前转模块。 采用上述技术方案, 本发明至少具有下列优点: 本发明所述移动虚拟专用网集团智能业务实现方法和装置, 在 SMP上 配置集团编号和该集团所分布的 SCP模块号的对应关系 ,在集团所分布的每 个 SCP的业务数据库中配置该集团的相关数据信息,统一管理分布在不同的 SCP上集团的相关数据信息, 一旦集团的相关数据信息变化时, 该集团分布 的所有 SCP 上的集团的相关数据信息都能得到更新并同步, 因此为跨 SCP 虚拟专用网集团用户提供非跨 SCP 虚拟专用网集团用户所具有的所有业务 属性。 采用本发明的技术方案, 不仅充分利用了现有的智能网设备, 降低了 硬件成本 , 而且对集团的相关数据信息的管理和维护也极为灵活方便。 附图说明 图 1为本发明第一实施例中移动虚拟专用网组网原理图; 图 2为根据本发明实施例的在 SMP上配置的集团号和 SCP模块号的对 应关系图; 图 3为本发明第一实施例中的主叫流程图; 图 4为本发明第一实施例中的被叫流程图; 图 5为本发明第一实施例中的前转流程图; 图 6为本发明第二实施例中的主叫流程图; 图 7为本发明第二实施例中的被叫流程图; 图 8为本发明第二实施例中的前转流程图; 图 9为本发明第三实施例中的主叫流程图; 图 10为本发明第三实施例中的被叫流程图; 图 11为本发明第三实施例中的前转流程图;
图 12为本发明第四实施例中所述移动虚拟专用网集团智能业务实现装 置的示意图。 具体实施方式 功能相克述 考虑相关技术中移动虚拟专用网集团只能归属于一个业务控制点而导 致已经不能满足虚拟集团业务发展需求的问题, 本发明实施例提供了一种移 动虚拟专用网集团智能业务实现方案, 该方案处理原则如下: 在 SMP 上配 置集团编号与该集团所分布的 SCP模块号的对应关系,在集团所分布的每个 SCP 的业务数据库中配置该集团的相关数据信息; 统一管理分布在不同的 SCP上集团的相关数据信息; 当用户触发某项智能业务时,对呼叫进行判断、 控制及计费。 需要说明的是, 在不冲突的情况下, 本申请中的实施例及实施例中的特 征可以相互组合。 下面将参考附图并结合实施例来详细说明本发明。 在以下实施例中,在附图的流程图示出的步骤可以在诸如一组计算机可 执行指令的计算机系统中执行, 并且, 虽然在流程图中示出了逻辑顺序, 但 是在某些情况下 , 可以以不同于此处的顺序执行所示出或描述的步骤。 为更进一步阐述本发明为达成预定目的所采取的技术手段及功效,以下 结合附图及较佳实施例 , 对本发明提出的所述移动虚拟专用网集团智能业务 实现方法和装置, 详细说明如后。 图 1为本发明第一实施例中移动虚拟专用网组网原理图, 如图 1所示,
SMP与业务管理接入点 ( service management access point, 筒称为 SMAP ) 之间、 SMP与 SCP之间均通过 TCP/IP协议相互通讯。 SCP、 移动交换中心 ( Mobile Switching Center, 筒称为 MSC ) 或者拜访位置寄存器 ( Visitor Location Register, 筒称为 VLR )或者业务交换点(Service Switching Point, 筒 称为 SSP)、 归属位置寄存器 (Home Location Register, 筒称为 HLR)之间通过 七号信令网相互连接, 其中第一业务控制点 SCP1 和第二业务控制点 SCP2 之间通过七号信令网和 TCP/IP 网络连接。 在移动虚拟专用网中为每一个集 团指定唯一的集团编号,移动通信的各项业务在跨 SCP移动虚拟专用网的集 团所分布的每个 SCP上实现。
图 1 中集团 11分布在第一业务控制点 SCP1 和第二业务控制点 SCP2 上面, 则在这两个业务控制点上分别加载业务。 集团 11的编号在该集团所分 布的 SCP上都是相同的。 SMP通过 SMAP来对运行在第一业务控制点 SCP1 和第二业务控制点 SCP2上的业务进行管理。 MSC或者 VLR实现业务交换 功能, HLR存储并管理移动用户或集团成员的签约信息。 在判断出某个用户 是归属于本 SCP的某个集团时才能将该用户称作该集团的集团成员。 本实施例中所述移动虚拟专用网集团智能业务实现方法, 包括如下步 骤: 步骤一、在 SMP上配置集团编号与该集团所分布的 SCP模块号的对应 关系, 在集团所分布的每个 SCP 的业务数据库中配置该集团的相关数据信 息。 具体地, 图 2为根据本发明实施例的在 SMP上配置的集团号和 SCP模 块号的对应关系图 , 如图 2所示, 在 SMP上配置了集团编号和 SCP模块号 的对应关系, 每个 SCP有一个唯一的 SCP模块号, SCP模块号对应了 SCP 的 IP地址。 第一业务控制点 SCP1 的模块号为 135 , 第二业务控制点 SCP2 模块号为 136。 知道了 SCP的模块号以后, SMP可以通过 SCP模块号来区 分不用的 SCP, 并利用 TCP/IP协议来对 SCP上的数据进行操作, 以实现对 各个 SCP中集团的相关数据进行统一管理。 在该集团所分布的每个 SCP上业务数据库中填写该集团在其分布的所 有 SCP上的集团的相关数据信息, 所述集团的相关数据信息包括: 集团信息 和用户信息, 用户信息包括: 集团成员的长号码和短号码、 集团成员的呼叫 权限以及集团成员对 SCP的归属信息。 对一个特定的 SCP来说, 集团成员分为两种: 第一种集团成员归属于 本 SCP即该集团成员签约了虚拟专用网智能业务, 将触发本 SCP的虚拟专 用网智能业务, 第二种集团成员不归属于本 SCP, 不会触发虚拟专用网智能 业务到本 SCP, 因此需要在 SCP的业务数据库的用户信息表里面标识集团成 员对 SCP的归属信息, ^区别这两种集团成员。 步骤二、 SMP统一管理该集团分布的 SCP上的集团的相关数据信息。 具体的, 当集团信息、 集团成员信息等发生变化时, SMP 需要更新并 同步该集团分布的 SCP上的集团的相关数据信息,所述集团成员信息包括集
团成员的长号码和短号码、集团成员的呼叫权限以及集团成员对 SCP的归属 信息等。 所述更新并同步该集团分布的 SCP上的集团的相关数据信息包括: SMP 根据该集团所分布的 SCP模块号, 依次向该集团所分布的 SCP发送指令, SCP收到指令后在本地数据库中对集团相关数据信息进行更新。 所述对集团 的相关数据信息进行更新至少包括一下其中之一: 集团的创建和删除、 集团 成员的增加和删除、 集团成员短号码的设置和修改、 集团成员呼叫权限的设 置和修改。 需要说明的是, 由于每个集团成员均具有唯一的长号码, 如果需 要对集团成员的长号码进行设置和修改,相当于对集团成员进行增加和删除。 为此 SMP需要通过 TCP/IP协议对 SCP定义如下接口:
1. 增加集团时所用的接口, 筒称增加集团接口, 通过该接口发送指令 所具有的基本字段如下: 集团编号, 集团所分布的 SCP模块号; 2. 删除集团时所用的接口, 筒称删除集团接口, 通过该接口发送指令 所具有的基本字段如下: 集团编号, 集团所分布的 SCP的模块号;
3. 增加集团成员时所用的接口, 筒称增加集团成员接口, 通过该接口 发送指令所具有的基本字段如下: 集团编号, 集团成员长号码, 集团成员短号码, 集团成员呼叫权限, 集团成员归属的 SCP模块号,
集团所分布的 SCP的模块号;
4. 删除集团成员时所用的接口, 筒称删除集团成员接口, 通过该接口 发送指令所具有的基本字段如下: 集团编号, 成员用户长号码, 集团所分布的 SCP模块号;
5. 设置或修改集团成员短号码是所用的接口, 筒称修改短号码接口, 通过该接口发送指令所具有的基本字段如下: 集团编号, 集团成员长号码, 集团成员新短号码, 集团所分布的 SCP模块号;
6. 设置或 4爹改集团成员的呼叫权限时所用的接口 , 筒称^"改呼叫权限 接口, 通过该接口发送指令所具有的基本字段如下: 集团编号, 集团成员长号码, 集团成员新呼叫权限, 集团所分布的 SCP模块号。 以增加集团成员为例 , 描述一下 SMP统一管理该集团分布的 SCP进行 管理的过程, 集团管理操作员通过第一业务管理接入点 SMAP1发起增加一 个长号码为 8613905190600的集团成员到集团 11 的操作, 指定其短号码为 61001 , 呼叫权限为网内呼叫, 该集团成员归属于模块号为 135 的第一业务 控制点 SCP1。
SMP查询本地数据库中的配置信息, 获知集团 11分布在模块号为 135 的第一业务控制点 SCP1和模块号为 137的第二业务控制点 SCP2上。 SMP
收到第一业务管理接入点 SMAP1 发送过来的集团编号、 集团成员长号码和 短号码、 呼叫权限、 集团成员对 SCP 的归属信息, 以及集团所分布的 SCP 信息以后,按照集团所分布的 SCP信息,将包含集团编号、集团成员长号码、 集团成员短号码、 集团成员呼叫权限、 集团成员归属的 SCP模块号和集团所 分布的 SCP的模块号等字段信息的指令依次发送给第一业务控制点 SCP1和 第二业务控制点 SCP2的增加集团成员接口。 然后, 第一业务控制点 SCP1和第二业务控制点 SCP2将集团号码、 集 团成员长号码和短号码、 呼叫权限信息在本地业务数据库中添加, 在第一业 务控制点 SCP1 上设置该集团成员归属于本 SCP, 在第二业务控制点 SCP2 上设置该集团成员不归属于本 SCP。 优选的,可以在 SMP与 SCP之间连接一台接口机, SMP与接口机之间、 接口机与 SCP之间均通过 TCP/IP协议相互通讯。 SMP可以通过 TCP/IP协 议在接口机上定义增加集团接口、 删除集团接口、 增加集团成员接口、 删除 集团成员接口、 修改短号码接口和修改呼叫权限接口等六个接口及其使用时 所须包含的基本字段。 将发生变化的集团的相关信息打包发送给接口机, 由 接口机向该集团分布的 SCP的分发指令。 此时, 由于增加了接口机, 专门用 于帮助 SMP向 SCP分发各种指令以对其进行统一管理,使 SMP的资源消耗 负担减少, 提高了系统的效率。 步骤三、 当用户通过其归属的 SCP触发某项智能业务时, SCP对网内 网外呼叫进行判断、 控制及计费。 具体地, 智能业务由集团成员在 HLR的签约信息触发, 触发的 SCP为 用户归属的 SCP。 网内网外呼叫判断、 呼叫控制及呼叫计费的过程贯穿于主 叫流程、 被叫流程和前转流程。 图 3为本发明第一实施例中的主叫流程图, 所述主叫流程如图 3所示, 包括如下步骤: 步骤 1 a、 SCP收到呼叫时, 在本 SCP的业务数据库中查找判断主叫用 户是否归属于本 SCP, 如果是, 在获取主叫用户所在的集团编号后, 进一步 判断主叫用户拨打的是长号码还是短号码, 若是长号码, 则执行步骤 2a, 若 是短号码, 则执行步骤 3a; 否则执行步骤 4a; 步骤 2a、 才艮据所述长号码和主叫用户所在的集团编号, 在主叫用户归
属的 SCP的业务数据库中查找被叫用户 ,判断被叫用户与主叫用户是否属于 同一集团, 如果是, 则执行步骤 5a, 否则执行步骤 6a; 步骤 3a、 才艮据所述短号码和主叫用户所在的集团编号, 在主叫用户归 属的 SCP的业务数据库中查找被叫用户,判断被叫用户与主叫用户是否属于 同一集团, 如果是, 则执行步骤 5a, 否则执行步骤 6a; 步骤 4a、 SCP将该呼叫直接转交 MSC处理, 不再进行呼叫控制及呼叫 计费; 步骤 5a、 才艮据主叫用户账户余额和呼叫类型进行计费控制和优惠计费; 步骤 6a、 根据主叫用户账户余额和呼叫类型进行计费控制和非优惠计 费。具体怎样根据主叫用户账户余额和呼叫类型进行计费控制和优惠的方式, 可以由移动运营商自行设定, 但并不限于 jt匕。 图 4为本发明第一实施例中的被叫流程图, 所述被叫流程如图 4所示, 包括如下步骤: 步骤 lb、 SCP收到呼叫时, 在本 SCP的业务数据库中查找判断被叫用 户是否归属于本 SCP, 如果是, 在获取被叫用户所在的集团编号后, 进一步 判断主叫用户的号码是长号码还是短号码, 若是长号码, 则执行步骤 2b, 若 是短号码, 则执行步骤 3b; 否则执行步骤 4b; 步骤 2b、 才艮据所述主叫用户的长号码和被叫所在的集团编号, 在被叫 用户归属的 SCP的业务数据库中查找主叫用户,判断被叫用户与主叫用户是 否属于同一集团, 如果是, 则执行步骤 5b, 否则执行步骤 6b; 步骤 3b、 才艮据所述主叫用户的短号码和被叫所在的集团编号, 在被叫 用户归属的 SCP的业务数据库中查找主叫用户,判断被叫用户与主叫用户是 否属于同一集团, 如果是, 则执行步骤 5b, 否则执行步骤 6b; 步骤 4b、 SCP将该呼叫直接转交 MSC处理, 不再进行呼叫控制及呼叫 计费; 步骤 5b、 根据被叫用户账户余额和呼叫类型进行计费控制和优惠计费; 步骤 6b、 根据被叫用户账户余额和呼叫类型进行计费控制和非优惠计
费。 图 5为本发明第一实施例中的前转流程图 , 所述前转流程如图 5所示, 包括如下步骤: 步骤 1 c、 SCP收到呼叫时, 在本 SCP的业务数据库中查找判断发生前 转的用户是否归属于本 SCP, 如果是, 在获得发生前转的用户所在的集团编 号之后, 执行步骤 2c, 否则执行步骤 3c; 步骤 2c、 才艮据发生前转的用户所在的集团编号和前转到的用户的号码, 在发生前转的用户归属的 SCP的业务数据库中查找前转到的用户,判断发生 前转的用户和前转到的用户是否属于同一集团, 如果是, 则执行步骤 4c, 否 则执行步骤 5c; 需要说明的是, 前转业务作为一种智能业务, 是由集团成员 在 HLR的签约信息触发, 如果一个用户需要发生呼叫前转, 那么它在 HLR 签约信息中必须登记其长号码, 因此, 步骤 2c中所述前转到的用户的号码指 的是长号码。 步骤 3c、 SCP将该呼叫直接转交 MSC处理, 不再进行呼叫控制及呼叫 计费; 步骤 4c、 才艮据发生前转的用户的账户余额和呼叫类型进行计费控制和 优惠计费; 步骤 5c、 才艮据发生前转的用户的账户余额和呼叫类型进行计费控制和 非优惠计费。 本发明第二实施例, 在集团具有网外号码组的情况下, 本实施例所述移 动虚拟专用网集团智能业务实现方法与第一实施例的区别在于, 创建集团时 在所述集团信息中增加一个包含该集团所对应的网外号码组信息的字段, 除 此之外, 在步骤三中当集团成员通过其归属的 SCP触发某项智能业务时, 主 叫流程在判断出主被叫用户不属于同一集团之后 , 还要进一步判断被叫用户 是否属于主叫用户所在集团的网外号码组, 以便^)夺网内用户之间的呼叫、 网 内用户与网外号码组用户之间的呼叫和网内用户与普通网外用户之间的呼叫 这三种情况区别开来, 分别进行呼叫控制和计费, 以实现不同优惠的计费。 图 6为本发明第二实施例中的主叫流程图, 所述主叫流程如图 6所示, 包括如下步骤:
步骤 1 a、 SCP收到呼叫时, 在本 SCP的业务数据库中查找判断主叫用 户是否归属于本 SCP, 如果是, 在获取主叫用户所在的集团编号后, 则进一 步判断主叫用户拨打的是被叫用户的长号码还是短号码 , 若是长号码 , 则执 行步骤 2a, 若是短号码, 则执行步骤 3; 否则执行步骤 4a; 步骤 2a、 才艮据所述长号码和主叫用户所在的集团编号, 在主叫用户归 属的 SCP的业务数据库中查找被叫用户,判断被叫用户与主叫用户是否属于 同一集团, 如果是, 则执行步骤 5a, 否则执行步骤 6a; 步骤 3a、 才艮据所述短号码和主叫用户所在的集团编号, 在主叫用户归 属的 SCP的业务数据库中查找被叫用户,判断被叫用户与主叫用户是否属于 同一集团, 如果是, 则执行步骤 5a, 否则执行步骤 6a; 步骤 4a、 SCP将该呼叫直接转交 MSC处理, 不再进行呼叫控制及呼叫 计费; 步骤 5a、 才艮据主叫用户的账户余额和呼叫类型进行第一级优惠计费; 步骤 6a、 判断被叫用户是否属于主叫用户所在集团的网外号码组, 若 是, 则才艮据主叫用户账户余额和呼叫类型进行第二级优惠计费, 否则, 根据 主叫用户账户余额和呼叫类型进行第三级优惠计费。 具体怎样才艮据主叫用户 账户余额和呼叫类型进行计费控制和优惠的方式, 可以由移动运营商自行设 定, 但并不限于此。 图 7为本发明第二实施例中的被叫流程图, 所述被叫流程如图 7所示, 包括如下步骤: 步骤 1 a、 SCP收到呼叫时, 在本 SCP的业务数据库中查找判断被叫用 户是否归属于本 SCP, 如果是, 在获取被叫用户所在的集团编号后, 则进一 步判断主叫用户的号码是长号码还是短号码 , 若是长号码 , 则执行步骤 2a, 若是短号码, 则执行步骤 3; 否则执行步骤 4a; 步骤 2a、 才艮据所述长号码和被叫用户所在的集团编号, 在被叫用户归 属的 SCP的业务数据库中查找被叫用户,判断被叫用户与主叫用户是否属于 同一集团, 如果是, 则执行步骤 5a, 否则执行步骤 6a; 步骤 3a、 才艮据所述短号码和被叫用户所在的集团编号, 在被叫用户归 属的 SCP的业务数据库中查找被叫用户,判断被叫用户与主叫用户是否属于
同一集团, 如果是, 则执行步骤 5a, 否则执行步骤 6a; 步骤 4a、 SCP将该呼叫直接转交 MSC处理, 不再进行呼叫控制及呼叫 计费; 步骤 5a、 根据被叫用户的账户余额和呼叫类型进行第一级优惠计费; 步骤 6a、 判断主叫用户是否属于被叫用户所在集团的网外号码组, 若 是, 则根据被叫用户账户余额和呼叫类型进行第二级优惠计费, 否则, 根据 被叫用户账户余额和呼叫类型进行第三级优惠计费。 具体怎样根据主叫用户 账户余额和呼叫类型进行计费控制和优惠的方式, 可以由移动运营商自行设 定, 但并不限于此。 本实施例在前转流程中 ,在判断出发生前转的用户和前转到用户不属于 同一集团之后 , 还要进一步判断前转到的用户是否属于发生前转的用户所在 集团的网外号码组, 以便在前转流程中将网内用户之间的前转呼叫、 网内用 户向普通网外用户前转呼叫和网内用户向网外号码组用户前转呼叫这三种情 况区别开来, 分别进行呼叫控制和计费, 以实现不同优惠的计费。 图 8为本发明第二实施例中的前转流程图, 所述前转流程如图 8所示, 包括如下步骤: 步骤 1 c、 SCP收到呼叫时, 在本 SCP的业务数据库中查找判断发生前 转的用户是否归属于本 SCP, 如果是, 在获取发生前转的用户所在的集团编 号之后, 执行步骤 2c, 否则执行步骤 3c; 步骤 2c、 才艮据发生前转的用户所在的集团编号和前转到的用户的号码, 在发生前转的集团成员归属的 SCP的业务数据库中查找前转到的用户,判断 发生前转的用户和前转到的用户是否属于同一集团,如果是,则执行步骤 4c, 否则执行步骤 5c; 步骤 3c、 SCP将该呼叫直接转交 MSC处理, 不再进行呼叫控制及呼叫 计费; 步骤 4c、 才艮据发生前转的用户账户余额和呼叫类型进行第一级优惠计 费; 步骤 5c、 判断前转到的用户是否属于发生前转的用户所在集团的网外
号码组, 若是, 则才艮据发生前转的集团成员账户余额和呼叫类型进行第二级 优惠计费, 否则, 才艮据发生前转的集团成员账户余额和呼叫类型进行第三级 优惠计费。 本发明第三实施例, 在集团具有网内闭合用户群的情况下, 本实施例所 述移动虚拟专用网集团智能业务实现方法与第一实施例的区别在于, 创建集 团时, 在所述集团信息中增加一个包含该集团所对应的网内闭合用户群信息 的字段, 除此之外, 在步骤三中当用户通过其归属的 SCP触发某项智能业务 时, 主叫流程和被叫流程在判断出主被用户属于同一集团之后, 还要进一步 判断主被叫用户是否属于同一网内闭合用户群, 以便将网内闭合用户之间的 呼叫、 网内普通用户之间的呼叫以及网内用户与网外用户之间的呼叫这三种 情况区别开来, 分别进行呼叫控制和计费, 以实现不同优惠的计费。 图 9为本发明第三实施例中的主叫流程图, 所述主叫流程如图 9所示, 包括如下步骤: 步骤 1 a、 SCP收到呼叫时, 在本 SCP的业务数据库中查找判断主叫用 户是否归属于本 SCP, 如果是, 在获取主叫用户所在的集团编号之后, 进一 步判断主叫用户拨打的是长号码还是短号码, 若是长号码, 则执行步骤 2a, 若是短号码, 则执行步骤 3; 否则执行步骤 4a; 步骤 2a、 才艮据所述长号码和主叫用户所在的集团编号, 在主叫用户归 属的 SCP的业务数据库中查找被叫用户,判断被叫用户与主叫用户是否属于 同一集团, 如果是, 则执行步骤 5a, 否则执行步骤 6a; 步骤 3a、 才艮据所述短号码和主叫用户所在的集团编号, 在主叫用户归 属的 SCP的业务数据库中查找被叫用户,判断被叫用户与主叫用户是否属于 同一集团, 如果是, 则执行步骤 5a, 否则执行步骤 6a; 步骤 4a、 SCP将该呼叫直接转交 MSC处理, 不再进行呼叫控制及呼叫 计费; 步骤 5a、 判断主叫用户和被叫用户是否属于同一网内闭合用户群, 若 是, 则才艮据主叫用户账户余额和呼叫类型进行第一级优惠计费, 否则根据主 叫用户账户余额和呼叫类型进行第二级优惠计费; 步骤 6a、 根据主叫用户账户余额和呼叫类型进行第三级优惠计费。 具
体怎样根据主叫用户账户余额和呼叫类型进行计费控制和优惠的方式, 可以 由移动运营商自行设定, 但并不限于此。 图 10为本发明第三实施例中的被叫流程图,所述被叫流程如图 10所示, 包括如下步骤: 步骤 lb、 SCP收到呼叫时, 在本 SCP的业务数据库中查找判断被叫用 户是否归属于本 SCP, 如果是, 获取被叫用户所在的集团编号, 进一步判断 主叫用户的号码是长号码还是短号码, 若是长号码, 则执行步骤 2b, 若是短 号码, 则执行步骤 3b; 否则执行步骤 4b; 步骤 2b、 才艮据所述长号码和被叫用户所在的集团编号, 在被叫用户归 属的 SCP的业务数据库中查找主叫用户 ,判断被叫用户与主叫用户是否属于 同一集团, 如果是, 则执行步骤 5b, 否则执行步骤 6b; 步骤 3b、 才艮据所述短号码和被叫用户所在的集团编号, 在被叫用户归 属的 SCP的业务数据库中查找主叫用户,判断被叫用户与主叫用户是否属于 同一集团, 如果是, 则执行步骤 5b, 否则执行步骤 6b; 步骤 4b、 SCP将该呼叫直接转交 MSC处理, 不再进行呼叫控制及呼叫 计费; 步骤 5b、 判断主叫用户和被叫用户是否属于同一网内闭合用户群, 若 是, 则根据被叫用户账户余额和呼叫类型进行第一级优惠计费, 否则根据被 叫用户账户余额和呼叫类型进行第二级优惠计费; 步骤 6a、 根据被叫用户账户余额和呼叫类型进行第三级优惠计费。 本实施例在前转流程中,在判断发生前转的用户和前转到的用户是否属 于同一集团之后 , 还要进一步判断前转到的用户是否属于同一网内闭合用户 群, 以便在前转流程中将网内闭合用户群内的用户之间的前转呼叫、 网内普 通用户之间的前转呼叫和网内用户向网外用户的前转呼叫这三种情况区别开 来, 分别进行呼叫控制和计费, 以实现不同优惠的计费。 图 11为本发明第三实施例中的前转流程图,所述前转流程如图 11所示, 包括如下步骤: 步骤 1 c、 SCP收到呼叫时, 在本 SCP的业务数据库中查找判断发生前
转的用户是否归属于本 SCP,如果是,获取发生前转的用户所在的集团编号, 执行步骤 2c , 否则执行步骤 3c; 步骤 2c、 才艮据发生前转的用户所在的集团编号和前转到的用户的号码, 在发生前转的用户归属的 SCP的业务数据库中查找前转到的用户,判断发生 前转的用户和前转到的用户是否属于同一集团, 如果是, 则执行步骤 4c, 否 则执行步骤 5c; 所述号码可以是长号码或者短号码; 步骤 3c、 SCP将该呼叫直接转交 MSC处理, 不再进行呼叫控制及呼叫 计费; 步骤 4c、 判断发生前转的用户和前转到的用户是否属于同一网内闭合 用户群, 若是, 则才艮据发生前转的用户账户余额和呼叫类型进行第一级优惠 计费, 否则,才艮据发生前转的用户账户余额和呼叫类型进行第二级优惠计费; 步骤 5c、 才艮据发生前转的用户账户余额和呼叫类型进行第三级优惠计 费。 图 12为本发明第四实施例中所述移动虚拟专用网集团智能业务实现装 置的示意图, 如图 12所示, 包括: 配置模块, 用于在 SMP上配置集团编号与该集团所分布的 SCP模块号 的对应关系 ,在集团所分布的每个 SCP的业务数据库中配置该集团的相关数 据信息。 所述配置该集团的相关数据信息是指, 在该集团所分布的每个 SCP上 业务数据库中填写该集团在其分布的所有 SCP上的集团的相关数据信息 ,所 述集团的相关数据信息包括: 集团信息和集团成员信息, 所述集团成员信息 包括集团成员的长号码和短号码、集团成员的呼叫权限及集团成员对 SCP的 归属信息, 可选的, 所述集团的相关数据信息还进一步包括集团的网外号码 组和闭合用户群信息。 管理模块,用于统一管理分布在不同的 SCP上集团的相关数据信息, 当 集团的相关数据信息变化时 , 根据 SCP模块号或者通过接口机 , 依次向该集 团所分布的 SCP发送指令, 然后 SCP在本地数据库中进行集团的创建和删 除、 集团成员的增加和删除、 集团成员短号码的设置和修改、 集团成员呼叫 权限的设置和修改。 可选的, 管理模块还可以对集团的网外号码组和闭合用
户群信息进行设置和修改。 在具体实现时, 管理模块可以作为 SMP 的组成 部分之一。 业务执行模块 , 用于当用户触发某项虚拟专用网智能业务时 , 对网内网 外的呼叫进行判断、 控制及计费。 所述业务执行模块包括主叫执行模块、 被 叫执行模块和前转执行模块。 在具体实现时, 业务执行模块可以作为 SCP的 组成部分之一。 所述主叫执行模块, 用于判断主叫用户是否归属于本 SCP, 如果主叫用 户归属于本 SCP , 则进一步判断被叫用户与主叫用户是否归属于同一集团, 若是, 则才艮据主叫用户账户余额和呼叫类型进行计费控制和优惠计费, 否则 根据主叫用户账户余额和呼叫类型进行计费控制和非优惠计费; 如果主叫用 户不归属于本 SCP, 则将该呼叫直接转交 MSC处理, 不再进行呼叫控制及 呼叫计费。 所述被叫执行模块, 用于判断被叫用户是否归属于本 SCP, 如果被叫用 户归属于本 SCP , 则进一步判断被叫用户与主叫用户是否归属于同一集团, 若是, 则根据被叫用户账户余额和呼叫类型进行计费控制和优惠计费, 否则 才艮据被叫用户账户余额和呼叫类型进行计费控制和非优惠计费; 如果被叫用 户不归属于本 SCP, 则将该呼叫直接转交 MSC处理, 不再进行呼叫控制及 呼叫计费。 所述前转执行模块, 用于判断发生前转的用户是否归属于本 SCP, 如果 发生前转的用户归属于本 SCP, 则进一步判断发生前转的用户与前转到的用 户是否属于同一集团, 若是, 则才艮据发生前转的用户账户余额和呼叫类型进 行计费控制和优惠计费 , 否则才艮据发生前转的用户账户余额和呼叫类型进行 计费控制和非优惠计费; 如果发生前转的用户不归属于本 SCP, 则将该呼叫 直接转交 MSC处理 , 不再进行呼叫控制及呼叫计费。 本实施例上面记载的所述主叫执行模块、所述被叫执行模块以及所述前 转执行模块所完成的功能均是与本发明第一实施例中所述主叫流程、 被叫流 程以及前转流程对应的, 但本实施例中所述主叫执行模块、 所述被叫执行模 块以及所述前转执行模块所完成的功能并不限于与第一实施例对应 , 还可以 与第二、 三实施例中的所述主叫流程、 被叫流程以及前转流程对应。 本发明实施例利用 SMP管理多个 SCP , 保证 SCP之间数据同步。 业务
在跨 SCP移动虚拟专用网集团所分布的每个 SCP上实现。 在全网中为每一 个集团指定一个集团编号, 唯一标识该集团, 故该集团编号在每个 SCP上也 是唯一的, 但是可以在全网多个 SCP上同时存在。 由 SMP统一管理分布在 不同的 SCP上的该集团的各种事务, 保证集团所分布的 SCP的集团的相关 数据信息同步, 本发明实施例所述移动虚拟专用网集团智能业务实现方法功 能强大、 实现筒单, 采用本发明技术方案可以实现移动虚拟专用网集团的所 有业务属性, 是解决跨 SCP的移动虚拟专用网集团的一个非常好的方法, 具 有艮高的经济效益。 通过具体实施方式的说明 ,应当可对本发明为达成预定目的所采取的技 术手段及功效得以更加深入且具体的了解, 然而所附图示仅是提供参考与说 明之用, 并非用来对本发明加以限制。 显然, 本领域的技术人员应该明白, 上述的本发明的各模块或各步骤可 以用通用的计算装置来实现, 它们可以集中在单个的计算装置上, 或者分布 在多个计算装置所组成的网络上, 可选地, 它们可以用计算装置可执行的程 序代码来实现, 从而, 可以将它们存储在存储装置中由计算装置来执行, 或 者将它们分别制作成各个集成电路模块, 或者将它们中的多个模块或步骤制 作成单个集成电路模块来实现。 这样, 本发明不限制于任何特定的硬件和软 件结合。 以上所述仅为本发明的优选实施例而已, 并不用于限制本发明, 对于本 领域的技术人员来说, 本发明可以有各种更改和变化。 凡在本发明的 4青申和 原则之内, 所作的任何修改、 等同替换、 改进等, 均应包含在本发明的保护 范围之内。
Claims
权 利 要 求 书 一种移动虚拟专用网集团智能业务实现方法, 其特征在于, 包括:
在业务管理点 SMP上配置集团编号与该集团所分布的业务控制点 SCP模块号的对应关系, 在集团所分布的每个 SCP的业务数据库中配置 该集团的相关数据信息;
统一管理分布在不同的 SCP上集团的相关数据信息;
当用户触发某项智能业务时, 对呼叫进行判断、 控制及计费。 才艮据权利要求 1所述移动虚拟专用网集团智能业务实现方法, 其特征在 于 , 所述统一管理分布在不同的 SCP上集团的相关数据信息包括: 当集 团的相关数据信息变化时, 更新并同步该集团分布的 SCP上的集团的相 关数据信息;
其中, 所述集团的相关数据信息包括: 集团信息和集团成员信息。 才艮据权利要求 2所述移动虚拟专用网集团智能业务实现方法, 其特征在 于, 所述更新并同步该集团分布的 SCP上的集团的相关数据信息包括: SMP才艮据集团所分布的 SCP模块号或者通过接口机,依次向相关的 SCP 发送指令, 所述相关的 SCP收到指令后在本地数据库中对集团相关数据 信息进行更新;
所述对集团的相关数据信息进行更新至少包括以下其中之一: 集团 的创建和删除、 集团成员的增加和删除、 集团成员短号码的设置和 4爹改、 集团成员呼叫权限的设置和 4爹改。 才艮据权利要求 1或 2或 3所述移动虚拟专用网集团智能业务实现方法, 其特征在于, 所述对呼叫判断、 控制及计费的过程贯穿于主叫流程、 被 叫流程和前转流程。 才艮据权利要求 4所述移动虚拟专用网集团智能业务实现方法, 其特征在 于, 所述主叫流程包括:
SCP收到呼叫时, 判断主叫用户是否归属于本 SCP, 如果主叫用户 归属于本 SCP,则进一步判断被叫用户与主叫用户是否归属于同一集团, 若是, 则根据主叫用户账户余额和呼叫类型进行计费控制和优惠计费 ,
否则根据主叫用户账户余额和呼叫类型进行计费控制和非优惠计费; 如 果主叫用户不归属于本 SCP, 则将该呼叫直接转交 MSC处理, 不再进 行呼叫控制及呼叫计费;
所述被叫流程包括:
SCP收到呼叫时, 判断被叫用户是否归属于本 SCP, 如果被叫用户 归属于本 SCP,则进一步判断被叫用户与主叫用户是否归属于同一集团, 若是, 则根据被叫用户账户余额和呼叫类型进行计费控制和优惠计费 , 否则根据被叫用户账户余额和呼叫类型进行计费控制和非优惠计费; 如 果被叫用户不归属于本 SCP, 则将该呼叫直接转交 MSC处理, 不再进 行呼叫控制及呼叫计费;
所述前转流程包括:
SCP收到呼叫, 判断发生前转的用户是否归属于本 SCP, 如果发生 前转的用户归属于本 SCP, 则进一步判断发生前转的用户与前转到的用 户是否属于同一集团, 若是, 则才艮据发生前转的用户账户余额和呼叫类 型进行计费控制和优惠计费, 否则根据发生前转的用户账户余额和呼叫 类型进行计费控制和非优惠计费;如果发生前转的用户不归属于本 SCP, 则将该呼叫直接转交 MSC处理 , 不再进行呼叫控制及呼叫计费。
6. 根据权利要求 4所述移动虚拟专用网集团智能业务实现方法, 其特征在 于, 在所述集团信息中增加一个包含该集团所对应的网外号码组信息的 字段,
所述主叫流程包括如下步骤:
SCP收到呼叫时, 判断主叫用户是否归属于本 SCP, 如果主叫用户 归属于本 SCP,则进一步判断被叫用户与主叫用户是否归属于同一集团, 若是 , 则根据主叫用户账户余额和呼叫类型进行第一级优惠计费, 否则 再进一步判断被叫用户是否属于主叫用户所在集团的网外号码组,若是, 则才艮据主叫用户账户余额和呼叫类型进行第二级优惠计费, 否则, 根据 主叫用户账户余额和呼叫类型进行第三级优惠计费; 如果主叫用户不归 属于本 SCP, 则将该呼叫直接转交 MSC处理, 不再进行呼叫控制及呼 叫计费;
所述被叫流程包括如下步骤:
SCP收到呼叫时, 判断被叫用户是否归属于本 SCP, 如果被叫用户
归属于本 SCP,则进一步判断被叫用户与主叫用户是否归属于同一集团, 若是 , 则根据被叫用户账户余额和呼叫类型进行第一级优惠计费, 否则 再进一步判断主叫用户是否属于被叫用户所在集团的网外号码组,若是, 则才艮据被叫用户账户余额和呼叫类型进行第二级优惠计费, 否则, 根据 被叫用户账户余额和呼叫类型进行第三级优惠计费; 如果被叫用户不归 属于本 SCP, 则将该呼叫直接转交 MSC处理, 不再进行呼叫控制及呼 叫计费;
所述前转流程包括:
SCP收到呼叫, 判断发生前转的用户是否归属于本 SCP, 如果发生 前转的用户归属于本 SCP, 则进一步判断发生前转的用户与前转到的用 户是否属于同一集团, 若是, 则才艮据发生前转的用户账户余额和呼叫类 型进行第一级优惠计费, 否则再进一步判断前转到的用户是否属于网外 号码组, 若是, 则才艮据发生前转的用户账户余额和呼叫类型进行第二级 优惠计费, 否则 , 才艮据发生前转的用户账户余额和呼叫类型进行第三级 优惠计费; 如果发生前转的用户不归属于本 SCP, 则将该呼叫直接转交 MSC处理 , 不再进行呼叫控制及呼叫计费。
7. 根据权利要求 4所述移动虚拟专用网集团智能业务实现方法, 其特征在 于, 在所述集团信息中增加一个包含该集团所对应的网内闭合用户群信 息的字段,
所述主叫流程包括如下步骤:
SCP收到呼叫时, 判断主叫用户是否归属于本 SCP, 如果主叫用户 归属于本 SCP,则进一步判断被叫用户与主叫用户是否归属于同一集团, 若是, 则再进一步判断主叫用户和被叫用户是否属于同一网内闭合用户 群 , 若是 , 则根据主叫用户账户余额和呼叫类型进行第一级优惠计费 , 否则根据主叫用户账户余额和呼叫类型进行第二级优惠计费; 否则才艮据 主叫用户账户余额和呼叫类型进行第三级优惠计费; 如果主叫用户不归 属于本 SCP, 则将该呼叫直接转交 MSC处理, 不再进行呼叫控制及呼 叫计费;
所述被叫流程包括:
SCP收到呼叫时, 判断被叫用户是否归属于本 SCP, 如果被叫用户 归属于本 SCP,则进一步判断被叫用户与主叫用户是否归属于同一集团, 若是, 则再进一步判断主叫用户和被叫用户是否属于同一网内闭合用户
群 , 若是 , 则根据被叫用户账户余额和呼叫类型进行第一级优惠计费 , 否则才艮据被叫用户账户余额和呼叫类型进行第二级优惠计费; 否则根据 被叫用户账户余额和呼叫类型进行第三级优惠计费; 如果被叫用户不归 属于本 SCP, 则将该呼叫直接转交 MSC处理, 不再进行呼叫控制及呼 叫计费;
所述前转流程包括:
SCP收到呼叫, 判断发生前转的用户是否归属于本 SCP, 如果发生 前转的用户归属于本 SCP, 则进一步判断发生前转的用户与前转到的用 户是否属于同一集团, 若是, 则再进一步判断发生前转的用户和前转到 的用户是否属于同一网内闭合用户群, 若是, 则才艮据发生前转的用户账 户余额和呼叫类型进行第一级优惠计费, 否则 , 才艮据发生前转的用户账 户余额和呼叫类型进行第二级优惠计费; 否则才艮据发生前转的用户账户 余额和呼叫类型进行第三级优惠计费; 如果发生前转的用户不归属于本
SCP, 则将该呼叫直接转交 MSC处理, 不再进行呼叫控制及呼叫计费。
8. 一种移动虚拟专用网集团智能业务实现装置, 其特征在于, 包括:
配置模块, 用于在 SMP上配置集团编号与该集团所分布的 SCP模 块号的对应关系 , 在集团所分布的每个 SCP的业务数据库中配置该集团 的相关数据信息;
管理模块, 用于统一管理分布在不同的 SCP 上集团的相关数据信 息;
业务执行模块,用于当用户触发某项智能业务时,对呼叫进行判断、 控制及计费。
9. 才艮据权利要求 8所述移动虚拟专用网集团智能业务实现装置, 其特征在 于 , 所述统一管理分布在不同的 SCP上集团的相关数据信息 , 包括当集 团的相关数据信息变化时, 更新并同步该集团分布的 SCP上的集团的相 关数据信息;
所述集团的相关数据信息包括: 集团信息和集团成员信息。
10. 才艮据权利要求 8或 9所述移动虚拟专用网集团智能业务实现装置 , 其特 征在于, 所述业务执行模块包括主叫执行模块、 被叫执行模块和前转执 行模块。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP09845093.5A EP2437527B1 (en) | 2009-05-26 | 2009-09-04 | Method and device for implementing intelligent group service of mobile virtual private network |
US13/322,900 US8817667B2 (en) | 2009-05-26 | 2009-09-04 | Method and device for implementing group intelligent service of mobile virtual private network |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200910143467.0A CN101562759B (zh) | 2009-05-26 | 2009-05-26 | 一种移动虚拟专用网集团智能业务实现方法和装置 |
CN200910143467.0 | 2009-05-26 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2010135877A1 true WO2010135877A1 (zh) | 2010-12-02 |
Family
ID=41221345
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2009/073754 WO2010135877A1 (zh) | 2009-05-26 | 2009-09-04 | 移动虚拟专用网集团智能业务实现方法和装置 |
Country Status (4)
Country | Link |
---|---|
US (1) | US8817667B2 (zh) |
EP (1) | EP2437527B1 (zh) |
CN (1) | CN101562759B (zh) |
WO (1) | WO2010135877A1 (zh) |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102131171A (zh) * | 2010-01-20 | 2011-07-20 | 华为技术有限公司 | 实现跨地域的虚拟专用网业务的方法及设备 |
CN101867481B (zh) * | 2010-06-21 | 2014-12-10 | 中兴通讯股份有限公司 | Vpn业务的计费方法、装置和系统 |
CN102404696B (zh) * | 2010-09-14 | 2014-04-09 | 中国移动通信集团江苏有限公司 | 一种主叫识别回铃音设置方法和装置 |
CN101951584B (zh) * | 2010-09-19 | 2015-06-03 | 中兴通讯股份有限公司 | 一种移动虚拟专用网集团智能业务的计费方法和系统 |
CN103118347B (zh) * | 2011-11-16 | 2015-11-18 | 中国移动通信集团上海有限公司 | 一种终端间短号码呼叫的方法、系统和查询设备 |
CN105656745B (zh) * | 2014-11-12 | 2020-03-31 | 中兴通讯股份有限公司 | 虚拟专用网vpn集团中数据的更新方法及装置 |
CN108399476B (zh) * | 2017-02-06 | 2020-12-04 | 中国移动通信集团湖南有限公司 | 用户关系数据处理方法及装置 |
CN108668244B (zh) * | 2018-08-06 | 2021-05-18 | 中国联合网络通信集团有限公司 | 业务处理方法、装置及存储介质 |
US11805209B2 (en) * | 2020-07-24 | 2023-10-31 | Starlogik Ip Llc | Systems and methods for switching zero charge callers |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1999053696A2 (en) * | 1998-04-09 | 1999-10-21 | Nokia Networks Oy | Distribution of services in telecommunications network |
KR20010075927A (ko) * | 2000-01-21 | 2001-08-11 | 박종섭 | 다중 scp 시스템의 데이터 분배를 위한 sms 및 그분배 방법 |
CN1467977A (zh) * | 2002-07-08 | 2004-01-14 | 华为技术有限公司 | 企业无线总机接入移动虚拟专用网的方法 |
CN1780338A (zh) * | 2004-11-26 | 2006-05-31 | 华为技术有限公司 | 用户同时加入多个移动虚拟专用网集团的业务实现方法 |
WO2006114113A1 (en) * | 2005-04-26 | 2006-11-02 | Telecom Italia S.P.A. | Method for allowing access to services offered by an intelligent mobile communications network |
CN101621748A (zh) * | 2008-06-30 | 2010-01-06 | 中兴通讯股份有限公司 | 跨业务控制点移动虚拟专用网集团业务的实现方法和装置 |
Family Cites Families (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6243453B1 (en) * | 1996-07-17 | 2001-06-05 | Alcatel Usa Sourcing, L.P. | Programmable call processing system and method |
FI106515B (fi) * | 1998-03-17 | 2001-02-15 | Nokia Networks Oy | Älyverkkopalvelun konfigurointi |
US6876632B1 (en) * | 1998-09-25 | 2005-04-05 | Hitachi, Ltd. | Intelligent network with an internet call waiting function |
AU2565200A (en) * | 1999-02-19 | 2000-09-04 | Nokia Networks Oy | Network arrangement for communication |
FI20001111A (fi) * | 2000-05-10 | 2001-11-11 | Nokia Corp | Hajautetun tietokantajärjestelmän keskitetty hallinta |
FI110656B (fi) * | 2000-05-15 | 2003-02-28 | Nokia Corp | Puhelun muodostamisen ja jatkumisen ohjaaminen |
CN1146286C (zh) * | 2000-08-29 | 2004-04-14 | 华为技术有限公司 | 一种在移动网上实现虚拟专用网业务的方法及系统 |
GB0108995D0 (en) * | 2001-04-10 | 2001-05-30 | Nokia Corp | Provisioning services to groups of subscribers |
CN1306771C (zh) * | 2002-07-16 | 2007-03-21 | 华为技术有限公司 | 多个业务控制节点间实现虚拟专用网的方法 |
WO2004100575A2 (en) * | 2003-05-08 | 2004-11-18 | Ari Kahn | Call management protocol with nominated caller group |
CN1283073C (zh) * | 2003-08-15 | 2006-11-01 | 华为技术有限公司 | 一种实现预付费用户进行虚拟专用网业务的方法 |
US20050105706A1 (en) * | 2003-09-26 | 2005-05-19 | Antti Kokkinen | Method and apparatus for providing pre-connection messaging and output |
CN100563279C (zh) * | 2004-12-20 | 2009-11-25 | 华为技术有限公司 | 一种实现彩铃的方法及其网络系统 |
-
2009
- 2009-05-26 CN CN200910143467.0A patent/CN101562759B/zh not_active Expired - Fee Related
- 2009-09-04 EP EP09845093.5A patent/EP2437527B1/en not_active Not-in-force
- 2009-09-04 WO PCT/CN2009/073754 patent/WO2010135877A1/zh active Application Filing
- 2009-09-04 US US13/322,900 patent/US8817667B2/en not_active Expired - Fee Related
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1999053696A2 (en) * | 1998-04-09 | 1999-10-21 | Nokia Networks Oy | Distribution of services in telecommunications network |
KR20010075927A (ko) * | 2000-01-21 | 2001-08-11 | 박종섭 | 다중 scp 시스템의 데이터 분배를 위한 sms 및 그분배 방법 |
CN1467977A (zh) * | 2002-07-08 | 2004-01-14 | 华为技术有限公司 | 企业无线总机接入移动虚拟专用网的方法 |
CN1780338A (zh) * | 2004-11-26 | 2006-05-31 | 华为技术有限公司 | 用户同时加入多个移动虚拟专用网集团的业务实现方法 |
WO2006114113A1 (en) * | 2005-04-26 | 2006-11-02 | Telecom Italia S.P.A. | Method for allowing access to services offered by an intelligent mobile communications network |
CN101621748A (zh) * | 2008-06-30 | 2010-01-06 | 中兴通讯股份有限公司 | 跨业务控制点移动虚拟专用网集团业务的实现方法和装置 |
Non-Patent Citations (1)
Title |
---|
See also references of EP2437527A4 * |
Also Published As
Publication number | Publication date |
---|---|
CN101562759B (zh) | 2011-07-20 |
CN101562759A (zh) | 2009-10-21 |
EP2437527A4 (en) | 2013-09-18 |
EP2437527A1 (en) | 2012-04-04 |
US20120127896A1 (en) | 2012-05-24 |
US8817667B2 (en) | 2014-08-26 |
EP2437527B1 (en) | 2014-12-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2010135877A1 (zh) | 移动虚拟专用网集团智能业务实现方法和装置 | |
CN101282503A (zh) | 号码携带实现方法及用于号码携带用户的短消息处理方法 | |
WO2006060959A1 (fr) | Procede de facturation dans un reseau intelligent | |
CN101621748B (zh) | 跨业务控制点移动虚拟专用网集团业务的实现方法和装置 | |
CN1343425A (zh) | 通信网络 | |
CN102694824B (zh) | 一种用户数据存储系统及其数据访问方法 | |
EP1816797B1 (en) | Method for invoking a service in an intelligent network | |
WO2012034317A1 (zh) | 一种呼叫限制业务的实现方法及系统 | |
CN104469721A (zh) | 一卡多号业务系统和实现方法 | |
CN101984687B (zh) | Vpn智能业务号码携带的实现方法、系统及业务控制点 | |
CN101018410B (zh) | 呼叫连接建立方法及系统 | |
JPH10502221A (ja) | 電気通信ネットワークにおける移動性 | |
CN100512464C (zh) | 归属地短号码业务的系统、平台及实现方法 | |
WO2011160344A1 (zh) | Vpn业务的计费方法、装置和系统 | |
US11917505B2 (en) | Methods and systems for provisioning rate plan features in a wireless communication network | |
CN101951584B (zh) | 一种移动虚拟专用网集团智能业务的计费方法和系统 | |
WO2022143983A1 (zh) | Lan群组计费的方法、及相关装置 | |
CN101594436A (zh) | 一种固定电话免骚扰实现方法及装置 | |
CN1852366B (zh) | 一种为用户同时提供多种业务的方法 | |
CN101489206B (zh) | 一种解决一机多号副号做虚拟网被叫问题的方法和平台 | |
CN101056314B (zh) | 智能网络系统、业务开发方法、实现业务与协议分离的方法 | |
CN105656745B (zh) | 虚拟专用网vpn集团中数据的更新方法及装置 | |
KR100491739B1 (ko) | 이동통신 지능망 서비스에서의 가입자 데이터 불일치개선방법 | |
CN101193153A (zh) | 一种实现控制计费的方法、系统及装置 | |
KR100325694B1 (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: 09845093 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 9698/CHENP/2011 Country of ref document: IN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2009845093 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 13322900 Country of ref document: US |