WO2013097652A1 - 一种用户带宽通知方法 - Google Patents

一种用户带宽通知方法 Download PDF

Info

Publication number
WO2013097652A1
WO2013097652A1 PCT/CN2012/087151 CN2012087151W WO2013097652A1 WO 2013097652 A1 WO2013097652 A1 WO 2013097652A1 CN 2012087151 W CN2012087151 W CN 2012087151W WO 2013097652 A1 WO2013097652 A1 WO 2013097652A1
Authority
WO
WIPO (PCT)
Prior art keywords
bandwidth
user
service
network side
requirement
Prior art date
Application number
PCT/CN2012/087151
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 EP12862462.4A priority Critical patent/EP2787695A4/en
Priority to RU2014131724/07A priority patent/RU2582573C2/ru
Publication of WO2013097652A1 publication Critical patent/WO2013097652A1/zh
Priority to US14/319,245 priority patent/US20140317280A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/04—Processing captured monitoring data, e.g. for logfile generation
    • H04L43/045—Processing captured monitoring data, e.g. for logfile generation for graphical visualisation of monitoring data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0876—Network utilisation, e.g. volume of load or congestion level
    • H04L43/0882—Utilisation of link capacity
    • 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/1432—Metric aspects
    • 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/5061—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the interaction between service providers and their network customers, e.g. customer relationship management
    • H04L41/5067—Customer-centric QoS measurements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/75—Indicating network or usage conditions on the user display

