WO2016011831A1 - 计费方法和设备、接入设备、服务质量控制方法和设备 - Google Patents

计费方法和设备、接入设备、服务质量控制方法和设备 Download PDF

Info

Publication number
WO2016011831A1
WO2016011831A1 PCT/CN2015/075984 CN2015075984W WO2016011831A1 WO 2016011831 A1 WO2016011831 A1 WO 2016011831A1 CN 2015075984 W CN2015075984 W CN 2015075984W WO 2016011831 A1 WO2016011831 A1 WO 2016011831A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
traffic
content
service
request
Prior art date
Application number
PCT/CN2015/075984
Other languages
English (en)
French (fr)
Inventor
杨恩锋
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to JP2017503587A priority Critical patent/JP6552068B2/ja
Priority to EP15824591.0A priority patent/EP3163795B1/en
Priority to BR112017001250A priority patent/BR112017001250A2/pt
Priority to EP18155765.3A priority patent/EP3410634A1/en
Publication of WO2016011831A1 publication Critical patent/WO2016011831A1/zh
Priority to US15/411,631 priority patent/US10700879B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5019—Ensuring fulfilment of SLA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
    • H04L65/612—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1453—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network
    • H04L12/1467—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network involving prepayment

Definitions

  • the present invention relates to charging and quality of service control technologies, and more particularly to charging methods and devices, access devices, service quality control methods, and devices.
  • the rapid development of network transmission technology has made the content available through the Internet more and more abundant. For example, users can read news, listen to music, and watch movies over the Internet. With the latest network transmission technology, the content provided by the content provider site (ie content source) can be transmitted to the user terminal with very low latency.
  • the content provider site ie content source
  • the telecom operator can develop a special traffic package for the cooperating content provider. By ordering the traffic package, the traffic generated when the user obtains the content from the content provider site will be separately counted into the above traffic package.
  • the telecommunications carrier can analyze the content request sent by the user to obtain information related to the content provider site. For example, the telecommunications carrier can analyze the IP (Internet Protocol) address pointed to by the content request to determine the site to which the content request is directed, that is, the content provider site, so that the content can be determined according to the content provider site. Provider.
  • IP Internet Protocol
  • the telecommunication operator can also determine the content provider site by analyzing the URL, and then determine the content according to the content provider site. Provider. In this way, the telecom operator can enter the flow meter generated by the requested content into the user-defined traffic plan for the content provider.
  • URL Uniform/Universal Resource Locator
  • the circle of friends provided by WeChat allows users to access content shared by friends, such as articles, pictures, songs and movies.
  • the friend can embed an access portal of the video content in the circle of friends, and the access portal can be displayed as a video play window in the circle of friends.
  • the WeChat requests the video content from the content provider site that provides the video content, and plays the obtained video content in the video play window.
  • the content provider that provides the above video content is likely not to develop WeChat's service provider Tencent, so the access request for the above video content may not point to Tencent's site.
  • WeChat's service provider Tencent the access request for the above video content may not point to Tencent's site.
  • the access request for the above video content may not point to Tencent's site.
  • WeChat requests the video content from the Youku website, instead of requesting the video content from the Tencent website.
  • the traffic generated by the video content It should be included in the traffic plan corresponding to WeChat.
  • the traffic generated when the user accesses the content through the social application may not be counted in the traffic package corresponding to the social application.
  • an access device is provided, and the flow meter generated when the content accessed by the application is generated can be input into the corresponding data package of the application.
  • a billing device which can generate a flow meter generated by the application to access the corresponding data package of the application.
  • a service quality control method that can apply the quality of service applied to an application to content accessed through an application.
  • a service quality control method which can update the accumulated traffic of the application as the traffic generated by the application as the traffic generated by the application, so as to determine the service quality of the application according to the updated cumulative traffic.
  • an access device that can apply the quality of service applied to an application to content accessed through an application.
  • a service quality control device which can update the accumulated traffic of the application as the traffic generated by the application as the traffic generated by the application, so as to determine the service quality of the application according to the updated cumulative traffic.
  • a charging method including:
  • the content request carries a content identifier and an application identifier, where the content identifier is used to identify the requested content, and the application identifier is used to identify the application and is used to identify that the content request is triggered by the application;
  • the charging request is a credit control request CCR
  • the application is indicated by a service identifier service identifier carried in the credit control request.
  • the charging request is a credit control request CCR, and the Indicated by the application parameters carried in the credit control request.
  • the traffic is indicated by the used traffic USU carried in the credit control request, and the credit control request further carries a service identifier service identifier for indicating the content, so that
  • the billing device generates a consumption record according to the application, the content, and the traffic, wherein the consumption record is used to indicate that the traffic is generated by the content, and the content is requested by the application And the traffic is charged as traffic generated by the application.
  • the method further includes determining a content source of the content, the traffic being indicated by the used traffic volume USU carried in the credit control request, the credit control request further carrying Instructing the service identifier service identifier of the content source, so that the charging device generates a consumption record according to the application, the content source, and the traffic, wherein the consumption record is used to indicate that the traffic is in an access
  • the access to the content source generated by the content source is triggered by the application, and the traffic is charged as the traffic generated by the application.
  • a charging method for charging traffic generated by content requested by an application, including:
  • the traffic is charged as traffic generated by the application.
  • the charging request is a credit control request CCR
  • the application is indicated by an application parameter carried in the credit control request.
  • the traffic is indicated by the used traffic USU carried in the credit control request, and the credit control request further carries a service identifier service identifier for indicating the content
  • the method further includes generating a consumption record according to the application, the content, and the traffic, wherein the consumption record is used to indicate that the traffic is generated by the content, and the content is requested by the application And the traffic is charged as traffic generated by the application.
  • the traffic is indicated by the used traffic volume USU carried in the credit control request, and the credit control request further carries a service identifier service identifier for indicating a content source of the content
  • the method further includes generating a consumption record according to the application, the content source, and the traffic, wherein the consumption record is used to indicate that the traffic is in progress
  • access to the content source is triggered by the application, and the traffic is charged as traffic generated by the application.
  • an access device including:
  • a receiving module configured to receive a content request, where the content request carries a content identifier and an application identifier, where the content identifier is used to identify the requested content, and the application identifier is used to identify the application and is used to identify the content request
  • the application triggers
  • the charging module is configured to send a charging request indicating the traffic and the application to the charging device, so that the charging device performs charging by using the traffic as the traffic generated by the application.
  • the charging request is a credit control request CCR
  • the application is indicated by a service identifier service identifier carried in the credit control request.
  • the charging request is a credit control request CCR
  • the application is indicated by an application parameter carried in the credit control request.
  • the traffic is indicated by the used traffic USU carried in the credit control request, and the credit control request further carries a service identifier service identifier for indicating the content, so that
  • the billing device generates a consumption record according to the application, the content, and the traffic, wherein the consumption record is used to indicate that the traffic is generated by the content, and the content is requested by the application And the traffic is charged as traffic generated by the application.
  • the device further includes a determining module for determining a content source of the content, the traffic being indicated by the used traffic USU carried in the credit control request, the credit control request And carrying a service identifier service identifier for indicating the content source, so that the billing device generates a consumption record according to the application, the content source, and the traffic, wherein the consumption record is used to indicate The traffic is generated when the content source is accessed, the access to the content source is triggered by the application, and the traffic is charged as traffic generated by the application.
  • a determining module for determining a content source of the content, the traffic being indicated by the used traffic USU carried in the credit control request, the credit control request And carrying a service identifier service identifier for indicating the content source, so that the billing device generates a consumption record according to the application, the content source, and the traffic, wherein the consumption record is used to indicate The traffic is generated when the content source is accessed, the access to the content source is triggered by the application, and the traffic is charged as traffic generated
  • a fourth aspect provides a charging device for charging traffic generated by content requested by an application, including:
  • a receiving module configured to receive a charging request sent by the access device, indicating the application and the traffic
  • the charging module is configured to charge the traffic as the traffic generated by the application.
  • the charging request is a credit control request CCR
  • the application is indicated by an application parameter carried in the credit control request.
  • the traffic is indicated by the used traffic volume USU carried in the credit control request, and the credit control request further carries a service identifier service identifier for indicating the content
  • the device A generating module is further configured to generate a consumption record according to the application, the content, and the traffic, wherein the consumption record is used to indicate that the traffic is generated by the content, and the content is The application is requested, and the traffic is charged as traffic generated by the application.
  • the traffic is indicated by the used traffic volume USU carried in the credit control request, and the credit control request further carries a service identifier service identifier for indicating a content source of the content
  • the device further includes a generating module, configured to generate a consumption record according to the application, the content source, and the traffic, wherein the consumption record is used to indicate that the traffic is generated when accessing the content source
  • the access to the content source is triggered by the application, and the traffic is charged as traffic generated by the application.
  • a method for controlling quality of service including:
  • the content request carries a content identifier and an application identifier, where the content identifier is used to identify the requested content, and the application identifier is used to identify the application and is used to identify that the content request is triggered by the application;
  • the method further includes:
  • the quality of service control request is a credit control request CCR, and the application is indicated by a service identifier service identifier carried in the credit control request.
  • the quality of service control request is a credit control request CCR
  • the application is indicated by an application parameter carried in the credit control request.
  • a sixth aspect provides a service quality control method for determining a service quality of an application, where a request for content is triggered by the application, and the method includes:
  • the quality of service control request is a credit control request CCR
  • the application is indicated by an application parameter carried in the credit control request.
  • an access device including:
  • a content request receiving module configured to receive a content request, where the content request carries a content identifier and an application identifier, where the content identifier is used to identify the requested content, and the application identifier is used to identify the application and is used to identify the content
  • the request is triggered by the application
  • a service quality determining module configured to determine a service quality corresponding to the application
  • the device further includes:
  • a traffic determining module configured to determine traffic generated by the content
  • a sending module configured to send, to the quality of service control device, a quality of service control request indicating the traffic and the application, so that the quality of service control device updates the application as the traffic generated by the application flow;
  • the service quality receiving module is configured to receive the quality of service determined by the service quality control device according to the updated cumulative traffic.
  • the quality of service control request is a credit control request CCR, and the application is indicated by a service identifier service identifier carried in the credit control request.
  • the quality of service control request is a credit control request CCR
  • the application is indicated by an application parameter carried in the credit control request.
  • the eighth aspect provides a service quality control device, configured to determine a service quality of an application, where a request for content is triggered by the application, where the device includes:
  • a receiving module configured to receive, by the access device, the traffic generated by the content and the response Service quality control request
  • An update module configured to update the cumulative traffic of the application by using the traffic as the traffic generated by the application
  • a determining module configured to determine a quality of service of the application according to the updated cumulative traffic
  • the quality of service control request is a credit control request CCR
  • the application is indicated by an application parameter carried in the credit control request.
  • the embodiment of the present invention obtains an application indicated by the application identifier according to the application identifier carried in the content request, and the content request is triggered by the application. In this way, the embodiment of the present invention can send the traffic generated by the requested content and the charging request of the application to the charging device, so as to enable the charging device to charge the traffic generated by the application as the application. purpose.
  • FIG. 1 is an exemplary flowchart of a charging method according to an embodiment of the present invention
  • FIG. 2 is an exemplary flowchart of a charging method according to an embodiment of the present invention.
  • FIG. 3 is an exemplary signaling diagram of a charging method in accordance with an embodiment of the present invention.
  • FIG. 4 is a schematic diagram showing an exemplary logical structure of an access device according to an embodiment of the invention.
  • FIG. 5 is a schematic diagram showing an exemplary logical structure of a charging device according to an embodiment of the present invention.
  • FIG. 6 is a schematic diagram showing an exemplary logical structure of a charging system according to an embodiment of the present invention.
  • FIG. 7 is an exemplary flowchart of a method for controlling quality of service according to an embodiment of the present invention.
  • FIG. 8 is an exemplary flowchart of a method for controlling quality of service according to an embodiment of the present invention.
  • FIG. 9 is an exemplary signaling diagram of a quality of service control method in accordance with an embodiment of the present invention.
  • FIG. 10 is a schematic diagram showing an exemplary logical structure of an access device according to an embodiment of the invention.
  • FIG. 11 is a schematic diagram showing an exemplary logical structure of a quality of service control device according to an embodiment of the present invention.
  • FIG. 12 is a schematic diagram showing an exemplary logical structure of a quality of service control system according to an embodiment of the present invention.
  • FIG. 13 is a schematic structural diagram of hardware of an access device according to an embodiment of the invention.
  • the charging method 100 can be performed by, for example, but not limited to, an access device.
  • the access device may be, for example but not limited to, a GGSN (Gateway GPRS (General Packet Radio Service) Support Node, a Gateway GPRS Support Node).
  • GGSN Gateway GPRS (General Packet Radio Service) Support Node
  • Gateway GPRS Support Node a Gateway GPRS Support Node
  • Step 102 Receive a content request, where the content request carries a content identifier and an application identifier, where the content identifier is used to identify the requested content, and the application identifier is used to identify the application and is used to identify the content request by using the Application trigger.
  • the content request is from, for example, but not limited to, a user terminal, such as various mobile terminals. More specifically, the above content request is triggered by an application running on the user terminal.
  • the content identifier may be, for example, but not limited to, a URL of content carried in the content request, or information obtained from the URL that can be used to identify the content.
  • Step 104 returning the content and determining the traffic generated by the content.
  • Step 106 Send a charging request indicating the traffic and the application to the charging device, so that the charging device charges the traffic as the traffic generated by the application.
  • the charging request may be a credit control request (CCR), and the application indicates by using a service identifier service identifier carried in the credit control request.
  • CCR credit control request
  • the information carried in the service identifier is not information indicating the content, such as the content identifier described above, but information indicating the application, such as the application identifier described above.
  • the charging request is also a credit control request, but the application is indicated by an application parameter carried in the credit control request.
  • the application parameter is a new parameter, and the information carried in the parameter will be information indicating the application, such as the application identifier.
  • the application can be indicated in the credit control request in two ways.
  • the first way is to use the service identifier service identifier indication carried in the credit control request
  • the second way is to use the application parameter indication carried in the credit control request. It is not difficult to understand that since the service identifier service identifier already exists in the existing credit control request, the first method does not require modification of the existing credit control request. However, in the second mode, since the application parameters are new parameters, the existing credit control request needs to be modified.
  • the charging request is a credit control request and the application is carried in the credit control request
  • the application parameter indicates, the traffic is indicated by a used service unit (USU) carried in the credit control request.
  • the credit control request further carries a service identifier service identifier for indicating the content, so that the charging device generates a consumption record according to the application, the content, and the traffic, where The consumption record is used to indicate that the traffic is generated by the content, the content is requested by the application, and the traffic is charged as traffic generated by the application.
  • the service identifier carries information for indicating the content such as the above-described content identifier, and is not information for indicating the application such as the above-described application identifier.
  • the service identifier service identifier carried in the credit control request may also be used to indicate the content source of the content, not the content.
  • the billing device can generate another type of consumption record.
  • the method 100 may further include determining a content source of the content.
  • the traffic is indicated by the used traffic volume USU carried in the credit control request, and the credit control request further carries a service identifier service identifier for indicating the content source, so that the charging device according to the Generating a consumption record by using the application, the content source, and the traffic, wherein the consumption record is used to indicate that the traffic is generated when accessing the content source, and access to the content source is by The application is triggered, and the traffic is charged as traffic generated by the application.
  • the service identifier carries information indicating the content source of the content, such as the name of the content source, the domain name, and the like, instead of the information for indicating the application, such as the above-mentioned application identifier, and is not used.
  • the information indicating the content is, for example, the above content identification.
  • the content source of the content may be determined according to an IP address pointed to by the content request.
  • the content request typically contains the URL of the requested content, the content source can also be determined by analyzing the URL.
  • the charging device in step 106 uses the traffic as the traffic generated by the application, and the charging device sends the flow meter into the traffic package corresponding to the application. It can be seen that, because the traffic is counted in the traffic plan corresponding to the application, instead of counting the traffic package corresponding to the content provider corresponding to the content, the present invention can achieve the traffic generated by using the traffic as the application. The purpose of the fee.
  • the embodiment of the present invention obtains an application indicated by the application identifier according to the application identifier carried in the content request, and the content request is triggered by the application. In this way, the embodiment of the present invention can send the traffic generated by the requested content and the charging request of the application to the charging device, so as to enable the charging device to charge the traffic generated by the application as the application. purpose.
  • FIG. 2 is an exemplary flow diagram of a charging method 200 in accordance with an embodiment of the present invention.
  • the charging method 200 shown in FIG. 2 is used to charge the traffic generated by the content requested by the application.
  • the charging method 200 can be performed by, for example, but not limited to, a billing device.
  • the foregoing charging device may be, for example but not limited to, an OCS (Online Charging System).
  • Step 202 Receive a charging request sent by the access device to indicate the application and the traffic.
  • the charging request is a credit control request CCR
  • the application is indicated by an application parameter carried in the credit control request.
  • the application parameter is a new parameter
  • the information carried in the parameter will be information indicating the application, such as the application identifier. It is not difficult to understand that since the application parameters are a new parameter, the existing credit control request needs to be modified.
  • Step 204 Perform the charging as the traffic generated by the application.
  • charging the traffic as the traffic generated by the application refers to loading the flowmeter into a traffic package corresponding to the application. It can be seen that, because the traffic is counted in the traffic plan corresponding to the application, instead of counting the traffic package corresponding to the content provider corresponding to the content, the present invention can achieve the traffic generated by using the traffic as the application. The purpose of the fee.
  • the charging request is a credit control request CCR and the application indicates by the application parameter carried in the credit control request
  • the traffic is indicated by the used traffic USU carried in the credit control request
  • the credit control The request further carries a service identifier service identifier for indicating the content
  • the method 200 may further include generating a consumption record according to the application, the content, and the traffic, wherein the consumption record is used to indicate The traffic is generated by the content, the content is requested by the application, and the traffic is charged as traffic generated by the application.
  • the service identifier service identifier carried in the credit control request may also be used to indicate the content Content source, not the content.
  • the billing device can generate another type of consumption record.
  • the charging request is a credit control request CCR and the application indicates by the application parameter carried in the credit control request
  • the traffic is indicated by the used traffic USU carried in the credit control request
  • the credit control request further carries a service identifier service identifier for indicating a content source of the content
  • the method 200 may further include: generating a consumption record according to the application, the content source, and the traffic, wherein The consumption record is used to indicate that the traffic is generated when the content source is accessed, the access to the content source is triggered by the application, and the traffic is performed as the traffic generated by the application. Billing.
  • the embodiment of the present invention obtains an application indicated by the application identifier according to the application identifier carried in the content request, and the content request is triggered by the application. In this way, the embodiment of the present invention can send the traffic generated by the requested content and the charging request of the application to the charging device, so as to enable the charging device to charge the traffic generated by the application as the application. purpose.
  • FIG. 3 is an exemplary signaling diagram of a charging method 300 in accordance with an embodiment of the present invention.
  • the mobile terminal shown in FIG. 3 may be a computing device with an Internet access function, such as, but not limited to, a personal digital assistant, a smart phone, a tablet computer, etc., and the mobile terminal runs an application through which the user can trigger a content request. In order to access the content.
  • the GGSN corresponds to the access devices in methods 100 and 200
  • the OCS corresponds to the charging devices in methods 100 and 200.
  • Step 302 The user triggers a content request by using an application running on the mobile terminal, where the content request carries a content identifier and an application identifier, where the content identifier is used to identify the requested content, and the application identifier is used to identify the application.
  • the request for identifying the content is triggered by the application. Details of technical features such as content request, content identification, and application identification have been described in detail above in connection with method 100 and method 200, and thus are not described herein.
  • Step 304 The GGSN obtains the content of the request according to the content identifier, and determines the traffic generated by the content.
  • step 306 the GGSN returns the requested content to the mobile terminal.
  • Step 308 The GGSN sends a charging request indicating the foregoing traffic and an application to the charging device.
  • Step 310 The charging device charges the traffic as the traffic generated by the application according to the application and the traffic indicated in the charging request, that is, the charging device puts the flowmeter into the traffic corresponding to the application. meal.
  • the sequence of some steps in the method 300 may be set according to specific needs.
  • the operation of determining the traffic generated by the content in step 304 may be performed after step 306 and before step 308.
  • method 300 can also include the step of generating a consumption record, which has been described in detail above in connection with method 100 and method 200, and thus will not be described again herein.
  • the GGSN in the method 300 described in connection with FIG. 3 corresponds to the access devices in the methods 100 and 200
  • the OCS corresponds to the charging devices in the methods 100 and 200.
  • the specific operation of each device, each device, and the specific details involved in each device and its operation have been described in detail above in connection with Figures 1 and 2, and will also be described below in conjunction with Figures 4-6. Further description is made.
  • FIG. 4 is a schematic diagram showing an exemplary logical structure of an access device 400 according to an embodiment of the invention. As shown in FIG. 4, the access device 400 includes a receiving module 402, a return module 404, and a billing module 406.
  • the receiving module 402 is configured to receive a content request, where the content request carries a content identifier and an application identifier, where the content identifier is used to identify the requested content, and the application identifier is used to identify the application and is used to identify the content request
  • the application triggers.
  • the return module 404 is configured to return the content and determine the traffic generated by the content.
  • the charging module 406 is configured to send a charging request indicating the traffic and the application to the charging device, so that the charging device charges the traffic as the traffic generated by the application.
  • the content request is from, for example, but not limited to, a user terminal, such as various mobile terminals. More specifically, the above content request is triggered by an application running on the user terminal.
  • the content identifier may be, for example, but not limited to, a URL of the content carried in the content request, or information obtained by the receiving module 402 from the URL and used to identify the content.
  • the charging request may be a credit control request (CCR), and the application is indicated by a service identifier service identifier carried in the credit control request.
  • CCR credit control request
  • the information carried in the service identifier is not information indicating the content, such as the content identifier described above, but information indicating the application, such as the application identifier described above.
  • the charging request is also a credit control request CCR, but the application is indicated by an application parameter carried in the credit control request.
  • the application parameter is a new parameter, and the information carried in the parameter will be information indicating the application, such as the application identifier.
  • the application can be indicated in the credit control request in two ways.
  • the first way is to use the service identifier service identifier indication carried in the credit control request
  • the second way is to use the application parameter indication carried in the credit control request. It is not difficult to understand that since the service identifier service identifier already exists in the existing credit control request, the first method does not require modification of the existing credit control request. However, in the second mode, since the application parameters are new parameters, the existing credit control request needs to be modified.
  • the charging request is a credit control request CCR and the application indicates by the application parameter carried in the credit control request
  • the traffic is indicated by the used traffic USU carried in the credit control request.
  • the credit control request further carries a service identifier service identifier for indicating the content, so that the charging device generates a consumption record according to the application, the content, and the traffic, where The consumption record is used to indicate that the traffic is generated by the content, the content is requested by the application, and the traffic is charged as traffic generated by the application.
  • the service identifier carries information for indicating the content such as the above-described content identifier, and is not information for indicating the application such as the above-described application identifier.
  • the service identifier service identifier carried in the credit control request may also be used to indicate the content source of the content, not the content.
  • the billing device can generate another type of consumption record.
  • the access device 400 may further include a determining module (not shown in FIG. 4). A content source for determining the content.
  • the traffic is indicated by the used traffic volume USU carried in the credit control request, and the credit control request further carries a service identifier service identifier for indicating the content source, so that the charging device according to the Generating a consumption record by using the application, the content source, and the traffic, wherein the consumption record is used to indicate that the traffic is generated when accessing the content source, and access to the content source is by The application is triggered, and the traffic is charged as traffic generated by the application.
  • the service identifier carries information indicating the content source of the content, such as the name of the content source, the domain name, and the like, instead of the information for indicating the application, such as the above-mentioned application identifier, and is not used. Yu
  • the information indicating the content is, for example, the above content identification.
  • the determining module may determine a content source of the content according to an IP address pointed to by the content request. Furthermore, since the content request typically contains the URL of the requested content, the determination module can also determine the content source by analyzing the URL.
  • the charging device uses the traffic as the traffic generated by the application, and the charging device sends the traffic meter into the traffic package corresponding to the application. It can be seen that, because the traffic is counted in the traffic plan corresponding to the application, instead of counting the traffic package corresponding to the content provider corresponding to the content, the present invention can achieve the traffic generated by using the traffic as the application. The purpose of the fee.
  • the access device 400 shown in FIG. 4 is for performing the method 100 shown in FIG. 1, the access device and its operation, and the technical details related to the access device and its operation are in the method 200 and the diagram shown in FIG.
  • the method 300 shown in FIG. 3 is also described, and will be further described below in conjunction with FIGS. 5-6.
  • the embodiment of the present invention obtains an application indicated by the application identifier according to the application identifier carried in the content request, and the content request is triggered by the application. In this way, the embodiment of the present invention can send the traffic generated by the requested content and the charging request of the application to the charging device, so as to enable the charging device to charge the traffic generated by the application as the application. purpose.
  • FIG. 5 is a schematic diagram showing an exemplary logical structure of a charging device 500 according to an embodiment of the invention.
  • the charging device 500 shown in FIG. 5 is used to charge the traffic generated by the content requested by the application.
  • the charging device 500 includes a receiving module 502 and a charging module 504.
  • the receiving module 502 is configured to receive a charging request sent by the access device to indicate the application and the traffic.
  • the charging request is a credit control request CCR
  • the application is indicated by an application parameter carried in the credit control request.
  • the application parameter is a new parameter
  • the information carried in the parameter will be information indicating the application, such as the application identifier. It is not difficult to understand that since the application parameters are a new parameter, the existing credit control request needs to be modified.
  • the charging module 504 is configured to charge the traffic as the traffic generated by the application.
  • the charging module 504 when the traffic is used as the traffic generated by the application, the charging module 504 is specifically configured to: import the flowmeter into a traffic package corresponding to the application. Therefore, the present invention can achieve the above-mentioned traffic as the above-mentioned application product, because the traffic is counted in the traffic package corresponding to the application, instead of counting the traffic package corresponding to the content provider corresponding to the content.
  • the raw traffic is used for billing purposes.
  • the charging device 500 may further include a generating module (not shown in FIG. 5) for generating a consumption record according to the application, the content, and the traffic, wherein the consumption record is used to indicate The traffic is generated by the content, the content is requested by the application, and the traffic is charged as traffic generated by the application.
  • the service identifier service identifier carried in the credit control request may also be used to indicate the content source of the content, rather than the content, thereby generating another consumption record.
  • the charging request is a credit control request CCR and the application indicates by the application parameter carried in the credit control request
  • the traffic is indicated by the used traffic USU carried in the credit control request
  • the credit control request further carries a service identifier service identifier for indicating a content source of the content.
  • the charging device 500 may further include a generating module (not shown in FIG.
  • the consumption record is used to indicate The traffic is generated when the content source is accessed, the access to the content source is triggered by the application, and the traffic is charged as traffic generated by the application.
  • the charging device 500 shown in FIG. 5 is for performing the method 200 shown in FIG. 2, the charging device and its operation, and the technical details related to the charging device and its operation are in the method 100 and the diagram shown in FIG.
  • the method 300 shown in FIG. 3 and the apparatus 400 shown in FIG. 4 are also described, and will be further described below in conjunction with FIG. 6.
  • the embodiment of the present invention obtains an application indicated by the application identifier according to the application identifier carried in the content request, and the content request is triggered by the application. In this way, the embodiment of the present invention can send the traffic generated by the requested content and the charging request of the application to the charging device, so as to enable the charging device to charge the traffic generated by the application as the application. purpose.
  • FIG. 6 is a schematic diagram showing an exemplary logical structure of a charging system 600 according to an embodiment of the invention.
  • the billing system 600 includes an access device 602 and a billing device 604.
  • the access device 602 is configured to receive a content request, where the content request carries a content identifier and an application identifier, where the content identifier is used to identify the requested content, and the application identifier is used to identify the application. And for identifying that the content request is triggered by the application; returning the content and determining traffic generated by the content; and transmitting a charging request indicating the traffic and the application to the charging device 604.
  • the charging device 604 is configured to receive an accounting request sent by the access device 602 to indicate the application and the traffic, and charge the traffic as the traffic generated by the application.
  • the charging request may be a credit control request
  • the application is indicated by a service identifier service identifier carried in the credit control request.
  • the information carried in the service identifier is not information indicating the content, such as the content identifier described above, but information indicating the application, such as the application identifier described above.
  • the charging request is also a credit control request CCR, but the application is indicated by an application parameter carried in the credit control request.
  • the application parameter is a new parameter, and the information carried in the parameter will be information indicating the application, such as the application identifier.
  • the application can be indicated in the credit control request in two ways.
  • the first way is to use the service identifier service identifier indication carried in the credit control request
  • the second way is to use the application parameter indication carried in the credit control request. It is not difficult to understand that since the service identifier service identifier already exists in the existing credit control request, the first method does not require modification of the existing credit control request. However, in the second mode, since the application parameters are new parameters, the existing credit control request needs to be modified.
  • the charging request is a credit control request CCR and the application indicates the application parameter carried in the credit control request
  • the traffic passes the used service unit (USU) carried in the credit control request.
  • the credit control request further carries a service identifier service identifier for indicating the content, so the charging device 604 can generate a consumption record according to the application, the content, and the traffic, where The consumption record is used to indicate that the traffic is generated by the content, the content is requested by the application, and the traffic is charged as traffic generated by the application.
  • the service identifier carries information for indicating the content such as the above-described content identifier, and is not information for indicating the application such as the above-described application identifier.
  • the service identifier service identifier carried in the credit control request may also be used to indicate the content source of the content, not the content.
  • billing device 604 can generate another type of consumption record. Specifically, when the charging request is a credit control request CCR and the application passes the The access device 602 is further configured to determine a content source of the content when the application parameter indication carried in the credit control request is indicated.
  • the traffic is indicated by the used traffic USU carried in the credit control request, and the credit control request further carries a service identifier service identifier for indicating the content source, so that the charging device 604 is configured according to the Generating a consumption record by the application, the content source, and the traffic, wherein the consumption record is used to indicate that the traffic is generated when accessing the content source, and access to the content source is through
  • the application is triggered, and the traffic is charged as traffic generated by the application.
  • the service identifier carries information indicating the content source of the content, such as the name of the content source, the domain name, and the like, instead of the information for indicating the application, such as the above-mentioned application identifier, and is not used.
  • the information indicating the content is, for example, the above content identification.
  • the access device 602 may determine a content source of the content according to the IP address pointed to by the content request. Moreover, since the content request typically contains the URL of the requested content, the access device 602 can also determine the content source by analyzing the URL.
  • the charging device 604 charges the traffic as the traffic generated by the application, and the charging device 604 enters the traffic meter into the traffic package corresponding to the application. It can be seen that, because the traffic is counted in the traffic plan corresponding to the application, instead of counting the traffic package corresponding to the content provider corresponding to the content, the present invention can achieve the traffic generated by using the traffic as the application. The purpose of the fee.
  • the access device 602 is configured to perform the method 100 illustrated in FIG. 1, the device and its operation, and the specific details related to the device and its operation are also described in FIGS. 2-5, and thus are not described herein again.
  • the billing device 604 is configured to perform the method 200 shown in FIG. 2, the device and its operation, and the specific details related to the device and its operation are also described in FIG. 1, FIG. 3 to FIG. 5, so Let me repeat.
  • the embodiment of the present invention obtains an application indicated by the application identifier according to the application identifier carried in the content request, and the content request is triggered by the application. In this way, the embodiment of the present invention can send the traffic generated by the requested content and the charging request of the application to the charging device, so as to enable the charging device to charge the traffic generated by the application as the application. purpose.
  • FIG. 7 is an exemplary flow diagram of a quality of service control method 700 in accordance with an embodiment of the present invention.
  • the quality of service control method 700 can be performed by, for example, but not limited to, an access device, which can be, for example, but not limited to, a GGSN.
  • Step 702 Receive a content request, where the content request carries a content identifier and an application identifier
  • the content identifier is used to identify the requested content
  • the application identifier is used to identify the application and is used to identify that the content request is triggered by the application.
  • the content identifier may be, for example, but not limited to, a URL of the content carried in the content request, or information obtained from the URL and used to identify the content.
  • the content request, the content identifier, and the application identifier in the description of the embodiment are the content request, the content identifier, and the application identifier described in FIG. 1-6.
  • Step 704 Determine a service quality corresponding to the application.
  • Step 706 Return the content according to the quality of service.
  • the method 700 may further include:
  • the service quality control request may be a credit control request (CCR), and the application is indicated by a service identifier service identifier carried in the credit control request.
  • CCR credit control request
  • the information carried in the service identifier is not information indicating the content, such as the content identifier described above, but information indicating the application, such as the application identifier described above.
  • the quality of service control request is also a credit control request CCR, but the application is indicated by an application parameter carried in the credit control request.
  • the application parameter is a new parameter, and the information carried in the parameter will be information indicating the application, such as the application identifier.
  • the application can be indicated in the credit control request in two ways.
  • the first way is to use the service identifier service identifier indication carried in the credit control request
  • the second way is to use the application parameter indication carried in the credit control request. It is not difficult to understand that since the service identifier service identifier already exists in the existing credit control request, the first method does not require modification of the existing credit control request. However, in the second mode, since the application parameters are new parameters, the existing credit control request needs to be modified.
  • the service quality control device can respond by credit control (Credit) Control Answer, CCA) returns the determined quality of service.
  • Credit Credit Control Answer
  • the embodiment of the present invention obtains an application indicated by the application identifier according to the application identifier carried in the content request, and the content request is triggered by the application. In this way, the embodiment of the present invention can use the quality of service applied to the application when returning the above content.
  • the embodiment of the present invention can report the traffic generated by the requested content and the service quality control request of the application to the QoS control device, and use the traffic generated by the requested content as the traffic generated by the application.
  • the cumulative traffic of the application is implemented to achieve an update of the cumulative traffic for the application.
  • the quality of service control device can determine the service quality of the application according to the updated cumulative traffic, and return the determined service quality of the application to the access device.
  • FIG. 8 is an exemplary flow diagram of a quality of service control method 800 in accordance with an embodiment of the present invention.
  • the quality of service control method 800 shown in FIG. 8 is used to determine the quality of service of an application, wherein a request for content is triggered by the application.
  • the quality of service control method 800 may be performed by, for example, but not limited to, a quality of service control device, which may be, for example, but not limited to, a PCRF (Policy and charging rules function).
  • a quality of service control device which may be, for example, but not limited to, a PCRF (Policy and charging rules function).
  • the content and application described in this embodiment are the content and application described in FIGS. 1-6.
  • Step 802 Receive, by the access device, a flow indicating the content generated by the content and a quality of service control request of the application.
  • the service quality control request is a credit control request CCR
  • the application is indicated by an application parameter carried in the credit control request.
  • the application parameter is a new parameter
  • the information carried in the parameter will be information indicating the application, such as the application identifier. It is not difficult to understand that since the application parameters are a new parameter, the existing credit control request needs to be modified.
  • Step 804 Update the cumulative traffic of the application by using the traffic as the traffic generated by the application.
  • Step 806 Determine a service quality of the application according to the updated cumulative traffic.
  • Step 808 returning the determined quality of service.
  • the quality of service control device may return the updated quality of service through the credit control response CCA.
  • the traffic generated by the requested content and the service quality control request of the application may be reported to the service quality control device, and the traffic generated by the requested content may be used as the traffic generated by the application. Cumulative traffic, thereby enabling an update of the cumulative traffic to the application.
  • the quality of service control device can determine the service quality of the application according to the updated cumulative traffic, and return the determined service quality of the application to the access device.
  • the mobile terminal shown in FIG. 9 may be a computing device with an Internet access function, such as, but not limited to, a personal digital assistant, a smart phone, a tablet computer, etc., and the mobile terminal runs an application through which the user can trigger a content request. In order to access the content.
  • the GGSN corresponds to access devices in methods 700 and 800
  • PCRF corresponds to quality of service control devices in methods 700 and 800.
  • Step 902 The user triggers a content request by using an application running on the mobile terminal, where the content request carries a content identifier and an application identifier, where the content identifier is used to identify the requested content, and the application identifier is used to identify the application.
  • the request for identifying the content is triggered by the application. Details of the technical features such as content request, content identification, and application identification have been described in detail above in connection with method 700 and method 800, and thus are not described herein.
  • Step 904 The GGSN obtains the requested content according to the content identifier, and determines the service quality corresponding to the application.
  • Step 906 The GGSN returns the requested content to the mobile terminal according to the quality of service corresponding to the application.
  • step 908 the GGSN determines the traffic generated by the content.
  • step 910 the GGSN sends a quality of service control request indicating the traffic and the application to the PCRF.
  • Step 912 The PCRF updates the accumulated traffic of the application according to the application and the traffic indicated in the quality of service control request, and uses the traffic as the traffic generated by the application.
  • Step 914 the PCRF determines the quality of service of the application according to the updated cumulative traffic.
  • step 916 the PCRF returns the determined quality of service to the GGSN.
  • step 908 may be performed after step 904 and before step 906.
  • the GGSN in the method 900 described in connection with FIG. 9 corresponds to the access devices in methods 700 and 800, which correspond to the quality of service control devices in methods 700 and 800.
  • the specific operation of each device, each device, and the specific details involved in each device and its operation have been described in detail above in connection with Figures 7 and 8, and will be described below in connection with Figures 10-12. Further description.
  • FIG. 10 is a schematic diagram showing an exemplary logical structure of an access device 1000 according to an embodiment of the invention.
  • the access device 1000 includes a content request receiving module 1002, a quality of service determining module 1004, and a returning module 1006.
  • the content request receiving module 1002 is configured to receive a content request, where the content request carries a content identifier and an application identifier, where the content identifier is used to identify the requested content, and the application identifier is used to identify the application and is used to identify the content.
  • the request is triggered by the application.
  • the content identifier may be, for example, but not limited to, a URL of the content carried in the content request, or information obtained by the content request receiving module 1002 from the URL, which may be used to identify the content.
  • the content request, the content identifier, and the application identifier in the description of the embodiment are the content request, the content identifier, and the application identifier described in FIG. 1-6.
  • the quality of service determination module 1004 is configured to determine a quality of service corresponding to the application.
  • the return module 1006 is configured to return the content according to the quality of service.
  • the access device 1000 may further include:
  • a flow determination module (not shown in Figure 10) is used to determine the flow generated by the content.
  • a sending module (not shown in FIG. 10), configured to send, to the quality of service control device, a quality of service control request indicating the traffic and the application, so that the quality of service control device generates the traffic as the application Traffic to update the cumulative traffic of the application.
  • the quality of service receiving module (not shown in FIG. 10) is configured to receive the quality of service determined by the quality of service control device according to the updated cumulative traffic.
  • the service quality control request may be a credit control request (CCR), and the application is indicated by a service identifier service identifier carried in the credit control request.
  • CCR credit control request
  • the information carried in the service identifier is not information indicating the content, such as the content identifier described above, but information indicating the application, such as the application identifier described above.
  • the quality of service control request is also a credit control request CCR, but the application is indicated by an application parameter carried in the credit control request.
  • Application parameter For a new parameter what is carried in the parameter will be information for indicating the application, such as the above application identifier.
  • the application can be indicated in the credit control request in two ways.
  • the first way is to use the service identifier service identifier indication carried in the credit control request
  • the second way is to use the application parameter indication carried in the credit control request. It is not difficult to understand that since the service identifier service identifier already exists in the existing credit control request, the first method does not require modification of the existing credit control request. However, in the second mode, since the application parameters are new parameters, the existing credit control request needs to be modified.
  • the quality of service control device can return the updated quality of service through a credit control response (CCA).
  • CCA credit control response
  • the access device 1000 shown in FIG. 10 is for performing the method 700 shown in FIG. 7, the access device and its operation, and the technical details related to the access device and its operation, in the method 800 and the diagram shown in FIG.
  • the method 900 shown in FIG. 9 is also described and will be further described below in conjunction with FIGS. 11-12.
  • the embodiment of the present invention obtains an application indicated by the application identifier according to the application identifier carried in the content request, and the content request is triggered by the application. In this way, the embodiment of the present invention can use the quality of service applied to the application when returning the above content.
  • the embodiment of the present invention can report the traffic generated by the requested content and the service quality control request of the application to the QoS control device, and use the traffic generated by the requested content as the traffic generated by the application.
  • the cumulative traffic of the application is implemented to achieve an update of the cumulative traffic for the application.
  • the quality of service control device can determine the service quality of the application according to the updated cumulative traffic, and return the determined service quality of the application to the access device.
  • FIG. 11 is a schematic diagram showing an exemplary logical structure of a quality of service control device 1100 according to an embodiment of the present invention.
  • the quality of service control device 1100 shown in FIG. 11 is used to determine the quality of service of an application, wherein a request for content is triggered by the application.
  • the quality of service control device 1100 includes a receiving module 1102, an updating module 1104, a determining module 1106, and a returning module 1108.
  • the content and application described in this embodiment are the content and application described in FIGS. 1-6.
  • the receiving module 1102 is configured to receive, by the access device, the traffic generated by the content indication and the quality of service control request of the application.
  • the update module 1104 is configured to update the cumulative traffic of the application by using the traffic as the traffic generated by the application.
  • the determining module 1106 is configured to determine a quality of service of the application according to the updated cumulative traffic.
  • the return module 1108 is configured to return the determined quality of service.
  • the service quality control request is a credit control request CCR
  • the application is indicated by an application parameter carried in the credit control request.
  • the application parameter is a new parameter
  • the information carried in the parameter will be information indicating the application, such as the application identifier. It is not difficult to understand that since the application parameters are a new parameter, the existing credit control request needs to be modified.
  • the return module 1108 can return the updated quality of service by the credit control response CCA.
  • the service quality control device 1100 shown in FIG. 11 is for performing the method 800 shown in FIG. 8, the service quality control device and its operation, and the technical details related to the service quality control device and its operation are shown in FIG. 700 and the method 900 shown in FIG. 9 and the apparatus 1000 shown in FIG. 10 are also described and will be further described below in conjunction with FIG.
  • the traffic generated by the requested content and the service quality control request of the application may be reported to the service quality control device, and the traffic generated by the requested content may be used as the traffic generated by the application. Cumulative traffic, thereby enabling an update of the cumulative traffic to the application.
  • the quality of service control device can determine the service quality of the application according to the updated cumulative traffic, and return the determined service quality of the application to the access device.
  • FIG. 12 is a schematic diagram showing an exemplary logical structure of a quality of service control system 1200 in accordance with an embodiment of the present invention. As shown in FIG. 12, the quality of service control system 1200 includes an access device 1202 and a quality of service control device 1204.
  • the access device 1202 is configured to receive a content request, where the content request carries a content identifier and an application identifier, where the content identifier is used to identify the requested content, and the application identifier is used to identify the application and is used to identify the content request. Trimming by the application; determining a quality of service corresponding to the application; and returning the content according to the quality of service.
  • the access device 1202 is further configured to determine the traffic generated by the content; send a quality of service control request indicating the traffic and the application to the quality of service control device 1204, so that the quality of service control device 1204 treats the traffic as Generating the generated traffic of the application to update the cumulative traffic of the application; the receiving quality of service control device 1204 is determined according to the updated cumulative traffic of the application The quality of service of the application.
  • the QoS control device 1204 is configured to receive, by the access device 1202, the traffic generated by the content and the quality of service control request of the application, and use the traffic as the traffic generated by the application to update the cumulative traffic of the application. Determining the quality of service of the application according to the accumulated traffic, and returning the determined quality of service to the access device 1202.
  • the quality of service control request may be a credit control request CCR
  • the application is indicated by a service identifier service identifier carried in the credit control request.
  • the information carried in the service identifier is not information indicating the content, such as the content identifier described above, but information indicating the application, such as the application identifier described above.
  • the quality of service control request is also a credit control request CCR, but the application is indicated by an application parameter carried in the credit control request.
  • the application parameter is a new parameter, and the information carried in the parameter will be information indicating the application, such as the application identifier.
  • the application can be indicated in the credit control request in two ways.
  • the first way is to use the service identifier service identifier indication carried in the credit control request
  • the second way is to use the application parameter indication carried in the credit control request. It is not difficult to understand that since the service identifier service identifier already exists in the existing credit control request, the first method does not require modification of the existing credit control request. However, in the second mode, since the application parameters are new parameters, the existing credit control request needs to be modified.
  • the quality of service control device 1204 may return the determined quality of service through a Credit Control Answer (CCA).
  • CCA Credit Control Answer
  • the access device 1202 is configured to perform the method 700 illustrated in FIG. 7, the device and its operation, and the specific details related to the device and its operation are also described in FIGS. 8-11, and thus are not described herein again.
  • the quality of service control device 1204 is for performing the method 800 shown in FIG. 8, the device and its operation, and the specific details related to the device and its operation are also described in FIG. 7, FIG. 9 to FIG. 11, so Let me repeat.
  • the embodiment of the present invention obtains an application indicated by the application identifier according to the application identifier carried in the content request, and the content request is triggered by the application. In this way, the embodiment of the present invention can use the quality of service applied to the application when returning the above content.
  • the embodiment of the present invention can report the traffic generated by the requested content and the service quality control request of the application to the QoS control device, and use the traffic generated by the requested content as the traffic generated by the application.
  • the cumulative traffic of the application is implemented to achieve an update of the cumulative traffic for the application.
  • the quality of service control device can determine the service quality of the application according to the updated cumulative traffic, and return the determined service quality of the application to the access device.
  • FIG. 13 is a schematic structural diagram of hardware of an access device 1300 according to an embodiment of the invention.
  • access device 1300 includes a processor 1302, a memory 1304, an input/output interface 1306, a communication interface 1308, and a bus 1310.
  • the processor 1302, the memory 1304, the input/output interface 1306, and the communication interface 1308 implement communication connections with each other through the bus 1310.
  • the processor 1302 may be a general-purpose central processing unit (CPU), a microprocessor, an application specific integrated circuit (ASIC), or one or more integrated circuits for executing related programs.
  • CPU central processing unit
  • ASIC application specific integrated circuit
  • the memory 1304 may be a read only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM).
  • Memory 1304 can store operating systems and other applications.
  • the program code for implementing the technical solution provided by the embodiment of the present invention is stored in the memory 1304 and executed by the processor 1302.
  • the input/output interface 1306 is configured to receive input data and information, and output data such as operation results.
  • Communication interface 1308 implements communication between access device 1300 and other devices or communication networks using transceivers such as, but not limited to, transceivers.
  • Bus 1310 can include a path for communicating information between various components of access device 1300 (e.g., processor 1302, memory 1304, input/output interface 1306, and communication interface 1308).
  • access device 1300 shown in FIG. 13 only shows the processor 1302, the memory 1304, the input/output interface 1306, the communication interface 1308, and the bus 1310, in a specific implementation process, those skilled in the art should It is understood that the access device 1300 also includes other devices necessary to achieve proper operation. In the meantime, those skilled in the art will appreciate that the access device 1300 may also include hardware devices that implement other additional functions, depending on the particular needs. Moreover, those skilled in the art will appreciate that access device 1300 may also only include the components necessary to implement embodiments of the present invention, and does not necessarily include all of the devices shown in FIG.
  • FIG. 13 The hardware structure and the foregoing description shown in FIG. 13 are applicable to various access devices, charging devices, and quality of service control devices provided by the embodiments of the present invention. Based on the hardware structure shown in FIG. 13, the operations of the access device shown in FIG. 4, the charging device shown in FIG. 5, the access device shown in FIG. 10, and the service quality control device shown in FIG. 11 should be understood as The operation of the module by issuing corresponding instructions to the appropriate hardware device in FIG.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Computer Security & Cryptography (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Information Transfer Between Computers (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明实施例公开了一种业务办理的信息处理装置，包括：第一确定模块，用于接收用户办理业务的请求，所述请求中包含用户办理业务的渠道标识；处理模块，用于提供所述渠道标识对应的用户界面给用户终端，并提示用户通过用户界面提交业务办理信息；更新模块，用于接收提交的业务办理信息，并更新业务的办理状态信息；第二确定模块，用于接收客服请求，确定请求对应的用户办理业务的渠道标识；调用模块，用于调用所述渠道标识对应的用户界面将所述业务的办理状态信息返回给客服终端。本发明实施例还公开了一种业务办理的信息处理方法。采用本发明，具有可实现多渠道办理业务的业务信息的共享，提高业务办理效率、增强业务自助办理的用户体验的优点。

Description

计费方法和设备、接入设备、服务质量控制方法和设备
本申请要求于2014年7月23日提交中国专利局、申请号为201410352743.5发明名称为“计费方法和设备、接入设备、服务质量控制方法和设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及计费和服务质量控制技术，尤其涉及计费方法和设备、接入设备、服务质量控制方法和设备。
背景技术
网络传输技术的飞速发展，使得可以通过互联网提供的内容越来越丰富。例如，用户可以通过互联网读新闻，听音乐，看电影。借助最新的网络传输技术，内容提供商站点(即内容源)所提供的内容可以以极低的延迟传输到用户终端。
通过加强与内容提供商之间的合作，电信运营商开发出了一种新的计费模式。电信运营商可以为合作的内容提供商开发专门的流量套餐，通过订制这种流量套餐，用户从该内容提供商站点获取内容时产生的流量，将全部单独计入上述流量套餐。在具体实现过程中，电信运营商可以分析用户发出的内容请求，以获得与内容提供商站点有关的信息。例如，电信运营商可以分析内容请求所指向的IP(Internet Protocol，网际协议)地址，以确定内容请求所指向的站点，即内容提供商站点，如此一来便可根据该内容提供商站点确定内容提供商。此外，由于内容请求通常包含所请求内容的URL(Uniform/Universal Resource Locator，统一资源定位符)，电信运营商还可以通过分析该URL来确定内容提供商站点，继而根据该内容提供商站点确定内容提供商。如此一来，电信运营商便可将请求的内容所产生的流量计入用户所订制的针对该内容提供商的流量套餐之中。
伴随着移动终端的快速普及，越来越多的服务提供商通过安装在移动终 端上的专用软件来向用户提供服务。这种专用软件通常称为应用(Application，App)，其由服务提供商开发，借助这种应用，用户可以方便的享受服务提供商所提供的服务。在众多应用之中，社交类应用最为流行。这种应用不仅可以实现用户与好友之间的即时通信，还可以方便用户随时查阅好友分享的各类信息。
仿效为内容提供商专门开发的流量套餐，电信运营商也为社交类应用开发了对应的流量套餐。依照电信运营商的最初设想，借助这一流量套餐，用户通过社交类应用享受服务(例如即时通信)和访问内容(例如好友分享的信息)时产生的流量，将全部计入用户订制的为社交类应用设置的流量套餐之中。然而，在使用过程中，用户发现其使用社交类应用所产生的流量并未完全计入对应的流量套餐之中。产生这一问题的根本原因在于，用户使用社交类应用所访问的内容，并非全部由提供社交类应用的服务提供商站点提供，即针对上述内容的访问请求，并非都是指向提供社交类应用的服务提供商站点。
以下以用户通过腾讯公司提供的微信应用(以下简称微信)访问好友分享的内容的过程为例，来解释产生上述问题的原因。微信提供的朋友圈功能允许用户访问好友分享的内容，例如文章、图片、歌曲和电影等。在分享一段视频内容时，好友可以在朋友圈中嵌入该视频内容的访问入口，该访问入口可以展现为朋友圈窗口中的一个视频播放窗口。在用户点击该视频播放窗口上的播放按钮时，微信便向提供该视频内容的内容提供商站点请求该视频内容，并在上述视频播放窗口中播放获取的该视频内容。然而，提供上述视频内容的内容提供商很可能并非开发微信的服务提供商腾讯公司，因此对上述视频内容的访问请求可能并非指向腾讯公司的站点。例如，当好友在微信朋友圈中分享优酷公司提供的视频内容时，尽管用户通过微信请求这一视频内容，但这一视频内容仍然由优酷公司的站点(而非腾讯公司的站点)提供。如此一来，在用户点击播放按钮时，微信是向优酷公司的站点请求上述视频内容，而不是向腾讯公司的站点请求上述视频内容。然而，在用户看来，由于用户是通过微信的朋友圈窗口中的视频窗口来观看这一视频内容的(即用户观看这一视频内容时并未跳出微信应用)，这一视频内容产生的流量应当计入微信对应的流量套餐。
由此可见，依照现有的计费技术，用户通过社交类应用访问内容时产生的流量，不一定能够计入社交类应用对应的流量套餐。
发明内容
有鉴于此，实有必要提供一种计费方法，可将通过应用访问的内容时产生的流量计入该应用对应的流量套餐。
同时，提供一种接入设备，可将通过应用访问的内容时产生的流量计入该应用对应的流量套餐。
同时，提供一种计费设备，可将通过应用访问的内容时产生的流量计入该应用对应的流量套餐。
同时，提供一种服务质量控制方法，可将应用于应用的服务质量应用于通过应用访问的内容。
同时，提供一种服务质量控制方法，可将通过应用访问的内容时产生的流量作为应用产生的流量来更新应用的累计流量，以便根据更新后的累计流量确定应用的服务质量。
同时，提供一种接入设备，可将应用于应用的服务质量应用于通过应用访问的内容。
同时，提供一种服务质量控制设备，可将通过应用访问的内容时产生的流量作为应用产生的流量来更新应用的累计流量，以便根据更新后的累计流量确定应用的服务质量。
第一方面，提供一种计费方法，包括：
接收内容请求，其中，所述内容请求携带内容标识和应用标识，所述内容标识用于标识请求的内容，所述应用标识用于标识应用且用于标识所述内容请求通过所述应用触发；
返回所述内容并确定该内容产生的流量；
向计费设备发送指示所述流量和所述应用的计费请求，以便计费设备将所述流量作为所述应用产生的流量进行计费。
结合第一方面的第一可能，所述计费请求为信用控制请求CCR，所述应用通过该信用控制请求中携带的服务标识service identifier指示。
结合第一方面的第二可能，所述计费请求为信用控制请求CCR，所述应 用通过该信用控制请求中携带的应用参数指示。
结合第二可能的第三可能，所述流量通过该信用控制请求中携带的已使用业务量USU指示，所述信用控制请求中还携带用于指示所述内容的服务标识service identifier，以便所述计费设备根据所述应用、所述内容和所述流量，生成消费记录，其中，所述消费记录用于指示所述流量是由所述内容产生的，所述内容是通过所述应用请求的，且所述流量是作为所述应用产生的流量进行计费的。
结合第二可能的第四可能，所述方法还包括确定所述内容的内容源，所述流量通过该信用控制请求中携带的已使用业务量USU指示，所述信用控制请求中还携带用于指示所述内容源的服务标识service identifier，以便所述计费设备根据所述应用、所述内容源和所述流量，生成消费记录，其中，所述消费记录用于指示所述流量是在访问所述内容源时产生的，对所述内容源的访问是通过所述应用触发的，且所述流量是作为所述应用产生的流量进行计费的。
第二方面，提供一种计费方法，用于对通过应用请求的内容所产生的流量进行计费，包括：
接收接入设备发送的指示所述应用和所述流量的计费请求；
将所述流量作为所述应用产生的流量进行计费。
结合第二方面的第一可能，所述计费请求为信用控制请求CCR，所述应用通过该信用控制请求中携带的应用参数指示。
结合第一可能的第二可能，所述流量通过该信用控制请求中携带的已使用业务量USU指示，所述信用控制请求中还携带用于指示所述内容的服务标识service identifier，所述方法还包括，根据所述应用、所述内容和所述流量，生成消费记录，其中，所述消费记录用于指示所述流量是由所述内容产生的，所述内容是通过所述应用请求的，且所述流量是作为所述应用产生的流量进行计费的。
结合第一可能的第三可能，所述流量通过该信用控制请求中携带的已使用业务量USU指示，所述信用控制请求中还携带用于指示所述内容的内容源的服务标识service identifier，所述方法还包括，根据所述应用、所述内容源和所述流量，生成消费记录，其中，所述消费记录用于指示所述流量是在访 问所述内容源时产生的，对所述内容源的访问是通过所述应用触发的，且所述流量是作为所述应用产生的流量进行计费的。
第三方面，提供一种接入设备，包括：
接收模块，用于接收内容请求，其中，所述内容请求携带内容标识和应用标识，所述内容标识用于标识请求的内容，所述应用标识用于标识应用且用于标识所述内容请求通过所述应用触发；
返回模块，用于返回所述内容并确定该内容产生的流量；
计费模块，用于向计费设备发送指示所述流量和所述应用的计费请求，以便计费设备将所述流量作为所述应用产生的流量进行计费。
结合第三方面的第一可能，所述计费请求为信用控制请求CCR，所述应用通过该信用控制请求中携带的服务标识service identifier指示。
结合第三方面的第二可能，所述计费请求为信用控制请求CCR，所述应用通过该信用控制请求中携带的应用参数指示。
结合第二可能的第三可能，所述流量通过该信用控制请求中携带的已使用业务量USU指示，所述信用控制请求中还携带用于指示所述内容的服务标识service identifier，以便所述计费设备根据所述应用、所述内容和所述流量，生成消费记录，其中，所述消费记录用于指示所述流量是由所述内容产生的，所述内容是通过所述应用请求的，且所述流量是作为所述应用产生的流量进行计费的。
结合第二可能的第四可能，所述设备还包括确定模块，用于确定所述内容的内容源，所述流量通过该信用控制请求中携带的已使用业务量USU指示，所述信用控制请求中还携带用于指示所述内容源的服务标识service identifier，以便所述计费设备根据所述应用、所述内容源和所述流量，生成消费记录，其中，所述消费记录用于指示所述流量是在访问所述内容源时产生的，对所述内容源的访问是通过所述应用触发的，且所述流量是作为所述应用产生的流量进行计费的。
第四方面，提供一种计费设备，用于对通过应用请求的内容所产生的流量进行计费，包括：
接收模块，用于接收接入设备发送的指示所述应用和所述流量的计费请求；
计费模块，用于将所述流量作为所述应用产生的流量进行计费。
结合第四方面的第一可能，所述计费请求为信用控制请求CCR，所述应用通过该信用控制请求中携带的应用参数指示。
结合第一可能的第二可能，所述流量通过该信用控制请求中携带的已使用业务量USU指示，所述信用控制请求中还携带用于指示所述内容的服务标识service identifier，所述设备还包括生成模块，用于根据所述应用、所述内容和所述流量，生成消费记录，其中，所述消费记录用于指示所述流量是由所述内容产生的，所述内容是通过所述应用请求的，且所述流量是作为所述应用产生的流量进行计费的。
结合第一可能的第三可能，所述流量通过该信用控制请求中携带的已使用业务量USU指示，所述信用控制请求中还携带用于指示所述内容的内容源的服务标识service identifier，所述设备还包括生成模块，用于根据所述应用、所述内容源和所述流量，生成消费记录，其中，所述消费记录用于指示所述流量是在访问所述内容源时产生的，对所述内容源的访问是通过所述应用触发的，且所述流量是作为所述应用产生的流量进行计费的。
第五方面，提供一种服务质量控制方法，包括：
接收内容请求，其中，所述内容请求携带内容标识和应用标识，所述内容标识用于标识请求的内容，所述应用标识用于标识应用且用于标识所述内容请求通过所述应用触发；
确定所述应用对应的服务质量；
根据所述服务质量返回所述内容。
结合第五方面的第一可能，所述方法还包括：
确定所述内容产生的流量；
向服务质量控制设备发送指示所述流量和所述应用的服务质量控制请求，以便所述服务质量控制设备将所述流量作为所述应用产生的流量来更新所述应用的累计流量；
接收服务质量控制设备返回的根据更新后的累计流量确定的服务质量。
结合第一可能的第二可能，所述服务质量控制请求为信用控制请求CCR，所述应用通过该信用控制请求中携带的服务标识service identifier指示。
结合第一可能的第三可能，所述服务质量控制请求为信用控制请求 CCR，所述应用通过该信用控制请求中携带的应用参数指示。
第六方面，提供一种服务质量控制方法，用于确定应用的服务质量，其中，对内容的请求通过所述应用触发，所述方法包括：
接收接入设备发送的指示所述内容产生的流量和所述应用的服务质量控制请求；
将所述流量作为所述应用产生的流量来更新所述应用的累计流量；
根据更新后的累计流量确定所述应用的服务质量；
返回确定的服务质量。
结合第六方面的第一可能，所述服务质量控制请求为信用控制请求CCR，所述应用通过该信用控制请求中携带的应用参数指示。
第七方面，提供一种接入设备，包括：
内容请求接收模块，用于接收内容请求，其中，所述内容请求携带内容标识和应用标识，所述内容标识用于标识请求的内容，所述应用标识用于标识应用且用于标识所述内容请求通过所述应用触发；
服务质量确定模块，用于确定所述应用对应的服务质量；
返回模块，用于根据所述服务质量返回所述内容。
结合第七方面的第一可能，所述设备还包括：
流量确定模块，用于确定所述内容产生的流量；
发送模块，用于向服务质量控制设备发送指示所述流量和所述应用的服务质量控制请求，以便所述服务质量控制设备将所述流量作为所述应用产生的流量来更新所述应用的累计流量；
服务质量接收模块，用于接收服务质量控制设备返回的根据更新后的累计流量确定的服务质量。
结合第一可能的第二可能，所述服务质量控制请求为信用控制请求CCR，所述应用通过该信用控制请求中携带的服务标识service identifier指示。
结合第一可能的第三可能，所述服务质量控制请求为信用控制请求CCR，所述应用通过该信用控制请求中携带的应用参数指示。
第八方面，提供一种服务质量控制设备，用于确定应用的服务质量，其中，对内容的请求通过所述应用触发，所述设备包括：
接收模块，用于接收接入设备发送的指示所述内容产生的流量和所述应 用的服务质量控制请求；
更新模块，用于将所述流量作为所述应用产生的流量来更新所述应用的累计流量；
确定模块，用于根据更新后的累计流量确定所述应用的服务质量；
返回模块，用于返回确定的服务质量。
结合第八方面的第一可能，所述服务质量控制请求为信用控制请求CCR，所述应用通过该信用控制请求中携带的应用参数指示。
本发明实施例根据内容请求中携带的应用标识，获知该应用标识所指示的应用，以及该内容请求是通过该应用触发的。如此一来，本发明实施例便可向计费设备发送指示所请求内容所产生的流量和上述应用的计费请求，从而达到由计费设备将上述流量作为上述应用产生的流量进行计费的目的。
附图说明
图1是依据本发明一实施例的计费方法的示范性流程图；
图2是依据本发明一实施例的计费方法的示范性流程图；
图3是依据本发明一实施例的计费方法的示范性信令图；
图4是依据本发明一实施例的接入设备的示范性逻辑结构示意图；
图5是依据本发明一实施例的计费设备的示范性逻辑结构示意图；
图6是依据本发明一实施例的计费系统的示范性逻辑结构示意图；
图7是依据本发明一实施例的服务质量控制方法的示范性流程图；
图8是依据本发明一实施例的服务质量控制方法的示范性流程图；
图9是依据本发明一实施例的服务质量控制方法的示范性信令图；
图10是依据本发明一实施例的接入设备的示范性逻辑结构示意图；
图11是依据本发明一实施例的服务质量控制设备的示范性逻辑结构示意图；
图12是依据本发明一实施例的服务质量控制系统的示范性逻辑结构示意图；
图13是依据本发明一实施例的接入设备的硬件结构示意图。
具体实施方式
图1是依据本发明一实施例的计费方法100的示范性流程图。在具体实现过程中，计费方法100可由例如但不限于接入设备来执行。上述接入设备可以是例如但不限于GGSN(Gateway GPRS(General Packet Radio Service，通用分组无线业务)Support Node，网关GPRS支持节点)。
步骤102，接收内容请求，其中，所述内容请求携带内容标识和应用标识，所述内容标识用于标识请求的内容，所述应用标识用于标识应用且用于标识所述内容请求通过所述应用触发。
具体来说，上述内容请求来自例如但不限于用户终端，例如各种移动终端。更具体的，上述内容请求是通过运行在用户终端上的应用来触发的。上述内容标识可以是例如但不限于内容请求中携带的内容的URL，或者从该URL中获取的可用于标识上述内容的信息。
步骤104，返回所述内容并确定该内容产生的流量。
步骤106，向计费设备发送指示所述流量和所述应用的计费请求，以便计费设备将所述流量作为所述应用产生的流量进行计费。
具体来说，所述计费请求可以为信用控制请求(Credit control Request，CCR)，所述应用通过该信用控制请求中携带的服务标识service identifier指示。在这种情况下，服务标识中携带的不是用于指示内容的信息例如上述内容标识，而是用于指示应用的信息例如上述应用标识。
在另一种实现方案中，所述计费请求同样为信用控制请求，但所述应用通过该信用控制请求中携带的应用参数指示。该应用参数为一新增参数，在该参数中携带的将是用于指示应用的信息例如上述应用标识。
由此可见，在所述计费请求为信用控制请求时，可通过两种方式在信用控制请求中指示上述应用。第一种方式是通过信用控制请求中携带的服务标识service identifier指示，第二种方式是通过信用控制请求中携带的应用参数指示。不难理解，由于服务标识service identifier在现有信用控制请求中已经存在，因此第一种方式不需要对现有信用控制请求进行修改。然而，在第二种方式中，由于应用参数是新增参数，因此需要对现有信用控制请求进行修改。
当所述计费请求为信用控制请求且所述应用通过该信用控制请求中携带 的应用参数指示时，所述流量通过该信用控制请求中携带的已使用业务量(Used Service Unit，USU)指示。此时，所述信用控制请求中还携带用于指示所述内容的服务标识service identifier，以便所述计费设备根据所述应用、所述内容和所述流量，生成消费记录，其中，所述消费记录用于指示所述流量是由所述内容产生的，所述内容是通过所述应用请求的，且所述流量是作为所述应用产生的流量进行计费的。应注意，在这种情况下，服务标识中携带的是用于指示内容的信息例如上述内容标识，而不是用于指示应用的信息例如上述应用标识。
信用控制请求中携带的服务标识service identifier还可用于指示所述内容的内容源，而非所述内容。在这种情况下，计费设备可生成另外一种消费记录。具体来说，当所述计费请求为信用控制请求且所述应用通过该信用控制请求中携带的应用参数指示时，方法100还可包括确定所述内容的内容源。此时，所述流量通过该信用控制请求中携带的已使用业务量USU指示，所述信用控制请求中还携带用于指示所述内容源的服务标识service identifier，以便所述计费设备根据所述应用、所述内容源和所述流量，生成消费记录，其中，所述消费记录用于指示所述流量是在访问所述内容源时产生的，对所述内容源的访问是通过所述应用触发的，且所述流量是作为所述应用产生的流量进行计费的。应注意，在这种情况下，服务标识中携带的是用于指示内容的内容源的信息，例如内容源的名称、域名等，而不是用于指示应用的信息例如上述应用标识，也不是用于指示内容的信息例如上述内容标识。在具体实现过程中，所述内容的内容源可根据内容请求所指向的IP地址来确定。此外，由于内容请求通常包含所请求内容的URL，因此也可以通过分析该URL来确定内容源。
在具体实现过程中，步骤106中所述的计费设备将所述流量作为所述应用产生的流量进行计费，是指计费设备将所述流量计入所述应用对应的流量套餐。由此可见，由于所述流量被计入所述应用对应的流量套餐而不是计入所述内容对应的内容提供商对应的流量套餐，本发明可以达到将上述流量作为上述应用产生的流量进行计费的目的。
有关计费设备、该设备的具体操作以及计费设备及其操作所涉及的具体细节，将在下文结合图2-图6进行详细描述。
本发明实施例根据内容请求中携带的应用标识，获知该应用标识所指示的应用，以及该内容请求是通过该应用触发的。如此一来，本发明实施例便可向计费设备发送指示所请求内容所产生的流量和上述应用的计费请求，从而达到由计费设备将上述流量作为上述应用产生的流量进行计费的目的。
图2是依据本发明一实施例的计费方法200的示范性流程图。图2所示的计费方法200用于对通过应用请求的内容所产生的流量进行计费。在具体实现过程中，计费方法200可由例如但不限于计费设备来执行。上述计费设备可以是例如但不限于OCS(Online Charging System，在线计费系统)。
步骤202，接收接入设备发送的指示所述应用和所述流量的计费请求。
具体来说，所述计费请求为信用控制请求CCR，所述应用通过该信用控制请求中携带的应用参数指示。该应用参数为一新增参数，在该参数中携带的将是用于指示应用的信息例如上述应用标识。不难理解，由于应用参数为一新增参数，因此需要对现有信用控制请求进行修改。
有关接入设备、该设备的具体操作以及接入设备及其操作所涉及的具体细节，已经在上文结合图1进行了详细的描述，同时，在下文图3-图6中也将进行进一步的描述。
步骤204，将所述流量作为所述应用产生的流量进行计费。
在具体实现过程中，步骤204中所述的将所述流量作为所述应用产生的流量进行计费，是指将所述流量计入所述应用对应的流量套餐。由此可见，由于所述流量被计入所述应用对应的流量套餐而不是计入所述内容对应的内容提供商对应的流量套餐，本发明可以达到将上述流量作为上述应用产生的流量进行计费的目的。
当所述计费请求为信用控制请求CCR且所述应用通过该信用控制请求中携带的应用参数指示时，所述流量通过该信用控制请求中携带的已使用业务量USU指示，所述信用控制请求中还携带用于指示所述内容的服务标识service identifier，此时方法200还可包括，根据所述应用、所述内容和所述流量，生成消费记录，其中，所述消费记录用于指示所述流量是由所述内容产生的，所述内容是通过所述应用请求的，且所述流量是作为所述应用产生的流量进行计费的。
信用控制请求中携带的服务标识service identifier还可用于指示所述内容 的内容源，而非所述内容。在这种情况下，计费设备可生成另外一种消费记录。具体来说，当所述计费请求为信用控制请求CCR且所述应用通过该信用控制请求中携带的应用参数指示时，所述流量通过该信用控制请求中携带的已使用业务量USU指示，所述信用控制请求中还携带用于指示所述内容的内容源的服务标识service identifier，此时方法200还可包括，根据所述应用、所述内容源和所述流量，生成消费记录，其中，所述消费记录用于指示所述流量是在访问所述内容源时产生的，对所述内容源的访问是通过所述应用触发的，且所述流量是作为所述应用产生的流量进行计费的。
本发明实施例根据内容请求中携带的应用标识，获知该应用标识所指示的应用，以及该内容请求是通过该应用触发的。如此一来，本发明实施例便可向计费设备发送指示所请求内容所产生的流量和上述应用的计费请求，从而达到由计费设备将上述流量作为上述应用产生的流量进行计费的目的。
图3是依据本发明一实施例的计费方法300的示范性信令图。图3所示的移动终端可以是例如但不限于个人数字助理、智能电话、平板电脑等具备互联网接入功能的计算设备，该移动终端上运行有应用，用户可通过该应用来触发内容请求，以便访问内容。GGSN对应方法100和200中的接入设备，OCS对应方法100和200中的计费设备。
步骤302，用户通过运行在移动终端上的应用触发一内容请求，其中，所述内容请求携带内容标识和应用标识，所述内容标识用于标识请求的内容，所述应用标识用于标识应用且用于标识所述内容请求通过所述应用触发。内容请求、内容标识和应用标识等技术特征的细节已经在上文结合方法100和方法200进行了详细的描述，因此此处不再赘述。
步骤304，GGSN根据内容标识获取请求的内容，并确定该内容产生的流量。
步骤306，GGSN向移动终端返回请求的内容。
步骤308，GGSN向计费设备发送指示上述流量和应用的计费请求。
计费请求等技术特征的细节已经在上文结合方法100和方法200进行了详细的描述，因此此处不再赘述。
步骤310，计费设备根据计费请求中指示的应用和流量，将流量作为应用产生的流量进行计费，即计费设备将所述流量计入所述应用对应的流量套 餐。
计费过程的细节已经在上文结合方法100和方法200进行了详细的描述，因此此处不再赘述。
在具体实现过程中，方法300中一些步骤的顺序可根据具体需要进行设置，例如步骤304中确定内容产生的流量的操作可在步骤306之后、步骤308之前执行。
此外，方法300还可包含生成消费记录的步骤，与生成消费记录有关的内容已经在上文结合方法100和方法200进行了详细的描述，因此此处不再赘述。
如上文所述，结合图3来描述的方法300中的GGSN对应方法100和200中的接入设备，OCS对应方法100和200中的计费设备。每种设备、每种设备的具体操作以及每种设备及其操作所涉及的具体细节，已经在上文结合图1和图2进行了详细的描述，同时还将在下文结合图4-图6进行进一步的描述。
图4是依据本发明一实施例的接入设备400的示范性逻辑结构示意图。如图4所示，接入设备400包括接收模块402、返回模块404和计费模块406。
接收模块402用于接收内容请求，其中，所述内容请求携带内容标识和应用标识，所述内容标识用于标识请求的内容，所述应用标识用于标识应用且用于标识所述内容请求通过所述应用触发。
返回模块404用于返回所述内容并确定该内容产生的流量。
计费模块406用于向计费设备发送指示所述流量和所述应用的计费请求，以便计费设备将所述流量作为所述应用产生的流量进行计费。
具体来说，上述内容请求来自例如但不限于用户终端，例如各种移动终端。更具体的，上述内容请求是通过运行在用户终端上的应用来触发的。上述内容标识可以是例如但不限于内容请求中携带的内容的URL，或者是接收模块402从该URL中获取的可用于标识上述内容的信息。
此外，所述计费请求可以为信用控制请求(Credit control Request，CCR)，所述应用通过该信用控制请求中携带的服务标识service identifier指示。在这种情况下，服务标识中携带的不是用于指示内容的信息例如上述内容标识，而是用于指示应用的信息例如上述应用标识。
在另一种实现方案中，所述计费请求同样为信用控制请求CCR，但所述应用通过该信用控制请求中携带的应用参数指示。该应用参数为一新增参数，在该参数中携带的将是用于指示应用的信息例如上述应用标识。
由此可见，在所述计费请求为信用控制请求CCR时，可通过两种方式在信用控制请求中指示上述应用。第一种方式是通过信用控制请求中携带的服务标识service identifier指示，第二种方式是通过信用控制请求中携带的应用参数指示。不难理解，由于服务标识service identifier在现有信用控制请求中已经存在，因此第一种方式不需要对现有信用控制请求进行修改。然而，在第二种方式中，由于应用参数是新增参数，因此需要对现有信用控制请求进行修改。
当所述计费请求为信用控制请求CCR且所述应用通过该信用控制请求中携带的应用参数指示时，所述流量通过该信用控制请求中携带的已使用业务量USU指示。此时，所述信用控制请求中还携带用于指示所述内容的服务标识service identifier，以便所述计费设备根据所述应用、所述内容和所述流量，生成消费记录，其中，所述消费记录用于指示所述流量是由所述内容产生的，所述内容是通过所述应用请求的，且所述流量是作为所述应用产生的流量进行计费的。应注意，在这种情况下，服务标识中携带的是用于指示内容的信息例如上述内容标识，而不是用于指示应用的信息例如上述应用标识。
信用控制请求中携带的服务标识service identifier还可用于指示所述内容的内容源，而非所述内容。在这种情况下，计费设备可生成另外一种消费记录。具体来说，当所述计费请求为信用控制请求CCR且所述应用通过该信用控制请求中携带的应用参数指示时，接入设备400还可包括确定模块(图4中未示出)，用于确定所述内容的内容源。此时，所述流量通过该信用控制请求中携带的已使用业务量USU指示，所述信用控制请求中还携带用于指示所述内容源的服务标识service identifier，以便所述计费设备根据所述应用、所述内容源和所述流量，生成消费记录，其中，所述消费记录用于指示所述流量是在访问所述内容源时产生的，对所述内容源的访问是通过所述应用触发的，且所述流量是作为所述应用产生的流量进行计费的。应注意，在这种情况下，服务标识中携带的是用于指示内容的内容源的信息，例如内容源的名称、域名等，而不是用于指示应用的信息例如上述应用标识，也不是用于 指示内容的信息例如上述内容标识。在具体实现过程中，确定模块可根据内容请求所指向的IP地址来确定所述内容的内容源。此外，由于内容请求通常包含所请求内容的URL，因此确定模块也可通过分析该URL来确定内容源。
在具体实现过程中，上述计费设备将所述流量作为所述应用产生的流量进行计费，是指计费设备将所述流量计入所述应用对应的流量套餐。由此可见，由于所述流量被计入所述应用对应的流量套餐而不是计入所述内容对应的内容提供商对应的流量套餐，本发明可以达到将上述流量作为上述应用产生的流量进行计费的目的。
图4所示的接入设备400用于执行图1所示的方法100，该接入设备及其操作以及与该接入设备及其操作相关的技术细节在图2所示的方法200和图3所示的方法300中也做了描述，同时还将在下文结合图5-图6进行进一步的描述。
本发明实施例根据内容请求中携带的应用标识，获知该应用标识所指示的应用，以及该内容请求是通过该应用触发的。如此一来，本发明实施例便可向计费设备发送指示所请求内容所产生的流量和上述应用的计费请求，从而达到由计费设备将上述流量作为上述应用产生的流量进行计费的目的。
图5是依据本发明一实施例的计费设备500的示范性逻辑结构示意图。图5所示的计费设备500用于对通过应用请求的内容所产生的流量进行计费。如图5所示，计费设备500包括接收模块502和计费模块504。
接收模块502用于接收接入设备发送的指示所述应用和所述流量的计费请求。
具体来说，所述计费请求为信用控制请求CCR，所述应用通过该信用控制请求中携带的应用参数指示。该应用参数为一新增参数，在该参数中携带的将是用于指示应用的信息例如上述应用标识。不难理解，由于应用参数为一新增参数，因此需要对现有信用控制请求进行修改。
计费模块504用于将所述流量作为所述应用产生的流量进行计费。
在具体实现过程中，在将所述流量作为所述应用产生的流量进行计费时，计费模块504具体用于，将所述流量计入所述应用对应的流量套餐。由此可见，由于所述流量被计入所述应用对应的流量套餐而不是计入所述内容对应的内容提供商对应的流量套餐，本发明可以达到将上述流量作为上述应用产 生的流量进行计费的目的。
当所述计费请求为信用控制请求CCR且所述应用通过该信用控制请求中携带的应用参数指示时，所述流量通过该信用控制请求中携带的已使用业务量USU指示，所述信用控制请求中还携带用于指示所述内容的服务标识service identifier。此时，计费设备500还可包括生成模块(图5中未示出)，用于根据所述应用、所述内容和所述流量，生成消费记录，其中，所述消费记录用于指示所述流量是由所述内容产生的，所述内容是通过所述应用请求的，且所述流量是作为所述应用产生的流量进行计费的。
信用控制请求中携带的服务标识service identifier还可用于指示所述内容的内容源，而非所述内容，由此便可生成另外一种消费记录。具体来说，当所述计费请求为信用控制请求CCR且所述应用通过该信用控制请求中携带的应用参数指示时，所述流量通过该信用控制请求中携带的已使用业务量USU指示，所述信用控制请求中还携带用于指示所述内容的内容源的服务标识service identifier。此时，计费设备500还可包括生成模块(图5中未示出)，用于根据所述应用、所述内容源和所述流量，生成消费记录，其中，所述消费记录用于指示所述流量是在访问所述内容源时产生的，对所述内容源的访问是通过所述应用触发的，且所述流量是作为所述应用产生的流量进行计费的。
图5所示的计费设备500用于执行图2所示的方法200，该计费设备及其操作以及与该计费设备及其操作相关的技术细节在图1所示的方法100和图3所示的方法300中以及图4所示的设备400中也做了描述，同时还将在下文结合图6进行进一步的描述。
本发明实施例根据内容请求中携带的应用标识，获知该应用标识所指示的应用，以及该内容请求是通过该应用触发的。如此一来，本发明实施例便可向计费设备发送指示所请求内容所产生的流量和上述应用的计费请求，从而达到由计费设备将上述流量作为上述应用产生的流量进行计费的目的。
图6是依据本发明一实施例的计费系统600的示范性逻辑结构示意图。如图6所示，计费系统600包括接入设备602和计费设备604。
接入设备602用于接收内容请求，其中，所述内容请求携带内容标识和应用标识，所述内容标识用于标识请求的内容，所述应用标识用于标识应用 且用于标识所述内容请求通过所述应用触发；返回所述内容并确定该内容产生的流量；以及向计费设备604发送指示所述流量和所述应用的计费请求。
计费设备604用于接收接入设备602发送的指示所述应用和所述流量的计费请求，将所述流量作为所述应用产生的流量进行计费。
具体来说，所述计费请求可以为信用控制请求，所述应用通过该信用控制请求中携带的服务标识service identifier指示。在这种情况下，服务标识中携带的不是用于指示内容的信息例如上述内容标识，而是用于指示应用的信息例如上述应用标识。
在另一种实现方案中，所述计费请求同样为信用控制请求CCR，但所述应用通过该信用控制请求中携带的应用参数指示。该应用参数为一新增参数，在该参数中携带的将是用于指示应用的信息例如上述应用标识。
由此可见，在所述计费请求为信用控制请求CCR时，可通过两种方式在信用控制请求中指示上述应用。第一种方式是通过信用控制请求中携带的服务标识service identifier指示，第二种方式是通过信用控制请求中携带的应用参数指示。不难理解，由于服务标识service identifier在现有信用控制请求中已经存在，因此第一种方式不需要对现有信用控制请求进行修改。然而，在第二种方式中，由于应用参数是新增参数，因此需要对现有信用控制请求进行修改。
当所述计费请求为信用控制请求CCR且所述应用通过该信用控制请求中携带的应用参数指示时，所述流量通过该信用控制请求中携带的已使用业务量(Used Service Unit，USU)指示。此时，所述信用控制请求中还携带用于指示所述内容的服务标识service identifier，因此计费设备604可根据所述应用、所述内容和所述流量，生成消费记录，其中，所述消费记录用于指示所述流量是由所述内容产生的，所述内容是通过所述应用请求的，且所述流量是作为所述应用产生的流量进行计费的。应注意，在这种情况下，服务标识中携带的是用于指示内容的信息例如上述内容标识，而不是用于指示应用的信息例如上述应用标识。
信用控制请求中携带的服务标识service identifier还可用于指示所述内容的内容源，而非所述内容。在这种情况下，计费设备604可生成另外一种消费记录。具体来说，当所述计费请求为信用控制请求CCR且所述应用通过该 信用控制请求中携带的应用参数指示时，接入设备602还用于确定所述内容的内容源。此时，所述流量通过该信用控制请求中携带的已使用业务量USU指示，所述信用控制请求中还携带用于指示所述内容源的服务标识service identifier，以便所述计费设备604根据所述应用、所述内容源和所述流量，生成消费记录，其中，所述消费记录用于指示所述流量是在访问所述内容源时产生的，对所述内容源的访问是通过所述应用触发的，且所述流量是作为所述应用产生的流量进行计费的。应注意，在这种情况下，服务标识中携带的是用于指示内容的内容源的信息，例如内容源的名称、域名等，而不是用于指示应用的信息例如上述应用标识，也不是用于指示内容的信息例如上述内容标识。在具体实现过程中，所述接入设备602可根据内容请求所指向的IP地址来确定内容的内容源。此外，由于内容请求通常包含所请求内容的URL，因此接入设备602也可以通过分析该URL来确定内容源。
在具体实现过程中，计费设备604将所述流量作为所述应用产生的流量进行计费，是指计费设备604将所述流量计入所述应用对应的流量套餐。由此可见，由于所述流量被计入所述应用对应的流量套餐而不是计入所述内容对应的内容提供商对应的流量套餐，本发明可以达到将上述流量作为上述应用产生的流量进行计费的目的。
接入设备602用于执行图1所示的方法100，该设备及其操作以及与该设备及其操作有关的具体细节在图2-图5中也做了描述，因此此处不再赘述。
计费设备604用于执行图2所示的方法200，该设备及其操作以及与该设备及其操作有关的具体细节在图1、图3-图5中也做了描述，因此此处不再赘述。
本发明实施例根据内容请求中携带的应用标识，获知该应用标识所指示的应用，以及该内容请求是通过该应用触发的。如此一来，本发明实施例便可向计费设备发送指示所请求内容所产生的流量和上述应用的计费请求，从而达到由计费设备将上述流量作为上述应用产生的流量进行计费的目的。
图7是依据本发明一实施例的服务质量控制方法700的示范性流程图。在具体实现过程中，服务质量控制方法700可由例如但不限于接入设备来执行，该接入设备可以是例如但不限于GGSN。
步骤702，接收内容请求，其中，所述内容请求携带内容标识和应用标 识，所述内容标识用于标识请求的内容，所述应用标识用于标识应用且用于标识所述内容请求通过所述应用触发。
具体来说，上述内容标识可以是例如但不限于内容请求中携带的内容的URL，或者从该URL中获取的可用于标识上述内容的信息。此外，本实施例描述中的内容请求、内容标识和应用标识，即为图1-6中描述的内容请求、内容标识和应用标识。
步骤704，确定所述应用对应的服务质量。
步骤706，根据所述服务质量返回所述内容。
在具体实现过程中，方法700还可包括：
确定所述内容产生的流量；
向服务质量控制设备发送指示所述流量和所述应用的服务质量控制请求，以便所述服务质量控制设备将所述流量作为所述应用产生的流量来更新所述应用的累计流量；
接收服务质量控制设备返回的根据更新后的累计流量确定的服务质量。
具体来说，所述服务质量控制请求可以为信用控制请求(Credit control Request，CCR)，所述应用通过该信用控制请求中携带的服务标识service identifier指示。在这种情况下，服务标识中携带的不是用于指示内容的信息例如上述内容标识，而是用于指示应用的信息例如上述应用标识。
在另一种实现方案中，所述服务质量控制请求同样为信用控制请求CCR，但所述应用通过该信用控制请求中携带的应用参数指示。该应用参数为一新增参数，在该参数中携带的将是用于指示应用的信息例如上述应用标识。
由此可见，在所述服务质量控制请求为信用控制请求CCR时，可通过两种方式在信用控制请求中指示上述应用。第一种方式是通过信用控制请求中携带的服务标识service identifier指示，第二种方式是通过信用控制请求中携带的应用参数指示。不难理解，由于服务标识service identifier在现有信用控制请求中已经存在，因此第一种方式不需要对现有信用控制请求进行修改。然而，在第二种方式中，由于应用参数是新增参数，因此需要对现有信用控制请求进行修改。
在具体实现过程中，服务质量控制设备可通过信用控制应答(Credit  Control Answer，CCA)返回确定的服务质量。
有关服务质量控制设备、该设备的具体操作以及服务质量控制设备及其操作所涉及的具体细节，将在下文结合图8-图12进行详细描述。
本发明实施例根据内容请求中携带的应用标识，获知该应用标识所指示的应用，以及该内容请求是通过该应用触发的。如此一来，本发明实施例便可在返回上述内容时使用应用于该应用的服务质量。
此外，本发明实施例通过向服务质量控制设备上报指示所请求内容所产生的流量和上述应用的服务质量控制请求，可将所请求内容所产生的流量作为所述应用产生的流量，计入所述应用的累计流量，从而实现对所述应用的累计流量的更新。如此一来，服务质量控制设备便可根据更新后的累计流量确定上述应用的服务质量，并向接入设备返回确定的所述应用的服务质量。
图8是依据本发明一实施例的服务质量控制方法800的示范性流程图。图8所示的服务质量控制方法800用于确定应用的服务质量，其中，对内容的请求通过所述应用触发。在具体实现过程中，服务质量控制方法800可由例如但不限于服务质量控制设备来执行，该服务质量控制设备可以是例如但不限于PCRF(Policy and charging rules function，策略和计费规则功能)。此外，本实施例中描述的内容和应用，即为图1-6中描述的内容和应用。
步骤802，接收接入设备发送的指示所述内容产生的流量和所述应用的服务质量控制请求。
在具体实现过程中，所述服务质量控制请求为信用控制请求CCR，所述应用通过该信用控制请求中携带的应用参数指示。该应用参数为一新增参数，在该参数中携带的将是用于指示应用的信息例如上述应用标识。不难理解，由于应用参数为一新增参数，因此需要对现有信用控制请求进行修改。
有关接入设备、该设备的具体操作以及接入设备及其操作所涉及的具体细节，已经在上文结合图7进行了详细的描述，并将在下文结合图9-12进行进一步的描述。
步骤804，将所述流量作为所述应用产生的流量来更新所述应用的累计流量。
步骤806，根据更新后的累计流量确定所述应用的服务质量。
步骤808，返回确定的服务质量。
在具体实现过程中，服务质量控制设备可通过信用控制应答CCA返回更新的服务质量。
本发明实施例通过向服务质量控制设备上报指示所请求内容所产生的流量和上述应用的服务质量控制请求，可将所请求内容所产生的流量作为所述应用产生的流量，计入所述应用的累计流量，从而实现对所述应用的累计流量的更新。如此一来，服务质量控制设备便可根据更新后的累计流量确定上述应用的服务质量，并向接入设备返回确定的所述应用的服务质量。
图9是依据本发明一实施例的服务质量控制方法900的示范性信令图。图9所示的移动终端可以是例如但不限于个人数字助理、智能电话、平板电脑等具备互联网接入功能的计算设备，该移动终端上运行有应用，用户可通过该应用来触发内容请求，以便访问内容。GGSN对应方法700和800中的接入设备，PCRF对应方法700和800中的服务质量控制设备。
步骤902，用户通过运行在移动终端上的应用触发一内容请求，其中，所述内容请求携带内容标识和应用标识，所述内容标识用于标识请求的内容，所述应用标识用于标识应用且用于标识所述内容请求通过所述应用触发。内容请求、内容标识和应用标识等技术特征的细节已经在上文结合方法700和方法800进行了详细的描述，因此此处不再赘述。
步骤904，GGSN根据内容标识获取请求的内容，并确定应用对应的服务质量。
步骤906，GGSN根据应用对应的服务质量向移动终端返回请求的内容。
步骤908，GGSN确定内容产生的流量。
步骤910，GGSN向PCRF发送指示该流量和应用的服务质量控制请求。
服务质量控制请求等技术特征的细节已经在上文结合方法700和方法800进行了详细的描述，因此此处不再赘述。
步骤912，PCRF根据服务质量控制请求中指示的应用和流量，将所述流量作为所述应用产生的流量来更新所述应用的累计流量。
步骤914，PCRF根据更新后的累计流量确定所述应用的服务质量。
步骤916，PCRF向GGSN返回确定的服务质量。
在具体实现过程中，方法900中一些步骤的顺序可根据具体需要进行设置，例如步骤908可在步骤904之后、步骤906之前执行。
如上文所述，结合图9来描述的方法900中的GGSN对应方法700和800中的接入设备，PCRF对应方法700和800中的服务质量控制设备。每种设备、每种设备的具体操作以及每种设备及其操作所涉及的具体细节，已经在上文结合图7和图8进行了详细的描述，并将在下文结合图10-图12进行进一步的描述。
图10是依据本发明一实施例的接入设备1000的示范性逻辑结构示意图。如图10所示，接入设备1000包括内容请求接收模块1002、服务质量确定模块1004和返回模块1006。
内容请求接收模块1002用于接收内容请求，其中，所述内容请求携带内容标识和应用标识，所述内容标识用于标识请求的内容，所述应用标识用于标识应用且用于标识所述内容请求通过所述应用触发。
具体来说，上述内容标识可以是例如但不限于内容请求中携带的内容的URL，或者内容请求接收模块1002从该URL中获取的可用于标识上述内容的信息。此外，本实施例描述中的内容请求、内容标识和应用标识，即为图1-6中描述的内容请求、内容标识和应用标识。
服务质量确定模块1004用于确定所述应用对应的服务质量。
返回模块1006用于根据所述服务质量返回所述内容。
在具体实现过程中，接入设备1000还可包括：
流量确定模块(图10中未示出)，用于确定所述内容产生的流量。
发送模块(图10中未示出)，用于向服务质量控制设备发送指示所述流量和所述应用的服务质量控制请求，以便所述服务质量控制设备将所述流量作为所述应用产生的流量来更新所述应用的累计流量。
服务质量接收模块(图10中未示出)，用于接收服务质量控制设备返回的根据更新后的累计流量确定的服务质量。
具体来说，所述服务质量控制请求可以为信用控制请求(Credit control Request，CCR)，所述应用通过该信用控制请求中携带的服务标识service identifier指示。在这种情况下，服务标识中携带的不是用于指示内容的信息例如上述内容标识，而是用于指示应用的信息例如上述应用标识。
在另一种实现方案中，所述服务质量控制请求同样为信用控制请求CCR，但所述应用通过该信用控制请求中携带的应用参数指示。该应用参数 为一新增参数，在该参数中携带的将是用于指示应用的信息例如上述应用标识。
由此可见，在所述服务质量控制请求为信用控制请求CCR时，可通过两种方式在信用控制请求中指示上述应用。第一种方式是通过信用控制请求中携带的服务标识service identifier指示，第二种方式是通过信用控制请求中携带的应用参数指示。不难理解，由于服务标识service identifier在现有信用控制请求中已经存在，因此第一种方式不需要对现有信用控制请求进行修改。然而，在第二种方式中，由于应用参数是新增参数，因此需要对现有信用控制请求进行修改。
在具体实现过程中，服务质量控制设备可通过信用控制应答(Credit Control Answer，CCA)返回更新的服务质量。
图10所示的接入设备1000用于执行图7所示的方法700，该接入设备及其操作以及与该接入设备及其操作有关的技术细节在图8所示的方法800和图9所示的方法900中也做了描述，并将在下文结合图11-图12进行进一步的描述。
本发明实施例根据内容请求中携带的应用标识，获知该应用标识所指示的应用，以及该内容请求是通过该应用触发的。如此一来，本发明实施例便可在返回上述内容时使用应用于该应用的服务质量。
此外，本发明实施例通过向服务质量控制设备上报指示所请求内容所产生的流量和上述应用的服务质量控制请求，可将所请求内容所产生的流量作为所述应用产生的流量，计入所述应用的累计流量，从而实现对所述应用的累计流量的更新。如此一来，服务质量控制设备便可根据更新后的累计流量确定上述应用的服务质量，并向接入设备返回确定的所述应用的服务质量。
图11是依据本发明一实施例的服务质量控制设备1100的示范性逻辑结构示意图。图11所示的服务质量控制设备1100用于确定应用的服务质量，其中，对内容的请求通过所述应用触发。如图11所示，服务质量控制设备1100包括接收模块1102、更新模块1104、确定模块1106和返回模块1108。此外，本实施例中描述的内容和应用，即为图1-6中描述的内容和应用。
接收模块1102用于接收接入设备发送的指示所述内容产生的流量和所述应用的服务质量控制请求。
更新模块1104用于将所述流量作为所述应用产生的流量来更新所述应用的累计流量。
确定模块1106用于根据更新后的累计流量确定所述应用的服务质量。
返回模块1108用于返回确定的服务质量。
在具体实现过程中，所述服务质量控制请求为信用控制请求CCR，所述应用通过该信用控制请求中携带的应用参数指示。该应用参数为一新增参数，在该参数中携带的将是用于指示应用的信息例如上述应用标识。不难理解，由于应用参数为一新增参数，因此需要对现有信用控制请求进行修改。
在具体实现过程中，返回模块1108可通过信用控制应答CCA返回更新的服务质量。
图11所示的服务质量控制设备1100用于执行图8所示的方法800，该服务质量控制设备及其操作以及与该服务质量控制设备及其操作相关的技术细节在图7所示的方法700和图9所示的方法900以及图10所示的设备1000中也做了描述，并将在下文结合图12进行进一步的描述。
本发明实施例通过向服务质量控制设备上报指示所请求内容所产生的流量和上述应用的服务质量控制请求，可将所请求内容所产生的流量作为所述应用产生的流量，计入所述应用的累计流量，从而实现对所述应用的累计流量的更新。如此一来，服务质量控制设备便可根据更新后的累计流量确定上述应用的服务质量，并向接入设备返回确定的所述应用的服务质量。
图12是依据本发明一实施例的服务质量控制系统1200的示范性逻辑结构示意图。如图12所示，服务质量控制系统1200包括接入设备1202和服务质量控制设备1204。
接入设备1202用于接收内容请求，其中，所述内容请求携带内容标识和应用标识，所述内容标识用于标识请求的内容，所述应用标识用于标识应用且用于标识所述内容请求通过所述应用触发；确定所述应用对应的服务质量；根据所述服务质量返回所述内容。
接入设备1202还用于确定所述内容产生的流量；向服务质量控制设备1204发送指示所述流量和所述应用的服务质量控制请求，以便所述服务质量控制设备1204将所述流量作为所述应用产生的流量来更新所述应用的累计流量；接收服务质量控制设备1204根据更新后的所述应用的累计流量确定的 所述应用的服务质量。
服务质量控制设备1204用于接收接入设备1202发送的指示所述内容产生的流量和所述应用的服务质量控制请求；将所述流量作为所述应用产生的流量来更新所述应用的累计流量；根据所述累计流量确定所述应用的服务质量，向接入设备1202返回确定的服务质量。
具体来说，所述服务质量控制请求可以为信用控制请求CCR，所述应用通过该信用控制请求中携带的服务标识service identifier指示。在这种情况下，服务标识中携带的不是用于指示内容的信息例如上述内容标识，而是用于指示应用的信息例如上述应用标识。
在另一种实现方案中，所述服务质量控制请求同样为信用控制请求CCR，但所述应用通过该信用控制请求中携带的应用参数指示。该应用参数为一新增参数，在该参数中携带的将是用于指示应用的信息例如上述应用标识。
由此可见，在所述服务质量控制请求为信用控制请求CCR时，可通过两种方式在信用控制请求中指示上述应用。第一种方式是通过信用控制请求中携带的服务标识service identifier指示，第二种方式是通过信用控制请求中携带的应用参数指示。不难理解，由于服务标识service identifier在现有信用控制请求中已经存在，因此第一种方式不需要对现有信用控制请求进行修改。然而，在第二种方式中，由于应用参数是新增参数，因此需要对现有信用控制请求进行修改。
在具体实现过程中，服务质量控制设备1204可通过信用控制应答(Credit Control Answer，CCA)返回确定的服务质量。
接入设备1202用于执行图7所示的方法700，该设备及其操作以及与该设备及其操作有关的具体细节在图8-图11也做了描述，因此此处不再赘述。
服务质量控制设备1204用于执行图8所示的方法800，该设备及其操作以及与该设备及其操作有关的具体细节在图7、图9-图11也做了描述，因此此处不再赘述。
本发明实施例根据内容请求中携带的应用标识，获知该应用标识所指示的应用，以及该内容请求是通过该应用触发的。如此一来，本发明实施例便可在返回上述内容时使用应用于该应用的服务质量。
此外，本发明实施例通过向服务质量控制设备上报指示所请求内容所产生的流量和上述应用的服务质量控制请求，可将所请求内容所产生的流量作为所述应用产生的流量，计入所述应用的累计流量，从而实现对所述应用的累计流量的更新。如此一来，服务质量控制设备便可根据更新后的累计流量确定上述应用的服务质量，并向接入设备返回确定的所述应用的服务质量。
图13是依据本发明一实施例的接入设备1300的硬件结构示意图。如图13所示，接入设备1300包括处理器1302、存储器1304、输入/输出接口1306、通信接口1308和总线1310。其中，处理器1302、存储器1304、输入/输出接口1306和通信接口1308通过总线1310实现彼此之间的通信连接。
处理器1302可以采用通用的中央处理器(Central Processing Unit，CPU)，微处理器，应用专用集成电路(Application Specific Integrated Circuit，ASIC)，或者一个或多个集成电路，用于执行相关程序，以实现本发明实施例所提供的技术方案。
存储器1304可以是只读存储器(Read Only Memory，ROM)，静态存储设备，动态存储设备或者随机存取存储器(Random Access Memory，RAM)。存储器1304可以存储操作系统和其他应用程序。在通过软件或者固件来实现本发明实施例提供的技术方案时，用于实现本发明实施例提供的技术方案的程序代码保存在存储器1304中，并由处理器1302来执行。
输入/输出接口1306用于接收输入的数据和信息，输出操作结果等数据。
通信接口1308使用例如但不限于收发器一类的收发装置，来实现接入设备1300与其他设备或通信网络之间的通信。
总线1310可包括一通路，在接入设备1300各个部件(例如处理器1302、存储器1304、输入/输出接口1306和通信接口1308)之间传送信息。
应注意，尽管图13所示的接入设备1300仅仅示出了处理器1302、存储器1304、输入/输出接口1306、通信接口1308以及总线1310，但是在具体实现过程中，本领域的技术人员应当明白，接入设备1300还包含实现正常运行所必须的其他器件。同时，根据具体需要，本领域的技术人员应当明白，接入设备1300还可包含实现其他附加功能的硬件器件。此外，本领域的技术人员应当明白，接入设备1300也可仅仅包含实现本发明实施例所必须的器件，而不必包含图13中所示的全部器件。
图13所示的硬件结构以及上述描述适用于本发明实施例所提供的各种接入设备、计费设备和服务质量控制设备。基于图13所示的硬件结构，图4所示接入设备、图5所示计费设备、图10所示接入设备和图11所示服务质量控制设备中各模块的操作应理解为各模块通过向图13中的适当硬件器件下发对应的指令来实现的操作。
本领域普通技术人员可知，上述方法中的全部或部分步骤可以通过程序指令相关的硬件完成，该程序可以存储于一计算机可读存储介质中，该计算机可读存储介质如ROM、RAM和光盘等。
综上所述，以上仅为本发明的较佳实施例而已，并非用于限定本发明的保护范围。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (30)

  1. 一种计费方法，其特征在于，包括：
    接收内容请求，其中，所述内容请求携带内容标识和应用标识，所述内容标识用于标识请求的内容，所述应用标识用于标识应用且用于标识所述内容请求通过所述应用触发；
    返回所述内容并确定该内容产生的流量；
    向计费设备发送指示所述流量和所述应用的计费请求，以便计费设备将所述流量作为所述应用产生的流量进行计费。
  2. 如权利要求1所述的方法，其特征在于，所述计费请求为信用控制请求CCR，所述应用通过该信用控制请求中携带的服务标识service identifier指示。
  3. 如权利要求1所述的方法，其特征在于，所述计费请求为信用控制请求CCR，所述应用通过该信用控制请求中携带的应用参数指示。
  4. 如权利要求3所述的方法，其特征在于，所述流量通过该信用控制请求中携带的已使用业务量USU指示，所述信用控制请求中还携带用于指示所述内容的服务标识service identifier，以便所述计费设备根据所述应用、所述内容和所述流量，生成消费记录，其中，所述消费记录用于指示所述流量是由所述内容产生的，所述内容是通过所述应用请求的，且所述流量是作为所述应用产生的流量进行计费的。
  5. 如权利要求3所述的方法，其特征在于，所述方法还包括确定所述内容的内容源，所述流量通过该信用控制请求中携带的已使用业务量USU指示，所述信用控制请求中还携带用于指示所述内容源的服务标识service identifier，以便所述计费设备根据所述应用、所述内容源和所述流量，生成消费记录，其中，所述消费记录用于指示所述流量是在访问所述内容源时产生的，对所述内容源的访问是通过所述应用触发的，且所述流量是作为所述应用产生的流量进行计费的。
  6. 一种计费方法，用于对通过应用请求的内容所产生的流量进行计费，其特征在于，包括：
    接收接入设备发送的指示所述应用和所述流量的计费请求；
    将所述流量作为所述应用产生的流量进行计费。
  7. 如权利要求6所述的方法，其特征在于，所述计费请求为信用控制请求CCR，所述应用通过该信用控制请求中携带的应用参数指示。
  8. 如权利要求7所述的方法，其特征在于，所述流量通过该信用控制请求中携带的已使用业务量USU指示，所述信用控制请求中还携带用于指示所述内容的服务标识service identifier，所述方法还包括，根据所述应用、所述内容和所述流量，生成消费记录，其中，所述消费记录用于指示所述流量是由所述内容产生的，所述内容是通过所述应用请求的，且所述流量是作为所述应用产生的流量进行计费的。
  9. 如权利要求7所述的方法，其特征在于，所述流量通过该信用控制请求中携带的已使用业务量USU指示，所述信用控制请求中还携带用于指示所述内容的内容源的服务标识service identifier，所述方法还包括，根据所述应用、所述内容源和所述流量，生成消费记录，其中，所述消费记录用于指示所述流量是在访问所述内容源时产生的，对所述内容源的访问是通过所述应用触发的，且所述流量是作为所述应用产生的流量进行计费的。
  10. 一种接入设备，其特征在于，包括：
    接收模块，用于接收内容请求，其中，所述内容请求携带内容标识和应用标识，所述内容标识用于标识请求的内容，所述应用标识用于标识应用且用于标识所述内容请求通过所述应用触发；
    返回模块，用于返回所述内容并确定该内容产生的流量；
    计费模块，用于向计费设备发送指示所述流量和所述应用的计费请求，以便计费设备将所述流量作为所述应用产生的流量进行计费。
  11. 如权利要求10所述的设备，其特征在于，所述计费请求为信用控制请求CCR，所述应用通过该信用控制请求中携带的服务标识service identifier指示。
  12. 如权利要求10所述的设备，其特征在于，所述计费请求为信用控制请求CCR，所述应用通过该信用控制请求中携带的应用参数指示。
  13. 如权利要求12所述的设备，其特征在于，所述流量通过该信用控制请求中携带的已使用业务量USU指示，所述信用控制请求中还携带用于指示所述内容的服务标识service identifier，以便所述计费设备根据所述应用、所 述内容和所述流量，生成消费记录，其中，所述消费记录用于指示所述流量是由所述内容产生的，所述内容是通过所述应用请求的，且所述流量是作为所述应用产生的流量进行计费的。
  14. 如权利要求12所述的设备，其特征在于，所述设备还包括确定模块，用于确定所述内容的内容源，所述流量通过该信用控制请求中携带的已使用业务量USU指示，所述信用控制请求中还携带用于指示所述内容源的服务标识service identifier，以便所述计费设备根据所述应用、所述内容源和所述流量，生成消费记录，其中，所述消费记录用于指示所述流量是在访问所述内容源时产生的，对所述内容源的访问是通过所述应用触发的，且所述流量是作为所述应用产生的流量进行计费的。
  15. 一种计费设备，用于对通过应用请求的内容所产生的流量进行计费，其特征在于，包括：
    接收模块，用于接收接入设备发送的指示所述应用和所述流量的计费请求；
    计费模块，用于将所述流量作为所述应用产生的流量进行计费。
  16. 如权利要求15所述的设备，其特征在于，所述计费请求为信用控制请求CCR，所述应用通过该信用控制请求中携带的应用参数指示。
  17. 如权利要求16所述的设备，其特征在于，所述流量通过该信用控制请求中携带的已使用业务量USU指示，所述信用控制请求中还携带用于指示所述内容的服务标识service identifier，所述设备还包括生成模块，用于根据所述应用、所述内容和所述流量，生成消费记录，其中，所述消费记录用于指示所述流量是由所述内容产生的，所述内容是通过所述应用请求的，且所述流量是作为所述应用产生的流量进行计费的。
  18. 如权利要求16所述的设备，其特征在于，所述流量通过该信用控制请求中携带的已使用业务量USU指示，所述信用控制请求中还携带用于指示所述内容的内容源的服务标识service identifier，所述设备还包括生成模块，用于根据所述应用、所述内容源和所述流量，生成消费记录，其中，所述消费记录用于指示所述流量是在访问所述内容源时产生的，对所述内容源的访问是通过所述应用触发的，且所述流量是作为所述应用产生的流量进行计费的。
  19. 一种服务质量控制方法，其特征在于，包括：
    接收内容请求，其中，所述内容请求携带内容标识和应用标识，所述内容标识用于标识请求的内容，所述应用标识用于标识应用且用于标识所述内容请求通过所述应用触发；
    确定所述应用对应的服务质量；
    根据所述服务质量返回所述内容。
  20. 如权利要求19所述的方法，其特征在于，所述方法还包括：
    确定所述内容产生的流量；
    向服务质量控制设备发送指示所述流量和所述应用的服务质量控制请求，以便所述服务质量控制设备将所述流量作为所述应用产生的流量来更新所述应用的累计流量；
    接收服务质量控制设备返回的根据更新后的累计流量确定的服务质量。
  21. 如权利要求20所述的方法，其特征在于，所述服务质量控制请求为信用控制请求CCR，所述应用通过该信用控制请求中携带的服务标识service identifier指示。
  22. 如权利要求20所述的方法，其特征在于，所述服务质量控制请求为信用控制请求CCR，所述应用通过该信用控制请求中携带的应用参数指示。
  23. 一种服务质量控制方法，用于确定应用的服务质量，其中，对内容的请求通过所述应用触发，其特征在于，所述方法包括：
    接收接入设备发送的指示所述内容产生的流量和所述应用的服务质量控制请求；
    将所述流量作为所述应用产生的流量来更新所述应用的累计流量；
    根据更新后的累计流量确定所述应用的服务质量；
    返回确定的服务质量。
  24. 如权利要求23所述的方法，其特征在于，所述服务质量控制请求为信用控制请求CCR，所述应用通过该信用控制请求中携带的应用参数指示。
  25. 一种接入设备，其特征在于，包括：
    内容请求接收模块，用于接收内容请求，其中，所述内容请求携带内容标识和应用标识，所述内容标识用于标识请求的内容，所述应用标识用于标识应用且用于标识所述内容请求通过所述应用触发；
    服务质量确定模块，用于确定所述应用对应的服务质量；
    返回模块，用于根据所述服务质量返回所述内容。
  26. 如权利要求25所述的设备，其特征在于，所述设备还包括：
    流量确定模块，用于确定所述内容产生的流量；
    发送模块，用于向服务质量控制设备发送指示所述流量和所述应用的服务质量控制请求，以便所述服务质量控制设备将所述流量作为所述应用产生的流量来更新所述应用的累计流量；
    服务质量接收模块，用于接收服务质量控制设备返回的根据更新后的累计流量确定的服务质量。
  27. 如权利要求26所述的设备，其特征在于，所述服务质量控制请求为信用控制请求CCR，所述应用通过该信用控制请求中携带的服务标识service identifier指示。
  28. 如权利要求26所述的设备，其特征在于，所述服务质量控制请求为信用控制请求CCR，所述应用通过该信用控制请求中携带的应用参数指示。
  29. 一种服务质量控制设备，用于确定应用的服务质量，其中，对内容的请求通过所述应用触发，其特征在于，所述设备包括：
    接收模块，用于接收接入设备发送的指示所述内容产生的流量和所述应用的服务质量控制请求；
    更新模块，用于将所述流量作为所述应用产生的流量来更新所述应用的累计流量；
    确定模块，用于根据更新后的累计流量确定所述应用的服务质量；
    返回模块，用于返回确定的服务质量。
  30. 如权利要求29所述的设备，其特征在于，所述服务质量控制请求为信用控制请求CCR，所述应用通过该信用控制请求中携带的应用参数指示。
PCT/CN2015/075984 2014-07-23 2015-04-07 计费方法和设备、接入设备、服务质量控制方法和设备 WO2016011831A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
JP2017503587A JP6552068B2 (ja) 2014-07-23 2015-04-07 課金方法及び装置、アクセス装置、サービス品質制御方法及び装置
EP15824591.0A EP3163795B1 (en) 2014-07-23 2015-04-07 Charging methods, access device, and charging device
BR112017001250A BR112017001250A2 (pt) 2014-07-23 2015-04-07 processo e dispositivo de carga, dispositivo de acesso, processo e dispositivo de controle de qualidade de serviço
EP18155765.3A EP3410634A1 (en) 2014-07-23 2015-04-07 Charging methods, access device and charging device
US15/411,631 US10700879B2 (en) 2014-07-23 2017-01-20 Charging method and device, access device, service quality control method and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410352743.5 2014-07-23
CN201410352743.5A CN105338506B (zh) 2014-07-23 2014-07-23 计费方法和设备、接入设备、服务质量控制方法和设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/411,631 Continuation US10700879B2 (en) 2014-07-23 2017-01-20 Charging method and device, access device, service quality control method and device

Publications (1)

Publication Number Publication Date
WO2016011831A1 true WO2016011831A1 (zh) 2016-01-28

Family

ID=55162484

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/075984 WO2016011831A1 (zh) 2014-07-23 2015-04-07 计费方法和设备、接入设备、服务质量控制方法和设备

Country Status (6)

Country Link
US (1) US10700879B2 (zh)
EP (2) EP3163795B1 (zh)
JP (1) JP6552068B2 (zh)
CN (1) CN105338506B (zh)
BR (1) BR112017001250A2 (zh)
WO (1) WO2016011831A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107786765A (zh) * 2016-08-25 2018-03-09 中兴通讯股份有限公司 一种信息交互方法和装置

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105338506B (zh) * 2014-07-23 2019-05-28 华为技术有限公司 计费方法和设备、接入设备、服务质量控制方法和设备
CN108712586B (zh) * 2018-04-12 2020-08-28 合肥天源迪科信息技术有限公司 一种信控提醒方法及装置
KR102472177B1 (ko) * 2018-06-20 2022-11-28 주식회사 케이티 어플리케이션별 실시간 서비스 품질 관리가 가능한 서비스 제공 시스템 및 그 방법

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101098293A (zh) * 2006-06-26 2008-01-02 西门子通信技术（北京）有限公司 一种通用分组无线业务网络网关支持节点装置及计费方法
US20090307312A1 (en) * 2008-06-10 2009-12-10 Vianix Delaware, Llc System and Method for Signaling and Media Protocol for Multi-Channel Recording
CN103684803A (zh) * 2013-12-11 2014-03-26 中国联合网络通信集团有限公司 流量采集装置和定向流量计费系统和方法
CN104053140A (zh) * 2014-06-11 2014-09-17 中兴通讯股份有限公司 服务提供方法、装置及系统

Family Cites Families (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3895165B2 (ja) 2001-12-03 2007-03-22 株式会社エヌ・ティ・ティ・ドコモ 通信制御システム、通信制御方法、通信基地局及び移動端末
JP2009033269A (ja) * 2007-07-24 2009-02-12 Sony Corp 帯域制御システム、端末装置、管理サーバ、帯域制御方法とそのプログラム
JP5115091B2 (ja) 2007-08-14 2013-01-09 ソニー株式会社 制御装置、コンテンツ送信システム及びコンテンツ送信方法
CN101257394A (zh) * 2008-04-14 2008-09-03 北京首信科技有限公司 一种在线实时内容计费的方法
US7937300B2 (en) * 2008-07-10 2011-05-03 Bridgewater Systems Corp. System and method for providing interoperability between diameter policy control and charging in a 3GPP network
US10200541B2 (en) * 2009-01-28 2019-02-05 Headwater Research Llc Wireless end-user device with divided user space/kernel space traffic policy system
US8745191B2 (en) * 2009-01-28 2014-06-03 Headwater Partners I Llc System and method for providing user notifications
KR101411329B1 (ko) * 2009-06-30 2014-06-25 알까뗄 루슨트 수익 배당을 갖는 엔티티 마다 과금 데이터를 생성하는 프론트 엔드 과금 시스템
CN101998682A (zh) * 2009-08-27 2011-03-30 中兴通讯股份有限公司 一种个人网设备获取业务内容的装置、方法及相关装置
US8473379B2 (en) * 2009-12-30 2013-06-25 Telefonaktiebolaget L M Ericsson (Publ) Dynamic centralized unit determination in a credit control charging system
CN102142966B (zh) * 2010-06-13 2014-05-07 华为技术有限公司 基于业务嵌套计费的业务关联方法、装置和系统
EP2458779A1 (en) * 2010-11-29 2012-05-30 Telefonaktiebolaget L M Ericsson (Publ) Usage-sensitive policy and charging control method, servers, systems and computer programs
KR101941634B1 (ko) * 2011-01-28 2019-01-24 삼성전자 주식회사 이동통신 시스템의 과금 제어장치 및 방법
US9489666B2 (en) * 2011-04-29 2016-11-08 Verizon Patent And Licensing Inc. Methods and systems for providing subsidized access to network content
US9526004B2 (en) * 2011-06-15 2016-12-20 Orange Method of and apparatus for providing an indication of data consumption
US9396482B2 (en) * 2011-08-31 2016-07-19 Verizon Patent And Licensing Inc. Data usage plan associated with user device
JP4911737B1 (ja) 2011-09-09 2012-04-04 株式会社アクティス 通信速度制御システム
CN103220158B (zh) * 2012-01-21 2016-12-14 阿尔卡特朗讯 一种对赞助数据应用进行计费控制的方法与设备
CN103220651A (zh) * 2012-01-21 2013-07-24 阿尔卡特朗讯 一种对应用层数据进行计费控制的方法与设备
WO2013133676A1 (ko) * 2012-03-08 2013-09-12 삼성전자 주식회사 무선 통신 시스템에서 무선 억세스 네트워크의 트래픽 제어 방법 및 장치
CN102811135B (zh) * 2012-08-20 2015-04-29 中国联合网络通信集团有限公司 流量通知系统及方法
US9660818B2 (en) * 2012-08-27 2017-05-23 Telefonktiebolaget Lm Ericsson (Publ) Advanced service-aware policy and charging control methods, network nodes, and computer programs
US9699323B2 (en) * 2013-06-28 2017-07-04 Alcatel Lucent Separate charging for supplemental content in a data flow
WO2015017716A1 (en) * 2013-07-31 2015-02-05 Opanga Networks, Inc. Pre-delivery of content to a user device
EP3039815A1 (en) * 2013-08-29 2016-07-06 Telefonaktiebolaget LM Ericsson (publ) A node and method for service usage reporting and quota establishment
US9413900B2 (en) * 2014-03-24 2016-08-09 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for online charging of pre-fetched content
CN105338506B (zh) * 2014-07-23 2019-05-28 华为技术有限公司 计费方法和设备、接入设备、服务质量控制方法和设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101098293A (zh) * 2006-06-26 2008-01-02 西门子通信技术（北京）有限公司 一种通用分组无线业务网络网关支持节点装置及计费方法
US20090307312A1 (en) * 2008-06-10 2009-12-10 Vianix Delaware, Llc System and Method for Signaling and Media Protocol for Multi-Channel Recording
CN103684803A (zh) * 2013-12-11 2014-03-26 中国联合网络通信集团有限公司 流量采集装置和定向流量计费系统和方法
CN104053140A (zh) * 2014-06-11 2014-09-17 中兴通讯股份有限公司 服务提供方法、装置及系统

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107786765A (zh) * 2016-08-25 2018-03-09 中兴通讯股份有限公司 一种信息交互方法和装置
CN107786765B (zh) * 2016-08-25 2020-12-18 中兴通讯股份有限公司 一种信息交互方法和装置

Also Published As

Publication number Publication date
EP3163795A1 (en) 2017-05-03
JP2017522819A (ja) 2017-08-10
EP3410634A1 (en) 2018-12-05
CN105338506B (zh) 2019-05-28
BR112017001250A2 (pt) 2017-11-28
EP3163795A4 (en) 2017-05-10
EP3163795B1 (en) 2018-06-13
JP6552068B2 (ja) 2019-07-31
CN105338506A (zh) 2016-02-17
US10700879B2 (en) 2020-06-30
US20170134177A1 (en) 2017-05-11

Similar Documents

Publication Publication Date Title
US11601555B2 (en) Methods and apparatuses for service layer charging correlation with underlying networks
US9014663B2 (en) Sponsored data plan management
US10075303B2 (en) Method and apparatus for performing charging control to a sponsored data application
US20200267008A1 (en) Api content based charging method and capability exposure function entity
JP5947403B2 (ja) アプリケーション層データに対して課金制御を実行するための方法および装置
JP2012517725A5 (zh)
EP2695402A2 (en) Methods and apparatus for managing data connectivity
US11108720B2 (en) Upsell framework for network services
US11503442B2 (en) Methods of enabling flexible charging in M2M IoT service layer
US10700879B2 (en) Charging method and device, access device, service quality control method and device
WO2012164384A1 (en) Method and apparatus for charging in a communication network
WO2016078443A1 (zh) 基于4g网络的流量红包控制方法及系统
WO2015062026A1 (zh) 应用服务器、终端设备、网络能力调用系统及方法
WO2014153720A1 (zh) 计费方法、接入设备和计费设备
OA18992A (en) Method to push toll-free applications to a user device

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15824591

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2017503587

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2015824591

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2015824591

Country of ref document: EP

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112017001250

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 112017001250

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20170119