WO2017114220A1 - Procédé de surveillance de quantité de terminaux utilisateur et dispositif associé - Google Patents

Procédé de surveillance de quantité de terminaux utilisateur et dispositif associé Download PDF

Info

Publication number
WO2017114220A1
WO2017114220A1 PCT/CN2016/110798 CN2016110798W WO2017114220A1 WO 2017114220 A1 WO2017114220 A1 WO 2017114220A1 CN 2016110798 W CN2016110798 W CN 2016110798W WO 2017114220 A1 WO2017114220 A1 WO 2017114220A1
Authority
WO
WIPO (PCT)
Prior art keywords
transmission
policy
event
pcrf
transmission event
Prior art date
Application number
PCT/CN2016/110798
Other languages
English (en)
Chinese (zh)
Inventor
叶婉玲
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2017114220A1 publication Critical patent/WO2017114220A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • 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

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method for monitoring the number of user terminals and related devices.
  • the 3rd Generation Partnership Project (3GPP) introduced the Service Capability Exposure Function (SCEF) to study the opening of the operator's network capabilities to application providers.
  • SCEF Service Capability Exposure Function
  • the SCEF forwards the service data transmission request sent by the application device in the application provider to a Policy and Charging Rules Function (PCRF), so that the PCRF formulates a transmission policy (for example, transmission) for transmitting the service data.
  • PCRF Policy and Charging Rules Function
  • the time window, the traffic rate corresponding to the time window, etc.) the PCRF specifically obtains the user subscription information from the User Profile Repository (SPR) or the User Data Repository (UDR), and the operator configuration
  • SPR User Profile Repository
  • UDR User Data Repository
  • the policy is used to determine the transmission policy from multiple policies in combination with the network congestion level/load status, and the determined transmission policy is delivered to the Policy and Charging Enforcement Function (PCEF) or bearer binding.
  • PCEF Policy and Charging Enforcement Function
  • Bearer Binding and Event Report Function BBERF
  • TDF Traffic Detection and Control
  • the embodiment of the invention provides a method for monitoring the number of user terminals and related devices, which can monitor the number of user terminals related to the transmission event and transmit events exceeding the threshold of the number of user terminals when the transmission device reports a transmission event. Transfer control is performed to save transmission costs.
  • a first aspect of the embodiments of the present invention provides a method for monitoring the number of user terminals, where the monitoring device receives a notification message that the transmission device reports a transmission event, where the notification message carries a policy identifier, and the monitoring The device increases the number of statistics corresponding to the policy identifier by one, and when the number of statistics is greater than a threshold of the number of user terminals associated with the policy identifier, the monitoring device performs transmission control on the transmission event.
  • the number of statistics recorded by the monitoring device is the number of times the transmission device reports the notification message that the transmission event is detected, and one transmission event corresponds to one user terminal. Therefore, the statistics count recorded by the monitoring device is related to the transmission event.
  • the number of user terminals By reporting the transmission event on the transmission device, the number of user terminals related to the transmission event is monitored, and the transmission event exceeding the threshold of the number of user terminals is transmitted and controlled to save transmission costs.
  • the monitoring device is a policy and charging rule entity PCRF.
  • the transmission event is used to indicate that the service data is transmitted; and the PCRF receives the notification message that is detected by the transmission device and detects the transmission event.
  • the threshold of the number of user terminals sent by the application device is also received to monitor the number of user terminals related to the transmission event.
  • the application device may carry the user terminal quantity threshold in the policy negotiation request sent to the PCRF, where the policy negotiation request is to determine a target transmission policy for transmitting service data, where the policy negotiation request may further include The information of the transmitted service data size, the expected time window, and the like, so that the PCRF determines the target transmission policy according to the information in the policy negotiation request, where the target transmission policy includes a policy identifier that uniquely identifies the target transmission policy, and may further include indicating the application device a preset time window for transmitting the service data, a charging rate of the preset time window, and the like.
  • the PCRF After receiving the threshold number of the user terminal, the PCRF obtains a preset transmission policy from the user subscription database SPR or the user data storage UDR; the PCRF determines the transmission station according to the preset transmission policy and the current network state.
  • a target transmission policy of the service data the target transmission policy including a policy identifier for uniquely identifying the target transmission policy.
  • the PCRF determines the preset transmission policy to transmit the service data.
  • the target transmission policy is sent to the application device, so that the application device sends the transmission event according to information such as a preset time window in the target transmission policy.
  • the PCRF sends all or part of the plurality of preset transmission policies to the application device, so that the application device selects one of the policies as the target transmission policy and The selected target transmission policy is fed back to the monitoring device, so that the monitoring device can monitor the transmission event according to the target transmission policy.
  • the PCRF sends the target transmission policy to the transmission device. For example, a preset time window indicating that the application device transmits the service data, a policy identifier uniquely identifying the target transmission policy, a charging rate of the preset time window, and the like are sent to the transmission device, so that the transmission device according to the The information reports the detected transmission event to the monitoring device.
  • the PCRF may send the target code identifier corresponding to the target transmission policy to the transmission device, and the transmission may determine a corresponding target transmission policy according to the target code identifier.
  • the monitoring device is an SPR or a UDR.
  • the SPR or the UDR before receiving the notification message of the transmission event reported by the transmission device, is required to receive the user terminal sent by the PCRF.
  • a quantity threshold, the user terminal number threshold is sent by the application device to the PCRF for monitoring the number of user terminals related to the transmission event.
  • the transmission event is used to indicate transmission service data; the SPR or UDR reception Before the notification message of the transmission event is detected by the transmission device, the target transmission policy for the application device to transmit the service data may be determined, where the target transmission policy may include a policy identifier that uniquely identifies the target transmission policy, and may also include And a preset time window for instructing the application device to transmit the service data, a charging rate of the preset time window, and the like.
  • the preset transmission policy may be determined to be transmitted.
  • the target transmission policy of the service data is sent to the application device, so that the application device sends the transmission event according to information such as a preset time window in the target transmission policy.
  • receiving, by the PCRF, a target transmission policy for transmitting the service data if the SPR or the UDR stores a plurality of preset transmission policies.
  • the monitoring device receives the transmission device
  • the reported notification message for detecting the transmission event is specifically a notification message that the SPR or the UDR receiving transmission device forwards the PCR event to detect the transmission event.
  • the transmission event includes the policy identifier;
  • the device performs transmission control on the transmission event, where the monitoring device instructs the transmission device to perform packet loss processing on a transmission event carrying the policy identifier and/or send an indication to the application device that initiates the transmission event that the transmission device has reached the location
  • the prompt message of the threshold number of the user terminal is used to enable the application device to feedback whether to continue the transmission of the confirmation message, which can effectively save network resources.
  • the second aspect of the embodiments of the present invention provides another method for monitoring the number of user terminals, including: the transmission device receives a transmission event sent by the application device, and the transmission device determines whether the transmission event is reported to the monitoring device, when the determination result is If not, the transmitting device reports a notification message that the transmission event is detected to the monitoring device, where the notification message carries a policy identifier.
  • the transmitting device may report the unreported notification message that the transmission event is detected to the monitoring device, so that the monitoring device monitors the number of user terminals related to the transmission event.
  • the same transmission event is repeatedly reported, thereby improving the accuracy of monitoring the number of user terminals by the monitoring device.
  • the transmission event is used to indicate that the service data is transmitted; and before the transmission device receives the transmission event sent by the application device, the transmission device needs to receive the transmission sent by the PCRF.
  • a target transmission policy of the service data the target transmission policy includes an identifier for uniquely identifying the target transmission policy, so that after the transmission device determines the policy identifier of the transmission event, acquiring a target transmission policy corresponding to the policy identifier, The transmission event is detected and judged according to the target transmission strategy.
  • the target transmission policy further includes: a preset time window for transmitting the service data; the transmission event includes the policy identifier
  • the method further includes: the transmission device determining, according to the policy identifier in the transmission event, a target transmission policy corresponding to the policy identifier, where the transmission device determines the transmission Whether the time of occurrence of the event is within a preset time window of the target transmission policy, and when it is determined that the occurrence time of the transmission event is within a preset time window of the target transmission policy, the transmission device determines whether to monitor The device reported the transmission event.
  • the transmitting device reports the detected location to the monitoring device After the notification message of the transmission event, the transmission device records the transmission event record indicating that the transmission event has been reported.
  • the transmitting The device includes a Policy and Charging Enforcement Entity PCEF, a Bearer Binding, and an Event Reporting Entity BBERF or a Traffic Detection Entity TDF.
  • a third aspect of the embodiments of the present invention provides a monitoring device, which has the function of realizing the behavior of the monitoring device in the foregoing method.
  • the functions may be implemented by hardware, or may be implemented by hardware correspondingly.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the structure of the monitoring device includes a processor and a memory for storing application code supporting the monitoring device to perform the above method, the processor being configured to perform the storage in the memory s application.
  • the monitoring device can also include a communication interface for monitoring the device to communicate with other devices or communication networks.
  • a fourth aspect of the embodiments of the present invention provides a transmission device, which has the function of implementing the behavior of the transmission device in the foregoing method.
  • the functions may be implemented by hardware, or may be implemented by hardware correspondingly.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the structure of the transmission device includes a processor and a memory for storing application code supporting the transmission device to perform the above method, the processor being configured to perform the storage in the memory s application.
  • the transmission device may also include a communication interface for the transmission device to communicate with other devices or communication networks.
  • a fifth aspect of the embodiments of the present invention provides a monitoring system for the number of user terminals, where the system includes a monitoring device and a transmission device, where the monitoring device may be the monitoring device introduced in the first aspect and the third aspect.
  • the transmission device can be the transmission device described in the second aspect and the third aspect.
  • a sixth aspect of the embodiments of the present invention provides a computer storage medium for storing computer software instructions for use in the monitoring device, including a program designed to perform the above aspects for a monitoring device.
  • a seventh aspect of the embodiments of the present invention provides a computer storage medium for storing computer software instructions for use in the foregoing transmission device, comprising a program designed to execute the above aspects for a transmission device.
  • the names of the monitoring device, the transmission device, and the application device are not limited to the device itself. In actual implementation, these devices may appear under other names. As long as the functions of the respective devices are similar to the present invention, they are within the scope of the claims and the equivalents thereof.
  • the solution provided by the present invention can monitor the number of user terminals related to the transmission event, and perform transmission control on the transmission event exceeding the threshold number of the user terminal, in the case that the transmission device reports the transmission event. Save on transmission costs.
  • the transmission device determines whether the transmission event is reported, and avoids repeatedly reporting the same transmission event, thereby improving the accuracy of monitoring the number of user terminals by the monitoring device.
  • FIG. 1 is a schematic diagram of a possible system network according to an embodiment of the present invention.
  • FIG. 2 is a schematic diagram of a monitoring system for the number of user terminals according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of a computer device according to an embodiment of the present invention.
  • FIG. 4 is a schematic flowchart of a method for monitoring the number of user terminals according to an embodiment of the present invention
  • FIG. 5 is a schematic flowchart of another method for monitoring the number of user terminals according to an embodiment of the present invention.
  • FIG. 6 is a schematic flowchart of another method for monitoring the number of user terminals according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a monitoring device according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of a transmission device according to an embodiment of the present invention.
  • FIG. 1 is a schematic diagram of a possible system network according to an embodiment of the present invention.
  • the system network diagram includes: AS/SCS, SPR/UDR, PCEF/BBERF/TDF, and PCRF.
  • AS/SCS needs to transmit service data to multiple user terminals
  • the AS/SCS and the PCRF perform policy negotiation to determine a transmission policy for transmitting the service data.
  • the PCRF obtains multiple configured policies from the SPR/UDR, and The transmission policy for transmitting the service data is determined in multiple policies, and the PCRF sends the determined transmission policy to the PCEF/BBERF/TDF for execution.
  • the PCRF notifies the SPR/UDR of the determined transmission policy.
  • the transmission policy may further include a time window for transmitting the service data, a charging rate of the time window, a maximum aggregation bit rate, and the like.
  • the AS/SCS transmits the service data to a plurality of user terminals according to the determined transmission policy.
  • the AS/SCS communicates with the PCRF through the SCEF.
  • the SCEF and the PCRF communicate through the Nt interface, and the AS/SCS and the PCRF transmit before the transmission.
  • the service data of the service data for example, AS/SCS identifier, UE identifier, service data, and the like
  • the SCEF communicates with the PCRF through the Rx interface; and the application programming interface can be invoked between the AS/SCS and the SCEF ( Application Programming Interface (API) communication, optionally, SCEF can be provided by AS/SCS.
  • the SPR stores information related to all contracted users or subscriptions, multiple policies configured, and the like.
  • the PCRF communicates with the PCEF/BBERF/TDF through the Gx interface, and the PCRF sends the determined transmission policy to the PCEF/BBERF/TDF for execution, specifically sending the installation/modification/deletion policy and charging control (Policy and Charging Control) to the PCEF.
  • PCC a request for a rule; or a request to install/modify/delete an ADC rule to a PCEF supporting Application Detection and Control (ADC) rules, in order to add a determined transmission policy to the PCC rule or In the ADC rules, the PCEF is executed according to the rules.
  • FIG. 2 is a schematic diagram of a monitoring system for the number of user terminals according to an embodiment of the present invention.
  • the monitoring system of the number of user terminals includes a monitoring device 201 and a transmission device 202.
  • the monitoring device 201 may be the PCRF in FIG. 1 or the SPR/UDR in FIG. 1 or other gateway devices, which is not limited by the present invention; the transmission device 202 may be a figure in practice.
  • the PCEF/BBERF/TDF in 1 can also be other gateway devices.
  • the "monitoring device” and "transport device” are just a name, and the name itself does not limit the device.
  • the monitoring device 201 and the transmission device 202 in FIG. 2 can be implemented in the manner of the computer device in FIG.
  • FIG. 3 is a schematic diagram of a computer device according to an embodiment of the present invention. As shown in FIG. 3, the computer device 3 includes at least one processor 301, a communication bus 302, a memory 303, and at least one communication interface 304.
  • Processor 301 can be a general purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present invention.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • Communication bus 302 can include a path for communicating information between the components described above.
  • the communication interface 304 uses devices such as any transceiver for communicating with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Networks (WLAN), and the like.
  • RAN Radio Access Network
  • WLAN Wireless Local Area Networks
  • the memory 303 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions.
  • the dynamic storage device can also be an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this.
  • the memory can exist independently and be connected to the processor via a bus.
  • the memory can also be integrated with the processor.
  • the memory 303 is used to store application code for executing the solution of the present invention, and is controlled by the processor 301 for execution.
  • the processor 301 is configured to execute application code stored in the memory 303.
  • processor 301 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • computer device 3 may include multiple processors, such as processor 301 and processor 307 in FIG. Each of these processors can be a single-CPU processor or a multi-core processor.
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
  • computer device 3 may also include an output device 305 and an input device 306.
  • Output device 305 is in communication with processor 301 and can display information in a variety of ways.
  • the output device 305 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector.
  • Input device 306 is in communication with processor 301 and can accept user input in a variety of ways.
  • input device 306 can be a mouse, keyboard, touch screen device, or sensing device, and the like.
  • the computer device 3 described above may be a general purpose computer device or a special purpose computer device.
  • the computer device 3 may be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, a communication device, an embedded device, or have FIG. A device of similar structure.
  • PDA personal digital assistant
  • the embodiment of the invention does not limit the type of computer device 3.
  • the monitoring device 201 in FIG. 2 may be the computer device 3 shown in FIG. 3, and the memory 303 of the computer device 3 stores one or more software modules (eg, a policy determination module, a first interaction module, a monitoring module, etc.).
  • the monitoring device 201 can implement the software module through the processor and the program code in the memory, and realize the monitoring of the number of user terminals related to the transmission event and the transmission of the threshold exceeding the number of user terminals in the case of reporting the transmission event on the transmission device. Events are transmitted and controlled to save on transmission costs.
  • the transmission device 202 in FIG. 2 may be the computer device 3 shown in FIG. 3, and the memory 303 of the computer device 3 stores one or more software modules (eg, a second interaction module, an event determination module, etc.).
  • the transmission device 202 can implement the software module by using the processor and the program code in the memory to report the unreported notification message of the detected transmission event to the monitoring device, so that the monitoring device monitors the number of user terminals related to the transmission event. .
  • the same transmission event is repeatedly reported, thereby improving the accuracy of monitoring the number of user terminals by the monitoring device.
  • FIG. 4 is a schematic flowchart diagram of a method for monitoring the number of user terminals according to an embodiment of the present invention. As shown in FIG. 4, the method of the embodiment of the present invention may include the following steps S401-S407.
  • the application device sends a transmission event to the transmission device.
  • the application device sends a transmission event to the transmission device.
  • the transmission event is a transmission of service data (for example, an upgrade package, etc.) to the UE.
  • the transmission event may include a target UE identifier, so that the service data is transmitted according to the target UE identifier, where the target UE identifier may include an Internet Protocol (IP) address interconnected between the UE's networks, Port number and so on.
  • IP Internet Protocol
  • the user equipment UE involved in the present application may include various handheld devices, wireless devices, wearable devices, computing devices, or other processing devices connected to the wireless modem, and various forms of user equipment.
  • MS Mobile station
  • terminal equipment terminal equipment
  • soft terminal soft terminal
  • the above mentioned devices are collectively referred to as a user terminal or a UE.
  • the transmission device receives a transmission event sent by the application device.
  • the transmitting device receives the transmission event sent by the application device, and further performs step S403 to determine the transmission event.
  • the transmission device determines whether the transmission event is reported to the monitoring device.
  • the transmitting device determines whether the transmission event is reported to the monitoring device.
  • the transmission event carries the target UE identifier, and the transmission device determines whether the transmission event about the target UE identifier is reported to the monitoring device.
  • the transmission device may record the identifier of the transmission event that has been reported, for example, after the transmission event is reported, the transmission device will transmit the target UE identifier and the reported identifier carried by the transmission event.
  • the association saves, so that when the other transmission events are received subsequently, it is determined by the recorded information whether the transmission event is reported to the monitoring device.
  • the transmitting device reports, to the monitoring device, a notification message that the transmission event is detected, where the notification message carries a policy identifier.
  • the transmitting device reports a notification message that the transmission event is detected to the monitoring device, where the notification message carries a policy identifier.
  • the policy identifier is a policy identifier for uniquely identifying a target transmission policy for transmitting the service data.
  • the transmission event represents a transmission service data
  • the target transmission policy is a policy for transmitting service data that is determined by the application device and the PCRF before the application device sends the transmission event
  • the target transmission policy may include a unique identification of the target transmission policy.
  • the policy identifier may further include a preset time window for instructing the application device to transmit the service data, a charging rate of the preset time window, and the like.
  • the transmission event includes a policy identifier
  • the transmission device may determine a policy identifier carried in the reported notification message according to the policy identifier in the transmission event.
  • the PCRF further sends the multiple UE identifiers of the transmission service data sent by the application device to the transmission device, where the transmission device may transmit the policy and multiple UEs.
  • the identifier association is saved, and the policy identifier in the target transmission policy associated with the target UE identifier is determined according to the target UE identifier in the transmission event, and further, the policy identifier carried in the reported notification message is determined.
  • the monitoring device receives a notification message that is detected by the transmission device and detects a transmission event, where the notification message carries a policy identifier.
  • the monitoring device increases the number of statistics corresponding to the policy identifier by one.
  • the monitoring device increases the number of statistics corresponding to the policy identifier by one.
  • the number of statistics corresponding to the policy identifier is used to record the number of reported transmission events. It can be seen that the monitoring device counts the number of transmission events that are not repeatedly sent by the application device. Since one transmission event is for one UE, the current statistical count corresponding to the policy identifier is the transmission service. The current number of user terminals for the data.
  • the monitoring device performs transmission control on the transmission event.
  • the number of statistics is greater than a threshold of the number of user terminals associated with the policy identifier.
  • the number of UEs that actually transmit the service data is greater than the threshold of the number of user terminals associated with the policy identifier.
  • the monitoring device performs transmission control on the transmission event.
  • the monitoring device performs transmission control on the transmission event, and may instruct the transmission device to perform packet loss processing on the transmission event carrying the policy identifier.
  • the notification may be sent to the transmission device.
  • the monitoring device may further send a prompt message indicating that the threshold number of the user terminal has been reached to the application device that initiates the transmission event, so that the application device determines whether to continue to perform the transmission by the monitoring device. The event will be sent back to the monitoring device after the message is determined.
  • the monitoring device performs transmission control on the transmission event, and may send a message to any one of the application device and the transmission device, or two devices, which are not limited in this embodiment of the present invention.
  • the transmitting device reports the unreported notification message that the transmission event is detected to the monitoring device, where the notification message carries the policy identifier, and the monitoring device increases the number of statistics corresponding to the policy identifier by one, when the number of statistics is greater than
  • the monitoring device performs transmission control on the transmission event.
  • the number of statistics recorded by the monitoring device is the number of times the transmission device reports the notification message that the transmission event is detected.
  • One transmission event corresponds to one user terminal. Therefore, the number of statistics recorded by the monitoring device is the number of user terminals related to the transmission event.
  • the transmission device By reporting the transmission event on the transmission device, the number of user terminals related to the transmission event is monitored, and the transmission event exceeding the threshold of the number of user terminals is transmitted and controlled to save transmission costs.
  • the transmission device avoids repeatedly reporting the same transmission event by judging whether the transmission event is reported, thereby improving the accuracy of monitoring the number of user terminals by the monitoring device.
  • FIG. 5 is a schematic flowchart diagram of another method for monitoring the number of user terminals according to an embodiment of the present invention.
  • the application device takes the AS as an example
  • the transmission device takes the PCEF as an example
  • the monitoring device takes the PCRF as an example, and further includes an SPR/UDR.
  • the method of the embodiment of the present invention may include the following steps S501 to S517.
  • the AS sends a threshold number of user terminals to the PCRF.
  • the AS sends a threshold of the number of user terminals to the PCRF, where the threshold of the number of user terminals is a maximum value of the number of user terminals that receive the transmission event sent by the AS, so that the PCRF performs the number of user terminals related to the transmission event. monitor.
  • the AS when it transmits service data through the carrier network, it needs to perform policy negotiation with the PCRF to determine a target transmission policy for transmitting the service data. Therefore, the AS sends a policy negotiation request to the PCRF.
  • the policy negotiation request carries a threshold number of the user terminal, where the policy negotiation request may further include information such as a service data size and a desired time window to be transmitted, so as to facilitate The PCRF negotiates a transmission strategy that is more capable of meeting AS requirements.
  • the user equipment UE involved in the present application may include various handheld devices, wireless devices, wearable devices, computing devices, or other processing devices connected to the wireless modem, and various forms of user equipment.
  • MS Mobile station
  • terminal equipment terminal equipment
  • soft terminal soft terminal
  • the above mentioned devices are collectively referred to as a user terminal or a UE.
  • the PCRF receives the threshold of the number of user terminals sent by the AS, and saves the threshold of the number of the user terminals, after the AS transmission event reported by the PCEF is received, and determines whether to The secondary transmission event is transmitted and controlled.
  • the PCRF sends a preset transmission policy acquisition request to the SPR/UDR. Accordingly, the SPR/UDR receives the preset transmission policy acquisition request.
  • the SPR/UDR sends a preset transmission policy to the PCRF. Accordingly, the SPR/UDR receives the preset transmission policy.
  • the PCRF acquires a preset transmission policy from the SPR/UDR, where the preset transmission policy includes one or more time windows that can be used to transmit service data, and traffic corresponding to each time window. Rates, etc.
  • the PCRF determines, according to the preset transmission policy and a current network state, a target transmission policy for transmitting the service data, where the target transmission policy includes a policy identifier for uniquely identifying the target transmission policy.
  • the PCRF determines, according to the preset transmission policy and the current network status, a target transmission policy for transmitting the service data, where the current network status includes a congestion level, a load status, and the like.
  • the target transmission policy includes a policy identifier for uniquely identifying the target transmission policy.
  • the PCRF saves the determined target transmission policy in association with the user terminal number threshold. In a feasible solution, the number of preset transmission policies acquired by the PCRF is different, and the corresponding manner of determining the target transmission strategy is also different, and is divided into the following two cases.
  • the PCRF determines the preset transmission policy as a target transmission policy, and determines a policy identifier of the target transmission policy, where the policy identifier uniquely identifies The target transmission policy, the PCRF sends the target transmission policy carrying the policy identifier to the AS, and the AS saves the target transmission policy, so that the AS sends a transmission event to the PCEF according to a preset time window in the target transmission policy.
  • the PCRF determines a candidate transmission policy according to the preset transmission policy and the current network state.
  • the PCRF may further The information about the desired time window in the policy negotiation request sent by the AS selects a candidate transmission policy.
  • the candidate transmission policy is determined as a target transmission policy, and the target transmission policy is determined.
  • the policy identifier uniquely identifies the target transmission policy
  • the PCRF sends the target transmission policy carrying the policy identifier to the AS, and correspondingly, the AS receives the target transmission policy; when the number of candidate transmission policies determined by the PCRF is two
  • the PCRF determines the policy identifier of the candidate transmission policy, and sends two or more candidate transmission policies carrying the policy identifier to the AS, so that the AS is from the received candidate transmission policy.
  • Selecting a policy as the target transmission policy the AS saves the target transmission policy and sends a response carrying the target transmission policy to the PCRF.
  • Target transmission policy information respectively, the PCRF receives the AS response message carried.
  • the PCRF sends the target transmission policy and the number of user terminals to the SPR/UDR. Accordingly, the SPR/UDR receives the target transmission policy and the number of user terminal thresholds.
  • the PCRF sends the target transmission policy and the number of user terminals to the SPR/UDR, so that the SPR/UDR associates the determined target transmission policy with the threshold number of user terminals.
  • this step is an optional step for assisting the PCRF to store information.
  • the AS sends service information about the service data to the PCRF.
  • the AS sends, to the PCRF, service information related to the transmission of the service data, where the service involved in transmitting the service data is
  • the information may include a device identifier (eg, an AS identifier) that sends the service data, multiple UE identifiers that receive the service data, service data, a preset time window in the target policy, and a policy identifier, where the device identifier and the UE identifier may include the UE.
  • the IP address, the port number, and the like, the device identifier and the UE identifier in the service information may be in the form of IP quintuple information, IP quaternary group information, and the like.
  • the AS sends the preset time window and the policy identifier in the target transmission policy to the PCRF, so that the PCRF authenticates and authorizes the service information sent by the AS.
  • the PCRF receives service information about the service data sent by the AS.
  • the PCRF authenticates the service information related to the transmission of the service data, specifically according to the received service information.
  • the policy identifier identifies an IP-Connectivity Access Network (IP-CAN) session. If the session is successful, the process proceeds to step S507. If the session does not exist, the authentication fails. The AS sends a notification message that the authentication fails.
  • IP-CAN IP-Connectivity Access Network
  • step S506 may be performed at any time before the preset time window in which the AS included in the target transmission policy transmits the service data. This embodiment of the present invention does not limit this.
  • the PCRF sends service information and a target transmission policy about the service data to the PCEF.
  • the PCRF sends service information and a target transmission policy about the service data to the PCEF.
  • the PCRF may send the service information about the service data and the target code identifier corresponding to the target transmission policy to the transmission device, and the transmission may determine a corresponding target transmission policy according to the target code identifier.
  • the sending, by the PCRF, the target transmission policy to the PCEF may be sending a request to install/modify/delete a PCC rule to a PCEF, or sending an install/modify/delete ADC rule to a PCEF supporting an ADC rule.
  • the request wherein the target transmission policy or the target code identifier may be carried in the sent request.
  • the purpose is to add the determined target transmission policy to the PCC rules or ADC rules so that the PCEF performs according to the rules.
  • the PCRF may send service information about the service data to the PCEF at different times and send a target transmission policy to the PCEF.
  • the PCEF receives service information and a target transmission policy regarding the service data.
  • the PCEF after receiving the service information about the service data and the target transmission policy, the PCEF adds the received target transmission policy to a PCC rule or an ADC rule to follow the received transmission event according to the rule.
  • the PCRF is reported.
  • the AS sends a transmission event to the PCEF.
  • the AS sends a transmission event to the PCEF.
  • the transmission event is a transmission of service data (for example, an upgrade package, etc.) to the UE.
  • the transmission event may include a target UE identifier of the transmission event, so that the service data is transmitted according to the target UE identifier, where the target UE identifier may include an IP address, a port number, and the like of the UE.
  • the PCEF receives a transmission event sent by the AS.
  • the PCEF determines whether a time of occurrence of the transmission event is within a preset time window of the target transmission policy.
  • the PCEF After receiving the transmission event sent by the AS, the PCEF acquires an occurrence time of the transmission event, and determines whether the occurrence time of the transmission event is within a preset time window of the target transmission policy, if In the preset time window of the target transmission policy, step S510 is performed; if not in the preset time window of the target transmission policy, the process ends, or the sending to the AS is not sent within the preset time window.
  • the PCEF determines whether the transmission event is reported to the PCRF.
  • the PCEF determines whether the transmission event is reported to the PCRF, and if the transmission event is reported, the process ends, or And sending, to the AS, a notification message that the transmission event has been reported; if the transmission event is not reported, step S511 is performed.
  • the transmission event carries the target UE identifier, and the PCEF determines whether the transmission event about the target UE identifier is reported to the PCRF.
  • the PCEF reports a notification message that the transmission event is detected to the PCRF, where the notification message carries a policy identifier.
  • the PCEF reports a notification message that the transmission event is detected to the PCRF, where the notification message carries a policy identifier.
  • the policy identifier is a policy identifier for uniquely identifying a target transmission policy for transmitting the service data.
  • the transmission event represents a transmission service data
  • the target transmission policy is a policy for transmitting service data determined by the AS and the PCRF before the AS sends the transmission event
  • the target transmission policy may include a policy identifier that uniquely identifies the target transmission policy.
  • the transmission event includes a policy identifier
  • the PCEF may determine a policy identifier carried in the reported notification message according to the policy identifier in the transmission event.
  • the PCRF after the AS and the PCRF determine the target transmission policy for transmitting the service data, the PCRF sends the multiple UE identifiers of the transmission service data sent by the AS to the PCEF, and the PCEF may save the transmission policy and the multiple UE identifiers. And determining, according to the target UE identifier in the transmission event, the policy identifier in the target transmission policy that is associated with the target UE identifier, and further determining the policy identifier carried in the reported notification message.
  • the PCEF determines the transmission event for the preset time window in the target transmission policy, and also determines whether the transmission event is reported to the PCRF, because the transmission event carries the transmission service.
  • a target UE identifier of the data and the PCEF receives service information about the service data, and thus the PCEF And determining whether the target UE identifier in the transmission event exists in the service information of the service data, if yes, reporting the signal to the PCRF, if not, ending, or notifying the AS that the target UE identifier does not belong to A notification message for previously transmitted service information. It can enhance the accuracy of reported transmission events and avoid malicious attacks, thereby saving network resources.
  • the PCRF receives a notification message that is detected by the PCEF and detects a transmission event, where the notification message carries a policy identifier.
  • the PCRF feeds back an acknowledgement message to the PCEF.
  • the PCRF after receiving the notification message of the transmission event reported by the PCEF, the PCRF feeds back an acknowledgement message to the PCEF, where the acknowledgement message is used to indicate that the PCRF receives the notification message that the transmission event is detected. .
  • the PCEF indicates, to the transmission event record, that the identifier of the transmission event has been reported.
  • the PCEF indicates, to the transmission event record, that the identifier of the transmission event has been reported. For example, after the transmission event is reported, the PCEF associates the target UE identifier carried in the transmission event with the reported identifier, so as to determine whether the transmission event is reported to the PCRF through the recorded information when the subsequent transmission event is received.
  • the PCRF increases the number of statistics corresponding to the policy identifier by one.
  • the PCRF After receiving the notification message of the transmission event reported by the PCEF, the PCRF increases the number of statistics corresponding to the policy identifier by one.
  • the number of statistics corresponding to the policy identifier is used to record the number of reported transmission events. It can be seen that the PCRF counts the number of transmission events that are not repeatedly sent by the AS. Since one transmission event is for one UE, the current statistics counted by the PCRF corresponding to the policy identifier is the current data of the transmission service data. The number of user terminals.
  • the PCRF may perform step S512 and step S514 in parallel, or may perform step S512 and step S514, respectively, and step S512 and step S514. There is no order.
  • the PCRF determines whether the number of statistics is greater than a threshold number of user terminals associated with the policy identifier.
  • the PCRF determines whether the number of statistics is greater than a threshold number of user terminals associated with the policy identifier. When the number of statistics is greater than a threshold number of user terminals associated with the policy identifier, then steps S516 and/or S517 are performed. When the number of statistics is not greater than the number of user terminals associated with the policy identifier, the PCEF may perform the transmission event. In a feasible solution, the PCRF may send the statistics to the PCEF. A notification message that is greater than a threshold number of user terminals associated with the policy identifier to notify the PCEF to allow the transmission event to continue.
  • the PCEF may perform the transmission event according to the start; or in any step of step S511, step S512 or step S513 And then, the transmission event is started; or, in a feasible solution, the PCRF may send a notification message that the number of statistics is not greater than the threshold of the number of user terminals to the PCEF, so the PCEF may receive the PCRF sent.
  • the transmitting event is started after the notification message whose number of statistics is not greater than the threshold number of the user terminal.
  • the PCRF may not send the notification message that the number of statistics is not greater than the threshold of the number of user terminals to the PCEF, and the PCEF may be in the When the notification message indicating the packet loss processing sent by the PCRF is not received within a preset time range after the notification message of the transmission event is detected, the transmission event is started.
  • the PCRF instructs the PCEF to perform packet loss processing on the transmission event.
  • the PCRF indicates that the PCEF performs packet loss processing on the transmission event carrying the policy identifier.
  • the indication may be sent to the PCEF.
  • a prompt message that reaches the threshold of the number of user terminals is indicated.
  • the PCRF sends a prompt message to the AS indicating that the threshold number of the user terminals has been reached.
  • the PCRF may further send a prompt message indicating that the threshold of the number of user terminals has been reached to the AS that initiates the transmission event, so that The AS determines whether to continue the PCRF to perform the transmission event and feeds the determined message back to the PCRF.
  • the PCRF additionally charges the traffic fee generated by the transmission event.
  • Step S516 and step S517 are processes in which the PCRF performs transmission control on the transmission event when the number of statistics is greater than a threshold number of user terminals associated with the policy identifier.
  • the PCRF may perform any one or two steps of step S516 and step S517. If the PCRF performs two steps, step S516 and step S517 are not sequential.
  • the actions of the above PCRF may be performed by the PCRF in accordance with the software modules in the memory mentioned above.
  • S504 may be performed according to the policy determination module in FIG. 3;
  • S502, S505, S507, S512, S516, and S517 may be performed according to the first interaction module in FIG. 3;
  • S514 and S515 may be according to the monitoring module in FIG. To execute.
  • the actions of the PCEF described above can be performed by the PCEF in accordance with the software modules in the memory mentioned above.
  • S511 can be performed according to the second interaction module in FIG. 3;
  • S509, S510, and S513 can be performed according to the event determination module in FIG.
  • the transmitting device reports the unreported notification message that the transmission event is detected to the monitoring device, where the notification message carries the policy identifier, and the monitoring device increases the number of statistics corresponding to the policy identifier by one, when the number of statistics is greater than
  • the monitoring device performs transmission control on the transmission event.
  • the number of statistics recorded by the monitoring device is the number of times the transmission device reports the notification message that the transmission event is detected.
  • One transmission event corresponds to one user terminal. Therefore, the number of statistics recorded by the monitoring device is the number of user terminals related to the transmission event.
  • the transmission equipment By reporting the transmission event on the transmission device, the number of user terminals related to the transmission event is monitored, and the transmission event exceeding the threshold of the number of user terminals is transmitted and controlled to save transmission costs.
  • the transmission equipment passes After determining whether the transmission event is reported, the same transmission event is repeatedly reported, thereby improving the accuracy of monitoring the number of user terminals by the monitoring device.
  • FIG. 6 is a schematic flowchart diagram of another method for monitoring the number of user terminals according to an embodiment of the present invention.
  • the application device takes the AS as an example
  • the transmission device takes the PCEF as an example
  • the monitoring device takes the SPR/UDR as an example.
  • the method in the embodiment of the present invention may include the following step S601- Step S619.
  • the AS sends a threshold number of user terminals to the PCRF.
  • the AS sends a threshold of the number of user terminals to the PCRF, where the threshold of the number of user terminals is a maximum value of the number of user terminals that receive the transmission event sent by the AS, so that the PCRF performs the number of user terminals related to the transmission event. monitor.
  • the AS when it transmits service data through the carrier network, it needs to perform policy negotiation with the PCRF to determine a target transmission policy for transmitting the service data. Therefore, the AS sends a policy negotiation request to the PCRF.
  • the policy negotiation request carries a threshold number of the user terminal, where the policy negotiation request may further include information such as a service data size and a desired time window to be transmitted, so as to facilitate The PCRF negotiates a transmission strategy that is more capable of meeting AS requirements.
  • the data sent by the AS to the PCRF may be forwarded by using a service capability open function SCEF, where the AS and the SCEF can communicate by calling an API; and the SCEF and the PCRF communicate through the Rx interface, where Data refers to any data that interacts between the AS and the PCRF.
  • SCEF service capability open function
  • the user equipment UE involved in the present application may include various handheld devices, wireless devices, wearable devices, computing devices, or other processing devices connected to the wireless modem, and various forms of user equipment.
  • MS Mobile station
  • terminal equipment terminal equipment
  • soft terminal soft terminal
  • the above mentioned devices are collectively referred to as a user terminal or a UE.
  • the PCRF receives the threshold of the number of user terminals sent by the AS, and saves the threshold of the number of the user terminals, after the AS transmission event reported by the PCEF is received, and determines whether to The secondary transmission event is transmitted and controlled.
  • the PCRF sends a preset transmission policy acquisition request to the SPR/UDR.
  • the SPR/UDR receives a preset transmission policy acquisition request.
  • the SPR/UDR sends a preset transmission policy to the PCRF.
  • the SPR/UDR receives a preset transmission policy.
  • the PCRF acquires a preset transmission policy from the SPR/UDR, where the preset transmission policy includes one or more time windows that can be used to transmit service data, and traffic corresponding to each time window. Rates, etc.
  • the PCRF determines, according to the preset transmission policy and a current network state, a target transmission policy for transmitting the service data, where the target transmission policy includes a policy identifier for uniquely identifying the target transmission policy.
  • the PCRF determines, according to the preset transmission policy and the current network status, a target transmission policy for transmitting the service data, where the current network status includes a congestion level, a load status, and the like.
  • the target transmission policy includes a policy identifier for uniquely identifying the target transmission policy.
  • the number of preset transmission policies is different, and the corresponding manner of determining the target transmission strategy is also different, and is divided into the following two cases.
  • the first case is: when the number of the preset transmission policies is one, the SPR/UDR sends the preset transmission policy to the PCRF, and after the PCRF receives the SPR/UDR to send the preset transmission policy, determining the Determining a policy identifier of the transmission policy, sending the preset transmission device carrying the policy identifier to the AS, determining a target transmission policy for transmitting the service data, and the AS saves the target transmission policy, so that the AS follows the target transmission policy
  • the preset time window in the middle sends a transmission event to the PCEF.
  • step S605 the PCRF feeds back the determined policy identifier and the number of user terminals to the SPR/UDR, so that the SPR/UDR adds the policy identifier to the preset transmission policy, and adds the policy identifier.
  • the preset transmission policy is determined as a target transmission policy, and the target transmission policy is associated with the user terminal number threshold.
  • the second case is: when the number of the preset transmission policies is two or more, the PCRF determines a candidate transmission policy according to the preset transmission policy and the current network state.
  • the PCRF further The candidate transmission policy may be selected according to information such as a desired time window in the policy negotiation request sent by the AS.
  • the candidate transmission policy is determined as a target transmission policy, and the target is determined.
  • a policy identifier of the transmission policy the policy identifier uniquely identifies the target transmission policy, and the PCRF sends the target transmission policy that carries the policy identifier to the AS; when the number of candidate transmission policies determined by the PCRF is two or more, The PCRF determines a policy identifier of the candidate transmission policy, and sends two or more candidate transmission policies carrying the policy identifier to the AS, so that the AS selects one policy from the AS as the target transmission policy, and the AS saves the target transmission. And sending a response message carrying the target transmission policy to the PCRF, and correspondingly, the PCRF receives the response message of the AS Carry goals transmission strategy. And executing step S605, the PCRF sends the target transmission policy and the number of user terminals to the SPR/UDR, so that the SPR/UDR associates the target transmission policy with a threshold number of user terminals.
  • the SPR/UDR determines a target transmission policy and a threshold for saving a number of user terminals.
  • the SPR/UDR receives the policy identifier and the number of user terminals sent by the PCRF, and determines the preset transmission policy of adding the policy identifier.
  • the target transmission policy is saved and associated with the target terminal number threshold.
  • the SPR/UDR receives the target transmission policy and the number of user terminals sent by the PCRF, so that the SPR/UDR associates the target transmission policy with a threshold number of user terminals. .
  • the AS sends service information about the service data to the PCRF.
  • the AS sends, to the PCRF, service information related to the transmission of the service data, where the service involved in transmitting the service data is
  • the information may include a device identifier (eg, an AS identifier) for transmitting service data, a plurality of UE identifiers for receiving service data, and a number of services. According to the preset time window and policy identification in the target strategy.
  • the device identifier and the UE identifier may include an IP address, a port number, and the like of the UE, and the device identifier and the UE identifier in the service information may be in the form of IP quintuple information, IP quaternary group information, and the like.
  • the AS sends the preset time window and the policy identifier in the target transmission policy to the PCRF, so that the PCRF authenticates and authorizes the service information sent by the AS.
  • the PCRF receives service information about the service data sent by the AS.
  • the PCRF authenticates the service information related to the transmission of the service data, specifically according to the received service information.
  • the policy identifier identifies an IP-Connectivity Access Network (IP-CAN) session. If the session is successful, the process proceeds to step S608. If the session does not exist, the authentication fails. The AS sends a notification message that the authentication fails.
  • IP-CAN IP-Connectivity Access Network
  • step S607 may be performed at any time before the preset time window in which the AS included in the target transmission policy transmits the service data. This embodiment of the present invention does not limit this.
  • the PCRF sends service information and a target transmission policy about the service data to the PCEF.
  • the PCRF sends service information and a target transmission policy about the service data to the PCEF.
  • the PCRF may send the service information about the service data and the target code identifier corresponding to the target transmission policy to the transmission device, and the transmission may determine a corresponding target transmission policy according to the target code identifier.
  • the sending, by the PCRF, the target transmission policy to the PCEF may be sending a request to install/modify/delete a PCC rule to a PCEF, or sending an install/modify/delete ADC rule to a PCEF supporting an ADC rule.
  • the request wherein the target transmission policy or the target code identifier may be carried in the sent request.
  • the purpose is to add the determined target transmission policy to the PCC rules or ADC rules so that the PCEF performs according to the rules.
  • the PCRF may send service information about the service data to the PCEF at different times and send a target transmission policy to the PCEF.
  • the PCEF receives service information and a target transmission policy regarding the service data.
  • the PCEF after receiving the service information about the service data and the target transmission policy, the PCEF adds the received target transmission policy to a PCC rule or an ADC rule to follow the received transmission event according to the rule.
  • the PCRF is reported.
  • the AS sends a transmission event to the PCEF.
  • the AS sends a transmission event to the PCEF.
  • the transmission event is a transmission of service data (for example, an upgrade package, etc.) to the UE.
  • the transmission event may include a target UE identifier of the transmission event, so that the service data is transmitted according to the target UE identifier, where the target UE identifier may include an IP address, a port number, and the like of the UE.
  • the PCEF receives a transmission event sent by the AS.
  • the PCEF determines whether a time of occurrence of the transmission event is within a preset time window of the target transmission policy.
  • the PCEF After receiving the transmission event sent by the AS, the PCEF acquires an occurrence time of the transmission event, And determining whether the time of occurrence of the transmission event is within a preset time window of the target transmission policy, if it is within a preset time window of the target transmission policy, executing step S611; if not in the target transmission policy Within the preset time window, it ends, or sends a notification message to the AS that does not send the transmission event within a preset time window.
  • the PCEF determines whether the transmission event is reported to the PCRF.
  • the PCEF determines whether the transmission event is reported to the PCRF, and if the transmission event is reported, the process ends, or And sending, to the AS, a notification message that has reported the transmission event; if the transmission event is not reported, step S612 is performed.
  • the transmission event carries the target UE identifier, and the PCEF determines whether the transmission event about the target UE identifier is reported to the PCRF.
  • the PCEF reports a notification message that the transmission event is detected to the PCRF, where the notification message carries a policy identifier.
  • the PCEF reports a notification message that the transmission event is detected to the PCRF, where the notification message carries a policy identifier.
  • the policy identifier is a policy identifier for uniquely identifying a target transmission policy for transmitting the service data.
  • the transmission event represents a transmission service data
  • the target transmission policy is a policy for transmitting service data determined by the AS and the PCRF before the AS sends the transmission event
  • the target transmission policy may include a policy identifier that uniquely identifies the target transmission policy.
  • the transmission event includes a policy identifier
  • the PCEF may determine a policy identifier carried in the reported notification message according to the policy identifier in the transmission event.
  • the PCRF after the AS and the PCRF determine the target transmission policy for transmitting the service data, the PCRF sends the multiple UE identifiers of the transmission service data sent by the AS to the PCEF, and the PCEF may save the transmission policy and the multiple UE identifiers. And determining, according to the target UE identifier in the transmission event, the policy identifier in the target transmission policy that is associated with the target UE identifier, and further determining the policy identifier carried in the reported notification message.
  • the PCEF determines the transmission event for the preset time window in the target transmission policy, and also determines whether the transmission event is reported to the PCRF, because the transmission event carries the transmission service.
  • a target UE identifier of the data and the PCEF receives the service information about the service data, so the PCEF may further determine whether the target UE identifier in the transmission event exists in the service information related to the service data, if Then, it may report to the PCRF, if not, end, or notify the AS that the target UE identifies a notification message that does not belong to the previously transmitted service information. It can enhance the accuracy of reported transmission events and avoid malicious attacks, thereby saving network resources.
  • the PCRF receives a notification message that is detected by the PCEF and detects a transmission event, where the notification message carries a policy identifier.
  • the PCRF feeds back an acknowledgement message to the PCEF.
  • the PCRF after receiving the notification message of the transmission event reported by the PCEF, the PCRF feeds back an acknowledgement message to the PCEF, where the acknowledgement message is used to indicate that the PCRF receives the notification message that the transmission event is detected. .
  • the PCEF indicates, to the transmission event record, that the identifier of the transmission event has been reported.
  • the PCEF indicates, to the transmission event record, that the identifier of the transmission event has been reported. For example, after the transmission event is reported, the PCEF associates the target UE identifier carried in the transmission event with the reported identifier, so as to determine whether the transmission event is reported to the PCRF through the recorded information when the subsequent transmission event is received.
  • the PCRF sends a notification message that detects a transmission event to the SPR/UDR, where the notification message carries a policy identifier.
  • the PCRF sends a notification message that detects a transmission event to the SPR/UDR, where the notification message carries a policy identifier. It can be seen from step S612 and step S615 that the PCRF is used to forward the notification message of the PCEF detection transmission event to the SPR/UDR.
  • the SPR/UDR receives a notification message that is detected by the PCRF and detects a transmission event, where the notification message carries a policy identifier.
  • the PCRF may perform step S613 and step S615 in parallel, or may perform step S613 and step S615, respectively, and step S613 and step S615. There is no order.
  • the SPR/UDR increases the number of statistics corresponding to the policy identifier by one.
  • the SPR/UDR After receiving the notification message of the transmission event reported by the PCRF, the SPR/UDR increases the number of statistics corresponding to the policy identifier by one. The number of statistics corresponding to the policy identifier is used to record the number of reported transmission events. It can be seen that the SPR/UDR counts the number of transmission events that are not repeatedly sent by the AS. Since one transmission event is for one UE, the current statistics of the SPR/UDR corresponding to the policy identifier are transmissions. The current number of user terminals for business data.
  • the SPR/UDR determines whether the number of statistics is greater than a threshold of a number of user terminals associated with the policy identifier.
  • the SPR/UDR determines whether the number of statistics is greater than a threshold number of user terminals associated with the policy identifier. If the number of statistics is greater than the number of user terminals associated with the policy identifier, step S618 and/or S619 are performed; if the number of statistics is not greater than a threshold of the number of user terminals associated with the policy identifier, then Representing that the PCEF can perform the transmission event.
  • the SPR/UDR may indicate, by using a PCRF, that the PCEF performs packet loss processing on a transmission event carrying the policy identifier and/or initiates the AS. A prompt message indicating that the threshold number of the user terminals has been reached is sent.
  • the PCEF may perform the transmission event according to the start; or in any step of step S612, step S613 or step S614. Then, the transmission event is started; or, as a feasible solution, the SPR/UDR may send a notification message to the PCEF that the statistics number is not greater than the threshold number of the user terminal through the PCRF, so the PCEF may receive the The transmission event is started after the notification message sent by the PCRF is not greater than the notification threshold of the number of user terminals; or, the SPR/UDR may not send the statistics to the PCEF that the number of statistics is not greater than the threshold of the number of user terminals. a notification message, the PCEF may start to perform the transmission event when the notification message indicating the packet loss processing sent by the SPR/UDR through the PCRF is not received within a preset time range after reporting the notification message of the transmission event is detected. .
  • the SPR/UDR instructs the PCEF to perform packet loss processing on the transmission event.
  • the SPR/UDR indicates that the PCEF performs packet loss processing on the transmission event carrying the policy identifier by using the PCRF.
  • the indication may be indicated by sending a prompt message to the PCEF indicating that the threshold number of the user terminals has been reached.
  • the SPR/UDR sends a prompt message indicating that the threshold number of the user terminals has been reached to the AS.
  • the SPR/UDR sends, by using the PCRF, a prompt indicating that the threshold number of the user terminal has been reached to the AS that initiates the transmission event.
  • the PCEF additionally charges the traffic fee generated by the transmission event.
  • Step S618 and step S619 are processes in which the SPR/UDR performs transmission control on the transmission event when the number of statistics is greater than a threshold number of user terminals associated with the policy identifier.
  • the transmission control of the transmission event may perform any one or two steps of step S618 and step S619. If the SPR/UDR performs two steps, step S618 and step S619 are not sequentially divided.
  • S606 may be performed according to the policy determination module in FIG. 3; S603, S618, and S619 may be performed according to the first interaction module in FIG. 3; S616 and S617 may be performed according to the monitoring module in FIG.
  • the actions of the PCEF described above can be performed by the PCEF in accordance with the software modules in the memory mentioned above.
  • S612 may be performed according to the second interaction module in FIG. 3; S610, S611, and S614 may be performed according to the event determination module in FIG.
  • the embodiment shown in FIG. 5 is that the PCRF is used as a monitoring device to monitor the number of user terminals related to the transmission event; the embodiment shown in FIG. 6 is the SPR/UDR as the monitoring device for the user terminal related to the transmission event. The quantity is monitored.
  • the PCEF reports to the PCRF that the notification message of the transmission event is detected, it may report to one or more reachable PCRFs.
  • a PCRF When a PCRF receives the notification message that the transmission event is detected, Monitoring, by the PCRF, the number of user terminals related to the transmission event, or the SPR/UDR may also monitor the number of user terminals related to the transmission event; when multiple PCRFs receive the notification that the transmission event is detected At the time of the message, the number of user terminals associated with the transmission event is monitored by the SPR/UDR.
  • the transmitting device reports the unreported notification message that the transmission event is detected to the monitoring device, where the notification message carries the policy identifier, and the monitoring device increases the number of statistics corresponding to the policy identifier by one, when the number of statistics is greater than
  • the monitoring device performs transmission control on the transmission event.
  • the number of statistics recorded by the monitoring device is the number of times the transmission device reports the notification message that the transmission event is detected.
  • One transmission event corresponds to one user terminal. Therefore, the number of statistics recorded by the monitoring device is the number of user terminals related to the transmission event.
  • the transmission device By reporting the transmission event on the transmission device, the number of user terminals related to the transmission event is monitored, and the transmission event exceeding the threshold of the number of user terminals is transmitted and controlled to save transmission costs.
  • the transmission device avoids repeatedly reporting the same transmission event by judging whether the transmission event is reported, thereby improving the accuracy of monitoring the number of user terminals by the monitoring device.
  • FIG. 7 is a schematic structural diagram of a monitoring device according to an embodiment of the present invention.
  • the monitoring device 7 of the embodiment of the present invention may include: a receiving unit 701, an adding unit 702, and a control unit 703.
  • the monitoring device 7 further includes an obtaining unit 704 and a determining unit 705.
  • the receiving unit 701 is configured to receive a notification message that is detected by the transmission device and that detects a transmission event, where the notification message carries a policy identifier.
  • the adding unit 702 is configured to increase the number of statistics corresponding to the policy identifier by one.
  • the control unit 703 is configured to perform transmission control on the transmission event when the number of statistics is greater than a threshold number of user terminals associated with the policy identifier.
  • the monitoring device is a policy and charging rule entity PCRF.
  • the transmission event is used to indicate that the service data is transmitted.
  • the receiving unit 701 is further configured to receive a threshold number of user terminals sent by the application device before receiving the notification message of the transmission event reported by the transmission device.
  • the monitoring device further includes an obtaining unit 704 and a determining unit 705:
  • the obtaining unit 704 is configured to obtain a preset transmission policy from the user subscription database SPR or the user data storage UDR.
  • the determining unit 705 is configured to determine, according to the preset transmission policy and the current network state, a target transmission policy for transmitting the service data, where the target transmission policy includes a policy identifier for uniquely identifying the target transmission policy. .
  • the determining unit 705 is configured to send, by using the preset transmission policy and the current network state, at least two candidate transmission policies to the application device, and receive a response message of the application device. Determining the target transmission policy by a target transmission policy carried in, the target transmission policy being one of the at least two candidate transmission policies.
  • the monitoring device is an SPR or a UDR.
  • the receiving unit 701 is further configured to receive, after receiving the notification message of the transmission event reported by the transmission device, a threshold of the number of user terminals sent by the PCRF, where the user The terminal number threshold is sent by the application device to the PCRF.
  • the transmission event includes the policy identifier.
  • the control unit 703 is specifically configured to: instruct the transmitting device to perform packet loss processing on a transmission event carrying the policy identifier, and/or send an indication to the application device that initiates the transmission event that the threshold number of the user terminal has been reached. Message.
  • the monitoring device 7 is presented in the form of a functional unit.
  • a "unit” herein may refer to an application-specific integrated circuit (ASIC), circuitry, a processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other functions that provide the functionality described above. Device.
  • ASIC application-specific integrated circuit
  • the receiving unit 701, the adding unit 702, the control unit 703, the obtaining unit 704, and the determining unit 705 may be implemented by the processor and the memory of FIG. 3. Specifically, the obtaining unit 704 and the determining unit 705 may perform policy determination by the processor.
  • the module is implemented.
  • the receiving unit 701 can be implemented by executing a first interaction module by a processor.
  • the adding unit 702 and the control unit 703 can be implemented by executing a monitoring module by a processor.
  • the monitoring device increases the number of statistics corresponding to the policy identifier by 1 when the number of statistics is greater than the threshold of the number of user terminals associated with the policy identifier. , transmission control of transmission events.
  • the number of statistics recorded by the monitoring device is the number of times the transmission device reports the notification message of the transmission event.
  • One transmission event corresponds to one user terminal. Therefore, the number of statistics recorded by the monitoring device is the number of user terminals related to the transmission event.
  • FIG. 8 is a schematic structural diagram of a transmission device according to an embodiment of the present invention.
  • the transmission device 8 of the embodiment of the present invention may include: a receiving unit 801, a determining unit 802, and a reporting unit 803.
  • the transmitting device 8 further includes a determining unit 804 and a recording unit 805.
  • the receiving unit 801 is configured to receive a transmission event sent by the application device.
  • the determining unit 802 is configured to determine whether the transmission event is reported to the monitoring device.
  • the reporting unit 803 is configured to: when the determination result is no, the transmitting device reports, to the monitoring device, a notification message that the transmission event is detected, where the notification message carries a policy identifier.
  • the foregoing transmission event is used to indicate that the service data is transmitted.
  • the receiving unit 801 is further configured to: before receiving the transmission event sent by the application device, receive the target transmission policy that is sent by the policy and charging rule entity PCRF to transmit the service data, where the target transmission policy includes: The policy ID of the transport policy.
  • the target transmission policy further includes a preset time window for transmitting the service data.
  • Transmission event package The policy identifier is included.
  • the transmission device further includes a determining unit 804:
  • the determining unit 804 is configured to determine, after the receiving unit 801 receives the transmission event sent by the application device, the target transmission policy corresponding to the policy identifier according to the policy identifier in the transmission event.
  • the determining unit 802 is further configured to determine whether a time of occurrence of the transmission event is within a preset time window of the target transmission policy. When the determining unit 802 determines that the occurrence time of the transmission event is within a preset time window of the target transmission policy, the determining unit 802 continues to determine whether the transmission event is reported to the monitoring device.
  • the transmitting device further includes a recording unit 805, configured to report, by the reporting unit 803, a notification message that the transmission event is detected to the monitoring device, and indicate that the transmission event report has been reported. The identity of the event.
  • the transmission device includes a policy and charging execution entity PCEF, a bearer binding, and an event reporting entity BBERF or a traffic detection entity TDF.
  • the transmission device 8 is presented in the form of a functional unit.
  • a "unit” herein may refer to an application-specific integrated circuit (ASIC), circuitry, a processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other functions that provide the functionality described above. Device.
  • ASIC application-specific integrated circuit
  • the transmission device 8 can take the form shown in FIG.
  • the receiving unit 801, the determining unit 802, the reporting unit 803, the determining unit 804, and the recording unit 805 can be implemented by the processor and the memory of FIG. 3.
  • the receiving unit 801, and the reporting unit 803 can be executed by the processor.
  • the two interaction modules are implemented, and the determining unit 802, the determining unit 804, and the recording unit 805 can be implemented by executing an event determining module by the processor.
  • the transmission device when the transmission device receives the transmission event, the transmission event that is not reported to the monitoring device is reported to the monitoring device, so that the monitoring device monitors the number of user terminals related to the transmission event. In addition, by determining whether to report the transmission event, it is avoided to repeatedly report the same transmission event, thereby improving the accuracy of monitoring the number of user terminals by the monitoring device.
  • the embodiment of the invention further provides a computer storage medium for storing computer software instructions for the monitoring device shown in FIG. 7 above, which comprises a program designed to execute the above aspects for the monitoring device.
  • a computer storage medium for storing computer software instructions for the monitoring device shown in FIG. 7 above, which comprises a program designed to execute the above aspects for the monitoring device.
  • the embodiment of the present invention further provides another computer storage medium for storing computer software instructions for the transmission device shown in FIG. 8 above, which comprises a program designed to execute the above aspects for the transmission device.
  • the transmission device can report the unreported notification message that the transmission event is detected to the monitoring device, so that the monitoring device monitors the number of user terminals related to the transmission event.
  • embodiments of the present invention can be provided as a method, apparatus (device), or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • the computer program is stored/distributed in a suitable medium, provided with other hardware or as part of the hardware, or in other distributed forms, such as over the Internet or other wired or wireless telecommunication systems.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Telephonic Communication Services (AREA)

Abstract

Conformément à un mode de réalisation, la présente invention concerne un procédé et un dispositif associé pour surveiller la quantité de terminaux utilisateur, le procédé comprenant les opérations suivantes : un dispositif de surveillance reçoit un message de notification rapporté par un dispositif de transmission concernant la détection d'un événement de transmission, le message de notification transportant un identificateur de politique ; le dispositif de surveillance accroît un nombre statistique de fois correspondant à l'identificateur de politique par un ; et le dispositif de surveillance réalise une commande de transmission sur l'événement de transmission lorsque le nombre statistique de fois est supérieur à une valeur de seuil du nombre de terminaux utilisateur associés à l'identificateur de politique. Selon la présente invention, il est possible de surveiller le nombre de terminaux utilisateur associés à l'événement de transmission et de réaliser la commande de transmission sur l'événement de transmission dépassant la valeur de seuil du nombre de terminaux utilisateur, de façon à économiser le coût de transmission, et dans un cas dans lequel l'événement de transmission est rapporté par le dispositif de transmission.
PCT/CN2016/110798 2015-12-30 2016-12-19 Procédé de surveillance de quantité de terminaux utilisateur et dispositif associé WO2017114220A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201511027075.XA CN106937323B (zh) 2015-12-30 2015-12-30 一种用户终端数量的监控方法及相关设备
CN201511027075.X 2015-12-30

Publications (1)

Publication Number Publication Date
WO2017114220A1 true WO2017114220A1 (fr) 2017-07-06

Family

ID=59224645

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/110798 WO2017114220A1 (fr) 2015-12-30 2016-12-19 Procédé de surveillance de quantité de terminaux utilisateur et dispositif associé

Country Status (2)

Country Link
CN (1) CN106937323B (fr)
WO (1) WO2017114220A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111585914A (zh) * 2019-02-15 2020-08-25 阿里巴巴集团控股有限公司 一种服务限流方法、装置、及电子设备
CN115118575A (zh) * 2022-06-23 2022-09-27 奇安信科技集团股份有限公司 一种监控方法、装置、电子设备及存储介质

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109660996B (zh) * 2017-10-10 2022-05-13 中国移动通信有限公司研究院 用户数监控方法、网元实体及存储介质
CN110830422B (zh) * 2018-08-10 2022-04-01 中国移动通信有限公司研究院 一种终端行为数据处理方法及设备
CN108880917B (zh) 2018-08-23 2021-01-05 华为技术有限公司 控制面设备的切换方法、装置及转控分离系统

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101119211A (zh) * 2007-09-18 2008-02-06 中兴通讯股份有限公司 一种公平用户策略的业务实现方法
CN101945370A (zh) * 2010-09-25 2011-01-12 中兴通讯股份有限公司 一种实施动态策略控制的方法及系统
CN102209310A (zh) * 2010-03-31 2011-10-05 华为技术有限公司 对用户业务的数据流进行控制的方法和装置
CN102907066A (zh) * 2010-05-28 2013-01-30 瑞典爱立信有限公司 高效的数据传递方法和装置
CN103379043A (zh) * 2012-04-28 2013-10-30 中兴通讯股份有限公司 一种网络拥塞的处理方法、系统和控制网元
CN103477587A (zh) * 2011-04-27 2013-12-25 阿尔卡特朗讯 用于控制访客用户的qos和/或策略和计费控制的方法和设备

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102075900B (zh) * 2009-11-23 2014-03-12 中兴通讯股份有限公司 一种实现用量监测控制的方法及系统
CN102075898B (zh) * 2010-12-21 2014-02-26 华为技术有限公司 业务控制方法、装置及系统
CN102142990B (zh) * 2010-12-31 2016-11-02 华为技术有限公司 业务用量监控方法及设备

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101119211A (zh) * 2007-09-18 2008-02-06 中兴通讯股份有限公司 一种公平用户策略的业务实现方法
CN102209310A (zh) * 2010-03-31 2011-10-05 华为技术有限公司 对用户业务的数据流进行控制的方法和装置
CN102907066A (zh) * 2010-05-28 2013-01-30 瑞典爱立信有限公司 高效的数据传递方法和装置
CN101945370A (zh) * 2010-09-25 2011-01-12 中兴通讯股份有限公司 一种实施动态策略控制的方法及系统
CN103477587A (zh) * 2011-04-27 2013-12-25 阿尔卡特朗讯 用于控制访客用户的qos和/或策略和计费控制的方法和设备
CN103379043A (zh) * 2012-04-28 2013-10-30 中兴通讯股份有限公司 一种网络拥塞的处理方法、系统和控制网元

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"Policy control based on groups of subscriber", ZTE, 3 September 2010 (2010-09-03), pages 2 - 103419 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111585914A (zh) * 2019-02-15 2020-08-25 阿里巴巴集团控股有限公司 一种服务限流方法、装置、及电子设备
CN111585914B (zh) * 2019-02-15 2024-03-22 阿里巴巴集团控股有限公司 一种服务限流方法、装置、及电子设备
CN115118575A (zh) * 2022-06-23 2022-09-27 奇安信科技集团股份有限公司 一种监控方法、装置、电子设备及存储介质
CN115118575B (zh) * 2022-06-23 2024-05-03 奇安信科技集团股份有限公司 一种监控方法、装置、电子设备及存储介质

Also Published As

Publication number Publication date
CN106937323A (zh) 2017-07-07
CN106937323B (zh) 2021-03-30

Similar Documents

Publication Publication Date Title
EP3627865B1 (fr) Procédé de commande de politique, éléments de réseau et système
US11083033B2 (en) Small data usage enablement in 3GPP networks
WO2017114220A1 (fr) Procédé de surveillance de quantité de terminaux utilisateur et dispositif associé
US10681222B2 (en) Charging management method, user plane function entity, and control plane function entity
WO2019196813A1 (fr) Procédé et dispositif d'abonnement à un service
EP3198892B1 (fr) Commande de communication à l'aide d'un chaînage de fonctions de service
WO2017193427A1 (fr) Procédé et terminal de reconnaissance de service de commutation de paquets
US9641346B2 (en) Method and apparatus for performing charging control to application-layer data
US10298744B2 (en) Method and arrangement for policy regulation of electronic communication devices
WO2016134772A1 (fr) Facturation et commande de services périphériques
EP3297323B1 (fr) Procédé, appareil, et système de gestion du trafic
US9374317B2 (en) Providing provisioning and data flow transmission services via a virtual transmission system
EP2548388A2 (fr) Procédés, systèmes et supports lisibles par ordinateur permettant de communiquer des informations de politique entre une fonction de facture et de contrôle de politiques et un n ud de service
EP3890398A1 (fr) Procédé, appareil et système de rapport d'utilisation de données
US9820183B2 (en) User plane congestion control
JP2016526357A (ja) Ｐｃｒｆを決定するための方法および装置
US10149186B2 (en) Node and method for monitoring an ability of a wireless device to receive downlink data
WO2017076126A1 (fr) Procédé, dispositif et système de commutation de session
WO2009056063A1 (fr) Procédé, dispositif et système de demande d'informations dans une architecture pcc
WO2014190517A1 (fr) Procédé et dispositif de commande de transmission de données basés sur un réseau de communication sans fil
US10193815B2 (en) Mobile network handling of unattended traffic
EP3641248B1 (fr) Dispositif d'optimisation de trafic, système de communication, procédé d'optimisation de trafic, et programme
CN113169884A (zh) 移除应用标识符
WO2014179919A1 (fr) Procédé de commande de service, système et dispositif correspondant
WO2023138796A1 (fr) Technique permettant la sélection de politiques de qos de domaine central dans un domaine de fournisseur de contenu

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16881009

Country of ref document: EP

Kind code of ref document: A1