WO2010045493A2

WO2010045493A2 - Charging and accounting method and system for multicast and broadcast services

Info

Publication number: WO2010045493A2
Application number: PCT/US2009/060898
Authority: WO
Inventors: Tricci So
Original assignee: Zte U.S.A., Inc.
Priority date: 2008-10-15
Filing date: 2009-10-15
Publication date: 2010-04-22
Also published as: WO2010045493A3

Abstract

A system for charging and accounting for multicast and broadcast service (MCBCS) is disclosed. The system includes an accounting agent located at an access service network (ASN) configured to, when triggered by a session control or a mobile station event, collect identification information from a mobile station receiving a MCBCS and service identification information of an MCBCS content provider. An accounting client at the ASN is configured to create a usage detail record based on the identification information of the mobile station and the service identification information of the MCBCS content provider. A generating unit then generates charging and accounting information based on the usage detail record.

Description

CHARGING AND ACCOUNTING METHOD AND SYSTEM FOR MULTICAST AND BROADCAST SERVICES

Cross-Reference to Related Applications

[0001] This application claims priority to U.S. Provisional Patent Application No. 61/105,735 filed on October 15, 2008, entitled "MCBCS Charging and Accounting Method and System," the contents of which are incorporated by reference herein in their entirety.

Field

[0002] The present invention relates generally to wireless communications, and more particularly to charging and accounting for multicast and broadcast service(s) (MCBCS), as described in an Institute of Electrical and Electronics Engineers (IEEE) 802.16 communication system protocol.

Background

[0003] With the increasing popularity of mobile devices, there exists a need to allow users to attach to various domains, depending on their current location. A user may require access to resources being provided by a visited network different than their home network. The need for service from a visited network requires, in many models, negotiation and authorization between the mobile device and the visited network. [0004] An IEEE 802.16 MCBCS specification for providing multicast and broadcast services to one or a plurality of mobile devices allows for operation within the same multicast and broadcast service area by using different Connection Identifiers (CIDs) or different Security Associations (SAs). A Multicast and Broadcast Service zone indicates a region where MCBCS are operating by means of the CID and/or the SA. [0005] There is presently a need to provide charging and accounting of services provided at the exact time when a mobile device authorizes or requests the MCBCS, and to accurately record the exact duration of the service and/or the volume of data usage for the service.

Summary

[0006] The presently disclosed embodiments are directed to solving one or more of the problems presented in the prior art, described above, as well as providing additional features that will become readily apparent by reference to the following detailed description when taken in conjunction with the accompanying drawings.

[0007] One embodiment of the present disclosure is directed to a method of charging and accounting for multicast and broadcast service (MCBCS). The method includes collecting identification information from a mobile station receiving a MCBCS by an accounting agent located at an access service network (ASN); collecting service identification information of an MCBCS content provider by the accounting agent; creating a usage detail record based on the identification information of the mobile station and the service identification information of the MCBCS content provider collected at the ASN; and generating charging and accounting information based on the usage detail record.

[0008] Another embodiment is directed to a system for charging and accounting for MCBCS. The system includes an accounting agent located at an ASN configured to collect identification information from a mobile station receiving a MCBCS and service identification information of an MCBCS content provider. The system further includes an accounting client in the ASN configured to create a usage detail record based on the identification information of the mobile station and the service identification information of the MCBCS content provider; and a generating unit configured to generate charging and accounting information based on the usage detail record.

[0009] Yet another embodiment is directed to an ASN capable of performing charging and accounting for MCBCS. The ASN includes means for collecting identification information from a mobile station receiving a MCBCS and service identification information of an MCBCS content provider. The ASN further includes means for creating a usage detail record based on the identification information of the mobile station and the service identification information of the MCBCS content provider; and means for generating charging and accounting information based on the usage detail record.

