CN101102550A - Method for guaranteeing consistent CDR of different GPRS supported nodes in multicast service - Google Patents
Method for guaranteeing consistent CDR of different GPRS supported nodes in multicast service Download PDFInfo
- Publication number
- CN101102550A CN101102550A CNA2007101435424A CN200710143542A CN101102550A CN 101102550 A CN101102550 A CN 101102550A CN A2007101435424 A CNA2007101435424 A CN A2007101435424A CN 200710143542 A CN200710143542 A CN 200710143542A CN 101102550 A CN101102550 A CN 101102550A
- Authority
- CN
- China
- Prior art keywords
- ggsn
- sgsn
- mbms
- session
- ticket
- 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.)
- Granted
Links
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The method comprises: when the gateway GPRS supporting node (GGSN) receives the session starting request message of multimedia broadcast multicast service under multicast mode (MBMS), it generates a call-ticket ID of said service, and sends the call-ticket ID to the serving GPRS supporting node SGSN in the downstream node list of said GGSN.
Description
Technical field
The present invention relates to guarantee in a kind of multicast service the method for consistent CDR of different GPRS supported nodes, relate in particular among the mobile communication system broadcasting multicast service MBMS, guarantee in the multicast service mode the conforming method of charging bill between the core net different GPRS support node GSN.
Background technology
In order to effectively utilize mobile network resource, existing mobile communication system has proposed to use the thought of broadcast group broadcast transport service, i.e. multimedia broadcast-multicast service MBMS (MultimediaBroadcast/Multicast Service is hereinafter to be referred as MBMS).MBMS provides the point-to-multipoint service of a data source to a plurality of users send data in the mobile network, realize that Internet resources are shared, raising utilization rate of network resource, the interface resource of especially eating dishes without rice or wine.MBMS provides dual mode: broadcast mode and multicast mode.MBMS can not only realize the classes of messages multicast and the broadcasting of plain text low rate, and can also realize the multicast and the broadcasting of high-speed multimedia business, multimedia broadcast/multicast service MBMS is based on the WCDMA/GSM Packet Based Network, by increasing some new functional entitys, as broadcast multicast service center BM-SC (Broadcast Multicast Service Centre, hereinafter to be referred as BM-SC), to existing packet domain functional entity such as packet service node SGSN (Serving GPRS Support Node, it is the network element that core-network side is responsible for mobile management, hereinafter to be referred as SGSN), packet gateway node GGSN (Gateway GPRS Support Node, it is the network element that core-network side is responsible for being linked into and sending out core net, hereinafter to be referred as GGSN), Radio Access Network RAN and user terminal UE increase the MBMS function, and have defined new logic shared channel and realize that interface-free resources shares.The network architecture of use MBMS as shown in Figure 1 under the mobile communication system.Except BM-SC, all the other all are the carrying network elements of mobile communication system, are used to finish data-transformation facility among the figure.Signaling exchange between GGSN and the BM-SC is carried out in the Gmb reference point, realizes the chain of command of MBMS, comprises following signaling:
-GGSN sets up the bearer context of MBMS and registers at BM-SC;
-GGSN or BM-SC discharge the MBMS bearer context, and GGSN goes registration at BM-SC;
-BM-SC begins and finishes to the GGSN announcement session.
Realize inserting the MBMS business, need a series of step and Signalling exchange, comprise that at least service announcements, user add the access step of broadcasting or multicast group (comprising activation, registration etc.), and the step of leaving (comprising deactivation, cancellation etc.).
In order to finish the processing of MBMS signaling and MBMS business data transmission, existing MBMS mechanism is to existing packet domain core network functional entity SGSN and GGSN, increased the relevant information that MBMS bearer context (MBMS Bearer Context) is used to write down some business.In the MBMS of GGSN, SGSN bearer context, information such as IP multicast address, APN APN (AccessPoint Name), Temporary Mobile Group Identity TMGI (Temporary Mobile Group Identities), MBMS session attribute and descendant node tabulation have been comprised.The foundation of MBMS bearer context is finished by registration message in the multicast service.The address information of the next network node that downlink data will arrive has been enumerated in descendant node tabulation.The descendant node list records of GGSN receive the address information of all SGSN of this business, the descendant node list records of SGSN receive the address information of all base station control stations/radio network controller BSC/RNC (Base Station Controller/Radio NetworkController) of this business.
In order to allow the user receive business datum, when being ready for sending data, BM-SC initiates the MBMS session and begins flow process, as shown in Figure 2.The network carrying resource that is used for transmitting the MBMS data that its requesting activation was necessary, and notify this users interest, data send and are about to begin.Begin flow process by this MBMS session, the MBMS session attribute is as QoS, the MBMS service area, estimate the session duration, the MBMS data transmission time started etc. can offer GGSN and the SGSN that all have registered corresponding MBMS carrying service and all BSC/RNC that link to each other with registered SGSN.Simultaneously, this flow process is all registered GGSN and SGSN, and response session begins the BSC/RNC distribution load plane resource of request message.
The MBMS framework is supported offline charging and online charging, as shown in Figure 3, in off-line mode charges, SGSN, the GGSN network element is gathered metering data, and the detailed single CDR of triggering charging, SGSN produces SGSN MBMS ticket S-MB-CDR (SGSN MBMS Charging Data Record, hereinafter to be referred as SGSN MBMS ticket), GGSN produces GGSN MBMS ticket G-MB-CDR (GGSNMBMS Charging Data Record, hereinafter to be referred as GGSN MBMS ticket) send to charging gateway module (Charging Gateway Function) by the Ga interface protocol, be sent in the charge system (Billing Domain) through the Bp interface again.In addition, the charge information function CDF of SGSN and GGSN can transmit the charging triggering event message by the Rf interface based on Diameter, also can be with the part of CDF function as SGSN or GGSN functions of the equipments.
In the existing MBMS framework, the ticket that produces by the unique definite bearer service in the chain of command IP address of ticket sign ChargingID and GGSN among S-MB-CDR and the G-MB-CDR.Yet, in the prior art, for a certain multicast bear business, GGSN does not pass to SGSN with Charging ID, this makes the SGSN and the S-MB-CDR of GGSN generation and the Charging ID among the G-MB-CDR to be consistent, the ticket that SGSN and GGSN produce can't be mapped, and obviously is irrational.
Summary of the invention
The technical problem to be solved in the present invention provides the method for guaranteeing consistent CDR of different GPRS supported nodes in a kind of mobile communication system multicast service.
In order to address the above problem, the invention provides the method for guaranteeing consistent CDR of different GPRS supported nodes in a kind of multicast service, comprise the steps: that Gateway GPRS Support Node GGSN receives when the session of multimedia broadcast-multicast service MBMS under the multicast pattern begins request message, produce the ticket sign of described business, and described ticket sign being passed to Serving GPRS Support Node SGSN in the downstream node tabulation of described GGSN, described GGSN and SGSN use above-mentioned identical ticket sign in the G-MB-CDR that produces separately and S-MB-CDR ticket.
Further, described method is divided into following steps:
A: when described GGSN receives that the session of multimedia broadcast-multicast service MBMS begins request message, if GGSN does not have effective ticket sign, then GGSN produces the ticket sign, and described ticket sign is stored in the MBMS bearer context of GGSN, SGSN in the downstream node tabulation of described GGSN sends session and begins request, has described ticket sign in the message;
B: after described SGSN receives that session begins message, described GGSN is carried the ticket sign of coming store in the MBMS bearer context of SGSN, and return session to described GGSN and begin response message;
C: at this multicast service, described GGSN and SGSN gather charge information respectively, and will be separately ticket sign in the MBMS bearer context be filled up to respectively in separately the ticket.
Further, in the steps A, the session of described MBMS begins to ask the broadcast multicast service center BM-SC by described MBMS to initiate, and the register requirement of described MBMS is initiated by SGSN.
Further, described ticket is meant GGSN MBMS ticket and SGSN MBMS ticket.
Further, the session of described MBMS begins to ask the broadcast multicast service center BM-SC by described MBMS to initiate.
Further, in the steps A, described GGSN receives that the session of described MBMS begins in the request message, carries the session association attributes, and described GGSN is kept at described session association attributes in the MBMS bearer context of described GGSN.
Further, among the step B, the session that described SGSN receives begins in the message, includes the session attribute association attributes, and described SGSN is stored in described session association attributes in the MBMS bearer context of described SGSN.
Further, in the steps A, when described GGSN received that the session of described MBMS begins request message, described GGSN joined in the descendant node tabulation of described BM-SC by registration process, and described GGSN has created described MBMS bearer context.
Further, described GGSN joins in the descendant node tabulation of described BM-SC by registration process, and described G GSN has created described MBMS bearer context and has comprised the steps: when GGSN receives the register requirement of downstream SGSN node or receives that UE activates request, if GGSN does not have the MBMS bearer context, then GGSN creates the MBMS bearer context, and to BM-SC initiation register flow path, BM-SC joins the GGSN node identification in its descendant node tabulation.
Further, if described GGSN judges that this GGSN has produced the ticket sign and also has been stored in the MBMS bearer context of this GGSN, then described GGSN begins request to described SGSN initiation session separately, carries described ticket sign in the request.
Further, for multicast service, the SGSN in the tabulation of the downstream node of described GGSN joins in the descendant node tabulation of described GGSN by registration process.
Further, described SGSN joins in the descendant node tabulation of described GGSN by registration process, comprise the steps: when SGSN receives the register requirement of downstream BSC/RNC node or receives that UE activates request, if SGSN does not have the MBMS bearer context, then SGSN creates the MBMS bearer context, and to GGSN initiation register flow path, GGSN joins this SGSN node identification in its descendant node tabulation.
The present invention is directed to the MBMS business of multicast pattern, begin to increase in the request message the such charging bill identification information of Charging ID in the GGSN session, the Charging ID that makes GGSN produce can pass to SGSN smoothly, guaranteed that GGSN and SGSN go out charging bill and can be mapped, prevented from error bills and repeat to charge.
Description of drawings
Fig. 1 is a network architecture diagram of using MBMS under the existing mobile communication system;
Fig. 2 is that existing MBMS session begins flow chart;
Fig. 3 is a mobile communication system core net offline charging Organization Chart;
Fig. 4 is that present embodiment MBMS session begins flow chart.
Embodiment
The objective of the invention is to provide the conforming method of charging bill between core network packet-domain SGSN and the GGSN node of guaranteeing in a kind of mobile communication system multicast service, overcoming G-MB-CDR ticket that the GGSN that exists in the prior art and SGSN produce and S-MB-CDR ticket can't corresponding problem, prevents from error bills and repeat to charge.
Because SGSN and GGSN finish in the session process of beginning for the foundation of MBMS bearing resource, SGSN, GGSN just can the MBMS transmission data after bearing resource was set up, therefore SGSN, GGSN should begin to gather metering data information after session begins, and produce the G-MB-CDR ticket.
The present invention is directed to the MBMS business of multicast pattern, begin to increase in the request message the such charging bill identification information of Charging ID in the GGSN session, the Charging ID that makes GGSN produce can pass to SGSN smoothly, has guaranteed that GGSN and SGSN go out the G-MB-CDR ticket and the S-MB-CDR ticket can be mapped.
MBMS session in the present embodiment under the multicast service pattern begins flow process to be initiated by BM-SC, as shown in Figure 4, may further comprise the steps:
Step 401, BM-SC prepares to initiate the MBMS business of certain multicast pattern, begin request (Session StartRequest) so all GGSN in its downstream node tabulation initiate the session of multicast pattern, indicate transfer of data on the horizon, and session attribute is provided.
The tabulation of described downstream node is meant the tabulation that joins the GGSN that BM-SC should business, and for multicast service, GGSN joins in the downstream node tabulation of BM-SC by registration process.
Step 402, GGSN receives that the session of BM-SC begins request (Session Start Request), carry the relevant property parameters of session in the request message, GGSN produces Charging ID, the session attribute parameter of carrying with BM-SC is stored in the MBMS bearer context in the lump, status attribute in the MBMS bearer context is set to " Active ", and returns session to BM-SC and begin response message (Session Start Response).
If GGSN receives that the session that BM-SC sends begins request message, illustrate that GGSN joins in the descendant node tabulation of BM-SC by registration process, and GGSN has created the MBMS bearer context.
The MBMS bearer context of GGSN is created by register flow path, when GGSN receives the register requirement of downstream SGSN node or receives that UE activates request, if GGSN does not have the MBMS bearer context, then GGSN creates the MBMS bearer context, and to BM-SC initiation register flow path, BM-SC joins the GGSN node identification in its descendant node tabulation.
Step 403, GGSN all SGSN in its downstream node tabulation send session and begin request message (Session Start Request), have the Charging ID that GGSN produces in the message.
The tabulation of described downstream node is meant the tabulation that joins the SGSN that GGSN should business, and for multicast service, SGSN joins in the descendant node tabulation of GGSN by registration process.
Step 404, after SGSN receives that session begins request, SGSN store session attribute and ChargingID are in the MBMS bearer context, and the status attribute in the MBMS bearer context is set to " Active ", and return session to GGSN and begin response message (Session Start Response);
The MBMS bearer context of SGSN is created by register flow path, when SGSN receives the register requirement of downstream BSC/RNC node or receives that UE activates request, if SGSN does not have the MBMS bearer context, then SGSN creates the MBMS bearer context, and to GGSN initiation register flow path, GGSN joins this SGSN node identification in its descendant node tabulation.
If GGSN receives the login request message that SGSN sends, GGSN joins this SGSN in the descendant node tabulation of MBMS bearer context, and gives the response of SGSN re-injection volume.This moment, GGSN judged whether the state of MBMS bearer context is activated state (Active), judge promptly whether this GGSN has produced the ticket sign and also be stored in the MBMS bearer context of this GGSN, if the state of the MBMS bearer context of described GGSN is activated state (Active), just this GGSN has produced the ticket sign and has been stored in the MBMS bearer context of this GGSN, then this GGSN begins request to this SGSN initiation session separately, carries charging identifier Charging ID in the request.
When GGSN receives the register requirement of downstream SGSN node or receives that UE activates request, if GGSN does not have the MBMS bearer context, then GGSN creates the MBMS bearer context, and initiates register flow path to BM-SC, and BM-SC joins the GGSN node identification in its descendant node tabulation
Step 405, at this multicast service, the charge information function of GGSN is gathered charge information, and the Charging ID in its MBMS bearer context is filled up among the GGSN MBMS ticket G-MB-CDR, GGSN sends the G-MB-CDR ticket by charging gateway module CGF to charge system Billing Domain.
GGSN and SGSN send to charging gateway module (ChargingGateway Function) by the Ga interface protocol, are sent in the charge system (Billing Domain) through the Bp interface again.In addition, the charge information function CDF of GGSN and SGSN can be by transmitting the charging triggering event message based on the Rf interface of Diameter, also with the part of CDF function as SGSN or GGSN functions of the equipments.
The present invention is directed to the MBMS business of multicast pattern, begin to increase in the message the such charging bill identification information of Charging ID in the GGSN session, the Charging ID that makes GGSN produce can pass to SGSN smoothly, has guaranteed that GGSN and SGSN go out the unification of charging bill.Prevent from error bills and repeat to charge.
The present invention also can have other various embodiments; under the situation that does not deviate from spirit of the present invention and essence thereof; those of ordinary skill in the art are when making various corresponding changes and distortion according to the present invention, and these change and be out of shape the protection range that all should belong to the appended claim of the present invention accordingly.
Claims (12)
1, guarantees the method for consistent CDR of different GPRS supported nodes in a kind of multicast service, comprise the steps:
Gateway GPRS Support Node GGSN receives when the session of multimedia broadcast-multicast service MBMS under the multicast pattern begins request message, produce the ticket sign of described business, and described ticket is identified the Serving GPRS Support Node SGSN in the downstream node tabulation that passes to described GGSN.
2, the method for claim 1 is characterized in that, is further divided into following steps:
A: when described GGSN receives that the session of multimedia broadcast-multicast service MBMS begins request message, if GGSN does not have effective ticket sign, then GGSN produces the ticket sign, and described ticket sign is stored in the MBMS bearer context of GGSN, SGSN in the downstream node tabulation of described GGSN sends session and begins request, has described ticket sign in the message;
B: after described SGSN receives that session begins message, described GGSN is carried the ticket sign of coming store in the MBMS bearer context of SGSN, and return session to described GGSN and begin response message;
C: at this multicast service, described GGSN and SGSN gather charge information respectively, and will be separately ticket sign in the MBMS bearer context be filled up to respectively in separately the ticket.
3, method as claimed in claim 1 or 2 is characterized in that, described ticket is meant GGSNMBMS ticket and SGSN MBMS ticket.
4, method as claimed in claim 1 or 2 is characterized in that, the session of described MBMS begins to ask the broadcast multicast service center BM-SC by described MBMS to initiate.
5, method as claimed in claim 2, it is characterized in that in the steps A, the session of the described MBMS that described GGSN receives begins in the request message, carry the session association attributes, described GGSN is kept at described session association attributes in the MBMS bearer context of described GGSN.
6, method as claimed in claim 5 is characterized in that, among the step B, the session that described SGSN receives begins in the message, includes the session attribute association attributes, and described SGSN is stored in described session association attributes in the MBMS bearer context of described SGSN.
7, method as claimed in claim 4, it is characterized in that, in the steps A, when described GGSN receives that the session of described MBMS begins request message, described GGSN joins in the descendant node tabulation of described BM-SC by registration process, and described GGSN has created described MBMS bearer context.
8, method as claimed in claim 7, it is characterized in that, described GGSN joins in the descendant node tabulation of described BM-SC by registration process, and described GGSN has created described MBMS bearer context and has comprised the steps: when GGSN receives the register requirement of downstream SGSN node or receives that UE activates request, if GGSN does not have the MBMS bearer context, then GGSN creates the MBMS bearer context, and to BM-SC initiation register flow path, BM-SC joins the GGSN node identification in its descendant node tabulation.
9, method as claimed in claim 8, it is characterized in that, if described GGSN judges that this GGSN has produced the ticket sign and also has been stored in the MBMS bearer context of this GGSN, then described GGSN begins request to described SGSN initiation session separately, carries described ticket sign in the request.
10, method as claimed in claim 1 or 2 is characterized in that, for multicast service, the SGSN in the tabulation of the downstream node of described GGSN joins in the descendant node tabulation of described GGSN by registration process.
11, method as claimed in claim 10, it is characterized in that, described SGSN joins in the descendant node tabulation of described GGSN by registration process, comprise the steps: when SGSN receives the register requirement of downstream BSC/RNC node or receives that UE activates request, if SGSN does not have the MBMS bearer context, then SGSN creates the MBMS bearer context, and initiates register flow path to GGSN, and GGSN joins this SGSN node identification in its descendant node tabulation.
12, method as claimed in claim 2 is characterized in that, comprises the steps: further after the step C that described GGSN and SGSN send described ticket separately to charge system respectively, and the ticket identification parameter that carries in the described ticket is identical.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007101435424A CN101102550B (en) | 2007-08-07 | 2007-08-07 | Method for guaranteeing consistent CDR of different GPRS supported nodes in multicast service |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007101435424A CN101102550B (en) | 2007-08-07 | 2007-08-07 | Method for guaranteeing consistent CDR of different GPRS supported nodes in multicast service |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101102550A true CN101102550A (en) | 2008-01-09 |
| CN101102550B CN101102550B (en) | 2011-10-26 |
Family
ID=39036592
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2007101435424A Expired - Fee Related CN101102550B (en) | 2007-08-07 | 2007-08-07 | Method for guaranteeing consistent CDR of different GPRS supported nodes in multicast service |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101102550B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102137369A (en) * | 2010-01-25 | 2011-07-27 | 中国移动通信集团广西有限公司 | Method, device, relevant system and equipment for processing charging ticket |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108521527B (en) * | 2018-03-14 | 2020-12-11 | 北京思特奇信息技术股份有限公司 | Ticket difference detection method, system, computer storage medium and computer equipment |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100346600C (en) * | 2003-11-19 | 2007-10-31 | 华为技术有限公司 | Method of realizing multimeding broadcasting/group broadcasting service business charging |
| CN100373988C (en) * | 2004-09-28 | 2008-03-05 | 华为技术有限公司 | Method for carrying out multicast in mobile communication system |
-
2007
- 2007-08-07 CN CN2007101435424A patent/CN101102550B/en not_active Expired - Fee Related
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102137369A (en) * | 2010-01-25 | 2011-07-27 | 中国移动通信集团广西有限公司 | Method, device, relevant system and equipment for processing charging ticket |
| CN102137369B (en) * | 2010-01-25 | 2014-12-24 | 中国移动通信集团广西有限公司 | Method, device, relevant system and equipment for processing charging ticket |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101102550B (en) | 2011-10-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101883321B (en) | Method and system for acquiring access information and charging in multimedia broadcast multicast service | |
| US20060107287A1 (en) | Multimedia broadcast/multicast service announcement and notification | |
| CN107743714A (en) | To the messaging charging based on business group | |
| CN100502358C (en) | Method for establishing GTP tunnel in multimedia broadcast/multicast service | |
| CN100502570C (en) | Method for terminal in mobile communication system to obtain APN when joining in multicast service group | |
| CN101094457B (en) | Method for establishing data transmission channel on MBMS carrying face based on MBMS gateway | |
| CN103581836A (en) | Method and system for sending group small data | |
| CN100473013C (en) | Method for establishing context in multicast service of mobile communication system | |
| CN102045643B (en) | Resource adjustment method and multi-cell/multicast coordination entity | |
| CN100531137C (en) | Method for establishing control side tunnel in mobile communication system multicast service | |
| CN101094439B (en) | Method and device of assigning resources dynamically for broadcast service in wireless communication system | |
| CN100426886C (en) | Method for realizing stream media service | |
| CN101102549B (en) | Method for guaranteeing consistent billing record of different GPRS supported nodes in multicast service | |
| CN101090327A (en) | Method and system for broadcast/multicase service and supporting IPV4 and IPV6 address at same time | |
| CN101102550B (en) | Method for guaranteeing consistent CDR of different GPRS supported nodes in multicast service | |
| US20160182244A1 (en) | Method and System for Obtaining Content Location Information Enabling Differential Charging Algorithms in Multimedia Broadcast and Multicast Service (MBMS) | |
| CN100477657C (en) | Method for realizing activation of multi-media broadcasting/multicast service | |
| CN101370170A (en) | Wireless resource coordination method | |
| CN100421410C (en) | Method for realizing mobile communication network multimedia enhancement service | |
| CN100518390C (en) | Method for establishing MBMS bearing face data transmission channel based on MBMS conversation | |
| CN101925009B (en) | Method and system for distinguishing MBMS (Multimedia Broadcast Multicast Service) user surface data sending modes during charging | |
| CN100428860C (en) | Multimedia broadcast/multicast service linking method | |
| CN100456732C (en) | Method of realizing multimedia broadcasting group broadcnsting business deactivation | |
| CN101163332B (en) | Method for mobile communication system roaming user to access to multicast service | |
| CN100401800C (en) | Method for providing broadcast multicast service to users |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20111026 Termination date: 20160807 |