CN101296094B

CN101296094B - Method, system and device for detecting bearing event

Info

Publication number: CN101296094B
Application number: CN200710102006XA
Authority: CN
Inventors: 谭仕勇; 李岩; 魏伟华; 黄世碧; 赵鹏; 毛玉欣
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2007-04-26
Filing date: 2007-04-26
Publication date: 2011-02-16
Anticipated expiration: 2027-04-26
Also published as: CN101296094A; WO2008131674A1

Abstract

The embodiment of the invention discloses a method for detecting a carrying event which comprises the steps as follows: an application layer functional entity (AF) transmits a detection application of the carrying event to a policy control and charge rule function entity (PCRF), and the detection application of the carrying event comprises the scopes of event detection types and the event detection scopes of each event type corresponding to the scopes of the event detection types, the PCRF detects the events of each type within the event detection scopes of each event type, and returns the event types and influencing scopes of the detected events to the AF. The invention also discloses a system and device for detecting the carrying events. The use of the invention solves the problem of unnecessary message exchanges caused by too large event detection granularity, reduces redundant message exchanges, and also solves the problem of the existing inflexible applications of the reporting system for the event detection; moreover, the method, system and device of the invention can be further applied to the status detection of signaling paths without establishing a separate Diameter conversation.

Description

Detect the mthods, systems and devices of bearing event

Technical field

The present invention relates to communication technical field, more particularly, the present invention relates to detect the mthods, systems and devices of bearing event.

Background technology

(Internet Protocol IP) in the process of evolution, for satisfied business is provided, needs to solve end-to-end quality of service (Quality Of Service, QoS) problem to the whole network border agreement at communication network.IP network can provide various business, and such as multimedia call, file download, web page browsing etc., wherein different business has different requirements to QoS (comprising bandwidth, time delay, packet loss etc.), and the requirement of charging aspect is also different.Such as: can adopt online charging or offline charging, can also be according to charge on traffic or according to time-based charging etc.

In order to solve relevant issues such as above-mentioned QoS and charging, third generation partner program (The ThirdGeneration Partnership Project, 3GPP) strategy and control (the Policy andCharging Control that charges have been defined, PCC) framework can satisfy different QoS control and charging demand by this framework.

Fig. 1 is the schematic diagram of PCC structure in the prior art, the wherein following description of each functional entity effect:

Policy control and charging regulation function entity (Policy Control and Charging RulesFunction, PCRF), mainly finish the strategy decision-making and based on stream functions such as charging control.The PCRF entity is according to the corresponding strategy of decisions such as carrier policy, user contracting data and the current ongoing business information of user, and offer this strategy tactful and charging execution entity (Policy and ChargingEnforcement Function, PCEF), carry out these strategies by PCEF.User contracting data can (Subscription Profile Repository SPR) obtains in the functional entity from the user contracting data database.Strategy comprise the detection rule of business data flow (finishing set of the IP stream of certain professional as voice communication), whether gate, QoS, based on the charging regulation that flows etc.

PCEF is mainly used in the execution of the detection of finishing business data flow, strategy, based on the functions such as charging of stream.This entity carries out that PCRF issues or the strategy of appointment, is exactly the detection and measurement, the QoS of assurance business data flow that carry out business data flow specifically, user's surface current amount is handled and trigger the session management etc. of chain of command.

SPR, this functional entity is used for providing user contracting data to PCRF.

Application level function entity (Application Function, AF), this functional entity is used for dynamically providing to PCRF the session information of application layer business, formulate corresponding strategy for PCRF, AF can obtain IP connectivity access network from PCRF, and (IP-Connectivity Access Network, IP-CAN) relevant information and IP-CAN carry relevant incident etc.

Interface between AF and the PCRF is the Rx reference point.This reference point is used for AF and issues the application layer relevant information, comprises the IP filter (as source IP address, purpose IP address, protocol type, source port number, destination slogan etc.), application or the required bandwidth information of medium that are used for the identification services data flow.PCRF also can provide the relevant information of IP-CAN, report bearing event etc. to AF by this reference point.This reference point is used (Internet Engineering Task Force, IETF) Ding Yi Diameter.

The Diameter serial protocols is that the Authentication Authorization of a new generation is replied (Auth-Authorization-Request, AAA) technology its objective is the aaa protocol that one of establishment can fully be satisfied at present and even the control of IP network (comprising NGN and 3G etc.) user capture from now on requires.Diameter is remote authentication dial-in user service (Remote Authentication Dial-InUser Service, RADIUS) upgrading of agreement, comprise basic agreement, transportation protocol and at the Extended Protocol (will be called application at the expansion of different application scene among the Diameter, be exactly that two different Diameter use such as Rx, Gx reference point in the PCC framework) of different application scene.The shared basic function of various application realizes in basic agreement, and the specific function definition in each is used of different application scene.

Different with the agreement (as RADIUS) of traditional customer end/server mode, Diameter client and Diameter server can initiatively send a request message to the opposite end.Diameter client and Diameter server carry out a series of information exchange, and such one from being initiated to a series of information interactions of termination, be called a Diameter session.The foundation of Diameter session generally is to be initiated by client.The end of Diameter session, determine by client fully, but server also can send the termination conversation request in advance, agree in client under the situation of abort request, can response termination session reply, client is sent the conversation end request more then, the session of announcement server end user, otherwise session is still kept.

Diameter message is made up of message header and message body, comprise protocol version, application identities (identifying different Diameter uses), command code (Command Code in the message header, the expression type of message), information such as message-length, message body by property value to (Attribute-Value-Pair AVP) forms.Dissimilar Diameter message can comprise different AVP, and each application can define this and use distinctive AVP, thereby realize new function a kind of extension mechanism of Diameter just by defining new AVP.

When roaming (during position change) in access network, the user still can preserve IP operation continuity (non-interrupting service), access network with such character is called IP-CAN, such as (General PacketRadio Service, GPRS) network, intercommunicated wireless local (Inter working-WLAN, I-WLAN) network etc.The IP-CAN session refers to the incidence relation between UE and the PDN, and (User Equipment, the sign (as IMSI) of IP address UE) and UE is discerned by subscriber equipment.As long as UE has distributed the IP address and can have been discerned by IP network, then IP-CAN exists.An IP-CAN session can comprise one or more IP-CAN carrying.The foundation of IP-CAN carrying can be initiated by user side or network side.The strategy of PCRF formulation and concrete IP-CAN bearing binding also there are dual mode, can realize by PCRF or PCEF respectively.Set up process by the IP-CAN session, the IP-CAN loading establishing process is at the actual binding relationship that has formed between IP-CAN session as shown in Figure 2, IP-CAN carrying, PCC rule and the IP stream on the PCEF.

Fig. 2 is the corresponding relation schematic diagram between IP stream, PCC rule, IP-CAN carrying, the IP-CAN session.As can be seen from Figure 2, can set up a plurality of IP-CAN carryings in the IP-CAN session, and an IP-CAN carrying can be used to transmit one or more IP stream (requiring the requirement unanimity of these IP streams to QoS), a PCC rule can only be at an IP-CAN carrying, can comprise one or more IP stream, in the IP-CAN carrying one or more of PCC rules can be arranged.

When UE after PDN has distributed addressable IP address, UE has just set up the IP-CAN session, in order to satisfy different qos requirements, in same IP-CAN session, can set up the IP-CAN carrying that different QoS requires, suppose that IP-CAN carrying 1 has higher QoS than IP-CAN carrying 2 among Fig. 2, like this for the higher business of qos requirement (as VOIP, multimedia call etc.) can use IP-CAN carrying 1, for qos requirement low professional (such as file download etc., web page browsing etc.) can use IP-CAN carrying 2.PCEF discerns IP stream according to stream description information in the PCC rule (as source IP address, purpose IP address, protocol type, source port number, destination slogan etc.).

On the Rx reference point, each Media Stream is described by a Media-Component-DescriptionAVP.A plurality of Media Streams in the same session are by Media-Component-Number AVP sign.If AF adopts Session Description Protocol (SDP) that medium are described, a Media Stream is with regard to the m among the corresponding SDP capable (media description is capable) so, and the Media-Component-Number of this Media Stream correspondence is exactly the capable serial number that occurs in SDP of this m.The sub-stream of medium is that Media Stream is further segmented, when adopting the real-time transport protocol (rtp) mode to transmit such as an audio medium stream, and not corresponding medium of corresponding rtp streaming and RTCP flow point stream.On the Rx reference point, each medium stream is described by a Media-Sub-Component AVP.A plurality of medium stream in the same Media Stream is by Flow-Number AVP sign, and Flow-Number can number wait ordering according to each medium stream corresponding port.The sub-stream of medium can a corresponding bidirectional flow (comprise two Flow-Description AVP, describes two IP streams), also can a corresponding way flow (only comprise a Flow-Description AVP, describe an IP and flow).

IP stream is (to be collectively referred to as the IP five-tuple by having identical source IP address, purpose IP address, transport layer protocol, source port number and destination slogan, if corresponding transport layer protocol does not have the notion of port numbers, source port number and destination slogan can omit) the way flow formed of IP message.On the Rx reference point, each IPFlow describes by a Flow-Description AVP.

In sum, the user activates a business, can comprise one or more Media Stream (audio stream, video flowing, data flow etc.) in the business, each Media Stream can comprise one or more medium stream, and the sub-stream of each medium can comprise one or two IP stream.

This shows in the prior art, have following shortcoming:

At first, the AF request event reports can only can have a lot of IP streams at the whole Diameter session between AF and the PCRF in the session, and the requirement of these IP stream QoS can be different, thereby is carried in a plurality of IP-CAN carryings.Yet all the IP streams in the not necessarily whole session that AF need pay close attention to may only be some IP stream, only pay close attention to the interruption situation (this will cause the suspension of service) of IP stream 1 as shown in Figure 2 such as AF, and do not pay close attention to other IP streams as shown in Figure 2.Use existing mechanism, PCRF must indicate PCEF to report all IP-CAN carrying interruption situations in this session.If IP-CAN carrying 2 is interrupted, after PCEF reported PCRF, PCRF also needed to report to AF.In fact AF does not need these information, and this just causes between PCEF and the PCRF, redundant interacting message occurs between PCRF and the AF, has increased unnecessary load between three equipment.

Secondly, because giving the correct time on AF, PCRF use Flows AVP to describe the IP stream of influence, can only navigate to medium stream as can be seen at most from the definition of Flows AVP, for the situation that comprises two-way IP stream in the medium stream, can't distinguish the incident that reports at be upstream, downstream or at both.

Also have, AF can only ask the PCRF reported event in first request message of the Diameter session between foundation and the PCRF, just can't change afterwards, cause AF not increase deletion detection incident, perhaps revise the detection range of incident according to change situation professional in the conversation procedure (such as increasing deletion Media Stream or the like).

In addition, because event detection can only be at a session, so when AF only need detect the relevant incident of signaling flow, for avoiding on non-signaling flow, detecting reported event, can only set up an independent Diameter session with PCRF is used for the relevant event detection of signaling flow and reports, cause like this needing to safeguard a plurality of Diameter sessions between AF and the PCRF, cause the AF and the PCRF wasting of resources.PCRF need also cause Diameter size of message increase (becoming twice such as the message that finishes the Diameter session) between AF and the PCRF simultaneously repeatedly with the Diameter session and the IP-CAN session association of Rx reference point.

Summary of the invention

In view of this, the main purpose of the embodiment of the invention is to propose a kind of method that detects bearing event, to reduce redundant interacting message.

Another purpose of the embodiment of the invention is to propose a kind of system that detects bearing event, to reduce redundant interacting message.

A purpose again of the embodiment of the invention is to propose a kind of AF, to reduce redundant interacting message.

Another purpose of the embodiment of the invention is to propose a kind of PCRF, to reduce redundant interacting message.

For achieving the above object, the technical scheme of the embodiment of the invention is achieved in that

A kind of method that detects bearing event, this method comprises:

Application level function entity A F sends bearing event to policy control and charging regulation function entity PCRF and detects request, and described bearing event detects and comprises event detection type scope in the request and corresponding to the event detection scope of each event type in the described event detection type scope;

PCRF detects the incident of this type in the event detection scope of each event type, and returns event type and this coverage that detects incident of the incident that detects to AF.

A kind of system that detects bearing event, this system comprises AF and PCRF, wherein:

AF is used for sending bearing event to PCRF and detects request, and described bearing event detects and comprises event detection type scope in the request and corresponding to the event detection scope of each event type in the described event detection type scope;

PCRF is used for detecting the incident of this type in the event detection scope of each event type, and returns event type and this coverage that detects incident of the incident that detects to AF.

A kind of AF, this AF comprise that bearing event detects request transmitting unit and event handling unit, wherein:

Bearing event detects request transmitting unit, is used for sending bearing event to PCRF and detects request, and described bearing event detects and comprises event detection type scope in the request and corresponding to the event detection scope of each event type in the described event detection type scope;

The event handling unit is used for according to the application layer strategy incident being handled behind the event type and this coverage that detects incident received by incident that PCRF detects.

A kind of PCRF, this PCRF comprise that event detection unit and testing result return the unit, wherein:

The event detection unit, be used to receive the bearing event that sends by AF and detect request, and in the event detection scope of each event type, detecting the incident of this type, wherein said bearing event detects and comprises event detection type scope in the request and corresponding to the event detection scope of each event type in the described event detection type scope;

Testing result is returned the unit, is used for returning to AF event type and this coverage that detects incident of the incident that detects.

From technique scheme as can be seen, in embodiments of the present invention, when AF request PCRF detects reported event, indicate the event type scope and the detection range of detection, detection range can be the combination in any of whole Diameter session or Media Stream, medium stream and IP stream, and the detection range of different event can be different.PCRF is according to the request of AF, be engaged in the incident that detects the AF appointment in the scope of AF appointment with PCEF, after detecting corresponding event, PCRF is to the type of AF reported event and the coverage of incident, and wherein coverage can be the combination in any of whole Diameter session or Media Stream, medium stream and IP stream.This shows, use after the present invention, having solved the indication of the unnecessary interacting message that is caused by event detection granularity excessive (can only be whole Diameter session) in the current mechanism, events affecting scope, indeterminate (minimum can only flow to medium, can not indicate IP stream) problem, therefore can reduce redundant interacting message significantly.Simultaneously, also having solved existing event detection reports mechanism to use the problem of inflexible problem (can only specify follow-up can not the modification in AF sends to first request message of PCRF).

In addition, in embodiments of the present invention, in the whole life of the Diameter session between AF and PCRF, AF can ask PCRF to detect reported event, can ask to increase, delete, revise reported event, can send to the request message of PCRF at AF, Authentication Authorization request message (Auth-Authorization-Request for example, AAR) indication in, also can reply the response message of PCRF at AF, for example re-authenticate authorization response message (Re-Auth-Answer, RAA) in indication, so practical operation is got up more flexible.

In addition, the embodiment of the invention can also be applied in the signaling paths state-detection, need not to set up independent Diameter session, thus the resource that can also save AF and PCRF.

Description of drawings

Fig. 1 is the schematic diagram of PCC structure in the prior art;

Fig. 2 is the corresponding relation schematic diagram between IP stream, PCC rule, IP-CAN carrying, the IP-CAN session;

Fig. 3 is the method flow schematic diagram according to the detection bearing event of the embodiment of the invention;

Fig. 4 is the method flow schematic diagram according to the detection bearing event of first embodiment of the invention;

Fig. 5 is the method flow schematic diagram according to the detection bearing event of second embodiment of the invention;

Fig. 6 is the system configuration schematic diagram according to the detection bearing event of the embodiment of the invention;

Fig. 7 is the AF structural representation according to the embodiment of the invention;

Fig. 8 is the PCRF structural representation according to the embodiment of the invention.

Embodiment

For making the purpose, technical solutions and advantages of the present invention express clearlyer, the present invention is further described in more detail below in conjunction with drawings and the specific embodiments.

Fig. 3 is the method flow schematic diagram according to the detection bearing event of the embodiment of the invention.As shown in Figure 3, this method comprises:

Step 301:AF sends bearing event to PCRF and detects request, and bearing event detects and comprises event detection type scope in the request and corresponding to the event detection scope of each event type in the event detection type scope.

Wherein, described event detection scope can be whole Diameter session, perhaps the combination in any of Media Stream, medium stream and IP stream.And event detection type scope can comprise all event types, perhaps comprises the event type that at least one is specific.

, when AF request PCRF detects reported event, indicate the event type and the detection range that need detection here, wherein the detection range of dissimilar incidents can be different.

Step 302:PCRF detects the incident of this type in the event detection scope of each event type, and returns event type and this coverage that detects incident of the incident that detects to AF.

Here, PCRF is according to the request of AF, be engaged in the incident that detects the AF appointment in the scope of AF appointment with PCEF, after detecting corresponding event, PCRF is to the type of AF reported event and the coverage of incident, and coverage can be the combination in any of whole Diameter session or Media Stream, medium stream and IP stream.