[0010] Yet another embodiment is directed to a computer-readable medium storing instructions thereon configured to, when executed by a processor, perform a method of charging and accounting for MCBCS. The method comprises collecting identification information from a mobile station receiving a MCBCS by an accounting agent located at an ASN; collecting service identification information of an MCBCS content provider by the accounting agent; creating a usage detail record based on the identification information of the mobile station and the service identification information of the MCBCS content provider collected at the ASN; and generating charging and accounting information based on the usage detail record.

[0011] The charging and accounting of the MCBCS may be triggered using a session control or a predetermined mobile station event, for example. Access-based or service- based charging may be implemented, depending on the type of service provided by the MCBCS.

[0012] Further features and advantages of the present disclosure, as well as the structure and operation of various embodiments of the present disclosure, are described in detail below with reference to the accompanying drawings.

Brief Description of the Drawings

[0013] The present disclosure, in accordance with one or more various embodiments, is described in detail with reference to the following Figures. The drawings are provided for purposes of illustration only and merely depict exemplary embodiments of the disclosure. These drawings are provided to facilitate the reader's understanding of the disclosure and should not be considered limiting of the breadth, scope, or applicability of the disclosure. It should be noted that for clarity and ease of illustration these drawings are not necessarily made to scale. [0014] FIG. 1 is a schematic illustrating an exemplary architecture of a charging and accounting system for a wireless communication system according to one embodiment of the present disclosure.

[0015] FIG. 2 is a block diagram illustrating an exemplary mobile station in a wireless communication network according to one embodiment of the present disclosure.

[0016] FIG. 3 is a block diagram illustrating an exemplary access service network according to one embodiment of the present disclosure.

[0017] FIG. 4 is a block diagram illustrating an exemplary connectivity service network according to one embodiment of the present disclosure.

[0018] FIG. 5 is a graphical illustration of various exemplary levels and identifiers used for charging and accounting for multicast and broadcast services, according to one embodiment of the present disclosure.

[0019] FIG. 6 is an exemplary flow diagram illustrating a method of charging and accounting for multicast and broadcast service, according to one embodiment of the present disclosure.

Detailed Description of Exemplary Embodiments

[0020] The following description is presented to enable a person of ordinary skill in the art to make and use the invention. Descriptions of specific devices, techniques, and applications are provided only as examples. Various modifications to the examples described herein will be readily apparent to those of ordinary skill in the art, and the general principles defined herein may be applied to other examples and applications without departing from the spirit and scope of the invention. Thus, the present invention is not intended to be limited to the examples described herein and shown, but is to be accorded the scope consistent with the claims.

[0021] As used herein, the term "access service network" (ASN) includes without limitation any set of network functions that provide radio access to a mobile station. [0022] As used herein, the term "connectivity service network" (CSN) includes without limitation any set of network functions that provide IP connectivity services to a mobile station which has IP connectivity capability. [0023] As used herein, the term "mobile station" (MS) includes without limitation a station with mobile service intended to be used while in motion or during halts at unspecified points.

[0024] As used herein, the term "reference point" (RP) includes without limitation a conceptual link that connects two groups of functions which reside in different functional entities of an ASN, CSN, or MS. Note that a "reference point" is not necessarily required to be a physical interface.

[0025] As used herein, the term "Simple Ethernet Service" includes without limitation a service which uses non-MIP based functional entities (i.e., an Ethernet bridge in a CSN) to provide Ethernet service through a WiMAX network. The bridge attached to the CSN may provide a dedicated bridge port for each of the mobile stations anchored at the CSN.

[0026] As used herein, the term "MIP -based Ethernet Service" includes without limitation a service which deploys Mobile IP to provide a dynamic tunnel setup on RD so as to realize wide area roaming and mobility for Ethernet-CS-based terminals. Due to its dynamic behavior, the R3 interface may be fully defined for MIP -based Ethernet Services.

[0027] As used herein, the term "WiMAX network" includes without limitation a network architecture based on the IEEE 802.16 d/e wireless standard.

[0028] The word "exemplary" is used herein to mean "serving as an example or illustration." Any aspect or design described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects or designs.

[0029] Reference will now be made in detail to aspects of the subject technology, examples of which are illustrated in the accompanying drawings, wherein like reference numerals refer to like elements throughout.

[0030] It should be understood that the specific order or hierarchy of steps in the processes disclosed herein is an example of exemplary approaches. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged while remaining within the scope of the present disclosure. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

[0031] A WiMAX network, for example, can provide IP and Ethernet Services to an end user based on service provider business requirements, subscriber profiles, network architecture and network entity capability information. As will be described in more detail below, in order to provide a successful user service session, several major network entities may be involved, including, for example, an access service network (ASN), and a connectivity service network (CSN), which may include a home connectivity service network (H-CSN) and/or a visited connectivity service network (V-CSN). Each network entity may be capable of providing multiple Ethernet and IP services. Capabilities that may be associated with an ASN may include, for example, DHCPv4 Relay, DHCPvό Relay, DHCPv4 Proxy, DHCPvό Proxy, FA, PMIP Client, AR with IPv4 transport, AR with IPv6 transport, eAFF with IPv4 transport, and eAFF with iPvό transport. Capabilities that may be associated with a V-CSN may include, for example, v-DHCPv4 Server, v- DHCPvό Server, MIP-HAv4, MIP-HAvό, MIP-eHAv4, and MIP-eHAv6. [0032] An Accounting Client located at an ASN can support statistic collection for network access protection (NAP) and can provide more information than an Accounting Client located at a CSN, for example. A MCBCS Accounting Client can be co-located with an Anchor Service Flow Authorization (SFA), which is a logical entity responsible for evaluating a service request against a user's QoS profile in the case where it is downloaded from the Authentication, Authorization and Accounting (AAA), and an Accounting Agent can be used to support ASN statistic collection. The Accounting client located at the ASN can be used to support collection at the exact time when the MS authorized the service, the exact duration of the service and the volume of data usage for a specific service.

[0033] FIG. 1 is a schematic illustrating an exemplary architecture of a charging and accounting system for a wireless communication system according to one embodiment of the present invention. The wireless communication network may be a WiMAX network that complies with the Institute of Electrical and Electronics Engineers (IEEE) 802.16 communication system protocol. However, the present invention is not limited to any particular network type, and various network technologies performing service capability negotiation may be implemented without departing from the scope of the present disclosure.

[0034] According to the embodiment depicted in FIG. 1, a wireless communication network includes a mobile station 100. An ASN 120 associated with a network access provider (NAP) may provide a set of network functions that support radio access to mobile station 100. Thus, when the mobile station 100 is in close proximity to an ASN 120, the mobile station 110 may attempt to acquire Ethernet and/or IP services from the ASN 120. [0035] In some embodiments, the ASN 120 can negotiate and determine which Ethernet and/or IP services will be provided to mobile station 100 after such services have been authorized by the CSN 130. The wireless communication network of FIG. 1 may also include a V-CSN (not shown), which may act as a proxy to the CSN 130. That is, the ASN 120 may transfer IP data to CSN 130 by "tunneling" through the V-CSN. [0036] In one embodiment, the WiMAX protocol can collect the MCBCS charging/accounting information for mobile station 100 receiving the services with the support of MBS Accounting Agent 124 which can be co-located with MBS Distribution data path function (DPF) within the ASN 120.

[0037] The MBS Accounting Agent 124 is configured to collect charging/accounting information (e.g., information for a user data record (UDR)) which is keyed on one or more of the following service identifications, for the MCBCS user and/or MCBCS content provider. Of course these service identifications are merely exemplary, and various other types of identification may be implemented without departing from the scope of the present disclosure:

• Identification of the source of content (e.g., Program Packet ID)

• Type of user service (e.g. streaming, download, etc.)

• Type of transport used to deliver content (e.g. broadcast, multicast or unicast)

• Identification of subscribers (e.g. Network Access Identifier (NAI)) receiving service.

[0038] CSN 130 can be communicatively coupled to an accounting server 132 with functional capabilities performed by an AAA processor 134, Prepaid Server (PPS) 136, and Offline Charging System/Online Charging System (OFCS/OCS) 138. CSN 130 can further include a MCBCS controller/server 140 with an Accounting Client 140 of its own. [0039] FIG. 2 is an illustration of an exemplary mobile station 100 in a wireless communication network according to one embodiment of the present invention. In an exemplary embodiment, the mobile station 100 may be a user device such as a mobile phone. Alternately, mobile station 100 may be a personal digital assistant (PDA) such as a Blackberry device, MP3 player or other similar portable device. According to still other embodiments, the mobile station 100 may be a personal wireless computer such as a wireless notebook computer or a wireless palmtop computer.

[0040] As shown in FIG. 2, the exemplary mobile station 100 may include a transceiver module 200 configured to support alternate or additional wireless data communication protocols. These protocols include, without limitation, future variations of IEEE 802.16 (such as 802.16e, 802.16m, etc).

[0041] The transceiver module 200 may generally enable bi-directional communication between mobile station 100 and various network entities via antenna 230. Note that the transceiver module 200 may be configured to support internet or WiMAX traffic as well as to provide an 802.3 Ethernet interface.

[0042] In some embodiments, the mobile station 100 comprises a processor module 210 that is configured to carry out the functions, techniques, and processing tasks associated with the operation of mobile station 100. The processor module 210 may include any number of devices or device combinations as known in the art. These include, for example, general purpose processors, content addressable memory modules, digital signal processors, application-specific integrated circuits, field programmable gate arrays, programmable logic arrays, discrete gate or transistor logic, or other such electronic components.

[0043] Furthermore, the steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in firmware, in a software module executed by processor module 210, or in any practical combination thereof. A software module may reside in computer-readable storage 220, which may be realized as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. hi this regard, computer-readable storage 220 may be coupled to processor module 210 so that processor module 210 can read information from, and write information to, the computer-readable storage 220. In some embodiments, the computer-readable storage 220 includes cache memory for storing temporary variables or other intermediate information during execution of instructions by the processor module 210. In some embodiments, the computer-readable storage 220 also includes non- volatile memory. [0044] The computer-readable storage 220 may also include a frame structure database (not shown) in accordance with some embodiments of the present invention. This frame structure database may be configured to store, maintain, and provide data as needed to support the functionality of a wireless communication system. Additionally, the frame structure database may include a lookup table for purposes of storing frame structure parameters. Note that the frame structure database may consist of either a local database (e.g., coupled to the processor module 210), or a remote database (e.g., a central network database).

[0045] Fig. 3 is an illustration of an exemplary ASN 120 according to one embodiment of the present invention. The ASN 120 may include a transceiver module 300 coupled to an antenna 340, a processor module 310, and computer-readable storage 320. The transceiver module 300, the processor module 310, and the computer-readable storage 320 may be configured similarly to the transceiver module 200, the processor module 210 and computer-readable storage 220 as described above with reference to FIG. 2. The ASN 120 may additionally include an authenticator module 330 for transmitting service capability data associated with the ASN 120 to a remote module via transceiver module 300. This service capability data may be used by the CSN 130 to determine a set of Ethernet and/or IP services authorized for the mobile station 100. The processor module 310 may include the functional capability of accounting client 122 and Accounting Agent 124. Of course, any number of processors/servers may be included within ASN 120 to execute the functions described herein.

[0046] FIG. 4 is an illustration of an exemplary CSN 130 according to one embodiment of the present invention. The CSN 130 may include a transceiver module 400 communicatively coupled to antenna 440, as well as a computer-readable storage 420 with functionality similar to the transceiver module 200 and the computer-readable storage 220 as described with reference to Fig. 2. The CSN 130 may additionally include a processor module/server module 410 which may serve as the Accounting server 132 to perform functions of the AAA 134 in CSN 130. The processor module/server module 410 may further provide the functions of MCBCS controller/server 140. Note that the processor module/server module 410 may be implemented similarly to processor module 210 described above with reference to Fig. 2. [0047] If the CSN comprises a V-CSN, a proxy authenticator module 430 may also be included. In one embodiment, the proxy authenticator module 430 is adapted to transmit ASN 120 service capability data and V-CSN service capability data to the CSN 130. The CSN 130 may then transmit authorization data to the V-CSN proxy authenticator module upon determining a set of authorized Ethernet and/or IP services for the mobile station 100. This data may then be forwarded by the proxy authenticator module 430 to the ASN 120 for local storage.

[0048] Of course, one of ordinary skill in the art would realize that the above- described mobile station 100, the above described ASN 120, and the above described CSN 130 are merely exemplary in nature. Various other components and component combinations may also be utilized without departing from the scope of the present disclosure.

[0049] FIG. 5 is a graphical illustration of various exemplary levels and identifiers for charging and accounting for multicast and broadcast services, according to one embodiment of the present invention. This section details the terminology and accounting modes used in WiMAX MCBCS, for example.

[0050] As shown in FIG. 5, a subscriber 500 may be identifiable using one or more subscription(s) 510(1) to 510(n) based on a network access identifier (NAI). Each subscription 510(1) to 510(n) may be charged based on one or more identifiable program package(s) 520(1) to 520(n), which may be identifiable by corresponding program package IDs. Each program package 520(1) to 520(n) may be associated with chargeable services 530(1) to 53O(n), which are identifiable based on multicast addresses and/or service IDs.

[0051] As described above, the MBS Accounting Agent 124 (at ASN 120) is configured to collect charging/accounting information (e.g., information for a user data record (UDR)) which is keyed on one or more of these service identifications, for the MCBCS user and/or MCBCS content provider.

[0052] In one embodiment, MCBCS charging/accounting support can be partitioned into service-based charging/accounting and access-based charging/accounting. For the service-based charging/accounting, service may be charged either by subscription or flat rate. [0053] In one embodiment, charging/accounting associated with the service-based option can be treated independently from the charging/accounting associated with the access-based option. Alternatively, if the service-based option is implemented, the access- based option can be applied in addition as a charging/accounting operation. [0054] Table 1 below shows charging and accounting requirements for service delivery, according to various exemplary embodiments:

Table 1

[0055] In one embodiment, for access-based accounting, charges may be based on the session information (e.g. QoS, media type, and/or MCBCS service coverage within ASN 120) as described below. Of course various other types of charges based on session information may be obtained without departing from the scope of the present disclosure:

• Session duration (time from Session-Start and Session-Stop functions performed at mobile station 100, for example);

• Volume of data during the MCBCS programming session;

• Duration of time while mobile station 100 is registered to receive the MCBCS service or is between the joining/leaving the MCBCS service; and/or

• Volume of data transferred while mobile station 100 is registered to receive the MCBCS or is between the joining/leaving the MCBCS service.

[0056] Table 2 below shows exemplary applicability of various charging mechanisms, according to various embodiments:

Table 2

[0057] In one embodiment, in the case of service-based accounting, the accounting triggers could be made by a Session Controller {e.g. performing Session-Start or Session- Stop functions) or mobile station 100 events {e.g. Join or Leave functions initiated by a user of mobile station 100, for example). If a large volume of users is expected to use the MCBCS service, generating the charging/accounting information {e.g. UDR) can be performed in a manner that ensures the charging entities and billing domain are not overloaded.

[0058] Hence, according to an embodiment, the MBS Accounting Client 122 generates the UDR and then redistributes the information to the corresponding mobile station's 100 associated Accounting Client if per-MS 100 accounting is enabled. The mobile station's 100 associated Accounting Client may or may not be the same as MBS Accounting Client 122, although the mobile station's 100 associated Accounting Client can be located within the ASN 120. A UDR generated by MBS Accounting Client 122 may be only for MCBCS services, according to certain embodiments, and the mobile station's 100 associated Accounting Client may be used for all the services for the mobile station 100.

