CN1756285B - Processing method for realizing group user preferential charge - Google Patents
Processing method for realizing group user preferential charge Download PDFInfo
- Publication number
- CN1756285B CN1756285B CN200410079083.4A CN200410079083A CN1756285B CN 1756285 B CN1756285 B CN 1756285B CN 200410079083 A CN200410079083 A CN 200410079083A CN 1756285 B CN1756285 B CN 1756285B
- Authority
- CN
- China
- Prior art keywords
- cug
- subscriber
- group
- msc
- called
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Landscapes
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
Abstract
The invention discloses a method to realize favour charge for group user. Wherein, when calling, recording CUG code information of both sides on dialog sheet and obtained by charge center when charging, calculating charge data according to opposite favour rule. This invention avoids calling succeeded speed slowly with intelligent device to take up signaling resource and bottleneck of SSP/SCP treatment, brings convenience to both user and operator, and enriches precharge business; CUG needs not support of mobile phone, and existing device and realize different charge strategy.
Description
Technical field
The present invention relates to a kind of implementation method of using Closed User Group, be meant a kind of when caller and called users is carried out dial-up especially, calling subscriber and/or called subscriber's closed user group (CUG) coded message is recorded in the corresponding ticket, and extract when the billing operation by the charging center and give corresponding rate preferential processing method by calling subscriber and/or called subscriber's CUG coded message.Belong to data communication technology field.
Background technology
Give the price policy of special preferential treatment to group user, brought interests for group user and operation commercial city, make that the group user development is very fast.But because the technical problem on the rate, the popularity that makes this business carry out is restricted.
Utilize the preferential mode of existing techniques in realizing group user rate roughly to have two kinds at present:
One, use unified group user numbering plan, (Bill Server is called for short: BS) carry out reprocessing when the clearing according to user's number by the charging center of operator; Use unified group user numbering plan, the charging center need be at the detailed number of judging caller, called, charged party etc. when single that handle to charge, and the user's rate in group that belongs to certain group is done special preferential.Specifically group user need be added unified database, when wholesale price, analyze for calling number, called number, transferred number in caller, called, the preceding transfer list, if user's (number is in same group section) in the net, the calling and called user in then calling out is preferential with telephone expenses.The user of non-same group section then deducts fees by common rate.
The shortcoming of this mode is: because the charging center is common and group is in same region, it can only give preferential charging to business, then owing to participate in the charging center difference of statistics, in fact group user can not obtain preferential accordingly in the services of roaming of group user; Therefore, if realize the group service of a certain group in the whole nation, above-mentioned method then can't realize corresponding preferential charging.
They are two years old, adopt intelligent MVPN (VPMN, Mobile Virtual Private Network) triggering mode realizes that the rate of group user is preferential: group user starts or during receipt of call at every turn, (the Mobile Switch Center of mobile switching centre, be called for short: MSC) all trigger intelligent MVPN flow process to SCP (Service Control Point, be called for short: SCP), SCP has write down the account information of group user, thereby can judge that this calling is in the net or off-net call by it, and by the charging center cooperation, it is preferential to give telephone expenses to calling in the group.
Above-mentioned billing scheme needs the MSC network element of Operation Network to have intelligent capability; And it is relatively slow by the call proceeding speed of smart machine participation; Intelligence MVPN scheme takies the signal resource between MSC/SSP (Service Switching Point, Service Switch Point are called for short SSP) and the SCP, simultaneously, the disposal ability of SCP also may become the processing bottleneck of scheme for this reason, thereby, to a certain degree having influenced the development of group user quantity; Because the restriction on the flow process, MVPN can not contract simultaneously with PPS (prepayment service, Pre-Paid Service) at present, therefore for the prepaid user, also can't add MVPN group, enjoys the preferential of telephone expenses.
At 3GPP (The 3rd Generation Partnership Project, the plan of third generation partnership) TS (technical specification, Technical Specification) definition has closed user group (Closed User Group in, be called for short: CUG) business, this CUG (closed user group) business are the supplementary services of a kind of GSM phase2 (GSM second stage) definition.It towards to as if group user or special population, for example: company or kith and kin family.Closed user group provides the user to follow that other users form the function of closed group between Home Network or net, and the visit outer to the group limits.In certain CUG inside, can normally call out between the user, but can not receive group outcall and be initiated to the outer calling of group (have OA/IA, go out group/go into except group access capability authority).
The CUG supplementary service does not influence urgent call.A user can belong to one or more CUG simultaneously, at most can not be above 10.These CUG distinguish by the CUG index, and index is provided by operator and distributes.But 3GPP TS does not define its charging process, thereby CUG is never well utilized.
Summary of the invention
Technical problem underlying to be solved by this invention provides a kind of billing scheme based on CUG business realizing group user preferential charge, can provide the whole network rate preferential at users dissimilar, different regions, can be for group user provide the preferential charging method that comprises services of roaming, avoid simultaneously adopting smart machine and the call proceeding speed brought is slow, occupied signaling resource and SSP/SCP handle problems such as bottleneck.
The present invention has specifically solved above-mentioned technical problem by the following technical solutions:
A kind of processing method that realizes group user preferential charge, when calling subscriber and called subscriber carry out dial-up, calling subscriber and/or called subscriber's CUG coded message is recorded in the corresponding ticket, this calling subscriber and/or called subscriber's CUG coded message is extracted when the billing operation by the charging center, and calculates the cost data of group user preferential according to corresponding rate preferential rule.
The present invention is by adopting CUG, avoided adopting smart machine and the call proceeding speed brought is slow, occupied signaling resource and SSP/SCP handle problems such as bottleneck, and had following advantage:
Adopt CUG to realize that different classes of user is virtual in a group user group, thereby avoided the prepaid user to change phone number, brought facility for user and operator, also enriched prepaid user's business.
CUG does not need the mobile phone support can realize yet, thus aspect terminal without limits; Also can obtain preferential rate when the user roams, realize the world, domestic, the group's business in the net, between net in the scope.
CUG itself is the supplementary service that GSM has defined, and existing online equipment just can provide such function, and the only slight change of needs just can realize rich and varied charging policy.
Embodiment
The present invention is described in further detail below in conjunction with specific embodiment:
In the charging standard, general essential ticket has caller ticket (MOC), called ticket (MTC) and preceding transfer list (CFW).Because this supplementary service of CUG generally is applicable to audio call, data service and facsimile service, so in these three kinds of tickets (MOC, MTC, CFW), need to provide sufficient CUG information in the ticket directly related with the user, so that charging center (Bill Server, be called for short: BS) during wholesale price according to the group user mark that writes down in the ticket, treat the outer calling of net Intranet with a certain discrimination.
At first, preferential by CUG business realizing group user rate, need in the detailed single caller ticket (MOC) of the charging of MSC, preceding transfer list (CFW), called ticket (MTC), increase separately:
1) is used to identify the field (CallerCUGInterlockCode) that calling subscriber CUG encodes;
2) be used to identify the field (CalledCUGInterlockCode) that called subscriber CUG encodes.
The field of above-mentioned CUG coding is to be the integer number of two bytes, for example: 1234.Operator can plan in the whole network, also can plan in its each subnet.
Introduced the CUG charging flow in addition, the non-CUG before fully compatible charges and handles, below respectively with 8 embodiment, from the angle of the call flow and the letter sorting of chargeing, the present invention is further illustrated:
Embodiment 1, mobile subscriber-mobile subscriber's outbound call, and its CUG intra-group call flow process and detailed process of singly filling in thereof are as follows:
Calling out called subscriber (CUG group 1 user) with calling subscriber (CUG group 1 user) is the calling procedure of the CUG intra-group call of example:
At first definite:
Calling subscriber's CUG group has only contracted, and this CUG group's CUG group code (CUGInterlock)=1, to user index (CUGIndex)=11 that should CUG group;
Called subscriber's CUG group has only contracted, and this CUG group's CUGInterlock=1, to user CUGIndex=22 that should CUG group;
If the calling subscriber is CUG user, mobile phone can be with the user index of going up this calling subscriber when sending call setup setup (initial call setup message) message;
The MSC/VLR that makes a start sends routing iinformation according to calling subscriber's subscription data to Home Location Register (HomeLocation Register is called for short HLR), goes out the group energy force information with CUG group code that goes up the calling subscriber and this user's CUG;
HLR inquiry called subscriber's information, carry out CUG principle coupling according to called subscriber's CUG group code, find that calling and called are with the group user, therefore call accepted, to MSC/ access location register (the Visit Location Register that makes a start, be called for short VLR) when sending called subscriber routing iinformation MSRN (Mobile Station Roaming Number mobile station roaming number), go out the group energy force information with the CUG group code and the CUG that go up the called subscriber;
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, just directly notes.When finally go out chargeing detailed single MOC, with calling subscriber's CUG group code record in the CallerCUGInterlockCode of MOC field, called subscriber's CUG group code record in CalledCUGInterlockCode;
Call proceeding, the MSC that makes a start sends IAM (Initial Address Message, initial address message, article one signaling of ISUP) message to receiving end MSC, goes out the group energy force information with the CUG group code and the CUG that go up the calling subscriber;
Receiving end MSC notes calling subscriber's CUG group code after receiving IAM message, so that when finally producing MTC, be recorded in the CallerCUGInterlockCode field of MTC; On the other hand, when obtaining called party data in the handshaking procedure, receiving end MSC can obtain called subscriber's CUG group code, finally can be recorded among the CalledCUGInterlockCode of MTC ticket;
The charging center is after receiving the MOC ticket of the MSC that makes a start, the information that compares CallerCUGInterlockCode field and CalledCUGInterlockCode field, consistent if (all being 1), think that then caller and called users is CUG group user together, it is preferential just to give the corresponding rate of this group of calling subscriber.Accordingly, the charging center is after receiving the MTC ticket of receiving end MSC, the information that compares CallerCUGInterlockCode field and CalledCUGInterlockCode field, consistent if (all being 1), think that then caller and called users is CUG group user together, it is preferential just to give the corresponding rate of this group of called subscriber.
Embodiment 2, mobile subscriber-mobile subscriber's outbound call, and call flow and detailed process of singly filling in thereof are as follows between its CUG group:
Calling out called subscriber (CUG group 2 users) with calling subscriber (CUG group 1 user) is example, and the calling procedure of calling out between CUG group is described:
The calling subscriber: the CUG group that only contracted, and this CUG group's CUGInterlock=1, to user CUGIndex=11 that should CUG group, and CUG-OA (CUG goes out group energy power) is yes (can go out the group);
The called subscriber: the CUG group that only contracted, and this CUG group's CUGInterlock=2, to user CUGIndex=22 that should CUG group, and CUG-IA (CUG goes into group energy power) is yes (can go into the group);
If the calling subscriber is CUG user, mobile phone can be with the user index of going up this calling subscriber when sending call setup setup message;
The MSC/VLR that makes a start sends routing iinformation according to calling subscriber's subscription data to HLR, goes out the group energy force information with CUG group code that goes up the calling subscriber and this user's CUG;
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 not with the group user, therefore check calling subscriber's CUG-OA and called subscriber's CUG-IA, discovery can call accepted, just when the MSC/VLR that makes a start sends called subscriber's routing iinformation MSRN, go out the group energy force information with the CUG group code and the CUG that go up the called subscriber;
The MSC/VLR that makes a start receives routing iinformation response, finds to have the CUG group code among a routing iinformation (Send Routing Info is called for short SRI)-ACK (please provide Chinese and English full name) and CUG goes out the group energy force information, just directly notes.When finally go out chargeing detailed single MOC, with calling subscriber's CUG group code record in the CallerCUGInterlockCode of MOC field; Called subscriber's CUG group code record is in CalledCUGInterlockCod;
Call proceeding, the MSC that makes a start sends IAM message to receiving end MSC, goes out the group energy force information with the CUG group code and the CUG that go up the calling subscriber;
Receiving end MSC notes calling subscriber's CUG group code after receiving IAM message, so that when finally producing MTC, be recorded in the CallerCUGInterlockCode field of MTC; On the other hand, when obtaining called party data in the handshaking procedure, receiving end MSC can obtain called subscriber's CUG group code, finally can be recorded among the CalledCUGInterlockCode of MTC ticket;
The charging center is after receiving the MOC ticket of the MSC that makes a start, the information that compares CallerCUGInterlockCode field and CalledCUGInterlockCode field, inconsistent, think that then caller and called users is non-CUG group user together, but it is preferential to give the corresponding rate of calling subscriber according to the calling preferential policy between different group users.Accordingly, the charging center is after receiving the MTC ticket of receiving end MSC, the information that compares CallerCUGInterlockCode field and CalledCUGInterlockCode field, inconsistent, then think the non-CUG of caller and called users with the group user, but it is preferential to give the corresponding rate of called subscriber according to the calling preferential policy between different group users.
Embodiment 3, and mobile calling subscriber-Mobile terminating call user-Call Forwarding Unconditional is to another mobile subscriber, and CUG intra-group call flow process and detailed process of singly filling in thereof are as follows:
Calling out second mobile subscriber (CUG group 1 user) Call Forwarding Unconditional to the three mobile subscribers (CUG group 1 user) with first mobile subscriber (CUG group 1 user) is example, and the calling procedure of CUG intra-group call under the preceding commentaries on classics situation below has been described:
First mobile subscriber's CUG group has only contracted, and this CUG group's CUGInterlock=1, to user CUGIndex=11 that should CUG group;
Second mobile subscriber: the CUG group that only contracted, and this CUG group's CUGInterlock=1, to user CUGIndex=22 that should CUG group;
The 3rd mobile subscriber: the CUG group that only contracted, and this CUG group's CUGInterlock=1, to user CUGIndex=33 that should CUG group;
Process description:
If first mobile subscriber is CUG user, mobile phone can be with the user index of going up this first mobile subscriber when sending call setup setup message;
The MSC/VLR that makes a start sends routing iinformation according to first mobile subscriber's subscription data to HLR, goes out the group energy force information with last first mobile subscriber's CUG group code and this first mobile subscriber's CUG;
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, therefore call accepted, look into second mobile user data again, find this second mobile subscriber Call Forwarding Unconditional to the three mobile subscribers, just when the MSC/VLR that makes a start sends by the 3rd mobile subscriber FTN (the 3rd mobile subscriber's number), go out the group energy force information with last second mobile subscriber's CUG group code and CUG;
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, just directly notes.When finally go out chargeing detailed single MOC, with first mobile subscriber's CUG group code record in the CallerCUGInterlockCode of MOC field, the second mobile subscriber CUG group code record in CalledCUGInterlockCode;
What the MSC/VLR that makes a start found to fetch is the FTN number, inquires about the 3rd mobile subscriber's information once more to HLR, at this moment, second mobile subscriber's CUG group code and CUG is gone out the group energy force information be used as first mobile subscriber's side CUG information and issue HLR;
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, therefore call accepted, just find behind the 3rd mobile subscriber's the MSRN when the MSC/VLR that makes a start sends the second mobile subscriber MSRN (mobile station roaming number), go out the group energy force information with last second mobile subscriber's CUG group code and CUG;
The MSC/VLR that makes a start receives routing iinformation response for the second time, finds to have the CUG group code among the SRI-ACK and CUG goes out the group energy force information, just directly notes.When finally go out chargeing detailed single CFW, with second mobile subscriber's CUG group code record in the CallerCUGInterlockCode of CFW field, the 3rd mobile subscriber's CUG group code record in CalledCUGInterlockCode;
Call proceeding, the MSC that makes a start sends IAM message to receiving end MSC, goes out the group energy force information with last second mobile subscriber's CUG group code and CUG;
Receiving end MSC notes second mobile subscriber's CUG group code after receiving IAM message, so that when finally producing MTC, be recorded in the CallerCUGInterlockCode field of MTC; On the other hand, when obtaining called party data in the handshaking procedure, receiving end MSC can obtain the 3rd mobile subscriber's CUG group code, finally can be recorded among the CalledCUGInterlockCode of MTC ticket;
The charging center is after receiving the MOC ticket of the MSC that makes a start, the information that compares CallerCUGInterlockCode field and CalledCUGInterlockCode field, consistent if (all being 1), think that then first mobile subscriber/second mobile subscriber is CUG group user together, it is preferential just to give the corresponding rate of this group of first mobile subscriber; The charging center is after receiving the CFW ticket of the MSC that makes a start, the information that compares CallerCUGInterlockCode field and CalledCUGInterlockCode field, consistent if (all being 1), think that then second mobile subscriber/the 3rd mobile subscriber is CUG group user together, it is preferential just to give the corresponding rate of second mobile subscriber; The charging center is after receiving the MTC ticket of receiving end MSC, the information that compares CallerCUGInterlockCode field and CalledCUGInterlockCode field, consistent if (all being 1), think that then second mobile subscriber/the 3rd mobile subscriber is CUG group user together, it is preferential just to give the corresponding rate of this group of second mobile subscriber.
Embodiment 4, and mobile calling subscriber-Mobile terminating call user-Call Forwarding Unconditional is to another mobile subscriber CUG intra-group call flow process and detailed singly fill in;
Calling out called subscriber (CUG group 1 user) Call Forwarding Unconditional with first mobile subscriber (CUG group 1 user) is example to end user C (CUG group 1 user), and the calling procedure of CUG intra-group call under the preceding commentaries on classics situation below has been described:
First mobile subscriber: the CUG group that only contracted, and this CUG group's CUGInterlock=1, to user CUGIndex=11 that should CUG group;
Second mobile subscriber: the CUG group that only contracted, and this CUG group's CUGInterlock=1, to user CUGIndex=22 that should CUG group;
The 3rd mobile subscriber: the CUG group that only contracted, and this CUG group's CUGInterlock=1, to user CUGIndex=33 that should CUG group;
Process description:
If first mobile subscriber is CUG user, mobile phone can be with the user index of going up this first mobile subscriber when sending call setup setup message;
The MSC/VLR that makes a start sends routing iinformation according to first mobile subscriber's subscription data to HLR, goes out the group energy force information with last first mobile subscriber's CUG group code and this first mobile subscriber's CUG;
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, therefore call accepted, look into second mobile user data again, find this user's Call Forwarding Unconditional to the three mobile subscribers, just when the MSC/VLR that makes a start sends the 3rd mobile subscriber FTN (the 3rd mobile subscriber's number), go out the group energy force information with last the 3rd mobile subscriber's CUG group code and CUG;
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, just directly notes.When finally go out chargeing detailed single MOC, with first mobile subscriber's CUG group code record in the CallerCUGInterlockCode of MOC field, second mobile subscriber's CUG group code record in CalledCUGInterlockCode;
What the MSC/VLR that makes a start found to fetch is the FTN number, inquires about the 3rd mobile subscriber's information once more to HLR, at this moment, second mobile subscriber's CUG group code and CUG is gone out the group energy force information be used as Calling Side CUG information and issue HLR;
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, therefore call accepted, just find behind the 3rd mobile subscriber's the MSRN when the MSC/VLR that makes a start sends the 3rd mobile subscriber MSRN, go out the group energy force information with last the 3rd mobile subscriber's CUG group code and CUG;
The MSC/VLR that makes a start receives routing iinformation response for the second time, finds to have the CUG group code among the SRI-ACK and CUG goes out the group energy force information,, just directly note.When finally go out chargeing detailed single CFW, with second mobile subscriber's CUG group code record in the CallerCUGInterlockCode of CFW field, the 3rd mobile subscriber's CUG group code record in CalledCUGInterlockCode;
Call proceeding, the MSC that makes a start sends IAM message to receiving end MSC, goes out the group energy force information with last second mobile subscriber's CUG group code and CUG;
Receiving end MSC notes second mobile subscriber's CUG group code after receiving IAM message, so that when finally producing MTC, be recorded in the CallerCUGInterlockCode field of MTC; On the other hand, when obtaining second mobile user data in the handshaking procedure, receiving end MSC can obtain the 3rd mobile subscriber's CUG group code, finally can be recorded among the CalledCUGInterlockCode of MTC ticket;
The charging center is after receiving the MOC ticket of the MSC that makes a start, the information that compares CallerCUGInterlockCode field and CalledCUGInterlockCode field, consistent if (all being 1), think that then the one or three mobile subscriber A/ second mobile subscriber is CUG group user together, it is preferential just to give the corresponding rate of this group of first mobile subscriber; The charging center is after receiving the CFW ticket of the MSC that makes a start, the information that compares CallerCUGInterlockCode field and CalledCUGInterlockCode field, consistent if (all being 1), think that then second mobile subscriber/the 3rd mobile subscriber is CUG group user together, it is preferential just to give the corresponding rate of second mobile subscriber; The charging center is after receiving the MTC ticket of receiving end MSC, the information that compares CallerCUGInterlockCode field and CalledCUGInterlockCode field, consistent if (all being 1), think that then second mobile subscriber/the 3rd mobile subscriber is CUG group user together, it is preferential just to give the corresponding rate of this group of the 3rd mobile subscriber.
Embodiment 5, mobile subscriber-landline telephone outbound call, and CUG calls flow process and detailed handling process of singly filling in thereof:
Calling out called subscriber's (PSTN, fixed telephone network) with calling subscriber (CUG group 1 user) is example, and the calling procedure of CUG customer call PSTN below has been described:
The calling subscriber: the CUG group that only contracted, and this CUG group's CUGInterlock=1, to user CUGIndex=11 that should CUG group;
Called subscriber: can not consider the CUG group that whether contracts;
Process description:
If the calling subscriber is CUG user, mobile phone can be with the user index of going up this calling subscriber when sending call setup setup message;
Call proceeding, the MSC that makes a start sends IAM message to the GMSC that makes a start, and goes out the group energy force information with the CUG group code and the CUG that go up the calling subscriber;
The GMSC that makes a start sends IAM to receiving end, and content is with what receive, and receiving end GMSC sends IAM to landline telephone Local Exchange, carries CUG information;
The final relevant information that in the fixedly ticket that landline telephone Local Exchange goes out, also can note the CUG of caller and called users;
The CallerCUGInterlockCode field is found to have in the charging center after receiving the MOC ticket of the MSC that makes a start; And do not have the CalledCUGInterlockCode field, think that then caller and called users is the distinct group user.
Embodiment 6, landline telephone-mobile subscriber's incoming call, CUG calls flow process and detailed handling process of singly filling in thereof;
Calling out called calling subscriber (CUG group 1 user) with calling subscriber (PSTN) is example, has illustrated that below the fixed telephone subscriber calls out CUG user's calling procedure:
The calling subscriber: the CUG group that only contracted, and this CUG group's CUGInterlock=1, to user CUGIndex=11 that should CUG group;
The called subscriber: CUG group 3 supposes to have contracted
Process description:
If the calling subscriber is CUG user, call proceeding, landline telephone Local Exchange sends IAM message to the GMSC that makes a start (Gateway MSC, gateway exchange MSC), goes out the group energy force information with the CUG group code and the CUG that go up the calling subscriber;
The GMSC that makes a start transmits the IAM that it is received to receiving end, and receiving end GMSC sends IAM to MSC, carries CUG information;
Receiving end MSC if support landline telephone and the same group of mobile subscriber, then notes called subscriber's CUG group code after receiving IAM message, if do not support, then do not fill in this field; When finally producing MTC, be recorded in the CallerCUGInterlockCode field of MTC; On the other hand, when obtaining called party data in the handshaking procedure, receiving end MSC can obtain calling subscriber's CUG group code, finally can be recorded among the CalledCUGInterlockCode of MTC ticket;
The information of CallerCUGInterlockCode field and CalledCUGInterlockCode field is compared in the charging center after receiving the MTC ticket of receiving end MSC, it is preferential just to give the corresponding rate of this group of calling subscriber; Perhaps the charging center is after receiving the MOC ticket of the MSC that makes a start, discovery has the CallerCUGInterlockCode field, do not have the CalledCUGInterlockCode field, think that then caller and called users is the distinct group user, then calculate called subscriber's tariff data according to common expenses standard.
Embodiment 7, intelligent network user-mobile subscriber, CUG intra-group call flow process and detailed handling process of singly filling in thereof
Calling out called subscriber (CUG group 1 user) with calling subscriber (CUG group 1 user, PPS user) is example, and intelligent network user is done the calling procedure of the CUG intra-group call of caller:
The calling subscriber: the CUG group that only contracted, and this CUG group's CUGInterlock=1, to user CUGIndex=11 that should CUG group, and this user PPS that contracted;
The called subscriber: the CUG group that only contracted, and this CUG group's CUGInterlock=1, to user CUGIndex=22 that should CUG group;
Process description:
If the calling subscriber is CUG user, mobile phone can be with the user index of going up this calling subscriber when sending call setup setup message;
Because the calling subscriber is intelligent network user, calling subscriber's MSC triggers MO (intelligent dialing) flow process according to calling subscriber's OCSI (intelligent dialing subscription information), and the CUG group code and the CUG that carry the calling subscriber go out the group energy force information;
Service control point (Service Control Point, be called for short SCP) find to have CUG information (MO flow process in IDP (Initial Detection Point message) (the DP2 intelligent dialing trigger detection point) message, thereby think that what carry is calling subscriber's CUG information), just send the CUG ability of ATI (query messages in real time) message to HLR inquiry called subscriber, CUG group code and CUG that HLR returns the called subscriber go out the group energy force information; SCP judges that caller and called users be with crowd user, and it is preferential just the calling subscriber to be carried out real-time rate, calculates the maximum duration that the calling subscriber can converse, and is handed down to calling subscriber's MSC by section;
The MSC/VLR that makes a start sends routing iinformation according to calling subscriber's subscription data to HLR, goes out the group energy force information with CUG group code that goes up the calling subscriber and this user's CUG;
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, go out the group energy force information with the CUG group code and the CUG that go up the called subscriber;
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, just directly notes.When finally go out chargeing detailed single MOC, with calling subscriber's CUG group code record in the CallerCUGInterlockCode of MOC field, called subscriber's CUG group code record in CalledCUGInterlockCode;
Call proceeding, the MSC that makes a start sends IAM message to receiving end MSC, goes out the group energy force information with the CUG group code and the CUG that go up the calling subscriber;
Receiving end MSC notes calling subscriber's CUG group code after receiving IAM message, so that when finally producing MTC, be recorded in the CallerCUGInterlockCode field of MTC; On the other hand, when obtaining called party data in the handshaking procedure, receiving end MSC can obtain called subscriber's CUG group code, finally can be recorded among the CalledCUGInterlockCode of MTC ticket;
The charging center is after receiving the MOC ticket of the MSC that makes a start, owing to be intelligent MOC ticket, calling subscriber's rate are preferential in real time, and just no longer handle the charging center, and this is single only as the foundation with the SCP accounting checking.Accordingly, the charging center is after receiving the MTC ticket of receiving end MSC, the information that compares CallerCUGInterlockCode field and CalledCUGInterlockCode field, consistent if (all being 1), think that then caller and called users is CUG group user together, it is preferential just to give the corresponding rate of this group of called subscriber.
Embodiment 8, mobile subscriber-intelligent network user, and CUG intra-group call flow process and detailed processing procedure of singly filling in thereof:
Calling out called subscriber (CUG group 1 user, PPS user) with calling subscriber (CUG group 1 user) is example, and intelligent network user is done the calling procedure of called CUG intra-group call:
The calling subscriber: the CUG group that only contracted, and this CUG group's CUGInterlock=1, to user CUGIndex=11 that should CUG group;
The called subscriber: the CUG group that only contracted, and this CUG group's CUGInterlock=1, to user CUGIndex=22 that should CUG group, and this user PPS that contracted.
Process description:
If the calling subscriber is CUG user, mobile phone can be with the user index of going up this calling subscriber when sending call setup setup message;
The MSC/VLR that makes a start sends routing iinformation according to calling subscriber's subscription data to HLR, goes out the group energy force information with CUG group code that goes up the calling subscriber and this user's CUG;
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 the CUG group code and the CUG that carry the called subscriber go out the group energy force information;
The MSC that makes a start triggers called IN process according to TCSI, and the CUG group code and the CUG that carry the called subscriber go out the group energy force information;
SCP finds IDP (DP12, the test point of called intelligent trigger) has CUG information (MT (called intelligence) flow process in the message, thereby think that what carry is called subscriber's CUG information), just send ATI message to HLR inquiring calling user's CUG ability, 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 crowd user, and it is preferential just the called subscriber to be carried out real-time rate, calculates the maximum duration that B can converse, and is handed down to calling subscriber's MSC by section;
Calling subscriber's MSC continues to call out, and asks called subscriber's routing iinformation once more to HLR;
HLR inquires about called subscriber's information once more, 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 routing iinformation MSRN (mobile station roaming number), go out group energy force information (can not being with) here with the CUG group code that goes up the called subscriber and CUG because brought calling subscriber's MSC when getting route for the first time;
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, just directly notes.When finally go out chargeing detailed single MOC, with calling subscriber's CUG group code record in the CallerCUGInterlockCode of MOC field, called subscriber's CUG group code record in CalledCUGInterlockCode;
Call proceeding, the MSC that makes a start sends IAM message to receiving end MSC, goes out the group energy force information with the CUG group code and the CUG that go up the calling subscriber;
Receiving end MSC notes calling subscriber's CUG group code after receiving IAM message, so that when finally producing MTC, be recorded in the CallerCUGInterlockCode field of MTC; On the other hand, when obtaining called party data in the handshaking procedure, receiving end MSC can obtain called subscriber's CUG group code, finally can be recorded among the CalledCUGInterlockCode of MTC ticket;
The charging center is behind the MOC ticket of receiving the MSC A that makes a start, the information that compares CallerCUGInterlockCode field and CalledCUGInterlockCode field, consistent (all being 1) thinks that then caller and called users is CUG group user together, and it is preferential just to give the corresponding rate of this group of calling subscriber.Accordingly, the charging center is behind the MTC ticket of receiving receiving end MSC B, because it is called to be that intelligent network user is done, called subscriber's rate are preferential in real time by SCP, and (by the Call Reference Number associated deletion) just no longer handled in the charging center.In addition, because MSC calling subscriber is called subscriber's a triggering office, might produce intelligent MTC ticket, this ticketing center does not deal with yet, and this ticket is only as the foundation with the SCP accounting checking.
It should be noted that at last: above embodiment only in order to the explanation the present invention and and unrestricted technical scheme described in the invention; Therefore, although this specification has been described in detail the present invention with reference to each above-mentioned embodiment,, those of ordinary skill in the art should be appreciated that still and can make amendment or be equal to replacement the present invention; And all do not break away from the technical scheme and the improvement thereof of the spirit and scope of the present invention, and it all should be encompassed in the middle of the claim scope 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.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200410079083.4A CN1756285B (en) | 2004-09-30 | 2004-09-30 | Processing method for realizing group user preferential charge |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200410079083.4A CN1756285B (en) | 2004-09-30 | 2004-09-30 | Processing method for realizing group user preferential charge |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1756285A CN1756285A (en) | 2006-04-05 |
| CN1756285B true CN1756285B (en) | 2010-08-25 |
Family
ID=36689204
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200410079083.4A Expired - Fee Related CN1756285B (en) | 2004-09-30 | 2004-09-30 | Processing method for realizing group user preferential charge |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1756285B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101039364A (en) * | 2007-03-01 | 2007-09-19 | 华为技术有限公司 | Group telephone exchange service expense calculating method, system and equipment |
| CN101110983B (en) * | 2007-07-26 | 2010-08-18 | 中兴通讯股份有限公司 | Method for implementing commercial VPMN business based on intelligent network |
| CN101198171B (en) * | 2007-12-27 | 2011-09-21 | 中兴通讯股份有限公司 | Routing method for strategy charging control information in roaming scene |
| CN101453723B (en) * | 2008-11-11 | 2010-12-08 | 华为技术有限公司 | Communication service implementing method, equipment and system |
| CN101945368A (en) * | 2009-07-06 | 2011-01-12 | 华为技术有限公司 | Group charging method, charging processor and communication system |
| CN111008875B (en) * | 2019-12-24 | 2023-07-14 | 北京思特奇信息技术股份有限公司 | Method and system for calculating group preference based on personal real-time |
-
2004
- 2004-09-30 CN CN200410079083.4A patent/CN1756285B/en not_active Expired - Fee Related
Non-Patent Citations (1)
| Title |
|---|
| 郝振武.中兴通讯ZXPCS10.0无线市话系统各种新业务的实现.移动通信.2003,31-34. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1756285A (en) | 2006-04-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20120282903A1 (en) | Virtual number gateway | |
| US20030050042A1 (en) | Method for billing short messages in a mobile radio network and device for carrying out the method | |
| CN1968428B (en) | CDMA intelligent network system and its method for implementing global roaming service | |
| US20110263220A1 (en) | Regional Zone Based Mobile Charging | |
| WO2007098668A1 (en) | A method, service control device and communication system for realizing the service of one card for multiple numbers | |
| WO2008125034A1 (en) | Charging method, routing method and relative device based on number portability | |
| CN1171494C (en) | Tariff determination in mobile telecommunication networks | |
| CN101394450B (en) | Inteligent network real-time charging method and platform implementing using subsequent number based on SCP multiple number for one phone | |
| CN1756285B (en) | Processing method for realizing group user preferential charge | |
| CN103379462A (en) | Method and device for processing charging requests | |
| CN101800965A (en) | Charging method, apparatus and system | |
| CN1738344B (en) | Charging method for intelligence service | |
| CN100499893C (en) | A method for implementing local pre-paid charging service for international roaming subscriber | |
| CN101106809B (en) | Billing method for prepayment user to send SMS upon cross-network roaming | |
| CN101516080A (en) | Calling method based on one-card multi-number service and one-card multi-number server | |
| AU2006256962A1 (en) | Network controlled classification of service tariff class | |
| CN100591018C (en) | Business control equipment, roaming charging system and charging method | |
| CN101835128B (en) | Intelligent network call charging method and network | |
| CN102137362B (en) | Intelligent number-correcting calling method and system of prepayment user, and relevant device | |
| WO2012034338A1 (en) | Mobile virtual private network group intelligent service billing method and system | |
| CN1997092A (en) | An implementation method and system for call charging of the smart network subscribers | |
| CN100551098C (en) | The method of pre-payment service user callingcalled payment telephone service party | |
| EP1299997B1 (en) | Arranging of billing in a telecommunication system | |
| CN103781042A (en) | Method for carrying out service charging on prepaid called user in roaming state | |
| CN101299787A (en) | Method for implementing mobile intelligent network pre-payment service |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20100825 Termination date: 20210930 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |