CN101335630B

Movatterモバイル変換

Info

Publication number: CN101335630B
Application number: CN2008100949891A
Authority: CN
Inventors: 史欣; 李晓峰; 乔秀全
Original assignee: Huawei Technologies Co Ltd; Beijing University of Posts and Telecommunications
Current assignee: Huawei Technologies Co Ltd; Beijing University of Posts and Telecommunications
Priority date: 2008-04-30
Filing date: 2008-04-30
Publication date: 2011-09-14
Anticipated expiration: 2028-04-30
Also published as: CN101335630A

Abstract

本发明公开了一种计费关联的方法和装置。该计费关联的方法包括：产生会话计费标识；产生内容计费标识；产生承载计费标识；根据所述内容计费标识、会话计费标识和承载计费标识关联内容计费话单、会话计费话单和承载计费话单。该计费关联的装置包括：会话标识模块，用于产生会话计费标识；内容标识模块，用于产生内容计费标识；承载标识模块，用于承载计费标识；关联模块，用于根据所述内容计费标识、会话计费标识和承载计费标识关联内容计费话单、会话计费话单和承载计费话单。通过本发明实施例可以实现各层的计费话单的关联，进而实现精确计费。

The invention discloses a charging association method and device. The charging association method includes: generating a session charging identifier; generating a content charging identifier; generating a bearer charging identifier; associating a content charging bill according to the content charging identifier, the session charging identifier and the bearer charging identifier, Session billing bills and bearer billing bills. The charging association device includes: a session identification module, used to generate a session charging ID; a content identification module, used to generate a content charging ID; a bearer ID module, used to bear a charging ID; an association module, used to The content charging ID, session charging ID, and bearer charging ID are associated with content charging bills, session billing bills, and bearer billing bills. Through the embodiments of the present invention, the association of billing bills of each layer can be realized, thereby realizing accurate billing.

Description

Translated fromChinese

计费关联的方法和装置Method and device for billing association

技术领域technical field

本发明涉及移动通信技术领域，尤其是一种计费关联的方法和装置。The invention relates to the technical field of mobile communication, in particular to a charging association method and device.

背景技术Background technique