Definitions

  • the present invention relates to the field of communications, and in particular, to a user bandwidth notification method. Background technique
  • the prior art basically detects the user's network speed through the terminal, and reminds the user to wait for the cache to solve the problem when the user's network speed is insufficient. For example, ppstream software, when the user bandwidth is small, will prompt the user "current network is not strong, please buffer wait”.
  • PCEF Policy and Charging Enforcement Function
  • the embodiment of the invention provides a user bandwidth notification method, which is used to solve the technical problem that the network side cannot sense the actual bandwidth of the user in time and the user experience is poor.
  • an embodiment of the present invention provides a user bandwidth notification method, where the method includes:
  • the network side detects the available bandwidth of the user and the bandwidth requirement of the service currently used by the user, and the network side compares the available bandwidth of the user with the bandwidth requirement of the service currently used by the user, and the network side notifies the user according to the comparison result.
  • Bandwidth status The embodiment of the invention further provides a method for detecting user experience quality QoE, the method comprising:
  • the network side detects the available bandwidth of the user and the bandwidth requirement of the service currently used by the user, and the network side compares the available bandwidth of the user with the bandwidth requirement of the service currently used by the user, and the network side determines the user according to the comparison result. QoE.
  • the embodiment of the invention further provides a gateway, where the gateway includes a bandwidth detecting unit and a policy execution unit;
  • the bandwidth detecting unit is configured to detect a service bandwidth requirement of the user, and report the service bandwidth requirement to the bandwidth determining network element.
  • the policy execution unit is configured to: when the bandwidth determining network element determines that the bandwidth is insufficient according to the obtained available bandwidth of the user and the service bandwidth requirement reported by the bandwidth detecting unit, the user bandwidth is increased.
  • the embodiment of the present invention further provides a charging device, where the charging device includes a service bandwidth requirement acquiring unit, a user available bandwidth acquiring unit, a determining unit, and a notification unit;
  • the service bandwidth requirement obtaining unit is configured to receive a service bandwidth requirement sent by the gateway;
  • the user available bandwidth acquiring unit is configured to acquire a user available bandwidth;
  • the determining unit is configured to compare the available bandwidth of the user with the service bandwidth requirement, and determine whether the available bandwidth of the user is sufficient;
  • the notification unit is configured to notify the user of the available bandwidth status according to the determination result of the determining unit.
  • the embodiment of the present invention further provides a client, where the client includes: a notification information receiving unit and a bandwidth adjustment triggering unit;
  • the notification information receiving unit is configured to receive, after the network side compares the available bandwidth of the user and the bandwidth requirement of the service currently used by the user, the bandwidth status notification information, where the bandwidth status notification information includes:
  • the bandwidth adjustment triggering unit is configured to send a bandwidth adjustment request to the network side according to the bandwidth adjustment triggering manner carried in the bandwidth status notification information, and trigger the network by using the bandwidth adjustment request.
  • the side adjusts the bandwidth product of the user, and the adjustment includes at least one of bandwidth upgrade, subscription or trial bandwidth products.
  • the technical solution provided by the embodiment of the present invention implements monitoring the bandwidth satisfaction of the current service of the user from the network side and notifying the user, so that the network side can timely sense the bandwidth experience when the user actually uses the service.
  • FIG. 1 is a flowchart of a bandwidth notification method according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a QoE detection method according to an embodiment of the present invention.
  • FIG. 3 is a flowchart of a user bandwidth adjustment method according to an embodiment of the present invention.
  • FIG. 4 is a system architecture diagram of implementing user bandwidth adjustment according to an embodiment of the present invention.
  • FIG. 5 is a signaling flowchart of implementing user bandwidth adjustment according to an embodiment of the present invention.
  • FIG. 6 is a schematic diagram of a gateway according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic diagram of a charging apparatus according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of a user client according to an embodiment of the present invention. detailed description
  • a flowchart of a bandwidth notification method according to an embodiment of the present invention includes the following steps:
  • Step 101 The network side detects the bandwidth available to the user and the bandwidth requirement of the service currently used by the user.
  • the method for detecting the available bandwidth of the user on the network side may use a static method and a dynamic method:
  • the method may include acquiring a package subscribed by the user.
  • the maximum bandwidth of the user for example, through the customer's customer subscription record, the user's subscription monthly subscription is 30 yuan, packet traffic is 200M, 1M bandwidth, then the user's current maximum possible bandwidth is 1M, that is, the network side detects the user's available.
  • the maximum bandwidth is 1M;
  • the network side can also detect the current available bandwidth of the user in real time.
  • the software can be configured to send a detection command to the user software when the user needs to detect the current available bandwidth of the user, and the user client software is required to report the user.
  • the current bandwidth information or the user client software periodically, or the event-triggered mechanism, reports the current available bandwidth information. Further, it can detect the service bandwidth occupied by each service currently running, or the current service usage. The percentage of total business bandwidth, etc.
  • the network side also needs to obtain the bandwidth requirements of the service currently used by the user. Generally, the network side obtains the minimum bandwidth requirement of the service source currently used by the user;
  • the data network PCEF entity judges the service according to the media information delivered by the service source, such as the bit rate in the Session Description Protocol (SDP). Bandwidth requirements;
  • SDP Session Description Protocol
  • the network side can also directly read the bandwidth requirements of each service configured in the system.
  • the network side can check the registration information of the service currently used by the user through the charging system, and obtain the bandwidth requirement of the current service used by the user. For example, when the Youku business is released in the BSS (Billing Support System), the minimum bandwidth requirement of the Youku website video service is marked.
  • BSS Biting Support System
  • the maximum bandwidth requirement of the currently used service of the user may be obtained.
  • the media description information delivered by the service source and the bandwidth requirement of each service configured in the system may be determined.
  • the current bandwidth requirement of the current service is used to compare with the current network bandwidth of the user.
  • the bandwidth requirement of the current service can be determined based on the SDP information sent by the service source. If the SDP information cannot be obtained, the The configuration information is not limited in the embodiment of the present invention.
  • Step 102 The network side compares the available bandwidth of the user with the bandwidth requirement of the service currently used by the user.
  • the network side compares the two. In general, it is judged whether the current available bandwidth of the user is sufficient relative to the service used by the current user. Specifically, the insufficient bandwidth judgment performed by the network side may be comparing the current available bandwidth of the user with the minimum bandwidth requirement of the currently used service; when the current bandwidth of the user is less than the minimum bandwidth requirement of the service source, the available bandwidth of the user is considered to be insufficient.
  • the network side can also compare the current available bandwidth of the user with the maximum bandwidth requirement of the currently used service (that is, the bandwidth requirement that can fully realize the service effect); or, the network side can also perform bandwidth redundancy. Judging, that is, comparing the current available bandwidth of the user with the bandwidth requirement of the currently used service, if the currently available bandwidth is significantly larger than the currently used service bandwidth requirement, or significantly larger than the bandwidth of all services used in the user history (a period of time before detection) If required, it is considered that the available bandwidth of the user is too large, or bandwidth redundancy;
  • the network side can obtain the network bandwidth requirements of all services together, and then summarize (sum, or calculate a summary according to some algorithm). Value), and then used to compare with the available bandwidth of the user; it is also possible to summarize only the bandwidth requirements of some services, and then compare it with the available bandwidth of the user; of course, it is also possible to use only a single service with the highest bandwidth requirement.
  • the user can compare the available bandwidth.
  • the specific comparison manner is not limited in the embodiment of the present invention.
  • the operator or the client may only allocate a certain percentage of network bandwidth to a certain type of service or a certain service, or limit the maximum or proportion of bandwidth occupied by a certain type or a type of service.
  • the available bandwidth of the user compared with the current service bandwidth requirement may be the total bandwidth currently available to the user, for example, a percentage of the total bandwidth of the user. Therefore, in the embodiment of the present invention, the available bandwidth of the user to be compared with the bandwidth requirement of the service currently used by the user is not limited to the current total bandwidth of the user, but may be the available bandwidth of the current service, and the total bandwidth of the user is fixed.
  • Step 103 The network side notifies the user of the bandwidth status according to the comparison result.
  • the network side determines that the available bandwidth of the user is insufficient, the user performs a bandwidth status notification.
  • the specific notification methods include but are not limited to: SMS (SMS), MMS (MMS), E-mail, ODP (On Device Portal) client.
  • SMS SMS
  • MMS MMS
  • E-mail E-mail
  • ODP On Device Portal
  • the real-time reminder and the like are not limited herein.
  • the method of the embodiment of the present invention implements monitoring the bandwidth satisfaction of the current service of the user from the network side and notifying the user, so that the network side can timely sense the bandwidth usage experience when the user actually uses various services, and notify the user. In many cases, when a user uses certain services, the experience is poor due to network bandwidth problems. Therefore, the method of the embodiment of the present invention can provide a clear understanding of the current service experience due to user bandwidth conditions (such as The use of the package case) and the current service bandwidth requirements do not match, so that appropriate measures can be taken to address and resolve.
  • user bandwidth conditions such as The use of
  • the network information may be carried in the notification information, the trial information, or the upgrade information, so that the user can further understand how to solve the problem of insufficient bandwidth.
  • the embodiment of the present invention further provides a QoE (Quality of Experience) detection method.
  • QoE is a concept related to QoS (Quality of Service).
  • ITU-T Rec E.800 originally defined QoS as "a comprehensive effect of service performance that determines user satisfaction" and includes a wide range of content.
  • QoS is narrowly understood as the performance indicators of the underlying packet data transmission, such as delay, jitter, bandwidth, and bit error.
  • Each performance indicator defines a separate KPI (key performance index).
  • KPI key performance index
  • QoS is not equal to QoE.
  • the KPI of common QoS in the network is very good, but the user experience is not good. Because QoE is measured from the perspective of the end user, it is an end-to-end concept.
  • QoE Quality of Experience
  • FIG. 2 is a flowchart of a QoE detection method according to an embodiment of a method of the present invention, where the method includes the following steps:
  • Step 201 The network side detects the bandwidth available to the user and the bandwidth requirement of the service currently used by the user.
  • Step 202 The network side compares the available bandwidth of the user with the bandwidth requirement of the service currently used by the user.
  • Step 203 The network side determines the QoE value of the user network according to the comparison result; compares the current available bandwidth of the user with the bandwidth requirement of the currently used service source; and when the current available bandwidth of the user is less than the bandwidth requirement of the service source , it is considered that the user may have poor QoE, and conversely, the user QoE is considered to meet the requirement.
  • the steps include:
  • Step 204 The network side notifies the user of the QoE situation, and collects feedback information about the QoE situation of the user;
  • the network side can:
  • the user When the QoE is poor, the user is notified that "the network bandwidth is insufficient to support the current business needs, please click the button to confirm whether it is true", and then, through the user click the Yes or No button, the user's feedback on the QoE situation is collected.
  • the user may not need to be notified and request feedback from the user to avoid unnecessary interference to the user.
  • the network information may be included in the notification information. Trial or upgrade information, so that users can further understand how to solve the current problem of poor QoE and enhance the user experience.
  • FIG. 3 is a flowchart of a user bandwidth adjustment method according to an embodiment of the present invention, where the method includes:
  • Step 301 The network side detects the bandwidth available to the user and the bandwidth requirement of the service currently used by the user.
  • Step 302 The network side compares the available bandwidth of the user with the bandwidth requirement of the service currently used by the user.
  • Step 303 The network side determines, according to the comparison result, whether the current bandwidth is sufficient.
  • the notification information for notifying the user of the bandwidth status includes a triggering manner that allows the user to directly trigger a bandwidth upgrade, a bandwidth subscription, or a bandwidth trial; for example, a bandwidth subscription, that is, a product upgrade, or a trial hyperlink; After clicking the hyperlink, you can directly enter the carrier's bandwidth order, upgrade, or trial page, or even directly order bandwidth, upgrade or trial, without the need to operate through other channels;
  • the network side can also select a suitable recommended package product according to the user information: for example, according to the user's local area, frequently accessed business types, user's age, occupation and other information, the user is recommended to the appropriate package product.
  • Step 305 The user needs to increase the bandwidth, selects a product trial, and the network side temporarily increases the bandwidth for the user;
  • Step 306 After the user trial period has elapsed, confirm to the user whether to order the official product. If the user confirms the formal order, proceed to step 307 to perform bandwidth adjustment. If the formal order is not performed, proceed to step 308 to restore the original user. Bandwidth
  • Step 307 For the user to directly order the bandwidth product and after the trial period, the user subscribes to the official product, adjusts the bandwidth for the user, and upgrades the user bandwidth;
  • Step 308 After the user trial period has elapsed, if the formal subscription is no longer performed, the original bandwidth of the user is restored;
  • Step 309 After a series of judgments and processing procedures, the user continues to use the business.
  • the user can adjust the bandwidth of the user directly by using the PCRF, the PCEF, and the charging system on the network side, and the adjustment may be real-time or according to a certain policy. Delay adjustment.
  • the user's current bandwidth can be temporarily upgraded, and the user is given a certain trial period for the increased bandwidth. After the trial period expires, the user is notified whether it is required to order a formal upgrade product (bandwidth), and then The user's selection proceeds to the next step. For example, when the user chooses to order the official product, the bandwidth adjustment is performed, and when the user chooses not to order the trial product, the user's previous bandwidth is restored. In addition, if the network side determines that the bandwidth is sufficient to support the current service, the user does not need to perform bandwidth adjustment notification for the user.
  • the method of the embodiment of the invention enables the network side to timely sense the bandwidth usage experience when the user actually uses various services, and gives the user a prompt, so that the user can understand the current network bandwidth status, and clearly understand the current network bandwidth product situation and use. Further, in the embodiment of the present invention, by carrying the product recommendation information in the notification message and/or triggering the trigger mode for the user to directly upgrade or try the product, the user can more conveniently try or upgrade the broadband product. , enhance the user experience.
  • FIG. 4 it is a system architecture diagram for implementing bandwidth adjustment according to an embodiment of the present invention.
  • the system includes a service gateway 401 (with PCEF function), a convergent charging system 402, a policy generation PCRF network element 403, and an ODP.
  • the server 404 and the ODP-capable terminal 405 can provide capabilities such as bandwidth notification, QoE detection, bandwidth adjustment reminder, bandwidth product upgrade, order or trial, and flexible billing, in conjunction with the signaling flow diagram 5 described later.
  • the system in this embodiment can support the real-time notification mode of the page pop-up, the notification mode such as SMS/MMS, and the ODP terminal and the ODP server.
  • the basic functions of each network element are detailed below:
  • the service gateway 401 (with PCEF function):
  • the service gateway provided by the embodiment of the present invention can be modified based on the function of the traditional data service gateway, and the new "bandwidth detection” and “strategy execution” capabilities are added;
  • PCRF Policy Generation
  • Converged billing system 402 can be implemented based on a traditional billing system, providing functions such as flexible billing, account management, product management, and notification triggering;
  • the ODP server 404 and the ODP client 405 The embodiment of the present invention adds a network element to provide self-service, notification, and the like for the terminal user.
  • a user bandwidth is implemented by using the system in FIG. Adjusted signaling flow chart.
  • Step 501 The user initiates a service access request.
  • the user initiates a service access request through a web browser on the client or a software client.
  • Steps 502-503 The service gateway with the PCEF function initiates service bandwidth requirement detection; that is, it determines the network bandwidth in which the user can use the current service to have a better experience.
  • PCEF can detect the current service bandwidth requirements by using the dynamic detection method of service bandwidth requirements;
  • the dynamic detection of the service bandwidth requirement means that when the user accesses the multimedia service, the PCEF entity can determine the service according to the media description information in the service source interaction signaling (if the signaling is carried).
  • the PCEF reports the service access request of the user to the charging system, and the reporting message may carry the currently accessed service ID, and the subsequent charging system performs authentication and charging according to the ID. Meanwhile, the reporting message is optional.
  • the required bandwidth value can be carried by a public AVP (Attribute Value Pair), such as a Service-Information field, or by a Vendor AVP.
  • the service gateway can obtain the bandwidth requirements of multiple running services occupying the network bandwidth.
  • Steps 504-505 Business authority judgment; This step is optional.
  • the billing system can first authenticate the user's service access and determine whether the user has the right to use the service. If there is no permission, the user's current service access request is directly denied, and the service access is terminated. If there is permission to access, the service is normally interacted. access.
  • Step 506 The bandwidth is insufficient to determine; the bandwidth shortage judgment is to compare the current available bandwidth of the user with the bandwidth requirement of the currently used service source; when the current available bandwidth of the user is less than the bandwidth requirement of the service source, the user may consider that the user may have poor QoE;
  • the bandwidth shortage judgment is to compare the current available bandwidth of the user with the bandwidth requirement of the currently used service source; when the current available bandwidth of the user is less than the bandwidth requirement of the service source, the user may consider that the user may have poor QoE;
  • the convergent charging system can use the static acquisition method, that is, the query
  • the package ordered by the user determines the maximum bandwidth that the user is currently in effect. For example, the monthly subscription ordered by the user is
  • the user's current maximum possible bandwidth is 1M; of course, the current bandwidth of the user can be detected in real time, which may include: through the software deployed on the user end, when it is necessary to detect the current bandwidth of the user, The client software sends a detection command, and the user client software is required to report the current bandwidth information of the user; or the client software periodically reports the bandwidth status; when the condition is met (for example, the bandwidth is reduced to a certain threshold), the client software is triggered to report;
  • the converged charging system can preferentially use the data reported by the PCEF in the foregoing step 503. If the PCEF fails to obtain the data due to the failure to obtain the data or other reasons, the converged charging system can obtain the data locally.
  • the method for obtaining the bandwidth requirement of the service source from the local charging system may be: reading the static data of the bandwidth requirement of the corresponding service configured in the system according to the service ID reported by the PCEF; for example, the service accessed by the PCEF reported by the PCEF according to the service ID.
  • the type is the Youku video service, and the charging system reads the configuration information of the local Youku video service to obtain the bandwidth requirement of the service.
  • the current solution cannot determine the current user's QoE, in which case The system can default the user's QoE to meet the user's needs, that is, the user's current bandwidth is sufficient to meet the business needs, and no reminder is sent to the user.
  • Step 507 Trigger real-time notification; if the billing system determines that the current bandwidth condition of the user is poor, the insufficient bandwidth notification may be sent to the ODP server.
  • Notification messages can include notification types (such as: "QoE Insufficient" message), target users (such as users currently using the service), recommended product information that meets the bandwidth requirements of the service source, that is, recommended higher bandwidth products, such as product list ID .
  • Step 508 The reminder mode is judged; the ODP Server can select an appropriate reminder mode according to the user state, and the reminder modes include but are not limited to SMS, MMS, email, real-time reminder of the ODP client, and the like.
  • Step 509 The reminder message is pushed: the ODP server sends the reminder message to the user terminal according to the insufficient bandwidth notification content sent by the charging system, and the user is reminded that the available bandwidth is insufficient.
  • the reminder message may include the bandwidth product recommendation information, the product upgrade message, or Product trial messages, etc., sent to the user;
  • the "Bandwidth Product Recommendation" message sent to the user by the ODP server can include the message type (with Wide product recommendation), a list of recommended products that meet the bandwidth requirements of the business source and a description of each product.
  • Each product description can be extracted from a locally stored product description information base based on the product ID received from the billing system.
  • the delay message may be further sent.
  • the purpose of the delay is to allow the user to actually experience the current service experience for a period of time.
  • the time interval for delaying the reminder bandwidth may be configured on the ODP server.
  • the reminder mode is real-time reminder of the ODP client
  • a reminder dialog box will pop up in real time on the user's mobile client to remind the user.
  • the reminder content may include: recommended products, trial packages, detailed descriptions, trial validity periods (cycles, cumulative traffic, access times, etc.), and trial fees (set by the operator, can be set to free).
  • Step 510 The user self-selects; because the message sent by the ODP server carries the product recommendation information, the trial information, and the corresponding trigger mode, the user can directly select the recommended or trial product; if the user agrees to try it first, the user can directly Click on "Trial" bandwidth product on the ODP message.
  • Step 511-512 The terminal (ODP Client) initiates a product trial request; the ODP Server forwards the request to the converged billing system.
  • the terminal can also directly initiate a product subscription or upgrade request.
  • other network elements do not need to implement the trial period limit, but can directly change the user bandwidth.
  • Step 513 The billing system performs product order processing; the billing system performs a trial product ordering operation, and records the order relationship between the user and the trial product.
  • Steps 514-516 The product is successfully tested, the user QoS is adjusted, the charging system notifies the PCRF user of the order relationship change, and the QoS policy is updated and delivered; the PCRF generates a new QoS policy according to the user's new product ordering relationship and the service usage information. .
  • the PCRF In this real-time example, if the user tries to use the high-bandwidth package, the PCRF generates a bandwidth-raising strategy and sends several parameters to be monitored: including the accumulated access duration, accumulated traffic, and accumulated access times.
  • Step 517 The PCRF sends a new QoS policy to the service gateway PCEF; the PCEF performs local Policy update to increase the bandwidth of the user;
  • Step 518-519 Trial of the ordering result display process: The billing system returns the ordering result to the ODP Server; the ODP Server pushes the trial result to the terminal (ODP Client), and the ODP Client presents the result to the user; the user continues the service access.
  • the service gateway PCEF interacts with the converged charging system to complete the service charging process (in this embodiment, it is free), and reports the user's access time, access traffic, number of accesses, etc., and the charging system performs the charging system. Cumulative statistics.
  • Steps 520-522 After the trial product fails, the QoS is adjusted in real time: Since the billing system records the usage of the user package product (accumulated access duration, accumulated traffic, cumulative access times, etc.), when the user subscribes for the high bandwidth trial product is invalid Time (product combination period, duration, flow rate, number of visits, etc.), the billing system updates the user's order relationship; the billing system triggers the QoS policy refresh, and restores the user bandwidth in real time (the network element interaction process is consistent with the product trial process); The user pushes the trial expiration reminder, and the reminder content includes the formal product recommendation (the network element interaction process is similar to the trial success notification).
  • the method of the embodiment of the invention can implement the functions of bandwidth notification, QoE detection, bandwidth adjustment reminder, bandwidth product upgrade, ordering or trial, flexible charging, etc., thereby improving the user's bandwidth perception and making the user more convenient to adjust the bandwidth. Flexible and improved user experience.
  • FIG. 6 is a schematic diagram of a gateway 600 according to an embodiment of the present invention, for performing the corresponding method steps in the foregoing embodiments, where the gateway includes a bandwidth detecting unit 601 and a policy executing unit 602:
  • the bandwidth detecting unit 601 is configured to detect a service bandwidth requirement of the user according to the service access request, and report the service bandwidth requirement to the bandwidth determining network element.
  • the bandwidth detecting unit 601 can determine a bandwidth requirement of the service according to the media description information in the service source interaction signaling.
  • the bandwidth determining network element may be specifically a charging system; or may be other network elements;
  • the policy execution unit 602 is configured to: when the bandwidth determining network element determines that the bandwidth is insufficient according to the obtained available bandwidth of the user and the service bandwidth requirement reported by the bandwidth detecting unit 601, the user bandwidth is increased.
  • FIG. 7 is a schematic diagram of a charging apparatus 700 according to an embodiment of the present invention, for performing the corresponding method steps in the foregoing embodiments, where the charging apparatus includes:
  • the service bandwidth requirement obtaining unit 701 is configured to receive a service bandwidth requirement sent by the gateway, and the user available bandwidth obtaining unit 702 is configured to acquire the available bandwidth of the user.
  • the user available bandwidth obtaining unit 702 can obtain the maximum bandwidth that the user is currently in effect by querying the package that the user subscribes to; or the user available bandwidth obtaining unit 702 can send a detection command to the client software, and request the user client software to report the current bandwidth of the user.
  • the user information is used to periodically report the bandwidth status.
  • the user-usable bandwidth acquisition unit 702 obtains the available bandwidth information reported by the client software.
  • the determining unit 703 is configured to compare the available bandwidth of the user and the bandwidth requirement of the service currently used by the user, and determine whether the available bandwidth of the user is sufficient; the determining unit 703 determines whether the available bandwidth of the user is sufficient, and the method in the foregoing step 102
  • the method in the foregoing step 102 For similar details and implementation manners, reference may be made to the related description in the foregoing step 102.
  • the notification unit 704 is configured to notify the user of the available bandwidth status according to the determination result of the determining unit.
  • the notification unit 704 may further carry information that requires the user to confirm the QoE in the notification information notifying the user of the available bandwidth status, so that the user confirms and feeds back the QoE situation according to the information; the notification unit 704 may further include the bandwidth product in the notification information.
  • Recommended information, product trial or upgrade information can further include triggers that allow users to directly trigger bandwidth upgrades, bandwidth subscriptions, or bandwidth trials.
  • FIG. 8 is a schematic diagram of a user client 800 according to an embodiment of the present invention, which is used to perform the corresponding steps of the foregoing methods in the foregoing embodiments.
  • the client 800 may be in various forms, such as a mobile terminal and a PC terminal.
  • the user client 800 includes:
  • the notification information receiving unit 801 is configured to receive the bandwidth status notification information sent by the network side after comparing the available bandwidth of the user and the bandwidth requirement of the service currently used by the user;
  • the information includes a triggering manner that enables the user to trigger a bandwidth upgrade, a bandwidth subscription, or a bandwidth trial, where the bandwidth status notification information includes bandwidth product recommendation information, product trial or upgrade information;
  • the bandwidth adjustment triggering unit 802 is configured to send a bandwidth adjustment request to the network side according to the bandwidth adjustment triggering manner carried in the bandwidth status notification information, and trigger the network side to adjust the bandwidth product of the user by using the bandwidth adjustment request.
  • the adjustments include bandwidth upgrades, ordering or trial bandwidth products.
  • the network side can timely sense the bandwidth usage experience when the user actually uses various services, and give the user a prompt, so that the user can understand the current network bandwidth status, and the explicit Understand the current network bandwidth product situation and the comparison relationship between the services being used; further, by carrying the bandwidth product recommendation information in the bandwidth status notification information sent to the user and/or triggering the user to directly upgrade or try the product triggering manner, so that the user It is more convenient to try or upgrade broadband products to enhance user experience.
  • the content is based on the same concept as the method embodiment of the present invention.
  • the description in the method embodiment of the present invention and details are not described herein again.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM: Read-Only Memory), or a random access memory (RAM: Random Access Memory), etc., 1 , - , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Mining & Analysis (AREA)
  • Environmental & Geological Engineering (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Telephonic Communication Services (AREA)

Abstract

一种用户带宽通知方法，所述方法包括：网络侧检测用户可用带宽和用户当前使用的业务的带宽要求，网络侧比较所述用户当前可用带宽和所述用户当前使用的业务的带宽要求，网络侧根据所述比较结果，通知所述用户带宽状况。使用本发明，可以让用户明确的了解当前业务体验不佳是由于用户带宽状况和当前业务带宽需求不匹配导致的，并可以采取适当的措施应对和解决。

Description

一种用户带宽通知方法
技术领域
本发明涉及通信领域， 具体涉及一种用户带宽通知方法。 背景技术
各种通信网络现在已经成为人们生活中不可或缺的一部分， 网络运营商 根据不同用户的需要， 为用户定制了各种不同的网络套餐产品， 但是， 随着 各种网络应用的丰富和发展， 业务对带宽的要求也越来越高， 同时不同业务 对网络带宽的要求也不平衡， 例如， 相对于文字聊天的网络应用， 视频类业 务， 特别是高清视频业务对网络带宽的要求就要高很多。
现有技术基本是通过终端来检测用户的网速， 在用户网速不够时， 提醒 用户緩存等待来解决问题。 例如 ppstream软件， 在用户带宽较小时， 会提示 用户 "当前网络不给力， 请緩冲等待"。
有部分运营商通过 ( PCC Policy and charging control, 策略与计费控制架 构）来改善用户体验。 其方案的核心是用户自己判断当前的网络带宽体验， 在体验不好时， 用户自己主动向运营商订购带宽， 网络侧 PCEF ( Policy and Charging Enforcement Function , 策略与计费策略执行 ) 实体根据用户订购执 行带宽调整， 提升用户体验。
上述方案或者仅仅为客户端软件的自身行为， 或者是用户根据自己的主 观感受釆取的举动， 网络侧都无法及时感知用户实际的带宽使用体验。 发明内容
本发明实施例提供了一种用户带宽通知方法， 用于解决网络侧无法及时 感知用户实际带宽而导致用户体验不佳的技术问题。
为解决上述技术问题， 本发明实施例提供了一种用户带宽通知方法， 所 述方法包括：
网络侧检测用户可用带宽和所述用户当前使用的业务的带宽要求， 网络侧比较所述用户可用带宽和所述用户当前使用的业务的带宽要求， 网络侧根据所述比较结果， 通知所述用户带宽状况。 本发明实施例还提供了一种用户体验质量 QoE的检测方法， 所述方法 包括：
网络侧检测用户可用带宽和所述用户当前使用的业务的带宽要求， 网络侧比较所述用户可用带宽和所述用户当前使用的业务的带宽要求， 网络侧根据所述比较结果， 确定所述用户的 QoE。
本发明实施例还提供了一种网关， 所述网关包括带宽检测单元和策略执 行单元；
所述带宽检测单元， 用于检测用户业务带宽要求， 将所述业务带宽要求 上报到带宽判断网元；
所述策略执行单元， 用于当所述带宽判断网元根据获得的用户可用带宽 以及所述带宽检测单元上报的业务带宽要求， 判断带宽不足时， 提升用户带 宽。
本发明实施例还提供了一种计费装置 , 所述计费装置包括业务带宽要求 获取单元， 用户可用带宽获取单元， 判断单元和通知单元；
所述业务带宽要求获取单元， 用于接收网关发送的业务带宽要求； 所述用户可用带宽获取单元， 用于获取用户可用带宽；
所述判断单元， 用于比较所述用户可用带宽和所述业务带宽要求， 判断 用户可用带宽是否足够；
所述通知单元， 用于根据所述判断单元的判断结果， 通知用户可用带宽 状况。
本发明实施例还提供了一种客户端， 所述客户端包括： 通知信息接收单 元和带宽调整触发单元；
所述通知信息接收单元， 用于接收网络侧比较用户可用带宽和所述用户 当前使用的业务的带宽要求后， 下发的带宽状况通知信息； 所述带宽状况通 知信息包含让用户触发带宽升级， 带宽订购或者带宽试用的触发方式； 所述带宽调整触发单元， 用于根据所述带宽状况通知信息中携带的带宽 调整触发方式， 向网络侧发送带宽调整请求， 通过所述带宽调整请求， 触发 网络侧对所述用户的带宽产品进行调整， 所述调整包括带宽升级， 订购或者 试用带宽产品中的至少一种。 通过本发明实施例提供的技术方案， 实现了从网络侧监控用户当前业务 的带宽满足情况并通知用户，从而使网络侧能够及时感知用户实际使用业务 时候的带宽体验。 附图说明
为了更清楚地说明本发明实施例中的技术方案， 下面将对实施例描述中 所需要使用的附图作简单地介绍， 显而易见地， 下面描述中的附图仅仅是本 发明的一些实施例， 对于本领域普通技术人员来讲， 在不付出创造性劳动性 的前提下， 还可以根据这些附图获得其他的附图。
图 1为本发明实施例提供的一种带宽通知方法的流程图；
图 2为本发明实施例提供的一种 QoE检测方法流程图；
图 3为本发明实施例提供的一种用户带宽调整方法流程图；
图 4为本发明实施例提供的实现用户带宽调整的系统架构图；
图 5为本发明实施例提供的实现用户带宽调整的信令流程图；
图 6为本发明实施例提供的一种网关示意图；
图 7为本发明实施例提供的一种计费装置示意图；
图 8为本发明实施例提供的一种用户客户端示意图。 具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行 清楚、 完整地描述， 显然， 所描述的实施例仅仅是本发明一部分实施例， 而 不是全部的实施例。 基于本发明中的实施例， 本领域普通技术人员在没有作 出创造性劳动前提下所获得的所有其他实施例 , 都属于本发明保护的范围。
参考附图 1 , 为本发明实施例提供的一种带宽通知方法的流程图， 包括 下列步骤：
步骤 101 :网络侧检测用户可用带宽和用户当前使用的业务的带宽要求； 网络侧检测用户可用带宽的方法， 可以使用静态的方法和动态的方法： 对于静态的方法， 可以包括获取用户订购的套餐的最大带宽， 例如， 通 过运营商的客户订购记录， 获取用户订购的月套餐为 30元， 包流量 200M, 1M带宽，则可以确认用户的当前最大可能带宽为 1M, 即网络侧检测用户可 用的最大带宽为 1M; 网络侧也可以动态实时的检测用户当前可用带宽， 具体可以包括： 通过 部署在用户客户端的软件， 在需要检测用户当前可用带宽时， 向该用户端软 件发送检测命令， 要求用户客户端软件上报用户当前带宽情况信息， 或者用 户客户端软件定期， 或者以事件触发的机制进行当前可用带宽信息上报； 进 一步的， 可以检测当前运行的各项业务分别占用的业务带宽， 或者当前运行 的各项业务占用的总的业务带宽的百分比等。
网络侧还需要获取用户当前使用的业务的带宽要求。 一般来说， 网络侧 获取的是用户当前使用的业务源的最低带宽要求；
对于如何识别业务源的带宽要求， 可以釆用动态识别的方法， 即数据网 络 PCEF 实体根据业务源下发的媒体信息， 如 SDP ( Session Description Protocol, 会话描述协议） 中的比特率， 来判断业务的带宽要求；
另外， 网络侧也可以直接读取系统中配置的各业务的带宽要求， 如网络 侧可以通过计费系统检查用户当前使用业务的注册信息，得到所述用户当前 使用业务的带宽要求。 例如在 BSS ( Billing Support System, 计费支持系统） 中发布优酷业务时， 标注了的优酷网站视频业务的最低带宽要求。
除了获取最低带宽要求以外，也可以是获取用户当前使用业务的最大带 宽要求； 另外， 还可以同时根据业务源下发的媒体描述信息， 以及读取系统 中配置的各业务的带宽要求， 来确定实际釆用的当前业务的带宽要求， 以用 于和用户当前网络带宽进行比较； 还可以优先根据业务源下发的 SDP信息， 确定当前业务的带宽要求， 如果无法通过 SDP信息获取， 再进一步通过读 取系统中的配置信息获取， 本发明实施例在此不作限定。
由于用户可能同时运行了两个或者以上需要占用网络带宽的业务， 因此 网络侧可以获得多个正在运行的占用网络带宽的业务的带宽要求。 步骤 102: 网络侧比较所述用户可用带宽和所述用户当前使用的业务的 带宽要求；
根据前述获取的用户可用带宽和用户当前使用的业务的带宽要求， 网络 侧将上述两者进行比较。 一般来说， 会进行相对当前用户使用的业务来说， 用户当前可用带宽是否足够的判断。 具体的， 网络侧进行的带宽不足判断， 可以是比较用户当前的可用带宽 和当前使用的业务的最低带宽要求； 当用户的当前带宽小于业务源的最低带 宽要求， 则认为用户可用带宽不足。
基于不同的目的， 网络侧也可以比较用户当前的可用带宽和当前使用的 业务的最大带宽要求 （亦即， 能使得业务效果得到充分实现的带宽要求）； 或者， 网络侧也可以进行带宽冗余的判断， 即比较用户当前可用带宽和当前 使用的业务的带宽要求，如果当前可用带宽显著大于当前使用的业务带宽要 求， 或者显著大于用户历史上（检测前一段时间）使用过的所有业务的带宽 要求， 则认为用户可用带宽过大， 或者说带宽冗余；
在客户端上， 可能存在两个或者以上占用网络带宽的业务同时运行的情 况， 网络侧可以一并获得所有业务的网络带宽要求， 然后进行汇总 （求和， 或者按照某种算法计算得到一个汇总值），再用来和用户可用带宽进行比较； 也可以只将部分业务的带宽要求汇总， 再用来和用户可用带宽进行比较； 当 然， 也可以只将带宽要求最高的单个业务， 用来和用户可用带宽进行比较。 具体比较方式， 本发明实施例不作限定。
由于运营商或者客户端基于某些策略， 可能对某一类业务或者某一个业 务只固定分配一定比例的网络带宽， 或者限制某一个或者一类业务占用带宽 的最大值或者比例， 因此， 用来和当前业务带宽要求进行比较的用户可用带 宽，可以是用户的部分当前可用的总带宽，例如是用户总带宽的一个百分比。 因此， 本发明实施例中， 用来和用户当前使用的业务的带宽要求进行比较的 用户可用带宽， 并不限定于用户的当前总带宽， 而具体可以为当前业务可用 带宽， 用户总带宽的固定比例值， 或者当前业务分配得到的带宽。 步骤 103: 网络侧根据所述比较结果， 通知所述用户带宽状况。
根据前述步骤 102中的比较结果， 网络侧如果判断确认用户可用带宽不 足， 则对用户进行带宽状况通知。 当然， 也可以对用户可用带宽冗余或者其 他情况进行通知， 具体的通知方式包括但不限于： SMS (短信）， MMS (彩 信）， E-mail, ODP ( On Device Portal, 终端门户）客户端实时提醒等， 本实 施例在此不作限定。 本发明实施例的方法， 实现了从网络侧监控用户当前业务的带宽满足情 况并通知用户，从而使网络侧能够及时感知用户实际使用各种业务时候的带 宽使用体验， 并通知用户。 很多时候， 当用户使用某些业务时， 是由于网络 带宽问题造成的体验不佳， 因此， 通过本发明实施例的方法， 可以让用户明 确的了解当前业务体验不佳是由于用户带宽状况（如使用的套餐情况）和当 前业务带宽需求不匹配导致的， 从而可以釆取适当的措施应对和解决。
进一步的， 网络侧在通知用户带宽状况时候， 可以在通知信息中携带带 宽产品推荐信息， 试用信息， 或升级信息， 从而使得用户进一步了解如何解 决目前带宽不足的问题。 结合前述本发明实施例提供的用户带宽通知方法， 本发明实施例进一步 提供了一种 QoE (Quality of Experience, 用户体验质量)检测方法。
QoE是一个和 QoS ( Quality of service,服务质量 )相关的概念。 ITU-T Rec E.800最初定义 QoS为 "决定用户满意程度的服务性能的综合效果"， 包 含多个层面较为广泛的内容。目前业界将 QoS狭义地理解为底层分组数据传 输的性能指标， 如时延、 抖动、 带宽、 误码等， 每个性能指标又定义了单独 的 KPI ( key performance index,主要性能指标）来衡量。但 QoS不等于 QoE, 网络中常见 QoS的 KPI很好， 但用户体验不好的情况， 因为 QoE是从终端 用户的角度来衡量的， 是一个端到端的概念。
移动宽带飞速发展， 但移动运营商对移动宽带用户的真实体验质量
( QoE ) 的感知和提升却存在很大的不足； 在用户上网速度慢， 无法获得很 好的体验时，如何确定用户的 QoE,是运营商在技术上需要解决的一个问题。
参考附图 2 , 为本发明方法实施例一种 QoE检测方法流程图， 所述方法 包括步骤：
步骤 201 :网络侧检测用户可用带宽和用户当前使用的业务的带宽要求； 步骤 202: 网络侧比较所述用户可用带宽和所述用户当前使用的业务的 带宽要求；
上述步骤 201和步骤 202和前述步骤 101和步骤 102类似， 具体细节和 实施方式可以参考前述步骤 101-102中的相关说明。 步骤 203: 网络侧根据所述比较结果， 确定所述用户网络的 QoE值； 比较用户的当前可用带宽和当前使用的业务源的带宽需求后； 当用户的 当前可用带宽小于业务源的带宽需求时， 则认为用户可能 QoE较差， 反之， 则认为用户 QoE满足要求。
进一步的， 由于 QoE是一个和用户实际体验密切关联的指标， 单纯的 检测结果和用户的实际体验可能还是会存在一定的偏差， 因此， 在确定 QoE 情况的时候， 还可以引入用户通知以及用户反馈的步骤， 具体包括：
步骤 204: 网络侧通知用户 QoE情况， 并收集用户对 QoE情况的反馈 信息；
通知用户 QoE情况并收集用户对 QoE情况的反馈，使得对用户 QoE检 测形成闭环， 从而实现对 QoE的精确检测。
具体的， 网络侧可以：
在 QoE较差时， 给用户通知 "网络带宽不足以支持当前业务需求， 请 点击按钮确认是否属实"， 然后， 通过用户点击是或者否的按钮， 收集用户 对 QoE情况的反馈。
当 QoE较好时候， 则可以不需要对用户进行通知和要求用户反馈， 以 避免对用户造成不必要的干扰。
与前述实施例类似， 进一步的， 网络侧在通知用户 QoE状况时， 或者 进一步要求用户确认 QoE状况， 特别是在要求用户确认 QoE较差时， 还可 以在通知信息中包含更高带宽产品推荐， 试用或者升级等信息， 从而使得用 户进一步了解如何解决目前 QoE较差的问题， 提升用户体验。
参考附图 3 , 为本发明实施例提供的一种用户带宽调整方法流程图， 所 述方法包括：
步骤 301：网络侧检测用户可用带宽和用户当前使用的业务的带宽要求； 步骤 302: 网络侧比较所述用户可用带宽和所述用户当前使用的业务的 带宽要求；
上述步骤 301和步骤 302, 和前述步骤 101和步骤 102类似， 具体细节 和实施方式可以参考前述步骤 101-102中的相关说明。
步骤 303: 网络侧根据所述比较结果， 判断当前带宽是否足够； 步骤 304: 若判断带宽不足， 通知所述用户带宽状况， 向用户确认是否 升级带宽； 如果用户需要提升带宽， 可以选择产品订购或者产品试用等处理 方式， 如果用户不需要提升带宽， 则直接进入业务使用步骤 309;
本发明实施例中，通知用户带宽状况的通知信息中包含可以让用户直接 触发带宽升级， 带宽订购或者带宽试用的触发方式； 例如，可以是带宽订购， 即产品升级， 或者试用的超链接； 用户点击所述超链接以后， 直接进入运营 商的带宽订购， 升级， 或者试用页面， 甚至也可以直接进行带宽订购， 升级 或者试用， 不需要通过其它的渠道进行的操作；
网络侧还可以根据用户信息， 选择合适的推荐套餐产品： 例如根据用户 所在地域， 经常访问的业务类型， 用户的年龄， 职业等信息， 给用户推荐合 适的套餐产品。
步骤 305: 用户需要提升带宽， 选择了进行产品试用， 网络侧为用户临 时提升带宽；
步骤 306: 在用户试用期过了以后， 再向用户确认是否订购正式产品， 如果用户确认正式订购， 则进入步骤 307 , 进行带宽调整； 如果不进行正式 订购， 则进入步骤 308, 恢复用户原有带宽；
步骤 307: 对于用户直接订购带宽产品和试用期过后， 用户订购正式产 品的情形， 为用户进行带宽调整， 升级用户带宽；
步骤 308: 对于用户试用期过了以后， 如果不再进行正式订购， 则恢复 用户原有带宽；
步骤 309: 经过一系列判断和处理流程后， 用户继续进行业务使用。 本发明实施例的方案， 对于用户选择产品订购的情况， 可以直接通过网 络侧的 PCRF, PCEF以及计费系统， 完成对用户带宽的调整， 该调整可以是 实时的， 也可以根据一定的策略进行延时调整。
当用户选择产品试用时， 可以对用户当前带宽进行临时提升， 给予用户 对提升后的带宽一定的试用期限， 试用期过了以后， 通知用户是否需要订购 正式的升级产品（带宽）， 然后在根据用户的选择进行下一步的处理， 例如， 当用户选择订购正式产品时，则执行带宽调整，当用户选择不订购试用产品， 则恢复用户之前的带宽。 另外， 网络侧若判断带宽足够支持当前业务， 则不需要对用户进行带宽 调整通知。
通过本发明实施例的方法，使网络侧能够及时感知用户实际使用各种业 务时候的带宽使用体验， 并给予用户提示， 可以让用户了解当前网络带宽状 况，明确的了解当前网络带宽产品情况和使用的业务的对比关系；进一步的， 本发明实施例，通过在通知消息中携带产品推荐信息和 /或触发用户直接升级 或者试用产品的触发方式，使得用户能够更加方便地对宽带产品进行试用或 者升级， 提升用户体验。
下面结合具体的系统架构图 4和信令流程图 5 , 通过具体的实施例， 详 细描述一个包含用户带宽通知， QoE检测，带宽调整提醒，带宽产品升级（含 订购）或者试用的实现过程， 本领域技术人员可以理解， 上述列举的各项功 能， 可以单独实现， 也可以部分或者全部一并实现。
如图 4所示， 为本发明实施例提供的一种实现带宽调整的系统架构图， 所述系统包括业务网关 401 (具备 PCEF功能）、 融合计费系统 402、 策 略生成 PCRF网元 403、 ODP服务器 404以及具备 ODP功能的终端 405 , 结 合后面述及的信令流程图 5 , 该系统可以提供诸如带宽通知， QoE检测， 带 宽调整提醒， 带宽产品升级， 订购或者试用， 灵活计费等能力。 其中， 通过 ODP终端和 ODP服务器， 本实施例的系统可以支持页面弹出的实时通知方 式、 SMS/MMS等通知方式。 下面详述各个网元的基本功能：
业务网关 401 (具备 PCEF功能）： 本发明实施例提供的业务网关， 可以 基于传统数据业务网关的功能进行改造， 新增 "带宽检测"、 "策略执行" 能 力；
策略生成 ( PCRF )服务器 403: 具备 PCRF功能的服务器是 PCC架构 下标准网元；
融合计费系统 402: 可以基于传统计费系统实现， 提供灵活计费、 账务 管理、 产品管理、 通知触发等功能；
ODP服务器 404以及 ODP客户端 405: 本发明实施例新增网元， 为终 端用户提供自服务、 通知等功能。
参考图 5 , 为本发明实施例提供的， 利用图 4中的系统， 实现用户带宽 调整的信令流程图。
步骤 501 : 用户发起业务访问请求；
用户通过客户端上的 web浏览器或者某种软件客户端，发起业务访问请 求。
步骤 502-503: 具备 PCEF功能的业务网关发起业务带宽需求检测； 即发起判断在什么样的网络带宽情况下， 用户使用当前业务才能有一个 比较好的体验。 PCEF可釆用业务带宽需求动态检测法对当前业务带宽需求 进行检测；
业务带宽需求动态检测， 是指用户访问多媒体业务时， 由于业务请求需 要经过 PCEF中转， PCEF实体可以根据业务源交互信令中的媒体描述信息 (如果信令中携带有的话） 来判断业务的带宽要求； 如 SDP ( Session Description Protocol, 会话描述协议） 中描述为 b=AS:2000, 表示该业务会 话要求带宽为 2M的比特率， 从而检测得到当前业务带宽需求。
在步骤 503中， PCEF上报用户的业务访问请求到计费系统， 上报消息 中可以携带当前访问的业务 ID ,后续计费系统将根据该 ID进行鉴权和计费； 同时， 上报消息中可选携带业务源的需求带宽， 需求带宽值可通过公共 AVP ( Attribute Value Pair, 属性值对）， 如 Service-Information字段携带， 也可 通过 Vendor AVP进行携带；
由于用户可能同时运行了两个或者以上需要占用网络带宽的业务， 因此 业务网关可以一并获得多个正在运行的占用网络带宽的业务的带宽要求。
步骤 504-505: 业务权限判断； 本步骤可选。 计费系统可以先对用户的 业务访问进行鉴权， 判断用户是否有权限使用业务， 如果没有权限， 则直接 拒绝用户的本次业务访问请求， 业务访问终止， 如果有权限访问， 则业务正 常交互访问。
步骤 506: 带宽不足判断； 带宽不足判断就是比较用户的当前可用带宽 和当前使用的业务源的带宽需求； 当用户的当前可用带宽小于业务源的带宽 需求时， 则可以认为用户可能 QoE较差； 对于带宽不足的具体判断方式， 可以参考前述实施例步骤 102中的方法和说明， 本实施例在此不赘述。
对用户的当前可用带宽， 融合计费系统可以釆用静态获取法， 即查询用 户订购的套餐， 判断用户当前生效的最大带宽， 例如， 用户订购的月套餐为
30元， 200M, 1M带宽， 则认为用户的当前最大可能带宽为 1M; 当然也可 以动态实时的检测用户当前带宽，具体可以包括：通过部署在用户端的软件， 在需要检测用户当前带宽时， 向该用户端软件发送检测命令， 要求用户客户 端软件上报用户当前带宽情况信息； 或者客户端软件定时进行带宽情况报 告； 条件满足时 （如带宽降低到一定阔值）触发客户端软件上报等；
对于业务源的带宽需求， 融合计费系统可以优先使用前述步骤 503 中 PCEF上报的数据， 如果 PCEF由于无法获取该数据或其他原因没有上报数 据， 则融合计费系统可以从本地获取该数据；
融合计费系统从本地获取业务源的带宽需求的方法可以是根据 PCEF上 报的业务 ID,读取系统中配置的对应业务的带宽要求的静态数据； 例如根据 业务 ID, PCEF上报的用户访问的业务类型为优酷视频业务， 则计费系统读 取本地优酷视频业务的配置信息， 获取该业务的带宽需求。
如果 PCEF未上 业务源的带宽需求， 而且计费系统本地没有配置当前 业务的带宽需求 （例如用户访问比较冷门的视频网站的时候）， 则当前方案 无法判断当前用户的 QoE, 在这种情况下， 系统可以默认用户的 QoE满足 用户需求， 即用户当前带宽足够满足业务需要， 不发送提醒给用户。
步骤 507: 触发实时通知； 如果计费系统判断用户当前带宽情况较差， 则可以发送带宽不足通知到 ODP server。通知消息中可以包含通知类型（如： "QoE不足" 消息）， 目标用户 （如： 当前使用业务的用户）， 满足业务源带 宽要求的建议产品信息， 即推荐更高带宽产品， 如产品列表 ID。
步骤 508: 提醒方式判断； ODP Server可以根据用户状态选择合适的提 醒方式， 提醒方式包括但不限于 SMS、 MMS、 email, ODP客户端实时提醒 等。
步骤 509: 提醒消息推送： ODP Server根据计费系统发送过来的带宽不 足通知内容， 组织给用户终端发送提醒消息， 提醒用户可用带宽不足， 所述 提醒消息可以包含带宽产品推荐信息， 产品升级消息或者产品试用消息等， 发送给用户；
ODP server发送给用户的 "带宽产品推荐"消息中可以包括消息类型（带 宽产品推荐）， 满足业务源带宽要求的推荐订购的产品列表以及各产品的描 述。 各产品描述可根据从计费系统接收到的产品 ID从本地保存的产品描述 信息库中提取。
还可以进一步对提醒消息进行延迟发送， 延迟发送的目的， 是为了让用 户可实际感受一段时间的当前业务体验是否可接受，对于延迟提醒带宽不足 的时间间隔， 可以在 ODP server上进行配置。
如果提醒方式为 ODP客户端实时提醒， 用户手机客户端上将实时弹出 提醒对话框， 提醒用户。 用户在终端 （ODP Client )上点击查看实时提醒， 提醒内容可以包括： 推荐的产品， 试用的套餐以及详细描述、 试用的有效期 (周期、 累计流量、 访问次数等参数组合控制）、 试用期间的资费 （由运营 商设定， 可以设置为免费）。
步骤 510: 用户自助选择； 由于 ODP Server发送的消息中携带有产品推 荐信息， 试用的信息以及相应的触发方式， 因此用户可以直接对推荐或者试 用的产品进行选择； 用户如果同意先试用，可以直接在 ODP消息上点击 "试 用" 带宽产品。
步骤 511-512: 终端（ ODP Client )发起产品试用请求； ODP Server将请 求前传至融合计费系统。
当然， 终端也可以直接发起产品订购或者升级请求， 在这种情况下， 后 续步骤中， 其他网元就不需要执行试用期的限制， 而是可以直接变更用户带 宽。
步骤 513: 计费系统进行产品订购处理； 计费系统进行试用产品订购操 作， 记录用户与该试用产品的订购关系。
步骤 514-516: 产品试用成功， 调整用户 QoS, 计费系统通知 PCRF用 户定购关系变化，更新 QoS策略并下发； PCRF根据用户新的产品定购关系， 结合业务使用情况等信息生成新的 QoS策略。
本实时例中，用户如果试用高带宽套餐包，则 PCRF生成带宽提升策略， 同时下发需要监控的几个参数： 包括累计访问时长、 累计流量、 累计访问次 数等；
步骤 517: PCRF下发新的 QoS策略至业务网关 PCEF; PCEF进行本地 策略更新， 提升该用户带宽；
步骤 518-519: 试用定购结果展示过程： 计费系统返回定购结果给 ODP Server; ODP Server推送试用结果给终端 （ODP Client ), ODP Client将结果 向用户展现； 用户继续业务访问。 业务访问过程中， 业务网关 PCEF与融合 计费系统交互， 完成业务计费流程（本实施例中是免费）， 同时上报该用户 每次的访问时长、 访问流量、 访问次数等， 计费系统进行累计统计。
步骤 520-522: 试用产品失效后， 实时调整 QoS: 由于计费系统记录了 该用户套餐产品的使用情况（累计访问时长、 累计流量、 累计访问次数等)， 当用户定购的高带宽试用产品失效时（产品有效期、 时长、 流量、 访问次数 等参数组合控制）， 计费系统更新用户定购关系； 计费系统触发 QoS策略刷 新， 实时恢复用户带宽 （网元交互过程与产品试用流程一致）； 向用户推送 试用到期提醒， 提醒内容包含正式产品推荐（网元交互过程与试用成功通知 类似 )。
通过本发明实施例的方法， 可以实现带宽通知， QoE检测， 带宽调整提 醒， 带宽产品升级， 订购或者试用， 灵活计费等功能， 提升了用户的带宽感 知度， 使得用户调整带宽的方式更加方便灵活， 提升了用户体验。
需要说明的是， 对于前述的各方法实施例， 为了简单描述， 故将其都表 述为一系列的动作组合， 但是本领域技术人员应该知悉， 本发明可能并不受 所描述的动作顺序的限制， 因为依据本发明， 某些步骤可以釆用其他顺序或 者同时进行。 其次， 本领域技术人员也应该知悉， 说明书中所描述的实施例 均属于优选实施例， 所涉及的动作和模块并不一定是本发明所必须的。
图 6所示为本发明实施例提供的一种网关 600示意图， 用于执行前述各 个实施例中相应的方法步骤， 所述网关包括带宽检测单元 601 和策略执行 单元 602:
带宽检测单元 601 , 用于根据业务访问请求， 检测用户业务带宽要求， 将所述业务带宽要求上报到带宽判断网元；
所述带宽检测单元 601 , 可以根据业务源交互信令中的媒体描述信息来 判断业务的带宽要求；
所述带宽判断网元具体可以是计费系统； 也可以是其他网元； 策略执行单元 602, 用于当所述带宽判断网元根据获得的用户可用带宽 以及所述带宽检测单元 601上报的业务带宽要求， 判断带宽不足时， 提升用 户带宽。
图 7所示为本发明实施例提供的一种计费装置 700示意图， 用于执行前 述各个实施例中的相应的方法步骤， 所述计费装置包括：
业务带宽要求获取单元 701 , 用于接收网关发送的业务带宽要求； 用户可用带宽获取单元 702 , 用于获取用户可用带宽；
具体的， 用户可用带宽获取单元 702可以通过查询用户订购的套餐， 获 取用户当前生效的最大带宽； 或者用户可用带宽获取单元 702可以向用户端 软件发送检测命令， 要求用户客户端软件上报用户当前带宽情况信息； 或者 客户端软件定时进行带宽情况报告； 条件满足时 （如带宽降低到一定阔值） 触发客户端软件上报等， 用户可用带宽获取单元 702获取客户端软件上报的 用户可用带宽信息。
判断单元 703 , 用于比较所述用户可用带宽和所述用户当前使用的业务 的带宽要求， 判断用户可用带宽是否足够； 判断单元 703判断用户可用带宽 是否足够的方式， 和前述步骤 102中的方法类似， 具体细节和实施方式可以 参考前述步骤 102中的相关说明。
通知单元 704 , 用于根据所述判断单元的判断结果， 通知用户可用带宽 状况。
通知单元 704可以在通知用户可用带宽状况的通知信息中进一步携带需 要用户确认 QoE的信息， 使用户根据所述信息， 确认并反馈 QoE情况； 通知单元 704还可以在所述通知信息中包含带宽产品推荐信息，产品试 用或者升级信息， 并可以进一步在通知信息中包含可以让用户直接触发带宽 升级， 带宽订购或者带宽试用的触发方式。
图 8所示为本发明实施例提供的一种用户客户端 800示意图， 用于执行 前述各个实施例中方法的相应步骤， 所述客户端 800 可以是移动终端， PC 终端等各种形式， 所述用户客户端 800包括：
通知信息接收单元 801 , 用于接收网络侧比较用户可用带宽和用户当前 使用的业务的带宽要求后， 下发的带宽状况通知信息； 所述带宽状况通知信 息包含能够让用户触发带宽升级， 带宽订购或者带宽试用的触发方式， 所述 带宽状况通知信息中包含带宽产品推荐信息， 产品试用或者升级信息；
带宽调整触发单元 802, 用于根据所述带宽状况通知信息中携带的带宽 调整触发方式， 向网络侧发送带宽调整请求， 通过所述带宽调整请求， 触发 网络侧对所述用户的带宽产品进行调整， 所述调整包括带宽升级， 订购或者 试用带宽产品。
通过本发明实施例的网关， 计费系统， 用户客户端， 使网络侧能够及时 感知用户实际使用各种业务时候的带宽使用体验， 并给予用户提示， 可以让 用户了解当前网络带宽状况， 明确的了解当前网络带宽产品情况和正在使用 的业务的对比关系； 进一步的， 通过在发给用户的带宽状况通知信息中携带 带宽产品推荐信息和 /或触发用户直接升级或者试用产品的触发方式，使得用 户能够更加方便的对宽带产品进行试用或者升级， 提升用户体验
上述装置和系统内的各模块之间的信息交互、 执行过程等内容， 由于与 本发明方法实施例基于同一构思， 具体内容可参见本发明方法实施例中的叙 述， 此处不再赘述。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流 程， 是可以通过计算机程序来指令相关的硬件来完成， 上述的程序可存储于 一计算机可读取存储介质中， 该程序在执行时， 可包括如上述各方法的实施 例的流程。 其中， 上述的存储介质可为磁碟、光盘、只读存储记忆体（ROM: Read-Only Memory )或随机存 4诸己'! "乙体 （RAM: Random Access Memory ) 等。 、 、： 八 ） 1 、 - 、 、 门术 、 、 施例的说明只是用于帮助理解本发明的方法及其思想； 同时， 对于本领域的 一般技术人员， 依据本发明的思想， 在具体实施方式及应用范围上均会有改 变之处， 综上所述， 本说明书内容不应理解为对本发明的限制。

Claims

权 利 要 求
1、 一种用户带宽通知方法， 其特征在于， 所述方法包括：
网络侧检测用户可用带宽和所述用户当前使用的业务的带宽要求， 网络侧比较所述用户可用带宽和所述用户当前使用的业务的带宽要求， 网络侧根据所述比较结果， 通知所述用户带宽状况。
2、 如权利要求 1 中所述的方法， 其特征在于， 所述网络侧检测用户可 用带宽， 具体包括：
计费系统查询所述用户订购的套餐， 根据所述用户订购的套餐， 获取用 户可用带宽。
3、 如权利要求 1或 2中所述的方法， 其特征在于， 所述网络侧检测用 户当前使用业务的带宽要求， 具体包括：
业务网关根据业务交互信令中的媒体描述信息，检测得到用户当前使用 业务的带宽要求。
4、 如权利要求 1或 2中所述的方法， 其特征在于， 所述网络侧检测用 户当前使用业务的带宽要求， 具体包括：
计费系统检查所述用户当前使用业务的注册信息，得到所述用户当前使 用业务的带宽要求。
5、 如权利要求 1-4 中所述的方法， 其特征在于， 所述根据比较结果， 通知所述用户可用带宽状况， 具体包括： 如果所述比较结果为所述用户可用 带宽小于所述用户当前使用的业务的带宽要求， 通知所述用户可用带宽不 足。
6、 如权利要求 1-5 中所述的方法， 其特征在于， 在通知所述用户带宽 状况时， 在通知信息中进一步包括用户带宽产品推荐信息， 试用信息， 或升 级信息中的至少一种。
7、 如权利要求 6 中所述的方法， 其特征在于， 网络侧根据用户属性， 选择相应的带宽产品， 包括在所述通知信息中。
8、 如权利要求 6或 7中所述的方法， 其特征在于， 所述通知信息中包 含能够让用户直接触发进行带宽升级， 带宽订购或者带宽试用的触发方式。
9、 如权利要求 1-8 中所述的方法， 其特征在于， 所述用户可用带宽具 体为当前业务可用带宽， 用户总带宽的固定比例值， 或者当前业务分配得到 的带宽。
10、 一种用户体验质量 QoE的检测方法， 其特征在于， 所述方法包括： 网络侧检测用户可用带宽和所述用户当前使用的业务的带宽要求， 网络侧比较所述用户可用带宽和所述用户当前使用的业务的带宽要求， 网络侧根据所述比较结果， 确定所述用户的 QoE。
11、 如权利要求 10 中所述的方法， 其特征在于， 所述网络侧确定所述 用户的 QoE后， 通知用户 QoE情况， 并收集所述用户对所述 QoE的反馈信 息， 利用所述反馈信息， 更新用户 QoE。
12、 如权利要求 11 中所述的方法， 其特征在于， 所述网络侧在通知用 户 QoE情况， 并收集用户对所述 QoE的反馈信息时， 在通知信息中进一步 包括用户可用带宽产品推荐信息， 试用信息， 或升级信息中的至少一种。
13、 如权利要求 12 中所述的方法， 其特征在于， 所述通知信息中包含 能够让用户直接触发带宽升级， 带宽订购或者带宽试用的触发方式。
14、 一种网关， 其特征在于， 所述网关包括带宽检测单元和策略执行单 元；
所述带宽检测单元， 用于检测用户业务带宽要求， 将所述业务带宽要求 上报到带宽判断网元；
所述策略执行单元， 用于当所述带宽判断网元根据获得的用户可用带宽 以及所述带宽检测单元上报的业务带宽要求， 判断带宽不足时， 提升用户带 宽。
15、 如权利要求 14 中所述的网关， 其特征在于， 所述带宽检测单元， 具体用于根据业务源交互信令中的媒体描述信息， 检测得到业务带宽要求。
16、 一种计费装置， 其特征在于， 所述计费装置包括业务带宽要求获取 单元， 用户可用带宽获取单元， 判断单元和通知单元；
所述业务带宽要求获取单元， 用于接收网关发送的业务带宽要求； 所述用户可用带宽获取单元， 用于获取用户可用带宽；
所述判断单元， 用于比较所述用户可用带宽和所述业务带宽要求， 判断 用户可用带宽是否足够； 所述通知单元， 用于根据所述判断单元的判断结果， 通知用户可用带宽 状况。
17、 如权利要求 16 中所述的计费装置， 其特征在于， 所述通知单元进 一步用于： 在所述通知用户可用带宽状况的通知消息中包含可以让用户直接 触发带宽升级， 带宽订购或者带宽试用的触发方式。
18、 一种客户端， 其特征在于， 所述客户端包括： 通知信息接收单元和 带宽调整触发单元；
所述通知信息接收单元， 用于接收网络侧比较用户可用带宽和所述用户 当前使用的业务的带宽要求后， 下发的带宽状况通知信息； 所述带宽状况通 知信息包含能够让用户触发带宽升级， 带宽订购或者带宽试用的触发方式； 所述带宽调整触发单元， 用于根据所述带宽状况通知信息中携带的带宽 调整触发方式， 向网络侧发送带宽调整请求， 通过所述带宽调整请求， 触发 网络侧对所述用户的带宽产品进行调整， 所述调整包括带宽升级， 订购或者 试用带宽产品中的至少一种。
PCT/CN2012/087151 2011-12-31 2012-12-21 一种用户带宽通知方法 WO2013097652A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP12862462.4A EP2787695A4 (en) 2011-12-31 2012-12-21 METHOD FOR NOTIFYING SUBSCRIBER BANDWIDTH
RU2014131724/07A RU2582573C2 (ru) 2011-12-31 2012-12-21 Способ уведомления о полосе пропускания пользователя
US14/319,245 US20140317280A1 (en) 2011-12-31 2014-06-30 User Bandwidth Notification Model

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110459641.X 2011-12-31
CN201110459641.XA CN102546297B (zh) 2011-12-31 2011-12-31 一种用户带宽通知方法和计费装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/319,245 Continuation US20140317280A1 (en) 2011-12-31 2014-06-30 User Bandwidth Notification Model

Publications (1)

Publication Number Publication Date
WO2013097652A1 true WO2013097652A1 (zh) 2013-07-04

Family

ID=46352299

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/087151 WO2013097652A1 (zh) 2011-12-31 2012-12-21 一种用户带宽通知方法

Country Status (5)

Country Link
US (1) US20140317280A1 (zh)
EP (1) EP2787695A4 (zh)
CN (1) CN102546297B (zh)
RU (1) RU2582573C2 (zh)
WO (1) WO2013097652A1 (zh)

Families Citing this family (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102546297B (zh) * 2011-12-31 2015-11-25 华为技术有限公司 一种用户带宽通知方法和计费装置
US9065752B2 (en) * 2012-08-23 2015-06-23 International Business Machines Corporation Dynamic service class upgrades in data networks
CN103780446A (zh) * 2012-10-23 2014-05-07 成都市迅电网络技术有限公司 一种实时监控网络带宽资源的方法及系统
US20140207847A1 (en) * 2013-01-22 2014-07-24 Karma Mobility Inc. Portable bandwidth server
CN103117960A (zh) * 2013-01-24 2013-05-22 成都网丁科技有限公司 一种宽带用户自助提速接入带宽的系统及方法
CN103973588B (zh) * 2013-01-29 2017-08-25 华为技术有限公司 数据业务加速方法及装置
CN103269493A (zh) * 2013-05-27 2013-08-28 华为技术有限公司 一种推送带宽业务的方法及设备
US10291503B2 (en) * 2013-09-26 2019-05-14 Taiwan Semiconductor Manufacturing Co., Ltd. File block placement in a distributed network
CN103747429B (zh) * 2014-01-14 2017-06-27 中国联合网络通信集团有限公司 实现业务质量定制的方法及系统
CN104219647B (zh) 2014-05-23 2019-06-21 华为技术有限公司 无线信道控制方法、流量包交易、推荐方法及相关设备
WO2016122448A1 (en) * 2015-01-26 2016-08-04 Hewlett Packard Enterprise Development Lp Resource allocation
CN104967528B (zh) * 2015-05-12 2019-05-17 中国联合网络通信集团有限公司 一种基于sdn控制器的带宽调整方法及系统
CN105898383A (zh) * 2015-11-26 2016-08-24 乐视云计算有限公司 带宽分配方法及系统
US10708795B2 (en) * 2016-06-07 2020-07-07 TUPL, Inc. Artificial intelligence-based network advisor
US10511680B2 (en) 2016-09-13 2019-12-17 Gogo Llc Network profile configuration assistance tool
US10491531B2 (en) 2016-09-13 2019-11-26 Gogo Llc User directed bandwidth optimization
US10523524B2 (en) 2016-09-13 2019-12-31 Gogo Llc Usage-based bandwidth optimization
CN107800886A (zh) * 2017-11-15 2018-03-13 珠海市魅族科技有限公司 终端控制方法、装置、计算机装置及计算机可读存储介质
US10931768B2 (en) 2018-08-28 2021-02-23 Cujo LLC Determining active application usage through a network traffic hub
US10795721B2 (en) * 2018-11-02 2020-10-06 International Business Machines Corporation Transferring tasks from failing devices using IoT
CN109547244A (zh) * 2018-11-16 2019-03-29 郑州云海信息技术有限公司 一种基于NFS系统的QoS客户端读写带宽配置方法及终端
US11109082B2 (en) * 2019-11-14 2021-08-31 Charter Communications Operating, Llc Video quality monitoring in a network environment
CN113438118A (zh) * 2021-08-02 2021-09-24 北京金山云网络技术有限公司 数据传输带宽的调整方法、装置、计算机设备和存储介质
US11893377B2 (en) * 2022-04-27 2024-02-06 Salesforce, Inc. Dependency-aware rules engine for delivering managed package upgrades

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1881890A (zh) * 2005-06-17 2006-12-20 华为技术有限公司 数据业务保护倒换触发方法及装置
CN101330459A (zh) * 2008-07-31 2008-12-24 电子科技大学 一种基于Hose软管VPN的用户宽带控制方法
CN101621351A (zh) * 2008-06-30 2010-01-06 华为技术有限公司 一种调节多媒体编码速率的方法、装置及系统
US20110116374A1 (en) * 2009-11-13 2011-05-19 At&T Intellectual Property I, Lp. System and Method to Provide Bundled Services Through a Communication Device
CN102546297A (zh) * 2011-12-31 2012-07-04 华为技术有限公司 一种用户带宽通知方法

Family Cites Families (30)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2000183915A (ja) * 1998-12-18 2000-06-30 Fujitsu Ltd パス設定制御方法及び交換システム
US20020075844A1 (en) * 2000-12-15 2002-06-20 Hagen W. Alexander Integrating public and private network resources for optimized broadband wireless access and method
JP3591498B2 (ja) * 2001-08-31 2004-11-17 三菱電機株式会社 帯域更新方法
US7644167B2 (en) * 2004-01-30 2010-01-05 Hewlett-Packard Development Company, L.P. Identifying a service node in a network
KR20060064926A (ko) * 2004-12-09 2006-06-14 삼성전자주식회사 다중 모드 및 다중 대역 시스템에서의 모드 전환 및 대역전환 방법
EP1897276B1 (en) * 2005-06-28 2018-06-20 Telecom Italia S.p.A. Indication of service availability for a user terminal
US9432710B2 (en) * 2005-07-08 2016-08-30 At&T Intellectual Property I, L.P. Methods systems, and products for conserving bandwidth
US20070106782A1 (en) * 2005-11-10 2007-05-10 Scientific-Atlanta, Inc. Bandwidth management in each network device in a switched digital video environment
KR100766067B1 (ko) * 2005-11-29 2007-10-11 한국전자통신연구원 인터넷 서비스망에서의 게스트 액세스 허용을 통한 사용자이동성 지원 방법 및 장치와 이를 기반으로 하는 과금 방법
US7974292B1 (en) * 2005-12-31 2011-07-05 At&T Intellectual Property Ii, L.P. Method and apparatus for dynamically adjusting broadband access bandwidth
CN101166182B (zh) * 2006-10-18 2012-01-18 中国电信股份有限公司 基于面板操作的宽带接入带宽调节方法及系统
CN101018199A (zh) * 2007-01-12 2007-08-15 华为技术有限公司 移动流媒体码流的无线带宽分配方法、装置和网关设备
EP1950893A1 (en) * 2007-01-24 2008-07-30 Siemens Aktiengesellschaft Method and system for allocating bandwidth
WO2009052762A1 (fr) * 2007-10-19 2009-04-30 Huawei Technologies Co., Ltd. Procédé, dispositif et système d'amélioration de service de diffusion (bc)
US7844724B2 (en) * 2007-10-24 2010-11-30 Social Communications Company Automated real-time data stream switching in a shared virtual area communication environment
US20090116379A1 (en) * 2007-11-02 2009-05-07 At&T Knowledge Ventures, Lp Insufficient bandwidth notification for transmission of multimedia program
US20100027560A1 (en) * 2008-07-29 2010-02-04 At&T Intellectual Property I, L.P. System and method for service mitigation in a communication system
JP5554238B2 (ja) * 2008-09-26 2014-07-23 京セラ株式会社 アクセスポイント、無線通信端末、およびサーバ
KR101193160B1 (ko) * 2008-11-27 2012-10-19 한국전자통신연구원 상위등급 서비스의 요청 수락률 보장을 위한 네트워크 자원제어 방법 및 이를 위한 장치
RU2009144127A (ru) * 2008-12-01 2011-06-10 РАЗУМ, Инк. (US) Управление качеством обслуживания на основе контроля состояния потока без сигнализации пользователя
US9197678B2 (en) * 2008-12-11 2015-11-24 Skype Method and system for data transmission
US8837287B2 (en) * 2009-04-14 2014-09-16 Alcatel Lucent Application-specific management of high-bandwidth transfers
GB2469509B8 (en) * 2009-04-16 2012-05-30 Aircom Internat Ltd Modelling apparatus and method
EP2398293A1 (en) * 2010-06-17 2011-12-21 Alcatel Lucent Method for managing a wireless telecommunication network
KR101837085B1 (ko) * 2010-08-20 2018-03-09 삼성전자주식회사 Ａｖ 인터페이스에 기초해 성립된 네트워크에서 경로 대역폭을 확보하여 데이터를 송수신하는 방법 및 장치
EP2429190A1 (en) * 2010-09-13 2012-03-14 NTT DoCoMo, Inc. Method and apparatus for transferring a video stream
US9137620B1 (en) * 2010-12-27 2015-09-15 Sprint Communications Company L.P. Conformity analysis system for analyzing conformity to restrictions on the use of a wireless communication device
US9467507B2 (en) * 2011-01-03 2016-10-11 Verizon Patent And Licensing Inc. Wireless network cloud computing resource management
US9130848B2 (en) * 2011-03-30 2015-09-08 Alcatel Lucent Method and apparatus for enhancing QoS during home network remote access
US8614945B2 (en) * 2011-12-15 2013-12-24 The Boeing Company Dynamic service level allocation system and method

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1881890A (zh) * 2005-06-17 2006-12-20 华为技术有限公司 数据业务保护倒换触发方法及装置
CN101621351A (zh) * 2008-06-30 2010-01-06 华为技术有限公司 一种调节多媒体编码速率的方法、装置及系统
CN101330459A (zh) * 2008-07-31 2008-12-24 电子科技大学 一种基于Hose软管VPN的用户宽带控制方法
US20110116374A1 (en) * 2009-11-13 2011-05-19 At&T Intellectual Property I, Lp. System and Method to Provide Bundled Services Through a Communication Device
CN102546297A (zh) * 2011-12-31 2012-07-04 华为技术有限公司 一种用户带宽通知方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2787695A4 *

Also Published As

Publication number Publication date
EP2787695A1 (en) 2014-10-08
CN102546297A (zh) 2012-07-04
CN102546297B (zh) 2015-11-25
EP2787695A4 (en) 2014-11-12
RU2014131724A (ru) 2016-02-20
US20140317280A1 (en) 2014-10-23
RU2582573C2 (ru) 2016-04-27

Similar Documents

Publication Publication Date Title
WO2013097652A1 (zh) 一种用户带宽通知方法
US11202240B2 (en) Systems and methods for managing and monitoring communication sessions
KR101911215B1 (ko) 네트워크 용량을 보호하기 위한 디바이스-보조 서비스들
JP5855268B2 (ja) ポリシー制御装置を使用するネットワーク統計の生成
US9544195B1 (en) Bandwidth monitoring for data plans
US9722889B2 (en) Facilitating high quality network delivery of content over a network
JP6054421B2 (ja) 携帯電話ネットワークにおけるパケットベースのサービスに対する認可要求のハンドリング
EP2627032B1 (en) Method, policy server and gateway for determining policies
EP3108641B1 (en) Assessing qoe of a service in a communication network
JP2013534081A5 (zh)
JP5830185B2 (ja) ネットワークリソースを管理するための方法及びノード並びに対応するシステム及びコンピュータプログラム
WO2012088919A1 (zh) 业务用量监控方法及设备
US20160050124A1 (en) Quality of experience in communication networks
WO2013091410A1 (zh) 网络接入方法、系统及设备
WO2014005455A1 (zh) 一种数据业务的策略控制方法、装置及系统
WO2019042351A1 (zh) 会话流量用量监测控制方法、服务器及存储介质
CN113475039B (zh) 基于开放信息的网络和/或管理功能适配的装置和方法
US10320621B1 (en) Network loading management system and method
EP2627034A1 (en) System and method for policy and/or charging control in a mobile communication network
US20150103754A1 (en) Base station conditions resource adaptation
US11843673B2 (en) Systems and methods for modifying connectivity and cloud services
WO2023066398A1 (zh) 一种会话信息的订阅方法、装置及设备
CN117320119A (zh) 一种切片选择方法及装置
CN116033593A (zh) 一种会话信息的订阅方法、装置及设备
CN109714798A (zh) 后向QoS保障方法、加速平台以及通信系统

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: 12862462

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2012862462

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2012862462

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2014131724

Country of ref document: RU

Kind code of ref document: A