WO2020259058A1 - 一种策略和计费控制的实现方法及装置 - Google Patents

一种策略和计费控制的实现方法及装置 Download PDF

Info

Publication number
WO2020259058A1
WO2020259058A1 PCT/CN2020/087078 CN2020087078W WO2020259058A1 WO 2020259058 A1 WO2020259058 A1 WO 2020259058A1 CN 2020087078 W CN2020087078 W CN 2020087078W WO 2020259058 A1 WO2020259058 A1 WO 2020259058A1
Authority
WO
WIPO (PCT)
Prior art keywords
rule
pcc
predefined
smf
session
Prior art date
Application number
PCT/CN2020/087078
Other languages
English (en)
French (fr)
Inventor
梁琳琳
顾嘉
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2020259058A1 publication Critical patent/WO2020259058A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • 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

Definitions

  • the embodiments of the present application relate to, but are not limited to, the field of communication technology, and particularly refer to a method and device for implementing policy and charging control.
  • the PCC (Policy and Charging Control) of the fifth generation mobile communication technology (5G) is in TS 23.501 of 3GPP (Third Generation Partnership Project) R15 (Release 15, version 15) Gives an overview. Although the agreement specifies the pre-defined (predefined) PCC rules and the dynamic (dynamic) PCC rules, it only provides a framework for policy control and cannot meet the implementation requirements.
  • This application provides a method and device for implementing policy and charging control, which can improve a 5GC (5G Core, 5G core network) policy control scheme to support meeting implementation requirements.
  • 5GC 5G Core, 5G core network
  • this application provides a method for implementing policy and charging control, including: session management function entity (SMF) issuing local policy and charging control (PCC) rules to user plane function entity (UPF) through rule management messages
  • SMF session management function entity
  • PCC local policy and charging control
  • UPF user plane function entity
  • the local PCC rules are configured on the SMF
  • the local PCC rules include: a predefined rule name, a packet detection rule (PDR) associated with the predefined rule name, and business processing associated with the PDR Strategy.
  • this application provides a method for implementing policy and charging control, including: the UPF receives the local PCC rules issued by the SMF through a rule management message; the UPF saves the received local PCC rules; wherein, the SMF The local PCC rule is configured thereon, and the local PCC rule includes: a predefined rule name, a PDR associated with the predefined rule name, and a service processing strategy associated with the PDR.
  • the present application provides a device for implementing policy and charging control, including: a first memory, a first processor, and a computer stored in the first memory and capable of running on the first processor A program, wherein the first processor is configured to execute the computer program to implement the steps of the method on the SMF side.
  • this application provides a device for implementing policy and charging control, including: a second memory, a second processor, and a computer stored in the second memory and capable of running on the second processor A program, wherein the second processor is used to execute the computer program to implement the steps of the UPF side method.
  • the present application also provides a computer-readable storage medium that stores a computer program that, when executed, realizes the steps of the above-mentioned SMF-side or UPF-side method.
  • Figure 1 is a schematic diagram of the 5G system architecture in the 3GPP 23.501 standard
  • Figure 2 is a schematic diagram of the rule relationship in an embodiment of the application.
  • Figure 3 is an example diagram of the interaction between SMF and UPF in an embodiment of this application.
  • FIG. 4 is an example diagram of the configuration and use flow of the predefined PCC rules in an embodiment of the application
  • FIG. 5 is an example diagram of the configuration and use flow of local PCC rules in an embodiment of the application.
  • FIG. 6 is an example diagram of a processing flow when a UPF-side message does not match a PCC rule in an embodiment of the application;
  • FIG. 7 is a flowchart of a method for implementing policy and charging control provided by an embodiment of the application.
  • Fig. 8 is a flowchart of another method for implementing policy and charging control provided by an embodiment of the application.
  • FIG. 9 is a schematic diagram of a device for implementing policy and charging control according to an embodiment of the application.
  • FIG. 10 is a schematic diagram of another device for implementing policy and charging control provided by an embodiment of the application.
  • Figure 1 is a schematic diagram of the 5G system architecture in the 3GPP 23.501 standard.
  • Figure 1 depicts the 5G system architecture under non-roaming conditions, using reference point notation to show how various network functions interact.
  • the 5G system architecture includes the following structures: network slice selection function entity (NSSF, Network Slice Selection Function), network open function entity (NEF, Network Exposure Function), network repository function entity (NRF, Network Repository Function) , Policy Control Function Entity (PCF, Policy Control Function), Unified Data Management Entity (UDM, Unified Data Management), Application Service Function Entity (AF, Application Function), Access Management Function Entity (AMF, Access and Mobility Management Function) , Authentication Server Function Entity (AUSF, Authentication Server Function), Session Management Function Entity (SMF, Session Management Function), (Wireless) Access Network ((R) AN, (Radio) Access Network), User Plane Function Entity ( UPF, User Plane Function), User Equipment (UE, User Equipment), and Data Network (DN, Data Network).
  • Nnssf represents the interface of NSSF
  • Nnef represents the interface of NEF
  • Nnrf represents the interface of NRF
  • Npcf represents the interface of PCF
  • Nudm represents the interface of UDM
  • Naf represents the interface of AF
  • Nausf represents the interface of AUSF
  • Namf represents the interface of AMF
  • Nsmf represents the interface of SMF.
  • N1 represents the reference point between UE and AMF
  • N2 represents the reference point between (R)AN and AMF
  • N3 represents the reference point between (R)AN and UPF
  • N4 represents the reference point between SMF and UPF
  • N6 represents the reference point between UPF and DN
  • N9 represents the reference point between two UPFs.
  • the current 5G standard protocol only provides a framework for policy control, and does not give specific process implementations, such as the processing method for business flow matching PCC rules, and how to deal with PCC rule matching failures.
  • the embodiment of the application provides a method and device for implementing policy and charging control.
  • local PCC rules between SMF and UPF are defined, and the 5GC policy control scheme is improved through the use of local PCC rules;
  • the embodiments of the present application also provide examples of the definition of predefined PCC rules and dynamic PCC rules, the issuance of PCC rules between SMF and UPF, matching processing procedures, and collaboration procedures, so as to support meeting specific implementation requirements.
  • FIG. 2 is a schematic diagram of the rule relationship in an embodiment of the application.
  • the SMF may include a PFDF (Packet Flow Description Function) module, a session management module, and a policy control module.
  • the session management module can issue tunnel information (Tunnel Info), QER (QoS (Quality of Service) Enforcement Rule, QoS enforcement rule), URR (Usage Reporting Rule, usage report rule), FAR (Forwarding Action Rule) , Forwarding action rules);
  • the policy control module can issue SDF (Service Data Flow), ADC (Application Detection and Control, application detection and control) rules, QER, URR, and FAR.
  • PDR Packet Detection Rule
  • SDF Packet Detection Rule
  • ADC rules Packet Flow Descriptions
  • ID Application Identifier
  • a PCC rule may include PDR, QER, URR, and FAR.
  • the embodiments of the present application provide an implementation process of policy and charging control between SMF and UPF.
  • the SMF is configured with local PCC rules, and the SMF delivers the local PCC rules to the UPF through a rule management message; the UPF receives and saves the local PCC rules; where the local PCC rules include: Predefined Rules (Predefined Rules) Name), the PDR associated with the predefined rule name, and the business processing strategy associated with the PDR.
  • Predefined Rules Predefined Rules
  • the service processing policy may include: one or more QERs, one or more FARs, and one or more URRs; or, a traffic steering policy (traffic steering policy).
  • SMF and UPF have the same local PCC rules, and the local PCC rules are maintained synchronously, which helps to improve the success rate of matching the PCC rules to business packets, thereby reducing the interaction between SMF and UPF, and Meet specific implementation needs.
  • the SMF may send the pre-defined rule name of the activated local PCC rule to the UPF through a session establishment request message or a session modification request message; wherein, the session establishment request message or the session modification request message includes the activated The message field of the predefined rule name.
  • UPF receives the session establishment request message or the session modification request message sent by the SMF, and according to the predefined rule name of the activated local PCC rule carried in the session establishment request message or the session modification request message, searches for the pre-defined rule name from the saved local PCC rules.
  • the message field (Active Local Defined Rules IE) carrying the name of the activated predefined rule may include: field type, length information, planning identifier (Enterprise ID), and the name of the activated predefined rule.
  • the SMF may also send the predefined rule name of the deactivated local PCC rule to the UPF through the session modification request message; wherein, the session modification request message includes a message field carrying the deactivated predefined rule name .
  • the UPF receives the session modification request message sent by the SMF, and according to the predefined rule name of the inactivated local PCC rule carried in the session modification request message, finds and deletes the local PCC rule matching the predefined rule name from the corresponding session context.
  • the message field (Deactive Local Defined Rules IE) that carries the name of the deactivated predefined rule may include: field type, length information, planning identifier (Enterprise ID), and the name of the deactivated predefined rule.
  • the local PCC rule can be activated or deactivated on the UPF side for the corresponding session.
  • the SMF may also issue a predefined PCC rule to the UPF through a rule management message; the UPF may receive and save the predefined PCC rule; wherein the predefined PCC rule includes at least one of the following: predefined rule name And its associated business processing strategy, application identifier and its associated business processing strategy, traffic directional strategy identifier and its associated business processing strategy.
  • the SMF is configured with at least one of the following information: SDF and its associated predefined rule name, application detection filter (Application Detection Filter) and its associated application identifier, SDF and its associated traffic directional policy identifier ( traffic steering policy identifier), application identifier and its associated traffic steering policy identifier. In this way, when a certain predefined PCC rule is activated or deactivated, the SMF can determine which information is provided to the UPF so that the UPF can determine which predefined PCC rule is activated or deactivated.
  • application detection filter Application Detection Filter
  • the SMF when the session is created or after the session is created, when the predefined PCC rules are activated by the PCF, the SMF can activate the predefined PCC rules in the UPF in the following ways:
  • the SMF receives the SDF related to the activated PCC rule from the PCF, according to the SDF in In the configured information, check whether there is a predefined rule name or traffic directional policy identifier associated with it);
  • the pre-defined rule name, application identifier or traffic directional policy identifier corresponding to the activated PCC rule is found, the pre-defined rule name, application identifier or traffic directional policy identifier found is sent to the UPF through a session establishment request message or a session modification request message. Traffic directional policy identifier, so that UPF can determine which predefined PCC rule configured on UPF is activated according to the predefined rule name, application identifier or traffic directional policy identifier;
  • SMF creates the PDR used to identify the service data flow referenced by the activated predefined PCC rule and the corresponding business processing Strategies (for example, including QER(s), FAR(s) and URR(s)), associate the created PDR with the business processing strategy, obtain the activated predefined PCC rules, and deliver the activated predefined PCC to the UPF rule.
  • business processing Strategies for example, including QER(s), FAR(s) and URR(s)
  • the UPF when the UPF receives the predefined rule name, application identifier, or traffic directional policy identifier corresponding to the activated predefined PCC rule issued by the SMF through the session establishment request message or the session modification request message; then According to the predefined rule name, application identifier or traffic directional policy identifier, search for the predefined PCC rule matching the predefined rule name, application identifier or traffic directional policy identifier from the saved predefined PCC rules, and then After the found pre-defined PCC rules are associated with the PDR issued by the SMF, they are mounted under the session context of the established session. In this example, UPF determines the activated pre-defined PCC according to the saved pre-defined PCC rules and the corresponding information issued by the SMF.
  • the UPF when the UPF receives the activated pre-defined PCC rule issued by the SMF, the UPF can mount the received activated pre-defined PCC rule under the session context of the corresponding session.
  • the activated predefined PCC rules can be completely issued by the SMF.
  • the SMF can obtain dynamic PCC rules from the PCF, and issue dynamic PCC rules applicable to the established session to the UPF when the session is established (for example, the SMF can issue dynamic PCC rules to the UPF through a rule management message).
  • PCC rules include at least one of the following: a business processing strategy; a traffic directional strategy identifier.
  • the SMF side can determine the business processing strategy of the dynamic PCC rules (for example, including QER(s), FAR(s) and URR(s)) according to the application identifier or SDF(s); the SMF side can also determine the business processing strategy according to the SDF(s) ) Or application identifier to determine the corresponding traffic directional policy identifier.
  • the UPF side may be configured with at least one of the following: application identifier and corresponding PFD(s), traffic directional strategy identifier and its associated traffic directional strategy.
  • the UPF after the UPF receives the service processing policy of the dynamic PCC rule issued by the SMF, it can determine its associated PDR, and mount the service processing policy after the associated PDR in the session context of the established session.
  • the UPF can search for the PCC rule applicable to the received message in the PCC rules mounted under the session context of the session; when If the PCC rule applicable to the message is not found in the context of the session, UPF will search for the PCC rule applicable to the message from the saved local PCC rules; when the message is found to be applicable in the session context or the saved local PCC rules According to the found PCC rules, UPF processes the message according to the found PCC rules. Among them, when the PCC rule applicable to the message is found in the saved local PCC rules, the UPF will mount the found local PCC rule under the context of the session.
  • the UPF when no PCC rule applicable to the message is found in the saved local PCC rules, the UPF sends a session report request message indicating that the message does not match the applicable PCC rule to the SMF.
  • SMF receives the session report request message sent by UFP to indicate that the message has not matched the applicable PCC rules
  • SMF sends the default rule to UPF, or SMF according to the message information carried in the session report request message , Request new dynamic PCC rules or activated pre-defined PCC rules from PCF, and deliver the new dynamic PCC rules or activated pre-defined PCC rules to UPF.
  • UPF receives the PCC rules re-issued after the SMF receives the session message request message.
  • UPF processes the message according to the PCC rules re-issued by SMF; among them, SMF reissues
  • the issued PCC rules include: default rules, new dynamic PCC rules, or activated pre-defined PCC rules.
  • the UPF can mount the PCC rules reissued by the SMF under the session context of the session, and process the message according to the reissued PCC rules.
  • UPF determines that the PCC rule matching fails.
  • the multi-level PCC rule matching process can improve the success rate of the packet matching the PCC rule.
  • the rule management message may include a PFCP (Packet Forwarding Control Protocol, Packet Forwarding Control Protocol) PCC rule management request message.
  • the SMF can send a PFCP PCC rule management request message through the Sxb, Sxc, and N4 interfaces to provide the UPF with local PCC rules, predefined PCC rules, or dynamic PCC rules.
  • UPF can send a PFCP PCC rule management response message to SMF through the Sxb, Sxc, and N4 interfaces as a response to the PFCP PCC rule management request message.
  • Fig. 3 is an example diagram of the interaction between SMF and UPF in an embodiment of the application.
  • the implementation method of the policy and charging control provided by the embodiment of the present application will be described below with reference to FIG. 3 through an example.
  • PCC rules can be defined between SMF and UPF: predefined PCC rules, dynamic PCC rules, and local PCC rules.
  • Table 1 shows the rule content table in this embodiment. Each line of rule content shown in Table 1 can correspond to a business scenario. Moreover, Table 1 only illustrates the framework of each PCC rule, and does not give actual parameters or strategy information. The actual parameters or strategy information can be determined according to actual application scenarios, so it will not be repeated here.
  • the predefined PCC rules are defined as follows: First, if the predefined PCC rules include an application identifier (application identifier, APP ID), and the corresponding application detection filters (application detection filters) are configured in UPF , SMF should provide the corresponding APP ID to UPF; second, if the predefined PCC rules include traffic steering policy identifier (s), SMF should provide UPF; third, if the predefined PCC rules include Service data flow filter (service data flow filter(s)), SMF should be provided to UPF; fourth, if the pre-defined PCC rule contains the traffic processing policy pre-configured on UPF, SMF should be activated through Rule ID(s) Traffic processing strategy.
  • application identifier application identifier
  • APP ID application detection filters
  • SMF configure the key as SDF(s) or application identifier, and the value as traffic steering policy identifier(s); in UPF, configure the key as traffic steering policy as identifier(s) and the value as traffic steering policy.
  • SMF can provide pre-defined PCC rules to UPF.
  • the dynamic PCC rule is defined as follows: When the SMF receives the dynamic PCC policy from the PCF, the policy includes the application identifier or the parameters used for traffic processing in the UPF. First, if the SMF is configured with the application detection filter, SMF brings application detection filter to UPF in service data flow filter; second, it provides application detection filters in UPF, and SMF brings application identifier to UPF in service data flow filter.
  • the key value issued in SMF is application identifier, and the value is QER(s), FAR(s) and URR(s); in UPF, the key is application identifier and PFD(s) to match SMF QER(s), FAR(s) and URR(s) issued.
  • the key value issued in SMF is SDF(s) or application identifier, and the value is traffic steering policy identifier(s); in UPF, the key is traffic steering policy identifier(s), and the value is traffic steering policy matching.
  • the key for the local PCC rules, as shown in Table 1, you can configure the key as Predefined Rules Name in the SMF, and the value as PDR(s) ⁇ QER(s), FAR(s) and URR(s) (ie The QER(s), FAR(s), and URR(s)) associated with PDR(s) have the same local PCC rules in UPF, so that the local PCC rule configurations of SMF and UPF are consistent.
  • the interaction between SMF and UPF in this embodiment includes the following processing:
  • the SMF sends the predefined PCC rules and local PCC rules through the newly added rule management message (for example, PFCP PCC Rules Management Request), and UPF saves the received predefined PCC rules in the local predefined In the rule pool, save the received local PCC rules in the local rule pool.
  • the predefined PCC rules and local PCC rules through the newly added rule management message (for example, PFCP PCC Rules Management Request), and UPF saves the received predefined PCC rules in the local predefined In the rule pool, save the received local PCC rules in the local rule pool.
  • each predefined PCC rule saved by UPF may include: a predefined rule name (for example, PreDefName1, PreDefName2, PreDefNamen) and its associated QERs, URRs, and FARs.
  • Each local PCC rule saved by the UPF may include: a predefined rule name (for example, UniID21, UniID22, UniID2n), a PDR (including ADC and SDF) associated with the predefined rule name, and QERs, URRs, and FARs associated with the PDR.
  • the SMF issues a dynamic PCC rule to the UPF, and the UPF mounts the dynamic PCC rule under the corresponding session context.
  • the dynamic PCC rules saved by the UPF may include: the rule name (for example, DynID1, DynID2), the PDR (including ADC and SDF) associated with the rule name, and the QERs and URRs associated with the PDR And FAR.
  • the rule name for example, DynID1, DynID2
  • the PDR including ADC and SDF
  • the QERs and URRs associated with the PDR And FAR.
  • the SMF issues the activated predefined rule name, and UPF copies the predefined PCC rule matching the predefined rule name to the predefined rule pool according to the activated predefined rule name, and then matches
  • the pre-defined PCC rules and the PDR issued by SMF are mounted in the session context.
  • the activated predefined rules are named PreDefName2 and PreDefNamen, then the predefined PCC rules corresponding to these two predefined rule names plus the PDR issued by the SMF are mounted under the session context.
  • the UPF After the service is initiated through the established session, the UPF performs PDR matching according to the received message. That is, to determine which PDR the PFD of the message matches, the PCC rule associated with the matched PDR is the PCC rule that matches the message.
  • the message matches the PCC rule from the session context (that is, the PCC rule that matches the message is found from the PCC rule mounted under the session context), then execute S307; if the PCC rule is not matched in the session context, Then UPF matches the PCC rule in the local rule pool. If a local PCC rule matching the message is found from the local rule pool, copy the matched local PCC rule and mount it under the session context (for example, in the figure In 3, two local PCC rules named UniID21 and UniID22 are matched), and then S307 is executed; if no PCC rule is matched from the local rule pool, S305 is continued.
  • the UPF initiates a PFCP session report request (Session Report Request) message to the SMF, which carries the 5-tuple of the current service (for example, source address, source port number, Destination address, destination port number, protocol number) or APP ID; moreover, UPF buffers the received messages locally for subsequent processing.
  • PFCP session report request Session Report Request
  • the SMF performs PCC rule matching according to the information reported by the UPF, and issues the SMF matching the PCC rule to the UPF, and then replies a PFCP session report response (Session Report Response) message to the UPF.
  • PFCP session report response Session Report Response
  • the SMF can select the default rule with the lowest priority configured according to the information reported by the UPF, or the SMF can request a new dynamic PCC rule from the PCF or activate a predefined PCC rule.
  • the SMF can match the default rule with a predefined rule named UniIDn from the low-priority default rules maintained by the SMF according to the information reported by the UPF.
  • the UPF can retrieve the cached message and process the message (for example, forwarding or packet loss) according to the newly issued PCC rule.
  • the PCC rules re-issued by the SMF still do not match the service packet, the processing failure is returned.
  • the SMF performs charging according to the SEID (session context ID) and the URR ID.
  • the SMF may notify the UPF, and the UPF synchronously updates the corresponding PCC rule mounted under the session context of the existing session.
  • the SMF can deliver activated or deactivated local PCC rules and predefined PCC rules to the UPF through a PFCP session modification request message.
  • the SMF may send the PFCP PCC rule management request message through the Sxb, Sxc, and N4 interfaces.
  • Table 2 shows the description of the message field (Information Element, IE) of the PFCP PCC rule management request message.
  • the UPF can send a PFCP PCC rule management response message to the SMF through the Sxb, Sxc, and N4 interfaces as a response to the PFCP PCC rule management request message.
  • Table 3 shows the description of the message field (IE) of the PFCP PCC rule management response message.
  • the message field used to activate the local PCC rules can be encoded in the manner shown in Table 4.
  • the message field should indicate the predefined rule name of one or more local PCC rules. These local PCC rules Need to be activated in UPF.
  • the message field used to deactivate the local PCC rules can be encoded in the manner shown in Table 5.
  • the message field should indicate the predefined rule name of one or more local PCC rules.
  • the rules need to be inactivated in UPF.
  • the predefined rule name should be encoded as an octal string.
  • the sources of PCC rules in UPF can be divided into the following three types: PCC rules issued entirely by the user plane (CP, Control Plane); predefined PCC rules configured by UPF; local configured by UPF PCC rules.
  • the UPF cannot see the difference between the local PCC rules, the predefined PCC rules, and the dynamic PCC rules.
  • SMF as CP
  • FIG. 4 is an example diagram of the configuration and use flow of the predefined PCC rules in the embodiment of the application.
  • the business processing strategy of the predefined PCC rules configured by the UPF the PDR (SDF or ADC) is issued by the SMF, and the predefined PCC rules are activated by interacting the predefined rule names between the UPF and the SMF.
  • the process provided by this embodiment includes the following processing:
  • SMF provides UPF with predefined PCC rules through a newly-added rule management message.
  • the predefined PCC rules include: predefined rule names and their associated business processing strategies (for example, predefined QER(s), FAR( s) and URR(s)).
  • UPF saves the predefined PCC rules to a local predefined rule pool.
  • the UE initiates a PDU (Protocol Data Unit, protocol data unit) session establishment request.
  • PDU Protocol Data Unit, protocol data unit
  • the SMF obtains the dynamic PCC rule or the activated predefined PCC rule from the PCF. Among them, the SMF can obtain information about dynamic PCC rules or activated predefined PCC rules from the PCF through the Npcf interface.
  • the SMF uses the Create PDR IE in the PFCP session establishment request, or the update PDR IE in the PFCP session modification request to include the PDR->Activate Predefined Rules IE (ie, the message field of the activated predefined PCC rule associated with the PDR) To activate the predefined PCC rules configured on the UPF.
  • PDR->Activate Predefined Rules IE ie, the message field of the activated predefined PCC rule associated with the PDR
  • the UPF associates the received PDR with the activated predefined PCC rule, that is, associates the PDR with the activated predefined QER(s), FAR(s) and URR(s).
  • UPF can match the predefined PCC rules in the predefined rule pool according to the information carried in PDR->Activate Predefined Rules IE, associate the PDR issued by the SMF with the predefined PCC rules matched, and mount it to the corresponding session Context.
  • the UE transmits service flow data.
  • the UPF For service packets matching the PDR associated with the activated predefined PCC rule, the UPF executes the activated predefined PCC rule. For URR, UPF generates usage reports and sends them to SMF, and SMF can process usage reports. It should be noted that the URR ID used in the usage report triggered by the predefined PCC rule in the UPF must also be pre-configured on the CP side.
  • the SMF deactivates the predefined PCC rule activated in the UPF
  • the SMF may include the Deactivate Predefined Rules IE in the update PDR IE in the PFCP session modification request to notify the UPF to deactivate the predefined PCC rules associated with the relevant PDR.
  • UPF updates all relevant session contexts, for example, deletes the pre-defined PCC rules for deactivation mounted under the session context.
  • Fig. 5 is an example diagram of a configuration and usage flow of local PCC rules according to an embodiment of the application.
  • the local PCC rules are completely configured in UPF, and the local PCC rules are activated by interacting with the pre-defined rules name (Predefined Rules name) between UPF and SMF.
  • Predefined Rules name the pre-defined rules name
  • the process provided by this embodiment includes the following processing:
  • the SMF provides the local PCC rules to the UPF through a newly added rule management message;
  • the local PCC rules include: a predefined rule name, its associated PDR and PDR associated business processing strategy ( That is, the predefined PDR(s) ⁇ QER(s), FAR(s) and URR(s)).
  • S503 The UE initiates a PDU session establishment request.
  • the SMF obtains the dynamic PCC rule or the activated predefined PCC rule from the PCF.
  • the SMF can obtain information about dynamic PCC rules or activated predefined PCC rules from the PCF through the Npcf interface.
  • the SMF activates the configuration on the UPF by including the Activate Local Defined Rules IE (the message field of the activated local PCC rule) in the Create PDR IE in the PFCP session establishment request, or the Update PDR IE in the PFCP session modification request.
  • Local PCC rules (which can include a set of business processing strategies). Among them, UPF mounts the activated local PCC rules to the corresponding session context.
  • S506 The UE transmits the service message.
  • UPF searches for the PCC rule associated with the PDR matching the business packet from the PCC rules mounted under the session context. If there is no match in the PCC rules mounted under the session context, it searches the local rule pool and searches for the business report. The local PCC rule associated with the matching PDR.
  • UPF finds the matched local PCC rule from the local rule pool, mounts the successfully matched local PCC rule under the session context, and executes the matched local PCC rule.
  • UPF For URR, UPF generates a usage report and sends it to SMF, and SMF should be able to process the usage report. It should be noted that the URR ID used in the usage report triggered by the local PCC rules in the UPF must also be pre-configured on the CP side.
  • S510 The SMF deactivates the local PCC rules that have been activated in the UPF;
  • the SMF may include the Deactivate Local Defined Rules IE in the update PDR IE in the PFCP session modification request to notify the UPF to deactivate the local PCC rules of the relevant PDR.
  • UPF updates all relevant session contexts, for example, deletes deactivated local PCC rules mounted under the relevant session context.
  • FIG. 6 is an example diagram of a processing flow in which a UPF side message does not match a PCC rule in an embodiment of the application. As shown in Figure 6, the process of this embodiment may include the following processing:
  • S601 The UE initiates a PDU session establishment request.
  • the SMF obtains the dynamic PCC rule or the activated predefined PCC rule from the PCF.
  • the SMF can obtain information about dynamic PCC rules or activated predefined PCC rules from the PCF through the Npcf interface.
  • the SMF sends a PFCP session establishment request or a session modification request message, where the URR of the default rule enables the Solicited Application Reporting function.
  • the UPF receives the uplink message.
  • the UPF sends a Solicited Application Reporting to the SMF, which carries the SDF or Application ID of the current message.
  • the SMF requests a new dynamic PCC rule or an activated predefined PCC rule from the PCF.
  • the SMF issues new dynamic PCC rules or activated predefined PCC rules to the PCF.
  • UPF can process business messages according to new dynamic PCC rules or activated pre-defined PCC rules.
  • SMF can find the default rule with the lowest priority according to the APP ID carried in Solicited Application Reporting, and send the found default rule to UPF; then, UPF can follow the FAR of the default rule Perform message forwarding, discarding or caching.
  • Fig. 7 is a flowchart of a method for implementing policy and charging control provided by an embodiment of the application. As shown in Figure 7, the method provided in this embodiment includes:
  • the SMF issues local PCC rules to the UPF through a rule management message; where the local PCC rules are configured on the SMF, and the local PCC rules include: a predefined rule name, the PDR associated with the predefined rule name, and the business associated with the PDR Processing strategy.
  • the method of this embodiment may further include: the SMF sends a predefined PCC rule to the UPF through a rule management message, where the predefined PCC rule includes at least one of the following: a predefined rule name and Its associated business processing strategy, application identifier and its associated business processing strategy, traffic directional strategy identifier and its associated business processing strategy;
  • SMF is configured with at least one of the following: SDF and its associated predefined rule name, application detection filter and its associated application identifier, SDF and its associated traffic directional policy identifier, application identifier and its association The identifier of the traffic targeting policy.
  • the method of this embodiment may further include: when the session is created or after the session is created, after the predefined PCC rules are activated by the policy control function entity PCF, SMF activates the predefined definitions in the UPF in the following manner PCC rules:
  • the found pre-defined rule name, application identifier, or traffic directional policy identifier are sent to UPF through a session establishment request message or a session modification request message.
  • the PDR used to identify the service data flow referenced by the activated pre-defined PCC rule and the corresponding business are created Processing strategy, associating the PDR with a service processing strategy to obtain an activated predefined PCC rule, and sending the activated predefined PCC rule to the UPF.
  • the method of this embodiment may further include:
  • the SMF sends the pre-defined rule name of the activated local PCC rule to the UPF through the session establishment request message or the session modification request message; wherein the session establishment request message or the session modification request message includes the name of the pre-defined rule that is activated. Message field.
  • the method of this embodiment may further include: SMF sends a predefined rule name of the inactivated local PCC rule to the UPF through a session modification request message; wherein, the session modification The request message includes a message field carrying the name of the predefined rule that is inactivated.
  • the method of this embodiment may further include: when a message is transmitted through an established session, when the SMF receives a message sent by the UPF to indicate that the message has not yet matched the applicable PCC rule After the session report request message, the SMF sends the default rules to the UPF, or the SMF requests new dynamic PCC rules or activated pre-defined PCC rules from the PCF according to the message information carried in the session report request message, and adds the new The dynamic PCC rules or activated pre-defined PCC rules are issued to UPF.
  • the rule management message may include a PFCP PCC rule management request message.
  • SMF can issue or update local PCC rules, predefined PCC rules, or dynamic PCC rules to UPF through rule management messages.
  • the SMF can activate or deactivate local PCC rules or predefined PCC rules through a session establishment request or a session modification request message.
  • Fig. 8 is a flowchart of another method for implementing policy and charging control provided by an embodiment of the application. As shown in Figure 8, the method provided in this embodiment includes:
  • UPF receives the local PCC rules issued by the SMF through the rule management message;
  • local PCC rules are configured on the SMF, and the local PCC rules include: a predefined rule name, a PDR associated with the predefined rule name, and a business processing strategy associated with the PDR.
  • the method of this embodiment may further include: UPF receives the predefined PCC rules issued by the SMF through a rule management message; UPF saves the received predefined PCC rules; wherein, the predefined The PCC rule includes at least one of the following: a predefined rule name and its associated business processing strategy; an application identifier and its associated business processing strategy; a traffic directional strategy identifier and its associated business processing strategy.
  • the method of this embodiment may further include at least one of the following:
  • UPF receives the session establishment request message or the session modification request message sent by the SMF, and according to the predefined rule name, application identifier or traffic directional policy identifier corresponding to the activated predefined PCC rule carried in the session establishment request message or the session modification request message Search for the predefined PCC rule matching the predefined rule name, application identifier or traffic directional policy identifier from the saved predefined PCC rules, and associate the found predefined PCC rule with the PDR sent by the SMF. Contained in the session context of the established session;
  • UPF receives activated predefined PCC rules issued by SMF.
  • the method of this embodiment may further include: UPF receiving the session establishment request message or the session modification request message sent by the SMF, and according to the information carried in the session establishment request message or the session modification request message
  • the predefined rule name of the activated local PCC rule, the local PCC rule matching the predefined rule name is searched from the saved local PCC rule, and the found local PCC rule is mounted under the session context of the established session.
  • the method of this embodiment may further include: the UPF receives the session modification request message sent by the SMF, and according to the predefined rule name of the inactivated local PCC rule carried in the session modification request message, read Find and delete the local PCC rule matching the predefined rule name under the conversation context of the conversation.
  • the method of this embodiment may further include: when the message is transmitted through the established session, the UPF searches for the received message in the PCC rules mounted under the session context of the session.
  • the PCC rule applicable to the message when the PCC rule applicable to the message is not found in the session context, the PCC rule applicable to the message is searched from the saved local PCC rules; when in the session context or saved If the PCC rule applicable to the message is found in the local PCC rules of, the message is processed according to the found PCC rule.
  • the method of this embodiment may further include: when no PCC rule applicable to the message is found in the saved local PCC rules, sending to the SMF indicating that the message does not match Session report request message of applicable PCC rules; PCC rule re-issued after receiving the session message request message by the receiving SMF; when the message applies to the PCC rule re-issued by SMF, it is re-issued according to SMF
  • the PCC rules process the message; wherein the PCC rules reissued by the SMF include: default rules, new dynamic PCC rules, or activated pre-defined PCC rules.
  • the rule management message may include a PFCP PCC rule management request message.
  • SMF can issue or update local PCC rules, predefined PCC rules, or dynamic PCC rules to UPF through rule management messages.
  • the SMF can activate or deactivate local PCC rules or predefined PCC rules through a session establishment request or a session modification request message.
  • the embodiment of the present application also provides a device for implementing policy and charging control, including a first memory, a first processor, and a computer program stored on the first memory and running on the first processor.
  • the first processor The above-mentioned operation on the SMF side is realized when the computer program is executed.
  • the device for implementing policy and charging control can be applied to SMF, including: a first processor 910, a first memory 920, a bus system 930, and a first transceiver 940, where the The first processor 910, the first memory 920, and the first transceiver 940 are connected through the bus system 930, the first memory 920 is used to store instructions, and the first processor 910 is used to execute the first memory 920 to store Command to control the first transceiver 940 to send signals.
  • the first processor 910 may be a central processing unit (Central Processing Unit, referred to as "CPU"), and the first processor 910 may also be other general-purpose processors, digital signal processors (DSP), or application specific integrated circuits ( ASIC), ready-made programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the first memory 920 may include a read-only memory and a random access memory, and provides instructions and data to the first processor 910. A part of the first memory 920 may further include a non-volatile random access memory. For example, the first memory 920 may also store device type information.
  • the bus system 930 may also include a power bus, a control bus, and a status signal bus. However, for clarity of description, various buses are marked as the bus system 930 in FIG. 9.
  • the processing performed by the foregoing apparatus may be completed by an integrated logic circuit of hardware in the first processor 910 or instructions in the form of software. That is, the steps of the method disclosed in the embodiments of the present application may be embodied as being executed by a hardware processor, or executed by a combination of hardware and software modules in the processor.
  • the software module can be located in storage media such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the first memory 920, and the first processor 910 reads information in the first memory 920, and completes the steps of the foregoing method in combination with its hardware. To avoid repetition, it will not be described in detail here.
  • an embodiment of the present application also provides a device for implementing policy and charging control, including a second memory, a second processor, and a computer program stored in the second memory and running on the second processor.
  • a device for implementing policy and charging control including a second memory, a second processor, and a computer program stored in the second memory and running on the second processor.
  • the device for implementing policy and charging control can be applied to UPF, including: a second processor 1010, a second memory 1020, a bus system 1030, and a second transceiver 1040, where the The second processor 1010, the second memory 1020, and the second transceiver 1040 are connected through the bus system 1030, the second memory 1020 is used to store instructions, and the second processor 1010 is used to execute the second memory 1020 to store instructions. Command to control the second transceiver 1040 to send signals.
  • an embodiment of the present application also provides a computer-readable storage medium that stores a computer program that, when executed by a processor, implements the steps of the above-mentioned SMF-side or UPF-side method.
  • Such software may be distributed on a computer-readable medium, and the computer-readable medium may include a computer storage medium (or a non-transitory medium) and a communication medium (or a transitory medium).
  • the term computer storage medium includes volatile and non-volatile memory implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Sexual, removable and non-removable media.
  • Computer storage media include but are not limited to RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassette, tape, magnetic disk storage or other magnetic storage device, or Any other medium used to store desired information and that can be accessed by a computer.
  • communication media usually contain computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as carrier waves or other transmission mechanisms, and may include any information delivery media .

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

一种策略和计费控制的实现方法，包括：SMF将配置的本地PCC规则通过规则管理消息下发给UPF，UPF接收并保存本地PCC规则；其中，本地PCC规则包括：预定义规则名、该预定义规则名关联的PDR以及该PDR关联的业务处理策略。

Description

一种策略和计费控制的实现方法及装置
相关申请的交叉引用
本申请基于申请号为201910559276.6、申请日为2019年6月26日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此以引入方式并入本申请。
技术领域
本申请实施例涉及但不限于通信技术领域，尤指一种策略和计费控制的实现方法及装置。
背景技术
第五代移动通信技术(5G)的PCC(Policy and Charging Control，策略和计费控制)在3GPP(Third Generation Partnership Project，第三代合作伙伴计划)R15(Release 15，第15版)的TS 23.501中做了概述。虽然协议中针对预定义(predefined)PCC规则和动态(dynamic)PCC规则做了说明，但是仅提供了一种策略控制的框架，不能满足实施需求。
发明内容
本申请提供了一种策略和计费控制的实现方法及装置，可以完善5GC(5G Core，5G核心网)策略控制方案，以支持满足实施需求。
一方面，本申请提供一种策略和计费控制的实现方法，包括：会话管理功能实体(SMF)通过规则管理消息向用户面功能实体(UPF)下发本地策略和计费控制(PCC)规则；其中，所述SMF上配置有所述本地PCC规则，且所述本地PCC规则包括：预定义规则名、所述预定义规则名关联的包探测规则(PDR)以及所述PDR关联的业务处理策略。
另一方面，本申请提供一种策略和计费控制的实现方法，包括：UPF接收 SMF通过规则管理消息下发的本地PCC规则；所述UPF保存接收到的本地PCC规则；其中，所述SMF上配置有所述本地PCC规则，且所述本地PCC规则包括：预定义规则名、所述预定义规则名关联的PDR以及所述PDR关联的业务处理策略。
另一方面，本申请提供一种策略和计费控制的实现装置，包括：第一存储器、第一处理器以及存储在所述第一存储器上并可在所述第一处理器上运行的计算机程序，其中，所述第一处理器用于执行所述计算机程序以实现上述SMF侧的方法的步骤。
另一方面，本申请提供一种策略和计费控制的实现装置，包括：第二存储器、第二处理器以及存储在所述第二存储器上并可在所述第二处理器上运行的计算机程序，其中，所述第二处理器用于执行所述计算机程序以实现上述UPF侧的方法的步骤。
此外，本申请还提供一种计算机可读存储介质，存储有计算机程序，所述计算机程序被执行时实现上述SMF侧或UPF侧的方法的步骤。
本申请的其它特征和优点将在随后的说明书中阐述，并且，部分地从说明书中变得显而易见，或者通过实施本申请而了解。本申请的目的和其他优点可通过在说明书、权利要求书以及附图中所特别指出的结构来实现和获得。
附图说明
附图用来提供对本申请技术方案的进一步理解，并且构成说明书的一部分，与本申请的实施例一起用于解释本申请的技术方案，并不构成对本申请技术方案的限制。
图1为3GPP 23.501标准中的5G系统架构示意图；
图2为本申请实施例中的规则关系示意图；
图3为本申请实施例中SMF和UPF之间的交互示例图；
图4为本申请实施例中预定义PCC规则的配置和使用流程示例图；
图5为本申请实施例中本地PCC规则的配置和使用流程示例图；
图6为本申请实施例中在UPF侧报文未匹配到PCC规则的处理流程示例图；
图7为本申请实施例提供的一种策略和计费控制的实现方法的流程图；
图8为本申请实施例提供的另一种策略和计费控制的实现方法的流程图；
图9为本申请实施例提供的一种策略和计费控制的实现装置的示意图；
图10为本申请实施例提供的另一种策略和计费控制的实现装置的示意图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚明白，下文中将结合附图对本申请的实施例进行详细说明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。
在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行。并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
图1为3GPP 23.501标准中的5G系统架构示意图。图1描述了非漫游情况下的5G系统架构，使用参考点表示法显示各种网络功能如何相互作用。在图1中，5G系统架构包括以下结构：网络切片选择功能实体(NSSF，Network Slice Selection Function)、网络开放功能实体(NEF，Network Exposure Function)、网络存储库功能实体(NRF，Network Repository Function)、策略控制功能实体(PCF，Policy Control Function)、统一数据管理实体(UDM，Unified Data Management)、应用服务功能实体(AF，Application Function)、接入管理功能实体(AMF，Access and Mobility Management Function)、鉴权服务器功能实体(AUSF，Authentication Server Function)、会话管理功能实体(SMF，Session Management Function)、(无线)接入网络((R)AN，(Radio)Access Network)、用户面功能实体(UPF，User Plane Function)、用户设备(UE，User Equipment)、数据网络(DN，Data Network)。其中，Nnssf表示NSSF的接口，Nnef表示NEF的接口，Nnrf表示NRF的接口，Npcf表示PCF的接口，Nudm表示UDM的接口，Naf表示AF的接口，Nausf表示AUSF的接口，Namf表示AMF的接口，Nsmf表示SMF的接口。N1表示UE和AMF之间的参考点，N2表示(R)AN和AMF之间的参考点，N3表示(R)AN和UPF之间的参考点，N4表示SMF和UPF之间的参考点，N6表示UPF和DN之间的参考点，N9表示两个UPF之间的参考点。
目前的5G标准协议只提供了策略控制的框架，没有给出具体的流程实现，比如，业务流匹配PCC规则的处理方式，以及PCC规则匹配失败后该如何处理等。
本申请实施例提供一种策略和计费控制的实现方法及装置，在目前协议的 基础上，定义了SMF和UPF之间的本地PCC规则，通过本地PCC规则的使用来完善5GC策略控制方案；而且，本申请实施例还提供了预定义PCC规则和动态PCC规则的定义示例、SMF和UPF之间的PCC规则下发、匹配处理流程以及协作流程，从而支持满足具体实施需求。
图2为本申请实施例中的规则关系示意图。如图2所示，SMF可以包括PFDF(Packet Flow Description Function，包流描述功能)模块、会话管理模块和策略控制模块。其中，会话管理模块可以下发通道信息(Tunnel Info)、QER(QoS(Quality of Service，服务质量)Enforcement Rule，QoS执行规则)、URR(Usage Reporting Rule，使用报告规则)、FAR(Forwarding Action Rule，转发动作规则)；策略控制模块可以下发SDF(Service Data Flow，业务数据流)、ADC(Application Detection and Control，应用探测和控制)规则、QER、URR以及FAR。PDR(Packet Detection Rule，包探测规则)可以包括通道信息、SDF、ADC规则。PFDF模块下发的PFDs(Packet Flow Descriptions，包流描述)，可以通过应用标识符(Application Identifier(ID))关联ADC规则。在本申请实施例中，一个PCC规则可以包括PDR、QER、URR以及FAR。
本申请实施例提供SMF和UPF之间的策略和计费控制的实现过程。在本实施例中，SMF上配置有本地PCC规则，且SMF通过规则管理消息向UPF下发本地PCC规则；UPF接收并保存本地PCC规则；其中，本地PCC规则包括：预定义规则名(Predefined Rules Name)、该预定义规则名关联的PDR以及该PDR关联的业务处理策略。
在本实施例中，业务处理策略可以包括：一个或多个QER、一个或多个FAR和一个或多个URR；或者，流量定向策略(traffic steering policy)。在本实施例中，SMF和UPF具有相同的本地PCC规则，并同步维护本地PCC规则，有助于提高给业务报文匹配PCC规则的成功率，从而可以减少SMF和UPF之间的交互，并满足具体实施需求。
在一示例性实施方式中，SMF可以通过会话建立请求消息或会话修改请求消息向UPF发送激活的本地PCC规则的预定义规则名；其中，会话建立请求消息或会话修改请求消息中包括携带激活的预定义规则名的消息字段。UPF接收SMF发送的会话建立请求消息或会话修改请求消息，并根据会话建立请求消息或会话修改请求消息携带的激活的本地PCC规则的预定义规则名，从保存的本地PCC规则中查找匹配该预定义规则名的本地PCC规则，并将找到的本地PCC 规则挂载在所建立会话的会话上下文下。其中，携带激活的预定义规则名的消息字段(Active Local Defined Rules IE)可以包括：字段类型、长度信息、规划标识(Enterprise ID)以及激活的预定义规则名。
在本示例性实施方式中，SMF还可以通过会话修改请求消息向UPF发送失活的本地PCC规则的预定义规则名；其中，会话修改请求消息中包括携带失活的预定义规则名的消息字段。UPF接收SMF发送的会话修改请求消息，并根据会话修改请求消息携带的失活的本地PCC规则的预定义规则名，从对应的会话上下文下找到并删除匹配该预定义规则名的本地PCC规则。其中，携带失活的预定义规则名的消息字段(Deactive Local Defined Rules IE)可以包括：字段类型、长度信息、规划标识(Enterprise ID)以及失活的预定义规则名。
在本示例性实施方式中，通过新增用于指示激活或失活本地PCC规则的消息字段，可以针对相应的会话在UPF侧激活或失活本地PCC规则。
在一示例性实施方式中，SMF还可以通过规则管理消息向UPF下发预定义PCC规则；UPF可以接收并保存预定义PCC规则；其中，预定义PCC规则包括以下至少一项：预定义规则名及其关联的业务处理策略、应用标识符及其关联的业务处理策略、流量定向策略标识符及其关联的业务处理策略。其中，SMF上配置有以下至少一项信息：SDF及其关联的预定义规则名、应用检测过滤器(Application Detection Filter)及其关联的应用标识符、SDF及其关联的流量定向策略标识符(traffic steering policy identifier)、应用标识符及其关联的流量定向策略标识符。如此一来，当某一预定义PCC规则被激活或失活时，SMF可以确定提供哪些信息给UPF，以便UPF确定哪个预定义PCC规则被激活或失活。
在本示例性实施方式中，在会话创建时或会话创建后，当预定义PCC规则被PCF激活后，SMF可以通过以下方式激活UPF中的预定义PCC规则：
从配置在SMF上的信息中查找激活的预定义PCC规则对应的预定义规则名、应用标识符或流量定向策略标识符(比如，SMF从PCF接收到激活的PCC规则相关的SDF，根据SDF在配置的信息中查找是否存在其关联的预定义规则名或流量定向策略标识符)；
当查找到激活的PCC规则对应的预定义规则名、应用标识符或流量定向策略标识符，则通过会话建立请求消息或会话修改请求消息向UPF下发找到的预定义规则名、应用标识符或流量定向策略标识符，以便于UPF根据预定义规则名、应用标识符或流量定向策略标识符确定UPF上配置的哪个预定义PCC规则 被激活；
当没有查找到激活的PCC规则对应的预定义规则名、应用标识符或流量定向策略标识符，则SMF创建用于识别激活的预定义PCC规则所引用的服务数据流的PDR以及对应的业务处理策略(比如，包括QER(s)、FAR(s)及URR(s))，将创建的PDR与业务处理策略进行关联，得到激活的预定义PCC规则，并向UPF下发激活的预定义PCC规则。
在本示例性实施方式中，当UPF接收到SMF通过会话建立请求消息或会话修改请求消息下发的激活的预定义PCC规则对应的预定义规则名、应用标识符或流量定向策略标识符；则根据预定义规则名、应用标识符或流量定向策略标识符，从保存的预定义PCC规则中查找该预定义规则名、应用标识符或流量定向策略标识符所匹配的预定义PCC规则，并将查找到的预定义PCC规则与SMF下发的PDR关联后，挂载在所建立会话的会话上下文下。在本示例中，UPF根据保存的预定义PCC规则以及SMF下发的相应信息来确定激活的预定义PCC。
在本示例性实施方式中，当UPF接收到SMF下发的激活的预定义PCC规则，则UPF可以将接收到的激活的预定义PCC规则挂载到相应会话的会话上下文下。在本示例中，激活的预定义PCC规则可以完全由SMF下发。
在一示例性实施方式中，SMF可以从PCF获取动态PCC规则，并在会话建立时向UPF下发适用于所建立的会话的动态PCC规则(比如，SMF可以通过规则管理消息向UPF下发动态PCC规则)；其中，SMF下发的动态PCC规则包括以下至少一项：业务处理策略；流量定向策略标识符。其中，SMF侧可以根据应用标识符或SDF(s)确定动态PCC规则的业务处理策略(比如，包括QER(s)、FAR(s)及URR(s))；SMF侧还可以根据SDF(s)或应用标识符，确定对应的流量定向策略标识符。UPF侧可以配置有以下至少一项：应用标识符和对应的PFD(s)、流量定向策略标识符及其关联的流量定向策略。其中，UPF接收SMF下发的动态PCC规则的业务处理策略后，可以确定其关联的PDR，并将关联PDR后的业务处理策略挂载在所建立会话的会话上下文下。
在一示例性实施方式中，在会话建立后，通过建立的会话进行报文传输时，UPF可以在该会话的会话上下文下挂载的PCC规则中查找接收到的报文适用的PCC规则；当在该会话上下文下没有找到该报文适用的PCC规则，则UPF从保存的本地PCC规则中查找该报文适用的PCC规则；当在该会话上下文或保存的本地PCC规则中找到该报文适用的PCC规则，则UPF根据找到的PCC规则处 理该报文。其中，当在保存的本地PCC规则中找到该报文适用的PCC规则，则UPF将找到的本地PCC规则挂载在该会话上下文下。
在本示例性实施方式中，当在保存的本地PCC规则中没有找到该报文适用的PCC规则，则UPF向SMF发送用于指示该报文未匹配到适用的PCC规则的会话报告请求消息。当SMF接收到UFP发送的用于指示该报文尚未匹配到适用的PCC规则的会话报告请求消息后，SMF将默认规则下发给UPF，或者，SMF根据该会话报告请求消息携带的报文信息，向PCF请求新的动态PCC规则或激活的预定义PCC规则，并将新的动态PCC规则或激活的预定义PCC规则下发给UPF。UPF接收SMF收到会话报文请求消息后重新下发的PCC规则，当该报文适用SMF重新下发的PCC规则，则UPF根据SMF重新下发的PCC规则处理该报文；其中，SMF重新下发的PCC规则包括：默认规则、新的动态PCC规则、或激活的预定义PCC规则。其中，UPF可以将SMF重新下发的PCC规则挂载在该会话的会话上下文下，并根据重新下发的PCC规则处理该报文。当SMF重新下发的PCC规则仍不适用于该报文，则UPF确定PCC规则匹配失败。
在本示例性实施例方式中，通过多层次的PCC规则匹配过程可以提升报文匹配PCC规则的成功率。
在一示例性实施方式中，规则管理消息可以包括PFCP(Packet Forwarding Control Protocol，包转发控制协议)PCC规则管理请求消息。其中，SMF可以通过Sxb、Sxc和N4接口发送PFCP PCC规则管理请求消息，以向UPF提供本地PCC规则、预定义PCC规则或动态PCC规则。UPF可以通过Sxb、Sxc和N4接口发送PFCP PCC规则管理响应消息给SMF，作为对PFCP PCC规则管理请求消息的响应。
图3为本申请实施例中SMF和UPF之间的交互示例图。下面参照图3通过一个示例对本申请实施例提供的策略和计费控制的实现方法进行举例说明。
在本示例性实施例中，SMF和UPF之间可以定义以下三种类型的PCC规则：预定义PCC规则、动态PCC规则以及本地PCC规则。表1所示为本实施例中的规则内容表。表1所示的每一行规则内容可以对应一种业务场景。而且，表1仅示意出各个PCC规则的框架，并未给出实际的参数或策略信息。实际的参数或策略信息可以根据实际应用场景确定，故于此不再赘述。
在本实施例中，预定义PCC规则定义如下：第一、如果预定义PCC规则包含一个应用标识符(application identifier，APP ID)，且对应的应用检测过滤器 (application detection filters)被配置在UPF，SMF应提供对应的APP ID给UPF；第二、如果预定义PCC规则包含流量定向策略标识符(traffic steering policy identifier(s))，SMF应提供给UPF；第三、如果预定义PCC规则包含服务数据流过滤器(service data flow filter(s))，SMF应提供给UPF；第四、如果预定义PCC规则包含为UPF上预配置的流量处理的策略，SMF应通过Rule ID(s)激活流量处理策略。
如表1所示，可以在SMF中配置key为application detection filter(s)，value为application identifier；在UPF中配置key为application identifier，value为predefined QER(s),FAR(s)and URR(s)。
在SMF中配置key为SDF(s)or application identifier，value为traffic steering policy identifier(s)；在UPF中配置key值为traffic steering policy identifier(s)，value为traffic steering policy。
在SMF中配置key为SDF(s)，value为QER(s),FAR(s)and URR(s)；SMF可以将预定义PCC规则提供给UPF。
在SMF中配置key为SDF(s)，value为预定义规则名(Predefined Rules Name)；在UPF中配置key为Predefined Rules Name，value为predefined QER(s),FAR(s)and URR(s)。
在本实施例中，动态PCC规则定义如下：当SMF从PCF接收到动态PCC策略，策略包含application identifier或在UPF中用于流量处理的参数，则：第一、如果SMF配置了application detection filter，SMF在service data flow filter中把application detection filter带给UPF；第二、在UPF中提供了application detection filters，SMF在service data flow filter中把application identifier带给UPF。
如表1所示，在SMF中下发key值为application identifier，value为QER(s),FAR(s)and URR(s)；在UPF中通过key为application identifier和PFD(s)匹配SMF下发的QER(s),FAR(s)and URR(s)。
在SMF中下发key值为SDF(s)或application identifier，value为traffic steering policy identifier(s)；在UPF中通过key为traffic steering policy identifier(s)，value为traffic steering policy匹配。
在本实施例中，针对本地PCC规则，如表1所示，可以在SMF配置key为Predefined Rules Name，value为PDR(s)→QER(s),FAR(s)and URR(s)(即PDR(s)关联的QER(s)、FAR(s)及URR(s))，在UPF中具有同样的本地PCC规 则，达到SMF和UPF的本地PCC规则配置一致。
Figure PCTCN2020087078-appb-000001
表1 规则内容表
如图3所示，本实施例中SMF和UPF之间的交互包括以下处理：
S301、UPF注册成功后，SMF通过新增的规则管理消息(例如，PFCP PCC  Rules Management Request)下发预定义PCC规则和本地PCC规则，UPF将接收到的预定义PCC规则保存在本地的预定义规则池中，将接收到的本地PCC规则保存在本地规则池中。
在本示例中，如图3所示，UPF保存的每一个预定义PCC规则可以包括：预定义规则名(例如，PreDefName1、PreDefName2、PreDefNamen)和其关联的QERs、URRs及FAR。UPF保存的每一个本地PCC规则可以包括：预定义规则名(例如，UniID21、UniID22、UniID2n)、该预定义规则名关联的PDR(包括ADC和SDF)以及该PDR关联的QERs、URRs及FAR。
S302、在用户接入时，会话建立时，SMF向UPF下发动态PCC规则，UPF将动态PCC规则挂载在对应的会话上下文下。
如图3所示，在本示例中，UPF保存的动态PCC规则可以包括：规则名(例如，DynID1、DynID2)、该规则名关联的PDR(包括ADC和SDF)以及该PDR关联的QERs、URRs及FAR。
S303、在会话建立之后，SMF下发激活的预定义规则名，UPF根据激活的预定义规则名到预定义规则池中复制一份与该预定义规则名匹配的预定义PCC规则，再给匹配到的预定义PCC规则加上SMF下发的PDR后挂载在会话上下文下。
在本示例中，激活的预定义规则名为PreDefName2和PreDefNamen，则将这两个预定义规则名对应的预定义PCC规则加上SMF下发的PDR后挂载在会话上下文下。
S304、在通过建立的会话发起业务后，UPF根据接收到的报文进行PDR匹配。即，判断报文的PFD匹配哪个PDR，则匹配到的PDR关联的PCC规则即为与该报文匹配的PCC规则。
若从会话上下文给该报文匹配到PCC规则(即，从会话上下文下挂载的PCC规则中找到与该报文匹配的PCC规则)，则执行S307；若在会话上下文没有匹配到PCC规则，则UPF到本地规则池中匹配PCC规则，若从本地规则池找到与该报文匹配的本地PCC规则，则将匹配到的本地PCC规则复制一份后挂载在会话上下文下(比如，在图3中，匹配到预定义规则名为UniID21和UniID22的两个本地PCC规则)，然后执行S307；若从本地规则池也没有匹配到PCC规则，则继续执行S305。
S305、若无法从会话上下文和本地规则池匹配到PCC规则，则UPF发起 PFCP会话报告请求(Session Report Request)消息给SMF，其中携带当前业务的五元组(比如，源地址、源端口号、目的地址、目的端口号、协议号)或APP ID；而且，UPF在本地缓存接收到的报文，以便于后续处理。
S306、SMF根据UPF上报的信息，进行PCC规则匹配，并下发SMF匹配到PCC规则给UPF，然后回复PFCP会话报告响应(Session Report Response)消息给UPF。
其中，SMF可以根据UPF上报的信息，选择配置的优先级最低的默认规则，或者，SMF可以向PCF请求新的动态PCC规则或激活预定义PCC规则。
比如，在一示例中，SMF可以根据UPF上报的信息，从SMF维护的低优先级的默认规则中匹配到预定义规则名为UniIDn的默认规则。
在本示例中，UPF收到SMF重新下发的PCC规则后，可以取出缓存的报文，并按新下发的PCC规则处理该报文(例如，转发或丢包)。当SMF重新下发的PCC规则仍不匹配业务报文，则返回处理失败。
S307、当URR定时定量上报时，SMF根据SEID(会话上下文ID)和URR ID进行计费。
S308、当本地PCC规则或预定义PCC规则有修改时，SMF可以通知UPF，UPF同步更新已有会话的会话上下文下挂载的相应PCC规则。
在一示例中，SMF可以通过PFCP会话修改请求消息下发激活或失活的本地PCC规则、预定义PCC规则给UPF。
在本示例性实施例中，在S301中，SMF可以通过Sxb、Sxc和N4接口发送PFCP PCC规则管理请求消息。表2为PFCP PCC规则管理请求消息的消息字段(Information Element，IE)说明。
Figure PCTCN2020087078-appb-000002
Figure PCTCN2020087078-appb-000003
Figure PCTCN2020087078-appb-000004
表2
其中，UPF可以通过Sxb、Sxc和N4接口发送PFCP PCC规则管理响应消息给SMF，作为对PFCP PCC规则管理请求消息的响应。表3为PFCP PCC规则管理响应消息的消息字段(IE)说明。
Figure PCTCN2020087078-appb-000005
Figure PCTCN2020087078-appb-000006
表3
在本示例性实施例中，用于激活本地PCC规则的消息字段可以参照表4所示的方式进行编码，该消息字段应指明一个或多个本地PCC规则的预定义规则名，这些本地PCC规则需要在UPF中激活。
Figure PCTCN2020087078-appb-000007
表4
在本示例性实施例中，用于失活本地PCC规则的消息字段可以参照表5所 示的方式进行编码，该消息字段应指明一个或多个本地PCC规则的预定义规则名，这些本地PCC规则需要在UPF中失活。
Figure PCTCN2020087078-appb-000008
表5
在表4和表5中，预定义规则名应编码为八进制字符串。
下面参照图4至图6对图3所示的交互流程的实现细节进行举例说明。在本示例性实施例中，UPF中PCC规则的来源可以分以下三种：完全由用户面(CP，Control Plane)下发的PCC规则；由UPF配置的预定义PCC规则；由UPF配置的本地PCC规则。
在一示例中，当预定义PCC规则完全由CP下发时，UPF看不到本地PCC规则、预定义PCC规则与动态PCC规则的区别。其中，SMF(作为CP)可以通过以下方式激活UPF中的预定义PCC规则：
确定激活的预定义PCC规则所引用的业务数据application IDs以及相应的QoS和计费控制信息；如果application不存在，则创建必要的PDR以识别预定义PCC规则所引用的服务数据流；创建必要的QER以在相应的业务流或应用级上执行QoS；如果由于承载绑定和QoS控制而需要创建新的FAR以转发检测到的业务流或应用业务，或者，如果在预定义PCC规则中包括重定向或应用业务转向控制，则创建必要的FAR；为每个monitoring key(监控键值)，charging key(计费键值)，charging key和Service ID(服务标识符)，或charging key、Sponsor ID和Application Service Provider ID(应用服务提供者标识符)(如果包括在预定义PCC规则中)创建必要的URR；然后，将创建的URR与新创建的PDR相关联，将已有的FAR或新的FAR与新创建的PDR相关联；然后，SMF可以直接下发激活的预定义PCC规则给UPF。
图4为本申请实施例中预定义PCC规则的配置和使用流程示例图。在本示例中，由UPF配置的预定义PCC规则的业务处理策略，PDR(SDF或ADC)由SMF下发，UPF和SMF之间通过交互预定义规则名来激活预定义PCC规则。
如图4所示，本实施例提供的流程包括以下处理：
S401、SMF通过新增的规则管理消息向UPF提供预定义PCC规则，其中，预定义PCC规则包括：预定义规则名及其关联的业务处理策略(比如，预定义的QER(s)、FAR(s)及URR(s))。
S402、UPF保存预定义PCC规则至本地的预定义规则池。
S403、UE发起PDU(Protocol Data Unit，协议数据单元)会话建立请求。
S404、SMF到PCF中获取动态PCC规则或者激活的预定义PCC规则。其中，SMF可以通过Npcf接口从PCF获取动态PCC规则或激活的预定义PCC规则的信息。
S405、SMF通过在PFCP会话建立请求中的创建PDR IE，或者在PFCP会话修改请求中的更新PDR IE中包括PDR->Activate Predefined Rules IE(即PDR关联的激活的预定义PCC规则的消息字段)来激活配置在UPF上的预定义PCC规则。
S406、UPF将接收到的PDR关联到激活的预定义PCC规则，即将PDR关联到激活的预定义的QER(s)、FAR(s)及URR(s)。
其中，UPF可以根据PDR->Activate Predefined Rules IE中携带的信息在预定义规则池中匹配预定义PCC规则，将SMF下发的PDR关联匹配到的预定义PCC规则，并挂载到相应的会话上下文下。
S407、UE传输业务流数据。
S408、对于与激活的预定义PCC规则关联的PDR匹配的业务报文，UPF执行该激活的预定义PCC规则。对于URR，UPF产生用量报告并发送给SMF，SMF可以处理用量报告。需要说明的是：在UPF中由预定义PCC规则触发的用量报告中使用的URR ID也必须在CP侧预先配置。
S409、SMF去激活在UPF中激活的预定义PCC规则；
其中，SMF可以在PFCP会话修改请求中的更新PDR IE中包括Deactivate Predefined Rules IE，以通知UPF去激活相关PDR关联的预定义PCC规则。
其中，Activate Predefined Rules IE和Deactivate Predefined Rules IE的格式类似于表4和表5，故于此不再赘述。
S410、UPF更新所有相关的会话上下文，比如，删除会话上下文下挂载的去激活的预定义PCC规则。
图5为本申请实施例本地PCC规则的配置和使用流程示例图。在本示例中，本地PCC规则完全在UPF配置，UPF和SMF之间通过交互预定义规则名(Predefined Rules name)来激活本地PCC规则。
如图5所示，本实施例提供的流程包括以下处理：
S501、根据运营商配置的本地PCC规则，SMF通过新增的规则管理消息向UPF提供本地PCC规则；其中，本地PCC规则包括：预定义规则名、其关联的PDR及PDR关联的业务处理策略(即，预定义的PDR(s)→QER(s)，FAR(s)及URR(s))。
S502、UPF保存本地PCC规则至本地规则池。
S503、UE发起PDU会话建立请求。
S504、SMF从PCF中获取动态PCC规则或者激活的预定义PCC规则。
其中，SMF可以通过Npcf接口从PCF获取动态PCC规则或激活的预定义PCC规则的信息。
S505、SMF通过在PFCP会话建立请求中的创建PDR IE，或者在PFCP会话修改请求中的更新PDR IE中包括Activate Local Defined Rules IE(即激活的本地PCC规则的消息字段)来激活配置在UPF上的本地PCC规则(其中，可以包括一组业务处理策略)。其中，UPF将激活的本地PCC规则挂载到相应的会话上下文下。
S506、UE传输业务报文。
S507、UPF从会话上下文下挂载的PCC规则中查找与业务报文匹配的PDR关联的PCC规则，若在会话上下文下挂载的PCC规则中没有匹配到，则从本地规则池查找与业务报文匹配的PDR关联的本地PCC规则。
S508、UPF从本地规则池查找到匹配的本地PCC规则，将匹配成功的本地PCC规则挂载到会话上下文下，并执行该匹配成功的本地PCC规则。
S509、对于URR，UPF产生用量报告并发送给SMF，SMF应能处理用量报告。需要说明的是：在UPF中由本地PCC规则触发的用量上报中使用的URR ID也必须在CP侧预先配置。
S510、SMF去激活在UPF中已经激活的本地PCC规则；
其中，SMF可以在PFCP会话修改请求中的更新PDR IE中包括Deactivate  Local Defined Rules IE，以通知UPF去激活相关PDR的本地PCC规则。
其中，Activate Local Defined Rules IE和Deactivate Local Defined Rules IE的格式参照表4和表5，故于此不再赘述。
S511、UPF更新所有相关的会话上下文，比如，删除相关的会话上下文下挂载的去激活的本地PCC规则。
图6为本申请实施例中在UPF侧报文未匹配到PCC规则的处理流程示例图。如图6所示，本实施例的流程可以包括以下处理：
S601、UE发起PDU会话建立请求。
S602、SMF从PCF中获取动态PCC规则或者激活的预定义PCC规则。
其中，SMF可以通过Npcf接口从PCF获取动态PCC规则或激活的预定义PCC规则的信息。
S603、SMF发送PFCP会话建立请求或会话修改请求消息，其中，默认规则的URR打开Solicited Application Reporting功能。
S604、UPF收到上行报文。
S605、UPF在会话上下文下挂载的PCC规则和本地规则池内的PCC规则中均未查找到与业务报文匹配的PDR关联的PCC规则。
S606、UPF向SMF发送Solicited Application Reporting，其中携带当前报文的SDF或Application ID。
S607、SMF向PCF要新的动态PCC规则或激活的预定义PCC规则。
S608、SMF向PCF下发新的动态PCC规则或激活的预定义PCC规则。UPF可以根据新的动态PCC规则或激活的预定义PCC规则处理业务报文。
S609、业务报文正常转发。
然而，本申请对此并不限定。在其他实现方式中，在S606之后，SMF可以根据Solicited Application Reporting携带的APP ID，查找优先级最低的默认规则，并将查找到的默认规则下发给UPF；然后，UPF可以根据默认规则的FAR进行报文转发、丢弃或缓存。
图7为本申请实施例提供的一种策略和计费控制的实现方法的流程图。如图7所示，本实施例提供的方法包括：
S701、SMF通过规则管理消息向UPF下发本地PCC规则；其中，SMF上配置有本地PCC规则，且本地PCC规则包括：预定义规则名、该预定义规则名关联的PDR以及该PDR关联的业务处理策略。
在一示例性实施方式中，本实施例的方法还可以包括：SMF通过规则管理消息向所述UPF下发预定义PCC规则，其中，预定义PCC规则包括以下至少一项：预定义规则名及其关联的业务处理策略、应用标识符及其关联的业务处理策略、流量定向策略标识符及其关联的业务处理策略；
其中，SMF上配置有以下至少一项：SDF及其关联的预定义规则名、应用检测过滤器及其关联的应用标识符、SDF及其关联的流量定向策略标识符、应用标识符及其关联的流量定向策略标识符。
在一示例性实施方式中，本实施例的方法还可以包括：在会话创建时或会话创建后，当预定义PCC规则被策略控制功能实体PCF激活后，SMF通过以下方式激活UPF中的预定义PCC规则：
从SMF上配置的信息中查找所述激活的预定义PCC规则对应的预定义规则名、应用标识符或流量定向策略标识符；
当查找到激活的预定义PCC规则对应的预定义规则名、应用标识符或流量定向策略标识符，则通过会话建立请求消息或会话修改请求消息向UPF发送所述查找到的预定义规则名、应用标识符或流量定向策略标识符；
当未查找到激活的预定义PCC规则对应的预定义规则名、应用标识符或流量定向策略标识符，则创建用于识别激活的预定义PCC规则所引用的服务数据流的PDR以及对应的业务处理策略，将所述PDR与业务处理策略进行关联，得到激活的预定义PCC规则，并向所述UPF发送所述激活的预定义PCC规则。
在一示例性实施方式中，在S701之后，本实施例的方法还可以包括：
S702、SMF通过会话建立请求消息或会话修改请求消息向UPF发送激活的本地PCC规则的预定义规则名；其中，会话建立请求消息或会话修改请求消息中包括携带激活的所述预定义规则名的消息字段。
在一示例性实施方式中，在S702之后，本实施例的方法还可以包括：SMF通过会话修改请求消息向所述UPF发送失活的本地PCC规则的预定义规则名；其中，所述会话修改请求消息中包括携带失活的所述预定义规则名的消息字段。
在一示例性实施方式中，本实施例的方法还可以包括：在通过建立的会话进行报文传输时，当SMF接收到UPF发送的用于指示所述报文尚未匹配到适用的PCC规则的会话报告请求消息后，SMF将默认规则下发给UPF，或者，SMF根据所述会话报告请求消息携带的报文信息，向PCF请求新的动态PCC规则或激活的预定义PCC规则，并将新的动态PCC规则或激活的预定义PCC规则下 发给UPF。
在一示例性实施方式中，规则管理消息可以包括PFCP PCC规则管理请求消息。其中，SMF可以通过规则管理消息向UPF下发或更新本地PCC规则、预定义PCC规则或动态PCC规则。在会话建立时或会话建立后，SMF可以通过会话建立请求或会话修改请求消息来激活或去激活本地PCC规则或预定义PCC规则。
关于本实施例提供的方法的相关描述可以参照图3至图6所示实施例的说明，故于此不再赘述。
图8为本申请实施例提供的另一种策略和计费控制的实现方法的流程图。如图8所示，本实施例提供的方法包括：
S801、UPF接收SMF通过规则管理消息下发的本地PCC规则；
S802、UPF保存接收到的本地PCC规则；
其中，SMF上配置有本地PCC规则，且本地PCC规则包括：预定义规则名、该预定义规则名关联的PDR以及该PDR关联的业务处理策略。
在一示例性实施方式中，本实施例的方法还可以包括：UPF接收所述SMF通过规则管理消息下发的预定义PCC规则；UPF保存接收到的预定义PCC规则；其中，所述预定义PCC规则包括以下至少一项：预定义规则名及其关联的业务处理策略；应用标识符及其关联的业务处理策略；流量定向策略标识符及其关联的业务处理策略。
在一示例性实施方式中，本实施例的方法还可以包括以下至少之一：
UPF接收SMF发送的会话建立请求消息或会话修改请求消息，根据所述会话建立请求消息或会话修改请求消息携带的激活的预定义PCC规则对应的预定义规则名、应用标识符或流量定向策略标识符，从保存的预定义PCC规则中查找匹配所述预定义规则名、应用标识符或流量定向策略标识符的预定义PCC规则，并将找到的预定义PCC规则与SMF发送的PDR关联后挂载在所建立会话的会话上下文下；
UPF接收SMF下发的激活的预定义PCC规则。
在一示例性实施方式中，在S802之后，本实施例的方法还可以包括：UPF接收SMF发送的会话建立请求消息或会话修改请求消息，根据所述会话建立请求消息或会话修改请求消息携带的激活的本地PCC规则的预定义规则名，从保存的本地PCC规则中查找匹配所述预定义规则名的本地PCC规则，并将找到的 本地PCC规则挂载在所建立会话的会话上下文下。
在一示例性实施方式中，本实施例的方法还可以包括：UPF接收SMF发送的会话修改请求消息，根据所述会话修改请求消息携带的失活的本地PCC规则的预定义规则名，从所述会话的会话上下文下找到并删除匹配所述预定义规则名的本地PCC规则。
在一示例性实施方式中，本实施例的方法还可以包括：在通过建立的会话进行报文传输时，UPF在所述会话的会话上下文下挂载的PCC规则中查找所述接收到的报文适用的PCC规则；当在所述会话上下文下没有找到所述报文适用的PCC规则，则从保存的本地PCC规则中查找所述报文适用的PCC规则；当在所述会话上下文或保存的本地PCC规则中找到所述报文适用的PCC规则，则根据找到的PCC规则处理所述报文。
在本示例性实施方式中，本实施例的方法还可以包括：当在保存的本地PCC规则中没有找到所述报文适用的PCC规则，则向SMF发送用于指示所述报文未匹配到适用的PCC规则的会话报告请求消息；接收SMF收到所述会话报文请求消息后重新下发的PCC规则；当所述报文适用SMF重新下发的PCC规则，则根据SMF重新下发的PCC规则处理所述报文；其中，SMF重新下发的PCC规则包括：默认规则、新的动态PCC规则、或激活的预定义PCC规则。
在一示例性实施方式中，规则管理消息可以包括PFCP PCC规则管理请求消息。其中，SMF可以通过规则管理消息向UPF下发或更新本地PCC规则、预定义PCC规则或动态PCC规则。在会话建立时或会话建立后，SMF可以通过会话建立请求或会话修改请求消息来激活或去激活本地PCC规则或预定义PCC规则。
关于本实施例提供的方法的相关描述可以参照图3至图6所示实施例的说明，故于此不再赘述。
本申请实施例还提供一种策略和计费控制的实现装置，包括第一存储器、第一处理器及存储在第一存储器上并可在第一处理器上运行的计算机程序，第一处理器执行所述计算机程序时实现上述SMF侧的操作。
如图9所示，在一个示例中，策略和计费控制的实现装置可应用于SMF，包括：第一处理器910、第一存储器920、总线系统930和第一收发器940，其中，该第一处理器910、该第一存储器920和该第一收发器940通过该总线系统930相连，该第一存储器920用于存储指令，该第一处理器910用于执行该第一 存储器920存储的指令，以控制该第一收发器940发送信号。
应理解，第一处理器910可以是中央处理单元(Central Processing Unit，简称为“CPU”)，第一处理器910还可以是其他通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现成可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
第一存储器920可以包括只读存储器和随机存取存储器，并向第一处理器910提供指令和数据。第一存储器920的一部分还可以包括非易失性随机存取存储器。例如，第一存储器920还可以存储设备类型的信息。
总线系统930除包括数据总线之外，还可以包括电源总线、控制总线和状态信号总线等。但是为了清楚说明起见，在图9中将各种总线都标为总线系统930。
在实现过程中，上述装置所执行的处理可以通过第一处理器910中的硬件的集成逻辑电路或者软件形式的指令完成。即本申请实施例所公开的方法的步骤可以体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等存储介质中。该存储介质位于第一存储器920，第一处理器910读取第一存储器920中的信息，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
此外，本申请实施例还提供一种策略和计费控制的实现装置，包括第二存储器、第二处理器及存储在第二存储器上并可在第二处理器上运行的计算机程序，第二处理器执行所述计算机程序时实现上述UPF侧的操作。
如图10所示，在一个示例中，策略和计费控制的实现装置可应用于UPF，包括：第二处理器1010、第二存储器1020、总线系统1030和第二收发器1040，其中，该第二处理器1010、该第二存储器1020和该第二收发器1040通过该总线系统1030相连，该第二存储器1020用于存储指令，该第二处理器1010用于执行该第二存储器1020存储的指令，以控制该第二收发器1040发送信号。
图10所示的各个器件的相关说明可以参照图9所示的对应器件的描述，故于此不再赘述。
此外，本申请实施例还提供一种计算机可读存储介质，存储有计算机程序，所述计算机程序被处理器执行时实现上述SMF侧或UPF侧的方法的步骤。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些组件或所有组件可以被实施为由处理器，如数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。

Claims (18)

  1. 一种策略和计费控制的实现方法，包括：
    会话管理功能实体SMF通过规则管理消息向用户面功能实体UPF下发本地策略和计费控制PCC规则；
    其中，所述SMF上配置有所述本地PCC规则，且所述本地PCC规则包括：预定义规则名、所述预定义规则名关联的包探测规则PDR以及所述PDR关联的业务处理策略。
  2. 根据权利要求1所述的方法，其中，所述方法还包括：
    所述SMF通过规则管理消息向所述UPF下发预定义PCC规则，其中，所述预定义PCC规则包括以下至少一项：预定义规则名及其关联的业务处理策略、应用标识符及其关联的业务处理策略、流量定向策略标识符及其关联的业务处理策略；
    其中，所述SMF上配置有以下至少一项：业务数据流SDF及其关联的预定义规则名、应用检测过滤器及其关联的应用标识符、SDF及其关联的流量定向策略标识符、应用标识符及其关联的流量定向策略标识符。
  3. 根据权利要求2所述的方法，其中，所述方法还包括：
    在会话创建时或会话创建后，当预定义PCC规则被策略控制功能实体PCF激活后，所述SMF通过以下方式激活所述UPF中的预定义PCC规则：
    从SMF上配置的信息中查找所述激活的预定义PCC规则对应的预定义规则名、应用标识符或流量定向策略标识符；
    当查找到所述激活的预定义PCC规则对应的预定义规则名、应用标识符或流量定向策略标识符，则通过会话建立请求消息或会话修改请求消息向所述UPF发送所述查找到的预定义规则名、应用标识符或流量定向策略标识符；
    当未查找到所述激活的预定义PCC规则对应的预定义规则名、应用标识符或流量定向策略标识符，则创建用于识别激活的预定义PCC规则所引用的服务数据流的PDR以及对应的业务处理策略，将所述PDR与业务处理策略进行关联，得到激活的预定义PCC规则，并向所述UPF发送所述激活的预定义PCC规则。
  4. 根据权利要求1所述的方法，其中，所述方法还包括：
    所述SMF通过会话建立请求消息或会话修改请求消息向所述UPF发送激活的本地PCC规则的预定义规则名；其中，所述会话建立请求消息或会话修改请求消息中包括携带激活的所述预定义规则名的消息字段。
  5. 根据权利要求4所述的方法，其中，所述方法还包括：
    所述SMF通过会话修改请求消息向所述UPF发送失活的本地PCC规则的预定义规则名；其中，所述会话修改请求消息中包括携带失活的所述预定义规则名的消息字段。
  6. 根据权利要求1至5中任一项所述的方法，其中，所述方法还包括：
    在通过建立的会话进行报文传输时，当所述SMF接收到所述UPF发送的用于指示所述报文尚未匹配到适用的PCC规则的会话报告请求消息后，所述SMF将默认规则下发给所述UPF，或者，所述SMF根据所述会话报告请求消息携带的报文信息，向策略控制功能实体PCF请求新的动态PCC规则或激活的预定义PCC规则，并将新的动态PCC规则或激活的预定义PCC规则下发给所述UPF。
  7. 根据权利要求6所述的方法，其中，所述规则管理消息包括包转发控制协议PFCP PCC规则管理请求消息。
  8. 一种策略和计费控制的实现方法，包括：
    用户面功能实体UPF接收会话管理功能实体SMF通过规则管理消息下发的本地策略和计费控制PCC规则；
    所述UPF保存接收到的本地PCC规则；
    其中，所述SMF上配置有所述本地PCC规则，且所述本地PCC规则包括：预定义规则名、所述预定义规则名关联的包探测规则PDR以及所述PDR关联的业务处理策略。
  9. 根据权利要求8所述的方法，其中，所述方法还包括：
    所述UPF接收所述SMF通过规则管理消息下发的预定义PCC规则；
    所述UPF保存接收到的预定义PCC规则；
    其中，所述预定义PCC规则包括以下至少一项：预定义规则名及其关联的业务处理策略；应用标识符及其关联的业务处理策略；流量定向策略标识符及其关联的业务处理策略。
  10. 根据权利要求9所述的方法，其中，所述方法还包括以下至少之一：
    所述UPF接收所述SMF发送的会话建立请求消息或会话修改请求消息，根据所述会话建立请求消息或会话修改请求消息携带的激活的预定义PCC规则对应的预定义规则名、应用标识符或流量定向策略标识符，从保存的预定义PCC规则中查找匹配所述预定义规则名、应用标识符或流量定向策略标识符的预定义PCC规则，并将找到的预定义PCC规则与所述SMF发送的PDR关联后挂载在所建立会话的会话上下文下；
    所述UPF接收所述SMF下发的激活的预定义PCC规则。
  11. 根据权利要求8所述的方法，其中，所述方法还包括：
    所述UPF接收所述SMF发送的会话建立请求消息或会话修改请求消息，根据所述会话建立请求消息或会话修改请求消息携带的激活的本地PCC规则的预定义规则名，从保存的本地PCC规则中查找匹配所述预定义规则名的本地PCC规则，并将找到的本地PCC规则挂载在所建立会话的会话上下文下。
  12. 根据权利要求11所述的方法，其中，所述方法还包括：
    所述UPF接收所述SMF发送的会话修改请求消息，根据所述会话修改请求消息携带的失活的本地PCC规则的预定义规则名，从所述会话的会话上下文下找到并删除匹配所述预定义规则名的本地PCC规则。
  13. 根据权利要求8至12中任一项所述的方法，其中，所述方法还包括：
    在通过建立的会话进行报文传输时，所述UPF在所述会话的会话上下文下挂载的PCC规则中查找所述接收到的报文适用的PCC规则；
    当在所述会话上下文下没有找到所述报文适用的PCC规则，则从保存的本地PCC规则中查找所述报文适用的PCC规则；
    当在所述会话上下文或保存的本地PCC规则中找到所述报文适用的PCC规则，则根据找到的PCC规则处理所述报文。
  14. 根据权利要求13所述的方法，其中，所述方法还包括：当在保存的本地PCC规则中没有找到所述报文适用的PCC规则，则向所述SMF发送用于指示所述报文未匹配到适用的PCC规则的会话报告请求消息；
    接收所述SMF收到所述会话报文请求消息后重新下发的PCC规则；当所述报文适用所述SMF重新下发的PCC规则，则根据所述SMF重新下发的PCC规则处理所述报文；其中，所述SMF重新下发的PCC规则包括：默认规则、新的动态PCC规则、或激活的预定义PCC规则。
  15. 根据权利要求8或9所述的方法，其中，所述规则管理消息包括包转发控制协议PFCP PCC规则管理请求消息。
  16. 一种策略和计费控制的实现装置，包括：第一存储器、第一处理器以及存储在所述第一存储器上并可在所述第一处理器上运行的计算机程序，其中，所述第一处理器用于执行所述计算机程序以实现如权利要求1至7中任一项所述的方法的步骤。
  17. 一种策略和计费控制的实现装置，包括：第二存储器、第二处理器以及存储在所述第二存储器上并可在所述第二处理器上运行的计算机程序，其中，所述第二处理器用于执行所述计算机程序以实现如权利要求8至15中任一项所述的方法的步骤。
  18. 一种计算机可读存储介质，存储有计算机程序，所述计算机程序被执行时实现如权利要求1至15中任一项所述的方法的步骤。
PCT/CN2020/087078 2019-06-26 2020-04-26 一种策略和计费控制的实现方法及装置 WO2020259058A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910559276.6A CN112153584A (zh) 2019-06-26 2019-06-26 一种策略和计费控制的实现方法及装置
CN201910559276.6 2019-06-26

Publications (1)

Publication Number Publication Date
WO2020259058A1 true WO2020259058A1 (zh) 2020-12-30

Family

ID=73869654

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/087078 WO2020259058A1 (zh) 2019-06-26 2020-04-26 一种策略和计费控制的实现方法及装置

Country Status (2)

Country Link
CN (1) CN112153584A (zh)
WO (1) WO2020259058A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115529566B (zh) * 2022-10-27 2023-10-31 广州爱浦路网络技术有限公司 基于预定义Urr的计费控制方法、装置及存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109151913A (zh) * 2017-06-16 2019-01-04 电信科学技术研究院 一种服务质量的控制方法及相关装置
CN109756430A (zh) * 2017-11-07 2019-05-14 华为技术有限公司 一种规则的处理方法及装置

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109151913A (zh) * 2017-06-16 2019-01-04 电信科学技术研究院 一种服务质量的控制方法及相关装置
CN109756430A (zh) * 2017-11-07 2019-05-14 华为技术有限公司 一种规则的处理方法及装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "I-SMF relocation with I-UPF as an ULCL or BP", 3GPP TSG-SA WG2 MEETING #132 ; S2-1904309 WAS S2-1904279 WAS S2-1903580 TS 23.502, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), SOPHIA-ANTIPOLIS CEDEX ; FRANCE, 12 April 2019 (2019-04-12), Xi’an, China; 20190408 - 20190412, XP051704799 *
NOKIA, NOKIA SHANGHAI BELL, HUAWEI: "Traffic offload by UPF controlled by the I-SMF", 3GPP SA WG2 MEETING #133; S2-1905099 WAS S2-1904312 ETSUN, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Reno, Nevada, USA; 20190513 - 20190517, 7 May 2019 (2019-05-07), Reno, Nevada, USA 13-17 May 2019, XP051735329 *