目前，第三代移动通信技术(3^rd Generation，以下简称3G)已成为电信网络的发展方向，该技术结合了无线通信技术和国际互联网多媒体通信技术，能够处理图像、音频、视频等多种媒体形式。3G网络采用了水平分层的业务提供体系，自下而上分为：承载层、业务/会话控制层、应用/内容层，不同层次提供的业务涉及到不同的网络资源，因此对于不同层次提供的业务其计费涉及的网络资源也不尽相同。对于只依赖于承载层提供的基础业务，如普通的端到端的通话业务，可视电话等，其计费只涉及到承载层的承载设备；通过业务/会话控制层(包括因特网协议多媒体子系统(Internetprotocol Multimedia Subsystem，以下简称IMS、及其他的数据业务网络系统，如彩铃系统、短信系统等)提供的业务，如彩信、短信等业务，既需要业务/会话控制层的相关网元支持，同时又要借助于承载层相关网元来通信，因此，其计费既涉及到业务/会话层的业务引擎设备，同时也涉及到承载层的承载设备；通过应用/内容层提供的增值业务，如下载歌曲、浏览网页等，其计费既涉及到应用/内容层的服务提供商(ServiceProvide，以下简称SP)设备、内容提供商(Content Provide，以下简称CP)设备，又涉及到业务/会话控制层的业务引擎设备，又涉及到承载层的承载设备。对于运营商来说，不同的网络资源采用的计费策略是不同的，因此，如何将各层的计费关联以实现对一次业务中涉及的各层的网络资源进行精确计费，成为运营商需要考虑的问题。At present, the third generation mobile communication technology (^3rd Generation, hereinafter referred to as 3G) has become the development direction of the telecommunication network. form. The 3G network adopts a horizontally layered service provision system, which is divided into: bearer layer, service/session control layer, and application/content layer from bottom to top. The services provided by different layers involve different network resources. Therefore, the services provided by different layers The network resources involved in the charging of different services are also different. For basic services that only rely on the bearer layer, such as common end-to-end call services, videophones, etc., the billing only involves the bearer equipment at the bearer layer; (Internetprotocol Multimedia Subsystem, hereinafter referred to as IMS, and other data service network systems, such as color ring system, short message system, etc.), such as MMS, short message and other services, require the support of relevant network elements in the service/session control layer, and at the same time It also needs to communicate with the relevant network elements of the bearer layer. Therefore, its billing involves both the service engine equipment at the service/session layer and the bearer equipment at the bearer layer; the value-added services provided through the application/content layer, such as Downloading songs, browsing the web, etc., the billing involves not only the service provider (Service Provider, hereinafter referred to as SP) equipment and content provider (Content Provider, hereinafter referred to as CP) equipment at the application/content layer, but also involves business/session control Layer service engine equipment, and related to bearer layer bearer equipment. For operators, different network resources adopt different charging strategies. Therefore, how to associate the charging of each layer to realize the Accurate billing of the network resources involved in each layer has become a problem that operators need to consider.

3G的标准化工作由第三代移动通信标准化伙伴项目(3^rd GenerationPartnership Project，以下简称3GPP)组织完成，在其发布的R5版本中，3G网络引入IMS叠加在分组域网络上，即将IMS层作为业务/会话控制层。IMS包括呼叫会话控制功能(Call Session Control Function，以下简称CSCF)，在IMS中采用会话发起协议(Session Initiation Protocol，以下简称SIP)作为因特网协议(Internet Protocol，以下简称IP)多媒体会话的信令控制协议。3GPP组织制定了承载层和IMS层(业务/会话控制层)的计费规范，如采用基于业务的本地策略控制(Service-Based Local Policy，以下简称SBLP)机制、基于流的计费(Flow-Based Charging，以下简称FBC)机制或策略和计费控制(Policy and Charging Control，以下简称PCC)机制等来交换IMS层和承载层的计费标识以实现话单的计费关联。在2G/2.5G运营商已经采用增值业务管理平台来负责对SP/CP提供的业务/内容进行计费，在3G时代，这仍是各运营商提供增值业务的方式，但是，现有技术中缺乏针对SP/CP提供的增值业务/内容的计费管理，即缺乏对应用/内容层的计费话单的关联，应用/内容层的增值业务由于不能与其他层面的计费关联，导致计费不精确的问题，如下载不同的歌曲收取的费用相同，可实际上每首歌的内容或占用的网络资源不尽相同，目前的计费方式无法区分这些不同，即无法实现应用/内容层和IMS层(业务/会话控制层)、承载层三者的计费关联，造成计费不够精确。The standardization work of 3G is organized by the^3rd Generation Partnership Project (hereinafter referred to as 3GPP). In the R5 version released by it, the 3G network introduces IMS to be superimposed on the packet domain network, that is, the IMS layer is used as a service /session control layer. The IMS includes a call session control function (Call Session Control Function, hereinafter referred to as CSCF), and the Session Initiation Protocol (hereinafter referred to as SIP) is used in the IMS as the signaling control of the Internet Protocol (Internet Protocol, hereinafter referred to as IP) multimedia session protocol. The 3GPP organization has formulated charging specifications for the bearer layer and the IMS layer (service/session control layer), such as using the Service-Based Local Policy (SBLP) mechanism, Flow-based charging (Flow- Based Charging, hereinafter referred to as FBC) mechanism or Policy and Charging Control (Policy and Charging Control, hereinafter referred to as PCC) mechanism, etc. to exchange the charging identification of the IMS layer and the bearer layer to realize the charging association of the bill. In 2G/2.5G operators have adopted the value-added service management platform to be responsible for charging the service/content provided by SP/CP. In the 3G era, this is still the way for each operator to provide value-added services. However, in the prior art Lack of billing management for value-added services/content provided by SP/CP, that is, lack of association with billing bills at the application/content layer. Value-added services at the application/content layer cannot be associated with billing at other levels, resulting in billing The problem of imprecise fees, such as the same fee for downloading different songs, but in fact the content or network resources occupied by each song are different. The current billing method cannot distinguish these differences, that is, the application/content layer cannot be realized. It is associated with the charging of the IMS layer (service/session control layer) and the bearer layer, resulting in inaccurate charging.

发明内容Contents of the invention

本发明实施例提供一种计费关联的方法和装置，以实现3G网络中各层的计费关联，进而实现精确计费。Embodiments of the present invention provide a charging association method and device, so as to realize the charging association of each layer in the 3G network, and then realize accurate charging.

为此，本发明实施例提供了一种计费关联的方法，包括：To this end, an embodiment of the present invention provides a charging association method, including:

产生用于标识业务/会话控制层的资源使用情况的会话计费标识；Generate a session charging identifier for identifying the resource usage of the service/session control layer;

产生用于标识应用/内容层的资源使用情况的内容计费标识；Generate a content billing identifier for identifying resource usage at the application/content layer;

产生用于标识承载层的资源使用情况的承载计费标识；Generate a bearer charging identifier for identifying the resource usage of the bearer layer;

根据所述内容计费标识、会话计费标识和承载计费标识关联内容计费话单、会话计费话单和承载计费话单，所述内容计费话单用于对应用/内容层进行计费，所述会话计费话单用于对业务/会话控制层进行计费，所述承载计费话单用于对承载层进行计费；According to the content charging ID, the session charging ID and the bearer charging ID, the content charging bill, the session charging bill and the bearer charging bill are associated, and the content charging bill is used for application/content layer performing charging, the session charging bill is used for charging the service/session control layer, and the bearer billing bill is used for charging the bearer layer;

所述根据所述内容计费标识、会话计费标识和承载计费标识关联内容计费话单、会话计费话单和承载计费话单包括：The associating content charging bill, session charging bill and bearer charging bill according to the content charging identifier, session charging identifier and bearer charging identifier includes:

应用/内容层得到业务/会话控制层产生的会话计费标识、承载层产生的承载计费标识，并将所述会话计费标识、承载计费标识及产生的内容计费标识记录在内容计费话单中；The application/content layer obtains the session charging identifier generated by the service/session control layer and the bearer charging identifier generated by the bearer layer, and records the session charging identifier, the bearer charging identifier and the generated content charging identifier in the content accounting in the bill;

业务/会话控制层得到应用/内容层产生的内容计费标识、承载层产生的承载计费标识，并将所述内容计费标识、承载计费标识及产生的会话计费标识记录在会话计费话单中；The service/session control layer obtains the content charging identifier generated by the application/content layer and the bearer charging identifier generated by the bearer layer, and records the content charging identifier, the bearer charging identifier and the generated session charging identifier in the session accounting in the bill;

承载层得到应用/内容层产生的内容计费标识、业务/会话控制层产生的会话计费标识，并将所述内容计费标识、会话计费标识及产生的承载计费标识记录在承载计费话单中。The bearer layer obtains the content charging identifier generated by the application/content layer and the session charging identifier generated by the service/session control layer, and records the content charging identifier, the session charging identifier and the generated bearer charging identifier in the bearer meter in the bill.

本发明实施例提供了一种计费关联的方法，包括：An embodiment of the present invention provides a charging association method, including:

业务/会话控制层得到承载层产生的承载计费标识，并将所述承载计费标识及产生的会话计费标识记录在会话计费话单中；The service/session control layer obtains the bearer charging identifier generated by the bearer layer, and records the bearer charging identifier and the generated session charging identifier in the session charging bill;

承载层产生承载计费标识，并将所述承载计费标识记录在承载计费话单中。The bearer layer generates the bearer charging identifier, and records the bearer charging identifier in the bearer charging bill.

应用/内容层产生内容计费标识，并将所述内容计费标识记录在内容计费话单中；The application/content layer generates the content charging identifier, and records the content charging identifier in the content charging bill;

业务/会话控制层得到应用/内容层产生的内容计费标识，并将所述内容计费标识及产生的会话计费标识记录在会话计费话单中；The service/session control layer obtains the content charging identification generated by the application/content layer, and records the content charging identification and the generated session charging identification in the session charging bill;

应用/内容层获取内容计费标识，并将所述内容计费标识记录在内容计费话单中；The application/content layer obtains the content charging identifier, and records the content charging identifier in the content charging bill;

业务/会话控制层获取会话计费标识，并将所述会话计费标识记录在会话计费话单中；The service/session control layer obtains the session charging identifier, and records the session charging identifier in the session charging bill;

承载层获取承载计费标识，并将所述承载计费标识记录在承载计费话单中；The bearer layer obtains the bearer charging identifier, and records the bearer charging identifier in the bearer charging bill;

所述内容计费标识、会话计费标识、承载计费标识已预先匹配有计费策略；The content charging ID, session charging ID, and bearer charging ID have been pre-matched with charging policies;

所述会话计费标识为多个，所述会话计费话单为一个，不同的会话计费标识记录在所述会话计费话单的不同的媒体资源协商项中；There are multiple session charging identifiers, one session charging bill, and different session charging identifiers are recorded in different media resource negotiation items of the session charging bill;

所述承载计费标识为多个，所述承载计费话单为一个，不同的承载计费标识记录在所述承载计费话单的不同的业务数据项中。There are multiple bearer charging IDs, and one bearer charging bill, and different bearer charging IDs are recorded in different service data items in the bearer billing bill.

本发明实施例提供了一种计费关联的装置，包括：An embodiment of the present invention provides a billing association device, including:

会话标识模块，用于产生标识业务/会话控制层的资源使用情况的会话计费标识；The session identification module is used to generate a session charging identification for identifying the resource usage of the service/session control layer;

内容标识模块，用于产生标识应用/内容层的资源使用情况的内容计费标识；A content identification module, configured to generate a content charging identification for identifying the resource usage of the application/content layer;

承载标识模块，用于产生标识承载层的资源使用情况的承载计费标识；A bearer identification module, configured to generate a bearer charging identification for identifying the resource usage of the bearer layer;

关联模块，用于根据所述内容计费标识、会话计费标识和承载计费标识关联内容计费话单、会话计费话单和承载计费话单，所述内容计费话单用于对应用/内容层进行计费，所述会话计费话单用于对业务/会话控制层进行计费，所述承载计费话单用于对承载层进行计费；An associating module, configured to associate content charging bills, session charging bills, and bearer billing bills according to the content charging identifier, session charging identifier, and bearer charging identifier, and the content charging bill is used for Charging the application/content layer, the session charging bill is used for charging the service/session control layer, and the bearer billing bill is used for charging the bearer layer;

所述关联模块包括：The associated modules include:

内容子模块，用于将所述会话计费标识、承载计费标识、内容计费标识记录在内容计费话单中；The content sub-module is used to record the session charging identifier, the bearer charging identifier, and the content charging identifier in the content charging bill;

会话子模块，用于将所述内容计费标识、承载计费标识、会话计费标识记录在会话计费话单中；The session sub-module is used to record the content charging identifier, the bearer charging identifier, and the session charging identifier in the session charging bill;

承载子模块，用于将所述内容计费标识、会话计费标识、承载计费标识记录在承载计费话单中；The bearer submodule is used to record the content charging identifier, session charging identifier, and bearer charging identifier in the bearer charging bill;

或者，or,

所述关联模块包括：The associated modules include:

会话子模块，用于将所述承载计费标识、会话计费标识记录在会话计费话单中；The session sub-module is used to record the bearer charging identifier and the session charging identifier in the session charging bill;

承载子模块，用于将所述承载计费标识记录在承载计费话单中；The bearer submodule is configured to record the bearer charging identifier in the bearer bill;

或者，or,

所述关联模块包括：The associated modules include:

内容子模块，用于将所述内容计费标识记录在内容计费话单中；A content submodule, configured to record the content charging identifier in the content charging bill;

会话子模块，用于将所述内容计费标识、会话计费标识记录在会话计费话单中；The session sub-module is used to record the content charging identifier and the session charging identifier in the session charging bill;

承载子模块，用于将所述内容计费标识、会话计费标识、承载计费标识记录在承载计费话单中。The bearer submodule is configured to record the content charging identifier, session charging identifier, and bearer charging identifier in the bearer charging bill.

本发明实施例通过产生各层的计费标识，由这些计费标识实现各层的计费话单的关联，进而实现精确计费。In the embodiment of the present invention, charging identifications of each layer are generated, and the charging records of each layer are associated by these charging identifications, thereby realizing accurate charging.

附图说明Description of drawings

图1为本发明计费关联的方法实施例一流程图；FIG. 1 is a flow chart of Embodiment 1 of the charging association method of the present invention;

图2为本发明计费关联的方法实施例中分层体系结构示意图；FIG. 2 is a schematic diagram of a layered architecture in an embodiment of a charging association method in the present invention;

图3为本发明计费关联的方法实施例二流程图；FIG. 3 is a flow chart of Embodiment 2 of the charging association method of the present invention;

图4为本发明计费关联的方法实施例二话单关联示意图；Fig. 4 is a schematic diagram of bill association in the second embodiment of the method of billing association in the present invention;

图5为本发明计费关联的方法实施例三流程图；FIG. 5 is a flow chart of Embodiment 3 of the billing association method of the present invention;

图6为本发明计费关联的方法实施例三话单关联示意图；Fig. 6 is a schematic diagram of bill association in the third embodiment of the billing association method of the present invention;

图7为本发明计费关联的方法实施例四流程图；FIG. 7 is a flow chart of Embodiment 4 of the billing association method of the present invention;

图8为本发明计费关联的方法实施例四话单关联示意图；FIG. 8 is a schematic diagram of bill association in Embodiment 4 of the billing association method of the present invention;

图9为本发明计费关联的方法实施例五流程图；FIG. 9 is a flow chart of Embodiment 5 of the billing association method of the present invention;

图10为本发明计费关联的方法实施例六流程图；FIG. 10 is a flow chart of Embodiment 6 of the billing association method of the present invention;

图11为本发明计费关联的方法实施例五、六部署计费策略的配置示意图；FIG. 11 is a schematic configuration diagram of deploying a charging policy in Embodiments 5 and 6 of the charging association method of the present invention;

图12为本发明计费关联的方法实施例五、六话单关联示意图；Fig. 12 is a schematic diagram of bill association in Embodiments 5 and 6 of the charging association method of the present invention;

图13为本发明计费关联的装置实施例结构示意图。Fig. 13 is a schematic structural diagram of an embodiment of a charging association device according to the present invention.

具体实施方式Detailed ways

下面通过附图和实施例，对本发明的技术方案做进一步的详细描述。The technical solutions of the present invention will be described in further detail below with reference to the accompanying drawings and embodiments.

图1为本发明计费关联的方法实施例一流程图，并参照图2所示的分层计费体系结构示意图，该实施例包括：Fig. 1 is a flow chart of the first embodiment of the charging association method of the present invention, and referring to the hierarchical charging architecture schematic diagram shown in Fig. 2, this embodiment includes:

步骤11：产生会话计费标识，所述会话计费标识用于标识业务/会话控制层的资源使用情况。参见图2，在业务/会话控制层面，主要包括了IMS子系统的各种主要网元，如服务呼叫状态控制功能(Service Call SessionControl Function，以下简称，S-CSCF)、查询呼叫状态控制功能(Interrogating Call Session Control Function，以下简称I-CSCF)、代理呼叫状态控制功能(Proxy Call Session Control Function，以下简称P-CSCF)、IMS网关功能(IMS Gateway Function，以下简称IMS-GWF)等，负责对IMS会话、IMS用户进行管理。其中，S-CSCF主要负责IMS会话的控制，S-CSCF通过IMS-GWF和在线计费系统OCS联系，可以实现会话/业务控制层面实时计费；S-CSCF通过和离线计费系统OFCS联系，可以实现会话/业务控制层面的离线计费。Step 11: Generate a session charging identifier, the session charging identifier is used to identify the resource usage of the service/session control layer. Referring to Figure 2, at the service/session control level, it mainly includes various main network elements of the IMS subsystem, such as the service call state control function (Service Call Session Control Function, hereinafter referred to as S-CSCF), query call state control function ( Interrogating Call Session Control Function, hereinafter referred to as I-CSCF), proxy call state control function (Proxy Call Session Control Function, hereinafter referred to as P-CSCF), IMS Gateway Function (IMS Gateway Function, hereinafter referred to as IMS-GWF), etc. Manage IMS sessions and IMS users. Among them, the S-CSCF is mainly responsible for the control of the IMS session. The S-CSCF communicates with the online charging system OCS through the IMS-GWF to realize real-time charging at the session/service control level; the S-CSCF communicates with the offline charging system OFCS. Offline charging at the session/service control level can be realized.

步骤12：产生内容计费标识，所述内容计费标识用于标识应用/内容层的资源使用情况。参见图2，在应用/内容层，主要包括第三方SIP应用服务器、SIP应用接入网关和增值业务管理平台，第三方SIP应用服务器(SP/CP)用于提供SIP增值业务(应用/内容)，SIP应用接入网关负责内容计费的事件触发，增值业务管理平台负责进行业务鉴权、用户鉴权和业务定购关系检查，并通过和计费系统交互，实现业务/内容批价。增值业务管理平台负责判断业务使用者的用户类型，如果是预付费用户，则增值业务管理平台和在线计费系统(Online Charging System，以下简称OCS)联系；如果是后付费用户，则增值业务管理平台和离线计费系统(OfflineCharging System，以下简称OFCS)联系。Step 12: Generate a content charging ID, which is used to identify resource usage at the application/content layer. Referring to Figure 2, the application/content layer mainly includes a third-party SIP application server, a SIP application access gateway and a value-added service management platform, and a third-party SIP application server (SP/CP) is used to provide SIP value-added services (application/content) , the SIP application access gateway is responsible for event triggering of content charging, and the value-added service management platform is responsible for service authentication, user authentication and service order relationship check, and realizes service/content approval by interacting with the billing system. The value-added service management platform is responsible for judging the user type of the service user. If it is a prepaid user, the value-added service management platform will contact the online charging system (Online Charging System, hereinafter referred to as OCS); if it is a post-paid user, the value-added service management The platform contacts the Offline Charging System (OFCS for short).

步骤13：产生承载计费标识，所述承载计费标识用于标识承载层的资源使用情况。参见图2，承载层面，主要包括了无线接入网(Radio Access)和分组域核心网。终端(UE)通过无线接入网接入该网络；分组域核心网主要包括了通用无线分组业务(General Packet Radio Service，以下简称GPRS)服务支持节点(Serving GPRS Supporting Node，以下简称SGSN)和GPRS网关支持节点(Gateway GPRS Supporting Node，以下简称GGSN)，SGSN和GGSN通过计费网关(Charging Gateway，以下简称CG)与离线计费系统(OFCS)联系，GGSN和在线计费系统(OCS)直接联系，负责完成分组域的实时在线计费。Step 13: Generate a bearer charging identifier, where the bearer charging identifier is used to identify the resource usage of the bearer layer. Referring to Figure 2, the bearer layer mainly includes a radio access network (Radio Access) and a packet domain core network. The terminal (UE) accesses the network through the wireless access network; the packet domain core network mainly includes the general packet radio service (General Packet Radio Service, hereinafter referred to as GPRS) serving support node (Serving GPRS Supporting Node, hereinafter referred to as SGSN) and GPRS Gateway GPRS Supporting Node (Gateway GPRS Supporting Node, hereinafter referred to as GGSN), SGSN and GGSN communicate with Offline Charging System (OFCS) through Charging Gateway (Charging Gateway, hereinafter referred to as CG), and GGSN directly communicates with Online Charging System (OCS) , responsible for completing the real-time online charging of the packet domain.

步骤14：根据所述内容计费标识、会话计费标识和承载计费标识将内容计费话单、会话计费话单和承载计费话单进行关联，内容计费话单为应用/内容层的计费话单，会话计费话单为业务/会话控制层的计费话单，承载计费话单为承载层的计费话单。参见表1，运营商可以将一次会话中涉及的各个层面的计费话单准确的关联，然后根据该会话所对应的各层的计费策略对计费话单进行批价，从而精确的计算出用户本次使用的业务费用，避免了计费的重复性。Step 14: According to the content charging ID, session charging ID and bearer charging ID, associate the content charging bill, the session charging bill and the bearer billing bill, and the content billing bill is application/content layer, the session billing bill is the billing bill of the service/session control layer, and the bearer billing bill is the billing bill of the bearer layer. Referring to Table 1, the operator can accurately associate the billing bills of all levels involved in a session, and then evaluate the billing bills according to the charging policies of each layer corresponding to the session, so as to accurately calculate The service fee for the user's current use is calculated to avoid duplication of billing.

表1Table 1

本实施例通过为应用/内容层、业务/会话控制层和承载层设置相应的内容计费标识、会话计费标识和承载计费标识，实现各层的计费话单关联，能够使运营商根据不同的市场营销模式，在不同层面采用不同的计费策略，从而支持不同的计费策略。In this embodiment, by setting corresponding content charging identifiers, session charging identifiers, and bearer charging identifiers for the application/content layer, service/session control layer, and bearer layer, the charging bill association of each layer can be realized, which can enable the operator to According to different marketing models, different billing strategies are adopted at different levels to support different billing strategies.

其中，步骤14中的各层计费话单关联的具体实现可采用如下方式：Wherein, the specific realization of the association of billing bills of each layer instep 14 can adopt the following methods:

(1)各层的计费话单中记录有这三层的计费标识，具体包括：(1) The billing IDs of these three layers are recorded in the billing bills of each layer, including:

(2)上层计费话单中记录有该层及其下层的计费标识，具体包括：(2) The charging identification of this layer and its lower layer is recorded in the billing bill of the upper layer, specifically including:

上述两种方法可适用于3GPP R5规范，该规范中承载层通过策略决策功能(PDF)实体和业务/会话控制层之间进行信息交互，因此，上述的计费标识通过PDF进行传输。具体可参见下面的图3、5所示的实施例。The above two methods can be applied to the 3GPP R5 specification. In this specification, the bearer layer performs information interaction between the policy decision function (PDF) entity and the service/session control layer. Therefore, the above-mentioned charging identifier is transmitted through PDF. For details, reference may be made to the embodiments shown in FIGS. 3 and 5 below.

(3)下层话单中记录有该层及其上层的计费标识，具体包括：(3) The billing identifiers of this layer and its upper layer are recorded in the bill of the lower layer, specifically including:

(4)各层的计费话单中记录各层的计费标识，具体包括：(4) The charging identification of each layer is recorded in the billing bill of each layer, specifically including:

所述内容计费标识、会话计费标识、承载计费标识已预先匹配有计费策略。The content charging ID, session charging ID, and bearer charging ID are pre-matched with charging policies.

上述方法(3)、(4)可适用于3GPP R5之后的规范，3GPP R5之后的规范中承载层通过策略和计费规则功能(PCRF)实体和业务/会话控制层之间进行信息交互，因此，上述的计费标识通过PCRF进行传输。具体可参见图7、10所示的实施例。The above methods (3) and (4) can be applied to specifications after 3GPP R5. In the specifications after 3GPP R5, the bearer layer performs information exchange between the policy and charging rule function (PCRF) entity and the service/session control layer, so , the above charging identifier is transmitted through the PCRF. For details, refer to the embodiments shown in FIGS. 7 and 10 .

上述的方法中，前三种不需要预先对各层进行计费策略的配置，各层第一个接收到内容请求的网元产生计费标识，用于关联各网络资源，计费系统对具有相同计费标识的资源进行统一计费，实现精确计费，同时，利用计费标识将各层的计费话单关联，避免重复计费。第四种方法需要预先在各层配置计费策略，各层接收到内容请求后，根据请求获取相应的计费标识，使计费系统实现精确计费。Among the above methods, the first three methods do not need to pre-configure charging policies for each layer. The first network element in each layer that receives a content request generates a charging identifier for associating each network resource. The resources with the same billing ID are billed uniformly to achieve accurate billing. At the same time, the billing records of each layer are associated by using the billing ID to avoid repeated billing. The fourth method needs to pre-configure billing policies at each layer. After each layer receives a content request, it obtains the corresponding billing ID according to the request, so that the billing system can realize accurate billing.

应用上述方法的具体流程可参见以下的实施例：The specific process of applying the above method can refer to the following examples:

图3为本发明计费关联方法实施例二流程图，该实施例包括：FIG. 3 is a flow chart of Embodiment 2 of the billing association method of the present invention, which embodiment includes:

步骤301：终端发送内容请求给承载层网元，如GGSN，用于发起一个SIP消息以建立承载信道。Step 301: The terminal sends a content request to a bearer layer network element, such as a GGSN, for initiating a SIP message to establish a bearer channel.

步骤302：GGSN将该内容请求发送到业务/会话控制层的IMS域。Step 302: GGSN sends the content request to the IMS domain of the service/session control layer.

步骤303：第一个收到该内容请求的业务/会话控制层网元，如P-CSCF，负责产生业务/会话控制层面的会话计费标识(ICID)，用来关联IMS域的相关网元产生的话单。并将该会话计费标识ICID插入到SIP消息的ChargingVector头域中。Step 303: The first service/session control layer network element that receives the content request, such as P-CSCF, is responsible for generating a session charging identifier (ICID) at the service/session control layer, which is used to associate with relevant network elements in the IMS domain Generate bills. And insert the session charging identifier ICID into the ChargingVector header field of the SIP message.

步骤304：SIP信令携带着ICID在IMS域中传输，并通过SIP应用接入网关传递到应用/内容层。这样，应用/内容层就拥有了业务/会话控制层的计费标识(ICID)，在生成内容计费话单时，便可将ICID记录在内容计费话单中。Step 304: The SIP signaling carries the ICID and is transmitted in the IMS domain, and delivered to the application/content layer through the SIP application access gateway. In this way, the application/content layer has the charging identification (ICID) of the service/session control layer, and the ICID can be recorded in the content charging bill when generating the bill for content billing.

步骤305：SIP应用接入网关将添加有ICID的业务鉴权/计费请求发送给内容子模块，如增值业务管理平台(VASMP)。Step 305: The SIP application access gateway sends the service authentication/charging request added with the ICID to the content sub-module, such as a value-added service management platform (VASMP).

步骤306：如果业务鉴权/计费成功，增值业务管理平台(VASMP)负责产生应用/内容层面的内容计费标识(CCID)，CCID作为应用/内容层话单的主标识，唯一地标识针对一次应用或者一个内容的使用记录。因此，不同的内容(内容请求)，对应不同的内容计费标识，不同的内容计费标识记录在不同的内容计费话单中，即内容与内容计费话单是一一对应的，有几个内容请求，应用/内容层便会生成几个内容计费话单。此处CCID是由增值业务管理平台产生的，可替代的是，SIP应用接入网关也可以用来产生CCID，如在步骤305中SIP接入网关产生CCID，并通过业务鉴权/计费请求将该CCID发送给增值业务管理平台。Step 306: If the service authentication/billing is successful, the value-added service management platform (VASMP) is responsible for generating the content charging identifier (CCID) of the application/content layer, and the CCID is used as the main identifier of the application/content layer bill, uniquely identifying A usage record of an application or a content. Therefore, different contents (content requests) correspond to different content billing identifiers, and different content billing identifiers are recorded in different content billing bills, that is, there is a one-to-one correspondence between content and content billing bills. For several content requests, the application/content layer will generate several content billing records. Here, the CCID is generated by the value-added service management platform. Alternatively, the SIP application access gateway can also be used to generate the CCID. For example, in step 305, the SIP access gateway generates the CCID and passes the service authentication/billing request Send the CCID to the value-added service management platform.

步骤307：如果业务鉴权/计费成功，则增值业务管理平台(VASMP)在给SIP应用接入网关的业务鉴权/计费响应消息中携带CCID，将CCID传给SIP应用接入网关。Step 307: If the service authentication/charging is successful, the value-added service management platform (VASMP) carries the CCID in the service authentication/charging response message to the SIP application access gateway, and transmits the CCID to the SIP application access gateway.

步骤308：SIP应用接入网关将应用/内容层的内容计费标识(CCID)插入到SIP消息的ChargingVector头域中，根据目标地址对SIP消息进行路由，转发携带有ICID和CCID的内容请求给SIP应用服务器。Step 308: The SIP application access gateway inserts the content charging identifier (CCID) of the application/content layer into the ChargingVector header field of the SIP message, routes the SIP message according to the destination address, and forwards the content request carrying the ICID and CCID to the SIP application server.

步骤309：SIP应用服务器根据业务逻辑进行处理，并返回相应的SIP响应消息(业务响应)。Step 309: the SIP application server processes according to the business logic, and returns a corresponding SIP response message (service response).

步骤310：SIP应用接入网关转发该携带有CCID和ICID的SIP消息(业务响应)给IMS域的P-CSCF。携带有ICID和CCID的业务响应在IMS域上传送，从而会话涉及到的IMS相关网元都能够同时获得CCID和ICID。由于在一次会话中，IMS域只需采用唯一的计费标识ICID来关联一次业务实例在该层面所有网元所产生的计费话单，对于一次业务会话过程中涉及到的不同内容对会话层资源的使用，在IMS域的话单中具体通过媒体资源协商项(List of SDP MediaComponents，以下简称SDP项)来逐个记录。因此，在生成会话计费话单时，针对同一会话中的不同内容，会话子模块将同一会话涉及的同一ICID记录在同一会话计费话单中，将不同内容涉及的CCID记录在该同一会话计费话单的不同SDP项中，即对应同一会话中的不同的内容，业务/会话层不像应用/内容层那样生成多个计费话单，而只是生成一个会话计费话单，该会话计费话单中记录着一个ICID，该会话计费话单的不同SDP项中对应记录着对应于不同内容的CCID。Step 310: The SIP application access gateway forwards the SIP message (service response) carrying the CCID and ICID to the P-CSCF in the IMS domain. The service response carrying the ICID and CCID is transmitted on the IMS domain, so that all IMS-related network elements involved in the session can obtain the CCID and ICID at the same time. Because in a session, the IMS domain only needs to use the unique charging identifier ICID to correlate the billing bills generated by all network elements of a service instance at this level. The use of resources is recorded one by one in the IMS domain call list through the media resource negotiation item (List of SDP Media Components, hereinafter referred to as SDP item). Therefore, when generating a session charging bill, for different contents in the same session, the session submodule records the same ICID involved in the same session in the same session billing bill, and records the CCIDs involved in different contents in the same session In the different SDP items of the billing bill, that is, corresponding to different contents in the same session, the business/session layer does not generate multiple billing bills like the application/content layer, but only generates one billing bill for the session. An ICID is recorded in the session charging bill, and CCIDs corresponding to different contents are correspondingly recorded in different SDP items of the session billing bill.

步骤311：P-CSCF在收到返回的业务响应后，通过SBLP机制，将CCID和ICID以及媒体资源协商(SDP)信息通过业务授权消息发送给策略决策功能(Policy Decision Function，以下简称PDF)，PDF是IMS中的一个功能实体，业务/会话控制层将协商后的承载信息通过PDF来控制承载层的承载信道的建立。在3GPP的R5版本中，采用了基于业务的本地策略控制(SBLP)机制实现了IMS业务/会话控制层和承载层之间的承载和计费控制。Step 311: After receiving the returned service response, the P-CSCF sends the CCID, ICID and media resource negotiation (SDP) information to the Policy Decision Function (Policy Decision Function, hereinafter referred to as PDF) through the service authorization message through the SBLP mechanism, The PDF is a functional entity in the IMS, and the service/session control layer uses the negotiated bearer information to control the establishment of the bearer channel of the bearer layer through the PDF. In the R5 version of 3GPP, the service-based local policy control (SBLP) mechanism is adopted to realize the bearing and charging control between the IMS service/session control layer and the bearer layer.

步骤312：同时，P-CSCF在收到返回的业务响应后，向终端返回业务响应的SIP消息。由于终端不产生话单，因此CCID、ICID无需传递给终端(UE)。Step 312: At the same time, after receiving the returned service response, the P-CSCF returns the SIP message of the service response to the terminal. Since the terminal does not generate bills, the CCID and ICID do not need to be passed to the terminal (UE).

步骤313：终端(UE)根据会话协商结果向GGSN发起承载建立请求，以通过建立的承载信道传输媒体流。Step 313: The terminal (UE) initiates a bearer establishment request to the GGSN according to the session negotiation result, so as to transmit the media stream through the established bearer channel.

步骤314：GGSN向PDF发起承载授权请求。Step 314: The GGSN initiates a bearer authorization request to the PDF.

步骤315：PDF在授权响应消息中将CCID和ICID传递给GGSN。这样GGSN就获得了其它两层的计费标识(CCID和ICID)，在生成承载计费话单时，GGSN将应用/内容层的计费标识CCID和业务/会话控制层的计费标识ICID记录到承载计费话单中。Step 315: The PDF transmits the CCID and ICID to the GGSN in the authorization response message. In this way, the GGSN has obtained the charging identification (CCID and ICID) of the other two layers. When generating the bearer charging bill, the GGSN will record the charging identification CCID of the application/content layer and the charging identification ICID of the service/session control layer. to the bearer billing bill.

步骤316：GGSN在获得承载授权后，通过创建分组数据协议上下文(Packet Data Protocol Context，以下简称PDP上下文)来传输媒体流，并为每一个PDF上下文产生针对该业务的承载层的承载计费标识(如GCID)。在3GPP发布的R5版本中，GGSN不支持区分具体的业务流，每个应用/内容的使用在承载层面都需要激活一个新的PDP上下文，因此，采用唯一的计费标识(如GPRS网络中的GCID)来标识一次业务实例在该承载层面对资源的使用情况。那么，像应用/内容层一样，对于不同的内容，承载层产生不同GCID，对应不同的GCID，承载层产生不同的承载计费话单，即有几个内容请求便会有几个承载计费话单。对于同一会话中的不同内容，参见图4，将根据第一内容请求产生的第一CCID、第一GCID及同一ICID记录在第一承载计费话单中，将根据第二内容请求产生的第二CCID、第二GCID及同一ICID记录在第二承载计费话单中，将根据第三内容请求产生的第三CCID、第三GCID及同一ICID记录在第三承载计费话单中。Step 316: After obtaining the bearer authorization, the GGSN creates a packet data protocol context (Packet Data Protocol Context, hereinafter referred to as the PDP context) to transmit the media stream, and generates a bearer charging identifier for the bearer layer of the service for each PDF context (such as GCID). In the R5 version released by 3GPP, the GGSN does not support distinguishing specific service flows. The use of each application/content needs to activate a new PDP context at the bearer level. Therefore, a unique charging identifier (such as the GCID) to identify the resource usage of a service instance at the bearer level. Then, like the application/content layer, for different content, the bearer layer generates different GCIDs, corresponding to different GCIDs, the bearer layer generates different bearer billing bills, that is, there are several content requests and there will be several bearer billing bill. For different contents in the same session, referring to Fig. 4, the first CCID, the first GCID and the same ICID generated according to the first content request are recorded in the first bearer charging bill, and the first CCID generated according to the second content request The second CCID, the second GCID and the same ICID are recorded in the second bearer billing bill, and the third CCID, the third GCID and the same ICID generated according to the third content request are recorded in the third bearer billing bill.

步骤317：GGSN在授权通知消息添加该GCID，并发送给策略决策功能(PDF)。Step 317: The GGSN adds the GCID to the authorization notification message and sends it to the Policy Decision Function (PDF).

步骤318：PDF向P-CSCF传递承载层的计费标识(GCID)。P-CSCF在获得承载层的计费标识(GCID)之后，将其插入到SIP消息的ChargingVector头域中并进行传输。因此携带应用/内容层的计费标识CCID、业务/会话控制层的计费标识ICID和承载层的计费标识GCID的SIP消息将在IMS域中传输。这样，IMS域的相关网元就获得了其它两层的计费标识(CCID、GCID)，并在生成该层的计费话单的时候插入其它两层的计费标识，参见图4，对于同一会话中不同内容产生的会话计费话单，由于是同一会话因此只产生一个会话计费话单，其中记录有一个ICID，由于是不同的内容因此会对应产生多个GCID和CCID，像记录CCID一样，GCID也要被记录在SDP项中，即对应不同的内容将与内容对应的CCID和GCID记录在不同的SDP项中，如根据第一内容产生的第一CCID和第一GCID记录在第一SDP项中，根据第二内容产生的第二CCID和第二GCID记录在第二SDP项中，根据第三内容产生的第三CCID和第三GCID记录在第三SDP项中。同时，携带应用/内容层的计费标识CCID、业务/会话控制层的计费标识ICID和承载层的计费标识GCID的SIP消息随着SIP信令的交互传输到SIP应用接入网关。Step 318: The PDF transfers the charging identifier (GCID) of the bearer layer to the P-CSCF. After obtaining the charging identifier (GCID) of the bearer layer, the P-CSCF inserts it into the ChargingVector header field of the SIP message and transmits it. Therefore, the SIP message carrying the CCID of the application/content layer, the ICID of the service/session control layer, and the GCID of the bearer layer will be transmitted in the IMS domain. In this way, the relevant network elements in the IMS domain have just obtained the charging identifiers (CCID, GCID) of the other two layers, and insert the charging identifiers of the other two layers when generating the charging bill of this layer, see Figure 4, for The session billing bill generated by different content in the same session, because it is the same session, only one session billing bill is generated, and one ICID is recorded in it, and multiple GCIDs and CCIDs are correspondingly generated because of different content, like records Like the CCID, the GCID should also be recorded in the SDP item, that is, the CCID and GCID corresponding to the content will be recorded in different SDP items corresponding to different contents, such as the first CCID and the first GCID generated according to the first content are recorded in In the first SDP item, the second CCID and the second GCID generated according to the second content are recorded in the second SDP item, and the third CCID and the third GCID generated according to the third content are recorded in the third SDP item. At the same time, the SIP message carrying the CCID of the application/content layer, the ICID of the service/session control layer, and the GCID of the bearer layer is transmitted to the SIP application access gateway along with the interaction of SIP signaling.

步骤319-321：当用户结束使用业务或内容时，SIP应用接入网关将向增值业务管理平台发起计费确认的请求，并将承载层的计费标识(如GCID)发送给增值业务管理平台。这样，应用/内容层面就获得了其它两层的计费标识(GCID、ICID)，增值业务管理平台在生成话单的时候就插入其它两层的计费标识，对于同一会话中的不同内容，参见图4，将根据第一内容请求产生的第一CCID和第一GCID及同一的ICID记录在第一内容计费话单中，将根据第二内容请求产生的第二CCID和第二GCID及同一的ICID记录在第二内容计费话单中，将根据第三内容请求产生的第三CCID和第三GCID及同一的ICID记录在第三内容计费话单中。Steps 319-321: When the user finishes using the service or content, the SIP application access gateway will initiate a request for charging confirmation to the value-added service management platform, and send the charging identifier (such as GCID) of the bearer layer to the value-added service management platform . In this way, the application/content layer obtains the charging identifiers (GCID, ICID) of the other two layers, and the value-added service management platform inserts the charging identifiers of the other two layers when generating the bill. For different contents in the same session, Referring to Fig. 4, the first CCID and the first GCID and the same ICID generated according to the first content request are recorded in the first content billing bill, and the second CCID generated according to the second content request and the second GCID and The same ICID is recorded in the second content billing record, and the third CCID and third GCID generated according to the third content request and the same ICID are recorded in the third content billing bill.

上述流程将每层的计费标识传递到其它各层，使得每个层面的话单中都有其它两层话单的计费标识，最终实现三层的计费话单关联。具体来讲，IMS域的P-CSCF通过策略决策功能(PDF)将应用/内容层的计费标识CCID和业务/会话控制层的计费标识ICID传递给承载层的充当策略执行功能(Policy Enforcement Function，以下简称PEF)的GGSN，GGSN在回复消息中将承载层的计费标识GCID传递给业务/会话控制层和应用/内容层。The above process transmits the billing identifier of each layer to other layers, so that the bills of each layer have the billing identifiers of the bills of the other two layers, and finally realize the association of billing bills of the three layers. Specifically, the P-CSCF in the IMS domain transfers the CCID of the application/content layer and the ICID of the service/session control layer to the policy enforcement function (Policy Enforcement) of the bearer layer through the policy decision function (PDF). Function, hereinafter referred to as the GGSN of the PEF), the GGSN transmits the charging identifier GCID of the bearer layer to the service/session control layer and the application/content layer in the reply message.

上述流程示出了一次IMS会话过程中使用一个内容的情况，对于一次会话中涉及多个内容的情况，在应用/内容层，针对每个内容的使用形成一个独立的话单，用唯一的计费标识CCID来标记，即对应于第二内容请求产生第二内容计费标识；在业务/会话控制层的IMS域，对于一次会话过程中使用到多个内容的情况，由于是在一次会话中，所以只有一个会话计费话单，记录有该层的计费标识ICID，由于是多个内容，在该话单中利用SDP项(List of SDP Media Components项)来逐个记录，每个SDP项中对应记录承载计费标识和内容计费标识，即对应第一内容请求，第一SDP项记录第一CCID和第一GCID，第二SDP项记录第二CCID和第二GCID；在承载层面，由于GGSN无法区分具体的业务流，因此，每个应用/内容都需要创建新的PDP上下文来进行承载，由唯一GCID来进行标识，即对应第一内容请求，该层的计费标识为第一GCID、对应第二内容请求，该层的计费标识为第二GCID。即对于同一会话的不同内容，参见图4，会话子模块产生同一个ICID，承载子模块和内容子模块产生不同的GCID和CCID，相应的会话层只产生一个会话计费话单，承载层和应用/内容层产生多个承载计费话单和内容计费话单，不同内容对应的CCID和GCID记录在同一个会话计费话单中的不同的SDP项中，不同内容对应的不同CCID和不同GCID及同一ICID记录在不同的内容计费话单和不同的承载计费话单中。除了上述计费标识及记录上述标识的计费话单的不同，针对不同内容请求的流程是一致的。The above process shows the case of using one content during one IMS session. For the case of multiple content involved in one session, at the application/content layer, an independent bill is formed for the use of each content, and a unique billing Identifies the CCID to mark, that is, generates the second content charging identifier corresponding to the second content request; in the IMS domain of the service/session control layer, for the situation that multiple contents are used during one session, since it is in one session, Therefore, there is only one session billing bill, and the billing identifier ICID of this layer is recorded. Since there are multiple contents, the SDP item (List of SDP Media Components item) is used in the bill to record one by one. In each SDP item Correspondingly record the bearer charging ID and content charging ID, that is, corresponding to the first content request, the first SDP item records the first CCID and the first GCID, and the second SDP item records the second CCID and the second GCID; at the bearer level, due to GGSN cannot distinguish specific service flows. Therefore, each application/content needs to create a new PDP context for carrying, which is identified by a unique GCID, that is, corresponding to the first content request, the charging identifier of this layer is the first GCID , corresponding to the second content request, the charging ID of this layer is the second GCID. That is, for different contents of the same session, see Figure 4, the session submodule generates the same ICID, the bearer submodule and the content submodule generate different GCIDs and CCIDs, and the corresponding session layer only generates one session billing bill, the bearer layer and the content submodule generate different GCIDs and CCIDs. The application/content layer generates multiple bearer billing bills and content billing bills. CCIDs and GCIDs corresponding to different contents are recorded in different SDP items in the same session billing bill. Different CCIDs and GCIDs corresponding to different contents Different GCIDs and the same ICID are recorded in different content billing records and different bearer billing records. Except for the differences in the above-mentioned billing identifiers and the billing bills that record the above-mentioned identifiers, the processes for requesting different content are the same.

