CN1756285B - The Processing Method of Realizing the Group User's Preferential Tariff - Google Patents

Abstract

The invention discloses a method for realizing group user preferential billing. When the calling user and the called user make a call, the CUG code information of the calling user/called user is recorded in the call list, and the calling user/called user The CUG code information of the CUG is extracted by the billing center during the billing operation, and calculated according to the corresponding tariff preferential rules to obtain the group user preferential fee data. The present invention avoids problems such as slow call connection speed, occupation of signaling resources, and SSP/SCP processing bottlenecks caused by the use of smart devices, and realizes the virtualization of different types of users in a group user group, thereby avoiding prepayment Users change mobile phone numbers, which brings convenience to users and operators, and also enriches the services of prepaid users. CUG can be implemented without the support of mobile phones, and there is no limitation on terminals; users can also get preferential tariffs when roaming, and existing online devices can implement rich and diverse billing strategies.

Description

The Processing Method of Realizing the Group User's Preferential Tariff

technical field

The present invention relates to a method for realizing closed user group services, in particular to recording the closed user group (CUG) coding information of the calling user and/or the called user when the calling user and the called user make a call. Into the corresponding bill, and the CUG coded information of the calling user and/or the called user is extracted by the billing center during the billing operation and given a corresponding tariff discount. It belongs to the technical field of data communication.

Background technique

The special preferential tariff policy for group users has brought benefits to both group users and operators, making group users develop very rapidly. However, due to technical problems in tariffs, the popularity of this service is limited.

At present, there are roughly two ways to use existing technologies to realize preferential tariffs for group users:

1. Using a unified group user numbering scheme, the operator's billing center (Bill Server, BS for short) performs post-processing according to the user's number during settlement; using a unified group user numbering scheme, the billing center needs to process Judging the numbers of the calling party, called party, billing party, etc. when billing details, and giving special discounts to users belonging to a certain group within the group. Specifically, it is necessary to add group users to the unified database. When approving prices, analyze the calling number, called number, and forwarding number in the calling list, called number, and forwarding number. within the group number range), the caller and called party during the call will be given a discount on the call fee. Users who are not in the same group number segment will be charged at the normal rate.

The disadvantage of this method is: since the billing center is usually in the same area as the group, it can only give preferential billing to the business, while the roaming business of the group users is actually not available to the group users due to the different billing centers participating in the statistics. Get the corresponding discount; therefore, if you want to realize the cluster business of a certain group in the whole country, the above method cannot realize the corresponding preferential billing.

Second, the smart MVPN (Mobile Virtual Private Network, Mobile Virtual Private Network) trigger method is used to realize the preferential rate for group users: each time a group user initiates or receives a call, the mobile switching center (Mobile Switch Center, referred to as: MSC) Both trigger the intelligent MVPN process to the service control point (Service Control Point, referred to as: SCP), and the SCP records the account information of the group user, so it can be used to judge whether the call is on-net or off-net, and the billing center will cooperate , give discounts on calls within the group.

The above billing scheme requires the MSC network element of the operating network to have intelligent capabilities; while the call connection speed participated by intelligent devices is relatively slow; the intelligent MVPN scheme occupies MSC/SSP (Service Switch Point, SSP for short) and SCP At the same time, the processing capacity of SCP may also become the processing bottleneck of this solution, thus affecting the development of the number of group users to a certain extent; due to the limitation of the process, currently MVPN and PPS (prepaid service, Pre-Paid Service) cannot be signed at the same time, so for pre-paid users, it is still not possible to join the MVPN group and enjoy the discount on call charges.

In 3GPP (The 3rd Generation Partnership Project, 3rd Generation Partnership Project) TS (Technical Specification, Technical Specification), a closed user group (Closed User Group, referred to as: CUG) service is defined, and the CUG (closed user group) service is A supplementary service defined by GSM phase2 (GSM phase 2). It is aimed at group users or special groups of people, such as companies or relatives and friends. The closed user group provides users with the function of forming a closed group with other users on the network or in the network, and restricts access outside the group. Within a certain CUG, users can normally make calls between users, but cannot receive or initiate calls outside the group (except for OA/IA, group-out/group-in access capabilities).

CUG supplementary services do not affect emergency calls. A user can belong to one or more CUGs at the same time, up to 10. These CUGs are distinguished by a CUG index, which is provided and allocated by the operator. However, 3GPP TS does not define its charging process, therefore, CUG has not been well utilized.

Contents of the invention

The main technical problem to be solved by the present invention is to provide a billing scheme based on the CUG service to realize preferential tariffs for group users, which can provide preferential tariffs for the entire network for users of different types and regions, and can provide group users with roaming services. At the same time, it avoids problems such as slow call connection speed, occupation of signaling resources, and SSP/SCP processing bottlenecks caused by the use of smart devices.

The present invention specifically solves the above-mentioned technical problems through the following technical solutions:

A processing method for realizing preferential tariffs for group users. When the calling user and the called user make a call, the CUG code information of the calling user and/or the called user is recorded in the corresponding bill, and the calling user and the called user /or the CUG code information of the called user is extracted by the billing center during the billing operation, and calculated according to the corresponding preferential tariff rules to obtain the group user preferential fee data.

By adopting the CUG, the present invention avoids problems such as slow call connection speed, occupation of signaling resources, and SSP/SCP processing bottleneck caused by the use of smart devices, and has the following advantages:

Using CUG enables different types of users to be virtualized in a group user group, thereby avoiding the need for prepaid users to change mobile phone numbers, bringing convenience to users and operators, and enriching the services of prepaid users.

CUG can be implemented without the support of mobile phones, so there is no limitation in terms of terminals; users can also get preferential tariffs when roaming, realizing international, domestic, intra-network, and inter-network group services.

CUG itself is a supplementary service already defined by GSM. Existing devices on the network can provide such a function, and various billing strategies can be implemented with only minor changes.

Detailed ways

Below in conjunction with specific embodiment the present invention is described in further detail:

In the billing specification, the generally required bills include the calling bill (MOC), the called bill (MTC) and the forwarding bill (CFW). Since the supplementary service CUG is generally applicable to voice calls, data services and fax services, in these three bills (MOC, MTC, CFW), it is necessary to provide sufficient CUG information in the bills directly related to users, so as to calculate The bill server (Bill Server, referred to as: BS) treats the calls in and out of the network differently according to the group user mark recorded in the bill when approving the price.

First of all, to realize group user tariff discounts through the CUG service, it is necessary to add each in the calling bill (MOC), forwarding bill (CFW), and called bill (MTC) of the billing bill of MSC:

1) A field (CallerCUGInterlockCode) for identifying the CUG code of the calling user;

2) A field for identifying the CUG code of the called user (CalledCUGInterlockCode).

The above-mentioned CUG encoded field is an integer number of two bytes, for example: 1234. Operators can plan in the entire network or in each subnet.

In addition, the CUG billing process is introduced, which is fully compatible with the previous non-CUG billing process. The following 8 embodiments are used to further illustrate the present invention from the perspective of call process and billing sorting:

Embodiment 1, mobile user-mobile user's outbound call, the call flow in the CUG group and the process of filling in the detailed list are as follows:

The call process of a call within a CUG group, taking the calling user (CUG group 1 user) calling the called user (CUG group 1 user) as an example:

First make sure:

The calling user only subscribes to one CUG group, and the CUG group code (CUGInterlock) of the CUG group=1, and the user index (CUGIndex) of the corresponding CUG group=11;

The called user only subscribes to one CUG group, and the CUGInterlock of the CUG group=1, corresponding to the user CUGIndex of the CUG group=22;

If the calling user is a CUG user, the mobile phone can carry the user index of the calling user when sending the call setup setup (initial call setup message) message;

The originating MSC/VLR sends routing information to the HomeLocation Register (HLR) according to the calling user's subscription data, and carries the calling user's CUG group code and the user's CUG outgoing group capability information;

HLR queries the information of the called user, performs CUG principle matching according to the CUG group code of the called user, and finds that the calling party and the called party are users in the same group, so accepting the call, and sending the call to the originating MSC/Visit Location Register (VLR for short) ) while sending the called user routing information MSRN (Mobile Station Roaming Number mobile station roaming number), bring the called user's CUG group code and CUG out-group capability information;

The originating MSC/VLR receives the routing information response, finds that the SRI-ACK contains the CUG group code and the CUG outgoing capability information, and records it directly. When MOC is finally issued, record the CUG group code of the calling user in the CallerCUGInterlockCode field of the MOC, and record the CUG group code of the called user in CalledCUGInterlockCode;

Call connection, the originating MSC sends an IAM (Initial Address Message, initial address message, the first signaling of ISUP) message to the receiving MSC, carrying the calling user's CUG group code and CUG outgoing group capability information;

After receiving the IAM message, the MSC at the receiving end records the CUG group code of the calling user, so that when the MTC is finally generated, it is recorded in the CallerCUGInterlockCode field of the MTC; The terminal MSC will get the CUG group code of the called user, which will eventually be recorded in the CalledCUGInterlockCode of the MTC bill;

After receiving the MOC bill from the originating MSC, the billing center compares the information in the CallerCUGInterlockCode field and the CalledCUGInterlockCode field. If they are consistent (both are 1), the calling user and the called user are considered to be CUG users in the same group, and the calling user is given the Group corresponding tariff discounts. Correspondingly, after receiving the MTC bill from the MSC at the receiving end, the billing center compares the information in the CallerCUGInterlockCode field and the CalledCUGInterlockCode field, and if they are consistent (both are 1), then the calling user and the called user are considered to be CUG users in the same group, and the The corresponding tariff discount for the called user group.

Embodiment 2, mobile user-mobile user's outbound call, its CUG inter-group call flow and the process of filling in the detailed list are as follows:

Take the calling user (CUG group 1 user) calling the called user (CUG group 2 user) as an example to illustrate the call process between CUG groups:

Calling user: only subscribed to one CUG group, and the CUGInterlock of the CUG group=1, the corresponding user CUGIndex of the CUG group=11, and the CUG-OA (CUG group exit ability) is yes (can exit the group);

Called user: only subscribed to one CUG group, and the CUGInterlock of the CUG group=2, corresponding to the user CUGIndex of the CUG group=22, and CUG-IA (CUG group entry ability) is yes (can join the group);

If the calling user is a CUG user, the mobile phone can carry the user index of the calling user when sending a call setup message;

The originating MSC/VLR sends routing information to the HLR according to the calling user's subscription data, and carries the calling user's CUG group code and the user's CUG out-group capability information;

HLR queries the information of the called user, performs CUG matching according to the CUG group code of the called user, and finds that the calling user and the called user are not in the same group, so check the CUG-OA of the calling user and the CUG-IA of the called user, When it is found that the call can be accepted, it sends the called user's routing information MSRN to the originating MSC/VLR, and at the same time carries the called user's CUG group code and CUG group outgoing capability information;

The originating MSC/VLR receives the routing information response and finds that the Send Routing Info (SRI for short)-ACK (please give the full name in Chinese and English) contains CUG group code and CUG outgoing group capability information, and records it directly. When the MOC is finally issued, the CUG group code of the calling user is recorded in the CallerCUGInterlockCode field of the MOC; the CUG group code of the called user is recorded in CalledCUGInterlockCod;

When the call is connected, the originating MSC sends an IAM message to the receiving MSC, carrying the calling user's CUG group code and CUG outgoing group capability information;

After receiving the IAM message, the MSC at the receiving end records the CUG group code of the calling user, so that when the MTC is finally generated, it is recorded in the CallerCUGInterlockCode field of the MTC; The terminal MSC will get the CUG group code of the called user, which will eventually be recorded in the CalledCUGInterlockCode of the MTC bill;

After receiving the MOC bill of the originating MSC, the billing center compares the information in the CallerCUGInterlockCode field with the CalledCUGInterlockCode field. If they are inconsistent, the calling user and the called user are considered to be non-CUG group users. Give the calling user a corresponding tariff discount. Correspondingly, after receiving the MTC bill from the MSC at the receiving end, the billing center compares the information in the CallerCUGInterlockCode field with the CalledCUGInterlockCode field. The call preferential policy gives the called user the corresponding preferential tariff.

Embodiment 3, mobile calling user-mobile called user-forwarding to another mobile user unconditionally, the call flow in the CUG group and the process of filling in the detailed form are as follows:

Taking the first mobile user (CUG group 1 user) to call the second mobile user (CUG group 1 user) unconditionally forwarded to the third mobile user (CUG group 1 user) as an example, the following describes the call in the CUG group in the case of forwarding The calling process:

The first mobile user has signed only one CUG group, and the CUGInterlock of the CUG group=1, corresponding to the user CUGIndex of the CUG group=11;

The second mobile user: only subscribed to one CUG group, and the CUGInterlock of the CUG group=1, corresponding to the user CUGIndex of the CUG group=22;

The third mobile user: only subscribed to one CUG group, and the CUGInterlock of the CUG group=1, corresponding to the user CUGIndex of the CUG group=33;

Flow Description:

If the first mobile user is a CUG user, the mobile phone may carry the user index of the first mobile user when sending the call setup setup message;

The originating MSC/VLR sends routing information to the HLR according to the subscription data of the first mobile user, and carries the CUG group code of the first mobile user and the CUG group outgoing capability information of the first mobile user;

HLR queries the information of the second mobile user, performs CUG principle matching according to the CUG group code of the second mobile user, and finds that the first and second mobile users are users in the same group, so accepts the call, and then checks the data of the second mobile user, and finds that the first mobile user is in the same group. The second mobile user forwards to the third mobile user unconditionally, and sends the third mobile user's FTN (the third mobile user's number) to the originating MSC/VLR while carrying the second mobile user's CUG group code and CUG out of the group capability information;

The originating MSC/VLR receives the routing information response, finds that the SRI-ACK contains the CUG group code and the CUG outgoing capability information, and records it directly. When MOC is finally issued, record the CUG group code of the first mobile user in the CallerCUGInterlockCode field of the MOC, and record the CUG group code of the second mobile user in CalledCUGInterlockCode;

The originating MSC/VLR finds that the retrieved FTN number is retrieved, and inquires the information of the third mobile user to the HLR again. At this time, the CUG group code and CUG group-out ability information of the second mobile user are regarded as the CUG information of the first mobile user side Send to HLR;

HLR queries the information of the third mobile user, performs CUG principle matching according to the CUG group code of the third mobile user, finds that the second and third mobile users are users in the same group, therefore accepts the call, and sends the call after finding the MSRN of the third mobile user When the originating MSC/VLR sends the MSRN (mobile station roaming number) of the second mobile user, it also carries the CUG group code and CUG group-out ability information of the second mobile user;

When the originating MSC/VLR receives the second routing information response, it finds that the SRI-ACK contains CUG group code and CUG outgoing group capability information, and records it directly. When the detailed billing CFW is finally issued, record the CUG group code of the second mobile user in the CallerCUGInterlockCode field of CFW, and record the CUG group code of the third mobile user in CalledCUGInterlockCode;

The call is connected, and the originating MSC sends an IAM message to the receiving MSC, carrying the CUG group code and CUG outgoing capability information of the second mobile user;

After receiving the IAM message, the receiving end MSC records the CUG group code of the second mobile user, so that when the MTC is finally generated, it is recorded in the CallerCUGInterlockCode field of the MTC; on the other hand, while obtaining the called user data during the connection process, The receiving end MSC will get the CUG group code of the third mobile user, which will be finally recorded in the CalledCUGInterlockCode of the MTC bill;

After receiving the MOC bill of the originating MSC, the billing center compares the information in the CallerCUGInterlockCode field and the CalledCUGInterlockCode field, and if they are consistent (both are 1), then it is considered that the first mobile user/second mobile user is a CUG co-group user, and the billing center will give The corresponding tariff discount for the group of the first mobile user; after receiving the CFW bill of the originating MSC, the billing center compares the information in the CallerCUGInterlockCode field and the CalledCUGInterlockCode field, and if they are consistent (both are 1), then it is considered that the second mobile user/the first mobile user The third mobile user is a CUG user in the same group, and the second mobile user will be given a corresponding tariff discount; after receiving the MTC bill from the MSC at the receiving end, the billing center compares the information in the CallerCUGInterlockCode field and the CalledCUGInterlockCode field, and if they are consistent (both are 1 ), then it is considered that the second mobile user/third mobile user is a CUG user in the same group, and the second mobile user is given a corresponding tariff discount for the group.

Embodiment 4, mobile calling user-mobile called user-unconditional forwarding to another mobile user CUG group call flow and its detailed form filling;

Taking the first mobile user (CUG group 1 user) calling the called user (CUG group 1 user) unconditionally forwarded to the end user C (CUG group 1 user) as an example, the following describes the calls in the CUG group in the case of forwarding process:

The first mobile user: only subscribed to one CUG group, and the CUGInterlock of the CUG group=1, corresponding to the user CUGIndex of the CUG group=11;

The second mobile user: only subscribed to one CUG group, and the CUGInterlock of the CUG group=1, corresponding to the user CUGIndex of the CUG group=22;

The third mobile user: only subscribed to one CUG group, and the CUGInterlock of the CUG group=1, corresponding to the user CUGIndex of the CUG group=33;

Flow Description:

If the first mobile user is a CUG user, the mobile phone may carry the user index of the first mobile user when sending the call setup setup message;

The originating MSC/VLR sends routing information to the HLR according to the subscription data of the first mobile user, and carries the CUG group code of the first mobile user and the CUG group outgoing capability information of the first mobile user;

HLR queries the information of the second mobile user, performs CUG principle matching according to the CUG group code of the second mobile user, and finds that the first and second mobile users are users in the same group, so accepts the call, and then checks the data of the second mobile user to find the user Forwarding to the third mobile user unconditionally, while sending the third mobile user FTN (number of the third mobile user) to the originating MSC/VLR, carrying the CUG group code and CUG group-out ability information of the third mobile user;

The originating MSC/VLR receives the routing information response, finds that the SRI-ACK contains the CUG group code and the CUG outgoing capability information, and records it directly. When finally billing MOC, record the CUG group code of the first mobile user in the CallerCUGInterlockCode field of MOC, and record the CUG group code of the second mobile user in CalledCUGInterlockCode;

The MSC/VLR at the originating end discovers that the FTN number is retrieved, and inquires the information of the third mobile user to the HLR again. At this time, the CUG group code and CUG ability information of the second mobile user are sent as the CUG information of the calling side to the HLR;

HLR queries the information of the third mobile user, performs CUG principle matching according to the CUG group code of the third mobile user, finds that the second and third mobile users are users in the same group, therefore accepts the call, and sends the call after finding the MSRN of the third mobile user When the originating MSC/VLR sends the MSRN of the third mobile user, it also carries the CUG group code and CUG outgoing capability information of the third mobile user;

The originating MSC/VLR receives the second routing information response and finds that the SRI-ACK contains the CUG group code and the CUG outgoing capability information, and records it directly. When the detailed billing CFW is finally issued, record the CUG group code of the second mobile user in the CallerCUGInterlockCode field of CFW, and record the CUG group code of the third mobile user in CalledCUGInterlockCode;

The call is connected, and the originating MSC sends an IAM message to the receiving MSC, carrying the CUG group code and CUG outgoing capability information of the second mobile user;

After receiving the IAM message, the receiving MSC records the CUG group code of the second mobile user, so that when the MTC is finally generated, it is recorded in the CallerCUGInterlockCode field of the MTC; , the MSC at the receiving end will get the CUG group code of the third mobile user, which will eventually be recorded in the CalledCUGInterlockCode of the MTC bill;