Wherein, the event detection scope of each event detection type and inequality in the event detection type scope, and it is also also inequality respectively to detect the coverage of incident; Or the event detection scope of each event detection type is identical in the described event detection type scope, and it is also identical respectively to detect the coverage of incident; Or the event detection scope of each event detection type and inequality in the described event detection type scope, and it is identical respectively to detect the coverage of incident; Or the event detection scope of each event detection type is identical in the described event detection type scope, and respectively detects the coverage of incident and inequality.

In addition, in the whole life of the Diameter session between AF and PCRF, AF can ask PCRF to detect reported event, can ask to increase, delete, revise reported event, can send to indication in the request message (such as AAR) of PCRF at AF, also can in AF replys the response message (such as RAA) of PCRF, indicate.

Particularly: such as, when needs increase cancellation detects the event type that reports, AF can further send the cancellation bearing event to PCRF and detect request, and described cancellation bearing event detects and comprises the event detection scope that cancellation detects the event type scope and detects each event type in the event type scope corresponding to described cancellation in the request; PCRF detects in the event detection scope of event type in each cancellation, and cancellation detects the incident of this type.

Alternatively, when the needs increase detects the event type that reports, AF can send to PCRF increases bearing event detection request, and described increase bearing event detects and comprises the event detection scope that increases detection event type scope and detect each event type in the event type scope corresponding to described increase in the request; PCRF detects the incident of this type, and returns event type and this coverage that detects incident of the incident that detects to AF in each increases the event detection scope that detects event type.

When needs revise to detect the event type that reports and detection range, AF can send revise bearing event to PCRF and detect request, described modification bearing event detect comprise in the request detection event type scope to be revised and corresponding to described wait to revise detect each event type in the event type scope wait to revise the event detection scope; PCRF each wait to revise detect event type wait revise in the event detection scope, detect the incident of this type, and return event type and this coverage that detects incident of the incident that detects to AF.

The present invention can also be used for the signaling paths state-detection.For avoiding the conflict with the Media-Component-Number of Media Stream, the Media-Component-Number of signaling flow can be 0 or special numeral (such as 0xFFFFFFFF).Flow-Number AVP is specified by AF, and signaling flow is described by Flow-Description AVP, and the event detection of signaling flow reports and reports consistently with the event detection of Media Stream like this, need not to set up new Diameter session for the signaling paths state-detection.

AF can ask PCRF to detect reported event in request message.Fig. 4 is the method flow schematic diagram according to the detection bearing event of first embodiment of the invention.

As shown in Figure 4, this method comprises:

Step 401:AF is to PCRF send a request message (such as being AAR message), request PCRF detects reported event, in this request message, indicate the event type scope and the detection range of detection, detection range can be the combination in any of whole Diameter session or Media Stream, medium stream and IP stream, and the detection range of different event can be identical or different.Wherein, event type can adopt request detection of mode of wildcard to report all event types, also can request detection reports certain or some incidents.

Step 402:PCRF is to AF echo reply message (such as being AAA message).

Step 403:PCRF cooperates according to AF indication and PCEF, detects the incident of AF appointment in the scope of AF appointment.

After step 404:PCRF detects corresponding event, PCRF sends a request message (as RAR message) to AF, the coverage of reported event type and incident, coverage can be the combination in any of whole Diameter session or Media Stream, medium stream and IP stream.Within the events affecting scope detection range that must when AF asks, indicate of indication of giving the correct time on the PCRF.Event does not report outside the detection range of AF appointment, and AF does not have the event type of appointment not report yet.PCRF can once report a plurality of incidents, and the coverage of these incidents can be identical or different.

Step 405:AF sends response message (such as RAA message) to PCRF;

Step 406:AF is according to the strategy of application layer and the incident that reports, and (professional such as removing, by signaling modification business etc.) takes appropriate measures.

AF can also ask PCRF to detect reported event in response message.Fig. 5 is the method flow schematic diagram according to the detection bearing event of second embodiment of the invention.

As shown in Figure 5, this method comprises:

Step 501:PCRF is to AF send a request message (such as RAR message).

Step 502:AF is to PCRF echo reply message (such as RAA message), request PCRF detects reported event, indicate the event type scope and the detection range of detection in the message, detection range can be the combination in any of whole Diameter session or Media Stream, medium stream and IP stream, and the detection range of different event can be different.Wherein event type can adopt request detection of mode of wildcard to report all event types, also can request detection reports certain or some incidents.

Step 503:PCRF indicates according to AF and PCEF cooperates, and detects the incident of AF appointment in the scope of AF appointment.

After step 504:PCRF detects corresponding event, PCRF is to AF send a request message (such as RAR message), the coverage of reported event type and incident, coverage can be the combination in any of whole Diameter session or Media Stream, medium stream and IP stream.Within the events affecting scope detection range that must when AF asks, indicate of indication of giving the correct time on the PCRF.Event does not report outside the detection range of AF appointment, and AF does not have the event type of appointment not report yet.PCRF can once report a plurality of incidents, and the coverage of these incidents can be identical or different;

Step 505:AF sends response message (such as RAA message) to PCRF;

Step 506:AF is according to the strategy of application layer and the incident that reports, and (professional such as removing, by signaling modification business etc.) takes appropriate measures.

At present, the agreement between AF and the PCRF is generally Diameter.Be example with the Diameter below, the present invention will be described in detail.Yet, it will be appreciated by those of skill in the art that the present invention is not limited to Diameter.

Mode one:

At first existing AVP is expanded (comprise the several new AVP of definition and be the new value of existing AVP definition):

1.IP-Flows?AVP

　-Flows::＝<AVP?Header：x>

{Media-Component-Number}

*[Flow-Number]

[Direction]

IP-Flows AVP is the AVP of redetermination.This AVP is used to locate one or more IP stream, and wherein Direction is an enumeration type, and value can be UPLINK (0, up), DOWNLINK (1, descending), BOTH (2, two-way).... expression is than selecting parameter, [... ] the expression optional parameters, ^*Expression can have a plurality of (rules that following adopted is identical).Flow-Number does not occur representing that all medium in the Media Stream of Media-Component-Number correspondence flow, and Direction expression do not occur and comprises upstream and downstream.

2.Specific-Action?AVP

Specific-Action AVP is existing AVP, but no longer be directly used in AF request PCRF and detect reported event, be not directly used in PCRF to the AF reported event yet, only be used to define the variety of event type, new enumerated value: ALL of definition on original value basis, all event types of expression wildcard, ALL can only be used for the message that AF sends to PCRF.

3.IP-Flows-Specific-Action?AVP

IP-Flows-Specific-Action: : ＝<AVP?Header：x>

*{Specific-Action}

*[IP-Flows]

IP-Flows-Specific-Action AVP is the AVP of redetermination, and incident and IP stream are bound together, and it is at whole Diameter that presentation of events does not appear in IP-Flows.

4.Operation-Type?AVP

IP-Flows-Specific-Action AVP is the AVP of redetermination, and enumeration type, value are ADD (0, increase), REMOVE (1, deletion), UPDATE (2, upgrade), are used for the mode of operation of AF indication PCRF to IP-Flows-Specific-Action.Wherein ADD can be used for increasing new event type or increases the detection range of having asked the incident that reports, REMOVE is used to delete the detection range of the incident of having asked the event type that reports or having reduced to ask to report, UPDATE is used to delete the incident that original all requests report, and replaces with the incident in the new information.

5.IP-Flows-Specific-Action-Operation?AVP

IP-Flows-Specific-Action-Operation::＝<AVP?Header：x>

{Operation-Type}

*[IP-Flows-Specific-Action}

IP-Flows-Specific-Action-Operation AVP is the AVP of redetermination, and being used for AF increases, deletes, upgrades the detection incident that reports to PCRF.

When the AF request reports PCRF to detect reported event, only need to comprise one or more IP-Flows-Specific-Action-Operation AVP in sending to the request message of PCRF (as AAR) or response message (as RAA), the incident that a plurality of detection ranges are identical can be included among the same IP-Flows-Specific-Action-Operation AVP.If the detection range of certain or some incidents is whole Diameter session, then Dui Ying IP-Flows-Specific-Action AVP does not comprise IP-Flows AVP, otherwise corresponding IP-Flows-Specific-Action AVP can comprise one or more IP-Flows AVP with indication event detection scope (combination in any of Media Stream, medium stream and IP stream).AF adopts different Operation-Type can increase, delete, revise, upgrade reported event neatly.

PCRF is when the AF reported event, only needing to comprise one or more IP-Flows-Specific-Action AVP in sending to the request message of AF (as RAR) or response message (as AAA) just can be neatly to the AF reported event, and the incident that a plurality of coverages are identical can be included among the same IP-Flows-Specific-Action-Operation AVP.If the coverage of certain or some incidents is whole Diameter session, then Dui Ying IP-Flows-Specific-Action AVP does not comprise IP-Flows AVP, otherwise corresponding IP-Flows-Specific-Action AVP can comprise the coverage (combination in any of Media Stream, medium stream and IP stream) of one or more IP-Flows AVP with the indication incident.

This scheme is changed bigger to current mechanism, benefit is very flexible,

Mode two:

1.Flows?AVP

Flows::＝<AVP?Header：x>

{Media-Component-Number}

*[Flow-Number]

[Direction]

Flows AVP is existing AVP, has increased Direction AVP on original basis, so that can navigate to an IP stream.Direction is an enumeration type, and value can be UPLINK (0, up), DOWNLINK (1, descending), BOTH (2, two-way).Flow-Number does not occur representing that all medium in the Media Stream of Media-Component-Number correspondence flow, and Direction expression do not occur and comprises upstream and downstream.

2.Specific-Action?AVP

Specific-Action AVP is existing AVP, still can be used for AF asks reported event and PCRF to the AF reported event to PCRF, define two new enumerated value: DETECT_ALL and REMOVE_ALL, wherein DETECT_ALL represents that AF request PCRF detects all incidents that report, REMOVE_ALL represents that AF request PCRF cancellation detection reports all incidents, and the value of these two redeterminations all can only be used for the message that AF sends to PCRF.

When the AF request reports PCRF to detect reported event, only need in sending to the request message of PCRF (as AAR) or response message (as RAA), to comprise one or more Specific-ActionAVP, do not carry FlowsAVP in the Diameter message when event detection scope is whole Diameter session, otherwise can carry one or more Flows AVP with indication coverage (combination in any of Media Stream, medium stream and IP stream).The Specific-Action AVP that newly issues superposes on the original basis, when needing deletion certain or some reporting events, can in message, comprise a plurality of Specific-Action AVP, wherein first value is REMOVE_ALL, the incident that request reports before the cancellation, the reported event that follow-up Specific-Action indication need keep.When needing cancel all, only need carry a Specific-Action AVP in Diameter message, are worth to be REMOVE_ALL.

PCRF is when the AF reported event, only need in sending to the request message of AF (as RAR) or response message (as AAA), to comprise one or more Specific-Action AVP, do not carry Flows AVP in the message when events affecting scope is whole Diameter session, otherwise can carry one or more Flows AVP with indication coverage (combination in any of Media Stream, medium stream and IP stream).

The advantage of this scheme is to change less to current mechanism.

Mode three:

1.Flows?AVP

Flows::＝<AVP?Header：x>

{Media-Component-Number}

*[Flow-Number]

[Direction]

2.Specific-Action?AVP

3.Media-Component-Description?AVP

Media-Component-DescriptionAVP is existing AVP, increases parameter S pecific-Action AVP, and being used for AF, to indicate detection range when PCRF request detection reported event be the incident of Media Stream.

4.Media-Sub-Component?AVP

Media-Sub-Component AVP is existing AVP, increases parameter S pecific-ActionAVP, and being used for AF, indicate detection range when PCRF request detection reported event be the incidents that medium flows.

In the mode three, AF is when PCRF request detection reported event, can report the different incident of detection range by comprise different Specific-Action AVP request PCRF in Media-Component-DescriptionAVP and/or Media-Sub-Component AVP in same Diameter message, other aspects are identical with mode two.

Mode four:

1.Flows?AVP

Flows::＝<AVP?Header：x>

{Media-Component-Number}

*[Flow-Number]

[Direction]

2.Specific-Action?AVP

Specific-Action AVP is existing AVP, but no longer is directly used in AF request PCRF reported event, also is not directly used in PCRF to the AF reported event, only is used to define the variety of event type.Define two new enumerated value: DETECT_ALL and REMOVE_ALL, wherein DETECT_ALL represents that AF request PCRF detects all incidents that report, REMOVE_ALL represents that AF request PCRF cancellation detection reports all incidents, and the value of these two redeterminations all can only be used for the message that AF sends to PCRF.

3.IP-Flows-Specific-Action?AVP

IP-Flows-Specific-Action: : ＝<AVP?Header：x>

*{Specific-Action}

*[IP-Flows]

When the AF request reports PCRF to detect reported event, only need in sending to the request message of PCRF (as AAR) or response message (as RAA), to comprise one or more IP-Flows-Specific-Action AVP, if wherein the detection range of certain incident is whole Diameter session, then Dui Ying IP-Flows-Specific-Action AVP does not comprise Flows AVP, otherwise corresponding IP-Flows-Specific-Action AVP can comprise one or more Flows AVP with indication event detection scope (Media Stream, the combination in any of medium stream and IP stream).The Specific-Action AVP that newly issues superposes on the original basis, when needing deletion certain or some reporting events, can in message, comprise a plurality of IP-Flows-Specific-Action AVP, wherein the value of Specific-Action is REMOVE_ALL among first IP-Flows-Specific-Action, the incident that request reports before the cancellation, the reporting events that follow-up IP-Flows-Specific-Action indication need keep.When needing cancel all, only need to carry an IP-Flows-Specific-Action AVP in Diameter message, the value of its Specific-Action is REMOVE_ALL.

PCRF is when the AF reported event, only needing to comprise one or more IP-Flows-Specific-Action AVP in sending to the request message of AF (as RAA) or response message (as AAA) just can be neatly to the AF reported event, if wherein the coverage of certain incident is whole Diameter session, then Dui Ying IP-Flows-Specific-Action AVP does not comprise Flows AVP, otherwise corresponding IP-Flows-Specific-Action AVP can comprise the coverage (Media Stream of one or more Flows AVP with the indication incident, the combination in any of medium stream and IP stream).

Fig. 6 is the system configuration schematic diagram according to the detection bearing event of the embodiment of the invention.As shown in Figure 6, this system comprises AF601 and PCRF602, wherein:

AF601 is used for sending bearing event to PCRF602 and detects request, and described bearing event detects and comprises event detection type scope in the request and corresponding to the event detection scope of each event type in the described event detection type scope;

PCRF602 is used for detecting the incident of this type in the event detection scope of each event type, and returns event type and this coverage that detects incident of the incident that detects to AF601.

Wherein, AF601, can be further used for sending the cancellation bearing event to PCRF602 and detect request, described cancellation bearing event detects and comprises the cancellation event detection scope that cancellation detects the event type scope and detects each event type in the event type scope corresponding to described cancellation in the request;

PCRF602 is further used for detecting in the cancellation event detection scope of event type in each cancellation, and cancellation detects the incident of this type.

AF601, can be further used for sending the increase bearing event to PCRF602 and detect request, described increase bearing event detects and comprises the event detection scope that increase detects the event type scope and detects each event type in the event type scope corresponding to described increase in the request;

PCRF602 can be further used for detecting the incident of this type, and returning event type and this coverage that detects incident of the incident that detects to AF601 in each increases the event detection scope that detects event type.

AF601 can be further used for sending the bearing event detection request of revising to PCRF602.Described modification bearing event detect comprise in the request detection event type scope to be revised and corresponding to described wait to revise detect each event type in the event type scope wait to revise the event detection scope;

PCRF602, be further used for each wait to revise detect event type wait revise in the event detection scope, detect the incident of this type, and return event type and this coverage that detects incident of the incident that detects to AF601.

AF601 can send bearing event to PCRF602 by AAR message or RAA message and detect request.PCRF602 can return event type and this coverage that detects incident of the incident that detects by RAR message or AAA message to AF601.AF601 can also be further used for according to the application layer strategy incident being handled after the event type of receiving the incident of detecting and this detect the coverage of incident.

Fig. 7 is the AF structural representation according to the embodiment of the invention.

As shown in Figure 7, this AF comprises that bearing event detects request transmitting unit 701 and event handling unit 702, wherein:

Bearing event detects request transmitting unit 701, be used for sending bearing event to PCRF and detect request, described bearing event detects and comprises event detection type scope in the request and corresponding to the event detection scope of each event type in the described event detection type scope.

Event handling unit 702 is used for according to the application layer strategy incident being handled behind the event type and this coverage that detects incident received by incident that PCRF detects.

As shown in Figure 8, this PCRF comprises that event detection unit 801 and testing result return unit 802.

Event detection unit 801, be used to receive the bearing event that sends by AF and detect request, and in the event detection scope of each event type, detecting the incident of this type, wherein said bearing event detects and comprises event detection type scope in the request and corresponding to the event detection scope of each event type in the described event detection type scope.

Testing result is returned unit 802, is used for returning to AF event type and this coverage that detects incident of the incident that detects.

In sum, the embodiment of the invention at first provides a kind of AF to detect the method for bearing event.

Detect in the method for bearing event at this AF, when AF request PCRF detects reported event, indicate the event type and the detection range of detection, detection range can be the combination in any of whole Diameter session or Media Stream, medium stream and IP stream, the detection range of different event can be identical or different, wherein event type can adopt request detection of mode of wildcard to report all event types, also can request detection reports certain or some incidents; Detect the incident of AF appointment in the scope that PCRF is engaged in the AF appointment according to request and the PCEF of AF again.After detecting corresponding event, PCRF is to AF reported event type and coverage, coverage can be the combination in any of whole Diameter session or Media Stream, medium stream and IP stream, within the events affecting scope detection range that must when AF asks, indicate of indication of wherein giving the correct time on the PCRF, event does not report outside the detection range of AF appointment, and AF does not have the event type of appointment not report yet.

PCRF can once report a plurality of incidents, and the coverage of these incidents can be identical or different.

AF can also take appropriate measures according to the strategy of application layer and the incident that reports (professional, by signaling modification business etc.) such as removing.

AF request PCRF detects after the reported event, can ask the PCRF cancellation to report bearing event, indicates event type and detection range that cancellation detects, and detection range can be the combination in any of whole Diameter session or Media Stream, medium stream and IP stream.Wherein event type can adopt the mode of wildcard once to cancel to detect and reports all event types, also can cancel certain or some incident of reporting that detects.The detection range that detection range during AF cancellation reported event can be indicated when asking reported event before is bigger (such as request after reporting certain incident on certain Media Stream, this incident that reports is cancelled in request on whole session, certainly also cancelling on this Media Stream), littler (such as the request after whole Diameter session reports certain incident, this incident that reports is cancelled in request on certain Media Stream, be illustrated in and continue to detect this incident that reports on other Media Streams), also can equate.

AF request PCRF detects after the reported event, can ask PCRF to increase detection and report bearing event, can ask to revise the scope (increase, dwindle) that detects bearing event for asking PCRF to detect the incident AF that reports.

AF request PCRF detects after the reported event, can ask PCRF to upgrade and detect event type and the detection range that reports, the request before promptly directly replacing it with reported event type of carrying in the new information and detection range.

In the whole life of the Diameter session between AF and PCRF, AF can ask the PCRF reported event, also can ask to increase, cancel, revise reported event, can send to indication in the request message (such as AAR) of PCRF at AF, also can in AF replys the response message (such as RAA) of PCRF, indicate.

PCRF can send to indication in the request message (such as RAR) of AF at PCRF when the AF reported event, also can indicate in PCRF replys the response message (such as AAA) of AF.

By the method for the embodiment of the invention, AF can ask PCRF to report some incident at any time, also can cancel detecting reporting some incident, increase to detect the detection range that reports other incidents or the incident of modification.The detection granularity of incident can be the combination in any of whole Diameter session or Media Stream, medium stream and IP stream.Thereby (minimum can only arrive medium and flow to have solved that the unnecessary messages that current mechanism event detection granularity excessive (can only be whole Diameter session) causes is mutual, the indication of events affecting scope is indeterminate, can not indicate IP stream) problem, also having solved simultaneously existing event detection reports mechanism to use inflexible problem (can only specify follow-up can not the modification in AF sends to first request message of PCRF).

The mechanism of describing in the invention process also can be used for the signaling paths state-detection simultaneously, for avoiding conflicting with the Media-Component-Number of Media Stream, the Media-Component-Number of signaling flow can be 0 or special numeral (such as 0xFFFFFFFF), Flow-Number AVP specifies (can according to the size ordering of port numbers etc.) by AF, signaling flow also can be described by Flow-Description AVP, the event detection of signaling flow reports and reports consistently with the event detection of Media Stream like this, does not need to set up new Diameter session for the signaling paths state-detection.

The above is preferred embodiment of the present invention only, is not to be used to limit protection scope of the present invention.Within the spirit and principles in the present invention all, any modification of being done, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.

Claims

1. a method that detects bearing event is characterized in that, this method comprises:

The application level function entity sends bearing event to policy control and charging regulation function entity and detects request, and described bearing event detects and comprises event detection type scope in the request and corresponding to the event detection scope of each event type in the described event detection type scope;

Policy control and charging regulation function entity detect the incident of this type in the event detection scope of each event type, and return event type and this coverage that detects incident of the incident that detects to the application level function entity.

2. the method for detection bearing event according to claim 1 is characterized in that, described event detection scope is whole Diameter session, perhaps the combination in any of Media Stream, medium stream and IP stream.

3. the method for detection bearing event according to claim 1 is characterized in that, described coverage is whole Diameter session, perhaps the combination in any of Media Stream, medium stream and IP stream.

4. the method for detection bearing event according to claim 1 is characterized in that, described event detection type scope comprises all event types, perhaps comprises the event type that at least one is specific.

5. the method for detection bearing event according to claim 1 is characterized in that, this method further comprises:

The application level function entity sends cancellation bearing event detection request to policy control and charging regulation function entity, and described cancellation bearing event detects the event detection scope that comprises cancellation detection event type scope in the request and detect each event type in the event type scope corresponding to described cancellation;

Policy control and charging regulation function entity detect in the event detection scope of event type in each cancellation, and cancellation detects the incident of this type.

6. the method for detection bearing event according to claim 1 is characterized in that, this method further comprises:

The application level function entity sends increase bearing event detection request to policy control and charging regulation function entity, and described increase bearing event detects the event detection scope that comprises increase detection event type scope in the request and detect each event type in the event type scope corresponding to described increase;

Policy control and charging regulation function entity are in each increases the event detection scope that detects event type, detect the incident of this type, and to the application level function entity return increase the event type of the incident of detecting and the coverage that this increase detects incident.

7. the method for detection bearing event according to claim 1 is characterized in that, this method further comprises:

The application level function entity sends to policy control and charging regulation function entity and revises bearing event and detect request, described modification bearing event detect comprise in the request detection event type scope to be revised and corresponding to described wait to revise detect each event type in the event type scope wait to revise the event detection scope;

Policy control and charging regulation function entity each wait to revise detect event type wait to revise in the event detection scope, detect the incident of this type, and return event type and this coverage that detects incident of the incident that detects to the application level function entity.

8. the method for detection bearing event according to claim 1, it is characterized in that, described event detection scope is a signaling flow, wherein the Media-Component-Number of signaling flow is 0 or special numeral, Flow-NumberAVP is specified by the application level function entity, and signaling flow is described by Flow-DescriptionAVP.

9. the method for detection bearing event according to claim 1, it is characterized in that, the application level function entity sends bearing event detection request by the Authentication Authorization request message to policy control and charging regulation function entity, and perhaps the application level function entity detects request by re-authenticating authorization response message to policy control and charging regulation function entity transmission bearing event.

10. the method for detection bearing event according to claim 1, it is characterized in that, policy control and charging regulation function entity return event type and this coverage that detects incident of the incident that detects by re-authenticating authorization request message to the application level function entity, and perhaps policy control and charging regulation function entity return event type and this coverage that detects incident of the incident that detects to the application level function entity by the Authentication Authorization request message.

11. the method for detection bearing event according to claim 1 is characterized in that, the event detection scope of each event detection type and inequality in the described event detection type scope, and it is also also inequality respectively to detect the coverage of incident; Or

The event detection scope of each event detection type is identical in the described event detection type scope, and it is also identical respectively to detect the coverage of incident; Or

The event detection scope of each event detection type and inequality in the described event detection type scope, and it is identical respectively to detect the coverage of incident; Or

The event detection scope of each event detection type is identical in the described event detection type scope, and respectively detects the coverage of incident and inequality.

12. a system that detects bearing event is characterized in that, this system comprises application level function entity and policy control and charging regulation function entity, wherein:

The application level function entity, be used for sending bearing event to policy control and charging regulation function entity and detect request, described bearing event detects and comprises event detection type scope in the request and corresponding to the event detection scope of each event type in the described event detection type scope;

Policy control and charging regulation function entity are used for detecting the incident of this type in the event detection scope of each event type, and return event type and this coverage that detects incident of the incident that detects to the application level function entity.

13. the system of detection bearing event according to claim 12 is characterized in that,

The application level function entity, be further used for sending cancellation bearing event detection request to policy control and charging regulation function entity, described cancellation bearing event detects the cancellation event detection scope that comprises cancellation detection event type scope in the request and detect each event type in the event type scope corresponding to described cancellation;

Policy control and charging regulation function entity are further used for detecting in the cancellation event detection scope of event type in each cancellation, and cancellation detects the incident of this type.

14. the system of detection bearing event according to claim 12 is characterized in that,

The application level function entity, be further used for sending increase bearing event detection request to policy control and charging regulation function entity, described increase bearing event detects the event detection scope that comprises increase detection event type scope in the request and detect each event type in the event type scope corresponding to described increase;

Policy control and charging regulation function entity, be further used in each increases the event detection scope that detects event type, detect the incident of this type, and to the application level function entity return increase the event type of the incident of detecting and the coverage that this increase detects incident.

15. the system of detection bearing event according to claim 12 is characterized in that

The application level function entity, be further used for sending and revise bearing event and detect request to policy control and charging regulation function entity, described modification bearing event detect comprise in the request detection event type scope to be revised and corresponding to described wait to revise detect each event type in the event type scope wait to revise the event detection scope;

Policy control and charging regulation function entity, be further used for each wait to revise detect event type wait to revise in the event detection scope, detect the incident of this type, and return event type and this coverage that detects incident of the incident that detects to the application level function entity.

16. the system of detection bearing event according to claim 12 is characterized in that,

The application level function entity is used for by the Authentication Authorization request message or re-authenticates authorization response message sending bearing event detection request to policy control and charging regulation function entity.

17. the system of detection bearing event according to claim 12 is characterized in that,

Policy control and charging regulation function entity are used for by re-authenticating authorization request message or Authentication Authorization request message return event type from the incident that detects to the application level function entity and this coverage that detects incident.

18. the system of detection bearing event according to claim 12 is characterized in that,

The application level function entity is further used for according to the application layer strategy incident being handled after the event type of receiving the incident of detecting and this detect the coverage of incident.

19. an application level function entity is characterized in that, this application level function entity comprises that bearing event detects request transmitting unit and event handling unit, wherein:

Bearing event detects request transmitting unit, be used for sending bearing event to policy control and charging regulation function entity and detect request, described bearing event detects and comprises event detection type scope in the request and corresponding to the event detection scope of each event type in the described event detection type scope;

The event handling unit is used for according to the application layer strategy incident being handled behind the event type and this coverage that detects incident received by policy control and incident that charging regulation function entity detects.

20. policy control and charging regulation function entity is characterized in that, this policy control and charging regulation function entity comprise that event detection unit and testing result return the unit, wherein:

The event detection unit, be used to receive the bearing event that sends by the application level function entity and detect request, and in the event detection scope of each event type, detecting the incident of this type, wherein said bearing event detects and comprises event detection type scope in the request and corresponding to the event detection scope of each event type in the described event detection type scope;

Testing result is returned the unit, is used for returning to the application level function entity event type and this coverage that detects incident of the incident that detects.