本实施例使得每个层面的计费话单都有其他层面的计费标识，可以清晰地知道一次业务使用过程中涉及了几层计费，通过任意一层的话单都可以快速的找到其他层面相关联的话单，便于进行各种统计分析和计费关联。This embodiment makes the billing bills of each level have billing identifiers of other levels, so that it can be clearly known how many layers of billing are involved in a service use process, and other levels can be quickly found through the bills of any level The related bills are convenient for various statistical analysis and billing association.

图5为本发明计费关联的方法实施例三流程图，该实施例包括：FIG. 5 is a flow chart of Embodiment 3 of the charging association method of the present invention. This embodiment includes:

步骤501：终端发送内容请求给承载子模块，如GGSN，用于发起一个SIP消息以建立承载信道。Step 501: The terminal sends a content request to the bearer submodule, such as GGSN, for initiating a SIP message to establish a bearer channel.

步骤502：GGSN将该内容请求发送到业务/会话控制层的IMS域。Step 502: GGSN sends the content request to the IMS domain of the service/session control layer.

步骤503：第一个收到该内容请求的业务/会话控制层网元，如P-CSCF，负责产生业务/会话控制层面的会话计费标识(ICID)，用来关联IMS域的相关网元产生的话单。并将该会话计费标识ICID插入到SIP消息的ChargingVector头域中。Step 503: The first service/session control layer network element that receives the content request, such as P-CSCF, is responsible for generating a session charging identifier (ICID) at the service/session control layer, which is used to associate with relevant network elements in the IMS domain Generate bills. And insert the session charging identifier ICID into the ChargingVector header field of the SIP message.

步骤504：SIP信令携带着ICID在IMS域中传输，并通过SIP应用接入网关传递到应用/内容层。这样，应用/内容层就拥有了业务/会话控制层的计费标识(ICID)，在生成内容计费话单时，便可将ICID记录在内容计费话单中。Step 504: The SIP signaling carries the ICID and is transmitted in the IMS domain, and is delivered to the application/content layer through the SIP application access gateway. In this way, the application/content layer has the charging identification (ICID) of the service/session control layer, and the ICID can be recorded in the content charging bill when generating the bill for content billing.

步骤505：SIP应用接入网关将添加有ICID的业务鉴权/计费请求发送给内容子模块，如增值业务管理平台(VASMP)。Step 505: The SIP application access gateway sends the service authentication/charging request added with the ICID to the content sub-module, such as a value-added service management platform (VASMP).

步骤506：如果业务鉴权/计费成功，增值业务管理平台(VASMP)负责产生应用/内容层面的内容计费标识(CCID)，CCID作为应用/内容层话单的主标识，唯一地标识针对一次应用或者一个内容的使用记录。因此，不同的内容(内容请求)，对应不同的内容计费标识，不同的内容计费标识记录在不同的内容计费话单中，即内容与内容计费话单是一一对应的，有几个内容请求，应用/内容层便会生成几个内容计费话单。此处CCID是由增值业务管理平台产生的，可替代的是，SIP应用接入网关也可以用来产生CCID，如在步骤505中SIP接入网关产生CCID，并通过业务鉴权/计费请求将该CCID发送给增值业务管理平台。Step 506: If the service authentication/billing is successful, the value-added service management platform (VASMP) is responsible for generating the content charging identifier (CCID) of the application/content layer, and the CCID is used as the main identifier of the application/content layer bill to uniquely identify A usage record of an application or a content. Therefore, different contents (content requests) correspond to different content billing identifiers, and different content billing identifiers are recorded in different content billing bills, that is, there is a one-to-one correspondence between content and content billing bills. For several content requests, the application/content layer will generate several content billing records. Here, the CCID is generated by the value-added service management platform. Alternatively, the SIP application access gateway can also be used to generate the CCID. For example, instep 505, the SIP access gateway generates the CCID and passes the service authentication/billing request Send the CCID to the value-added service management platform.

步骤507：如果业务鉴权/计费成功，则增值业务管理平台(VASMP)向SIP应用接入网关发送业务鉴权/计费响应消息，该业务鉴权/计费响应消息中没有携带CCID。Step 507: If the service authentication/charging is successful, the value-added service management platform (VASMP) sends a service authentication/charging response message to the SIP application access gateway, and the service authentication/charging response message does not carry CCID.

步骤508：SIP应用接入网关根据目标地址对SIP消息(内容请求)进行路由，转发该内容请求给SIP应用服务器。Step 508: The SIP application access gateway routes the SIP message (content request) according to the target address, and forwards the content request to the SIP application server.

步骤509：SIP应用服务器根据业务逻辑进行处理，并返回相应的SIP响应消息(业务响应)。Step 509: The SIP application server processes according to the business logic, and returns a corresponding SIP response message (service response).

步骤510：SIP应用接入网关转发该业务响应给P-CSCF，该业务响应中携带有ICID。携带有ICID的业务响应在IMS域上传送，从而会话涉及到的IMS相关网元都能够获得ICID。由于在一次会话中，IMS域只需采用唯一的计费标识ICID来关联一次业务实例在该层面所有网元所产生的计费话单。Step 510: The SIP application access gateway forwards the service response to the P-CSCF, and the service response carries the ICID. The service response carrying the ICID is transmitted on the IMS domain, so that all IMS-related network elements involved in the session can obtain the ICID. Because in a session, the IMS domain only needs to use the unique charging identifier ICID to correlate the charging bills generated by all network elements of a service instance at this level.

步骤511：P-CSCF在收到返回的业务响应后，向PDF发送业务授权消息。Step 511: After receiving the returned service response, the P-CSCF sends a service authorization message to the PDF.

步骤512：同时，P-CSCF在收到返回的业务响应后，向终端返回该业务响应。Step 512: At the same time, after receiving the returned service response, the P-CSCF returns the service response to the terminal.

步骤513：终端(UE)根据会话协商结果向承载层网元，如GGSN，发起承载建立请求，以通过建立的承载信道传输媒体流。Step 513: The terminal (UE) initiates a bearer establishment request to the bearer layer network element, such as the GGSN, according to the session negotiation result, so as to transmit the media stream through the established bearer channel.

步骤514：GGSN向PDF发起承载授权请求。Step 514: The GGSN initiates a bearer authorization request to the PDF.

步骤515：PDF向GGSN发送对应的授权响应消息。Step 515: the PDF sends a corresponding authorization response message to the GGSN.

步骤516：GGSN在获得承载授权后，通过PDP上下文来传输媒体流，并为每一个PDF上下文产生针对该业务的承载层的承载计费标识(GCID)。在3GPP发布的R5版本中，GGSN不支持区分具体的业务流，每个应用/内容的使用在承载层面都需要激活一个新的PDP上下文，因此，采用唯一的计费标识(如GPRS网络中的GCID)来标识一次业务实例在该承载层面对资源的使用情况。那么，像应用/内容层一样，对于不同的内容，承载层产生不同GCID，对应不同的GCID，承载层产生不同的承载计费话单，即有几个内容请求便会有几个承载计费话单。对于同一会话中的不同内容，参见图6，将根据第一内容请求产生的第一GCID记录在第一承载计费话单中，将根据第二内容请求产生的第二GCID记录在第二承载计费话单中，将根据第三内容请求产生的第三GCID记录在第三承载计费话单中。Step 516: After obtaining the bearer authorization, the GGSN transmits the media stream through the PDP context, and generates a bearer charging identifier (GCID) for the bearer layer of the service for each PDF context. In the R5 version released by 3GPP, the GGSN does not support distinguishing specific service flows. The use of each application/content needs to activate a new PDP context at the bearer level. Therefore, a unique charging identifier (such as the GCID) to identify the resource usage of a service instance at the bearer level. Then, like the application/content layer, for different content, the bearer layer generates different GCIDs, corresponding to different GCIDs, the bearer layer generates different bearer billing bills, that is, there are several content requests and there will be several bearer billing bill. For different content in the same session, see Figure 6, record the first GCID generated according to the first content request in the first bearer billing bill, and record the second GCID generated according to the second content request in the second bearer In the billing bill, record the third GCID generated according to the third content request in the third bearer billing bill.

步骤517：GGSN在授权通知消息添加该GCID，并发送给策略决策功能(PDF)。Step 517: The GGSN adds the GCID to the authorization notification message and sends it to the Policy Decision Function (PDF).

步骤518：PDF向P-CSCF传递承载层的计费标识(GCID)。P-CSCF在获得承载层的计费标识(GCID)之后，将其插入到SIP消息的ChargingVector头域中并进行传输。因此携带业务/会话控制层的计费标识ICID和承载层的计费标识GCID的SIP消息将在IMS域中传输。这样，IMS域的相关网元就获得了承载层的计费标识(GCID)，并在生成该层的计费话单的时候插入承载层的计费标识，参见图6，对于同一会话中不同内容产生的会话计费话单，由于是同一会话因此只产生一个会话计费话单，其中记录有一个ICID，由于是不同的内容因此会对应产生多个GCID，对于一次业务会话过程中涉及到的不同内容对会话层资源的使用，在IMS域的话单中具体通过SDP项来逐个记录，即在生成会话计费话单时，针对同一会话中的不同内容，会话子模块将同一会话涉及的同一ICID记录在同一会话计费话单中，将不同内容涉及的GCID记录在该同一会话计费话单的不同SDP项中，即对应同一会话中的不同的内容，业务/会话层不像应用/内容层那样生成多个计费话单，而只是生成一个会话计费话单，该会话计费话单中记录着一个ICID，该会话计费话单的不同SDP项中对应记录着对应于不同内容的GCID，如根据第一内容产生的第一GCID记录在第一SDP项中，根据第二内容产生的第二GCID记录在第二SDP项中，根据第三内容产生的第三GCID记录在第三SDP项中。同时，携带承载层的计费标识GCID的SIP消息随着SIP信令的交互传输到SIP应用接入网关。Step 518: The PDF transfers the charging identifier (GCID) of the bearer layer to the P-CSCF. After obtaining the charging identifier (GCID) of the bearer layer, the P-CSCF inserts it into the ChargingVector header field of the SIP message and transmits it. Therefore, the SIP message carrying the ICID of the service/session control layer and the GCID of the bearer layer will be transmitted in the IMS domain. In this way, the relevant network elements in the IMS domain obtain the charging identifier (GCID) of the bearer layer, and insert the charging identifier (GCID) of the bearer layer when generating the charging bill of this layer, as shown in Figure 6. For different The session billing bill generated by the content, because it is the same session, only one session billing bill is generated, and one ICID is recorded in it, and multiple GCIDs will be generated correspondingly because of different content. The use of session layer resources by different content of different content is recorded one by one in the IMS domain bill through SDP items, that is, when generating a session charging bill, for different content in the same session, the session sub-module The same ICID is recorded in the same session billing record, and the GCID involved in different content is recorded in different SDP items of the same session billing record, that is, corresponding to different contents in the same session. The service/session layer is not like the application / content layer to generate multiple billing bills, but only generate a session billing bill, the session billing bill records an ICID, and the different SDP items of the session billing bill correspondingly record the corresponding GCIDs of different contents, for example, the first GCID generated based on the first content is recorded in the first SDP item, the second GCID generated based on the second content is recorded in the second SDP item, and the third GCID generated based on the third content is recorded In the third SDP item. At the same time, the SIP message carrying the charging identifier GCID of the bearer layer is transmitted to the SIP application access gateway along with the interaction of the SIP signaling.

步骤519-521：当用户结束使用业务或内容时，SIP应用接入网关将向增值业务管理平台发起计费确认的请求，并将承载层的计费标识(GCID)发送给增值业务管理平台。这样，应用/内容层面就获得了其它两层的计费标识(GCID、ICID)，增值业务管理平台在生成话单的时候就插入其它两层的计费标识，对于同一会话中的不同内容，参见图6，将根据第一内容请求产生的第一CCID和第一GCID及同一的ICID记录在第一内容计费话单中，将根据第二内容请求产生的第二CCID和第二GCID及同一的ICID记录在第二内容计费话单中，将根据第三内容请求产生的第三CCID和第三GCID及同一的ICID记录在第三内容计费话单中。Steps 519-521: When the user finishes using the service or content, the SIP application access gateway will initiate a charging confirmation request to the value-added service management platform, and send the charging identification (GCID) of the bearer layer to the value-added service management platform. In this way, the application/content layer obtains the charging identifiers (GCID, ICID) of the other two layers, and the value-added service management platform inserts the charging identifiers of the other two layers when generating the bill. For different contents in the same session, Referring to Fig. 6, the first CCID and the first GCID and the same ICID generated according to the first content request are recorded in the first content billing bill, and the second CCID generated according to the second content request and the second GCID and The same ICID is recorded in the second content billing record, and the third CCID and third GCID generated according to the third content request and the same ICID are recorded in the third content billing bill.

计费系统在收到应用/内容层、业务/会话控制层和承载层传来的话单后，就可以根据话单中包含的计费标识将同一次业务实例在各个层面所产生的话单关联起来。其中：After the billing system receives bills from the application/content layer, business/session control layer, and bearer layer, it can associate the bills generated by the same service instance at all levels according to the billing identifier contained in the bills . in:

应用/内容层话单中表示计费标识的项如下：The items representing the billing identifier in the application/content layer CDR are as follows:

CCID：用来唯一标识应用/内容层针对一次应用或者一个内容的使用。CCID: used to uniquely identify the use of an application or content at the application/content layer.

ICID：IMS域为一次会话产生的计费标识ID。ICID: The charging ID generated by the IMS domain for a session.

GCID：承载网络中GGSN为GPRS PDP上下文产生的计费标识。GCID: The charging identifier generated by the GGSN in the bearer network for the GPRS PDP context.

业务/会话话单中表示计费标识的项如下：The items representing the charging ID in the service/session bill are as follows:

GCID：承载网络中GGSN为GPRS PDP上下文产生的计费标识，具体包含在话单的SDP Media Component中的Access Correlation ID字段中。GCID: The charging identifier generated by the GGSN in the bearer network for the GPRS PDP context, which is specifically included in the Access Correlation ID field in the SDP Media Component of the bill.

承载层话单中表示计费标识的项如下：The items representing the billing ID in the bearer layer CDR are as follows:

上述流程示出了一次IMS会话过程中使用一个内容的情况，对于一次会话中涉及多个内容的情况，在应用/内容层，针对每个内容的使用形成一个独立的话单，用唯一的计费标识CCID来标记，即对应于第二内容请求产生第二内容计费标识；在业务/会话控制层的IMS域，对于一次会话过程中使用到多个内容的情况，由于是在一次会话中，所以只有一个会话计费话单，记录有该层的计费标识ICID，由于是多个内容，在该话单中利用SDP项(List of SDP Media Components项)来逐个记录，每个SDP项中对应记录承载计费标识，即对应第一内容请求，第一SDP项记录第一GCID，第二SDP项记录第二GCID；在承载层面，由于GGSN无法区分具体的业务流，因此，每个应用/内容都需要创建新的PDP上下文来进行承载，由唯一GCID来进行标识，即对应第一内容请求，该层的计费标识为第一GCID、对应第二内容请求，该层的计费标识为第二GCID。即对于同一会话的不同内容，参见图6，会话子模块产生同一个ICID，承载子模块和内容子模块产生不同的GCID和CCID，相应的会话层只产生一个会话计费话单，承载层和应用/内容层产生多个承载计费话单和内容计费话单，不同内容对应的GCID记录在同一个会话计费话单中的不同的SDP项中，不同内容对应的不同CCID和不同GCID及同一ICID记录在不同的内容计费话单中，不同内容对应的不同GCID记录在不同的承载计费话单中。除了上述计费标识及记录上述标识的计费话单的不同，针对不同内容请求的流程是一致的。The above process shows the case of using one content during one IMS session. For the case of multiple content involved in one session, at the application/content layer, an independent bill is formed for the use of each content, and a unique billing Identifies the CCID to mark, that is, generates the second content charging identifier corresponding to the second content request; in the IMS domain of the service/session control layer, for the situation that multiple contents are used during one session, since it is in one session, Therefore, there is only one session billing bill, and the billing identifier ICID of this layer is recorded. Since there are multiple contents, the SDP item (List of SDP Media Components item) is used in the bill to record one by one. In each SDP item Correspondingly record the bearer charging ID, that is, corresponding to the first content request, the first SDP item records the first GCID, and the second SDP item records the second GCID; at the bearer level, since the GGSN cannot distinguish specific service flows, each application /Content needs to create a new PDP context to bear, and is identified by a unique GCID, that is, corresponding to the first content request, the billing identifier of this layer is the first GCID, corresponding to the second content request, and the billing identifier of this layer is the second GCID. That is, for different contents of the same session, see Figure 6, the session sub-module generates the same ICID, the bearer sub-module and the content sub-module generate different GCIDs and CCIDs, and the corresponding session layer only generates one session billing bill, and the bearer layer and the content sub-module generate different GCIDs and CCIDs. The application/content layer generates multiple bearer billing bills and content billing bills. The GCIDs corresponding to different contents are recorded in different SDP items in the same session billing bill. Different CCIDs and different GCIDs correspond to different contents and the same ICID are recorded in different content billing records, and different GCIDs corresponding to different contents are recorded in different bearer billing records. Except for the differences in the above-mentioned billing identifiers and the billing bills that record the above-mentioned identifiers, the processes for requesting different content are the same.

图3所示的实施例一，由于要实现层间的计费标识的相互传递，流程相对比较复杂；同时，因为需要下传应用/内容层面的计费标识CCID，除了需要在现有的基于业务的本地策略SBLP的基础上，对现有的接口进行扩展，在接口消息中扩充记录应用/内容层面的计费标识CCID的字段外，还需要对IMS域和GGSN所产生的话单进行扩展，添加记录应用/内容层面的计费标识CCID的字段。因此，实施例一需要对3GPP的规范做一些扩展，对系统的影响比较大。而本实施例使得上层的计费话单都有其下所有层面的计费标识，通过上层的话单就可以快速的找到其他层面相关联的话单，关联过程清晰易实现，基本不用修改现有的接口协议和话单；另外，由于只需要实现层间的计费标识的单向传递，流程相对比较简单，实施起来对系统的影响不大。In the first embodiment shown in Figure 3, the process is relatively complicated due to the mutual transfer of charging identifiers between layers; at the same time, because the charging identifier CCID at the application/content level needs to be downloaded, in addition to the existing On the basis of the local policy SBLP of the service, the existing interface is extended. In addition to expanding the field for recording the charging identifier CCID at the application/content level in the interface message, it is also necessary to expand the bills generated by the IMS domain and GGSN. Add a field for recording the CCID at the application/content level. Therefore, Embodiment 1 needs to make some extensions to the 3GPP specifications, which has a relatively large impact on the system. However, in this embodiment, the billing bills of the upper layer have the billing identifiers of all the lower layers, and the bills associated with other layers can be quickly found through the bills of the upper layer. The association process is clear and easy to implement, and there is basically no need to modify the existing Interface protocol and bill; In addition, because only one-way transfer of billing identification between layers is required, the process is relatively simple, and the implementation has little impact on the system.

图7为本发明计费关联的方法实施例四流程图，该实施例包括：Fig. 7 is a flow chart of Embodiment 4 of the charging association method of the present invention, this embodiment includes:

步骤701：终端发送承载建立请求给承载层网元，如GGSN。Step 701: The terminal sends a bearer establishment request to a bearer layer network element, such as a GGSN.

步骤702：GGSN通过创建PDP上下文来传输媒体流，并为每一个PDF上下文产生针对该业务的承载层的承载计费标识(GCID)。在R5之后的版本中，在承载层引入区分不同业务流的技术后，GCID已经不能用来唯一标识一个应用/内容在承载层的话单。由于GGSN支持区分具体的业务流，多个应用/内容的使用在承载层面可以共享一个PDP上下文，不需要再激活一个新的PDP上下文。在支持FBC/PCC的GGSN的增强型话单eG-CDR中，有一个话单项为业务数据表(List of Service Data)，专门用来记录每个业务流的详细情况，主要包括针对该业务流的批价组(Rating Group)、计费规则库名称(Charging Rule Base Name)、使用的时间(Time Usage)、上行流量(Data Volume Uplink)、下行流量(Data Volume Downlink)、应用功能记录信息(AF-Record-Information)等，其中，应用功能记录信息(AF-Record-Information)项可以具体包含从应用功能传过来的计费标识，如应用/内容层的CCID和业务/会话控制层的ICID。Step 702: The GGSN transmits the media stream by creating a PDP context, and generates a bearer charging identifier (GCID) for the bearer layer of the service for each PDF context. In versions after R5, after introducing the technology for distinguishing different service flows at the bearer layer, GCID can no longer be used to uniquely identify an application/content in the bearer layer. Since the GGSN supports the distinction of specific service flows, multiple applications/contents can share a PDP context at the bearer level without activating a new PDP context. In the enhanced bill eG-CDR of GGSN that supports FBC/PCC, there is a bill item called List of Service Data, which is specially used to record the details of each service flow, mainly including Rating Group (Rating Group), Charging Rule Base Name (Charging Rule Base Name), Time Usage (Time Usage), Uplink Traffic (Data Volume Uplink), Downlink Traffic (Data Volume Downlink), Application Function Record Information ( AF-Record-Information), etc., wherein the item of application function record information (AF-Record-Information) can specifically include the charging identifier transmitted from the application function, such as the CCID of the application/content layer and the ICID of the service/session control layer .

步骤703：终端发送内容请求给GGSN，用于发起一个SIP消息以建立承载信道。Step 703: the terminal sends a content request to the GGSN for initiating a SIP message to establish a bearer channel.

步骤704：GGSN将该内容请求发送到业务/会话控制层的IMS域。Step 704: GGSN sends the content request to the IMS domain of the service/session control layer.

步骤705：第一个收到该内容请求的业务/会话控制层网元，如P-CSCF，负责产生业务/会话控制层面的会话计费标识(ICID)，用来关联IMS域的相关网元产生的话单。并将该会话计费标识ICID插入到SIP消息的ChargingVector头域中。Step 705: The first service/session control layer network element that receives the content request, such as P-CSCF, is responsible for generating a session charging identifier (ICID) at the service/session control layer, which is used to associate with relevant network elements in the IMS domain Generate bills. And insert the session charging identifier ICID into the ChargingVector header field of the SIP message.

步骤706：SIP信令携带着ICID在IMS域中传输，关联IMS域的相关网元。Step 706: The SIP signaling carries the ICID and is transmitted in the IMS domain, and associated with relevant network elements in the IMS domain.

步骤707：SIP应用接入网关在向增值业务管理平台发送业务鉴权/计费请求。Step 707: The SIP application access gateway is sending a service authentication/charging request to the value-added service management platform.

步骤708：如果业务鉴权/计费成功，内容子模块，如，增值业务管理平台(VASMP)负责产生应用/内容层面的内容计费标识(CCID)，CCID作为应用/内容层话单的主标识，唯一地标识针对一次应用或者一个内容的使用记录。此处CCID是由增值业务管理平台产生的，可替代的是，SIP应用接入网关也可以用来产生CCID，如在步骤705中SIP接入网关产生CCID，并通过业务鉴权/计费请求将该CCID发送给增值业务管理平台。参见图8，对于同一会话中不同内容，在生成内容计费话单时，由于不同的内容对应不同的CCID，进而对应不同的内容计费话单，如将根据第一内容请求生成的第一CCID记录在第一内容计费话单中，将根据第二内容请求生成的第二CCID记录在第二内容计费话单中，将根据第三内容请求生成的第三CCID记录在第三内容计费话单中。Step 708: If the service authentication/billing is successful, the content sub-module, such as the value-added service management platform (VASMP) is responsible for generating the content charging identifier (CCID) at the application/content level, and the CCID is used as the main bill of the application/content layer ID, which uniquely identifies a usage record for an application or a content. Here, the CCID is generated by the value-added service management platform. Alternatively, the SIP application access gateway can also be used to generate the CCID. For example, instep 705, the SIP access gateway generates the CCID and passes the service authentication/billing request Send the CCID to the value-added service management platform. Referring to Fig. 8, for different contents in the same session, when generating content billing bills, since different contents correspond to different CCIDs, and thus correspond to different content billing bills, for example, the first content bill generated according to the first content request The CCID is recorded in the first content billing record, the second CCID generated according to the second content request is recorded in the second content billing record, and the third CCID generated according to the third content request is recorded in the third content billing record. Billing call list.

步骤709：如果业务鉴权/计费成功，则增值业务管理平台(VASMP)在给SIP应用接入网关的业务鉴权/计费响应消息中携带CCID，将CCID传给SIP应用接入网关。Step 709: If the service authentication/charging is successful, the value-added service management platform (VASMP) carries the CCID in the service authentication/charging response message to the SIP application access gateway, and transmits the CCID to the SIP application access gateway.

步骤710：SIP应用接入网关根据目标地址对SIP消息进行路由，将内容请求转发给给SIP应用服务器。Step 710: The SIP application access gateway routes the SIP message according to the target address, and forwards the content request to the SIP application server.

步骤711：SIP应用服务器根据业务逻辑进行处理，并返回相应的SIP响应消息(业务响应)。Step 711: The SIP application server processes according to the service logic, and returns a corresponding SIP response message (service response).

步骤712：SIP应用接入网关将ICID、CCID添加进业务响应中，并转发该携带有CCID和ICID的业务响应给IMS域的会话子模块(P-CSCF)。携带有ICID和CCID的业务响应在IMS域上传送，从而业务涉及到的IMS相关网元都能够同时获得CCID和ICID。由于在一次会话中，IMS域只需采用唯一的计费标识ICID来关联一次业务实例在该层面所有网元所产生的计费话单，对于一次业务会话过程中涉及到的不同内容对会话层资源的使用，在IMS域的话单中具体通过SDP项来逐个记录。因此，在生成会话计费话单时，会话子模块将ICID记录在会话计费话单中，将CCID记录在会话计费话单的SDP项中。参见图8，对于同一会话中不同的内容，在生成会话计费话单时，由于是同一会话因此产生一个ICID，对应产生一个会话计费话单，由于多个内容，将根据多个内容产生的不同的CCID记录在会话计费话单的不同SDP项中，如将根据第一内容产生的第一CCID记录在第一SDP项中，将根据第二内容产生的第二CCID记录在第二SDP项中，将根据第三内容产生的第三CCID记录在第三SDP项中。Step 712: The SIP application access gateway adds the ICID and CCID to the service response, and forwards the service response carrying the CCID and ICID to the session submodule (P-CSCF) of the IMS domain. The service response carrying the ICID and CCID is transmitted on the IMS domain, so that all IMS-related network elements involved in the service can obtain the CCID and ICID at the same time. Because in a session, the IMS domain only needs to use the unique charging identifier ICID to correlate the billing bills generated by all network elements of a service instance at this level. The use of resources is recorded one by one through SDP items in the IMS domain bill. Therefore, when generating the session bill, the session submodule records the ICID in the session bill, and records the CCID in the SDP item of the session bill. Referring to Figure 8, for different contents in the same session, when generating a session charging bill, because it is the same session, an ICID is generated, and a session billing bill is generated correspondingly. Due to multiple contents, it will be generated according to multiple contents Different CCIDs are recorded in different SDP items of the session charging bill. For example, the first CCID generated according to the first content is recorded in the first SDP item, and the second CCID generated according to the second content is recorded in the second SDP item. In the SDP item, the third CCID generated according to the third content is recorded in the third SDP item.

步骤713：P-CSCF在收到返回的业务响应后，通过PCC机制，将CCID和ICID以及媒体资源协商(SDP)信息通过PCC规则创建请求发送给策略和计费规则功能(Policy Charging Rule Function，以下简称PCRF)。PCRF是IMS中的一个功能实体，业务/会话控制层将协商后的承载信息通过PCRF来控制承载层的承载信道的建立。在图3和图5所示的实施例中是针对3GPP的R5版本，采用了基于业务的本地策略控制(SBLP)机制实现了IMS业务/会话控制层和承载层之间的承载和计费控制，而3GPP R5及之前版本的计费方式在承载层面主要是针对PDP上下文的计费，随着IMS规范和市场需求的发展，其局限性主要表现为：R5计费方式无法区别不同的IP Flow，计费方式不适用于其它接入方式(WLAN、xDSL、Cable.....)；支持二次PDP上下文的终端数量有限，二次PDPContext占用手机终端的处理和存储资源，并缩短电池寿命；另外，PDPContext的激活和去激活，会大量增加GPRS/UMTS系统中的信令开销，并增加了业务建立的时延。因此，3GPP R6中，在承载层引入了能够区分业务流的基于流的计费(Flow Based Charging，以下简称FBC)机制，一个PDP上下文可以承载多个业务流。在R7和R8规范中，又将策略控制和计费控制结合起来，把策略决策功能(PDF)和基于流的计费功能(FBC)合并，提出了一种新的架构，即策略和计费控制(Policy and Charging Control，以下简称PCC)，用来实现上层的功能实体对承载网络层的承载策略和计费控制。利用FBC或PCC机制，应用/内容层和业务/会话控制层可以实现与承载层间的策略和计费控制信息的传送。Step 713: After receiving the returned service response, the P-CSCF sends the CCID, ICID and media resource negotiation (SDP) information to the policy and charging rule function (Policy Charging Rule Function, Hereinafter referred to as PCRF). The PCRF is a functional entity in the IMS. The service/session control layer uses the negotiated bearer information to control the establishment of the bearer channel of the bearer layer through the PCRF. In the embodiment shown in Fig. 3 and Fig. 5, it is aimed at the R5 version of 3GPP, adopting the service-based local policy control (SBLP) mechanism to realize the bearer and charging control between the IMS service/session control layer and the bearer layer , while the charging method of 3GPP R5 and previous versions is mainly for the charging of the PDP context at the bearer level. With the development of IMS specifications and market demand, its limitations are mainly manifested in: the R5 charging method cannot distinguish between different IP Flow , the billing method is not applicable to other access methods (WLAN, xDSL, Cable...); the number of terminals supporting the secondary PDP context is limited, and the secondary PDPContext occupies the processing and storage resources of the mobile terminal and shortens the battery life ; In addition, the activation and deactivation of the PDPContext will greatly increase the signaling overhead in the GPRS/UMTS system and increase the delay of service establishment. Therefore, in 3GPP R6, a flow-based charging (Flow Based Charging, hereinafter referred to as FBC) mechanism capable of distinguishing service flows is introduced in the bearer layer, and one PDP context can carry multiple service flows. In the R7 and R8 specifications, the policy control and charging control are combined, the policy decision function (PDF) and the flow-based charging function (FBC) are merged, and a new architecture is proposed, that is, policy and charging Control (Policy and Charging Control, hereinafter referred to as PCC), is used to implement the bearer policy and charging control of the upper layer functional entities on the bearer network layer. Using the FBC or PCC mechanism, the application/content layer and the service/session control layer can realize the transmission of policy and charging control information with the bearer layer.

步骤714：PCRF通过PCC规则将CCID和ICID传递给承载子模块(GGSN)。这样GGSN就获得了其它两层的计费标识(CCID和ICID)，以便在生成承载计费话单的时，承载子模块(GGSN)将应用/内容层的计费标识CCID和业务/会话控制层的计费标识ICID记录到承载计费话单中。参见图8，对于同一会话中不同的内容，在生成会话计费话单时，R5之后的版本中，由于承载层引入区分不同业务流的技术，GCID已经不能用来唯一标识一个应用/内容在承载层的计费话单，需要将CCID、ICID记录在业务数据(Service Data)项中标识承载层的计费话单，如将GCID记录在一个承载计费话单中，将根据第一内容请求产生的第一CCID及同一ICID记录在该承载计费话单的第一业务数据项中，将根据第二内容请求产生的第二CCID及同一ICID记录在该承载计费话单的第二业务数据项中，将根据第三内容请求产生的第三CCID及同一ICID记录在该承载计费话单的第三业务数据项中。具体CCID、ICID可记录在业务数据项的应用功能记录信息(AF-Record-Information)项中。Step 714: The PCRF transmits the CCID and the ICID to the bearer submodule (GGSN) through the PCC rule. In this way, the GGSN has obtained the charging identifiers (CCID and ICID) of the other two layers, so that when generating the bearer charging bill, the bearer submodule (GGSN) will use the charging identifier CCID of the application/content layer and the service/session control The charging identifier ICID of the layer is recorded in the bearer billing bill. See Figure 8. For different content in the same session, when generating session billing bills, in versions after R5, the GCID cannot be used to uniquely identify an application/content in the version after R5 due to the introduction of technology to distinguish different service For the billing bill of the bearer layer, the CCID and ICID need to be recorded in the service data (Service Data) item to identify the billing bill of the bearer layer. If the GCID is recorded in a bearer billing bill, the The first CCID and the same ICID generated by the request are recorded in the first service data item of the bill for bearer charging, and the second CCID and the same ICID generated according to the second content request are recorded in the second item of the bill for bearer billing. In the service data item, the third CCID and the same ICID generated according to the third content request are recorded in the third service data item of the bearer charging bill. The specific CCID and ICID can be recorded in the application function record information (AF-Record-Information) item of the service data item.

步骤715：GGSN向PCRF返回PCC规则响应。Step 715: The GGSN returns a PCC rule response to the PCRF.

步骤716：P-CSCF接收到业务响应后，将该业务响应转发给终端。Step 716: After receiving the service response, the P-CSCF forwards the service response to the terminal.

步骤717-719：当用户结束使用业务或内容时，SIP应用接入网关将向增值业务管理平台发起计费确认的请求，增值业务管理平台返回相应的计费确认响应，完成计费流程。Steps 717-719: When the user finishes using the service or content, the SIP application access gateway will initiate a charging confirmation request to the value-added service management platform, and the value-added service management platform will return a corresponding charging confirmation response to complete the charging process.

上述流程示出了一次IMS会话过程中使用一个内容的情况，对于一次会话中涉及多个内容的情况，在应用/内容层，针对每个内容的使用形成一个独立的话单，用唯一的计费标识CCID来标记，即对应于第二内容请求产生第二内容计费标识；在业务/会话控制层的IMS域，对于一次会话过程中使用到多个内容的情况，由于是在一次会话中，所以只有一个会话计费话单，记录有该层的计费标识ICID，由于是多个内容，在该话单中利用SDP项(List of SDP Media Components项)来逐个记录，每个SDP项中对应记录承载计费标识和内容计费标识，即对应第一内容请求，第一SDP项记录第一CCID，第二SDP项记录第二CCID；在承载层面，由于GGSN支持区分具体的业务流，因此，每个应用/内容不需要创建新的PDP上下文来进行承载，GCID不能用于唯一标识一个应用/内容在承载层的话单，不同内容在承载层的使用还需要用eG-CDR话单中的不同业务数据(ServiceData)项来记录，即将对应第一内容请求的第一CCID、ICID记录在第一业务数据项中，将对应第二内容请求的第二CCID、ICID记录在第二业务数据项中。除了上述计费标识及记录上述标识的计费话单的不同，针对不同内容请求的流程是一致的。The above process shows the case of using one content during one IMS session. For the case of multiple content involved in one session, at the application/content layer, an independent bill is formed for the use of each content, and a unique billing Identifies the CCID to mark, that is, generates the second content charging identifier corresponding to the second content request; in the IMS domain of the service/session control layer, for the situation that multiple contents are used during one session, since it is in one session, Therefore, there is only one session billing bill, and the billing identifier ICID of this layer is recorded. Since there are multiple contents, the SDP item (List of SDP Media Components item) is used in the bill to record one by one. In each SDP item Correspondingly record the bearer charging ID and content charging ID, that is, corresponding to the first content request, the first SDP item records the first CCID, and the second SDP item records the second CCID; at the bearer level, since the GGSN supports distinguishing specific service flows, Therefore, each application/content does not need to create a new PDP context for carrying. GCID cannot be used to uniquely identify an application/content in the bill of the bearer layer. The use of different content in the bearer layer also needs to be used in the eG-CDR bill Record different service data (ServiceData) items, that is, record the first CCID and ICID corresponding to the first content request in the first service data item, and record the second CCID and ICID corresponding to the second content request in the second service data item. Except for the differences in the above-mentioned billing identifiers and the billing bills that record the above-mentioned identifiers, the processes for requesting different content are the same.

本实施例，在业务的执行过程中，通过SIP协议将应用/内容层面的计费标识CCID传递到业务/会话控制层的IMS域，通过FBC/PCC机制将应用/内容层面的计费标识CCID和业务/会话控制层的IMS域的计费标识ICID传递到承载层网关。然后，得到其它层面计费标识的网元将得到的计费标识插入到各自的计费话单中，其中，IMS域的网元将得到的应用/内容层面的计费标识CCID插入到与该次内容相关的SDP Media Component话单项中，即将对应第一内容请求的第一CCID记录在会话计费话单的第一SDP项中，将对应第二内容请求的第二CCID记录在会话计费话单的第二SDP项中；支持FBC/PCC增强型的GGSN将得到的应用/内容层面的计费标识CCID和业务/会话控制层的IMS域的计费标识ICID插入到与该次内容相关的Service Data话单项中的应用功能记录信息(AF-Record-Information)子项中，即将对应第一内容请求的第一CCID、ICID记录在承载计费话单的第一业务数据项中，将对应第二内容请求的第二CCID、ICID记录在承载计费话单的第二业务数据项中。当计费系统收到三个层面传来的计费话单后，可以根据下层话单中包含的计费标识信息将一次增值应用/内容的使用过程中涉及到的三个层面的计费话单关联起来，支持运营商采取灵活的计费模式完成批价和话单核减，避免重复计费，实现面向内容的精确计费。In this embodiment, in the execution process of the service, the charging identification CCID of the application/content level is transferred to the IMS domain of the service/session control layer through the SIP protocol, and the charging identification CCID of the application/content level is transferred through the FBC/PCC mechanism and the charging identity ICID of the IMS domain of the service/session control layer are transmitted to the bearer layer gateway. Then, the network elements that have obtained the charging identifiers of other levels insert the obtained charging identifiers into their respective billing bills, wherein, the network elements in the IMS domain insert the obtained application/content-level charging identifiers CCID into the In the SDP Media Component bill item related to the second content, the first CCID corresponding to the first content request is recorded in the first SDP item of the session billing bill, and the second CCID corresponding to the second content request is recorded in the session billing In the second SDP item of the bill: the GGSN supporting FBC/PCC enhanced will insert the obtained charging identifier CCID at the application/content level and the charging identifier ICID of the IMS domain at the service/session control layer into the In the application function record information (AF-Record-Information) subitem in the Service Data bill item of the Service Data, the first CCID and ICID corresponding to the first content request are about to be recorded in the first service data item of the bearer billing bill, and the The second CCID and ICID corresponding to the second content request are recorded in the second service data item carrying the charging bill. When the billing system receives the billing bills from the three levels, it can transfer the billing bills of the three levels involved in the use of a value-added application/content according to the billing identification information contained in the lower-level bill It supports operators to adopt a flexible billing mode to complete price approval and bill verification, avoid repeated billing, and achieve accurate content-oriented billing.

图9为本发明计费关联的方法实施例五流程图，该实施例包括：FIG. 9 is a flow chart of Embodiment 5 of the charging association method of the present invention. This embodiment includes:

步骤901：终端发送内容请求给承载层网元，如GGSN，用于发起一个SIP消息以建立承载信道。Step 901: The terminal sends a content request to a bearer layer network element, such as a GGSN, for initiating a SIP message to establish a bearer channel.

步骤902：GGSN将该内容请求发送到业务/会话控制层的IMS域。Step 902: GGSN sends the content request to the IMS domain of the service/session control layer.

步骤903：第一个收到该内容请求的业务/会话控制层网元(如S-CSCF)根据内容请求获取会话计费标识，如业务计费键(S-ChargingKey)，如可以根据SIP消息头的字段或者字段的组合来判断业务类型，从而匹配到该业务所对应的计费键S-ChargingKey。计费键(ChargingKey)是在线或离线计费系统进行批价所需的信息，运营商可以灵活配置每个业务所对应的计费键的取值。在业务/会话控制层采用计费键S-ChargingKey(即Session-ChargingKey)来标识增值应用/内容在业务/会话控制层面的计费子策略，S-ChargingKey在配置该层的计费策略时产生。IMS域中的计费网元在生成计费话单时，将S-ChargingKey插入到话单的批价项RatingGroup中。对于一次业务会话过程中涉及到的不同内容对会话层资源的使用，在IMS域的话单中具体通过Listof SDP Media Components项来逐个记录。Step 903: The first service/session control layer network element (such as S-CSCF) that receives the content request obtains the session charging identifier, such as the service charging key (S-ChargingKey), according to the content request, for example, according to the SIP message The field or combination of fields in the header is used to determine the service type, so as to match the charging key S-ChargingKey corresponding to the service. The charging key (ChargingKey) is the information required by the online or offline charging system for rating. The operator can flexibly configure the value of the charging key corresponding to each service. At the service/session control layer, the charging key S-ChargingKey (Session-ChargingKey) is used to identify the charging sub-policy of the value-added application/content at the service/session control layer, and the S-ChargingKey is generated when the charging policy of this layer is configured . The charging network element in the IMS domain inserts the S-ChargingKey into the rating item RatingGroup of the bill when generating the billing bill. For the use of session layer resources by different content involved in a business session, it is recorded one by one in the IMS domain call list through the Listof SDP Media Components item.

如图11所示，分层综合的计费策略在业务部署时通过管理系统来进行配置，主要有有两个入口：客户关系管理CRM和增值业务管理平台VASMP，其中CRM是主入口，支持所有业务的配置。对于涉及VASMP管理范围的业务配置，可以在VASMP提供的界面或接口上进行配置。若通过VASMP进行业务配置，VASMP的业务信息必须同步到CRM。如果通过CRM进行业务配置，CRM分拣出与VASMP相关的信息同步到VASMP上。所有业务相关的信息和用户相关的信息都保存在共享信息数据SID(Shared Information Data)中。通过在SID中添加一个策略分发模块，它负责各层相关计费策略信息的分发。当计费策略相关的数据被同步时，就通过公共开放策略服务COPS协议发送给各层相关的网络节点。如承载层分组域的GGSN，会话控制层的S-CSCF、应用/内容层的增值业务管理平台等。SID中策略分发模块相当于策略决策点PDP，而各层的计费网元相当于策略执行点PEP。它们可以主动向PDP请求策略信息。当SID中数据有更新时，SID中的策略分发模块(PDP)也可以通过COPS协议向这些PEP发送下发计费策略。通过计费策略的自动配置流程，各个层面的计费网元就获得了增值应用/内容在该层面的计费子策略相关的配置信息，如计费触发点、计费键(ChargingKey)、业务标识等。当有内容请求的时候，检测相应的计费触发点，在生成话单的时候将计费键插入到话单中。As shown in Figure 11, the hierarchical and comprehensive billing strategy is configured through the management system during service deployment. There are two main entrances: customer relationship management CRM and value-added service management platform VASMP. CRM is the main entrance and supports all Business configuration. For the service configuration involving the VASMP management range, it can be configured on the interface or interface provided by VASMP. If service configuration is performed through VASMP, the service information of VASMP must be synchronized to CRM. If the service configuration is performed through the CRM, the CRM sorts out the information related to the VASMP and synchronizes it to the VASMP. All business-related information and user-related information are stored in shared information data SID (Shared Information Data). By adding a policy distribution module in the SID, it is responsible for the distribution of relevant charging policy information of each layer. When the data related to the charging policy is synchronized, it is sent to the relevant network nodes of each layer through the common open policy service COPS protocol. Such as the GGSN in the packet domain of the bearer layer, the S-CSCF in the session control layer, and the value-added service management platform in the application/content layer. The policy distribution module in the SID is equivalent to the policy decision point PDP, and the charging network elements of each layer are equivalent to the policy execution point PEP. They can proactively request policy information from the PDP. When the data in the SID is updated, the policy distribution module (PDP) in the SID can also send the charging policy to these PEPs through the COPS protocol. Through the automatic configuration process of the charging policy, the charging network elements at each level can obtain the configuration information related to the charging sub-policy of the value-added application/content at that level, such as the charging trigger point, charging key (ChargingKey), service logo, etc. When there is a content request, detect the corresponding charging trigger point, and insert the charging key into the bill when generating the bill.