After receiving the MOC bill of the originating MSC, the billing center compares the information of the CallerCUGInterlockCode field and the CalledCUGInterlockCode field, and if they are consistent (both are 1), then it is considered that the first and third mobile users A/second mobile users are CUG co-group users, Just give the first mobile user the corresponding tariff discount of this group; After receiving the CFW bill of originating MSC, the billing center compares the information of the CallerCUGInterlockCode field and the CalledCUGInterlockCode field, if they are consistent (both are 1), then consider the second mobile user /The third mobile user is a CUG user in the same group, and the second mobile user will be given a corresponding tariff discount; after receiving the MTC bill of the MSC at the receiving end, the billing center compares the information in the CallerCUGInterlockCode field and the CalledCUGInterlockCode field, and if they are consistent (both If it is 1), then it is considered that the second mobile user/third mobile user is a CUG user in the same group, and the third mobile user is given a corresponding tariff discount for the group.

Embodiment 5, mobile user-fixed phone outgoing call, CUG call flow and the processing flow of filling in the detailed form:

Taking the calling user (CUG group 1 user) calling the called user (PSTN, fixed telephone network) as an example, the following describes the call process of the CUG user calling the PSTN:

Calling user: only subscribed to one CUG group, and the CUGInterlock of this CUG group=1, corresponding to the user CUGIndex of this CUG group=11;

Called user: It is not necessary to consider whether to sign a CUG group;

Flow Description:

If the calling user is a CUG user, the mobile phone can carry the user index of the calling user when sending a call setup message;

When the call is connected, the originating MSC sends an IAM message to the originating GMSC, carrying the CUG group code and CUG outgoing capability information of the calling user;

The originating GMSC sends an IAM to the receiving end, and if the content is the same as received, the receiving end GMSC sends an IAM to the fixed telephone local exchange, carrying CUG information;

Finally, the CUG related information of the calling and called users can also be recorded in the fixed bill issued by the local exchange of the fixed telephone;

After the billing center receives the MOC bill of the originating MSC, it finds that there is a CallerCUGInterlockCode field; but there is no CalledCUGInterlockCode field, so it considers that the calling user and the called user are users of different groups.

Embodiment 6, fixed phone-mobile user incoming call, CUG call flow and the processing flow of detailed list filling;

Taking the calling user (PSTN) calling the called calling user (CUG group 1 user) as an example, the following describes the calling process of a fixed phone user calling a CUG user:

Calling user: only subscribed to one CUG group, and the CUGInterlock of this CUG group=1, corresponding to the user CUGIndex of this CUG group=11;

Called user: Assume that you have signed up for CUG group 3

Flow Description:

If the calling user is a CUG user, the call is connected, and the local exchange of the fixed telephone sends an IAM message to the originating GMSC (Gateway MSC, gateway MSC), carrying the CUG group code and CUG outgoing capability information of the calling user;

The originating GMSC forwards the received IAM to the receiving end, and the receiving end GMSC sends the IAM to the MSC, carrying CUG information;

After receiving the IAM message, the MSC at the receiving end records the CUG group code of the called user if it supports the same group of fixed phones and mobile users. If it does not support it, it does not fill in this field; In the CallerCUGInterlockCode field; on the other hand, while obtaining the called user data during the connection process, the MSC at the receiving end will obtain the CUG group code of the calling user, which will eventually be recorded in the CalledCUGInterlockCode of the MTC bill;

After receiving the MTC bill of the receiving MSC, the billing center compares the information in the CallerCUGInterlockCode field with the CalledCUGInterlockCode field, and then gives the calling user the corresponding tariff discount for the group; or the billing center receives the MOC bill of the originating MSC , if there is a CallerCUGInterlockCode field but no CalledCUGInterlockCode field, then the calling user and the called user are considered to be users of different groups, and the tariff data of the called user is calculated according to the common tariff standard.

Embodiment 7, Intelligent Network User-Mobile User, CUG Group Call Flow and Processing Flow of Filling in the Detailed Form

Taking the calling user (CUG group 1 user, PPS user) calling the called user (CUG group 1 user) as an example, the calling process of the call within the CUG group where the IN user is the calling party:

Calling user: only subscribed to one CUG group, and the CUGInterlock of the CUG group=1, corresponding to the user CUGIndex of the CUG group=11, and the user has signed the PPS;

Called user: only subscribed to one CUG group, and the CUGInterlock of the CUG group=1, corresponding to the user CUGIndex of the CUG group=22;

Flow Description:

If the calling user is a CUG user, the mobile phone can carry the user index of the calling user when sending a call setup message;

Since the calling user is an intelligent network user, the calling user's MSC triggers the MO (calling smart subscription information) process according to the calling user's OCSI (calling smart subscription information), and carries the calling user's CUG group code and CUG out-of-group capability information;

The Service Control Point (SCP) finds that the IDP (initial detection point message) (DP2 caller intelligent trigger detection point) message contains CUG information (MO process, so it is considered to carry the CUG information of the calling user) , just send ATI (real-time query message) message to inquire about the CUG capability of the called user to the HLR, and the HLR returns the CUG group code and CUG ability information of the called user; the SCP judges that the calling user and the called user are users in the same group, and then The calling user performs real-time tariff discounts, calculates the maximum duration of the calling user's call, and sends it to the calling user's MSC by segment;

The originating MSC/VLR sends routing information to the HLR according to the calling user's subscription data, and carries the calling user's CUG group code and the user's CUG out-group capability information;

HLR queries the information of the called user, performs CUG matching according to the CUG group code of the called user, finds that the calling user and the called user are in the same group, accepts the call, and sends the routing information MSRN of the called user to the originating MSC/VLR at the same time , bring the CUG group code and CUG group ability information of the called user;

The originating MSC/VLR receives the routing information response, finds that the SRI-ACK contains the CUG group code and the CUG outgoing capability information, and records it directly. When MOC is finally issued, record the CUG group code of the calling user in the CallerCUGInterlockCode field of the MOC, and record the CUG group code of the called user in CalledCUGInterlockCode;

When the call is connected, the originating MSC sends an IAM message to the receiving MSC, carrying the calling user's CUG group code and CUG outgoing group capability information;

After receiving the IAM message, the MSC at the receiving end records the CUG group code of the calling user, so that when the MTC is finally generated, it is recorded in the CallerCUGInterlockCode field of the MTC; The terminal MSC will get the CUG group code of the called user, which will eventually be recorded in the CalledCUGInterlockCode of the MTC bill;

After the billing center receives the MOC bill from the originating MSC, because it is an intelligent MOC bill, the tariff of the calling user has been discounted in real time, so the billing center will no longer process it. This bill is only used as a basis for reconciliation with the SCP. Correspondingly, after receiving the MTC bill from the MSC at the receiving end, the billing center compares the information in the CallerCUGInterlockCode field and the CalledCUGInterlockCode field, and if they are consistent (both are 1), then the calling user and the called user are considered to be CUG users in the same group, and the The corresponding tariff discount for the called user group.

Embodiment 8, mobile user-Intelligent network user, CUG group intra-call flow and the processing process of filling in the detailed form:

Taking the calling user (CUG group 1 user) calling the called user (CUG group 1 user, PPS user) as an example, the call process of the IN user making a call within the called CUG group:

Calling user: only subscribed to one CUG group, and the CUGInterlock of this CUG group=1, corresponding to the user CUGIndex of this CUG group=11;

Called user: only subscribed to one CUG group, and the CUGInterlock of this CUG group=1, corresponds to the user CUGIndex of this CUG group=22, and this user subscribes to PPS.

Flow Description:

If the calling user is a CUG user, the mobile phone can carry the user index of the calling user when sending a call setup message;

The originating MSC/VLR sends routing information to the HLR according to the calling user's subscription data, and carries the calling user's CUG group code and the user's CUG out-group capability information;

The HLR queries the information of the called user. Since the called user is an intelligent network user, the HLR returns the called smart subscription information TCSI of the called user, and carries the CUG group code and CUG group-out ability information of the called user;

The originating MSC triggers the called intelligent process according to the TCSI, and carries the called user's CUG group code and CUG out-group capability information;

The SCP finds that the IDP (DP12, the detection point triggered by the called intelligence) message contains CUG information (MT (called intelligence) process, so it thinks that it is the CUG information of the called user), and sends an ATI message to the HLR to query the host. Calling user's CUG capability, HLR returns calling user's CUG group code and CUG group ability information; SCP judges that the calling user and called user are in the same group, and then offers real-time tariff discounts to the called user, and calculates that B can call The maximum duration, and sent to the MSC of the calling user by segment;

The MSC of the calling user continues the call, and requests the routing information of the called user from the HLR again;

The HLR queries the information of the called user again, performs CUG principle matching according to the CUG group code of the called user, finds that the calling user and the called user are users in the same group, therefore accepts the call, and sends the called user routing information MSRN to the originating MSC/VLR ( Mobile station roaming number) at the same time, bring the CUG group code and CUG group capability information of the called user (you can not bring it here, because it has been brought to the MSC of the calling user when the route is taken for the first time);

The originating MSC/VLR receives the routing information response, finds that the SRI-ACK contains the CUG group code and the CUG outgoing capability information, and records it directly. When MOC is finally issued, record the CUG group code of the calling user in the CallerCUGInterlockCode field of the MOC, and record the CUG group code of the called user in CalledCUGInterlockCode;

When the call is connected, the originating MSC sends an IAM message to the receiving MSC, carrying the calling user's CUG group code and CUG outgoing group capability information;

After receiving the IAM message, the MSC at the receiving end records the CUG group code of the calling user, so that when the MTC is finally generated, it is recorded in the CallerCUGInterlockCode field of the MTC; The terminal MSC will get the CUG group code of the called user, which will eventually be recorded in the CalledCUGInterlockCode of the MTC bill;

After receiving the MOC bill of the originating MSC A, the billing center compares the information in the CallerCUGInterlockCode field and the CalledCUGInterlockCode field, and if they are consistent (both are 1), then the calling user and the called user are considered to be CUG users in the same group, and the calling user is given the Group corresponding tariff discounts. Correspondingly, after the billing center receives the MTC bill of the receiving end MSC B, because the intelligent network user is called, the tariff of the called user has been discounted by the SCP in real time, and the billing center will no longer process it (by calling the reference number association delete). In addition, since the MSC calling user is the triggering office of the called user, it is possible to generate an intelligent MTC bill, which will not be processed by the billing center, and this bill is only used as a basis for reconciliation with the SCP.

Finally, it should be noted that: the above embodiments are only used to illustrate the present invention rather than limit the technical solutions described in the present invention; Those of ordinary skill in the art should understand that the present invention can still be modified or equivalently replaced; and all technical solutions and improvements that do not depart from the spirit and scope of the present invention should be covered by the claims of the present invention.

Claims (17)

1. processing method that realizes group user preferential charge is characterized in that:

Step 1: when calling subscriber and called subscriber carry out dial-up, calling subscriber and/or called subscriber's closed user group CUG coded message is recorded in the corresponding ticket, and the ticket that will preserve described CUG coded message sends to the charging center;

Step 2: described charging center receives described ticket, obtain described calling subscriber and/or called subscriber's CUG coded message, and determine described calling subscriber and/or called subscriber's charging regulation described calling subscriber and/or called subscriber to be chargeed according to described CUG coded message.

2. the processing method of realization group user preferential charge according to claim 1 is characterized in that: when the mobile subscriber who belongs to same CUG calls out mutually, described step 1 specifically:

Step 10: when calling subscriber's mobile phone when sending call setup setup message, its CUG index information is together sent;

Step 11: the moving exchanging center MSC of making a start/VLR Visitor Location Register VLR sends routing iinformation according to calling subscriber's subscription data to Home Location Register HLR, and the CUG group code and the CUG that send the calling subscriber simultaneously go out the group energy force information;

Step 12:HLR inquiry called subscriber's information, and carry out CUG principle coupling according to called subscriber's CUG group code, if caller and called users is with the group user, then call accepted, and sending called subscriber's routing iinformation mobile station roaming number MSRN to the MSC/VLR that makes a start, the CUG group code and the CUG that send the called subscriber simultaneously go out the group energy force information;

Step 13: the MSC/VLR that makes a start receives the routing iinformation response, find sending out a routing iinformation replys and has the CUG group code among the SRI-ACK and CUG goes out the group energy force information, then directly described CUG group code of record and CUG go out the group energy force information, when generate chargeing detailed single caller ticket MOC, with calling subscriber's CUG group code and called subscriber CUG group code record in MOC;

Step 14, call proceeding, the MSC that makes a start sends initial address message IAM message to receiving end MSC, and the CUG group code and the CUG that send the calling subscriber simultaneously go out the group energy force information;

Step 15: receiving end MSC notes calling subscriber's CUG group code after receiving IAM message, when generating called ticket MTC, with calling subscriber's CUG group code record in MTC; In handshaking procedure, when obtaining called party data, receiving end MSC with called subscriber's CUG group code record in MTC.

3. the processing method of realization group user preferential charge according to claim 1 and 2, it is characterized in that: described step 2 is: the charging center is after receiving the MOC ticket of the MSC that makes a start, calling subscriber CUG coded message and called subscriber's CUG coded message wherein, if it is consistent, think that then caller and called users is CUG with the group user, then according to the corresponding preferential charge criterion calculation of this group calling subscriber's tariff data; The charging center is after receiving the MTC ticket of receiving end MSC, calling subscriber CUG coded message and called subscriber's CUG coded message wherein, if consistent, think that then caller and called users is that CUG is with the group user, then according to the corresponding preferential charge criterion calculation of this group called subscriber's tariff data.

4. the processing method of realization group user preferential charge according to claim 1 is characterized in that: when the mobile subscriber who belongs to different CUG calls out mutually, described step 1 specifically:

Step 20: when calling subscriber's mobile phone when sending call setup setup message, its CUG index information is together sent;

Step 21: the MSC/VLR that makes a start sends routing iinformation according to calling subscriber's subscription data to HLR, and the CUG group code and the CUG that send the calling subscriber simultaneously go out the group energy force information;

Step 22:HLR inquiry called subscriber's information, and carry out CUG principle coupling according to called subscriber's CUG group code, if caller and called users is the distinct group user, the CUG that the CUG that then checks the calling subscriber goes out group energy power CUG-OA and called subscriber goes into group energy power CUG-IA, if can call accepted, then send called subscriber's routing iinformation MSRN to the MSC/VLR that makes a start, the CUG group code and the CUG that send the called subscriber simultaneously go out the group energy force information;

Step 23: the MSC/VLR that makes a start receives the routing iinformation response, find to have called subscriber CUG group code among the SRI-ACK and CUG goes out the group energy force information, then directly described CUG group code of record and CUG go out the group energy force information, when generate chargeing detailed single MOC, with calling subscriber's CUG group code and called subscriber CUG group code record in MOC;

Step 24, call proceeding, the MSC that makes a start sends IAM message to receiving end MSC, and the CUG group code and the CUG that send the calling subscriber simultaneously go out the group energy force information;

Step 25: receiving end MSC notes calling subscriber's CUG group code after receiving IAM message, when generating MTC, with calling subscriber's CUG group code record in MTC; In handshaking procedure, obtain in the called party data, receiving end MSC with called subscriber's CUG group code record in MTC.

5. according to the processing method of claim 1 or 4 described realization group user preferential charges, it is characterized in that: described step 2 is: the charging center is after receiving the MOC ticket of the MSC that makes a start, calling subscriber CUG coded message and called subscriber's CUG coded message wherein, if it is inconsistent, think that then caller and called users is non-CUG with the group user, then according to the preferential charge criterion calculation calling subscriber's who calls out between distinct group tariff data; Correspondingly, the charging center is after receiving the MTC ticket of receiving end MSC, calling subscriber CUG coded message and called subscriber's CUG coded message wherein, if it is consistent, think that then caller and called users is non-CUG with the group user, then according to the preferential charge criterion calculation called subscriber's who calls out between distinct group tariff data.

6. the processing method of realization group user preferential charge according to claim 1 is characterized in that: when first mobile subscriber who belongs to identical CUG calls out Call Forwarding Unconditional to the three mobile subscribers' second mobile subscriber, described step 1 specifically:

Step 30: when first mobile subscriber's mobile phone when sending call setup setup message, its CUG index information is together sent;

Step 31: the MSC/VLR that makes a start sends routing iinformation according to first mobile subscriber's subscription data to HLR, sends first mobile subscriber's CUG group code and this first mobile subscriber's CUG simultaneously and goes out the group energy force information;

Step 32:HLR inquires about second mobile subscriber's information, carry out CUG principle coupling according to second mobile subscriber's CUG group code, find that first and second mobile subscriber is with the group user, then call accepted, detect second mobile user data again, find this second mobile subscriber Call Forwarding Unconditional to the three mobile subscribers, then when the MSC/VLR that makes a start sent the 3rd mobile subscriber FTN, the CUG group code and the CUG that send second mobile subscriber went out group energy information;

Step 33: the MSC/VLR that makes a start sends routing iinformation according to first mobile subscriber's subscription data to HLR, and the CUG group code and the CUG that send first mobile subscriber simultaneously go out the group energy force information;

Step 34:HLR inquires about second mobile subscriber's information, carry out CUG principle coupling according to second mobile subscriber's CUG group code, if first and second mobile subscriber is with the group user, then call accepted, further check second mobile subscriber's data, if this second mobile subscriber Call Forwarding Unconditional to the three mobile subscribers then send the 3rd mobile subscriber's transferred number FTN to the MSC/VLR that makes a start, the CUG group code and the CUG that send second mobile subscriber simultaneously go out the group energy force information;

Step 35: the MSC/VLR that makes a start receives routing iinformation response, finds to have the CUG group code among the SRI-ACK and CUG goes out the group energy force information, and then direct described CUG group code and CUG go out the group energy force information; When generating MOC, with first and second mobile subscriber's CUG group code record in MOC;

Step 36: what the MSC/VLR that makes a start found to fetch is the FTN number, then inquires about the 3rd mobile subscriber's information once more to HLR, and second mobile subscriber's CUG group code and CUG are gone out the group energy force information is used as Calling Side CUG information and issues HLR;

Step 37:HLR inquires about the 3rd mobile subscriber's information, carry out CUG principle coupling according to the 3rd mobile subscriber's CUG group code, find that second and third mobile subscriber is with the group user, then call accepted, just send the 3rd mobile subscriber MSRN to the MSC/VLR that makes a start after finding the 3rd mobile subscriber's MSRN, the CUG group code and the CUG that send the 3rd mobile subscriber simultaneously go out the group energy force information;

Step 38: receiving end MSC notes second mobile subscriber's CUG group code after receiving IAM message, and when generating MTC, with second mobile subscriber's CUG group code record in MTC; In handshaking procedure, when obtaining the 3rd mobile user data, receiving end MSC with the 3rd mobile subscriber's CUG group code record in MTC.

7. according to the processing method of claim 1 or 6 described realization group user preferential charges, it is characterized in that: described step 2 is: the charging center is after receiving the MOC ticket of the MSC that makes a start, first and second mobile subscriber's CUG coded message wherein, if it is consistent, think that then first and second mobile subscriber is CUG group user together, then according to tariff data with preferential charge criterion calculation first mobile subscriber who calls out between the group; The charging center is after receiving the preceding transfer list CFW ticket of the MSC that makes a start, second and third mobile subscriber's CUG coded message wherein, if it is consistent, think that then second and third mobile subscriber is CUG group user together, then according to tariff data with preferential charge criterion calculation second mobile subscriber who calls out between the group; The charging center is after receiving the MTC ticket of receiving end MSC, second and third mobile subscriber's CUG coded message wherein, if consistent, think that then second and third mobile subscriber is CUG group together, then according to tariff data with preferential charge criterion calculation the 3rd mobile subscriber who calls out between the group.

8. the processing method of realization group user preferential charge according to claim 1, it is characterized in that: when first mobile subscriber and second mobile subscriber belong to same CUG, the 3rd mobile subscriber belongs to another CUG, and during second mobile subscriber's Call Forwarding Unconditional to the, three mobile subscribers, described step 1 specifically:

Step 40: when first mobile subscriber's mobile phone when sending call setup setup message, its CUG index information is together sent;

Step 41: the MSC/VLR that makes a start sends routing iinformation according to first mobile subscriber's subscription data to HLR, sends first mobile subscriber's CUG group code and this first mobile subscriber's CUG simultaneously and goes out the group energy force information;

Step 42:HLR inquires about second mobile subscriber's information, carry out CUG principle coupling according to second mobile subscriber's CUG group code, find that first and second mobile subscriber is with the group user, then call accepted, detect second mobile user data again, find this second mobile subscriber Call Forwarding Unconditional to the three mobile subscribers, then when the MSC/VLR that makes a start sent the second mobile subscriber FTN, the CUG group code and the CUG that send second mobile subscriber went out group energy information;

Step 43: the MSC/VLR that makes a start sends routing iinformation according to first mobile subscriber's subscription data to HLR, and the CUG group code and the CUG that send first mobile subscriber simultaneously go out the group energy force information;

Step 44:HLR inquires about second mobile subscriber's information, carry out CUG principle coupling according to second mobile subscriber's CUG group code, if first and second mobile subscriber is with the group user, then call accepted, further check second mobile subscriber's data, if this second mobile subscriber Call Forwarding Unconditional to the three mobile subscribers then send second mobile subscriber's FTN to the MSC/VLR that makes a start, the CUG group code and the CUG that send second mobile subscriber simultaneously go out the group energy force information;

Step 45: the MSC/VLR that makes a start receives routing iinformation response, finds to have the CUG group code among the SRI-ACK and CUG goes out the group energy force information, and then direct described CUG group code and CUG go out the group energy force information; When generating MOC, with first and second mobile subscriber's CUG group code record in MOC;

Step 46: what the MSC/VLR that makes a start found to fetch is the FTN number, then inquires about the 3rd mobile subscriber's information once more to HLR, and second mobile subscriber's CUG group code and CUG are gone out the group energy force information is used as Calling Side CUG information and issues HLR;

Step 47:HLR inquires about the 3rd mobile subscriber's information, carry out CUG principle coupling according to the 3rd mobile subscriber's CUG group code, find that second and third mobile subscriber is non-CUG group user together, then check second mobile subscriber's CUG-OA and the 3rd mobile subscriber's CUG-IA, if can call accepted, just send the 3rd mobile subscriber MSRN to the MSC/VLR that makes a start after finding the 3rd mobile subscriber's MSRN, the CUG group code and the CUG that send the 3rd mobile subscriber simultaneously go out the group energy force information;

Step 48: receiving end MSC notes second mobile subscriber's CUG group code after receiving IAM message, and when generating MTC, with second mobile subscriber's CUG group code record in MTC; In handshaking procedure, when obtaining the 3rd mobile user data, receiving end MSC with the 3rd mobile subscriber's CUG group code record in MTC.

9. according to the processing method of claim 1 or 8 described realization group user preferential charges, it is characterized in that: described step 2 is: the charging center is after receiving the MOC ticket of the MSC that makes a start, first and second mobile subscriber's CUG coded message wherein, if it is consistent, think that then first and second mobile subscriber is CUG group user together, then according to tariff data with preferential charge criterion calculation first mobile subscriber who calls out between the group; The charging center is after receiving the CFW ticket of the MSC that makes a start, second and third mobile subscriber's CUG coded message wherein, if inconsistent, then think second and third mobile subscriber for non-CUG with the group user, then according to non-preferential charge criterion calculation second mobile subscriber's with groupcall tariff data; The charging center is after receiving the MTC ticket of receiving end MSC, second and third mobile subscriber's CUG coded message wherein, if consistent, think that then second and third mobile subscriber is non-CUG group together, then according to non-tariff data with preferential charge criterion calculation the 3rd mobile subscriber who calls out between the group.

10. the processing method of realization group user preferential charge according to claim 1 is characterized in that: when the calling subscriber is mobile CUG group user, when the called subscriber is the fixed telephone subscriber, described step 1 specifically:

Step 50: when first mobile subscriber's mobile phone when sending call setup setup message, its CUG index information is together sent;

Step 51: call proceeding, make a start MSC when the GMSC that makes a start sends IAM message, the CUG group code and the CUG that send the calling subscriber go out the group energy force information; When generating MOC, with calling subscriber's CUG group code record in MOC;

Step 52: make a start GMSC when transmitting the described IAM message of landline telephone Local Exchange, the CUG group code and the CUG that send the calling subscriber go out the group energy force information;

Step 53: landline telephone Local Exchange records calling subscriber's CUG group code and called subscriber's CUG information in the corresponding fixedly ticket.

11. processing method according to claim 1 or 10 described realization group user preferential charges, it is characterized in that: described step 2 is: the charging center is after receiving the MOC ticket of the MSC that makes a start, calling subscriber CUG coded message and called subscriber's CUG coded message wherein, if it is inconsistent, think that then caller and called users is non-CUG with the group user, then according to the preferential charge criterion calculation calling subscriber's who calls out between distinct group tariff data.

12. the processing method of realization group user preferential charge according to claim 1 is characterized in that: when the calling subscriber for the fixed telephone subscriber and when belonging to CUG group user with the called subscriber, described step 1 specifically:

Step 60: the landline telephone calling subscriber as CUG group user sends IAM message by landline telephone Local Exchange to the GMSC that makes a start, and the CUG group code and the CUG that send the calling subscriber simultaneously go out the group energy force information, and carry out call proceeding;

Step 61: the GMSC of gateway exchange mobile switching centre that makes a start transmits its IAM message received and corresponding C UG information to receiving end;

