WO2008131674A1 - Method, system and device for examining a carrying event - Google Patents

Method, system and device for examining a carrying event Download PDF

Info

Publication number
WO2008131674A1
WO2008131674A1 PCT/CN2008/070762 CN2008070762W WO2008131674A1 WO 2008131674 A1 WO2008131674 A1 WO 2008131674A1 CN 2008070762 W CN2008070762 W CN 2008070762W WO 2008131674 A1 WO2008131674 A1 WO 2008131674A1
Authority
WO
WIPO (PCT)
Prior art keywords
event
type
range
detection
bearer
Prior art date
Application number
PCT/CN2008/070762
Other languages
French (fr)
Chinese (zh)
Inventor
Shiyong Tan
Yan Li
Weihua Wei
Shibi Huang
Peng Zhao
Yuxin Mao
Original Assignee
Huawei Technologies Co., Ltd.
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 Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2008131674A1 publication Critical patent/WO2008131674A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/14Charging, metering or billing arrangements for data wireline or wireless communications
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0894Policy-based network configuration management

Definitions

  • This invention relates to the field of communications technology and, more particularly, to a method, system and apparatus for detecting bearer events.
  • IP networks can provide a variety of services, such as multimedia calls, file downloads, web browsing, etc., where different services have different requirements for QoS (including bandwidth, delay, packet loss rate, etc.), and billing The requirements are also different. For example: Online billing or offline billing can be used, and it can be charged according to the flow rate or according to the time.
  • QoS Quality of Service
  • the Third Generation Partnership Project (3GPP) defines a Policy and Charging Control (PCC) architecture, through which different schemes can be satisfied. QoS control and billing requirements.
  • PCRF Policy Control and Charging Rules Function
  • the PCRF entity determines the corresponding policy according to the operator policy, the user subscription data, and the service information currently being performed by the user, and provides the policy to the Policy and Charging Enforcement Function (PCEF), which is executed by the PCEF.
  • PCEF Policy and Charging Enforcement Function
  • User subscription data can be obtained from the User Profile Data Repository (SPR) function entity.
  • SPR User Profile Data Repository
  • Policies include detection rules for service data flows (collections of IP flows that complete a service such as voice communication), whether to gate, QoS, flow-based charging rules, and so on.
  • PCEF is mainly used to complete the detection of service data flows, the execution of policies, flow-based charging, etc.
  • the entity performs the policy that is sent or specified by the PCRF, specifically, performs detection and measurement of the service data flow, guarantees QoS of the service data flow, user plane traffic processing, and session management of the trigger control plane.
  • the functional entity is used to provide user subscription data to the PCRF.
  • the application layer function entity (Appl ica t ion Funct ion, AF), the function entity is used to dynamically provide session information of the application layer service to the PCRF, and the PCRF formulates a corresponding policy, and the AF can obtain the IP connectivity access network from the PCRF ( IP-Connect iv i ty Acces s Network , IP-CAN ) related information and IP-CAN bearer related events.
  • PCRF IP-Connect iv i ty Acces s Network , IP-CAN
  • the interface between AF and PCRF is the Rx reference point.
  • the reference point is used by the AF to deliver application layer related information, including an IP filter (such as a source IP address, a destination IP address, a protocol type, a source port number, a destination port number, etc.) for identifying a service data flow, an application, or a media. Required bandwidth information.
  • the PCRF can also provide IP-CAN related information, report bearer events, etc. to the AF through the reference point. This reference point uses the Diameter ten defined by the Internet Eng ineering Task Force (IETF).
  • IP-CAN When the user roams within the access network (when the location changes), the IP service continuity can be preserved (ie, the service is not interrupted).
  • the access network with such a nature is called IP-CAN, such as (Genera l Packet Radio Service, GPRS). Network, interworking-WLAN (I-WLAN) network, etc.
  • IP-CAN session refers to the association between the UE and the PDN, and is identified by the IP address of the User Equipment (UE) and the identity of the UE (such as IMSI).
  • UE User Equipment
  • IMSI Interworking-WLAN
  • the IP-CAN exists as long as the UE is assigned an IP address and can be identified by the IP network.
  • An IP-CAN session can contain one or more IP-CAN bearers.
  • the strategy formulated by the PCRF and the specific IP-CAN bearer binding can be implemented by PCRF or PCEF, respectively.
  • IP-CAN bearer 1 in Figure 2 has higher QoS than IP-CAN bearer 2, thus for QoS.
  • High-demand services such as VOIP, multimedia calls, etc.
  • IP-CAN bearer 1 for lower QoS requirements (such as file downloading, web browsing) Etc.)
  • IP-CAN bearer 2 can be used.
  • the PCEF identifies the IP flow according to the flow description information (such as source IP address, destination IP address, protocol type, source port number, destination port number, etc.) in the PCC rule.
  • the IP flow is composed of the same source IP address, destination IP address, transport layer protocol, source port number, and destination port number (collectively IP quintuple, if the corresponding transport layer protocol does not have a port number concept, source port number and destination A one-way flow consisting of IP packets whose port number can be omitted.
  • each IP Flow is described by an F low-Descr ipt ion AVP.
  • multiple IP-CAN bearers can be established in one IP-CAN session, and one IP-CAN bearer can be used to transmit one or more IP flows (requires that these IP flows have the same QoS requirements)
  • a PCC rule can only be used for one IP-CAN bearer, and one IP-CAN bearer can have one or more PCC rules.
  • the AF request event escalation can only be directed to the entire D i ame t e r session between AF and PCRF.
  • AF needs to pay attention not to all IP flows in the entire session, and may only be some IP flows, but the prior art PCEF may detect IP-CAN bearers or IP flows that are not concerned, and will appear. The detection status is reported, and the PCRF also needs to report to the AF.
  • AF does not need this information, which leads to redundant message interaction between PCEF and PCRF, between PCRF and AF, adding unnecessary load between the three devices.
  • AF only pays attention to the interruption of IP flow 1 as shown in Figure 1 (this will cause the service to abort), and does not pay attention to other IP flows as shown in Figure 2.
  • the PCRF must instruct the PCEF to report all IP-CAN bearer interruptions in the session. Summary of the invention
  • the main purpose of the embodiments of the present invention is to provide a method for detecting bearer events to reduce redundant message interaction.
  • Another object of embodiments of the present invention is to provide a system for detecting bearer events to reduce redundant message interaction.
  • a further object of embodiments of the present invention is to propose an AF to reduce redundant message interaction.
  • Another object of embodiments of the present invention is to propose a PCRF to reduce redundant message interaction.
  • the technical solution of the embodiment of the present invention is implemented as follows: A method for detecting a bearer event, the method includes:
  • the application layer function entity AF sends a bearer event detection request to the policy control and charging rule function entity PCRF, where the bearer event detection request includes an event detection type range and event detection corresponding to each event type in the event detection type range. Scope
  • the PCRF detects this type of event within the event detection range of each event type, and returns the type of event of the detected event to the AF and the range of influence of the detected event.
  • a system for detecting bearer events comprising AF and PCRF, wherein:
  • An AF configured to send a bearer event detection request to the PCRF, where the bearer event detection request includes an event detection type range and an event detection range corresponding to each event type in the event detection type range;
  • the PCRF is configured to detect the type of event within the event detection range of each event type, and return the type of the event of the detected event to the AF and the range of influence of the detected event.
  • An AF includes a bearer event detection request sending unit and an event processing unit, where: a bearer event detecting request sending unit is configured to send a bearer event detecting request to the PCRF, where the bearer event detecting request includes an event detecting type range and Corresponding to an event detection range of each event type in the event detection type range;
  • the event processing unit is configured to process the event according to an application layer policy after receiving the event type of the event detected by the PCRF and the scope of the detected event.
  • the PCRF includes an event detecting unit and a detection result returning unit, where: an event detecting unit is configured to receive a bearer event detecting request sent by the AF, and detect the type in the event detecting range of each event type.
  • An event where the bearer event detection request includes an event detection type range and an event detection range corresponding to each event type in the event detection type range;
  • the detection result returning unit is configured to return the type of the event of the detected event to the AF and the influence range of the detected event.
  • the AF request PCRF detects the reported event, it indicates the range of the detected event type and the detection range, and the detection range may be the entire D i ame ter session or the media stream or the media sub- Any combination of stream and IP flow, the detection range of different events can be different.
  • the PCRF detects the event specified by the AF in the range specified by the AF according to the request of the AF. After detecting the corresponding event, the PCRF reports the type of the event and the scope of the event to the AF, where the impact range may be the entire Diameter session or media.
  • FIG. 1 is a schematic diagram of a PCC structure in the prior art
  • FIG. 2 is a schematic diagram of correspondence between IP flows, PCC rules, IP-CAN bearers, and IP-CAN sessions in the prior art
  • FIG. 3 is a schematic flowchart of a method for detecting a bearer event according to an embodiment of the present invention
  • FIG. 4 is a schematic flowchart of a method for detecting a bearer event according to a first embodiment of the present invention
  • FIG. 5 is a schematic flowchart of a method for detecting a bearer event according to a second embodiment of the present invention
  • FIG. 6 is a diagram for detecting a bearer event according to an embodiment of the present invention. Schematic diagram of the system structure
  • Figure ⁇ is a schematic diagram of an AF structure according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram showing the structure of a PCRF according to an embodiment of the present invention.
  • the Diameter series protocol used in the embodiments of the present invention is a new generation of Authentication Authorization Answer (AAA) technology, and the purpose is to create an IP network (including NGN) that can fully satisfy the current and future. And 3G, etc.) AAA protocol for user access control requirements.
  • the Diame ter protocol is a remote authentication dial-up user service ( Remote Authent ica t ion Upgrade of the Dia L-In User Service (RADIUS) protocol, including the basic protocol, the transport protocol, and the extended protocol for different application scenarios.
  • the extension for different application scenarios in Diameter is called an application, such as the Rx and Gx reference in the PCC architecture. Points are two different Diameter applications).
  • the basic functions shared by various applications are implemented in the base protocol, and the functions specific to different application scenarios are defined in each application.
  • both the Diameter client and the Diameter server can actively send request messages to the peer.
  • the Diameter client performs a series of information exchange with the Diameter server, and such a series of information interactions from initiation to suspension is called a Diameter session.
  • the establishment of a Diameter session is generally initiated by the client.
  • the end of the Diameter session is completely determined by the client, but the server can also issue an abort session request first. If the client agrees to abort the request, it will respond to the abort session response, and then the client will issue a session end request to notify the server to end the user. Session, otherwise the session is still maintained.
  • the Diameter message consists of a message header and a message body.
  • the message header includes the protocol version number, the application identifier (identifying different Diameter applications), the command code (Command Code, indicating the message type), the message length, etc., and the message body is composed of attribute values. (At tr ibute-Va lue-Pa ir , AVP ) composition.
  • Different types of Diameter messages can contain different AVPs. Each application can define an AVP specific to the application. It is an extension mechanism of Diameter to define a new AVP to implement new functions.
  • FIG. 3 is a schematic flowchart of a method for detecting a bearer event according to an embodiment of the present invention. As shown in Figure 3, the method includes:
  • Step 301 The AF sends a bearer event detection request to the PCRF, where the bearer event detection request includes an event detection type range and an event detection range corresponding to each event type in the event detection type range.
  • the event detection range may be an entire Diameter session, or any combination of a media stream, a media substream, and an IP stream. Also, the event detection type range can include all event types. Or include at least one specific event type.
  • each media stream is described by a Media-Component-Descr i pt ion AVP. Multiple media streams in the same session are identified by ber AVP via Media-Component-N. If AF uses the Session Description Protocol (SDP) to describe the media, then a media stream corresponds to the m line (media description line) in the SDP. The Media-Component-Number corresponding to the media stream is that the m line appears in the SDP. The sequence number.
  • SDP Session Description Protocol
  • the media substream is further subdivided into the media stream.
  • RTP Real Time Transport Protocol
  • the corresponding RTP stream and the RTCP stream respectively correspond to one media substream.
  • each media substream is described by a Media-Sub-Component AVP.
  • the multiple media substreams in the same media stream are identified by the Flow-Number AVP, and the Flow-Number can be sorted according to the port number corresponding to each media substream.
  • the media substream can correspond to a bidirectional flow (containing two Flow-Descr IVPs, describing two IP flows), or a unidirectional flow (containing only one Flow-Descr iption AVP, describing an IP flow).
  • the AF request PCRF detects the reported event, it indicates the type of the event to be detected and the detection range, and the detection range of the different types of events may be different.
  • Step 302 The PCRF detects the type of event in the event detection range of each event type, and returns the type of the event of the detected event to the AF and the influence range of the detected event.
  • the PCRF detects the event specified by the AF in the range specified by the AF according to the request of the AF. After detecting the corresponding event, the PCRF reports the type of the event and the scope of the event to the AF, and the impact range may be the entire Diameter session. Or any combination of media streams, media substreams, and IP streams.
  • the event detection range of each event detection type in the event detection type range is not the same, and the range of influence of each detected event is not the same; or the event detection range of each event detection type in the event detection type range is the same, And the range of the impact of each detected event is the same; or the event detection range of each event detection type in the range of the event detection type is not the same, and the range of influence of each detected event is the same; or each of the types of event detection types
  • the event detection type has the same range of event detection, and the range of influence of each detected event is not the same.
  • the AF may request the PCRF to detect the reported event, and may request to add, delete, and modify the reported event, and may send a request message (such as AAR) to the PCRF in the AF.
  • AAR request message
  • the indication in can also be indicated in the response message (such as RAA) of the AF response PCRF.
  • the AF may further send a cancel bearer event detection request to the PCRF, where the cancel bearer event detection request includes a cancel detection event type range and corresponding to the cancel detection event, when the event type of the cancellation detection report needs to be increased.
  • the AF may further send an increase bearer event detection request to the PCRF, where the increased bearer event detection request includes an increase detection event type range and corresponding to the increased detection event type.
  • the AF may send a modify bearer event detection request to the PCRF, where the modified bearer event detection request includes the detection event type range to be modified and the type of the detection event to be modified.
  • the invention can also be used for signaling path state detection.
  • the Media-Component-Number of the signaling stream can be 0 or a special number (3x4 OxFFFFFF).
  • the flow-number AVP is specified by the AF, and the signaling flow is described by the Flow-Description AVP, so that the event detection report of the signaling flow is consistent with the event detection report of the media stream, and there is no need to establish a new Diameter session for the signaling path state detection.
  • the AF may request the PCRF to detect the reported event in the request message.
  • Figure 4 is the first in accordance with the present invention A schematic diagram of a method for detecting a bearer event of an embodiment.
  • the method includes:
  • Step 401 The AF sends a request message (for example, may be an AAR message to the PCRF), and requests the PCRF to detect the reported event, where the detected event type range and the detection range are specified, and the detection range may be the entire Diameter session or the media stream, Any combination of media sub-flow and IP flow, the detection range of different events may be the same or different.
  • the event type can use the wildcard method to request to detect and report all event types at one time, or request to detect and report one or some events.
  • Step 402 The PCRF returns a response message to the AF (for example, an AAA message;).
  • Step 403 The PCRF detects the AF-specified event within the range specified by the AF according to the AF indication and the PCEF.
  • Step 404 After the PCRF detects the corresponding event, the PCRF sends a request message (such as a RAR message) to the AF, and reports the event type and the scope of the event.
  • the impact range may be the entire Diameter session or the media stream, the media substream, and the IP stream. combination.
  • the event impact range indicated when the PCRF is reported must be within the detection range specified by the AF request. Events that occur outside the detection range specified by the AF are not reported, and the event types that the AF does not specify are not reported.
  • the PCRF can report multiple events at once, and the impact range of these events can be the same or different.
  • Step 405 The AF sends a response message to the PCRF (such as a RAA message;);
  • Step 406 The AF extracts corresponding measures according to the policy of the application layer and the reported event (such as tearing down the service, modifying the service by signaling, etc.).
  • FIG. 5 is a flow chart showing a method for detecting a bearer event according to a second embodiment of the present invention.
  • the method includes:
  • Step 501 The PCRF sends a request message (such as a RAR message;) to the AF.
  • a request message such as a RAR message
  • Step 502 The AF returns a response message (such as a RAA message) to the PCRF, and requests the PCRF to detect the reported event.
  • the message indicates the range of the detected event type and the detection range.
  • the detection range may be the entire Diameter session or the media stream, the media substream, and the IP stream. Any combination of different events
  • the measurement range can be different.
  • the event type may request to detect and report all event types in a wildcard manner, or may request to detect and report one or some events.
  • Step 503 The PCRF cooperates with the PCEF according to the AF indication to detect the AF-specified event within the range specified by the AF.
  • Step 504 After the PCRF detects the corresponding event, the PCRF sends a request message (such as a RAR message) to the AF, and reports the event type and the scope of the event.
  • the impact range may be the entire Diameter session or the media stream, the media substream, and the IP stream. combination.
  • the event impact range indicated when the PCRF is reported must be within the detection range specified by the AF request. Events that occur outside the detection range specified by AF are not reported, and AF does not report the type of event that is not specified.
  • the PCRF can report multiple events at a time, and the impact range of these events can be the same or different;
  • Step 505 The AF sends a response message to the PCRF (such as an RAA message;);
  • Step 506 The AF extracts corresponding measures according to the policy of the application layer and the reported event (such as tearing down the service, modifying the service by signaling, etc.).
  • Diameter protocol the protocol between AF and PCRF.
  • the present invention will be described in detail below by taking the Diameter protocol as an example. However, those skilled in the art will appreciate that the present invention is not limited to the Diameter protocol.
  • IP-Flows AVP is a newly defined AVP. This AVP is used to locate one or more IP flows.
  • the Direction is an enumerated type. The value can be UPLINK (0, Up), DOWNLINK. (1, down), BOTH (2, two-way). ⁇ ... ⁇ indicates comparison parameters, tincter indicates optional parameters, and * indicates that there can be multiple (subsequent use of the same rules).
  • Flow-Number does not appear to represent all media substreams in the media stream corresponding to Media-Component-Number, and Direction does not appear to indicate that upstream and downstream are included.
  • the specific-action AVP is an existing AVP. However, it is not used directly for the AF request to detect the reported event. It is not directly used by the PCRF to report events to the AF. It is only used to define various event types and is defined on the basis of the original value. A new enumeration value: ALL, which means that all event types are wildcarded, and ALL can only be used in messages sent by the AF to the PCRF.
  • IP-Flows-Specific-Action AVP is a newly defined AVP that binds events and IP flows together. IP-Flows does not appear to indicate that the event is for the entire Diameter.
  • IP-Flows-Specific-Action AVP is a newly defined AVP, enumerated type, with values of ADD (0, increase;), REMOVE (1, delete;), UPDATE (2, update;), for AF indication PCRF How to operate IP-Flows-Specific-Action.
  • ADD can be used to add a new event type or increase the detection range of the event that has been requested to be reported.
  • REMOVE is used to delete the event type that has been requested to be reported or to reduce the detection range of the event that has been requested to be reported.
  • UPDATE is used to delete all the original requests. The escalated event is replaced with the event in the new message.
  • IP-Flows-Specific- Action-Operation: : ⁇ AVP Header: x >
  • IP-Flows-Specific-Action-Operation AVP is a newly defined AVP for AF direction
  • the PCRF adds, deletes, and updates the reported detection event.
  • IP-Flows-Specific-Action-Operation AVPs are included in the request message (such as AAR) or response message (such as RAA) sent to the PCRF, and multiple detection ranges are included.
  • the same event can be included in the same IP-Flows-Specific-Action-Operation AVP. If the detection range of one or some events is the entire Diameter session, the corresponding IP-Flows-Specific-Action AVP does not include the IP-Flows AVP, otherwise the corresponding IP-Flows-Specific-Action AVP may contain one or more.
  • IP-Flows AVP to indicate the event detection range (any combination of media stream, media substream, and IP stream). AF uses different Operation-Types to flexibly add, delete, modify, and update reported events.
  • the PCRF When the PCRF reports an event to the AF, it can flexibly report the event to the AF by including one or more IP-Flows-Specific-Action AVPs in the request message (such as RAR) or the response message (such as AAA) sent to the AF. Multiple events with the same range of influences can be included in the same IP-Flows-Specific-Action-Operation AVP. If the impact scope of one or some events is the entire Diameter session, the corresponding IP-Flows-Specific-Action AVP does not include the IP-Flows AVP, otherwise the corresponding IP-Flows-Specific-Action AVP may contain one or more. IP-Flows AVP to indicate the scope of impact of the event (any combination of media stream, media substream, and IP stream).
  • This kind of scheme has a large change to the existing mechanism, and the advantage is that it is very flexible and convenient.
  • Flows AVP is an existing AVP that adds Direction AVP to the original so that it can locate an IP stream.
  • Direction is an enumerated type, which can be UPLINK (0, Up), DOWNLINK (1, Down), BOTH (2, Bidirectional).
  • Flow-Number does not appear to indicate all media substreams in the media stream corresponding to Media-Component-Number, and Direction does not appear to indicate that upstream and downstream are included.
  • the Specific-Action AVP is an existing AVP. It can still be used by the AF to report events to the PCRF and the PCRF to report events to the AF.
  • Two new enumeration values are defined: DETECT—ALL and REMOVE—ALL, where DETECT—ALL indicates the AF request.
  • the PCRF detects all events, and REMOVE_ALL indicates that the AF request PCRF cancels the detection and reports all events.
  • the two newly defined values can only be used in the message sent by the AF to the PCRF.
  • the AF request is reported to the PCRF to detect the reported event
  • only one or more Specific-Action AVPs are included in the request message (such as AAR) or response message (such as RAA) sent to the PCRF, and the event detection range is the Diameter message in the entire Diameter session.
  • the Flow AVP is not carried in the flow, otherwise one or more Flows AVPs may be carried to indicate the scope of influence (any combination of media stream, media substream and IP stream).
  • the newly issued Specific-Action AVP is superimposed on the original basis.
  • you need to delete one or some events you can include multiple Specific-Action AVPs in the message.
  • the first value is REMOVE-ALL.
  • the event that is requested to be reported, and the subsequent Specific-Action indicates the reported event that needs to be retained.
  • the PCRF When the PCRF reports an event to the AF, it only needs to include one or more Specific-Action AVPs in the request message (such as RAR) or response message (such as AAA) sent to the AF.
  • the event impact range is not carried in the message when the entire Diameter session is used.
  • Flows AVP otherwise one or more Flows AVPs can be carried to indicate the scope of influence (any combination of media stream, media substream and IP stream).
  • Flows AVP is an existing AVP that adds Direction AVP to the original so that it can locate an IP stream.
  • Direction is an enumerated type, which can be UPLINK (0, Up), DOWNLINK (1, Down), BOTH (2, Bidirectional).
  • Flow-Number does not appear to indicate all media substreams in the media stream corresponding to Media-Component-Number, and Direction does not appear to indicate that upstream and downstream are included.
  • the Specific-Action AVP is an existing AVP. It can still be used by the AF to report events to the PCRF and the PCRF to report events to the AF.
  • Two new enumeration values are defined: DETECT—ALL and REMOVE—ALL, where DETECT—ALL indicates the AF request.
  • the PCRF detects all events, and REMOVE_ALL indicates that the AF request PCRF cancels the detection and reports all events.
  • the two newly defined values can only be used in the message sent by the AF to the PCRF.
  • the Media-Component-Description AVP is an existing AVP, and the Specific-Action AVP is used to indicate that the detection range is the media stream when the AF requests the PCRF to report the reported event.
  • the Media-Sub-Component AVP is an existing AVP, and the parameter Specific-Action AVP is used to indicate that the detection range is a media sub-flow when the AF requests the PCRF to detect the reported event.
  • the AF when the AF requests the PCRF to detect the reported event, it can be in the same Diameter.
  • the PCRF is used to report different events with different detection scopes by including different Specific-Action AVPs in the Media-Component-Description AVP and/or the Media-Sub-Component AVP, and the other aspects are the same as the second method.
  • Flows AVP is an existing AVP that adds Direction AVP to the original so that it can locate an IP stream.
  • Direction is an enumerated type, which can be UPLINK (0, Up), DOWNLINK (1, Down), BOTH (2, Bidirectional).
  • Flow-Number does not appear to indicate all media substreams in the media stream corresponding to Media-Component-Number, and Direction does not appear to indicate that upstream and downstream are included.
  • the Specific-Action AVP is an existing AVP. However, it is not used directly for the AF request PCRF report event. It is not directly used by the PCRF to report events to the AF. It is only used to define various event types. Define two new enumeration values: DETECT—ALL and REMOVE—ALL, where DETECT—ALL indicates that the AF request PCRF detection reports all events, and REMOVE—ALL indicates that the AF request PCRF cancels detection and reports all events, these two newly defined values. Both can only be used in messages sent by the AF to the PCRF.
  • IP-Flows-Specific-Action AVP is a newly defined AVP that binds events and IP flows together. IP-Flows does not appear to indicate that the event is for the entire Diameter.
  • IP-Flows-Specific-Action AVPs are included in the request message (such as AAR) or response message (such as RAA) sent to the PCRF, if one of the events
  • the detection range is the entire Diameter session, and the corresponding IP-Flows-Specific-Action AVP does not include the Flows AVP. Otherwise, the corresponding IP-Flows-Specific-Action AVP may include one or more Flows AVPs to indicate the event detection range (media stream). , any combination of media substream and IP stream).
  • the newly-issued Specific-Action AVP is superimposed on the original basis.
  • IP-Flows-Specific-Action AVPs When you need to delete one or some events, you can include multiple IP-Flows-Specific-Action AVPs in the message, the first IP-Flows-Specific The value of the Specific-Action in the -Action is REMOVE_ALL, the event that was requested to be reported is canceled, and the subsequent IP-Flows-Specific-Action indicates that the event needs to be reported. To cancel all the packets, you need to carry an IP-Flows-Specific-Action AVP in the Diameter message with the value of Specific-Action being REMOVE-ALL.
  • the PCRF When the PCRF reports an event to the AF, it can flexibly report the event to the AF by including one or more IP-Flows-Specific-Action AVPs in the request message (such as RAA) or the response message (such as AAA) sent to the AF. If the impact range of one of the events is the entire Diameter session, the corresponding IP-Flows-Specific-Action AVP does not include the Flows AVP, otherwise the corresponding IP-Flows-Specific-Action AVP may include one or more Flows AVPs to indicate The scope of the event (any combination of media stream, media substream, and IP stream).
  • FIG. 6 is a schematic structural diagram of a system for detecting a bearer event according to an embodiment of the present invention. As shown in Figure 6, the system includes AF 601 and PCRF 602, where:
  • the AF 601 is configured to send a bearer event detection request to the PCRF 602, where the bearer event detection request includes an event detection type range and an event detection range corresponding to each event type in the event detection type range;
  • PCRF 602 which is used to detect this type of event within the event detection range of each event type. And returning to AF 601 the type of event of the detected event and the range of influence of the detected event.
  • the AF 601 may be further configured to send a cancel bearer event detection request to the PCRF 602, where the cancel bearer event detection request includes a cancel detection event type range and a cancellation corresponding to each event type in the cancel detection event type range. Range of event detection;
  • the PCRF 602 is further configured to cancel the detection of the event of the type within the cancellation event detection range of each cancellation detection event type.
  • the AF 601 may be further configured to send an increase bearer event detection request to the PCRF 602, where the increase bearer event detection request includes an increase detection event type range and an event detection range corresponding to each event type in the increase detection event type range. ;
  • the PCRF 602 can be further configured to detect the event of the type within the event detection range of each of the increased detection event types, and return the type of the event of the detected event to the AF 601 and the range of influence of the detected event.
  • the AF 601 may be further configured to send a modified bearer event detection request to the PCRF 602.
  • the modified bearer event detection request includes a detection event type range to be modified and an event detection range to be modified corresponding to each event type in the range of the detection event type to be modified;
  • the PCRF 602 is further configured to detect the event of the type to be modified within the range of the event to be modified for each type of the detected event to be modified, and return the type of the event of the detected event to the AF 601 and the range of influence of the detected event.
  • the AF 601 can send a bearer event detection request to the PCRF 602 through an AAR message or a RAA message.
  • the PCRF 602 can return the type of the event of the detected event and the range of influence of the detected event to the AF 601 through the RAR message or the AAA message.
  • the AF 601 may be further configured to process the event according to an application layer policy after receiving the type of the event in which the event is detected and the scope of the detected event.
  • the AF may request the PCRF to detect the reported event, and may request to add, delete, and modify the reported event, and may send the request to the PCRF in the AF.
  • Message such as an authentication authorization request message
  • the indication in (Auth-Author iza t ion-Reques t , AAR ) can also be indicated in the response message of the AF response PCRF, such as Re-Auth-Answer (RAA), so the actual operation More flexible.
  • Figure ⁇ is a schematic diagram of an AF structure in accordance with an embodiment of the present invention.
  • the AF includes a bearer event detection request transmitting unit 701 and an event processing unit 702, where:
  • the bearer event detection request sending unit 701 is configured to send a bearer event detection request to the PCRF, where the bearer event detection request includes an event detection type range and an event detection range corresponding to each event type in the event detection type range.
  • the event processing unit 702 is configured to process the event according to an application layer policy after receiving the event type of the event detected by the PCRF and the affected range of the detected event.
  • FIG. 8 is a schematic diagram showing the structure of a PCRF according to an embodiment of the present invention.
  • the PCRF includes an event detecting unit 801 and a detection result returning unit 802.
  • the event detecting unit 801 is configured to receive a bearer event detection request sent by the AF, and detect the event of the type in the event detection range of each event type, where the bearer event detection request includes an event detection type range and corresponding An event detection range for each event type in the range of event detection types.
  • the detection result return unit 802 is configured to return the type of the event of the detected event to the AF and the influence range of the detected event.
  • the embodiment of the present invention first provides a method for detecting a bearer event by using an AF.
  • the AF request PCRF detects the reported event type and the detection range, and the detection range may be any combination of the entire Diameter session or the media stream, the media substream, and the IP stream, and different
  • the detection range of the event may be the same or different.
  • the event type may request to detect and report all event types in a wildcard manner, or may request to detect and report one or some events; the PCRF cooperates with the PCEF according to the AF request.
  • the AF specified event is detected within the range specified by the AF. After detecting the corresponding event, the PCRF reports to the AF
  • the event type and the scope of the impact may be any combination of the entire Diameter session or the media stream, the media substream, and the IP stream.
  • the event impact range indicated by the PCRF reporting must be within the detection range specified by the AF request, and the AF designation. Events that occur outside of the detection range are not reported, and AF does not specify the type of event and does not report it.
  • the PCRF can report multiple events at once, and the impact range of these events can be the same or different.
  • the AF can also take corresponding measures according to the policies of the application layer and the reported events (such as tearing down services, modifying services through signaling, etc.).
  • the PCRF can be requested to cancel the report bearer event, indicating the type of the event to be canceled and the detection range.
  • the detection range can be any combination of the entire Diameter session or media stream, media substream and IP stream.
  • the event type can be used in the wildcard mode to cancel the detection and report all event types, or cancel the detection to report some or some events.
  • the detection range when the AF cancels the reporting event may be larger than the detection range indicated when the previous requesting the reporting event (for example, after requesting an event to be reported on a certain media stream, requesting to cancel the reporting event on the entire session, in the media stream) Of course, it is also canceled.) (For example, after requesting an event to be reported on the entire Diameter session, requesting to cancel the event on a media stream, indicating that the event is continuously detected on other media streams) may also be equal. .
  • the PCRF can be requested to increase the detection and reporting of the bearer event.
  • the AF can request to modify the range of detecting the bearer event (increase or decrease).
  • the PCRF After the PCRF detects the reported event, it can request the PCRF to update and detect the reported event type and detection range, that is, directly replace the request with the reported event type and detection range carried in the new message.
  • the AF may request the PCRF to report the event, or may request to add, cancel, or modify the reported event, which may be indicated in the request message (such as AAR) sent by the AF to the PCRF. It can also be indicated in the response message (such as RAA) of the AF response PCRF.
  • the PCRF reports an event to the AF, it may be indicated in a request message (such as RAR) sent by the PCRF to the AF, or may be indicated in a response message (such as AAA) of the PCRF response AF.
  • the AF may request the PCRF to report certain events at any time, and may also cancel the detection of reporting certain events, increasing the detection of other events, or modifying the detection range of the event.
  • the granularity of detection of an event can be any combination of the entire Diameter session or media stream, media substream, and IP stream. Therefore, the problem that the existing mechanism event detection granularity is too large (only the entire Diameter session) is unnecessary, the event influence range indication is ambiguous (the minimum can only reach the media substream, and the IP flow cannot be indicated) is solved. At the same time, it also solves the problem that the existing event detection reporting mechanism is inflexible (can only be specified in the first request message sent by the AF to the PCRF, and cannot be modified later).
  • the mechanism described in the implementation of the present invention can also be used for signaling path state detection.
  • the signaling-Media-Component-Number can be 0 or a special number (a ratio of 3 ⁇ 4 ports).
  • OxFFFFFFFF the flow-number AVP is specified by the AF (which can be sorted according to the size of the port number, etc.), and the signaling flow can also be described by the Flow-Description AVP, so that the event detection report of the signaling flow is consistent with the event detection report of the media stream. There is no need to establish a new Diameter session for signaling path state detection.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