[0059] In one embodiment, if there is no per-MS trigger for the accounting event in the case of the MCBCS broadcast services, the statistic collection and the accounting for the MCBCS broadcast services may be dependent on the session duration and/or the volume count within the MCBCS programming session. [0060] Unlike the MCBCS broadcast service, the MCBCS multicast services can be based on user subscription or flat rate; and if user subscription is chosen, any of the four access-based options as described above can be applied for the charging/accounting operation, for example.

[0061] Online charging and accounting support may not be applicable for the MCBCS broadcast service. As for charging for the MCBCS multicast service applicability to the

MS, it may be fee-for-service (FFS).

[0062] MCBCS charging data record (CDR) for the user can be opened for collection as soon as mobile station 100 is triggered by an Accounting-Start or ACR(Start) function

(initiated, e.g., by Accounting Client 122 in ASN 120) once the user has completed the successful network entry. The volume for the MCBCS CDR for the user may be counted in the downlink direction only.

[0063] MCBCS UDR for a content provider can be opened for collection as soon as a

Session Start function is initiated, which triggers Account-Start or ACR(Start) for the given MCBCS service. The volume for the content provider may be counted in the downlink direction only.

[0064] FIG. 6 is an exemplary flow diagram illustrating a method of charging and accounting for multicast and broadcast service, triggered by mobile station's 100 joint/leave function, according to one embodiment of the present invention.

[0065] At operation 600, mobile station 100 sends a join trigger to ASN 120, to indicate that it is interested in joining one or more MCBCS services. After mobile station

100 gets authorization and successfully initiated a DSx procedure, it will trigger the

Accounting Client 122 to start the accounting process.

[0066] At operation 610, the Accounting Client 122, upon receiving this join trigger, sends an accounting request/start message to the AAA 134 at CSN 140 to start the accounting process. AAA 134 then sends an Accounting response message to Accounting

Client 122 and the Accounting Client 122 will start to create an UDR, at operation 620.

[0067] At operation 630, while the user is enjoying the MCBCS service, the

Accounting Client 122 may send an Accounting Request to update the accounting information periodically. At operation 640, the AAA 134 may return an interim accounting update, if necessary, according to certain embodiments. [0068] If mobile station 100 is not interested in one or more MCBCS services, mobile stations 100 can send a leaving message to Accounting Client 122, at operation 650. Upon receiving the leaving successful trigger, Accounting Client 122 will generate a UDR record and send an Accounting request stop message (operation 660) to stop the accounting session. AAA 134 may respond back by sending an Accounting Respons Stop message, at operation 670.

[0069] While various embodiments of the invention have been described above, it should be understood that they have been presented by way of example only, and not by way of limitation. Likewise, the various diagrams may depict an example architectural or other configuration for the disclosure, which is done to aid in understanding the features and functionality that can be included in the disclosure. The disclosure is not restricted to the illustrated example architectures or configurations, but can be implemented using a variety of alternative architectures and configurations. Additionally, although the disclosure is described above in terms of various exemplary embodiments and implementations, it should be understood that the various features and functionality described in one or more of the individual embodiments are not limited in their applicability to the particular embodiment with which they are described. They instead can be applied alone or in some combination, to one or more of the other embodiments of the disclosure, whether or not such embodiments are described, and whether or not such features are presented as being a part of a described embodiment. Thus the breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments.

[0070] In this document, the term "module" as used herein, refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purpose of discussion, the various modules are described as discrete modules; however, as would be apparent to one of ordinary skill in the art, two or more modules may be combined to form a single module that performs the associated functions according embodiments of the invention.