步骤904：S-CSCF向SIP应用接入网关转发内容请求。Step 904: The S-CSCF forwards the content request to the SIP application access gateway.

步骤905：SIP应用接入网关在向增值业务管理平台发送业务鉴权/计费请求。Step 905: the SIP application access gateway is sending a service authentication/charging request to the value-added service management platform.

步骤906：增值业务管理平台(VASMP)根据请求信息获取相应的内容计费标识，如内容计费键(C-ChargingKey)，如可以根据请求的内容来匹配该内容所对应的计费键C-ChargingKey。在应用/内容层，用内容计费键C-ChargingKey(即Content-ChargingKey)来标识增值应用/内容在应用/内容层面的计费子策略，C-ChargingKey在配置该层的计费策略时产生。应用/内容层的计费网元在生成计费话单时，将C-ChargingKey插入到话单的批价项RatingGroup中。应用/内容层的计费网元可以是增值业务管理VASMP，也可以是SIP应用接入网关。Step 906: The value-added service management platform (VASMP) obtains the corresponding content charging identifier according to the request information, such as the content charging key (C-ChargingKey), for example, the charging key C-ChargingKey corresponding to the content can be matched according to the requested content. ChargingKey. At the application/content layer, the content charging key C-ChargingKey (Content-ChargingKey) is used to identify the charging sub-policy of the value-added application/content at the application/content layer, and the C-ChargingKey is generated when the charging policy of this layer is configured . When the charging network element at the application/content layer generates a charging bill, it inserts the C-ChargingKey into the rating item RatingGroup of the bill. The billing network element at the application/content layer can be a value-added service management VASMP, or a SIP application access gateway.

步骤907：增值业务管理平台(VASMP)向SIP应用接入网关返回相应的业务鉴权/计费响应。Step 907: The value-added service management platform (VASMP) returns a corresponding service authentication/charging response to the SIP application access gateway.

步骤908-909：SIP应用接入网关向SIP应用服务器转发内容请求、接收相应的业务响应，并转发业务响应给S-CSCF、终端。Steps 908-909: The SIP application access gateway forwards the content request to the SIP application server, receives the corresponding service response, and forwards the service response to the S-CSCF and the terminal.

步骤910：终端向GGSN发送承载建立请求。Step 910: the terminal sends a bearer establishment request to the GGSN.

步骤911：GGSN根据业务流信息获取相应的承载计费标识，如承载计费键(B-ChargingKey)。在承载层面，采用计费键B-ChargingKey(即Bearer-ChargingKey)来标识增值应用/内容在承载层面的计费子策略，B-ChargingKey在配置该层的计费策略时产生。对于基于PCC架构的动态计费策略，B-ChargingKey将配置在策略和计费规则功能PCRF(Policy andCharging Rule Function)用于动态计费策略的动态生成和下发，当具有策略和计费执行功能PCEF(Policy and Charging Enforcement Function)的承载层网关(如GGSN)检测到业务流时，向PCRF请求计费策略，PCRF将包含B-ChargingKey的计费规则下发给承载层网关；对于静态的承载层计费策略，B-ChargingKey可以直接配置在具有策略和计费执行功能PCEF(Policy andCharging Enforcement Function)的承载层网关(如GGSN)上。由于GGSN支持区分具体的业务流，多个应用/内容的使用在承载层面可以共享一个PDP上下文，不需要再激活一个新的PDP上下文。在支持FBC/PCC的GGSN的增强型话单eG-CDR中，有一个话单项为“List of Service Data”，专门用来记录每个业务流的详细情况，主要包括针对该业务流的批价组(Rating Group)、计费规则库名称(Charging Rule Base Name)、使用的时间(Time Usage)、上行流量(Data Volume Uplink)、下行流量(Data Volume Downlink)、应用功能记录信息(AF-Record-Information)等，其中，批价组(RatingGroup)项可以用来记录针对该业务流的承载层计费子策略的计费键B-ChargingKey。Step 911: The GGSN acquires the corresponding bearer charging identifier, such as the bearer charging key (B-ChargingKey), according to the service flow information. At the bearer level, the charging key B-ChargingKey (ie Bearer-ChargingKey) is used to identify the charging sub-policy of the value-added application/content at the bearer level, and the B-ChargingKey is generated when configuring the charging policy at this layer. For dynamic charging policies based on PCC architecture, B-ChargingKey will be configured in the policy and charging rule function PCRF (Policy and Charging Rule Function) for dynamic generation and delivery of dynamic charging policies, when it has the policy and charging execution function When the bearer layer gateway (such as GGSN) of PCEF (Policy and Charging Enforcement Function) detects the service flow, it requests the charging policy from PCRF, and PCRF sends the charging rules including B-ChargingKey to the bearer layer gateway; for static bearer Layer charging policy, B-ChargingKey can be directly configured on the bearer layer gateway (such as GGSN) with policy and charging enforcement function PCEF (Policy and Charging Enforcement Function). Since the GGSN supports the distinction of specific service flows, multiple applications/contents can share a PDP context at the bearer level without activating a new PDP context. In the enhanced bill eG-CDR of GGSN that supports FBC/PCC, there is a bill item called "List of Service Data", which is specially used to record the details of each service flow, mainly including the approval price for the service flow Group (Rating Group), Charging Rule Base Name (Charging Rule Base Name), Time Usage (Time Usage), Uplink Traffic (Data Volume Uplink), Downlink Traffic (Data Volume Downlink), Application Function Record Information (AF-Record -Information), etc., wherein the item RatingGroup (RatingGroup) can be used to record the charging key B-ChargingKey of the bearer layer charging sub-policy for the service flow.

步骤912：GGSN向终端发送相应的承载建立应答。以建立一个承载信道用于传输媒体流。Step 912: the GGSN sends a corresponding bearer establishment response to the terminal. To establish a bearer channel for transmitting media streams.

步骤913-915：当用户结束使用业务或内容时，SIP应用接入网关将向增值业务管理平台发起计费确认的请求，增值业务管理平台返回相应的计费确认响应，完成计费流程。Steps 913-915: When the user finishes using the service or content, the SIP application access gateway will initiate a charging confirmation request to the value-added service management platform, and the value-added service management platform will return a corresponding charging confirmation response to complete the charging process.

上述流程示出了一次IMS会话过程中使用一个内容的情况，对于一次会话中涉及多个内容的情况，在应用/内容层，针对每个内容的使用形成一个独立的话单，用唯一的内容计费键来标记，即对应于第一内容请求产生第一C-ChargingKey，对应于第二内容请求产生第二C-ChargingKey；在业务/会话控制层的IMS域，对于一次会话过程中使用到多个内容的情况，由于是在一次会话中，所以只有一个会话计费话单，由于是多个内容，在该话单中利用SDP项(List of SDP Media Components项)来逐个记录对应的业务计费键，即对应第一内容请求，第一SDP项记录第一S-ChargingKey，第二SDP项记录第二S-ChargingKey；在承载层面，由于GGSN支持区分具体的业务流，因此，每个应用/内容不需要创建新的PDP上下文来进行承载，GCID不能用于唯一标识一个应用/内容在承载层的话单，不同内容在承载层的使用还需要用eG-CDR话单中的不同业务数据(Service Data)项的RatingGroup来记录不同的承载计费键，即将对应第一内容请求的第一B-ChargingKey记录在第一业务数据项中，将对应第二内容请求的第二B-ChargingKey记录在第二业务数据项中，除了上述记录计费标识的项不同，针对第二内容请求的流程和第一内容请求的流程是一致的，只是S-CSCF根据第二内容请求获取第二S-ChargingKey、增值业务管理平台根据第二内容请求获取第二C-ChargingKey、GGSN根据第二内容请求获取第二B-ChargingKey。并在生成计费话单时，参见图12，将第一C-ChargingKey记录在第一内容计费话单中，将第一S-ChargingKey记录在会话计费话单的第一SDP项中，将第一B-ChargingKey记录在承载计费话单的第一业务数据项中；将第二C-ChargingKey记录在第二内容计费话单中，将第二S-ChargingKey记录在会话计费话单的第二SDP项中，将第二B-ChargingKey记录在承载计费话单的第二业务数据项中；将第三C-ChargingKey记录在第三内容计费话单中，将第三S-ChargingKey记录在会话计费话单的第三SDP项中，将第三B-ChargingKey记录在承载计费话单的第三业务数据项中。具体B-ChargingKey可记录在业务数据项的批价组(RatingGroup)项中。The above process shows the case of using one content during one IMS session. For the case of multiple content involved in one session, at the application/content layer, an independent bill is formed for the use of each content, and the unique content counts To mark with a fee key, that is, the first C-ChargingKey is generated corresponding to the first content request, and the second C-ChargingKey is generated corresponding to the second content request; in the IMS domain of the service/session control layer, multiple In the case of one content, because it is in one session, there is only one session billing bill. Since there are multiple contents, the SDP item (List of SDP Media Components item) is used in the bill to record the corresponding business billing one by one. Charge key, corresponding to the first content request, the first SDP item records the first S-ChargingKey, and the second SDP item records the second S-ChargingKey; at the bearer level, since the GGSN supports distinguishing specific service flows, each application /Content does not need to create a new PDP context for bearer, GCID cannot be used to uniquely identify an application/content in the bearer layer bill, and the use of different content in the bearer layer also needs to use different service data in the eG-CDR bill ( Service Data) item RatingGroup to record different bearer charging keys, that is, record the first B-ChargingKey corresponding to the first content request in the first service data item, and record the second B-ChargingKey corresponding to the second content request in In the second service data item, except for the above-mentioned items that record the charging identifier, the process for the second content request is the same as that for the first content request, except that the S-CSCF obtains the second S-ChargingKey according to the second content request . The value-added service management platform obtains the second C-ChargingKey according to the second content request, and the GGSN obtains the second B-ChargingKey according to the second content request. And when generating the charging bill, referring to Fig. 12, the first C-ChargingKey is recorded in the first content billing bill, and the first S-ChargingKey is recorded in the first SDP item of the session billing bill, Record the first B-ChargingKey in the first service data item of the bearer charging bill; record the second C-ChargingKey in the second content charging bill, and record the second S-ChargingKey in the session billing In the second SDP item of the bill, record the second B-ChargingKey in the second service data item of the bearer charging bill; record the third C-ChargingKey in the third content charging bill, and record the third S - Recording the ChargingKey in the third SDP item of the session charging bill, and recording the third B-ChargingKey in the third service data item of the bearer billing bill. The specific B-ChargingKey can be recorded in the RatingGroup item of the business data item.

图10为本发明计费关联的方法实施例六流程图，相比于图9所示的承载层为静态策略控制的实施例五，本实施例的承载层为动态策略控制的，承载层为静态策略控制时，承载网络层的计费子策略信息在业务部署的时候通过自动配置机制已经加载到具有支持PCEF的承载网关上，因此，承载层网关不需要再向PCRF动态请求策略和计费控制规则，直接通过业务流的信息就可以获得针对该业务流的计费键，即B-ChargingKey，因此在流程中，本实施例将图9中的步骤911替换为如下的步骤9111和步骤9112：Fig. 10 is a flow chart of Embodiment 6 of the charging association method of the present invention. Compared with Embodiment 5 shown in Fig. 9 in which the bearer layer is controlled by a static policy, the bearer layer in this embodiment is controlled by a dynamic policy, and the bearer layer is Under static policy control, the charging sub-policy information of the bearer network layer has been loaded to the bearer gateway that supports PCEF through the automatic configuration mechanism during service deployment. Therefore, the bearer layer gateway does not need to dynamically request policy and charging from PCRF. Control rules, the charging key for the service flow, that is, B-ChargingKey, can be obtained directly through the information of the service flow, so in the process, this embodiment replacesstep 911 in Figure 9 with the following steps 9111 and 9112 :

步骤9111：GGSN向PCRF发送承载授权请求。Step 9111: GGSN sends a bearer authorization request to PCRF.

步骤9112：PCRF通过授权响应返回计费键第一B-ChargingKey。Step 9112: PCRF returns the charging key first B-ChargingKey through the authorization response.

随后在生成承载层的计费话单时，将B-ChargingKey插入到该业务流对应的Service Data项中的RatingGroup字段中。而本实施由于是动态策略控制，承载层网关需要向PCRF动态请求策略和计费控制规则后，才能获得针对该业务流的计费键，即B-ChargingKey，然后在生成承载层的计费话单时，将B-ChargingKey插入到该业务流对应的Service Data项中的RatingGroup字段中。而业务/会话控制层面和应用/内容层面的计费网元，如S-CSCF和VASMP，将根据内容请求所携带的信息，从计费策略的配置信息表中查找到相匹配的计费键，在生成各自的话单的时候插入到相应的RatingGroup字段中，如应用/内容层可以根据请求的内容来匹配该内容所对应的计费键C-ChargingKey，而业务/会话控制层的S-CSCF可以根据SIP消息头的字段或者字段的组合来判断业务类型，从而匹配到该业务所对应的计费键S-ChargingKey。Then, when generating the billing bill at the bearer layer, insert the B-ChargingKey into the RatingGroup field in the Service Data item corresponding to the service flow. However, since this implementation is dynamic policy control, the bearer layer gateway needs to dynamically request policies and charging control rules from the PCRF in order to obtain the charging key for the service flow, that is, B-ChargingKey, and then generate the charging call of the bearer layer. Insert the B-ChargingKey into the RatingGroup field in the Service Data item corresponding to the business flow. The charging network elements at the service/session control level and application/content level, such as S-CSCF and VASMP, will find the matching charging key from the configuration information table of the charging policy according to the information carried in the content request , and insert it into the corresponding RatingGroup field when generating respective bills. For example, the application/content layer can match the charging key C-ChargingKey corresponding to the content according to the content of the request, and the S-CSCF of the service/session control layer The service type can be judged according to the field or field combination of the SIP message header, so as to match the charging key S-ChargingKey corresponding to the service.

同样的，在一次IMS会话过程中，可能会存在使用多个应用/内容的情况。图12示出在一次会话中多个内容的话单关联方式示意图，在应用内容层面，每个应用/内容的使用都产生独立的计费话单，话单中包含各自相对应的计费键C-ChargingKey。在业务/会话控制层的IMS域的计费网元，在一个话单中利用List of SDP Media Components项来逐个记录不同内容在会话层的资源使用情况，每个SDP Media Components中包含各自相对应的计费键S-ChargingKey。在承载层面，支持FBC/PCC的GGSN可以区分不同的业务流，即在一个PDP上下文中可以承载不同的业务流。因此，在GGSN产生的增强型话单eG-CDR中，利用“List of Service Data”话单项记录不同的业务流的详细情况，每个Service Data项的RatingGroup用来保存针对该业务流的计费键B-ChargingKey。Likewise, during an IMS session, there may be situations in which multiple applications/contents are used. Figure 12 shows a schematic diagram of bill association methods for multiple contents in one session. At the application content level, the use of each application/content generates an independent billing bill, which contains its corresponding billing key C -ChargingKey. The billing network element in the IMS domain of the service/session control layer uses the List of SDP Media Components item in a bill to record the resource usage of different contents at the session layer one by one. Each SDP Media Components contains its corresponding The charging key S-ChargingKey. At the bearer level, the GGSN supporting FBC/PCC can distinguish different service flows, that is, different service flows can be carried in one PDP context. Therefore, in the enhanced bill eG-CDR generated by GGSN, the "List of Service Data" bill item is used to record the details of different service flows, and the RatingGroup of each Service Data item is used to save the billing for the service flow Key B—Charging Key.

本发明计费关联的方法通过实施例，实现了应用/内容层面、业务/会话控制层面和承载层面的计费话单关联，运营商可以根据不同的市场营销模式，在不同的计费层面上采用不同的计费策略，从而可以支持灵活的业务计费方式，计费系统可以利用本发明所述的计费关联方法，将一次业务使用所涉及到的各个层面的计费话单准确的关联起来，然后根据该业务所对应的各层的计费策略对话单进行批价，从而精确的计算出用户本次使用的业务费用，避免了计费的重复性。The billing association method of the present invention implements the billing bill association at the application/content level, service/session control level, and bearer level through the embodiments, and operators can use different charging modes according to different marketing models. Adopting different billing strategies can support flexible service billing methods, and the billing system can use the billing association method described in the present invention to accurately associate the billing bills of various levels involved in a service use Then, according to the billing strategy dialog sheet of each layer corresponding to the service, the price is approved, so as to accurately calculate the service fee used by the user this time, and avoid the duplication of billing.

图13为本发明计费关联的装置实施例结构示意图，该实施例包括：会话标识模块1、内容标识模块2、承载标识模块3和关联模块4；会话标识模块1用于产生会话计费标识，所述会话计费标识用于标识业务/会话控制层的资源使用情况；内容标识模块2用于产生内容计费标识，所述内容计费标识用于标识应用/内容层的资源使用情况；承载标识模块3用于产生承载计费标识，所述承载计费标识用于标识承载层的资源使用情况；关联模块4用于根据所述内容计费标识、会话计费标识和承载计费标识关联内容计费话单、会话计费话单和承载计费话单，所述内容计费话单用于对应用/内容层进行计费，所述会话计费话单用于对业务/会话控制层进行计费，所述承载计费话单用于对承载层进行计费。其中，关联模块4包括：会话子模块41、内容子模块42和承载子模块43。Figure 13 is a schematic structural diagram of an embodiment of an apparatus for charging association in the present invention, which includes: a session identification module 1, a content identification module 2, a bearer identification module 3, and an association module 4; the session identification module 1 is used to generate a session charging identification The session charging identifier is used to identify the resource usage of the service/session control layer; the content identification module 2 is used to generate a content charging identifier, and the content charging identifier is used to identify the resource usage of the application/content layer; The bearer identification module 3 is used to generate a bearer charging ID, and the bearer charging ID is used to identify the resource usage of the bearer layer; the association module 4 is used to base the content charging ID, the session charging ID, and the bearer charging ID Associate content billing bills, session billing bills and bearer billing bills, the content billing bills are used for charging the application/content layer, and the session billing bills are used for service/session The control layer performs charging, and the bearer charging bill is used for charging the bearer layer. Wherein, the association module 4 includes: asession submodule 41 , acontent submodule 42 and abearer submodule 43 .

其中，内容子模块用于将所述会话计费标识、承载计费标识、内容计费标识记录在内容计费话单中；会话子模块，用于将所述内容计费标识、承载计费标识、会话计费标识记录在会话计费话单中；承载子模块，用于将所述内容计费标识、会话计费标识、承载计费标识记录在承载计费话单中。Wherein, the content sub-module is used to record the session charging ID, bearer charging ID, and content charging ID in the content charging bill; the session sub-module is used to record the content charging ID, bearer charging ID The identifier and the session charging identifier are recorded in the session charging bill; the bearer submodule is used to record the content charging identifier, the session charging identifier, and the bearer charging identifier in the bearer charging bill.

或者，内容子模块，用于将所述会话计费标识、承载计费标识、内容计费标识记录在内容计费话单中；会话子模块，用于将所述承载计费标识、会话计费标识记录在会话计费话单中；承载子模块，用于将所述承载计费标识记录在承载计费话单中。Or, the content submodule is used to record the session charging identifier, the bearer charging identifier and the content charging identifier in the content charging bill; the session submodule is used to record the bearer charging identifier, the session charging identifier The charge identifier is recorded in the session billing bill; the bearer submodule is configured to record the bearer billing identifier in the bearer billing bill.

或者，内容子模块，用于将所述内容计费标识记录在内容计费话单中；会话子模块，用于将所述内容计费标识、会话计费标识记录在会话计费话单中；承载子模块，用于将所述内容计费标识、会话计费标识、承载计费标识记录在承载计费话单中。Or, the content submodule is used to record the content charging identifier in the content charging bill; the session submodule is used to record the content charging identifier and the session charging identifier in the session charging bill ; A bearer submodule, configured to record the content charging identifier, session charging identifier, and bearer charging identifier in the bearer charging bill.

或者，内容子模块，用于将所述内容计费标识记录在内容计费话单中；会话子模块，用于将所述会话计费标识记录在会话计费话单中；承载子模块，用于将所述承载计费标识记录在承载计费话单中。Or, the content submodule is used to record the content charging identifier in the content charging bill; the session submodule is used to record the session charging identifier in the session charging bill; the bearer submodule, It is used to record the bearer charging identifier in the bearer charging bill.

具体的，会话子模块41用于将会话标识模块1产生的会话计费标识添加进内容请求中；内容子模块42用于将所述内容请求中携带的会话计费标识以及根据内容请求产生的内容计费标识记录在内容计费话单中，并将所述会话计费标识和内容计费标识添加进业务响应中；会话子模块41用于将所述业务响应中携带的会话计费标识记录在会话计费话单中，将所述业务响应中携带的内容计费标识记录在所述会话计费话单的媒体资源协商项中，并将所述会话计费标识和内容计费标识添加进授权响应中；承载子模块43用于将所述授权响应中携带的会话计费标识和内容计费标识以及根据内容请求产生的承载计费标识记录在承载计费话单中，并将所述承载计费标识添加进授权通知中；会话子模块41用于将所述授权通知中携带的承载计费标识记录在已记录有所述会话计费标识的会话计费话单的已记录有所述内容计费标识的媒体资源协商项中，并将所述承载计费标识添加进会话发起协议消息中；内容子模块42用于将所述会话发起协议消息中携带的承载计费标识记录在已记录有所述会话计费标识、内容计费标识的内容计费话单中。Specifically, thesession sub-module 41 is used to add the session charging identifier generated by the session identifier module 1 into the content request; thecontent sub-module 42 is used to add the session charging identifier carried in the content request and the The content charging identifier is recorded in the content charging bill, and the session charging identifier and the content charging identifier are added into the service response; thesession submodule 41 is used to add the session charging identifier carried in the service response record in the session charging bill, record the content charging identifier carried in the service response in the media resource negotiation item of the session charging bill, and record the session charging identifier and the content charging identifier Added in the authorization response; thebearer submodule 43 is used to record the session charging identifier and content charging identifier carried in the authorization response and the bearer charging identifier generated according to the content request in the bearer charging bill, and The bearer charging identifier is added into the authorization notification; thesession sub-module 41 is used to record the bearer charging identifier carried in the authorization notification in the recorded session charging bill of the session charging identifier. In the media resource negotiation item with the content charging identifier, add the bearer charging identifier into the session initiation protocol message; thecontent submodule 42 is used to add the bearer charging identifier carried in the session initiation protocol message Recorded in the content charging call record in which the session charging identifier and the content charging identifier have been recorded.

或者，会话子模块41用于将产生的会话计费标识添加进内容请求中；内容子模块42用于将所述内容请求中携带的会话计费标识以及根据内容请求产生的内容计费标识记录在内容计费话单中，并将所述会话计费标识添加进业务响应中；会话子模块41用于将所述业务响应中携带的会话计费标识记录在会话计费话单中；承载子模块43用于将根据内容请求产生的承载计费标识记录在承载计费话单中，并将所述承载计费标识添加进授权通知中；会话子模块41用于将所述授权通知中携带的承载计费标识记录在已记录有所述会话计费标识的会话计费话单的媒体资源协商项中，并将所述承载计费标识添加进会话发起协议消息中；内容子模块42用于将所述会话发起协议消息中携带的承载计费标识记录在已记录有所述会话计费标识、内容计费标识的内容计费话单中。Alternatively, thesession submodule 41 is used to add the generated session charging identifier into the content request; thecontent submodule 42 is used to record the session charging identifier carried in the content request and the content charging identifier generated according to the content request In the content billing bill, and add the session charging identifier into the service response; thesession submodule 41 is used to record the session billing identifier carried in the service response in the session billing bill; bear The sub-module 43 is used to record the bearer charging identifier generated according to the content request in the bearer charging bill, and add the bearer charging identifier into the authorization notice; thesession sub-module 41 is used to include the The carried bearer charging identifier is recorded in the media resource negotiation item of the session charging bill that has recorded the session charging identifier, and the bearer charging identifier is added into the session initiation protocol message; thecontent submodule 42 It is used to record the bearer charging identifier carried in the session initiation protocol message in the content charging bill in which the session charging identifier and the content charging identifier have been recorded.

或者，会话子模块41用于将产生的会话计费标识添加进内容请求中；内容子模块42用于将根据内容请求产生的内容计费标识记录在内容计费话单中，并将所述内容计费标识以及所述内容请求中携带的会话计费标识添加进业务响应中；会话子模块41用于将所述业务响应中携带的会话计费标识记录在会话计费话单中，将所述业务响应中携带的内容计费标识记录在所述会话计费话单的媒体资源协商项中，并将所述会话计费标识和内容计费标识添加进策略和计费控制规则中；承载子模块43，用于将产生的承载计费标识记录在承载计费话单中，并将所述策略和计费控制规则中携带的会话计费标识和内容计费标识记录在所述承载计费话单的业务数据项中。Or, thesession submodule 41 is used to add the generated session charging identifier into the content request; thecontent submodule 42 is used to record the content charging identifier generated according to the content request in the content billing record, and The content charging identifier and the session charging identifier carried in the content request are added into the service response; thesession submodule 41 is used to record the session charging identifier carried in the service response in the session charging bill, and The content charging identifier carried in the service response is recorded in the media resource negotiation item of the session charging bill, and the session charging identifier and the content charging identifier are added to the policy and charging control rules; Thebearer sub-module 43 is configured to record the generated bearer charging ID in the bearer billing bill, and record the session charging ID and content charging ID carried in the policy and charging control rules in the bearer billing In the service data item of the billing bill.

或者，所述会话计费标识为会话计费键、所述内容计费标识为内容计费键、所述承载计费标识为承载计费键。此时，会话子模块41用于将根据内容请求获取的会话计费键记录在会话计费话单的媒体资源协商项中；内容子模块42用于将根据内容请求获取的内容计费键记录在内容计费话单中；承载子模块43用于将根据内容请求获取的承载计费标识记录在承载计费话单的业务数据项中。Alternatively, the session charging identifier is a session charging key, the content charging identifier is a content charging key, and the bearer charging identifier is a bearer charging key. At this point, thesession submodule 41 is used to record the session charging key obtained according to the content request in the media resource negotiation item of the session charging bill; thecontent submodule 42 is used to record the content charging key obtained according to the content request In the content charging bill: thebearer submodule 43 is used to record the bearer charging identifier acquired according to the content request in the service data item of the bearer charging bill.

并且，上述承载计费标识是承载标识模块向策略和计费控制规则功能实体(PCRF)动态获取的或者所述承载计费标识是通过预置的配置机制静态获取的(即承载标识模块根据内容请求生成的)。上述内容标识模块为会话发起协议接入网关或者增值业务管理平台。In addition, the above-mentioned bearer charging identity is dynamically obtained by the bearer identity module from the Policy and Charging Control Rules Function (PCRF), or the bearer charging identity is statically obtained through a preset configuration mechanism (that is, the bearer identity module generated by the request). The above-mentioned content identification module is a session initiation protocol access gateway or a value-added service management platform.

本实施例通过会话标识模块产生会话计费标识、内容标识模块产生内容计费标识、承载标识模块产生承载计费标识，关联模块再将这些计费标识关联起来，实现整个系统的计费关联。In this embodiment, the session identification module generates the session charging ID, the content identification module generates the content charging ID, the bearer ID module generates the bearer charging ID, and the association module associates these charging IDs to realize the charging association of the whole system.

本发明计费关联的装置通过实施例，实现了应用/内容层面、业务/会话控制层面和承载层面的计费话单关联，运营商可以根据不同的市场营销模式，在不同的计费层面上采用不同的计费策略，从而可以支持灵活的业务计费方式，计费系统可以利用本发明所述的计费关联装置，将一次业务使用所涉及到的各个层面的计费话单准确的关联起来，然后根据该业务所对应的各层的计费策略对话单进行批价，从而精确的计算出用户本次使用的业务费用，避免了计费的重复性。The billing association device of the present invention realizes billing bill association at the application/content level, service/session control level, and bearer level through the embodiments, and operators can use different charging modes according to different marketing models. Adopting different charging strategies can support flexible service charging methods, and the charging system can use the charging association device described in the present invention to accurately associate the charging bills of various levels involved in a service use Then, according to the billing strategy dialog sheet of each layer corresponding to the service, the price is approved, so as to accurately calculate the service fee used by the user this time, and avoid the duplication of billing.

最后应说明的是：以上实施例仅用以说明本发明的技术方案而非对其进行限制，尽管参照较佳实施例对本发明进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对本发明的技术方案进行修改或者等同替换，而这些修改或者等同替换亦不能使修改后的技术方案脱离本发明技术方案的精神和范围。Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and not to limit them. Although the present invention has been described in detail with reference to the preferred embodiments, those of ordinary skill in the art should understand that: it still Modifications or equivalent replacements can be made to the technical solutions of the present invention, and these modifications or equivalent replacements cannot make the modified technical solutions deviate from the spirit and scope of the technical solutions of the present invention.