Also Published As

Publication number Publication date
CN112153584A (zh) 2020-12-29

Similar Documents

Publication Publication Date Title
CN114145054B (zh) 用于支持流量导向通过服务功能链的系统和方法
US11528770B2 (en) Session management method, apparatus, and system
CN109842906B (zh) 一种通信的方法、装置及系统
AU2017427437B2 (en) Pdu type setting method, ue policy setting method, and related entity
WO2018205150A1 (zh) 网络切片选择策略更新方法、及装置
WO2019095908A1 (zh) 一种实现边缘网络能力开放的方法、装置、设备及存储介质
WO2018161803A1 (zh) 一种网络切片的选择方法及装置
WO2019223661A1 (zh) 一种识别应用标识的方法、设备及系统
WO2021037175A1 (zh) 一种网络切片的管理方法及相关装置
WO2019192518A1 (zh) 订阅处理方法、网络节点及用户数据库
WO2020224559A1 (zh) 群组管理方法、装置及系统
AU2019422391B2 (en) Method and apparatus for invoking application programming interface
WO2018112897A1 (zh) 一种会话激活方法及装置和系统
WO2020015634A1 (zh) 一种mec信息获取方法及装置
WO2019223526A1 (zh) 上下文管理方法及装置
US11388661B2 (en) Network slice configuration update
WO2018126342A1 (zh) 一种通信方法及设备
WO2018090386A1 (zh) 一种nf组件异常的处理方法、设备及系统
WO2018076976A1 (zh) 位置变更上报方法、设备及系统
WO2019158093A1 (zh) 一种确定ssc模式的方法及装置
US20210352535A1 (en) Notification control in a communication system
WO2021212939A1 (zh) 通信方法、装置及系统
WO2019242698A1 (zh) 一种管理网元的方法、设备及系统
JP2022541184A (ja) 互換性のないネットワークスライスのサポートと管理
WO2020259058A1 (zh) 一种策略和计费控制的实现方法及装置

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

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

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 27/05/2022)

122 Ep: pct application non-entry in european phase

Ref document number: 20831999

Country of ref document: EP

Kind code of ref document: A1