WO2023134630A1 - 配置策略的方法和装置 - Google Patents

配置策略的方法和装置 Download PDF

Info

Publication number
WO2023134630A1
WO2023134630A1 PCT/CN2023/071344 CN2023071344W WO2023134630A1 WO 2023134630 A1 WO2023134630 A1 WO 2023134630A1 CN 2023071344 W CN2023071344 W CN 2023071344W WO 2023134630 A1 WO2023134630 A1 WO 2023134630A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
network element
user equipment
service
policy
Prior art date
Application number
PCT/CN2023/071344
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 WO2023134630A1 publication Critical patent/WO2023134630A1/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
    • 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
    • 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/0889—Techniques to speed-up the configuration process
    • 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
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/20—Traffic policing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition

Definitions

  • the present application relates to the field of communication technologies, and in particular to a method and device for configuring policies.
  • the application function can use the group (group) mechanism to provide traffic routing control policies for multiple user equipment (user equipment, UE) at the same time.
  • group group
  • AF can pre-define a group and its multiple members, and then use the group ID (group ID) to refer to the group members in the service flow routing control policy.
  • group ID group ID
  • the policy control network element policy control function, PCF
  • PCF policy control function
  • the existing protocol there are problems in the group-based method of providing service flow control policies for multiple user equipments.
  • using the group method can only provide service flow control policies for multiple user equipments at the group granularity, but cannot Granularity provides service flow control policies for multiple user equipments; as members of a group should belong to the same public land mobile network (PLMN), in the scenario of mobile network roaming, roaming users and non-roaming users When belonging to different PLMNs, the AF cannot simultaneously provide traffic routing control policies for roaming users and non-roaming users through the group mechanism.
  • PLMN public land mobile network
  • the present application provides a method and device for configuring policies, which can configure policies for multiple users at the same time.
  • a method for configuring a policy includes: a policy control network element receives service flow routing control information and first service type information corresponding to the service flow routing control information, and the first service type information includes First service category information and/or first subscriber category information; the policy control network element generates policy and charging control rules for user equipment corresponding to the first service type information according to the service flow routing control information; the policy control network Yuan sends the policy and charging control rules.
  • the policy control network element can generate a policy and charging control rule for the user equipment corresponding to the first service type information according to the service flow routing control information. Therefore, the above solution can configure policies for one or more users corresponding to the first service type information at the same time, for example, policies can be configured for users belonging to different PLMNs, and users in the same group can correspond to different first service type information , therefore, based on the first service type information, policies can be configured for one or more users at a granularity smaller than that of a group, thereby improving the efficiency of policy configuration and saving resources.
  • the service flow routing control information corresponds to the first service type information, which means that the service flow routing control information is used to generate policy and charging control rules for the user equipment corresponding to the first service type information.
  • the user equipment corresponding to the first service type information includes roaming user equipment and non-roaming user equipment.
  • policies can be configured for roaming users and non-roaming users at the same time, thereby improving the efficiency of policy configuration and saving resources.
  • the policy control network element generates a policy and charging control rule for the user equipment corresponding to the first service type information according to the service flow routing control information, including: the The policy control network element determines that the user equipment is the user equipment corresponding to the first service type information according to the subscription information of the user equipment; the policy control network element generates the policy and charging control rule for the user equipment according to the service flow routing control information .
  • the method further includes: the policy control network element acquires the subscription information of the user equipment.
  • the policy control network element acquiring the subscription information of the user equipment includes: the policy control network element receiving the Subscription information of the user equipment.
  • the subscription information of the user equipment may be the subscription information between the user equipment and the operator, or the subscription information between the user equipment and the application service provider.
  • the contract information between the user equipment and the application service provider may also be referred to as "application data".
  • the subscription information of the user equipment can also be understood as information related to the user equipment, and other names can also be used, such as user equipment information, user equipment association information, etc., which are not limited here.
  • the subscription information of the user equipment may also be called user equipment subscription information, user equipment subscription, and the like.
  • the policy control network element can determine whether the user equipment is the user equipment corresponding to the first service type information according to the subscription information of the user equipment, and if the user equipment is determined to be the user equipment corresponding to the first service type information , the policy control network element generates policy and charging control rules for the user equipment, or more specifically, the policy control network element generates policy and charging control rules for the protocol data unit session (PDU session) of the user equipment, that is, the The policy control network element generates policy and charging control rules for the user equipment corresponding to the first service type information according to the service flow routing control information
  • the protocol data unit session (PDU session) of the user equipment corresponding to the first service type information generates policies and charging control rules, so as to achieve the purpose of configuring policies for one or more user equipment corresponding to the first service type information, so that it can be Improve the efficiency of policy configuration and save resources.
  • the policy control network element determines that the user equipment is the user equipment corresponding to the first service type information according to the subscription information of the user equipment, including: in the first When the service type information matches the second service type information, the policy control network element determines that the user equipment is the user equipment corresponding to the first service type information, and the second service type information is included in the subscription information of the user equipment , the second service type information includes second service type information and/or second subscriber category information.
  • the policy control network element can judge whether a user equipment is the user equipment corresponding to the first service type information according to the first service type information and the second service type information in the subscription information of the user equipment.
  • the policy control network element determines that the user equipment is the first service type information
  • the corresponding user equipment includes: when the second service type information includes the first service type information, the policy control network element determines that the user equipment is the user equipment corresponding to the first service type information; or, in the
  • the first service type information includes multiple service type information
  • the policy control network element determines that the user equipment is the first service The user equipment corresponding to the type information, or, when the second service type information includes at least one of the plurality of service type information in the first service type information, the policy control network element determines that the user equipment is the first service type
  • each service type information in the plurality of service type information includes first service type information and/or first subscriber type information.
  • the first service type information may include only one service type information, or may include multiple service type information.
  • the first service type information includes multiple service type information
  • the second service type information includes all service type information in the multiple service type information in the first service type information
  • the policy control network element determines that the user equipment is the user equipment corresponding to the first service type information; in another implementation manner, when the second service type information includes a plurality of service type information in the first service type information
  • the policy control network element determines that the user equipment is the user equipment corresponding to the first service type information.
  • first service category information and/or the first subscriber category information included in each of the above multiple service type information may be the same or different, which is not limited in this application.
  • the second service type information matches the first service type information, so as to determine whether a user equipment is the user equipment corresponding to the first service type information.
  • the method further includes: receiving, by the policy control network element, first application identification information and/or a first application service provider identification corresponding to the first service type information information.
  • the policy control network element determines that the user equipment is the user equipment corresponding to the first service type information, including: in the first application identification information and/or the first If the application service provider identification information matches the second application identification information and/or the second application service provider identification information, the policy control network element determines that the user equipment is the user equipment corresponding to the first service type information, and the second The second application identification information and/or the second application service provider identification information are included in the subscription information of the user equipment.
  • the policy control network element may also use the first application identification information and/or the first application service provider identification information to determine a user equipment as the user equipment corresponding to the first service type information.
  • the method further includes: combining the first application identification information and/or the first application service provider identification information with the second application identification information and/or the second If the application service provider identification information is the same, the policy control network element determines that the first application identification information and/or the first application service provider identification information matches the second application identification information or the second application service provider identification information.
  • the policy control network element may determine that a user equipment is the first application identification information and/or the first application service provider identification information, and the second application identification information and/or the second application service provider identification information according to the first application identification information and/or the second application service provider identification information.
  • the user equipment corresponding to the service type information.
  • the policy control network element receives service flow routing control information and first service type information corresponding to the service flow routing control information, including: the policy control network element Receive the service flow routing control information and the first service type information corresponding to the service flow routing control information from the network opening function network element.
  • the network opening function network element receives the service flow routing control information and the first service type information corresponding to the service flow routing control information from the application function network element, and transmits the service flow routing control information and the service flow routing control information
  • the first service type information corresponding to the flow routing control information is sent to the policy control network element, or after the network opening function network element converts part of the information in the service flow routing control information, the service flow routing control information and the
  • the first service type information corresponding to the service flow routing control information is sent to the policy control network element.
  • the method further includes: the policy control network element receiving the subscription information of the user equipment from a unified data storage network element or a session management network element.
  • the policy control network element generates a policy and charging control rule for the user equipment corresponding to the first service type information according to the service flow routing control information, including: the The policy control network element generates policy and charging control rules for the protocol data unit session of the user equipment corresponding to the first service type information according to the service flow routing control information.
  • a method for configuring a policy includes: a policy control network element receives service flow routing control information and identification information of a subscriber corresponding to the service flow routing control information; the policy control network element receives the service flow routing control information according to the The service flow routing control information generates policy and charging control rules for the subscriber; the policy control network element sends the policy and charging control rules.
  • the policy control network element can generate policy and charging control rules for subscribers according to the service flow routing control information. Therefore, the above solution can configure policies for one or more subscriptions at the same time, for example, can configure policies for subscribers belonging to different PLMNs, thereby improving the efficiency of policy configuration and saving resources.
  • the service flow routing control information corresponds to the subscriber's identification information, which means that the service flow routing control information is associated with the subscriber's identification information, or the service flow routing control information is used for the subscriber
  • the user equipment generates policies and charging control rules corresponding to the identification information of the subscriber, or the service flow routing control information corresponds to the user equipment group to which the subscriber belongs in the identification information of the subscriber.
  • the subscribed users include roaming users and non-roaming users.
  • policies can be configured for roaming users and non-roaming users at the same time, thereby improving the efficiency of policy configuration and saving resources.
  • the policy control network element generates a policy and charging control rule for the subscriber according to the service flow routing control information, including: the policy control network element determines that the user The equipment belongs to the subscriber; the policy control network element generates policy and charging control rules for the user equipment according to the service flow routing control information.
  • the method further includes: the policy control network element acquires subscription information of the user equipment, where the subscription information of the user equipment includes an identifier of the user equipment.
  • the policy control network element acquiring the subscription information of the user equipment includes: the policy control network element receiving the Subscription information of the user equipment.
  • the policy control network element can determine whether a user equipment is a subscriber, for example, determine whether a user equipment is a subscriber through subscription information of the user equipment.
  • the policy control network element can generate policy and charging control rules for the user equipment, thereby improving the efficiency of policy configuration and saving resources.
  • the policy control network element determining that the user equipment belongs to the subscriber includes: when the identifier of the user equipment is included in the identifier of the subscriber, The policy control network element determines that the user equipment belongs to the subscriber.
  • the policy control network element when the policy control network element determines that the identity of the user equipment is included in the identity of the subscriber, the policy control network element can generate policy and charging control rules for the user equipment according to the policy information corresponding to the identity of the subscriber , so as to achieve the purpose of configuring access control policies for multiple users.
  • the policy control network element receives service flow routing control information and the identifier of the subscriber corresponding to the service flow routing control information, including: the policy control network element receives The service flow routing control information from the application function network element and the identifier of the subscriber corresponding to the service flow routing control information.
  • a method for configuring a policy includes: an application function network element sends service flow routing control information and first service type information corresponding to the service flow routing control information, and the first service type information includes First service category information and/or first signatory category information.
  • the application function network element sends the service flow routing control information and the first service type corresponding to the service flow routing control information (for example, through the network opening function network element to the unified data storage network element), so that the service flow can be used
  • the routing control information configures policies for one or more users corresponding to the first service type information, so that policies can be configured for one or more users corresponding to the first service type information at the same time, for example, policies can be configured for users belonging to different PLMNs, Therefore, the efficiency of policy configuration can be improved and resources can be saved.
  • the method includes: applying a functional network element to generate a policy, where the policy corresponds to the service flow routing control information and the first service type information.
  • the method further includes: the application function network element sending the subscriber's identification information and the first service type information, the subscriber's identification information and the first service type information Service type information is associated.
  • the application function network element sends the subscriber identification information and the first service type information to the unified data storage network element through the network opening function network element.
  • the application function network element may send the identification information of the subscriber and the first service type information, so as to configure a policy for the subscriber corresponding to the first service type information .
  • the first service type information includes multiple pieces of service type information.
  • the method further includes: the application function network element sending the first application identification information and/or the first application service provider identification corresponding to the first service type information information.
  • a method for configuring policies comprising: receiving service flow routing control information by a unified data storage network element and identification information of a user equipment group corresponding to the service flow routing control information; the unified data storage network The unit determines the identification information of the subscriber corresponding to the identification information of the user equipment group according to the identification information of the user equipment group; the unified data storage network element sends the service flow routing control information and the identification of the subscriber to the policy control network element information, the service flow routing control is associated with the subscriber's identification information.
  • the unified data storage network element can determine the identification information of the subscriber corresponding to the identification information of the user equipment group according to the identification information of the user equipment group, and store the identification information of the subscriber and the service flow received by it
  • the routing control information is sent to the policy control network element, so that the policy control network element can configure policies for subscribers based on these information.
  • the unified data storage network element receives service flow routing control information from the application function network element and identification information of a user equipment group corresponding to the service flow routing control information Before, the method further includes: the unified data storage network element receives the identification information of the user equipment group and the identification information of the subscriber from the application function network element, and the identification of the user equipment group is related to the identification information of the subscriber couplet.
  • a method for configuring policies comprising: receiving service flow routing control information and first service type information corresponding to the service flow routing control information by a unified data storage network element, the first service type information Including the first service category information and/or the first subscriber type information; the data management network element determines the identification information of the subscriber corresponding to the first service type information according to the first service type information; the unified data storage network element Send the service flow routing control information and the identification information of the subscriber to the policy control network element.
  • the unified data storage network element may be a network element with a unified data storage function.
  • the unified data storage network element may be a UDR.
  • the unified data storage network element can determine the identification information of the subscriber corresponding to the identification information of the user equipment group according to the first service type information, and route the identification information of the subscriber and the service flow received by it
  • the control information is sent to the policy control network element, so that the policy control network element can configure policies for subscribers according to these information.
  • the unified data storage network element receives service flow routing control information from the application function network element and the first service type corresponding to the service flow routing control information Before the information, the method further includes: the unified data storage network element receives the subscriber's identification information and the first service type information from the application function network element, and the subscriber's identification information is related to the first service type information couplet.
  • a method for configuring a policy including: the application function network element sends service flow routing control information and identification information of the user equipment group corresponding to the service flow routing control information to the unified data storage network element,
  • the group of user equipment includes subscribers.
  • the application function network element sends the service flow routing control information and the identification information of the user equipment group corresponding to the service flow routing control information (for example, through the network opening function network element to the unified data storage network element), so that it can be used
  • the service flow routing control information configures policies for one or more subscribers in the user equipment group, so that policies can be configured for one or more subscribers in the user equipment group at the same time, for example, policies can be configured for users belonging to different PLMNs, Therefore, the efficiency of policy configuration can be improved and resources can be saved.
  • the application function network element sends the service flow routing control information and the identifier of the user equipment group corresponding to the service flow routing control information to the unified data storage network element before the information, the method further includes: the application function network element sending the identifier of the user equipment group and the identifier information of the subscriber to the unified data storage network element, and the user identifier information is associated with the identifier of the user equipment group.
  • a method for configuring policies comprising: a session management network element receives subscription information of a user equipment from a unified data management network element, the subscription information includes service type information, and the service type information includes service category information and/or subscriber category information; the session management network element sends the subscription information to the policy control network element.
  • the session management network element can send the subscription information of the user equipment received from the unified data management network element to the policy control network element, so that the policy control network element can configure policies for the user equipment.
  • the method further includes: the session management network element sends the unified data
  • the storage network element sends a subscription information request message, the subscription information request message includes the identifier of the user equipment, and the subscription information request message is used to request the subscription information of the user equipment.
  • a method for configuring policies includes: a unified data management network element receives subscription information and identification information of subscribers, the subscription information includes service type information, and the service type information includes service category information and/or or the category information of the signatory, the sign-up information is associated with the sign-off user's identification information; the unified data management network element saves the sign-up information and the sign-off user's sign-off information.
  • the unified data management network element may pre-store the received subscription information and the identification information of the subscribers corresponding to the subscription information, so that policies can be configured for one or more subscribers according to these information.
  • the method further includes: the unified data management network element receives a subscription information request message from the session management network element, and the subscription information request message includes identification information of the user equipment , the subscription information request message is used to request the subscription information of the user equipment; if the identification information of the user equipment includes the identification information of the subscriber, the unified data management network element sends the subscription information to the session management network element information.
  • the subscription information further includes the second application identification information and/or the second application service provider identification information.
  • a method for configuring a policy comprising: a policy control network element receives service flow routing control information and group information corresponding to the service flow routing control information, where the group information includes multiple group identifiers; the The policy control network element generates policy and charging control rules for user equipment matching the group information according to the service flow routing control information; the policy control network element sends the policy and charging control rules.
  • the policy control network element can generate policy and charging control rules for user equipment that matches the group information according to the service flow routing control information, so that policies can be configured for one or more subscribers at the same time.
  • the user equipment of the PLMN for example, roaming user equipment and non-roaming user equipment
  • the policy control network element may receive service flow routing control information and group information corresponding to the service flow routing control information, for example, the policy control network element may receive the service flow routing control information and The group information, or the policy control network element may receive the service flow routing control information and the group information from the network opening function network element, or the policy control network element may receive the service flow routing control information and the group information from the application function network element .
  • the policy control network element determines that a user equipment matches the group information, the policy control network element can use the service flow routing control information to generate policy control and charging rules for the user equipment.
  • the policy control network element receives service flow routing control information and group information corresponding to the service flow routing control information, including: the policy control network element receives from the unified data storage The service flow routing control information of the network element and the group information corresponding to the service flow routing control information.
  • group information may be the information provided by the application function network element, or the information obtained by converting the information provided by the application function network element by the network opening function network element.
  • the following are examples for description.
  • the application function network element after the application function network element generates the service flow routing control information, it sends the service flow routing control information and group information (denoted as the first group information) to the network opening function network element, wherein the first group information Include multiple internal group IDs.
  • the network opening function network element receives the service flow routing control information and the first group of information from the application function network element, it sends the service flow routing control information and group information (referred to as the second group of information) to the unified data storage network element.
  • the first set of information is the same as the second set of information.
  • the unified data storage network element After receiving the service flow routing control information and the second group of information, the unified data storage network element sends the service flow routing control information and the second group of information to the policy control network element.
  • the application function network element after the application function network element generates the service flow routing control information, it sends the service flow routing control information and group information (denoted as the first group information) to the network opening function network element, wherein the first group The information includes multiple external group IDs.
  • the network opening function network element After the network opening function network element receives the service flow routing control information and the first group information from the application function network element, it converts multiple external group identifiers in the first group information into internal group identifiers to obtain new group information (denoted as the first group information) The second group of information), and then the network opening function network element sends the service flow routing control information and group information (denoted as the second group of information) to the unified data storage network element. In this case, the first group of information and the second group of information same. After receiving the service flow routing control information and the second group of information, the unified data storage network element sends the service flow routing control information and the second group of information to the policy control network element.
  • the group information received by the policy control network element and corresponding to the service flow routing control information may correspond to the second group information in the above example.
  • the group information received by the policy control network element and corresponding to the service flow routing control information may correspond to the second group information in the above example.
  • the policy control network element generates a policy and charging control rule for the user equipment matching the group information according to the service flow routing control information, including: the policy control The network element determines that the user equipment matches the group information according to the subscription information of the user equipment; the policy control network element generates the policy and charging control rules for the user equipment according to the service flow routing control information.
  • the policy control network element After the policy control network element obtains the subscription information of the user equipment, it can judge whether the user equipment matches the group information according to the subscription information.
  • the information generates policy control and charging rules for user equipment, so that policies can be configured for multiple subscribers at the same time, thereby improving efficiency and saving resources.
  • the policy control network element determines that the user equipment matches the group information according to the subscription information of the user equipment, including: the subscription information of the user equipment includes the group information In the case of multiple group identifiers in , the policy control network element determines that the user equipment matches the group information.
  • the policy control network element can generate policy and charging control rules for user equipment whose subscription information includes multiple group identifiers of group information, that is, the policy control network element can generate for one or more different user equipment Policies and billing control rules can improve efficiency.
  • the policy control network element determines that the user equipment matches the group information according to the subscription information of the user equipment, It includes: when the subscription information of the user equipment satisfies the logical relationship of the plurality of group identifiers, the policy control network element determines that the user equipment matches the group information.
  • the policy control network element can generate policy and charging control rules for user equipment whose subscription information satisfies the logical relationship of multiple group identifiers in the group information, that is, the policy control network element can generate policy and charging control rules for one or more different User equipment generates policies and charging control rules, thereby improving efficiency.
  • a method for configuring a policy includes: an application function network element sends service flow routing control information and group information corresponding to the service flow routing control information, and the group information includes multiple group identifiers.
  • the method further includes: the policy control network element receiving the subscription information of the user equipment from a unified data storage network element or a session management network element.
  • a communication device which includes: a transceiver module configured to receive service flow routing control information and first service type information corresponding to the service flow routing control information, where the first service type information includes First service category information and/or first subscriber category information; a processing module, configured to generate policy and charging control rules for user equipment corresponding to the first service type information according to the service flow routing control information; the policy control network Yuan sends the policy and charging control rules.
  • the processing module may be specifically configured to determine, according to subscription information of the user equipment, that the user equipment is the user equipment corresponding to the first service type information; and, according to the The service flow routing control information generates the policy and charging control rule for the user equipment.
  • the processing module may be specifically configured to determine that the user equipment is the second service type A user equipment corresponding to service type information, the second service type information is included in the subscription information of the user equipment, and the second service type information includes the second service type information and/or the second subscriber category information.
  • the processing module when the second service type information includes the first service type information, the processing module may be specifically configured to determine that the user equipment is the first service type A user equipment corresponding to service type information; or, when the second service type information includes at least one of a plurality of service type information in the first service type information, the processing module can be specifically used to determine the user equipment The device is the user equipment corresponding to the first service type information.
  • the transceiver module is further configured to receive first application identification information and/or first application service provider identification information corresponding to the first service type information .
  • the processing module may be specifically configured to combine the first application identification information and/or the first application service provider identification information with the second application identification information and/or or the second application service provider identification information matches, determine that the user equipment is the user equipment corresponding to the first service type information, and the second application identification information and/or the second application service provider identification information are included in the user equipment in the contract information.
  • the processing module is further configured to combine the first application identification information and/or the first application service provider identification information with the second application identification information or When the second application service provider identification information is the same, the policy control network element determines that the first application identification information and/or the first application service provider identification information matches the second application identification information or the second application service provider identification information .
  • the transceiver module may be specifically configured to receive the service flow routing control information and the first service flow routing control information corresponding to the service flow routing control information from the network opening function network element. - service type information.
  • the processing module may be specifically configured to generate a policy and charging for a session of the user equipment corresponding to the first service type information according to the service flow routing control information control rules.
  • a communication device which includes: a transceiver module, configured to receive service flow routing control information and identification information of a subscriber corresponding to the service flow routing control information; a processing module, configured to receive the service flow routing control information according to the The service flow routing control information generates policy and charging control rules for the subscriber; the transceiver module is also used to send the policy and charging control rules.
  • the processing module may be specifically configured to determine that the user equipment belongs to the subscriber; and generate a policy and Billing control rules.
  • the processing module may be specifically configured to determine that the user equipment belongs to the subscription when the user equipment identifier is included in the subscriber identifier. user.
  • the transceiver module may be specifically configured to receive the service flow routing control information from the application function network element and the subscriber corresponding to the service flow routing control information logo.
  • a device for configuring policies including: a transceiver module, configured to send service flow routing control information and first service type information corresponding to the service flow routing control information, the first service type
  • the information includes first service category information and/or first signatory category information.
  • the transceiver module is further configured to send the identification information of the subscriber and the first service type information, the identification information of the subscriber and the first service type information Type information is associated.
  • the first service type information includes multiple pieces of service type information.
  • the transceiver module is further configured to send the first application identification information and/or the first application service provider identification information corresponding to the first service type information .
  • an apparatus for configuring policies comprising: a transceiver module configured to receive service flow routing control information and identification information of a user equipment group corresponding to the service flow routing control information; a processing module configured to Determine the identification information of the subscriber corresponding to the identification information of the user equipment group according to the identification information of the user equipment group; the transceiver module is also used to send the service flow routing control information and the subscription user's Identification information, the service flow routing control is associated with the identification information of the subscriber.
  • the transceiver module is further configured to receive the identification information of the user equipment group and the identification information of the subscriber from the application function network element, the user The identifier of the device group is associated with the identifier information of the subscriber.
  • an apparatus for configuring policies comprising: a transceiver module configured to receive service flow routing control information and first service type information corresponding to the service flow routing control information, the first service type The information includes the first service category information and/or the first subscriber type information; the processing module is configured to determine the identification information of the subscriber corresponding to the first service type information according to the first service type information; the transceiver module also It is used to send the service flow routing control information and the identification information of the subscriber to the policy control network element.
  • the transceiver module is further configured to receive the subscriber's identification information and the first service type information from the application function network element, and the subscriber's The identification information of is associated with the first service type information.
  • a device for configuring policies including: a transceiver module, configured to send service flow routing control information and an identifier of a user equipment group corresponding to the service flow routing control information to a unified data storage network element information, the user equipment group includes subscribers.
  • the transceiver module is further configured to send the identifier of the user equipment group and the identifier information of the subscriber to the unified data storage network element, and the subscriber The identification information of the user equipment group is associated with the identification of the user equipment group.
  • the identifier information of the subscriber is associated with the identifier of the user equipment group, which may refer to the subscriber corresponding to the identifier information of the subscriber belongs to the user equipment group corresponding to the identifier of the user equipment group.
  • an apparatus for configuring policies including: a transceiver module, configured to receive subscription information of a user equipment from a unified data storage network element or a session management network element, where the subscription information includes second service type information ; and, sending the subscription information to the policy control network element.
  • the transceiver module is configured to send a subscription information request message to the unified data management network element, where the subscription information request message includes the identifier of the user equipment, and the subscription information The information request message is used to request the subscription information of the user equipment.
  • an apparatus for configuring policies comprising: a transceiver module configured to receive subscription information and an identifier of a subscriber, the subscription information includes service type information, the service type information includes service category information and/or or the category information of the signatory, the sign-up information is associated with the sign-on user's identification information; the processing module is used to save the sign-up information and the first or multiple sign-on user's identification information.
  • the transceiver module is further configured to receive a subscription information request message from a session management network element, where the subscription information request message includes identification information of the user equipment, the The subscription information request message is used to request the subscription information of the user equipment; when the identification information of the user equipment includes the identification information of the subscriber, the transceiver module is also used to send the subscription information to the session management network element .
  • the subscription information further includes second application identification information and/or second application service provider identification information.
  • a communication device including: a transceiver module, configured to receive service flow routing control information and group information corresponding to the service flow routing control information, where the group information includes multiple group identifiers;
  • the processing module is used to generate policy and charging control rules for user equipment matching the group information according to the service flow routing control information; the transceiver module is also used to send the policy and charging control rules.
  • the processing module is specifically configured to determine that the user equipment matches the group information according to the subscription information of the user equipment; The user equipment generates the policy and charging control rules.
  • the processing module is specifically configured to determine that the user equipment The device matches this set of information.
  • the nineteenth aspect there is a logical relationship between multiple group identifiers in the group information; In the case of the logical relationship of the group identifier, it is determined that the user equipment matches the group information.
  • the transceiving module is further configured to: receive subscription information of the user equipment from a unified data storage network element or a session management network element.
  • a communication device which includes: a transceiver module, configured to send service flow routing control information and group information corresponding to the service flow routing control information, where the group information includes multiple group identifiers.
  • a communication device is provided, and the device is configured to execute the methods provided in the first aspect to the tenth aspect above.
  • the apparatus may include units and/or modules for executing the methods provided in the first aspect to the tenth aspect, such as a processing module and/or a transceiver module (also called a communication module).
  • the device is a network device, for example, the device is a policy control network element, or an application function network element, or a unified data storage network element.
  • the transceiver module may be a transceiver, or an input/output interface; the processing module may be a processor.
  • the apparatus is a chip, a chip system or a circuit used in a network device.
  • the transceiver module may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip, chip system or circuit etc.
  • the processing module may be a processor, a processing circuit or a logic circuit and the like.
  • a communication device which includes: a memory for storing programs; a processor for executing the programs stored in the memory, and when the programs stored in the memory are executed, the processor is used for executing the above-mentioned first Aspects to the methods provided in the tenth aspect.
  • the present application provides a processor, configured to execute the methods provided in the foregoing aspects.
  • the process of sending the above information and obtaining/receiving the above information in the above method can be understood as the process of outputting the above information by the processor and the process of receiving the input of the above information by the processor.
  • the processor When outputting the above information, the processor outputs the above information to the transceiver for transmission by the transceiver. After the above information is output by the processor, other processing may be required before reaching the transceiver.
  • the transceiver acquires/receives the above-mentioned information and inputs it into the processor. Furthermore, after the transceiver receives the above information, the above information may need to be processed before being input to the processor.
  • the receiving request message mentioned in the foregoing method may be understood as the processor receiving input information.
  • processor For the operations of transmitting, sending, and acquiring/receiving involved in the processor, if there is no special description, or if it does not conflict with its actual function or internal logic in the relevant description, it can be understood more generally as the processor Output and receive, input and other operations, rather than the transmission, transmission and reception operations performed directly by radio frequency circuits and antennas.
  • the above-mentioned processor may be a processor dedicated to performing these methods, or may be a processor that executes computer instructions in a memory to perform these methods, such as a general-purpose processor.
  • the above-mentioned memory can be a non-transitory (non-transitory) memory, such as a read-only memory (read only memory, ROM), which can be integrated with the processor on the same chip, or can be respectively arranged on different chips.
  • ROM read-only memory
  • a twenty-fourth aspect provides a computer-readable storage medium, where the computer-readable medium stores program code for execution by a device, and the program code includes a method for executing the methods provided in the first aspect to the tenth aspect above.
  • a computer program product containing instructions is provided, and when the computer program product is run on a computer, it causes the computer to execute the methods provided in the first aspect to the tenth aspect above.
  • a twenty-sixth aspect provides a chip, the chip includes a processor and a communication interface, the processor reads instructions stored in the memory through the communication interface, and executes the methods provided in the first aspect to the tenth aspect above.
  • the chip may further include a memory, the memory stores instructions, the processor is configured to execute the instructions stored in the memory, and when the instructions are executed, the processor is configured to execute the above-mentioned first The methods provided in the first aspect to the tenth aspect.
  • FIG. 1 is a schematic diagram of a communication system architecture applicable to an embodiment of the present application.
  • FIG. 2 is an exemplary flowchart of a method 200 of configuring policies.
  • Fig. 3 is an exemplary flow chart of a method for configuring a policy provided by an embodiment of the present application.
  • Fig. 4 is an exemplary flow chart of another method for configuring policies provided by an embodiment of the present application.
  • Fig. 5 is an exemplary flow chart of another method for configuring policies provided by an embodiment of the present application.
  • Fig. 6 is an exemplary flow chart of another method for configuring a policy provided by an embodiment of the present application.
  • Fig. 7 is an exemplary flow chart of another method for configuring a policy provided by an embodiment of the present application.
  • Fig. 8 is an exemplary flow chart of another method for configuring a policy provided by an embodiment of the present application.
  • Fig. 9 is an exemplary flow chart of another method for configuring a policy provided by an embodiment of the present application.
  • Fig. 10 is a schematic block diagram of a communication device provided by an embodiment of the present application.
  • Fig. 11 is a schematic block diagram of a communication device provided by another embodiment of the present application.
  • Fig. 12 is a schematic block diagram of a communication device provided by another embodiment of the present application.
  • the technical solution provided by this application can be applied to various communication systems, such as: the fifth generation (5th generation, 5G) or new radio (new radio, NR) system, long term evolution (long term evolution, LTE) system, LTE frequency division Duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD) system, etc.
  • 5G fifth generation
  • NR new radio
  • long term evolution long term evolution
  • LTE long term evolution
  • LTE frequency division Duplex frequency division duplex
  • FDD frequency division duplex
  • TDD time division duplex
  • the technical solution provided by this application can also be applied to device to device (device to device, D2D) communication, vehicle to everything (vehicle-to-everything, V2X) communication, machine to machine (machine to machine, M2M) communication, machine type Communication (machine type communication, MTC), and Internet of things (internet of things, IoT) communication system or other communication systems.
  • D2D device to device
  • V2X vehicle-to-everything
  • M2M machine to machine
  • M2M machine type Communication
  • MTC machine type communication
  • IoT Internet of things
  • FIG. 1 it is a schematic diagram of a fifth generation (5th generation, 5G) network architecture based on a service architecture.
  • 5G fifth generation
  • the 5G network architecture shown in Figure 1 may include three parts, namely a terminal equipment part, a data network (data network, DN) and an operator network part.
  • a terminal equipment part namely a terminal equipment part, a data network (data network, DN) and an operator network part.
  • DN data network
  • operator network part namely a data network (data network, DN) and a operator network part.
  • the operator network may include one or more of the following network elements: authentication server function (authentication server function, AUSF) network element, network exposure function (network exposure function, NEF) network element, policy control function (policy control function, PCF) network element, unified data management (unified data management, UDM) network element, unified database (unified data repository, UDR), network storage function (network repository function, NRF) network element, application function (application function, AF) ) network elements, access and mobility management function (access and mobility management function, AMF) network elements, session management function (session management function, SMF) network elements, radio access network (radioaccess network, RAN) and user plane functions (user plane function, UPF) network element, etc.
  • authentication server function authentication server function, AUSF
  • NEF network exposure function
  • policy control function policy control function
  • PCF policy control function
  • unified data management unified data management
  • UDM unified database
  • NRF network repository function
  • application function application function, AF
  • AMF access and mobility management function
  • Terminal device It can also be called user equipment (UE), which is a device with wireless transceiver function, which can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; it can also be deployed On the water (such as ships, etc.); can also be deployed in the air (such as aircraft, balloons and satellites, etc.).
  • the terminal device may be a mobile phone, a tablet computer (pad), a computer with a wireless transceiver function, a virtual reality (virtual reality, VR) terminal, an augmented reality (augmented reality, AR) terminal, an industrial control (industrial control ), wireless terminals in self driving, wireless terminals in remote medical, wireless terminals in smart grid, wireless terminals in transportation safety , wireless terminals in smart cities, wireless terminals in smart homes, etc.
  • the terminal device here refers to a 3rd generation partnership project (3rd generation partnership project, 3GPP) terminal.
  • 3rd generation partnership project 3rd generation partnership project
  • the above-mentioned terminal device can establish a connection with the operator network through an interface provided by the operator network (such as N1, etc.), and use services such as data and/or voice provided by the operator network.
  • the terminal device can also access the DN through the operator's network, and use the operator's service deployed on the DN, and/or the service provided by a third party.
  • the above-mentioned third party may be a service party other than the operator's network and the terminal device, and may provide other services such as data and/or voice for the terminal device.
  • the specific form of expression of the above-mentioned third party can be determined according to the actual application scenario, and is not limited here.
  • Wireless access network radio access network, RAN
  • RAN radio access network
  • the RAN is a sub-network of the operator's network and an implementation system between service nodes and terminal equipment in the operator's network.
  • the terminal equipment To access the operator's network, the terminal equipment first passes through the RAN, and then can be connected to the service node of the operator's network through the RAN.
  • the RAN device in this application is a device that provides a wireless communication function for a terminal device, and the RAN device is also called an access network device.
  • the RAN equipment in this application includes but is not limited to: next-generation base station (g nodeB, gNB) in 5G, evolved node B (evolved node B, eNB), radio network controller (radio network controller, RNC), node B (node B, NB), base station controller (base station controller, BSC), base transceiver station (base transceiver station, BTS), home base station (for example, home evolved nodeB, or home node B, HNB), baseband unit (baseBand unit, BBU), transmission point (transmitting and receiving point, TRP), transmission point (transmitting point, TP), mobile switching center, etc.
  • next-generation base station g nodeB, gNB
  • 5G evolved node B (evolved node B, eNB), radio network controller (radio network controller, RNC), node B (node B, NB), base station controller (base station controller, BSC), base transceiver station (base transceiver station, BTS
  • User plane function used for packet routing and forwarding and quality of service (QoS) processing of user plane data.
  • QoS quality of service
  • the user plane network element may be a user plane function (user plane function, UPF) network element.
  • UPF user plane function
  • the user plane network element may still be a UPF network element, or may have other names, which are not limited in this application.
  • the access and mobility management network element is mainly used for mobility management and access management, etc., and can be used to implement other functions in the MME function except session management, for example, functions such as access authorization/authentication.
  • the access and mobility management network element may be an access and mobility management function (access and mobility management function, AMF).
  • AMF access and mobility management function
  • the access and mobility management device may still be an AMF, or may have other names, which are not limited in this application.
  • Session management function session management function, SMF: mainly used for session management, user equipment network interconnection protocol (internet protocol, IP) address allocation and management, selection of manageable user plane functions, policy control and charging function interface endpoints and downlink data notifications, etc.
  • the session management network element may be a session management function network element.
  • the session management network element may still be an SMF network element, or may have other names, which are not limited in this application.
  • PCF Policy control function
  • the policy control network element may be a policy and charging rules function (policy and charging rules function, PCRF) network element.
  • policy control network element may be a policy control function PCF network element.
  • the policy control network element may still be a PCF network element, or may have other names, which are not limited in this application.
  • Application function (Application function, AF): It is used for data routing affected by applications, open function network elements of wireless access networks, and interacts with policy frameworks for policy control, etc.
  • the application network element may be an application function network element.
  • the application network element may still be an AF network element, or may have other names, which are not limited in this application.
  • Unified data management used to process UE identification, access authentication, registration and mobility management.
  • the data management network element may be a unified data management network element; in a 4G communication system, the data management network element may be a home subscriber server (HSS) network element.
  • HSS home subscriber server
  • the unified data management may still be a UDM network element, or may have other names, which are not limited in this application.
  • AUSF Authentication server function
  • the authentication server may be an authentication server functional network element.
  • the authentication server functional network element may still be an AUSF network element, or may have other names, which are not limited in this application.
  • DN is a network located outside the operator's network.
  • the operator's network can access multiple DNs, and multiple services can be deployed on the DN, which can provide data and/or voice for terminal equipment. and other services.
  • DN is a private network of a smart factory.
  • the sensors installed in the workshop of the smart factory can be terminal devices.
  • the control server of the sensor is deployed in the DN, and the control server can provide services for the sensor.
  • the sensor can communicate with the control server, obtain instructions from the control server, and transmit the collected sensor data to the control server according to the instructions.
  • DN is a company's internal office network, and the mobile phone or computer of the company's employees can be a terminal device, and the employee's mobile phone or computer can access information and data resources on the company's internal office network.
  • Nausf, Nnef, Npcf, Nudm, Naf, Namf, Nsmf, N1, N2, N3, N4, and N6 are interface serial numbers.
  • interface serial numbers refer to the meanings defined in the 3GPP standard protocol, and there is no limitation here.
  • network elements can communicate through the interfaces shown in the figure.
  • the UE and the AMF may interact through the N1 interface, and the interaction message may be called an N1 message (N1Message), for example.
  • the RAN and the AMF can interact through the N2 interface, and the N2 interface can be used for sending non-access stratum (non-access stratum, NAS) messages, etc.
  • the RAN and UPF can interact through the N3 interface, and the N3 interface can be used to transmit user plane data, etc.
  • the SMF and UPF can interact through the N4 interface, and the N4 interface can be used to transmit information such as the tunnel identification information of the N3 connection, data cache indication information, and downlink data notification messages.
  • the UPF and DN can interact through the N6 interface, and the N6 interface can be used to transmit data on the user plane.
  • the relationship between other interfaces and each network element is shown in FIG. 1 , and for the sake of brevity, details are not described here one by one.
  • Functional network elements can be combined into network slices on demand.
  • These core network elements may be independent devices, or may be integrated into the same device to implement different functions. This application does not limit the specific forms of the above network elements.
  • the above-mentioned network element or function may be a network element in a hardware device, or a software function running on dedicated hardware, or a virtualization function instantiated on a platform (for example, a cloud platform).
  • the network device is the access and mobility management network element AMF
  • the base station is the radio access network RAN as an example for description.
  • the network architecture and business scenarios described in the embodiments of the present application are for more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute limitations on the technical solutions provided by the embodiments of the present application.
  • the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.
  • Computer-readable media may include, but are not limited to: magnetic storage devices (e.g., hard disk, floppy disk, or tape, etc.), optical disks (e.g., compact disc (compact disc, CD), digital versatile disc (digital versatile disc, DVD) etc.), smart cards and flash memory devices (for example, erasable programmable read-only memory (EPROM), card, stick or key drive, etc.).
  • magnetic storage devices e.g., hard disk, floppy disk, or tape, etc.
  • optical disks e.g., compact disc (compact disc, CD), digital versatile disc (digital versatile disc, DVD) etc.
  • smart cards and flash memory devices for example, erasable programmable read-only memory (EPROM), card, stick or key drive, etc.
  • various storage media described herein can represent one or more devices and/or other machine-readable media for storing information.
  • the term "machine-readable medium” may include, but is not limited to, wireless channels and various other media capable of storing, containing and/or carrying instructions and/or data.
  • the evolved packet system (EPS) defined in the 3rd generation partnership project (3GPP) includes the 5G network architecture based on the service interface or the 5G network architecture based on the point-to-point interface.
  • the 5G network can It is divided into three parts, namely UE, DN and operator network.
  • the operator's network may include one or more of the network elements shown in Figure 1 except UE and DN, or may also include other network elements.
  • This application does not limit the structure of the 5G network. Introduction in related technologies.
  • the traditional centralized anchor point deployment method in LTE is becoming more and more difficult to support the fast-growing mobile service traffic model.
  • the increased traffic is finally concentrated at the gateway and the core computer room, which puts forward higher and higher requirements for the backhaul network bandwidth, the throughput of the computer room, and the specifications of the gateway;
  • the long-distance backhaul network and complex transmission environment from the access network to the anchor gateway lead to large delay and jitter in the transmission of user packets.
  • edge computing By moving the user plane network elements and business processing capabilities down to the edge of the network, edge computing realizes distributed local processing of business traffic and avoids excessive concentration of traffic, thereby greatly reducing the specification requirements for core computer rooms and centralized gateways. At the same time, edge computing also shortens the distance of the backhaul network, reduces the end-to-end transmission delay and jitter of user packets, and makes the deployment of ultra-low-latency services possible.
  • the edge computing platform is deployed at the sinking UPF (that is, the local UPF); the DN network is deployed at the remote UPF.
  • the path (shown by the solid line) for the UE to access the DN the path (shown by the dotted line) for the UE to access the edge computing platform is greatly shortened. Therefore, edge computing technology can provide users with low-latency, high-bandwidth services.
  • Roaming refers to the situation where a mobile user belonging to operator A accesses the network of operator B. For example, when a user of China Mobile accesses the network of China Unicom, it is said that the user of China Mobile roams to the network of China Unicom. .
  • the user's home network is called the user's home network, also called the home public land mobile network (home public land mobile network, HPLMN); the network to which the user roams is called the user's visited network, also called the visited public land mobile network.
  • Network (visited public land mobile network, VPLMN).
  • PDU session Session
  • home routed PDU session home routed PDU Session
  • HR PDU Session home routed PDU Session
  • local transfer out PDU session local breakout PDU Session, LBO PDU session
  • a group is usually composed of multiple group members, and managing members in groups can bring convenience to management.
  • a group is identified by a group identifier (group ID), and a group can contain multiple group members (all members belong to the same PLMN).
  • AF When AF creates a group, it provides an external group ID (External Group ID), which is used to identify the group on the AF side, and also provides a list of UE members contained in the group;
  • External Group ID External Group ID
  • the group information provided by AF will eventually be sent to UDM, and UDM will generate an Internal group ID corresponding to the External group ID, which is used to identify the group within the 5GC network; at the same time, UDM will save the group members corresponding to the Internal group ID list.
  • the embodiments shown below do not specifically limit the specific structure of the execution subject of the method provided by the embodiment of the present application, as long as the program that records the code of the method provided by the embodiment of the present application can be run to provide the method according to the embodiment of the present application.
  • the execution subject of the method provided by the embodiment of the present application may be a core network device, or a functional module in the core network device that can call a program and execute the program.
  • for indicating can be understood as “enabling”, and “enabling” can include direct enabling and indirect enabling.
  • enabling can include direct enabling and indirect enabling.
  • information for enabling A it may include that the information directly enables A or indirectly enables A, but it does not mean that A must be carried in the information.
  • the information enabled by the information is called the information to be enabled.
  • the information to be enabled can be directly enabled.
  • the to-be-enabled information may also be indirectly enabled by enabling other information, where there is an association relationship between the other information and the to-be-enabled information.
  • specific information can also be enabled by means of a pre-agreed (for example, protocol-specified) arrangement order of each information, thereby reducing the enabling overhead to a certain extent.
  • common parts of each information can be identified and enabled uniformly, so as to reduce the enabling overhead caused by enabling the same information separately.
  • pre-configuration may include pre-definition, for example, protocol definition.
  • predefinition for example, protocol definition.
  • “predefine” can be realized by pre-saving corresponding codes, tables or other methods that can be used to indicate related information in the device (for example, including each network element), and this application does not limit its specific implementation.
  • the "storage” mentioned in the embodiment of the present application may refer to saving in one or more memories.
  • the one or more memories may be provided independently, or may be integrated in an encoder or decoder, a processor, or a communication device.
  • the one or more memories may also be partially set independently, and partially integrated in a decoder, processor, or communication device.
  • the type of the storage may be any form of storage medium, which is not limited in this application.
  • the "protocol” involved in the embodiment of this application may refer to a standard protocol in the communication field, for example, it may include 5G protocol, new radio (new radio, NR) protocol and related protocols applied in future communication systems. Applications are not limited to this.
  • the following introduces a method 200 for configuring policies with reference to FIG. 2 .
  • the method 200 includes:
  • the AF generates an AF request (Creation of AF request) message, which may include the following information elements: relevant information of the target UE (such as target UE identifier (Target UE Identifier)), edge computing/application server address list (DNAIs) with information for identifying traffic (DNN, S-NSSAI, ApplicationID or AF-service-Identifier), data path QoS monitoring requests, etc.
  • relevant information of the target UE such as target UE identifier (Target UE Identifier)
  • DNAIs edge computing/application server address list with information for identifying traffic
  • DNN S-NSSAI
  • ApplicationID ApplicationID
  • AF-service-Identifier data path QoS monitoring requests
  • the relevant information of the target UE can be a single UE (individualUE), which can be identified by GPSI, IP address/prefix or MAC address, or a group of UEs (agroup of UE), which can be identified by an external groupID, or can be identified by DNN, S - Any UE identified by a combination of NSSAI and DNAI (anyUE).
  • individualUE can be identified by GPSI, IP address/prefix or MAC address
  • a group of UEs which can be identified by an external groupID, or can be identified by DNN, S - Any UE identified by a combination of NSSAI and DNAI (anyUE).
  • the AF can also carry traffic routing control information through the AF request message.
  • the AF can carry a group ID (groupID) in the AF request message, so as to provide access control for multiple UEs in the group Strategy.
  • groupID group ID
  • the AF sends an AF request message to the NEF.
  • the AF invokes the Nnef_TrafficInfluence service to send the generated application layer information to the NEF, and the main operations include creating, updating, and deleting requests.
  • the NEF saves the received application layer information into the UDR.
  • the NEF deletes the application layer information in the UDR.
  • the NEF sends an AF request response message to the AF.
  • NEF sends a response message to AF.
  • the UDR sends a DM notification message to the PCF.
  • the PCF subscribes to the modification requested by the AF, and the UDR sends a Nudr_DM_Notify notification of the data change to the PCF.
  • PCF determines service-related PDU session formulation and corresponding policies according to application layer information and requests.
  • PCF sends SM policy control update notification to SMF
  • PCF calls Npcf_SMPolicyControl_UpdateNotify service to send the policy update to SMF/I SMF, and the message can carry groupID to indicate that the policy is aimed at multiple UEs in the group.
  • the SMF and the UPF perform traffic routing reconfiguration (Traffic Routing Reconfiguration).
  • SMF After receiving relevant policies from PCF, SMF performs service flow routing reconfiguration with UPF according to relevant policies.
  • AF can define policies through the group mechanism, that is, AF can pre-define a group and the group members it contains, and then use the group ID to refer to the group members.
  • the group mechanism can only target the non-roaming (non-roaming) scenario of the same PLMN, that is, the group can only contain UEs of the same PLMN. Therefore, the AF cannot simultaneously define policies for UEs of different PLMNs. For example, the AF cannot simultaneously perform access policy control on roaming users and non-roaming users.
  • FIG. 3 shows an exemplary flowchart of a method 300 for configuring a policy provided by an embodiment of the present application.
  • a possible implementation manner (referred to as scheme A) provided by the embodiment of the present application is introduced in conjunction with method 300 .
  • the method 300 includes:
  • the AF generates a policy
  • the policy may be an application-specific policy, and the policy may also be called an access control policy, or a traffic offload policy (traffic offload policy).
  • the policy may be, for example, allowing members belonging to a certain group to access the edge control.
  • the AF sends service flow routing control information and first service type information to the NEF.
  • the AF may call the Nnef_TrafficInfluence service to send the traffic routing control information corresponding to the policy and the first service category (service category) information to the NEF, where the traffic routing control information corresponds to the first service category information.
  • the service flow routing control information may be information used to control/influence the service flow routing, for example, the service flow routing control information is used to route the service flow to the local access of the data network.
  • the service flow routing control information may include service descriptor information (e.g. Application ID, FQDN, IP quintuple), application location information (e.g. DNAI), target UE identification information (e.g. UE ID, group ID), N6 interface Service routing requirements information, etc.
  • service descriptor information e.g. Application ID, FQDN, IP quintuple
  • application location information e.g. DNAI
  • target UE identification information e.g. UE ID, group ID
  • N6 interface Service routing requirements information etc.
  • the service flow routing control information may have other names, for example, the service flow routing control information may also be called access control policy information or service routing control information, which is not limited in this application.
  • service flow in this application can also be called “service”, for example, “service flow routing control information” can also be called “service routing control information”, and the two can be interchanged in equivalent value.
  • service flow routing control information may also be referred to as application function request information.
  • the first service type information may be between the user equipment and an operator (such as a network operator), or between the user equipment and an application service provider (such as a company that provides various Internet application services, such as Google, Facebook, Tencent, etc.) Signing information between members (for example, video member (Video VIP) signing information).
  • the operator or the application service provider can provide different services, strategies, etc. for the subscriber according to the subscription information.
  • the first service type information may include information about services or applications that users are allowed to use, such as: service identification information, service name information, service scope information, service category information, service category information that is allowed to be used, and service name information that is allowed to be used , service scope information allowed, application descriptor information (fully qualified domain name (fully qualified domain name, FQDN), application identifier (App ID), five-tuple, etc.), subscriber level information, subscriber category information, group identification information to which the user belongs, etc.
  • the first service type information includes first service type information and/or first subscriber type information.
  • the first service category information may be information about services or applications that can be used by the user equipment. For example, information about services or applications that users are allowed to use (for example, service identification information, service name information, service scope information, service category information, service category information that is allowed to be used, service name information that is allowed to be used, service scope information that is allowed to be used, Application descriptor information (FQDN, App ID, quintuple, etc.); the first subscriber category information can be the service information subscribed by the user equipment, the level information of the subscriber (such as gold, silver and copper users), and the category information of the subscriber , the group identification information to which the user belongs, etc.
  • the first service type information may be included in the service flow routing control information as part of the service flow routing control information, or the first service type information may not be included in the service flow routing control information. control information.
  • the message may also include an identifier of the target UE (Target UE Identifier), and the AF sets the Target UE Identifier to any UE (anyUE) or Group ID.
  • Target UE Identifier an identifier of the target UE
  • the AF sets the Target UE Identifier to any UE (anyUE) or Group ID.
  • the message may further include the first application identification information and/or the first application service provider identification information.
  • the first application identification information and the first application service provider identification information correspond to the first service type information. It should be understood that the AF may only send one of the first application identification information and the first application service provider identification information.
  • the first application identification information is used to identify the application, and the first application service provider identification information is used to identify the application service provider.
  • the first application identification information may be, for example, an application identifier (APP ID) or FQDN information, IP quintuple information etc.;
  • the application service provider identifier can be, for example, an application service provider identifier (application service provider identifier, ASP ID), application service provider name, etc., such as Tencent, Google, WeChat, YouTube, etc.
  • the NEF sends the service flow routing control information and the first service type information to the UDR.
  • the UDR receives service flow routing control information and first service type information from the NEF.
  • the UDR sends the service flow routing control information and the first service type information to the PCF.
  • the PCF receives service flow routing control information and first service type information from the UDR.
  • the NEF also sends the first application identification information and/or the first application service provider identification information to the UDR.
  • the UDR sends the first application identification information and/or the first application service provider identification information to the PCF.
  • the NEF invokes the Nnef_TrafficInfluence service to send traffic routing control information and first service type information to the UDR, and the Target UE Identifier is set to anyUE or group ID.
  • the message further includes first application identification information and/or first application service provider identification information.
  • the UDR After receiving the service flow routing control information and the first service type information (optionally including the first application identification information and/or the first application service provider identification information) from the NEF, the UDR uses the Nudr_DM_Notify service to send the received service to the PCF.
  • the flow routing control information, the first service type information, the Target UE Identifier is set to anyUE or group ID, and optionally the message also includes the first application identification information and/or the first application service provider identification information.
  • the PCF may store these information.
  • S301 to S304 may be performed independently, or may be performed in combination with subsequent steps (S305 to S310), which are not limited in this application.
  • subsequent steps may be executed immediately after S304 is executed, or may be executed after a period of time after S304 is executed, which is not limited in this application.
  • the PCF acquires subscription information of the user equipment.
  • the PCF obtains subscription information of the user equipment from the UDR.
  • the UDR sends subscription information of the user equipment to the PCF, where the subscription information includes second service type information and an identifier of the user equipment (denoted as UEID).
  • the subscription information includes second service type information and an identifier of the user equipment (denoted as UEID).
  • the subscription information of the user equipment may be the subscription information between the user equipment and the operator, or the subscription information between the user equipment and the application service provider.
  • the contract information between the user equipment and the application service provider may also be referred to as "application data”.
  • the second service type information includes second service type information and/or second subscriber type information.
  • second service type For the explanation of the second service type, reference may be made to the above explanation for the first service type information, which will not be repeated here.
  • the subscription information further includes second application identification information and/or second application service provider identification information.
  • the UDR pre-stores the subscription information with the user equipment, and the specific manner is not limited here.
  • the PCF obtains the subscription information of the user equipment from the UDM through the SMF.
  • the SMF receives subscription information of the user equipment from the UDM, where the subscription information includes the second service type information and the UEID of the user equipment.
  • the SMF may request the UDM to acquire the subscription information of the user equipment when the user equipment accesses the network.
  • the UDM finds the subscription information of the user equipment according to the request of the SMF, it sends the subscription information of the user equipment to the SMF.
  • the UDM receives a subscription information request message from the SMF, the subscription information request message includes UEID, the UEID may be SUPI, for example, and the subscription information request message is used to request the subscription information of the user equipment.
  • the UDM stores and retrieves the subscription information of the user equipment locally according to the UEID.
  • the UDM When the UDM retrieves the subscription information of the user equipment, the UDM sends the subscription information of the UE to the SMF, and the subscription information includes the second service type of the UE. information.
  • the subscription information includes the second service type of the UE. information.
  • second application identification information and/or second application service provider identification information are also included.
  • the UDM pre-stores the subscription information of the user equipment, and the specific manner is not limited here.
  • the SMF sends the subscription information to the PCF, where the subscription information includes the second service type information, and optionally also includes the second application identification information and/or the second application service provider identification information.
  • the SMF obtains the subscription information of the user equipment through the UDM, it calls the Npcf_SMPolicyControl service to send the subscription information to the PCF.
  • the PCF generates a PCC rule (policy and charging control rule) for the user equipment corresponding to the first service type information according to the service flow routing control information.
  • the PCF After the PCF acquires the subscription information of the user equipment, it judges whether the user equipment is the user equipment corresponding to the first service type information according to the subscription information of the user equipment, and if so, the PCF provides the service flow routing control information for the user equipment according to the service flow routing control information.
  • the user equipment generates a PCC rule.
  • the PCF generates the PCC rule for the user equipment according to the service flow routing control information, which may mean that the PCF generates the PCC rule for the user equipment session (for example, a PDU session) according to the service flow routing control information.
  • the user equipment corresponding to the first service type information may refer to a user equipment that subscribes to the first service type information, or a user equipment that indicates a corresponding relationship with the first service type information in the application data.
  • PCC rules are used to control the routing of service flows.
  • the PCC rule includes service flow guidance control information, for example, service flow identification information, DNAI information, service flow guidance policy information, N6 interface service flow routing information, and the like.
  • the PCF may also need other information to generate the PCC rule, which is not limited in this application.
  • the user equipment corresponding to the first service type information may refer to the user equipment that has subscribed to the first service type information, or refers to the user equipment corresponding to the first service type information in the application data.
  • the user equipment that has signed the first service type information may refer to the user equipment that has signed the first service type information with the operator, or may refer to the user equipment that has signed the first service type information with the application.
  • the PCF judges whether the second service type information matches the first service type information, and if they match, the PCF determines that the user equipment is the user equipment corresponding to the first service type information.
  • the matching of the second service type information with the first service type information may mean that the second service type information is included in the first service type information.
  • the PCF may also determine whether the second application identification information and/or the second application service provider identification information match the first application identification information and/or the first application service provider identification information, and if they match, the PCF determines The user equipment is the user equipment corresponding to the first service type information.
  • the second application identification information and/or the second application service provider identification information matches the first application identification information and/or the first application service provider identification information, which may refer to the second application identification information and/or the second application
  • the service provider identification information is the same as the first application identification information and/or the first application service provider identification information.
  • the PCF sends the PCC rule to the SMF.
  • the PCF after the PCF generates the PCC rule for the user equipment, it sends the PCC rule to the SMF.
  • the PCF invokes the Npcf_SMPolicyControl service to send the PCC rule to the SMF.
  • the UEID is also carried in the message.
  • the SMF configures the user plane of the UE based on the PCC rule.
  • the SMF after receiving the PCC rule for the user equipment from the PCF, the SMF generates the corresponding user plane configuration, that is, executes the policy, and the specific method is not limited in this application.
  • the AF when the AF provides the service flow routing control information to the PCF through the UDR, it also provides service type information corresponding to the service flow routing control information (that is, the first service type information). Therefore, when the PCF determines that the service type information in the subscription information of a user equipment is the same as the service type information corresponding to the service flow routing control information, the PCF can use the service flow routing control information to generate a PCC rule for the user equipment.
  • the network device configures access control policies for multiple different users at the same time, and the multiple different users may belong to users under different PLMNs, that is, the method for configuring policies provided in the embodiment of the present application can simultaneously provide access control policies for roaming users Configure access control policies for non-roaming users.
  • solution B Another possible implementation manner (referred to as solution B) provided by the embodiment of the present application is introduced below with reference to the exemplary flowchart of the method 300 in FIG. 3 .
  • the first service type information includes multiple service type information.
  • the first service type information may be a collection of multiple service type information, and each service type information in the multiple service type information here may include the first service type information and/or the first signatory category information , but it should be understood that the first service type information and/or the first subscriber category information included in different service type information may be the same or different, which is not limited in this application.
  • the first service type information includes Service Category#1 and Service Category#2; or, the first service type information is a logical combination of multiple service type information, for example, the first service type information is Service Category#1 OR Service Category #2, or Service Category#1 AND Service Category#2.
  • the PCF generates a policy and charging control rule for the user equipment corresponding to the first service type information according to the service flow routing control information.
  • the PCF After the PCF acquires the subscription information of the user equipment, it judges whether the user equipment is the user equipment corresponding to the first service type information according to the subscription information of the user equipment, and if so, the PCF provides the service flow routing control information for the user equipment according to the service flow routing control information.
  • the user equipment generates policy and charging control rules (PCC rules).
  • PCC rules policy and charging control rules
  • the PCF generates the PCC rule for the user equipment according to the service flow routing control information, which may refer to that the PCF generates the PCC rule for the PDU session of the user equipment according to the service flow routing control information.
  • the PCF judges whether the second service type information matches the first service type information, and if they match, the PCF determines that the user equipment is the user equipment corresponding to the first service type information.
  • the first service type information includes multiple pieces of service type information.
  • the matching of the second service type information with the first service type information may mean that the second service type information includes multiple service type information in the first service type information, or the second service type information includes At least one of the plurality of service type information in the first service type information.
  • the first service type information includes Service Category#1 and Service Category#2, and when the second service type information includes Service Category#1 and Service Category#2, it means that the second service type information matches the first service type information; Or, when the second service type information includes at least one or more of Service Category#1 and Service Category#2, it means that the second service type information matches the first service type information;
  • the first service type information is a logical combination of multiple service type information.
  • the matching of the second service type information with the first service type information may refer to that the second service type information satisfies a logical combination of the plurality of service type information.
  • the combination information of the first service type is service category#1 AND service category#2, when the second service type information includes service category#1 and service category#2 at the same time, it means that the second service type information and the plurality of service A logical combination of type information.
  • the first service type combination information is service category#1 OR service category#2, then when the second service type information includes at least one of service category#1 and service category#3, it means that the second service type information and The logical combination of the plurality of service type information matches.
  • S309 and S310 in solution B are similar to S309 and S310 in solution A, and will not be repeated here.
  • the policy control network element can generate a policy and charging control rule for the user equipment corresponding to the first service type information according to the service flow routing control information. Therefore, the above solution can simultaneously configure policies for one or more users corresponding to the first service type information, for example, configure policies for users belonging to different PLMNs, thereby improving the efficiency of policy configuration and saving resources.
  • the user equipment corresponding to the first service type information includes roaming user equipment and non-roaming user equipment.
  • FIG. 4 shows an exemplary flowchart of a method 400 for configuring policies provided by an embodiment of the present application.
  • method 400 includes:
  • an operator or an application service provider signs an application layer service with one or more users.
  • the AF sends the subscriber's identification information and service type information to the NEF.
  • the NEF receives the identification information and service type information of the subscriber from the AF.
  • the subscriber ID information includes one or more subscriber IDs (Subscriber ID(s)).
  • Subscriber ID(s) subscriber ID(s)
  • the AF can call Nnef_ParameterProvision to send the identification information of the subscribers and the service type information corresponding to the subscription to the NEF.
  • subscriber may also be referred to as “user equipment”, and the two may be used interchangeably.
  • subscriber identification may also be referred to as “user equipment identification”
  • subscriber identification information may also be referred to as As “identification information of user equipment”
  • subscriber group may also be referred to as “user equipment group”.
  • the AF may also send application identification information (such as APPID) and/or application service provider identification information (such as ASP ID) to the NEF;
  • application identification information such as APPID
  • application service provider identification information such as ASP ID
  • the AF may also send validity period information to the NEF, and the validity period may refer to the subscription validity period.
  • the NEF authenticates and authorizes the message from the AF.
  • the NEF authenticates and authorizes the message from the AF to ensure that the AF has the right to perform related operations.
  • the NEF After the NEF passes the authentication and authorization of the message from the AF, the NEF sends the received application subscription information to the UDR or UDM, and examples are given below.
  • AF sends application subscription information to UDR:
  • the NEF sends the identification information of the subscriber and the service type information corresponding to the identification information of the subscriber to the UDR.
  • the UDR receives the identification information of the subscriber and the service type information from the NEF.
  • the NEF may also send application identification information and/or application provider identification information to the UDR.
  • the NEF can also send validity period information to the UDR.
  • the UDR stores the identification information and service type information of the subscriber.
  • the UDR after receiving the identification information and service type information of the subscriber from the NEF, the UDR stores the identification information and the service type information of the subscriber locally.
  • the UDR receives application identification information and/or application provider identification information, or validity period information from the NEF, the UDR also saves these information locally.
  • the AF sends the application subscription information to the UDM.
  • the NEF sends the identification information of the subscriber and the service type information corresponding to the identification information of the subscriber to the UDM.
  • the UDM receives the identification information of the subscriber and the service type information from the NEF.
  • the NEF may also send application identification information and/or application provider identification information to the UDM.
  • the NEF can also send validity period information to the UDM.
  • the UDM saves the ASPID/APP ID, service type information, and validity period in the subscription data of the subscriber.
  • the UDM after receiving the identification information and service type information of the subscriber from the NEF, the UDM saves the service type information to the subscriber (Subscriber(s)) corresponding to the identification information (Subscriber ID(s)) of the subscriber In the subscription data (Subscription data).
  • the UDM receives the application identification information and/or application provider identification information, or validity period information from the NEF, the UDM also saves these information in the subscription data of the subscriber corresponding to the identification information of the subscriber.
  • the UDM sends the subscriber's identification information and service type information to the UDR.
  • the UDM may send the information received from the NEF to the UDR, so as to store the information parameters in the UDR database.
  • the method 400 can be implemented independently or in combination with the method 300 .
  • the method 400 may be used as a preparation solution of the method 300 and executed before the method 300, which is not limited in the present application.
  • the signing information can be sent to the UDM/UDR through the AF.
  • the UDM/UDR can save the received subscription information of the user. So that the subsequent PCF can determine whether a corresponding PCC rule can be generated for the user according to the parameters in the subscription information of the user, so as to achieve the purpose of configuring policies for multiple users.
  • FIG. 5 shows an exemplary flowchart of a method 500 for configuring a policy provided by an embodiment of the present application. As can be seen from FIG. 5, method 500 includes:
  • the AF generates an application-specific policy.
  • the AF can generate a policy for the application, and the policy can also be called an access control policy, or a traffic offload policy (traffic offload policy).
  • the policy may be, for example, allowing members belonging to a certain group to access the edge control.
  • the AF sends the service flow routing control information and the identification information of the user equipment group to the NEF.
  • the AF may call the Nnef_TrafficInfluence service to send the service flow routing control information corresponding to the policy and the identification information of the user equipment group to the NEF.
  • the identification information of the user equipment group may include an identification for identifying the user equipment group, and the user equipment group includes one or more subscribers.
  • the identification of the user equipment group may be called a group identification (group ID) or an external group identification, for example. (external group ID).
  • group ID group identification
  • external group ID for example.
  • the identification information of the user equipment group can be used to index information in the UDR.
  • a user equipment group can also be called a subscriber group, and a subscriber can also be called a user equipment, that is, this application does not limit the names of related terms, and similar names can be used in different scenarios Mutual replacements, expressions that can be understood or conceived by those skilled in the art should all fall within the protection scope of the embodiments of the present application.
  • the message may also carry the first application identification information and/or the first application service provider identification information.
  • the first application identification information and the first application service provider identification information correspond to the first service type information. It should be understood that the AF may only send one of the first application identification information and the first application service provider identification information.
  • the NEF sends the service flow routing control information and the identification information of the user equipment group to the UDR.
  • the UDR receives the service flow routing control information and the identification information of the user equipment group from the NEF.
  • the NEF sends the information received from the AF to the UDR.
  • the NEF invokes the Nnef_TrafficInfluence service to send the received service flow routing control information and user equipment group identification information to the UDR.
  • the NEF also receives the first application identifier and/or the first application provider identifier, the NEF also sends the first application identifier and/or the first application provider identifier to the UDR.
  • the UDR sends the service flow routing control information and the identification information of the subscriber to the PCF.
  • the UDR determines the identification information of one or more subscribers corresponding to the identification information of the user equipment group according to the identification information of the user equipment group.
  • the one or more subscribers may refer to subscribers belonging to the user equipment group, and the identification information of the one or more subscribers may be an identification set (Subscriber ID(s)) of the one or more subscribers.
  • the UDR sends the service flow routing control information and the identification information of the one or more subscribers to the PCF.
  • the UDR uses the Nudr_DM_Notify message to send service flow routing control information and identification information of one or more subscribers to the PCF.
  • the UDR pre-stores the association relationship between the identification information of the user equipment group and the identification information of one or more subscribers. After the ASP signs up with the user, the UDR may receive and save the identification information of the user equipment group and the identification information of one or more subscribers from the NEF. This embodiment does not specifically limit the specific implementation.
  • the PCF can store these information.
  • the identification information of the subscriber may correspond to the service flow routing control information.
  • the service flow routing control information corresponds to the subscriber's identification information, which means that the service flow routing control information is associated with the subscriber's identification information, or the service flow routing control information is used for the subscriber.
  • the user equipment generates policies and charging control rules corresponding to the identification information of the subscriber, or the service flow routing control information corresponds to the user equipment group to which the subscriber belongs in the identification information of the subscriber.
  • S501 to S504 may be performed independently, or may be performed in combination with subsequent steps (S505 to S510), which are not limited in this application.
  • subsequent steps may be executed immediately after S504 is executed, or may be executed after a period of time after S504 is executed, which is not limited in this application.
  • the PCF acquires subscription information of the user equipment.
  • the PCF obtains subscription information of the user equipment from the UDR.
  • the UDR sends subscription information of the user equipment to the PCF, where the subscription information includes an identifier of the user equipment.
  • the identifier of the user equipment may be, for example, the GPSI of the user equipment.
  • the UDR receives the subscription information of the user equipment from the PCF.
  • the subscription information further includes second application identification information and/or second application service provider identification information.
  • the UDR pre-stores the subscription information of the user equipment that has subscribed with the ASP, and the specific method is not limited here.
  • the PCF obtains the subscription information of the user equipment from the UDM through the SMF.
  • the SMF receives subscription information of the user equipment from the UDM, where the subscription information includes the identifier of the user equipment (optionally, may also include second application identifier information and/or second application service provider identifier information).
  • the subscription information includes the identifier of the user equipment (optionally, may also include second application identifier information and/or second application service provider identifier information).
  • the specific implementation manner is similar to S306 in the method 300, and will not be repeated here.
  • the UDM pre-saves the subscription information of the UE that has subscribed with the ASP, and the specific method is not limited here.
  • the SMF sends the subscription information to the PCF, where the subscription information includes the identifier of the user equipment.
  • the identifier of the user equipment may include the GPSI and/or SUPI of the user equipment.
  • the SMF invokes the Npcf_SMPolicyControl service to send the subscription information to the PCF.
  • the PCF generates a PCC rule for the subscriber according to the service flow routing control information.
  • the PCF obtains the subscription information of the user equipment, it judges whether the user equipment belongs to a subscriber according to the identifier of the user equipment, and if so, the PCF generates a PCC rule for the user equipment according to the service flow routing control information.
  • the PCF generates the PCC rule for the user equipment according to the service flow routing control information, which may refer to that the PCF generates the PCC rule for the PDU session of the user equipment according to the service flow routing control information.
  • the PCF After the PCF obtains the subscription information of the user equipment, it obtains the identifier of the user equipment from the subscription information of the user equipment. When the identifier of the user equipment is included in the identifier of the subscriber, the PCF determines that the user equipment belongs to the subscriber.
  • the PCF may also determine whether the second application identification information and/or the second application service provider identification information match the first application identification information and/or the first application service provider identification information, and if they match, the PCF determines The user equipment is the user equipment corresponding to the first service type information.
  • the second application identification information and/or the second application service provider identification information matches the first application identification information and/or the first application service provider identification information, which may refer to the second application identification information and/or the second application
  • the service provider identification information is the same as the first application identification information and/or the first application service provider identification information.
  • S509 and S510 are similar to S309 and S310 in the method 300, and will not be repeated here.
  • AF when AF provides service flow routing control information to PCF through UDR, it also provides identification information of the user equipment group corresponding to the service flow routing control information, and UDR can group the user equipment group according to the identification information of the user equipment group
  • the list of subscriber IDs in the service flow is sent to the PCF together with the service flow routing control information. Therefore, when the PCF determines that the identifier of a certain user equipment is included in the subscriber identifier list, the PCF can use the service flow routing control information to generate a PCC rule for the user equipment.
  • the policy control network element can generate policy and charging control rules for subscribers according to the service flow routing control information. Therefore, the above solution can configure policies for one or more subscribers at the same time, for example, can configure policies for subscribers belonging to different PLMNs, thereby improving the efficiency of policy configuration and saving resources.
  • FIG. 6 shows an exemplary flowchart of a method 600 provided by an embodiment of the present application. As can be seen from FIG. 6, the method 600 includes:
  • an application service provider signs an application layer service with one or more users.
  • the AF sends the identification information of the subscriber and the identification of the user equipment group to the NEF.
  • the NEF receives the identification information of the subscriber and the identification of the user equipment group from the AF.
  • the identification information of the subscriber includes one or more subscriber IDs (Subscriber ID(s)), and the user equipment group includes the one or more subscribers.
  • the identification information of the subscriber corresponds to the identification of the user equipment group.
  • the AF may call Nnef_ParameterProvision to send the identification information of the one or more subscribed users and the identification of the user equipment group corresponding to the subscription to the NEF.
  • the AF may also send application identification information (such as APP ID) and/or application service provider identification information (such as ASP ID) to the NEF;
  • application identification information such as APP ID
  • ASP ID application service provider identification information
  • the AF may also send validity period information to the NEF, and the validity period may refer to the subscription validity period.
  • the NEF authenticates and authorizes the message from the AF.
  • the NEF authenticates and authorizes the message from the AF to ensure that the AF has the right to perform related operations.
  • the NEF After the NEF passes the authentication and authorization of the message from the AF, the NEF sends the received application subscription information to the UDR or UDM, and examples are given below.
  • AF sends application subscription information to UDR:
  • the NEF sends the identification information of the subscriber and the identification of the user equipment group corresponding to the identification information of the subscriber to the UDR.
  • the UDR receives the identification information of the subscriber and the identification of the user equipment group from the NEF.
  • the NEF may also send application identification information and/or application provider identification information to the UDR.
  • the NEF can also send validity period information to the UDR.
  • the UDR stores the identification information of the subscriber and the identification of the user equipment group.
  • the UDR after receiving the identification information of the subscriber and the identification of the user equipment group from the NEF, the UDR stores the identification information of the subscriber and the identification of the user equipment group locally.
  • the UDR receives application identification information and/or application provider identification information, or validity period information from the NEF, the UDR also saves these information locally.
  • the AF sends the application subscription information to the UDM.
  • the NEF sends the identification information of the subscriber and the identification of the user equipment group corresponding to the identification information of the subscriber to the UDM.
  • the UDM receives the identification information of the subscriber and the identification of the user equipment group from the NEF.
  • the NEF may also send application identification information and/or application provider identification information to the UDM.
  • the NEF can also send validity period information to the UDM.
  • the UDM saves the ASP ID/APP ID, the identifier of the user equipment group, and the validity period in the subscription data of the subscriber.
  • the UDM after receiving the identification information of the subscriber and the identification of the user equipment group from the NEF, the UDM saves the identification of the user equipment group to the subscriber (Subscriber ID(s)) corresponding to the identification information (Subscriber ID(s)) of the subscriber. (s)) in the subscription data (Subscription data).
  • the UDM receives the application identification information and/or application provider identification information, or validity period information from the NEF, the UDM also saves these information in the subscription data of the subscriber corresponding to the identification information of the subscriber.
  • the UDM sends the identification information of the subscriber and the identification of the user equipment group to the UDR.
  • the UDM may send the information received from the NEF to the UDR, so as to store the information parameters in the UDR database.
  • the method 600 can be implemented independently or in combination with the method 500 .
  • the method 600 may be used as a preparation solution of the method 500 and executed before the method 500, which is not limited in the present application.
  • the AF can send the ID of the user equipment group and the ID information of the subscriber to the UDM/UDR, so that the PCF can generate PCC rules for the subscriber according to the service flow routing control information, thereby implementing multiple The purpose of individual user configuration policies.
  • FIG. 7 shows an exemplary flowchart of a method 700 for configuring a policy provided by an embodiment of the present application. As can be seen from FIG. 7, method 700 includes:
  • the AF generates an application-specific policy.
  • the AF sends service flow routing control information and service type information to the NEF.
  • the NEF sends service flow routing control information and service type information to the UDR.
  • S701 to S703 are similar to S301 to S303 in the method 400, and for the sake of brevity, the description is not repeated here.
  • the UDR sends the service flow routing control information and the identification information of the subscriber to the PCF.
  • the UDR determines the identification information of the subscriber corresponding to the service type information according to the service type information, and sends the identification information of the subscriber together with the service flow routing control information to the PCF.
  • the UDR uses the Nudr_DM_Notify message to send the service flow routing control information and the identification information of the subscriber to the PCF.
  • the UDR pre-stores the association between the service type information and the identification information of the subscriber. After the ASP signs up with the user, the UDR may receive and save the service type information and the identification information of the subscriber from the NEF, which is not specifically limited in this embodiment.
  • the PCF can save these information .
  • S701 to S704 may be performed independently, or may be performed in combination with subsequent steps (S705 to S710), which are not limited in this application.
  • subsequent steps may be executed immediately after S804 is executed, or may be executed after a period of time after S704 is executed, which is not limited in this application.
  • the PCF acquires subscription information of the user equipment.
  • the PCF obtains subscription information of the user equipment from the UDR.
  • the UDR sends subscription information of the user equipment to the PCF, where the subscription information includes an identifier of the user equipment.
  • the identifier of the user equipment may be, for example, the GPSI of the user equipment.
  • the UDR receives the subscription information of the user equipment from the PCF.
  • the subscription information further includes second application identification information and/or second application service provider identification information.
  • the UDR pre-stores the subscription information of the user equipment that has subscribed with the ASP, and the specific method is not limited here.
  • the PCF obtains the subscription information of the user equipment from the UDM through the SMF.
  • the SMF receives subscription information of the user equipment from the UDM, where the subscription information includes the identifier of the user equipment.
  • the second application identification information and/or the second application service provider identification information may also be included.
  • the specific implementation manner is similar to S306 in the method 400, and will not be repeated here.
  • the SMF sends the subscription information to the PCF, where the subscription information includes the identifier of the user equipment.
  • the identifier of the user equipment may include the GPSI and/or SUPI of the user equipment.
  • the SMF invokes the Npcf_SMPolicyControl service to send the subscription information to the PCF.
  • the PCF generates a PCC rule for the subscriber according to the service flow routing control information.
  • S708 is similar to S508 in method 500, and for the sake of brevity, details are not repeated here.
  • S709 and S710 are similar to S309 and S310 in the method 300, and will not be repeated here.
  • the AF when the AF provides the service flow routing control information to the PCF through the UDR, it also provides the service type information corresponding to the service flow routing control information.
  • the subscriber ID and the service flow routing control information are sent to the PCF together. Therefore, when the PCF determines that the identity of a certain user equipment is included in the identity of the subscriber, the PCF can use the service flow routing control information to generate a PCC rule for the user equipment.
  • the policy control network element can generate policy and charging control rules for subscribers according to the service flow routing control information. Therefore, the above solution can configure policies for one or more subscriptions at the same time, for example, can configure policies for subscribers belonging to different PLMNs, thereby improving the efficiency of policy configuration and saving resources.
  • FIG. 8 shows an exemplary flowchart of a method 800 provided by an embodiment of the present application. As can be seen from FIG. 8, method 800 includes:
  • an application service provider signs an application layer service with one or more users.
  • the AF sends the subscriber's identification information and service type information to the NEF.
  • the NEF receives the identification information and service type information of the subscriber from the AF.
  • the subscriber identification information includes one or more subscriber IDs (Subscriber ID(s)).
  • the identification information of the subscriber corresponds to the service type information.
  • the AF may call Nnef_ParameterProvision to send the identification information of the one or more subscribed users and the service type information corresponding to the subscription to the NEF.
  • the AF may also send application identification information (such as APP ID) and/or application service provider identification information (such as ASP ID) to the NEF;
  • application identification information such as APP ID
  • ASP ID application service provider identification information
  • the AF may also send validity period information to the NEF, and the validity period may refer to the subscription validity period.
  • the NEF authenticates and authorizes the message from the AF.
  • the NEF authenticates and authorizes the message from the AF to ensure that the AF has the right to perform related operations.
  • the NEF After the NEF passes the authentication and authorization of the message from the AF, the NEF sends the received application subscription information to the UDR or UDM, and examples are given below.
  • AF sends application subscription information to UDR:
  • the NEF sends the identification information of the subscriber and the service type information corresponding to the identification information of the subscriber to the UDR.
  • the UDR receives the identification information of the subscriber and the service type information from the NEF.
  • the NEF may also send application identification information and/or application provider identification information to the UDR.
  • the NEF can also send validity period information to the UDR.
  • the UDR stores the identification information and service type information of the subscriber.
  • the UDR after receiving the identification information and service type information of the subscriber from the NEF, the UDR stores the identification information and the service type information of the subscriber locally.
  • the UDR receives application identification information and/or application provider identification information, or validity period information from the NEF, the UDR also saves these information locally.
  • the AF sends the application subscription information to the UDM.
  • the NEF sends the identification information of the subscriber and the service type information corresponding to the identification information of the subscriber to the UDM.
  • the UDM receives the identification information of the subscriber and the service type information from the NEF.
  • the NEF may also send application identification information and/or application provider identification information to the UDM.
  • the NEF can also send validity period information to the UDM.
  • the UDM saves the ASP ID/APP ID, service type information, and validity period in the subscription data of the subscriber.
  • the UDM after receiving the identification information and service type information of the subscriber from the NEF, the UDM saves the service type information to the subscriber (Subscriber(s)) corresponding to the identification information (Subscriber ID(s)) of the subscriber In the subscription data (Subscription data).
  • the UDM receives the application identification information and/or application provider identification information, or validity period information from the NEF, the UDM also saves these information in the subscription data of the subscriber corresponding to the identification information of the subscriber.
  • the UDM sends the subscriber's identification information and service type information to the UDR.
  • the UDM may send the information received from the NEF to the UDR, so as to store the information parameters in the UDR database.
  • the method 800 can be implemented independently or in combination with the method 700 .
  • the method 800 may be used as a preparation solution of the method 700 and executed before the method 700, which is not limited in the present application.
  • the service type information and the identification information of the subscriber can be sent to UDM/UDR through the AF, so that the PCF can generate PCC rules for the subscriber according to the service flow routing control information, thereby realizing multiple users The purpose of the configuration policy.
  • the ASP after the ASP signs up with the user, it can send the service type information and the identifier of the subscriber to the UDR through the AF.
  • the AF provides the service flow routing control information and the service flow routing control information to the UDR
  • the UDR can determine the identifier of the corresponding subscriber according to the service type information, and send the identifier of the subscriber and the service flow routing control information to the PCF. Therefore, when the PCF determines that a certain user equipment belongs to the subscriber, it can generate a PCC rule for the user equipment according to the service flow routing control information provided by the AF, thereby achieving the purpose of configuring policies for multiple users.
  • the names of various information or messages in this application are only possible examples, and there may be other names in different scenarios.
  • the first service type information may also be called first information
  • first The service category information may also be called the second information
  • the first signatory category information may also be called the third information
  • the service flow routing control information may also be called the service flow routing information, or the service flow routing influence information, or the service routing control information. information, or service routing impact information, or application function request information, etc., which are not limited in this application.
  • FIG. 9 shows an exemplary flowchart of a method 900 for configuring a policy provided by an embodiment of the present application.
  • solution a a possible implementation manner provided by the embodiment of the present application is introduced in combination with method 900 .
  • method 900 includes:
  • the AF generates service flow routing control information.
  • the AF may generate service flow routing control information, and the service flow routing control information may also be called an access control policy, or a traffic offload policy (traffic offload policy).
  • the service flow routing control information may be, for example, information used to control/influence the routing of the service flow, for example, the service flow routing control information is used to route the service flow to a local access to the data network.
  • the AF sends the service flow routing control information and the first group of information to the NEF.
  • the AF may invoke the Nnef_TrafficInfluence service to send the traffic routing control information and the first group of information to the NEF, where the first group of information corresponds to the traffic routing control information.
  • the first group of information includes a plurality of group IDs (group ID), for example, the first group of information includes a first group ID (marked as group ID1) and a second group ID (marked as group ID2), the first Group information can be recorded as group comb1. That is to say, the first group information in this embodiment may be a collection of multiple group identifiers. However, it should be noted that the first group of information may also include other information except the group identifier, which is not limited in this application.
  • group identifier in this application may also be referred to as group identifier information.
  • the group ID here can be either an internal ID or an external ID.
  • the first group ID is an internal group ID
  • the second group ID is an external group ID.
  • both the first group identifier and the second group identifier are internal group identifiers, etc., which are not specifically limited in this application.
  • the first group of information corresponds to the service flow routing control information, which means that the service flow routing control information is applicable to user equipment matching the first group of information, or in other words, the service flow routing control information is applicable to simultaneous subscription
  • the user equipments of the groups corresponding to the multiple group identifiers in the first group information in other words, the service flow routing control information is used to generate user equipments that simultaneously subscribe to the groups corresponding to the multiple group identifiers in the first group information Policy and charging control rules.
  • the AF may provide multiple pieces of first group information at the same time, and at this time, the service flow routing control information is used for user equipment whose subscription information matches at least one first group information.
  • the first group of information and the service flow routing control information may be two separate information elements; or, the first group of information may also be used as part of the service flow routing control information.
  • S902 may It is expressed as: the AF sends service flow routing control information to the NEF, and the service flow routing control information includes the first group of information.
  • the NEF sends the service flow routing control information and the second group of information to the UDR.
  • the NEF may call the Nudr_DM_Create service to send the service flow routing control information and the second set of information to the UDR, where the second set of information may be the same as the first set of information A set of information is the same, or may be converted from the first set of information.
  • the multiple group identifiers included in the first group information are all internal group identifiers, then the second group information is the same as the first group information at this time, that is, the NEF can directly send the received first group information to the UDR.
  • the NEF converts the external group identifiers in the first group information into internal group identifiers to obtain the second group information, and then The NEF sends the second set of information to the UDR.
  • the AF may also directly send the service flow routing control information and the first group of information to the UDR, which is not limited in this application.
  • the UDR sends the service flow routing control information and the second group of information to the PCF.
  • the UDR after receiving the service flow routing control information and the second group of information from the NEF, the UDR sends the service flow routing control information and the second group of information to the PCF.
  • the UDR uses the Nudr_DM_Notify message to send the service flow routing control information and the second group of information to the PCF.
  • the service flow routing control information and the second group of information may be carried in the same message, or in different messages, that is, the UDR may simultaneously send the service flow routing control information and the second group of information. information, or send the service flow routing control information and the second group of information separately.
  • the second group of information may be part of the service flow routing control information, or the second group of information and the service flow routing control information may be two separate information elements, which is not limited in this application.
  • the PCF may store these information.
  • the second group of information and the service flow routing control information may be two separate information elements; or, the second group of information may also be used as part of the service flow routing control information.
  • S903 may Expressed as: NEF sends service flow routing control information to UDR, the service flow routing control information includes the second group of information;
  • S904 can be expressed as: UDR sends service flow routing control information to PCF, and the service flow routing control information includes the second group of information information.
  • S901 to S904 may be performed independently, or may be performed in combination with subsequent steps (S905 to S910), which are not limited in this application.
  • subsequent steps may be executed immediately after S904 is executed, or may be executed after a period of time after S904 is executed, which is not limited in this application.
  • the PCF acquires subscription information of the user equipment.
  • the PCF obtains subscription information of the user equipment from the UDR.
  • the UDR sends the subscription information of the user equipment to the PCF.
  • the subscription information includes the group ID (group ID) of the group to which the user equipment subscribes, or in other words, the subscription information includes the group ID of the group to which the user equipment belongs.
  • the group identification in the subscription information may include identification information of one or more groups.
  • the UDR pre-stores the subscription information of the user equipment, and the specific manner is not limited here.
  • the PCF obtains the subscription information of the user equipment from the UDM through the SMF.
  • the SMF receives subscription information of the user equipment from the UDM, where the subscription information includes a group identifier of a group to which the user equipment subscribes.
  • the specific implementation manner is similar to S306 in the method 300, and will not be repeated here.
  • the UDM pre-stores the subscription information of the UE, and the specific manner is not limited here.
  • the SMF sends the subscription information to the PCF, where the subscription information includes the group identifier of the group subscribed by the user equipment.
  • the SMF invokes the Npcf_SMPolicyControl service to send the subscription information to the PCF.
  • the PCF generates a PCC rule for the user equipment matching the second group of information according to the service flow routing control information.
  • the PCF obtains the subscription information of the user equipment, it judges whether the user equipment matches the second group information according to the group identifier carried in the subscription information, and if it matches, the PCF generates an PCC rules.
  • the PCF generates the PCC rule for the user equipment according to the service flow routing control information may refer to that the PCF generates the PCC rule for the PDU session of the user equipment according to the service flow routing control information.
  • the PCF judges that the user equipment matches the second group information. In this case, the PCF routes the service flow according to the control information as The user equipment generates corresponding PCC rules.
  • the PCF sends the PCC rule to the SMF.
  • the SMF configures a user plane of the UE based on the PCC rule.
  • S909 and S910 are similar to S309 and S310 in the method 300, and will not be repeated here.
  • the AF when the AF provides the service flow routing control information to the PCF through the UDR, it also provides the group information corresponding to the service flow routing control information.
  • the PCF may use the service flow routing control information to generate a PCC rule for the user equipment.
  • the PCF can generate policy and charging control rules for the user equipment corresponding to the group information according to the service flow routing control information. Therefore, the above solution can configure policies for one or more subscribers at the same time, for example, can configure policies for subscribers belonging to different PLMNs, thereby improving the efficiency of configuring policies and saving resources.
  • solution b Another possible implementation provided by the embodiment of the present application (referred to as solution b) is introduced below with reference to the exemplary flow chart of the method in FIG. 9 .
  • the first group of information includes a logical combination of multiple group identification (group ID) information, for example, the first group of information includes the following information: group ID1 AND group ID2 NOT group ID3, or, group ID1 AND group ID2 AND group ID3. That is to say, the first group information in this embodiment may include multiple group identifiers, and the multiple group identifiers have a logical relationship. However, it should be noted that the first group of information may also include other information except the group identifier, which is not limited in this application.
  • the service flow routing control information corresponds to the first group of information, which means that the service flow routing control information is applicable to user equipment whose subscription data logically matches the first group of information.
  • the PCF generates a PCC rule for the user equipment matching the second group of information according to the service flow routing control information.
  • the PCF obtains the subscription information of the user equipment, it judges whether the user equipment matches the second group information according to the group identifier carried in the subscription information, and if it matches, the PCF generates an PCC rules.
  • the PCF determines that the user equipment matches the second group of information, where the subscription information of the user equipment logically matches the second group of information , means that the group identifier included in the subscription information of the user equipment satisfies the logical combination of multiple group identifier information in the second group information, for example, the second group information includes the following information: group ID1 AND group ID2 NOT group ID3, Then when the subscription information of the user equipment includes group ID1 and group 2, but does not include group ID3, it means that the subscription information of the user equipment is logically matched with the second group of information; for another example, the second group of information includes the following information: group ID1 AND group ID2 AND group ID3, when the subscription information of the user equipment includes group ID1, group ID2 and group ID3, it means that the subscription information of the user equipment logically matches the second group of information.
  • S909 and S910 are similar to S309 and S310 of the method 300, and are not repeated here for brevity.
  • the policy control network element can generate policy and charging control rules for the user equipment corresponding to the group information according to the service flow routing control information. Therefore, the above solution can simultaneously configure policies for one or more users corresponding to the first group of information, for example, configure policies for users belonging to different PLMNs, thereby improving the efficiency of policy configuration and saving resources.
  • FIG. 10 is a schematic block diagram of an apparatus 10 for configuring policies provided by an embodiment of the present application.
  • the device 10 includes a transceiver module 11 and a processing module 12 .
  • the transceiver module 11 can realize corresponding communication functions, the processing module 12 is used for data processing, or the transceiver module 11 is used for performing receiving and sending related operations, and the processing module 12 is used for performing other operations except receiving and sending .
  • the transceiver module 11 can also be called a communication interface or a communication unit.
  • the device 10 may correspond to various network devices in the above method embodiments, such as unified data management network elements (such as UDM), session management network elements (such as SMF), policy control network elements (such as PCF), unified data storage network element (such as UDR), and application function network element (such as AF).
  • unified data management network elements such as UDM
  • session management network elements such as SMF
  • policy control network elements such as PCF
  • UDR unified data storage network element
  • AF application function network element
  • the device 10 may correspond to the unified data management network element or session management network element or policy control network element or unified data storage network element or application function network element (UDM or SMF or PCF or UDR or AF).
  • UDM unified data management network element or session management network element or policy control network element or unified data storage network element or application function network element (UDM or SMF or PCF or UDR or AF).
  • the apparatus 10 may include modules for executing the methods executed by the foregoing network devices in FIG. 2 to FIG. 9 . Moreover, each unit in the device 10 and the above-mentioned other operations and/or functions are respectively for realizing the corresponding flow of the method shown in Fig. 2 to Fig. 9 .
  • the transceiver module 11 in the apparatus 10 performs the receiving and sending operations performed by the network devices in the above method embodiments, and the processing module 12 performs operations other than the receiving and sending operations.
  • FIG. 11 is a schematic diagram of an apparatus 20 for configuring a policy provided in an embodiment of the present application.
  • the device 20 may correspond to various network devices in the above method embodiments, such as unified data management network elements (such as UDM), session management network elements (such as SMF), policy control network elements (such as PCF), unified data storage network element (such as UDR), and application function network element (such as AF).
  • unified data management network elements such as UDM
  • SMF session management network elements
  • PCF policy control network elements
  • UDR unified data storage network element
  • AF application function network element
  • the device 20 may include a processor 21 (ie, an example of a processing module) and a memory 22 .
  • the memory 22 is used to store instructions
  • the processor 21 is used to execute the instructions stored in the memory 22, so that the apparatus 20 implements the steps performed by each network device in the method corresponding to FIG. 2 to FIG. 9 .
  • the device 20 may also include an input port 23 (ie, an example of a transceiver module) and an output port 24 (ie, another example of a transceiver module).
  • the processor 21 , the memory 22 , the input port 23 and the output port 24 can communicate with each other through internal connection paths, and transmit control and/or data signals.
  • the memory 22 is used to store a computer program, and the processor 21 can be used to call and run the computer program from the memory 22, to control the input port 23 to receive signals, and to control the output port 24 to send signals, so as to complete the terminal equipment or Steps for network devices.
  • the memory 22 can be integrated in the processor 21 or can be set separately from the processor 21 .
  • the input port 23 is a receiver
  • the output port 24 is a transmitter.
  • the receiver and the transmitter may be the same or different physical entities. When they are the same physical entity, they can be collectively referred to as transceivers.
  • the input port 23 is an input interface
  • the output port 24 is an output interface
  • the functions of the input port 23 and the output port 24 may be realized by a transceiver circuit or a dedicated chip for transceiver.
  • the processor 21 may be realized by a dedicated processing chip, a processing circuit, a processor or a general-purpose chip.
  • a general-purpose computer to implement the communication device provided in the embodiment of the present application.
  • the program codes to realize the functions of the processor 21 , the input port 23 and the output port 24 are stored in the memory 22 , and the general processor realizes the functions of the processor 21 , the input port 23 and the output port 24 by executing the codes in the memory 22 .
  • FIG. 12 shows a schematic structural diagram of a simplified network device 30 .
  • the network equipment includes 31 parts and 32 parts.
  • Part 31 is mainly used for the transmission and reception of radio frequency signals and the conversion between radio frequency signals and baseband signals; part 32 is mainly used for baseband processing and control of network equipment.
  • Part 31 may generally be referred to as a transceiver module, a transceiver, a transceiver circuit, or a transceiver.
  • the part 32 is usually the control center of the network device, which can be generally referred to as a processing module, and is used to control the network device to perform the processing operations on the network device side in the foregoing method embodiments.
  • the transceiver module of Part 31, which may also be referred to as a transceiver or transceiver, etc., includes an antenna and a radio frequency circuit, wherein the radio frequency circuit is mainly used for radio frequency processing.
  • the device used to realize the receiving function in Part 31 can be regarded as a receiving module
  • the device used to realize the sending function can be regarded as a sending module, that is, Part 31 includes a receiving module and a sending module.
  • the receiving module may also be called a receiver, receiver, or receiving circuit, etc.
  • the sending module may be called a transmitter, transmitter, or transmitting circuit, etc.
  • Section 32 may include one or more single boards, and each single board may include one or more processors and one or more memories.
  • the processor is used to read and execute programs in the memory to implement baseband processing functions and control network devices. If there are multiple single boards, each single board can be interconnected to enhance the processing capability. As an optional implementation, it is also possible that multiple single boards share one or more processors, or that multiple single boards share one or more memories, or that multiple single boards share one or more processors at the same time. device.
  • the network device shown in FIG. 12 may be any network device shown in the methods shown in FIG. 2 to FIG. 9, such as a unified data management network element (such as UDM), a session management network element (such as SMF), policy control network element (such as PCF), unified data storage network element (such as UDR), application function network element (such as AF) and so on.
  • a unified data management network element such as UDM
  • a session management network element such as SMF
  • policy control network element such as PCF
  • UDR unified data storage network element
  • AF application function network element
  • the transceiver module in part 31 is used to execute the steps related to the sending and receiving of any network device in the methods shown in FIGS. 2 to 9 ; step.
  • FIG. 12 is only an example rather than a limitation, and the foregoing network device including a transceiver module and a processing module may not depend on the structure shown in FIG. 12 .
  • the chip When the device 30 is a chip, the chip includes a transceiver module and a processing module.
  • the transceiver module may be an input-output circuit or a communication interface;
  • the processing module is a processor or a microprocessor or an integrated circuit integrated on the chip.
  • the embodiment of the present application further provides a computer-readable storage medium, on which computer instructions for implementing the method executed by the first network device in the above method embodiment are stored.
  • the computer program when executed by a computer, the computer can implement the method performed by the network device in the foregoing method embodiments.
  • the embodiments of the present application also provide a computer program product including instructions, which, when executed by a computer, enable the computer to implement the method executed by the first device or the method executed by the second device in the above method embodiments.
  • An embodiment of the present application further provides a communication system, where the communication system includes the network device in the foregoing embodiments.
  • the network device may include a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer.
  • the hardware layer may include hardware such as a central processing unit (central processing unit, CPU), a memory management unit (memory management unit, MMU), and memory (also called main memory).
  • the operating system of the operating system layer can be any one or more computer operating systems that realize business processing through processes, for example, Linux operating system, Unix operating system, Android operating system, iOS operating system, or windows operating system.
  • the application layer may include applications such as browsers, address books, word processing software, and instant messaging software.
  • the embodiment of the present application does not specifically limit the specific structure of the execution subject of the method provided in the embodiment of the present application, as long as the program that records the code of the method provided in the embodiment of the present application can be executed according to the method provided in the embodiment of the present application Just communicate.
  • the execution subject of the method provided by the embodiment of the present application may be a network device, or a functional module in the network device that can call a program and execute the program.
  • Computer-readable media may include, but are not limited to: magnetic storage devices (for example, hard disks, floppy disks, or tapes, etc.), optical disks (for example, compact discs (compact disc, CD), digital versatile discs (digital versatile disc, DVD), etc. ), smart cards and flash memory devices (for example, erasable programmable read-only memory (EPROM), card, stick or key drive, etc.).
  • magnetic storage devices for example, hard disks, floppy disks, or tapes, etc.
  • optical disks for example, compact discs (compact disc, CD), digital versatile discs (digital versatile disc, DVD), etc.
  • smart cards and flash memory devices for example, erasable programmable read-only memory (EPROM), card, stick or key drive, etc.
  • Various storage media described herein can represent one or more devices and/or other machine-readable media for storing information.
  • the term "machine-readable medium” may include, but is not limited to, wireless channels and various other media capable of storing, containing and/or carrying instructions and/or data.
  • processors mentioned in the embodiment of the present application may be a central processing unit (central processing unit, CPU), and may also be other general purpose processors, digital signal processors (digital signal processor, DSP), application specific integrated circuits ( application specific integrated circuit (ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • a general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.
  • the memory mentioned in the embodiments of the present application may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories.
  • the non-volatile memory can be read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically programmable Erases programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be random access memory (RAM).
  • RAM can be used as an external cache.
  • RAM may include the following forms: static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM) , double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (synchlink DRAM, SLDRAM) and Direct memory bus random access memory (direct rambus RAM, DR RAM).
  • static random access memory static random access memory
  • dynamic RAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM synchronous DRAM
  • double data rate SDRAM double data rate SDRAM
  • DDR SDRAM double data rate SDRAM
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous connection dynamic random access memory
  • Direct memory bus random access memory direct rambus RAM, DR RAM
  • the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components
  • the memory storage module may be integrated in the processor.
  • memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.
  • the disclosed devices and methods may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to implement the solutions provided in this application.
  • each functional unit in each embodiment of the present application may be integrated into one unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices.
  • the computer may be a personal computer, a server, or a network device.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server, or data center by wired (eg, coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrated with one or more available media.
  • the available medium may be a magnetic medium, (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, DVD), or a semiconductor medium (for example, a solid state disk (SSD)).
  • a magnetic medium for example, a floppy disk, a hard disk, a magnetic tape
  • an optical medium for example, DVD
  • a semiconductor medium for example, a solid state disk (SSD)
  • the aforementioned available The medium may include but not limited to: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disk and other media that can store program codes .

Abstract

本申请提供了一种配置策略的方法和装置，该方法可以包括：策略控制网元接收业务流路由控制信息以及与该业务流路由控制信息对应的第一服务类型信息，其中，该第一服务类型信息包括第一服务类别信息和/或第一签约者类别信息；该策略控制网元根据该业务流路由控制信息为该第一服务类型信息对应的用户设备生成策略与计费控制规则；该策略控制网元发送该策略与计费控制规则。通过上述方案，可以同时为多个用户配置策略。

Description

配置策略的方法和装置
本申请要求于2022年1月14日提交中国专利局、申请号为202210044585.1、发明名称为“配置策略的方法和装置”的中国专利申请的优先权，以及于2022年03月11日提交中国专利局、申请号为202210239496.2、申请名称为“配置策略的方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种配置策略的方法和装置。
背景技术
在边缘计算或是其他一些场景中，应用功能(application function，AF)可以利用组(group)机制同时为多个用户设备(user equipment，UE)提供业务流路由控制策略。例如，AF可以预先定义一个group及其所包含的多个成员，然后在业务流路由控制策略中使用组标识(group ID)来指代group成员，通过这种方式可以同时为该多个成员配置业务流路由控制策略，策略控制网元(policy control function，PCF)可以根据AF提供的业务流路由控制策略生成策略与计费控制规则，以用于对业务流的路由进行控制。
然而根据现有协议，基于group的方式为多个用户设备提供业务流控制策略的方式存在问题，例如使用group方式只能在group粒度为多个用户设备提供业务流控制策略，而不能在更细粒度为多个用户设备提供业务流控制策略；再如同一个group的成员应属于相同的公用陆地移动通信网(public land mobile network，PLMN)，在移动网络漫游的场景下，漫游用户和非漫游用户属于不同的PLMN时，AF便无法通过group机制同时为漫游用户和非漫游用户提供业务流路由控制策略。
发明内容
本申请提供了一种配置策略的方法和装置，可以同时为多个用户配置策略。
第一方面，提供了一种配置策略的方法，该方法包括：策略控制网元接收业务流路由控制信息以及与该业务流路由控制信息对应的第一服务类型信息，该第一服务类型信息包括第一服务类别信息和/或第一签约者类别信息；该策略控制网元根据该业务流路由控制信息为该第一服务类型信息对应的用户设备生成策略与计费控制规则；该策略控制网元发送该策略与计费控制规则。
基于上述方案，策略控制网元可以根据业务流路由控制信息为第一服务类型信息对应的用户设备生成策略与计费控制规则。因此，上述方案可以同时为第一服务类型信息对应的一个或多个用户配置策略，例如可以为属于不同PLMN下的用户配置策略，而且同一个group内的用户可以对应不同的第一服务类型信息，所以，基于第一服务类型信息可以在比group更小粒度上为一个或者多个用户配置策略，从而可以提高策略配置的效率，节约资源。
应理解，业务流路由控制信息与第一服务类型信息对应，指的是该业务流路由控制信息用于为该第一服务类型信息对应的用户设备生成策略与计费控制规则。
结合第一方面，在第一方面的某些实现方式中，该第一服务类型信息对应的用户设备，包括漫游用户设备和非漫游用户设备。
基于上述方案，可以同时为漫游用户和非漫游用户配置策略，从而可以提高策略配置的效率，节约资源。
结合第一方面，在第一方面的某些实现方式中，该策略控制网元根据该业务流路由控制信息为该第一服务类型信息对应的用户设备生成策略与计费控制规则，包括：该策略控制网元根据用户设备的签约信息确定该用户设备为该第一服务类型信息对应的用户设备；该策略控制网元根据该业务流路由控制信息为该用户设备生成该策略与计费控制规则。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：策略控制网元获取该用户设备的签约信息。
结合第一方面，在第一方面的某些实现方式中，该策略控制网元获取该用户设备的签约信息，包括：该策略控制网元接收来自统一数据存储网元或会话管理网元的该用户设备的签约信息。
应理解，用户设备的签约信息可以是用户设备与运营商之间的签约信息，也可以是用户设备与应用服务商之间的签约信息。其中，用户设备与应用服务商之间的签约信息也可以称为“应用数据”。用户设备的签约信息还可以理解为与用户设备相关的信息，也可以使用其他名称，例如用户设备信息，用户设备关联信息等，此处不做限制。在本申请中，用户设备的签约信息也可称为用户设备签约信息、用户设备签约等。
基于上述方案，策略控制网元可以根据用户设备的签约信息确定该用户设备是否是第一服务类型信息对应的用户设备，在确定该用户设备为该第一服务类型信息对应的用户设备的情况下，策略控制网元为该用户设备生成策略与计费控制规则，或者更加具体地，策略控制网元为该用户设备的协议数据单元会话(PDU会话)生成策略与计费控制规则，也即所述策略控制网元根据所述业务流路由控制信息为所述第一服务类型信息对应的用户设备生成策略与计费控制规则是指所述策略控制网元根据所述业务流路由控制信息为所述第一服务类型信息对应的用户设备的协议数据单元会话(PDU会话)生成策略与计费控制规则，从而实现为第一服务类型信息对应的一个或多个用户设备配置策略的目的，从而可以提高策略配置的效率，节约资源。
结合第一方面，在第一方面的某些实现方式中，该策略控制网元根据该用户设备的签约信息确定该用户设备为该第一服务类型信息对应的用户设备，包括：在该第一服务类型信息和第二服务类型信息匹配的情况下，该策略控制网元确定该用户设备为该第一服务类型信息对应的用户设备，该第二服务类型信息包括在该用户设备的签约信息中，该第二服务类型信息包括第二服务类型信息和/或第二签约者类别信息。
基于上述方案，策略控制网元可以根据第一服务类型信息，以及用户设备的签约信息中的第二服务类型信息，判断一个用户设备是否是第一服务类型信息对应的用户设备。
结合第一方面，在第一方面的某些实现方式中，在该第一服务类型信息和第二服务类型信息匹配的情况下，该策略控制网元确定该用户设备为该第一服务类型信息对应的用户设备，包括：在该第二服务类型信息包括该第一服务类型信息的情况下，该策略控制网元 确定该用户设备为该第一服务类型信息对应的用户设备；或者，在该第一服务类型信息包括多个服务类型信息的情况下，当第二服务类型信息包括该多个服务类型信息中的所有服务类型信息时，该策略控制网元确定该用户设备为该第一服务类型信息对应的用户设备，或者，当该第二服务类型信息包括该第一服务类型信息中的多个服务类型信息中的至少一个时，该策略控制网元确定该用户设备为该第一服务类型信息对应的用户设备，该多个服务类型信息中的每个服务类型信息均包括第一服务类别信息和/或第一签约者类别信息。其中，第一服务类型信息可以仅包括一个服务类型信息，也可以包括多个服务类型信息。在第一服务类型信息包括多个服务类型信息的情况下，在一种实现方式中，当第二服务类型信息包括第一服务类型信息中的多个服务类型信息中的所有服务类型信息时，策略控制网元确定该用户设备为该第一服务类型信息对应的用户设备；在另一种实现方式中，当第二服务类型信息包括该第一服务类型信息中的多个服务类型信息中的至少一个的情况下，该策略控制网元确定该用户设备为该第一服务类型信息对应的用户设备。
应理解，上述多个服务类型信息中的每个服务类型信息所包括的第一服务类别信息和/或第一签约者类别信息可能相同也可能不同，本申请不作限定。
基于上述方案，可以通过各种不同的方式确定第二服务类型信息是否与第一服务类型信息匹配，从而确定一个用户设备是否是第一服务类型信息对应的用户设备。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：该策略控制网元接收与该第一服务类型信息对应的第一应用标识信息和/或第一应用服务商标识信息。结合第一方面，在第一方面的某些实现方式中，该策略控制网元确定该用户设备为该第一服务类型信息对应的用户设备，包括：在第一应用标识信息和/或第一应用服务商标识信息，与第二应用标识信息和/或第二应用服务商标识信息匹配的情况下，该策略控制网元确定该用户设备为该第一服务类型信息对应的用户设备，该第二应用标识信息和/或第二应用服务商标识信息包括在该用户设备的签约信息中。
基于上述方案，策略控制网元还可以利用第一应用标识信息和/或第一应用服务商标识信息，确定一个用户设备为第一服务类型信息对应的用户设备。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：在该第一应用标识信息和/或第一应用服务商标识信息与该第二应用标识信息和/或第二应用服务商标识信息相同的情况下，该策略控制网元确定该第一应用标识信息和/或第一应用服务商标识信息与该第二应用标识信息或第二应用服务商标识信息匹配。
基于上述方案，策略控制网元可以根据第一应用标识信息和/或第一应用服务商标识信息，以及第二应用标识信息和/或第二应用服务商标识信息，判断一个用户设备为第一服务类型信息对应的用户设备。
结合第一方面，在第一方面的某些实现方式中，该策略控制网元接收业务流路由控制信息以及与该业务流路由控制信息对应的第一服务类型信息，包括：该策略控制网元接收来自网络开放功能网元网元的该业务流路由控制信息以及与该业务流路由控制信息对应的该第一服务类型信息。所述网络开放功能网元从应用功能网元接收所述业务流路由控制信息以及与该业务流路由控制信息对应的该第一服务类型信息，并将所述业务流路由控制信息以及与该业务流路由控制信息对应的该第一服务类型信息发送给该策略控制网元，或者网络开放功能网元对业务流路由控制信息中的部分信息进行转换之后，将所述业务流路 由控制信息以及与该业务流路由控制信息对应的该第一服务类型信息发送给该策略控制网元。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：该策略控制网元接收来自统一数据存储网元或者会话管理网元的该用户设备的签约信息。
结合第一方面，在第一方面的某些实现方式中，该策略控制网元根据该业务流路由控制信息为该第一服务类型信息对应的用户设备生成策略与计费控制规则，包括：该策略控制网元根据该业务流路由控制信息为该第一服务类型信息对应的用户设备的协议数据单元会话生成策略与计费控制规则。
第二方面，提供了一种配置策略的方法，该方法包括：策略控制网元接收业务流路由控制信息以及与该业务流路由控制信息对应的签约用户的标识信息；该策略控制网元根据该业务流路由控制信息为该签约用户生成策略与计费控制规则；该策略控制网元发送该策略与计费控制规则。
基于上述方案，策略控制网元可以根据业务流路由控制信息为签约用户生成策略与计费控制规则。因此，上述方案可以同时为一个或多个签约配置策略，例如可以为属于不同PLMN下的签约用户配置策略，从而可以提高策略配置的效率，节约资源。
该业务流路由控制信息与该签约用户的标识信息对应，指的是，该业务流路由控制信息与该签约用户的标识信息存在关联关系，或者，该业务流路由控制信息用于为该签约用户的标识信息对应的用户设备生成策略与计费控制规则，或者，该业务流路由控制信息与该签约用户的标识信息中的签约用户所在的用户设备组对应。
结合第二方面，在第二方面的某些实现方式中，该签约用户包括漫游用户和非漫游用户。
基于上述方案，可以同时为漫游用户和非漫游用户配置策略，从而可以提高策略配置的效率，节约资源。结合第二方面，在第二方面的某些实现方式中，该策略控制网元根据该业务流路由控制信息为该签约用户生成策略与计费控制规则，包括：该策略控制网元确定该用户设备属于该签约用户；该策略控制网元根据该业务流路由控制信息为该用户设备生成策略与计费控制规则。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：策略控制网元获取该用户设备的签约信息，该用户设备的签约信息包括该用户设备的标识。
结合第二方面，在第二方面的某些实现方式中，该策略控制网元获取该用户设备的签约信息，包括：该策略控制网元接收来自统一数据存储网元或会话管理网元的该用户设备的签约信息。
基于上述方案，策略控制网元可以确定一个用户设备是否是签约用户，例如，通过用户设备的签约信息确定一个用户设备是否是签约用户。当一个用户设备是签约用户，则策略控制网元可以为该用户设备生成策略与计费控制规则，从而可以提高策略配置的效率，节约资源。
结合第二方面，在第二方面的某些实现方式中，该策略控制网元确定该用户设备属于该签约用户，包括：在该用户设备的标识包括在该签约用户的标识中的情况下，该策略控制网元确定该用户设备属于该签约用户。
基于上述方案，当策略控制网元确定该用户设备的标识包括在签约用户的标识中时， 策略控制网元可以根据该签约用户的标识对应的策略信息为该用户设备生成策略与计费控制规则，从而实现为多个用户配置访问控制策略的目的。
结合第二方面，在第二方面的某些实现方式中，该策略控制网元接收业务流路由控制信息以及与该业务流路由控制信息对应的签约用户的标识，包括：该策略控制网元接收来自应用功能网元的该业务流路由控制信息以及与该业务流路由控制信息对应的签约用户的标识。
第三方面，提供了一种配置策略的方法，该方法包括：应用功能网元发送业务流路由控制信息以及与该业务流路由控制信息对应的第一服务类型信息，该第一服务类型信息包括第一服务类别信息和/或第一签约者类别信息。
基于上述方案，应用功能网元发送业务流路由控制信息和与该业务流路由控制信息对应的第一服务类型(例如通过网络开放功能网元发送给统一数据存储网元)，以便可以利用业务流路由控制信息为第一服务类型信息对应的一个或多个用户配置策略，从而可以同时为第一服务类型信息对应的一个或多个用户配置策略，例如可以为属于不同PLMN下的用户配置策略，从而可以提高策略配置的效率，节约资源。
结合第三方面，在第三方面的某些实现方式中，该方法包括：应用功能网元生成策略，该策略与该业务流路由控制信息以及该第一服务类型信息对应。
结合第三方面，在第三方面的某些实现方式中，该方法还包括：该应用功能网元发送签约用户的标识信息和该第一服务类型信息，该签约用户的标识信息与该第一服务类型信息相关联。
在一种实现方式中，应用功能网元通过网络开放功能网元向统一数据存储网元发送该签约用户的标识信息和该第一服务类型信息。
结合第三方面，在第三方面的某些实现方式中，应用功能网元可以发送签约用户的标识信息和该第一服务类型信息，以便为与该第一服务类型信息对应的签约用户配置策略。
结合第三方面，在第三方面的某些实现方式中，该第一服务类型信息包括多个服务类型信息。
结合第三方面，在第三方面的某些实现方式中，该方法还包括：该应用功能网元发送与该第一服务类型信息对应的第一应用标识信息和/或第一应用服务商标识信息。
第四方面，提供了一种配置策略的方法，该方法包括：统一数据存储网元接收业务流路由控制信息以及与该业务流路由控制信息对应的用户设备组的标识信息；该统一数据存储网元根据该用户设备组的标识信息确定与该用户设备组的标识信息对应的签约用户的标识信息；该统一数据存储网元向策略控制网元发送该业务流路由控制信息和该签约用户的标识信息，该业务流路由控制与该签约用户的标识信息相关联。
基于上述方案，统一数据存储网元可以根据用户设备组的标识信息确定与该用户设备组的标识信息对应的签约用户的标识信息，并将该签约用户的标识信息，以及其接收到的业务流路由控制信息发送给策略控制网元，以便策略控制网元可以根据这些信息为签约用户配置策略。
结合第四方面，在第四方面的某些实现方式中，该统一数据存储网元接收来自应用功能网元的业务流路由控制信息以及与该业务流路由控制信息对应的用户设备组的标识信息之前，该方法还包括：该统一数据存储网元接收来自该应用功能网元的该用户设备组的 标识信息和该签约用户的标识信息，该用户设备组的标识和该签约用户的标识信息相关联。
第五方面，提供了一种配置策略的方法，该方法包括：统一数据存储网元接收业务流路由控制信息以及与该业务流路由控制信息对应的第一服务类型信息，该第一服务类型信息包括第一服务类别信息和/或第一签约者类型信息；该数据管理网元根据该第一服务类型信息确定与该第一服务类型信息对应的签约用户的标识信息；该统一数据存储网元向策略控制网元发送该业务流路由控制信息和该签约用户的标识信息。
在一种实现方式中，该统一数据存储网元可以是统一数据存储功能网元。例如在5G系统中，该统一数据存储网元可以是UDR。
基于上述方案，统一数据存储网元可以根据第一服务类型信息确定与该用户设备组的标识信息对应的签约用户的标识信息，并将该签约用户的标识信息，以及其接收到的业务流路由控制信息发送给策略控制网元，以便策略控制网元可以根据这些信息为签约用户配置策略。结合第五方面，在第五方面的某些实现方式中，在该统一数据存储网元接收来自应用功能网元的业务流路由控制信息以及与该业务流路由控制信息对应的和第一服务类型信息之前，该方法还包括：该统一数据存储网元接收来自该应用功能网元的该签约用户的标识信息和该第一服务类型信息，该签约用户的标识信息与该第一服务类型信息相关联。
第六方面，提供了一种配置策略的方法，该方法包括：应用功能网元向统一数据存储网元发送业务流路由控制信息以及与该业务流路由控制信息对应的用户设备组的标识信息，该用户设备组包括签约用户。
基于上述方案，应用功能网元发送业务流路由控制信息和与该业务流路由控制信息对应的用户设备组的标识信息(例如通过网络开放功能网元发送给统一数据存储网元)，以便可以利用业务流路由控制信息为用户设备组中的一个或多个签约用户配置策略，从而可以同时为用户设备组中的一个或多个签约用户配置策略，例如可以为属于不同PLMN下的用户配置策略，从而可以提高策略配置的效率，节约资源。
结合第六方面，在第六方面的某些实现方式中，在该应用功能网元向统一数据存储网元发送该业务流路由控制信息以及与该业务流路由控制信息对应的用户设备组的标识信息之前，该方法还包括：该应用功能网元向统一数据存储网元发送该用户设备组的标识和该签约用户的标识信息，该用户的标识信息和该用户设备组的标识相关联。
第七方面，提供了一种配置策略的方法，该方法包括：会话管理网元从统一数据管理网元接收用户设备的签约信息，该签约信息包括服务类型信息，该服务类型信息包括包括服务类别信息和/或签约者类别信息；该会话管理网元向策略控制网元发送该签约信息。
基于上述方案，会话管理网元可以向策略控制网元发送从统一数据管理网元接收到的用户设备的签约信息，以便策略控制网元可以为该用户设备配置策略。
结合第七方面，在第七方面的某些实现方式中，在该会话管理网元从统一数据存储网元接收用户设备的签约信息之前，该方法还包括：该会话管理网元向该统一数据存储网元发送签约信息请求消息，该签约信息请求消息包括该用户设备的标识，该签约信息请求消息用于请求该用户设备的签约信息。
第八方面，提供了一种配置策略的方法，该方法包括：统一数据管理网元接收签约信息和签约用户的标识信息，该签约信息包括服务类型信息，该服务类型信息包括服务类别信息和/或签约者类别信息，该签约信息和该签约用户的标识信息相关联；该统一数据管 理网元保存该签约信息和该签约用户的标识信息。
基于上述方案，统一数据管理网元可以预先保存接收到的签约信息，以及与该签约信息对应的签约用户的标识信息，以便可以根据这些信息为一个或多个签约用户配置策略。
结合第八方面，在第八方面的某些实现方式中，该方法还包括：该统一数据管理网元接收来自会话管理网元的签约信息请求消息，该签约信息请求消息包括用户设备的标识信息，该签约信息请求消息用于请求该用户设备的签约信息；在该用户设备的标识信息包括在该签约用户的标识信息的情况下，该统一数据管理网元向该会话管理网元发送该签约信息。
结合第八方面，在第八方面的某些实现方式中，该签约信息还包括第二应用标识信息和/或第二应用服务商标识信息。
第九方面，提供了一种配置策略的方法，该方法包括：策略控制网元接收业务流路由控制信息以及与该业务流路由控制信息对应的组信息，该组信息包括多个组标识；该策略控制网元根据该业务流路由控制信息为与该组信息匹配的用户设备生成策略与计费控制规则；该策略控制网元发送该策略与计费控制规则。
基于上述方案，策略控制网元可以根据业务流路由控制信息为与组信息匹配的用户设备生成策略与计费控制规则，从而可以同时为为一个或多个签约用户配置策略，例如可以为属于不同PLMN的用户设备(例如漫游的用户设备和非漫游的用户设备)配置策略，从而可以提高配置策略的效率，节约资源。
具体来说，策略控制网元可以接收业务流路由控制信息，以及与该业务流路由控制信息对应的组信息，例如，策略控制网元可以从统一数据存储网元接收该业务流路由控制信息和该组信息，或者策略控制网元可以从网络开放功能网元接收该业务流路由控制信息和该组信息，或者策略控制网元可以从应用功能网元接收该业务流路由控制信息和该组信息。当策略控制网元确定某个用户设备与该组信息匹配时，策略控制网元可以使用该业务流路由控制信息为该用户设备生成策略控制与计费规则。
结合第九方面，在第九方面的某些实现方式中，策略控制网元接收业务流路由控制信息以及与该业务流路由控制信息对应的组信息，包括：策略控制网元接收来自统一数据存储网元的该业务流路由控制信息以及与该业务流路由控制信息对应的组信息。
需要说明的是，这里的组信息，可以是应用功能网元提供的信息，也可以是网络开放功能网元对应用功能网元提供的信息进行转换得到的信息。下面结合示例分别进行说明。
在一种实现方式中，应用功能网元生成业务流路由控制信息之后，向网络开放功能网元发送该业务流路由控制信息和组信息(记为第一组信息)，其中该第一组信息包括多个内部组标识。网络开放功能网元接收来自应用功能网元的业务流路由控制信息和第一组信息之后，向统一数据存储网元发送业务流路由控制信息和组信息(记为第二组信息)，在这种情况下，第一组信息和第二组信息相同。统一数据存储网元接收到业务流路由控制信息和第二组信息之后，向策略控制网元发送该业务流路由控制信息和第二组信息。
在另一种实现方式中，应用功能网元生成业务流路由控制信息之后，向网络开放功能网元发送该业务流路由控制信息和组信息(记为第一组信息)，其中该第一组信息包括多个外部组标识。网络开放功能网元接收来自应用功能网元的业务流路由控制信息和第一组信息之后，将第一组信息中的多个外部组标识转换为内部组标识得到新的组信息(记为第 二组信息)，然后网络开放功能网元向统一数据存储网元发送业务流路由控制信息和组信息(记为第二组信息)，在这种情况下，第一组信息和第二组信息相同。统一数据存储网元接收到业务流路由控制信息和第二组信息之后，向策略控制网元发送该业务流路由控制信息和第二组信息。
结合上述示例，策略控制网元接收到的与业务流路由控制信息对应的组信息可对应于上述示例中的第二组信息。更详细的示例可参见后续具体实施方式部分的方法900中的S902-S904部分的描述，这里不再详细说明。
结合第九方面，在第九方面的某些实现方式中，该策略控制网元根据该业务流路由控制信息为与该组信息匹配的用户设备生成策略与计费控制规则，包括：该策略控制网元根据用户设备的签约信息确定该用户设备与该组信息匹配；该策略控制网元根据该业务流路由控制信息为该用户设备生成该策略与计费控制规则。
基于上述方案，策略控制网元获取用户设备的签约信息之后，可以根据该签约信息判断用户设备是否与组信息匹配，如果匹配的话，策略控制网元可以根据与该组信息对应的业务流路由控制信息为用户设备生成策略控制与计费规则，从而可以同时为多个签约用户配置策略，从而提升效率，节约资源。
结合第九方面，在第九方面的某些实现方式中，该策略控制网元根据用户设备的签约信息确定该用户设备与该组信息匹配，包括：在该用户设备的签约信息包括该组信息中的多个组标识的情况下，该策略控制网元确定该用户设备与该组信息匹配。
基于上述方案，策略控制网元可以为签约信息包括组信息的多个组标识的用户设备生成策略与计费控制规则，也就是说，策略控制网元可以为一个或多个不同的用户设备生成策略与计费控制规则，从而可以提升效率。
结合第九方面，在第九方面的某些实现方式中，该组信息中的多个组标识存在逻辑关系；该策略控制网元根据用户设备的签约信息确定该用户设备与该组信息匹配，包括：在该用户设备的签约信息满足该多个组标识的逻辑关系的情况下，该策略控制网元确定该用户设备与该组信息匹配。
基于上述方案，策略控制网元可以为签约信息满足组信息中的多个组标识的逻辑关系的用户设备生成策略与计费控制规则，也就是说，策略控制网元可以为一个或多个不同的用户设备生成策略与计费控制规则，从而可以提升效率。
第十方面，提供了一种配置策略的方法，该方法包括：应用功能网元发送业务流路由控制信息以及与该业务流路由控制信息对应的组信息，该组信息包括多个组标识。
结合第十方面，在第十方面的某些实现方式中，该组信息中的多个组标识存在逻辑关系。
结合第十方面，在第十方面的某些实现方式中，该方法还包括：该策略控制网元接收来自统一数据存储网元或者会话管理网元的该用户设备的签约信息。
第十一方面，提供了一种通信装置，该装置包括：收发模块，用于接收业务流路由控制信息以及与该业务流路由控制信息对应的第一服务类型信息，该第一服务类型信息包括第一服务类别信息和/或第一签约者类别信息；处理模块，用于根据该业务流路由控制信息为该第一服务类型信息对应的用户设备生成策略与计费控制规则；该策略控制网元发送该策略与计费控制规则。
结合第十一方面，在第十一方面的某些实现方式中该处理模块，具体可用于根据用户设备的签约信息确定该用户设备为该第一服务类型信息对应的用户设备；以及，根据该业务流路由控制信息为该用户设备生成该策略与计费控制规则。
结合第十一方面，在第十一方面的某些实现方式中，在该第一服务类型信息和第二服务类型信息匹配的情况下，该处理模块，具体可用于确定该用户设备为该第一服务类型信息对应的用户设备，该第二服务类型信息包括在该用户设备的签约信息中，该第二服务类型信息包括第二服务类型信息和/或第二签约者类别信息。
结合第十一方面，在第十一方面的某些实现方式中，在该第二服务类型信息包括该第一服务类型信息的情况下，该处理模块，具体可用于确定该用户设备为该第一服务类型信息对应的用户设备；或者，在该第二服务类型信息包括该第一服务类型信息中的多个服务类型信息中的至少一个的情况下，该处理模块，具体可用于确定该用户设备为该第一服务类型信息对应的用户设备。
结合第十一方面，在第十一方面的某些实现方式中，该收发模块，还用于接收与该第一服务类型信息对应的第一应用标识信息和/或第一应用服务商标识信息。
结合第十一方面，在第十一方面的某些实现方式中，该处理模块，具体可用于在第一应用标识信息和/或第一应用服务商标识信息，与第二应用标识信息和/或第二应用服务商标识信息匹配的情况下，确定该用户设备为该第一服务类型信息对应的用户设备，该第二应用标识信息和/或第二应用服务商标识信息包括在该用户设备的签约信息中。
结合第十一方面，在第十一方面的某些实现方式中，该处理模块，还用于在该第一应用标识信息和/或第一应用服务商标识信息与该第二应用标识信息或第二应用服务商标识信息相同的情况下，该策略控制网元确定该第一应用标识信息和/或第一应用服务商标识信息与该第二应用标识信息或第二应用服务商标识信息匹配。
结合第十一方面，在第十一方面的某些实现方式中，该收发模块，具体可用于接收来自网络开放功能网元的该业务流路由控制信息以及与该业务流路由控制信息对应的第一服务类型信息。
结合第十一方面，在第十一方面的某些实现方式中，该处理模块，具体可用于根据该业务流路由控制信息为该第一服务类型信息对应的用户设备的会话生成策略与计费控制规则。
第十二方面，提供了一种通信装置，该装置包括：收发模块，用于接收业务流路由控制信息以及与该业务流路由控制信息对应的签约用户的标识信息；处理模块，用于根据该业务流路由控制信息为该签约用户生成策略与计费控制规则；收发模块，还用于发送该策略与计费控制规则。
结合第十二方面，在第十二方面的某些实现方式中，该处理模块，具体可用于确定该用户设备属于该签约用户；以及，根据该业务流路由控制信息为该用户设备生成策略与计费控制规则。
结合第十二方面，在第十二方面的某些实现方式中，该处理模块，具体可用于在该用户设备的标识包括在该签约用户的标识中的情况下，确定该用户设备属于该签约用户。
结合第十二方面，在第十二方面的某些实现方式中，该收发模块，具体可用于接收来自应用功能网元的该业务流路由控制信息以及与该业务流路由控制信息对应的签约用户 的标识。
第十三方面，提供了一种配置策略的装置，该装置包括：收发模块，用于发送业务流路由控制信息以及与该业务流路由控制信息对应的第一服务类型信息，该第一服务类型信息包括第一服务类别信息和/或第一签约者类别信息。
结合第十三方面，在第十三方面的某些实现方式中，该收发模块，还用于发送签约用户的标识信息和该第一服务类型信息，该签约用户的标识信息与该第一服务类型信息相关联。
结合第十三方面，在第十三方面的某些实现方式中，该第一服务类型信息包括多个服务类型信息。
结合第十三方面，在第十三方面的某些实现方式中，该收发模块，还用于发送与该第一服务类型信息对应的第一应用标识信息和/或第一应用服务商标识信息。
第十四方面，提供了一种配置策略的装置，该装置包括：收发模块，用于接收业务流路由控制信息以及与该业务流路由控制信息对应的用户设备组的标识信息；处理模块，用于根据该用户设备组的标识信息确定与该用户设备组的标识信息对应的签约用户的标识信息；该收发模块，还用于向策略控制网元发送该业务流路由控制信息和该签约用户的标识信息，该业务流路由控制与该签约用户的标识信息相关联。
结合第十四方面，在第十四方面的某些实现方式中，该收发模块，还用于接收来自该应用功能网元的该用户设备组的标识信息和该签约用户的标识信息，该用户设备组的标识和该签约用户的标识信息相关联。
第十五方面，提供了一种配置策略的装置，该装置包括：收发模块，用于接收业务流路由控制信息以及与该业务流路由控制信息对应的第一服务类型信息，该第一服务类型信息包括第一服务类别信息和/或第一签约者类型信息；处理模块，用于根据该第一服务类型信息确定与该第一服务类型信息对应的签约用户的标识信息；该收发模块，还用于向策略控制网元发送该业务流路由控制信息和该签约用户的标识信息。
结合第十五方面，在第十五方面的某些实现方式中，该收发模块，还用于接收来自该应用功能网元的该签约用户的标识信息和该第一服务类型信息，该签约用户的标识信息与该第一服务类型信息相关联。
第十六方面，提供了一种配置策略的装置，该装置包括：收发模块，用于向统一数据存储网元发送业务流路由控制信息以及与该业务流路由控制信息对应的用户设备组的标识信息，该用户设备组包括签约用户。
结合第十六方面，在第十六方面的某些实现方式中，该收发模块，还用于向该统一数据存储网元发送该用户设备组的标识和该签约用户的标识信息，该签约用户的标识信息和该用户设备组的标识相关联。
应理解，该签约用户的标识信息和该用户设备组的标识相关联，可以指的是该签约用户的标识信息所对应的签约用户，属于该用户设备组的标识所对应的用户设备组。
第十七方面，提供了一种配置策略的装置，该装置包括：收发模块，用于从统一数据存储网元或会话管理网元接收用户设备的签约信息，该签约信息包括第二服务类型信息；以及，向策略控制网元发送该签约信息。
结合第十七方面，在第十七方面的某些实现方式中，收发模块，用于向该统一数据管 理网元发送签约信息请求消息，该签约信息请求消息包括该用户设备的标识，该签约信息请求消息用于请求该用户设备的签约信息。
第十八方面，提供了一种配置策略的装置，该装置包括：收发模块，用于接收签约信息和签约用户的标识，该签约信息包括服务类型信息，该服务类型信息包括服务类别信息和/或签约者类别信息，该签约信息和该签约用户的标识信息相关联；处理模块，用于保存该签约信息和该第一或多个签约用户的标识信息。
结合第十八方面，在第十八方面的某些实现方式中，该收发模块，还用于接收来自会话管理网元的签约信息请求消息，该签约信息请求消息包括用户设备的标识信息，该签约信息请求消息用于请求该用户设备的签约信息；在该用户设备的标识信息包括在该签约用户的标识信息的情况下，该收发模块，还用于向该会话管理网元发送该签约信息。
结合第十八方面，在第十八方面的某些实现方式中，该签约信息还包括第二应用标识信息和/或第二应用服务商标识信息。
第十九方面，提供了一种通信装置，该装置包括：收发模块，用于接收业务流路由控制信息以及与该业务流路由控制信息对应的组信息，该组信息包括多个群组标识；处理模块，用于根据该业务流路由控制信息为与该组信息匹配的用户设备生成策略与计费控制规则；该收发模块，还用于发送该策略与计费控制规则。
结合第十九方面，在第十九方面的某些实现方式中，该处理模块，具体用于根据用户设备的签约信息确定该用户设备与该组信息匹配；根据该业务流路由控制信息为该用户设备生成该策略与计费控制规则。
结合第十九方面，在第十九方面的某些实现方式中，该处理模块，具体用于在该用户设备的签约信息包括该组信息中的多个群组标识的情况下，确定该用户设备与该组信息匹配。
结合第十九方面，在第十九方面的某些实现方式中，该组信息中的多个群组标识存在逻辑关系；该处理模块，具体用于在该用户设备的签约信息满足该多个群组标识的逻辑关系的情况下，确定该用户设备与该组信息匹配。
结合第十九方面，在第十九方面的某些实现方式中，该收发模块还用于：接收来自统一数据存储网元或者会话管理网元的该用户设备的签约信息。
第二十方面，提供了一种通信装置，该装置包括：收发模块，用于发送业务流路由控制信息以及与该业务流路由控制信息对应的组信息，该组信息包括多个群组标识。
结合第二十方面，在第二十方面的某些实现方式中，该组信息中的多个群组标识存在逻辑关系。
第二十一方面，提供一种通信装置，该装置用于执行上述第一方面至第十方面提供的方法。具体地，该装置可以包括用于执行第一方面至第十方面提供的方法的单元和/或模块，如处理模块和/或收发模块(也可以称为通信模块)。
在一种实现方式中，该装置为网络设备，例如该装置为策略控制网元，或者是应用功能网元，或者是统一数据存储网元。当该装置为网络设备时，收发模块可以是收发器，或，输入/输出接口；处理模块可以是处理器。
在另一种实现方式中，该装置为用于网络设备中的芯片、芯片系统或电路。当该装置为用于通信设备中的芯片、芯片系统或电路时，收发模块可以是该芯片、芯片系统或电路 上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等；处理模块可以是处理器、处理电路或逻辑电路等。
第二十二方面，提供一种通信装置，该装置包括：存储器，用于存储程序；处理器，用于执行存储器存储的程序，当存储器存储的程序被执行时，处理器用于执行上述第一方面至第十方面提供的方法。
第二十三方面，本申请提供一种处理器，用于执行上述各方面提供的方法。在执行这些方法的过程中，上述方法中有关发送上述信息和获取/接收上述信息的过程，可以理解为由处理器输出上述信息的过程，以及处理器接收输入的上述信息的过程。在输出上述信息时，处理器将该上述信息输出给收发器，以便由收发器进行发射。该上述信息在由处理器输出之后，还可能需要进行其他的处理，然后才到达收发器。类似的，处理器接收输入的上述信息时，收发器获取/接收该上述信息，并将其输入处理器。更进一步的，在收发器收到该上述信息之后，该上述信息可能需要进行其他的处理，然后才输入处理器。
基于上述原理，举例来说，前述方法中提及的接收请求消息可以理解为处理器接收输入的信息。
对于处理器所涉及的发射、发送和获取/接收等操作，如果没有特殊说明，或者，如果未与其在相关描述中的实际作用或者内在逻辑相抵触，则均可以更加一般性的理解为处理器输出和接收、输入等操作，而不是直接由射频电路和天线所进行的发射、发送和接收操作。
在实现过程中，上述处理器可以是专门用于执行这些方法的处理器，也可以是执行存储器中的计算机指令来执行这些方法的处理器，例如通用处理器。上述存储器可以为非瞬时性(non-transitory)存储器，例如只读存储器(read only memory，ROM)，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
第二十四方面，提供一种计算机可读存储介质，该计算机可读介质存储用于设备执行的程序代码，该程序代码包括用于执行上述第一方面至第十方面提供的方法。
第二十五方面，提供一种包含指令的计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行上述第一方面至第十方面提供的方法。
第二十六方面，提供一种芯片，该芯片包括处理器与通信接口，该处理器通过该通信接口读取存储器上存储的指令，执行上述第一方面至第十方面提供的方法。
可选地，作为一种实现方式，该芯片还可以包括存储器，该存储器中存储有指令，该处理器用于执行该存储器上存储的指令，当该指令被执行时，该处理器用于执行上述第一方面至第十方面提供的方法。
附图说明
图1是一种适用于本申请实施例的一种通信系统架构示意图。
图2是一种配置策略的方法200的示例性流程图。
图3是本申请实施例提供的一种配置策略的方法的示例性流程图。
图4是本申请实施例提供的另一种配置策略的方法的示例性流程图。
图5是本申请实施例提供的另一种配置策略的方法的示例性流程图。
图6是本申请实施例提供的又一种配置策略的方法的示例性流程图。
图7是本申请实施例提供的又一种配置策略的方法的示例性流程图。
图8是本申请实施例提供的又一种配置策略的方法的示例性流程图。
图9是本申请实施例提供的又一种配置策略的方法的示例性流程图。
图10是本申请一个实施例提供的通信装置的示意性框图。
图11是本申请另一个实施例提供的通信装置的示意性框图。
图12是本申请又一个实施例提供的通信装置的示意性框图。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图，对本申请中的技术方案进行描述。方法实施例中的具体操作方法也可以应用于装置实施例或系统实施例中。其中，在本申请的描述中，除非另有说明，“多个”的含义是两个或两个以上。
在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，不同的实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
可以理解的是，在本申请中涉及的各种数字编号仅为描述方便进行的区分，并不用来限制本申请的范围。上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”、“第四”以及其他各种术语标号等(如果存在)是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的实施例能够以除了在这里图示或描述的内容以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
本申请提供的技术方案可以应用于各种通信系统，例如：第五代(5th generation，5G)或新无线(new radio，NR)系统、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)系统等。本申请提供的技术方案还可以应用于未来的通信系统，如第六代移动通信系统。本申请提供的技术方案还可以应用于设备到设备(device to device，D2D)通信，车到万物(vehicle-to-everything，V2X)通信，机器到机器(machine to machine，M2M)通信，机器类型通信(machine type communication，MTC)，以及物联网(internet of things，IoT)通信系统或者其他通信系统。
如图1所示，为基于服务化架构的第五代(5th generation，5G)网络架构示意图。
图1所示的5G网络架构中可包括三部分，分别是终端设备部分、数据网络(data network，DN)和运营商网络部分。下面对其中的部分网元的功能进行简单介绍说明。
其中，运营商网络可包括以下网元中的一个或多个：鉴权服务器功能(authentication server function，AUSF)网元、网络开放功能(network exposure function，NEF)网元、策略控制功能(policy control function，PCF)网元、统一数据管理(unified data management， UDM)网元、统一数据库(unified data repository，UDR)、网络存储功能(network repository function，NRF)网元、应用功能(application function，AF)网元、接入与移动性管理功能(access and mobility management function，AMF)网元、会话管理功能(session management function，SMF)网元、无线接入网(radioaccess network，RAN)以及用户面功能(user plane function，UPF)网元等。上述运营商网络中，除无线接入网部分之外的部分可以称为核心网络部分。
1、终端设备(terminal device)：也可以称为用户设备(user equipment，UE)，是一种具有无线收发功能的设备，可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。所述终端设备可以是手机(mobile phone)、平板电脑(pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端、增强现实(augmented reality，AR)终端、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。这里的终端设备，指的是第三代合作伙伴计划(3rd generation partnership project，3GPP)终端。为便于说明，本申请后续以UE代指终端设备为例进行说明。
上述终端设备可通过运营商网络提供的接口(例如N1等)与运营商网络建立连接，使用运营商网络提供的数据和/或语音等服务。终端设备还可通过运营商网络访问DN，使用DN上部署的运营商业务，和/或第三方提供的业务。其中，上述第三方可为运营商网络和终端设备之外的服务方，可为终端设备提供他数据和/或语音等服务。其中，上述第三方的具体表现形式，具体可根据实际应用场景确定，在此不做限制。
2、无线接入网络(radio access network，RAN)网元：在下文中简称为RAN，对应接入网设备。
RAN是运营商网络的子网络，是运营商网络中业务节点与终端设备之间的实施系统。终端设备要接入运营商网络，首先是经过RAN，进而可通过RAN与运营商网络的业务节点连接。本申请中的RAN设备，是一种为终端设备提供无线通信功能的设备，RAN设备也称为接入网设备。本申请中的RAN设备包括但不限于：5G中的下一代基站(g nodeB，gNB)、演进型节点B(evolved node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved nodeB，或home node B，HNB)、基带单元(baseBand unit，BBU)、传输点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、移动交换中心等。
3、用户面功能(user plane function，UPF)：用于分组路由和转发以及用户面数据的服务质量(quality of service，QoS)处理等。
在5G通信系统中，该用户面网元可以是用户面功能(user plane function，UPF)网元。在未来通信系统中，用户面网元仍可以是UPF网元，或者，还可以有其它的名称，本申请不做限定。
4、接入和移动管理网元
接入和移动管理网元主要用于移动性管理和接入管理等，可以用于实现MME功能中 除会话管理之外的其它功能，例如，接入授权/鉴权等功能。
在5G通信系统中，该接入和移动管理网元可以是接入和移动管理功能(access and mobility management function，AMF)。在未来通信系统中，接入和移动管理设备仍可以是AMF，或者，还可以有其它的名称，本申请不做限定。
5、会话管理功能(session management function，SMF)：主要用于会话管理、用户设备的网络互连协议(internet protocol，IP)地址分配和管理、选择可管理用户平面功能、策略控制和收费功能接口的终结点以及下行数据通知等。
在5G通信系统中，该会话管理网元可以是会话管理功能网元。在未来通信系统中，会话管理网元仍可以是SMF网元，或者，还可以有其它的名称，本申请不做限定。
6、策略控制功能(policy control function，PCF)：用于指导网络行为的统一策略框架，为控制面功能网元(例如AMF，SMF等)提供策略规则信息等。
在4G通信系统中，该策略控制网元可以是策略和计费规则功能(policy and charging rules function，PCRF)网元。在5G通信系统中，该策略控制网元可以是策略控制功能PCF网元。在未来通信系统中，策略控制网元仍可以是PCF网元，或者，还可以有其它的名称，本申请不做限定。
7、应用功能(application function，AF)：用于进行应用影响的数据路由，无线接入网络开放功能网元，与策略框架交互进行策略控制等。
在5G通信系统中，该应用网元可以是应用功能网元。在未来通信系统中，应用网元仍可以是AF网元，或者，还可以有其它的名称，本申请不做限定。
8、统一数据管理(unified data management，UDM)：用于处理UE标识，接入鉴权，注册以及移动性管理等。
在5G通信系统中，该数据管理网元可以是统一数据管理网元；在4G通信系统中，该数据管理网元可以是归属用户服务器(home subscriber server，HSS)网元在未来通信系统中，统一数据管理仍可以是UDM网元，或者，还可以有其它的名称，本申请不做限定。
9、认证服务器(authentication server function，AUSF)：用于鉴权服务、产生密钥实现对用户设备的双向鉴权，支持统一的鉴权框架。
在5G通信系统中，该认证服务器可以是认证服务器功能网元。在未来通信系统中，认证服务器功能网元仍可以是AUSF网元，或者，还可以有其它的名称，本申请不做限定。
10、数据网络(data network，DN)：DN是位于运营商网络之外的网络，运营商网络可以接入多个DN，DN上可部署多种业务，可为终端设备提供数据和/或语音等服务。例如，DN是某智能工厂的私有网络，智能工厂安装在车间的传感器可为终端设备，DN中部署了传感器的控制服务器，控制服务器可为传感器提供服务。传感器可与控制服务器通信，获取控制服务器的指令，根据指令将采集的传感器数据传送给控制服务器等。又例如，DN是某公司的内部办公网络，该公司员工的手机或者电脑可为终端设备，员工的手机或者电脑可以访问公司内部办公网络上的信息、数据资源等。
图1中Nausf、Nnef、Npcf、Nudm、Naf、Namf、Nsmf、N1、N2、N3、N4，以及N6为接口序列号。这些接口序列号的含义可参见3GPP标准协议中定义的含义，在此不做限制。
在图1所示的网络架构中，各网元之间可以通过图中所示的接口通信。如图所示，UE 和AMF之间可以通过N1接口进行交互，交互消息例如可以称为N1消息(N1Message)。RAN和AMF之间可以通过N2接口进行交互，N2接口可以用于非接入层(non-access stratum，NAS)消息的发送等。RAN和UPF之间可以通过N3接口进行交互，N3接口可以用于传输用户面的数据等。SMF和UPF之间可以通过N4接口进行交互，N4接口可以用于传输例如N3连接的隧道标识信息，数据缓存指示信息，以及下行数据通知消息等信息。UPF和DN之间可以通过N6接口进行交互，N6接口可以于传输用户面的数据等。其他接口与各网元之间的关系如图1中所示，为了简洁，这里不一一详述。
应理解，上述应用于本申请实施例的网络架构仅是举例说明的从服务化架构的角度描述的网络架构，适用本申请实施例的网络架构并不局限于此，任何能够实现上述各个网元的功能的网络架构都适用于本申请实施例。
还应理解，图1中所示的AMF、SMF、UPF、网络切片选择功能网元(network slice selection function，NSSF)、NEF、AUSF、NRF、PCF、UDM可以理解为核心网中用于实现不同功能的网元，例如可以按需组合成网络切片。这些核心网网元可以各自独立的设备，也可以集成于同一设备中实现不同的功能，本申请对于上述网元的具体形态不作限定。
还应理解，上述命名仅为便于区分不同的功能而定义，不应对本申请构成任何限定。本申请并不排除在5G网络以及未来其它的网络中采用其他命名的可能。例如，在6G网络中，上述各个网元中的部分或全部可以沿用5G中的术语，也可能采用其他名称等。图1中的各个网元之间的接口名称只是一个示例，具体实现中接口的名称可能为其他的名称，本申请对此不作具体限定。此外，上述各个网元之间的所传输的消息(或信令)的名称也仅仅是一个示例，对消息本身的功能不构成任何限定。
可以理解的是，上述网元或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。为方便说明，本申请后续，以网络设备为接入和移动管理网元AMF，基站为无线接入网络RAN为例进行说明。
应理解，上述应用于本申请实施例的网络架构仅是一种举例说明，适用本申请实施例的网络架构并不局限于此，任何能够实现上述各个网元的功能的网络架构都适用于本申请实施例。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
本申请实施例的各个方面或特征可以实现成方法、装置或使用标准编程和/或工程技术的制品。本申请中使用的术语“制品”涵盖可从任何计算机可读器件、载体或介质访问的计算机程序。例如，计算机可读介质可以包括，但不限于：磁存储器件(例如，硬盘、软盘或磁带等)，光盘(例如，压缩盘(compact disc，CD)、数字通用盘(digital versatile disc，DVD)等)，智能卡和闪存器件(例如，可擦写可编程只读存储器(erasable programmable read-only memory，EPROM)、卡、棒或钥匙驱动器等)。另外，本文描述的各种存储介质可代表用于存储信息的一个或多个设备和/或其它机器可读介质。术语“机器可读介质”可包括但不限于，无线信道和能够存储、包含和/或承载指令和/或数据的各种其它介质。
为便于理解本申请实施例，首先对本申请中涉及到的术语或技术做简单说明。
1、5G架构。
第三代合作伙伴计划(3rd generation partnership project，3GPP)中定义的演进分组系统(evolved packet system，EPS)包括基于服务化接口的5G网络架构中或基于点对点接口的5G网络架构中，5G网络可分为三部分，分别是UE、DN和运营商网络。
其中，运营商网络可以包括图1中除UE和DN之外所示的网元中的一个或者多个，或者还可以包括其他的网元，本申请对于5G网络结构不做限定，可以参考目前相关技术中的介绍。
2、边缘计算
移动通信的飞速发展促进了各种新型业务的不断涌现，除了传统的移动宽带、物联网之外，移动通信催生了许多新的应用领域如增强现实(augmented reality，AR)技术、虚拟现实(virtual reality，VR)技术、车联网技术、工业控制、IOT等，同时对网络带宽、时延等性能也提出了更高的需求，网络负荷进一步加重。
LTE中传统的集中式锚点部署方式越来越难以支撑快速增长的移动业务流量模型。一方面，在锚点网关集中式部署的网络中，增长的流量最终集中在网关及核心机房处，对回程网络带宽、机房吞吐量和网关规格提出了越来越高的要求；另一方面，从接入网到锚点网关长距离的回程网络和复杂的传输环境，导致用户报文传输的较大时延和抖动。
基于上述情况，业界提出了边缘计算(edge computing，EC)。边缘计算通过将用户面网元及业务处理能力下移到网络边缘，实现了分布式的业务流量本地处理，避免了流量的过度集中，从而大大降低了对核心机房和集中网关的规格要求。同时边缘计算也缩短了回程网络的距离，降低了用户报文的端到端传输时延和抖动，使得超低时延业务的部署称为可能。
相比于DN网络而言，边缘计算平台部署在下沉的UPF(即本地UPF)处；DN网络部署在远端UPF处。与UE访问DN的路径(如实线所示)相比，UE访问边缘计算平台的路径(如点划线所示)大大缩短。因此，边缘计算技术可以为用户提供低时延、高带宽服务。
3、移动网络漫游
漫游(roaming)是指属于运营商A的移动用户接入到了运营商B的网络的情况，例如中国移动的用户接入到中国联通的网络中就称为该中国移动用户漫游到了中国联通的网络。
用户的归属网络称为用户的家乡网络，也称为归属公用陆地移动通信网(home public land mobile network，HPLMN)；用户漫游到的网络称为用户的拜访网络，也称为访问公用陆地移动通信网(visited public land mobile network，VPLMN)。
在漫游场景中有两种协议数据单元(protocol data unit，PDU)会话(Session)类型：归属地路由PDU会话(home routed PDU Session，HR PDU Session)和本地转出PDU会话(local breakout PDU Session，LBO PDU session)，两者的区别在于PDU Session是否要连接到家乡网络的UPF。
3、组管理
组(group)通常由多个组成员组成，以组为单位对成员进行管理能够带来管理的便 利性。
在5G网络中，通过组标识(group Identifier，group ID)来标识一个组，一个组中可以包含多个组成员(所有成员属于相同PLMN)。
AF在创建组时，提供一个外部组标识(External Group ID)，用于在AF侧标识该组，同时提供该组所包含的UE成员列表；
AF所提供的组信息最终会被发送给UDM，UDM生成一个External group ID所对应的Internal group ID，该ID用于在5GC网络内部标识该组；同时UDM会保存Internal group ID所对应的组成员列表。
上文结合图1介绍了本申请实施例能够应用的场景，还简单介绍了本申请中涉及的基本概念，下文中将结合附图详细介绍本申请提供的选择边缘应用服务器的方法。
下文示出的实施例并未对本申请实施例提供的方法的执行主体的具体结构特别限定，只要能够通过运行记录有本申请实施例的提供的方法的代码的程序，以根据本申请实施例提供的方法进行通信即可，例如，本申请实施例提供的方法的执行主体可以是核心网设备，或者是核心网设备中能够调用程序并执行程序的功能模块。
为了便于理解本申请实施例，做出以下几点说明。
第一，在本申请中，“用于指示”可以理解为“使能”，“使能”可以包括直接使能和间接使能。当描述某一信息用于使能A时，可以包括该信息直接使能A或间接使能A，而并不代表该信息中一定携带有A。
将信息所使能的信息称为待使能信息，则具体实现过程中，对待使能信息进行使能的方式有很多种，例如但不限于，可以直接使能待使能信息，如待使能信息本身或者该待使能信息的索引等。也可以通过使能其他信息来间接使能待使能信息，其中该其他信息与待使能信息之间存在关联关系。还可以仅仅使能待使能信息的一部分，而待使能信息的其他部分则是已知的或者提前约定的。例如，还可以借助预先约定(例如协议规定)的各个信息的排列顺序来实现对特定信息的使能，从而在一定程度上降低使能开销。同时，还可以识别各个信息的通用部分并统一使能，以降低单独使能同样的信息而带来的使能开销。
第二，在本申请中示出的第一、第二以及各种数字编号(例如，“#1”、“#2”等)仅为描述方便，用于区分的对象，并不用来限制本申请实施例的范围。例如，区分不同消息等。而不是用于描述特定的顺序或先后次序。应该理解这样描述的对象在适当情况下可以互换，以便能够描述本申请的实施例以外的方案。
第三，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
第四，在本申请中，“预配置”可包括预先定义，例如，协议定义。其中，“预先定义”可以通过在设备(例如，包括各个网元)中预先保存相应的代码、表格或其他可用于指示相关信息的方式来实现，本申请对于其具体的实现方式不做限定。
第五，本申请实施例中涉及的“保存”，可以是指的保存在一个或者多个存储器中。所述一个或者多个存储器，可以是单独的设置，也可以是集成在编码器或者译码器，处理器、或通信装置中。所述一个或者多个存储器，也可以是一部分单独设置，一部分集成在 译码器、处理器、或通信装置中。存储器的类型可以是任意形式的存储介质，本申请并不对此限定。
第六，本申请实施例中涉及的“协议”可以是指通信领域的标准协议，例如可以包括5G协议、新空口(new radio，NR)协议以及应用于未来的通信系统中的相关协议，本申请对此不做限定。
以下，以网元之间的交互为例详细说明本申请实施例提供的配置策略的方法。应理解，本申请中的各实施例中术语和步骤可以互相参考。
下面结合图2介绍一种配置策略的方法200。该方法200包括：
S201，生成AF请求。
示例性地，AF生成AF请求(Creation of AF request)消息，该请求消息中可以包括以下信息元素：目标UE的相关信息(例如目标UE标识(Target UE Identifier))、边缘计算/应用服务器地址列表(DNAIs)与用于识别流量的信息(DNN、S-NSSAI、ApplicationID或AF-service-Identifier)、数据路径QoS监视请求等。其中，目标UE的相关信息可以是单个UE(individualUE)，可通过GPSI、IP地址/前缀或MAC地址标识，也可以是一组UE(agroupofUE)，可由外部groupID进行标识，或者是由DNN、S-NSSAI和DNAI组合标识的任意UE(anyUE)。具体内容可参考现有协议，本申请不对此作具体限定。
该AF还可以通过该AF请求消息携带业务流路由控制信息，在这种情况下，AF可以在该AF请求消息中携带组标识(groupID)，以便可以针对该组中的多个UE提供访问控制策略。
S202，AF向NEF发送AF请求消息。
示例性地，AF调用Nnef_TrafficInfluence服务，将生成的应用层信息发送给NEF，主要操作包括创建、更新、删除请求。
S203，UDR和NEF保存信息/更新信息/移除信息。
示例性地，在AF调用的是Nnef_TrafficInfluence_Creat/Updating服务的情况下，NEF将接收到的应用层信息保存到UDR中。在AF调用的是Nnef_TrafficInfluence_Delete服务的情况下，NEF将应用层信息在UDR中删除。
S204，NEF向AF发送AF请求响应消息。
NEF向AF发送响应消息。
S205，UDR向PCF发送DM通知消息。
PCF订阅了AF请求的修改，则UDR向PCF发送数据更改的Nudr_DM_Notify通知。PCF根据应用层信息和请求确定业务相关的PDU会话制定以及相应策略。
S206，PCF向SMF发送SM策略控制更新通知
相关策略生成后，PCF调用Npcf_SMPolicyControl_UpdateNotify服务，将策略更新发送给SMF/I SMF，同时消息中可以携带groupID，以表示该策略针对该组中的多个UE。
S207，SMF和UPF进行业务流路由重配置(Traffic Routing Reconfiguration)。
SMF从PCF接收到相关策略后，根据相关策略与UPF进行业务流路由重配置。
通过上述方案，AF可以通过group机制进行策略定义，即AF可以预先定义一个group及其所包含的组成员，然后使用group ID来指代group成员。然而，group机制只能针对同一个PLMN的非漫游(non-roaming)场景，也就是说，group只能包含相同的PLMN 的UE。因此，AF无法同时为不同PLMN的UE进行策略定义，例如，AF无法同时对漫游用户和非漫游用户进行访问策略控制。
有鉴于此，下文将结合附图详细说明本申请实施例提供的配置策略的方法。本申请提供的实施例可以应用于上述图1所示的网络架构中，不作限定。
图3示出了本申请实施例提供的配置策略的方法300的示例性流程图。首先结合方法300介绍本申请实施例提供的一种可能的实现方式(记为方案A)。从图3中可以看出，方法300包括：
S301，AF生成策略。
示例性地，AF生成策略，该策略可以是针对应用的策略，该策略也可以称为访问控制策略，或者是流量卸载策略(traffic offload policy)。具体地，该策略例如可以是允许属于某个组的成员访问边缘控制。
S302，AF向NEF发送业务流路由控制信息和第一服务类型信息。
示例性地，AF可以调用Nnef_TrafficInfluence服务将该策略对应的业务流路由控制信息以及第一服务类型(servicecategory)信息发送给NEF，该业务流路由控制信息与该第一服务类型信息对应。
其中，该业务流路由控制信息可以是用于对业务流的路由进行控制/影响的信息，例如该业务流路由控制信息用于将业务流路由到数据网络的本地接入。例如该业务流路由控制信息中可以包含业务描述符信息(e.g.Application ID,FQDN,IP五元组)，应用位置信息(e.g.DNAI)，目标UE标识信息(e.g.UE ID，group ID)，N6接口业务路由需求信息等。应理解，在不同场景中，该业务流路由控制信息还可能有其他名称，例如，该业务流路由控制信息还可以称作访问控制策略信息或者业务路由控制信息，本申请不作限定。
本申请中的“业务流”也可称为“业务”，例如“业务流路由控制信息”也可称为“业务路由控制信息”，两者可以等价互换。“业务流路由控制信息”也可称为应用功能请求信息。
其中，该第一服务类型信息可以是用户设备与运营商(例如网络运营商)之间，或者用户设备与应用服务商(例如提供各种互联网应用服务的公司，例如Google，Facebook，Tencent等)之间签约信息(例如视频会员(Video VIP)签约信息)。运营商或者应用服务商可以根据该签约信息为签约用户提供不同的服务，策略等。例如，第一服务类型信息可以包括允许用户使用的服务或者应用的信息，例如：服务标识信息、服务名称信息、服务范围信息，服务类别信息，允许使用的服务类别信息，允许使用的服务名称信息，允许使用的服务范围信息，应用描述符信息(完全限定域名(fully qualified domain name，FQDN)、应用标识(application identifier，App ID)、五元组等)、签约用户的等级信息、签约用户类别信息、用户所属的组标识信息等。
第一服务类型信息包括第一服务类别信息和/或第一签约者类别信息。其中，第一服务类别信息可以是用户设备可以使用的服务或者应用的信息。例如允许用户使用的服务或者应用的信息(例如，服务标识信息、服务名称信息、服务范围信息，服务类别信息，允许使用的服务类别信息，允许使用的服务名称信息，允许使用的服务范围信息，应用描述符信息(FQDN，App ID，五元组)等)；第一签约者类别信息可以是用户设备所签约的业务信息、签约用户的等级信息(例如金银铜用户)、签约用户类别信息、用户所属的组 标识信息等。
应理解，在某种实现方式中，第一服务类型信息可以包含在业务流路由控制信息中，作为业务流路由控制信息的一部分，或者，该第一服务类型信息也可以不包括在业务流路由控制信息中。
应理解，上述针对业务流路由控制信息、第一服务类型信息等术语的描述也适用于本申请实施例中其他步骤，或其他实施例中相关术语的解释，后续不再重复说明。
可选地，消息中还可以包括目标UE的标识(Target UE Identifier)，并且AF将该Target UE Identifier设置为任意UE(anyUE)或者Group ID。
可选地，消息中还可以包括第一应用标识信息和/或第一应用服务商标识信息。其中，该第一应用标识信息以及该第一应用服务商标识信息与该第一服务类型信息对应。应理解，AF可以只发送第一应用标识信息和第一应用服务商标识信息中的一个。
第一应用标识信息用于标识应用，第一应用服务商标识信息用于标识应用服务商，第一应用标识信息例如可以是应用标识(application identifier，APP ID)或者FQDN信息，IP五元组信息等；应用服务商标识例如可以是应用服务商标识(application service provider identifier，ASP ID)，应用服务商名称等，具体例如Tencent，Google，WeChat，YouTube等。
S303，NEF向UDR发送业务流路由控制信息和第一服务类型信息。对应地，UDR接收来自NEF的业务流路由控制信息和第一服务类型信息。
S304，UDR向PCF发送业务流路由控制信息和第一服务类型信息。对应地，PCF接收来自UDR的业务流路由控制信息和第一服务类型信息。
可选地，如果AF还向NEF发送了第一应用标识信息和/或第一应用服务商标识信息，则NEF还向UDR发送该第一应用标识信息和/或第一应用服务商标识信息。对应地，UDR向PCF发送该第一应用标识信息和/或第一应用服务商标识信息。
示例性地，NEF调用Nnef_TrafficInfluence服务向UDR发送业务流路由控制信息、第一服务类型信息，Target UE Identifier设置为anyUE或者group ID。可选地，消息中还包括第一应用标识信息和/或第一应用服务商标识信息。
UDR接收来自NEF的业务流路由控制信息以及第一服务类型信息(可选地还包括第一应用标识信息和/或第一应用服务商标识信息)之后，使用Nudr_DM_Notify服务向PCF发送接收到的业务流路由控制信息、第一服务类型信息，Target UE Identifier设置为anyUE或者group ID，可选地消息中还包括第一应用标识信息和/或第一应用服务商标识信息。
对应地，PCF从UDR接收该业务流路由控制信息以及第一服务类型信息(可选地还包括第一应用标识信息和/或第一应用服务商标识信息)之后，PCF可以将这些信息保存。
应理解，S301至S304可以单独执行，也可以与后续步骤(S305至S310)结合起来执行，本申请不做限定。当S301至S304与后续步骤结合执行的时候，后续步骤可能是在S304执行完成之后立刻执行，也可能在S304执行完成之后经过了一段时间后才执行，本申请不做限定。
进一步地，PCF获取用户设备的签约信息。
在一种实现方式(记为方式1)中，PCF从UDR获取用户设备的签约信息。
S305，UDR向PCF发送用户设备的签约信息，该签约信息包括第二服务类型信息， 以及该用户设备的标识(记为UEID)。
应理解，用户设备的签约信息可以是用户设备与运营商之间的签约信息，也可以是用户设备与应用服务商之间的签约信息。其中，用户设备与应用服务商之间的签约信息也可以称为“应用数据”。
该第二服务类型信息包括第二服务类别信息和/或第二签约者类别信息。针对第二服务类型的解释可参照上述针对第一服务类型信息的解释，这里不再赘述。
可选地，该签约信息还包括第二应用标识信息和/或第二应用服务商标识信息。
应理解，UDR预先保存了与用户设备的签约信息，具体方式这里不做限定。
在另一种实现方式(记为方式2)中，PCF通过SMF从UDM获取用户设备的签约信息。
S306，SMF从UDM接收用户设备的签约信息，该签约信息中包括第二服务类型信息以及该用户设备的UEID。示例性地，SMF可以在一个用户设备接入网络的时候，向UDM请求获取该用户设备的签约信息。UDM根据SMF的请求查找到该用户设备的签约信息之后，将该用户设备的签约信息发送给SMF。例如，UDM接收到来自SMF的签约信息请求消息，该签约信息请求消息包括UEID，该UEID例如可以是SUPI，该签约信息请求消息用于请求该用户设备的签约信息。UDM根据该UEID在本地存储检索该用户设备的签约信息，当UDM检索到该用户设备的签约信息后，则UDM将该UE的签约信息发送给SMF，该签约信息包括该UE的第二服务类型信息。可选地还包括第二应用标识信息和/或第二应用服务商标识信息。
应理解，UDM预先保存了用户设备的签约信息，具体方式这里不做限定。
S307，SMF向PCF发送该签约信息，该签约信息中包括第二服务类型信息，可选还包括第二应用标识信息和/或第二应用服务商标识信息。
示例性地，SMF通过UDM获取到用户设备的签约信息之后，调用Npcf_SMPolicyControl服务将该签约信息发送给PCF。
S308，PCF根据业务流路由控制信息为第一服务类型信息对应的用户设备生成PCC规则(策略与计费控制规则)。
示例性地，PCF获取该用户设备的签约信息之后，根据该用户设备的签约信息判断该用户设备是否是第一服务类型信息对应的用户设备，如果是的话，PCF根据业务流路由控制信息为该用户设备生成PCC规则。其中，PCF根据业务流路由控制信息为该用户设备生成PCC规则，可以指的是，PCF根据业务流路由控制信息为该用户设备的会话(例如是PDU会话)生成PCC规则。
应理解，“第一服务类型信息所对应的用户设备”可以是指签约所述第一服务类型信息的用户设备，或者应用数据中指示了与第一服务类型信息存在对应关系的用户设备。
应理解，在本申请中，PCC规则用于对业务流的路由进行控制。PCC规则中包含业务流引导控制信息，例如可以包含业务流标识信息，DNAI信息，业务流引导策略信息，N6接口业务流路由信息等。
应理解，除了业务流路由控制信息以外，PCF可能还需要其他信息来生成PCC规则，本申请不作限定。
还应理解，第一服务类型信息对应的用户设备，可以指的是签约了第一服务类型信息 的用户设备，或者指的是应用数据中与第一服务类型信息存在对应关系的用户设备。其中，签约了第一服务类型信息的用户设备，可以指的是与运营商签约了第一服务类型信息的用户设备，也可以指的是与应用签约了第一服务类型信息的用户设备。
下面结合示例介绍一种PCF判断该用户设备是否为第一服务类型信息对应的用户设备的具体实现方式。
PCF判断第二服务类型信息是否与第一服务类型信息匹配，在匹配的情况下，PCF确定该用户设备为第一服务类型信息对应的用户设备。
其中，第二服务类型信息与第一服务类型信息匹配，可以指的是第二服务类型信息包括在第一服务类型信息中。
可选地，PCF还可以判断第二应用标识信息和/或第二应用服务商标识信息与第一应用标识信息和/或第一应用服务商标识信息是否匹配，在匹配的情况下，PCF确定该用户设备为第一服务类型信息对应的用户设备。
其中，第二应用标识信息和/或第二应用服务商标识信息与第一应用标识信息和/或第一应用服务商标识信息匹配，可以指的是第二应用标识信息和/或第二应用服务商标识信息与第一应用标识信息和/或第一应用服务商标识信息相同。
本申请对PCF根据业务流路由控制信息生成PCC规则的具体方式不做限定，现有技术中的或本领域技术人员能够想到的PCC规则生成方式都应在本申请的保护范围内。
S309，PCF向SMF发送PCC规则。
示例性地，在PCF为该用户设备生成PCC规则之后，向SMF发送该PCC规则。例如，PCF调用Npcf_SMPolicyControl服务将该PCC规则发送给SMF。应理解，消息中还携带UEID。
S310，SMF基于PCC规则配置UE的用户面。
示例性地，SMF接收到来自PCF的针对该用户设备的PCC规则之后，生成相应的用户面配置，即进行policy的执行，具体方式本申请不做限定。
在上述方案中，AF通过UDR向PCF提供业务流路由控制信息的时候，同时提供与该业务流路由控制信息对应的服务类型信息(即第一服务类型信息)。因此，当PCF确定某个用户设备的签约信息中的服务类型信息与该业务流路由控制信息对应的服务类型信息相同时，则PCF可以使用该业务流路由控制信息为该用户设备生成PCC规则。
基于上述方案，网络设备同时为多个不同的用户配置访问控制策略，且该多个不同的用户可以属于不同PLMN下的用户，即本申请实施例提供的配置策略的方法，可以同时为漫游用户和非漫游用户配置访问控制策略。
下面结合图3中的方法300的示例性流程图，介绍本申请实施例提供的另一种可能的实现方式(记为方案B)。
应理解，在方案B中，S301-S307与方案A中的S301-S307类似，因此不再重复说明。但需要注意的是，在方案B中，第一服务类型信息包括多个服务类型信息。应理解，这里的服务类型信息均可以参考上述实施例中关于第一服务类型的解释，这里不再重复说明。也就是说，第一服务类型信息可以是多个服务类型信息的集合，这里的多个服务类型信息中的每个服务类型信息均可以包括第一服务类型信息和/或第一签约者类别信息，但应理解，不同服务类型信息所包括的第一服务类型信息和/或第一签约者类别信息可能相同也 可能不同，本申请不作限定。例如，第一服务类型信息包括Service Category#1和Service Category#2；或者，第一服务类型信息为多个服务类型信息的逻辑组合，例如，第一服务类型信息为Service Category#1 OR Service Category#2，或者Service Category#1 AND Service Category#2。
S308，PCF根据业务流路由控制信息为第一服务类型信息对应的用户设备生成策略与计费控制规则。
示例性地，PCF获取该用户设备的签约信息之后，根据该用户设备的签约信息判断该用户设备是否是第一服务类型信息对应的用户设备，如果是的话，PCF根据业务流路由控制信息为该用户设备生成策略与计费控制规则(PCC规则)。其中，PCF根据业务流路由控制信息为该用户设备生成PCC规则，可以指的是，PCF根据业务流路由控制信息为该用户设备的PDU会话生成PCC规则。
下面结合示例介绍一种PCF判断该用户设备是否为第一服务类型信息对应的用户设备的具体实现方式。
PCF判断第二服务类型信息是否与第一服务类型信息匹配，在匹配的情况下，PCF确定该用户设备为第一服务类型信息对应的用户设备。
在第一种实现方式中，第一服务类型信息包括多个服务类型信息。在这种实现方式中，第二服务类型信息与第一服务类型信息匹配，可以指的是第二服务类型信息包括第一服务类型信息中的多个服务类型信息，或者第二服务类型信息包括第一服务类型信息中的多个服务类型信息中的至少一个。例如，第一服务类型信息包括Service Category#1和Service Category#2，当第二服务类型信息包括Service Category#1以及Service Category#2时，表示第二服务类型信息与第一服务类型信息匹配；或者，当第二服务类型信息包括Service Category#1以及Service Category#2中的至少一个或多个时，表示第二服务类型信息与第一服务类型信息匹配；
在第二种实现方式中，第一服务类型信息为多个服务类型信息的逻辑组合。在这种实现方式中，第二服务类型信息与第一服务类型信息匹配，可以指的是第二服务类型信息满足该多个服务类型信息的逻辑组合。
例如，第一服务类型组合信息为service category#1 AND service category#2，则当第二服务类型信息同时包括service category#1和service category#2时，表示第二服务类型信息与该多个服务类型信息的逻辑组合。又例如，第一服务类型组合信息为service category#1 OR service category#2，则当第二服务类型信息包括service category#1和service category#3中的至少一个，则表示第二服务类型信息与该多个服务类型信息的逻辑组合匹配。
方案B中的S309与S310与方案A中的S309与S310类似，这里不再重复说明。
基于上述方案，策略控制网元可以根据业务流路由控制信息为第一服务类型信息对应的用户设备生成策略与计费控制规则。因此，上述方案可以同时为第一服务类型信息对应的一个或多个用户配置策略，例如可以为属于不同PLMN下的用户配置策略，从而可以提高策略配置的效率，节约资源。结合第一方面，在第一方面的某些实现方式中，该第一服务类型信息对应的用户设备，包括漫游用户设备和非漫游用户设备。
图4示出了本申请实施例提供的配置策略的方法400的示例性流程图。从图4中可以看出，方法400包括：
S401，用户进行签约。
示例性地，运营商或应用服务商与一个或多个用户进行应用层服务签约。
S402，AF向NEF发送签约用户的标识信息和服务类型信息。对应地，NEF接收来自AF的签约用户的标识信息和服务类型信息。
该签约用户的标识信息包括一个或多个签约用户的标识(Subscriber ID(s))。示例性地，一个或多个用户与应用进行签约之后，AF可以调用Nnef_ParameterProvision将签约用户的标识信息，以及签约对应的服务类型信息发送给NEF。
本申请中，“签约用户”也可称为“用户设备”，两者可以通用，例如“签约用户的标识”也可称为“用户设备的标识”，“签约用户的标识信息”也可称为“用户设备的标识信息”，“签约用户组”也可以称为“用户设备组”。
可选地，AF还可以向NEF发送应用标识信息(例如APPID)和/或应用服务商标识信息(例如ASP ID)；
可选地，AF还可以向NEF发送有效期period信息，该有效期可以指的是签约有效期。
S403，NEF对来自AF的消息进行认证授权。
示例性地，NEF对来自AF的消息进行认证授权，以确保AF有权进行相关操作。
在NEF对来自AF的消息认证授权通过之后，NEF将接收到的应用签约信息发送给UDR或UDM，下面分别举例说明。
在一种实现方式(记为方案1)中，AF将应用签约信息发送给UDR：
S404，NEF向UDR发送签约用户的标识信息，以及与该签约用户的标识信息对应的服务类型信息。对应地，UDR接收来自NEF的签约用户的标识信息和该服务类型信息。
可选地，NEF还可以向UDR发送应用标识信息和/或应用商标识信息。
可选地，NEF还可以向UDR发送有效期信息。
S405，UDR保存签约用户的标识信息和服务类型信息。
示例性地，UDR接收来自NEF的签约用户的标识信息和服务类型信息之后，在本地保存该签约用户的标识信息和该服务类型信息。
可选地，若UDR接收到来自NEF的应用标识信息和/或应用商标识信息，或者有效期信息，UDR也将这些信息保存在本地。
在另一种实现方式(记为方案2)中，AF将应用签约信息发送给UDM。
S406，NEF向UDM发送签约用户的标识信息，以及与该签约用户的标识信息对应的服务类型信息。对应地，UDM接收来自NEF的签约用户的标识信息和该服务类型信息。
可选地，NEF还可以向UDM发送应用标识信息和/或应用商标识信息。
可选地，NEF还可以向UDM发送有效期信息。
S407，UDM将ASPID/APP ID、服务类型信息、有效期保存到签约用户的签约数据中。
示例性地，UDM接收来自NEF的签约用户的标识信息和服务类型信息之后，将该服务类型信息保存到该签约用户的标识信息(Subscriber ID(s))对应的签约用户(Subscriber(s))的签约数据(Subscription data)中。
可选地，若UDM接收到来自NEF的应用标识信息和/或应用商标识信息，或者有效期信息，UDM也将这些信息保存到该签约用户的标识信息对应的签约用户的签约数据中。
可选地，S408，UDM向UDR发送签约用户的标识信息、服务类型信息。
可选地，UDM可以将从NEF接收到的信息发送给UDR，以将该信息参数保存到UDR的数据库中。
应理解，方法400可以独立实施，也可以与方法300结合实施。例如，方法400可以作为方法300的准备方案，在方法300之前进行执行，本申请对此不做限定。
在上述方案中，用户签约之后，可以通过AF将签约信息发送给UDM/UDR。对应地，UDM/UDR可以保存接收到的用户的签约信息。以便后续PCF可以根据该用户的签约信息中的参数确定是否可以为该用户生成对应的PCC规则，从而实现为多个用户配置策略的目的。
图5示出了本申请实施例提供的配置策略方法500的示例性流程图。从图5中可以看出，方法500包括：
S501，AF生成针对应用的策略。
示例性地，AF可以生成针对应用的策略，该策略也可以称为访问控制策略，或者是流量卸载策略(traffic offload policy)。具体地，该策略例如可以是允许属于某个组的成员访问边缘控制。
S502，AF向NEF发送业务流路由控制信息和用户设备组的标识信息。
示例性地，AF可以调用Nnef_TrafficInfluence服务将该策略对应的业务流路由控制信息以及用户设备组的标识信息发送给NEF。该用户设备组的标识信息可以包括用于标识用户设备组的标识，该用户设备组包括一个或多个签约用户，该用户设备组的标识例如可以称为组标识(group ID)或外部组标识(external group ID)。该用户设备组的标识信息可以用于索引UDR中的信息。
应理解，在本申请实施例中，用户设备组还可以称为签约用户组，签约用户还可以称为用户设备，即本申请对相关术语的名称不作限定，在不同场景下，可以采用类似名称相互替换，本领域一般技术人员能够理解或能够想到的表达方式均应在本申请实施例的保护范围内。
可选地，消息中还可以携带第一应用标识信息和/或第一应用服务商标识信息。其中，该第一应用标识信息以及该第一应用服务商标识信息与该第一服务类型信息对应。应理解，AF可以只发送第一应用标识信息和第一应用服务商标识信息中的一个。
S503，NEF向UDR发送业务流路由控制信息和用户设备组的标识信息。对应地，UDR接收来自NEF的业务流路由控制信息和用户设备组的标识信息。
示例性地，NEF将从AF接收到的信息发送给UDR。例如，NEF调用Nnef_TrafficInfluence服务将接收到的业务流路由控制信息和用户设备组的标识信息发送给UDR。
可选地，如果NEF还接收到第一应用标识和/或第一应用服务商标识，则NEF还向UDR发送该第一应用标识和/或该第一应用服务商标识。
S604，UDR向PCF发送业务流路由控制信息和签约用户的标识信息。
示例性地，UDR根据用户设备组的标识信息确定与该用户设备组的标识信息对应的一个或多个签约用户的标识信息。该一个或多个签约用户可以指的是属于该用户设备组的签约用户，该一个或多个签约用户的标识信息可以是该一个或多个签约用户的标识集合(Subscriber ID(s))。然后UDR将业务流路由控制信息，以及该一个或多个签约用户的 标识信息发送给PCF。例如，UDR使用Nudr_DM_Notify消息向PCF发送业务流路由控制信息和一个或多个签约用户的标识信息。
应理解，在上述方案之前，UDR预先保存了用户设备组的标识信息和一个或多个签约用户的标识信息之间的关联关系。UDR可以在ASP与用户签约之后，从NEF接收并保存了用户设备组的标识信息和一个或多个签约用户的标识信息，本实施例对具体实现方式不做具体限定。
对应地，PCF从UDR接收该业务流路由控制信息和签约用户的标识信息之后，PCF可以将这些信息进行保存。
应理解，该签约用户的标识信息可以与该业务流路由控制信息对应。该业务流路由控制信息与该签约用户的标识信息对应，指的是，该业务流路由控制信息与该签约用户的标识信息存在关联关系，或者，该业务流路由控制信息用于为该签约用户的标识信息对应的用户设备生成策略与计费控制规则，或者，该业务流路由控制信息与该签约用户的标识信息中的签约用户所在的用户设备组对应。
应理解，S501至S504可以单独执行，也可以与后续步骤(S505至S510)结合起来执行，本申请不做限定。当S501至S504与后续步骤结合执行的时候，后续步骤可能是在S504执行完成之后立刻执行，也可能在S504执行完成之后经过了一段时间后才执行，本申请不做限定。
进一步地，PCF获取用户设备的签约信息。
在一种实现方式(记为方式1)中，PCF从UDR获取用户设备的签约信息。
S505，UDR向PCF发送用户设备的签约信息，该签约信息包括用户设备的标识，该用户设备的标识例如可以是该用户设备的GPSI。对应地，UDR接收来自PCF的用户设备的签约信息。
可选地，该签约信息还包括第二应用标识信息和/或第二应用服务商标识信息。
应理解，UDR预先保存了与ASP签约的用户设备的签约信息，具体方式这里不做限定。
在另一种实现方式(记为方式2)中，PCF通过SMF从UDM获取用户设备的签约信息。
S506，SMF从UDM接收用户设备的签约信息，该签约信息中包括该用户设备的标识(可选地，还可以包括第二应用标识信息和/或第二应用服务商标识信息)。具体实现方式与方法300中的S306类似，这里不再赘述。
应理解，UDM预先保存了与ASP签约的UE的签约信息，具体方式这里不做限定。
S507，SMF向PCF发送该签约信息，该签约信息中包括用户设备的标识。此时该用户设备的标识可以包括该用户设备的GPSI和/或SUPI。
示例性地，SMF通过UDM获取到UE的签约信息之后，调用Npcf_SMPolicyControl服务将该签约信息发送给PCF。
S508，PCF根据业务流路由控制信息为签约用户生成PCC规则。
示例性地，PCF获取该用户设备的签约信息之后，根据该用户设备的标识判断该用户设备是否属于签约用户，如果属于的话，PCF根据业务流路由控制信息为该用户设备生成PCC规则。其中，PCF根据业务流路由控制信息为该用户设备生成PCC规则，可以指的 是，PCF根据业务流路由控制信息为该用户设备的PDU会话生成PCC规则。
下面结合示例介绍一种PCF判断该用户设备是否属于签约用户的具体实现方式。
PCF获取用户设备的签约信息之后，从该用户设备的签约信息中获取该用户设备的标识，当该用户设备的标识包括在签约用户的标识中时，PCF确定该用户设备属于签约用户。
可选地，PCF还可以判断第二应用标识信息和/或第二应用服务商标识信息与第一应用标识信息和/或第一应用服务商标识信息是否匹配，在匹配的情况下，PCF确定该用户设备为第一服务类型信息对应的用户设备。
其中，第二应用标识信息和/或第二应用服务商标识信息与第一应用标识信息和/或第一应用服务商标识信息匹配，可以指的是第二应用标识信息和/或第二应用服务商标识信息与第一应用标识信息和/或第一应用服务商标识信息相同。
应理解，S509与S510与方法300中的S309和S310类似，这里不再赘述。
在上述方案中，AF通过UDR向PCF提供业务流路由控制信息的时候，同时提供与该业务流路由控制信息对应的用户设备组的标识信息，而UDR可以根据该用户设备组的标识信息将组中的签约用户标识列表与该业务流路由控制信息一起发送给PCF。因此，当PCF确定某个用户设备的标识包括在该签约用户的标识列表中时，PCF可以使用该业务流路由控制信息为该用户设备生成PCC规则。
基于上述方案，策略控制网元可以根据业务流路由控制信息为签约用户生成策略与计费控制规则。因此，上述方案可以同时为一个或多个签约用户配置策略，例如可以为属于不同PLMN下的签约用户配置策略，从而可以提高策略配置的效率，节约资源。
图6示出了本申请实施例提供的方法600的示例性流程图。从图6中可以看出，该方法600包括：
S601，用户进行签约。
示例性地，应用服务商与一个或多个用户进行应用层服务签约。
S602，AF向NEF发送签约用户的标识信息和用户设备组的标识。对应地，NEF接收来自AF的签约用户的标识信息和用户设备组的标识。
其中，该签约用户的标识信息包括一个或多个签约用户的标识(Subscriber ID(s))，该用户设备组包括该一个或多个签约用户。该签约用户的标识信息与该用户设备组的标识对应。
示例性地，一个或多个用户与应用进行签约之后，AF可以调用Nnef_ParameterProvision将该一个或多个签约用户的标识信息，以及签约对应的用户设备组的标识发送给NEF。
可选地，AF还可以向NEF发送应用标识信息(例如APP ID)和/或应用服务商标识信息(例如ASP ID)；
可选地，AF还可以向NEF发送有效期period信息，该有效期可以指的是签约有效期。
S603，NEF对来自AF的消息进行认证授权。
示例性地，NEF对来自AF的消息进行认证授权，以确保AF有权进行相关操作。
在NEF对来自AF的消息认证授权通过之后，NEF将接收到的应用签约信息发送给UDR或UDM，下面分别举例说明。
在一种实现方式(记为方案1)中，AF将应用签约信息发送给UDR：
S604，NEF向UDR发送签约用户的标识信息，以及与该签约用户的标识信息对应的用户设备组的标识。对应地，UDR接收来自NEF的签约用户的标识信息和该用户设备组的标识。
可选地，NEF还可以向UDR发送应用标识信息和/或应用商标识信息。
可选地，NEF还可以向UDR发送有效期信息。
S605，UDR保存签约用户的标识信息和用户设备组的标识。
示例性地，UDR接收来自NEF的签约用户的标识信息和用户设备组的标识之后，在本地保存该签约用户的标识信息和该用户设备组的标识。
可选地，若UDR接收到来自NEF的应用标识信息和/或应用商标识信息，或者有效期信息，UDR也将这些信息保存在本地。
在另一种实现方式(记为方案2)中，AF将应用签约信息发送给UDM。
S606，NEF向UDM发送签约用户的标识信息，以及与该签约用户的标识信息对应的用户设备组的标识。对应地，UDM接收来自NEF的签约用户的标识信息和该用户设备组的标识。
可选地，NEF还可以向UDM发送应用标识信息和/或应用商标识信息。
可选地，NEF还可以向UDM发送有效期信息。
S607，UDM将ASP ID/APP ID、用户设备组的标识、有效期保存到签约用户的签约数据中。
示例性地，UDM接收来自NEF的签约用户的标识信息和用户设备组的标识之后，将该用户设备组的标识保存到该签约用户的标识信息(Subscriber ID(s))对应的签约用户(Subscriber(s))的签约数据(Subscription data)中。
可选地，若UDM接收到来自NEF的应用标识信息和/或应用商标识信息，或者有效期信息，UDM也将这些信息保存到该签约用户的标识信息对应的签约用户的签约数据中。
可选地，S608，UDM向UDR发送签约用户的标识信息、用户设备组的标识。
可选地，UDM可以将从NEF接收到的信息发送给UDR，以将该信息参数保存到UDR的数据库中。
应理解，方法600可以独立实施，也可以与方法500结合实施。例如，方法600可以作为方法500的准备方案，在方法500之前进行执行，本申请对此不做限定。
在上述方案中，用户签约之后，可以通过AF将用户设备组的标识和签约用户的标识信息发送给UDM/UDR，以便PCF可以根据业务流路由控制信息为签约用户生成PCC规则，从而实现为多个用户配置策略的目的。
图7示出了本申请实施例提供的配置策略的方法700的示例性流程图。从图7中可以看出，方法700包括：
S701，AF生成针对应用的策略。
S702，AF向NEF发送业务流路由控制信息以及服务类型信息。
S703，NEF向UDR发送业务流路由控制信息以及服务类型信息。
应理解，S701至S703与方法400中的S301至S303类似，为了简洁，这里不再重复说明。
S804，UDR向PCF发送业务流路由控制信息以及签约用户的标识信息。
示例性地，UDR根据服务类型信息，确定该服务类型信息对应的签约用户的标识信息，并将该签约用户的标识信息和业务流路由控制信息一起发送给PCF。例如，UDR使用Nudr_DM_Notify消息向PCF发送业务流路由控制信息和签约用户的标识信息。
应理解，在上述方案之前，UDR预先保存了服务类型信息和签约用户的标识信息之间的关联关系。UDR可以在ASP与用户签约之后，从NEF接收并保存了该服务类型信息和签约用户的标识信息，本实施例对此不做具体限定。
对应地，PCF从UDR接收该业务流路由控制信息和签约用户的标识信息(可选地还包括第一应用标识信息和/或第一应用服务商标识信息)之后，PCF可以将这些信息进行保存。
应理解，S701至S704可以单独执行，也可以与后续步骤(S705至S710)结合起来执行，本申请不做限定。当S701至S704与后续步骤结合执行的时候，后续步骤可能是在S804执行完成之后立刻执行，也可能在S704执行完成之后经过了一段时间后才执行，本申请不做限定。
进一步地，PCF获取用户设备的签约信息。
在一种实现方式(记为方式1)中，PCF从UDR获取用户设备的签约信息。
S705，UDR向PCF发送用户设备的签约信息，该签约信息包括用户设备的标识，该用户设备的标识例如可以是该用户设备的GPSI。对应地，UDR接收来自PCF的用户设备的签约信息。
可选地，该签约信息还包括第二应用标识信息和/或第二应用服务商标识信息。
应理解，UDR预先保存了与ASP签约的用户设备的签约信息，具体方式这里不做限定。
在另一种实现方式(记为方式2)中，PCF通过SMF从UDM获取用户设备的签约信息。
S706，SMF从UDM接收用户设备的签约信息，该签约信息中包括该用户设备的标识。(可选地，还可以包括第二应用标识信息和/或第二应用服务商标识信息)。具体实现方式与方法400中的S306类似，这里不再赘述。
S707，SMF向PCF发送该签约信息，该签约信息中包括用户设备的标识。此时该用户设备的标识可以包括该用户设备的GPSI和/或SUPI。
示例性地，SMF通过UDM获取到UE的签约信息之后，调用Npcf_SMPolicyControl服务将该签约信息发送给PCF。
S708，PCF根据业务流路由控制信息为签约用户生成PCC规则。
应理解，S708与方法500中的S508类似，为了简洁，这里不再赘述。
还应理解，S709与S710与方法300中的S309和S310类似，这里不再赘述。
在上述方案中，AF通过UDR向PCF提供业务流路由控制信息的时候，同时提供与该业务流路由控制信息对应的服务类型信息，而UDR可以根据该服务类型信息，将该服务类型信息对应的签约用户标识和该业务流路由控制信息一起发送给PCF。因此，当PCF确定某个用户设备的标识包括在该签约用户的标识中时，PCF可以使用该业务流路由控制信息为该用户设备生成PCC规则。
基于上述方案，策略控制网元可以根据业务流路由控制信息为签约用户生成策略与计 费控制规则。因此，上述方案可以同时为一个或多个签约配置策略，例如可以为属于不同PLMN下的签约用户配置策略，从而可以提高策略配置的效率，节约资源。
图8示出了本申请实施例提供的方法800的示例性流程图。从图8中可以看出，方法800包括：
S801，用户进行签约。
示例性地，应用服务商与一个或多个用户进行应用层服务签约。
S802，AF向NEF发送签约用户的标识信息和服务类型信息。对应地，NEF接收来自AF的签约用户的标识信息和服务类型信息。
其中，该签约用户的标识信息包括一个或多个签约用户的标识(Subscriber ID(s))。该签约用户的标识信息与该服务类型信息对应。
示例性地，一个或多个用户与应用进行签约之后，AF可以调用Nnef_ParameterProvision将该一个或多个签约用户的标识信息，以及签约对应的服务类型信息发送给NEF。
可选地，AF还可以向NEF发送应用标识信息(例如APP ID)和/或应用服务商标识信息(例如ASP ID)；
可选地，AF还可以向NEF发送有效期period信息，该有效期可以指的是签约有效期。
S803，NEF对来自AF的消息进行认证授权。
示例性地，NEF对来自AF的消息进行认证授权，以确保AF有权进行相关操作。
在NEF对来自AF的消息认证授权通过之后，NEF将接收到的应用签约信息发送给UDR或UDM，下面分别进行举例说明。
在一种实现方式(记为方案1)中，AF将应用签约信息发送给UDR：
S804，NEF向UDR发送签约用户的标识信息，以及与该签约用户的标识信息对应的服务类型信息。对应地，UDR接收来自NEF的签约用户的标识信息和该服务类型信息。
可选地，NEF还可以向UDR发送应用标识信息和/或应用商标识信息。
可选地，NEF还可以向UDR发送有效期信息。
S805，UDR保存签约用户的标识信息和服务类型信息。
示例性地，UDR接收来自NEF的签约用户的标识信息和服务类型信息之后，在本地保存该签约用户的标识信息和该服务类型信息。
可选地，若UDR接收到来自NEF的应用标识信息和/或应用商标识信息，或者有效期信息，UDR也将这些信息保存在本地。
在另一种实现方式(记为方案2)中，AF将应用签约信息发送给UDM。
S806，NEF向UDM发送签约用户的标识信息，以及与该签约用户的标识信息对应的服务类型信息。对应地，UDM接收来自NEF的签约用户的标识信息和该服务类型信息。
可选地，NEF还可以向UDM发送应用标识信息和/或应用商标识信息。
可选地，NEF还可以向UDM发送有效期信息。
S807，UDM将ASP ID/APP ID、服务类型信息、有效期保存到签约用户的签约数据中。
示例性地，UDM接收来自NEF的签约用户的标识信息和服务类型信息之后，将该服务类型信息保存到该签约用户的标识信息(Subscriber ID(s))对应的签约用户(Subscriber(s)) 的签约数据(Subscription data)中。
可选地，若UDM接收到来自NEF的应用标识信息和/或应用商标识信息，或者有效期信息，UDM也将这些信息保存到该签约用户的标识信息对应的签约用户的签约数据中。
可选地，S808，UDM向UDR发送签约用户的标识信息、服务类型信息。
可选地，UDM可以将从NEF接收到的信息发送给UDR，以将该信息参数保存到UDR的数据库中。
应理解，方法800可以独立实施，也可以与方法700结合实施。例如，方法800可以作为方法700的准备方案，在方法700之前进行执行，本申请对此不做限定。
在上述方案中，用户签约之后，可以通过AF将服务类型信息和签约用户的标识信息发送给UDM/UDR，以便PCF可以根据业务流路由控制信息为签约用户生成PCC规则，从而实现为多个用户配置策略的目的。
在上述方案中，ASP与用户签约之后，可以通过AF将服务类型信息和签约用户的标识发送给UDR，在这种情况下，当AF向UDR提供业务流路由控制信息和该业务流路由控制信息对应的服务类型信息时，UDR可以根据该服务类型信息确定对应的签约用户的标识，并将该签约用户的标识并该业务流路由控制信息发送给PCF。因此，当PCF确定某个用户设备属于该签约用户时，便可以根据AF提供的业务流路由控制信息为该用户设备生成PCC规则，从而实现为多个用户配置策略的目的。
应理解，本申请中的各种信息或者消息的名称仅仅是一种可能的示例，在不同场景下，还可以有其他名称，例如，第一服务类型信息也可以称为第一信息，第一服务类别信息也可以称为第二信息，第一签约者类别信息也可以称为第三信息，业务流路由控制信息也可以称为业务流路由信息，或者业务流路由影响信息，或者业务路由控制信息，或者业务路由影响信息或者应用功能请求信息等等，本申请对此不作限定。
图9示出了本申请实施例提供的配置策略的方法900的示例性流程图。首先结合方法900介绍本申请实施例提供的一种可能的实现方式(记为方案a)。从图9中可以看出，方法900包括：
S901，AF生成业务流路由控制信息。
示例性地，AF可以生成业务流路由控制信息，该业务流路由控制信息也可以称为访问控制策略，或者是流量卸载策略(traffic offload policy)。具体地，该业务流路由控制信息例如可以是用于对业务流的路由进行控制/影响的信息，例如该业务流路由控制信息用于将业务流路由到到数据网络的本地接入。
S902，AF向NEF发送业务流路由控制信息和第一组信息。
示例性地，AF可以调用Nnef_TrafficInfluence服务将业务流路由控制信息以及第一组信息发送给NEF，该第一组信息与该业务流路由控制信息对应。
其中，该第一组信息包括多个组标识(group ID)，例如，该第一组信息包括第一组标识(记为group ID1)以及第二组标识(记为group ID2)，该第一组信息可以记为group comb1。也就是说，本实施例中的第一组信息可以是多个组标识的合集。但需要说明的是，第一组信息还可能包括除了组标识以外的其他信息，本申请对此不作限定。
应理解，本申请中组标识也可以称为组标识信息。
应理解，这里的组标识(group ID)既可以是内部标识也可以是外部标识，例如，第 一组标识为内部组标识(internal group ID)，第二组标识为外部组标识(external group ID)，或者第一组标识和第二组标识都为内部组标识等，本申请不作具体限定。
该第一组信息与该业务流路由控制信息对应，指的是，该业务流路由控制信息适用于与该第一组信息匹配的用户设备，或者说，该业务流路由控制信息适用于同时签约该第一组信息中的多个组标识对应的组的用户设备，或者说，该业务流路由控制信息用于为同时签约该第一组信息中的多个组标识对应的组的用户设备生成策略与计费控制规则。
还应理解，AF可以同时提供多个第一组信息，此时该业务流路由控制信息用于签约信息匹配至少一个第一组信息的用户设备。
还应理解，该第一组信息和该业务流路由控制信息可以是两个单独的信元；或者，第一组信息也可以作为业务流路由控制信息的一部分，在这种情况下，S902可以表达为：AF向NEF发送业务流路由控制信息，该业务流路由控制信息包括第一组信息。
S903，NEF向UDR发送业务流路由控制信息和第二组信息。
示例性地，NEF接收来自AF的业务流路由控制信息和第一组信息之后，可以调用Nudr_DM_Create服务向UDR发送该业务流路由控制信息和第二组信息，其中，该第二组信息可能与第一组信息相同，也可能是由第一组信息转换得到的。例如，第一组信息包括的多个组标识均为内部组标识，则此时第二组信息与第一组信息相同，即NEF可以直接将接收到第一组信息发送给UDR。又例如，第一组信息包括的多个组标识为外部组标识，则NEF接收到第一组信息之后，将第一组信息中的外部组标识转换为内部组标识得到第二组信息，然后NEF将第二组信息发送给UDR。
需要说明的是，AF也可以将业务流路由控制信息和第一组信息直接发送给UDR，本申请不作限定。
S904，UDR向PCF发送业务流路由控制信息和第二组信息。
示例性地，UDR接收来自NEF的业务流路由控制信息和第二组信息之后，将该业务流路由控制信息和该第二组信息发送给PCF。例如，例如，UDR使用Nudr_DM_Notify消息向PCF发送将该业务流路由控制信息和该第二组信息。
应理解，该业务流路由控制信息和该第二组信息可以承载于同一条消息中，也可以承载于不同消息中，也就是说，UDR可以同时发送该业务流路由控制信息和该第二组信息，也可以分别发送该业务流路由控制信息和该第二组信息。该第二组信息可以作为业务流路由控制信息的一部分，或者第二组信息与业务流路由控制信息可以是两个单独的信元，本申请不作限定。
对应地，PCF从UDR接收该业务流路由控制信息和该第二组信息之后，PCF可以将这些信息保存。
应理解，该第二组信息和该业务流路由控制信息可以是两个单独的信元；或者，该第二组信息也可以作为业务流路由控制信息的一部分，在这种情况下，S903可以表达为：NEF向UDR发送业务流路由控制信息，该业务流路由控制信息包括第二组信息；S904可以表达为：UDR向PCF发送业务流路由控制信息，该业务流路由控制信息包括第二组信息。
还应理解，S901至S904可以单独执行，也可以与后续步骤(S905至S910)结合起来执行，本申请不做限定。当S901至S904与后续步骤结合执行的时候，后续步骤可能是 在S904执行完成之后立刻执行，也可能在S904执行完成之后经过了一段时间后才执行，本申请不做限定。
进一步地，PCF获取用户设备的签约信息。
在一种实现方式(记为方式1)中，PCF从UDR获取用户设备的签约信息。
S905，UDR向PCF发送用户设备的签约信息。
示例性地，该签约信息包括该用户设备所签约的组的组标识(group ID)，或者说，该签约信息包括该用户设备所属组的组标识。
应理解，该签约信息中的组标识可以包括一个或多个组的标识信息。
应理解，UDR预先保存了用户设备的签约信息，具体方式这里不做限定。
在另一种实现方式(记为方式2)中，PCF通过SMF从UDM获取用户设备的签约信息。
S906，SMF从UDM接收用户设备的签约信息，该签约信息中包括该用户设备所签约的组的组标识。具体实现方式与方法300中的S306类似，这里不再赘述。
应理解，UDM预先保存了UE的签约信息，具体方式这里不做限定。
S907，SMF向PCF发送该签约信息，该签约信息中包括用户设备所签约的组的组标识。
示例性地，SMF通过UDM获取到UE的签约信息之后，调用Npcf_SMPolicyControl服务将该签约信息发送给PCF。
S908，PCF根据业务流路由控制信息为与第二组信息匹配的用户设备生成PCC规则。
示例性地，PCF获取用户设备的签约信息之后，根据该签约信息中携带的组标识判断该用户设备与第二组信息是否匹配，如果匹配的话，PCF根据业务流路由控制信息为该用户设备生成PCC规则。其中，PCF根据业务流路由控制信息为该用户设备生成PCC规则可以指的是，PCF根据业务流路由控制信息为该用户设备的PDU会话生成PCC规则。
作为一种可能的实现方式，当签约信息包括第二组信息中所有的组标识时，则PCF判断该用户设备与第二组信息匹配，在这种情况下，PCF根据业务流路由控制信息为该用户设备生成相应的PCC规则。
S909，PCF向SMF发送PCC规则。
S910，SMF基于该PCC规则配置UE的用户面。
应理解，S909与S910与方法300中的S309和S310类似，这里不再赘述。
在上述方案中，AF通过UDR向PCF提供业务流路由控制信息的时候，同时提供与该业务流路由控制信息对应的组信息。当PCF确定某个用户设备与该组信息匹配时，PCF可以使用该业务流路由控制信息为该用户设备生成PCC规则。
基于上述方案，PCF可以根据业务流路由控制信息为与组信息对应的用户设备生成策略与计费控制规则。因此，上述方案可以同时为一个或多个签约用户配置策略，例如可以为属于不同PLMN下的签约用户配置策略，从而可以提高配置策略的效率，节约资源。
下面结合图9中的方法的示例性流程图，介绍本申请实施例提供的另一种可能的实现方式(记为方案b)。
应理解，在方案b中，S901-S907与方案a中的S901-S907类似，因此不再重复说明。但需要注意的是，在方案b中，第一组信息包括多个组标识(group ID)信息的逻辑组合， 例如，第一组信息包括以下信息：group ID1 AND group ID2 NOT group ID3，或者，group ID1 AND group ID2 AND group ID3。也就是说，本实施例中的第一组信息可以包括多个组标识，且该多个组标识存在逻辑关系。但需要说明的是，第一组信息还可能包括除了组标识以外的其他信息，本申请对此不作限定。
此时，业务流路由控制信息与第一组信息对应，指的是，该业务流路由控制信息适用于签约数据与第一组信息逻辑匹配的用户设备。
S908，PCF根据业务流路由控制信息为与第二组信息匹配的用户设备生成PCC规则。
示例性地，PCF获取用户设备的签约信息之后，根据该签约信息中携带的组标识判断该用户设备与第二组信息是否匹配，如果匹配的话，PCF根据业务流路由控制信息为该用户设备生成PCC规则。
作为一种可能的实现方式，当该用户设备的签约信息与第二组信息逻辑匹配时，PCF确定该用户设备与第二组信息匹配，其中，用户设备的签约信息与第二组信息逻辑匹配，指的是用户设备的签约信息中包括的组标识满足第二组信息中的多个组标识信息的逻辑组合关系，例如，第二组信息包括以下信息：group ID1 AND group ID2 NOT group ID3，则当用户设备的签约信息包括group ID1以及group 2，但不包括group ID3时，表示该用户设备的签约信息与该第二组信息逻辑匹配；又例如，第二组信息包括以下信息：group ID1 AND group ID2 AND group ID3，则当用户设备的签约信息包括group ID1、group ID2和group ID3时，表示该用户设备的签约信息与该第二组信息逻辑匹配。
S909和S910与方法300的S309和S310类似，为了简洁，这里不再赘述。
基于上述方案，策略控制网元可以根据业务流路由控制信息为与组信息对应的用户设备生成策略与计费控制规则。因此，上述方案可以同时为第一组信息对应的一个或多个用户配置策略，例如可以为属于不同PLMN下的用户配置策略，从而可以提高策略配置的效率，节约资源。
以上，结合图2至图9详细说明了本申请实施例提供的配置策略的方法。以下，结合图10至图12详细说明本申请实施例提供的用于配置策略的装置。应理解，装置实施例的描述与方法实施例的描述相互对应，因此，未详细描述的内容可以参见上文方法实施例，为了简洁，这里不再赘述。
图10是本申请实施例提供的配置策略的装置10的示意性框图。该装置10包括收发模块11和处理模块12。收发模块11可以实现相应的通信功能，处理模块12用于进行数据处理，或者说该收发模块11用于执行接收和发送相关的操作，该处理模块12用于执行除了接收和发送以外的其他操作。收发模块11还可以称为通信接口或通信单元。
在一种可能的设计中，该装置10可对应于上文方法实施例中的各种网络设备，例如统一数据管理网元(例如UDM)、会话管理网元(例如SMF)、策略控制网元(例如PCF)、统一数据存储网元(例如UDR)、应用功能网元(例如AF)。
示例性地，该装置10可对应于本申请实施例的方法300-800中的统一数据管理网元或会话管理网元或策略控制网元或统一数据存储网元或应用功能网元(UDM或SMF或PCF或UDR或者AF)。
该装置10可以包括用于执行图2至图9中的上述各网络设备所执行的方法的模块。并且，该装置10中的各单元和上述其他操作和/或功能分别为了实现图2至图9所示方法 的相应流程。
该装置10中的该收发模块11执行上述各方法实施例中的各网络设备所执行的接收和发送操作，该处理模块12则执行除了该接收和发送操作之外的操作。
根据前述方法，图11为本申请实施例提供的用于配置策略的装置20的示意图。在一种可能的设计中，该装置20可对应于上文方法实施例中的各种网络设备，例如统一数据管理网元(例如UDM)、会话管理网元(例如SMF)、策略控制网元(例如PCF)、统一数据存储网元(例如UDR)、应用功能网元(例如AF)。
该装置20可以包括处理器21(即，处理模块的一例)和存储器22。该存储器22用于存储指令，该处理器21用于执行该存储器22存储的指令，以使该装置20实现如图2至图9对应的方法中的各网络设备执行的步骤。
进一步地，该装置20还可以包括输入口23(即，收发模块的一例)和输出口24(即，收发模块的另一例)。进一步地，该处理器21、存储器22、输入口23和输出口24可以通过内部连接通路互相通信，传递控制和/或数据信号。该存储器22用于存储计算机程序，该处理器21可以用于从该存储器22中调用并运行该计算机程序，以控制输入口23接收信号，控制输出口24发送信号，完成上述方法中终端设备或网络设备的步骤。该存储器22可以集成在处理器21中，也可以与处理器21分开设置。
可选地，若该通信装置20为通信设备，该输入口23为接收器，该输出口24为发送器。其中，接收器和发送器可以为相同或者不同的物理实体。为相同的物理实体时，可以统称为收发器。
可选地，若该通信装置20为芯片或电路，该输入口23为输入接口，该输出口24为输出接口。
作为一种实现方式，输入口23和输出口24的功能可以考虑通过收发电路或者收发的专用芯片实现。处理器21可以考虑通过专用处理芯片、处理电路、处理器或者通用芯片实现。
作为另一种实现方式，可以考虑使用通用计算机的方式来实现本申请实施例提供的通信设备。即将实现处理器21、输入口23和输出口24功能的程序代码存储在存储器22中，通用处理器通过执行存储器22中的代码来实现处理器21、输入口23和输出口24的功能。
该装置20所涉及的与本申请实施例提供的技术方案相关的概念，解释和详细说明及其他步骤请参见前述方法或其他实施例中关于这些内容的描述，此处不做赘述。
图12示出了一种简化的网络设备30的结构示意图。网络设备包括31部分以及32部分。31部分主要用于射频信号的收发以及射频信号与基带信号的转换；32部分主要用于基带处理，对网络设备进行控制等。31部分通常可以称为收发模块、收发机、收发电路、或者收发器等。32部分通常是网络设备的控制中心，通常可以称为处理模块，用于控制网络设备执行上述方法实施例中网络设备侧的处理操作。
31部分的收发模块，也可以称为收发机或收发器等，其包括天线和射频电路，其中射频电路主要用于进行射频处理。例如，可以将31部分中用于实现接收功能的器件视为接收模块，将用于实现发送功能的器件视为发送模块，即31部分包括接收模块和发送模块。接收模块也可以称为接收机、接收器、或接收电路等，发送模块可以称为发射机、发射器或者发射电路等。
32部分可以包括一个或多个单板，每个单板可以包括一个或多个处理器和一个或多个存储器。处理器用于读取和执行存储器中的程序以实现基带处理功能以及对网络设备的控制。若存在多个单板，各个单板之间可以互联以增强处理能力。作为一种可选的实施方式，也可以是多个单板共用一个或多个处理器，或者是多个单板共用一个或多个存储器，或者是多个单板同时共用一个或多个处理器。
例如，在一种实现方式中，图12所示的网络设备可以是图2至图9所示的方法中所示的任意网络设备，例如统一数据管理网元(例如UDM)、会话管理网元(例如SMF)、策略控制网元(例如PCF)、统一数据存储网元(例如UDR)、应用功能网元(例如AF)等。
31部分的收发模块用于执行图2至图9所示的方法中任意网络设备的收发相关的步骤；32部分用于执行图2至图9所示的方法中的任意网络设备的处理相关的步骤。
应理解，图12仅为示例而非限定，上述包括收发模块和处理模块的网络设备可以不依赖于图12所示的结构。
当该装置30为芯片时，该芯片包括收发模块和处理模块。其中，收发模块可以是输入输出电路、通信接口；处理模块为该芯片上集成的处理器或者微处理器或者集成电路。
本申请实施例还提供一种计算机可读存储介质，其上存储有用于实现上述方法实施例中由第网络设备执行的方法的计算机指令。
例如，该计算机程序被计算机执行时，使得该计算机可以实现上述方法实施例中由网络设备执行的方法。
本申请实施例还提供一种包含指令的计算机程序产品，该指令被计算机执行时使得该计算机实现上述方法实施例中由第一设备执行的方法，或由第二设备执行的方法。
本申请实施例还提供一种通信系统，该通信系统包括上文实施例中的网络设备。
上述提供的任一种装置中相关内容的解释及有益效果均可参考上文提供的对应的方法实施例，此处不再赘述。
在本申请实施例中，网络设备可以包括硬件层、运行在硬件层之上的操作系统层，以及运行在操作系统层上的应用层。其中，硬件层可以包括中央处理器(central processing unit，CPU)、内存管理单元(memory management unit，MMU)和内存(也称为主存)等硬件。操作系统层的操作系统可以是任意一种或多种通过进程(process)实现业务处理的计算机操作系统，例如，Linux操作系统、Unix操作系统、Android操作系统、iOS操作系统或windows操作系统等。应用层可以包含浏览器、通讯录、文字处理软件、即时通信软件等应用。
本申请实施例并未对本申请实施例提供的方法的执行主体的具体结构进行特别限定，只要能够通过运行记录有本申请实施例提供的方法的代码的程序，以根据本申请实施例提供的方法进行通信即可。例如，本申请实施例提供的方法的执行主体可以是网络设备，或者，是网络设备中能够调用程序并执行程序的功能模块。
本申请的各个方面或特征可以实现成方法、装置或使用标准编程和/或工程技术的制品。本文中使用的术语“制品”可以涵盖可从任何计算机可读器件、载体或介质访问的计算机程序。例如，计算机可读介质可以包括但不限于：磁存储器件(例如，硬盘、软盘或磁带等)，光盘(例如，压缩盘(compact disc，CD)、数字通用盘(digital versatile disc， DVD)等)，智能卡和闪存器件(例如，可擦写可编程只读存储器(erasable programmable read-only memory，EPROM)、卡、棒或钥匙驱动器等)。
本文描述的各种存储介质可代表用于存储信息的一个或多个设备和/或其它机器可读介质。术语“机器可读介质”可以包括但不限于：无线信道和能够存储、包含和/或承载指令和/或数据的各种其它介质。
应理解，本申请实施例中提及的处理器可以是中央处理单元(central processing unit，CPU)，还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还应理解，本申请实施例中提及的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)。例如，RAM可以用作外部高速缓存。作为示例而非限定，RAM可以包括如下多种形式：静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
需要说明的是，当处理器为通用处理器、DSP、ASIC、FPGA或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件时，存储器(存储模块)可以集成在处理器中。
还需要说明的是，本文描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的保护范围。
所属领域的技术人员可以清楚地了解到，为描述方便和简洁，上述描述的装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。此外，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元实现本申请提供的方案。
另外，在本申请各个实施例中的各功能单元可以集成在一个单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。例如，所述计算机可以是个人计算机，服务器，或者网络设备等。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，(SSD))等。例如，前述的可用介质可以包括但不限于：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到的变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求和说明书的保护范围为准。

Claims (32)

  1. 一种配置策略的方法，其特征在于，包括：
    策略控制网元接收业务流路由控制信息以及与所述业务流路由控制信息对应的第一服务类型信息，所述第一服务类型信息包括第一服务类别信息和/或第一签约者类别信息；
    所述策略控制网元根据所述业务流路由控制信息为所述第一服务类型信息对应的用户设备生成策略与计费控制规则；
    所述策略控制网元发送所述策略与计费控制规则。
  2. 根据权利要求1所述的方法，其特征在于，所述策略控制网元根据所述业务流路由控制信息为所述第一服务类型信息对应的用户设备生成策略与计费控制规则，包括：
    所述策略控制网元根据用户设备的签约信息确定所述用户设备为所述第一服务类型信息对应的用户设备；
    所述策略控制网元根据所述业务流路由控制信息为所述用户设备生成所述策略与计费控制规则。
  3. 根据权利要求2所述的方法，其特征在于，所述策略控制网元根据所述用户设备的签约信息确定所述用户设备为所述第一服务类型信息对应的用户设备，包括：
    在所述第一服务类型信息和第二服务类型信息匹配的情况下，所述策略控制网元确定所述用户设备为所述第一服务类型信息对应的用户设备，所述第二服务类型信息包括在所述用户设备的签约信息中，所述第二服务类型信息包括第二服务类型信息和/或第二签约者类别信息。
  4. 根据权利要求3所述的方法，其特征在于，所述在所述第一服务类型信息和第二服务类型信息匹配的情况下，所述策略控制网元确定所述用户设备为所述第一服务类型信息对应的用户设备，包括：
    在所述第二服务类型信息包括所述第一服务类型信息的情况下，所述策略控制网元确定所述用户设备为所述第一服务类型信息对应的用户设备；或者，
    在所述第一服务类型信息包括多个服务类型信息的情况下，当所述第二服务类型信息包括所述多个服务类型信息中所有服务类型信息时，所述策略控制网元确定所述用户设备为所述第一服务类型信息对应的用户设备，或者，当所述第二服务类型信息包括所述多个服务类型信息中的至少一个时，所述策略控制网元确定所述用户设备为所述第一服务类型信息对应的用户设备，所述多个服务类型信息中的每个服务类型信息均包括所述第一服务类别信息和/或第一签约者类别信息。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述方法还包括：
    所述策略控制网元接收与所述第一服务类型信息对应的第一应用标识信息和/或第一应用服务商标识信息。
  6. 根据权利要求5所述的方法，其特征在于，所述策略控制网元确定所述用户设备为所述第一服务类型信息对应的用户设备，包括：
    在第一应用标识信息和/或第一应用服务商标识信息，与第二应用标识信息和/或第二应用服务商标识信息匹配的情况下，所述策略控制网元确定所述用户设备为所述第一服务 类型信息对应的用户设备，所述第二应用标识信息和/或第二应用服务商标识信息包括在所述用户设备的签约信息中。
  7. 根据权利要求5或6所述的方法，其特征在于，所述方法还包括：
    在所述第一应用标识信息和/或第一应用服务商标识信息与所述第二应用标识信息和/或第二应用服务商标识信息相同的情况下，所述策略控制网元确定所述第一应用标识信息和/或第一应用服务商标识信息与所述第二应用标识信息或第二应用服务商标识信息匹配。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述策略控制网元接收业务流路由控制信息以及与所述业务流路由控制信息对应的第一服务类型信息，包括：
    所述策略控制网元接收来自网络开放功能网元的所述业务流路由控制信息以及与所述业务流路由控制信息对应的所述第一服务类型信息。
  9. 根据权利要求1至8中任一项所述的方法，其特征是在于，所述方法还包括：
    所述策略控制网元接收来自统一数据存储网元或者会话管理网元的所述用户设备的签约信息。
  10. 一种配置策略的方法，其特征在于，包括：
    策略控制网元接收业务流路由控制信息以及与所述业务流路由控制信息对应的签约用户的标识信息；
    所述策略控制网元根据所述业务流路由控制信息为所述签约用户生成策略与计费控制规则；
    所述策略控制网元发送所述策略与计费控制规则。
  11. 根据权利要求10所述的方法，其特征在于，所述策略控制网元根据所述业务流路由控制信息为所述签约用户生成策略与计费控制规则，包括：
    所述策略控制网元根据所述业务流路由控制信息为属于所述签约用户的用户设备生成策略与计费控制规则。
  12. 根据权利要求11所述的方法，其特征在于，所述方法还包括：
    在所述用户设备的标识包括在所述签约用户的标识信息中的情况下，所述策略控制网元确定所述用户设备属于所述签约用户。
  13. 根据权利要求11或12所述的方法，其特征在于，所述方法还包括：
    所述策略控制网元接收来自统一数据存储网元或会话管理网元的所述用户设备的签约信息，所述用户设备的签约信息包括所述用户设备的标识。
  14. 根据权利要求10至13中任一项所述的方法，其特征在于，所述策略控制网元接收业务流路由控制信息以及与所述业务流路由控制信息对应的签约用户的标识信息，包括：
    所述策略控制网元接收来自网络开放功能网元网元的所述业务流路由控制信息以及与所述业务流路由控制信息对应的签约用户的标识信息。
  15. 一种配置策略的方法，其特征在于，包括：
    应用功能网元发送业务流路由控制信息以及与所述业务流路由控制信息对应的第一服务类型信息，所述第一服务类型信息包括第一服务类别信息和/或第一签约者类别信息。
  16. 根据权利要求15所述的方法，其特征在于，所述方法还包括：
    所述应用功能网元发送一个或多个签约用户的标识信息和所述第一服务类型信息，所述一个或多个签约用户的标识信息与所述第一服务类型信息相关联。
  17. 根据权利要求15或16所述的方法，其特征在于，所述第一服务类型信息包括多个服务类型信息，所述多个服务类型信息中的每一个服务类型信息包括所述第一服务类别信息和/或所述第一签约者类别信息。
  18. 根据权利要求15至17中任一项所述的方法，其特征在于，所述方法还包括：
    所述应用功能网元发送与所述第一服务类型信息对应的第一应用标识信息和/或第一应用服务商标识信息。
  19. 一种配置策略的方法，其特征在于，包括：
    统一数据存储网元接收业务流路由控制信息以及与所述业务流路由控制信息对应的用户设备组的标识信息；
    所述统一数据存储网元根据所述用户设备组的标识信息确定与所述用户设备组的标识信息对应的签约用户的标识信息；
    所述统一数据存储网元向策略控制网元发送所述业务流路由控制信息和所述签约用户的标识信息，所述业务流路由控制与所述签约用户的标识信息相关联。
  20. 根据权利要求19所述的方法，其特征在于，所述统一数据存储网元接收来自应用功能网元的业务流路由控制信息以及与所述业务流路由控制信息对应的用户设备组的标识信息之前，所述方法还包括：
    所述统一数据存储网元接收来自所述应用功能网元的所述用户设备组的标识信息和所述签约用户的标识信息，所述用户设备组的标识和所述签约用户的标识信息相关联。
  21. 一种配置策略的方法，其特征在于，包括：
    策略控制网元接收业务流路由控制信息以及与所述业务流路由控制信息对应的组信息，所述组信息包括多个组标识；
    所述策略控制网元根据所述业务流路由控制信息为与所述组信息匹配的用户设备生成策略与计费控制规则；
    所述策略控制网元发送所述策略与计费控制规则。
  22. 根据权利要求21所述的方法，其特征在于，所述策略控制网元根据所述业务流路由控制信息为与所述组信息匹配的用户设备生成策略与计费控制规则，包括：
    所述策略控制网元根据用户设备的签约信息确定所述用户设备与所述组信息匹配；
    所述策略控制网元根据所述业务流路由控制信息为所述用户设备生成所述策略与计费控制规则。
  23. 根据权利要求22所述的方法，其特征在于，所述策略控制网元根据用户设备的签约信息确定所述用户设备与所述组信息匹配，包括：
    在所述用户设备的签约信息包括所述组信息中的多个组标识的情况下，所述策略控制网元确定所述用户设备与所述组信息匹配。
  24. 根据权利要求22所述的方法，其特征在于，所述组信息中的多个组标识存在逻辑关系；
    所述策略控制网元根据用户设备的签约信息确定所述用户设备与所述组信息匹配，包括：
    在所述用户设备的签约信息满足所述多个群组标识的逻辑关系的情况下，所述策略控制网元确定所述用户设备与所述组信息匹配。
  25. 根据权利要求22至24中任一项所述的方法，其特征在于，所述方法还包括：
    所述策略控制网元接收来自统一数据存储网元或者会话管理网元的所述用户设备的签约信息。
  26. 一种配置策略的装置，其特征在于，所述装置包括：用于执行如权利要求1至9中任一项所述的方法的模块，或者用于执行如权利要求10至14中任一项所述的方法的模块，或者用于执行如权利要求15至18中任一项所述的方法的模块，或者用于执行如权利要求19至20中任一项所述的方法的模块，或者用于执行如权利要求21至25中任一项所述的方法的模块。
  27. 一种配置策略的装置，其特征在于，包括：
    处理器，用于执行存储器中存储的计算机程序，以使得所述装置执行如权利要求1至9中任一项所述的方法，或者以使得所述装置执行如权利要求10至14中任一项所述的方法，或者以使得所述装置执行如权利要求15至18中任一项所述的方法，或者以使得所述装置执行如权利要求19至20中任一项所述的方法，或者以使得所述装置执行如权利要求21至25中任一项所述的方法。
  28. 一种计算机程序产品，其特征在于，所述计算机程序产品包括用于执行如权利要求1至9中任一项所述的方法的指令，或者，所述计算机程序产品包括用于执行如权利要求10至14中任一项所述的方法的指令，或者，所述计算机程序产品包括用于执行如权利要求15至18中任一项所述的方法的指令，或者，所述计算机程序产品包括用于执行如权利要求19至20中任一项所述的方法的指令，或者，所述计算机程序产品包括用于执行如权利要求21至25中任一项所述的方法的指令。
  29. 一种计算机可读存储介质，其特征在于，包括：所述计算机可读存储介质存储有计算机程序；所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求1至9中任一项所述的方法，或者使得所述计算机执行如权利要求10至14中任一项所述的方法，或者以使得所述计算机执行如权利要求15至18中任一项所述的方法，或者以使得所述计算机执行如权利要求19至20中任一项所述的方法，或者以使得所述计算机执行如权利要求21至25中任一项所述的方法的指令。
  30. 一种配置策略的方法，其特征在于，包括：
    应用功能网元向策略控制网元发送业务流路由控制信息以及与所述业务流路由控制信息对应的第一服务类型信息，所述第一服务类型信息包括第一服务类别信息和/或第一签约者类别信息；
    所述策略控制网元接收来自所述应用功能网元的所述业务流路由控制信息以及所述第一服务类型信息；
    所述策略控制网元根据所述业务流路由控制信息为所述第一服务类型信息对应的用户设备生成策略与计费控制规则；
    所述策略控制网元发送所述策略与计费控制规则。
  31. 一种配置策略的方法，其特征在于，包括：
    统一数据存储网元接收业务流路由控制信息以及与所述业务流路由控制信息对应的用户设备组的标识信息；
    所述统一数据存储网元根据所述用户设备组的标识信息确定与所述用户设备组的标 识信息对应的签约用户的标识信息；
    所述统一数据存储网元向策略控制网元发送所述业务流路由控制信息和所述签约用户的标识信息；
    所述策略控制网元接收来自所述统一数据存储网元的所述业务流路由控制信息以及所述签约用户的标识信息；
    所述策略控制网元根据所述业务流路由控制信息为所述签约用户生成策略与计费控制规则；
    所述策略控制网元发送所述策略与计费控制规则。
  32. 一种配置策略的方法，其特征在于，包括：
    应用功能网元向网络开放功能网元发送业务流路由控制信息，以及与所述业务流路由控制信息对应的第一组信息；
    所述网络开放功能网元接收来自所述应用功能网元的所述业务流路由控制信息以及所述第一组信息；
    所述网络开放功能网元向统一数据存储网元发送所述业务流路由控制信息，以及与所述业务流路由控制信息对应的第二组信息，所述第二组信息是根据所述第一组信息得到的；
    所述统一数据存储网元接收来自所述网络开放功能网元的所述业务流路由控制信息和所述第二组信息；
    所述统一数据存储网元向策略控制网元发送业务流路由控制信息和第二组信息；
    所述策略控制网元接收来自所述统一数据存储网元的所述业务流路由控制信息以及所述第二组信息，所述第二组信息包括多个组标识；
    所述策略控制网元根据所述业务流路由控制信息为与所述第二组信息匹配的用户设备生成策略与计费控制规则；
    所述策略控制网元发送所述策略与计费控制规则。
PCT/CN2023/071344 2022-01-14 2023-01-09 配置策略的方法和装置 WO2023134630A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202210044585 2022-01-14
CN202210044585.1 2022-01-14
CN202210239496.2A CN116489609A (zh) 2022-01-14 2022-03-11 配置策略的方法和装置
CN202210239496.2 2022-03-11

Publications (1)

Publication Number Publication Date
WO2023134630A1 true WO2023134630A1 (zh) 2023-07-20

Family

ID=87220097

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/071344 WO2023134630A1 (zh) 2022-01-14 2023-01-09 配置策略的方法和装置

Country Status (2)

Country Link
CN (1) CN116489609A (zh)
WO (1) WO2023134630A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103490908A (zh) * 2012-06-12 2014-01-01 中兴通讯股份有限公司 策略和计费规则功能的选择方法、装置及系统
CN112311691A (zh) * 2019-07-26 2021-02-02 华为技术有限公司 策略控制方法、设备及系统
CN112314032A (zh) * 2018-06-22 2021-02-02 华为技术有限公司 通过使多个策略以信息元素为条件优化用户设备操作
WO2021046794A1 (en) * 2019-09-12 2021-03-18 Zte Corporation A method for influencing data traffic routing in core networks by service applications
CN113518319A (zh) * 2020-04-09 2021-10-19 华为技术有限公司 一种临近服务的业务处理方法、设备及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103490908A (zh) * 2012-06-12 2014-01-01 中兴通讯股份有限公司 策略和计费规则功能的选择方法、装置及系统
CN112314032A (zh) * 2018-06-22 2021-02-02 华为技术有限公司 通过使多个策略以信息元素为条件优化用户设备操作
CN112311691A (zh) * 2019-07-26 2021-02-02 华为技术有限公司 策略控制方法、设备及系统
WO2021046794A1 (en) * 2019-09-12 2021-03-18 Zte Corporation A method for influencing data traffic routing in core networks by service applications
CN113518319A (zh) * 2020-04-09 2021-10-19 华为技术有限公司 一种临近服务的业务处理方法、设备及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NOKIA, NOKIA SHANGHAI BELL: "Correcting AMF behaviour for Service Request that is not integrity protected", 3GPP DRAFT; S2-1903668, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, 2 April 2019 (2019-04-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 376, XP051719814 *

Also Published As

Publication number Publication date
CN116489609A (zh) 2023-07-25

Similar Documents

Publication Publication Date Title
CN111010744B (zh) 建立会话的方法和装置以及发送报文的方法和装置
WO2023284584A1 (zh) 通信方法和装置
WO2023280121A1 (zh) 一种获取边缘服务的方法和装置
WO2023011210A1 (zh) 一种获取边缘服务的方法和装置
WO2020253701A1 (zh) 管理背景数据传输策略的方法、装置和系统
CN113994633B (zh) 通信系统中的网络功能集合的授权
KR20210055546A (ko) 무선 통신 시스템에서 mbs 서비스 제공에 대한 mbs 서비스 세션의 설정을 위한 장치 및 방법
WO2022159725A1 (en) Federated identity management in fifth generation (5g) system
US11622025B2 (en) Techniques in retrieving cached content using information centric networking for protocol data unit sessions
CN115004635A (zh) 签约信息获取方法及装置
CN116723507B (zh) 针对边缘网络的终端安全方法及装置
EP4207828A1 (en) Data communication method and communication apparatus
WO2022222745A1 (zh) 一种通信方法及装置
WO2023134630A1 (zh) 配置策略的方法和装置
US20220141704A1 (en) Systems and methods for obtaining and indicating subscription information for a wireless communication service
KR20230137998A (ko) Af 세션에 대한 외부 매개변수 프로비저닝을 위한 새로운 방법
WO2020200297A1 (zh) 选择会话管理网元的方法和装置
CN116458138A (zh) 网络节点及通信方法
WO2023116560A1 (zh) 通信的方法与装置
WO2024051313A1 (zh) 通信资源管理方法、装置、系统及存储介质
WO2023143212A1 (zh) 一种通信方法及装置
WO2023005714A1 (zh) 一种无线通信方法和装置
WO2023231450A1 (zh) 一种时间同步方法及通信装置
WO2023051631A1 (zh) 数据调用的方法和装置
WO2023040958A1 (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: 23739972

Country of ref document: EP

Kind code of ref document: A1