WO2017173897A1 - 一种基于应用的策略和计费控制方法、装置及系统 - Google Patents

一种基于应用的策略和计费控制方法、装置及系统 Download PDF

Info

Publication number
WO2017173897A1
WO2017173897A1 PCT/CN2017/074786 CN2017074786W WO2017173897A1 WO 2017173897 A1 WO2017173897 A1 WO 2017173897A1 CN 2017074786 W CN2017074786 W CN 2017074786W WO 2017173897 A1 WO2017173897 A1 WO 2017173897A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
identifier
qos
correspondence
network side
Prior art date
Application number
PCT/CN2017/074786
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
Priority claimed from CN201610319489.8A external-priority patent/CN107294737A/zh
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2017173897A1 publication Critical patent/WO2017173897A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup

Definitions

  • the present application relates to, but is not limited to, the field of communication technologies, and in particular, to an application-based policy and charging control method, apparatus, and system.
  • next-generation wireless access network a plurality of wireless networks are supported to access a unified core network, and it is desirable that the radio access network (RAN) and the core network (CN, Core Network) minimize the coupling relationship, that is, regardless of The RAN access of the access technology from the terminal can be accessed to the unified CN.
  • RAN radio access network
  • CN core network
  • the core network function of the next generation network may be different from the existing technology.
  • the core network architecture of the prior art includes a Home Subscriber Server (HSS) and a Mobility Management Entity (MME). ), Serving GPRS Support Node (SGSN), Policy and Charging Rule Function (PCRF) entity, Serving Gateway (S-GW), Packet Data Gateway (P-GW, PDN Gateway) and Packet Data Network (PDN).
  • HSS Home Subscriber Server
  • MME Mobility Management Entity
  • SGSN Serving GPRS Support Node
  • PCRF Policy and Charging Rule Function
  • S-GW Serving Gateway
  • P-GW Packet Data Gateway
  • PDN Gateway Packet Data Network
  • the HSS is a permanent storage location of the user subscription data, and is located in the home network that the user subscribes to
  • the MME is the location where the user subscription data is stored in the current network, and is responsible for the non-access layer signaling management of the terminal to the network, and the security verification function of the terminal.
  • SGSN is service support for GERAN (GSM/EDGE radio access network) and UTRAN (UMTS radio access network) users accessing core network Point, functionally similar to the MME, responsible for user location update, paging management, and bearer management
  • S-GW is the gateway from the core network to the wireless system, responsible for the user plane bearer of the terminal to the core network, and the terminal idle mode Data cache, network side initiates service request function, lawful interception and packet data routing and forwarding functions; S-GW is also responsible for counting user terminal use of wireless network, and production The live terminal uses the CDR of the wireless network and transmits it to the charging gateway.
  • the P-GW is a gateway of the evolved system and the external packet data network of the system. It is connected to the Internet and the packet data network, and is responsible for the Internet Protocol (IP) address allocation, charging function, packet filtering, and policy control of the terminal. And other functions.
  • IP Internet Protocol
  • the packet data network is the operator's IP service network, which provides IP services to users through the operator's core network; the PCRF entity is responsible for providing charging control, online credit control, threshold control, and quality of service (QoS, Quality). Of Service) Servers for policy aspects.
  • the policy and charging control architecture defined by the 3GPP is as shown in FIG. 1 and includes: PCRF, Policy and Charging Enforcement Function (PCEF), Application Function Entity (AF), and online charging system.
  • PCRF Policy and Charging Enforcement Function
  • AF Application Function Entity
  • OCS Online Charging System
  • OFCS Off-line Charging System
  • SPR User Profile Attribute
  • BBERF Bearer Binding and Event Report Function
  • TDF Traffic Detection Function
  • Rx is the reference point between AF and PCRF
  • Gx is the reference point between PCEF and PCRF
  • Sp is the reference point between SPR and PCRF
  • Gy is the reference point between OCS and PCEF
  • Gz is PCEF and The reference point between OFCS
  • Sd is the reference point between TDF and PCRF
  • Gxx is the reference point between PCRF and BBERF.
  • the 3GPP network provides QoS guarantee based on bearer granularity. Services that are mapped to the same bearer will be forwarded using the same bearer layer packet. If a different bearer layer packet forwarding process is required, the service flow needs to be mapped to a different Evolved Packet System (EPS) bearer.
  • EPS Evolved Packet System
  • the uplink traffic flow template (UL TFT) is a set of uplink packet filters in the TFT.
  • the downlink traffic flow template (DL TFT) is a downlink packet filter set in the TFT.
  • One host per PDN (Public Data Network) connection is allowed to have no TFT.
  • the EPS IP connection access network IP-CAN, IP-Connectivity Access Network
  • IP-CAN IP-Connectivity Access Network
  • the policy and charging control (PCC, Policy and Charging Control) or QoS rule delivered by the PCRF entity includes a service data flow template (SDF template), and the SDF template usually includes one or more services. Data stream filter.
  • the PCRF entity can provide a PCC rule containing a wild-carded traffic stream filter to allow packets that cannot match any other PCC or QoS rules to pass.
  • the PEF Policy Enforcement Function
  • QCI QoS Class Identifier
  • the ARP Allocation and Retention Priority performs a bearer binding and constructs a TFT according to the SDF template in the rule to be sent to the user equipment (UE, User Equipment).
  • UE User Equipment
  • the same QCI/ARP rules can be bound to the same bearer, not the same QCI/ARP rules are always bound to the same bearer. Therefore, the PCRF cannot determine which bearer the rule is bound to when providing the policy rule, and the PEF finally decides to bind the policy rule to the specific bearer.
  • the PEF For a guaranteed bit rate (GBR) bearer, the PEF sets the GBR to be the sum of the GBRs bound to all the policy rules of the bearer, and sets the maximum bit rate (MBR) of the bearer to be bound to the bearer. The sum of the MBRs of all the policy rules.
  • GBR guaranteed bit rate
  • MBR maximum bit rate
  • the MBR carried by the Non-GBR is set as the sum of the MBRs bound to all the policy rules of this bearer.
  • the core network and the radio side will allocate corresponding resources for the bearers according to QCI, ARP, GBR, and MRB.
  • the existing QoS guarantee mechanism requires the network or terminal to identify a service data packet according to the service filter, thereby applying corresponding QoS to the identified data packet.
  • this method often fails to notify the UE of the QoS parameters of the uplink data, and specifically has the following problems:
  • the core network includes a control plane (CP) functional entity and a user plane (UP) functional entity, and these functional entities may be multiple.
  • the CP functional entity may be more specifically classified into a mobility management entity, a session management entity, an address assignment entity, a QoS policy formulation entity, and the like according to the managed content.
  • the UP functional entity may be one or more functional entities for data forwarding. If there are multiple CP functional entities, there may be a unique interface to the access network (AN, Access Network), or there may be multiple interfaces to the AN.
  • next-generation networks where AN is collectively referred to.
  • the interfaces and protocol types of the CP functional entities of the CN that may be connected are different.
  • the concept of bearer may not exist in some cases, but the problem in the existing network still exists, that is, the QoS parameters of the uplink data cannot be notified to the UE.
  • the embodiments of the present invention provide an application-based policy and charging control method, apparatus, and system, to at least solve the problem that the uplink bearer cannot be effectively notified to the UE in the related art.
  • an embodiment of the present invention provides an application-based policy and a charging control method, including:
  • the UE receives the quality of service (QoS) information authorized by the network side for the application identifier, and the application identifier is an application identifier (Application Id) that is pre-delivered by the network side;
  • QoS quality of service
  • Application Id application identifier
  • the UE processes the uplink data of the application corresponding to the Application Id according to the QoS information;
  • the QoS information includes at least one of the following: a QoS parameter, and wireless logical channel information.
  • the method may further include: the UE sending a QoS information request message to the network side, where the QoS information is sent by the UE to the network side.
  • the request message carries the application identifier and the requested QoS information.
  • the method may further include: the UE assigning an instance identifier to the application, and carrying the instance identifier in the QoS information request message, where the UE sends a QoS information request message to the network side,
  • the instance identification is used to identify different applications with the same Application Id.
  • the method may further include: the UE negotiates with an application layer of the application, and provides the application identifier and the requested QoS information to the MME. And applying, by the application layer, the application identifier and the requested QoS information to the network side.
  • the method may further include: the UE assigning an instance identifier to the application, where the instance identifier is used to identify different applications having the same Application Id;
  • the method may further include: the UE negotiates with the application layer of the application, and provides the application identifier, the instance identifier, and the requested QoS information to the UE.
  • the application layer provides the application identifier, the instance identifier, and the requested QoS information to the network side.
  • the method may further include: the mapping between the locally saved Application Id and the operating system application identifier by the UE, Or determining the application ID of the application, or the correspondence between the application IP address of the application IP address or the IP triplet, or the correspondence between the Application Id and the URL of the application.
  • the method may further include: the UE acquiring, from the network side, a correspondence between the Application Id and an operating system application identifier, or the Application Id and a server IP address or an IP triplet of the application. Correspondence relationship or correspondence between the Application Id and the URL of the application is saved.
  • the UE obtains the correspondence between the Application Id and the operating system application identifier, or the correspondence between the Application Id and the server IP address or the IP triplet, or the Application, from the network side.
  • Corresponding relationship between the Id and the URL of the application may include: the UE requests and receives a correspondence between the Application Id and an operating system application identifier, or the Application Id and a server IP of the application to the network side.
  • the UE may obtain a correspondence between the Application Id and an operating system application identifier, or the Application ID and the application, in a process of establishing a packet data network (PDN) connection or a packet data unit (PDU) session. a correspondence between a server IP address or an IP triplet, or a correspondence between the Application Id and the URL of the application, and associating the correspondence with the PDN connection or the PDU session;
  • PDN packet data network
  • PDU packet data unit
  • the UE may obtain a correspondence between the Application Id and an operating system application identifier, or a correspondence between the Application Id and a server IP address or an IP triplet of the application, after the PDN connection or the PDU session is established. Or a correspondence between the Application ID and the URL of the application, and associate the correspondence with the PDN connection or the PDU session.
  • the UE receives the QoS information that is authorized by the network for the application identifier, and may include at least one of the following: the UE receives the message sent by the network side, where the message carries the Application Id and the network side authorized a QoS parameter, the QoS parameter includes a QoS parameter in an uplink direction; the UE receives a message sent by the network side, where the message carries the Application Id and wireless logical channel information, where the wireless logical channel information includes an uplink direction Wireless logical channel information.
  • the message may also carry an instance identifier of the application, where the instance identifier may be used to identify different applications with the same Application ID.
  • the UE processes the uplink data of the application corresponding to the Application Id according to the QoS information, and may include at least one of the following: the UE performs corresponding scheduling on the uplink data of the application according to the QoS parameter.
  • the algorithm sends the uplink data by using the wireless logical channel corresponding to the wireless logical channel information.
  • the method may further include: determining, by the UE, whether the application ID corresponding to the application already has the QoS information authorized by the network side, if the UE does not exist before sending the QoS information request message to the network side, if the UE does not exist
  • the QoS information the UE sends the QoS letter If the QoS information is present, the UE determines whether there is a guaranteed bit rate (GBR) parameter in the QoS parameter, and if the GBR parameter exists, the UE sends the QoS information request message; If the GBR parameter does not exist, the UE processes the uplink data of the application according to the QoS information corresponding to the Application Id.
  • GBR guaranteed bit rate
  • the embodiment of the present invention further provides an application-based policy and charging control apparatus, including:
  • the first receiving module is configured to receive the QoS information authorized by the network side for the application identifier, where the application identifier is an operator-defined application identifier (Application Id) that is pre-delivered by the network side;
  • Application Id operator-defined application identifier
  • the processing module is configured to process uplink data of the application corresponding to the Application Id according to the QoS information;
  • the QoS information includes at least one of the following: a QoS parameter, and wireless logical channel information.
  • the device may further include: a first sending module, configured to send a QoS information request message to the network side, where the QoS information request message carries the application identifier and the requested QoS information.
  • a first sending module configured to send a QoS information request message to the network side, where the QoS information request message carries the application identifier and the requested QoS information.
  • the device may further include: an allocating module, configured to allocate an instance identifier to the application, where the instance identifier is used to identify different applications having the same Application ID; the first sending module may also be configured to When the QoS information request message is sent to the network side, the instance identifier is also carried in the QoS information request message.
  • an allocating module configured to allocate an instance identifier to the application, where the instance identifier is used to identify different applications having the same Application ID
  • the first sending module may also be configured to When the QoS information request message is sent to the network side, the instance identifier is also carried in the QoS information request message.
  • the device may further include: a first sending module, configured to negotiate with an application layer of the application, and provide the application identifier and the requested QoS information to the application layer, so that the application layer The application identifier and the requested QoS information are provided to the network side.
  • a first sending module configured to negotiate with an application layer of the application, and provide the application identifier and the requested QoS information to the application layer, so that the application layer The application identifier and the requested QoS information are provided to the network side.
  • the device may further include: an allocating module, configured to allocate an instance identifier to the application, where the instance identifier is used to identify different applications having the same Application ID; the first sending module may also be configured to When the application identifier and the requested QoS information are provided to the application layer of the application, an instance identifier of the application is also provided to the application layer.
  • an allocating module configured to allocate an instance identifier to the application, where the instance identifier is used to identify different applications having the same Application ID
  • the first sending module may also be configured to When the application identifier and the requested QoS information are provided to the application layer of the application, an instance identifier of the application is also provided to the application layer.
  • the device may further include: a determining module and a storage module; and a storage module configured to save a correspondence between the Application Id and the operating system application identifier, or a correspondence between the Application Id and the server IP address or the IP triplet of the application. Relationship, or Application Id and the stated The corresponding relationship of the used URLs; the determining module is configured to determine the Application Id of the application according to the correspondence relationship saved by the storage module.
  • the first receiving module may be configured to obtain a correspondence between the Application Id and an operating system application identifier, or a correspondence between an Application Id and a server IP address or an IP triplet, or an Application Id. Corresponding relationship with the URL of the application is saved to the storage module, where the corresponding relationship is actively sent by the network side, or after the first sending module of the device actively requests the network side The network side delivers.
  • the first receiving module may be configured to: obtain a correspondence between the Application Id and an operating system application identifier, or the Application Id and a server IP of the application in a process of establishing a PDN connection or a PDU session. a correspondence between an address or an IP triplet, or a correspondence between the Application Id and a URL of the application, and associating the correspondence with the PDN connection or the PDU session; or, in a PDN connection or PDU After the session is established, the correspondence between the Application ID and the operating system application identifier, or the correspondence between the Application Id and the server IP address or the IP triplet, or the Application ID and the URL of the application are obtained. Correspondence relationship and associate the correspondence with the PDN connection or the PDU session.
  • the first receiving module may be configured to perform at least one of: receiving a message sent by the network side, where the message carries the Application Id and the QoS parameter authorized by the network side, the QoS The parameter includes a QoS parameter in the uplink direction, and receives a message sent by the network side, where the message carries the Application Id and the wireless logical channel information, where the wireless logical channel information includes the wireless logical channel information in the uplink direction.
  • the message may also carry an instance identifier of the application, where the instance identifier may be used to identify different applications with the same Application ID.
  • the device may further include: a determining module, configured to determine whether the QoS information authorized by the network side exists in the Application Id corresponding to the application, and if the QoS information does not exist, notify the first sending module Sending the QoS information request message; if the QoS information exists, determining whether there is a guaranteed bit rate (GBR) parameter in the QoS information, and if the GBR parameter exists, notifying the first sending module to send the a QoS information request message; if the GBR parameter does not exist, notifying the processing module according to the Application Id
  • the QoS parameters process the uplink data of the application.
  • the processing module may be configured to perform at least one of: performing a corresponding scheduling algorithm on the uplink data of the application according to the QoS parameter; and transmitting uplink data by using a wireless logical channel corresponding to the wireless logical channel information.
  • the embodiment of the present invention further provides an application-based policy and charging control apparatus, including: a second receiving module and a second sending module;
  • the second receiving module is configured to receive an application identifier corresponding to the application provided by the UE, where the application identifier is an operator-defined application identifier (Application Id) that is pre-delivered by the network side;
  • Application Id operator-defined application identifier
  • the second sending module is configured to return QoS information to the UE, where the QoS information includes at least one of the following: a QoS parameter authorized by the network side for the application, and wireless logical channel information.
  • the second receiving module may be further configured to receive an instance identifier of the application that is further provided by the UE while providing the application identifier, where the instance identifier is used to identify that the application ID is different. application.
  • the second sending module may be configured to perform at least one of: actively sending a correspondence between the Application Id and the operating system application identifier to the UE, or the Application Id and the server IP address of the application or Corresponding relationship of the IP triplet, or a correspondence between the Application Id and the URL of the application; after the second receiving module receives the request of the UE, sending the Application Id and the operation to the UE Corresponding relationship of the system application identifier, or a correspondence between the Application Id and the server IP address or IP triplet of the application, or a correspondence between the Application ID and the URL of the application.
  • the second sending module may be configured to perform at least one of: returning a message to the UE, where the message carries the Application Id and the QoS parameter authorized by the network side, where the QoS parameter includes a QoS parameter in the uplink direction; a message is returned to the UE, where the message carries the Application Id and wireless logical channel information, and the wireless logical channel information includes wireless logical channel information in an uplink direction.
  • the second receiving module may be configured to receive a QoS information request message sent by the UE to the network side, where the QoS information request message carries the Application Id of the application and the requested QoS parameter; a sending module, configured to return to the UE The message of Application Id and network side authorized QoS parameters, wherein the QoS parameter includes an QoS parameter in an uplink direction.
  • the QoS information request message may further include an instance identifier of the application; the message carrying the QoS parameter of the Application Id and the network side authorization may further include an instance identifier of the application; Identify different applications with the same Application Id.
  • the embodiment of the present invention further provides an application-based policy and charging control system, including: a UE and a network side entity; the UE includes the apparatus of the foregoing second aspect, and the network side entity includes the foregoing third Aspect of the device.
  • an embodiment of the present invention further provides a computer readable storage medium storing computer executable instructions, which are implemented by a processor to implement the above application-based policy and charging control method.
  • the UE acquires the QoS information of the application according to the application identifier, and the QoS information may include at least one of the following: a QoS parameter, a wireless logical channel information, and when the data of the application needs to be sent to the network side, the UE is configured according to the UE.
  • the QoS information is processed. In this way, the network side can timely notify the QoS information of the uplink data of the UE, and solve the problem that the uplink bearer cannot be effectively notified to the UE.
  • FIG. 1 is a schematic diagram of a policy and charging control architecture defined by 3GPP in the related art
  • FIG. 2 is a schematic diagram of the architecture of a next generation network
  • FIG. 3 is a schematic flowchart of an application-based policy and a charging control method according to an embodiment of the present invention
  • FIG. 5 is a flowchart of Embodiment 2 of the present invention.
  • FIG. 6 is a flowchart of initiating resource reservation by a network side according to Embodiment 3 of the present invention.
  • FIG. 7 is a flowchart of initiating resource reservation by a network side according to Embodiment 4 of the present invention.
  • FIG. 8 is a flowchart of a UE initiating resource reservation according to Embodiment 5 of the present invention.
  • FIG. 9 is a flowchart of a UE initiating resource reservation according to Embodiment 6 of the present invention.
  • FIG. 10 is a flowchart of initiating resource reservation by a network side according to Embodiment 7 of the present invention.
  • FIG. 11 is a flowchart of initiating resource reservation by a network side according to Embodiment 8 of the present invention.
  • FIG. 12 is a schematic structural diagram of a component-based policy and charging control apparatus deployed on a UE side according to an embodiment of the present invention
  • FIG. 13 is a schematic structural diagram of a component-based policy and charging control apparatus deployed on a network side according to an embodiment of the present invention
  • FIG. 14 is a schematic structural diagram of an application-based policy and charging control system according to an embodiment of the present invention.
  • an application-based policy and a charging control method may mainly include the following steps:
  • Step 301 The UE receives the QoS information authorized by the network side for the application identifier, where the application identifier is an operator-defined application identifier (Application Id) that is pre-delivered by the network side;
  • the application identifier is an operator-defined application identifier (Application Id) that is pre-delivered by the network side;
  • Step 302 The UE processes the uplink data of the application corresponding to the Application Id according to the QoS information.
  • the QoS information includes at least one of the following: a QoS parameter, and wireless logical channel information.
  • the method may further include: the UE sending a QoS information request message to the network side, where the QoS information request message carries the application identifier and the requested QoS information.
  • the method may further include: the UE assigning an instance identifier to the application, and carrying the instance identifier in the QoS information request message, The instance identification is used to identify different applications with the same Application Id.
  • the method may further include: the UE negotiating with the application layer of the application, providing the application identifier and the requested QoS information to the application layer, and then The application layer provides the application identifier and the requested QoS information to the network side.
  • the method may further include: the UE assigning an instance identifier to the application, where the instance identifier is used to identify different applications having the same Application Id; and before the UE receives the QoS information authorized by the network side for the application identifier, The method may further include: the UE negotiates with an application layer of the application, and provides an application identifier, an instance identifier, and the requested QoS information of the application to the application layer, where the application layer is to the network side. The application identifier, the instance identifier, and the requested QoS information are provided.
  • the method may further include: the UE according to the locally stored correspondence between the Application ID and the operating system application identifier, or the Application Id and the third-party application (the third-party application herein) That is, the application corresponding to the Application Id in the step 302, the correspondence between the IP address of the server or the IP triplet, or the correspondence between the Application Id and the Uniform Resource Locator (URL) of the third-party application. Relationship, determining the Application Id of the application.
  • the method may further include: the UE acquiring, from the network side, a correspondence between the Application Id and an operating system application identifier, or a correspondence between an Application Id and a server IP address or an IP triplet of a third-party application. Or the correspondence between the Application Id and the URL of the third-party application and save it.
  • the UE may request and receive the correspondence between the Application Id and the operating system application identifier, or the correspondence between the Application Id and the server IP address or the IP triplet of the third-party application, or Application Id to the network side.
  • the UE may receive the correspondence between the Application Id and the operating system application identifier actively sent by the network side, or the server ID of the Application Id and the third-party application Address or IP triplet pair Correspondence, or the correspondence between the Application Id and the URL of the third-party application should be saved.
  • the UE may acquire a correspondence between the Application Id and an operating system application identifier, or Application Id, in a packet data network (PDN) connection or a packet data unit (PDU) session establishment process.
  • PDN packet data network
  • PDU packet data unit
  • the UE may obtain the correspondence between the Application Id and the operating system application identifier, or the correspondence between the Application Id and the server IP address or the IP triplet of the third-party application, or Application Id and Corresponding relationship of the URL of the third-party application, and associating the correspondence with the PDN connection or the PDU session.
  • the UE receives the QoS information authorized by the network side for the application identifier, and may include at least one of the following: the UE receives the message sent by the network side, where the message carries the Application Id And the network side authorized QoS parameter, the QoS parameter includes an QoS parameter in an uplink direction; the UE receives a message sent by the network side, where the message carries the Application Id and the network side authorized transmission station
  • the wireless logical channel information of the application data where the wireless logical channel information includes wireless logical channel information in an uplink direction.
  • the message may also carry an instance identifier of the application, where the instance identifier is used to identify different applications with the same Application ID.
  • the method may further include: determining, by the UE, whether the application ID corresponding to the application already has the QoS authorized by the network side. Information, if the QoS information does not exist, the UE sends the QoS information request message; if the QoS information exists, the UE determines whether there is a guaranteed bit rate (GBR) parameter in the QoS information, if If the GBR parameter is present, the UE sends the QoS information request message; if the GBR parameter does not exist, the UE does not send the QoS information request message, and according to the QoS information corresponding to the Application Id
  • GBR guaranteed bit rate
  • FIG. 4 is a network side-side terminal side providing a correspondence between an operator-defined application identifier (Application Id) and an operating system application identifier, or an application ID and a third-party application server IP address or an IP triplet according to an embodiment of the present invention.
  • Application Id operator-defined application identifier
  • FIG. 4 A flow chart of the correspondence relationship, or the correspondence between the URLs of the Application Id and the third-party application, as shown in FIG. 4, the steps are as follows:
  • Step S401 The policy service function entity deployed in the operator network configures the correspondence between the Application Id and the operating system application identifier. After the UE accesses the network and establishes a connection with the policy service function entity, the policy service function entity sends the Application Id and the UE to the UE.
  • the operating system application identifier may include two parts: an operating system identifier (OSId) and an OS specific application identifier (OSAppId).
  • OSId is an identifier of an operating system type, such as an Android operating system and an iOS operating system.
  • the OSAppId is used to identify an application in a particular operating system. If the policy service function entity obtains the operating system identifier of the UE before the corresponding relationship is delivered, the operating system application identifier may only include the OSAppId.
  • Step S402 the UE receives and saves the correspondence between the Application Id and the operating system application identifier delivered by the policy service function entity, or the correspondence between the Application Id and the server IP address or IP triplet of the third-party application, or Application Id. Correspondence with the URL of the third-party application and return a confirmation message.
  • the UE obtains the Application Id corresponding to the application installed in the operating system, such as QQ and WeChat corresponding to Application Id1; WeChat and Taobao correspond to Application Id2.
  • the service function entity needs to update the corresponding relationship to the UE, and the update process can also be implemented by the process of this embodiment.
  • FIG. 5 is the UE of the embodiment requests the Application Id and the operating system application identifier from the network side.
  • the flow chart of the corresponding relationship is as follows:
  • step S501 the UE installs or runs an application, and the UE detects that there is no Application Id corresponding to the application locally, and the UE requests the Application Id from the policy service function entity, where the request message carries one or more operating system application identifiers and third-party applications.
  • Step S502 The policy service function entity returns an acknowledgement message to the UE, where the acknowledgement message carries the Application Id corresponding to the application, and the UE receives and saves the correspondence between the Application Id and the operating system application identifier, the Application Id, and the server IP of the third-party application.
  • Policy service functional entities can be deployed independently or integrated with other functional entities.
  • the policy service function entity may be integrated in the P-GW or the PCRF.
  • the policy service function may be integrated in the CP function entity (CP Function) or the UP function entity ( In UP Function).
  • the UE before the UE establishes a connection with the policy service function entity, the UE needs to access the network and establish a PDN connection or a Packet Data Unit (PDU) session.
  • PDU Packet Data Unit
  • the network side The UE can be provided with the address of the policy service function entity so that the UE can establish a connection with the policy service function entity.
  • the foregoing correspondence may be provided to the UE by using a separate message.
  • the policy service function entity may also establish a PDN connection or a PDU session initiated by the UE.
  • the corresponding correspondence is sent to the UE in the response message.
  • the UE may save multiple correspondences.
  • the policy is provided in the same network as the gateway function entity that provides the UE with access to the PDN network.
  • the service function entity provides the UE with the correspondence between the Application Id of the PDN connection or the PDU session and the operating system application identifier, the correspondence between the Application Id and the server IP address or the IP triplet of the third-party application, or the Application Id and the third party.
  • the correspondence of the applied URLs The UE also associates the correspondence between the Application Id and the operating system application identifier, or the correspondence between the Application Id and the server IP address or the IP triplet of the third-party application, or the correspondence between the Application Id and the URL of the third-party application.
  • the policy service function entity located in the HPLMN provides the Application Id and operating system application for the home roaming PDN connection.
  • the corresponding relationship of the identifier, or the correspondence between the Application Id and the server IP address or the IP triplet of the third-party application, or the correspondence between the Application Id and the URL of the third-party application to the UE, and the policy service function entity located in the VPLMN is local
  • the groomed PDN connection provides a correspondence between the Application Id and an operating system application identifier, or a correspondence between an Application Id and a server IP address or an IP triplet of a third-party application, or a correspondence between an Application Id and a URL of a third-party application.
  • the policy service function entity that provides the same PLMN with the UP function entity that provides access to the PDN network to the UE provides the UE with the correspondence between the Application Id and the operating system application identifier associated with the PDN connection or the PDU session, or Application.
  • FIG. 6 is a flowchart of the network side initiating resource reservation in this embodiment, and the steps are as follows:
  • Step S601 After the UE establishes a PDN connection with the network, the UE interacts with the application layer to negotiate the application to be initiated.
  • the UE provides the Application Id and the instance identifier corresponding to the application, or the application layer provides the Application to the UE. Id and instance ID. If the application saves the corresponding relationship, the Application Id only corresponds to one operating system application identifier, or the Application Id only corresponds to the server IP address or IP triplet of the third-party application, or the Application Id only corresponds to the URL of the third-party application. You may not carry an instance ID.
  • the instance identifier is used to identify different applications with the same Application Id.
  • the instance identifier is dynamically allocated to the UE, ensuring that it is unique under the same Application Id, that is, the Application Id and the instance identifier can uniquely identify an application to be initiated by one UE.
  • Step S602 The application function entity (AF, Application Function) located at the application layer provides the service information of the application to the PCRF, and provides the Application Id, the instance identifier, and the requested QoS information in the service information.
  • AF Application Function
  • Step S603 the PCRF formulates a PCC rule for the application, where the PCC rule includes an Application Id, an instance identifier, a QoS parameter (such as QCI, ARP, etc.), and a charging parameter.
  • the PCC rule includes an Application Id, an instance identifier, a QoS parameter (such as QCI, ARP, etc.), and a charging parameter.
  • the QoS parameter includes a QoS parameter in the uplink direction.
  • the PCRF is the QCI for applying the authorized GBR
  • the guaranteed bandwidth GBR is included in the QoS parameters.
  • Step S604 The PCRF sends a policy and charging rule providing message to the PCEF, and carries the PCC rule.
  • step S605 the PCEF returns a policy and charging rule providing confirmation message to the PCRF.
  • Step S606 the PCEF executes a PCC rule, and initiates a process of resource reservation.
  • the PCEF performs bearer binding, creation, or modification of the bearer process according to the PCC rule.
  • the gateway where the PCEF is located sends a create bearer request message or an update bearer request message.
  • the message carries the Application Id, the instance identifier, and the QoS parameter.
  • the message is sent to the UE through one or more intermediate nodes. After receiving the message, the UE returns to the network. Confirm the message.
  • the network ie, the radio base station
  • the network also sends the Application Id and the corresponding wireless logical channel information to the UE, and the UE acquires the logical channel used to send the Application Id corresponding data. In this way, the UE obtains the QoS information of the network side authorization corresponding to the application through the creation or modification process initiated by the PCEF.
  • the network may provide the QoS information authorized by the network side to the UE in only one of the above manners.
  • the PCEF In order for the PCEF to perform the corresponding QoS policy on the data of the application, the PCEF is required to have an application detection function, that is, the PCEF can detect the application corresponding to the Application Id.
  • the UE negotiates with the application layer, and the Application Id and the requested QoS information are provided by the AF to the PCRF.
  • the application detection functions (such as PCEF and TDF) deployed in the network may also be used.
  • the data being transmitted by the UE and the application layer is detected, and the Application Id and the instance identifier (optional) are reported to the PCRF.
  • the PCRF performs step S603. QoS authorization.
  • the UE determines, according to the Application Id and the instance identifier (optional), the QoS information of the network authorization to be initiated, in particular, the QoS information in the uplink direction.
  • the UE performs processing according to the QoS information sent by the network side (for example, sending the uplink data to the network by using the created or updated bearer or the wireless logical channel corresponding to the application Id by the UE). Send uplink data or perform corresponding scheduling algorithm according to QoS parameters).
  • the UE can also check whether the downlink data sent by the network is on the correct bearer.
  • FIG. 7 is a flowchart of the network side initiating resource reservation in this embodiment.
  • the process of initiating resource reservation on the network side in this embodiment is as follows:
  • Step S701 After the UE establishes a PDN connection with the network, the UE interacts with the application layer to negotiate the application to be initiated. In the negotiation process, the UE provides the Application Id and the instance identifier corresponding to the application. If the application saves the corresponding relationship, the Application Id only corresponds to one operating system application identifier, or the Application Id only corresponds to the server IP address or IP triplet of the third-party application, or the Application Id only corresponds to the URL of a third-party application, then It is also possible not to carry the instance ID.
  • the instance identifier is used to identify different applications with the same Application Id.
  • the instance identifier is dynamically allocated to the UE, ensuring that it is unique under the same Application Id, that is, the Application Id and the instance identifier can uniquely identify an application to be initiated by one UE.
  • Step S702 The AF located at the application layer provides the service information of the application to the PCRF, and provides the Application Id, the instance identifier, and the requested QoS information in the service information.
  • Step S703 the PCRF formulates a PCC rule for the application, where the PCC rule includes Application Id, QoS parameters (such as QCI, ARP), and charging parameters.
  • the PCRF further formulates QoS rules according to the PCC rules, and the QoS rules include Application Id, instance identifiers, and QoS parameters.
  • the QoS parameter includes a QoS parameter in the uplink direction.
  • Step S704 the PCRF sends a policy and charging rule providing message to the PCEF, and carries the PCC rule.
  • Step S705 the PCEF returns a policy and charging rule providing confirmation message to the PCRF.
  • Step S706 the PCRF sends a QoS rule providing message to the BBERF, and carries the QoS rule.
  • Step S707 the BBERF returns a QoS rule providing confirmation message to the PCRF.
  • Step S708 the BBERF executes a QoS rule, and initiates a process of resource reservation.
  • the BBERF performs bearer binding, creation, or modification of the bearer process according to the QoS rule.
  • the gateway or the base station where the BBERF is located sends a create bearer request message or an update bearer request message, where the message carries the Application Id, the instance identifier, and the QoS parameter, and the message is sent to the UE through one or more intermediate nodes, and after receiving the message, the UE sends the message to the UE.
  • the network returns a confirmation message.
  • the network ie, the radio base station
  • the network also sends the Application Id and the corresponding wireless logical channel information to the UE, and the UE acquires the logical channel used to send the Application Id corresponding data.
  • the UE obtains the QoS information of the network side authorization corresponding to the application through the creation or modification process initiated by the BBERF.
  • the network may provide the QoS information authorized by the network side to the UE in only one of the above manners.
  • the PCEF In order for the PCEF to perform the corresponding QoS policy on the data of the application, the PCEF is required to have an application detection function, that is, the PCEF can detect the application corresponding to the Application Id. If the BBERF is to implement the QoS rules, the BBERF also needs to have the ability to perform the identification application. For example, if the BBERF has the function of application detection or the PCEF performs the application detection, the identifier associated with the Application Id is marked on the application data packet.
  • the UE negotiates with the application layer, and the Application Id and the requested QoS information are provided by the AF to the PCRF.
  • the application detection functions (such as PCEF and TDF) deployed in the network may also be used.
  • the data being transmitted by the UE and the application layer is detected, and the Application Id and the instance identifier (optional) are reported to the PCRF.
  • the PCRF performs step S703 to perform QoS authorization.
  • the UE determines, according to the Application Id and the instance identifier (optional), the QoS information of the network authorization to be initiated, in particular, the QoS information in the uplink direction.
  • the UE performs processing according to the QoS information sent by the network side (for example, the uplink data is sent to the network side by using the bearer created or updated, or the wireless logical channel corresponding to the application Id is adopted by the UE. Send uplink data or perform corresponding scheduling algorithm according to QoS parameters).
  • the UE can also check whether the downlink data sent by the network is on the correct bearer.
  • FIG. 8 is a flowchart of the UE initiating resource reservation in this embodiment.
  • the process of the UE initiating resource reservation in this embodiment is as follows:
  • Step S801 after the UE establishes a PDN connection with the network, the UE decides to request a specific QoS guarantee for the application to be started or an ongoing application, and the UE according to the correspondence between the Application Id and the operating system application identifier, or the Application Id and the third-party application.
  • the corresponding relationship between the server IP address or the IP triplet, or the correspondence between the Application Id and the URL of the third-party application determines the Application Id corresponding to the application, and assigns the instance identifier.
  • the UE sends a resource reservation request message to the network side, where the message carries the Application Id, the instance identifier, and the QoS request parameter, and the message is sent to the gateway where the PCEF is located through one or more intermediate nodes.
  • the application saves the corresponding relationship, the Application Id only corresponds to one operating system application identifier, or the Application Id only corresponds to the server IP address or IP triplet of the third-party application, or the Application Id only corresponds to the URL of the third-party application. You may not carry an instance ID.
  • the UE before the UE sends the resource reservation request, the UE first checks whether the Application Id corresponding to the application already has a corresponding bearer (that is, whether the Application Id has the corresponding network side authorized QoS information), if not The UE performs step S801; if yes, the UE further checks whether the bearer is a GBR bearer (that is, whether there is a GBR parameter in the QoS information authorized by the network side), and if yes, the UE performs step S801; otherwise, the process ends, where needed When the uplink data of the application is sent, the UE directly sends the uplink data on the bearer corresponding to the Application Id, that is, the UE directly processes the uplink data according to the QoS information corresponding to the Application Id.
  • Step S802 the gateway where the PCEF is located receives the resource reservation request message, and sends a policy and charging rule request message to the PCRF, where the policy and charging rule request message carries an Application Id, an instance identifier, and a QoS request parameter.
  • Step S803 the PCRF receives the policy and charging rule request message and performs policy decision.
  • the PCRF formulates PCC rules for the application according to the policy and charging rule request message from the PCEF.
  • the PCC rules include Application Id, instance identifier, QoS parameters (such as QCI, ARP), and charging parameters.
  • Step S804 the PCRF sends a policy and charging rule request confirmation message to the PCEF, and carries the PCC rule.
  • Step S805 the PCEF executes a PCC rule, and initiates a process of resource reservation.
  • the process of performing bearer binding, creating or updating a bearer according to the PCC rule is performed by the PCEF.
  • the gateway where the PCEF is located sends a create bearer request message or an update bearer request message, and the message carries Application Id and QoS parameters.
  • the message is sent to the UE through one or more intermediate nodes, and the UE receives the message and returns an acknowledgement message to the network side.
  • the network ie, the radio base station
  • the network also sends the Application Id and the corresponding wireless logical channel information to the UE, and the UE acquires the logical channel used to send the Application Id corresponding data.
  • the network may provide the QoS information authorized by the network side to the UE in only one of the above manners. In this way, the UE obtains the QoS information of the network side authorization corresponding to the application by using the bearer creation or bearer modification process initiated by the PCEF.
  • the PCEF In order for the PCEF to perform the corresponding QoS policy on the data of the application, the PCEF is required to have an application detection function, that is, the PCEF can detect the application corresponding to the Application Id.
  • the UE determines, according to the Application Id and the instance identifier (optional), the QoS information of the network authorization to be initiated, in particular, the QoS information in the uplink direction.
  • the UE sends the uplink data to the network side by using the created or modified bearer, or the UE sends the uplink data to the network by using the wireless logical channel corresponding to the Application Id. Or execute the corresponding scheduling algorithm according to the QoS parameters.
  • the UE can also check whether the downlink data sent by the network is on the correct bearer.
  • FIG. 9 is a flowchart of the UE initiating resource reservation in this embodiment.
  • the process of the UE initiating resource reservation in this embodiment is as follows:
  • Step S901 After the UE establishes a PDN connection with the network, the UE determines to request a specific QoS guarantee for the application to be started or the application in progress, and the UE according to the correspondence between the Application Id and the operating system application identifier, or the Application Id and the third-party application.
  • the corresponding relationship between the server IP address or the IP triplet, or the correspondence between the Application Id and the URL of the third-party application determines the Application Id corresponding to the application, and assigns the instance identifier.
  • the UE sends a resource reservation request message to the network side, where the message carries the Application Id and the QoS request parameter, and the message is sent to the gateway or the base station where the BBERF is located through one or more intermediate nodes. If the UE saves the corresponding relationship, Application Id only corresponds to one operating system application identifier, or Application Id only corresponds to one The server IP address or IP triplet or Application Id of the three-party application only corresponds to the URL of the third-party application, and the instance identifier may not be carried.
  • the UE before the UE sends the resource reservation request, the UE first checks whether the Application Id corresponding to the application already has a corresponding bearer (that is, whether the Application Id already has authorized QoS information), if not, the UE Step S901 is performed; if yes, the UE further checks whether the bearer is a GBR bearer (that is, whether the authorized QoS information includes a GBR parameter), and if yes, the UE performs step S901; otherwise, the process ends, and the application needs to be sent.
  • the uplink data is sent by the UE directly on the bearer corresponding to the Application Id or the corresponding wireless logical channel, that is, the UE directly processes the uplink data according to the QoS information corresponding to the Application Id.
  • Step S902 the gateway or the base station where the BBERF is located receives the resource reservation request message, and then the BBERF sends a QoS rule request message to the PCRF, where the QoS rule request message carries the Application Id and the QoS request parameter;
  • Step S903 the PCRF receives the QoS rule request message and makes a policy decision.
  • the PCRF formulates a PCC rule for the application according to the request from the BBERF.
  • the PCC rule includes Application Id, QoS parameters (such as QCI, ARP), and charging parameters. Further, the PCRF formulates QoS rules according to PCC rules, the QoS rules including Application Id and QoS parameters.
  • Step S904 the PCRF sends a policy and charging rule to the BBERF to provide a QoS rule request acknowledgement message, and carries the QoS rule.
  • Step S905 The PCRF sends a policy and charging rule providing message to the PCEF, and carries the PCC rule.
  • Step S906 the PCEF returns a policy and charging rule to provide an acknowledgement message.
  • Step S907 the BBERF executes a QoS rule, and initiates a process of resource reservation.
  • the BBERF performs a process of binding, creating, or updating a bearer according to the QoS rule.
  • the gateway and the base station where the BBERF is located send a create bearer request message or an update bearer request message, where the message carries Application Id and QoS parameters, and the message is sent to the UE through one or more intermediate nodes, and after receiving the message, the UE returns a confirmation to the network.
  • the network ie wireless base station
  • the Application Id and the corresponding wireless logical channel information are also sent to the UE, and the UE acquires the logical channel used to send the Application Id corresponding data.
  • the network may provide the QoS information authorized by the network side to the UE in only one of the above manners. In this way, the UE obtains the QoS information of the network side authorization corresponding to the application through the bearer creation or modification process initiated by the BBERF.
  • the UE determines the QoS information of the network authorization of the application according to the Application Id and the instance identifier, in particular, the QoS information in the uplink direction. Thereafter, when the UE needs to send the data of the application identified by the Application Id to the network, the UE sends the uplink data to the network through the created or modified bearer, or the UE sends the uplink data to the network by using the wireless logical channel corresponding to the Application Id. In addition, the UE can also check whether the downlink data sent by the network is on the correct bearer.
  • the PCEF In order for the PCEF to perform the corresponding QoS policy on the data of the application, the PCEF is required to have an application detection function, that is, the PCEF can detect the application corresponding to the Application Id. If the BBERF is to implement the QoS rules, the BBERF also needs to have the ability to perform the identification application. For example, if the BBERF has the function of application detection or the PCEF performs the application detection, the application Id-related tag is marked on the application data packet.
  • the UE and the network side reserve resource channels for the application through the bearer creation or modification process.
  • the corresponding resource channel may be reserved for the application or the corresponding wireless logical channel may be negotiated by other means.
  • the PCRF sends a rule (PCC rule or QoS rule) carrying the application identifier (ie, Application Id) and the QoS parameter to the UE and the BBERF (where the BBERF can be located at the base station), and the UE and the BBERF reserve the resource channel for the application locally or
  • the PCRF sends the correspondence between the Application Id and the wireless logical channel to the UE and the BBERF, respectively, and the UE and the BBERF are saved locally, without interaction between the UE and the BBERF.
  • FIG. 10 is a flowchart of the network side initiating resource reservation in this embodiment.
  • the process of initiating resource reservation by the network side in this embodiment is as follows:
  • Step S1001 After the UE establishes a PDU session with the network, the UE interacts with the application layer of the application to negotiate the application to be initiated. In the negotiation process, the UE provides the Application Id and the instance identifier corresponding to the application, or the application layer provides the Application to the UE. Id and instance ID. If the application ID is only associated with one operating system application identifier, or a third-party application server IP address or IP triplet, or a third-party application URL, the application ID may not be carried. Instance ID.
  • the instance identifier is used to identify different applications with the same Application Id.
  • the instance identifier is dynamically allocated to the UE or the application server, ensuring that it is unique under the same Application Id, that is, the Application Id and the instance identifier can uniquely identify an application to be initiated by one UE.
  • Step S1002 The AF provides service information to the core network CP function entity, and provides Application Id, instance identifier, and requested QoS information in the service information.
  • Step S1003 The CP function entity performs a policy decision, that is, formulates a QoS policy for the application, where the QoS policy includes Application Id, QoS parameters (such as QCI, ARP), and charging parameters. Among them, the QoS parameters may also include GBR parameters.
  • Step S1004 The CP function entity sends the QoS policy to the core network UP function entity, where the Application Id, the QoS parameter, and the charging parameter are provided.
  • step S1005 the UP function entity returns an acknowledgement message.
  • Step S1006 The CP function entity sends the QoS policy to an access network (AN), where the Application Id and the QoS parameter are provided.
  • AN access network
  • the instance identifier may be selectively carried in the QoS policy sent to the AN.
  • step S1007 the AN returns a confirmation message.
  • Step S1008 in an exemplary embodiment, the CP function entity directly provides a QoS policy to the UE, where the QoS policy includes an Application Id, an instance identifier, and a QoS parameter.
  • step S1009 the UE returns an acknowledgement message to the CP function entity.
  • step S1010 the UE and the AN perform related air interface operations.
  • the AN provides the Application Id and the corresponding wireless logical channel information to the UE.
  • the UE and the AN perform related parameter configuration.
  • the AN will perform corresponding resource reservation. That is, a wireless logical channel that guarantees bandwidth is provided.
  • step S1008 and step S1009 are not performed, the AN will provide the UE with Application Id, QoS parameters and instance identification.
  • the CP function In order for the CP functional entity to perform the corresponding QoS policy on the applied data, the CP function is required.
  • the entity can have an application detection function, that is, the CP function entity can detect the application corresponding to the Application Id.
  • the AN also needs to have the ability to perform the identification application.
  • the AN has the function of application detection or the CP function entity performs the application detection, and marks the application Id related tag on the application data packet.
  • the UE negotiates with the application layer, and the Application Id and the requested QoS information are provided by the AF to the PCRF.
  • the application detection functions (such as PCEF and TDF) deployed in the network may also be used. Detecting the data being transmitted by the UE and the application layer, and reporting the Application Id and the instance identifier (optional) to the CP functional entity.
  • the CP function entity performs step QoS authorization in step S1003.
  • the UE determines, according to the Application Id and the instance identifier (optional), the QoS information of the network authorization of the application, in particular, the QoS information in the uplink direction.
  • the UE performs processing according to the QoS information sent by the network side (such as sending data through the reserved resource channel, or performing a corresponding scheduling algorithm according to the QoS parameter, or Transmitting data on the corresponding wireless logical channel).
  • the UE can also check whether the downlink data sent by the network performs the obtained QoS.
  • FIG. 11 is a flowchart of the network side initiating resource reservation in this embodiment.
  • the process of initiating resource reservation by the network side in this embodiment is as follows:
  • Step S1101 After the UE establishes a PDU session with the network, the UE decides to request a specific QoS guarantee for the new application to be started or the ongoing application, and the UE according to the correspondence between the Application Id and the operating system application identifier, or the Application Id and the third party.
  • the corresponding relationship between the server IP address or the IP triplet or the corresponding relationship between the Application Id and the URL of the third-party application is determined, and the application ID corresponding to the application is determined and the instance identifier is assigned.
  • the UE sends a QoS policy request message to the network side, where the message carries the Application Id, the instance identifier, and the QoS request parameters (such as QCI, GBR), and the message may be sent to the CP function entity through one or more intermediate nodes.
  • the application ID is associated with only one operating system application identifier, or a third-party application server IP address or an IP triplet, or a third-party application URL, the application ID may not carry the instance identifier.
  • the UE Before the UE sends the QoS policy request message, the UE first checks the corresponding application. Whether the application Id has the QoS information of the network authorization, if not, the UE performs step S1101; if yes, the UE further checks whether the QoS information includes the GBR parameter, and if so, the UE performs step S1101; otherwise, the process ends,
  • the UE directly sends the uplink data on the bearer corresponding to the Application Id or the corresponding wireless logical channel, that is, the UE directly performs the uplink data according to the QoS information corresponding to the Application Id. deal with.
  • Step S1102 The CP functional entity performs policy decision, and formulates a QoS policy for the application, where the QoS policy includes Application Id, QoS parameters (such as QCI, ARP), and charging parameters.
  • QoS policy includes Application Id, QoS parameters (such as QCI, ARP), and charging parameters.
  • the QoS parameters may also contain GBR parameters.
  • Step S1103 The CP function entity returns a QoS policy request acknowledgement message to the UE, where the message carries an authorized QoS policy, where the QoS policy includes an Application Id, an instance identifier, and a QoS parameter.
  • Step S1104 The CP function entity sends the QoS policy to the core network UP function entity, where the Application Id, the QoS parameter, and the charging parameter are provided.
  • step S1105 the UP function entity returns an acknowledgement message.
  • Step S1106 The CP function entity sends the QoS policy to the AN, where the Application Id and the QoS parameter are provided.
  • the QoS policy may also include an instance identification.
  • step S1107 the AN returns an acknowledgement message.
  • step S1108 the UE and the AN perform related air interface operations. That is, the AN sends the Application Id and the corresponding wireless logical channel information to the UE.
  • the UE and the AN perform related parameter configuration. If the QoS parameter carried in step S1106 includes the GBR parameter, the AN will perform corresponding resource reservation. If step S1103 is not performed, the AN will provide the UE with Application Id, QoS parameters, and instance identification.
  • the UE determines, according to the Application Id and the instance identifier, QoS information of the network authorization to be initiating the application, in particular, the QoS parameter in the uplink direction or the wireless logical channel information in the uplink direction.
  • the CP functional entity In order for the CP functional entity to perform a corresponding QoS policy on the data of the application, the CP functional entity is required to have an application detection function, that is, the CP functional entity can detect the corresponding application Id. application.
  • the AN also needs to have the ability to perform the identification application. For example, the AN has the function of application detection or the CP function entity performs the application detection, and marks the application Id related tag on the application data packet.
  • the UE performs processing according to the QoS parameters sent by the network side (such as sending data through the reserved resource channel or performing a corresponding scheduling algorithm according to the QoS parameter).
  • the UE can also check whether the downlink data sent by the network performs the obtained QoS.
  • an embodiment of the present invention further provides an application-based policy and a charging control device, where the device is deployed on a terminal, such as a UE, and includes: a first receiving module 1201 configured to receive a network side as The application identifies the authorized QoS information, where the application identifier is an Application Id pre-delivered by the network side, and is used to identify an application; the processing module 1202 is configured to apply, according to the QoS information, the application corresponding to the Application Id.
  • the uplink data is processed.
  • the QoS information includes at least one of the following: a QoS parameter, and wireless logical channel information.
  • the apparatus may further include: an allocation module 1203 configured to assign an instance identifier to the application, wherein the instance identifier is used to identify different applications having the same Application ID.
  • the apparatus may further include: a first sending module 1204 configured to send a QoS information request message to the network side, where the QoS information request message carries the application identifier and the requested QoS information.
  • the first sending module 1204 may be further configured to: when the QoS information request message is sent to the network side, further carry the instance identifier in the QoS information request message.
  • the apparatus may further include: a first sending module 1204 configured to negotiate with an application layer of the application, and provide the application identifier and the requested QoS information to the application layer, so that The application layer provides the application identifier and the requested QoS information to the network side.
  • the first sending module 1204 may be further configured to provide an instance identifier of the application to the application layer when the application identifier and the requested QoS information are provided to an application layer of the application.
  • the apparatus may further include: a determining module 1206 and a storage module 1205; and a storage module 1205, configured to save the Application Id and the operating system application identifier Corresponding relationship, or the correspondence between the Application Id and the server IP address or the IP triplet of the application, or the correspondence between the Application Id and the URL of the application; the determining module 1206 can be configured according to the storage module 1205 The stored correspondence is determined, and the Application Id of the application is determined.
  • the first receiving module 1201 may be further configured to acquire a correspondence between the Application Id and an operating system application identifier, or an Application Id and a server IP address or an IP triplet of the application. Corresponding relationship, or the correspondence between the application ID and the URL of the application, is saved in the storage module 1205, wherein the corresponding relationship is actively sent by the network side or sent in the first sending of the device.
  • the module 1204 sends the network side to the network side after the active request.
  • the first receiving module 1201 may be further configured to: obtain a correspondence between the Application Id and the operating system application identifier, or Application Id in a process of establishing a packet data network (PDN) connection or a packet data unit (PDU) session. a correspondence between a server IP address or an IP triplet of the application, or a correspondence between the Application Id and the URL of the application, and associating the correspondence with the PDN connection or the PDU session; or Obtaining, by the PDN connection or the PDU session, the correspondence between the Application Id and the operating system application identifier, or the correspondence between the Application Id and the server IP address or the IP triplet, or the Application Id and the application. Correspondence of the URL, and associating the correspondence with the PDN connection or the PDU session.
  • PDN packet data network
  • PDU packet data unit
  • the first receiving module 1201 may be configured to perform at least one of: receiving a message sent by the network side, where the message carries the Application Id and the network side authorized QoS a parameter, the QoS parameter includes a QoS parameter in an uplink direction, and a message sent by the network side, where the message carries the Application Id and wireless logical channel information, where the wireless logical channel information includes uplink wireless logic Channel information.
  • the message may also carry an instance identifier of the application, where the instance identifier is used to identify different applications with the same Application ID.
  • the apparatus may further include: a determining module 1207, configured to determine whether the QoS information authorized by the network side exists in the Application Id corresponding to the application, and if the QoS information does not exist, notify The first sending module 1204 sends the QoS information. a request message; if the QoS information is present, determining whether there is a guaranteed bit rate (GBR) parameter in the QoS information, and if the GBR parameter exists, notifying the first sending module 1204 to send the QoS information request message If the GBR parameter does not exist, the processing module 1202 is notified to process the uplink data of the application according to the QoS information corresponding to the Application Id.
  • a determining module 1207 configured to determine whether the QoS information authorized by the network side exists in the Application Id corresponding to the application, and if the QoS information does not exist, notify The first sending module 1204 sends the QoS information. a request message; if the QoS information is present, determining whether there is
  • the processing module 1202 may be configured to perform at least one of: performing a corresponding scheduling algorithm on the uplink data of the application according to the QoS parameter; and sending the uplink data by using a wireless logical channel corresponding to the wireless logical channel information. .
  • the embodiment of the present invention further provides another application-based policy and charging control device, which is deployed on a network side entity, and includes: a second receiving module 1302 and a second sending module 1301;
  • the second receiving module 1302 is configured to receive an application identifier corresponding to the application provided by the UE, where the application identifier is an Application Id pre-delivered by the network side, and the second sending module 1301 is configured to return to the UE.
  • QoS information wherein the QoS information includes at least one of the following: a QoS parameter authorized by the network side for the application, and wireless logical channel information.
  • the second receiving module 1302 may be further configured to receive an instance identifier of the application that is further provided by the UE while providing the application identifier, where the instance identifier is used to identify Different applications with the same Application Id.
  • the second sending module 1301 may be further configured to perform at least one of: actively sending a correspondence between the Application Id and the operating system application identifier to the UE, or the Application Id and the a correspondence between a server IP address or an IP triplet of the application, or a correspondence between the Application Id and the URL of the application; after the second receiving module 1302 receives the request of the UE, sending the Application Corresponding relationship between the Id and the operating system application identifier, or the correspondence between the Application Id and the server IP address or the IP triplet of the application, or the correspondence between the Application Id and the URL of the application to the UE .
  • the second sending module 1301 may be configured to perform at least one of: returning a message to the UE, where the message carries the Application Id and the network side authorized QoS parameter, the QoS parameter Include a QoS parameter in an uplink direction; return a message to the UE, where the message carries the Application Id and wireless logical channel information, the wireless logic
  • the channel information includes wireless logical channel information in the uplink direction.
  • the second receiving module 1302 may be configured to receive a QoS information request message sent by the UE to the network side, where the QoS information request message carries the Application Id of the application and the requested
  • the QoS parameter may be configured to return, to the UE, a message carrying the QoS parameters authorized by the Application Id and the network side, where the QoS parameter includes a QoS parameter in an uplink direction.
  • the QoS information request message may further carry an instance identifier of the application; the message carrying the QoS parameter of the Application Id and the network side authorization may further include an instance identifier of the application.
  • an embodiment of the present invention further provides an application-based policy and charging control system, where the system includes: a UE and a network side entity; the UE includes the apparatus shown in FIG. 12, and the network The side entity includes the device as shown in FIG.
  • an embodiment of the present invention further provides a computer readable storage medium storing computer executable instructions, which are implemented by a processor to implement the above application-based policy and charging control method.
  • computer storage medium includes volatile and nonvolatile, implemented in any method or technology for storing information, such as computer readable instructions, data structures, program modules or other data. Sex, removable and non-removable media.
  • Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridge, magnetic tape, magnetic disk storage or other magnetic storage device, or may Any other medium used to store the desired information and that can be accessed by the computer.
  • the letter medium typically includes computer readable instructions, data structures, program modules or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and can include any information delivery media.
  • the embodiment of the present invention provides an application-based policy and charging control method, device, and system, so that the network side can notify the UE of the QoS information of the uplink data in time, and solves the problem that the uplink bearer cannot be effectively notified to the UE.

