WO2021012750A1 - 一种通信方法及装置 - Google Patents

一种通信方法及装置 Download PDF

Info

Publication number
WO2021012750A1
WO2021012750A1 PCT/CN2020/089808 CN2020089808W WO2021012750A1 WO 2021012750 A1 WO2021012750 A1 WO 2021012750A1 CN 2020089808 W CN2020089808 W CN 2020089808W WO 2021012750 A1 WO2021012750 A1 WO 2021012750A1
Authority
WO
WIPO (PCT)
Prior art keywords
service package
entity
package
identifier
communication
Prior art date
Application number
PCT/CN2020/089808
Other languages
English (en)
French (fr)
Inventor
胡翔
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP20844902.5A priority Critical patent/EP3975593A4/en
Priority to JP2022504060A priority patent/JP7346706B2/ja
Publication of WO2021012750A1 publication Critical patent/WO2021012750A1/zh
Priority to US17/581,123 priority patent/US20220150139A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/02—Capturing of monitoring data
    • H04L43/022—Capturing of monitoring data by sampling
    • 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
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/06—Generation of reports
    • H04L43/062—Generation of reports related to network traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/58—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on statistics of usage or network monitoring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/61—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on the service used
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80—Rating or billing plans; Tariff determination aspects
    • H04M15/8027—Rating or billing plans; Tariff determination aspects based on network load situation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/82—Criteria or parameters used for performing billing operations
    • H04M15/8214—Data or packet based
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]

Definitions

  • This application relates to the field of communication technology, and in particular to a communication method and device.
  • FIG. 1 is a schematic diagram of a 4G (fourth generation mobile communication system) network architecture.
  • the core network of the 4G network includes a policy and charging rules function (PCRF) entity and a packet data network gateway (PGW).
  • PCRF policy and charging rules function
  • PGW packet data network gateway
  • PCC rules are a set of information used to implement service data flow detection and provide corresponding policy control and/or charging control parameters.
  • the PGW can be used to detect the service flow and execute the PCC rules issued by the PCRF entity.
  • the core network of the 4G network may also include a service detection function (traffic detection function, TDF) entity.
  • TDF service detection function
  • the TDF entity is connected to the PCRF entity and the PGW respectively.
  • the TDF entity is mainly used to perform application detection and report the detected application information to the PCRF entity.
  • the serving gateway (SGW), PGW, and TDF entities are respectively divided into serving gateway control plane function (SGW-C) entities , PDN gateway control plane function (PDN gateway control plane function, PGW-C) entity, service detection function control plane (traffic detection function control plane, TDF-C) entity, serving gateway user plane function (serving gateway user plane function, SGW) -U) entity, PDN gateway user plane function (PDN gateway user plane function, PGW-U) entity, service detection function user plane (traffic detection function user plane, TDF-U) entity.
  • SGW serving gateway control plane function
  • TDF-C service detection function control plane
  • Figure 2 is a schematic diagram of the separation of the core network control plane and the user plane in the 4G network.
  • the control plane functional entity is used to manage the user plane functional entity or implement other non-session-level management functions.
  • the user plane functional entity is used to provide services for the control plane functional entity.
  • the user plane functional entity can establish a session bearer according to a control instruction issued by the control plane to complete the forwarding of user data.
  • the PGW-U entity can execute the PCC rules issued by the PCRF entity.
  • the 5G (fifth generation mobile communication system) network architecture has re-adjusted the network architecture of the next-generation core network equipment.
  • Figure 3 shows the system architecture of a 5G network based on a service-oriented interface.
  • the policy control function (PCF) entity is used to issue PCC rules for the user according to the user's contract package information, used service information, etc.
  • the session management function (SMF) entity is used to manage the user plane function (UPF) entity.
  • the SMF entity needs to be responsible for managing the selection of the UPF entity.
  • the SMF entity also has non-session-level management functions such as policy issuance, event reporting, UPF entity heartbeat checking, and UPF entity load reporting.
  • the UPF entity is used to provide services for the SMF entity.
  • the UPF can establish a session bearer according to a control instruction issued by the SMF to complete the forwarding of user data.
  • the UPF entity can also implement PCC regulations issued by the PCF entity.
  • the PCF entity/PCRF entity can issue the PCC rules to the network elements such as the PGW, PGW-C entity or SMF entity according to the user's service package to activate the PCC rules.
  • the PGW, PGW-U entity, or UPF entity performs PCC rule matching on the user's service data flow based on the PCC rule activated by the user, and executes the charging and control policies carried by the successfully matched PCC rule.
  • devices under the PCF entity/PCRF entity (such as the PGW, PGW-U entity, or UPF entity, etc.) cannot determine the service package to which the received data message belongs, and thus cannot perform further related operations based on the service package. Therefore, how to enable these devices to accurately determine the service package to which the received data message belongs is a problem to be solved urgently at present.
  • the embodiments of the present application provide a communication method and device, which are beneficial for the device to accurately determine the service package to which the received data message belongs.
  • an embodiment of the present application provides a communication method.
  • the method includes: a first device obtains a service package subscribed by a user; the first device determines the policy and charging control PCC rule corresponding to the service package; The second device sends the identifier of the service package and the PCC rule corresponding to the service package. Based on the method described in the first aspect, it is beneficial for the device under the first device to accurately determine the service package to which the received data message belongs.
  • the first device receives the data analysis result corresponding to the target service package from the data analysis device; the first device performs traffic stimulation or traffic suppression on the target service package according to the data analysis result corresponding to the target service package. Based on this optional implementation manner, the traffic of the target service package can be flexibly controlled according to the data analysis result corresponding to the target service package.
  • the first device is a policy control function PCF entity, and the second device is a session management function SMF entity; or, the first device is a policy and charging rules function PCRF entity, and the second device is a packet data Gateway control plane PGW-C entity; or, the first device is a PCRF entity, and the second device is a service detection function control plane TDF-C entity; or, the first device is a PCRF entity, and the second device is a packet data gateway PGW; or , The first device is a PCRF entity, and the second device is a service detection function TDF entity.
  • the first device is a PCF entity
  • the second device is an SMF entity
  • the service package identifier is carried in the information element of the corresponding PCC rule and sent to the second device
  • the first device only sends An identifier of a service package
  • the identifier of the service package is carried in the cell of the session rule and sent to the second device.
  • the first device is a PCRF entity, and the second device is a PGW-C entity; or, the first device is a PCRF entity, and the second device is a TDF-C entity; or, the first device is a PCRF Entity, the second device is a PGW; or, the first device is a PCRF entity, and the second device is a TDF entity;
  • the service package identifier is carried in the cell of the Charging-Rule-Install message and sent to the second device;
  • the first device only sends the identifier of one service package, and the identifier of the service package is carried in the cell of the credit control response CCA message or the re-authentication request RAR message and sent to the second device.
  • an embodiment of the present application provides a communication method.
  • the method includes: a second device receives from the first device an identifier of a service package and a policy and charging control PCC rule corresponding to the service package; The corresponding PCC rule is converted into the packet detection rule PDR; the second device sends the identifier of the service package and the PDR corresponding to the service package to the third device. Based on the method described in the second aspect, it is helpful for the device under the first device to accurately determine the service package to which the received data message belongs.
  • the second device receives the data analysis result corresponding to the target service package from the data analysis device; the second device performs traffic stimulation or traffic suppression on the target service package according to the data analysis result corresponding to the target service package. Based on this optional implementation manner, the traffic of the target service package can be flexibly controlled according to the data analysis result corresponding to the target service package.
  • the first device is a policy control function PCF entity
  • the second device is a session management function SMF entity
  • the third device is a user plane function UPF entity
  • the first device is a policy and charging rule Functional PCRF entity
  • the second device is a packet data gateway control plane PGW-C entity
  • the third device is a packet data gateway user plane PGW-U entity
  • the first device is a PCRF entity
  • the second device is a service detection function control plane TDF-C entity
  • the third device is a user plane TDF-U entity with a service detection function.
  • the first device is a PCF entity
  • the second device is an SMF entity
  • the third device is a UPF entity
  • the service package identifier is carried in the information element of the corresponding PCC rule and sent to the second device
  • the first device only sends the identifier of one service package
  • the identifier of the service package is carried in the cell of the session rule and sent to the second device.
  • the SMF entity can accurately determine the correspondence between the service package and the PCC rule.
  • the first device is a PCRF entity
  • the second device is a PGW-C entity
  • the third device is a PGW-U entity
  • the service package identifier is carried in the cell of the Charging-Rule-Install message and sent to the second device; or when the first device only sends the identifier of one service package , The service package identifier is carried in the cell of the credit control response CCA message or the re-authentication request RAR message and sent to the second device.
  • the second device can accurately determine the correspondence between the service package and the PCC rule.
  • the service package identifier is carried in the information element of the PDR corresponding to the service package and sent to the third device; or, when the second device only sends the identifier of one service package, the service package identifier The information element carried in the session establishment request is sent to the third device. Based on this optional implementation manner, it is beneficial for the third device to accurately determine the correspondence between the service package and the PDR.
  • an embodiment of the present application provides a communication method.
  • the method includes: a third device receives an identifier of a service package from a second device and a packet detection rule PDR corresponding to the service package; and the third device records the service package and the PDR
  • the third device receives the data message; the third device determines the target message detection rule PDR that matches the data message; the third device obtains the target corresponding to the target PDR according to the recorded correspondence between the service package and the PDR Business package. Based on the method described in the third aspect, the third device can accurately determine the service package to which the received data message belongs.
  • the third device performs data statistics based on the target service package according to the data message, and obtains the data statistics result corresponding to the target service package. Based on this optional implementation manner, the third device can perform data statistics based on the target service package.
  • the third device sends the data statistics result corresponding to the target service package to the data analysis device.
  • the third device receives the data analysis result corresponding to the target service package from the data analysis device; the third device performs traffic stimulation or traffic suppression on the target service package according to the data analysis result corresponding to the target service package. Based on this optional implementation manner, the traffic of the target service package can be flexibly controlled according to the data analysis result corresponding to the target service package.
  • the second device is a session management function SMF entity, and the third device is a user plane function UPF entity; or, the second device is a packet data gateway control plane PGW-C entity, and the third device is a packet Data gateway user plane PGW-U entity; or, the second device is a service detection function control plane TDF-C entity, and the third device is a service detection function user plane TDF-U entity.
  • the service package identifier is carried in the information element of the PDR corresponding to the service package and sent to the third device, or when the second device only sends the identifier of one service package, the service package identifier carries It is sent to the third device in the cell of the session establishment request. Based on this optional implementation manner, the third device can accurately determine the correspondence between the service package and the PDR.
  • an embodiment of the present application provides a communication method.
  • the method includes: a second device receives an identifier of a service package and a PCC rule corresponding to the service package from a first device; the second device records the correspondence between the service package and the PCC rule Relationship; the second device receives the data message; the second device determines the target PCC rule matching the data message; the second device obtains the target business package corresponding to the target PCC rule according to the recorded correspondence between the PCC rule and the business package. Based on the method described in the fourth aspect, the second device can accurately determine the service package to which the received data message belongs.
  • the second device performs data statistics based on the target service package according to the data message, and obtains the data statistics result.
  • the third device can perform data statistics based on the target service package.
  • the second device sends the data statistics result corresponding to the target service package to the data analysis device.
  • the second device receives the data analysis result of the target service package from the data analysis device; the second device performs traffic excitation or traffic suppression on the target service package according to the data analysis result corresponding to the target service package. Based on this optional implementation manner, the traffic of the target service package can be flexibly controlled according to the data analysis result corresponding to the target service package.
  • the first device is a policy and charging rules function PCRF entity
  • the second device is a packet data gateway PGW; or, the first device is a PCRF, and the second device is a service detection function TDF entity; or , The first device is a PGW, and the second device is a TDF entity.
  • the first device is a PCRF entity, and the second device is a PGW; or, the first device is a PCRF, and the second device is a TDF entity; the identifier of the service package is carried in the charging rules and the Charging-Rule is installed -The cell of the Install message is sent to the second device; or, the first device only sends the identifier of one service package, and the identifier of the service package is carried in the cell of the credit control response CCA message or the re-authentication request RAR message and sent to The second device.
  • the second device can accurately determine the correspondence between the service package and the PCC rule.
  • an embodiment of the present application provides a communication method, which includes: a data analysis device receives a data statistics result corresponding to a target service package; the data analysis device analyzes the data statistics result to obtain a data analysis corresponding to the target service package Result: The data analysis device sends the data analysis result corresponding to the target service package. Based on this optional implementation manner, it is possible to perform data analysis on the data statistics result corresponding to the target service package.
  • a communication device may be a first device or a device for the first device.
  • the device used in the first device may be a chip in the first device.
  • the communication device can perform the method described in any one of the foregoing first aspect and optional implementation manners of the first aspect.
  • the functions of the communication device can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more units corresponding to the above-mentioned functions.
  • the unit can be software and/or hardware.
  • a communication device may be a second device or a device used for the second device.
  • the device used for the second device may be a chip in the second device.
  • the communication device can execute the method described in any one of the foregoing second aspect, fourth aspect, optional implementation manner of the first aspect, and optional implementation manner of the fourth aspect.
  • the functions of the communication device can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more units corresponding to the above-mentioned functions.
  • the unit can be software and/or hardware.
  • a communication device may be a third device or a device for the third device.
  • the device used for the third device may be a chip in the third device.
  • the communication device can execute the method described in any one of the foregoing third aspect and optional implementation manners of the third aspect.
  • the functions of the communication device can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more units corresponding to the above-mentioned functions.
  • the unit can be software and/or hardware.
  • a communication device may be a data analysis device or a device used for a data analysis device.
  • the device used in the data analysis device may be a chip in the data analysis device.
  • the communication device can execute the method described in any one of the foregoing fifth aspect and optional implementation manners of the fifth aspect.
  • the functions of the communication device can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more units corresponding to the above-mentioned functions.
  • the unit can be software and/or hardware.
  • a communication device may be a first device or a device for the first device.
  • the device used in the first device may be a chip in the first device.
  • the communication device includes a processor and a transceiver. Among them, the processor is connected to the transceiver.
  • the communication device further includes a memory. The processor is connected to the memory.
  • the transceiver when the communication device is the first device, the transceiver may include an antenna and a radio frequency circuit connected to the antenna. The transceiver is used to implement communication between the communication device and other network elements.
  • the transceiver when the communication device is a device used in the first device, the transceiver may be an interface circuit, and the interface circuit is used by the processor to obtain or output information or data.
  • the interface circuit is used for the processor to read data from the memory or write data.
  • the interface circuit is used for the processor to receive information or data from outside the device or send information or data to the outside of the device.
  • the processor is configured to execute the method of any one of the foregoing first aspect and optional implementation manners of the first aspect.
  • the memory is used to store a program
  • the processor calls the program stored in the memory to execute the method of any one of the foregoing first aspect and the optional implementation manner of the first aspect.
  • the processor calls the program stored in the memory to execute the method of any one of the foregoing first aspect and the optional implementation manner of the first aspect.
  • a communication device may be a second device or a device for the second device.
  • the device used for the second device may be a chip in the second device.
  • the communication device includes a processor and a transceiver. Among them, the processor is connected to the transceiver.
  • the communication device further includes a memory. The processor is connected to the memory.
  • the transceiver when the communication device is the second device, the transceiver may include an antenna and a radio frequency circuit connected to the antenna. The transceiver is used to implement communication between the communication device and other network elements.
  • the transceiver when the communication device is a device used for the second device, the transceiver may be an interface circuit, and the interface circuit is used for the processor to obtain or output information or data.
  • the interface circuit is used for the processor to read data from the memory or write data.
  • the interface circuit is used for the processor to receive information or data from outside the device or send information or data to the outside of the device.
  • the processor is configured to execute the method of any one of the foregoing second aspect, fourth aspect, optional implementation manner of the second aspect, and optional implementation manner of the fourth aspect.
  • the memory is used to store a program
  • the processor calls the program stored in the memory to execute the above-mentioned second aspect, fourth aspect, optional implementation manner of the second aspect and optional implementation manner of the fourth aspect Any one of the methods.
  • operations and beneficial effects performed by the processor refer to the method described in any one of the above-mentioned second aspect, fourth aspect, optional implementation manner of the second aspect, and optional implementation manner of the fourth aspect, and beneficial effects. The effect is not repeated here.
  • a communication device may be a third device or a device for the third device.
  • the device used for the third device may be a chip in the third device.
  • the communication device includes a processor and a transceiver. Among them, the processor is connected to the transceiver.
  • the communication device further includes a memory. The processor is connected to the memory.
  • the transceiver when the communication device is a third device, may include an antenna and a radio frequency circuit connected to the antenna. The transceiver is used to implement communication between the communication device and other network elements.
  • the transceiver may be an interface circuit, and the interface circuit is used by the processor to obtain or output information or data.
  • the interface circuit is used for the processor to read data from the memory or write data.
  • the interface circuit is used for the processor to receive information or data from outside the device or send information or data to the outside of the device.
  • the processor is configured to execute the method of any one of the foregoing third aspect and optional implementation manners of the third aspect.
  • the memory is used to store a program
  • the processor calls the program stored in the memory to execute the method of any one of the foregoing third aspect and optional implementation manners of the third aspect.
  • the operations and beneficial effects performed by the processor reference may be made to the method and beneficial effects described in any one of the foregoing third aspect and the optional implementation manners of the third aspect, and repetitions are not repeated here.
  • a communication device may be a data analysis device or a device for data analysis equipment.
  • the device used in the data analysis device may be a chip in the data analysis device.
  • the communication device includes a processor and a transceiver. Among them, the processor is connected to the transceiver.
  • the communication device further includes a memory. The processor is connected to the memory.
  • the transceiver when the communication device is a data analysis device, the transceiver may include an antenna and a radio frequency circuit connected to the antenna. The transceiver is used to implement communication between the communication device and other network elements.
  • the transceiver when the communication device is a device used in a data analysis device, the transceiver may be an interface circuit, and the interface circuit is used by the processor to obtain or output information or data.
  • the interface circuit is used for the processor to read data from the memory or write data.
  • the interface circuit is used for the processor to receive information or data from outside the device or send information or data to the outside of the device.
  • the processor is configured to execute the method of any one of the foregoing fifth aspect and optional implementation manners of the fifth aspect.
  • the memory is used to store a program
  • the processor calls the program stored in the memory to execute the method of any one of the foregoing fifth aspect and the optional implementation manner of the fifth aspect.
  • the operations and beneficial effects performed by the processor reference may be made to the method and beneficial effects described in any one of the fifth aspect and the optional implementation manners of the fifth aspect, and the repetition is not repeated here.
  • the fourteenth aspect provides a computer program product that, when it runs on a computer, enables the computer to execute the above-mentioned first, second, third, fourth, fifth, and first aspects.
  • the method of any one of the optional implementation manner, the optional implementation manner of the second aspect, the optional implementation manner of the third aspect, the optional implementation manner of the fourth aspect, and the optional implementation manner of the fifth aspect is not limited to any one of the optional implementation manner, the optional implementation manner of the second aspect, the optional implementation manner of the third aspect, the optional implementation manner of the fourth aspect, and the optional implementation manner of the fifth aspect .
  • a computer-readable storage medium stores instructions that, when run on a computer, cause the computer to execute the first, second, and third aspects above.
  • Figure 1 is a schematic diagram of an existing 4G grid system architecture
  • Figure 2 is a schematic diagram of an existing system architecture in which the control plane of the core network is separated from the user plane;
  • Figure 3 is a schematic diagram of an existing system architecture of a 5G network based on a service-oriented interface
  • FIG. 4 is a schematic diagram of a communication system provided by an embodiment of the present application.
  • FIG. 5 is a schematic diagram of another communication system provided by an embodiment of the present application.
  • FIG. 16 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 17 is a schematic structural diagram of another communication device provided by an embodiment of the present application.
  • the embodiments of the present application provide a communication method and device, which enable a core network device to determine the service package to which a received data message belongs.
  • Fig. 4 is a schematic diagram of a communication system provided by an embodiment of the present application.
  • the communication system includes a first device, a second device, a third device, and a data analysis device.
  • the first device and the second device are connected wirelessly.
  • the second device and the third device are connected wirelessly.
  • the data analysis device and the third device are connected wirelessly.
  • the data analysis device may also be connected to the first device and/or the second device in a wireless manner.
  • Fig. 4 is only a schematic diagram of a communication system provided by the implementation of this application.
  • Fig. 4 takes the communication system including the first device, the second device, the third device and the data analysis device as an example.
  • the communication system may also include other devices, which are not limited in the embodiment of the present application.
  • the data analysis device may be a network data analysis function (NWDAF) entity or a reporting system for generating reports or other devices that can perform data analysis.
  • NWAF network data analysis function
  • the first device is used to generate and issue a policy and charging control (policy and charging control, PCC) rule.
  • the second device is the control plane device.
  • the third device is a user plane device used to execute the PCC rules issued by the first device.
  • the communication system shown in Figure 4 is applied to a scenario where the control plane is separated from the user plane.
  • the communication system shown in Figure 4 can be applied to any of the following application scenarios 1 to 3:
  • the first device is a policy control function (PCF) entity
  • the second device is a session management function (SMF) entity
  • the third device is a user plane function (UPF) entity.
  • the PCF entity is used to issue a policy and charging control (PCC) rule to the user according to the user's contract package information, used service information, etc.
  • PCC policy and charging control
  • the UPF entity is used to execute the PCC rules issued by the PCF entity.
  • the communication system may also include a network slice selection function (NSSF) entity, a network capability exposure function (NEF) entity, and a network function warehouse (NEF) in Figure 3 repository function (NRF) entity, unified data management (UDM) entity, application function (AF) entity, authentication server function (authentication server function, AUSF), access and mobility management function entity (access and mobility management function, AMF), user terminal equipment (user equipment, UE), radio access network (RAN) and data network (data network, DN), etc.
  • NSF network slice selection function
  • NEF network capability exposure function
  • NEF network function warehouse
  • UDM unified data management
  • AF application function
  • authentication server function authentication server function
  • AUSF authentication server function
  • AMF access and mobility management function entity
  • user terminal equipment user equipment
  • RAN radio access network
  • DN data network
  • the first device is a policy and charging rules function (PCRF) entity
  • the second device is a PDN gateway control plane function (PGW-C) entity
  • the third device is a PDN gateway control plane function (PGW-C) entity
  • PGW-U PDN gateway user plane function
  • the PCRF entity is used to issue a policy and charging control (PCC) rule for the user according to the user's subscription package information, used service information, etc.
  • PGW-U entity is used to execute the PCC rules issued by the PCRF entity.
  • the communication system may also include the serving gateway control plane function (SGW-C) entity and the serving gateway user plane function (serving gateway user plane function, SGW-C) in Figure 2 U) Entity, traffic detection function control plane (TDF-C) entity and traffic detection function user plane (TDF-U) entity, etc.
  • SGW-C serving gateway control plane function
  • SGW-C serving gateway user plane function
  • TDF-C traffic detection function control plane
  • TDF-U traffic detection function user plane
  • the first device is a PCRF entity
  • the second device is a TDF-C entity
  • the third device is a TDF-U entity.
  • the PCRF entity is used to issue a policy and charging control (PCC) rule for the user according to the user's subscription package information, used service information, etc.
  • PCC policy and charging control
  • the TDF-U entity is used to execute the PCC rules issued by the PCRF entity.
  • the communication system may also include the SGW-C entity, SGW-U entity, PGW-C entity, and PGW-U entity in FIG. 2.
  • Fig. 5 is a schematic diagram of another communication system provided by an embodiment of the present application.
  • the communication system includes a first device, a second device and a data analysis device.
  • the first device and the second device are connected wirelessly.
  • the data analysis device and the second device are connected wirelessly.
  • the data analysis device may also be connected to the first device in a wireless manner.
  • FIG. 5 is only a schematic diagram of a communication system provided by the implementation of this application.
  • FIG. 5 takes the communication system including the first device, the second device, and the data analysis device as an example.
  • the communication system may also include other devices, which are not limited in the embodiment of the present application.
  • the data analysis device may be a network data analysis function (NWDAF) entity or a reporting system for generating reports or other devices that can perform data analysis.
  • NWAF network data analysis function
  • the communication system shown in FIG. 5 is applied to a scenario where the control plane and the user plane are not separated.
  • the communication system shown in FIG. 5 can be applied to any of the following application scenarios 4 and 5:
  • Application scenario 4 The first device is a PCRF entity, and the second device is a PGW.
  • the communication system shown in FIG. 5 may further include devices other than the PCRF entity and PGW in FIG. 1.
  • Application scenario 5 The first device is a PCRF entity, and the second device is a TDF entity.
  • the communication system shown in FIG. 5 may further include devices other than the PCRF entity in FIG. 1.
  • connection appearing in the embodiments of this application refers to various connection modes such as direct connection or indirect connection to realize communication between devices, which is not limited in the embodiments of this application.
  • FIG. 6 is a schematic flowchart of a communication method provided by an embodiment of the present application.
  • the execution subject of step 601 to step 603 is the first device or the chip in the first device.
  • the execution subject of step 604 and step 605 is the second device or the chip in the second device.
  • the execution subject of steps 606 to 609 is the third device or the chip in the third device.
  • the following uses the first device, the second device, and the third device as the execution subject of the method as an example for description.
  • the communication method includes the following steps 601 to 609, where:
  • the first device obtains the service package signed by the user.
  • the communication method shown in FIG. 6 can be applied to any one of the application scenarios 1 to 3 above. That is, the first device in FIG. 6 may be a PCF entity, the second device may be an SMF entity, and the third device may be a UPF entity. Alternatively, the first device may be a PCRF entity, the second device may be a PGW-C entity, and the third device may be a PGW-U entity. Alternatively, the first device may be a PCRF entity, the second device may be a TDF-C entity, and the third device may be a TDF-U entity. Of course, the first device may also be another entity for issuing PCC rules. The second device can also be other control plane devices. The third device may also be another user plane device, which is not limited in the embodiment of the present application.
  • the service package signed by the user is recorded in the first device.
  • Each user can sign up for one or more business packages.
  • the first device may obtain one or more service packages from the service packages that the user has signed according to the user's current attributes or status. For example, the user has signed up for 3 business packages.
  • Business package 1 is 20 yuan a month, 20G general traffic.
  • Business package 2 is 20 yuan a month, 30G application 1 traffic, 20G application 2 traffic.
  • Business package 3 is 10 yuan a month, 10G application 3 traffic, 10G application 4 traffic.
  • the first device obtains one service package, or obtains two service packages, or obtains three service packages from the three service packages according to the current attributes or status of the user.
  • the first device determines a policy and charging control (PCC) rule corresponding to the service package.
  • PCC policy and charging control
  • PCC rules are a set of information used to implement service data flow detection and provide corresponding policy control and/or charging control parameters.
  • PCC rules include service data flow detection information, and include policy control information and/or charging related information.
  • the service data flow detection information may include a service data flow template.
  • the service data flow detection information is used to match data packets.
  • the policy control information is used to perform policy control on the data packets matching the service data flow detection information.
  • the charging-related information is used to charge the data packets matching the service data flow detection information.
  • the PCC rule may be a dynamic PCC rule or a predefined PCC rule (charging rule name, CRN) or a PCC rule group (charging rule basename, CRBN).
  • the dynamic PCC rule is a rule issued by the first device to the third device.
  • the predefined PCC rules are pre-configured on the third device, and these rules can be referenced by the first device.
  • a PCC rule group can include multiple PCC rules.
  • the PCC rule group is pre-configured on the third device, and the PCC rule group can be referenced by the first device.
  • a business package can correspond to one or more PCC rules.
  • One PCC rule can also correspond to one or more business packages.
  • Table 1 the correspondence between the service package stored in the first device and the PCC rule is shown in Table 1 below.
  • Business package 1 corresponds to dynamic PCC rule 1
  • business package 2 corresponds to dynamic PCC rule 2 and predefined PCC rule 2
  • business package 3 corresponds to dynamic PCC rule 3, predefined PCC rule 3, and PCC rule group 3.
  • the first device determines the PCC rule corresponding to the obtained service package according to the correspondence between the pre-stored service package and the PCC rule. For example, if the first device obtains service package 1, the first device determines that the PCC rule corresponding to service package 1 is dynamic PCC rule 1. The first device sends the identifier of the service package 1 and the dynamic PCC rule 1 to the second device.
  • the first device determines that the PCC rule corresponding to business package 1 is dynamic PCC rule 1, and determines that the PCC rule corresponding to business package 2 is dynamic PCC rule 2 and predefined PCC rule 2.
  • the first device sends the identifier of the service package 1 and the dynamic PCC rule 1 corresponding to the service package 1, and the identifier of the service package 2 and the dynamic PCC rule 2 and the predefined PCC rule 2 corresponding to the service package 2 to the second device.
  • the first device determines that the PCC rule corresponding to business package 1 is dynamic PCC rule 1, and determines that the PCC rule corresponding to business package 2 is dynamic PCC rule 2 and pre-defined PCC rule 2, and determine the PCC rule corresponding to business package 3 as dynamic PCC rule 3, pre-defined PCC rule 3 and PCC rule group 3.
  • the first device sends to the second device the identifier of service package 1 and the dynamic PCC rule 1 corresponding to service package 1, and the identifier of service package 2 and the dynamic PCC rule 2 and predefined PCC rule 2 corresponding to service package 2, and The identifier of the service package 3 and the dynamic PCC rule 3, the predefined PCC rule 3, and the PCC rule group 3 corresponding to the service package 3.
  • the first device sends the identifier of the service package and the PCC rule corresponding to the service package to the second device.
  • the first device after obtaining the service package signed by the user and the PCC rule corresponding to the service package, the first device sends the identifier of the service package and the PCC rule corresponding to the service package to the second device.
  • the purpose of the first device sending the PCC rule corresponding to the service package to the second device is to activate the PCC rule corresponding to the service package.
  • the identifier of the service package may be the name or ID (Identity document) of the service package.
  • the second device converts the PCC rule corresponding to the service package into a packet detection rule (PDR).
  • PDR packet detection rule
  • the second device converts the PCC rule corresponding to the service package into PDR.
  • the second device may also store the correspondence between the identifier of the service package and the PCC rule.
  • the PDR may include one or more packet detection information (PDI), one or more PDR identifiers, and an identifier of a processing rule corresponding to each PDR identifier.
  • the processing rule includes at least one of a forwarding action rule (forwarding action rule, FAR), a usage reporting rule (URR), and a QoS enforcement rule (QoS enforcement rule, QER).
  • the second device sends the identifier of the service package and the PDR corresponding to the service package to the third device.
  • the second device converts the PCC rule corresponding to the service package to the PDR, it sends the identifier of the service package and the PDR corresponding to the service package to the third device.
  • business package 1 corresponds to dynamic PCC rule 1.
  • the second device After receiving the identifier of the service package 1 and the dynamic PCC rule 1, the second device converts the dynamic PCC rule 1 into a PDR, and sends the identifier of the service package 1 and the PDR to the third device.
  • the third device After receiving the identifier of the service package 1 and the PDR, the third device records the correspondence between the service package 1 and the PDR.
  • the service package identifier is carried in the information element of the PDR corresponding to the service package and sent to the third device; or, when the second device only sends the identifier of one service package, the service package identifier The information element carried in the session establishment request is sent to the third device. Based on this optional implementation manner, the third device can accurately determine the correspondence between the service package and the PDR.
  • the third device records the correspondence between the service package and the PDR.
  • the third device after the third device receives the identifier of the service package and the PDR corresponding to the service package from the second device, the third device records the correspondence between the service package and the PDR.
  • the third device receives the data packet.
  • the third device receives the data message after recording the correspondence between the service package and the PDR.
  • the data message may be an uplink data message or a downlink data message.
  • the third device determines a target PDR that matches the data packet.
  • the third device after receiving the data message, determines the target PDR that matches the data message.
  • the third device matches the attribute information of the data packet with the packet detection information in the PDR. If the match is successful, it is determined that the data message matches the PDR.
  • PDR1 and PDR2 of user 1 are activated in the third device.
  • PDR1 corresponds to business package 1
  • PDR2 corresponds to business package 2.
  • the third device matches the attribute information of the data message with the packet detection information in PDR1 and PDR2. If the attribute information of the data message matches the packet detection information in PDR1, then the data message matches the PDR1. Therefore, PDR1 is the target PDR.
  • the third device determines the service package 1 corresponding to PDR1 according to the pre-recorded correspondence between the service package and the PDR.
  • the third device obtains the target service package corresponding to the target PDR according to the recorded correspondence between the service package and the PDR.
  • the acquired target service package is the service package to which the data message received by the third device belongs. It can be seen that by implementing the method described in FIG. 6, it is beneficial for the device to accurately determine the service package to which the received data message belongs.
  • the third device After obtaining the target service package corresponding to the target PDR, the third device can perform related operations based on the service package.
  • the following describes the flow of related operations that the third device can perform based on the service package.
  • FIG. 7 is a schematic flowchart of another communication method provided by an embodiment of the present application.
  • the specific implementation manner of step 701 to step 709 is the same as the specific implementation manner of step 601 to step 609 described above, and will not be repeated here.
  • the third device may also execute the following steps 710 to 714. among them:
  • the third device performs data statistics based on the target service package according to the data message, and obtains a data statistics result corresponding to the target service package.
  • the target PDR is PDR1
  • the target service package corresponding to the target PDR is service package 1.
  • the third device performs data statistics based on the service package 1 according to the data message, and obtains the data statistics result.
  • the third device may also execute the charging and control policies defined in PDR1.
  • the third device may not perform step 710, and the third device may perform other operations based on the target service package, which is not limited in the embodiment of the present application.
  • the data statistics result may include the number of users using business package 1, the traffic usage information of business package 1, the duration usage information of business package 1, the traffic usage information of each application under business package 1, and the data under business package 1.
  • the traffic usage information of the business package 1 may be the traffic usage of the business package 1.
  • the traffic usage of the service package 1 may be the total traffic usage of the service package 1 by all users, that is, the third device can count the total traffic usage of the service package 1 by all users.
  • the traffic usage information of the business package 1 may be the traffic usage proportion of the business package 1. For example, there are a total of 10 service packages in the third device. If all users use 10 gigabytes of traffic in service package 1. The total traffic usage of the 10 business packages is 200G, and the traffic usage of business package 1 accounts for 1/20.
  • the duration usage information of the service package 1 may be the usage duration of the service package 1.
  • the usage duration of the service package 1 may be the total usage duration of the service package 1 by all users, that is, the third device can count the total usage duration of the service package 1 by all users.
  • the duration usage information of business package 1 may be the percentage of usage duration of business package 1. For example, there are a total of 10 service packages in the third device. If the total usage time of service package 1 by all users is 100 hours. The total usage time of 10 business packages is 2000 hours, and the usage time of business package 1 is 1/20.
  • the traffic usage information of each application under the business package 1 may be the traffic usage of each application under the business package 1.
  • the traffic usage of each application under business package 1 can be the total traffic usage of each application of the business package 1 by all users, that is, the third device can count the total traffic usage of all users on each application of the business package 1. the amount.
  • the traffic of user 1 using application 1 under service package 1 is 10G
  • the traffic using application 2 is 20G
  • User 2 uses 20G for application 1 and 20G for application 2 under service package 1.
  • the third device can calculate that the total traffic usage of application 1 under service package 1 is 30G, and the total traffic usage of application 2 is 40G.
  • the traffic usage information of each application under the business package 1 may be the traffic usage ratio of each application.
  • the traffic usage ratio of application 1 is 30G, and the total traffic usage of application 2 is 40G.
  • the traffic usage ratio of application 1 is 3/7, and the traffic usage ratio of application 2 is 4/7.
  • the duration usage information of each application under the service package 1 may be the usage duration of each application under the service package 1.
  • the usage duration of each application under business package 1 may be the total usage duration of each application of the business package 1 by all users, that is, the third device can count the total usage duration of each application of the business package 1 by all users.
  • the application duration usage information under business package 1 may be the percentage of application usage duration. For example, under the business package 1, the total usage time of application 1 is 100 hours, and the usage time of application 2 is 200 hours. The usage duration of application 1 under business package 1 is 1/3, and the usage duration of application 2 under business package 1 is 2/3.
  • the third device may perform step 711. Or, after the third device obtains the data statistics result corresponding to the target service package, it does not perform step 711 and performs other operations. For example, sending data statistics results to the first device or the second device, or directly analyzing the data statistics results, etc., which are not limited in the embodiment of the present application.
  • the third device sends the data statistics result corresponding to the target service package to the data analysis device.
  • the data analysis device performs data analysis on the data statistics result corresponding to the target service package, and obtains the data analysis result corresponding to the target service package.
  • the data analysis device after receiving the data statistical result corresponding to the target business package, performs data analysis on the data statistical result corresponding to the target business package to obtain the data analysis result corresponding to the target business package.
  • the data statistics results corresponding to business package 1 can be the number of users using business package 1, the traffic usage information of business package 1, the duration usage information of business package 1, and the traffic usage information of each application under business package 1. , One or more of the duration usage information of each application under business package 1, and the number of users sharing hotspots under business package 1.
  • the data analysis device performs data analysis on the data statistics result corresponding to the business package 1, and a specific implementation manner for obtaining the data analysis result corresponding to the business package 1 may be: the data analysis device determines whether the total traffic usage of the business package 1 is greater than the first threshold. The result of the judgment is the result of data analysis. If the total traffic usage of business package 1 is greater than the first threshold, it means that business package 1 is used more and is a mainstream business package.
  • the data analysis device performs data analysis on the data statistics results corresponding to business package 1
  • the specific implementation manner for obtaining the data analysis results corresponding to business package 1 may be: the data analysis device performs data analysis on all business packages according to the total traffic usage of the business package Sort to get the sort result of the business package.
  • the sorting result is the data analysis result. For example, all business packages are sorted according to the total traffic usage of the business packages in descending order. The business packages that are ranked before the preset position indicate that they are used more and are the mainstream business packages. It can be seen that, according to the data analysis results, it is possible to determine which service packages are mainstream service packages, so as to further stimulate or suppress mainstream service packages.
  • the traffic usage information of the business package 1 is the proportion of the total traffic usage of the business package 1, and the same is true, which is not repeated here.
  • the data statistics result includes the number of users who use the service package 1 and the duration usage information of the service package 1
  • the specific implementation method for data analysis on the data statistics result is the same, and will not be repeated here. That is to say, the data analysis result is obtained by performing data analysis on the number of users using the service package 1, the traffic usage information of the service package 1, or the duration usage information of the service package 1.
  • the data analysis result can be used to determine whether the business package 1 is a mainstream business package. Alternatively, other analysis operations may be performed on the number of users using the service package 1, the traffic usage information of the service package 1, or the duration usage information of the service package 1, which is not limited in the embodiment of the present application.
  • the data statistics result including the traffic usage information of business package 1 and the application traffic usage information of business package 1 as an example. If the traffic usage information of the business package 1 is the total traffic usage of all users on the business package 1, the traffic usage information of each application under the business package 1 is the total traffic usage of each application of the business package 1 by all users.
  • the data analysis device performs data analysis on the data statistics result corresponding to business package 1, and the specific implementation manner for obtaining the data analysis result corresponding to business package 1 may be: the data analysis device determines whether the total traffic usage of business package 1 is greater than the first threshold, And it is determined whether the total traffic usage of each application of the service package 1 is greater than the second threshold. The result of the judgment is the result of data analysis.
  • the data analysis device performs data analysis on the data statistics results corresponding to business package 1, and the specific implementation manner for obtaining the data analysis results corresponding to business package 1 may be: the data analysis device performs data analysis on all business packages according to the total traffic usage of the business package Sort to get the first sort result of the business package. The data analysis device sorts the applications of the business package 1 according to the total traffic usage of the applications of the business package 1, and obtains the second ranking result of the applications of the business package 1.
  • the first ranking result and the second ranking result are data analysis results. It can be seen that according to the data analysis results, it is possible to determine which business packages are mainstream business packages and which applications under the business packages are mainstream applications, so as to further stimulate or suppress the flow of mainstream applications of mainstream business packages. That is to say, through data analysis of the number of users using business package 1, the traffic usage information of business package 1, or the duration usage information of business package 1, and the application traffic usage information under business package 1 or the data under business package 1. The duration of each application uses information for data analysis, and the data analysis result is obtained. The data analysis result can be used to determine whether the business package 1 is a mainstream business package, and to determine the mainstream applications under the business package 1.
  • the data statistics result including the traffic usage information of service package 1 and the number of users sharing hotspots under service package 1 as an example. If the traffic usage information of business package 1 is the total traffic usage of business package 1 by all users.
  • the data analysis device performs data analysis on the data statistics result corresponding to business package 1, and the specific implementation manner for obtaining the data analysis result corresponding to business package 1 may be: the data analysis device determines whether the total traffic usage of business package 1 is greater than the first threshold, And determine whether the number of users sharing the hotspot under service package 1 is greater than the third threshold. The judgment result obtained is the result of data analysis. If the total traffic usage of business package 1 is greater than the first threshold, it means that business package 1 is used more and is a mainstream business package.
  • the data analysis device performs data analysis on the data statistics results corresponding to business package 1, and the specific implementation manner for obtaining the data analysis results corresponding to business package 1 may be: the data analysis device performs data analysis on all business packages according to the total traffic usage of the business package Sort to get the first sort result of the business package. Determine whether the number of users sharing the hotspot under service package 1 is greater than the third threshold. The obtained judgment result and the first sorting result are the data analysis results. It can be seen that, according to the data analysis result, it can be determined which service packages are mainstream service packages and which service packages have too many shared hotspots, so as to further suppress the traffic of low-value mainstream service packages with too many shared hotspots.
  • the data analysis device can also perform other data analysis operations on the above data statistics results, such as generating reports, etc., which is not limited in the embodiment of the present application.
  • the data analysis device sends the data analysis result corresponding to the target service package to the first device.
  • the first device performs traffic excitation or traffic suppression on the target service package according to the data analysis result corresponding to the target service package.
  • the first device after receiving the data analysis result corresponding to the target service package from the data analysis device, performs traffic stimulation or traffic suppression on the target service package according to the data analysis result corresponding to the target service package.
  • the first device may perform traffic stimulation on the target business package according to the data analysis result corresponding to the target business package.
  • High-value business packages refer to business packages whose price per bit of traffic is greater than the threshold. That is, a high-value business package refers to a business package with a higher price per bit of traffic.
  • the target business package is a high-value business package
  • the specific implementation manner for the first device to stimulate the target business package according to the data analysis result corresponding to the target business package is: if the first device analyzes the data corresponding to the target business package If the target business package is determined to be the mainstream business package, the target business package will be stimulated.
  • the specific implementation manner for the first device to stimulate the traffic of the target service package may be to improve the QOS of the service of the target service package or to improve the transmission quality of the transmission control protocol (transmission control protocol, TCP) transmission layer.
  • the first device may update the parameters in the PCC rule corresponding to the target service package, so as to improve the QOS of the service of the target service package or improve the transmission quality of the TCP transmission layer.
  • the first device may delete the PCC rule corresponding to the existing target service package, and regenerate a PCC rule for the target service package.
  • the PCC rule can improve the QOS of the target service package or improve the transmission quality of the TCP transport layer.
  • the first device may not delete the PCC rule corresponding to the existing target service package.
  • the first device may additionally generate an overlay rule, and the overlay rule may improve the QOS of the service of the target service package or improve the transmission quality of the TCP transport layer.
  • the target business package is a high-value business package
  • the first device performs traffic stimulation on the target business package according to the data analysis result corresponding to the target business package: If the first device analyzes the data corresponding to the target business package As a result, it is determined that the target business package is the mainstream business package, and the first application under the target business package is the mainstream application, then the traffic excitation is performed on the first application under the target business package.
  • a specific implementation manner for the first device to perform traffic stimulation on the target service package may be to improve QOS for the first application under the target service package or to improve the transmission quality of the transmission control protocol (transmission control protocol, TCP) transmission layer.
  • TCP transmission control protocol
  • the first device may update the parameters in the PCC rule corresponding to the target service package, so as to improve the QOS of the first application under the target service package or improve the transmission quality of the TCP transmission layer.
  • the first device can delete the PCC rule corresponding to the existing target service package, and regenerate a PCC rule for the target service package.
  • the PCC rule can improve the QOS or TCP transport layer transmission of the first application under the target service package quality.
  • the first device may not delete the PCC rule corresponding to the existing target service package.
  • the first device may additionally generate an overlay rule, and the overlay rule may improve the QOS of the first application under the target service package or improve the transmission quality of the TCP transport layer.
  • the first device may perform traffic suppression on the target service package according to the data analysis result corresponding to the target service package.
  • Low-value business packages refer to business packages whose price per bit of traffic is less than the threshold. That is, a low-value business package refers to a business package with a lower price per bit of traffic.
  • the first device performs traffic suppression on the target service package according to the data analysis result corresponding to the target service package: if the first device performs the traffic suppression according to the data analysis result corresponding to the target service package It is determined that the target service package is a mainstream service package, and the first device performs traffic suppression on the target service package.
  • the specific implementation manner for the first device to suppress the traffic of the target service package may be to reduce the bandwidth or reduce the QOS quality of the services of the target service package.
  • the first device may update the parameters in the PCC rule corresponding to the target service package, so as to reduce the bandwidth or QOS quality of the service of the target service package.
  • the first device may delete the PCC rule corresponding to the existing target service package, and regenerate a PCC rule for the target service package.
  • the PCC rule can reduce bandwidth or QOS quality for the services of the target service package.
  • the first device may not delete the PCC rule corresponding to the existing target service package.
  • the first device may generate an overlay rule for the target service package, and the overlay rule may reduce bandwidth or QOS quality for the services of the target service package.
  • the target business package is a low-value business package
  • the first device performs traffic suppression on the target business package according to the data analysis result corresponding to the target business package: If the first device analyzes the data corresponding to the target business package As a result, it is determined that the target business package is the mainstream business package, and the first application under the target business package is the mainstream application, then traffic suppression is performed on the first application under the target business package.
  • the specific implementation manner for the first device to suppress the traffic of the first application under the target service package may be to reduce the bandwidth or reduce the QOS quality of the first application under the target service package.
  • the first device may update the parameters in the PCC rule corresponding to the target service package, so as to reduce the bandwidth or reduce the QOS quality of the first application under the target service package.
  • the first device may delete the PCC rule corresponding to the existing target service package, and regenerate a PCC rule for the target service package.
  • the PCC rule may reduce the bandwidth or QOS quality of the first application under the target service package.
  • the first device may not delete the PCC rule corresponding to the existing target service package.
  • the first device may generate an overlay rule for the target service package, and the overlay rule may reduce the bandwidth or QOS quality of the first application under the target service package.
  • the target business package is a low-value business package
  • the first device performs traffic suppression on the target business package according to the data analysis result corresponding to the target business package: If the first device analyzes the data corresponding to the target business package As a result, it is determined that the target service package is a mainstream service package, and the number of users of the shared hotspot under the target service package is greater than the third threshold, then the target service package is traffic suppressed.
  • the specific implementation manner for the first device to suppress the traffic of the target service package may be to prohibit the hotspot sharing under the target service package. Specifically, the first device may delete the PCC rule corresponding to the existing target service package, and regenerate a PCC rule for the target service package.
  • the PCC rule may prohibit the hotspot sharing under the target service package.
  • the first device may not delete the PCC rule corresponding to the existing target service package.
  • the first device may generate an overlay rule for the target service package, and the overlay rule may prohibit hotspot sharing under the target service package.
  • step 713 and step 714 may not be performed.
  • the data analysis device performs data analysis on the data statistics result corresponding to the target business package, and after obtaining the data analysis result corresponding to the target business package, the data analysis device may send the data analysis result corresponding to the target business package to the second device.
  • the second device After receiving the data analysis result corresponding to the target service package from the data analysis device, the second device performs traffic stimulation or traffic suppression on the target service package according to the data analysis result corresponding to the target service package.
  • the target business package is a high-value business package
  • the second device may perform traffic stimulation on the target business package according to the data analysis result corresponding to the target business package.
  • the second device may perform traffic suppression on the target service package according to the data analysis result corresponding to the target service package.
  • the second device may generate an overlay rule for the target service package, and the overlay rule may perform traffic excitation or suppression on the target service package.
  • step 713 and step 714 may not be performed.
  • the data analysis device performs data analysis on the data statistics result corresponding to the target business package, and after obtaining the data analysis result corresponding to the target business package, the data analysis device may send the data analysis result corresponding to the target business package to the third device.
  • the third device After receiving the data analysis result corresponding to the target business package from the data analysis device, the third device performs traffic stimulation or traffic suppression on the target business package according to the data analysis result corresponding to the target business package.
  • the target business package is a high-value business package
  • the third device may perform traffic stimulation on the target business package according to the data analysis result corresponding to the target business package.
  • the third device may perform traffic suppression on the target service package according to the data analysis result corresponding to the target service package.
  • the third device may generate an overlay rule for the target service package, and the overlay rule may perform traffic stimulation or suppression on the target service package.
  • traffic excitation or suppression can be performed based on the service package.
  • FIG. 8 is a schematic flowchart of another communication method provided by an embodiment of the present application.
  • the execution subject of step 801 to step 803 and step 814 is the PCF entity or the chip in the PCF entity.
  • the execution subject of step 804 and step 805 is the SMF entity or the chip in the SMF entity.
  • the execution subject of step 806 to step 811 is the UPF entity or the chip in the UPF entity.
  • the execution subject of step 812 and step 813 is the data analysis device or the chip in the data analysis device.
  • the following takes PCF entity, SMF entity, UPF entity and data analysis device as the execution subject of the method as an example for description.
  • the communication method includes the following steps 801 to 814, wherein:
  • the PCF entity obtains the service package signed by the user.
  • the user terminal may send a session establishment request to the SMF entity through RAN or AMF.
  • the SMF entity After receiving the session establishment request, the SMF entity sends an Npcf_SMPolicyControl_Create message to the PCF entity. After the PCF entity receives the Npcf_SMPolicyControl_Create message, it triggers to obtain the service package signed by the user.
  • the user terminal may send a session update request to the SMF entity through RAN or AMF.
  • the SMF entity sends an Npcf_SMPolicyControl_Update message to the PCF entity. After the PCF entity receives the Npcf_SMPolicyControl_Update message, it triggers the acquisition of the service package signed by the user.
  • the PCF entity may also actively obtain the service package signed by the user.
  • the PCF entity may be triggered to obtain the service package signed by the user through other methods.
  • the PCF entity determines the PCC rule corresponding to the service package.
  • step 802 refers to the specific implementation manner of step 602 described above, which is not repeated here.
  • the PCF entity sends the identifier of the service package and the PCC rule corresponding to the service package to the SMF entity.
  • the service package identifier is carried in the information element of the corresponding PCC rule and sent to the SMF entity.
  • the information elements included in the PCC rule may be as follows, where the information elements pccServiceName/pccServiceID represent the identifier of the service package.
  • the identifier of the service package may specifically be carried in attribute value pairs (AVP) of the corresponding PCC rule.
  • AVP attribute value pairs
  • the PCF entity only sends the identifier of one service package, and the identifier of the service package is carried in the information element of the session rule (session rule) and sent to the SMF entity.
  • the information element included in the session rule may be as follows, where the information element sessServiceName/sessServiceID represents the identifier of the service package.
  • the identifier of the service package may specifically be carried in the AVP of the corresponding session rule. Based on this optional implementation manner, the SMF entity can accurately determine the correspondence between the service package and the PCC rule.
  • the SMF entity converts the PCC rule corresponding to the service package into a PDR.
  • the SMF entity converts the PCC rule corresponding to the service package into PDR.
  • the SMF entity sends the identifier of the service package and the PDR corresponding to the service package to the UPF entity.
  • the service package identifier is carried in the information element of the PDR corresponding to the service package and sent to the UPF entity.
  • a PDR may include a cell carrying a PDR identifier, a cell carrying a FAR ID, a cell carrying a URR ID, a cell carrying a QER ID, a cell carrying a service package identifier, and so on.
  • the UPF entity can accurately determine the correspondence between the service package and the PDR.
  • the identifier of the service package is carried in the information element of the session establishment request (session establishment request) and sent to the UPF entity.
  • the session establishment request may include an information element carrying a PDR, an information element carrying a node ID (Node ID), an information element carrying an identifier of a service package, and so on.
  • the UPF entity can accurately determine the correspondence between the service package and the PDR.
  • the UPF entity records the correspondence between the service package and the PDR.
  • the UPF entity After receiving the identifier of the service package and the PDR corresponding to the service package, the UPF entity records the correspondence between the service package and the PDR.
  • the UPF entity receives the data message.
  • the UPF entity determines a target PDR matching the data packet.
  • the UPF entity obtains the target service package corresponding to the target PDR according to the recorded correspondence between the service package and the PDR.
  • step 806 to step 809 refer to the specific implementation manners of step 606 to step 609 described above, which will not be repeated here.
  • the UPF entity performs data statistics based on the target service package according to the data message, and obtains a data statistics result corresponding to the target service package.
  • the UPF entity sends the data statistics result corresponding to the target service package to the data analysis device.
  • the data analysis device performs data analysis on the data statistics result corresponding to the target service package, and obtains the data analysis result corresponding to the target service package.
  • the data analysis device sends the data analysis result corresponding to the target service package to the PCF entity.
  • the PCF entity performs traffic stimulation or traffic suppression on the target service package according to the data analysis result corresponding to the target service package.
  • step 810 to step 814 refer to the specific implementation manner of step 710 to step 714 above, and details are not described herein.
  • step 813 and step 814 may not be performed.
  • the data analysis device performs data analysis on the data statistics result corresponding to the target business package, and after obtaining the data analysis result corresponding to the target business package, the data analysis device may send the data analysis result corresponding to the target business package to the SMF entity.
  • the SMF entity After receiving the data analysis result corresponding to the target service package from the data analysis device, the SMF entity performs traffic stimulation or traffic suppression on the target service package according to the data analysis result corresponding to the target service package.
  • step 813 and step 814 may not be performed.
  • the data analysis device performs data analysis on the data statistics result corresponding to the target business package, and after obtaining the data analysis result corresponding to the target business package, the data analysis device may send the data analysis result corresponding to the target business package to the UPF entity. After receiving the data analysis result corresponding to the target service package from the data analysis device, the UPF entity performs traffic stimulation or traffic suppression on the target service package according to the data analysis result corresponding to the target service package.
  • FIG. 9 is a schematic flowchart of another communication method provided by an embodiment of the present application.
  • the execution subject of step 901 to step 903 and step 914 is the PCRF entity or the chip in the PCRF entity.
  • the execution subject of step 904 and step 905 is the PGW-C entity or the chip in the PGW-C entity.
  • the execution subject of step 906 to step 911 is the PGW-U entity or the chip in the PGW-U entity.
  • the execution subject of step 912 and step 913 is the data analysis device or the chip in the data analysis device.
  • the following takes the PCRF entity, the PGW-C entity, the PGW-U entity and the data analysis device as the execution subject of the method as an example for description.
  • the communication method includes the following steps 901 to 914, where:
  • the PCRF entity obtains the service package signed by the user.
  • the user terminal may send a session establishment request to the PGW-C entity through the RAN or a mobility management node (mobility management entity, MME).
  • the PGW-C entity After receiving the session establishment request, the PGW-C entity sends a CCR-I (credit control request initial) message to the PCRF entity. After receiving the CCR-I message, the PCRF entity triggers the acquisition of the service package subscribed by the user.
  • the user terminal may send a session update request to the PGW-C entity through RAN or MME.
  • the PGW-C entity sends a CCR-U (credit control request update) message to the PCRF entity.
  • the PCRF entity After the PCRF entity receives the CCR-U message, it triggers the acquisition of the service package subscribed by the user.
  • the PCRF entity may also actively obtain the service package signed by the user.
  • the PCRF entity may be triggered to obtain the service package subscribed by the user through other methods.
  • the PCRF entity determines the PCC rule corresponding to the service package.
  • step 902 refers to the specific implementation manner of step 602 described above, which is not repeated here.
  • the PCRF entity sends the identifier of the service package and the PCC rule corresponding to the service package to the PGW-C entity.
  • the identifier of the service package is carried in the cell of the Charging-Rule-Install message and sent to the PGW-C entity.
  • the information element included in the Charging-Rule-Install message may be as follows, where the information element Service-Name/Service-Identifier represents the identifier of the service package.
  • the identifier of the service package may specifically be carried in the AVP of the Charging-Rule-Install message. Based on this optional implementation manner, the PGW-C entity can accurately determine the correspondence between the service package and the PCC rule.
  • the identifier of the service package is carried in the information element of the credit control response CCA message or re-auth-request (re-auth-request, RAR) message Sent to the PGW-C entity.
  • the information element included in the CCA message may be as follows, where the information element Service-Name/Service-Identifier represents the identifier of the service package.
  • the service package identifier may specifically be carried in the AVP of the corresponding CCA message or RAR message. Based on this optional implementation manner, the PGW-C entity can accurately determine the correspondence between the service package and the PCC rule.
  • the PGW-C entity converts the PCC rule corresponding to the service package into a PDR.
  • the PGW-C entity converts the PCC rule corresponding to the service package into PDR.
  • the PGW-C entity sends the identifier of the service package and the PDR corresponding to the service package to the PGW-U entity.
  • the service package identifier is carried in the information element of the PDR corresponding to the service package and sent to the PGW-U entity.
  • a PDR may include a cell carrying a PDR identifier, a cell carrying a FAR ID, a cell carrying a URR ID, a cell carrying a QER ID, a cell carrying a service package identifier, and so on.
  • the PGW-U entity can accurately determine the correspondence between the service package and the PDR.
  • the PGW-C entity when the PGW-C entity only sends the identifier of one service package, the identifier of the service package is carried in a session establishment request (session establishment request) cell and sent to the PGW-U entity.
  • the session establishment request may include an information element carrying a PDR, an information element carrying a node ID (Node ID), an information element carrying an identifier of a service package, and so on.
  • the PGW-U entity can accurately determine the correspondence between the service package and the PDR.
  • the PGW-U entity records the correspondence between the service package and the PDR.
  • the PGW-U entity After the PGW-U entity receives the service package identifier and the PDR corresponding to the service package from the PGW-C entity, the PGW-U entity records the correspondence between the service package and the PDR.
  • the PGW-U entity receives the data message.
  • the PGW-U entity determines a target PDR matching the data packet.
  • the PGW-U entity obtains the target service package corresponding to the target PDR according to the recorded correspondence between the service package and the PDR.
  • step 906 to step 909 please refer to the specific implementation manners of step 606 to step 609 above, and details are not described here.
  • the PGW-U entity performs data statistics based on the target service package according to the data message, and obtains a data statistics result corresponding to the target service package.
  • the PGW-U entity sends the data statistical result corresponding to the target service package to the data analysis device.
  • the data analysis device performs data analysis on the data statistics result corresponding to the target service package, and obtains the data analysis result corresponding to the target service package.
  • the data analysis device sends the data analysis result corresponding to the target service package to the PCRF entity.
  • the PCRF entity performs traffic stimulation or traffic suppression on the target service package according to the data analysis result corresponding to the target service package.
  • step 910 to step 914 refer to the specific implementation manners of step 710 to step 714 above, and details are not described herein.
  • step 913 and step 914 may not be performed.
  • the data analysis device performs data analysis on the data statistics result corresponding to the target business package, and after obtaining the data analysis result corresponding to the target business package, the data analysis device may send the data analysis result corresponding to the target business package to the PGW-C entity.
  • the PGW-C entity After receiving the data analysis result corresponding to the target service package from the data analysis device, the PGW-C entity performs traffic stimulation or traffic suppression on the target service package according to the data analysis result corresponding to the target service package.
  • step 913 and step 914 may not be performed.
  • the data analysis device performs data analysis on the data statistics result corresponding to the target business package, and after obtaining the data analysis result corresponding to the target business package, the data analysis device may send the data analysis result corresponding to the target business package to the PGW-U entity. After receiving the data analysis result corresponding to the target service package from the data analysis device, the PGW-U entity performs traffic stimulation or traffic suppression on the target service package according to the data analysis result corresponding to the target service package.
  • FIG. 10 is a schematic flowchart of another communication method provided by an embodiment of the present application.
  • the execution subject of step 1001 to step 1003 and step 1014 is the PCRF entity or the chip in the PCRF entity.
  • the execution subject of step 1004 and step 1005 is the TDF-C entity or the chip in the TDF-C entity.
  • the execution subject of step 1006 to step 1011 is the TDF-U entity or the chip in the TDF-U entity.
  • the execution subject of step 1012 and step 1013 is the data analysis device or the chip in the data analysis device.
  • the following takes the PCRF entity, TDF-C entity, TDF-U entity and data analysis equipment as the execution subject of the method as an example for description.
  • the communication method includes the following steps 1001 to 1014, where:
  • the PCRF entity obtains the service package signed by the user.
  • the user terminal may send a session establishment request to the TDF-C entity through the RAN or a mobility management node (mobility management entity, MME).
  • the TDF-C entity After receiving the session establishment request, the TDF-C entity sends a CCR-I (credit control request initial) message to the PCRF entity.
  • the PCRF entity After receiving the CCR-I message, the PCRF entity triggers the acquisition of the service package subscribed by the user.
  • the user terminal may send a session update request to the PGW-C entity through RAN or MME.
  • the TDF-C entity sends a CCR-U (credit control request update) message to the PCRF entity.
  • the PCRF entity After the PCRF entity receives the CCR-U message, it triggers the acquisition of the service package subscribed by the user.
  • the PCRF entity may also actively obtain the service package signed by the user.
  • the PCRF entity may be triggered to obtain the service package subscribed by the user through other methods.
  • the PCRF entity determines the PCC rule corresponding to the service package.
  • step 1002 please refer to the specific implementation manner of step 602, which is not repeated here.
  • the PCRF entity sends the identifier of the service package and the PCC rule corresponding to the service package to the TDF-C entity.
  • the service package identifier is carried in the information element of the Charging-Rule-Install message and sent to the TDF-C entity.
  • the identifier of the service package may specifically be carried in the AVP of the Charging-Rule-Install message.
  • the TDF-C entity can accurately determine the correspondence between the service package and the PCC rule.
  • the identifier of the service package is carried in the information element of the credit control response CCA message or re-auth-request (re-auth-request, RAR) message Sent to the TDF-C entity.
  • the service package identifier may specifically be carried in the AVP of the corresponding CCA message or RAR message. Based on this optional implementation manner, the TDF-C entity can accurately determine the correspondence between the service package and the PCC rule.
  • the TDF-C entity converts the PCC rule corresponding to the service package into a PDR.
  • the TDF-C entity converts the PCC rule corresponding to the service package into PDR.
  • the TDF-C entity sends the identifier of the service package and the PDR corresponding to the service package to the TDF-U entity.
  • the service package identifier is carried in the information element of the PDR corresponding to the service package and sent to the TDF-U entity.
  • a PDR may include a cell carrying a PDR identifier, a cell carrying a FAR ID, a cell carrying a URR ID, a cell carrying a QER ID, a cell carrying a service package identifier, and so on.
  • the TDF-U entity can accurately determine the correspondence between the service package and the PDR.
  • the TDF-C entity when the TDF-C entity only sends the identifier of one service package, the identifier of the service package is carried in the information element of the session establishment request and sent to the TDF-U entity.
  • the session establishment request may include an information element carrying a PDR, an information element carrying a node ID (Node ID), an information element carrying an identifier of a service package, and so on.
  • the TDF-U entity can accurately determine the correspondence between the service package and the PDR.
  • the TDF-U entity records the correspondence between the service package and the PDR.
  • the TDF-U entity receives the data message.
  • the TDF-U entity determines a target PDR matching the data message.
  • the TDF-U entity obtains the target service package corresponding to the target PDR according to the recorded correspondence between the service package and the PDR.
  • step 1006 to step 1009 please refer to the specific implementation manners of step 606 to step 609 above, and details are not described herein.
  • the TDF-U entity performs data statistics based on the target service package according to the data message, and obtains a data statistics result corresponding to the target service package.
  • the TDF-U entity sends the data statistics result corresponding to the target service package to the data analysis device.
  • the data analysis device performs data analysis on the data statistics result corresponding to the target business package, and obtains the data analysis result corresponding to the target business package.
  • the data analysis device sends the data analysis result corresponding to the target service package to the PCRF entity.
  • the PCRF entity performs traffic stimulation or traffic suppression on the target service package according to the data analysis result corresponding to the target service package.
  • step 1010 to step 1014 refer to the specific implementation manners of step 710 to step 714 above, and details are not described herein.
  • step 1013 and step 1014 may not be performed.
  • the data analysis device performs data analysis on the data statistics result corresponding to the target business package, and after obtaining the data analysis result corresponding to the target business package, the data analysis device may send the data analysis result corresponding to the target business package to the TDF-C entity. After receiving the data analysis result corresponding to the target business package from the data analysis device, the TDF-C entity performs traffic stimulation or traffic suppression on the target business package according to the data analysis result corresponding to the target business package.
  • step 1013 and step 1014 may not be performed.
  • the data analysis device performs data analysis on the data statistics result corresponding to the target business package, and after obtaining the data analysis result corresponding to the target business package, the data analysis device may send the data analysis result corresponding to the target business package to the TDF-U entity. After receiving the data analysis result corresponding to the target service package from the data analysis device, the TDF-U entity performs traffic stimulation or traffic suppression on the target service package according to the data analysis result corresponding to the target service package.
  • FIG. 11 is a schematic flowchart of another communication method provided by an embodiment of the present application.
  • the execution subject of step 1101 to step 1103 is the first device or the chip in the first device.
  • the execution subject of step 1104 to step 1107 is the second device, or the chip in the second device.
  • the following takes the first device and the second device as the execution body of the method as an example for description.
  • the communication method includes the following steps 1101 to 1107, where:
  • the first device obtains the service package signed by the user.
  • the communication method shown in FIG. 11 can be applied to any one of the foregoing application scenario 4 and application scenario 5. That is, the first device in FIG. 11 is a PCRF entity, and the second device is a PGW. Or, the first device is a PCRF entity, and the second device is a TDF entity. Of course, the first device may also be another entity for issuing PCC rules. The second device may also be another entity used to execute PCC rules, which is not limited in the embodiment of the present application.
  • the first device determines the PCC rule corresponding to the service package.
  • the first device sends the identifier of the service package and the PCC rule corresponding to the service package to the second device.
  • step 1101 to step 1103 is the same as the specific implementation manner of step 601 to step 603 described above, and will not be repeated here.
  • the second device records the correspondence between the service package and the PCC rule.
  • the second device After receiving the identifier of the service package and the PCC rule corresponding to the service package from the first device, the second device records the correspondence between the service package and the PCC rule.
  • the second device receives the data packet.
  • the data message may be an uplink data message or a downlink data message.
  • the second device determines a target PCC rule matching the data packet.
  • the second device after receiving the data message, determines the target PCC rule matching the data message.
  • the second device matches the attribute information of the data packet with the service data flow detection information in the PCC rule. If the match is successful, it is determined that the data message matches the PCC rule.
  • PCC rule 1 and PCC rule 2 of user 1 are activated in the third device. Among them, PCC rule 1 corresponds to business package 1, and PCC rule 2 corresponds to business package 2.
  • the second device matches the attribute information of the data packet with the service data flow detection information in PCC rule 1 and PCC rule 2. If the attribute information of the data packet matches the service data flow detection information in the PCC rule 1, the data packet matches the PCC rule 1. Therefore, PCC rule 1 is the target PCC rule.
  • the second device determines that the PCC rule 1 corresponds to the service package 1 according to the pre-recorded correspondence between the service package and the PCC rule.
  • the second device obtains the target service package corresponding to the target PCC rule according to the recorded correspondence between the PCC rule and the service package.
  • the acquired target service package is the service package to which the data message received by the second device belongs. It can be seen that by implementing the method described in FIG. 11, the core network device can determine the service package to which the received data message belongs.
  • the second device After obtaining the target service package corresponding to the target PCC rule, the second device can perform related operations based on the service package.
  • the following describes the flow of related operations that the second device can perform based on the service package.
  • FIG. 12 is a schematic flowchart of another communication method provided by an embodiment of the present application.
  • the specific implementation manners of step 1201 to step 1207 are the same as the specific implementation manners of step 1101 to step 1107 described above, and will not be repeated here.
  • the second device may also perform the following steps 1208 to 1212. among them:
  • the second device performs data statistics based on the target service package according to the data message, and obtains the data statistics result.
  • the target PCC rule is PCC rule 1
  • the target service package corresponding to target PCC rule 1 is service package 1.
  • the second device performs data statistics based on the service package 1 according to the data message, and obtains the data statistics result.
  • the second device may also execute the charging and control policy defined in PCC rule 1.
  • the second device may not perform step 1208, and the second device may perform other operations based on the target service package, which is not limited in this embodiment of the application.
  • the second device sends the data statistics result corresponding to the target service package to the data analysis device.
  • the data analysis device performs data analysis on the data statistics result corresponding to the target business package, and obtains the data analysis result corresponding to the target business package.
  • the data analysis device sends the data analysis result corresponding to the target service package to the first device.
  • the first device performs traffic excitation or traffic suppression on the target service package according to the data analysis result corresponding to the target service package.
  • step 1208 to step 1212 are the same as the specific implementation manners of step 710 to step 714 described above, and will not be repeated here.
  • step 1211 and step 1212 may not be performed.
  • the data analysis device performs data analysis on the data statistics result corresponding to the target business package, and after obtaining the data analysis result corresponding to the target business package, the data analysis device may send the data analysis result corresponding to the target business package to the second device.
  • the second device After receiving the data analysis result corresponding to the target service package from the data analysis device, the second device performs traffic stimulation or traffic suppression on the target service package according to the data analysis result corresponding to the target service package.
  • the target business package is a high-value business package
  • the second device may perform traffic stimulation on the target business package according to the data analysis result corresponding to the target business package.
  • the second device may perform traffic suppression on the target service package according to the data analysis result corresponding to the target service package.
  • the second device may generate an overlay rule for the target service package, and the overlay rule may perform traffic excitation or suppression on the target service package.
  • FIG. 13 is a schematic flowchart of another communication method provided by an embodiment of the present application.
  • the execution subject of step 1301 to step 1303 and step 1312 is the PCRF entity, or the chip in the PCRF entity.
  • the execution subject of steps 1304 to 1309 is PGW, or the chip in PGW.
  • the execution subject of step 1310 and step 1311 is the data analysis device or the chip in the data analysis device.
  • the following takes the PCRF entity, the PGW, and the data analysis device as the execution subject of the method as an example for description.
  • the communication method includes the following steps 1301 to 1312, where:
  • the PCRF entity obtains the service package signed by the user.
  • the user terminal may send a session establishment request to the PGW through the RAN or a mobility management entity (mobility management entity, MME).
  • the PGW After receiving the session establishment request, the PGW sends a CCR-I (credit control request initial) message to the PCRF entity.
  • the PCRF entity After receiving the CCR-I message, the PCRF entity triggers the acquisition of the service package subscribed by the user.
  • the user terminal may send a session update request to the PGW through the RAN or MME.
  • the PGW sends a CCR-U (credit control request update) message to the PCRF entity.
  • the PCRF entity After the PCRF entity receives the CCR-U message, it triggers the acquisition of the service package subscribed by the user.
  • the PCRF entity may also actively obtain the service package signed by the user.
  • the PCRF entity may be triggered to obtain the service package subscribed by the user through other methods.
  • the PCRF entity determines the PCC rule corresponding to the service package.
  • step 1302 please refer to the specific implementation manner of step 602 above, which is not repeated here.
  • the PCRF entity sends the identifier of the service package and the PCC rule corresponding to the service package to the PGW.
  • the identifier of the service package is carried in the information element of the Charging-Rule-Install message and sent to the PGW.
  • the identifier of the service package may specifically be carried in the AVP of the Charging-Rule-Install message. Based on this optional implementation manner, the PGW can accurately determine the correspondence between the service package and the PCC rule.
  • the identifier of the service package is carried in the information element of the credit control response CCA message or re-auth-request (re-auth-request, RAR) message Sent to PGW.
  • the identifier of the service package may specifically be carried in the AVP of the corresponding CCA message or RAR message.
  • the PGW can accurately determine the correspondence between the service package and the PCC rule.
  • the PGW records the correspondence between the service package and the PCC rule.
  • the PGW after receiving the identifier of the service package and the PCC rule corresponding to the service package, the PGW records the correspondence between the service package and the PCC rule.
  • the PGW receives the data message.
  • the data message may be an uplink data message or a downlink data message.
  • the PGW determines a target PCC rule matching the data packet.
  • the PGW obtains the target service package corresponding to the target PCC rule according to the recorded correspondence between the PCC rule and the service package.
  • step 1305 to step 1307 is the same as the specific implementation manner of step 1105 to step 1107 described above, and will not be repeated here.
  • the PGW performs data statistics based on the target service package according to the data message, and obtains the data statistics result.
  • the PGW sends the data statistics result corresponding to the target service package to the data analysis device.
  • the data analysis device performs data analysis on the data statistics result corresponding to the target business package, and obtains the data analysis result corresponding to the target business package.
  • the data analysis device sends the data analysis result corresponding to the target service package to the PCRF entity.
  • the PCRF entity performs traffic stimulation or traffic suppression on the target service package according to the data analysis result corresponding to the target service package.
  • step 1308 to step 1312 is the same as the specific implementation manner of step 710 to step 714 described above, and will not be repeated here.
  • step 1311 and step 1312 may not be performed.
  • the data analysis device performs data analysis on the data statistics result corresponding to the target business package, and after obtaining the data analysis result corresponding to the target business package, the data analysis device may send the data analysis result corresponding to the target business package to the PGW.
  • the PGW After receiving the data analysis result corresponding to the target service package from the data analysis device, the PGW performs traffic stimulation or traffic suppression on the target service package according to the data analysis result corresponding to the target service package.
  • the target service package is a high-value service package
  • the PGW may perform traffic stimulation on the target service package according to the data analysis result corresponding to the target service package.
  • the PGW may suppress the traffic of the target service package according to the data analysis result corresponding to the target service package.
  • the PGW may generate an overlay rule for the target service package, and the overlay rule may stimulate or suppress traffic of the target service package.
  • FIG. 14 is a schematic flowchart of another communication method provided by an embodiment of the present application.
  • the execution subject of step 1401 to step 1403 and step 1412 is the PCRF entity, or the chip in the PCRF entity.
  • the execution subject of steps 1404 to 1409 is the TDF entity or the chip in the TDF entity.
  • the execution subject of step 1410 and step 1411 is the data analysis device or the chip in the data analysis device.
  • the following takes the PCRF entity, the TDF entity, and the data analysis device as the execution body of the method as an example for description.
  • the communication method includes the following steps 1401 to 1412, where:
  • the PCRF entity obtains the service package signed by the user.
  • the user terminal may send a session establishment request to the TDF entity through the RAN or a mobility management node (mobility management entity, MME).
  • the TDF entity After receiving the session establishment request, the TDF entity sends a CCR-I (credit control request initial) message to the PCRF entity.
  • the PCRF entity After receiving the CCR-I message, the PCRF entity triggers the acquisition of the service package subscribed by the user.
  • the user terminal may send a session update request to the TDF entity through the RAN or MME.
  • the TDF entity sends a CCR-U (credit control request update) message to the PCRF entity.
  • the PCRF entity After the PCRF entity receives the CCR-U message, it triggers the acquisition of the service package subscribed by the user.
  • the PCRF entity may also actively obtain the service package signed by the user.
  • the PCRF entity may be triggered to obtain the service package subscribed by the user through other methods.
  • the PCRF entity determines the PCC rule corresponding to the service package.
  • step 1402 For the specific implementation manner of step 1402, please refer to the specific implementation manner of step 602 above, which is not repeated here.
  • the PCRF entity sends the identifier of the service package and the PCC rule corresponding to the service package to the TDF entity.
  • the identifier of the service package is carried in the information element of the Charging-Rule-Install message and sent to the TDF entity.
  • the identifier of the service package may specifically be carried in the AVP of the Charging-Rule-Install message. Based on this optional implementation manner, the TDF entity can accurately determine the correspondence between the service package and the PCC rule.
  • the identifier of the service package is carried in the information element of the credit control response CCA message or re-auth-request (re-auth-request, RAR) message Sent to the TDF entity.
  • the service package identifier may specifically be carried in the AVP of the corresponding CCA message or RAR message.
  • the TDF entity can accurately determine the correspondence between the service package and the PCC rule.
  • the TDF entity records the correspondence between the service package and the PCC rule.
  • the TDF entity after receiving the identifier of the service package and the PCC rule corresponding to the service package, the TDF entity records the correspondence between the service package and the PCC rule.
  • the TDF entity receives the data message.
  • the data message may be an uplink data message or a downlink data message.
  • the TDF entity determines a target PCC rule matching the data message.
  • the TDF entity obtains the target service package corresponding to the target PCC rule according to the recorded correspondence between the PCC rule and the service package.
  • step 1405 to step 1407 is the same as the specific implementation manner of step 1105 to step 1107 described above, and will not be repeated here.
  • the TDF entity performs data statistics based on the target service package according to the data message, and obtains the data statistics result.
  • the TDF entity sends the data statistics result corresponding to the target service package to the data analysis device.
  • the data analysis device performs data analysis on the data statistics result corresponding to the target business package, and obtains the data analysis result corresponding to the target business package.
  • the data analysis device sends the data analysis result corresponding to the target service package to the PCRF entity.
  • the PCRF entity performs traffic stimulation or traffic suppression on the target service package according to the data analysis result corresponding to the target service package.
  • step 1408 to step 1412 is the same as the specific implementation manner of step 710 to step 714 described above, and details are not described herein again.
  • step 1411 and step 1412 may not be performed.
  • the data analysis device performs data analysis on the data statistics result corresponding to the target business package, and after obtaining the data analysis result corresponding to the target business package, the data analysis device may send the data analysis result corresponding to the target business package to the TDF entity.
  • the TDF entity After receiving the data analysis result corresponding to the target service package from the data analysis device, the TDF entity performs traffic stimulation or traffic suppression on the target service package according to the data analysis result corresponding to the target service package.
  • the target business package is a high-value business package
  • the TDF entity may perform traffic stimulation on the target business package according to the data analysis result corresponding to the target business package.
  • the TDF entity may suppress the traffic of the target business package according to the data analysis result corresponding to the target business package.
  • the TDF entity may generate an overlay rule for the target service package, and the overlay rule may stimulate or suppress traffic of the target service package.
  • FIG. 15 is a schematic flowchart of another communication method provided by an embodiment of the present application.
  • the execution subject of step 1501 to step 1503 and step 1512 is the PCRF entity, or the chip in the PCRF entity.
  • the execution subject of step 1504 to step 1509 is PGW, or the chip in PGW.
  • the execution subject of step 1510 and step 1511 is the data analysis device or the chip in the data analysis device.
  • the following takes the PCRF entity, the PGW, and the data analysis device as the execution subject of the method as an example for description.
  • the communication method includes the following steps 1501 to 1512, where:
  • the PCRF entity obtains the service package signed by the user.
  • the PCRF entity determines the PCC rule corresponding to the service package.
  • the PCRF entity sends the identifier of the service package and the PCC rule corresponding to the service package to the PGW.
  • step 1501 to step 1503 are the same as the specific implementation manners of step 1401 to step 1403 described above, and will not be repeated here.
  • the PGW copies the identifier of the service package and the PCC rule corresponding to the service package to the TDF entity.
  • the PGW after receiving the identifier of the service package and the PCC rule corresponding to the service package from the PCRF entity, the PGW copies the identifier of the service package and the PCC rule corresponding to the service package to the TDF entity.
  • the PGW sends the identifier of the service package and the PCC rule corresponding to the service package to the TDF through the Radius CC interface.
  • the ID of the service package and the PCC rule corresponding to the service package can be sent to the TDF through the Accounting Start message or the Accounting Update message of the Radius CC interface.
  • the identifier of the service package and the PCC rule corresponding to the service package can also be sent to the TDF entity through the session dimension information.
  • the TDF entity records the correspondence between the service package and the PCC rule.
  • the TDF entity after receiving the identifier of the service package and the PCC rule corresponding to the service package, the TDF entity records the correspondence between the service package and the PCC rule.
  • the TDF entity receives the data message.
  • the TDF entity determines a target PCC rule matching the data message.
  • the TDF entity obtains the target service package corresponding to the target PCC rule according to the recorded correspondence between the PCC rule and the service package.
  • the TDF entity performs data statistics based on the target service package according to the data message, and obtains the data statistics result.
  • the TDF entity sends the data statistics result corresponding to the target service package to the data analysis device.
  • the data analysis device performs data analysis on the data statistics result corresponding to the target business package, and obtains the data analysis result corresponding to the target business package.
  • the data analysis device sends the data analysis result corresponding to the target service package to the PCRF entity.
  • the PCRF entity performs traffic stimulation or traffic suppression on the target service package according to the data analysis result corresponding to the target service package.
  • step 1505 to step 1513 are the same as the specific implementation manners of step 1404 to step 1412 described above, and will not be repeated here.
  • the embodiment of the present invention may divide the device into functional units according to the foregoing method examples.
  • each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit. It should be noted that the division of units in the embodiment of the present invention is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • FIG. 16 shows a schematic structural diagram of a communication device according to an embodiment of the present application.
  • the communication device shown in FIG. 16 may be used to perform part or all of the functions of the first device in the method embodiments described in FIG. 6 and FIG. 7.
  • the communication device shown in FIG. 16 may be used to perform part or all of the functions of the PCF entity in the method embodiment described in FIG. 8.
  • the communication device shown in FIG. 16 may be used to perform part or all of the functions of the PCRF entity in the method embodiments described in FIG. 9 and FIG. 10.
  • the communication device shown in FIG. 16 may be used to perform part or all of the functions of the first device in the method embodiments described in FIG. 11 and FIG. 12.
  • the communication device shown in FIG. 16 may be used to perform part or all of the functions of the PCRF entity in the method embodiments described in FIG. 13 to FIG. 15.
  • the communication device shown in FIG. 16 may include a communication unit 1601 and a processing unit 1602. among them:
  • the processing unit 1602 is used to obtain the service package signed by the user; the processing unit 1602 is also used to determine the policy and charging control PCC rules corresponding to the service package; the communication unit 1601 is used to send the service package identifier and service to the second device PCC rules corresponding to the package.
  • the communication unit 1601 is further configured to receive the data analysis result corresponding to the target service package from the data analysis device; the processing unit 1602 is further configured to analyze the target service package according to the data analysis result corresponding to the target service package Perform flow excitation or flow suppression.
  • the communication device is a policy control function PCF entity, and the second device is a session management function SMF entity; or, the communication device is a policy and charging rules function PCRF entity, and the second device is a packet data gateway control PGW-C entity; or, the communication device is a PCRF entity, and the second device is a service detection function control plane TDF-C entity; or, the communication device is a PCRF entity, and the second device is a packet data gateway PGW; or, the communication device is PCRF entity, the second device is a service detection function TDF entity.
  • the communication device is a PCF entity, and the second device is an SMF entity;
  • the service package identifier is carried in the information element of the corresponding PCC rule and sent to the second device; or, the communication device only sends the identifier of one service package, and the service package identifier is carried in the information element of the session rule and sent to the second device.
  • the communication device is a PCRF entity, and the second device is a PGW-C entity; or, the communication device is a PCRF entity, and the second device is a TDF-C entity; or, the communication device is a PCRF entity, and the first The second device is a PGW; or, the communication device is a PCRF entity, and the second device is a TDF entity;
  • the identifier of the service package is carried in the cell of the Charging-Rule-Install message and sent to the second device; or the communication device only sends the identifier of one service package, and the identifier of the service package is carried in the credit control response CCA message or The re-authentication request RAR message is sent to the second device in the cell.
  • FIG. 16 shows a schematic structural diagram of a communication device according to an embodiment of the present application.
  • the communication device shown in FIG. 16 may be used to perform part or all of the functions of the second device in the method embodiments described in FIG. 6 and FIG. 7.
  • the communication device shown in FIG. 16 may be used to perform part or all of the functions of the SMF entity in the method embodiment described in FIG. 8.
  • the communication device shown in FIG. 16 may be used to perform part or all of the functions of the PGW-C entity in the method embodiment described in FIG. 9 above.
  • the communication device shown in FIG. 16 may be used to perform part or all of the functions of the TDF-C entity in the method embodiment described in FIG. 10.
  • the communication device shown in FIG. 16 may include a communication unit 1601 and a processing unit 1602. among them:
  • the communication unit 1601 is configured to receive the identifier of the service package and the policy and charging control PCC rule corresponding to the service package from the first device; the processing unit 1602 is configured to convert the PCC rule corresponding to the service package into the packet detection rule PDR; The unit 1601 is also used to send the identifier of the service package and the PDR corresponding to the service package to the third device.
  • the communication unit 1601 is further configured to receive the data analysis result corresponding to the target service package from the data analysis device; the processing unit 1602 is further configured to analyze the target service package according to the data analysis result corresponding to the target service package Perform flow excitation or flow suppression.
  • the first device is a policy control function PCF entity
  • the communication device is a session management function SMF entity
  • the third device is a user plane function UPF entity
  • the first device is a policy and charging rules function PCRF entity
  • the communication device is a packet data gateway control plane PGW-C entity
  • the third device is a packet data gateway user plane PGW-U entity
  • the first device is a PCRF entity
  • the communication device is a service detection function control plane TDF-C Entity
  • the third device is a service detection function user plane TDF-U entity.
  • the first device is a PCF entity
  • the communication device is an SMF entity
  • the third device is a UPF entity
  • the identifier of the service package is carried in the information element of the corresponding PCC rule and sent to the communication device; or, the first device only sends the identifier of one service package, and the identifier of the service package is carried in the information element of the session rule and sent to the communication device.
  • the first device is a PCRF entity
  • the communication device is a PGW-C entity
  • the third device is a PGW-U entity
  • the first device is a PCRF entity
  • the communication device is a TDF-C entity
  • the third device is a TDF-U entity
  • the service package identifier is carried in the cell of the Charging-Rule-Install message and sent to the communication device; or, when the first device only sends the identifier of one service package, the service package identifier is carried in the credit control response CCA message Or the re-authentication request RAR message is sent to the communication device.
  • the service package identifier is carried in the information element of the PDR corresponding to the service package and sent to the third device; or, when the communication device only sends the identifier of one service package, the service package identifier is carried in The information element of the session establishment request is sent to the third device.
  • FIG. 16 shows a schematic structural diagram of a communication device according to an embodiment of the present application.
  • the communication device shown in FIG. 16 may be used to perform part or all of the functions of the third device in the method embodiments described in FIG. 6 and FIG. 7.
  • the communication device shown in FIG. 16 may be used to perform part or all of the functions of the UPF entity in the method embodiment described in FIG. 8.
  • the communication device shown in FIG. 16 may be used to perform part or all of the functions of the PGW-U entity in the method embodiment described in FIG. 9 above.
  • the communication device shown in FIG. 16 may be used to perform part or all of the functions of the TDF-U entity in the method embodiment described in FIG. 10.
  • the communication device shown in FIG. 16 may include a communication unit 1601 and a processing unit 1602. among them:
  • the communication unit 1601 is used to receive the identifier of the service package and the message detection rule PDR corresponding to the service package from the second device; the processing unit 1602 is used to record the correspondence between the service package and the PDR; the communication unit 1601 is also used to receive data The processing unit 1602 is also used to determine the target packet detection rule PDR matching the data packet; the processing unit 1602 is also used to obtain the target service corresponding to the target PDR according to the recorded correspondence between the service package and the PDR Package.
  • the processing unit 1602 is further configured to perform data statistics based on the target service package according to the data message, and obtain the data statistics result corresponding to the target service package.
  • the communication unit 1601 is further configured to send the data statistics result corresponding to the target service package to the data analysis device.
  • the communication unit 1601 is further configured to receive the data analysis result corresponding to the target service package from the data analysis device;
  • the processing unit 1602 is further configured to perform traffic stimulation or traffic suppression on the target service package according to the data analysis result corresponding to the target service package.
  • the second device is a session management function SMF entity, and the communication device is a user plane function UPF entity; or, the second device is a packet data gateway control plane PGW-C entity, and the communication device is a packet data gateway User plane PGW-U entity; or, the second device is a service detection function control plane TDF-C entity, and the communication device is a service detection function user plane TDF-U entity.
  • the service package identifier is carried in the information element of the PDR corresponding to the service package and sent to the communication device, or when the second device only sends the identifier of one service package, the service package identifier is carried in The cell of the session establishment request is sent to the communication device.
  • FIG. 16 shows a schematic structural diagram of a communication device according to an embodiment of the present application.
  • the communication device shown in FIG. 16 may be used to perform part or all of the functions of the second device in the method embodiments described in FIG. 11 and FIG. 12.
  • the communication device shown in FIG. 16 may be used to perform part or all of the functions of the PGW entity in the method embodiment described in FIG. 13.
  • the communication device shown in FIG. 16 may be used to perform part or all of the functions of the TDF entity in the method embodiments described in FIG. 14 and FIG. 15.
  • the communication device shown in FIG. 16 may include a communication unit 1601 and a processing unit 1602. among them:
  • the communication unit 1601 is used to receive the identifier of the service package and the PCC rule corresponding to the service package from the first device; the processing unit 1602 is used to record the correspondence between the service package and the PCC rule; the communication unit 1601 is also used to receive data packets The processing unit 1602 is also used to determine the target PCC rule matching the data message; the processing unit 1602 is also used to obtain the target business package corresponding to the target PCC rule according to the recorded correspondence between the PCC rule and the business package.
  • the processing unit 1602 is further configured to perform data statistics based on the target service package according to the data message to obtain the data statistics result.
  • the communication unit 1601 is further configured to send the data statistics result corresponding to the target service package to the data analysis device.
  • the communication unit 1601 is further configured to receive the data analysis result of the target service package from the data analysis device; the processing unit 1602 is further configured to perform data analysis on the target service package according to the data analysis result corresponding to the target service package. Flow excitation or flow suppression.
  • the first device is a policy and charging rule function PCRF entity, and the communication device is a packet data gateway PGW; or, the first device is a PCRF, and the communication device is a service detection function TDF entity; or, One device is PGW, and the communication device is a TDF entity.
  • the first device is a PCRF entity, and the communication device is a PGW; or, the first device is a PCRF, and the communication device is a TDF entity;
  • the identifier of the service package is carried in the cell of the Charging-Rule-Install message and sent to the communication device; or, the first device only sends the identifier of one service package, and the identifier of the service package is carried in the credit control response CCA message or The re-authentication request RAR message is sent to the communication device in the cell.
  • FIG. 16 shows a schematic structural diagram of a communication device according to an embodiment of the present application.
  • the communication device shown in FIG. 16 may be used to perform part or all of the functions of the data analysis device in the method embodiments described in FIGS. 6-15.
  • the communication device shown in FIG. 16 may include a communication unit 1601 and a processing unit 1602. among them:
  • the communication unit 1601 is used to receive the data statistics result corresponding to the target service package; the processing unit 1602 is used to analyze the data statistics result to obtain the data analysis result corresponding to the target service package; the communication unit 1601 is also used to send the target service package Corresponding data analysis results.
  • FIG. 17 is a schematic structural diagram of a communication device disclosed in an embodiment of the present application.
  • the communication device can be used to implement the communication method described in the foregoing method embodiment.
  • the communication device may be the aforementioned first device or a device for the first device.
  • the device used for the first device may be a chip of the first device.
  • the communication device may be a second device or a device for the second device.
  • the device used for the second device may be a chip of the second device.
  • the communication device may be a third device or a device for the third device.
  • the device for the third device may be a chip of the third device.
  • the communication device includes a processor 1701 and a transceiver 1702.
  • the processor 1701 is connected to the transceiver 1702.
  • the communication device may further include a memory 1703.
  • the memory 1703 is connected to the processor 1701.
  • the processor 1701 can support a communication device to implement the communication method in the embodiment of the present application.
  • the processor 1701 may execute the method executed by the first device in the method embodiment described in FIG. 4 or FIG. 6.
  • the first device may be a PCRF entity or a PCF entity.
  • the operations performed by the processor 1701 may also refer to the related description of the PCRF entity in the embodiment corresponding to FIG. 8, which is not repeated here.
  • the operations performed by the processor 1701 may also refer to related descriptions about the PCF entity in the embodiments corresponding to FIG. 9 and FIG. 10, and details are not described herein.
  • the processor 1701 may execute the method executed by the second device in the method embodiment described in FIG. 6, FIG. 7, FIG. 11, or FIG.
  • the processor 1701 For operations performed by the processor 1701, reference may be made to the related description of the second device in the embodiment corresponding to FIG. 6, FIG. 7, FIG. 11, or FIG. 12, and details are not described herein.
  • the second device may be an SMF entity or a PGW-C entity or a TDF-C entity or a PGW or TDF entity.
  • the operations performed by the processor 1701 may also refer to the related description of the SMF entity in the embodiment corresponding to FIG. 8, which is not repeated here.
  • the operations performed by the processor 1701 can also refer to the related description of the PGW-C entity in the embodiment corresponding to FIG. 9, which will not be repeated here.
  • the operations performed by the processor 1701 may also refer to the related description of the TDF-C entity in the embodiment corresponding to FIG. 10, which is not repeated here.
  • the operations performed by the processor 1701 may also refer to the related description of the PGW in the embodiment corresponding to FIG. 13, which is not repeated here.
  • the operations performed by the processor 1701 may also refer to the related description of TDF in the embodiment corresponding to FIG. 14 or FIG. 15, which is not repeated here.
  • the processor 1701 may execute the method executed by the third device in the method embodiment described in FIG. 6 or FIG. 7.
  • the third device may be a UPF entity or a PGW-U entity or a TDF-U entity.
  • the operations performed by the processor 1701 can also refer to the related description of the UPF entity in the embodiment corresponding to FIG. 8, which is not repeated here.
  • the operations performed by the processor 1701 may also refer to the related description of the PGW-U entity in the embodiment corresponding to FIG. 9, which is not repeated here.
  • the operations performed by the processor 1701 may also refer to the related description of the TDF-U entity in the embodiment corresponding to FIG. 10, which will not be repeated here.
  • the processor 1701 may be a central processing unit (CPU), a general-purpose processor, a coprocessor, a digital signal processor (digital signal processor, DSP), an application-specific integrated circuit (ASIC), on-site Field programmable gate array (FPGA) or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof.
  • the processor 1701 may also be a combination that implements computing functions, for example, it includes a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the transceiver 1702 may include an antenna and a radio frequency circuit connected to the antenna.
  • the transceiver 1702 is used to communicate with other network elements.
  • the transceiver 1702 may be an interface circuit for the processor to obtain or output information or data.
  • the interface circuit is used for the processor to read or write data from the memory.
  • the interface circuit is used for the processor 1701 to receive information or data from outside the device, or to send information or data to the outside of the device.
  • the communication device may include a memory 1703 on which a program (or an instruction or code) is stored, and the program may be executed by the processor 1701 so that the processor 1701 executes the communication method described in the foregoing method embodiment.
  • the memory 1703 may also store data.
  • the processor 1701 may also read data (for example, predefined information) stored in the memory 1703. The data may be stored at the same storage address as the program, or the data may be stored at a different storage address from the program. .
  • the processor 1701 and the memory 1703 may be provided separately or integrated together, for example, integrated on a single board or a system on chip (SOC).
  • SOC system on chip
  • the embodiment of the present invention also provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when it runs on a processor, the method flow of the foregoing method embodiment is realized.
  • the embodiment of the present invention also provides a computer program product.
  • the computer program product runs on a processor, the method flow of the above method embodiment is realized.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions may be transmitted from a website, computer, server, or data center.
  • 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 usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • Probability & Statistics with Applications (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例公开了一种一种通信方法及装置，该方法包括：第一设备获取用户签约的业务套餐；第一设备确定该业务套餐对应的策略与计费控制PCC规则；第一设备向第二设备发送该业务套餐的标识和该业务套餐对应的PCC规则。基于本申请实施例，有利于第一设备下的设备准确地确定接收的数据报文所属的业务套餐。

Description

一种通信方法及装置 技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法及装置。
背景技术
图1为4G(第四代移动通信系统)网络架构的示意图。如图1所示，4G网络的核心网中包括策略与计费规则功能(policy and charging rules function，PCRF)实体和分组数据网关(packet data network gateway，PGW)。其中，PCRF实体用于根据用户的签约套餐信息、使用的业务信息等为用户下发策略与计费控制(policy and charging control，PCC)规则。PCC规则是一组用于实现业务数据流检测，并提供相应的策略控制和/或计费控制的参数的信息。通常PGW可用于对业务流进行检测，并执行PCRF实体下发的PCC规则。4G网络的核心网中还可包括业务检测功能(traffic detection function，TDF)实体。TDF实体分别与PCRF实体和PGW连接。TDF实体主要用于执行应用检测，并将检测到的应用信息上报给PCRF实体。
在4G的核心网控制面与用户面分离的系统架构中，服务网关(serving gateway，SGW)、PGW、TDF实体分别被划分为服务网关控制面功能(serving gateway control plane function，SGW-C)实体、PDN网关控制面功能(PDN gateway control plane function，PGW-C)实体、业务检测功能控制面(traffic detection function control plane，TDF-C)实体、服务网关用户面功能(serving gateway user plane function，SGW-U)实体、PDN网关用户面功能(PDN gateway user plane function，PGW-U)实体、业务检测功能用户面(traffic detection function user plane，TDF-U)实体。如图2所示，图2为4G网络中核心网控制面与用户面分离的示意图。控制面功能实体用于对用户面功能实体进行管理，或实现其他非会话级的管理功能。用户面功能实体用于为控制面功能实体提供服务，例如用户面功能实体可根据控制平面下发的控制指令建立会话承载，完成用户数据的转发。在4G的核心网控制面与用户面分离的系统架构中，可由PGW-U实体执行PCRF实体下发的PCC规则。
5G(第五代移动通信系统)网络架构对下一代核心网设备的网络架构又进行了重新调整。如图3所示，图3为基于服务化接口的5G网络的系统架构。其中，策略控制功能(policy control function，PCF)实体用于根据用户的签约套餐信息、使用的业务信息等为用户下发PCC规则。会话管理功能(session management function，SMF)实体，用于对用户面功能实体(user plane function，UPF)进行管理。例如，SMF实体需要负责管理UPF实体的选择，SMF实体还具有策略下发，事件上报，UPF实体心跳检查，UPF实体负荷上报等非会话级的管理功能。UPF实体用于为SMF实体提供服务，例如，UPF可根据SMF下发的控制指令建立会话承载，完成用户数据的转发。UPF实体还可执行PCF实体下发的PCC规制。
PCF实体/PCRF实体可根据用户的业务套餐下发PCC规则到PGW、PGW-C实体或SMF实体等网元实现PCC规则的激活。PGW、PGW-U实体或UPF实体基于用户激活的PCC规则对用户的业务数据流执行PCC规则匹配，并执行匹配成功的PCC规则携带的计费与 控制策略。然而在实践中发现，PCF实体/PCRF实体下的设备(如PGW、PGW-U实体或UPF实体等)无法确定接收的数据报文所属的业务套餐，进而无法基于业务套餐进一步进行相关操作。因此，如何使这些设备能够准确地确定接收的数据报文所属的业务套餐是目前亟待解决的问题。
发明内容
本申请实施例提供了一种通信方法及装置，有利于设备准确地确定接收的数据报文所属的业务套餐。
第一方面，本申请实施例提供了一种通信方法，该方法包括：第一设备获取用户签约的业务套餐；第一设备确定该业务套餐对应的策略与计费控制PCC规则；第一设备向第二设备发送该业务套餐的标识和该业务套餐对应的PCC规则。基于第一方面所描述的方法，有利于第一设备下的设备准确地确定接收的数据报文所属的业务套餐。
作为一种可选的实施方式，第一设备从数据分析设备接收目标业务套餐对应的数据分析结果；第一设备根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发或流量抑制。基于该可选的实施方式，能够根据目标业务套餐对应的数据分析结果灵活地对目标业务套餐的流量进行控制。
作为一种可选的实施方式，第一设备为策略控制功能PCF实体，第二设备为会话管理功能SMF实体；或者，第一设备为策略与计费规则功能PCRF实体，第二设备为分组数据网关控制面PGW-C实体；或者，第一设备为PCRF实体，第二设备为业务检测功能控制面TDF-C实体；或者，第一设备为PCRF实体，第二设备为分组数据网关PGW；或者，第一设备为PCRF实体，第二设备为业务检测功能TDF实体。
作为一种可选的实施方式，第一设备为PCF实体，第二设备为SMF实体；业务套餐的标识携带于对应的PCC规则的信元中发送至第二设备；或者，第一设备只发送一个业务套餐的标识，业务套餐的标识携带于会话规则的信元中发送至第二设备。基于该可选的实施方式，有利于SMF实体能够准确地确定业务套餐与PCC规则的对应关系。
作为一种可选的实施方式，第一设备为PCRF实体，第二设备为PGW-C实体；或者，第一设备为PCRF实体，第二设备为TDF-C实体；或者，第一设备为PCRF实体，第二设备为PGW；或者，第一设备为PCRF实体，第二设备为TDF实体；业务套餐的标识携带于计费规则安装Charging-Rule-Install消息的信元中发送至第二设备；或者，第一设备只发送一个业务套餐的标识，业务套餐的标识携带于信用控制响应CCA消息或重新鉴权请求RAR消息的信元中发送至第二设备。基于该可选的实施方式，有利于第二设备能够准确地确定业务套餐与PCC规则的对应关系。
第二方面，本申请实施例提供了一种通信方法，该方法包括：第二设备从第一设备接收业务套餐的标识和业务套餐对应的策略与计费控制PCC规则；第二设备将业务套餐对应的PCC规则转换为报文探测规则PDR；第二设备发送业务套餐的标识和业务套餐对应的PDR至第三设备。基于第二方面所描述的方法，有利于第一设备下的设备准确地确定接收的数据报文所属的业务套餐。
作为一种可选的实施方式，第二设备从数据分析设备接收目标业务套餐对应的数据分 析结果；第二设备根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发或流量抑制。基于该可选的实施方式，能够根据目标业务套餐对应的数据分析结果灵活地对目标业务套餐的流量进行控制。
作为一种可选的实施方式，第一设备为策略控制功能PCF实体，第二设备为会话管理功能SMF实体，第三设备为用户面功能UPF实体；或者，第一设备为策略与计费规则功能PCRF实体，第二设备为分组数据网关控制面PGW-C实体，第三设备为分组数据网关用户面PGW-U实体；或者，第一设备为PCRF实体，第二设备为业务检测功能控制面TDF-C实体，第三设备为业务检测功能用户面TDF-U实体。
作为一种可选的实施方式，第一设备为PCF实体，第二设备为SMF实体，第三设备为UPF实体；业务套餐的标识携带于对应的PCC规则的信元中发送至第二设备；或者，第一设备只发送一个业务套餐的标识，业务套餐的标识携带于会话规则的信元中发送至第二设备。基于该可选的实施方式，SMF实体能够准确地确定业务套餐与PCC规则的对应关系。
作为一种可选的实施方式，第一设备为PCRF实体，第二设备为PGW-C实体，第三设备为PGW-U实体；或者，第一设备为PCRF实体，第二设备为TDF-C实体，第三设备为TDF-U实体；业务套餐的标识携带于计费规则安装Charging-Rule-Install消息的信元中发送至第二设备；或者，第一设备只发送一个业务套餐的标识时，该业务套餐的标识携带于信用控制响应CCA消息或重新鉴权请求RAR消息的信元中发送至第二设备。基于该可选的实施方式，第二设备能够准确地确定业务套餐与PCC规则的对应关系。
作为一种可选的实施方式，业务套餐的标识携带于业务套餐对应的PDR的信元中发送至第三设备；或者，第二设备只发送的一个业务套餐的标识时，该业务套餐的标识携带于会话建立请求的信元中发送至第三设备。基于该可选的实施方式，有利于第三设备能够准确地确定业务套餐与PDR的对应关系。
第三方面，本申请实施例提供了一种通信方法，该方法包括：第三设备从第二设备接收业务套餐的标识和业务套餐对应的报文探测规则PDR；第三设备记录业务套餐与PDR的对应关系；第三设备接收数据报文；第三设备确定与数据报文匹配的目标报文探测规则PDR；第三设备根据记录的业务套餐与PDR的对应关系，获取与目标PDR对应的目标业务套餐。基于第三方面所描述的方法，第三设备能够准确地确定接收的数据报文所属的业务套餐。
作为一种可选的实施方式，第三设备根据数据报文，基于目标业务套餐进行数据统计，得到目标业务套餐对应的数据统计结果。基于该可选的实施方式，第三设备能够基于目标业务套餐进行数据统计。
作为一种可选的实施方式，第三设备发送目标业务套餐对应的数据统计结果至数据分析设备。
作为一种可选的实施方式，第三设备从数据分析设备接收目标业务套餐对应的数据分析结果；第三设备根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发或流量抑制。基于该可选的实施方式，能够根据目标业务套餐对应的数据分析结果灵活地对目标业务套餐的流量进行控制。
作为一种可选的实施方式，第二设备为会话管理功能SMF实体，第三设备为用户面功能UPF实体；或者，第二设备为分组数据网关控制面PGW-C实体，第三设备为分组数据网关用户面PGW-U实体；或者，第二设备为业务检测功能控制面TDF-C实体，第三设备为业务检测功能用户面TDF-U实体。
作为一种可选的实施方式，业务套餐的标识携带于业务套餐对应的PDR的信元中发送至第三设备，或者，第二设备只发送的一个业务套餐的标识时，业务套餐的标识携带于会话建立请求的信元中发送至第三设备。基于该可选的实施方式，第三设备能够准确地确定业务套餐与PDR的对应关系。
第四方面，本申请实施例提供了一种通信方法，该方法包括：第二设备从第一设备接收业务套餐的标识和业务套餐对应的PCC规则；第二设备记录业务套餐和PCC规则的对应关系；第二设备接收数据报文；第二设备确定与数据报文匹配的目标PCC规则；第二设备根据记录的PCC规则与业务套餐的对应关系，获取与目标PCC规则对应的目标业务套餐。基于第四方面所描述的方法，第二设备能够准确地确定接收的数据报文所属的业务套餐。
作为一种可选的实施方式，第二设备根据数据报文，基于目标业务套餐进行数据统计，得到数据统计结果。基于该可选的实施方式，第三设备能够基于目标业务套餐进行数据统计。
作为一种可选的实施方式，第二设备发送目标业务套餐对应的数据统计结果至数据分析设备。
作为一种可选的实施方式，第二设备从数据分析设备接收目标业务套餐的数据分析结果；第二设备根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发或流量抑制。基于该可选的实施方式，能够根据目标业务套餐对应的数据分析结果灵活地对目标业务套餐的流量进行控制。
作为一种可选的实施方式，第一设备为策略与计费规则功能PCRF实体，第二设备为分组数据网关PGW；或者，第一设备为PCRF，第二设备为业务检测功能TDF实体；或者，第一设备为PGW，第二设备为TDF实体。
作为一种可选的实施方式，第一设备为PCRF实体，第二设备为PGW；或者，第一设备为PCRF，第二设备为TDF实体；业务套餐的标识携带于计费规则安装Charging-Rule-Install消息的信元中发送至第二设备；或者，第一设备只发送一个业务套餐的标识，业务套餐的标识携带于信用控制响应CCA消息或重新鉴权请求RAR消息的信元中发送至第二设备。基于该可选的实施方式，第二设备能够准确地确定业务套餐与PCC规则的对应关系。
第五方面，本申请实施例提供了一种通信方法，该方法包括：数据分析设备接收目标业务套餐对应的数据统计结果；数据分析设备对数据统计结果进行分析，得到目标业务套餐对应的数据分析结果；数据分析设备发送目标业务套餐对应的数据分析结果。基于该可选的实施方式，能够对目标业务套餐对应的数据统计结果进行数据分析。
第六方面，提供了一种通信装置，该通信装置可以为第一设备或用于第一设备的装置。例如，用于第一设备的装置可以为第一设备内的芯片。该通信装置可执行上述第一方面和 第一方面的可选的实施方式中任意一项所描述的方法。该通信装置的功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元。该单元可以是软件和/或硬件。该通信装置执行的操作及有益效果可以参见上述第一方面和第一方面的可选的实施方式中任意一项所描述的方法以及有益效果，重复之处不再赘述。
第七方面，提供了一种通信装置，该通信装置可以为第二设备或用于第二设备的装置。例如，用于第二设备的装置可以为第二设备内的芯片。该通信装置可执行上述第二方面、第四方面、第一方面的可选的实施方式和第四方面的可选的实施方式中任意一项所描述的方法。该通信装置的功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元。该单元可以是软件和/或硬件。该通信装置执行的操作及有益效果可以参见上述第二方面、第四方面、第一方面的可选的实施方式和第四方面的可选的实施方式中任意一项所描述的方法以及有益效果，重复之处不再赘述。
第八方面，提供了一种通信装置，该通信装置可以为第三设备或用于第三设备的装置。例如，用于第三设备的装置可以为第三设备内的芯片。该通信装置可执行上述第三方面和第三方面的可选的实施方式中任意一项所描述的方法。该通信装置的功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元。该单元可以是软件和/或硬件。该通信装置执行的操作及有益效果可以参见上述第三方面和第三方面的可选的实施方式中任意一项所描述的方法以及有益效果，重复之处不再赘述。
第九方面，提供了一种通信装置，该通信装置可以为数据分析设备或用于数据分析设备的装置。例如，用于数据分析设备的装置可以为数据分析设备内的芯片。该通信装置可执行上述第五方面和第五方面的可选的实施方式中任意一项所描述的方法。该通信装置的功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元。该单元可以是软件和/或硬件。该通信装置执行的操作及有益效果可以参见上述第五方面和第五方面的可选的实施方式中任意一项所描述的方法以及有益效果，重复之处不再赘述。
第十方面，提供了一种通信装置，该通信装置可以为第一设备或用于第一设备的装置。例如，用于第一设备的装置可以为第一设备内的芯片。该通信装置包括处理器以及收发器。其中，处理器与收发器相连。可选的，该通信装置还包括存储器。处理器与该存储器相连。
一种可选的设计中，当通信装置为第一设备时，收发器可以包括天线以及与天线相连的射频电路。该收发器用于实现通信装置与其他网元之间的通信。
又一种可选的设计中，该通信装置为用于第一设备的装置时，该收发器可以为接口电路，该接口电路用于该处理器获取或者输出信息或数据。例如，该接口电路用于该处理器从存储器读取数据或者写入数据，又如，该接口电路用于该处理器接收来自设备外部的信息或数据，或者向设备外部发送信息或数据。
其中，处理器用于执行上述第一方面和第一方面的可选的实施方式中任意一项的方法。
其中，该存储器用于存储程序，该处理器调用存储在该存储器中的程序以执行上述第 一方面和第一方面的可选的实施方式中任意一项的方法。该处理器所执行的操作及有益效果可以参见上述第一方面和第一方面的可选的实施方式中任意一项所描述的方法以及有益效果，重复之处不再赘述。
第十一方面，提供了一种通信装置，该通信装置可以为第二设备或用于第二设备的装置。例如，用于第二设备的装置可以为第二设备内的芯片。该通信装置包括处理器以及收发器。其中，处理器与收发器相连。可选的，该通信装置还包括存储器。处理器与该存储器相连。
一种可选的设计中，当通信装置为第二设备时，收发器可以包括天线以及与天线相连的射频电路。该收发器用于实现通信装置与其他网元之间的通信。
又一种可选的设计中，该通信装置为用于第二设备的装置时，该收发器可以为接口电路，该接口电路用于该处理器获取或者输出信息或数据。例如，该接口电路用于该处理器从存储器读取数据或者写入数据，又如，该接口电路用于该处理器接收来自设备外部的信息或数据，或者向设备外部发送信息或数据。
其中，处理器用于执行上述第二方面、第四方面、第二方面的可选的实施方式和第四方面的可选的实施方式中任意一项的方法。
其中，该存储器用于存储程序，该处理器调用存储在该存储器中的程序以执行上述第二方面、第四方面、第二方面的可选的实施方式和第四方面的可选的实施方式中任意一项的方法。该处理器所执行的操作及有益效果可以参见上述第二方面、第四方面、第二方面的可选的实施方式和第四方面的可选的实施方式中任意一项所描述的方法以及有益效果，重复之处不再赘述。
第十二方面，提供了一种通信装置，该通信装置可以为第三设备或用于第三设备的装置。例如，用于第三设备的装置可以为第三设备内的芯片。该通信装置包括处理器以及收发器。其中，处理器与收发器相连。可选的，该通信装置还包括存储器。处理器与该存储器相连。
一种可选的设计中，当通信装置为第三设备时，收发器可以包括天线以及与天线相连的射频电路。该收发器用于实现通信装置与其他网元之间的通信。
又一种可选的设计中，该通信装置为用于第三设备的装置时，该收发器可以为接口电路，该接口电路用于该处理器获取或者输出信息或数据。例如，该接口电路用于该处理器从存储器读取数据或者写入数据，又如，该接口电路用于该处理器接收来自设备外部的信息或数据，或者向设备外部发送信息或数据。
其中，处理器用于执行上述第三方面和第三方面的可选的实施方式中任意一项的方法。
其中，该存储器用于存储程序，该处理器调用存储在该存储器中的程序以执行上述第三方面和第三方面的可选的实施方式中任意一项的方法。该处理器所执行的操作及有益效果可以参见上述第三方面和第三方面的可选的实施方式中任意一项所描述的方法以及有益效果，重复之处不再赘述。
第十三方面，提供了一种通信装置，该通信装置可以为数据分析设备或用于数据分析设备的装置。例如，用于数据分析设备的装置可以为数据分析设备内的芯片。该通信装置包括处理器以及收发器。其中，处理器与收发器相连。可选的，该通信装置还包括存储器。 处理器与该存储器相连。
一种可选的设计中，当通信装置为数据分析设备时，收发器可以包括天线以及与天线相连的射频电路。该收发器用于实现通信装置与其他网元之间的通信。
又一种可选的设计中，该通信装置为用于数据分析设备的装置时，该收发器可以为接口电路，该接口电路用于该处理器获取或者输出信息或数据。例如，该接口电路用于该处理器从存储器读取数据或者写入数据，又如，该接口电路用于该处理器接收来自设备外部的信息或数据，或者向设备外部发送信息或数据。
其中，处理器用于执行上述第五方面和第五方面的可选的实施方式中任意一项的方法。
其中，该存储器用于存储程序，该处理器调用存储在该存储器中的程序以执行上述第五方面和第五方面的可选的实施方式中任意一项的方法。该处理器所执行的操作及有益效果可以参见上述第五方面和第五方面的可选的实施方式中任意一项所描述的方法以及有益效果，重复之处不再赘述。
第十四方面，提供了一种计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面、第二方面、第三方面、第四方面、第五方面、第一方面的可选的实施方式、第二方面的可选的实施方式、第三方面的可选的实施方式、第四方面的可选的实施方式和第五方面的可选的实施方式中任意一项的方法。
第十五方面，提了供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述第一方面、第二方面、第三方面、第四方面、第五方面、第一方面的可选的实施方式、第二方面的可选的实施方式、第三方面的可选的实施方式、第四方面的可选的实施方式和第五方面的可选的实施方式中任意一项的方法。
附图说明
图1是现有的一种4G网格的系统架构的示意图；
图2是现有的一种核心网控制面与用户面分离的系统架构的示意图；
图3是现有的一种基于服务化接口的5G网络的系统架构的示意图；
图4是本申请实施例提供的一种通信系统的示意图；
图5是本申请实施例提供的另一种通信系统的示意图；
图6～图15是本申请实施例提供的通信方法的流程示意图；
图16是本申请实施例提供的一种通信装置的结构示意图；
图17是本申请实施例提供的另一种通信装置的结构示意图。
具体实施方式
下面结合附图对本申请具体实施例作进一步的详细描述。
本申请实施例提供了一种通信方法及装置，能够使核心网设备确定接收的数据报文所属的业务套餐。
为了能够更好地理解本申请实施例，下面对本申请实施例可应用的系统架构进行说明。
图4是本申请实施例提供的一种通信系统的示意图。如图4所示，该通信系统包括第 一设备、第二设备、第三设备和数据分析设备。其中，第一设备与第二设备通过无线的方式相连。第二设备和第三设备通过无线的方式相连。数据分析设备与第三设备通过无线的方式相连。可选的，数据分析设备还可通过无线的方式与第一设备和/或第二设备相连。图4只是本申请实施提供的一种通信系统的示意图，图4以通信系统中包括第一设备、第二设备、第三设备和数据分析设备为例。当然，通信系统中还可以包括其他设备，本申请实施例不做限定。
其中，数据分析设备可以为网络数据分析功能(network data analytics function，NWDAF)实体或用于生成报表的报表系统或其他可以进行数据分析的设备。
其中，第一设备用于生成并下发策略与计费控制(policy and charging control，PCC)规则。第二设备为控制面设备。第三设备为用于执行第一设备下发的PCC规则的用户面设备。
图4所示的通信系统应用于控制面与用户面相分离的场景。例如，图4所示的通信系统可以应用于以下应用场景1～应用场景3中的任意一种：
应用场景1：第一设备为策略控制功能(policy control function，PCF)实体，第二设备为会话管理功能(session management function，SMF)实体，第三设备为用户面功能(user plane function，UPF)实体。其中，PCF实体用于根据用户的签约套餐信息、使用的业务信息等为用户下发策略与计费控制(policy and charging control，PCC)规则。UPF实体用于执行PCF实体下发的PCC规则。
可选的，在应用场景1中，通信系统还可以包括图3中网络切片选择功能(network slice selection function，NSSF)实体、网络能力开放功能(network exposure function，NEF)实体、网络功能仓库(NE repository function，NRF)实体、统一数据管理(unified data management，UDM)实体、应用功能(application function，AF)实体、认证服务器功能(authentication server function，AUSF)、接入和移动性管理功能实体(access and mobility management function，AMF)、用户终端设备(user equipment，UE)、无线接入网(radio access network，RAN)和数据网络(data network，DN)等。
应用场景2：第一设备为策略与计费规则功能(policy and charging rules function，PCRF)实体，第二设备为PDN网关控制面功能(PDN gateway control plane function，PGW-C)实体，第三设备为PDN网关用户面功能(PDN gateway user plane function，PGW-U)实体。其中，PCRF实体用于根据用户的签约套餐信息、使用的业务信息等为用户下发策略与计费控制(policy and charging control，PCC)规则。PGW-U实体用于执行PCRF实体下发的PCC规则。
可选的，在应用场景2中，通信系统还可以包括图2中服务网关控制面功能(serving gateway control plane function，SGW-C)实体、服务网关用户面功能(serving gateway user plane function，SGW-U)实体、业务检测功能控制面(traffic detection function control plane，TDF-C)实体和业务检测功能用户面(traffic detection function user plane，TDF-U)实体等。
应用场景3：第一设备为PCRF实体，第二设备为TDF-C实体，第三设备为TDF-U实体。其中，PCRF实体用于根据用户的签约套餐信息、使用的业务信息等为用户下发策略与计费控制(policy and charging control，PCC)规则。TDF-U实体用于执行PCRF实体下发 的PCC规则。可选的，在应用场景3中，通信系统还可以包括图2中SGW-C实体、SGW-U实体、PGW-C实体和PGW-U实体等。
图5是本申请实施例提供的另一种通信系统的示意图。如图5所示，该通信系统包括第一设备、第二设备和数据分析设备。其中，第一设备与第二设备通过无线的方式相连。数据分析设备与第二设备通过无线的方式相连。可选的，数据分析设备还可通过无线的方式与第一设备相连。图5只是本申请实施提供的一种通信系统的示意图，图5以通信系统中包括第一设备、第二设备和数据分析设备为例。当然，通信系统中还可以包括其他设备，本申请实施例不做限定。
其中，数据分析设备可以为网络数据分析功能(network data analytics function，NWDAF)实体或用于生成报表的报表系统或其他可以进行数据分析的设备。
图5所示的通信系统应用于控制面与用户面相未分离的场景。例如，图5所示的通信系统可以应用于以下应用场景4和应用场景5中的任意一种：
应用场景4：第一设备为PCRF实体，第二设备为PGW。可选的，在应用场景4中，图5所示的通信系统还可包括图1中除PCRF实体和PGW之外的设备。
应用场景5：第一设备为PCRF实体，第二设备为TDF实体。可选的，在应用场景5中，图5所示的通信系统还可包括图1中除PCRF实体之外的设备。
本申请实施例中出现的“多个”是指两个或两个以上。
本申请实施例中出现的第一、第二等描述，仅作示意与区分描述对象之用，没有次序之分，也不表示本申请实施例中对设备个数的特别限定，不能构成对本申请实施例的任何限制。
本申请实施例中出现的“连接”是指直接连接或者间接连接等各种连接方式，以实现设备间的通信，本申请实施例对此不做任何限定。
本申请实施例中出现的“网络”与“系统”表达的是同一概念，通信系统即为通信网络。
下面进一步对本申请所提供的通信方法及装置进行介绍。
基于图4所描述的通信系统，请参见图6，图6是本申请实施例提供的一种通信方法的流程示意图。其中，步骤601～步骤603的执行主语为第一设备，或者为第一设备中的芯片。步骤604和步骤605的执行主语为第二设备，或者为第二设备中的芯片。步骤606～步骤609的执行主语为第三设备，或者为第三设备中的芯片。以下以第一设备、第二设备以及第三设备为方法的执行主体为例进行说明。如图6所示，该通信方法包括如下步骤601～步骤609，其中：
601、第一设备获取用户签约的业务套餐。
图6所示的通信方法可以应用于上述应用场景1～应用场景3中的任意一个应用场景。即图6中第一设备可以为PCF实体，第二设备可以为SMF实体，第三设备可以为UPF实体。或者，第一设备可以为PCRF实体，第二设备可以为PGW-C实体，第三设备可以为PGW-U实体。或者，第一设备可以为PCRF实体，第二设备可以为TDF-C实体，第三设备可以为TDF-U实体。当然，第一设备还可以为其他用于下发PCC规则的实体。第二设备还可以为其他控制面设备。第三设备还可以为其他用户面设备，本申请实施例不做限定。
其中，第一设备中记录有用户签约的业务套餐。每个用户可以签约一个或多个业务套餐。第一设备可根据用户当前的属性或状态从用户已签约的业务套餐中获取一个或多个业务套餐。例如，用户签约了3个业务套餐。业务套餐1为一个月20元钱，20G通用流量。业务套餐2为一个月20元钱，30G应用1的流量，20G应用2的流量。业务套餐3为一个月10元钱，10G应用3的流量，10G应用4的流量。第一设备根据用户当前的属性或状态从这3个业务套餐中获取1个业务套餐，或者获取2个业务套餐，或者获取3个业务套餐。
602、第一设备确定该业务套餐对应的策略与计费控制(policy and charging control，PCC)规则。
其中，第一设备存储有业务套餐与PCC规则的对应关系。PCC规则是一组用于实现业务数据流检测，并提供相应的策略控制和/或计费控制的参数的信息。PCC规则包括业务数据流检测信息，并包括策略控制信息和/或计费相关信息。例如，业务数据流检测信息可以包括业务数据流模板。业务数据流检测信息用于匹配数据报文。策略控制信息用于对与业务数据流检测信息相匹配的数据报文进行策略控制。计费相关信息用于对与业务数据流检测信息相匹配的数据报文进行计费。
可选的，该PCC规则可以是动态PCC规则或预定义PCC规则(charging rule name，CRN)或PCC规则组(charging rule basename，CRBN)。
动态PCC规则是第一设备下发给第三设备的规则。动态PCC规则有两种：一种是在第一设备上预先配置的，另一种是在第一设备上动态生成的。
预定义PCC规则是在第三设备上预先配置的，这些规则可以被第一设备引用。
一个PCC规则组可包括多个PCC规则。PCC规则组是在第三设备上预先配置的，PCC规则组可以被第一设备引用。
其中，一个业务套餐可对应一个或多个PCC规则。一个PCC规则也可对应一个或多个业务套餐。例如，第一设备中存储的业务套餐与PCC规则的对应关系如下表1所示。业务套餐1对应动态PCC规则1，业务套餐2对应动态PCC规则2和预定义PCC规则2，业务套餐3对应动态PCC规则3、预定义PCC规则3和PCC规则组3。
表1
Figure PCTCN2020089808-appb-000001
本申请实施例中，第一设备获取业务套餐之后，根据预存的业务套餐与PCC规则的对应关系，确定与获取的业务套餐相对应的PCC规则。例如，如果第一设备获取业务套餐1，则第一设备确定与业务套餐1对应的PCC规则为动态PCC规则1。第一设备向第二设备发送业务套餐1的标识和动态PCC规则1。
如果第一设备获取业务套餐1和业务套餐2，则第一设备确定与业务套餐1对应的PCC规则为动态PCC规则1，并确定与业务套餐2对应的PCC规则为动态PCC规则2和预定义PCC规则2。第一设备向第二设备发送业务套餐1的标识和与业务套餐1对应的动态PCC 规则1，以及业务套餐2的标识和与业务套餐2对应的动态PCC规则2和预定义PCC规则2。
如果第一设备获取业务套餐1、业务套餐2和业务套餐3，则第一设备确定与业务套餐1对应的PCC规则为动态PCC规则1，并确定与业务套餐2对应的PCC规则为动态PCC规则2和预定义PCC规则2，并确定与业务套餐3对应的PCC规则为动态PCC规则3、预定义PCC规则3和PCC规则组3。第一设备向第二设备发送业务套餐1的标识和与业务套餐1对应的动态PCC规则1，以及业务套餐2的标识和与业务套餐2对应的动态PCC规则2和预定义PCC规则2，以及业务套餐3的标识和与业务套餐3对应的动态PCC规则3、预定义PCC规则3和PCC规则组3。
603、第一设备向第二设备发送业务套餐的标识和该业务套餐对应的PCC规则。
本申请实施例中，第一设备获取用户签约的业务套餐和业务套餐对应的PCC规则之后，向第二设备发送业务套餐的标识和业务套餐对应的PCC规则。第一设备向第二设备发送业务套餐对应的PCC规则的目的是激活该业务套餐对应的PCC规则。其中，业务套餐的标识可以为业务套餐的名称或ID(Identity document)。
604、第二设备将业务套餐对应的PCC规则转换为报文探测规则(packet detection rule，PDR)。
本申请实施例中，第二设备从第一设备接收业务套餐的标识和业务套餐对应的PCC规则之后，第二设备将业务套餐对应的PCC规则转换为PDR。可选的，第二设备还可存储业务套餐的标识和PCC规则的对应关系。
可选的，该PDR中可包括一个或多个包检测信息(packet detection information，PDI)、一个或多个PDR标识以及每个PDR标识对应的处理规则的标识。该处理规则包括转发动作规则(forwarding action rule，FAR)、使用量上报规则(usage reporting rule，URR)和QoS执行规则(QoS enforcement rule，QER)中的至少一个处理规则。
605、第二设备发送业务套餐的标识和该业务套餐对应的PDR至第三设备。
本申请实施例中，第二设备将业务套餐对应的PCC规则转换为PDR之后，发送业务套餐的标识和业务套餐对应的PDR至第三设备。例如，业务套餐1对应动态PCC规则1。第二设备接收业务套餐1的标识和动态PCC规则1之后，将动态PCC规则1转换为PDR，并向第三设备发送业务套餐1的标识和该PDR。第三设备接收业务套餐1的标识和该PDR之后，记录业务套餐1与该PDR的对应关系。
作为一种可选的实施方式，业务套餐的标识携带于业务套餐对应的PDR的信元中发送至第三设备；或者，第二设备只发送的一个业务套餐的标识时，该业务套餐的标识携带于会话建立请求的信元中发送至第三设备。基于该可选的实施方式，第三设备能够准确地确定业务套餐与PDR的对应关系。
606、第三设备记录业务套餐与PDR的对应关系。
本申请实施例中，第三设备从第二设备接收业务套餐的标识和业务套餐对应的PDR之后，第三设备记录该业务套餐与该PDR的对应关系。
607、第三设备接收数据报文。
具体地，第三设备记录业务套餐与PDR的对应关系之后，接收数据报文。
其中，该数据报文可以是上行的数据报文或者是下行的数据报文。
608、第三设备确定与该数据报文匹配的目标PDR。
本申请实施例中，第三设备接收数据报文之后，确定与该数据报文匹配的目标PDR。
具体地，第三设备将该数据报文的属性信息与PDR中的包检测信息进行匹配。如果匹配成功，则确定该数据报文与该PDR相匹配。
例如，第三设备中激活了用户1的PDR1和PDR2。其中，PDR1对应业务套餐1，PDR2对应业务套餐2。第三设备接收到用户1访问的数据报文之后，将该数据报文的属性信息与PDR1和PDR2中的包检测信息进行匹配。如果该数据报文的属性信息与PDR1中的包检测信息相匹配，则该数据报文与该PDR1匹配。因此，PDR1为目标PDR。第三设备根据预先记录的业务套餐与PDR的对应关系，确定PDR1对应业务套餐1。
609、第三设备根据记录的业务套餐与PDR的对应关系，获取与目标PDR对应的目标业务套餐。
其中，获取的目标业务套餐就为第三设备接收的数据报文所属的业务套餐。可见，通过实施图6所描述的方法，有利于设备准确地确定接收的数据报文所属的业务套餐。
第三设备获取与目标PDR对应的目标业务套餐之后，能够基于业务套餐执行相关操作。
以下介绍第三设备基于业务套餐可执行的相关操作的流程。
请参见图7，如图7所示，图7是本申请实施例提供的另一种通信方法的流程示意图。其中，步骤701～步骤709的具体实施方式与上述步骤601～步骤609的具体实施方式相同，在此不赘述。如图7所示，第三设备获取与目标PDR对应的目标业务套餐之后，还可执行以下步骤710～步骤714。其中：
710、第三设备根据数据报文，基于目标业务套餐进行数据统计，得到目标业务套餐对应的数据统计结果。
例如，目标PDR为PDR1，与目标PDR对应的目标业务套餐为业务套餐1。第三设备根据数据报文，基于业务套餐1进行数据统计，得到数据统计结果。可选的，第三设备还可执行PDR1中定义的计费与控制策略。当然，第三设备也可不执行步骤710，第三设备可基于目标业务套餐执行其他操作，本申请实施例不做限定。
可选的，数据统计结果可以包括使用业务套餐1的用户数、业务套餐1的流量使用信息、业务套餐1的时长使用信息、业务套餐1下的各应用的流量使用信息、业务套餐1下的各应用的时长使用信息和在业务套餐1下共享热点的用户数等中的一项或多项。
作为一种可选的实施方式，业务套餐1的流量使用信息可以为业务套餐1的流量使用量。例如，该业务套餐1的流量使用量可以为所有用户对业务套餐1的流量使用总量，即第三设备可统计所有用户对业务套餐1的流量使用总量。或者，业务套餐1的流量使用信息可以为业务套餐1的流量使用量占比。例如，第三设备中总共有10个业务套餐。如果所有用户对业务套餐1的流量使用总量为10个G。10个业务套餐的流量使用总量一共为200G，则业务套餐1的流量使用量占比为1/20。
作为一种可选的实施方式，业务套餐1的时长使用信息可以为业务套餐1的使用时长。例如，该业务套餐1的使用时长可以为所有用户对业务套餐1的总使用时长，即第三设备可统计所有用户对业务套餐1的总使用时长。或者，业务套餐1的时长使用信息可以为业 务套餐1的使用时长占比。例如，第三设备中总共有10个业务套餐。如果所有用户对业务套餐1的总使用时长为100个小时。10个业务套餐的总使用时长一共为2000小时，则业务套餐1的使用时长占比为1/20。
作为一种可选的实施方式，业务套餐1下的各应用的流量使用信息可以为业务套餐1下的各应用的流量使用量。例如，业务套餐1下的各应用的流量使用量可以为所有用户对该业务套餐1的各应用的流量使用总量，即第三设备可统计所有用户对业务套餐1的各应用的流量使用总量。例如，用户1在业务套餐1下使用应用1的流量为10G，使用应用2的流量为20G。用户2在业务套餐1下使用应用1的流量为20G，使用应用2的流量为20G。第三设备可统计得到在业务套餐1下应用1的流量使用总量为30G，应用2的流量使用总量为40G。
或者，业务套餐1下的各应用的流量使用信息可以为各应用的流量使用量占比。例如，所有用户在业务套餐1下对应用1的流量使用总量为30G，对应用2的流量使用总量为40G。业务套餐1下应用1的流量使用量占比为3/7，应用2的流量使用量占比为4/7。
作为一种可选的实施方式，业务套餐1下的各应用的时长使用信息可以为业务套餐1下的各应用的使用时长。例如，业务套餐1下的各应用的使用时长可以为所有用户对该业务套餐1的各应用的总使用时长，即第三设备可统计所有用户对业务套餐1的各应用的总使用时长。或者，业务套餐1下的应用时长使用信息可以为应用的使用时长占比。例如，所有用户在业务套餐1下对应用1的总使用时长为100小时，对应用2的使用时长为200小时。业务套餐1下应用1的使用时长占比为1/3，业务套餐1下应用2的使用时长占比为2/3。
其中，第三设备得到目标业务套餐对应的数据统计结果之后，可以执行步骤711。或者，第三设备得到目标业务套餐对应的数据统计结果之后，不执行步骤711，执行其他操作。例如发送数据统计结果至第一设备或第二设备，或者直接对数据统计结果进行分析等等，本申请实施例不做限定。
711、第三设备发送目标业务套餐对应的数据统计结果至数据分析设备。
712、数据分析设备对目标业务套餐对应的数据统计结果进行数据分析，得到目标业务套餐对应的数据分析结果。
其中，数据分析设备接收目标业务套餐对应的数据统计结果之后，对目标业务套餐对应的数据统计结果进行数据分析，得到目标业务套餐对应的数据分析结果。
以目标业务套餐为业务套餐1为例。如前述所述，业务套餐1对应的数据统计结果可以为使用业务套餐1的用户数、业务套餐1的流量使用信息、业务套餐1的时长使用信息、业务套餐1下的各应用的流量使用信息、业务套餐1下的各应用的时长使用信息和在业务套餐1下共享热点的用户数等中的一项或多项。
例如，以数据统计结果包括业务套餐1的流量使用信息为例。如果业务套餐1的流量使用信息为所有用户对业务套餐1的流量使用总量。数据分析设备对业务套餐1对应的数据统计结果进行数据分析，得到业务套餐1对应的数据分析结果的具体实施方式可以为：数据分析设备判断业务套餐1的流量使用总量是否大于第一阈值。得到的判断结果就为数据分析结果。如果业务套餐1的流量使用总量大于第一阈值，说明业务套餐1使用较多， 是主流的业务套餐。或者，数据分析设备对业务套餐1对应的数据统计结果进行数据分析，得到业务套餐1对应的数据分析结果的具体实施方式可以为：数据分析设备按照业务套餐的流量使用总量对所有业务套餐进行排序，得到业务套餐的排序结果。该排序结果为数据分析结果。例如，按照业务套餐的流量使用总量从大到小对所有业务套餐进行排序，排在预设位置之前的业务套餐说明使用较多，是主流的业务套餐。可见，根据数据分析结果就可确定哪些业务套餐是主流的业务套餐，以便进一步对主流的业务套餐进行流量激发或流量抑制。业务套餐1的流量使用信息为业务套餐1的流量使用总量占比同理，在此不赘述。数据统计结果包括使用业务套餐1的用户数、业务套餐1的时长使用信息时，对数据统计结果进行数据分析的具体实施方式同理，在此不赘述。也就是说，通过对使用业务套餐1的用户数、业务套餐1的流量使用信息或业务套餐1的时长使用信息进行数据分析，得到数据分析结果。该数据分析结果可用于确定业务套餐1是否为主流的业务套餐。或者，还可以对使用业务套餐1的用户数、业务套餐1的流量使用信息或业务套餐1的时长使用信息进行其他分析操作，本申请实施例不做限定。
再如，以数据统计结果包括业务套餐1的流量使用信息和业务套餐1下的应用流量使用信息为例。如果业务套餐1的流量使用信息为所有用户对业务套餐1的流量使用总量，业务套餐1下的各应用的流量使用信息为所有用户对该业务套餐1的各应用的流量使用总量。数据分析设备对业务套餐1对应的数据统计结果进行数据分析，得到业务套餐1对应的数据分析结果的具体实施方式可以为：数据分析设备判断业务套餐1的流量使用总量是否大于第一阈值，以及判断该业务套餐1的各应用的流量使用总量是否大于第二阈值。得到的判断结果就为数据分析结果。如果业务套餐1的流量使用总量大于第一阈值，说明业务套餐1使用较多，是主流的业务套餐。如果业务套餐1下的某个应用的流量使用总量大于第二阈值，则表明该应用是业务套餐1下的主流应用。或者，数据分析设备对业务套餐1对应的数据统计结果进行数据分析，得到业务套餐1对应的数据分析结果的具体实施方式可以为：数据分析设备按照业务套餐的流量使用总量对所有业务套餐进行排序，得到业务套餐的第一排序结果。数据分析设备按照业务套餐1的各应用的流量使用总量对业务套餐1的各应用进行排序，得到业务套餐1的各应用的第二排序结果。该第一排序结果和第二排序结果为数据分析结果。可见，根据数据分析结果就可确定哪些业务套餐是主流的业务套餐，业务套餐下的哪些应用为主流应用，以便进一步对主流的业务套餐的主流应用进行流量激发或流量抑制。也就是说，通过对使用业务套餐1的用户数、业务套餐1的流量使用信息或业务套餐1的时长使用信息进行数据分析，以及对业务套餐1下的应用流量使用信息或业务套餐1下的各应用的时长使用信息进行数据分析，得到数据分析结果。该数据分析结果可用于确定业务套餐1是否为主流的业务套餐，以及用于确定业务套餐1下的主流应用。
再如，以数据统计结果包括业务套餐1的流量使用信息和在业务套餐1下共享热点的用户数为例。如果业务套餐1的流量使用信息为所有用户对业务套餐1的流量使用总量。数据分析设备对业务套餐1对应的数据统计结果进行数据分析，得到业务套餐1对应的数据分析结果的具体实施方式可以为：数据分析设备判断业务套餐1的流量使用总量是否大于第一阈值，以及判断在业务套餐1下共享热点的用户数是否大于第三阈值。得到的判断 结果就为数据分析结果。如果业务套餐1的流量使用总量大于第一阈值，说明业务套餐1使用较多，是主流的业务套餐。如果在业务套餐1下共享热点的用户数大于第三阈值，则表明在业务套餐1下共享热点的人数过多。或者，数据分析设备对业务套餐1对应的数据统计结果进行数据分析，得到业务套餐1对应的数据分析结果的具体实施方式可以为：数据分析设备按照业务套餐的流量使用总量对所有业务套餐进行排序，得到业务套餐的第一排序结果。判断在业务套餐1下共享热点的用户数是否大于第三阈值。得到的判断结果和第一排序结果就为数据分析结果。可见，根据该数据分析结果可确定哪些业务套餐是主流的业务套餐，哪些业务套餐的共享热点人数过多，以便进一步对共享热点人数过多的低价值的主流业务套餐进行流量抑制。
当然数据分析设备还可对以上数据统计结果进行其他数据分析操作，例如生成报表等等，本申请实施例不做限定。
713、数据分析设备发送目标业务套餐对应的数据分析结果至第一设备。
714、第一设备根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发或流量抑制。
其中，第一设备从数据分析设备接收目标业务套餐对应的数据分析结果之后，根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发或流量抑制。
作为一种可选的实施方式，如果目标业务套餐为高价值的业务套餐，则第一设备可根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发。高价值的业务套餐是指每比特流量的价格大于阈值的业务套餐。即高价值的业务套餐是指每比特流量的价格较高的业务套餐。
例如，目标业务套餐为高价值的业务套餐，第一设备根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发的具体实施方式为：如果第一设备根据目标业务套餐对应的数据分析结果确定目标业务套餐为主流的业务套餐，则对目标业务套餐进行流量激发。第一设备对目标业务套餐进行流量激发的具体实施方式可以为对目标业务套餐的业务提升QOS或提升传输控制协议(transmission control protocol，TCP)传输层的传输质量等。具体地，第一设备可更新目标业务套餐对应的PCC规则中的参数，以对目标业务套餐的业务提升QOS或提升TCP传输层的传输质量。或者，第一设备可以删除已有的目标业务套餐对应的PCC规则，重新为目标业务套餐生成一个PCC规则，该PCC规则可以对目标业务套餐的业务提升QOS或提升TCP传输层的传输质量。或者，第一设备也可以不删除已有的目标业务套餐对应的PCC规则。第一设备额外可以生成一个叠加规则，该叠加规则可以对目标业务套餐的业务提升QOS或提升TCP传输层的传输质量。
再如，目标业务套餐为高价值的业务套餐，第一设备根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发的具体实施方式为：如果第一设备根据目标业务套餐对应的数据分析结果确定目标业务套餐为主流的业务套餐，并且目标业务套餐下的第一应用为主流应用，则对目标业务套餐下的第一应用进行流量激发。第一设备对目标业务套餐进行流量激发的具体实施方式可以为对目标业务套餐下的第一应用提升QOS或提升传输控制协议(transmission control protocol，TCP)传输层的传输质量等。具体地，第一设备可更新目标业务套餐对应的PCC规则中的参数，以对目标业务套餐下的第一应用提升QOS 或提升TCP传输层的传输质量。或者，第一设备可以删除已有的目标业务套餐对应的PCC规则，重新为目标业务套餐生成一个PCC规则，该PCC规则可以对目标业务套餐下的第一应用提升QOS或提升TCP传输层的传输质量。或者，第一设备也可以不删除已有的目标业务套餐对应的PCC规则。第一设备额外可以生成一个叠加规则，该叠加规则可以对目标业务套餐下的第一应用提升QOS或提升TCP传输层的传输质量。
作为一种可选的实施方式，如果目标业务套餐为低价值的业务套餐，则第一设备可根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量抑制。低价值的业务套餐是指每比特流量的价格小于阈值的业务套餐。即低价值的业务套餐是指每比特流量的价格较低的业务套餐。
例如，目标业务套餐为低价值的业务套餐，第一设备根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量抑制的具体实施方式为：如果第一设备根据目标业务套餐对应的数据分析结果确定目标业务套餐为主流的业务套餐，则第一设备对目标业务套餐进行流量抑制。第一设备对目标业务套餐进行流量抑制的具体实施方式可以为对目标业务套餐的业务降低带宽或降低QOS质量等。具体地，第一设备可更新目标业务套餐对应的PCC规则中的参数，以对目标业务套餐的业务降低带宽或降低QOS质量。或者，第一设备可以删除已有的目标业务套餐对应的PCC规则，重新为目标业务套餐生成一个PCC规则，该PCC规则可以对目标业务套餐的业务降低带宽或降低QOS质量。或者，第一设备也可以不删除已有的目标业务套餐对应的PCC规则。第一设备可以为目标业务套餐生成一个叠加规则，该叠加规则可以对目标业务套餐的业务降低带宽或降低QOS质量。
再如，目标业务套餐为低价值的业务套餐，第一设备根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量抑制的具体实施方式为：如果第一设备根据目标业务套餐对应的数据分析结果确定目标业务套餐为主流的业务套餐，并且目标业务套餐下的第一应用为主流应用，则对目标业务套餐下的第一应用进行流量抑制。第一设备对目标业务套餐下的第一应用进行流量抑制的具体实施方式可以为对目标业务套餐下的第一应用降低带宽或降低QOS质量等。具体地，第一设备可更新目标业务套餐对应的PCC规则中的参数，以对目标业务套餐下的第一应用降低带宽或降低QOS质量。或者，第一设备可以删除已有的目标业务套餐对应的PCC规则，重新为目标业务套餐生成一个PCC规则，该PCC规则可以对目标业务套餐下的第一应用降低带宽或降低QOS质量。或者，第一设备也可以不删除已有的目标业务套餐对应的PCC规则。第一设备可以为目标业务套餐生成一个叠加规则，该叠加规则可以对目标业务套餐下的第一应用降低带宽或降低QOS质量。
再如，目标业务套餐为低价值的业务套餐，第一设备根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量抑制的具体实施方式为：如果第一设备根据目标业务套餐对应的数据分析结果确定目标业务套餐为主流的业务套餐，并且目标业务套餐下共享热点的用户数大于第三阈值，则对目标业务套餐进行流量抑制。第一设备对目标业务套餐进行流量抑制的具体实施方式可以为禁止在目标业务套餐下共享热点。具体地，第一设备可以删除已有的目标业务套餐对应的PCC规则，重新为目标业务套餐生成一个PCC规则，该PCC规则可以禁止在目标业务套餐下共享热点。或者，第一设备也可以不删除已有的目标业务套餐对应的PCC规则。第一设备可以为目标业务套餐生成一个叠加规则，该叠加规则 可以禁止在目标业务套餐下共享热点。
作为一种可选的实施方式，也可不执行步骤713和步骤714。数据分析设备对目标业务套餐对应的数据统计结果进行数据分析，得到目标业务套餐对应的数据分析结果之后，数据分析设备可发送目标业务套餐对应的数据分析结果至第二设备。第二设备从数据分析设备接收目标业务套餐对应的数据分析结果之后，根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发或流量抑制。同理，如果目标业务套餐为高价值的业务套餐，则第二设备可根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发。如果目标业务套餐为低价值的业务套餐，则第二设备可根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量抑制。其中，第二设备可以为目标业务套餐生成一个叠加规则，该叠加规则可以对目标业务套餐进行流量激发或抑制。
作为一种可选的实施方式，也可不执行步骤713和步骤714。数据分析设备对目标业务套餐对应的数据统计结果进行数据分析，得到目标业务套餐对应的数据分析结果之后，数据分析设备可发送目标业务套餐对应的数据分析结果至第三设备。第三设备从数据分析设备接收目标业务套餐对应的数据分析结果之后，根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发或流量抑制。同理，如果目标业务套餐为高价值的业务套餐，则第三设备可根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发。如果目标业务套餐为低价值的业务套餐，则第三设备可根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量抑制。其中，第三设备可以为目标业务套餐生成一个叠加规则，该叠加规则可以对目标业务套餐进行流量激发或抑制。
可见，通过执行图7所描述的方法，能够基于业务套餐进行流量激发或抑制。
下面基于上述应用场景1对本申请所提供的通信方法进一步进行说明。请参见图8，图8是本申请实施例提供的又一种通信方法的流程示意图。其中，步骤801～步骤803和步骤814的执行主语为PCF实体，或者为PCF实体中的芯片。步骤804和步骤805的执行主语为SMF实体，或者为SMF实体中的芯片。步骤806～步骤811的执行主语为UPF实体，或者为UPF实体中的芯片。步骤812和步骤813的执行主语为数据分析设备或者为数据分析设备中的芯片。以下以PCF实体、SMF实体、UPF实体和数据分析设备为方法的执行主体为例进行说明。如图8所示，该通信方法包括如下步骤801～步骤814，其中：
801、PCF实体获取用户签约的业务套餐。
可选的，用户终端可通过RAN或AMF向SMF实体发送会话建立请求。SMF实体接收到该会话建立请求之后，向PCF实体发送Npcf_SMPolicyControl_Create消息。PCF实体接收到Npcf_SMPolicyControl_Create消息之后触发获取用户签约的业务套餐。或者，用户终端可通过RAN或AMF向SMF实体发送会话更新请求。SMF实体接收到该会话更新请求之后，向PCF实体发送Npcf_SMPolicyControl_Update消息。PCF实体接收到Npcf_SMPolicyControl_Update消息之后触发获取用户签约的业务套餐。或者，PCF实体也可主动获取用户签约的业务套餐。或者，还可通过其他方式触发PCF实体获取用户签约的业务套餐。
802、PCF实体确定业务套餐对应的PCC规则。
其中，步骤802的具体实施方式可参见上述步骤602的具体实现方式，在此不赘述。
803、PCF实体向SMF实体发送业务套餐的标识和该业务套餐对应的PCC规则。
作为一种可选的实施方式，业务套餐的标识携带于对应的PCC规则的信元中发送至SMF实体。例如，PCC规则包括的信元可如下所示，其中，信元pccServiceName/pccServiceID表示业务套餐的标识。可选的，业务套餐的标识具体可携带于对应的PCC规则的属性值对(attribute value pairs，AVP)中。基于该可选的实施方式，SMF实体能够准确地确定业务套餐与PCC规则的对应关系。
Figure PCTCN2020089808-appb-000002
Figure PCTCN2020089808-appb-000003
Figure PCTCN2020089808-appb-000004
作为一种可选的实施方式，PCF实体只发送一个业务套餐的标识，该业务套餐的标识携带于会话规则(session rule)的信元中发送至SMF实体。例如，会话规则包括的信元可如下所示，其中，信元sessServiceName/sessServiceID表示业务套餐的标识。可选的，业务套餐的标识具体可携带于对应的会话规则的AVP中。基于该可选的实施方式，SMF实体能够准确地确定业务套餐与PCC规则的对应关系。
Figure PCTCN2020089808-appb-000005
804、SMF实体将业务套餐对应的PCC规则转换为PDR。
具体地，SMF实体接收业务套餐的标识和该业务套餐对应的PCC规则之后，将业务套餐对应的PCC规则转换为PDR。
805、SMF实体发送业务套餐的标识和业务套餐对应的PDR至UPF实体。
作为一种可选的实施方式，业务套餐的标识携带于业务套餐对应的PDR的信元中发送至UPF实体。例如，PDR可包括携带PDR标识的信元、携带FAR ID的信元、携带URR ID的信元、携带QER ID的信元和携带业务套餐的标识的信元等。基于该可选的实施方式，UPF实体能够准确地确定业务套餐与PDR的对应关系。
作为一种可选的实施方式，SMF实体只发送的一个业务套餐的标识时，业务套餐的标识携带于会话建立请求(session establishment request)的信元中发送至UPF实体。例如，会话建立请求可包括携带PDR的信元、携带节点标识(Node ID)的信元和携带业务套餐的标识的信元等。基于该可选的实施方式，UPF实体能够准确地确定业务套餐与PDR的对应关系。
806、UPF实体记录业务套餐与PDR的对应关系。
具体地，UPF实体接收业务套餐的标识和业务套餐对应的PDR之后，记录业务套餐与PDR的对应关系。
807、UPF实体接收数据报文。
808、UPF实体确定与该数据报文匹配的目标PDR。
809、UPF实体根据记录的业务套餐与PDR的对应关系，获取与目标PDR对应的目标业务套餐。
其中，步骤806～步骤809的具体实现方式可参见上述步骤606～步骤609的具体实现方式，在此不赘述。
810、UPF实体根据数据报文，基于目标业务套餐进行数据统计，得到目标业务套餐对应的数据统计结果。
811、UPF实体发送目标业务套餐对应的数据统计结果至数据分析设备。
812、数据分析设备对目标业务套餐对应的数据统计结果进行数据分析，得到目标业务套餐对应的数据分析结果。
813、数据分析设备发送目标业务套餐对应的数据分析结果至PCF实体。
814、PCF实体根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发或流量抑制。
步骤810～步骤814的具体实现方式可参见上述步骤710～步骤714的具体实现方式，在此不赘述。
作为一种可选的实施方式，也可不执行步骤813和步骤814。数据分析设备对目标业务套餐对应的数据统计结果进行数据分析，得到目标业务套餐对应的数据分析结果之后，数据分析设备可发送目标业务套餐对应的数据分析结果至SMF实体。SMF实体从数据分析设备接收目标业务套餐对应的数据分析结果之后，根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发或流量抑制。
作为一种可选的实施方式，也可不执行步骤813和步骤814。数据分析设备对目标业务套餐对应的数据统计结果进行数据分析，得到目标业务套餐对应的数据分析结果之后，数据分析设备可发送目标业务套餐对应的数据分析结果至UPF实体。UPF实体从数据分析设备接收目标业务套餐对应的数据分析结果之后，根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发或流量抑制。
下面基于上述应用场景2对本申请所提供的通信方法进一步进行说明。请参见图9，图9是本申请实施例提供的又一种通信方法的流程示意图。其中，步骤901～步骤903和步骤914的执行主语为PCRF实体，或者为PCRF实体中的芯片。步骤904和步骤905的执行主语为PGW-C实体，或者为PGW-C实体中的芯片。步骤906～步骤911的执行主语为PGW-U实体，或者为PGW-U实体中的芯片。步骤912和步骤913的执行主语为数据分析设备或者为数据分析设备中的芯片。以下以PCRF实体、PGW-C实体、PGW-U实体和数据分析设备为方法的执行主体为例进行说明。如图9所示，该通信方法包括如下步骤901～步骤914，其中：
901、PCRF实体获取用户签约的业务套餐。
可选的，用户终端可通过RAN或移动管理节点(mobility management entity，MME)向PGW-C实体发送会话建立请求。PGW-C实体接收到该会话建立请求之后，向PCRF实体发送CCR-I(credit control request initial)消息。PCRF实体接收到CCR-I消息之后触发获取用户签约的业务套餐。或者，用户终端可通过RAN或MME向PGW-C实体发送会话更新请求。PGW-C实体接收到该会话更新请求之后，向PCRF实体发送CCR-U(credit control request update)消息。PCRF实体接收到CCR-U消息之后触发获取用户签约的业务套餐。或者，PCRF实体也可主动获取用户签约的业务套餐。或者，还可通过其他方式触发PCRF实体获取用户签约的业务套餐。
902、PCRF实体确定业务套餐对应的PCC规则。
其中，步骤902的具体实施方式可参见上述步骤602的具体实现方式，在此不赘述。
903、PCRF实体向PGW-C实体发送业务套餐的标识和该业务套餐对应的PCC规则。
作为一种可选的实施方式，业务套餐的标识携带于计费规则安装Charging-Rule-Install消息的信元中发送至PGW-C实体。例如，该Charging-Rule-Install消息包括的信元可如下所示，其中，信元Service-Name/Service-Identifier表示业务套餐的标识。可选的，业务套餐的标识具体可携带于Charging-Rule-Install消息的AVP中。基于该可选的实施方式，PGW-C实体能够准确地确定业务套餐与PCC规则的对应关系。
Figure PCTCN2020089808-appb-000006
作为一种可选的实施方式，PCRF实体只发送一个业务套餐的标识时，该业务套餐的标识携带于信用控制响应CCA消息或重新鉴权请求(re-auth-request，RAR)消息的信元中发送至PGW-C实体。例如，CCA消息包括的信元可如下所示，其中，信元Service-Name/Service-Identifier表示业务套餐的标识。可选的，业务套餐的标识具体可携带于对应的CCA消息或RAR消息的AVP中。基于该可选的实施方式，PGW-C实体能够准确地确定业务套餐与PCC规则的对应关系。
Figure PCTCN2020089808-appb-000007
904、PGW-C实体将业务套餐对应的PCC规则转换为PDR。
具体地，PGW-C实体接收业务套餐的标识和该业务套餐对应的PCC规则之后，将业务套餐对应的PCC规则转换为PDR。
905、PGW-C实体发送业务套餐的标识和业务套餐对应的PDR至PGW-U实体。
作为一种可选的实施方式，业务套餐的标识携带于业务套餐对应的PDR的信元中发送至PGW-U实体。例如，PDR可包括携带PDR标识的信元、携带FAR ID的信元、携带URR ID的信元、携带QER ID的信元和携带业务套餐的标识的信元等。基于该可选的实施方式，PGW-U实体能够准确地确定业务套餐与PDR的对应关系。
作为一种可选的实施方式，PGW-C实体只发送的一个业务套餐的标识时，业务套餐的标识携带于会话建立请求(session establishment request)的信元中发送至PGW-U实体。例如，会话建立请求可包括携带PDR的信元、携带节点标识(Node ID)的信元和携带业务套餐的标识的信元等。基于该可选的实施方式，PGW-U实体能够准确地确定业务套餐与PDR的对应关系。
906、PGW-U实体记录业务套餐与PDR的对应关系。
具体地，PGW-U实体从PGW-C实体接收业务套餐的标识和业务套餐对应的PDR之后，PGW-U实体记录业务套餐与PDR的对应关系。
907、PGW-U实体接收数据报文。
908、PGW-U实体确定与该数据报文匹配的目标PDR。
909、PGW-U实体根据记录的业务套餐与PDR的对应关系，获取与目标PDR对应的目标业务套餐。
其中，步骤906～步骤909的具体实现方式可参见上述步骤606～步骤609的具体实现方式，在此不赘述。
910、PGW-U实体根据数据报文，基于目标业务套餐进行数据统计，得到目标业务套餐对应的数据统计结果。
911、PGW-U实体发送目标业务套餐对应的数据统计结果至数据分析设备。
912、数据分析设备对目标业务套餐对应的数据统计结果进行数据分析，得到目标业务套餐对应的数据分析结果。
913、数据分析设备发送目标业务套餐对应的数据分析结果至PCRF实体。
914、PCRF实体根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发或流量抑制。
步骤910～步骤914的具体实现方式可参见上述步骤710～步骤714的具体实现方式，在此不赘述。
作为一种可选的实施方式，也可不执行步骤913和步骤914。数据分析设备对目标业务套餐对应的数据统计结果进行数据分析，得到目标业务套餐对应的数据分析结果之后，数据分析设备可发送目标业务套餐对应的数据分析结果至PGW-C实体。PGW-C实体从数据分析设备接收目标业务套餐对应的数据分析结果之后，根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发或流量抑制。
作为一种可选的实施方式，也可不执行步骤913和步骤914。数据分析设备对目标业务套餐对应的数据统计结果进行数据分析，得到目标业务套餐对应的数据分析结果之后，数据分析设备可发送目标业务套餐对应的数据分析结果至PGW-U实体。PGW-U实体从数据分析设备接收目标业务套餐对应的数据分析结果之后，根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发或流量抑制。
下面基于上述应用场景3对本申请所提供的通信方法进一步进行说明。请参见图10，图10是本申请实施例提供的又一种通信方法的流程示意图。其中，步骤1001～步骤1003和步骤1014的执行主语为PCRF实体，或者为PCRF实体中的芯片。步骤1004和步骤1005的执行主语为TDF-C实体，或者为TDF-C实体中的芯片。步骤1006～步骤1011的执行主语为TDF-U实体，或者为TDF-U实体中的芯片。步骤1012和步骤1013的执行主语为数据分析设备或者为数据分析设备中的芯片。以下以PCRF实体、TDF-C实体、TDF-U实体和数据分析设备为方法的执行主体为例进行说明。如图10所示，该通信方法包括如下步骤1001～步骤1014，其中：
1001、PCRF实体获取用户签约的业务套餐。
可选的，用户终端可通过RAN或移动管理节点(mobility management entity，MME)向TDF-C实体发送会话建立请求。TDF-C实体接收到该会话建立请求之后，向PCRF实体发送CCR-I(credit control request initial)消息。PCRF实体接收到CCR-I消息之后触发获取用户签约的业务套餐。或者，用户终端可通过RAN或MME向PGW-C实体发送会话更新请求。TDF-C实体接收到该会话更新请求之后，向PCRF实体发送CCR-U(credit control request update)消息。PCRF实体接收到CCR-U消息之后触发获取用户签约的业务套餐。或者，PCRF实体也可主动获取用户签约的业务套餐。或者，还可通过其他方式触发PCRF实体获取用户签约的业务套餐。
1002、PCRF实体确定业务套餐对应的PCC规则。
其中，步骤1002的具体实施方式可参见上述步骤602的具体实现方式，在此不赘述。
1003、PCRF实体向TDF-C实体发送业务套餐的标识和该业务套餐对应的PCC规则。
作为一种可选的实施方式，业务套餐的标识携带于计费规则安装Charging-Rule-Install消息的信元中发送至TDF-C实体。可选的，业务套餐的标识具体可携带于Charging-Rule-Install消息的AVP中。基于该可选的实施方式，TDF-C实体能够准确地确定业务套餐与PCC规则的对应关系。
作为一种可选的实施方式，PCRF实体只发送一个业务套餐的标识时，该业务套餐的标识携带于信用控制响应CCA消息或重新鉴权请求(re-auth-request，RAR)消息的信元中发送至TDF-C实体。可选的，业务套餐的标识具体可携带于对应的CCA消息或RAR消息的AVP中。基于该可选的实施方式，TDF-C实体能够准确地确定业务套餐与PCC规则的对应关系。
1004、TDF-C实体将业务套餐对应的PCC规则转换为PDR。
具体地，TDF-C实体接收业务套餐的标识和该业务套餐对应的PCC规则之后，将业务套餐对应的PCC规则转换为PDR。
1005、TDF-C实体发送业务套餐的标识和业务套餐对应的PDR至TDF-U实体。
作为一种可选的实施方式，业务套餐的标识携带于业务套餐对应的PDR的信元中发送至TDF-U实体。例如，PDR可包括携带PDR标识的信元、携带FAR ID的信元、携带URR ID的信元、携带QER ID的信元和携带业务套餐的标识的信元等。基于该可选的实施方式，TDF-U实体能够准确地确定业务套餐与PDR的对应关系。
作为一种可选的实施方式，TDF-C实体只发送的一个业务套餐的标识时，业务套餐的标识携带于会话建立请求(session establishment request)的信元中发送至TDF-U实体。例如，会话建立请求可包括携带PDR的信元、携带节点标识(Node ID)的信元和携带业务套餐的标识的信元等。基于该可选的实施方式，TDF-U实体能够准确地确定业务套餐与PDR的对应关系。
1006、TDF-U实体记录业务套餐与PDR的对应关系。
1007、TDF-U实体接收数据报文。
1008、TDF-U实体确定与该数据报文匹配的目标PDR。
1009、TDF-U实体根据记录的业务套餐与PDR的对应关系，获取与目标PDR对应的目标业务套餐。
其中，步骤1006～步骤1009的具体实现方式可参见上述步骤606～步骤609的具体实现方式，在此不赘述。
1010、TDF-U实体根据数据报文，基于目标业务套餐进行数据统计，得到目标业务套餐对应的数据统计结果。
1011、TDF-U实体发送目标业务套餐对应的数据统计结果至数据分析设备。
1012、数据分析设备对目标业务套餐对应的数据统计结果进行数据分析，得到目标业务套餐对应的数据分析结果。
1013、数据分析设备发送目标业务套餐对应的数据分析结果至PCRF实体。
1014、PCRF实体根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发或流量抑制。
步骤1010～步骤1014的具体实现方式可参见上述步骤710～步骤714的具体实现方式，在此不赘述。
作为一种可选的实施方式，也可不执行步骤1013和步骤1014。数据分析设备对目标业务套餐对应的数据统计结果进行数据分析，得到目标业务套餐对应的数据分析结果之后，数据分析设备可发送目标业务套餐对应的数据分析结果至TDF-C实体。TDF-C实体从数据分析设备接收目标业务套餐对应的数据分析结果之后，根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发或流量抑制。
作为一种可选的实施方式，也可不执行步骤1013和步骤1014。数据分析设备对目标业务套餐对应的数据统计结果进行数据分析，得到目标业务套餐对应的数据分析结果之后，数据分析设备可发送目标业务套餐对应的数据分析结果至TDF-U实体。TDF-U实体从数据分析设备接收目标业务套餐对应的数据分析结果之后，根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发或流量抑制。
基于图5所描述的通信系统，请参见图11，图11是本申请实施例提供的又一种通信方法的流程示意图。其中，步骤1101～步骤1103的执行主语为第一设备，或者为第一设备中的芯片。步骤1104～步骤1107的执行主语为第二设备，或者为第二设备中的芯片。以下以第一设备和第二设备为方法的执行主体为例进行说明。如图11所示，该通信方法包括如下步骤1101～步骤1107，其中：
1101、第一设备获取用户签约的业务套餐。
图11所示的通信方法可以应用于上述应用场景4和应用场景5中的任意一个应用场景。即图11中第一设备为PCRF实体，第二设备为PGW。或者，第一设备为PCRF实体，第二设备为TDF实体。当然，第一设备还可以为其他用于下发PCC规则的实体。第二设备还可以为其他用于执行PCC规则的实体，本申请实施例不做限定。
1102、第一设备确定业务套餐对应的PCC规则。
1103、第一设备向第二设备发送业务套餐的标识和该业务套餐对应的PCC规则。
其中，步骤1101～步骤1103的具体实现方式与上述步骤601～步骤603的具体实现方式相同，在此不赘述。
1104、第二设备记录业务套餐和PCC规则的对应关系。
具体地，第二设备从第一设备接收业务套餐的标识和业务套餐对应的PCC规则之后，记录业务套餐和PCC规则的对应关系。
1105、第二设备接收数据报文。
其中，该数据报文可以是上行的数据报文或者是下行的数据报文。
1106、第二设备确定与该数据报文匹配的目标PCC规则。
本申请实施例中，第二设备接收数据报文之后，确定与该数据报文匹配的目标PCC规则。
具体地，第二设备将该数据报文的属性信息与PCC规则中的业务数据流检测信息进行匹配。如果匹配成功，则确定该数据报文与该PCC规则相匹配。例如，第三设备中激活了用户1的PCC规则1和PCC规则2。其中，PCC规则1对应业务套餐1，PCC规则2对应业务套餐2。第二设备接收到用户1访问的数据报文之后，将该数据报文的属性信息与PCC规则1和PCC规则2中的业务数据流检测信息进行匹配。如果该数据报文的属性信息与PCC规则1中的业务数据流检测信息相匹配，则该数据报文与该PCC规则1匹配。因此，PCC规则1为目标PCC规则。第二设备根据预先记录的业务套餐与PCC规则的对应关系，确定PCC规则1对应业务套餐1。
1107、第二设备根据记录的PCC规则与业务套餐的对应关系，获取与目标PCC规则对应的目标业务套餐。
其中，获取的目标业务套餐就为第二设备接收的数据报文所属的业务套餐。可见，通过实施图11所描述的方法，能够使核心网设备确定接收的数据报文所属的业务套餐。
第二设备获取与目标PCC规则对应的目标业务套餐之后，能够基于业务套餐执行相关操作。
以下介绍第二设备基于业务套餐可执行的相关操作的流程。
请参见图12，如图12所示，图12是本申请实施例提供的又一种通信方法的流程示意图。其中，步骤1201～步骤1207的具体实施方式与上述步骤1101～步骤1107的具体实施方式相同，在此不赘述。如图12所示，第二设备获取与目标PCC规则对应的目标业务套餐之后，还可执行以下步骤1208～步骤1212。其中：
1208、第二设备根据数据报文，基于目标业务套餐进行数据统计，得到数据统计结果。
例如，目标PCC规则为PCC规则1，与目标PCC规则1对应的目标业务套餐为业务套餐1。第二设备根据该数据报文，基于业务套餐1进行数据统计，得到数据统计结果。可选的，第二设备还可执行PCC规则1中定义的计费与控制策略。
当然，第二设备也可不执行步骤1208，第二设备可基于目标业务套餐执行其他操作，本申请实施例不做限定。
1209、第二设备发送目标业务套餐对应的数据统计结果至数据分析设备。
1210、数据分析设备对目标业务套餐对应的数据统计结果进行数据分析，得到目标业务套餐对应的数据分析结果。
1211、数据分析设备发送目标业务套餐对应的数据分析结果至第一设备。
1212、第一设备根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发或流量抑制。
步骤1208～步骤1212的具体实施方式与上述步骤710～步骤714的具体实现方式相同，在此不赘述。
作为一种可选的实施方式，也可不执行步骤1211和步骤1212。数据分析设备对目标业务套餐对应的数据统计结果进行数据分析，得到目标业务套餐对应的数据分析结果之后，数据分析设备可发送目标业务套餐对应的数据分析结果至第二设备。第二设备从数据分析设备接收目标业务套餐对应的数据分析结果之后，根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发或流量抑制。可选的，如果目标业务套餐为高价值的业务套餐，则第二设备可根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发。如果目标业务套餐为低价值的业务套餐，则第二设备可根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量抑制。其中，第二设备可以为目标业务套餐生成一个叠加规则，该叠加规则可以对目标业务套餐进行流量激发或抑制。
下面基于上述应用场景4对本申请所提供的通信方法进一步进行说明。请参见图13，图13是本申请实施例提供的又一种通信方法的流程示意图。其中，步骤1301～步骤1303和步骤1312的执行主语为PCRF实体，或者为PCRF实体中的芯片。步骤1304～步骤1309的执行主语为PGW，或者为PGW中的芯片。步骤1310和步骤1311的执行主语为数据分析设备，或者为数据分析设备中的芯片。以下以PCRF实体、PGW以及数据分析设备为方法的执行主体为例进行说明。如图13所示，该通信方法包括如下步骤1301～步骤1312，其中：
1301、PCRF实体获取用户签约的业务套餐。
可选的，用户终端可通过RAN或移动管理节点(mobility management entity，MME)向PGW发送会话建立请求。PGW接收到该会话建立请求之后，向PCRF实体发送CCR-I(credit control request initial)消息。PCRF实体接收到CCR-I消息之后触发获取用户签约的业务套餐。或者，用户终端可通过RAN或MME向PGW发送会话更新请求。PGW接收到该会话更新请求之后，向PCRF实体发送CCR-U(credit control request update)消息。PCRF实体接收到CCR-U消息之后触发获取用户签约的业务套餐。或者，PCRF实体也可主动获取用户签约的业务套餐。或者，还可通过其他方式触发PCRF实体获取用户签约的业务套餐。
1302、PCRF实体确定业务套餐对应的PCC规则。
其中，步骤1302的具体实施方式可参见上述步骤602的具体实现方式，在此不赘述。
1303、PCRF实体向PGW发送业务套餐的标识和该业务套餐对应的PCC规则。
作为一种可选的实施方式，业务套餐的标识携带于计费规则安装Charging-Rule-Install消息的信元中发送至PGW。可选的，业务套餐的标识具体可携带于Charging-Rule-Install消息的AVP中。基于该可选的实施方式，PGW能够准确地确定业务套餐与PCC规则的对应关系。
作为一种可选的实施方式，PCRF实体只发送一个业务套餐的标识时，该业务套餐的标识携带于信用控制响应CCA消息或重新鉴权请求(re-auth-request，RAR)消息的信元中发送至PGW。可选的，业务套餐的标识具体可携带于对应的CCA消息或RAR消息的AVP 中。基于该可选的实施方式，PGW能够准确地确定业务套餐与PCC规则的对应关系。
1304、PGW记录业务套餐和PCC规则的对应关系。
本申请实施例中，PGW接收业务套餐的标识和该业务套餐对应的PCC规则之后，记录业务套餐和PCC规则的对应关系。
1305、PGW接收数据报文。
其中，该数据报文可以是上行的数据报文或者是下行的数据报文。
1306、PGW确定与该数据报文匹配的目标PCC规则。
1307、PGW根据记录的PCC规则与业务套餐的对应关系，获取与目标PCC规则对应的目标业务套餐。
步骤1305～步骤1307的具体实现方式与上述步骤1105～步骤1107的具体实现方式相同，在此不赘述。
1308、PGW根据数据报文，基于目标业务套餐进行数据统计，得到数据统计结果。
1309、PGW发送目标业务套餐对应的数据统计结果至数据分析设备。
1310、数据分析设备对目标业务套餐对应的数据统计结果进行数据分析，得到目标业务套餐对应的数据分析结果。
1311、数据分析设备发送目标业务套餐对应的数据分析结果至PCRF实体。
1312、PCRF实体根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发或流量抑制。
步骤1308～步骤1312的具体实施方式与上述步骤710～步骤714的具体实现方式相同，在此不赘述。
作为一种可选的实施方式，也可不执行步骤1311和步骤1312。数据分析设备对目标业务套餐对应的数据统计结果进行数据分析，得到目标业务套餐对应的数据分析结果之后，数据分析设备可发送目标业务套餐对应的数据分析结果至PGW。PGW从数据分析设备接收目标业务套餐对应的数据分析结果之后，根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发或流量抑制。可选的，如果目标业务套餐为高价值的业务套餐，则PGW可根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发。如果目标业务套餐为低价值的业务套餐，则PGW可根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量抑制。其中，PGW可以为目标业务套餐生成一个叠加规则，该叠加规则可以对目标业务套餐进行流量激发或抑制。
下面基于上述应用场景5对本申请所提供的通信方法进一步进行说明。请参见图14，图14是本申请实施例提供的又一种通信方法的流程示意图。其中，步骤1401～步骤1403和步骤1412的执行主语为PCRF实体，或者为PCRF实体中的芯片。步骤1404～步骤1409的执行主语为TDF实体，或者为TDF实体中的芯片。步骤1410和步骤1411的执行主语为数据分析设备，或者为数据分析设备中的芯片。以下以PCRF实体、TDF实体以及数据分析设备为方法的执行主体为例进行说明。如图14所示，该通信方法包括如下步骤1401～步骤1412，其中：
1401、PCRF实体获取用户签约的业务套餐。
可选的，用户终端可通过RAN或移动管理节点(mobility management entity，MME)向TDF实体发送会话建立请求。TDF实体接收到该会话建立请求之后，向PCRF实体发送CCR-I(credit control request initial)消息。PCRF实体接收到CCR-I消息之后触发获取用户签约的业务套餐。或者，用户终端可通过RAN或MME向TDF实体发送会话更新请求。TDF实体接收到该会话更新请求之后，向PCRF实体发送CCR-U(credit control request update)消息。PCRF实体接收到CCR-U消息之后触发获取用户签约的业务套餐。或者，PCRF实体也可主动获取用户签约的业务套餐。或者，还可通过其他方式触发PCRF实体获取用户签约的业务套餐。
1402、PCRF实体确定业务套餐对应的PCC规则。
其中，步骤1402的具体实施方式可参见上述步骤602的具体实现方式，在此不赘述。
1403、PCRF实体向TDF实体发送业务套餐的标识和该业务套餐对应的PCC规则。
作为一种可选的实施方式，业务套餐的标识携带于计费规则安装Charging-Rule-Install消息的信元中发送至TDF实体。可选的，业务套餐的标识具体可携带于Charging-Rule-Install消息的AVP中。基于该可选的实施方式，TDF实体能够准确地确定业务套餐与PCC规则的对应关系。
作为一种可选的实施方式，PCRF实体只发送一个业务套餐的标识时，该业务套餐的标识携带于信用控制响应CCA消息或重新鉴权请求(re-auth-request，RAR)消息的信元中发送至TDF实体。可选的，业务套餐的标识具体可携带于对应的CCA消息或RAR消息的AVP中。基于该可选的实施方式，TDF实体能够准确地确定业务套餐与PCC规则的对应关系。
1404、TDF实体记录业务套餐和PCC规则的对应关系。
本申请实施例中，TDF实体接收业务套餐的标识和该业务套餐对应的PCC规则之后，记录业务套餐和PCC规则的对应关系。
1405、TDF实体接收数据报文。
其中，该数据报文可以是上行的数据报文或者是下行的数据报文。
1406、TDF实体确定与该数据报文匹配的目标PCC规则。
1407、TDF实体根据记录的PCC规则与业务套餐的对应关系，获取与目标PCC规则对应的目标业务套餐。
步骤1405～步骤1407的具体实现方式与上述步骤1105～步骤1107的具体实现方式相同，在此不赘述。
1408、TDF实体根据数据报文，基于目标业务套餐进行数据统计，得到数据统计结果。
1409、TDF实体发送目标业务套餐对应的数据统计结果至数据分析设备。
1410、数据分析设备对目标业务套餐对应的数据统计结果进行数据分析，得到目标业务套餐对应的数据分析结果。
1411、数据分析设备发送目标业务套餐对应的数据分析结果至PCRF实体。
1412、PCRF实体根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发或流量抑制。
步骤1408～步骤1412的具体实施方式与上述步骤710～步骤714的具体实现方式相同， 在此不赘述。
作为一种可选的实施方式，也可不执行步骤1411和步骤1412。数据分析设备对目标业务套餐对应的数据统计结果进行数据分析，得到目标业务套餐对应的数据分析结果之后，数据分析设备可发送目标业务套餐对应的数据分析结果至TDF实体。TDF实体从数据分析设备接收目标业务套餐对应的数据分析结果之后，根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发或流量抑制。可选的，如果目标业务套餐为高价值的业务套餐，则TDF实体可根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发。如果目标业务套餐为低价值的业务套餐，则TDF实体可根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量抑制。其中，TDF实体可以为目标业务套餐生成一个叠加规则，该叠加规则可以对目标业务套餐进行流量激发或抑制。
请参见图15，图15是本申请实施例提供的又一种通信方法的流程示意图。其中，步骤1501～步骤1503和步骤1512的执行主语为PCRF实体，或者为PCRF实体中的芯片。步骤1504～步骤1509的执行主语为PGW，或者为PGW中的芯片。步骤1510和步骤1511的执行主语为数据分析设备，或者为数据分析设备中的芯片。以下以PCRF实体、PGW以及数据分析设备为方法的执行主体为例进行说明。如图15所示，该通信方法包括如下步骤1501～步骤1512，其中：
1501、PCRF实体获取用户签约的业务套餐。
1502、PCRF实体确定业务套餐对应的PCC规则。
1503、PCRF实体向PGW发送业务套餐的标识和该业务套餐对应的PCC规则。
其中，步骤1501～步骤1503的具体实施方式与上述步骤1401～步骤1403的具体实现方式相同，在此不赘述。
1504、PGW抄送业务套餐的标识和该业务套餐对应的PCC规则至TDF实体。
具体地，PGW从PCRF实体接收业务套餐的标识和该业务套餐对应的PCC规则之后，抄送业务套餐的标识和该业务套餐对应的PCC规则至TDF实体。可选的，PGW通过Radius抄送接口发送业务套餐的标识和该业务套餐对应的PCC规则至TDF。例如，可通过Radius抄送接口的Accounting Start消息或Accounting Update消息发送业务套餐的标识和该业务套餐对应的PCC规则至TDF。可选的，如果只发送一个业务套餐的标识，也可通过会话维度的信息发送业务套餐的标识和该业务套餐对应的PCC规则至TDF实体。
1505、TDF实体记录业务套餐和PCC规则的对应关系。
本申请实施例中，TDF实体接收业务套餐的标识和该业务套餐对应的PCC规则之后，记录业务套餐和PCC规则的对应关系。
1506、TDF实体接收数据报文。
1507、TDF实体确定与该数据报文匹配的目标PCC规则。
1508、TDF实体根据记录的PCC规则与业务套餐的对应关系，获取与目标PCC规则对应的目标业务套餐。
1509、TDF实体根据数据报文，基于目标业务套餐进行数据统计，得到数据统计结果。
1510、TDF实体发送目标业务套餐对应的数据统计结果至数据分析设备。
1511、数据分析设备对目标业务套餐对应的数据统计结果进行数据分析，得到目标业务套餐对应的数据分析结果。
1512、数据分析设备发送目标业务套餐对应的数据分析结果至PCRF实体。
1513、PCRF实体根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发或流量抑制。
其中，步骤1505～步骤1513的具体实施方式与上述步骤1404～步骤1412的具体实现方式相同，在此不赘述。
本发明实施例可以根据上述方法示例对设备进行功能单元的划分，例如，可以对应各个功能划分各个功能单元，也可以将两个或两个以上的功能集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。需要说明的是，本发明实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
请参见图16，图16示出了本申请实施例的一种通信装置的结构示意图。图16所示的通信装置可以用于执行上述图6和图7所描述的方法实施例中第一设备的部分或全部功能。或者，图16所示的通信装置可以用于执行上述图8所描述的方法实施例中PCF实体的部分或全部功能。或者，图16所示的通信装置可以用于执行上述图9和图10所描述的方法实施例中PCRF实体的部分或全部功能。或者，图16所示的通信装置可以用于执行上述图11和图12所描述的方法实施例中第一设备的部分或全部功能。或者，图16所示的通信装置可以用于执行上述图13～图15所描述的方法实施例中PCRF实体的部分或全部功能。图16所示的通信装置可以包括通信单元1601和处理单元1602。其中：
处理单元1602，用于获取用户签约的业务套餐；处理单元1602，还用于确定业务套餐对应的策略与计费控制PCC规则；通信单元1601，用于向第二设备发送业务套餐的标识和业务套餐对应的PCC规则。
作为一种可选的实施方式，通信单元1601，还用于从数据分析设备接收目标业务套餐对应的数据分析结果；处理单元1602，还用于根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发或流量抑制。
作为一种可选的实施方式，通信装置为策略控制功能PCF实体，第二设备为会话管理功能SMF实体；或者，通信装置为策略与计费规则功能PCRF实体，第二设备为分组数据网关控制面PGW-C实体；或者，通信装置为PCRF实体，第二设备为业务检测功能控制面TDF-C实体；或者，通信装置为PCRF实体，第二设备为分组数据网关PGW；或者，通信装置为PCRF实体，第二设备为业务检测功能TDF实体。
作为一种可选的实施方式，通信装置为PCF实体，第二设备为SMF实体；
业务套餐的标识携带于对应的PCC规则的信元中发送至第二设备；或者，通信装置只发送一个业务套餐的标识，业务套餐的标识携带于会话规则的信元中发送至第二设备。
作为一种可选的实施方式，通信装置为PCRF实体，第二设备为PGW-C实体；或者，通信装置为PCRF实体，第二设备为TDF-C实体；或者，通信装置为PCRF实体，第二设备为PGW；或者，通信装置为PCRF实体，第二设备为TDF实体；
业务套餐的标识携带于计费规则安装Charging-Rule-Install消息的信元中发送至第二设备；或者，通信装置只发送一个业务套餐的标识，业务套餐的标识携带于信用控制响应CCA消息或重新鉴权请求RAR消息的信元中发送至第二设备。
请参见图16，图16示出了本申请实施例的一种通信装置的结构示意图。图16所示的通信装置可以用于执行上述图6和图7所描述的方法实施例中第二设备的部分或全部功能。或者，图16所示的通信装置可以用于执行上述图8所描述的方法实施例中SMF实体的部分或全部功能。或者，图16所示的通信装置可以用于执行上述图9所描述的方法实施例中PGW-C实体的部分或全部功能。或者，图16所示的通信装置可以用于执行上述图10所描述的方法实施例中TDF-C实体的部分或全部功能。图16所示的通信装置可以包括通信单元1601和处理单元1602。其中：
通信单元1601，用于从第一设备接收业务套餐的标识和业务套餐对应的策略与计费控制PCC规则；处理单元1602，用于将业务套餐对应的PCC规则转换为报文探测规则PDR；通信单元1601，还用于发送业务套餐的标识和业务套餐对应的PDR至第三设备。
作为一种可选的实施方式，通信单元1601，还用于从数据分析设备接收目标业务套餐对应的数据分析结果；处理单元1602，还用于根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发或流量抑制。
作为一种可选的实施方式，第一设备为策略控制功能PCF实体，通信装置为会话管理功能SMF实体，第三设备为用户面功能UPF实体；或者，第一设备为策略与计费规则功能PCRF实体，通信装置为分组数据网关控制面PGW-C实体，第三设备为分组数据网关用户面PGW-U实体；或者，第一设备为PCRF实体，通信装置为业务检测功能控制面TDF-C实体，第三设备为业务检测功能用户面TDF-U实体。
作为一种可选的实施方式，第一设备为PCF实体，通信装置为SMF实体，第三设备为UPF实体；
业务套餐的标识携带于对应的PCC规则的信元中发送至通信装置；或者，第一设备只发送一个业务套餐的标识，业务套餐的标识携带于会话规则的信元中发送至通信装置。
作为一种可选的实施方式，第一设备为PCRF实体，通信装置为PGW-C实体，第三设备为PGW-U实体；或者，第一设备为PCRF实体，通信装置为TDF-C实体，第三设备为TDF-U实体；
业务套餐的标识携带于计费规则安装Charging-Rule-Install消息的信元中发送至通信装置；或者，第一设备只发送一个业务套餐的标识时，业务套餐的标识携带于信用控制响应CCA消息或重新鉴权请求RAR消息的信元中发送至通信装置。
作为一种可选的实施方式，业务套餐的标识携带于业务套餐对应的PDR的信元中发送至第三设备；或者，通信装置只发送的一个业务套餐的标识时，业务套餐的标识携带于会话建立请求的信元中发送至第三设备。
请参见图16，图16示出了本申请实施例的一种通信装置的结构示意图。图16所示的通信装置可以用于执行上述图6和图7所描述的方法实施例中第三设备的部分或全部功能。 或者，图16所示的通信装置可以用于执行上述图8所描述的方法实施例中UPF实体的部分或全部功能。或者，图16所示的通信装置可以用于执行上述图9所描述的方法实施例中PGW-U实体的部分或全部功能。或者，图16所示的通信装置可以用于执行上述图10所描述的方法实施例中TDF-U实体的部分或全部功能。图16所示的通信装置可以包括通信单元1601和处理单元1602。其中：
通信单元1601，用于从第二设备接收业务套餐的标识和业务套餐对应的报文探测规则PDR；处理单元1602，用于记录业务套餐与PDR的对应关系；通信单元1601，还用于接收数据报文；处理单元1602，还用于确定与数据报文匹配的目标报文探测规则PDR；处理单元1602，还用于根据记录的业务套餐与PDR的对应关系，获取与目标PDR对应的目标业务套餐。
作为一种可选的实施方式，处理单元1602，还用于根据数据报文，基于目标业务套餐进行数据统计，得到目标业务套餐对应的数据统计结果。
作为一种可选的实施方式，通信单元1601，还用于发送目标业务套餐对应的数据统计结果至数据分析设备。
作为一种可选的实施方式，通信单元1601，还用于从数据分析设备接收目标业务套餐对应的数据分析结果；
处理单元1602，还用于根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发或流量抑制。
作为一种可选的实施方式，第二设备为会话管理功能SMF实体，通信装置为用户面功能UPF实体；或者，第二设备为分组数据网关控制面PGW-C实体，通信装置为分组数据网关用户面PGW-U实体；或者，第二设备为业务检测功能控制面TDF-C实体，通信装置为业务检测功能用户面TDF-U实体。
作为一种可选的实施方式，业务套餐的标识携带于业务套餐对应的PDR的信元中发送至通信装置，或者，第二设备只发送的一个业务套餐的标识时，业务套餐的标识携带于会话建立请求的信元中发送至通信装置。
请参见图16，图16示出了本申请实施例的一种通信装置的结构示意图。图16所示的通信装置可以用于执行上述图11和图12所描述的方法实施例中第二设备的部分或全部功能。或者，图16所示的通信装置可以用于执行上述图13所描述的方法实施例中PGW实体的部分或全部功能。或者，图16所示的通信装置可以用于执行上述图14和图15所描述的方法实施例中TDF实体的部分或全部功能。图16所示的通信装置可以包括通信单元1601和处理单元1602。其中：
通信单元1601，用于从第一设备接收业务套餐的标识和业务套餐对应的PCC规则；处理单元1602，用于记录业务套餐和PCC规则的对应关系；通信单元1601，还用于接收数据报文；处理单元1602，还用于确定与数据报文匹配的目标PCC规则；处理单元1602，还用于根据记录的PCC规则与业务套餐的对应关系，获取与目标PCC规则对应的目标业务套餐。
作为一种可选的实施方式，处理单元1602，还用于根据数据报文，基于目标业务套餐 进行数据统计，得到数据统计结果。
作为一种可选的实施方式，通信单元1601，还用于发送目标业务套餐对应的数据统计结果至数据分析设备。
作为一种可选的实施方式，通信单元1601，还用于从数据分析设备接收目标业务套餐的数据分析结果；处理单元1602，还用于根据目标业务套餐对应的数据分析结果对目标业务套餐进行流量激发或流量抑制。
作为一种可选的实施方式，第一设备为策略与计费规则功能PCRF实体，通信装置为分组数据网关PGW；或者，第一设备为PCRF，通信装置为业务检测功能TDF实体；或者，第一设备为PGW，通信装置为TDF实体。
作为一种可选的实施方式，第一设备为PCRF实体，通信装置为PGW；或者，第一设备为PCRF，通信装置为TDF实体；
业务套餐的标识携带于计费规则安装Charging-Rule-Install消息的信元中发送至通信装置；或者，第一设备只发送一个业务套餐的标识，业务套餐的标识携带于信用控制响应CCA消息或重新鉴权请求RAR消息的信元中发送至通信装置。
请参见图16，图16示出了本申请实施例的一种通信装置的结构示意图。图16所示的通信装置可以用于执行上述图6～图15所描述的方法实施例中数据分析设备的部分或全部功能。图16所示的通信装置可以包括通信单元1601和处理单元1602。其中：
通信单元1601，用于接收目标业务套餐对应的数据统计结果；处理单元1602，用于对数据统计结果进行分析，得到目标业务套餐对应的数据分析结果；通信单元1601，还用于发送目标业务套餐对应的数据分析结果。
请参见图17，图17是本申请实施例公开的一种通信装置的结构示意图。该通信装置可用于实现上述方法实施例中描述的通信方法。该通信装置可以是上述第一设备、用于第一设备的装置。例如，用于第一设备的装置可以为第一设备的芯片。或者，该通信装置可以是第二设备或用于第二设备的装置。例如，用于第二设备的装置可以为第二设备的芯片。或者，该通信装置可以是第三设备或用于第三设备的装置。例如，用于第三设备的装置可以为第三设备的芯片。
如图17所示，该通信装置包括处理器1701和收发器1702。其中，处理器1701与收发器1702相连。可选的，该通信装置还可包括存储器1703。存储器1703与处理器1701相连。
其中，该处理器1701可支持通信装置实现本申请实施例中的通信方法。
例如，当通信装置为第一设备或用于第一设备的装置时，处理器1701可执行图4或图6所描述的方法实施例中第一设备所执行的方法。该处理器1701执行的操作可参见图4或图6对应的实施例中关于第一设备的相关描述，在此不做赘述。第一设备可以为PCRF实体或PCF实体。第一设备为PCRF实体时，该处理器1701执行的操作还可参见图8对应的实施例中关于PCRF实体的相关描述，在此不做赘述。第一设备为PCF实体时，该处理器1701执行的操作还可参见图9和图10对应的实施例中关于PCF实体的相关描述，在此 不做赘述。
当通信装置为第二设备或用于第二设备的装置时，处理器1701可执行图6、图7、图11或图12所描述的方法实施例中第二设备所执行的方法。该处理器1701执行的操作可参见图6、图7、图11或图12对应的实施例中关于第二设备相关描述，在此不做赘述。第二设备可以为SMF实体或PGW-C实体或TDF-C实体或PGW或TDF实体。第二设备为SMF实体时，该处理器1701执行的操作还可参见图8对应的实施例中关于SMF实体的相关描述，在此不做赘述。第二设备为PGW-C实体时，该处理器1701执行的操作还可参见图9对应的实施例中关于PGW-C实体的相关描述，在此不做赘述。第二设备为TDF-C实体时，该处理器1701执行的操作还可参见图10对应的实施例中关于TDF-C实体的相关描述，在此不做赘述。第二设备为PGW时，该处理器1701执行的操作还可参见图13对应的实施例中关于PGW的相关描述，在此不做赘述。第二设备为TDF实体时，该处理器1701执行的操作还可参见图14或图15对应的实施例中关于TDF的相关描述，在此不做赘述。
当通信装置为第三设备或用于第三设备的装置时，处理器1701可执行图6或图7所描述的方法实施例中第三设备所执行的方法。该处理器1701执行的操作可参见图6或图7对应的实施例中关于第三设备相关描述，在此不做赘述。第三设备可以为UPF实体或PGW-U实体或TDF-U实体。第三设备为UPF实体时，该处理器1701执行的操作还可参见图8对应的实施例中关于UPF实体的相关描述，在此不做赘述。第三设备为PGW-U实体时，该处理器1701执行的操作还可参见图9对应的实施例中关于PGW-U实体的相关描述，在此不做赘述。第三设备为TDF-U实体时，该处理器1701执行的操作还可参见图10对应的实施例中关于TDF-U实体的相关描述，在此不做赘述。
处理器1701可以是中央处理器(central processing unit，CPU)，通用处理器，协处理器，数字信号处理器(digital signal processor，DSP)，专用集成电路(application-specific integrated circuit，ASIC)，现场可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。该处理器1701也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。
其中，当通信装置为第一设备、第二设备或第三设备时，收发器1702可以包括天线以及与天线相连的射频电路。收发器1702用于与其他网元进行通信。
当通信装置为用于第一设备、第二设备或第三设备的装置时，收发器1702可以为接口电路，该接口电路用于该处理器获取或者输出信息或数据。例如，该接口电路用于该处理器从存储器读取数据或者写入数据，又如，该接口电路用于处理器1701接收来自设备外部的信息或数据，或者向设备外部发送信息或数据。
可选的，通信装置中可以包括存储器1703，其上存有程序(也可以是指令或者代码)，该程序可被处理器1701运行，使得处理器1701执行上述方法实施例中描述的通信方法。可选地，存储器1703中还可以存储有数据。可选地，处理器1701还可以读取存储器1703中存储的数据(例如，预定义的信息)，该数据可以与程序存储在相同的存储地址，该数据也可以与程序存储在不同的存储地址。
处理器1701和存储器1703可以单独设置，也可以集成在一起，例如，集成在单板或者系统级芯片(system on chip，SOC)上。
本发明实施例还提供一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在处理器上运行时，上述方法实施例的方法流程得以实现。
本发明实施例还提供一种计算机程序产品，当所述计算机程序产品在处理器上运行时，上述方法实施例的方法流程得以实现。
当使用软件实现本申请所提供的设备时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地实现本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程设备。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如软盘、硬盘、磁带)、光介质(例如DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
本申请提供的各实施例的描述可以相互参照，对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其他实施例的相关描述。为描述的方便和简洁，例如关于本申请实施例提供的各装置、设备的功能以及执行的步骤可以参照本申请方法实施例的相关描述，各方法实施例之间、各装置实施例之间也可以互相参考、结合或引用。
最后应说明的是：以上各实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述各实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分或者全部技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的范围。

Claims (57)

  1. 一种通信方法，其特征在于，所述方法包括：
    第一设备获取用户签约的业务套餐；
    所述第一设备确定所述业务套餐对应的策略与计费控制PCC规则；
    所述第一设备向第二设备发送所述业务套餐的标识和所述业务套餐对应的PCC规则。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述第一设备从数据分析设备接收目标业务套餐对应的数据分析结果；
    所述第一设备根据所述目标业务套餐对应的数据分析结果对所述目标业务套餐进行流量激发或流量抑制。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一设备为策略控制功能PCF实体，所述第二设备为会话管理功能SMF实体；或者，所述第一设备为策略与计费规则功能PCRF实体，所述第二设备为分组数据网关控制面PGW-C实体；或者，所述第一设备为PCRF实体，所述第二设备为业务检测功能控制面TDF-C实体；或者，所述第一设备为PCRF实体，所述第二设备为分组数据网关PGW；或者，所述第一设备为PCRF实体，所述第二设备为业务检测功能TDF实体。
  4. 根据权利要求3所述的方法，其特征在于，所述第一设备为PCF实体，所述第二设备为SMF实体；
    所述业务套餐的标识携带于对应的PCC规则的信元中发送至所述第二设备；或者，所述第一设备只发送一个业务套餐的标识，所述业务套餐的标识携带于会话规则的信元中发送至所述第二设备。
  5. 根据权利要求3所述的方法，其特征在于，所述第一设备为PCRF实体，所述第二设备为PGW-C实体；或者，所述第一设备为PCRF实体，所述第二设备为TDF-C实体；或者，所述第一设备为PCRF实体，所述第二设备为PGW；或者，所述第一设备为PCRF实体，所述第二设备为TDF实体；
    所述业务套餐的标识携带于计费规则安装Charging-Rule-Install消息的信元中发送至所述第二设备；或者，所述第一设备只发送一个业务套餐的标识，所述业务套餐的标识携带于信用控制响应CCA消息或重新鉴权请求RAR消息的信元中发送至所述第二设备。
  6. 一种通信方法，其特征在于，所述方法包括：
    第二设备从第一设备接收业务套餐的标识和所述业务套餐对应的策略与计费控制PCC规则；
    所述第二设备将所述业务套餐对应的PCC规则转换为报文探测规则PDR；
    所述第二设备发送所述业务套餐的标识和所述业务套餐对应的所述PDR至第三设备。
  7. 根据权利要求6所述的方法，其特征在于，所述方法还包括：
    所述第二设备从数据分析设备接收目标业务套餐对应的数据分析结果；
    所述第二设备根据所述目标业务套餐对应的数据分析结果对所述目标业务套餐进行流量激发或流量抑制。
  8. 根据权利要求6或7所述的方法，其特征在于，所述第一设备为策略控制功能PCF实体，所述第二设备为会话管理功能SMF实体，所述第三设备为用户面功能UPF实体；或者，所述第一设备为策略与计费规则功能PCRF实体，所述第二设备为分组数据网关控制面PGW-C实体，所述第三设备为分组数据网关用户面PGW-U实体；或者，所述第一设备为PCRF实体，所述第二设备为业务检测功能控制面TDF-C实体，所述第三设备为业务检测功能用户面TDF-U实体。
  9. 根据权利要求8所述的方法，其特征在于，所述第一设备为PCF实体，所述第二设备为SMF实体，所述第三设备为UPF实体；
    所述业务套餐的标识携带于对应的PCC规则的信元中发送至所述第二设备；或者，所述第一设备只发送一个业务套餐的标识，所述业务套餐的标识携带于会话规则的信元中发送至所述第二设备。
  10. 根据权利要求8所述的方法，其特征在于，所述第一设备为PCRF实体，所述第二设备为PGW-C实体，所述第三设备为PGW-U实体；或者，所述第一设备为PCRF实体，所述第二设备为TDF-C实体，所述第三设备为TDF-U实体；
    所述业务套餐的标识携带于计费规则安装Charging-Rule-Install消息的信元中发送至所述第二设备；或者，所述第一设备只发送一个业务套餐的标识时，所述业务套餐的标识携带于信用控制响应CCA消息或重新鉴权请求RAR消息的信元中发送至所述第二设备。
  11. 根据权利要求6～10中任意一项所述的方法，其特征在于，所述业务套餐的标识携带于所述业务套餐对应的PDR的信元中发送至所述第三设备；或者，所述第二设备只发送的一个业务套餐的标识时，所述业务套餐的标识携带于会话建立请求的信元中发送至所述第三设备。
  12. 一种通信方法，其特征在于，所述方法包括：
    第三设备从第二设备接收业务套餐的标识和所述业务套餐对应的报文探测规则PDR；
    所述第三设备记录所述业务套餐与所述PDR的对应关系；
    所述第三设备接收数据报文；
    所述第三设备确定与所述数据报文匹配的目标报文探测规则PDR；
    所述第三设备根据记录的业务套餐与PDR的对应关系，获取与所述目标PDR对应的目标业务套餐。
  13. 根据权利要求12所述的方法，其特征在于，所述方法还包括：
    所述第三设备根据所述数据报文，基于所述目标业务套餐进行数据统计，得到所述目标业务套餐对应的数据统计结果。
  14. 根据权利要求13所述的方法，其特征在于，所述方法还包括：
    所述第三设备发送所述目标业务套餐对应的数据统计结果至数据分析设备。
  15. 根据权利要求14所述的方法，其特征在于，所述方法还包括：
    所述第三设备从所述数据分析设备接收所述目标业务套餐对应的数据分析结果；
    所述第三设备根据所述目标业务套餐对应的数据分析结果对所述目标业务套餐进行流量激发或流量抑制。
  16. 根据权利要求12～15中任意一项所述的方法，其特征在于，所述第二设备为会话管理功能SMF实体，所述第三设备为用户面功能UPF实体；或者，所述第二设备为分组数据网关控制面PGW-C实体，所述第三设备为分组数据网关用户面PGW-U实体；或者，所述第二设备为业务检测功能控制面TDF-C实体，所述第三设备为业务检测功能用户面TDF-U实体。
  17. 根据权利要求12～16中任意一项所述的方法，其特征在于，所述业务套餐的标识携带于所述业务套餐对应的PDR的信元中发送至所述第三设备，或者，所述第二设备只发送的一个业务套餐的标识时，所述业务套餐的标识携带于会话建立请求的信元中发送至所述第三设备。
  18. 一种通信方法，其特征在于，所述方法包括：
    第二设备从第一设备接收业务套餐的标识和所述业务套餐对应的PCC规则；
    所述第二设备记录所述业务套餐和所述PCC规则的对应关系；
    所述第二设备接收数据报文；
    所述第二设备确定与所述数据报文匹配的目标PCC规则；
    所述第二设备根据记录的PCC规则与业务套餐的对应关系，获取与所述目标PCC规则对应的目标业务套餐。
  19. 根据权利要求18所述的方法，其特征在于，所述方法还包括：
    所述第二设备根据所述数据报文，基于所述目标业务套餐进行数据统计，得到数据统计结果。
  20. 根据权利要求19所述的方法，其特征在于，所述方法还包括：
    所述第二设备发送所述目标业务套餐对应的数据统计结果至数据分析设备。
  21. 根据权利要求20所述的方法，其特征在于，所述方法还包括：
    所述第二设备从数据分析设备接收目标业务套餐的数据分析结果；
    所述第二设备根据所述目标业务套餐对应的数据分析结果对所述目标业务套餐进行流量激发或流量抑制。
  22. 根据权利要求18～21中任意一项所述的方法，其特征在于，所述第一设备为策略与计费规则功能PCRF实体，所述第二设备为分组数据网关PGW；或者，所述第一设备为PCRF，所述第二设备为业务检测功能TDF实体；或者，所述第一设备为PGW，所述第二设备为TDF实体。
  23. 根据权利要求22所述的方法，其特征在于，所述第一设备为PCRF实体，所述第二设备为PGW；或者，所述第一设备为PCRF，所述第二设备为TDF实体；
    所述业务套餐的标识携带于计费规则安装Charging-Rule-Install消息的信元中发送至所述第二设备；或者，所述第一设备只发送一个业务套餐的标识，所述业务套餐的标识携带于信用控制响应CCA消息或重新鉴权请求RAR消息的信元中发送至所述第二设备。
  24. 一种通信装置，其特征在于，所述通信装置包括：
    处理单元，用于获取用户签约的业务套餐；
    所述处理单元，还用于确定所述业务套餐对应的策略与计费控制PCC规则；
    通信单元，用于向第二设备发送所述业务套餐的标识和所述业务套餐对应的PCC规则。
  25. 根据权利要求24所述的通信装置，其特征在于，
    所述通信单元，还用于从数据分析设备接收目标业务套餐对应的数据分析结果；
    所述处理单元，还用于根据所述目标业务套餐对应的数据分析结果对所述目标业务套餐进行流量激发或流量抑制。
  26. 根据权利要求24或25所述的通信装置，其特征在于，所述通信装置为策略控制功能PCF实体，所述第二设备为会话管理功能SMF实体；或者，所述通信装置为策略与计费规则功能PCRF实体，所述第二设备为分组数据网关控制面PGW-C实体；或者，所述通信装置为PCRF实体，所述第二设备为业务检测功能控制面TDF-C实体；或者，所述通信装置为PCRF实体，所述第二设备为分组数据网关PGW；或者，所述通信装置为PCRF实体，所述第二设备为业务检测功能TDF实体。
  27. 根据权利要求26所述的通信装置，其特征在于，所述通信装置为PCF实体，所述第二设备为SMF实体；
    所述业务套餐的标识携带于对应的PCC规则的信元中发送至所述第二设备；或者，所述通信装置只发送一个业务套餐的标识，所述业务套餐的标识携带于会话规则的信元中发送至所述第二设备。
  28. 根据权利要求26所述的通信装置，其特征在于，所述通信装置为PCRF实体，所述第二设备为PGW-C实体；或者，所述通信装置为PCRF实体，所述第二设备为TDF-C实体；或者，所述通信装置为PCRF实体，所述第二设备为PGW；或者，所述通信装置为PCRF实体，所述第二设备为TDF实体；
    所述业务套餐的标识携带于计费规则安装Charging-Rule-Install消息的信元中发送至所述第二设备；或者，所述通信装置只发送一个业务套餐的标识，所述业务套餐的标识携带于信用控制响应CCA消息或重新鉴权请求RAR消息的信元中发送至所述第二设备。
  29. 一种通信装置，其特征在于，所述通信装置包括：
    通信单元，用于从第一设备接收业务套餐的标识和所述业务套餐对应的策略与计费控制PCC规则；
    处理单元，用于将所述业务套餐对应的PCC规则转换为报文探测规则PDR；
    所述通信单元，还用于发送所述业务套餐的标识和所述业务套餐对应的所述PDR至第三设备。
  30. 根据权利要求29所述的通信装置，其特征在于，
    所述通信单元，还用于从数据分析设备接收目标业务套餐对应的数据分析结果；
    所述处理单元，还用于根据所述目标业务套餐对应的数据分析结果对所述目标业务套餐进行流量激发或流量抑制。
  31. 根据权利要求29或30所述的通信装置，其特征在于，所述第一设备为策略控制功能PCF实体，所述通信装置为会话管理功能SMF实体，所述第三设备为用户面功能UPF实体；或者，所述第一设备为策略与计费规则功能PCRF实体，所述通信装置为分组数据网关控制面PGW-C实体，所述第三设备为分组数据网关用户面PGW-U实体；或者，所述第一设备为PCRF实体，所述通信装置为业务检测功能控制面TDF-C实体，所述第三设备为业务检测功能用户面TDF-U实体。
  32. 根据权利要求31所述的通信装置，其特征在于，所述第一设备为PCF实体，所述通信装置为SMF实体，所述第三设备为UPF实体；
    所述业务套餐的标识携带于对应的PCC规则的信元中发送至所述通信装置；或者，所述第一设备只发送一个业务套餐的标识，所述业务套餐的标识携带于会话规则的信元中发送至所述通信装置。
  33. 根据权利要求31所述的通信装置，其特征在于，所述第一设备为PCRF实体，所述通信装置为PGW-C实体，所述第三设备为PGW-U实体；或者，所述第一设备为PCRF实体，所述通信装置为TDF-C实体，所述第三设备为TDF-U实体；
    所述业务套餐的标识携带于计费规则安装Charging-Rule-Install消息的信元中发送至所 述通信装置；或者，所述第一设备只发送一个业务套餐的标识时，所述业务套餐的标识携带于信用控制响应CCA消息或重新鉴权请求RAR消息的信元中发送至所述通信装置。
  34. 根据权利要求29～33中任意一项所述的通信装置，其特征在于，所述业务套餐的标识携带于所述业务套餐对应的PDR的信元中发送至所述第三设备；或者，所述通信装置只发送的一个业务套餐的标识时，所述业务套餐的标识携带于会话建立请求的信元中发送至所述第三设备。
  35. 一种通信装置，其特征在于，所述通信装置包括：
    通信单元，用于从第二设备接收业务套餐的标识和所述业务套餐对应的报文探测规则PDR；
    处理单元，用于记录所述业务套餐与所述PDR的对应关系；
    所述通信单元，还用于接收数据报文；
    所述处理单元，还用于确定与所述数据报文匹配的目标报文探测规则PDR；
    所述处理单元，还用于根据记录的业务套餐与PDR的对应关系，获取与所述目标PDR对应的目标业务套餐。
  36. 根据权利要求35所述的通信装置，其特征在于，
    所述处理单元，还用于根据所述数据报文，基于所述目标业务套餐进行数据统计，得到所述目标业务套餐对应的数据统计结果。
  37. 根据权利要求36所述的通信装置，其特征在于，
    所述通信单元，还用于发送所述目标业务套餐对应的数据统计结果至数据分析设备。
  38. 根据权利要求37所述的通信装置，其特征在于，
    所述通信单元，还用于从所述数据分析设备接收所述目标业务套餐对应的数据分析结果；
    所述处理单元，还用于根据所述目标业务套餐对应的数据分析结果对所述目标业务套餐进行流量激发或流量抑制。
  39. 根据权利要求35～38中任意一项所述的通信装置，其特征在于，所述第二设备为会话管理功能SMF实体，所述通信装置为用户面功能UPF实体；或者，所述第二设备为分组数据网关控制面PGW-C实体，所述通信装置为分组数据网关用户面PGW-U实体；或者，所述第二设备为业务检测功能控制面TDF-C实体，所述通信装置为业务检测功能用户面TDF-U实体。
  40. 根据权利要求35～39中任意一项所述的通信装置，其特征在于，所述业务套餐的标识携带于所述业务套餐对应的PDR的信元中发送至所述通信装置，或者，所述第二设备 只发送的一个业务套餐的标识时，所述业务套餐的标识携带于会话建立请求的信元中发送至所述通信装置。
  41. 一种通信装置，其特征在于，所述通信装置包括：
    通信单元，用于从第一设备接收业务套餐的标识和所述业务套餐对应的PCC规则；
    处理单元，用于记录所述业务套餐和所述PCC规则的对应关系；
    所述通信单元，还用于接收数据报文；
    所述处理单元，还用于确定与所述数据报文匹配的目标PCC规则；
    所述处理单元，还用于根据记录的PCC规则与业务套餐的对应关系，获取与所述目标PCC规则对应的目标业务套餐。
  42. 根据权利要求41所述的通信装置，其特征在于，
    所述处理单元，还用于根据所述数据报文，基于所述目标业务套餐进行数据统计，得到数据统计结果。
  43. 根据权利要求42所述的通信装置，其特征在于，
    所述通信单元，还用于发送所述目标业务套餐对应的数据统计结果至数据分析设备。
  44. 根据权利要求43所述的通信装置，其特征在于，
    所述通信单元，还用于从数据分析设备接收目标业务套餐的数据分析结果；
    所述处理单元，还用于根据所述目标业务套餐对应的数据分析结果对所述目标业务套餐进行流量激发或流量抑制。
  45. 根据权利要求41～44中任意一项所述的通信装置，其特征在于，所述第一设备为策略与计费规则功能PCRF实体，所述通信装置为分组数据网关PGW；或者，所述第一设备为PCRF，所述通信装置为业务检测功能TDF实体；或者，所述第一设备为PGW，所述通信装置为TDF实体。
  46. 根据权利要求45所述的通信装置，其特征在于，所述第一设备为PCRF实体，所述通信装置为PGW；或者，所述第一设备为PCRF，所述通信装置为TDF实体；
    所述业务套餐的标识携带于计费规则安装Charging-Rule-Install消息的信元中发送至所述通信装置；或者，所述第一设备只发送一个业务套餐的标识，所述业务套餐的标识携带于信用控制响应CCA消息或重新鉴权请求RAR消息的信元中发送至所述通信装置。
  47. 一种用户面网元，其特征在于，包括：处理器和存储器；所述存储器用于存储计算机执行指令，当所述用户面网元运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述用户面网元执行如权利要求12-17任一项所述的通信方法。
  48. 一种通信装置，其特征在于，包括：处理器和存储器；所述存储器用于存储计算机执行指令，当所述通信装置运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述通信装置执行如权利要求1-5任一项，或权利要求6-11任一项，或权利要求18-23任一项所述的通信方法。
  49. 一种处理装置，其特征在于，包括：
    存储器，用于存储计算机程序；
    处理器，用于从所述存储器调用并运行所述计算机程序，以执行如权利要求1-5任一项，或权利要求6-11任一项，或权利要求12-17任一项，或权利要求18-23任一项所述的通信方法。
  50. 一种处理器，其特征在于，用于执行如权利要求1-5任一项，或权利要求6-11任一项，或权利要求12-17任一项，或权利要求18-23任一项所述的通信方法。
  51. 一种芯片系统，其特征在于，包括：
    存储器，用于存储计算机程序；
    处理器，用于从所述存储器调用并运行所述计算机程序，使得安装有所述芯片系统的设备执行如权利要求1-5任一项，或权利要求6-11任一项，或权利要求12-17任一项，或权利要求18-23任一项所述的通信方法。
  52. 一种计算机可读存储介质，包括计算机程序，当其在计算机上运行时，使得所述计算机执行如权利要求1-5任一项，或权利要求6-11任一项，或权利要求12-17任一项，或权利要求18-23任一项所述的通信方法。
  53. 一种计算机程序产品，所述计算机程序产品包括计算机程序，当所述计算机程序在计算机上运行时，使得计算机执行如权利要求1-5任一项，或权利要求6-11任一项，或权利要求12-17任一项，或权利要求18-23任一项所述的通信方法。
  54. 一种用来执行权利要求1-5任一项所述的通信方法的装置。
  55. 一种用来执行权利要求6-11任一项所述的通信方法的装置。
  56. 一种用来执行权利要求12-17任一项所述的通信方法的装置。
  57. 一种用来执行权利要求18-23任一项所述的通信方法的装置。
PCT/CN2020/089808 2019-07-22 2020-05-12 一种通信方法及装置 WO2021012750A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP20844902.5A EP3975593A4 (en) 2019-07-22 2020-05-12 COMMUNICATION METHOD AND APPARATUS
JP2022504060A JP7346706B2 (ja) 2019-07-22 2020-05-12 通信方法及び装置
US17/581,123 US20220150139A1 (en) 2019-07-22 2022-01-21 Communication method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910661345.4A CN112291725B (zh) 2019-07-22 2019-07-22 一种通信方法及装置
CN201910661345.4 2019-07-22

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/581,123 Continuation US20220150139A1 (en) 2019-07-22 2022-01-21 Communication method and apparatus

Publications (1)

Publication Number Publication Date
WO2021012750A1 true WO2021012750A1 (zh) 2021-01-28

Family

ID=74193096

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/089808 WO2021012750A1 (zh) 2019-07-22 2020-05-12 一种通信方法及装置

Country Status (5)

Country Link
US (1) US20220150139A1 (zh)
EP (1) EP3975593A4 (zh)
JP (1) JP7346706B2 (zh)
CN (2) CN112291725B (zh)
WO (1) WO2021012750A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015196433A1 (zh) * 2014-06-26 2015-12-30 华为技术有限公司 一种处理上行数据的方法和装置
CN108809667A (zh) * 2017-05-02 2018-11-13 中兴通讯股份有限公司 Pcrf实体、存储介质、竞态条件解除方法及系统
WO2019011794A1 (en) * 2017-07-12 2019-01-17 Nokia Solutions And Networks Oy OFFLINE INVOICING CONTINUITY IN NEXT GENERATION NETWORKS
CN109428734A (zh) * 2017-08-30 2019-03-05 中兴通讯股份有限公司 计费实现系统、计费实现方法及计费管理功能实体

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9231774B2 (en) 2012-09-27 2016-01-05 Alcatel Lucent Congestion control for radio access networks (RAN)
US9077821B2 (en) * 2012-12-27 2015-07-07 Telefonaktiebolaget L M Ericsson (Publ) Maximizing end-user's quality of experience within a mobile data plan
US9471937B2 (en) * 2013-12-16 2016-10-18 Verizon Patent And Licensing Inc. Download account with shared data plan
CN105307219A (zh) * 2014-06-20 2016-02-03 中国电信股份有限公司 对通信业务进行服务质量控制的方法和系统
CN105450552B (zh) * 2014-07-02 2018-12-14 阿尔卡特朗讯 基于sdn网络对应用服务链的策略与计费控制方法与设备
KR20160042692A (ko) * 2014-10-10 2016-04-20 삼성전자주식회사 트래픽 처리를 위한 방법 및 장치
CN106612499A (zh) * 2015-10-22 2017-05-03 华为技术有限公司 带宽和计费策略处理的方法和装置
US9986104B2 (en) * 2016-08-30 2018-05-29 Verizon Patent And Licensing Inc. Routing of diameter protocol messages based on a subscriber policy
CN108270808B (zh) * 2016-12-30 2021-04-09 华为技术有限公司 一种实现应用检测与控制的方法、装置和系统
KR20200035146A (ko) 2017-08-11 2020-04-01 콘비다 와이어리스, 엘엘씨 통신 네트워크에서의 네트워크 데이터 애널리틱스
CN109548063B (zh) 2017-09-20 2020-09-04 华为技术有限公司 处理报文的方法、装置、设备及存储介质
CN109936460B (zh) * 2017-12-18 2021-11-02 中兴通讯股份有限公司 一种流量计费的方法及设备
CN109831752B (zh) * 2019-04-03 2021-04-16 深圳联想懂的通信有限公司 一种通信流量控制方法和系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015196433A1 (zh) * 2014-06-26 2015-12-30 华为技术有限公司 一种处理上行数据的方法和装置
CN108809667A (zh) * 2017-05-02 2018-11-13 中兴通讯股份有限公司 Pcrf实体、存储介质、竞态条件解除方法及系统
WO2019011794A1 (en) * 2017-07-12 2019-01-17 Nokia Solutions And Networks Oy OFFLINE INVOICING CONTINUITY IN NEXT GENERATION NETWORKS
CN109428734A (zh) * 2017-08-30 2019-03-05 中兴通讯股份有限公司 计费实现系统、计费实现方法及计费管理功能实体

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
3GPP: "3GPP TSG SSA System Architecture for the 5G System; Stage 2(releease 15)", 3GPP TS 23.501 V15.3.0, 30 September 2018 (2018-09-30), pages 1 - 226, XP051487016, DOI: 20200801060456Y *
NOKIA ET AL.: "PDR ID for Predefined PDRs", 3GPP TSG CT WG4 MEETING #85 BIS C4-185191, 13 July 2018 (2018-07-13), XP051472304 *

Also Published As

Publication number Publication date
US20220150139A1 (en) 2022-05-12
CN112291725A (zh) 2021-01-29
EP3975593A4 (en) 2022-08-03
JP2022541816A (ja) 2022-09-27
JP7346706B2 (ja) 2023-09-19
CN112291725B (zh) 2021-11-09
EP3975593A1 (en) 2022-03-30
CN113891301B (zh) 2022-11-22
CN113891301A (zh) 2022-01-04

Similar Documents

Publication Publication Date Title
US11277522B2 (en) Service domain charging systems and methods
US10498657B2 (en) System and method for account level maximum bit rate enforcement
US8989047B2 (en) Rules system versions
US8897749B1 (en) Policy decisions based on subscriber spending limits
US20110320622A1 (en) Managing internet protocol connectivity access network sessions
MX2012013659A (es) Servicios asistidos por dispositivo para proteger la capacidad de una red.
JP7478267B2 (ja) 課金方法、装置、及びシステム
US20120250613A1 (en) Rules system version cloning
CN111130855B (zh) 一种问题定位方法和装置
US20150236914A1 (en) Method and node for controlling resources for a media service as well as a corresponding system and computer program
CN111466101A (zh) 用于电子通信设备的策略调节的方法和装置
US11470202B2 (en) Charging method, apparatus, and system
WO2020135848A1 (zh) 计费的方法、装置及系统
US20190182838A1 (en) Arrangement and method for dynamic quota allocation in communication network
US20150312761A1 (en) Enhanced authentication for provision of mobile services
WO2019210780A1 (zh) 计费方法、设备及系统
WO2022110152A1 (zh) 数据用量更新方法、装置及系统
US20110282981A1 (en) Behavioral rule results
WO2021012750A1 (zh) 一种通信方法及装置
JP7132239B2 (ja) マシンツーマシンネットワーク最適化およびオンライン課金
EP4064756B1 (en) Bandwidth throttling in a radio access network
US11736623B2 (en) Systems and methods for granular charging in mobile wireless networks
WO2019007387A1 (en) BANDWIDTH SHARING BETWEEN A PLURALITY OF FLOWS
WO2023179709A1 (zh) 信息处理方法、装置、通信设备及可读存储介质
WO2016206071A1 (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: 20844902

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020844902

Country of ref document: EP

Effective date: 20211221

ENP Entry into the national phase

Ref document number: 2022504060

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE