CA2214568A1 - Communicating billing identification information for call delivery - Google Patents
Communicating billing identification information for call delivery Download PDFInfo
- Publication number
- CA2214568A1 CA2214568A1 CA002214568A CA2214568A CA2214568A1 CA 2214568 A1 CA2214568 A1 CA 2214568A1 CA 002214568 A CA002214568 A CA 002214568A CA 2214568 A CA2214568 A CA 2214568A CA 2214568 A1 CA2214568 A1 CA 2214568A1
- Authority
- CA
- Canada
- Prior art keywords
- msc
- call
- identification data
- billing identification
- message
- 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.)
- Abandoned
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/41—Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/49—Connection to several service providers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/50—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP for cross-charging network operators
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/80—Rating or billing plans; Tariff determination aspects
- H04M15/8038—Roaming or handoff
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/24—Accounting or billing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
- H04M2215/01—Details of billing arrangements
- H04M2215/0164—Billing record, e.g. Call Data Record [CDR], Toll Ticket[TT], Automatic Message Accounting [AMA], Call Line Identifier [CLI], details, i.e. parameters, identifiers, structure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
- H04M2215/20—Technology dependant metering
- H04M2215/2026—Wireless network, e.g. GSM, PCS, TACS
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
- H04M2215/32—Involving wireless systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
- H04M2215/34—Roaming
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
- H04M2215/46—Connection to several service providers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
- H04M2215/52—Interconnection, inter-exchange, reseller billing, billing agreements between different operators, e.g. billing identifier added on the CDR in order to cross charge the other operator, inter-operator accounting, reconciliation, bill directly resellers customers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
- H04M2215/74—Rating aspects, e.g. rating parameters or tariff determination apects
- H04M2215/7442—Roaming
Abstract
There is disclosed a system and method for communicating accounting and billing operations informations between a gateway mobile switching center (G-MSC) (42) and a visiting mobile switching center (V-MSC) (52) to which a call is being directed to a mobile station (16) within a cellular telecommunications network. The method comprises the steps of: generating in the serving MSC (42) first biling identification data for the call;
transmitting the first billing identification data to the destination MSC
(52); generating second billing identification data in the destination MSC
(52) corresponding to a call transaction that has occurred in the destination MSC (52); and returning the second billing identification data as related billing identification data to the serving MSC (42) after an outcome for the call has been determined in the destination MSC (52). The outcome of the call is determined when a page response has been received in the V-MSC (52) from the mobile station or alternatively, a call has been delivered by seizing a trunk from the serving MSC (42) to the destination MSC (52). The method has application in a data message handler communication protocol system for communicating accounting and billing operations within the cellular telecommunications network.
transmitting the first billing identification data to the destination MSC
(52); generating second billing identification data in the destination MSC
(52) corresponding to a call transaction that has occurred in the destination MSC (52); and returning the second billing identification data as related billing identification data to the serving MSC (42) after an outcome for the call has been determined in the destination MSC (52). The outcome of the call is determined when a page response has been received in the V-MSC (52) from the mobile station or alternatively, a call has been delivered by seizing a trunk from the serving MSC (42) to the destination MSC (52). The method has application in a data message handler communication protocol system for communicating accounting and billing operations within the cellular telecommunications network.
Description
-CA 02214~68 1997-09-03 -2 PCT/~ .5G~ 7 Communicating Billing Identification Information for Call Delivery FIELD OF THE INVENTION
The present invention relates to a Data Message Handler (DMH) cnmmnn:A~tion protocol system for use in a cellular telecommunications network and a related method for communicating accounting and billing operations within the network.
I~ACKGRQUND OF THL INVENTION
Cellular telecommunications networks currently employ multi-system mobile switching center (MSC) networks that operate with dirr~rel,L proprietary billingprotocols. Consequently, it is ~liffi~llt for opeldlo~ to correlate billing information amongst these MSC networks. It is not possible at this time to correlate this ill~JlllldLi~;)n on a real time basis. Due to the dirrelel1ces in proprietary billing protocols between MSC n~Lw~lk~, calls that are setup through several multi-system MSC's are rated according to the hlrolllldLion logged in either the gateway MSC through which the call is setup to the PSTN or the anchor MSC through which the call is delivered to the mobile station (MS).
Currently, the Tfle~,.. i~ ";c~ n~ Industry Association (TIA) standard known as IS41, herein incol~,ldLed by lerelence, makes provisions for billing h~llll-dLion to be sent in the rul w~ d direction from a serving or gateway MSC (G-MSC), serving a call request, to a d~stin~tion or visiting MSC (V-MSC) delivering the call to the mobile subscriber. This billing h~llllaLion corresponds to a "BillingId" data field that is deflned to include the switch identity (SVVID), the IS-41 Call Identity (CALLID), and the leg of the call (LEG NO) (hereinafter collectively referred to as BillingId). The purpose ofthe BillingId in the "call-delivery" is to deliver a correlating BillingId in an IS-41 invoke message from the G-MSC to V-MSC. IS-41 makes no provision to return to the G-MSC any billing information genc:ldled in the V-MSC for the purpose of cc,llela~ g the billing hlrolllldLion.
CA 02214~68 1997-09-03 WO 96/31072 PCI~ G~ 72 The Telecommunications Industry Association (TIA) is currently developing standard IS-124 known as the DMH standard. The TIA has sl~ggested in the IS-41 Rev C Ballot, July 11, 1994, SYNACOM TECHNOLOGY (herein incorporated by reference) the introduction of a BillingId data field in the "call-delivery" IS-41 retum result mes~g~. IS-124 proposes sending a BillingId, comprising SWID+CALLID+LEG NO infommation which identifies a leg of a call at a V-MSC, from the V-MSC to the G-MSC. The BillingId generated in the visiting MSC (V-MSC) is sent back to the serving or gateway MSC (G-MSC) as part of the "RouteRequestRetum" and RetumResults messages such as retum results for LocateRequest, FeatureRequest, OriginationRequest, and T~ relNumberRequest.
By using the ~L~ldal di~t d IS-124 DMH communication protocol it should be possible to share call event h~~ Lion amongst multi-system MSC networks and perfomm immediate accounting and billing operations. In certain call scenarios, however, this proposed standard would retum unreliable and incorrect billing h~ll,.aLion to the G-MSC.
In in~t~nrec where the "BillingId" is sent from a bordering/destin~tion system or V-MSC towards a serving system or G-MSC, the BillingId can be incorrect in certain situations, or the BillingId can be allocated and not used to tag billing data.
Thus the current proposed IS-124 standard in certain call delivery situations can result in the L t.. .~ ;ol- of unreliable RillingTtl i.~l.l.alion from the V-MSC to the G-MSC.
For ~ , in a s~ tir~n where a call is initi~ted to a MS that is located at a V-MSC
and where a voice channel is not allocated prior to delivering a call to the MS, the BillingId will be allocated to the called party by the V-MSC upon reception of the RouteRequest m~s~e (ROUTREO). If the call is ended by the calling party in the G-MSC while the BillingId is being Ll ~ ecl by the V-MSC to the G-MSC then the BillingId gets wasted because the BillingId does not get to tag a call in the V-MSC.
The result is an unreliable BillingId.
Another eA~ll~le of an unreliable BillingId can occur in a situation where the MS is in the V-MSC, the MS has made a three way call and the current call LEG NO.
is tagged as LEGNO. = n. Should a subsequent call waiting call be initi~ted to the MS
in the V-MSC, then a BillingId of LEG NO. = n+l would be allocated to the call CA 022l4~68 lgg7-09-03 Wo 96/31072 pcrlsEs6loo272 waiting call upon reception of a RouteRequest message in the V-MSC. This BillingId would then be returned to the G-MSC via the IS-41 RouteRequest/ LocationRequest messages. Should the MS end the call while the BillingId is being tr~ncmittecl to the G-MSC and the MS subsequently initi~tes a new call with a new CALLID and a LEG
NO. = 0, then the subsequent received three way call with the previously generated CALLID and LEG NO. = n+1 would be inconcict~nt with the new call. The result is an unreliable BillingId.
Yet another exarnple of an unreliable BillingId can occur when the MS is in the V-MSC already setup on a call that is tagged as LEG NO. = n and a subsequent call waiting is ~Llell~Led to the MS. A BillingId of LEG NO. = n+ 1 is allocated to the call waiting at reception of the IS-41 RouteRequest mess~ge and returned to the G-MSC.
Should the call be delivered to the V-MSC but not answered, then subsequent "C-number" call diversions may possibly occur in the V-MSC being tagged with BillingId LEG NOs. n+2, n+3 and so on. If the called party in the V-MSC happens to initiate a three way call in parallel, there potentially could be confiicting or interleaved leg numbering. Thus there is a need to be able to tag the diverted calls with a new CALLID which is an aspect addressed by the present invention.
These above mP.ntif~n~ ,co~ ipe in the l t;~Ol ~ing of BillingId information results in unreliable billing identification illrol,na~ion being fed back to the G-MSC
network.
It would be a distinct advantage to have a DMH communication protocol system that is capable of ret~-rning to the G-MSC reliable Related BillingId information for call delivery. The present invention provides such a system.
SUMMARY QF THE Il~VENTION
The present invention is directed to a DMH communication protocol system that is capable of returning to the G-MSC reliable related billing i~l~ntific~tion information for call delivery. The present invention provides such a system by returning a new Illrolm~Lion Back for.Call Delivery (INFOBACKCD) (invoke) m~c~g~. from the ~3e~ ;nn MSC, or V-MSC, to the serving MSC, or G-MSC, after CA 02214~68 1997-09-03 -WO96/31072 PCT/~l~5G~r~c /~
an outcome for the call has been d~ in the V- MSC. The new rNFOBACKCD
message comprises two parts. The first part is the BillingId (invoke) sent in the forward direction from the G-MSC to the V-MSC. The second part of the INFOBACKCD meee~ge is a Related BillingId which is the BillingId allocated in the V-MSC after a call has been delivered. It should be understood that a Related BillingId describes the billing h~llllaLion sent to the G-MSC. In the industry, the BillingId genc:l~led in the G-MSC becomes the Related BillingId from the perspective ofthe V-MSC. However, the for the purposes of the sperific~tion and claims, unless identified otherwise, the term Related BillingId refers to the BillingId il~ull~la~ion generated at the V-MSC as seen by the G-MSC.
The outcome of a call can be determined when a page response is received by the V-MSC from the mobile station or after the call delivery is made from the G-MSC
to the V-MSC. At this time a more reliable meSs~ge is returned to the G-MSC. This illr(~l ~ ~ ~,-~ ion can be used exclusively to tag call transactions or can be used to correlate call transactions in the G-MSC and V-MSC.
In accordance with an aspect of the present invention there is provided a data message handler (DMH) communication protocol system for use in a cellular telecomm-mir~tions network for commllnic~ting accoullling and billing hlr~llllalion associated with a call to a mobile station within the network. The system inr.lndes a visiting mobile ~wilcl~ g center (V-MSC) where said mobile station to which the call is being directed is located and a gal~w~y mobile swiLcl~ g center (G-MSC) whichupon delivery of said call to the G-MSC, generates first billing itl~.ntifir,~tinn data and Ll~:ulSllli~:~ the first billing identification data as part of a call invoke message to said V-MSC. The V-MSC inrllldes means for allocating second billing identification datacoll~oll&l~, to a call tr~ne~rtion that has occurred in the V-MSC in response to said the invoke mree~ The V-MSC also inr.1~ltlre means V-MSC for returning the secondbilling idrntific~tion data to the G-MSC as related billing identifir.~tion data after an outcome for the call has been determined.
Preferably, the V-MSC returns an "IllÇullll~lion Back for Call Delivery"
Illr~;~n~ ~FOBACKCD) that inr.lndes the related billing identification data from the V-MSC and the billing identification message ~lw~ded from the G-MSC to the V--CA 02214~68 1997-09-03 WO 96/31072 PCT/~ G~57 MSC It is envisaged that the related billing identification data is form~ te~l in the V-MSC by the V-MSC allocating an increm~nted leg number to previously generated billing i-l~?ntific~tic)n data when the delivered call is an extension of the original call to the mobile station, such as for e~ plc, a call waiting leg that is to be answered, or the V-MSC allocating new billing identification data when the delivered call is a new call or not an extension of the existing call In accor~ ce with another aspect of the present invention there is provided a method of commllni~ting accounting and billing operations il~l,.laLion between aserving MSC and a destin~tion MSC to which a call is being directed to a mobile station within a cellular tel~commllni~tif)ne network The method comprises the steps of g~ ~ in the serving MSC first billing id~ntific~tion data representative of the call in the serving MSC;
tr~nemhting the first billing identification data to the ~le,etin~tion MSC;
generating second billing i(l~ntifi~tion data in the destin~tion MSC
corresponding to a call transaction that has occurred in the destination MSC; and returning the second biliing identification data as related billing identification data to the serving MSC after an outcome for the call has been determined l~RIEF DESCRIPTION OF THE DRAWINGS
For a better underst~n~ling of the nature and objects of the present invention reference may be had to the acco...p~h-ying diag.~.~--aLic drawings in which Figure 1 is a network node drawing illustrating the eign~ling utilized in the IS-4 1 and proposed in the IS-124 specification;
Figure 2 is a network node dl~whlg illustrating the eign~ling ofthe p.er~l-ed embodiment of the present invention;
Figure 3 is a meee~ge flow diagram illu~ li..g the steps occurring during serving invoke requests and passing of biliing identifiers in the p- t;re-- ~d embodiment of the present invention;
Figure 4 is a flow diagram of the steps the V-MSC takes to generate the Related BillingId i~lru~ alion in accordance with the p-t:rt;--~d embodiment of the CA 02214~68 1997-09-03 -WO 96/31072 PCTISE~G~ C27 present invention; and, Figure S is a is a message flow diagram illustrating the steps occurring in an alternative embodiment of the present invention that utilizes a hybrid solution comprising the INFOBACKCD mess~e of the present invention and the BillingIds proposed by Synacom Technology, Inc. in the above referenced paper entitled IS-124 Tmr~c.t~ on IS-41, Revision 0.
DETAILED DESCRIPTION
While any commllnir~tiQn protocol may be utilized within the scope and intent of the present invention, the prer~ . t;d embodiment described herein utilizes the most commonly used commnnic~tions protocol in the cellular industry set by the IS-41 standard.
The present invention contemplates a new message being added to the IS-41, Revision C. This new mee~ge is a billing il~lllldlion return message referred tothroughout the sFerifir~fion as the INFOBACKCD mec$~ge The significant difference about this message is that it is returned after an outcome for the call has beend~Lellllilled. This may be either a page response received from the mobile station or when a call has been delivered to the mobile station (MS). At this time the lNFOBACKCD mrc~ge cc .~ the billing identification data (BillingId) contained in the IS41 me~gec is sent from the serving MSC (G-MSC) to the ciestin~tion MSC
or (V-MSC) and inr.l~lcles related billing i~1entific~tiQn data (Related BillingId) generated by the V-MSC which is not prone to the inCon~ictenries described in the background of the invention.
The BillingId and Related BillingIds ofthe present invention cOl~ llll to the IS-41 standard protocol. The BillingId's are composed of a 24 bit global e~rc.h~nge identity (GLEXM) (switch identity SWID) + a 24 bit call icientifir.~tiQn (CALLID) + an 8 bit Segment number. The CALLID part is used to tag a specific caller, i.e. one "CALLID"
is tied to each caller in a call. The Segment Number lt;plesell~ a "leg number" to identify all the calls a ca11er has been involved in, i.e. the first call setup by a caller would have a "leg number = 0", a second.three way call would be tagged with a "leg number 1", reception of a call waiting call would be tagged with a "leg number = 2", CA 02214~68 1997-09-03 WO 96/3 1 072 PCT/~ C;~ _ 27 2 and so on. The BillingId and Related BillingId data forrning parts of the INFOBACKCD message are used to tag the IS-124 Origination, Redirection, Feature Activation, and Terrnination Leg Subrecords. The l.leani..~, of "Segment Number" in each of these IS-41 BillingId fields is to identify a "Leg No. " The leg number is passed S between MSC's in the ~ign~ling messages of IS-41 as part of the RillingTd field of RouteRequest, LocationRequest, InLe- ~y~Le~llPage, UnsolicitedResponse and Redirection Messages.
Referring to Figure 1 there is shown a network node drawing illustrating the sign~ling utilized in the IS-41 as proposed by the IS-124 speçific~tion. Currently, in the IS-41 s~ld~ud, a caU is setup or delivered from a public switching network (PSTN) 10 or a mobile station (MS) 12 to a serving MSC 14, heleanel referred to as MSC-A
14. The call delivery h~rullllalion contains the B identification number for the MS-B
16. To set up the caU to MS-B 16, the MSC-A 14 sends a Location/Request mese~
(LOCREQ) (invoke) to HLR-B 18. The LOCREQ number inrllldes the B-number h~ollllaLion and BillingId in accordance with the IS-41 protocol set out in the above p~ . For .eimplirity this RillingTd is listed as SWID=A, CALLID--102, and LEG
NUMBER = 0. In other words the BillingId identifies the call coming from MSC-A
to be the 102nd caU set up by MSC-A with this particular call being the first leg of the caU. The d.~i,.g illustrates this i.~.-l,alion as BillingId [A-102-0]. Upon receipt of the LOCREQ m~cs~ge7 the HLR-B 18 then d~lel.. Ji-les if the B-number is a valid number. If the B-number is a valid number, the HLR-B 18 sends a RouteRequest (ROUTREQ) (invoke) .,.~c~ge to MSC-B 20. This ROUTREQ inrl~ldes the BillingId [A-102-0]. Upon receipt ofthis ROUTREQ MSC-B 20 creates its own call record by s e~ignin~ its own BillingId. In this example, a SWID=B, CALLID=500 and a LEG
NUMBER=0 is ~eei ned [B-500-0]. MSC-B 20 sends a RouteRequestReturn (ROUTREQR) (response) message to HLR-B. It is in the proposal for the IS-124 dald that ROI~EQR m~e~ge inrllld~s the BillingId [B-500-0] generated in the MSC-B 20. This feature was not originally provided in the IS-41 standard. Next, the HLR-B sends aT oc~t~Re~ stReturn ~LOCREQR) (l~ol s~) m~e~ge to MSC-A 14 The LOCREQR mres~ge also in~ lde,e the.MSC-B BillingId [B-500-0]. The MSC-A
14 then establishes a trunk 22 to MSC-B 20 along which the call is delivered.
CA 02214~68 1997-09-03 WO 96/31072 PCT/~ GJ'~C272 Below dotted line 23 in Figure 1 is shown the billing records that are established for the call delivered at 22 during the call setup process. The billing record established by MSC-A 14 for the origination or redirection leg ofthe call is shown at 24. The billing record established by MSC-B 20 for the tel ll,i"aLion leg of the call is shown at 26. The BillingId [A-102-0] shown in box 28 of record 24 is first generated by MSC-A
14. Next, MSC-B 20 stores the BillingId [A-102-0] at 32 in record 26 as a Related BillingId. MSC-B 20 stores its generated BillingId [B-500-0] at 30 in record 26. The standard IS-41 provides for the three pieces of information to be stored in these two records. This means that the termination leg record 26 of the call could trace the call back to the origination leg record of the call 24 if need be at a later date. With the introduction of the MSC-B 20 BillingId [B-500-0] being sent back in the response.,..o~;~,.ges during call setup to MSC-A 14 as provided for by proposed standard IS-124, the origination call record 24 then has a Related BillingId [B-500-0] at 34. This now allows for forward call correlation at a later date or upon call completion. Thepl~1 s associated with this call set up scheme proposed by the standard IS-124 relate to the return of incorrect BillingId il~""~lion to the MSC-A in the event the call is not delivered and these problems have been di.~c~lssed heretofore in the Background of the Invention.
Referring to Figure 2 the l~lerelled embodiment for the present invention is illuskated For the most part, the si~n~ling provided in Figure 2 is consistent with the IS-41 ~ign~ling as shown in Figure 1. However, there are filntl~m~.nt~l differences in ~i n~ling between Figure 1 and Figure 2. The first fimtl~m~nt~l difference is that the ROUTREQR m~Ss~ge in Figure 2 from the MSC-B 20 to the HLR-B 18 from the MSC-A does not include the BillingId [B-500-0]. The second filnt1~m~nt~l difference is that the LOCREQR message sent from the HLR-B 18 to the MSC-A 14 does not include the RillingT~1 [B-500-0]. These two fim-l~m~nt~l differences are peculiar to the plc;relled embodiment ofthe present invention. In the present invention, it is only after an outcome of a call is determined either by a page ~e~Ollse being received from MS-B
16 or a trunk 22 being established that a separate "h~ Lion back for call deliver"
INFOBACKCD (invoke) message 33 is sent to the MSC-A 14 from the MSC-B 20.
The INFOBACKCD m~se~ 33 ~--~ the BillingId number generated by the MSC-CA 02214~68 1997-09-03 WO 96/31072 PcT/~ G~c ~ i2 - B tB-500-0] the BillingId number generated in the MSC-A 14 [A-102-0]. The ~ ;"ru. ,~ ion iS sent back in a protocol of [BillingTfl, Related BillingId] or [A- 102-0, B-500-0] in this example, such that this information can now be stored in a new billing record 24 for the origination leg of the call. Furthermore, this INFOBACKCD
message can be sent back directly by the MSC-B 20 to the MSC-A 4. Next, the commnnications protocol of the present invention has the MSC-A 14 send an ";..ro....~I;on back for call delivery response" (INFOBACKCDR) (response) message 35 to the MSC-B 20 as an acknowle~lgment that the INFOBACKCD message 33 was received. While Figure 2 does not show billing records 24 and 26, it should be understood from the ru.egoi,.g description that the eign~lin~ protocol ofthe present invention will provide for the gene- aLion of the illustrated billing records of Figure 1.
Referring to Figure 3, a p.ere--ed embodiment for the present invention is described in the form of a me.e.e~ge flow diagram illustrating the steps occurring during serving invoke requests and passing of billing identifiers.
While this description may be somewhat rednn-l~nt in view of the previous description of Figure 2, it is believed that it will be helpful to the impl~m~nt~tion ofthe ei~ling protocol ofthe present invention. First a call origination 36 and dialed mobile address digits (i.e., directory number) 38 are received either from another mobile station via a cel or from the public switched telephc-n~ network (PSTN) 40 at a serving or gateway MSC (G-MSC) 42 using protocols defined by the IS-41 h~Le.~iomlection standard. The delivery of this call is illustrated by call delivery 39.
Next the G-MSC 42 sends an lNVOKE (invoke) m~es~ge 44 request incl~7~1ing the BillingId to the home location register (EILR) 46 associated with the called mobile station. The association of the called mobile station to the ~R 46 is made through di-~u-y number 38. It should be understood that the INVOKE message 44 may be - comprise anyone of several di~l~.. L types of messages such as a FeatureRequest ~ge ~EiEATREQ), an OriginationRequest meee~ge (ORREQ), a LocationRequest mess~ge (LOCREQ), or a Transfer Number request (T Q). All of these m~ee~ges will include BillingId data.
Next,ifthedi~ ,Lo-ynumberis~eeign~toale~;l;"l~lesubscriber,the~R46 sends a "RouteRequest (ROUTREQ) (invoke)" message 48 to a visiting HLR (VLR) CA 02214~68 1997-09-03 -WO 96/31072 PCT/~ Gl'WO~ /~
50 that last provided a ~ lion notification for the called mobile station. The VLR
50 then sends a ROUTREQ (invoke) mese~ge at 51 to a destin~tion MSC (V-MSC) 52. Both ROUTREQ meee~gee 48 and 51 include the BillingId.
Next, there are several ways the call can be delivered to the MS. First the V-MSC 52 sends out a page request in its area to see if the MS located in its area. If the MS is located in the V-MSC's 52 coverage area, the MS should respond to the pageand the V-MSC sends out a ROUTREQ (response) message 53 to the VLR 50.
At the same time the V-MSC 52 is sending out a page request to the MS, the V-MSC also sends ISPAGE (invoke) message 41 to several border MSC's 43. The 10 ISPAGE mess~ge 41 will include BillingId information allowing the border MSC 43 to bill the call in the event the border MSC 43 delivers the call to the MS. The purpose of the ISPAGE m.oee~ge is to locate the MS in the event the MS is not located in its last registered V-MSC 52, the bordering MSC's 43. In the event the MS is located in one of the border MSC's 43 and the MS sends a page ~ ollse back to the border MSC 43, 15 an ISPAGE (response) message 45 is sent back to the V-MSC 52. The V-MSC 52 then sends out the ROUTREQ ( ~sl~ollse) me.e.e~ge 53 to the VLR 50 advising that the border MSC is plepaled to set up the call.
Still yet another scenario to set up the call to the MS occurs when the MS in response to a page from the V-MSC 52, sends a page response meee~ge to another 20 border MSC 47 which did not receive the ISPAGE (invoke) m~es~e 41. This scenario can happen because upon receipt of a page, the MS goes through a rescan process looking for the ~L~ ge~L signal channel to lock onto. If that channel is associated with the coverage provided by border MSC 47, then the MS sends its page response backto the border MSC 47. At this time, the border MSC 47 sends an Unsolicited 25 Response (UNSOLRES) (invoke) m~ee~ge 47 to the V-MSC 52 with BillingId hlr~ ion. The V-MSC 52 returns an UNSOLRES (response) message 49R to the border MSC 47. This return mee.e~ge inr.lncles BillingId h~olllla~ion allowing the border MSC 47 to tag for the call. The V-MSC 52 then sends out a ROUTREQ
(response) meee~ge 53 to the VLR 50.
AP[er the ROUTREQ (response) message 53 is sent to the VLR 50, the VLR
50 in turn sends a ROUTREQ (response) message 54 back to HLR 46. HLR 46 then CA 02214~68 1997-09-03 WO 96/31072 PCT/~i~9~ 72 returns a return result (RETURNRESULT) m~ ge to the G-MSC.
- In accordance with the present invention, at this time any of V-MSC 52, or border MSC's 43 or 47 may receive a page response form the MS. If this happens it is an indication of a new call being set up to the MS and the an al,plupliate serving MSC (43, 47 or 52) allocates the BillingId. If one of the bordering MSC's 43 or 47 receives the page response then the INFOBACKCD (invoke) meec~ge 176 is sent fromthis MSC to the G-MSC 42. Message 176 is shown as one mess~ge and it should be understood that each of bordering MSC's 43 and 47 would have its own INFOBACKCD message 178. A return acknowle~lgm~nt INFOBACKCDR is sent from G-MSC 42 to the applc~ liate MSC 43 or 47 at 178.. If one ofthe V-MSC 52 receives the page response, then the ~IFOBACKCD (invoke) message 180 is sent from this V-MSC 52 to the G-MSC 42. A return acknowle ~m~nt INFOBACKCDR is sent from G-MSC 42 to the approl.liate V-MSC 52 at 182 Upon receipt of the RETURNRESULT (response) m~s~ge 55 the call is delivered to the MS by a call delivery being setup on trunk 56 or trunk 170 depending on which MSC (43,47, or 52) has received the page response from the MS.
In accc,l dallce with the present invention, if no page response is received form the mobile station in the V-MSC or bordering MSC's, then once the call delivery 56 or 170 is set up, an INFOBACKCD (invoke) m.s~Ege 57 or 172, l~ e~;Li~rely, is sent from the V-MSC 52 to G-MSC 42. The G-MSC 42 then sends a INFOBACKCDR
(response) message 58 or 174 to the applu~liaLe MSC to complete the comm- mlcations.
The INFOBACKCD me~s~ge comprises the BillingId originally forwarded by the G-MSC and a new piece of h~ollllalion. This new information comprises the Related BillingId which has been generated by the V-MSC.
- The generation of the Related BillingId in the V-MSC is shown in the flow chart of Figure 4 for a RouteRequest m~S~ge It should be understood that a flow chart for the ISPAGE or UNSOLRESPONSE mess~ges would be similar to that described below and the differences in the flow chart should be readily app~ to a man skilled in the art. Once a RouteRequest 65 is received at the V-MSC, the V-MSC
pages the MS and waits to receive a page at 67. If a page response is received from CA 02214~68 1997-09-03 ~
WO 96/31072 PCr/~G~_27~
the MS, then the V-MSC allocates a new BillingId at 69. Next, because the outcome of the call has been determined at 67 by the "YES" answer, the BillingId is sent back '-to the G-MSC as a Related BillingId as part of the INFOBACKCD message at 78. TheBillingId of the INFOBACKCD message corresponds to the BillingId originally generated in the G-MSC at call setup.
In the event no page response is received from the MS at 67, after the call is delivered from the G-MSC to the V-MSC at 70, the V-MSC then interrogates the call by detelll i. i.lg if the call is not an extension of the original call at 72. This may be a call that the first leg of the call, a call diversion, a call inhibit or a forward release. If the call is a~"---aLi~e for any of these inquiries, then the V-MSC allocates a new BillingId to the call at 74 and makes this part of the Related BillingId. The V-MSC
then form~ tes the INFOBACKCD message at 78 by putting together the BillingId h~l.ndLion sent by the G-MSC and the Related BillingId from step 78. Because theinterrogation of step at 72 is negative, then the call being delivered is an answered call waiting leg. The V-MSC then at 76 increments the leg number of this previously generated BillingId. Next the V-MSC form--l~tes the INFOBACKCD message at 78 by putting together the BillingId information sent by the G-MSC and the Related BillingId from either step 74 or 76.
1~ ~fP~rring to Figure S there is shown m~Sq~ge flow diagram illustrating the steps occurring during serving invoke requests and passing of billing i~l~ntif~rs in an alternative embodiment of the present invention that utilizes a hybrid solution comprising the INFOBACKCD m~ ge of the present invention and the BillingT~ls proposed by Synacom Technology, Inc. in the above referenced paper entitled IS-124 Impacts on IS-41, Revision 0. First a call origination 110 and dialed mobile address digits (i.e., directory number) 112 are received either from another mobile station or from the public switched t~lepl~ nelwu-h (PSTN) 116 at a serving or gateway MSC
(G-MSC) 118 using protocols defined by the IS-41 hlLeLconl~ection standard. The delivery of this call is illustrated by call delivery 114.
Next the G-MSC 118 sends an INVOKE (invoke) message 120 request including billing identification ;~rs~ ;on in the m~e~ge (BillingId) to the homelo~tion register (HLR) 122 a~oc;~L~;d with the called mobile station. The association :
CA 02214~68 1997-09-03 WO 96/31072 PCT/SE~G~'vC27~
of the called mobile station to the HLR 122 is made through directory number. It- should be understood that the rNVOKE mees~e 120 may be comprise anyone of several di~el~lll types of m~ss~gçs such as a FEATREQ, ORREQ, LOCREQ, and TRANI~EQ. All of these messages will include the BillingId.
S Next, if the directory number is ~eei~ned to a le~ le subscriber, the HLR
122 sends a ROUTREQ (invoke) ",~ A~e 124 to a visiting location register (VLR) 126 that last provided a registration notifi~tion for the called mobile station. The VLR 126 then sends a ROUTREQ (invoke) m~ce~g~ at 128 to a (l~stin~tion MSC (V-MSC) 130.
Both ROUTREQ messages 124 and 128 include BillingId.
Next, there are several ways the call can be delivered to the MS . First the V-MSC 130 sends out a page request in its area to see if the MS located in its area. If the MS is located in the V-MSC's 130 coverage area, the MS should respond to the page and the V-MSC sends out a ROUTREQ (l t:~ponse) m~ee~ 132 to the VLR 126. This message returns the BillingId information.
At the same time the V-MSC 130 is sending out a page request to the MS, the V-MSC also sends ISPAGE (invoke) m~ss~ge 134 to several border MSC's 136. The ISPAGE m~e.e~ge 134 will include BillingId h~lllldLion allo~,ving the border MSC 136 to bill the call in the event the border MSC 136 delivers the call to the MS. The purpose of the ISPAGE m~ee~ge is to locate the MS in the event the MS is not located in its last I ~Lel ed V-MSC. In the event the MS is located in one of the border MSC's 136 and the MS sends a page response back to the border MSC 136, an ISPAGE
(response) mloes~ge 138 is sent back to the V-MSC 130. Message 138 contains the BillingId i~ lldlion. The V-MSC 130 then sends out the ROUTREQ (response) mese~ge 132 to the VLR 126 advising that the border MSC is prepared to set up the call.
Still yet an~ el scenario to set up the call to the MS occurs when the MS in It;~onse to a page from the V-MSC sends a page response message to another border MSC 140 which did not receive the ISPAGE (invoke) message 134. This scenario canhappen because upon receipt of a page, the MS goes through a rescan process looking for the strongest signal channel to lock onto. If that channel is associated with the coverage provided by border MSC 140, then the MS sends its page response back to CA 02214~68 1997-09-03 the border MSC 140. At this tirne, the border MSC 140 sends an Unsolicited Response (UNSOLRES) (invoke) message 142 to the V-MSC 130 with BillingId hlrullllaLion.
The V-MSC 130 returns an UNSOLRES (response) message 144 to the border MSC
140. This return m~cc~ge in~ c BillingId hlrollllaLion allowing the border MSC 140 S to tag for the call. The V-MSC 130 then sends out the ROUTREQ (response) message 132 to the VLR 126 advising that the border MSC is prepared to set up the call.
APcer the ROUTREQ (le*,ollse) m~cs~ 132 is sent to the VLR 126, the VLR
126 in tum sends a ROUTREQ (response) message 146 back to HLR 122. HLR 122 then returns a return result (RETURNRESULT) message to the G-MSC. Mecs~es 132, 146, and 148 all contain the BillingId generated by the V-MSC. As has been discussed h~t;Lorul~ in the Background of the Invention, the BillingId returned in m~.cc~geS 132, 146 and 148 may not be reliable when the Leg No. is a value other than 0.
Upon receipt of the RETURNRESULT (response) message 148 the call is delivered to the MS. Depending on which MSC (130, 136 or 140) has received the page response from the MS, one of the call deliveries (invoke) 150 or 160 will be set up.
In accordance with the present invention, once the call delivery (invoke) message 150 or 160 is set up, a return h~rullnaLion back after call delivery (INFOBACKCDR) (response) .. ~ ge 152 or 162, le;~el;Li~ely will be sent back from the MSC 130 or MSC 136 or 140. For all intents and purposes, the MSC to which the call is delivered may now be referred to as the V-MSC. This G-MSC 118 then sendsa INFOBACKCDR (response) message 154 or 164 back to the V-MSC to complete the commlmiç~tions The INFOBACKCD meCc~ge comprises the BillingId information originally forwarded by the G-MSC and also contains a new piece of information. This new ;..r~ .n comprises the Related BillingId il~lllla~ion which is generated by the V-MSC. The Related BillingId in this embodiment is used to correct the BillingId ;--r,~ ;on returned by mecc~ges 132, 146, and 148. All ofthese m~cs~ges can thenbe used to tag call tr~nc~cti~ns to the MS.
It is thus believed that the operation and construction of the present invention WO 96/31072 - PCT/~h'~G/~272 will be a~palt;l-L from the foregoing description. While the method and system shown and described has been characterized as pl~r~lled, it will be readily appalellL that various çh~nges and modifications could be made therein ~,vithout departing from the spirit and scope of the invention as defined in the following claims.
The present invention relates to a Data Message Handler (DMH) cnmmnn:A~tion protocol system for use in a cellular telecommunications network and a related method for communicating accounting and billing operations within the network.
I~ACKGRQUND OF THL INVENTION
Cellular telecommunications networks currently employ multi-system mobile switching center (MSC) networks that operate with dirr~rel,L proprietary billingprotocols. Consequently, it is ~liffi~llt for opeldlo~ to correlate billing information amongst these MSC networks. It is not possible at this time to correlate this ill~JlllldLi~;)n on a real time basis. Due to the dirrelel1ces in proprietary billing protocols between MSC n~Lw~lk~, calls that are setup through several multi-system MSC's are rated according to the hlrolllldLion logged in either the gateway MSC through which the call is setup to the PSTN or the anchor MSC through which the call is delivered to the mobile station (MS).
Currently, the Tfle~,.. i~ ";c~ n~ Industry Association (TIA) standard known as IS41, herein incol~,ldLed by lerelence, makes provisions for billing h~llll-dLion to be sent in the rul w~ d direction from a serving or gateway MSC (G-MSC), serving a call request, to a d~stin~tion or visiting MSC (V-MSC) delivering the call to the mobile subscriber. This billing h~llllaLion corresponds to a "BillingId" data field that is deflned to include the switch identity (SVVID), the IS-41 Call Identity (CALLID), and the leg of the call (LEG NO) (hereinafter collectively referred to as BillingId). The purpose ofthe BillingId in the "call-delivery" is to deliver a correlating BillingId in an IS-41 invoke message from the G-MSC to V-MSC. IS-41 makes no provision to return to the G-MSC any billing information genc:ldled in the V-MSC for the purpose of cc,llela~ g the billing hlrolllldLion.
CA 02214~68 1997-09-03 WO 96/31072 PCI~ G~ 72 The Telecommunications Industry Association (TIA) is currently developing standard IS-124 known as the DMH standard. The TIA has sl~ggested in the IS-41 Rev C Ballot, July 11, 1994, SYNACOM TECHNOLOGY (herein incorporated by reference) the introduction of a BillingId data field in the "call-delivery" IS-41 retum result mes~g~. IS-124 proposes sending a BillingId, comprising SWID+CALLID+LEG NO infommation which identifies a leg of a call at a V-MSC, from the V-MSC to the G-MSC. The BillingId generated in the visiting MSC (V-MSC) is sent back to the serving or gateway MSC (G-MSC) as part of the "RouteRequestRetum" and RetumResults messages such as retum results for LocateRequest, FeatureRequest, OriginationRequest, and T~ relNumberRequest.
By using the ~L~ldal di~t d IS-124 DMH communication protocol it should be possible to share call event h~~ Lion amongst multi-system MSC networks and perfomm immediate accounting and billing operations. In certain call scenarios, however, this proposed standard would retum unreliable and incorrect billing h~ll,.aLion to the G-MSC.
In in~t~nrec where the "BillingId" is sent from a bordering/destin~tion system or V-MSC towards a serving system or G-MSC, the BillingId can be incorrect in certain situations, or the BillingId can be allocated and not used to tag billing data.
Thus the current proposed IS-124 standard in certain call delivery situations can result in the L t.. .~ ;ol- of unreliable RillingTtl i.~l.l.alion from the V-MSC to the G-MSC.
For ~ , in a s~ tir~n where a call is initi~ted to a MS that is located at a V-MSC
and where a voice channel is not allocated prior to delivering a call to the MS, the BillingId will be allocated to the called party by the V-MSC upon reception of the RouteRequest m~s~e (ROUTREO). If the call is ended by the calling party in the G-MSC while the BillingId is being Ll ~ ecl by the V-MSC to the G-MSC then the BillingId gets wasted because the BillingId does not get to tag a call in the V-MSC.
The result is an unreliable BillingId.
Another eA~ll~le of an unreliable BillingId can occur in a situation where the MS is in the V-MSC, the MS has made a three way call and the current call LEG NO.
is tagged as LEGNO. = n. Should a subsequent call waiting call be initi~ted to the MS
in the V-MSC, then a BillingId of LEG NO. = n+l would be allocated to the call CA 022l4~68 lgg7-09-03 Wo 96/31072 pcrlsEs6loo272 waiting call upon reception of a RouteRequest message in the V-MSC. This BillingId would then be returned to the G-MSC via the IS-41 RouteRequest/ LocationRequest messages. Should the MS end the call while the BillingId is being tr~ncmittecl to the G-MSC and the MS subsequently initi~tes a new call with a new CALLID and a LEG
NO. = 0, then the subsequent received three way call with the previously generated CALLID and LEG NO. = n+1 would be inconcict~nt with the new call. The result is an unreliable BillingId.
Yet another exarnple of an unreliable BillingId can occur when the MS is in the V-MSC already setup on a call that is tagged as LEG NO. = n and a subsequent call waiting is ~Llell~Led to the MS. A BillingId of LEG NO. = n+ 1 is allocated to the call waiting at reception of the IS-41 RouteRequest mess~ge and returned to the G-MSC.
Should the call be delivered to the V-MSC but not answered, then subsequent "C-number" call diversions may possibly occur in the V-MSC being tagged with BillingId LEG NOs. n+2, n+3 and so on. If the called party in the V-MSC happens to initiate a three way call in parallel, there potentially could be confiicting or interleaved leg numbering. Thus there is a need to be able to tag the diverted calls with a new CALLID which is an aspect addressed by the present invention.
These above mP.ntif~n~ ,co~ ipe in the l t;~Ol ~ing of BillingId information results in unreliable billing identification illrol,na~ion being fed back to the G-MSC
network.
It would be a distinct advantage to have a DMH communication protocol system that is capable of ret~-rning to the G-MSC reliable Related BillingId information for call delivery. The present invention provides such a system.
SUMMARY QF THE Il~VENTION
The present invention is directed to a DMH communication protocol system that is capable of returning to the G-MSC reliable related billing i~l~ntific~tion information for call delivery. The present invention provides such a system by returning a new Illrolm~Lion Back for.Call Delivery (INFOBACKCD) (invoke) m~c~g~. from the ~3e~ ;nn MSC, or V-MSC, to the serving MSC, or G-MSC, after CA 02214~68 1997-09-03 -WO96/31072 PCT/~l~5G~r~c /~
an outcome for the call has been d~ in the V- MSC. The new rNFOBACKCD
message comprises two parts. The first part is the BillingId (invoke) sent in the forward direction from the G-MSC to the V-MSC. The second part of the INFOBACKCD meee~ge is a Related BillingId which is the BillingId allocated in the V-MSC after a call has been delivered. It should be understood that a Related BillingId describes the billing h~llllaLion sent to the G-MSC. In the industry, the BillingId genc:l~led in the G-MSC becomes the Related BillingId from the perspective ofthe V-MSC. However, the for the purposes of the sperific~tion and claims, unless identified otherwise, the term Related BillingId refers to the BillingId il~ull~la~ion generated at the V-MSC as seen by the G-MSC.
The outcome of a call can be determined when a page response is received by the V-MSC from the mobile station or after the call delivery is made from the G-MSC
to the V-MSC. At this time a more reliable meSs~ge is returned to the G-MSC. This illr(~l ~ ~ ~,-~ ion can be used exclusively to tag call transactions or can be used to correlate call transactions in the G-MSC and V-MSC.
In accordance with an aspect of the present invention there is provided a data message handler (DMH) communication protocol system for use in a cellular telecomm-mir~tions network for commllnic~ting accoullling and billing hlr~llllalion associated with a call to a mobile station within the network. The system inr.lndes a visiting mobile ~wilcl~ g center (V-MSC) where said mobile station to which the call is being directed is located and a gal~w~y mobile swiLcl~ g center (G-MSC) whichupon delivery of said call to the G-MSC, generates first billing itl~.ntifir,~tinn data and Ll~:ulSllli~:~ the first billing identification data as part of a call invoke message to said V-MSC. The V-MSC inrllldes means for allocating second billing identification datacoll~oll&l~, to a call tr~ne~rtion that has occurred in the V-MSC in response to said the invoke mree~ The V-MSC also inr.1~ltlre means V-MSC for returning the secondbilling idrntific~tion data to the G-MSC as related billing identifir.~tion data after an outcome for the call has been determined.
Preferably, the V-MSC returns an "IllÇullll~lion Back for Call Delivery"
Illr~;~n~ ~FOBACKCD) that inr.lndes the related billing identification data from the V-MSC and the billing identification message ~lw~ded from the G-MSC to the V--CA 02214~68 1997-09-03 WO 96/31072 PCT/~ G~57 MSC It is envisaged that the related billing identification data is form~ te~l in the V-MSC by the V-MSC allocating an increm~nted leg number to previously generated billing i-l~?ntific~tic)n data when the delivered call is an extension of the original call to the mobile station, such as for e~ plc, a call waiting leg that is to be answered, or the V-MSC allocating new billing identification data when the delivered call is a new call or not an extension of the existing call In accor~ ce with another aspect of the present invention there is provided a method of commllni~ting accounting and billing operations il~l,.laLion between aserving MSC and a destin~tion MSC to which a call is being directed to a mobile station within a cellular tel~commllni~tif)ne network The method comprises the steps of g~ ~ in the serving MSC first billing id~ntific~tion data representative of the call in the serving MSC;
tr~nemhting the first billing identification data to the ~le,etin~tion MSC;
generating second billing i(l~ntifi~tion data in the destin~tion MSC
corresponding to a call transaction that has occurred in the destination MSC; and returning the second biliing identification data as related billing identification data to the serving MSC after an outcome for the call has been determined l~RIEF DESCRIPTION OF THE DRAWINGS
For a better underst~n~ling of the nature and objects of the present invention reference may be had to the acco...p~h-ying diag.~.~--aLic drawings in which Figure 1 is a network node drawing illustrating the eign~ling utilized in the IS-4 1 and proposed in the IS-124 specification;
Figure 2 is a network node dl~whlg illustrating the eign~ling ofthe p.er~l-ed embodiment of the present invention;
Figure 3 is a meee~ge flow diagram illu~ li..g the steps occurring during serving invoke requests and passing of biliing identifiers in the p- t;re-- ~d embodiment of the present invention;
Figure 4 is a flow diagram of the steps the V-MSC takes to generate the Related BillingId i~lru~ alion in accordance with the p-t:rt;--~d embodiment of the CA 02214~68 1997-09-03 -WO 96/31072 PCTISE~G~ C27 present invention; and, Figure S is a is a message flow diagram illustrating the steps occurring in an alternative embodiment of the present invention that utilizes a hybrid solution comprising the INFOBACKCD mess~e of the present invention and the BillingIds proposed by Synacom Technology, Inc. in the above referenced paper entitled IS-124 Tmr~c.t~ on IS-41, Revision 0.
DETAILED DESCRIPTION
While any commllnir~tiQn protocol may be utilized within the scope and intent of the present invention, the prer~ . t;d embodiment described herein utilizes the most commonly used commnnic~tions protocol in the cellular industry set by the IS-41 standard.
The present invention contemplates a new message being added to the IS-41, Revision C. This new mee~ge is a billing il~lllldlion return message referred tothroughout the sFerifir~fion as the INFOBACKCD mec$~ge The significant difference about this message is that it is returned after an outcome for the call has beend~Lellllilled. This may be either a page response received from the mobile station or when a call has been delivered to the mobile station (MS). At this time the lNFOBACKCD mrc~ge cc .~ the billing identification data (BillingId) contained in the IS41 me~gec is sent from the serving MSC (G-MSC) to the ciestin~tion MSC
or (V-MSC) and inr.l~lcles related billing i~1entific~tiQn data (Related BillingId) generated by the V-MSC which is not prone to the inCon~ictenries described in the background of the invention.
The BillingId and Related BillingIds ofthe present invention cOl~ llll to the IS-41 standard protocol. The BillingId's are composed of a 24 bit global e~rc.h~nge identity (GLEXM) (switch identity SWID) + a 24 bit call icientifir.~tiQn (CALLID) + an 8 bit Segment number. The CALLID part is used to tag a specific caller, i.e. one "CALLID"
is tied to each caller in a call. The Segment Number lt;plesell~ a "leg number" to identify all the calls a ca11er has been involved in, i.e. the first call setup by a caller would have a "leg number = 0", a second.three way call would be tagged with a "leg number 1", reception of a call waiting call would be tagged with a "leg number = 2", CA 02214~68 1997-09-03 WO 96/3 1 072 PCT/~ C;~ _ 27 2 and so on. The BillingId and Related BillingId data forrning parts of the INFOBACKCD message are used to tag the IS-124 Origination, Redirection, Feature Activation, and Terrnination Leg Subrecords. The l.leani..~, of "Segment Number" in each of these IS-41 BillingId fields is to identify a "Leg No. " The leg number is passed S between MSC's in the ~ign~ling messages of IS-41 as part of the RillingTd field of RouteRequest, LocationRequest, InLe- ~y~Le~llPage, UnsolicitedResponse and Redirection Messages.
Referring to Figure 1 there is shown a network node drawing illustrating the sign~ling utilized in the IS-41 as proposed by the IS-124 speçific~tion. Currently, in the IS-41 s~ld~ud, a caU is setup or delivered from a public switching network (PSTN) 10 or a mobile station (MS) 12 to a serving MSC 14, heleanel referred to as MSC-A
14. The call delivery h~rullllalion contains the B identification number for the MS-B
16. To set up the caU to MS-B 16, the MSC-A 14 sends a Location/Request mese~
(LOCREQ) (invoke) to HLR-B 18. The LOCREQ number inrllldes the B-number h~ollllaLion and BillingId in accordance with the IS-41 protocol set out in the above p~ . For .eimplirity this RillingTd is listed as SWID=A, CALLID--102, and LEG
NUMBER = 0. In other words the BillingId identifies the call coming from MSC-A
to be the 102nd caU set up by MSC-A with this particular call being the first leg of the caU. The d.~i,.g illustrates this i.~.-l,alion as BillingId [A-102-0]. Upon receipt of the LOCREQ m~cs~ge7 the HLR-B 18 then d~lel.. Ji-les if the B-number is a valid number. If the B-number is a valid number, the HLR-B 18 sends a RouteRequest (ROUTREQ) (invoke) .,.~c~ge to MSC-B 20. This ROUTREQ inrl~ldes the BillingId [A-102-0]. Upon receipt ofthis ROUTREQ MSC-B 20 creates its own call record by s e~ignin~ its own BillingId. In this example, a SWID=B, CALLID=500 and a LEG
NUMBER=0 is ~eei ned [B-500-0]. MSC-B 20 sends a RouteRequestReturn (ROUTREQR) (response) message to HLR-B. It is in the proposal for the IS-124 dald that ROI~EQR m~e~ge inrllld~s the BillingId [B-500-0] generated in the MSC-B 20. This feature was not originally provided in the IS-41 standard. Next, the HLR-B sends aT oc~t~Re~ stReturn ~LOCREQR) (l~ol s~) m~e~ge to MSC-A 14 The LOCREQR mres~ge also in~ lde,e the.MSC-B BillingId [B-500-0]. The MSC-A
14 then establishes a trunk 22 to MSC-B 20 along which the call is delivered.
CA 02214~68 1997-09-03 WO 96/31072 PCT/~ GJ'~C272 Below dotted line 23 in Figure 1 is shown the billing records that are established for the call delivered at 22 during the call setup process. The billing record established by MSC-A 14 for the origination or redirection leg ofthe call is shown at 24. The billing record established by MSC-B 20 for the tel ll,i"aLion leg of the call is shown at 26. The BillingId [A-102-0] shown in box 28 of record 24 is first generated by MSC-A
14. Next, MSC-B 20 stores the BillingId [A-102-0] at 32 in record 26 as a Related BillingId. MSC-B 20 stores its generated BillingId [B-500-0] at 30 in record 26. The standard IS-41 provides for the three pieces of information to be stored in these two records. This means that the termination leg record 26 of the call could trace the call back to the origination leg record of the call 24 if need be at a later date. With the introduction of the MSC-B 20 BillingId [B-500-0] being sent back in the response.,..o~;~,.ges during call setup to MSC-A 14 as provided for by proposed standard IS-124, the origination call record 24 then has a Related BillingId [B-500-0] at 34. This now allows for forward call correlation at a later date or upon call completion. Thepl~1 s associated with this call set up scheme proposed by the standard IS-124 relate to the return of incorrect BillingId il~""~lion to the MSC-A in the event the call is not delivered and these problems have been di.~c~lssed heretofore in the Background of the Invention.
Referring to Figure 2 the l~lerelled embodiment for the present invention is illuskated For the most part, the si~n~ling provided in Figure 2 is consistent with the IS-41 ~ign~ling as shown in Figure 1. However, there are filntl~m~.nt~l differences in ~i n~ling between Figure 1 and Figure 2. The first fimtl~m~nt~l difference is that the ROUTREQR m~Ss~ge in Figure 2 from the MSC-B 20 to the HLR-B 18 from the MSC-A does not include the BillingId [B-500-0]. The second filnt1~m~nt~l difference is that the LOCREQR message sent from the HLR-B 18 to the MSC-A 14 does not include the RillingT~1 [B-500-0]. These two fim-l~m~nt~l differences are peculiar to the plc;relled embodiment ofthe present invention. In the present invention, it is only after an outcome of a call is determined either by a page ~e~Ollse being received from MS-B
16 or a trunk 22 being established that a separate "h~ Lion back for call deliver"
INFOBACKCD (invoke) message 33 is sent to the MSC-A 14 from the MSC-B 20.
The INFOBACKCD m~se~ 33 ~--~ the BillingId number generated by the MSC-CA 02214~68 1997-09-03 WO 96/31072 PcT/~ G~c ~ i2 - B tB-500-0] the BillingId number generated in the MSC-A 14 [A-102-0]. The ~ ;"ru. ,~ ion iS sent back in a protocol of [BillingTfl, Related BillingId] or [A- 102-0, B-500-0] in this example, such that this information can now be stored in a new billing record 24 for the origination leg of the call. Furthermore, this INFOBACKCD
message can be sent back directly by the MSC-B 20 to the MSC-A 4. Next, the commnnications protocol of the present invention has the MSC-A 14 send an ";..ro....~I;on back for call delivery response" (INFOBACKCDR) (response) message 35 to the MSC-B 20 as an acknowle~lgment that the INFOBACKCD message 33 was received. While Figure 2 does not show billing records 24 and 26, it should be understood from the ru.egoi,.g description that the eign~lin~ protocol ofthe present invention will provide for the gene- aLion of the illustrated billing records of Figure 1.
Referring to Figure 3, a p.ere--ed embodiment for the present invention is described in the form of a me.e.e~ge flow diagram illustrating the steps occurring during serving invoke requests and passing of billing identifiers.
While this description may be somewhat rednn-l~nt in view of the previous description of Figure 2, it is believed that it will be helpful to the impl~m~nt~tion ofthe ei~ling protocol ofthe present invention. First a call origination 36 and dialed mobile address digits (i.e., directory number) 38 are received either from another mobile station via a cel or from the public switched telephc-n~ network (PSTN) 40 at a serving or gateway MSC (G-MSC) 42 using protocols defined by the IS-41 h~Le.~iomlection standard. The delivery of this call is illustrated by call delivery 39.
Next the G-MSC 42 sends an lNVOKE (invoke) m~es~ge 44 request incl~7~1ing the BillingId to the home location register (EILR) 46 associated with the called mobile station. The association of the called mobile station to the ~R 46 is made through di-~u-y number 38. It should be understood that the INVOKE message 44 may be - comprise anyone of several di~l~.. L types of messages such as a FeatureRequest ~ge ~EiEATREQ), an OriginationRequest meee~ge (ORREQ), a LocationRequest mess~ge (LOCREQ), or a Transfer Number request (T Q). All of these m~ee~ges will include BillingId data.
Next,ifthedi~ ,Lo-ynumberis~eeign~toale~;l;"l~lesubscriber,the~R46 sends a "RouteRequest (ROUTREQ) (invoke)" message 48 to a visiting HLR (VLR) CA 02214~68 1997-09-03 -WO 96/31072 PCT/~ Gl'WO~ /~
50 that last provided a ~ lion notification for the called mobile station. The VLR
50 then sends a ROUTREQ (invoke) mese~ge at 51 to a destin~tion MSC (V-MSC) 52. Both ROUTREQ meee~gee 48 and 51 include the BillingId.
Next, there are several ways the call can be delivered to the MS. First the V-MSC 52 sends out a page request in its area to see if the MS located in its area. If the MS is located in the V-MSC's 52 coverage area, the MS should respond to the pageand the V-MSC sends out a ROUTREQ (response) message 53 to the VLR 50.
At the same time the V-MSC 52 is sending out a page request to the MS, the V-MSC also sends ISPAGE (invoke) message 41 to several border MSC's 43. The 10 ISPAGE mess~ge 41 will include BillingId information allowing the border MSC 43 to bill the call in the event the border MSC 43 delivers the call to the MS. The purpose of the ISPAGE m.oee~ge is to locate the MS in the event the MS is not located in its last registered V-MSC 52, the bordering MSC's 43. In the event the MS is located in one of the border MSC's 43 and the MS sends a page ~ ollse back to the border MSC 43, 15 an ISPAGE (response) message 45 is sent back to the V-MSC 52. The V-MSC 52 then sends out the ROUTREQ ( ~sl~ollse) me.e.e~ge 53 to the VLR 50 advising that the border MSC is plepaled to set up the call.
Still yet another scenario to set up the call to the MS occurs when the MS in response to a page from the V-MSC 52, sends a page response meee~ge to another 20 border MSC 47 which did not receive the ISPAGE (invoke) m~es~e 41. This scenario can happen because upon receipt of a page, the MS goes through a rescan process looking for the ~L~ ge~L signal channel to lock onto. If that channel is associated with the coverage provided by border MSC 47, then the MS sends its page response backto the border MSC 47. At this time, the border MSC 47 sends an Unsolicited 25 Response (UNSOLRES) (invoke) m~ee~ge 47 to the V-MSC 52 with BillingId hlr~ ion. The V-MSC 52 returns an UNSOLRES (response) message 49R to the border MSC 47. This return mee.e~ge inr.lncles BillingId h~olllla~ion allowing the border MSC 47 to tag for the call. The V-MSC 52 then sends out a ROUTREQ
(response) meee~ge 53 to the VLR 50.
AP[er the ROUTREQ (response) message 53 is sent to the VLR 50, the VLR
50 in turn sends a ROUTREQ (response) message 54 back to HLR 46. HLR 46 then CA 02214~68 1997-09-03 WO 96/31072 PCT/~i~9~ 72 returns a return result (RETURNRESULT) m~ ge to the G-MSC.
- In accordance with the present invention, at this time any of V-MSC 52, or border MSC's 43 or 47 may receive a page response form the MS. If this happens it is an indication of a new call being set up to the MS and the an al,plupliate serving MSC (43, 47 or 52) allocates the BillingId. If one of the bordering MSC's 43 or 47 receives the page response then the INFOBACKCD (invoke) meec~ge 176 is sent fromthis MSC to the G-MSC 42. Message 176 is shown as one mess~ge and it should be understood that each of bordering MSC's 43 and 47 would have its own INFOBACKCD message 178. A return acknowle~lgm~nt INFOBACKCDR is sent from G-MSC 42 to the applc~ liate MSC 43 or 47 at 178.. If one ofthe V-MSC 52 receives the page response, then the ~IFOBACKCD (invoke) message 180 is sent from this V-MSC 52 to the G-MSC 42. A return acknowle ~m~nt INFOBACKCDR is sent from G-MSC 42 to the approl.liate V-MSC 52 at 182 Upon receipt of the RETURNRESULT (response) m~s~ge 55 the call is delivered to the MS by a call delivery being setup on trunk 56 or trunk 170 depending on which MSC (43,47, or 52) has received the page response from the MS.
In accc,l dallce with the present invention, if no page response is received form the mobile station in the V-MSC or bordering MSC's, then once the call delivery 56 or 170 is set up, an INFOBACKCD (invoke) m.s~Ege 57 or 172, l~ e~;Li~rely, is sent from the V-MSC 52 to G-MSC 42. The G-MSC 42 then sends a INFOBACKCDR
(response) message 58 or 174 to the applu~liaLe MSC to complete the comm- mlcations.
The INFOBACKCD me~s~ge comprises the BillingId originally forwarded by the G-MSC and a new piece of h~ollllalion. This new information comprises the Related BillingId which has been generated by the V-MSC.
- The generation of the Related BillingId in the V-MSC is shown in the flow chart of Figure 4 for a RouteRequest m~S~ge It should be understood that a flow chart for the ISPAGE or UNSOLRESPONSE mess~ges would be similar to that described below and the differences in the flow chart should be readily app~ to a man skilled in the art. Once a RouteRequest 65 is received at the V-MSC, the V-MSC
pages the MS and waits to receive a page at 67. If a page response is received from CA 02214~68 1997-09-03 ~
WO 96/31072 PCr/~G~_27~
the MS, then the V-MSC allocates a new BillingId at 69. Next, because the outcome of the call has been determined at 67 by the "YES" answer, the BillingId is sent back '-to the G-MSC as a Related BillingId as part of the INFOBACKCD message at 78. TheBillingId of the INFOBACKCD message corresponds to the BillingId originally generated in the G-MSC at call setup.
In the event no page response is received from the MS at 67, after the call is delivered from the G-MSC to the V-MSC at 70, the V-MSC then interrogates the call by detelll i. i.lg if the call is not an extension of the original call at 72. This may be a call that the first leg of the call, a call diversion, a call inhibit or a forward release. If the call is a~"---aLi~e for any of these inquiries, then the V-MSC allocates a new BillingId to the call at 74 and makes this part of the Related BillingId. The V-MSC
then form~ tes the INFOBACKCD message at 78 by putting together the BillingId h~l.ndLion sent by the G-MSC and the Related BillingId from step 78. Because theinterrogation of step at 72 is negative, then the call being delivered is an answered call waiting leg. The V-MSC then at 76 increments the leg number of this previously generated BillingId. Next the V-MSC form--l~tes the INFOBACKCD message at 78 by putting together the BillingId information sent by the G-MSC and the Related BillingId from either step 74 or 76.
1~ ~fP~rring to Figure S there is shown m~Sq~ge flow diagram illustrating the steps occurring during serving invoke requests and passing of billing i~l~ntif~rs in an alternative embodiment of the present invention that utilizes a hybrid solution comprising the INFOBACKCD m~ ge of the present invention and the BillingT~ls proposed by Synacom Technology, Inc. in the above referenced paper entitled IS-124 Impacts on IS-41, Revision 0. First a call origination 110 and dialed mobile address digits (i.e., directory number) 112 are received either from another mobile station or from the public switched t~lepl~ nelwu-h (PSTN) 116 at a serving or gateway MSC
(G-MSC) 118 using protocols defined by the IS-41 hlLeLconl~ection standard. The delivery of this call is illustrated by call delivery 114.
Next the G-MSC 118 sends an INVOKE (invoke) message 120 request including billing identification ;~rs~ ;on in the m~e~ge (BillingId) to the homelo~tion register (HLR) 122 a~oc;~L~;d with the called mobile station. The association :
CA 02214~68 1997-09-03 WO 96/31072 PCT/SE~G~'vC27~
of the called mobile station to the HLR 122 is made through directory number. It- should be understood that the rNVOKE mees~e 120 may be comprise anyone of several di~el~lll types of m~ss~gçs such as a FEATREQ, ORREQ, LOCREQ, and TRANI~EQ. All of these messages will include the BillingId.
S Next, if the directory number is ~eei~ned to a le~ le subscriber, the HLR
122 sends a ROUTREQ (invoke) ",~ A~e 124 to a visiting location register (VLR) 126 that last provided a registration notifi~tion for the called mobile station. The VLR 126 then sends a ROUTREQ (invoke) m~ce~g~ at 128 to a (l~stin~tion MSC (V-MSC) 130.
Both ROUTREQ messages 124 and 128 include BillingId.
Next, there are several ways the call can be delivered to the MS . First the V-MSC 130 sends out a page request in its area to see if the MS located in its area. If the MS is located in the V-MSC's 130 coverage area, the MS should respond to the page and the V-MSC sends out a ROUTREQ (l t:~ponse) m~ee~ 132 to the VLR 126. This message returns the BillingId information.
At the same time the V-MSC 130 is sending out a page request to the MS, the V-MSC also sends ISPAGE (invoke) m~ss~ge 134 to several border MSC's 136. The ISPAGE m~e.e~ge 134 will include BillingId h~lllldLion allo~,ving the border MSC 136 to bill the call in the event the border MSC 136 delivers the call to the MS. The purpose of the ISPAGE m~ee~ge is to locate the MS in the event the MS is not located in its last I ~Lel ed V-MSC. In the event the MS is located in one of the border MSC's 136 and the MS sends a page response back to the border MSC 136, an ISPAGE
(response) mloes~ge 138 is sent back to the V-MSC 130. Message 138 contains the BillingId i~ lldlion. The V-MSC 130 then sends out the ROUTREQ (response) mese~ge 132 to the VLR 126 advising that the border MSC is prepared to set up the call.
Still yet an~ el scenario to set up the call to the MS occurs when the MS in It;~onse to a page from the V-MSC sends a page response message to another border MSC 140 which did not receive the ISPAGE (invoke) message 134. This scenario canhappen because upon receipt of a page, the MS goes through a rescan process looking for the strongest signal channel to lock onto. If that channel is associated with the coverage provided by border MSC 140, then the MS sends its page response back to CA 02214~68 1997-09-03 the border MSC 140. At this tirne, the border MSC 140 sends an Unsolicited Response (UNSOLRES) (invoke) message 142 to the V-MSC 130 with BillingId hlrullllaLion.
The V-MSC 130 returns an UNSOLRES (response) message 144 to the border MSC
140. This return m~cc~ge in~ c BillingId hlrollllaLion allowing the border MSC 140 S to tag for the call. The V-MSC 130 then sends out the ROUTREQ (response) message 132 to the VLR 126 advising that the border MSC is prepared to set up the call.
APcer the ROUTREQ (le*,ollse) m~cs~ 132 is sent to the VLR 126, the VLR
126 in tum sends a ROUTREQ (response) message 146 back to HLR 122. HLR 122 then returns a return result (RETURNRESULT) message to the G-MSC. Mecs~es 132, 146, and 148 all contain the BillingId generated by the V-MSC. As has been discussed h~t;Lorul~ in the Background of the Invention, the BillingId returned in m~.cc~geS 132, 146 and 148 may not be reliable when the Leg No. is a value other than 0.
Upon receipt of the RETURNRESULT (response) message 148 the call is delivered to the MS. Depending on which MSC (130, 136 or 140) has received the page response from the MS, one of the call deliveries (invoke) 150 or 160 will be set up.
In accordance with the present invention, once the call delivery (invoke) message 150 or 160 is set up, a return h~rullnaLion back after call delivery (INFOBACKCDR) (response) .. ~ ge 152 or 162, le;~el;Li~ely will be sent back from the MSC 130 or MSC 136 or 140. For all intents and purposes, the MSC to which the call is delivered may now be referred to as the V-MSC. This G-MSC 118 then sendsa INFOBACKCDR (response) message 154 or 164 back to the V-MSC to complete the commlmiç~tions The INFOBACKCD meCc~ge comprises the BillingId information originally forwarded by the G-MSC and also contains a new piece of information. This new ;..r~ .n comprises the Related BillingId il~lllla~ion which is generated by the V-MSC. The Related BillingId in this embodiment is used to correct the BillingId ;--r,~ ;on returned by mecc~ges 132, 146, and 148. All ofthese m~cs~ges can thenbe used to tag call tr~nc~cti~ns to the MS.
It is thus believed that the operation and construction of the present invention WO 96/31072 - PCT/~h'~G/~272 will be a~palt;l-L from the foregoing description. While the method and system shown and described has been characterized as pl~r~lled, it will be readily appalellL that various çh~nges and modifications could be made therein ~,vithout departing from the spirit and scope of the invention as defined in the following claims.
Claims (28)
1. A data message handler (DMH) communication protocol system for use in a cellular telecommunications network for communicating accounting and billing information associated with a call to a mobile station within the network, said system comprising:
a visiting mobile switching center (V-MSC) where said mobile station to which the call is being directed is located;
a gateway mobile switching center (G-MSC) which upon delivery of said call to the G-MSC, generates first billing identification data and transmits the first billing identification data as part of a call invoke message to said V-MSC;
means within said V-MSC for allocating second billing identification data corresponding to a call transaction that has occurred in the V-MSC in response to said call invoke message; and means within said V-MSC for returning said second billing identification data to the G-MSC as related billing identification data after an outcome for the call has been determined.
a visiting mobile switching center (V-MSC) where said mobile station to which the call is being directed is located;
a gateway mobile switching center (G-MSC) which upon delivery of said call to the G-MSC, generates first billing identification data and transmits the first billing identification data as part of a call invoke message to said V-MSC;
means within said V-MSC for allocating second billing identification data corresponding to a call transaction that has occurred in the V-MSC in response to said call invoke message; and means within said V-MSC for returning said second billing identification data to the G-MSC as related billing identification data after an outcome for the call has been determined.
2. The system of claim 1 wherein the outcome for the call is determined by the V-MSC upon receipt of a page response from the mobile station or after a call has been delivered from the G-MSC to the V-MSC.
3. The system of claim 1 wherein the V-MSC returns an information back for call delivery message that includes the related billing identification data and the first billing identification data forwarded from the G-MSC to the V-MSC, the information back for call delivery message being returned after the outcome of the call is determined in the V-MSC.
4. The system of claim 1 wherein the related billing identification data is formulated in the V-MSC by the V-MSC allocating an incremented leg number to theleg number of a previously generated related billing identification data when the delivered call is an extension of the original call to the mobile station and by the V-MSC allocating a new billing identification data when the delivered call is a new call or not an extension of an existing call.
5. The system of claim 1 wherein the V-MSC is selected from the group consisting of a mobile switching center (MSC) where the mobile station was last paged, a bordering MSC to the MSC where the mobile station was last registered and fromwhich a page response message from the bordering MSC has been received, and a bordering MSC that receives an "unknown" page response from a mobile station that was paged by another MSC.
6. The system of claim 1 wherein the call invoke message generated by the G-MSC is selected for the group consisting of a feature request message, an origination request message, a location request message and a transfer number request message.
7. The system of claim 1 wherein the first billing identification data and therelated billing identification data each include a switch identity number, a call identification, and a segment number identifying a call leg.
8. The system of claim 1 wherein the invoke message is sent to a home locating register (HLR) associated with the G-MSC, the HLR in turn sending a route request message to a visiting location register (VLR) associated with the V-MSC
where the mobile station was last registered and said VLR in turn sending a route request message to said associated V-MSC.
where the mobile station was last registered and said VLR in turn sending a route request message to said associated V-MSC.
9. A method of communicating accounting and billing operations information between a serving mobile switching center (MSC) and a destination MSC
to which a call is being directed to a mobile station within a cellular telecommunications network, the method comprising the steps of:
generating in the serving MSC first billing identification data for the call;
transmitting the first billing identification data to the destination MSC;
generating second billing identification data in the destination MSC
corresponding to a call transaction that has occurred in the destination MSC; and returning the second billing identification data as related billing identification data to the serving MSC after an outcome for the call has been determined in thedestination MSC.
to which a call is being directed to a mobile station within a cellular telecommunications network, the method comprising the steps of:
generating in the serving MSC first billing identification data for the call;
transmitting the first billing identification data to the destination MSC;
generating second billing identification data in the destination MSC
corresponding to a call transaction that has occurred in the destination MSC; and returning the second billing identification data as related billing identification data to the serving MSC after an outcome for the call has been determined in thedestination MSC.
10. The method of claim 9 wherein the outcome of the call is determined in the V-MSC by the V-MSC first checking if there is a receipt of a page response from the mobile station and, if not, determining that a call has been delivered from the G-MSC to the V-MSC
11. The method of claim 9 wherein the step of returning a related billing identification data to the serving MSC includes returning an information back for call delivery message that includes the related billing identification data and the first billing identification data transmitted from the serving MSC to the destination MSC.
12. The method of claim 9 wherein the step of generating second related billing identification data in the destination MSC includes:
allocating an incremented leg number to the leg number of a previously generated related billing identification data when the delivered call is an extension of an original call to the mobile station, and allocating a new billing identification data when the delivered call is a new call or not an extension of an existing call.
allocating an incremented leg number to the leg number of a previously generated related billing identification data when the delivered call is an extension of an original call to the mobile station, and allocating a new billing identification data when the delivered call is a new call or not an extension of an existing call.
13. The method of claim 9 wherein the step of generating a first billing identification data for the call includes generating a call invoke message for one of the group consisting of a feature request message, an origination request message, alocation request message, and a transfer number request message.
14. The method of claim 9 wherein the first billing identification data and the related billing identification data each include a switch identity number, a call identification number, and a segment number identifying a call leg.
15. The method of claim 9 wherein the invoke message is sent to a home locating register (HLR) associated with the serving MSC, the HLR in turn sending a route request message to a visiting location register (VLR) associated with the V-MSC
where the mobile station was last registered and said VLR in turn sending a route request message to said associated MSC.
where the mobile station was last registered and said VLR in turn sending a route request message to said associated MSC.
16. A data message handler (DMH) communication protocol system for use in a cellular telecommunications network for communicating accounting and billing information associated with a call to a mobile station within the network, said system comprising:
a visiting mobile switching center (V-MSC) where said mobile station to which the call is being directed is located;
a gateway mobile switching center (G-MSC) which upon delivery of said call to the G-MSC, generates first billing identification data and transmits the first billing identification data as part of a call invoke message to said V-MSC;
means within said V-MSC for allocating second billing identification data corresponding to a call transaction that has occurred in the V-MSC in response to said call invoke message; and means within said V-MSC for returning said second billing identification data to the G-MSC as related billing identification data after the call has been delivered from the G-MSC to the V-MSC.
a visiting mobile switching center (V-MSC) where said mobile station to which the call is being directed is located;
a gateway mobile switching center (G-MSC) which upon delivery of said call to the G-MSC, generates first billing identification data and transmits the first billing identification data as part of a call invoke message to said V-MSC;
means within said V-MSC for allocating second billing identification data corresponding to a call transaction that has occurred in the V-MSC in response to said call invoke message; and means within said V-MSC for returning said second billing identification data to the G-MSC as related billing identification data after the call has been delivered from the G-MSC to the V-MSC.
17. The system of claim 16 wherein the V-MSC returns an information back for call delivery message that includes the related billing identification data and the first billing identification data forwarded from the G-MSC to the V-MSC, the information back for call delivery message being returned after the outcome of the call is determined in the V-MSC.
18. The system of claim 16 wherein the related billing identification data is formulated in the V-MSC by the V-MSC allocating an incremented leg number to theleg number of a previously generated related billing identification data when the delivered call is an extension of the original call to the mobile station and by the V-MSC allocating a new billing identification data when the delivered call is a new call or not an extension of an existing call.
19. The system of claim 16 wherein the V-MSC is selected from the group consisting of a mobile switching center (MSC) where the mobile station was last paged, a bordering MSC to the MSC where the mobile station was last registered and fromwhich a page response message from the bordering MSC has been received, and a bordering MSC that receives an "unknown" page response from a mobile station that was paged by another MSC.
20. The system of claim 16 wherein the call invoke message generated by the G-MSC is one of group consisting of a feature request message, an origination request message, a location request message and a transfer number request message.
21. The system of claim 16 wherein the first billing identification data and the related billing identification data each include a switch identity number, a call identification, and a segment number identifying a call leg.
22. The system of claim 16 wherein the invoke message is sent to a home locating register (HLR) associated with the G-MSC, the HLR in turn sending a route request message to a visiting location register (VLR) associated with the V-MSC
where the mobile station was last registered and said VLR in turn sending a route request message to said associated V-MSC.
where the mobile station was last registered and said VLR in turn sending a route request message to said associated V-MSC.
23. A method of communicating accounting and billing operations information between a serving mobile switching center (MSC) and a destination MSC
to which a call is being directed to a mobile station within a cellular telecommunications network, the method comprising the steps of:
generating in the serving MSC first billing identification data for the call;
transmitting the first billing identification data to the destination MSC;
generating second billing identification data in the destination MSC corresponding to a call transaction that has occurred in the destination MSC; and, returning the second billing identification data as related billing identification data to the serving MSC after the call has been delivered from the serving MSC to the destination MSC.
to which a call is being directed to a mobile station within a cellular telecommunications network, the method comprising the steps of:
generating in the serving MSC first billing identification data for the call;
transmitting the first billing identification data to the destination MSC;
generating second billing identification data in the destination MSC corresponding to a call transaction that has occurred in the destination MSC; and, returning the second billing identification data as related billing identification data to the serving MSC after the call has been delivered from the serving MSC to the destination MSC.
24. The method of claim 24 wherein the step of returning related billing identification data to the serving MSC includes returning an information back for call delivery message that includes the related billing identification data and the first billing identification data transmitted from the serving MSC to the destination MSC.
25. The method of claim 24 wherein the step of generating second billing identification data in the destination MSC includes:
allocating an incremented leg number to the leg number of a previously generated related billing identification data when the delivered call is an extension of an original call to the mobile station, and allocating a new billing identification data when the delivered call is a new call or not an extension of an existing call.
allocating an incremented leg number to the leg number of a previously generated related billing identification data when the delivered call is an extension of an original call to the mobile station, and allocating a new billing identification data when the delivered call is a new call or not an extension of an existing call.
26. The method of claim 24 wherein the step of generating a first billing identification data for the call includes generating a call invoke message for one of the group consisting of a feature request message, an origination request message, alocation request message and a transfer number request message.
27. The method of claim 24 wherein the first billing identification data and the related billing identification data each include a switch identity number, a call identification number, and a segment number identifying a call leg.
28. The method of claim 24 wherein the invoke message is sent to a home locating register (HLR) associated with the serving MSC, the HLR in turn sending a route request message to a visiting location register (VLR) associated with the MSC
where the mobile station was last registered, and said VLR in turn sending a route request message to its associated MSC.
where the mobile station was last registered, and said VLR in turn sending a route request message to its associated MSC.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US08/409,664 | 1995-03-24 | ||
| US08/409,664 US5796790A (en) | 1995-03-24 | 1995-03-24 | Reliable related billing ID information method for call delivery |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA2214568A1 true CA2214568A1 (en) | 1996-10-03 |
Family
ID=23621473
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002214568A Abandoned CA2214568A1 (en) | 1995-03-24 | 1996-03-01 | Communicating billing identification information for call delivery |
Country Status (10)
| Country | Link |
|---|---|
| US (1) | US5796790A (en) |
| EP (1) | EP0815693A1 (en) |
| JP (1) | JPH11502684A (en) |
| CN (1) | CN1104158C (en) |
| AU (1) | AU708913B2 (en) |
| BR (1) | BR9607654A (en) |
| CA (1) | CA2214568A1 (en) |
| NZ (1) | NZ304457A (en) |
| RU (1) | RU2139641C1 (en) |
| WO (1) | WO1996031072A1 (en) |
Families Citing this family (47)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| FI100075B (en) * | 1994-11-11 | 1997-09-15 | Ericsson Telefon Ab L M | A system for managing subscriber information in a telephone network |
| GB9603582D0 (en) | 1996-02-20 | 1996-04-17 | Hewlett Packard Co | Method of accessing service resource items that are for use in a telecommunications system |
| FR2745970B1 (en) * | 1996-03-07 | 1998-08-07 | France Telecom | PREPAYMENT METHOD FOR CONSUMPTION OF TELEPHONE COMMUNICATIONS |
| US6154445A (en) | 1996-04-18 | 2000-11-28 | Bell Atlantic Network Services, Inc. | Telephony communication via varied redundant networks |
| US6069890A (en) | 1996-06-26 | 2000-05-30 | Bell Atlantic Network Services, Inc. | Internet telephone service |
| DE19635581C1 (en) * | 1996-09-02 | 1997-10-23 | Siemens Ag | Cellular mobile communications network subscriber location method |
| JP2845831B2 (en) * | 1996-09-06 | 1999-01-13 | 静岡日本電気株式会社 | Radio selective call receiver |
| US5918177A (en) * | 1996-11-27 | 1999-06-29 | Telefonaktiebolaget Lm Ericsson (Publ) | System and method of providing a mobile station's service support information to a radio telecommunications network |
| US6134433A (en) * | 1996-12-09 | 2000-10-17 | Telefonaktiebolaget L M Ericsson (Publ) | System and method of forwarding data calls in a radio telecommunications network |
| US5950129A (en) * | 1996-12-09 | 1999-09-07 | Telefonaktiebolaget Lm Ericsson (Publ) | Two-way in-flight radio telecommunication system and method |
| US6078582A (en) | 1996-12-18 | 2000-06-20 | Bell Atlantic Network Services, Inc. | Internet long distance telephone service |
| US6058300A (en) | 1997-02-04 | 2000-05-02 | National Telemanagement Corporation | Prepay telecommunications system |
| US6137869A (en) | 1997-09-16 | 2000-10-24 | Bell Atlantic Network Services, Inc. | Network session management |
| US6574216B1 (en) | 1997-03-11 | 2003-06-03 | Verizon Services Corp. | Packet data network voice call quality monitoring |
| US6870827B1 (en) | 1997-03-19 | 2005-03-22 | Verizon Services Corp. | Voice call alternative routing through PSTN and internet networks |
| US6292479B1 (en) | 1997-03-19 | 2001-09-18 | Bell Atlantic Network Services, Inc. | Transport of caller identification information through diverse communication networks |
| EP0886422A1 (en) * | 1997-06-18 | 1998-12-23 | Alcatel | Telecommunication system and method for reaching a user via two numbers |
| US6138006A (en) * | 1997-09-20 | 2000-10-24 | Telefonaktiebolaget L M Ericsson | System and method of delivering collect calls in a radio telecommunications network |
| US6167250A (en) * | 1997-09-24 | 2000-12-26 | Telefonaktiebolaget Lm Ericsson (Publ) | Network based tariff acquisition system for roaming mobile subscribers |
| US6131024A (en) * | 1997-10-09 | 2000-10-10 | Ericsson Inc. | System and method for setting subscriber-defined usage limits on a mobile terminal |
| US6377982B1 (en) * | 1997-10-14 | 2002-04-23 | Lucent Technologies Inc. | Accounting system in a network |
| US6061341A (en) * | 1997-12-16 | 2000-05-09 | Telefonaktiebolaget Lm Ericsson (Publ) | Use of transmission control protocol proxy within packet data service transmissions in a mobile network |
| US6144723A (en) * | 1998-03-24 | 2000-11-07 | Nortel Networks Corporation | Method and apparatus for providing voice assisted call management in a telecommunications network |
| US6185414B1 (en) * | 1998-07-24 | 2001-02-06 | Telefonaktiebolaget Lm Ericsson (Publ) | Wireless telecommunication system with prepaid architecture |
| US6201957B1 (en) * | 1998-11-18 | 2001-03-13 | Neopoint, Inc. | System and method for implementing flexible calling plans |
| AU3320900A (en) | 1999-03-17 | 2000-10-04 | Star Home Gmbh | System and method for roaming for prepaid mobile telephone service |
| US6408173B1 (en) * | 1999-03-17 | 2002-06-18 | Telefonaktiebolaget L M Ericsson (Publ) | Billing ID correlation for inter-technology roaming |
| GB2350017B (en) * | 1999-05-06 | 2003-05-28 | Ericsson Telefon Ab L M | Tariff determination in mobile telecommunication networks |
| GB2354404B (en) * | 1999-09-18 | 2003-12-03 | Ericsson Telefon Ab L M | Collecting charging data in a telecommunications system |
| IL134741A (en) * | 2000-02-27 | 2003-11-23 | Adamtech Ltd | Mobile transaction system and method |
| US6577867B1 (en) * | 2000-03-31 | 2003-06-10 | Telefonaktiebolaget Lm Ericsson (Publ) | Method for conducting handoff back to anchor communication scenarios |
| FI113726B (en) * | 2000-05-25 | 2004-05-31 | Nokia Corp | Arranging subscriber billing in a telecommunications system |
| US20020042715A1 (en) * | 2000-06-28 | 2002-04-11 | Kelley Robert Richard | Mobile call detail record separation for billing purposes |
| US6700962B1 (en) * | 2000-07-11 | 2004-03-02 | Motorola, Inc. | System and method for creating a call detail record |
| US6751296B1 (en) * | 2000-07-11 | 2004-06-15 | Motorola, Inc. | System and method for creating a transaction usage record |
| WO2002005520A2 (en) * | 2000-07-11 | 2002-01-17 | Motorola Inc. | System and method for creating usage and detail records, and allowing access to a communication node |
| US6711246B1 (en) * | 2000-07-11 | 2004-03-23 | Motorola, Inc. | System and method for creating a page usage record |
| US6725256B1 (en) | 2000-07-11 | 2004-04-20 | Motorola, Inc. | System and method for creating an e-mail usage record |
| US6570969B1 (en) * | 2000-07-11 | 2003-05-27 | Motorola, Inc. | System and method for creating a call usage record |
| JP2002115187A (en) * | 2000-10-12 | 2002-04-19 | Japan Science & Technology Corp | New cellulose raw material and its laminate |
| KR100558988B1 (en) * | 2001-02-28 | 2006-03-10 | 에스케이 텔레콤주식회사 | Multi-party call service method in three generation mobile communication network and charging method thereof |
| GB0112202D0 (en) * | 2001-05-18 | 2001-07-11 | Nokia Corp | Charging in communication networks |
| US7395048B2 (en) * | 2002-12-26 | 2008-07-01 | Motorola, Inc. | Unsolicited wireless content delivery and billing apparatus and method |
| CN1905462B (en) * | 2005-07-27 | 2010-04-07 | 华为技术有限公司 | Charge correlation method and system of application service |
| DE102006014921A1 (en) * | 2006-03-30 | 2007-10-18 | Siemens Ag | Lawful interception method for call forwarding in a packet-oriented telecommunications network |
| CN101094442B (en) * | 2006-08-23 | 2010-08-18 | 中兴通讯股份有限公司 | Method for grappling final call in circuit switching domain |
| US8238538B2 (en) | 2009-05-28 | 2012-08-07 | Comcast Cable Communications, Llc | Stateful home phone service |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| GB9013605D0 (en) * | 1990-06-18 | 1990-08-08 | Stc Plc | Mobile communications |
| US5063591A (en) * | 1990-10-26 | 1991-11-05 | Telefonaktiebolaget L M Ericsson | Toll ticketing record generation for billing of intersystem handoff calls in a mobile telephone system |
| WO1993012606A1 (en) * | 1991-12-12 | 1993-06-24 | Cellular Technical Services Company, Inc. | Real-time information system for cellular telephones |
| US5353331A (en) * | 1992-03-05 | 1994-10-04 | Bell Atlantic Network Services, Inc. | Personal communications service using wireline/wireless integration |
| MX9404062A (en) * | 1993-06-03 | 1995-01-31 | Ericsson Telefon Ab L M | CALL TRANSFER WITHIN THE CELLULAR COMMUNICATIONS SYSTEM. |
-
1995
- 1995-03-24 US US08/409,664 patent/US5796790A/en not_active Expired - Fee Related
-
1996
- 1996-03-01 JP JP8529240A patent/JPH11502684A/en active Pending
- 1996-03-01 AU AU51651/96A patent/AU708913B2/en not_active Ceased
- 1996-03-01 NZ NZ304457A patent/NZ304457A/en unknown
- 1996-03-01 BR BR9607654A patent/BR9607654A/en active Search and Examination
- 1996-03-01 EP EP96908408A patent/EP0815693A1/en not_active Withdrawn
- 1996-03-01 WO PCT/SE1996/000272 patent/WO1996031072A1/en active IP Right Grant
- 1996-03-01 CN CN96193921.4A patent/CN1104158C/en not_active Expired - Fee Related
- 1996-03-01 RU RU97117360A patent/RU2139641C1/en active
- 1996-03-01 CA CA002214568A patent/CA2214568A1/en not_active Abandoned
Also Published As
| Publication number | Publication date |
|---|---|
| BR9607654A (en) | 1998-06-16 |
| RU2139641C1 (en) | 1999-10-10 |
| AU708913B2 (en) | 1999-08-19 |
| EP0815693A1 (en) | 1998-01-07 |
| WO1996031072A1 (en) | 1996-10-03 |
| NZ304457A (en) | 1999-04-29 |
| US5796790A (en) | 1998-08-18 |
| MX9707107A (en) | 1997-11-29 |
| CN1104158C (en) | 2003-03-26 |
| AU5165196A (en) | 1996-10-16 |
| CN1184581A (en) | 1998-06-10 |
| JPH11502684A (en) | 1999-03-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA2214568A1 (en) | Communicating billing identification information for call delivery | |
| EP1262076B1 (en) | Apparatus, method and system for short message service center storage control | |
| US5526400A (en) | System for routing calls to mobile subscribers | |
| US8918076B2 (en) | Regional zone based mobile charging | |
| US5711006A (en) | System and method for addressing a release resource message | |
| US8060087B2 (en) | CDMA intelligent network system and its method, device for realizing international roaming service | |
| CN1247671A (en) | System and method for changing subscriber service features in radio telecommunications network | |
| JP2003533071A (en) | Mobile Application Part (MAP) interface for exchanging short messages with SCP | |
| US6741849B1 (en) | Handling of forwarded calls | |
| US6070080A (en) | Called party availability announcement in a radio telecommunications network | |
| US7224975B2 (en) | Procedure and system for setting up a telecommunication connection | |
| KR20010108926A (en) | Homezone termination trigger service method | |
| US7089010B2 (en) | Method and apparatus for presentation of calling subscriber number in mobile networks | |
| JP4022793B2 (en) | Communication additional service system based on time difference correction time | |
| WO2002005533A1 (en) | Method for creating a call connection between a mobile subscriber and a second telephone subscription in response to a connection creation request made by the mobile subscriber | |
| US6771959B1 (en) | Transmitting call-related data between switching centres | |
| EP1308022B1 (en) | Method for offering a service number call with a predefined price for a subscriber of a mobile terminal | |
| US7903799B1 (en) | Method and apparatus for providing a communications service feature for a communication through a network | |
| WO2002005532A1 (en) | Method for offering a service for creating telephone connections for a subscriber of a mobile terminal | |
| MXPA97007107A (en) | Reliable information of the related idfacturation to send flame | |
| CA2288648A1 (en) | Method and apparatus for roamer port hlr barring | |
| KR20010065410A (en) | Method for called charging for prepaid service subscriber of mobile communication system | |
| CN106993272A (en) | Voice call method and system, attaching position register |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| FZDE | Discontinued |