Landscapes

  • Engineering & Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本文公布一种基于应用的策略和计费控制方法，包括：UE接收网络侧为应用标识授权的服务质量QoS信息，所述应用标识为所述网络侧预下发的运营商定义应用标识Application Id；所述UE根据所述QoS信息对所述Application Id对应的应用的上行数据进行处理；所述QoS信息包括以下至少之一：QoS参数、无线逻辑信道信息。相应的，本文还公布了一种基于应用的策略和计费控制装置及系统，使得网络侧能够及时通知UE上行数据的QoS参数，解决了相关技术中无法有效通知UE上行承载的问题。

Description

一种基于应用的策略和计费控制方法、装置及系统 技术领域
本申请涉及但不限于通信技术领域，尤指一种基于应用的策略和计费控制方法、装置及系统。
背景技术
为了保持第三代移动通信系统在通信领域的竞争力，为用户提供速率更快、时延更低、更加个性化的移动通信服务，同时，降低运营商的运营成本，第三代合作伙伴计划(3GPP，3rd Generation Partnership Project)标准工作组正致力于下一代无线移动接入网络的研究。下一代无线接入网络中，支持多种无线网络的接入统一的核心网，并且希望无线接入网(RAN，Radio Access Network)和核心网(CN，Core Network)尽量减少耦合关系，即不管终端从什么接入技术的RAN接入，都可以接入到统一的CN中去。
下一代网络的核心网功能可能与现有技术有很多不同，其中，现有技术的核心网架构中，包含了归属用户服务器(HSS，Home Subscriber Server)、移动性管理实体(MME，Mobility Management Entity)、服务GPRS支持节点(SGSN，Serving GPRS Support Node)、策略计费规则功能(PCRF，Policy and Charging Rule Function)实体、服务网关(S-GW，Serving Gateway)、分组数据网关(P-GW，PDN Gateway)和分组数据网络(PDN，Packet Data Network)。其中，HSS是用户签约数据的永久存放地点，位于用户签约的归属网；MME是用户签约数据在当前网络的存放地点，负责终端到网络的非接入层信令管理、终端的安全验证功能、终端的移动性管理、用户空闲模式下的跟踪和寻呼管理功能和承载管理；SGSN是GERAN(GSM/EDGE无线接入网)和UTRAN(UMTS无线接入网)用户接入核心网络的业务支持点，功能上与MME类似，负责用户的位置更新、寻呼管理和承载管理等功能；S-GW是核心网到无线系统的网关，负责终端到核心网的用户面承载、终端空闲模式下的数据缓存、网络侧发起业务请求的功能、合法监听和分组数据路由和转发功能；S-GW还负责统计用户终端使用无线网的情况，并产 生终端使用无线网的话单，传送给计费网关。P-GW是演进系统和该系统外部分组数据网络的网关，它连接到因特网和分组数据网络上，负责终端的互联网协议(IP，Internet Protocol)地址分配、计费功能、分组包过滤、策略控制等功能。分组数据网络是运营商的IP业务网络，该网络通过运营商的核心网为用户提供IP服务；PCRF实体是演进系统中负责提供计费控制、在线信用控制、门限控制、服务质量(QoS，Quality of Service)策略方面规则的服务器。
3GPP定义的策略和计费控制架构如图1所示，包括：PCRF、策略和计费执行功能实体(PCEF，Policy and Charging Enforcement Function)、应用功能实体(AF，Application Function)、在线计费系统(OCS，Online Charging System)、离线计费系统(OFCS，Offline Charging System)、用户属性存储器(SPR，Subscription Profile Repository)、承载绑定及事件报告功能实体(BBERF，Bearing Binding and Event Report Function)以及流量检测功能实体(TDF，Traffic Detection Function)。其中，Rx是AF和PCRF之间的参考点，Gx是PCEF和PCRF之间的参考点，Sp是SPR和PCRF之间的参考点，Gy是OCS和PCEF之间的参考点，Gz是PCEF和OFCS之间的参考点，Sd是TDF和PCRF之间的参考点，Gxx是PCRF和BBERF之间的参考点。
为了实现端到端的QoS保证，3GPP网络提供基于承载粒度的QoS保障。被映射到同一个承载的业务将被采用相同的承载层包转发处理。若需要提供不同的承载层包转发处理，则需要将业务流映射到不同的演进分组核心网承载业务架构(EPS，Evolved Packet System)承载上。一般一个承载有一个关联的过滤器模板(TFT，traffic flow template)。上行业务流模板(UL TFT)是TFT中的上行包过滤器集合。下行业务流模板(DL TFT)是TFT中的下行包过滤器集合。每个公用数据网(PDN，Public Data Network)连接中允许有一个承载没有TFT。EPS IP连接访问网络(IP-CAN，IP-Connectivity Access Network)默认承载可能没有TFT。
PCRF实体下发的策略和计费控制(PCC，Policy and Charging Control)或QoS规则中包含一个业务数据流过滤器模板(SDF template，Service Data Flow template)，SDF template中通常包含一个或多个业务数据流过滤器。 PCRF实体可以提供一个包含通配的(wild-carded)业务数据流过滤器的PCC规则，以便允许无法匹配其他任何PCC或QoS规则的数据包通过。
当位于P-GW或S-GW的策略执行功能(PEF，Policy Enforcement Function)安装或激活PCRF提供的策略规则后，PEF根据规则中的服务质量级别标识(QCI，QoS Class Identifier)/分配和保留优先级(ARP Allocation and Retention Priority)执行承载绑定，并根据规则中的SDF template构造TFT以发送给用户设备(UE，User Equipment)。尽管相同QCI/ARP的规则可以绑定到同一个承载上，但是并不是相同QCI/ARP的规则总是绑定到同一个承载。因此，PCRF在提供策略规则时无法确定规则绑定到哪个承载上，而PEF最终决定将策略规则绑定到特定的承载上。
对于保证比特率(GBR，Guaranteed Bit Rate)承载，PEF将承载的GBR设置为绑定到这个承载的所有策略规则的GBR的总和，将承载的最大比特率(MBR)设置为绑定到这个承载的所有策略规则的MBR的总和。当IP-CAN类型支持Non-GBR承载可以有分开的MBR时，将Non-GBR承载的MBR设置为绑定到这个承载的所有策略规则的MBR的总和。核心网和无线侧将根据QCI、ARP、GBR以及MRB为承载分配相应的资源。
因此，现有的QoS保障机制要求网络或终端根据业务过滤器识别一个业务的数据包，从而对识别出的数据包应用相应的QoS。然而，这种方式往往无法通知UE上行数据的QoS参数，具体存在以下问题：
1)对于同一个应用的不同业务数据流，尽管他们具有相同的QoS，但具有不同的业务过滤器，为了能够通知UE该业务数据流的上行QoS，则需要网络和终端之间进行交互，从而产生了不必要的信令。
2)当终端运行一类不可推倒(non-deducible)(即不能获得稳定业务过滤器)的应用时，比如对等网络(P2P，Peer-to-Peer)业务时，由于网络无法将业务过滤器与承载的绑定关系通知给终端，所以无法让终端获知这类应用的上行QoS参数。目前对这类应用的处理是将其放到默认承载上。
综上可知，在现有的相关技术中，存在无法有效通知UE上行承载的问题，也可以说无法通知UE上行数据的QoS参数的问题。针对此问题，目前还没有有效的解决方案。
此外，目前正在开展下一代网络架构的研究，而在下一代网络中上述问题也同样存在。下一代网络的框架如图2所示。其中，核心网包括控制面(CP)功能实体和用户面(UP)功能实体，这些功能实体可以是多个。CP功能实体可以根据所管理的内容更加具体的划分为移动管理实体、会话管理实体、地址分配实体、QoS策略制定实体等等。UP功能实体可以是用于数据转发的一个或者多个功能实体。如果存在多个CP功能实体，则可能有唯一的对接入网(AN，Access Network)的接口，也可能有多个对AN的接口。对于前者，当其他与AN没有接口的CP功能实体需要下发相关参数给AN时，可以通过有接口的CP功能实体转发。在下一代网络中支持多种接入网络，这里以AN作为统称。对于不同的接入点，可能连接的CN的CP功能实体的接口和协议类型都有所不同。在下一代网络中，承载的概念在有些情况下可能不存在，但是在现有网络中的问题还是存在的，即无法通知UE上行数据的QoS参数。
发明概述
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本发明实施例提供了一种基于应用的策略和计费控制方法及装置、系统，以至少解决相关技术中无法有效通知UE上行承载的问题。
第一方面，本发明实施例提供了一种基于应用的策略和计费控制方法，包括：
UE接收网络侧为应用标识授权的服务质量(QoS)信息，所述应用标识为所述网络侧预下发的运营商定义应用标识(Application Id)；
所述UE根据所述QoS信息对所述Application Id对应的应用的上行数据进行处理；
所述QoS信息包括以下至少之一：QoS参数、无线逻辑信道信息。
其中，所述UE接收网络侧为应用标识授权的QoS信息之前，所述方法还可以包括：所述UE向所述网络侧发送QoS信息请求消息，所述QoS信息 请求消息携带所述应用标识和请求的QoS信息。
其中，所述UE向所述网络侧发送QoS信息请求消息时，所述方法还可以包括：所述UE为所述应用分配实例标识，并在所述QoS信息请求消息中携带所述实例标识，所述实例标识用于标识具有相同Application Id的不同应用。
其中，所述UE接收网络侧为应用标识授权的QoS信息之前，所述方法还可以包括：所述UE与所述应用的应用层协商，将所述应用标识和请求的QoS信息提供给所述应用层，再由所述应用层向所述网络侧提供所述应用标识和请求的QoS信息。
其中，所述方法还可以包括：所述UE为所述应用分配实例标识，所述实例标识用于标识具有相同Application Id的不同应用；
所述UE接收网络侧为应用标识授权的QoS信息之前，所述方法还可以包括：所述UE与所述应用的应用层协商，将应用的应用标识、实例标识和请求的QoS信息提供给所述应用层，再由所述应用层向所述网络侧提供所述应用标识、实例标识和请求的QoS信息。
其中，所述UE根据所述QoS信息对所述Application Id对应的应用的上行数据进行处理之前，所述方法还可以包括：所述UE根据本地保存的Application Id和操作系统应用标识的对应关系、或Application Id和所述应用的服务器IP地址或IP三元组的对应关系、或Application Id和所述应用的URL的对应关系，确定所述应用的Application Id。
其中，所述方法还可以包括：所述UE从所述网络侧获取所述Application Id和操作系统应用标识的对应关系、或所述Application Id和所述应用的服务器IP地址或IP三元组的对应关系、或所述Application Id和所述应用的URL的对应关系并保存。
其中，所述UE从所述网络侧获取所述Application Id和操作系统应用标识的对应关系、或所述Application Id和所述应用的服务器IP地址或IP三元组的对应关系、或所述Application Id和所述应用的URL的对应关系，可以包括：所述UE向所述网络侧请求并接收所述Application Id和操作系统应用标识的对应关系、或所述Application Id和所述应用的服务器IP地址或IP三 元组的对应关系、或所述Application Id和所述应用的URL的对应关系并保存；或者，所述UE接收所述网络侧主动下发的所述Application Id和操作系统应用标识的对应关系或所述Application Id和所述应用的服务器IP地址或IP三元组的对应关系、或所述Application Id和所述应用的URL的对应关系并保存。
其中，所述UE可以在分组数据网络(PDN)连接或分组数据单元(PDU)会话建立的过程中获取所述Application Id和操作系统应用标识的对应关系、或所述Application Id和所述应用的服务器IP地址或IP三元组的对应关系、或所述Application Id和所述应用的URL的对应关系，并将所述对应关系与所述PDN连接或所述PDU会话关联；
或者，所述UE可以在PDN连接或PDU会话建立后获取所述Application Id和操作系统应用标识的对应关系、或所述Application Id和所述应用的服务器IP地址或IP三元组的对应关系、或所述Application Id和所述应用的URL的对应关系，并将所述对应关系与所述PDN连接或所述PDU会话关联。
其中，所述UE接收网络侧为应用标识授权的QoS信息，可以包括以下至少之一：所述UE接收所述网络侧发送的消息，所述消息携带所述Application Id和所述网络侧授权的QoS参数，所述QoS参数包含上行方向的QoS参数；所述UE接收所述网络侧发送的消息，所述消息携带所述Application Id和无线逻辑信道信息，所述无线逻辑信道信息包含上行方向的无线逻辑信道信息。
其中，所述消息还可以携带有所述应用的实例标识，所述实例标识可以用于标识具有相同Application Id的不同应用。
其中，所述UE根据所述QoS信息对所述Application Id对应的应用的上行数据进行处理，可以包括以下至少之一：所述UE根据所述QoS参数对所述应用的上行数据执行对应的调度算法；所述UE采用所述无线逻辑信道信息对应的无线逻辑信道发送上行数据。
其中，所述UE向所述网络侧发送QoS信息请求消息之前，所述方法还可以包括：所述UE判断所述应用对应的Application Id是否已存在所述网络侧授权的QoS信息，若不存在所述QoS信息，则所述UE发送所述QoS信 息请求消息；若存在所述QoS信息，则所述UE判断所述QoS参数中是否存在保证比特率(GBR)参数，若存在所述GBR参数，则所述UE发送所述QoS信息请求消息；若不存在所述GBR参数，所述UE根据所述Application Id对应的QoS信息对所述应用的上行数据进行处理。
第二方面，本发明实施例还提供一种基于应用的策略和计费控制装置，包括：
第一接收模块，配置为接收网络侧为应用标识授权的QoS信息，其中，所述应用标识为所述网络侧预下发的运营商定义应用标识(Application Id)；
处理模块，配置为根据所述QoS信息对所述Application Id对应的应用的上行数据进行处理；
其中，所述QoS信息包括以下至少之一：QoS参数、无线逻辑信道信息。
其中，所述装置还可以包括：第一发送模块，配置为向所述网络侧发送QoS信息请求消息，其中，所述QoS信息请求消息携带所述应用标识和请求的QoS信息。
其中，所述装置还可以包括：分配模块，配置为给所述应用分配实例标识，其中，所述实例标识用于标识具有相同Application Id的不同应用；所述第一发送模块，还可以配置为在向所述网络侧发送QoS信息请求消息时，还在所述QoS信息请求消息中携带所述实例标识。
其中，所述装置还可以包括：第一发送模块，配置为与所述应用的应用层协商，将所述应用标识和请求的QoS信息提供给所述应用层，以使得所述应用层将所述应用标识和请求的QoS信息提供给所述网络侧。
其中，所述装置还可以包括：分配模块，配置为给所述应用分配实例标识，其中，所述实例标识用于标识具有相同Application Id的不同应用；所述第一发送模块，还可以配置为在向所述应用的应用层提供所述应用标识和请求的QoS信息时，还向所述应用层提供所述应用的实例标识。
其中，所述装置还可以包括：确定模块和存储模块；存储模块，配置为保存Application Id和操作系统应用标识的对应关系、或Application Id和所述应用的服务器IP地址或IP三元组的对应关系、或Application Id和所述应 用的URL的对应关系；确定模块，配置为根据所述存储模块保存的所述对应关系，确定所述应用的Application Id。
其中，所述第一接收模块，还可以配置为获取所述Application Id和操作系统应用标识的对应关系、或Application Id和所述应用的服务器IP地址或IP三元组的对应关系、或Application Id和所述应用的URL的对应关系并保存到存储模块中，其中，所述对应关系为所述网络侧主动下发的、或者在所述装置的第一发送模块向所述网络侧主动请求之后所述网络侧下发的。
其中，所述第一接收模块，还可以配置为：在PDN连接或PDU会话建立的过程中获取所述Application Id和操作系统应用标识的对应关系、或所述Application Id和所述应用的服务器IP地址或IP三元组的对应关系、或所述Application Id和所述应用的URL的对应关系，并将所述对应关系与所述PDN连接或所述PDU会话关联；或者，在PDN连接或PDU会话建立后获取所述Application Id和操作系统应用标识的对应关系、或所述Application Id和所述应用的服务器IP地址或IP三元组的对应关系、或所述Application Id和所述应用的URL的对应关系，并将所述对应关系与所述PDN连接或所述PDU会话关联。
其中，所述第一接收模块，可以配置为执行以下至少一项：接收所述网络侧发送的消息，其中，所述消息携带所述Application Id和所述网络侧授权的QoS参数，所述QoS参数包含上行方向的QoS参数；接收所述网络侧发送的消息，其中，所述消息携带所述Application Id和无线逻辑信道信息，所述无线逻辑信道信息包含上行方向的无线逻辑信道信息。
其中，所述消息还可以携带有所述应用的实例标识，所述实例标识可以用于标识具有相同Application Id的不同应用。
其中，所述装置还可以包括：判断模块，配置为判断所述应用对应的Application Id是否已存在所述网络侧授权的QoS信息，若不存在所述QoS信息，则通知所述第一发送模块发送所述QoS信息请求消息；若存在所述QoS信息，则判断所述QoS信息中是否存在保证比特率(GBR)参数，若存在所述GBR参数，则通知所述第一发送模块发送所述QoS信息请求消息；若不存在所述GBR参数，则通知所述处理模块根据所述Application Id对应 的QoS参数对所述应用的上行数据进行处理。
其中，所述处理模块，可以配置为执行以下至少一项：根据所述QoS参数对所述应用的上行数据执行对应的调度算法；采用所述无线逻辑信道信息对应的无线逻辑信道发送上行数据。
第三方面，本发明实施例还提供了一种基于应用的策略和计费控制装置，包括：第二接收模块和第二发送模块；
第二接收模块，配置为接收UE提供的应用对应的应用标识，其中，所述应用标识为所述网络侧预下发的运营商定义应用标识(Application Id)；
第二发送模块，配置为向所述UE返回QoS信息，其中，所述QoS信息包括以下至少之一：网络侧为所述应用授权的QoS参数、无线逻辑信道信息。
其中，所述第二接收模块，还可以配置为接收所述UE在提供所述应用标识的同时还提供的所述应用的实例标识，其中，所述实例标识用于标识具有相同Application Id的不同应用。
其中，所述第二发送模块，还可以配置为执行以下至少一项：主动向所述UE发送Application Id和操作系统应用标识的对应关系、或所述Application Id和所述应用的服务器IP地址或IP三元组的对应关系、或所述Application Id和所述应用的URL的对应关系；在所述第二接收模块接收到所述UE的请求之后，向所述UE发送所述Application Id和操作系统应用标识的对应关系、或所述Application Id和所述应用的服务器IP地址或IP三元组的对应关系、或所述Application Id和所述应用的URL的对应关系。
其中，所述第二发送模块，可以配置为执行以下至少一项：向所述UE返回消息，其中，所述消息携带所述Application Id和所述网络侧授权的QoS参数，所述QoS参数包含上行方向的QoS参数；向所述UE返回消息，其中，所述消息携带所述Application Id和无线逻辑信道信息，所述无线逻辑信道信息包含上行方向的无线逻辑信道信息。
其中，所述第二接收模块，可以配置为接收所述UE向网络侧发送的QoS信息请求消息，其中，所述QoS信息请求消息携带所述应用的Application Id和请求的QoS参数；所述第二发送模块，可以配置为向所述UE返回携带所 述Application Id和网络侧授权的QoS参数的消息，其中，所述QoS参数包含上行方向的QoS参数。
其中，所述QoS信息请求消息还可以携带所述应用的实例标识；所述携带所述Application Id和网络侧授权的QoS参数的消息还可以包含所述应用的实例标识；所述实例标识可以用于标识具有相同Application Id的不同应用。
第四方面，本发明实施例还提供一种基于应用的策略和计费控制系统，包括：UE和网络侧实体；所述UE包括上述第二方面的装置，所述网络侧实体包括上述第三方面的装置。
此外，本发明实施例还提供一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被处理器执行时实现上述的基于应用的策略和计费控制方法。
本发明实施例中，UE根据应用标识获取所述应用的QoS信息，该QoS信息可包括以下至少之一：QoS参数、无线逻辑信道信息，需要向网络侧发送所述应用的数据时，UE根据所述QoS信息进行处理。如此，使得网络侧能够及时通知UE上行数据的QoS信息，解决了无法有效通知UE上行承载的问题。
本申请的其它特征和优点将在随后的说明书中阐述，并且，部分地从说明书中变得显而易见，或者通过实施本申请而了解。本申请的目的和其他优点可通过在说明书、权利要求书以及附图中所特别指出的结构来实现和获得。
附图概述
附图用来提供对本申请技术方案的进一步理解，并且构成说明书的一部分，与本申请的实施例一起用于解释本申请的技术方案，并不构成对本申请技术方案的限制。
图1为相关技术中3GPP定义的策略和计费控制架构示意图；
图2为下一代网络的架构示意图；
图3为本发明实施例的基于应用的策略和计费控制方法的流程示意图；
图4为根据本发明实施例一的流程图；
图5为本发明实施例二的流程图；
图6为本发明实施例三的网络侧发起资源预留的流程图；
图7为本发明实施例四的网络侧发起资源预留的流程图；
图8为本发明实施例五的UE发起资源预留的流程图；
图9为本发明实施例六的UE发起资源预留的流程图；
图10为本发明实施例七的网络侧发起资源预留的流程图；
图11为本发明实施例八的网络侧发起资源预留的流程图；
图12为本发明实施例的部署在UE侧的基于应用的策略和计费控制装置的组成结构示意图；
图13为本发明实施例的部署在网络侧的基于应用的策略和计费控制装置的组成结构示意图；
图14为本发明实施例的基于应用的策略和计费控制系统的组成结构示意图。
详述
下文中将结合附图对本申请的实施例进行详细说明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。
在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行。并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
如图3所示，本发明实施例的一种基于应用的策略和计费控制方法，主要可以包括如下步骤：
步骤301：UE接收网络侧为应用标识授权的QoS信息，所述应用标识为所述网络侧预下发的运营商定义应用标识(Application Id)；
步骤302：所述UE根据所述QoS信息对所述Application Id对应的应用的上行数据进行处理。
其中，所述QoS信息包括以下至少一项：QoS参数、无线逻辑信道信息。
在示例性实施方式中，在步骤301之前，所述方法还可以包括：所述UE向所述网络侧发送QoS信息请求消息，所述QoS信息请求消息携带所述应用标识和请求的QoS信息。这里，所述UE向所述网络侧发送QoS信息请求消息时，所述方法还可以包括：所述UE为所述应用分配实例标识，并在所述QoS信息请求消息中携带所述实例标识，所述实例标识用于标识具有相同Application Id的不同应用。
在示例性实施方式中，在步骤301之前，所述方法还可以包括：所述UE与所述应用的应用层协商，将所述应用标识和请求的QoS信息提供给所述应用层，再由所述应用层向所述网络侧提供所述应用标识和请求的QoS信息。这里，所述方法还可以包括：所述UE为所述应用分配实例标识，所述实例标识用于标识具有相同Application Id的不同应用；所述UE接收网络侧为应用标识授权的QoS信息之前，所述方法还可以包括：所述UE与所述应用的应用层协商，将应用的应用标识、实例标识和请求的QoS信息提供给所述应用层，再由所述应用层向所述网络侧提供所述应用标识、实例标识和请求的QoS信息。
在示例性实施方式中，在步骤302之前，所述方法还可以包括：所述UE根据本地保存的Application Id和操作系统应用标识的对应关系、或Application Id和第三方应用(这里的第三方应用即为步骤302中所述Application Id对应的应用，下文同，不做赘述)的服务器IP地址或IP三元组的对应关系、或Application Id和第三方应用的统一资源定位符(URL)的对应关系，确定所述应用的Application Id。这里，所述方法还可以包括：所述UE从所述网络侧获取所述Application Id和操作系统应用标识的对应关系、或Application Id和第三方应用的服务器IP地址或IP三元组的对应关系、或Application Id和第三方应用的URL的对应关系并保存。其中，所述UE可以向所述网络侧请求并接收所述Application Id和操作系统应用标识的对应关系、或Application Id和第三方应用的服务器IP地址或IP三元组的对应关系、或Application Id和第三方应用的URL的对应关系并保存；或者，所述UE可以接收所述网络侧主动下发的所述Application Id和操作系统应用标识的对应关系、或Application Id和第三方应用的服务器IP地址或IP三元组的对 应关系、或Application Id和第三方应用的URL的对应关系并保存。
在示例性实施方式中，所述UE可以在分组数据网络(PDN)连接或分组数据单元(PDU)会话建立的过程中，获取所述Application Id和操作系统应用标识的对应关系、或Application Id和第三方应用的服务器IP地址或IP三元组的对应关系、或Application Id和第三方应用的URL的对应关系，并将所述对应关系与所述PDN连接或所述PDU会话关联；或者，所述UE可以在PDN连接或PDU会话建立后，获取所述Application Id和操作系统应用标识的对应关系、或Application Id和第三方应用的服务器IP地址或IP三元组的对应关系、或Application Id和第三方应用的URL的对应关系，并将所述对应关系与所述PDN连接或所述PDU会话关联。
在示例性实施方式中，步骤301中，UE接收网络侧为应用标识授权的QoS信息，可以包括以下至少之一：所述UE接收所述网络侧发送的消息，所述消息携带所述Application Id和所述网络侧授权的QoS参数，所述QoS参数包含上行方向的QoS参数；所述UE接收所述网络侧发送的消息，所述消息携带所述Application Id和所述网络侧授权的传输所述应用数据的无线逻辑信道信息，所述无线逻辑信道信息包含上行方向的无线逻辑信道信息。这里，所述消息还可以携带有所述应用的实例标识，所述实例标识用于标识具有相同Application Id的不同应用。
在示例性实施方式中，所述UE向所述网络侧发送QoS信息请求消息之前，所述方法还可以包括：所述UE判断所述应用对应的Application Id是否已存在所述网络侧授权的QoS信息，若不存在所述QoS信息，则所述UE发送所述QoS信息请求消息；若存在所述QoS信息，则所述UE判断所述QoS信息中是否存在保证比特率(GBR)参数，若存在所述GBR参数，则所述UE发送所述QoS信息请求消息；若不存在所述GBR参数，所述UE不发送所述QoS信息请求消息，并根据所述Application Id对应的QoS信息对所述应用的上行数据进行处理。
下文中将参考附图并结合实施例来详细说明本申请。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
下面结合示例性实施例进行详细说明。
实施例一
图4是根据本发明实施例的网络侧向终端侧提供运营商定义应用标识(Application Id)和操作系统应用标识的对应关系、或Application Id和第三方应用的服务器IP地址或IP三元组的对应关系、或Application Id和第三方应用的URL的对应关系的流程图，如图4所示，步骤如下：
步骤S401，部署在运营商网络中的策略服务功能实体配置Application Id和操作系统应用标识的对应关系，UE接入网络并与策略服务功能实体建立连接后，策略服务功能实体向UE发送Application Id和操作系统应用标识的对应关系、Application Id和第三方应用的服务器IP地址或IP三元组的对应关系、或Application Id和第三方应用的URL的对应关系。
其中，操作系统应用标识可以包括两部分：操作系统标识(OSId，Operating System Identifier)和操作系统特定应用标识(OSAppId，OS specific Application Identifier)。其中，OSId为操作系统类型的标识，如Android操作系统、iOS操作系统等。OSAppId用于在特定操作系统中标识应用。若策略服务功能实体在下发所述对应关系前获取了UE的操作系统标识，那么操作系统应用标识可以只包含OSAppId。
步骤S402，UE接收并保存所述策略服务功能实体下发的Application Id和操作系统应用标识的对应关系、或Application Id和第三方应用的服务器IP地址或IP三元组的对应关系、或Application Id和第三方应用的URL的对应关系，并返回确认消息。
通过上述对应关系，UE获取了操作系统中安装的应用对应的Application Id，比如QQ、微信对应Application Id1；微信、淘宝对应Application Id2。
其中，Application Id和操作系统应用标识的对应关系、或Application Id和第三方应用的服务器IP地址或IP三元组的对应关系、或Application Id和第三方应用的URL的对应关系发生变化时，策略服务功能实体需要向UE更新所述对应关系，更新的过程也可以通过本实施例的流程实现。
实施例二
图5是本实施例的UE向网络侧请求Application Id和操作系统应用标识 的对应关系的流程图，步骤如下：
步骤S501，UE安装或运行了一个应用，UE检测到本地没有该应用对应的Application Id，则UE向策略服务功能实体请求Application Id，请求消息中携带一个或多个操作系统应用标识、第三方应用的服务器IP地址或IP三元组、或第三方应用的URL等；或是UE连接到网络后，根据UE配置的策略或网络下发的策略，UE向策略服务功能实体请求Application Id，请求消息中携带一个或多个操作系统应用标识、第三方应用的服务器IP地址或IP三元组、或第三方应用的URL等；
步骤S502，策略服务功能实体向UE返回确认消息，确认消息中携带该应用对应的Application Id，UE接收并保存所述Application Id与操作系统应用标识的对应关系、Application Id和第三方应用的服务器IP地址或IP三元组的对应关系、或Application Id和第三方应用的URL的对应关系。
策略服务功能实体可以独立部署，或是与其他功能实体集成。如在EPS系统中，策略服务功能实体可以集成在P-GW或PCRF中，在图2所示的下一代网络架构中，策略服务功能可以集成在CP功能实体(CP Function)或UP功能实体(UP Function)中。
在上述实施例中，在UE和策略服务功能实体建立连接之前，UE需要接入网络并建立PDN连接或分组数据单元(PDU，Packet Data Unit)会话，在建立PDN连接或PDU会话后，网络侧可以向UE提供策略服务功能实体的地址，这样UE就可以与策略服务功能实体建立连接了。
在上述实施例中，策略服务功能实体与UE建立连接后，可以采用单独的消息向UE提供上述对应关系；在其他实施例中，策略服务功能实体也可以在UE发起的PDN连接或PDU会话建立的应答消息中将上述对应关系发送给UE。
由于每个运营商都会定义自己的Application Id和操作系统应用标识的对应关系、或Application Id和第三方应用的服务器IP地址或IP三元组的对应关系、或Application Id和第三方应用的URL的对应关系，因此，UE可能会保存多份对应关系。在实际应用中，当UE接入网络建立PDN连接或PDN会话后，与向UE提供接入PDN网络的网关功能实体位于同一网络中的策略 服务功能实体会向UE提供该PDN连接或PDU会话的Application Id和操作系统应用标识的对应关系、Application Id和第三方应用的服务器IP地址或IP三元组的对应关系、或Application Id和第三方应用的URL的对应关系。UE还会将所述Application Id和操作系统应用标识的对应关系、或Application Id和第三方应用的服务器IP地址或IP三元组的对应关系、或Application Id和第三方应用的URL的对应关系，与所述PDN连接或PDU会话进行关联。
例如，在EPS系统中，若UE发生漫游时，UE同时建立了一个家乡漫游(Home-Routed)(P-GW位于HPLMN(Home Public Land Mobile Network，本地公用陆地移动网络))和一个本地疏导(Local Breakout)(P-GW位于VPLMN(Virtual Public Land Mobile Network，虚拟公共陆地移动网络))的PDN连接后，位于HPLMN的策略服务功能实体为家乡漫游的PDN连接提供所述Application Id和操作系统应用标识的对应关系、或Application Id和第三方应用的服务器IP地址或IP三元组的对应关系、或Application Id和第三方应用的URL的对应关系给UE，而位于VPLMN的策略服务功能实体为本地疏导的PDN连接提供所述Application Id和操作系统应用标识的对应关系、或Application Id和第三方应用的服务器IP地址或IP三元组的对应关系、或Application Id和第三方应用的URL的对应关系给UE。类似的，与向UE提供接入PDN网络的UP功能实体同一个PLMN的策略服务功能实体会向UE提供该PDN连接或PDU会话关联的所述Application Id和操作系统应用标识的对应关系、或Application Id和第三方应用的服务器IP地址或IP三元组的对应关系、或Application Id和第三方应用的URL的对应关系。
实施例三
图6是本实施例的网络侧发起资源预留的流程图，步骤如下：
步骤S601，UE和网络建立PDN连接后，UE与应用层进行交互，为要发起的应用进行协商，在协商过程中UE提供所述应用对应的Application Id和实例标识或是应用层向UE提供Application Id和实例标识。若UE保存的对应关系中，Application Id只对应一个操作系统应用标识、或Application Id只对应一个第三方应用的服务器IP地址或IP三元组、或Application Id只对应第三方应用的URL，那么也可以不携带实例标识。
其中，实例标识用于标识具有相同Application Id的不同应用。实例标识为UE动态分配，确保在同一个Application Id下唯一，即Application Id和实例标识可以唯一标识一个UE将要发起的应用。
步骤S602，位于应用层的应用功能实体(AF，Application Function)向PCRF提供应用的业务信息，在业务信息中提供Application Id、实例标识和请求的QoS信息等。
步骤S603，PCRF为应用制定PCC规则，PCC规则中包含Application Id、实例标识、QoS参数(如QCI、ARP等)和计费参数。
其中，QoS参数包括上行方向的QoS参数。当PCRF为应用授权GBR的QCI时，在QoS参数中包括保障带宽GBR。
步骤S604，PCRF向PCEF发送策略和计费规则提供消息，携带所述PCC规则。
步骤S605，PCEF向PCRF返回策略和计费规则提供确认消息。
步骤S606，PCEF执行PCC规则，发起资源预留的流程。
其中，PCEF根据PCC规则执行承载绑定、创建或修改承载流程。PCEF所在的网关发送创建承载请求消息或更新承载请求消息，消息中携带Application Id、实例标识和QoS参数，该消息会通过一个或多个中间节点发送给UE，UE接收该消息后，向网络返回确认消息。此外，网络(即无线基站)还将Application Id和对应的无线逻辑信道信息发送给UE，UE获取发送该Application Id对应数据所采用的逻辑信道。这样UE通过PCEF发起的创建或修改流程获取应用对应的网络侧授权的QoS信息。网络可以只采用以上一种方式将网络侧授权的QoS信息提供给UE。
为了PCEF能够对应用的数据执行对应的QoS策略，要求PCEF具有应用检测功能，即PCEF能够检测出Application Id对应的应用。
在上述实施例中，是UE和应用层进行协商，并由AF向PCRF提供Application Id和请求的QoS信息；在其他实施例中，也可以由部署在网络中的应用检测功能(如PCEF、TDF)检测UE和应用层正在传输的数据，并向PCRF报告Application Id和实例标识(可选)。PCRF执行步骤S603进行 QoS授权。
通过上述流程，UE根据Application Id和实例标识(可选)确定将要发起应用的网络授权的QoS信息，特别是上行方向的QoS信息。
此后，当UE需要向网络侧发送该应用的数据时，UE根据网络侧下发的QoS信息进行处理(如通过上述创建或更新的承载向网络发送上行数据或UE采用Application Id对应的无线逻辑信道发送上行数据或根据QoS参数执行对应的调度算法)。此外，UE还可以校验网络发送的下行数据是否在正确的承载上。
实施例四
图7是本实施例的网络侧发起资源预留的流程图，本实施例网络侧发起资源预留的流程步骤如下：
步骤S701，UE和网络建立PDN连接后，UE与应用层交互，为要发起的应用进行协商，在协商过程中UE提供所述应用对应的Application Id和实例标识。若UE保存的对应关系中，Application Id只对应一个操作系统应用标识、或Application Id只对应一个第三方应用的服务器IP地址或IP三元组、或Application Id只对应一个第三方应用的URL，那么也可以不携带实例标识。
其中，实例标识用于标识具有相同Application Id的不同应用。实例标识为UE动态分配，确保在同一个Application Id下唯一，即Application Id和实例标识可以唯一标识一个UE将要发起的应用。
步骤S702，位于应用层的AF向PCRF提供应用的业务信息，在业务信息中提供Application Id、实例标识和请求的QoS信息等。
步骤S703，PCRF为应用制定PCC规则，PCC规则中包含Application Id、QoS参数(如QCI、ARP)和计费参数。PCRF进一步根据PCC规则制定QoS规则，QoS规则中包含Application Id、实例标识、QoS参数。其中，QoS参数包括上行方向的QoS参数。
步骤S704，PCRF向PCEF发送策略和计费规则提供消息，携带PCC规则。
步骤S705，PCEF向PCRF返回策略和计费规则提供确认消息。
步骤S706，PCRF向BBERF发送QoS规则提供消息，携带所述QoS规则。
步骤S707，BBERF向PCRF返回QoS规则提供确认消息。
步骤S708，BBERF执行QoS规则，发起资源预留的流程。
其中，BBERF根据QoS规则执行承载绑定、创建或修改承载流程。BBERF所在的网关或基站发送创建承载请求消息或更新承载请求消息，消息中携带Application Id、实例标识和QoS参数，该消息会通过一个或多个中间节点发送给UE，UE接收该消息后，向网络返回确认消息。此外，网络(即无线基站)还将Application Id和对应的无线逻辑信道信息发送给UE，UE获取发送该Application Id对应数据所采用的逻辑信道。这样UE通过BBERF发起的创建或修改流程获取应用对应的网络侧授权的QoS信息。网络可以只采用以上一种方式将网络侧授权的QoS信息提供给UE。为了PCEF能够对应用的数据执行对应的QoS策略，要求PCEF具有应用检测功能，即PCEF能够检测出Application Id对应的应用。若BBERF要执行QoS规则，则也需要BBERF具有执行识别应用的能力，譬如BBERF具有应用检测的功能或是PCEF执行应用检测后，在应用的数据包上标记与Application Id相关的标识。
在上述实施例中，是UE和应用层进行协商，并由AF向PCRF提供Application Id和请求的QoS信息；在其他实施例中，也可以由部署在网络中的应用检测功能(如PCEF、TDF)检测UE和应用层正在传输的数据，并向PCRF报告Application Id和实例标识(可选)。PCRF执行步骤S703进行QoS授权。
通过上述流程，UE根据Application Id和实例标识(可选)确定将要发起应用的网络授权的QoS信息，特别是上行方向的QoS信息。
此后，当UE需要向网络侧发送应用的数据时，UE根据网络侧下发的QoS信息进行处理(如通过上述创建或更新的承载向网络侧发送上行数据或UE采用Application Id对应的无线逻辑信道发送上行数据或根据QoS参数执行对应的调度算法)。此外，UE还可以校验网络发送的下行数据是否在正确的承载上。
实施例五
图8是本实施例的UE发起资源预留的流程图，本实施例的UE发起资源预留的流程步骤如下：
步骤S801，UE和网络建立PDN连接后，UE决定为准备开始的应用或是正在进行的应用请求特定的QoS保障，UE根据Application Id和操作系统应用标识的对应关系、或Application Id和第三方应用的服务器IP地址或IP三元组的对应关系、或Application Id和第三方应用的URL的对应关系，确定应用对应的Application Id并分配实例标识。UE向网络侧发送资源预留请求消息，消息中携带Application Id、实例标识和QoS请求参数，该消息会经过一个或多个中间节点发送给PCEF所在的网关。若UE保存的对应关系中，Application Id只对应一个操作系统应用标识、或Application Id只对应一个第三方应用的服务器IP地址或IP三元组、或Application Id只对应第三方应用的URL，那么也可以不携带实例标识。在示例性实施方式中，在UE发送资源预留请求之前，UE首先会检查应用对应的Application Id是否已经存在一个对应的承载(即Application Id是否有对应的网络侧授权的QoS信息)，若没有，则UE执行步骤S801；若有，则UE进一步检查承载是否为GBR承载(即网络侧授权的QoS信息中是否有GBR参数)，若是，则UE执行步骤S801；否则，本流程结束，在需要发送所述应用的上行数据时，UE直接在所述Application Id对应的承载上发送上行数据，也就是说，UE直接根据所述Application Id对应的QoS信息对上行数据进行处理。
步骤S802，PCEF所在网关接收所述资源预留请求消息，并向PCRF发送策略和计费规则请求消息，该策略和计费规则请求消息中携带Application Id、实例标识和QoS请求参数；
步骤S803，PCRF接收所述策略和计费规则请求消息并进行策略决策。PCRF根据来自PCEF的策略和计费规则请求消息为应用制定PCC规则，PCC规则中包含Application Id、实例标识、QoS参数(如QCI、ARP)和计费参数。
步骤S804，PCRF向PCEF发送策略和计费规则请求确认消息，携带所述PCC规则。
步骤S805，PCEF执行PCC规则，发起资源预留的流程。
其中，PCEF根据PCC规则执行承载绑定、创建或更新承载的流程。PCEF所在的网关发送创建承载请求消息或更新承载请求消息，消息中携带Application Id和QoS参数，该消息会通过一个或多个中间节点发送给UE，UE接收该消息并向网络侧返回确认消息。此外，网络(即无线基站)还将Application Id和对应的无线逻辑信道信息发送给UE，UE获取发送该Application Id对应数据所采用的逻辑信道。网络可以只采用以上一种方式将网络侧授权的QoS信息提供给UE。如此，UE通过PCEF发起的承载创建或承载修改流程获取应用对应的网络侧授权的QoS信息。
为了PCEF能够对应用的数据执行对应的QoS策略，要求PCEF具有应用检测功能，即PCEF能够检测出Application Id对应的应用。
通过上述流程，UE根据Application Id和实例标识(可选)确定将要发起应用的网络授权的QoS信息，特别是上行方向的QoS信息。
此后，当UE需要向网络侧发送用Application Id标识的应用的数据时，UE通过上述创建或修改的承载向网络侧发送上行数据，或UE采用Application Id对应的无线逻辑信道向网络发送上行数据，或是根据QoS参数执行对应的调度算法。此外，UE还可以校验网络发送的下行数据是否在正确的承载上。
实施例六
图9是本实施例的UE发起资源预留的流程图，本实施例的UE发起资源预留的流程步骤如下：
步骤S901，UE和网络建立PDN连接后，UE决定为准备开始的应用或是正在进行的应用请求特定的QoS保障，UE根据Application Id和操作系统应用标识的对应关系、或Application Id和第三方应用的服务器IP地址或IP三元组的对应关系、或Application Id和第三方应用的URL的对应关系，确定应用对应的Application Id并分配实例标识。UE向网络侧发送资源预留请求消息，消息中携带Application Id和QoS请求参数，该消息会经过一个或多个中间节点发送给BBERF所在的网关或基站。若UE保存的对应关系中，Application Id只对应一个操作系统应用标识、或Application Id只对应一个第 三方应用的服务器IP地址或IP三元组、或Application Id只对应第三方应用的URL，那么也可以不携带实例标识。
在示例性实施方式中，在UE发送资源预留请求之前，UE首先会检查应用对应的Application Id是否已经存在一个对应的承载(即Application Id是否已经存在授权的QoS信息)，若没有，则UE执行步骤S901；若有，则UE进一步检查上述承载是否为GBR承载(即授权的QoS信息中是否包含GBR参数)，若是，则UE执行步骤S901；否则，本流程结束，在需要发送所述应用的上行数据时，UE直接在所述Application Id对应的承载或对应的无线逻辑信道上发送上行数据，也就是说，UE直接根据所述Application Id对应的QoS信息对上行数据进行处理。
步骤S902，BBERF所在网关或基站接收所述资源预留请求消息，之后，BBERF向PCRF发送QoS规则请求消息，QoS规则请求消息中携带Application Id和QoS请求参数；
步骤S903，PCRF接收所述QoS规则请求消息并进行策略决策。
其中，PCRF根据来自BBERF的请求为应用制定PCC规则，PCC规则中包含Application Id、QoS参数(如QCI、ARP)和计费参数。进一步地，PCRF根据PCC规则制定QoS规则，所述QoS规则包含Application Id和QoS参数。
步骤S904，PCRF向BBERF发送策略和计费规则提供QoS规则请求确认消息，携带所述QoS规则。
步骤S905，PCRF向PCEF发送策略和计费规则提供消息，携带所述PCC规则。
步骤S906，PCEF返回策略和计费规则提供确认消息。
步骤S907，BBERF执行QoS规则，发起资源预留的流程。
其中，BBERF根据QoS规则执行承载绑定、创建或更新承载的流程。BBERF所在的网关和基站发送创建承载请求消息或更新承载请求消息，消息中携带Application Id和QoS参数，该消息会通过一个或多个中间节点发送给UE，UE接收该消息后，向网络返回确认消息。此外，网络(即无线基站) 还将Application Id和对应的无线逻辑信道信息发送给UE，UE获取发送该Application Id对应数据所采用的逻辑信道。网络可以只采用以上一种方式将网络侧授权的QoS信息提供给UE。如此，UE通过BBERF发起的承载创建或修改流程获取应用对应的网络侧授权的QoS信息。
通过上述流程，UE根据Application Id和实例标识确定应用的网络授权的QoS信息，特别是上行方向的QoS信息。此后，当UE需要向网络发送用Application Id标识的应用的数据时，UE通过上述创建或修改的承载向网络发送上行数据，或UE采用Application Id对应的无线逻辑信道向网络发送上行数据。此外，UE还可以校验网络发送的下行数据是否在正确的承载上。
为了PCEF能够对应用的数据执行对应的QoS策略，要求PCEF具有应用检测功能，即PCEF能够检测出Application Id对应的应用。若BBERF要执行QoS规则，则也需要BBERF具有执行识别应用的能力，譬如BBERF具有应用检测的功能或是PCEF执行应用检测后，在应用的数据包上标记对Application Id相关的标记。
以上实施例中，UE和网络侧通过承载创建或修改流程为应用预留了资源通道。在其他实施例中，也可以通过其他方式为应用预留相应的资源通道或协商相应的无线逻辑信道。譬如，PCRF分别向UE和BBERF(此时BBERF可以位于基站)发送携带应用标识(即Application Id)和QoS参数的规则(PCC规则或者QoS规则)，UE和BBERF在本地为应用预留资源通道或PCRF分别向UE和BBERF发送携带Application Id和无线逻辑信道的对应关系，UE和BBERF在本地保存，而不需要UE和BBERF之间进行交互。
实施例七
图10是本实施例的网络侧发起资源预留的流程图，本实施例的网络侧发起资源预留的流程步骤如下：
步骤S1001，UE和网络建立PDU会话后，UE与应用的应用层交互，为要发起的应用进行协商，在协商过程中UE提供该应用对应的Application Id和实例标识或是应用层向UE提供Application Id和实例标识。若UE保存的对应关系中，Application Id只对应一个操作系统应用标识、或一个第三方应用的服务器IP地址或IP三元组、或第三方应用的URL，那么也可以不携带 实例标识。
其中，实例标识用于标识具有相同Application Id下的不同应用。实例标识为UE或应用服务器动态分配，确保在同一个Application Id下唯一，即Application Id和实例标识可以唯一标识一个UE将要发起的应用。
步骤S1002，AF向核心网CP功能实体提供业务信息，在业务信息中提供Application Id、实例标识和请求的QoS信息等。
步骤S1003，CP功能实体执行策略决策，即为应用制定QoS策略，所述QoS策略中包含Application Id、QoS参数(如QCI、ARP)和计费参数。其中，QoS参数中还可能包含GBR参数。
步骤S1004，CP功能实体向核心网UP功能实体发送所述QoS策略，该QoS策略中提供Application Id、QoS参数和计费参数。
步骤S1005，UP功能实体返回确认消息。
步骤S1006，CP功能实体向接入网(AN)发送所述QoS策略，所述QoS策略中提供Application Id和QoS参数。
其中，在发送给AN的QoS策略中可选择性地携带实例标识。
步骤S1007，AN返回确认消息。
步骤S1008，在示例性实施方式中，CP功能实体向UE直接提供QoS策略，所述QoS策略中包括Application Id、实例标识和QoS参数；
步骤S1009，UE向CP功能实体返回确认消息。
步骤S1010，UE和AN进行相关的空口操作。AN向UE提供Application Id和对应的无线逻辑信道信息。
其中，UE和AN执行相关的参数配置。
若步骤S1006中携带的QoS参数中包含GBR参数，则AN将进行相应的资源预留。即提供保障带宽的无线逻辑信道。
若步骤S1008和步骤S1009不执行，那么AN将向UE提供Application Id、QoS参数和实例标识。
为了CP功能实体能够对应用的数据执行对应的QoS策略，要求CP功 能实体具有应用检测功能，即CP功能实体能够检测出Application Id对应的应用。同样，AN要执行QoS策略，则也需要AN具有执行识别应用的能力，譬如AN具有应用检测的功能或是CP功能实体执行应用检测后，在应用的数据包上标记对Application Id相关的标记。
在上述实施例中，是UE和应用层进行协商，并由AF向PCRF提供Application Id和请求的QoS信息；在其他实施例中，也可以由部署在网络中的应用检测功能(如PCEF、TDF)检测UE和应用层正在传输的数据，并向CP功能实体报告Application Id和实例标识(可选)。CP功能实体执行步骤S1003进行QoS授权。
通过上述流程，UE根据Application Id和实例标识(可选)确定应用的网络授权的QoS信息，特别是上行方向的QoS信息。
此后，当UE需要向网络发送该应用的数据时，UE根据网络侧下发的QoS信息进行处理(如通过上述预留的资源通道发送数据、或是根据QoS参数执行对应的调度算法、或在对应的无线逻辑信道上发送数据)。此外，UE还可以校验网络发送的下行数据是否执行了争取的QoS。
实施例八
图11是本实施例的网络侧发起资源预留的流程图，本实施例的网络侧发起资源预留的流程步骤如下：
步骤S1101，UE和网络建立PDU会话后，UE决定为准备开始的新应用或是正在进行的应用请求特定的QoS保障，UE根据Application Id和操作系统应用标识的对应关系、或Application Id和第三方应用的服务器IP地址或IP三元组的对应关系、或Application Id和第三方应用的URL的对应关系，确定应用对应的Application Id并分配实例标识。UE向网络侧发送QoS策略请求消息，消息中携带Application Id、实例标识和QoS请求参数(如QCI、GBR)，该消息可能会经过一个或多个中间节点发送给CP功能实体。若UE保存的对应关系中，Application Id只对应一个操作系统应用标识、或一个第三方应用的服务器IP地址或IP三元组、或第三方应用的URL，那么也可以不携带实例标识。
在UE发送QoS策略请求消息之前，UE首先会检查应用对应的 Application Id是否已经有网络授权的QoS信息，若没有，则UE执行步骤S1101；若有，则UE进一步检查QoS信息是否包含GBR参数，若包含，则UE执行步骤S1101；否则，本流程结束，在需要发送所述应用的上行数据时，UE直接在所述Application Id对应的承载或对应的无线逻辑信道上发送上行数据，也就是说，UE直接根据所述Application Id对应的QoS信息对上行数据进行处理。
步骤S1102，CP功能实体进行策略决策，为应用制定QoS策略，该QoS策略中包含Application Id、QoS参数(如QCI、ARP)和计费参数。
其中，QoS参数还可能包含GBR参数。
步骤S1103，CP功能实体向UE返回QoS策略请求确认消息，消息中携带授权的QoS策略，该QoS策略包括Application Id、实例标识和QoS参数。
步骤S1104，CP功能实体向核心网UP功能实体发送所述QoS策略，该QoS策略中提供Application Id、QoS参数和计费参数。
步骤S1105，UP功能实体返回确认消息。
步骤S1106，CP功能实体向AN发送所述QoS策略，所述QoS策略中提供Application Id和QoS参数。
在示例性实施方式中，该QoS策略还可以包含实例标识。
步骤S1107，AN返回确认消息。
步骤S1108，UE和AN进行相关的空口操作。即AN向UE发送Application Id和对应的无线逻辑信道信息。
其中，UE和AN执行相关的参数配置。若步骤S1106中携带的QoS参数中包含GBR参数，则AN将进行相应的资源预留。若步骤S1103不执行，那么AN将向UE提供Application Id、QoS参数和实例标识。
通过上述流程，UE根据Application Id和实例标识确定将要发起应用的网络授权的QoS信息，特别是上行方向的QoS参数或上行方向的无线逻辑信道信息。
为了CP功能实体能够对应用的数据执行对应的QoS策略，要求CP功能实体具有应用检测功能，即CP功能实体能够检测出Application Id对应的 应用。同样，AN要执行QoS策略，则也需要AN具有执行识别应用的能力，譬如AN具有应用检测的功能或是CP功能实体执行应用检测后，在应用的数据包上标记对Application Id相关的标记。
此后，当UE需要向网络侧发送该应用的数据时，UE根据网络侧下发的QoS参数进行处理(如通过上述预留的资源通道发送数据、或是根据QoS参数执行对应的调度算法)。此外，UE还可以校验网络发送的下行数据是否执行了争取的QoS。
如图12所示，本发明实施例还提供了一种基于应用的策略和计费控制装置，该装置部署在终端侧，比如UE上，包括：第一接收模块1201，配置为接收网络侧为应用标识授权的QoS信息，其中，所述应用标识为所述网络侧预下发的Application Id，用于标识应用；处理模块1202，配置为根据所述QoS信息对所述Application Id对应的应用的上行数据进行处理。其中，所述QoS信息包括以下至少之一：QoS参数、无线逻辑信道信息。
在示例性实施方式中，所述装置还可以包括：分配模块1203，配置为给所述应用分配实例标识，其中，所述实例标识用于标识具有相同Application Id的不同应用。
在示例性实施方式中，所述装置还可以包括：第一发送模块1204，配置为向所述网络侧发送QoS信息请求消息，其中，所述QoS信息请求消息携带所述应用标识和请求的QoS信息。这里，所述第一发送模块1204，还可以配置为在向所述网络侧发送QoS信息请求消息时，还在所述QoS信息请求消息中携带所述实例标识。
在示例性实施方式中，所述装置还可以包括：第一发送模块1204，配置为与所述应用的应用层协商，将所述应用标识和请求的QoS信息提供给所述应用层，以使得所述应用层将所述应用标识和请求的QoS信息提供给所述网络侧。这里，所述第一发送模块1204，还可以配置为在向所述应用的应用层提供所述应用标识和请求的QoS信息时，还向所述应用层提供所述应用的实例标识。
在示例性实施方式中，所述装置还可以包括：确定模块1206和存储模块1205；存储模块1205，可以配置为保存Application Id和操作系统应用标识 的对应关系、或Application Id和所述应用的服务器IP地址或IP三元组的对应关系、或Application Id和所述应用的URL的对应关系；确定模块1206，可以配置为根据所述存储模块1205保存的所述对应关系，确定所述应用的Application Id。
在示例性实施方式中，所述第一接收模块1201，还可以配置为获取所述Application Id和操作系统应用标识的对应关系、或Application Id和所述应用的服务器IP地址或IP三元组的对应关系、或Application Id和所述应用的URL的对应关系并保存到所述存储模块1205中，其中，所述对应关系为所述网络侧主动下发的、或者在所述装置的第一发送模块1204向所述网络侧主动请求之后所述网络侧下发的。
其中，所述第一接收模块1201，还可以配置为：在分组数据网(PDN)连接或分组数据单元(PDU)会话建立的过程中获取Application Id和操作系统应用标识的对应关系、或Application Id和所述应用的服务器IP地址或IP三元组的对应关系、或Application Id和所述应用的URL的对应关系，并将所述对应关系与所述PDN连接或所述PDU会话关联；或者，在PDN连接或PDU会话建立后获取所述Application Id和操作系统应用标识的对应关系、或Application Id和所述应用的服务器IP地址或IP三元组的对应关系、或Application Id和所述应用的URL的对应关系，并将所述对应关系与所述PDN连接或所述PDU会话关联。
在示例性实施方式中，所述第一接收模块1201，可以配置为执行以下至少一项：接收所述网络侧发送的消息，其中所述消息携带所述Application Id和所述网络侧授权的QoS参数，所述QoS参数包含上行方向的QoS参数；接收所述网络侧发送的消息，其中，所述消息携带所述Application Id和无线逻辑信道信息，所述无线逻辑信道信息包含上行方向的无线逻辑信道信息。这里，所述消息还可以携带有所述应用的实例标识，所述实例标识用于标识具有相同Application Id的不同应用。
在示例性实施方式中，所述装置还可以包括：判断模块1207，配置为判断所述应用对应的Application Id是否已存在所述网络侧授权的QoS信息，若不存在所述QoS信息，则通知所述第一发送模块1204发送所述QoS信息 请求消息；若存在所述QoS信息，则判断所述QoS信息中是否存在保证比特率(GBR)参数，若存在所述GBR参数，则通知所述第一发送模块1204发送所述QoS信息请求消息；若不存在所述GBR参数，则通知所述处理模块1202根据所述Application Id对应的QoS信息对所述应用的上行数据进行处理。
其中，所述处理模块1202，可以配置为执行以下至少一项：根据所述QoS参数对所述应用的上行数据执行对应的调度算法；采用所述无线逻辑信道信息对应的无线逻辑信道发送上行数据。
如图13所示，本发明实施例还提供了另一种基于应用的策略和计费控制装置，该装置部署在网络侧实体上，包括：第二接收模块1302和第二发送模块1301；其中，第二接收模块1302，配置为接收UE提供的应用对应的应用标识，其中，所述应用标识为所述网络侧预下发的Application Id；第二发送模块1301，配置为向所述UE返回QoS信息，其中，所述QoS信息包括以下至少之一：网络侧为所述应用授权的QoS参数、无线逻辑信道信息。
在示例性实施方式中，所述第二接收模块1302，还可以配置为接收所述UE在提供所述应用标识的同时还提供的所述应用的实例标识，其中，所述实例标识用于标识具有相同Application Id的不同应用。
在示例性实施方式中，所述第二发送模块1301，还可以配置为执行以下至少一项：主动向所述UE发送Application Id和操作系统应用标识的对应关系、或所述Application Id和所述应用的服务器IP地址或IP三元组的对应关系、或所述Application Id和所述应用的URL的对应关系；在所述第二接收模块1302接收到所述UE的请求之后，发送所述Application Id和操作系统应用标识的对应关系、或所述Application Id和所述应用的服务器IP地址或IP三元组的对应关系、或所述Application Id和所述应用的URL的对应关系给所述UE。
其中，所述第二发送模块1301，可以配置为执行以下至少一项：向所述UE返回消息，其中，所述消息携带所述Application Id和所述网络侧授权的QoS参数，所述QoS参数包含上行方向的QoS参数；向所述UE返回消息，其中，所述消息携带所述Application Id和无线逻辑信道信息，所述无线逻辑 信道信息包含上行方向的无线逻辑信道信息。
在示例性实施方式中，所述第二接收模块1302，可以配置为接收所述UE向网络侧发送的QoS信息请求消息，其中，所述QoS信息请求消息携带所述应用的Application Id和请求的QoS参数；所述第二发送模块1301，可以配置为向所述UE返回携带所述Application Id和网络侧授权的QoS参数的消息，其中，所述QoS参数包含上行方向的QoS参数。这里，所述QoS信息请求消息还可以携带所述应用的实例标识；所述携带所述Application Id和网络侧授权的QoS参数的消息还可以包含所述应用的实例标识。
如图14所示，本发明实施例还提供了一种基于应用的策略和计费控制系统，该系统包括：UE和网络侧实体；所述UE包括如图12所示的装置，所述网络侧实体包括如图13所示的装置。
此外，本发明实施例还提供一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被处理器执行时实现上述的基于应用的策略和计费控制方法。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理单元的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些组件或所有组件可以被实施为由处理器，如数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通 信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。
虽然本申请所揭露的实施方式如上，但所述的内容仅为便于理解本申请而采用的实施方式，并非用以限定本申请。任何本申请所属领域内的技术人员，在不脱离本申请所揭露的精神和范围的前提下，可以在实施的形式及细节上进行任何的修改与变化，但本申请的专利保护范围，仍须以所附的权利要求书所界定的范围为准。
工业实用性
本申请实施例提供一种基于应用的策略和计费控制方法及装置、系统，使得网络侧能够及时通知UE上行数据的QoS信息，解决了无法有效通知UE上行承载的问题。

Claims (32)

  1. 一种基于应用的策略和计费控制方法，包括：
    用户设备UE接收网络侧为应用标识授权的服务质量QoS信息，所述应用标识为所述网络侧预下发的运营商定义应用标识Application Id；
    所述UE根据所述QoS信息对所述Application Id对应的应用的上行数据进行处理；
    所述QoS信息包括以下至少之一：QoS参数、无线逻辑信道信息。
  2. 根据权利要求1所述的方法，所述UE接收网络侧为应用标识授权的QoS信息之前，所述方法还包括：所述UE向所述网络侧发送QoS信息请求消息，所述QoS信息请求消息携带所述应用标识和请求的QoS信息。
  3. 根据权利要求2所述的方法，所述UE向所述网络侧发送QoS信息请求消息时，所述方法还包括：所述UE为所述应用分配实例标识，并在所述QoS信息请求消息中携带所述实例标识，所述实例标识用于标识具有相同Application Id的不同应用。
  4. 根据权利要求1所述的方法，所述UE接收网络侧为应用标识授权的QoS信息之前，所述方法还包括：所述UE与所述应用的应用层协商，将所述应用标识和请求的QoS信息提供给所述应用层，再由所述应用层向所述网络侧提供所述应用标识和请求的QoS信息。
  5. 根据权利要求4所述的方法，所述方法还包括：所述UE为所述应用分配实例标识，所述实例标识用于标识具有相同Application Id的不同应用；
    所述UE接收网络侧为应用标识授权的QoS信息之前，所述方法还包括：所述UE与所述应用的应用层协商，将应用的应用标识、实例标识和请求的QoS信息提供给所述应用层，再由所述应用层向所述网络侧提供所述应用标识、实例标识和请求的QoS信息。
  6. 根据权利要求1所述的方法，所述UE根据所述QoS信息对所述Application Id对应的应用的上行数据进行处理之前，所述方法还包括：
    所述UE根据本地保存的Application Id和操作系统应用标识的对应关系、 或Application Id和所述应用的服务器互联网协议IP地址或IP三元组的对应关系、或Application Id和所述应用的统一资源定位符URL的对应关系，确定所述应用的Application Id。
  7. 根据权利要求6所述的方法，所述方法还包括：所述UE从所述网络侧获取所述Application Id和操作系统应用标识的对应关系、或所述Application Id和所述应用的服务器IP地址或IP三元组的对应关系、或所述Application Id和所述应用的URL的对应关系并保存。
  8. 根据权利要求7所述的方法，其中，所述UE从所述网络侧获取所述Application Id和操作系统应用标识的对应关系、或所述Application Id和所述应用的服务器IP地址或IP三元组的对应关系、或所述Application Id和所述应用的URL的对应关系，包括：
    所述UE向所述网络侧请求并接收所述Application Id和操作系统应用标识的对应关系、或所述Application Id和所述应用的服务器IP地址或IP三元组的对应关系、或所述Application Id和所述应用的URL的对应关系并保存；或者，
    所述UE接收所述网络侧主动下发的所述Application Id和操作系统应用标识的对应关系、或所述Application Id和所述应用的服务器IP地址或IP三元组的对应关系、或所述Application Id和所述应用的URL的对应关系并保存。
  9. 根据权利要求7或8所述的方法，其中，所述UE在分组数据网络PDN连接或分组数据单元PDU会话建立的过程中获取所述Application Id和操作系统应用标识的对应关系、或所述Application Id和所述应用的服务器IP地址或IP三元组的对应关系、或所述Application Id和所述应用的URL的对应关系，并将所述对应关系与所述PDN连接或所述PDU会话关联；
    或者，所述UE在PDN连接或PDU会话建立后获取所述Application Id和操作系统应用标识的对应关系、或所述Application Id和所述应用的服务器IP地址或IP三元组的对应关系、或所述Application Id和所述应用URL的对应关系，并将所述对应关系与所述PDN连接或所述PDU会话关联。
  10. 根据权利要求1至8任一项所述的方法，其中，所述UE接收网络 侧为应用标识授权的QoS信息，包括以下至少之一：
    所述UE接收所述网络侧发送的消息，所述消息携带所述Application Id和所述网络侧授权的QoS参数，所述QoS参数包含上行方向的QoS参数；
    所述UE接收所述网络侧发送的消息，所述消息携带所述Application Id和无线逻辑信道信息，所述无线逻辑信道信息包含上行方向的无线逻辑信道信息。
  11. 根据权利要求10所述的方法，其中，所述消息还携带有所述应用的实例标识，所述实例标识用于标识具有相同Application Id的不同应用。
  12. 根据权利要求10所述的方法，其中，所述UE根据所述QoS信息对所述Application Id对应的应用的上行数据进行处理，包括以下至少之一：
    所述UE根据所述QoS参数对所述应用的上行数据执行对应的调度算法；
    所述UE采用所述无线逻辑信道信息对应的无线逻辑信道发送上行数据。
  13. 根据权利要求2所述的方法，所述UE向所述网络侧发送QoS信息请求消息之前，所述方法还包括：
    所述UE判断所述应用对应的Application Id是否已存在所述网络侧授权的QoS信息，若不存在所述QoS信息，则所述UE发送所述QoS信息请求消息；若存在所述QoS信息，则所述UE判断所述QoS参数中是否存在保证比特率GBR参数，若存在所述GBR参数，则所述UE发送所述QoS信息请求消息；若不存在所述GBR参数，所述UE根据所述Application Id对应的QoS信息对所述应用的上行数据进行处理。
  14. 一种基于应用的策略和计费控制装置，包括：
    第一接收模块，配置为接收网络侧为应用标识授权的服务质量QoS信息，其中，所述应用标识为所述网络侧预下发的运营商定义应用标识Application Id；
    处理模块，配置为根据所述QoS信息对所述Application Id对应的应用的上行数据进行处理；
    其中，所述QoS信息包括以下至少之一：QoS参数、无线逻辑信道信息。
  15. 根据权利要求14所述的装置，所述装置还包括：第一发送模块，配置为向所述网络侧发送QoS信息请求消息，其中，所述QoS信息请求消息携带所述应用标识和请求的QoS信息。
  16. 根据权利要求15所述的装置，所述装置还包括：分配模块，配置为给所述应用分配实例标识，其中，所述实例标识用于标识具有相同Application Id的不同应用；
    所述第一发送模块，还配置为在向所述网络侧发送QoS信息请求消息时，还在所述QoS信息请求消息中携带所述实例标识。
  17. 根据权利要求14所述的装置，所述装置还包括：第一发送模块，配置为与所述应用的应用层协商，将所述应用标识和请求的QoS信息提供给所述应用层，以使得所述应用层将所述应用标识和请求的QoS信息提供给所述网络侧。
  18. 根据权利要求17所述的装置，所述装置还包括：分配模块，配置为给所述应用分配实例标识，其中，所述实例标识用于标识具有相同Application Id的不同应用；
    所述第一发送模块，还配置为在向所述应用的应用层提供所述应用标识和请求的QoS信息时，还向所述应用层提供所述应用的实例标识。
  19. 根据权利要求14所述的装置，所述装置还包括：确定模块和存储模块；
    所述存储模块，配置为保存Application Id和操作系统应用标识的对应关系、或Application Id和所述应用的服务器互联网协议IP地址或IP三元组的对应关系、或Application Id和所述应用的统一资源定位符URL的对应关系；
    所述确定模块，配置为根据所述存储模块保存的所述对应关系，确定所述应用的Application Id。
  20. 根据权利要求14所述的装置，其中，所述第一接收模块，还配置为获取所述Application Id和操作系统应用标识的对应关系、或Application Id和所述应用的服务器互联网协议IP地址或IP三元组的对应关系、或Application Id和所述应用的统一资源定位符URL的对应关系，并保存到存 储模块中，其中，所述对应关系为所述网络侧主动下发的、或者在所述装置的第一发送模块向所述网络侧主动请求之后所述网络侧下发的。
  21. 根据权利要求20所述的装置，其中，所述第一接收模块，还配置为：在分组数据网络PDN连接或分组数据单元PDU会话建立的过程中获取所述Application Id和操作系统应用标识的对应关系、或所述Application Id和所述应用的服务器IP地址或IP三元组的对应关系、或所述Application Id和所述应用的URL的对应关系，并将所述对应关系与所述PDN连接或所述PDU会话关联；
    或者，在PDN连接或PDU会话建立后获取所述Application Id和操作系统应用标识的对应关系、或所述Application Id和所述应用的服务器IP地址或IP三元组的对应关系、或所述Application Id和所述应用的URL的对应关系，并将所述对应关系与所述PDN连接或所述PDU会话关联。
  22. 根据权利要求14至21任一项所述的装置，其中，所述第一接收模块，配置为执行以下至少一项：接收所述网络侧发送的消息，其中，所述消息携带所述Application Id和所述网络侧授权的QoS参数，所述QoS参数包含上行方向的QoS参数；接收所述网络侧发送的消息，其中，所述消息携带所述Application Id和无线逻辑信道信息，所述无线逻辑信道信息包含上行方向的无线逻辑信道信息。
  23. 根据权利要求22所述的装置，其中，所述消息还携带有所述应用的实例标识，所述实例标识用于标识具有相同Application Id的不同应用。
  24. 根据权利要求15所述的装置，所述装置还包括：判断模块，配置为判断所述应用对应的Application Id是否已存在所述网络侧授权的QoS信息，若不存在所述QoS信息，则通知所述第一发送模块发送所述QoS信息请求消息；若存在所述QoS信息，则判断所述QoS信息中是否存在保证比特率GBR参数，若存在所述GBR参数，则通知所述第一发送模块发送所述QoS信息请求消息；若不存在所述GBR参数，则通知所述处理模块根据所述Application Id对应的QoS信息对所述应用的上行数据进行处理。
  25. 根据权利要求14所述的装置，其中，所述处理模块，配置为执行以下至少一项：根据所述QoS参数对所述应用的上行数据执行对应的调度算法； 采用所述无线逻辑信道信息对应的无线逻辑信道发送上行数据。
  26. 一种基于应用的策略和计费控制装置，包括：第二接收模块和第二发送模块；
    所述第二接收模块，配置为接收用户设备UE提供的应用对应的应用标识，其中，所述应用标识为所述网络侧预下发的运营商定义应用标识Application Id；
    所述第二发送模块，配置为向所述UE返回服务质量QoS信息，其中，所述QoS信息包括以下至少之一：网络侧为所述应用授权的QoS参数、无线逻辑信道信息。
  27. 根据权利要求26所述的装置，其中，所述第二接收模块，还配置为接收所述UE在提供所述应用标识的同时还提供的所述应用的实例标识，其中，所述实例标识用于标识具有相同Application Id的不同应用。
  28. 根据权利要求26所述的装置，其中，所述第二发送模块，还配置为执行以下至少一项：主动向所述UE发送Application Id和操作系统应用标识的对应关系、或所述Application Id和所述应用的服务器互联网协议IP地址或IP三元组的对应关系、或所述Application Id和所述应用的统一资源定位符URL的对应关系；在所述第二接收模块接收到所述UE的请求之后，向所述UE发送所述Application Id和操作系统应用标识的对应关系、或所述Application Id和所述应用的服务器IP地址或IP三元组的对应关系、或所述Application Id和所述应用的URL的对应关系。
  29. 根据权利要求26所述的装置，其中，所述第二发送模块，配置为执行以下至少一项：向所述UE返回消息，其中，所述消息携带所述Application Id和所述网络侧授权的QoS参数，所述QoS参数包含上行方向的QoS参数；向所述UE返回消息，其中，所述消息携带所述Application Id和无线逻辑信道信息，所述无线逻辑信道信息包含上行方向的无线逻辑信道信息。
  30. 根据权利要求26所述的装置，其中，所述第二接收模块，配置为接收所述UE向网络侧发送的QoS信息请求消息，其中，所述QoS信息请求消息携带所述应用的Application Id和请求的QoS参数；
    所述第二发送模块，配置为向所述UE返回携带所述Application Id和网络侧授权的QoS参数的消息，其中，所述QoS参数包含上行方向的QoS参数。
  31. 根据权利要求30所述的装置，其中，所述QoS信息请求消息还携带所述应用的实例标识；
    所述携带所述Application Id和网络侧授权的QoS参数的消息还包含所述应用的实例标识；
    所述实例标识用于标识具有相同Application Id的不同应用。
  32. 一种基于应用的策略和计费控制系统，包括：用户设备UE和网络侧实体；所述UE包括如权利要求14至25任一项所述的装置，所述网络侧实体包括如权利要求26至31任一项所述的装置。
