WO2015055063A1 - Procédé de contrôle d'accès à une application et appareil d'entité de fonction d'application - Google Patents

Procédé de contrôle d'accès à une application et appareil d'entité de fonction d'application Download PDF

Info

Publication number
WO2015055063A1
WO2015055063A1 PCT/CN2014/086450 CN2014086450W WO2015055063A1 WO 2015055063 A1 WO2015055063 A1 WO 2015055063A1 CN 2014086450 W CN2014086450 W CN 2014086450W WO 2015055063 A1 WO2015055063 A1 WO 2015055063A1
Authority
WO
WIPO (PCT)
Prior art keywords
aac
pcrf
network
information
subscription
Prior art date
Application number
PCT/CN2014/086450
Other languages
English (en)
Chinese (zh)
Inventor
吴锦花
周晓云
刘小华
吴近峰
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2015055063A1 publication Critical patent/WO2015055063A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80—Rating or billing plans; Tariff determination aspects
    • H04M15/8038—Roaming or handoff
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0894—Policy-based network configuration management

Definitions

  • the present invention relates to the field of communications, and in particular to an application access control method and an application function entity device.
  • PCC Policy and Charging Control
  • PCRF Policy and Charging Rules Function
  • Policy and Charging Enforcement Function Policy and Charging Enforcement Function
  • PCEF Policy and Charging Enforcement Function
  • P-GW Packet Data Network Gateway
  • PDN GW Packet Data Network Gateway
  • BBERF Bearer Binding and Event Report Function
  • S-GW Serving Gateway
  • Application Function, AF Application Function
  • IP service network protocol
  • SPR Subscription Profile Repository
  • HSS Home Subscriber Server
  • the PCC implements policy charging control for an IP Connectivity Access Network (IP-CAN) session established by the UE to access a Packet Data Network (PDN) through the above functional entity.
  • IP-CAN IP Connectivity Access Network
  • PDN Packet Data Network
  • FIG. 1 is a schematic diagram of a PCC non-roaming architecture according to the related art.
  • the PCRF is mainly responsible for formulating policy and charging rules, and the PCC policy and charging rules are sent to the PCEF through the Gx interface, and the PCEF is installed. Execute a PCC policy, report related events, and exchange billing information with the billing system.
  • the AF provides the service information to the PCRF through the Rx interface, and the SPR stores the service information subscribed by the user.
  • the PCRF can query the SPR for the service information subscribed by the user through the Sp interface.
  • the PCEF sends the online charging information to the online charging system (OSC) through the Gy interface to calculate the online charging statistics, and sends the offline charging information to the offline charging system through the Gz interface (Offline Charging System, Referred to as OFCS).
  • PCEF also enhances Application Detection Control (ADC).
  • the traffic detection function (Traffic Detection Function, TDF for short) is connected to the PCRF through the Sd interface.
  • the TDF can perform application detection and policy execution according to the application detection control rules delivered by the pre-configuration or PCRF.
  • the network After the UE establishes an IP-CAN session to a certain PDN, the network provides a default subscription resource according to the corresponding authorized QoS.
  • the AF will provide new QoS information to the PCRF, and the PCRF initiates an IP-CAN session modification procedure to provide resource authorization for the service.
  • the service information required for the authorization of the service resource cannot be provided to the PCRF.
  • An improved method is to deploy a network element for performing application access control on a third-party reference between a third-party data application provider and an operation network PCRF, and FIG.
  • FIG. 2 is a PCC non-roaming according to the related art.
  • the Rx interface between the application access control network element and the third party can communicate using, for example, a SOAP or restful protocol, and the Rx interface between the PCRFs can communicate based on the Diameter or xml protocol.
  • the application access control network element application access control, AAC for short
  • the protocol converter (PC) function can implement protocol conversion between the third-party data application provider and the PCRF, and complete the application provider. Delivery of information, business information, QoS requirements, and billing information.
  • the application access control function is deployed in the user home network in the above enhanced architecture.
  • the service available for the user in the network not only belongs to the third party service subscribed by the network, but also includes the visited place.
  • the problem of implementing the service and charging and policy control of the service in the roaming scenario needs to be solved. For example, a third-party service contracting requires the operator to charge a third-party charging requirement. If the contracted carrier network is not the user's home network or the visited network, the existing PCC roaming architecture cannot support the service to meet such requirements.
  • a third-party service contract is represented by a specific operator for its secure access to all mobile operator networks.
  • the agent cannot directly access the AAC from the home location by distinguishing the requirements of the resource authorization and charging agent according to the own user level. .
  • how to support the development of third-party data application services of users in such roaming scenarios and meet the requirements of the above-mentioned services and operators in the roaming scenario has become a problem to be solved.
  • the present invention provides an application access control method and an application function entity device to solve at least the problem of related technologies that cannot implement charging and policy control of a certain type of service.
  • an application access control method including: an application function entity AF selects an access application access control network element AAC according to a priority principle; and the AF sends the PCR to the PCRF through the AAC. Information, wherein the information is used to cause the policy and charging rules function entity PCRF to perform policy and charging decisions.
  • the selecting, by the AF, the accessing the AAC according to the priority principle includes: the AF preferentially accessing the AAC of the nearest network according to the location priority; and/or the AF preferentially accessing the subscription according to the subscription priority AAC with a high priority.
  • the subscription priority depends on the roaming agreement.
  • the step of the AF transmitting the service information to the PCRF by using the AAC includes: the AAC sending a message to the DRA; the DRA selecting according to the message The correct PCRF; the AF sends the information to the PCRF selected by the DRA through the AAC.
  • the step of the AF transmitting the service information to the PCRF by using the AAC includes: in the case that the home network or the visited network is subscribed, the AAC selects a PCRF access of the subscription network. The AF sends the information to the PCRF accessed by the AAC through the AAC.
  • the method further includes: the AAC performing subscription information check and/or resource admission control on the AF access network.
  • an application function entity device comprising: a selection module, configured to select an access application access control network element AAC according to a priority principle; and a sending module configured to pass the The AAC sends information to the PCRF, where the information is used to cause the PCRF to perform policy and charging decisions.
  • the selecting module is configured to preferentially access the AAC of the nearest network according to the location priority; and/or, set to preferentially access the AAC with the highest subscription priority according to the subscription priority.
  • the subscription priority depends on the roaming agreement.
  • the sending module is configured to send information to the correct PCRF selected by the AAC to the DRA, wherein the information is used to enable the PCRF to perform policy and charging decisions.
  • the DRA is based on the message sent by the AAC to select the correct PCRF.
  • the application function entity AF is selected according to the priority principle, and the accessed application access control network element AAC is selected; the AF sends information to the PCRF through the AAC, where the information is used to enable the PCRF to perform policy and charging decisions. .
  • the problem of charging and policy control of a certain type of service cannot be realized by the related technology, and the billing and policy control of the service is realized.
  • FIG. 1 is a schematic diagram of a PCC non-roaming architecture according to the related art
  • FIG. 2 is a schematic diagram of a PCC non-roaming architecture according to the related art in which an AAC function is deployed;
  • FIG. 3 is a flowchart of an application access control method according to an embodiment of the present invention.
  • FIG. 4 is a structural block diagram of an application function entity device according to an embodiment of the present invention.
  • 5-1 is a schematic diagram (LBO) of an AF access proximity AAC architecture according to an embodiment of the present invention
  • 5-2 is a schematic diagram (HR) of an AF proximity access AAC architecture according to an embodiment of the present invention
  • FIG. 6 is a schematic flowchart of triggering an IP session of an IP-CAN session by an AF initiating an AF session through a 3rd party AAC according to a location priority relationship according to an embodiment of the present invention
  • FIG. 7-1 is a schematic diagram of an AAC architecture (LBO) for accessing a visited location according to a subscription relationship according to a location-to-access AAC architecture according to an embodiment of the present invention
  • LBO schematic diagram
  • FIG. 7-3 is a schematic diagram (HR) of an AAC architecture in which an AF accesses a home according to a subscription relationship according to an embodiment of the present invention
  • FIG. 8 is a schematic diagram of a process of triggering an AF session through an HAAC and triggering an IP-CAN session modification according to a subscription priority relationship according to an embodiment of the present invention.
  • FIG. 3 is a flowchart of an application access control method according to an embodiment of the present invention. As shown in FIG. 3, the process includes the following steps:
  • Step S302 the AF selects the accessed AAC according to the priority principle
  • Step S304 the AF sends information to the PCRF through the selected AAC, where the information is used to enable the PCRF to perform policy and charging decisions.
  • the AF can select the AAC and perform corresponding processing through the selected AAC, thereby solving the problem of the related technology that cannot implement the charging and policy control of a certain type of service, and realizing the charging and policy control of the service.
  • the priority principle may be varied, and preferably, two comparisons are provided in the embodiment: the first one is: the AF preferentially accesses the AAC of the nearest network according to the location priority; the second type, the AF According to the subscription priority, priority is given to AAC with high subscription priority. These two methods can be used alone or in combination.
  • the priority of the subscription may be formulated according to different situations.
  • the subscription priority depends on the roaming agreement, and as a preferred method, attribution
  • the signing priority of the local network can be higher than that of the visited network.
  • the AAC may send a message to the DRA; the DRA selects the correct PCRF according to the message; The AF transmits the above information to the PCRF selected by the DRA through the AAC.
  • DRA Diameter Routing Agent
  • the AAC selects a PCRF access of the subscription network; the AF sends the information to the PCRF accessed by the AAC through the AAC.
  • the AAC can also perform subscription information check and/or resource admission control on the AF access network.
  • FIG. 4 is a structural block diagram of an application function entity device according to an embodiment of the present invention. As shown in FIG. 4, the structure includes: a selection module 42 and a sending module 44. The structure will be described below.
  • the selecting module 42 is configured to select an access application access control network element AAC according to the priority principle
  • the sending module 44 is configured to send information to the PCRF through the AAC, where the information is used to cause the PCRF to perform policy and charging decisions.
  • the selection module 42 is configured to preferentially access the AAC of the nearest network according to the location priority; and/or, set to preferentially access the AAC with the highest subscription priority according to the subscription priority.
  • the application access control scheme in the user roaming scenario is provided, so that the user can use the third-party service independent of the visited network and the home network in the roaming scenario.
  • a third-party AF initiates an AF session through the AAC:
  • the AF preferentially accesses the AAC of the nearest deployed network according to the deployment priority; and/or,
  • the AF preferentially accesses the AAC with the highest priority of the subscription according to the priority of the contract (for example, when the visited network and the home network are simultaneously signed and the priority of the home network is high, the access is preferentially accessed from the home network AAC);
  • the AF initiates an AF session establishment request to the HPCRF through the AAC, and the request message carries the service information.
  • the HPCRF or VPCRF performs policy and charging decisions based on the information carried by the request message (for the service requested by the AF).
  • the AAC needs to perform PCRF selection through the DRA, and follows the prior art selection, that is, the AAC sends the request to the DRA, and the DRA selects correctly according to the UE ID/IP and the PDN identifier.
  • PCRF PCRF.
  • the UE ID here refers to the identity of the operator's subscriber, such as the MSISDN or IMSI number.
  • FIG 5-1 and Figure 5-2 show the schematic diagram of the third-party data application provider (AF) accessing the AAC architecture based on the location priority in the roaming LBO and HR scenarios.
  • AF third-party data application provider
  • the AAC can perform subscription check and resource admission control on the AF access mobile network.
  • the AAC can check the subscription information of the network and the AF, and the AAC can obtain the subscription information obtained through the internal storage or the subscription database, such as the AF list.
  • the AAC can perform resource adaptation or service according to the user priority. Refuse to wait for admission control.
  • FIG. 6 is a flowchart of an embodiment of a third-party data application provider accessing an AAC architecture according to a location-first priority. As shown in FIG. 6, the AF accesses the AAC, initiates an AF session through the AAC, and triggers an IP-CAN session modification. The process specifically includes the following steps:
  • Step S601 in the process of the UE requesting to establish an IP-CAN session, the gateway where the PCEF is located receives the IP-CAN session establishment request message, where the IP-CAN session establishment request message carries the user identifier and requests for access. PDN ID of the PDN network.
  • step S602 the PCEF sends an IP-CAN session establishment indication message to the PCRF, where the IP-CAN session establishment indication message carries the user identifier, the PDN identifier, and the IP address allocated for the UE.
  • Step S603 After determining, according to the user identifier, the PCRF does not have the subscription information of the user, and sends a subscription document request to the SPR, and carries the user identifier and the PDN identifier in the subscription document request.
  • Step S604 the SPR returns the corresponding user subscription information according to the user identifier and the PDN identifier (returned by the subscription document response).
  • Step S605 the PCRF makes a policy decision according to the returned user subscription information, the network policy, and the access information of the UE. Among them, it may include formulating PCC rules and event triggers.
  • Step S606 The PCRF sends an IP-CAN session establishment confirmation message to the PCEF, where the IP-CAN session establishment confirmation message carries a PCC rule and an event trigger.
  • Step S607 the PCEF installation policy, the gateway where the PCEF is located returns an IP-CAN session establishment response to the UE, where the IP-CAN session establishment response carries an IP address.
  • Step S608 if it is online charging, the PCEF sends a CCR message to the OCS, activates the online charging session, provides corresponding input information to the OCS for decision, and the PCEF carries the charging key, or the Charging key & service ID, to the OCS to request the credit information.
  • Step S609 the OCS decides whether to provide the credit authorization information to the PCEF according to the request message and the subscription information, and returns the information to the PCEF in the CCA message.
  • Step S610 The UE connects to the AS/AF of the third-party data application provider and requests the service, and the AS/AF sends an AF session request to the AAC to trigger the establishment of the AF session with the PCRF.
  • the request message carries service information such as a UE ID, a UE IP, and a service data flow description.
  • the third-party application provider AF initiates a request to the AAC that deploys the highest priority carrier network according to the deployment (eg, topology or geographic location) priority principle (eg, the geographical location is closest or the topology relationship is the closest).
  • the agreement between 3rd Party AF and AAC is not limited here; for example, it can be SOAP or restful protocol.
  • the carrier network where the AAC is located is not limited to the home network or the visited network of the UE, and may be a third-party carrier network other than the two; the network with the highest priority is the home or visited network.
  • the scenario is directly connected to the home or visited network AAC.
  • step S611 the third-party network AAC sends an AF session establishment request to the HPCRF, where the message carries the content carried in the S610.
  • the home network AAC can be used as a proxy route access of the third-party network AAC and the HPCRF, depending on operational requirements and network deployment;
  • Step S612 the HPCRF performs policy decision according to the AF session information, the service provider information, the charging information and the like, the AF session information, the subscription information provided by the SPR, and the IP-CAN session information provided by the PCEF, and determines whether to authorize the service. QoS and generation of PCC rules, generating corresponding rules and corresponding subscription events. If the AF usage threshold is provided or the usage monitoring of the service is signed, the PCEF also needs to send the usage monitoring keyword and the threshold to monitor the usage of the service;
  • the HPCRF rejects the authorization, the HPCRF returns a reject message to the AAC, the AF service fails, and the process ends.
  • step S613 the HPCRF provides the PCC rule installation and execution to the PCEF, and the RAR message sent to the PCEF carries the rule and event subscription generated in step S612, and the related usage monitoring related information, which is specifically described in S612.
  • Step S614 after the PCEF installs and executes the policy, returns a confirmation message to the H-PCRF;
  • Step S615 the PCEF performs rule matching and bearer modification or creation of an IP-CAN session modification process according to the received rule and event information; if the PCRF or AF subscribes to the rule execution result or the resource allocation result feedback, the PCEF will initiate The CCR message will report the execution result;
  • the user can use the third-party service in the roaming scenario
  • the AAC AF request is sent to the H-DRA, and the H-DRA selects the correct HPCRF according to the UE ID/IP and PDN identifiers (for example, IP- PCRF) associated with the CAN session; for the visited DRA scenario, if the third-party AAC accesses from the VPCRF, the VPCRF selection is required.
  • the AAC sends a request to the VDRA.
  • the VDRA selects the correct VPCRF according to the UE ID/IP and PDN identifiers. .
  • the UE ID here refers to the identity of the operator's subscriber, such as the MSISDN or IMSI number.
  • the third-party AAC can select according to the priority selection of the two (for example, preferentially selecting the home network HPCRF); this embodiment does not limit the AAC to determine whether the subscription is signed or not. For example, the AAC can determine that the IP address of the visited access scene is allocated by the visited network, and the IP address of the home access scene is allocated by the home network, so that the roaming scenario can be distinguished.
  • the third-party AAC selects the PCRF access of the subscription network. If the VPCRF accesses the visited network, the VPCRF interacts with the HPCRF through the S9 interface to transmit the AF service information to the HPCRF for policy decision.
  • the HPCRF returns the relevant rules and usage thresholds for decision production and various event subscriptions to the VPCRF to the GW for installation and execution through the S9 interface.
  • the service information can be transmitted to the PCRF for decision based on the S9 interface or the Gx interface of the DRA route according to the roaming protocol of the third-party network and the home network/visit network.
  • Figure 7-1, 7-2, and 7-3 are for the roaming visited access LBO and the home access HR scenario respectively.
  • the third-party data application (AF) preferentially accesses the contracted relationship according to the agreement/collaboration.
  • Figure 7-1 shows the architecture of the AF in the LBO scenario, where the AF is only signed in the visited network, and the AF accesses the visited AAC.
  • Figure 7-2 shows the AF contract in the home network or the simultaneous subscription and attribution.
  • FIG. 7-3 is the HR scenario, AF contracted The home network or the simultaneous subscription and home network, the AF accesses the architecture diagram of the home AAC.
  • the AF has no contract with the attribution and the visited place, and the architecture of the contract with the third-party network and AF access to the third-party network AAC is shown in Figures 7-1 and 7-2.
  • the AAC can be directly routed to the AAC, and the AAC can route the AF access mobile network.
  • the AAC may perform subscription checking and resource admission control on the AF access mobile network. For example, the AAC may check the subscription information of the network and the AF, and the AAC may obtain the subscription information obtained through the internal storage or the subscription database, such as the AF list.
  • resource admission control is performed on the overall QoS of the AF contract, for example, when the current total number of users or the total bandwidth or total usage of the AF exceeds the subscription value, the AAC may be based on User priority is used for admission control such as resource adaptation or service rejection.
  • FIG. 8 is a flowchart of an embodiment of a third-party data application provider preferentially accessing an AAC architecture according to a contracting relationship (for example, a collaboration relationship).
  • a contracting relationship for example, a collaboration relationship.
  • the AF has the highest subscription priority according to the collaboration priority.
  • the AAC of the network initiates an AF session through the AAC, and the process of triggering the IP-CAN session modification includes the following steps:
  • Step S801 in the process of the UE requesting to establish an IP-CAN session, the gateway where the PCEF is located receives the IP-CAN session establishment request message, where the IP-CAN session establishment request message carries the user identifier and requests for access. PDN ID of the PDN network.
  • step S802 the PCEF sends an IP-CAN session establishment indication message to the PCRF, where the IP-CAN session establishment indication message carries the user identifier, the PDN identifier, and the IP address allocated for the UE.
  • Step S803 After determining, according to the user identifier, the PCRF does not have the subscription information of the user, and sends a subscription document request to the SPR, and carries the user identifier and the PDN identifier in the subscription document request.
  • Step S804 the SPR returns the corresponding user subscription information according to the user identifier and the PDN identifier.
  • Step S805 the PCRF makes a policy decision according to the returned user subscription information, the network policy, and the access information of the UE. Among them, it may include formulating PCC rules and event triggers.
  • Step S806 the PCRF sends an IP-CAN session establishment confirmation message to the PCEF, where the IP-CAN session establishment confirmation message carries a PCC rule and an event trigger.
  • Step S807 the PCEF installs the policy, and the gateway where the PCEF is located returns an IP-CAN session establishment response to the UE, where the IP-CAN session establishment response carries an IP address.
  • Step S808 if it is online charging, the PCEF sends a CCR message to the OCS, activates the online charging session, provides corresponding input information to the OCS for decision, and the PCEF carries the charging key, or the Charging key & service ID, to the OCS to request the credit information.
  • Step S809 the OCS decides whether to provide the credit authorization information to the PCEF according to the request message and the subscription information, and returns the information to the PCEF in the CCA message.
  • Step S810 the UE connects to the AS/AF of the third-party data application provider and requests the service, and the AS/AF sends an AF session request to the AAC, triggering the establishment of the AF session with the PCRF.
  • the request message carries service information such as a UE ID, a UE IP, and a service data flow description.
  • the third-party application provider AF initiates a request to the AAC of the contracted carrier network according to the contract relationship and the contract priority according to the contract relationship priority (for example, the home network and the visited network simultaneously sign, attribution
  • the network takes precedence over visiting the network, or the visited network takes precedence over the home network).
  • the communication protocol between the 3rd Party AF and the AAC is not limited; for example, it may be a SOAP or a restful protocol.
  • the operator network in which the AAC is located is not limited to the home network or the visited network of the UE, and may be a third-party carrier network other than the two; for the AAC home network, that is, the home or visited network, It can directly access the home or visited network PCRF.
  • step S811 the third-party network AAC sends an AF session establishment request to the HPCRF, where the message carries the content carried in S810.
  • the home network AAC can be used as a proxy route access of the third-party network AAC and the HPCRF, depending on operational requirements and network deployment;
  • Step S812 the HPCRF performs policy decision according to the AF session information such as service information, service provider information, and charging information provided by the AAC, the subscription information provided by the SPR, and the IP-CAN session information provided by the PCEF, and determines whether to authorize the service.
  • the AF session information such as service information, service provider information, and charging information provided by the AAC
  • the subscription information provided by the SPR the subscription information provided by the SPR
  • the IP-CAN session information provided by the PCEF determines whether to authorize the service.
  • QoS and generation of PCC rules generating corresponding rules and corresponding subscription events. If the AF/AAC usage threshold is provided or the usage monitoring of the service is contracted, the PCEF also needs to send the usage monitoring keyword and the threshold to monitor the usage of the service;
  • the HPCRF rejects the authorization, the HPCRF returns a reject message to the AAC, the AF service fails, and the process ends.
  • step S813 the HPCRF provides PCC rule installation and execution to the PCEF, and the RAR message sent to the PCEF carries the rule and event subscription generated in step S812, and the related usage monitoring related information, which is specifically described in S812.
  • Step S814 after the PCEF installs and executes the policy, returns a confirmation message to the H-PCRF;
  • Step S815 the PCEF performs rule matching and bearer modification or creation of an IP-CAN session modification process according to the received rule and event information; if the PCRF or AF subscribes to the rule execution result or the resource allocation result feedback, the PCEF will initiate The CCR message will report the execution result;
  • the user can use the third-party service in the roaming scenario
  • the AAC AF request is sent to the H-DRA, and the H-DRA selects the correct HPCRF according to the UE ID/IP and PDN identifiers (for example, IP- PCRF) associated with the CAN session; for the visited DRA scenario, if the third-party AAC accesses from the VPCRF, the VPCRF selection is required.
  • the AAC sends the request to the VDRA, VDRA.
  • the correct VPCRF is selected according to the UE ID/IP and PDN identification.
  • the UE ID here refers to the identity of the operator's subscriber, such as the MSISDN or IMSI number.
  • the third-party AAC may select the PCRF access according to the default priority (for example, preferentially selecting the home network); this embodiment does not limit the implementation of the AAC to determine whether the subscription is successful or not. For example, the AAC can determine that the IP address of the visited access scene is allocated by the visited network, and the IP address of the home access scene is allocated by the home network, thereby distinguishing the roaming scenario.
  • the third-party AAC selects the PCRF access of the subscription network. If the visited network is connected to the VPCRF, the VPCRF interacts with the HPCRF through the S9 interface to transmit the AF service information to the HPCRF for policy decision.
  • the HPCRF returns the relevant rules and usage thresholds of the decision production and the various event subscriptions to the VPCRF to the GW installation and execution through the S9 interface; or the VPCRF local policy decision and the rule generation and delivery to the GW installation and execution.
  • the scenario where the visited place and the attribution are not signed only the scenario of signing the third-party network can be transmitted according to the roaming agreement of the third-party network and the home network/visiting network, based on the inter-network S9 interface or the Gx-port inter-network DRA routing mode. Business information is given to the HPCRF/VPCRF decision.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in a storage device by a computing device, or they may be fabricated into individual integrated circuit modules, or Multiple modules or steps are made into a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.
  • the foregoing embodiments and preferred embodiments solve the problem that the related technologies cannot implement charging and policy control of a certain type of service, and implement charging and policy control of services.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé de contrôle d'accès à une application et un appareil d'entité de fonction d'application. Le procédé comprend les opérations suivantes : une fonction d'application (AF) sélectionne un élément de réseau de contrôle d'accès à une application (AAC) ayant fait l'objet d'un accès selon une règle de priorité ; et l'AF envoie des informations à une fonction de contrôle des politiques et de la tarification (PCRF) par l'intermédiaire de l'AAC, les informations étant utilisées pour amener la PCRF à exécuter une décision de contrôle de politique et de tarification. La présente invention résout le problème de contrôle de tarification et de politique d'un certain type de service qui ne peut pas être réalisé par des technologies pertinentes.
PCT/CN2014/086450 2013-10-15 2014-09-12 Procédé de contrôle d'accès à une application et appareil d'entité de fonction d'application WO2015055063A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310483024.2 2013-10-15
CN201310483024.2A CN104581670B (zh) 2013-10-15 2013-10-15 应用接入控制方法及应用功能实体装置

Publications (1)

Publication Number Publication Date
WO2015055063A1 true WO2015055063A1 (fr) 2015-04-23

Family

ID=52827647

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/086450 WO2015055063A1 (fr) 2013-10-15 2014-09-12 Procédé de contrôle d'accès à une application et appareil d'entité de fonction d'application

Country Status (2)

Country Link
CN (1) CN104581670B (fr)
WO (1) WO2015055063A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017219973A1 (fr) * 2016-06-21 2017-12-28 Huawei Technologies Co., Ltd. Systèmes et procédés de sélection et de resélection de trajet de plan utilisateur, et de notification de changements de plan utilisateur
US10531420B2 (en) 2017-01-05 2020-01-07 Huawei Technologies Co., Ltd. Systems and methods for application-friendly protocol data unit (PDU) session management
US10972552B2 (en) 2016-09-30 2021-04-06 Huawei Technologies Co., Ltd. Method and system for user plane path selection

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106304195B (zh) * 2015-06-23 2020-06-19 中兴通讯股份有限公司 第三方应用的策略控制方法、scef和pcrf
EP3472986B1 (fr) 2016-06-20 2021-09-01 Telefonaktiebolaget LM Ericsson (PUBL) Commande de politique à base de réseau pour accès simultanés
KR102412288B1 (ko) * 2017-08-14 2022-06-23 삼성전자 주식회사 제 3자 응용 서버에서 단말의 무선 연결 타입 변경을 확인하는 방법
CN110557744B (zh) * 2018-05-31 2022-08-19 华为技术有限公司 订阅事件的方法与网络功能网元

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101217810A (zh) * 2008-01-16 2008-07-09 中兴通讯股份有限公司 一种策略和计费规则功能的选择方法
CN101355561A (zh) * 2008-08-29 2009-01-28 中兴通讯股份有限公司 Dra的会话消息管理方法和系统
CN101483826A (zh) * 2008-01-07 2009-07-15 华为技术有限公司 选择策略和计费规则功能实体的方法和装置

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100479586C (zh) * 2006-03-17 2009-04-15 华为技术有限公司 一种通信网络中业务流建立方法及其系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101483826A (zh) * 2008-01-07 2009-07-15 华为技术有限公司 选择策略和计费规则功能实体的方法和装置
CN101217810A (zh) * 2008-01-16 2008-07-09 中兴通讯股份有限公司 一种策略和计费规则功能的选择方法
CN101355561A (zh) * 2008-08-29 2009-01-28 中兴通讯股份有限公司 Dra的会话消息管理方法和系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Policy and charging control architecture (Release 12", 3GPP TS 23.203 V12.2.0, 30 September 2013 (2013-09-30) *

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017219973A1 (fr) * 2016-06-21 2017-12-28 Huawei Technologies Co., Ltd. Systèmes et procédés de sélection et de resélection de trajet de plan utilisateur, et de notification de changements de plan utilisateur
US10785696B2 (en) 2016-06-21 2020-09-22 Huawei Technologies Co., Ltd. Systems and methods for user plane path selection, reselection, and notification of user plane changes
US11184830B2 (en) 2016-06-21 2021-11-23 Huawei Technologies Co., Ltd. Systems and methods for user plane path selection, reselection, and notification of user plane changes
US11350336B2 (en) 2016-06-21 2022-05-31 Huawei Technologies Co., Ltd. Systems and methods for user plane path selection, reselection, and notification of user plane changes
US11856501B2 (en) 2016-06-21 2023-12-26 Huawei Technologies Co., Ltd. Systems and methods for user plane path selection, reselection, and notification of user plane changes
US10972552B2 (en) 2016-09-30 2021-04-06 Huawei Technologies Co., Ltd. Method and system for user plane path selection
US11700312B2 (en) 2016-09-30 2023-07-11 Huawei Technologies Co., Ltd. Method and system for user plane path selection
US10531420B2 (en) 2017-01-05 2020-01-07 Huawei Technologies Co., Ltd. Systems and methods for application-friendly protocol data unit (PDU) session management
US10812977B2 (en) 2017-01-05 2020-10-20 Huawei Technologies Co., Ltd. Systems and methods for application-friendly protocol data unit (PDU) session management
US11096046B2 (en) 2017-01-05 2021-08-17 Huawei Technologies Co., Ltd. Systems and methods for application-friendly protocol data unit (PDU) session management
US11838756B2 (en) 2017-01-05 2023-12-05 Huawei Technologies Co., Ltd. Systems and methods for application-friendly protocol data unit (PDU) session management

Also Published As

Publication number Publication date
CN104581670A (zh) 2015-04-29
CN104581670B (zh) 2019-03-15

Similar Documents

Publication Publication Date Title
JP5038534B2 (ja) 制限付きポリシー及び課金制御ケイパビリティの検出及び報告
EP2827623B1 (fr) Procédé de commande de politique et de facturation, et appareil v-pcrf
WO2015055063A1 (fr) Procédé de contrôle d'accès à une application et appareil d'entité de fonction d'application
US8516545B2 (en) Method and system for session modification
EP2702727B1 (fr) Procédé et dispositif destinés à la régulation de la qos et/ou à la commande de politique et de facturation pour un utilisateur invité
US20130122860A1 (en) Method for providing a monitoring of usage network resources of a user session within a network and a network device
JP2012509041A5 (fr)
WO2011097911A1 (fr) Procédé, dispositif et système pour sélectionner une entité de fonction de politique et de règles de facturation
WO2009046678A1 (fr) Procédé et dispositif pour obtenir la capacité de fonction d'application de politique et de facturation
WO2016201999A1 (fr) Procédé et appareil de facturation d'application tierce, et dispositif à fonction d'application
WO2011029289A1 (fr) Procédé et système de transmission d'un mode de commande de support dans des scénarios d'itinérance
EP2589203A1 (fr) Audits de sessions diameter
WO2013044730A1 (fr) Procédé et système de mise à jour de qualité de service pour règles de politique et de facturation
CN102131296A (zh) 在全业务融合网络中控制资源的方法和系统
WO2011085621A1 (fr) Procédé et système de traitement de service
WO2015120731A1 (fr) Procédé et dispositif de commande de politique de réseau visité
WO2012116600A1 (fr) Procédé et système de négociation de fonction pour entité à fonction de commande de politique et de facturation
WO2014107985A1 (fr) Procédé de facturation en ligne de services d'itinérance locale, h-ocs et v-ocs
CN102111740B (zh) 一种支持多接入的策略计费控制方法和系统
US9485105B2 (en) Method and telecommunications network utilizing more than one online charging system for a given user
WO2012083779A1 (fr) Procédé et dispositif de commande de politique
US20200112448A1 (en) Wireless Communication Method and Device
US20150036550A1 (en) Method and system for identifying application detection and control function mode
WO2013091705A1 (fr) Procédés et appareils pour établissement de session avec commande de politique entre réseaux mobiles et fixes
JP5872705B2 (ja) ローミング協定／パートナの抹消を契機とするローミングセッションの終了

Legal Events

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

Ref document number: 14854725

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14854725

Country of ref document: EP

Kind code of ref document: A1