[0071] In this document, the terms "computer program product", "computer-readable medium", and the like, may be used generally to refer to media such as, memory storage devices, or storage unit. These, and other forms of computer-readable media, may be involved in storing one or more instructions for use by processor to cause the processor to perform specified operations. Such instructions, generally referred to as "computer program code" (which may be grouped in the form of computer programs or other groupings), when executed, enable the computing system.

[0072] It will be appreciated that, for clarity purposes, the above description has described embodiments of the invention with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processors or domains may be used without detracting from the invention. For example, functionality illustrated to be performed by separate processors or controllers may be performed by the same processor or controller. Hence, references to specific functional units are only to be seen as references to suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.

[0073] Terms and phrases used in this document, and variations thereof, unless otherwise expressly stated, should be construed as open ended as opposed to limiting. As examples of the foregoing: the term "including" should be read as meaning "including, without limitation" or the like; the term "example" is used to provide exemplary instances of the item in discussion, not an exhaustive or limiting list thereof; and adjectives such as "conventional," "traditional," "normal," "standard," "known", and terms of similar meaning, should not be construed as limiting the item described to a given time period, or to an item available as of a given time. But instead these terms should be read to encompass conventional, traditional, normal, or standard technologies that may be available, known now, or at any time in the future. Likewise, a group of items linked with the conjunction "and" should not be read as requiring that each and every one of those items be present in the grouping, but rather should be read as "and/or" unless expressly stated otherwise. Similarly, a group of items linked with the conjunction "or" should not be read as requiring mutual exclusivity among that group, but rather should also be read as "and/or" unless expressly stated otherwise. Furthermore, although items, elements or components of the disclosure may be described or claimed in the singular, the plural is contemplated to be within the scope thereof unless limitation to the singular is explicitly stated. The presence of broadening words and phrases such as "one or more," "at least," "but not limited to", or other like phrases in some instances shall not be read to mean that the narrower case is intended or required in instances where such broadening phrases may be absent.

[0074] Additionally, memory or other storage, as well as communication components, may be employed in embodiments of the invention. It will be appreciated that, for clarity purposes, the above description has described embodiments of the invention with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processing logic elements or domains may be used without detracting from the invention. For example, functionality illustrated to be performed by separate processing logic elements, or controllers, may be performed by the same processing logic element, or controller. Hence, references to specific functional units are only to be seen as references to suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.

[0075] Furthermore, although individually listed, a plurality of means, elements or method steps may be implemented by, for example, a single unit or processing logic element. Additionally, although individual features may be included in different claims, these may possibly be advantageously combined. The inclusion in different claims does not imply that a combination of features is not feasible and/or advantageous. Also, the inclusion of a feature in one category of claims does not imply a limitation to this category, but rather the feature may be equally applicable to other claim categories, as appropriate.

Claims

WHAT IS CLAIMED IS:

1. A method of charging and accounting for multicast and broadcast service (MCBCS), comprising: collecting identification information from a mobile station receiving a MCBCS by an accounting agent located at an access service network (ASN); collecting service identification information of an MCBCS content provider by the accounting agent; creating a usage detail record based on the identification information of the mobile station and the service identification information of the MCBCS content provider collected at the ASN; and generating charging and accounting information based on the usage detail record.

2. The method of claim 1 , wherein the identification information of the mobile station receiving the MCBCS includes an identification of a subscriber.

3. The method of claim 1, wherein the service identification information of the MCBCS content provider is at least one of a program packet identifier, a type of the MCBCS, and a type of transport used to deliver content by the MCBCS.

4. The method of claim 1, wherein the charging and accounting information includes information related to access-based charging.

5. The method of claim 1 , wherein the charging and accounting information includes information related to service-based charging.

6. The method of claim 1 , further comprising triggering the charging and accounting of the MCBCS, using a session control or a mobile station event.

7. The method of claim 4, wherein the access-based charging is based on at least one of session duration, data volume during a MCBCS programming session, duration of time while the mobile station is registered to receive the MCBCS, and volume of data transferred while the mobile station is registered to receive the MCBCS.

8. A system for charging and accounting for multicast and broadcast service (MCBCS), comprising: an accounting agent located at an access service network (ASN) configured to collect identification information from a mobile station receiving a MCBCS and service identification information of an MCBCS content provider; an accounting client in the ASN configured to create a usage detail record based on the identification information of the mobile station and the service identification information of the MCBCS content provider; and a generating unit configured to generate charging and accounting information based on the usage detail record.

9. The system of claim 8, wherein the identification information of the mobile station receiving the MCBCS includes an identification of a subscriber.

10. The system of claim 8, wherein the service identification information of the MCBCS content provider is at least one of a program packet identifier, a type of the MCBCS, and a type of transport used to deliver content by the MCBCS.

11. The system of claim 8, wherein the charging and accounting information includes information related to access-based charging.

12. The system of claim 8, wherein the charging and accounting information includes information related to service-based charging.

13. The method of claim 8, further comprising a trigger unit configured to trigger the charging and accounting of the MCBCS, using a session control or a mobile station event.

14. The system of claim 11 , wherein the access-based charging is based on at least one of session duration, data volume during a MCBCS programming session, duration of time while the mobile station is registered to receive the MCBCS, and volume of data transferred while the mobile station is registered to receive the MCBCS.

15. An access service network capable of performing charging and accounting for multicast and broadcast service (MCBCS), comprising: means for collecting identification information from a mobile station receiving a MCBCS and service identification information of an MCBCS content provider; means for creating a usage detail record based on the identification information of the mobile station and the service identification information of the MCBCS content provider; and means for generating charging and accounting information based on the usage detail record.

16. The access service network of claim 15, wherein the identification information of the mobile station receiving the MCBCS includes an identification of a subscriber.

17. The access service network of claim 15, wherein the service identification information of the MCBCS content provider is at least one of a program packet identifier, a type of the MCBCS, and a type of transport used to deliver content by the MCBCS.

18. The access service network of claim 15, wherein the charging and accounting information includes information related to access-based charging.

19. The access service network of claim 15, wherein the charging and accounting information includes information related to service-based charging.

20. The access service network of claim 15, further comprising means for triggering the charging and accounting of the MCBCS, using a session control or a mobile station event.

21. The access service network of claim 18, wherein the access-based charging is based on at least one of session duration, data volume during a MCBCS programming session, duration of time while the mobile station is registered to receive the MCBCS, and volume of data transferred while the mobile station is registered to receive the MCBCS.

22. A computer-readable medium storing instructions thereon configured to, when executed by a processor, perform a method of charging and accounting for multicast and broadcast service (MCBCS), comprising: collecting identification information from a mobile station receiving a MCBCS by an accounting agent located at an access service network (ASN); collecting service identification information of an MCBCS content provider by the accounting agent; creating a usage detail record based on the identification information of the mobile station and the service identification information of the MCBCS content provider collected at the ASN; and generating charging and accounting information based on the usage detail record.

23. The computer-readable medium of claim 22, wherein the identification information of the mobile station receiving the MCBCS includes an identification of a subscriber.

24. The computer-readable medium of claim 22, wherein the service identification information of the MCBCS content provider is at least one of a program packet identifier, a type of the MCBCS, and a type of transport used to deliver content by the MCBCS.

25. The computer-readable medium of claim 22, wherein the charging and accounting information includes information related to access-based charging.

26. The computer-readable medium of claim 22, wherein the charging and accounting information includes information related to service-based charging.

27. The computer-readable medium of claim 22, the method further comprising triggering the charging and accounting of the MCBCS, using a session control or a mobile station event.

28. The computer-readable medium of claim 25, wherein the access-based charging is based on at least one of session duration, data volume during a MCBCS programming session, duration of time while the mobile station is registered to receive the MCBCS, and volume of data transferred while the mobile station is registered to receive the MCBCS.