PCT/CN2017/074786 2016-04-05 2017-02-24 一种基于应用的策略和计费控制方法、装置及系统 WO2017173897A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201610207567 2016-04-05
CN201610207567.5 2016-04-05
CN201610319489.8A CN107294737A (zh) 2016-04-05 2016-05-12 一种基于应用的策略和计费控制方法及装置、系统
CN201610319489.8 2016-05-12

Publications (1)

Publication Number Publication Date
WO2017173897A1 true WO2017173897A1 (zh) 2017-10-12

Family

ID=60000203

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/074786 WO2017173897A1 (zh) 2016-04-05 2017-02-24 一种基于应用的策略和计费控制方法、装置及系统

Country Status (1)

Country Link
WO (1) WO2017173897A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110580256A (zh) * 2018-05-22 2019-12-17 华为技术有限公司 一种识别应用标识的方法、设备及系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101009631A (zh) * 2006-01-24 2007-08-01 华为技术有限公司 一种QoS控制方法和系统
CN101692727A (zh) * 2009-09-16 2010-04-07 中兴通讯股份有限公司 一种策略计费控制的方法和分组数据网络网关
CN103404102A (zh) * 2012-12-31 2013-11-20 华为技术有限公司 一种承载创建方法、装置和系统
CN104010332A (zh) * 2013-02-21 2014-08-27 中兴通讯股份有限公司 承载绑定方法及系统
WO2015085685A1 (zh) * 2013-12-10 2015-06-18 华为技术有限公司 上行业务数据流的传输装置和方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101009631A (zh) * 2006-01-24 2007-08-01 华为技术有限公司 一种QoS控制方法和系统
CN101692727A (zh) * 2009-09-16 2010-04-07 中兴通讯股份有限公司 一种策略计费控制的方法和分组数据网络网关
CN103404102A (zh) * 2012-12-31 2013-11-20 华为技术有限公司 一种承载创建方法、装置和系统
CN104010332A (zh) * 2013-02-21 2014-08-27 中兴通讯股份有限公司 承载绑定方法及系统
WO2015085685A1 (zh) * 2013-12-10 2015-06-18 华为技术有限公司 上行业务数据流的传输装置和方法

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110580256A (zh) * 2018-05-22 2019-12-17 华为技术有限公司 一种识别应用标识的方法、设备及系统
CN110580256B (zh) * 2018-05-22 2022-06-10 华为技术有限公司 一种识别应用标识的方法、设备及系统
US11438425B2 (en) 2018-05-22 2022-09-06 Huawei Technologies Co., Ltd. Method, device and system for identifying application identifier