Step 62: receiving end MSC then writes down calling subscriber's CUG group code after receiving IAM message, and when generating MTC, with calling subscriber's CUG group code record in MTC; In handshaking procedure, obtain in the called party data, receiving end MSC with the called subscriber's that obtains CUG group code record in MTC.

13. processing method according to claim 1 or 12 described realization group user preferential charges, it is characterized in that: described step 2 is: the charging center is after receiving the MTC ticket of receiving end MSC, the CUG group code information that compares caller and called users is according to the preferential criterion calculation calling subscriber's of corresponding rate tariff data; Correspondingly, called subscriber's tariff data when not having called subscriber's CUG coded message if wherein have calling subscriber CUG coded message, is then calculated in the charging center according to the charging regulation of ordinary call after receiving the MOC ticket that the MSC that making a start generates.

14. the processing method of realization group user preferential charge according to claim 1 is characterized in that: when the calling subscriber is an Intelligent Network Terminal, and when belonging to identical CUG group user with the called subscriber, described step 1 specifically:

Step 70: when calling subscriber's mobile phone when sending call setup setup message, its CUG index information is together sent;

Step 71: the MSC that makes a start triggers intelligent dialing MO flow process according to calling subscriber's intelligent dialing subscription information OCSI, and the CUG group code and the CUG that send the calling subscriber simultaneously go out the group energy force information;

Step 72: service control point SCP is found to have CUG information in the IDP message, just sends real-time query messages ATI message to HLR, inquiry called subscriber's CUG ability, and CUG group code and CUG that HLR returns the called subscriber go out the group energy force information; SCP judges caller and called users for the group user according to described CUG group code, then calculates calling subscriber's the real-time tariff data and calling subscriber's the maximum duration of call according to corresponding rate preferential rule, and is handed down to the MSC that makes a start by section;

Step 73: the MSC/VLR that makes a start sends routing iinformation according to calling subscriber's subscription data to HLR, and the CUG group code and the CUG that send the calling subscriber simultaneously go out the group energy force information;

Step 74:HLR inquiry called subscriber's information, carry out CUG principle coupling according to called subscriber's CUG group code, find that caller and called users is with the group user, therefore call accepted, when the MSC/VLR that makes a start sends called subscriber's routing iinformation MSRN, the CUG group code and the CUG that send the called subscriber go out the group energy force information;

Step 75: the MSC/VLR that makes a start receives the routing iinformation response, finds that the CUG group code and the CUG that have the calling subscriber among the SRI-ACK go out the group energy force information, then directly note; When generate chargeing detailed single MOC, with the CUG group code record of caller and called users in MOC;

Step 76: call proceeding, the MSC that makes a start sends IAM message to receiving end MSC, and the CUG group code and the CUG that send the calling subscriber simultaneously go out the group energy force information;

Step 77: receiving end MSC notes calling subscriber's CUG group code after receiving described IAM message, when generating MTC, with calling subscriber's CUG group code record in MTC; Correspondingly, in handshaking procedure, when obtaining called party data, receiving end MSC can obtain called subscriber's CUG group code, is recorded among the MTC and with it.

15. processing method according to claim 1 or 14 described realization group user preferential charges, it is characterized in that: described step 2 is: the charging center is after receiving the MOC ticket of the MSC that makes a start, because this ticket is the MOC ticket of intelligent network, calling subscriber's rate are preferential in real time, and just no longer handle the charging center; Correspondingly, the charging center is after receiving the MTC ticket of receiving end MSC, and if calling subscriber and called subscriber's CUG group code consistent, thinks that then caller and called users is CUG group user together, then calculates called subscriber's preferential charge according to corresponding preferential Freight Basis.

16. the processing method of realization group user preferential charge according to claim 1 is characterized in that: when calling subscriber and called subscriber as Intelligent Network Terminal belong to identical CUG group user, described step 1 specifically:

Step 80: when calling subscriber's mobile phone when sending call setup setup message, its CUG index information is together sent;

Step 81: the MSC/VLR that makes a start sends routing iinformation according to calling subscriber's subscription data to HLR, and the CUG group code and the CUG that send the calling subscriber simultaneously go out the group energy force information;

Step 82:HLR inquiry called subscriber's information, because the called subscriber is an intelligent network user, HLR returns called subscriber's called intelligent CAMEL-Subscription-Information TCSI and called subscriber's CUG group code and CUG goes out the group energy force information;

Step 83: the MSC that makes a start triggers called subscriber's IN process according to described TCSI, and the CUG group code and the CUG that send the called subscriber go out the group energy force information to SCP;

Step 84:SCP finds to have CUG information in the Initial Detection Point message id P message, then sends ATI message to HLR inquiring calling user's CUG ability, and CUG group code and CUG that HLR returns the calling subscriber go out the group energy force information; SCP judges that caller and called users be with the group user, the maximum duration that can converse to calling subscriber's real-time tariff data and called subscriber according to corresponding rate preferential rule calculating then, and be handed down to calling subscriber's MSC by section;

Step 85: calling subscriber's MSC continues to call out, and asks called subscriber's routing iinformation once more to HLR;

Step 86:HLR inquires about called subscriber's information once more, and carry out CUG principle coupling according to called subscriber's CUG group code, find that caller and called users is with the group user, then call accepted, send called subscriber's routing iinformation MSRN to the MSC/VLR that makes a start, the CUG group code and the CUG that send the called subscriber simultaneously go out the group energy force information;

Step 87: the MSC/VLR that makes a start receives routing iinformation response, finds that the CUG group code and the CUG that have the calling subscriber among the SRI-ACK go out the group energy force information, then directly note, and when generating MOC, with the CUG group code record of caller and called users in MOC;

Step 88: call proceeding, the MSC that makes a start sends IAM message to receiving end MSC, and the CUG group code and the CUG that send the calling subscriber simultaneously go out the group energy force information;

Step 89: receiving end MSC notes calling subscriber's CUG group code after receiving IAM message, and when generating MTC, it is recorded among the MTC; Correspondingly, obtain in handshaking procedure in the called party data, receiving end MSC can obtain called subscriber's CUG group code, and is recorded among the MTC.

17. processing method according to claim 1 or 16 described realization group user preferential charges, it is characterized in that: described step 2 is: the charging center is behind the MOC ticket of receiving the MSC A that makes a start, the CUG group code that compares caller and called users, if it is consistent, think that then caller and called users is CUG group user together, then calculates the preferential charge data that give the calling subscriber according to corresponding rate preferential rule; Correspondingly, the charging center is after receiving the MTC ticket of receiving end MSC, because this called subscriber is an intelligent network user, called subscriber's rate have been undertaken preferential in real time by SCP, and no longer handle the charging center.