A method, system and device for examining a carrying event are provided, in which an application fυnction(AF) sends an examining request of the carrying event to a policy control and charging rules function(PCRF), the examining request of the carrying event comprises the types scope of an event examining and scope of the event examining corresponding to each event type in the types scope of the event examining; PCRF examines the event with this kind of type in the scope of the event examining of each event type, and returns the event type of an examined event and influence scope of the examined event to AF.

Description

检测承载事件的方法、 ***和装置 技术领域  Method, system and device for detecting bearer events
本发明涉及通信技术领域, 更具体地说, 本发明涉及检测承载事件的方 法、 ***和装置。  Field of the Invention This invention relates to the field of communications technology and, more particularly, to a method, system and apparatus for detecting bearer events.
背景技术 Background technique
在通信网络向全网际协议 ( Internet Protocol, IP) 演进的过程中, 为 了提供满意的业务, 需要解决端到端服务质量(Quality Of Service, QoS ) 问题。 IP 网络可以提供各种各样的业务, 比如多媒体呼叫、 文件下载、 网页 浏览等, 其中不同的业务对 QoS (包括带宽、 时延、丟包率等)有不同的要求, 而且计费方面的要求也不同。 比如: 可以釆用在线计费或者离线计费, 还可 以根据流量计费或者根据时间计费等。  In the process of evolving the communication network to the Internet Protocol (IP), in order to provide satisfactory services, it is necessary to solve the problem of end-to-end Quality of Service (QoS). IP networks can provide a variety of services, such as multimedia calls, file downloads, web browsing, etc., where different services have different requirements for QoS (including bandwidth, delay, packet loss rate, etc.), and billing The requirements are also different. For example: Online billing or offline billing can be used, and it can be charged according to the flow rate or according to the time.
为了解决上述 QoS和计费等相关问题, 第三代合作伙伴计划 (The Third Generation Partnership Project, 3GPP )定义了策略和计费控制 ( Policy and Charging Control, PCC) 架构, 通过该架构可以满足不同的 QoS控制和计费 需求。  In order to solve the above-mentioned problems related to QoS and billing, the Third Generation Partnership Project (3GPP) defines a Policy and Charging Control (PCC) architecture, through which different schemes can be satisfied. QoS control and billing requirements.
图 1为现有技术中 PCC结构的示意图, 其中各个功能实体作用如下描述: 策略控制和计费规则功能实体 ( Policy Control and Charging Rules Function , PCRF ), 主要完成策略的决策和基于流的计费控制等功能。 PCRF 实体根据运营商策略、 用户签约数据以及用户当前正在进行的业务信息等决 定相应的策略,并将该策略提供给策略和计费执行实体( Policy and Charging Enforcement Function , PCEF ), 由 PCEF执行这些策略。 用户签约数据可以 从用户签约数据数据库 ( Subscription Profile Repository , SPR )功能实 体中获取。 策略包括业务数据流(完成某业务如语音通信的 IP流的集合) 的 检测规则、 是否门控、 QoS、 基于流的计费规则等。  1 is a schematic diagram of a PCC structure in the prior art, in which each functional entity functions as follows: Policy Control and Charging Rules Function (PCRF), mainly completes policy decision and flow-based charging. Control and other functions. The PCRF entity determines the corresponding policy according to the operator policy, the user subscription data, and the service information currently being performed by the user, and provides the policy to the Policy and Charging Enforcement Function (PCEF), which is executed by the PCEF. Strategy. User subscription data can be obtained from the User Profile Data Repository (SPR) function entity. Policies include detection rules for service data flows (collections of IP flows that complete a service such as voice communication), whether to gate, QoS, flow-based charging rules, and so on.
PCEF, 主要用于完成业务数据流的检测、 策略的执行、 基于流的计费等 功能。 该实体执行 PCRF下发或者指定的策略, 具体来说就是执行业务数据流 的检测和测量、保证业务数据流的 QoS、用户面流量处理和触发控制面的会话 管理等。 PCEF is mainly used to complete the detection of service data flows, the execution of policies, flow-based charging, etc. Features. The entity performs the policy that is sent or specified by the PCRF, specifically, performs detection and measurement of the service data flow, guarantees QoS of the service data flow, user plane traffic processing, and session management of the trigger control plane.
SPR, 该功能实体用于向 PCRF提供用户签约数据。  SPR, the functional entity is used to provide user subscription data to the PCRF.
应用层功能实体( Appl ica t ion Funct ion , AF ), 该功能实体用于向 PCRF 动态提供应用层业务的会话信息, 供 PCRF制定相应的策略, AF可以从 PCRF 获取 IP连接性接入网络 ( IP-Connect iv i ty Acces s Network , IP-CAN )相 关的信息以及 IP-CAN承载相关的事件等。  The application layer function entity (Appl ica t ion Funct ion, AF), the function entity is used to dynamically provide session information of the application layer service to the PCRF, and the PCRF formulates a corresponding policy, and the AF can obtain the IP connectivity access network from the PCRF ( IP-Connect iv i ty Acces s Network , IP-CAN ) related information and IP-CAN bearer related events.
AF和 PCRF之间的接口为 Rx参考点。该参考点用于 AF下发应用层相关信 息, 包括用于识别业务数据流的 IP过滤器(如源 IP地址、 目的 IP地址、 协 议类型、 源端口号、 目的端口号等)、 应用或者媒体所需的带宽信息。 PCRF也 可以通过该参考点向 AF提供 IP-CAN相关的信息、 上报承载事件等。 该参考 点使用 ( Internet Eng ineer ing Task Force , IETF )定义的 Diameter十办议。  The interface between AF and PCRF is the Rx reference point. The reference point is used by the AF to deliver application layer related information, including an IP filter (such as a source IP address, a destination IP address, a protocol type, a source port number, a destination port number, etc.) for identifying a service data flow, an application, or a media. Required bandwidth information. The PCRF can also provide IP-CAN related information, report bearer events, etc. to the AF through the reference point. This reference point uses the Diameter ten defined by the Internet Eng ineering Task Force (IETF).
当用户在接入网络内漫游(位置改变时)仍能保存 IP业务连续性(即不 中断业务), 具有这样性质的接入网络称为 IP-CAN, 比如(Genera l Packet Radio Service , GPRS ) 网络, 互通无线局域( Inter working-WLAN , I-WLAN ) 网络等。 IP-CAN会话,指的是 UE和 PDN之间的关联关系,通过用户设备(User Equi pment , UE ) 的 IP地址和 UE的标识(如 IMSI )来识别。 只要 UE分配了 IP地址并且能被 IP网络识别, 则 IP-CAN存在。  When the user roams within the access network (when the location changes), the IP service continuity can be preserved (ie, the service is not interrupted). The access network with such a nature is called IP-CAN, such as (Genera l Packet Radio Service, GPRS). Network, interworking-WLAN (I-WLAN) network, etc. The IP-CAN session refers to the association between the UE and the PDN, and is identified by the IP address of the User Equipment (UE) and the identity of the UE (such as IMSI). The IP-CAN exists as long as the UE is assigned an IP address and can be identified by the IP network.
一个 IP-CAN会话可以包含一个或者多个 IP-CAN承载。 将 PCRF制定的策 略和具体的 IP-CAN承载绑定可以分别由 PCRF或者 PCEF实现。  An IP-CAN session can contain one or more IP-CAN bearers. The strategy formulated by the PCRF and the specific IP-CAN bearer binding can be implemented by PCRF or PCEF, respectively.
在 PCEF上形成如图 2所示的 IP-CAN会话、 IP-CAN承载、 PCC规则和 IP 流之间的绑定关系。 为了满足不同的 QoS要求, 在同一个 IP-CAN会话里可以 建立不同 QoS要求的 IP-CAN承载, 假设图 2中 IP-CAN承载 1比 IP-CAN承载 2有更高的 QoS , 这样对于 QoS要求较高的业务(如 VOIP , 多媒体呼叫等)可 以使用 IP-CAN承载 1 , 对于 QoS要求较低业务(比如文件下载等、 网页浏览 等)可以使用 IP-CAN承载 2。 PCEF根据 PCC规则中流描述信息 (如源 IP地 址、 目的 IP地址、 协议类型、 源端口号、 目的端口号等)来识别 IP流。 The binding relationship between the IP-CAN session, the IP-CAN bearer, the PCC rule, and the IP flow as shown in FIG. 2 is formed on the PCEF. In order to meet different QoS requirements, IP-CAN bearers with different QoS requirements can be established in the same IP-CAN session. Assume that IP-CAN bearer 1 in Figure 2 has higher QoS than IP-CAN bearer 2, thus for QoS. High-demand services (such as VOIP, multimedia calls, etc.) can use IP-CAN bearer 1 for lower QoS requirements (such as file downloading, web browsing) Etc.) IP-CAN bearer 2 can be used. The PCEF identifies the IP flow according to the flow description information (such as source IP address, destination IP address, protocol type, source port number, destination port number, etc.) in the PCC rule.
IP流是由具有相同源 IP地址、 目的 IP地址、 传输层协议、 源端口号和 目的端口号(合称 IP五元组, 如果对应的传输层协议没有端口号的概念, 源 端口号和目的端口号可以省略)的 IP报文所组成的单向流。 在 Rx参考点上, 每个 IP Flow通过一个 F low-Descr ipt ion AVP描述。  The IP flow is composed of the same source IP address, destination IP address, transport layer protocol, source port number, and destination port number (collectively IP quintuple, if the corresponding transport layer protocol does not have a port number concept, source port number and destination A one-way flow consisting of IP packets whose port number can be omitted. At the Rx reference point, each IP Flow is described by an F low-Descr ipt ion AVP.
从图 2中可以看出, 一个 IP-CAN会话中可以建立多个 IP-CAN承载, 而 一个 IP-CAN承载可以用于传输一个或者多个 IP流(要求这些 IP流对 QoS的 要求一致), 一个 PCC规则只能针对一个 IP-CAN承载, 且一个 IP-CAN承载上 可以有一条或者多条 PCC规则。  As can be seen from Figure 2, multiple IP-CAN bearers can be established in one IP-CAN session, and one IP-CAN bearer can be used to transmit one or more IP flows (requires that these IP flows have the same QoS requirements) A PCC rule can only be used for one IP-CAN bearer, and one IP-CAN bearer can have one or more PCC rules.
由此可见, 在现有技术中, 具有如下缺点:  Thus, in the prior art, the following disadvantages are encountered:
AF请求事件上报只能针对 AF与 PCRF之间的整个 D i ame t e r会话。 然而, AF需要关注的不一定是整个会话中的所有 IP流, 可能仅仅是某些 IP流, 但 现有技术 PCEF可能会对不关心的 IP-CAN承载或者 IP流进行检测,并将出 现的检测状态上报, PCRF也需要向 AF上报。 实际上 AF不需要这些信息, 这 就导致 PCEF和 PCRF之间、 PCRF和 AF之间出现冗余的消息交互, 增加了三个 设备之间不必要的负载。 比如 AF仅关注如图 1所示 IP流 1的中断情况(这 将导致业务中止), 而不关注如图 2所示的其他 IP流。使用现有的机制, PCRF 必须指示 PCEF上报该会话中所有 IP-CAN承载中断情况。 发明内容  The AF request event escalation can only be directed to the entire D i ame t e r session between AF and PCRF. However, AF needs to pay attention not to all IP flows in the entire session, and may only be some IP flows, but the prior art PCEF may detect IP-CAN bearers or IP flows that are not concerned, and will appear. The detection status is reported, and the PCRF also needs to report to the AF. In fact, AF does not need this information, which leads to redundant message interaction between PCEF and PCRF, between PCRF and AF, adding unnecessary load between the three devices. For example, AF only pays attention to the interruption of IP flow 1 as shown in Figure 1 (this will cause the service to abort), and does not pay attention to other IP flows as shown in Figure 2. Using the existing mechanism, the PCRF must instruct the PCEF to report all IP-CAN bearer interruptions in the session. Summary of the invention
有鉴于此, 本发明实施例的主要目的是提出一种检测承载事件的方法, 以降低冗余的消息交互。 本发明实施例的另一目的是提出一种检测承载事件的***, 以降低冗余 的消息交互。  In view of this, the main purpose of the embodiments of the present invention is to provide a method for detecting bearer events to reduce redundant message interaction. Another object of embodiments of the present invention is to provide a system for detecting bearer events to reduce redundant message interaction.
本发明实施例的再一目的是提出一种 AF, 以降低冗余的消息交互。  A further object of embodiments of the present invention is to propose an AF to reduce redundant message interaction.
本发明实施例的另一目的是提出一种 PCRF, 以降低冗余的消息交互。 为达到上述目的, 本发明实施例的技术方案是这样实现的: 一种检测承载事件的方法, 该方法包括: Another object of embodiments of the present invention is to propose a PCRF to reduce redundant message interaction. To achieve the above objective, the technical solution of the embodiment of the present invention is implemented as follows: A method for detecting a bearer event, the method includes:
应用层功能实体 AF向策略控制和计费规则功能实体 PCRF发送承载事件 检测请求, 所述承载事件检测请求中包含事件检测类型范围以及对应于所述 事件检测类型范围中每一事件类型的事件检测范围;  The application layer function entity AF sends a bearer event detection request to the policy control and charging rule function entity PCRF, where the bearer event detection request includes an event detection type range and event detection corresponding to each event type in the event detection type range. Scope
PCRF在每一事件类型的事件检测范围内检测该种类型的事件,并向 AF返 回所检测到事件的事件类型及该检测到事件的影响范围。  The PCRF detects this type of event within the event detection range of each event type, and returns the type of event of the detected event to the AF and the range of influence of the detected event.
一种检测承载事件的***, 该***包括 AF和 PCRF , 其中:  A system for detecting bearer events, the system comprising AF and PCRF, wherein:
AF , 用于向 PCRF发送承载事件检测请求, 所述承载事件检测请求中包含 事件检测类型范围以及对应于所述事件检测类型范围中每一事件类型的事件 检测范围;  An AF, configured to send a bearer event detection request to the PCRF, where the bearer event detection request includes an event detection type range and an event detection range corresponding to each event type in the event detection type range;
PCRF , 用于在每一事件类型的事件检测范围内检测该种类型的事件, 并 向 AF返回所检测到事件的事件类型及该检测到事件的影响范围。  The PCRF is configured to detect the type of event within the event detection range of each event type, and return the type of the event of the detected event to the AF and the range of influence of the detected event.
一种 AF , 该 AF包括承载事件检测请求发送单元和事件处理单元, 其中: 承载事件检测请求发送单元, 用于向 PCRF发送承载事件检测请求, 所述 承载事件检测请求中包含事件检测类型范围以及对应于所述事件检测类型范 围中每一事件类型的事件检测范围;  An AF, the AF includes a bearer event detection request sending unit and an event processing unit, where: a bearer event detecting request sending unit is configured to send a bearer event detecting request to the PCRF, where the bearer event detecting request includes an event detecting type range and Corresponding to an event detection range of each event type in the event detection type range;
事件处理单元, 用于在收到由 PCRF所检测到事件的事件类型及该检测到 事件的影响范围后, 根据应用层策略对事件进行处理。  The event processing unit is configured to process the event according to an application layer policy after receiving the event type of the event detected by the PCRF and the scope of the detected event.
一种 PCRF , 该 PCRF包括事件检测单元和检测结果返回单元, 其中: 事件检测单元, 用于接收由 AF发送的承载事件检测请求, 并在每一事件 类型的事件检测范围内检测该种类型的事件, 其中所述承载事件检测请求中 包含事件检测类型范围以及对应于所述事件检测类型范围中每一事件类型的 事件检测范围;  A PCRF, the PCRF includes an event detecting unit and a detection result returning unit, where: an event detecting unit is configured to receive a bearer event detecting request sent by the AF, and detect the type in the event detecting range of each event type. An event, where the bearer event detection request includes an event detection type range and an event detection range corresponding to each event type in the event detection type range;
检测结果返回单元, 用于向 AF返回所检测到事件的事件类型及该检测到 事件的影响范围。 从上述技术方案中可以看出, 在本发明实施例中, AF请求 PCRF检测上报 事件时,指明检测的事件类型范围和检测范围,检测范围可以是整个 D i ame t e r 会话或者媒体流、 媒体子流和 IP流的任意组合, 不同事件的检测范围可以不 同。 PCRF根据 AF的请求, 和 PCEF配合在 AF指定的范围内检测 AF指定的事 件, 检测到相应事件后, PCRF向 AF上报事件的类型和事件的影响范围, 其中 影响范围可以是整个 Diameter会话或者媒体流、 媒体子流和 IP流的任意组 合。 由此可见, 应用本发明以后, 解决了现有机制中由事件检测粒度过大(只 能是整个 Diameter会话)所导致的不必要消息交互、 事件影响范围指示不明 确 (最小只能到媒体子流, 不能指示 IP流) 的问题, 因此能够显著地降低冗 余的消息交互。 同时, 还解决了现有的事件检测上报机制使用不灵活的问题 (只能在 AF发送给 PCRF的第一个请求消息中指定, 后续不能修改)的问题。 附图说明 The detection result returning unit is configured to return the type of the event of the detected event to the AF and the influence range of the detected event. As shown in the foregoing technical solution, in the embodiment of the present invention, when the AF request PCRF detects the reported event, it indicates the range of the detected event type and the detection range, and the detection range may be the entire D i ame ter session or the media stream or the media sub- Any combination of stream and IP flow, the detection range of different events can be different. The PCRF detects the event specified by the AF in the range specified by the AF according to the request of the AF. After detecting the corresponding event, the PCRF reports the type of the event and the scope of the event to the AF, where the impact range may be the entire Diameter session or media. Any combination of streams, media substreams, and IP streams. It can be seen that, after applying the present invention, the unnecessary message interaction caused by the excessively large event detection granularity (only the entire Diameter session) in the existing mechanism is solved, and the indication range of the event impact is ambiguous (minimum only to the media sub- Streams, which cannot indicate IP traffic, can significantly reduce redundant message interactions. At the same time, it solves the problem that the existing event detection reporting mechanism is inflexible (can only be specified in the first request message sent by the AF to the PCRF, and cannot be modified later). DRAWINGS
图 1为现有技术中 PCC结构的示意图;  1 is a schematic diagram of a PCC structure in the prior art;
图 2为现有技术中 IP流、 PCC规则、 IP-CAN承载、 IP-CAN会话之间的 对应关系示意图;  2 is a schematic diagram of correspondence between IP flows, PCC rules, IP-CAN bearers, and IP-CAN sessions in the prior art;
图 3为根据本发明实施例的检测承载事件的方法流程示意图;  3 is a schematic flowchart of a method for detecting a bearer event according to an embodiment of the present invention;
图 4为根据本发明第一实施例的检测承载事件的方法流程示意图; 图 5为根据本发明第二实施例的检测承载事件的方法流程示意图; 图 6为根据本发明实施例的检测承载事件的***结构示意图;  4 is a schematic flowchart of a method for detecting a bearer event according to a first embodiment of the present invention; FIG. 5 is a schematic flowchart of a method for detecting a bearer event according to a second embodiment of the present invention; FIG. 6 is a diagram for detecting a bearer event according to an embodiment of the present invention. Schematic diagram of the system structure;
图 Ί为根据本发明实施例的 AF结构示意图;  Figure Ί is a schematic diagram of an AF structure according to an embodiment of the present invention;
图 8为根据本发明实施例的 PCRF结构示意图。  FIG. 8 is a schematic diagram showing the structure of a PCRF according to an embodiment of the present invention.
具体实施方式 detailed description
本发明实施例中所用到的 Diameter 系列协议是新一代的鉴权授权应答 ( Auth-Author iza t ion-Reques t , AAA )技术, 其目的是创建一个能够充分 满足目前乃至今后 IP网络 (包括 NGN以及 3G等)用户访问控制要求的 AAA 协议。 Diame ter 协议是远程鉴权拨号用户业务 ( Remote Authent ica t ion Dia l-In User Service , RADIUS )协议的升级, 包含基础协议、 传送协议、 以及针对不同应用场景的扩展协议(Diameter 中将针对不同应用场景的扩展 称为应用, 比如 PCC架构中 Rx、 Gx参考点就是两个不同的 Diameter应用)。 各种应用共用的基本功能在基础协议中实现, 而不同应用场景特定的功能在 各应用中定义。 The Diameter series protocol used in the embodiments of the present invention is a new generation of Authentication Authorization Answer (AAA) technology, and the purpose is to create an IP network (including NGN) that can fully satisfy the current and future. And 3G, etc.) AAA protocol for user access control requirements. The Diame ter protocol is a remote authentication dial-up user service ( Remote Authent ica t ion Upgrade of the Dia L-In User Service (RADIUS) protocol, including the basic protocol, the transport protocol, and the extended protocol for different application scenarios. The extension for different application scenarios in Diameter is called an application, such as the Rx and Gx reference in the PCC architecture. Points are two different Diameter applications). The basic functions shared by various applications are implemented in the base protocol, and the functions specific to different application scenarios are defined in each application.
和传统的客户端 /服务器模式的协议(如 RADIUS ) 不同, Diameter客户 端与 Diameter服务器都可以主动向对端发送请求消息。 Diameter客户端与 Diameter服务器进行一系列的信息交换, 而这样一个从发起到中止的一系列 信息交互, 称为一个 Diameter会话。 Diameter会话的建立, 一般是由客户端 发起。 Diameter会话的结束, 完全由客户端决定, 不过服务器也可以先行发 出中止会话请求, 在客户端同意中止请求的情况下, 会响应中止会话应答, 然后客户端再发出会话结束请求, 通知服务器结束用户会话, 否则会话仍然 得以保持。  Unlike traditional client/server mode protocols (such as RADIUS), both the Diameter client and the Diameter server can actively send request messages to the peer. The Diameter client performs a series of information exchange with the Diameter server, and such a series of information interactions from initiation to suspension is called a Diameter session. The establishment of a Diameter session is generally initiated by the client. The end of the Diameter session is completely determined by the client, but the server can also issue an abort session request first. If the client agrees to abort the request, it will respond to the abort session response, and then the client will issue a session end request to notify the server to end the user. Session, otherwise the session is still maintained.
Diameter 消息由消息头和消息体组成, 消息头中包括协议版本号、 应用 标识(标识不同的 Diameter应用)、 命令代码(Command Code , 表示消息类 型)、 消息长度等信息, 消息体由属性值对(At tr ibute-Va lue-Pa i r , AVP ) 组成。 不同类型的 Diameter消息可以包含不同的 AVP, 各个应用可以定义该 应用特有的 AVP, 通过定义新的 AVP从而实现新的功能正是 Diameter的一种 扩展机制。  The Diameter message consists of a message header and a message body. The message header includes the protocol version number, the application identifier (identifying different Diameter applications), the command code (Command Code, indicating the message type), the message length, etc., and the message body is composed of attribute values. (At tr ibute-Va lue-Pa ir , AVP ) composition. Different types of Diameter messages can contain different AVPs. Each application can define an AVP specific to the application. It is an extension mechanism of Diameter to define a new AVP to implement new functions.
图 3为根据本发明实施例的检测承载事件的方法流程示意图。 如图 3所 示, 该方法包括:  FIG. 3 is a schematic flowchart of a method for detecting a bearer event according to an embodiment of the present invention. As shown in Figure 3, the method includes:
步骤 301 : AF向 PCRF发送承载事件检测请求, 承载事件检测请求中 包含事件检测类型范围以及对应于事件检测类型范围中每一事件类型的事件 检测范围。  Step 301: The AF sends a bearer event detection request to the PCRF, where the bearer event detection request includes an event detection type range and an event detection range corresponding to each event type in the event detection type range.
其中, 所述事件检测范围可以为整个 Diameter会话, 或者媒体流、 媒体 子流和 IP流的任意组合。 并且, 事件检测类型范围可以包括所有事件类型, 或者包括至少一个特定的事件类型。 在 Rx 参考点上, 每个媒体流通过一个 Media-Component-Descr i pt ion AVP 描述。 同一个会话中的多个媒体流通过 Media-Component-N讓 ber AVP标识。 如果 AF釆用会话描述协议( SDP )对媒 体进行描述, 那么一个媒体流就对应 SDP中的 m行(媒体描述行), 这个媒体 流对应的 Media-Component-Number就是该 m行在 SDP中出现的顺序号。 媒体 子流是对媒体流进一步细分, 比如一个音频媒体流釆用实时传输协议(RTP ) 方式传输时, 相应的 RTP流和 RTCP流分别对应一个媒体子流。 在 Rx参考点 上, 每个媒体子流通过一个 Media-Sub-Component AVP描述。 同一个媒体流 中的多个媒体子流通过 Flow-Number AVP标识, Flow-Number可以根据各媒体 子流对应的端口号等排序。 媒体子流可以对应一个双向流 (包含两个 Flow-Descr ipt ion AVP, 描述两个 IP 流), 也可以对应一个单向流(只包含 一个 Flow-Descr ipt ion AVP , 描述一个 IP流)。 The event detection range may be an entire Diameter session, or any combination of a media stream, a media substream, and an IP stream. Also, the event detection type range can include all event types. Or include at least one specific event type. At the Rx reference point, each media stream is described by a Media-Component-Descr i pt ion AVP. Multiple media streams in the same session are identified by ber AVP via Media-Component-N. If AF uses the Session Description Protocol (SDP) to describe the media, then a media stream corresponds to the m line (media description line) in the SDP. The Media-Component-Number corresponding to the media stream is that the m line appears in the SDP. The sequence number. The media substream is further subdivided into the media stream. For example, when an audio media stream is transmitted by the Real Time Transport Protocol (RTP), the corresponding RTP stream and the RTCP stream respectively correspond to one media substream. At the Rx reference point, each media substream is described by a Media-Sub-Component AVP. The multiple media substreams in the same media stream are identified by the Flow-Number AVP, and the Flow-Number can be sorted according to the port number corresponding to each media substream. The media substream can correspond to a bidirectional flow (containing two Flow-Descr IVPs, describing two IP flows), or a unidirectional flow (containing only one Flow-Descr iption AVP, describing an IP flow).
在这里, AF请求 PCRF检测上报事件时, 指明需要检测的事件类型和检 测范围, 其中不同类型事件的检测范围可以不同。  Here, when the AF request PCRF detects the reported event, it indicates the type of the event to be detected and the detection range, and the detection range of the different types of events may be different.
步骤 302: PCRF在每一事件类型的事件检测范围内检测该种类型的事件, 并向 AF返回所检测到事件的事件类型及该检测到事件的影响范围。  Step 302: The PCRF detects the type of event in the event detection range of each event type, and returns the type of the event of the detected event to the AF and the influence range of the detected event.
在这里, PCRF根据 AF的请求, 和 PCEF配合在 AF指定的范围内检测 AF指定的事件, 检测到相应事件后, PCRF向 AF上报事件的类型和事件的 影响范围, 影响范围可以是整个 Diameter会话或者媒体流、 媒体子流和 IP流 的任意组合。  Here, the PCRF detects the event specified by the AF in the range specified by the AF according to the request of the AF. After detecting the corresponding event, the PCRF reports the type of the event and the scope of the event to the AF, and the impact range may be the entire Diameter session. Or any combination of media streams, media substreams, and IP streams.
其中, 事件检测类型范围中各事件检测类型的事件检测范围并不相同, 并且各检测到事件的影响范围也并不相同; 或所述事件检测类型范围中各事 件检测类型的事件检测范围相同, 并且各检测到事件的影响范围也相同; 或 所述事件检测类型范围中各事件检测类型的事件检测范围并不相同, 并且各 检测到事件的影响范围相同; 或所述事件检测类型范围中各事件检测类型的 事件检测范围相同, 并且各检测到事件的影响范围并不相同。 另夕卜, 在 AF与 PCRF之间的 Diameter会话的整个生命周期内, AF都可 以请求 PCRF检测上报事件, 可以请求增加、 删除、 修改上报事件, 可以在 AF发送给 PCRF的请求消息 (比如 AAR ) 中指示, 也可以在 AF应答 PCRF 的响应消息 (比如 RAA ) 中指示。 The event detection range of each event detection type in the event detection type range is not the same, and the range of influence of each detected event is not the same; or the event detection range of each event detection type in the event detection type range is the same, And the range of the impact of each detected event is the same; or the event detection range of each event detection type in the range of the event detection type is not the same, and the range of influence of each detected event is the same; or each of the types of event detection types The event detection type has the same range of event detection, and the range of influence of each detected event is not the same. In addition, during the entire life cycle of the Diameter session between the AF and the PCRF, the AF may request the PCRF to detect the reported event, and may request to add, delete, and modify the reported event, and may send a request message (such as AAR) to the PCRF in the AF. The indication in ) can also be indicated in the response message (such as RAA) of the AF response PCRF.
具体地: 比如, 当需要增加取消检测上报的事件类型时, AF可以进一步 向 PCRF发送取消承载事件检测请求, 所述取消承载事件检测请求中包含取 消检测事件类型范围以及对应于所述取消检测事件类型范围中每一事件类型 的事件检测范围; PCRF在每一取消检测事件类型的事件检测范围内, 取消检 测该种类型的事件。  Specifically, the AF may further send a cancel bearer event detection request to the PCRF, where the cancel bearer event detection request includes a cancel detection event type range and corresponding to the cancel detection event, when the event type of the cancellation detection report needs to be increased. The event detection range for each event type in the type range; the PCRF cancels the detection of this type of event within the event detection range of each cancellation detection event type.
可选地, 当需要增加检测上报的事件类型时, AF可以还可以向 PCRF发 送增加承载事件检测请求, 所述增加承载事件检测请求中包含增加检测事件 类型范围以及对应于所述增加检测事件类型范围中每一事件类型的事件检测 范围; PCRF在每一增加检测事件类型的事件检测范围内, 检测该种类型的事 件, 并向 AF返回所检测到事件的事件类型及该检测到事件的影响范围。  Optionally, the AF may further send an increase bearer event detection request to the PCRF, where the increased bearer event detection request includes an increase detection event type range and corresponding to the increased detection event type. The range of event detection for each event type in the range; the PCRF detects the type of event within the range of event detection for each type of increased detection event, and returns the type of event of the detected event to AF and the impact of the detected event. range.
当需要修改检测上报的事件类型和检测范围时, AF可以向 PCRF发送修 改承载事件检测请求, 所述修改承载事件检测请求中包含待修改的检测事件 类型范围以及对应于所述待修改检测事件类型范围中每一事件类型的待修改 事件检测范围; PCRF在每一待修改检测事件类型的待修改事件检测范围内, 检测该种类型的事件,并向 AF返回所检测到事件的事件类型及该检测到事件 的影响范围。  The AF may send a modify bearer event detection request to the PCRF, where the modified bearer event detection request includes the detection event type range to be modified and the type of the detection event to be modified. The event detection range to be modified for each event type in the range; the PCRF detects the event of the type within the range of the event to be modified for each type of the detection event to be modified, and returns the event type of the detected event to the AF and the The range of impact of the event was detected.
还可以将本发明用于信令路径状态检测。 为避免和媒体流的 Media-Component-Number冲突,信令流的 Media-Component-Number可以为 0 或者特殊的数字 (比 ¾口 OxFFFFFFFF )。 Flow-Number AVP由 AF指定, 信令 流由 Flow-Description AVP描述,这样信令流的事件检测上报和媒体流的事件 检测上报一致, 无需为信令路径状态检测建立新的 Diameter会话。  The invention can also be used for signaling path state detection. To avoid media-Component-Number conflicts with media streams, the Media-Component-Number of the signaling stream can be 0 or a special number (3x4 OxFFFFFFFF). The flow-number AVP is specified by the AF, and the signaling flow is described by the Flow-Description AVP, so that the event detection report of the signaling flow is consistent with the event detection report of the media stream, and there is no need to establish a new Diameter session for the signaling path state detection.
AF可以在请求消息中请求 PCRF检测上报事件。 图 4为根据本发明第一 实施例的检测承载事件的方法流程示意图。 The AF may request the PCRF to detect the reported event in the request message. Figure 4 is the first in accordance with the present invention A schematic diagram of a method for detecting a bearer event of an embodiment.
如图 4所示, 该方法包括:  As shown in Figure 4, the method includes:
步骤 401: AF向 PCRF发送请求消息(比如可以为 AAR消息;),请求 PCRF 检测上报事件, 在该请求消息中指明检测的事件类型范围和检测范围, 检测 范围可以是整个 Diameter会话或者媒体流、 媒体子流和 IP流的任意组合, 不 同事件的检测范围可以相同或者不同。 其中, 事件类型可以釆用通配的方式 一次请求检测上报所有事件类型, 也可以请求检测上报某个或者某些事件。  Step 401: The AF sends a request message (for example, may be an AAR message to the PCRF), and requests the PCRF to detect the reported event, where the detected event type range and the detection range are specified, and the detection range may be the entire Diameter session or the media stream, Any combination of media sub-flow and IP flow, the detection range of different events may be the same or different. The event type can use the wildcard method to request to detect and report all event types at one time, or request to detect and report one or some events.
步骤 402: PCRF向 AF返回应答消息 (比如为 AAA消息;)。  Step 402: The PCRF returns a response message to the AF (for example, an AAA message;).
步骤 403: PCRF根据 AF指示和 PCEF配合, 在 AF指定的范围内检测 AF指定的事件。  Step 403: The PCRF detects the AF-specified event within the range specified by the AF according to the AF indication and the PCEF.
步骤 404: PCRF检测到相应事件后 , PCRF向 AF发送请求消息(如 RAR 消息), 上报事件类型和事件的影响范围, 影响范围可以是整个 Diameter会话 或者媒体流、 媒体子流和 IP流的任意组合。 PCRF上报时指示的事件影响范 围必须在 AF请求时指明的检测范围之内。 AF指定的检测范围之外发生的事 件不上报, AF没有指定的事件类型也不上报。 PCRF可以一次上报多个事件, 这些事件的影响范围可以相同或者不同。  Step 404: After the PCRF detects the corresponding event, the PCRF sends a request message (such as a RAR message) to the AF, and reports the event type and the scope of the event. The impact range may be the entire Diameter session or the media stream, the media substream, and the IP stream. combination. The event impact range indicated when the PCRF is reported must be within the detection range specified by the AF request. Events that occur outside the detection range specified by the AF are not reported, and the event types that the AF does not specify are not reported. The PCRF can report multiple events at once, and the impact range of these events can be the same or different.
步骤 405: AF向 PCRF发送应答消息 (比如 RAA消息;);  Step 405: The AF sends a response message to the PCRF (such as a RAA message;);
步骤 406: AF根据应用层的策略和上报的事件, 釆取相应的措施(比如 拆除业务、 通过信令修改业务等)。  Step 406: The AF extracts corresponding measures according to the policy of the application layer and the reported event (such as tearing down the service, modifying the service by signaling, etc.).
AF还可以在应答消息中请求 PCRF检测上报事件。 图 5为根据本发明第 二实施例的检测承载事件的方法流程示意图。  The AF can also request the PCRF to detect the reported event in the response message. FIG. 5 is a flow chart showing a method for detecting a bearer event according to a second embodiment of the present invention.
如图 5所示, 该方法包括:  As shown in Figure 5, the method includes:
步骤 501: PCRF向 AF发送请求消息 (比如 RAR消息;)。  Step 501: The PCRF sends a request message (such as a RAR message;) to the AF.
步骤 502: AF向 PCRF返回应答消息 (比如 RAA消息 ), 请求 PCRF检 测上报事件, 消息中指明检测的事件类型范围和检测范围, 检测范围可以是 整个 Diameter会话或者媒体流、 媒体子流和 IP流的任意组合, 不同事件的检 测范围可以不同。 其中事件类型可以釆用通配的方式一次请求检测上报所有 事件类型, 也可以请求检测上报某个或者某些事件。 Step 502: The AF returns a response message (such as a RAA message) to the PCRF, and requests the PCRF to detect the reported event. The message indicates the range of the detected event type and the detection range. The detection range may be the entire Diameter session or the media stream, the media substream, and the IP stream. Any combination of different events The measurement range can be different. The event type may request to detect and report all event types in a wildcard manner, or may request to detect and report one or some events.
步骤 503: PCRF根据 AF指示, 和 PCEF配合, 在 AF指定的范围内检测 AF指定的事件。  Step 503: The PCRF cooperates with the PCEF according to the AF indication to detect the AF-specified event within the range specified by the AF.
步骤 504: PCRF检测到相应事件后, PCRF向 AF发送请求消息 (比如 RAR消息), 上报事件类型和事件的影响范围, 影响范围可以是整个 Diameter 会话或者媒体流、 媒体子流和 IP流的任意组合。 PCRF上报时指示的事件影 响范围必须在 AF请求时指明的检测范围之内。 AF指定的检测范围之外发生 的事件不上报, AF没有指定的事件类型也不上报。 PCRF可以一次上报多个 事件, 这些事件的影响范围可以相同或者不同;  Step 504: After the PCRF detects the corresponding event, the PCRF sends a request message (such as a RAR message) to the AF, and reports the event type and the scope of the event. The impact range may be the entire Diameter session or the media stream, the media substream, and the IP stream. combination. The event impact range indicated when the PCRF is reported must be within the detection range specified by the AF request. Events that occur outside the detection range specified by AF are not reported, and AF does not report the type of event that is not specified. The PCRF can report multiple events at a time, and the impact range of these events can be the same or different;
步骤 505: AF向 PCRF发送应答消息 (比如 RAA消息;);  Step 505: The AF sends a response message to the PCRF (such as an RAA message;);
步骤 506: AF根据应用层的策略和上报的事件, 釆取相应的措施(比如 拆除业务、 通过信令修改业务等)。  Step 506: The AF extracts corresponding measures according to the policy of the application layer and the reported event (such as tearing down the service, modifying the service by signaling, etc.).
目前, AF和 PCRF之间的协议通常为 Diameter协议。 下面以 Diameter 协议为例, 对本发明进行详细阐述。 然而, 本领域技术人员可以意识到, 本 发明并不局限于 Diameter协议。  Currently, the protocol between AF and PCRF is usually the Diameter protocol. The present invention will be described in detail below by taking the Diameter protocol as an example. However, those skilled in the art will appreciate that the present invention is not limited to the Diameter protocol.
方式一:  method one:
首先对现有的 AVP进行扩展 (包括定义几个新的 AVP和为现有的 AVP 定义新的值):  First extend the existing AVP (including defining several new AVPs and defining new values for existing AVPs):
1. IP-Flows AVP  1. IP-Flows AVP
IP-Flows: := < AVP Header: x >  IP-Flows: := < AVP Header: x >
{ Media-Component-Number }  { Media-Component-Number }
*[ Flow-Number ]  *[ Flow-Number ]
[ Direction ]  [ Direction ]
IP-Flows AVP是新定义的 AVP。 这个 AVP用于定位一个或者多个 IP 流,其中 Direction为枚举类型,取值可以为 UPLINK ( 0,上行)、 DOWNLINK ( 1 , 下行)、 BOTH ( 2, 双向)。 { ... }表示比选参数, […]表示可选参数, * 表示可以有多个 (后续釆用相同的规则)。 Flow-Number 不出现表示针对 Media-Component-Number对应的媒体流中的所有媒体子流, Direction不出现 表示包含上行流和下行流。 IP-Flows AVP is a newly defined AVP. This AVP is used to locate one or more IP flows. The Direction is an enumerated type. The value can be UPLINK (0, Up), DOWNLINK. (1, down), BOTH (2, two-way). { ... } indicates comparison parameters, [...] indicates optional parameters, and * indicates that there can be multiple (subsequent use of the same rules). Flow-Number does not appear to represent all media substreams in the media stream corresponding to Media-Component-Number, and Direction does not appear to indicate that upstream and downstream are included.
2. Specific-Action AVP  2. Specific-Action AVP
Specific-Action AVP是现有的 AVP, 不过不再直接用于 AF请求 PCRF检 测上报事件,也不直接用于 PCRF向 AF上报事件,只用于定义各种事件类型, 在原有取值基础上定义一个新的枚举值: ALL, 表示通配所有事件类型, ALL 只能用于 AF发送给 PCRF的消息中。  The specific-action AVP is an existing AVP. However, it is not used directly for the AF request to detect the reported event. It is not directly used by the PCRF to report events to the AF. It is only used to define various event types and is defined on the basis of the original value. A new enumeration value: ALL, which means that all event types are wildcarded, and ALL can only be used in messages sent by the AF to the PCRF.
3. IP-Flows-Specific-Action AVP  3. IP-Flows-Specific-Action AVP
IP-Flows-Specific-Action: := < AVP Header: x >  IP-Flows-Specific-Action: := < AVP Header: x >
* { Specific-Action }  * { Specific-Action }
*[ IP-Flows ]  *[ IP-Flows ]
IP-Flows-Specific-Action AVP是新定义的 AVP, 将事件和 IP流绑定在一 起, IP-Flows不出现表示事件是针对整个 Diameter。  The IP-Flows-Specific-Action AVP is a newly defined AVP that binds events and IP flows together. IP-Flows does not appear to indicate that the event is for the entire Diameter.
4. Operation- Type AVP  4. Operation-Type AVP
IP-Flows-Specific-Action AVP是新定义的 AVP, 枚举类型, 取值为 ADD ( 0, 增加;)、 REMOVE ( 1 , 删除;)、 UPDATE ( 2, 更新;), 用于 AF指示 PCRF 对 IP-Flows-Specific-Action的操作方式。 其中 ADD可用于增加新的事件类型 或者增大已经请求上报的事件的检测范围, REMOVE用于删除已经请求上报 的事件类型或者减小已经请求上报的事件的检测范围, UPDATE 用于删除原 来所有请求上报的事件, 用新消息中的事件替换。  IP-Flows-Specific-Action AVP is a newly defined AVP, enumerated type, with values of ADD (0, increase;), REMOVE (1, delete;), UPDATE (2, update;), for AF indication PCRF How to operate IP-Flows-Specific-Action. ADD can be used to add a new event type or increase the detection range of the event that has been requested to be reported. REMOVE is used to delete the event type that has been requested to be reported or to reduce the detection range of the event that has been requested to be reported. UPDATE is used to delete all the original requests. The escalated event is replaced with the event in the new message.
5. IP-Flows-Specific-Action-Operation AVP  5. IP-Flows-Specific-Action-Operation AVP
IP-Flows-Specific- Action-Operation: := < AVP Header: x >  IP-Flows-Specific- Action-Operation: := < AVP Header: x >
{ Operation-Type }  { Operation-Type }
*[ IP-Flows- Specific- Action }  *[ IP-Flows- Specific- Action }
IP-Flows-Specific- Action-Operation AVP 是新定义的 AVP, 用于 AF 向 PCRF增加、 删除、 更新上报检测事件。 IP-Flows-Specific-Action-Operation AVP is a newly defined AVP for AF direction The PCRF adds, deletes, and updates the reported detection event.
AF请求上报 PCRF检测上报事件时,只需在发送给 PCRF的请求消息(如 AAR ) 或 者 应 答 消 息 ( 如 RAA ) 中 包含一 个 或 者 多 个 IP-Flows-Specific-Action-Operation AVP ,多个检测范围相同的事件可以包含在 同一个 IP-Flows-Specific-Action-Operation AVP中。 如果某个或者某些事件的 检测范围是整个 Diameter会话, 则对应的 IP-Flows- Specific-Action AVP不包 含 IP-Flows AVP,否则对应的 IP-Flows-Specific-Action AVP可以包含一个或者 多个 IP-Flows AVP以指示事件检测范围 (媒体流、 媒体子流和 IP流的任意组 合)。 AF釆用不同的 Operation-Type可以灵活地增加、 删除、 修改、 更新上报 事件。  When the AF request is reported to the PCRF to detect the reported event, only one or more IP-Flows-Specific-Action-Operation AVPs are included in the request message (such as AAR) or response message (such as RAA) sent to the PCRF, and multiple detection ranges are included. The same event can be included in the same IP-Flows-Specific-Action-Operation AVP. If the detection range of one or some events is the entire Diameter session, the corresponding IP-Flows-Specific-Action AVP does not include the IP-Flows AVP, otherwise the corresponding IP-Flows-Specific-Action AVP may contain one or more. IP-Flows AVP to indicate the event detection range (any combination of media stream, media substream, and IP stream). AF uses different Operation-Types to flexibly add, delete, modify, and update reported events.
PCRF向 AF上报事件时, 只需在发送给 AF的请求消息(如 RAR )或者 应答消息 (如 AAA ) 中包含一个或者多个 IP-Flows-Specific-Action AVP就可 以灵活地向 AF 上报事件, 多个影响范围相同的事件可以包含在同一个 IP-Flows-Specific-Action-Operation AVP中。 如果某个或者某些事件的影响范 围是整个 Diameter 会话, 则对应的 IP-Flows- Specific-Action AVP 不包含 IP-Flows AVP , 否则对应的 IP-Flows-Specific-Action AVP可以包含一个或者多 个 IP-Flows AVP以指示事件的影响范围(媒体流、 媒体子流和 IP流的任意组 合)。  When the PCRF reports an event to the AF, it can flexibly report the event to the AF by including one or more IP-Flows-Specific-Action AVPs in the request message (such as RAR) or the response message (such as AAA) sent to the AF. Multiple events with the same range of influences can be included in the same IP-Flows-Specific-Action-Operation AVP. If the impact scope of one or some events is the entire Diameter session, the corresponding IP-Flows-Specific-Action AVP does not include the IP-Flows AVP, otherwise the corresponding IP-Flows-Specific-Action AVP may contain one or more. IP-Flows AVP to indicate the scope of impact of the event (any combination of media stream, media substream, and IP stream).
这种方案对现有机制改动较大, 好处是十分灵活方便,  This kind of scheme has a large change to the existing mechanism, and the advantage is that it is very flexible and convenient.
方式二:  Method 2:
首先对现有的 AVP进行扩展 (包括定义几个新的 AVP和为现有的 AVP 定义新的值):  First extend the existing AVP (including defining several new AVPs and defining new values for existing AVPs):
1. Flows AVP  Flows AVP
Flows: := < AVP Header: x >  Flows: := < AVP Header: x >
{ Media-Component-Number }  { Media-Component-Number }
*[ Flow-Number ] [ Direction ] *[ Flow-Number ] [ Direction ]
Flows AVP是现有的 AVP, 在原来的基础上增加了 Direction AVP, 以便 可以定位到一个 IP流。 Direction为枚举类型,取值可以为 UPLINK( 0,上行 )、 DOWNLINK ( 1 , 下行)、 BOTH ( 2, 双向)。 Flow-Number不出现表示针对 Media-Component-Number对应的媒体流中的所有媒体子流, Direction不出现 表示包含上行流和下行流。  Flows AVP is an existing AVP that adds Direction AVP to the original so that it can locate an IP stream. Direction is an enumerated type, which can be UPLINK (0, Up), DOWNLINK (1, Down), BOTH (2, Bidirectional). Flow-Number does not appear to indicate all media substreams in the media stream corresponding to Media-Component-Number, and Direction does not appear to indicate that upstream and downstream are included.
2. Specific-Action AVP  2. Specific-Action AVP
Specific-Action AVP是现有的 AVP, 仍可用于 AF向 PCRF请求上报事件 以及 PCRF 向 AF 上报事件, 定义两个新的枚举值: DETECT— ALL 和 REMOVE— ALL,其中 DETECT— ALL表示 AF请求 PCRF检测上报所有事件, REMOVE— ALL表示 AF请求 PCRF取消检测上报所有事件,这两个新定义的 值都只能用于 AF发送给 PCRF的消息中。  The Specific-Action AVP is an existing AVP. It can still be used by the AF to report events to the PCRF and the PCRF to report events to the AF. Two new enumeration values are defined: DETECT—ALL and REMOVE—ALL, where DETECT—ALL indicates the AF request. The PCRF detects all events, and REMOVE_ALL indicates that the AF request PCRF cancels the detection and reports all events. The two newly defined values can only be used in the message sent by the AF to the PCRF.
AF请求上报 PCRF检测上报事件时,只需在发送给 PCRF的请求消息(如 AAR )或者应答消息 (如 RAA ) 中包含一个或者多个 Specific- Action AVP, 事件检测范围是整个 Diameter会话时 Diameter消息中不携带 Flows AVP , 否 则可以携带一个或者多个 Flows AVP以指示影响范围 (媒体流、 媒体子流和 IP流的任意组合)。 新下发的 Specific-Action AVP在原有基础上叠加, 需要删 除某个或者某些事件上报时, 可以在消息中包含多个 Specific-Action AVP, 其 中第一个的值为 REMOVE— ALL , 取消之前请求上报的事件, 后续的 Specific-Action指示需要保留的上报事件。 需要全部取消时, 只需在 Diameter 消息中携带一个 Specific- Action AVP , 值为 REMOVE— ALL。  When the AF request is reported to the PCRF to detect the reported event, only one or more Specific-Action AVPs are included in the request message (such as AAR) or response message (such as RAA) sent to the PCRF, and the event detection range is the Diameter message in the entire Diameter session. The Flow AVP is not carried in the flow, otherwise one or more Flows AVPs may be carried to indicate the scope of influence (any combination of media stream, media substream and IP stream). The newly issued Specific-Action AVP is superimposed on the original basis. When you need to delete one or some events, you can include multiple Specific-Action AVPs in the message. The first value is REMOVE-ALL. The event that is requested to be reported, and the subsequent Specific-Action indicates the reported event that needs to be retained. When you need to cancel all, you only need to carry a Specific-Action AVP in the Diameter message with the value REMOVE_ALL.
PCRF向 AF上报事件时, 只需在发送给 AF的请求消息(如 RAR )或者 应答消息 (如 AAA ) 中包含一个或者多个 Specific- Action AVP, 事件影响范 围是整个 Diameter会话时消息中不携带 Flows AVP, 否则可以携带一个或者 多个 Flows AVP以指示影响范围 (媒体流、 媒体子流和 IP流的任意组合)。  When the PCRF reports an event to the AF, it only needs to include one or more Specific-Action AVPs in the request message (such as RAR) or response message (such as AAA) sent to the AF. The event impact range is not carried in the message when the entire Diameter session is used. Flows AVP, otherwise one or more Flows AVPs can be carried to indicate the scope of influence (any combination of media stream, media substream and IP stream).
这种方案的优点是对现有机制改动较小。 方式三: The advantage of this approach is that it has minor changes to existing mechanisms. Method three:
首先对现有的 AVP进行扩展 (包括定义几个新的 AVP和为现有的 AVP 定义新的值):  First extend the existing AVP (including defining several new AVPs and defining new values for existing AVPs):
1. Flows AVP  Flows AVP
Flows: := < AVP Header: x >  Flows: := < AVP Header: x >
{ Media-Component-Number }  { Media-Component-Number }
*[ Flow-Number ]  *[ Flow-Number ]
[ Direction ]  [ Direction ]
Flows AVP是现有的 AVP, 在原来的基础上增加了 Direction AVP, 以便 可以定位到一个 IP流。 Direction为枚举类型,取值可以为 UPLINK( 0,上行 )、 DOWNLINK ( 1 , 下行)、 BOTH ( 2, 双向)。 Flow-Number不出现表示针对 Media-Component-Number对应的媒体流中的所有媒体子流, Direction不出现 表示包含上行流和下行流。  Flows AVP is an existing AVP that adds Direction AVP to the original so that it can locate an IP stream. Direction is an enumerated type, which can be UPLINK (0, Up), DOWNLINK (1, Down), BOTH (2, Bidirectional). Flow-Number does not appear to indicate all media substreams in the media stream corresponding to Media-Component-Number, and Direction does not appear to indicate that upstream and downstream are included.
2. Specific-Action AVP  2. Specific-Action AVP
Specific-Action AVP是现有的 AVP, 仍可用于 AF向 PCRF请求上报事件 以及 PCRF 向 AF 上报事件, 定义两个新的枚举值: DETECT— ALL 和 REMOVE— ALL,其中 DETECT— ALL表示 AF请求 PCRF检测上报所有事件, REMOVE— ALL表示 AF请求 PCRF取消检测上报所有事件,这两个新定义的 值都只能用于 AF发送给 PCRF的消息中。  The Specific-Action AVP is an existing AVP. It can still be used by the AF to report events to the PCRF and the PCRF to report events to the AF. Two new enumeration values are defined: DETECT—ALL and REMOVE—ALL, where DETECT—ALL indicates the AF request. The PCRF detects all events, and REMOVE_ALL indicates that the AF request PCRF cancels the detection and reports all events. The two newly defined values can only be used in the message sent by the AF to the PCRF.
3. Media-Component-Description AVP  3. Media-Component-Description AVP
Media-Component-Description AVP 是现有 的 AVP , 增力口参数 Specific-Action AVP, 用于 AF向 PCRF请求检测上报事件时指示检测范围是 媒体流的事件。  The Media-Component-Description AVP is an existing AVP, and the Specific-Action AVP is used to indicate that the detection range is the media stream when the AF requests the PCRF to report the reported event.
4. Media-Sub-Component AVP  4. Media-Sub-Component AVP
Media-Sub-Component AVP是现有的 AVP,增加参数 Specific- Action AVP , 用于 AF向 PCRF请求检测上报事件时指示检测范围是媒体子流的事件。  The Media-Sub-Component AVP is an existing AVP, and the parameter Specific-Action AVP is used to indicate that the detection range is a media sub-flow when the AF requests the PCRF to detect the reported event.
方式三中, AF向 PCRF请求检测上报事件时, 可以在同一个 Diameter消 息中通过在 Media-Component-Description AVP 和 /或 Media-Sub-Component AVP中包含不同的 Specific-Action AVP请求 PCRF上报检测范围不同的事件, 其他方面和方式二相同。 In mode 3, when the AF requests the PCRF to detect the reported event, it can be in the same Diameter. In the information, the PCRF is used to report different events with different detection scopes by including different Specific-Action AVPs in the Media-Component-Description AVP and/or the Media-Sub-Component AVP, and the other aspects are the same as the second method.
方式四:  Method 4:
首先对现有的 AVP进行扩展 (包括定义几个新的 AVP和为现有的 AVP 定义新的值):  First extend the existing AVP (including defining several new AVPs and defining new values for existing AVPs):
1. Flows AVP  Flows AVP
Flows: := < AVP Header: x >  Flows: := < AVP Header: x >
{ Media-Component-Number }  { Media-Component-Number }
*[ Flow-Number ]  *[ Flow-Number ]
[ Direction ]  [ Direction ]
Flows AVP是现有的 AVP, 在原来的基础上增加了 Direction AVP, 以便 可以定位到一个 IP流。 Direction为枚举类型,取值可以为 UPLINK( 0,上行 )、 DOWNLINK ( 1 , 下行)、 BOTH ( 2, 双向)。 Flow-Number不出现表示针对 Media-Component-Number对应的媒体流中的所有媒体子流, Direction不出现 表示包含上行流和下行流。  Flows AVP is an existing AVP that adds Direction AVP to the original so that it can locate an IP stream. Direction is an enumerated type, which can be UPLINK (0, Up), DOWNLINK (1, Down), BOTH (2, Bidirectional). Flow-Number does not appear to indicate all media substreams in the media stream corresponding to Media-Component-Number, and Direction does not appear to indicate that upstream and downstream are included.
2. Specific-Action AVP  2. Specific-Action AVP
Specific-Action AVP是现有的 AVP, 不过不再直接用于 AF请求 PCRF上 报事件, 也不直接用于 PCRF向 AF上报事件, 只用于定义各种事件类型。 定 义两个新的枚举值: DETECT— ALL和 REMOVE— ALL, 其中 DETECT— ALL 表示 AF请求 PCRF检测上报所有事件, REMOVE— ALL表示 AF请求 PCRF 取消检测上报所有事件,这两个新定义的值都只能用于 AF发送给 PCRF的消 息中。  The Specific-Action AVP is an existing AVP. However, it is not used directly for the AF request PCRF report event. It is not directly used by the PCRF to report events to the AF. It is only used to define various event types. Define two new enumeration values: DETECT—ALL and REMOVE—ALL, where DETECT—ALL indicates that the AF request PCRF detection reports all events, and REMOVE—ALL indicates that the AF request PCRF cancels detection and reports all events, these two newly defined values. Both can only be used in messages sent by the AF to the PCRF.
3. IP-Flows-Specific-Action AVP  3. IP-Flows-Specific-Action AVP
IP-Flows-Specific-Action: := < AVP Header: x >  IP-Flows-Specific-Action: := < AVP Header: x >
* { Specific-Action }  * { Specific-Action }
*[ IP-Flows ] IP-Flows-Specific-Action AVP是新定义的 AVP, 将事件和 IP流绑定在一 起, IP-Flows不出现表示事件是针对整个 Diameter。 *[ IP-Flows ] The IP-Flows-Specific-Action AVP is a newly defined AVP that binds events and IP flows together. IP-Flows does not appear to indicate that the event is for the entire Diameter.
AF请求上报 PCRF检测上报事件时,只需在发送给 PCRF的请求消息(如 AAR )或者应答消息(如 RAA )中包含一个或者多个 IP-Flows-Specific-Action AVP , 如果其中某个事件的检测范围是整个 Diameter 会话, 则对应的 IP-Flows-Specific-Action AVP 不 包含 Flows AVP , 否 则 对应 的 IP-Flows-Specific-Action AVP可以包含一个或者多个 Flows AVP以指示事件检 测范围(媒体流、媒体子流和 IP流的任意组合)。新下发的 Specific-Action AVP 在原有基础上叠加, 需要删除某个或者某些事件上报时, 可以在消息中包含 多个 IP-Flows-Specific-Action AVP, 其中第一个 IP-Flows-Specific-Action 中 Specific-Action 的值为 REMOVE— ALL, 取消之前请求上报的事件, 后续的 IP-Flows-Specific-Action指示需要保留的事件上报。 需要全部取消时, 只需在 Diameter消息中携带一个 IP-Flows- Specific-Action AVP , 其 Specific-Action的 值为 REMOVE— ALL。  When the AF request is reported to the PCRF to detect the reported event, only one or more IP-Flows-Specific-Action AVPs are included in the request message (such as AAR) or response message (such as RAA) sent to the PCRF, if one of the events The detection range is the entire Diameter session, and the corresponding IP-Flows-Specific-Action AVP does not include the Flows AVP. Otherwise, the corresponding IP-Flows-Specific-Action AVP may include one or more Flows AVPs to indicate the event detection range (media stream). , any combination of media substream and IP stream). The newly-issued Specific-Action AVP is superimposed on the original basis. When you need to delete one or some events, you can include multiple IP-Flows-Specific-Action AVPs in the message, the first IP-Flows-Specific The value of the Specific-Action in the -Action is REMOVE_ALL, the event that was requested to be reported is canceled, and the subsequent IP-Flows-Specific-Action indicates that the event needs to be reported. To cancel all the packets, you need to carry an IP-Flows-Specific-Action AVP in the Diameter message with the value of Specific-Action being REMOVE-ALL.
PCRF向 AF上报事件时 , 只需在发送给 AF的请求消息(如 RAA )或者 应答消息 (如 AAA ) 中包含一个或者多个 IP-Flows-Specific-Action AVP就可 以灵活地向 AF上报事件, 如果其中某个事件的影响范围是整个 Diameter会 话, 则对应的 IP-Flows- Specific-Action AVP不包含 Flows AVP, 否则对应的 IP-Flows-Specific-Action AVP可以包含一个或者多个 Flows AVP以指示事件的 影响范围 (媒体流、 媒体子流和 IP流的任意组合)。  When the PCRF reports an event to the AF, it can flexibly report the event to the AF by including one or more IP-Flows-Specific-Action AVPs in the request message (such as RAA) or the response message (such as AAA) sent to the AF. If the impact range of one of the events is the entire Diameter session, the corresponding IP-Flows-Specific-Action AVP does not include the Flows AVP, otherwise the corresponding IP-Flows-Specific-Action AVP may include one or more Flows AVPs to indicate The scope of the event (any combination of media stream, media substream, and IP stream).
图 6为根据本发明实施例的检测承载事件的***结构示意图。 如图 6所 示, 该***包括 AF 601 和 PCRF 602, 其中:  FIG. 6 is a schematic structural diagram of a system for detecting a bearer event according to an embodiment of the present invention. As shown in Figure 6, the system includes AF 601 and PCRF 602, where:
AF 601 , 用于向 PCRF 602发送承载事件检测请求, 所述承载事件检测请 求中包含事件检测类型范围以及对应于所述事件检测类型范围中每一事件类 型的事件检测范围;  The AF 601 is configured to send a bearer event detection request to the PCRF 602, where the bearer event detection request includes an event detection type range and an event detection range corresponding to each event type in the event detection type range;
PCRF 602,用于在每一事件类型的事件检测范围内检测该种类型的事件, 并向 AF 601返回所检测到事件的事件类型及该检测到事件的影响范围。 PCRF 602, which is used to detect this type of event within the event detection range of each event type. And returning to AF 601 the type of event of the detected event and the range of influence of the detected event.
其中, AF 601 ,可以进一步用于向 PCRF 602发送取消承载事件检测请求, 所述取消承载事件检测请求中包含取消检测事件类型范围以及对应于所述取 消检测事件类型范围中每一事件类型的取消事件检测范围;  The AF 601 may be further configured to send a cancel bearer event detection request to the PCRF 602, where the cancel bearer event detection request includes a cancel detection event type range and a cancellation corresponding to each event type in the cancel detection event type range. Range of event detection;
PCRF 602,进一步用于在每一取消检测事件类型的取消事件检测范围内, 取消检测该种类型的事件。  The PCRF 602 is further configured to cancel the detection of the event of the type within the cancellation event detection range of each cancellation detection event type.
AF 601 , 可以进一步用于向 PCRF 602发送增加承载事件检测请求, 所述 增加承载事件检测请求中包含增加检测事件类型范围以及对应于所述增加检 测事件类型范围中每一事件类型的事件检测范围;  The AF 601 may be further configured to send an increase bearer event detection request to the PCRF 602, where the increase bearer event detection request includes an increase detection event type range and an event detection range corresponding to each event type in the increase detection event type range. ;
PCRF 602,可以进一步用于在每一增加检测事件类型的事件检测范围内, 检测该种类型的事件, 并向 AF 601返回所检测到事件的事件类型及该检测到 事件的影响范围。  The PCRF 602 can be further configured to detect the event of the type within the event detection range of each of the increased detection event types, and return the type of the event of the detected event to the AF 601 and the range of influence of the detected event.
AF 601 , 可以进一步用于向 PCRF 602发送修改承载事件检测请求。 所述 修改承载事件检测请求中包含待修改的检测事件类型范围以及对应于所述待 修改检测事件类型范围中每一事件类型的待修改事件检测范围;  The AF 601 may be further configured to send a modified bearer event detection request to the PCRF 602. The modified bearer event detection request includes a detection event type range to be modified and an event detection range to be modified corresponding to each event type in the range of the detection event type to be modified;
PCRF 602, 进一步用于在每一待修改检测事件类型的待修改事件检测范 围内, 检测该种类型的事件, 并向 AF 601返回所检测到事件的事件类型及该 检测到事件的影响范围。  The PCRF 602 is further configured to detect the event of the type to be modified within the range of the event to be modified for each type of the detected event to be modified, and return the type of the event of the detected event to the AF 601 and the range of influence of the detected event.
AF 601 , 可以通过 AAR消息或者 RAA消息向 PCRF 602发送承载事件 检测请求。 PCRF 602, 可以通过 RAR消息或 AAA消息向 AF 601返回所检 测到事件的事件类型及该检测到事件的影响范围。 AF 601 , 还可以进一步用 于在收到检测到事件的事件类型及该检测到事件的影响范围后, 根据应用层 策略对事件进行处理。  The AF 601 can send a bearer event detection request to the PCRF 602 through an AAR message or a RAA message. The PCRF 602 can return the type of the event of the detected event and the range of influence of the detected event to the AF 601 through the RAR message or the AAA message. The AF 601 may be further configured to process the event according to an application layer policy after receiving the type of the event in which the event is detected and the scope of the detected event.
上述本发明实施例中, 在 AF与 PCRF之间的 Diame ter会话的整个生命周 期内, AF都可以请求 PCRF检测上报事件, 可以请求增加、 删除、 修改上报事 件, 可以在 AF 发送给 PCRF 的请求消息, 例如鉴权授权请求消息 ( Auth-Author iza t ion-Reques t , AAR ) 中指示, 也可以在 AF应答 PCRF的 响应消息, 例如重新鉴权 4受权应答消息 ( Re-Auth-Answer , RAA ) 中指示, 因此实际操作起来更加灵活。 In the foregoing embodiment of the present invention, during the entire life cycle of the Diame ter session between the AF and the PCRF, the AF may request the PCRF to detect the reported event, and may request to add, delete, and modify the reported event, and may send the request to the PCRF in the AF. Message, such as an authentication authorization request message The indication in (Auth-Author iza t ion-Reques t , AAR ) can also be indicated in the response message of the AF response PCRF, such as Re-Auth-Answer (RAA), so the actual operation More flexible.
图 Ί为根据本发明实施例的 AF结构示意图。  Figure Ί is a schematic diagram of an AF structure in accordance with an embodiment of the present invention.
如图 7所示,该 AF包括承载事件检测请求发送单元 701和事件处理单元 702, 其中:  As shown in FIG. 7, the AF includes a bearer event detection request transmitting unit 701 and an event processing unit 702, where:
承载事件检测请求发送单元 701 , 用于向 PCRF发送承载事件检测请求, 所述承载事件检测请求中包含事件检测类型范围以及对应于所述事件检测类 型范围中每一事件类型的事件检测范围。  The bearer event detection request sending unit 701 is configured to send a bearer event detection request to the PCRF, where the bearer event detection request includes an event detection type range and an event detection range corresponding to each event type in the event detection type range.
事件处理单元 702,用于在收到由 PCRF所检测到事件的事件类型及该检 测到事件的影响范围后, 根据应用层策略对事件进行处理。  The event processing unit 702 is configured to process the event according to an application layer policy after receiving the event type of the event detected by the PCRF and the affected range of the detected event.
图 8为根据本发明实施例的 PCRF结构示意图。  FIG. 8 is a schematic diagram showing the structure of a PCRF according to an embodiment of the present invention.
如图 8所示, 该 PCRF包括事件检测单元 801和检测结果返回单元 802。 事件检测单元 801 , 用于接收由 AF发送的承载事件检测请求, 并在每一 事件类型的事件检测范围内检测该种类型的事件, 其中所述承载事件检测请 求中包含事件检测类型范围以及对应于所述事件检测类型范围中每一事件类 型的事件检测范围。  As shown in FIG. 8, the PCRF includes an event detecting unit 801 and a detection result returning unit 802. The event detecting unit 801 is configured to receive a bearer event detection request sent by the AF, and detect the event of the type in the event detection range of each event type, where the bearer event detection request includes an event detection type range and corresponding An event detection range for each event type in the range of event detection types.
检测结果返回单元 802 , 用于向 AF返回所检测到事件的事件类型及该检 测到事件的影响范围。  The detection result return unit 802 is configured to return the type of the event of the detected event to the AF and the influence range of the detected event.
综上所述, 本发明实施例首先提供一种 AF检测承载事件的方法。  In summary, the embodiment of the present invention first provides a method for detecting a bearer event by using an AF.
在这种 AF检测承载事件的方法中, AF请求 PCRF检测上报事件时, 指 明检测的事件类型和检测范围, 检测范围可以是整个 Diameter会话或者媒体 流、 媒体子流和 IP流的任意组合, 不同事件的检测范围可以相同或者不同, 其中事件类型可以釆用通配的方式一次请求检测上报所有事件类型, 也可以 请求检测上报某个或者某些事件; PCRF再根据 AF的请求, 和 PCEF配合在 AF指定的范围内检测 AF指定的事件。检测到相应事件后, PCRF向 AF上报 事件类型和影响范围, 影响范围可以是整个 Diameter会话或者媒体流、 媒体 子流和 IP流的任意组合, 其中 PCRF上报时指示的事件影响范围必须在 AF 请求时指明的检测范围之内, AF指定的检测范围之外发生的事件不上报, AF 没有指定的事件类型也不上报。 In the method of detecting the bearer event by the AF, the AF request PCRF detects the reported event type and the detection range, and the detection range may be any combination of the entire Diameter session or the media stream, the media substream, and the IP stream, and different The detection range of the event may be the same or different. The event type may request to detect and report all event types in a wildcard manner, or may request to detect and report one or some events; the PCRF cooperates with the PCEF according to the AF request. The AF specified event is detected within the range specified by the AF. After detecting the corresponding event, the PCRF reports to the AF The event type and the scope of the impact may be any combination of the entire Diameter session or the media stream, the media substream, and the IP stream. The event impact range indicated by the PCRF reporting must be within the detection range specified by the AF request, and the AF designation. Events that occur outside of the detection range are not reported, and AF does not specify the type of event and does not report it.
PCRF可以一次上报多个事件, 这些事件的影响范围可以相同或者不同。  The PCRF can report multiple events at once, and the impact range of these events can be the same or different.
AF还可以根据应用层的策略和上报的事件, 釆取相应的措施(比如拆除 业务、 通过信令修改业务等)。  The AF can also take corresponding measures according to the policies of the application layer and the reported events (such as tearing down services, modifying services through signaling, etc.).
AF请求 PCRF检测上报事件之后, 可以请求 PCRF取消上报承载事件, 指明取消检测的事件类型和检测范围, 检测范围可以是整个 Diameter会话或 者媒体流、 媒体子流和 IP流的任意组合。 其中事件类型可以釆用通配的方式 一次取消检测上报所有事件类型, 也可以取消检测上报某个或者某些事件。  AF Request After the PCRF detects the reported event, the PCRF can be requested to cancel the report bearer event, indicating the type of the event to be canceled and the detection range. The detection range can be any combination of the entire Diameter session or media stream, media substream and IP stream. The event type can be used in the wildcard mode to cancel the detection and report all event types, or cancel the detection to report some or some events.
AF取消上报事件时的检测范围可以比之前请求上报事件时指示的检测范围更 大(比如请求在某个媒体流上上报某个事件后, 请求在整个会话上取消上报 该事件, 在该媒体流上当然也取消了)、 更小(比如请求在整个 Diameter会话 上报某个事件后, 请求在某个媒体流上取消上报该事件, 表示在其他媒体流 上继续检测上报该事件), 也可以相等。 The detection range when the AF cancels the reporting event may be larger than the detection range indicated when the previous requesting the reporting event (for example, after requesting an event to be reported on a certain media stream, requesting to cancel the reporting event on the entire session, in the media stream) Of course, it is also canceled.) (For example, after requesting an event to be reported on the entire Diameter session, requesting to cancel the event on a media stream, indicating that the event is continuously detected on other media streams) may also be equal. .
AF请求 PCRF检测上报事件之后 , 可以请求 PCRF增加检测上报承载事 件,对于已经请求 PCRF检测上报的事件 AF可以请求修改检测承载事件的范 围 (增大、 缩小)。  AF Request After the PCRF detects the reported event, the PCRF can be requested to increase the detection and reporting of the bearer event. For the event AF that has been requested to be reported by the PCRF, the AF can request to modify the range of detecting the bearer event (increase or decrease).
AF请求 PCRF检测上报事件之后 , 可以请求 PCRF更新检测上报的事件 类型和检测范围, 即直接用新消息中携带的上报事件类型和检测范围替换之 前的请求。  AF request After the PCRF detects the reported event, it can request the PCRF to update and detect the reported event type and detection range, that is, directly replace the request with the reported event type and detection range carried in the new message.
在 AF与 PCRF之间的 Diameter会话的整个生命周期内, AF都可以请求 PCRF上报事件, 也可以请求增加、 取消、 修改上报事件, 可以在 AF发送给 PCRF的请求消息(比如 AAR )中指示, 也可以在 AF应答 PCRF的响应消息 (比如 RAA ) 中指示。 PCRF向 AF上报事件时,可以在 PCRF发送给 AF的请求消息(比如 RAR ) 中指示, 也可以在 PCRF应答 AF的响应消息 (比如 AAA ) 中指示。 During the entire life cycle of the Diameter session between the AF and the PCRF, the AF may request the PCRF to report the event, or may request to add, cancel, or modify the reported event, which may be indicated in the request message (such as AAR) sent by the AF to the PCRF. It can also be indicated in the response message (such as RAA) of the AF response PCRF. When the PCRF reports an event to the AF, it may be indicated in a request message (such as RAR) sent by the PCRF to the AF, or may be indicated in a response message (such as AAA) of the PCRF response AF.
通过本发明实施例的方法, AF可以随时请求 PCRF上报某些事件, 也可 以取消检测上报某些事件、 增加检测上报其他事件、 或者修改事件的检测范 围。 事件的检测粒度可以是整个 Diameter会话或者媒体流、 媒体子流和 IP流 的任意组合。 从而解决了现有机制事件检测粒度过大(只能是整个 Diameter 会话)导致的不必要的消息交互、 事件影响范围指示不明确 (最小只能到媒 体子流, 不能指示 IP流) 的问题, 同时也解决了现有的事件检测上报机制使 用不灵活的问题(只能在 AF发送给 PCRF的第一个请求消息中指定, 后续不 能修改)。  With the method of the embodiment of the present invention, the AF may request the PCRF to report certain events at any time, and may also cancel the detection of reporting certain events, increasing the detection of other events, or modifying the detection range of the event. The granularity of detection of an event can be any combination of the entire Diameter session or media stream, media substream, and IP stream. Therefore, the problem that the existing mechanism event detection granularity is too large (only the entire Diameter session) is unnecessary, the event influence range indication is ambiguous (the minimum can only reach the media substream, and the IP flow cannot be indicated) is solved. At the same time, it also solves the problem that the existing event detection reporting mechanism is inflexible (can only be specified in the first request message sent by the AF to the PCRF, and cannot be modified later).
同时本发明实施中描述的机制也可以用于信令路径状态检测, 为避免和 媒体¾¾0 Media-Component-Number中突,信令¾¾0 Media-Component-Number 可以为 0或者特殊的数字 (比 ¾口 OxFFFFFFFF ), Flow-Number AVP由 AF指 定(可以根据端口号等的大小排序), 信令流也可以由 Flow-Description AVP 描述, 这样信令流的事件检测上报和媒体流的事件检测上报一致, 不需要为 信令路径状态检测建立新的 Diameter会话。  At the same time, the mechanism described in the implementation of the present invention can also be used for signaling path state detection. To avoid media and component-number, the signaling-Media-Component-Number can be 0 or a special number (a ratio of 3⁄4 ports). OxFFFFFFFF), the flow-number AVP is specified by the AF (which can be sorted according to the size of the port number, etc.), and the signaling flow can also be described by the Flow-Description AVP, so that the event detection report of the signaling flow is consistent with the event detection report of the media stream. There is no need to establish a new Diameter session for signaling path state detection.
以上所述, 仅为本发明的较佳实施例而已, 并非用于限定本发明的保护 范围。 凡在本发明的精神和原则之内, 所作的任何修改、 等同替换、 改进等, 均应包含在本发明的保护范围之内。  The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

权利 要 求 书 Claim
1、 一种检测承载事件的方法, 其特征在于, 该方法包括: A method for detecting a bearer event, the method comprising:
策略控制和计费规则功能实体接收到应用层功能实体发送的承载事件检测 请求, 所述承载事件检测请求中包含事件检测类型范围以及对应于所述事件检 测类型范围中每一事件类型的事件检测范围;  The policy control and charging rule function entity receives the bearer event detection request sent by the application layer function entity, where the bearer event detection request includes an event detection type range and event detection corresponding to each event type in the event detection type range. Scope
策略控制和计费规则功能实体在每一事件类型的事件检测范围内检测该种 类型的事件, 并向应用层功能实体返回所检测到事件的事件类型及该检测到事 件的影响范围。  The policy control and charging rule function entity detects the type of event within the event detection range of each event type, and returns the event type of the detected event and the affected range of the detected event to the application layer function entity.
2、 根据权利要求 1所述的检测承载事件的方法, 其特征在于, 所述事件检 测范围为整个 Diameter会话, 或者媒体流、 媒体子流和 IP流的任意组合。  2. The method for detecting a bearer event according to claim 1, wherein the event detection range is an entire Diameter session, or any combination of a media stream, a media substream, and an IP stream.
3、 根据权利要求 1所述的检测承载事件的方法, 其特征在于, 所述影响范 围为整个 Diameter会话 , 或者媒体流、 媒体子流和 IP流的任意组合。  The method for detecting a bearer event according to claim 1, wherein the impact range is an entire Diameter session, or any combination of a media stream, a media substream, and an IP stream.
4、 根据权利要求 1所述的检测承载事件的方法, 其特征在于, 所述事件检 测类型范围包括所有事件类型, 或者包括至少一个特定的事件类型。  The method for detecting a bearer event according to claim 1, wherein the event detection type range includes all event types or at least one specific event type.
5、 根据权利要求 1所述的检测承载事件的方法, 其特征在于, 该方法进一 步包括:  5. The method of detecting a bearer event according to claim 1, wherein the method further comprises:
策略控制和计费规则功能实体接收到应用层功能实体发送的取消承载事件 检测请求, 所述取消承载事件检测请求中包含取消检测事件类型范围以及对应 于所述取消检测事件类型范围中每一事件类型的事件检测范围;  The policy control and charging rule function entity receives the cancel bearer event detection request sent by the application layer function entity, where the cancel bearer event detection request includes a cancel detection event type range and each event in the range of the cancel detection event type Type of event detection range;
策略控制和计费规则功能实体在每一取消检测事件类型的事件检测范围内, 取消检测该种类型的事件。  The policy control and charging rule function entity cancels detecting this type of event within the event detection range of each cancel detection event type.
6、 根据权利要求 1所述的检测承载事件的方法, 其特征在于, 该方法进一 步包括:  6. The method of detecting a bearer event according to claim 1, wherein the method further comprises:
策略控制和计费规则功能实体接收到应用层功能实体发送的增加承载事件 检测请求, 所述增加承载事件检测请求中包含增加检测事件类型范围以及对应 于所述增加检测事件类型范围中每一事件类型的事件检测范围; The policy control and charging rule function entity receives an increase bearer event detection request sent by the application layer function entity, where the increase bearer event detection request includes increasing the detection event type range and corresponding And increasing the event detection range of each event type in the range of detection event types;
策略控制和计费规则功能实体在每一增加检测事件类型的事件检测范围内, 检测该种类型的事件, 并向应用层功能实体返回所增加检测到事件的事件类型 及该增加检测到事件的影响范围。  The policy control and charging rule function entity detects the event of the type within the event detection range of each added detection event type, and returns the event type of the added detected event to the application layer function entity and the event that the detected event is added. Sphere of influence.
7、 根据权利要求 1所述的检测承载事件的方法, 其特征在于, 该方法进一 步包括:  7. The method of detecting a bearer event according to claim 1, wherein the method further comprises:
策略控制和计费规则功能实体接收到应用层功能实体发送的修改承载事件 检测请求, 所述修改承载事件检测请求中包含待修改的检测事件类型范围以及 对应于所述待修改检测事件类型范围中每一事件类型的待修改事件检测范围; 策略控制和计费规则功能实体在每一待修改检测事件类型的待修改事件检 测范围内, 检测该种类型的事件, 并向应用层功能实体返回所检测到事件的事 件类型及该检测到事件的影响范围。  The policy control and charging rule function entity receives the modified bearer event detection request sent by the application layer function entity, where the modified bearer event detection request includes the detection event type range to be modified and corresponds to the detection event type range to be modified. The event detection range to be modified for each event type; the policy control and charging rule function entity detects the event of the type to be modified within the to-be-modified event detection range of the type of the detection event to be modified, and returns to the application layer function entity The type of event in which the event was detected and the scope of the detected event.
8、 根据权利要求 1-7中任一项所述的检测承载事件的方法, 其特征在于, 所述事件检测范围为信令流,其中信令流的 Media-Component-Number为 0或者 特殊的数字, Flow-Number AVP 由应用层功能实体指定, 信令流由 Flow-Description AVP描述。  The method for detecting a bearer event according to any one of claims 1 to 7, wherein the event detection range is a signaling flow, wherein a Media-Component-Number of the signaling flow is 0 or a special The number, Flow-Number AVP is specified by the application layer functional entity, and the signaling flow is described by the Flow-Description AVP.
9、 根据权利要求 1所述的检测承载事件的方法, 其特征在于, 应用层功能 实体通过鉴权授权请求消息向策略控制和计费规则功能实体发送承载事件检测 请求, 或者应用层功能实体通过重新鉴权授权应答消息向策略控制和计费规则 功能实体发送承载事件检测请求。  The method for detecting a bearer event according to claim 1, wherein the application layer function entity sends a bearer event detection request to the policy control and charging rule function entity by using an authentication authorization request message, or the application layer function entity passes The re-authentication authorization response message sends a bearer event detection request to the policy control and charging rule function entity.
10、根据权利要求 1所述的检测承载事件的方法, 其特征在于, 策略控制和 计费规则功能实体通过重新鉴权授权请求消息向应用层功能实体返回所检测到 事件的事件类型及该检测到事件的影响范围, 或者策略控制和计费规则功能实 体通过鉴权授权请求消息向应用层功能实体返回所检测到事件的事件类型及该 检测到事件的影响范围。  The method for detecting a bearer event according to claim 1, wherein the policy control and charging rule function entity returns an event type of the detected event to the application layer function entity by using a re-authentication authorization request message and the detecting To the scope of the event, or the policy control and charging rule function entity returns the event type of the detected event and the affected range of the detected event to the application layer function entity through the authentication authorization request message.
11、根据权利要求 1所述的检测承载事件的方法, 其特征在于, 所述事件检 测类型范围中各事件检测类型的事件检测范围并不相同, 并且各检测到事件的 影响范围也并不相同; 或 The method for detecting a bearer event according to claim 1, wherein the event check The range of event detection for each event detection type in the measurement type range is not the same, and the range of influence of each detected event is not the same; or
所述事件检测类型范围中各事件检测类型的事件检测范围相同,并且各检测 到事件的影响范围也相同; 或  The event detection range of each event detection type in the event detection type range is the same, and the range of influence of each detected event is also the same; or
所述事件检测类型范围中各事件检测类型的事件检测范围并不相同,并且各 检测到事件的影响范围相同; 或  The event detection range of each event detection type in the event detection type range is not the same, and the range of influence of each detected event is the same; or
所述事件检测类型范围中各事件检测类型的事件检测范围相同,并且各检测 到事件的影响范围并不相同。  The event detection range of each event detection type in the event detection type range is the same, and the range of influence of each detected event is not the same.
12、 一种检测承载事件的***, 其特征在于, 该***包括应用层功能实体和 策略控制和计费规则功能实体, 其中:  12. A system for detecting bearer events, characterized in that the system comprises an application layer functional entity and a policy control and charging rule functional entity, wherein:
应用层功能实体,用于向策略控制和计费规则功能实体发送承载事件检测请 求, 所述承载事件检测请求中包含事件检测类型范围以及对应于所述事件检测 类型范围中每一事件类型的事件检测范围;  An application layer function entity, configured to send a bearer event detection request to the policy control and charging rule function entity, where the bearer event detection request includes an event detection type range and an event corresponding to each event type in the event detection type range examination range;
策略控制和计费规则功能实体,用于在每一事件类型的事件检测范围内检测 该种类型的事件, 并向应用层功能实体返回所检测到事件的事件类型及该检测 到事件的影响范围。  The policy control and charging rule function entity is configured to detect the event of the type within the event detection range of each event type, and return the event type of the detected event to the application layer function entity and the influence range of the detected event .
13、 根据权利要求 12所述的检测承载事件的***, 其特征在于, 应用层功能实体,进一步用于向策略控制和计费规则功能实体发送取消承载 事件检测请求, 所述取消承载事件检测请求中包含取消检测事件类型范围以及 对应于所述取消检测事件类型范围中每一事件类型的取消事件检测范围;  The system for detecting a bearer event according to claim 12, wherein the application layer function entity is further configured to send a cancel bearer event detection request to the policy control and charging rule function entity, and the cancel bearer event detection request Included in the cancellation detection event type range and the cancellation event detection range corresponding to each event type in the cancellation detection event type range;
策略控制和计费规则功能实体,进一步用于在每一取消检测事件类型的取消 事件检测范围内, 取消检测该种类型的事件。  The policy control and charging rule function entity is further configured to cancel detecting the type of event within the cancellation event detection range of each cancel detection event type.
14、 根据权利要求 12所述的检测承载事件的***, 其特征在于, 应用层功能实体,进一步用于向策略控制和计费规则功能实体发送增加承载 事件检测请求, 所述增加承载事件检测请求中包含增加检测事件类型范围以及 对应于所述增加检测事件类型范围中每一事件类型的事件检测范围; 策略控制和计费规则功能实体,进一步用于在每一增加检测事件类型的事件 检测范围内, 检测该种类型的事件, 并向应用层功能实体返回所增加检测到事 件的事件类型及该增加检测到事件的影响范围。 The system for detecting a bearer event according to claim 12, wherein the application layer function entity is further configured to send an increase bearer event detection request to the policy control and charging rule function entity, where the bearer event detection request is increased. The method includes increasing a range of detection event types and an event detection range corresponding to each event type in the range of the increased detection event types; The policy control and charging rule function entity is further configured to detect the event of the type within the event detection range of each additional detection event type, and return the event type of the added detected event to the application layer function entity and the increase The range of impact of the event was detected.
15、 根据权利要求 12所述的检测承载事件的***, 其特征在于  15. A system for detecting a bearer event according to claim 12, characterized in that
应用层功能实体,进一步用于向策略控制和计费规则功能实体发送修改承载 事件检测请求, 所述修改承载事件检测请求中包含待修改的检测事件类型范围 以及对应于所述待修改检测事件类型范围中每一事件类型的待修改事件检测范 围;  The application layer function entity is further configured to send a modify bearer event detection request to the policy control and charging rule function entity, where the modify bearer event detection request includes a detection event type range to be modified and a detection event type corresponding to the to-be-modified The range of event detection to be modified for each event type in the range;
策略控制和计费规则功能实体,进一步用于在每一待修改检测事件类型的待 修改事件检测范围内, 检测该种类型的事件, 并向应用层功能实体返回所检测 到事件的事件类型及该检测到事件的影响范围。  The policy control and charging rule function entity is further configured to detect the event of the type in the event detection range of the to-be-modified event of the type of the detection event to be modified, and return the event type of the detected event to the application layer function entity and The range of impact of the detected event.
16、 根据权利要求 12所述的检测承载事件的***, 其特征在于, 应用层功能实体,进一步用于在收到检测到事件的事件类型及该检测到事件 的影响范围后, 根据应用层策略对事件进行处理。  The system for detecting a bearer event according to claim 12, wherein the application layer function entity is further configured to: after receiving the event type of the detected event and the scope of the detected event, according to the application layer policy Process the event.
17、一种应用层功能实体, 其特征在于, 该应用层功能实体包括承载事件检 测请求发送单元和事件处理单元, 其中:  An application layer function entity, wherein the application layer function entity comprises a bearer event detection request sending unit and an event processing unit, wherein:
承载事件检测请求发送单元,用于向策略控制和计费规则功能实体发送承载 事件检测请求, 所述承载事件检测请求中包含事件检测类型范围以及对应于所 述事件检测类型范围中每一事件类型的事件检测范围;  a bearer event detection request sending unit, configured to send a bearer event detection request to the policy control and charging rule function entity, where the bearer event detection request includes an event detection type range and each event type corresponding to the event detection type range Range of event detection;
事件处理单元,用于在收到由策略控制和计费规则功能实体所检测到事件的 事件类型及该检测到事件的影响范围后, 根据应用层策略对事件进行处理。  The event processing unit is configured to process the event according to the application layer policy after receiving the event type of the event detected by the policy control and charging rule function entity and the scope of the detected event.
18、一种策略控制和计费规则功能实体, 其特征在于, 该策略控制和计费规 则功能实体包括事件检测单元和检测结果返回单元, 其中:  18. A policy control and charging rule function entity, wherein the policy control and charging rule function entity comprises an event detecting unit and a detecting result returning unit, wherein:
事件检测单元,用于接收由应用层功能实体发送的承载事件检测请求,并在 每一事件类型的事件检测范围内检测该种类型的事件, 其中所述承载事件检测 请求中包含事件检测类型范围以及对应于所述事件检测类型范围中每一事件类 型的事件检测范围; An event detecting unit, configured to receive a bearer event detection request sent by an application layer function entity, and detect the type of event in an event detection range of each event type, where the bearer event detection request includes an event detection type range And corresponding to each event class in the range of event detection types Type of event detection range;
检测结果返回单元, 用于向应用层功能实体返回所检测到事件的事件类型 及该检测到事件的影响范围。  The detection result returning unit is configured to return the type of the event of the detected event to the application layer function entity and the influence range of the detected event.
PCT/CN2008/070762 2007-04-26 2008-04-22 Method, system and device for examining a carrying event WO2008131674A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200710102006.X 2007-04-26
CN200710102006XA CN101296094B (en) 2007-04-26 2007-04-26 Method, system and device for detecting bearing event

Publications (1)

Publication Number Publication Date
WO2008131674A1 true WO2008131674A1 (en) 2008-11-06

Family

ID=39925205

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/070762 WO2008131674A1 (en) 2007-04-26 2008-04-22 Method, system and device for examining a carrying event

Country Status (2)

Country Link
CN (1) CN101296094B (en)
WO (1) WO2008131674A1 (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101453380B (en) * 2007-11-28 2011-08-24 华为技术有限公司 Method and system for application event detection and functional entity for packet stream optimization
CN107135184B (en) * 2016-02-26 2020-06-12 上海交通大学 Information interaction system in multimedia system and network transmission method
KR102153611B1 (en) * 2016-02-02 2020-09-08 상하이 지아오통 유니버시티 Multimedia system information exchange mechanism and network transmission method
CN107800544B (en) * 2016-08-30 2022-09-09 中兴通讯股份有限公司 User position information processing method and device

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005008496A1 (en) * 2003-07-11 2005-01-27 Alex Zakonov Dynamic discovery algorithm
CN1645806A (en) * 2004-08-11 2005-07-27 华为技术有限公司 Processing method based on packet data stream charging triggered event and re-authorized events
CN1874345A (en) * 2005-12-26 2006-12-06 华为技术有限公司 Method for statistical parameter values of terminal reported from media gateway

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005008496A1 (en) * 2003-07-11 2005-01-27 Alex Zakonov Dynamic discovery algorithm
CN1645806A (en) * 2004-08-11 2005-07-27 华为技术有限公司 Processing method based on packet data stream charging triggered event and re-authorized events
CN1874345A (en) * 2005-12-26 2006-12-06 华为技术有限公司 Method for statistical parameter values of terminal reported from media gateway

Also Published As

Publication number Publication date
CN101296094A (en) 2008-10-29
CN101296094B (en) 2011-02-16

Similar Documents

Publication Publication Date Title
CA2682979C (en) Method, system and entity of realizing event detection
US9503483B2 (en) Method and apparatuses for identifying and reporting quality of service rules applicable to a communication session
EP2339781B1 (en) Method and system for realizing the policy and charging control in the multiple packet data networks (pdn) scene
JP5298203B2 (en) Token-based correlation of control sessions for data session policy and charging control via NAT
US7957314B2 (en) System and method for provisioning charging and policy control in a network environment
CN101841797B (en) Charging method and system for terminal access through multiple access networks and reporting method
AU2006344794B2 (en) Loss of signalling bearer transport
RU2513711C2 (en) Service event trigger
US20100186064A1 (en) Method and device for obtaining capabilities of policy and charging enforcement function
US20070281699A1 (en) Inter-access handover with access specific policy control functions
KR101412683B1 (en) Method permitting the control of service quality and/or service fees of telecommunication services
US20160269905A1 (en) Handling of Authorization Requests For a Packet-Based Service in a Mobile Network
WO2012058998A1 (en) Policy and charging control method supporting ip flow mobility in roaming scenario
WO2011029289A1 (en) Method and system for transmitting a bearer control mode in roaming scenarios
WO2012103770A1 (en) Usage monitoring method and system supporting traffic detection function
WO2011079773A1 (en) Method, device and system for controlling user session policy
WO2006015548A1 (en) A processing method based on charging trigger event and re-authorisation event of packet data flow
WO2011063688A1 (en) Method and system for selecting policy and charging rules function entity
WO2011085621A1 (en) Method and system for service processing
US20170163819A1 (en) Method, Device, and System for Processing Policy Control
WO2011085614A1 (en) Method for controlling resources in full service converged network and system therefor
WO2009024056A1 (en) Method, system and device of expanding policy and charging control rule
WO2014135185A1 (en) User plane congestion control
WO2011088702A1 (en) Method and system for controlling resources in full-service convergence network
WO2008131674A1 (en) Method, system and device for examining a carrying event

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

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

Country of ref document: EP

Kind code of ref document: A1