Similar Documents

Publication Publication Date Title
EP2081332B1 (en) A method for sharing network resources, and a device and system thereof
CN107646197B (zh) 用于3gpp网络中的小数据使用使能的设备和方法
EP2093931B1 (en) Method, system and policy control and charging rules function for processing service data streams
JP5468180B2 (ja) サービス要求に基づいてｐｃｃルールを生成するためのシステムおよび方法
US9055411B2 (en) Method and system for selecting PCEF and PCRF in a wireless communication system
CN113475045A (zh) 基于控制面的时间敏感网络配置
EP2543163B1 (en) Methods, systems, and computer readable media for enhanced service detection and policy rule determination
US20120102174A1 (en) Policy And Charging Control Method And System For Multi-PDN Connections Of Single APN
EP2566197A1 (en) Policy application method for machine type communication and policy and charging enforcement function
EP2472918B1 (en) Method, apparatus and system for transmitting a bearer control mode in roaming scenarios
CN107294737A (zh) 一种基于应用的策略和计费控制方法及装置、系统
EP3007400B1 (en) Network resource prioritization for mobile terminating services
WO2014023327A1 (en) Dynamic content filtering of data traffic in a communication network
US10516783B2 (en) Method and device for processing PCC rule
US20150163813A1 (en) Bandwidth control method, device, and system
WO2017173941A9 (zh) 服务质量QoS策略的处理方法、装置及系统
EP2589203A1 (en) Diameter session audits
JP2015511432A (ja) 移動パケットコアネットワークにおけるセッション終了
WO2017173897A1 (zh) 一种基于应用的策略和计费控制方法、装置及系统
KR102315347B1 (ko) HSS(Home Subscriber Server) 및 HSS의 제어 방법
WO2013117221A1 (en) Methods, apparatuses, a system, and a related computer program product for defining, provisioning and activating packet filters
CN108781475B (zh) 一种事件上报的方法及装置
CN105376071A (zh) 实现后向QoS保障与内容计费的方法、系统与PCRF
EP2769581B1 (en) Roaming session termination triggered by roaming agreement/partner deletion
WO2017084603A1 (zh) Pcc规则的处理方法及装置

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

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

Ref document number: 17778562

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 17778562

Country of ref document: EP

Kind code of ref document: A1