WO2014179992A1

WO2014179992A1 - User plane event processing method, pcrf entity, and af entity

Info

Publication number: WO2014179992A1
Application number: PCT/CN2013/075490
Authority: WO
Inventors: 王硕
Original assignee: 华为技术有限公司
Priority date: 2013-05-10
Filing date: 2013-05-10
Publication date: 2014-11-13
Also published as: CN104303488A

Abstract

Embodiments of the present invention provide a user plane event processing method, a PCRF entity, and an AF entity. The method comprises: a policy and charging rule function (PCRF) entity establishing a long connection with an application function (AF) entity; the PCRF entity reporting, on the established long connection, a first user plane event and a second user plane event to the AF entity, the first user plane event and the second user plane event being non-null user plane events. In the method provided in the embodiment, by establishing a long connection with an AF entity, a PCRF entity reports, on the established long connection, a first user plane event and a second user plane event to the AF entity, a non-null plane event is restrained from being sent, and accordingly, it is not required to established a connection each time when there is a user plane event needing to reported, and a non-null user plane event does not need to be sent, thereby reducing the network signaling overhead.

Description

User plane event processing method, PCRF entity and AF entity

The embodiments of the present invention relate to communication technologies, and in particular, to a user plane event processing method, a PCRF entity, and an AF entity. Background technique

As Internet services continue to grow, mobile network operators need to support not only their own application servers, but also more and more third-party application servers. Under the existing network architecture, the operator's own application server can establish an interaction with the Policy and Charging Rule Function (PCRF) entity through the Rx interface.

In the prior art, an Extensible Markup Language (XML) is used for communication between an Application Function entity and a PCRF of a third-party network, and an XML-based protocol is a Simple Object Access protocol. Protocol (SOAP) or Representational State Transfer (Rest) is a standard client-server (C/S) mode. In this mode, it can only be activated by the AF as a client. The PCRF as the server sends a message. In the prior art, if the AF acquires the user plane event of the PCRF, it will receive an empty user plane event, which causes a waste of system resources.

The embodiment of the present invention provides a user plane event processing method, a PCRF entity, and an AF entity, which can implement the PCRF to report a user plane event to the AF.

A first aspect of the present invention provides a user plane event processing method, including:

Policy and charging rule function PCRF entity and application function AF entity establishes long connection

(keep-alive connection);

The PCRF entity reports the first user plane event and the second user plane event to the AF entity on the established long connection, where the first user plane event and the second user plane event are non-empty users. In the case of a face event, the PCRF entity suppresses sending empty user plane events on the long connection.

In a first possible implementation manner of the first aspect of the present invention, the PCRF entity and the AF Entities establish long connections, including:

The PCRF entity directly establishes the long connection with the AF entity; or

The PCRF entity establishes the long connection with the AF entity through an intermediate network element.

In a second possible implementation manner of the first aspect of the present invention, the long connection is a long connection based on a flow;

The PCRF entity reports the first user plane event and the second user plane event to the AF entity on the established long connection, including:

The PCRF entity reports the first user plane event and the second user plane event to the AF entity on the stream-based long connection.

In a third possible implementation manner of the first aspect of the present invention, the PCRF entity reports the first user plane event and the first to the AF entity on the frame based long connection. Two user plane events, including:

Receiving, by the PCRF entity, the first user plane event report request message sent by the AF entity, and sending the first user plane event report to the AF entity on the flow-based long connection The response message and the second user plane event report response message are in response to the first user plane event report request message, where the first user plane event report response message includes the first user plane event, the second user face The event reporting response message includes the second user plane event; or

Sending, by the PCRF entity, the first user plane event and the second user plane event to the intermediate network element on the stream-based long connection, so that the intermediate network element is on the stream-based long connection Receiving the first user plane event report response message and the second user plane event report response message to the AF entity on the flow-based long connection after receiving the first user plane event report request message sent by the AF entity In response to the first user plane event report request message, the first user plane event report response message includes a first user plane event, and the second user plane event report response message includes the second user plane event .

In a fourth possible implementation manner of the first aspect of the present invention, the long connection is a long connection based on a long-polling based;

The PCRF entity reports the first user plane event and the second user plane event to the AF on the established long connection, including:

Reporting, by the PCRF entity, the AF entity to the AF entity on the long connection based on long polling a first user plane event and the second user plane event.

In a fifth possible implementation manner of the first aspect of the present invention, the PCRF entity reports the first user plane event and the second user plane event to the AF entity on the long polling-based long connection, including :

Receiving, by the PCRF entity, the first user plane event report request message and the second user plane event report request message sent by the AF entity on the long polling-based long connection, in the long polling-based long connection Sending a first user plane event report response message and a second user plane event report response message to the AF entity, where the first user plane event report response message is responsive to the first two user plane event report request messages, The second user plane event report response message is sent to the second user plane event report request message, and the first user plane event report response message includes the first user plane event, and the second user plane event report response The message includes the second user plane event; or

Sending, by the PCRF entity, the first user plane event and the second user plane event to the intermediate network element on the long polling-based long connection, so that the intermediate network element is on the long polling-based long connection After receiving the first user plane event report request message and the second user plane event report request message sent by the AF entity, sending the first user plane event report to the AF entity on the long polling-based long connection The response message and the second user plane event report response message, the first user plane event report response message is responsive to the first user plane event report request message, and the second user plane event report response message is responsive to the second user The first user plane event report response message includes the first user plane event, and the second user plane event report response message includes the second user plane event.

A second aspect of the present invention provides a user plane event processing method, including:

The application function AF entity establishes a long connection with the policy and charging rule function PCRF entity; the AF entity receives the first user plane event and the second user plane event reported by the PCRF entity on the established long connection, where The first user plane event and the second user plane event are non-empty user plane events.

In a first possible implementation manner of the second aspect, the AF entity establishes a long connection with the PCRF entity, including:

The AF entity directly establishes the long connection with the PCRF entity; or

The AF entity establishes the long connection with the PCRF entity through an intermediate network element. In a second possible implementation manner of the second aspect of the present invention, the long connection is a long connection based on a flow;

Receiving, by the AF entity, the first user plane event and the second user plane event reported by the PCRF entity on the established long connection, including:

The AF entity receives the first user plane event and the second user plane event reported by the PCRF entity on the stream-based long connection.

In a third possible implementation manner of the second aspect of the present invention, the AF entity receives the first user plane event and the second user plane reported by the PCRF entity on the stream-based long connection. Events, including:

After the first entity plane event report request message is sent to the PCRF entity, the AF entity receives the first user plane event sent by the PCRF entity on the stream-based long connection. And reporting, by the first user plane event reporting message, the first user plane event reporting request message, where the first user plane event reporting response message includes the first user plane event, the second user The second event surface event is included in the face event report response message; or

After the first user plane event report request message is sent to the intermediate network element, the AF entity receives the first user plane event sent by the intermediate network element on the stream-based long connection. And reporting, by the first user plane event reporting message, the first user plane event reporting request message, where the first user plane event reporting response message includes the first user plane event, the second user The second event surface event is included in the face event report response message.

In a fourth possible implementation manner of the second aspect of the present invention, the long connection is a long connection based on long polling;

The AF entity receives the first user plane event and the second user plane event reported by the PCRF entity on the long polling-based long connection.

In a fifth possible implementation manner of the second aspect of the present invention, the AF entity receives the first user plane event and the second reported by the PCRF entity on the long polling-based long connection. User-side events, including:

Sending, by the AF entity, the first to the PCRF entity on the long poll-based long connection After the user plane event report request message and the second user plane event report request message, the first user plane event report response message and the second user plane event report sent by the PCRF entity are received on the long polling-based long connection. In response to the message, the first user plane event report response message is responsive to the first two user plane event report request messages, and the second user plane event report response message is responsive to the second user plane event report request message. The first user plane event report response message includes the first user plane event, and the second user plane event report response message includes the second user plane event; or

After the first user plane event report request message and the second user plane event are sent to the intermediate network element on the long polling-based long connection, the AF entity receives the long polling based long connection. The first user plane event report response message and the second user plane event report request message sent by the intermediate network element, the first user plane event report response message responding to the first user plane event report request message, The second user plane event report response message is sent to the second user plane event report request message, where the first user plane event report response message includes the first user plane event, and the second user plane event report response message The second user plane event is included.

With reference to the second aspect of the present invention and the first to fifth possible implementation manners of the second aspect, in the sixth possible implementation manner of the second aspect of the present invention, the AF entity establishes a long connection with the PCRF entity. , including:

The AF entity establishes a long connection with the PCRF entity after the session establishment is completed.

The third aspect of the present invention provides a policy and charging rule function PCRF entity, including: a long connection establishing module, configured to establish a long connection with an application function AF entity;

a user plane event reporting module, configured to report a first user plane event and a second user plane event to the AF entity on the established long connection, and suppress sending an empty user plane event on the long connection, where The first user plane event and the second user plane event are non-empty user plane events.

In a first possible implementation manner of the third aspect of the present invention, the long connection establishing module is specifically configured to:

Establishing the long connection directly with the AF entity; or establishing the long connection with the AF entity by using an intermediate network element.

In a second possible implementation manner of the third aspect of the present invention, the long connection is a long connection based on a flow;

The user plane event reporting module is specifically configured to: send the AF to the stream-based long connection The entity reports the first user plane event and the second user plane event.

In a third possible implementation manner of the third aspect of the present invention, the user plane event reporting module is specifically configured to:

Receiving, by the flow-based long connection, a first user plane event report request message sent by the AF entity, and sending a first user plane event report response message to the AF entity on the flow-based long connection The second user plane event reporting response message is responsive to the first user plane event reporting request message, and the at least two first user plane event reporting response messages include the first user plane event, the second user plane event The report response message includes the second user plane event; or

Transmitting the first user plane event and the second user plane event to the intermediate network element on the stream-based long connection, so that the intermediate network element receives the on the stream-based long connection After the first user plane event report request message sent by the AF entity, the first user plane event report response message and the second user plane event report response message are sent to the AF entity on the stream-based long connection in response to the The first user plane event report request message includes: the first user plane event report response message includes the first user plane event, and the second user plane event report response message includes the second user plane event.

In a fourth possible implementation manner of the third aspect of the present invention, the long connection is a long connection based on long polling;

The user plane event reporting module is configured to report the first user plane event and the second user plane event to the AF entity on the long polling-based long connection.

In a fifth possible implementation manner of the third aspect, the user plane event reporting module is specifically configured to:

Receiving, on the long polling-based long connection, a first user plane event reporting request message and a second user plane event reporting request message sent by the AF entity, to the long polling based long connection The AF entity sends a first user plane event report response message and a second user plane event report response message, and the first user plane event report response message is responsive to the first two user plane event report request messages, the second user The second user plane event report response message includes the first user plane event, and the second user plane event report response message includes the second user plane event report request message. Or describing the second user plane event; or sending the first user plane event and the second to the intermediate network element in the long polling based long connection a user plane event, after the intermediate network element receives the first user plane event report request message and the second user plane event report request message sent by the AF entity on the long polling-based long connection, The first user plane event report response message and the second user plane event report response message are sent to the AF entity, and the first user plane event report response message is responsive to the first user. The second user plane event report response message is responsive to the second user plane event report request message, and the first user plane event report response message includes the first user plane event, The second user plane event report response message includes the second user plane event.

A fourth aspect of the present invention provides an application function AF entity, including: a long connection establishing module, configured to establish a long connection with a policy and charging rule function PCRF entity; and a user plane event receiving module, configured to be established The first user plane event and the second user plane event reported by the PCRF entity are received on the long connection, where the first user plane event and the second user plane event are non-empty user plane events.

In a first possible implementation manner of the fourth aspect of the present invention, the long connection establishing module is specifically configured to:

Establishing the long connection directly with the PCRF entity; or establishing the long connection with the PCRF entity by using an intermediate network element.

In a second possible implementation manner of the fourth aspect of the present invention, the long connection is a long connection based on a flow;

The user plane event receiving module is specifically configured to receive the

The first user plane event and the second user plane event reported by the PCRF entity.

In a third possible implementation manner of the fourth aspect of the present invention, the user plane event receiving module is specifically configured to:

After the first user plane event report request message is sent to the PCRF entity on the flow-based long connection, the first user plane event report response message sent by the PCRF entity is received on the stream-based long connection. The second user plane event report response message is sent to the first user plane event report request message, where the first user plane event report response message includes the first user plane event, and the second user plane event report response The message includes the second user plane event; or, after sending the first user plane event report request message to the intermediate network element on the stream-based long connection, receiving the message on the stream-based long connection The first user plane event sent by the intermediate network element And reporting, by the second user plane event reporting message, the first user plane event reporting request message, where the first user plane event reporting response message includes the first user plane event, the second user The second event surface event is included in the face event report response message.

In a fourth possible implementation manner of the fourth aspect of the present invention, the long connection is a long connection based on a long polling;

The user plane event receiving module is configured to: receive the first user plane event and the second user plane event reported by the PCRF entity on the long polling-based long connection.

In a fifth possible implementation manner of the fourth aspect, the user plane event receiving module is specifically configured to:

Transmitting the first user plane event reporting request message and the second user plane event reporting request message to the PCRF entity on the long polling-based long connection, and receiving the long round polling long connection a first user plane event report response message and a second user plane event report response message sent by the PCRF entity, the first user plane event report response message responding to the first two user plane event report request messages, the second The user plane event report response message is responsive to the second user plane event report request message, the first user plane event report response message includes the first user plane event, and the second user plane event report response message includes The second user plane event; or

After the first user plane event reporting request message and the second user plane event reporting request message are sent to the intermediate network element on the long polling-based long connection, receiving the long round polling long connection a first user plane event report response message and a second user plane event report request message sent by the intermediate network element, the first user plane event report response message responding to the first user plane event report request message, the second user The second user plane event report response message includes the first user plane event, and the second user plane event report response message includes the second user plane event report request message. The second user plane event is described.

With reference to the second aspect of the present invention and the first to fifth possible implementation manners of the second aspect, in the sixth possible implementation manner of the fourth aspect of the present invention, the long connection establishing module is specifically configured to: After the session establishment is completed, a long connection is established with the PCRF entity.

A fifth aspect of the present invention provides a policy and charging rule function PCRF entity, including: a processor and a memory, where the memory stores an execution instruction, and when the PCRF entity is running, the processor communicates with the memory The processor executing the execution instruction such that the PCRF The entity performs any of the methods of the first aspect of the invention and the first to fifth possible implementations of the first aspect.

A sixth aspect of the present invention provides an application function AF entity, including: a processor and a memory, where the memory stores an execution instruction, when the AF entity is running, the processor and the memory communicate, the processing Executing the execution instructions causes the AF entity to perform the method of any of the first to sixth possible implementations of the second aspect of the invention and the second aspect.

According to the method provided by the embodiment of the present invention, the PCRF entity establishes a long connection with the AF entity, and the PCRF entity reports the first user plane event and the second user plane event to the AF entity on the established long connection, and suppresses sending the empty user. Face events do not have to establish a connection every time a user plane event needs to be reported, and do not have to send an empty user plane event, thereby reducing network signaling overhead. BRIEF DESCRIPTION OF THE DRAWINGS In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings to be used in the embodiments or the description of the prior art will be briefly described below, and obviously, in the following description The drawings are only some of the embodiments of the present invention, and other drawings may be obtained from those skilled in the art without departing from the drawings.

1 is a flowchart of Embodiment 1 of a method for processing a user plane event according to the present invention;

2 is a flowchart of Embodiment 2 of a method for processing a user plane event according to the present invention;

3 is a flowchart of Embodiment 3 of a method for processing a user plane event according to the present invention;

4 is a flowchart of Embodiment 4 of a method for processing a user plane event according to the present invention;

5 is a flowchart of Embodiment 5 of a method for processing a user plane event according to the present invention;

6 is a flowchart of Embodiment 6 of a method for processing a user plane event according to the present invention;

7 is a signaling flowchart of Embodiment 7 of a method for processing a user plane event according to the present invention;

8 is a signaling flowchart of Embodiment 8 of a method for processing a user plane event according to the present invention;

9 is a schematic structural diagram of a PCRF entity provided in Embodiment 9 of the present invention;

10 is a schematic structural diagram of an AF entity according to Embodiment 10 of the present invention;

11 is a schematic structural diagram of a PCRF entity according to Embodiment 11 of the present invention;

FIG. 12 is a schematic structural diagram of an AF entity according to Embodiment 12 of the present invention. detailed description The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is a partial embodiment of the invention, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without departing from the inventive scope are the scope of the present invention.

The technical solutions described in the embodiments of the present invention are mainly applicable to communication between a third-party application server (ie, an AF entity) and a PCRF entity provided by a mobile network operator. In the existing network architecture, the operator's own server can establish interaction with the PCRF entity through the Rx interface. The Diameter protocol is used, and the Diameter is the peer-to-peer protocol. Both ends of the protocol can be used as the client or server to send and receive messages. The third-party application server and PCRF entity use XML-based protocol communication, and the XML-based protocol, whether SOAP or Rest, is a standard C/S mode, ie client-server mode, in this mode can only be used as a client. The third-party application server actively sends a message to the PCRF entity that is the server, and the PCRF entity cannot initiate the message actively.

1 is a flowchart of Embodiment 1 of a method for processing a user plane event according to the present invention. The method provided in this embodiment may be performed by a user plane event processing device, and the device may be integrated on a PCRF entity or an intermediate network element device. The method provided by the example includes the following steps:

Step 101: The PCRF entity establishes a long connection with the AF entity.

In this embodiment, the PCRF entity can directly establish a long connection with the AF entity, or the PCRF entity establishes a long connection with the AF entity through the intermediate network element. When the PCRF entity directly establishes a long connection with the AF entity, an XML-based protocol is used between the PCRF entity and the AF entity, which may be a SOAP protocol or a Rest protocol. When the PCRF entity establishes a long connection with the AF entity through the intermediate network element, an XML-based protocol is used between the intermediate network element and the AF entity, and the Diameter protocol is used between the PCRF entity and the intermediate network element, because the PCRF entity and the intermediate network element are used. The Diameter protocol is a peer-to-peer protocol. User plane events at the PCRF entity can be directly reported to the intermediate network element, and then reported to the AF entity by the intermediate network element through the established long connection. The intermediate network element can be a gateway or other functional entity such as a protocol conversion unit.

The long connection established between the PCRF entity and the AF entity may be a long connection based on a flow or a long connection based on a long poll. The following is a brief introduction to the Hypertext Transfer Protocol (HTTP) long connection. The HTTP long connection does not need to establish a Transmission Control Protocol (TCP) connection every time an HTTP request is initiated. HTTP long connections use the same TCP connection to handle multiple HTTP requests and responses, also known as HTTP keep-alive, or HTTP connection reuse. There are many advantages to using HTTP long connections. Since TCP connections remain connected after sending data, you can continue to send and receive data over the TCP connection, and less need to establish and close TCP connections, saving new connections for each request. The time required to reduce network traffic, save bandwidth, and, in addition, reduce the latency of subsequent requests due to the TCP connection being maintained. To achieve a long connection, both the client and the server support a long connection. By adding the HTTP connection state to the keep-alive state in the header of the HTTP request and response message, the client and the server pass the connection state. Knowing that you need to establish is an HTTP long connection. Because TCP is a stream-based protocol, the HTTP protocol needs a way to indicate the end of the previous response and the beginning of the latter response to reuse the established connection. Therefore, it requires that the information transmitted in the connection must have a custom message length. Custom message length can be set by

The Content-Length header is implemented.

The following is a brief introduction to server push technology. The basic idea of server push technology is to change the browser's active query information to the server to send information actively. The server sends a batch of data, and the browser displays the data and ensures the connection with the server. So that the server still uses this connection for data transmission. HTTP long connection includes two methods. One is long polling mode. The server blocks the previous response to the client. After the event occurs, the event content is bound to the response and returned to the client. At the same time, the response ends. The client immediately sends a second request, and the server blocks the response waiting for the next event to occur. In the stream-based mode, after the server blocks the client's response, it does not close the response but keeps the connection and sends data to the client through the connection. Through this server push technology, the server side actively sends data to the client.

Step 102: The PCRF entity reports the first user plane event and the second user plane event to the AF entity on the established long connection, where the first user plane event and the second user plane event are non-empty user plane events, PCRF The entity suppresses sending empty user plane events on long connections.

After the PCRF entity establishes a long connection with the AF entity, when the first user plane event and the second user plane event occur, the PCRF entity may actively report the first user plane event and the second user plane event to the AF entity, where A user plane event and a second user plane event are non-empty user plane events, and the PCRF entity suppresses sending empty user plane events on long connections. Specifically, the PCRF entity may carry the user plane event in the user plane event report response message and send it to the AF entity. When the PCRF entity establishes a long connection with the AF entity through the intermediate network element, when the user plane event occurs, the PCRF real The user is notified of the intermediate network element user plane event, and then the intermediate network element carries the user plane event in the user plane event report response message and sends it to the AF entity. The user plane event may specifically be IP-CAN session termination, SDF deactivation, signaling path status notification, IP-CAN type change notification, access network charging information notification, sponsor data connection reporting, access network information reporting, etc. event.

In the method provided by the embodiment, the PCRF entity establishes a long connection with the AF entity, and the PCRF entity reports the first user plane event and the second user plane event to the AF entity on the established long connection, and suppresses sending the empty user plane. The event does not have to establish a connection every time a user plane event needs to be reported, and does not have to send an empty user plane event, thereby reducing network signaling overhead.

2 is a flowchart of a method for processing a user plane event according to a second embodiment of the present invention. In this embodiment, a method for actively reporting a user plane event to an AF entity by using a PCRF on a long-term connection is described. The following steps:

Step 201: The PCRF entity establishes a stream-based long connection with the AF entity.

In this embodiment, the PCRF entity and the AF entity may establish a direct long connection; or the PCRF entity establishes a long connection with the AF entity through the intermediate network element.

Specifically, after the AF entity determines that there is a PCRF entity or an intermediate network element of the connectable XML-based protocol, the AF entity establishes a TCP connection with the PCRF entity or the intermediate network element, where the TCP connection is a TCP long connection, and then Send and receive HTTP messages. In this embodiment, after the first entity user plane event report request message is sent by the AF entity to the PCRF entity, the first user plane event report request message is an HTTP message, and the first user plane event report request is sent. The message is used to establish a flow-based HTTP long connection. After receiving the first user plane event report request, the PCRF entity determines that the first user plane event report request message is used to establish a flow-based HTTP long connection, specifically The first entity plane event report request message sent by the AF entity to the PCRF entity carries the identifier information, which is used to indicate whether the HTTP long connection is based on a flow or a long polling manner. After the PCRF entity determines that the first user plane event report request message is used to establish a flow-based HTTP long connection, an ACK response message is returned to the AF entity, indicating that the HTTP long connection is successfully established.

Step 202: The PCRF entity reports the first user plane event and the second user plane event to the AF entity on the long connection based on the flow.

The PCRF entity reports the first user plane event and the second user plane event to the AF entity on the flow-based long connection. The specific: the PCRF entity receives the first sent by the AF entity on the long connection based on the flow. After the user plane event report request message, the first user plane event report response message and the second user plane event report response message are sent to the AF entity in response to the first user plane event report request message, where The first user plane event report response message includes the first user plane event, and the second user plane event report response message includes the second user plane event; or the PCRF entity sends the intermediate user element to the intermediate network element based on the long connection based on the flow a first user plane event and a second user plane event, so that the intermediate network element receives the first user plane event report request message sent by the AF entity on the long connection based on the flow, and then the AF entity on the long connection based on the flow Sending a first user plane event report response message and a second user plane event report response message in response to the first user plane event report request message, where the first user plane event report response message includes the first user plane event, the second user The second event surface response event is included in the face event report response message. The first user plane event and the second user plane event are non-empty user plane events.

Specifically, after the PCRF entity returns an ACK response message to the AF entity, the PCRF entity does not disconnect the HTTP long connection, but keeps the connection waiting for the corresponding user plane event to occur. When the first user plane event is detected, the AF entity is detected. The first user plane event is reported, and the PCRF entity may send the corresponding parameter of the user plane event to the AF entity in the first user plane event report response. After the first user plane event is reported, the PCRF entity maintains the HTTP long connection and continues to wait for the user plane event to occur. When the second user plane event occurs, the second user plane event is reported to the AF entity. It can be understood that, in this embodiment, after receiving the first user plane event request message sent by the AF entity, the PCRF entity or the intermediate network element can not only report two user plane event report response messages to the AF entity, that is, the first A user plane event report response message and a second user plane event report response message may also return multiple user plane event report response messages in response to the first user plane event, and each user plane event report response message includes a user. Face event.

In a long stream-based connection, the HTTP long connection uses a multi-answer method, the client sends a request message, and the server can return multiple messages in the form of a stream, that is, every time the PCRF entity detects a user plane event, The user plane event can be reported to the AF entity actively, and the AF entity does not need to request the data one by one. The HTTP long connection is not broken, and the HTTP long connection is broken only if the connection is wrong or the connection is reestablished. Of course, the AF entity may also actively terminate the HTTP long connection, and the AF entity sends a termination request message to the PCRF entity to notify the PCRF entity to stop reporting the user plane event, and the PCRF entity disconnects the HTTP long connection after receiving the termination request message. .

The method provided in this embodiment, the PCRF entity and the AF entity establish a long connection based on the flow, After receiving the first user plane event report request message, waiting for the user plane event to occur, when the user plane event occurs, sending the first user plane event report response message and the second user to the AF entity on the stream-based long connection The first event response message includes a first user plane event, and the second user plane event response message includes a second user plane event, and the PCRF entity actively reports the user plane event to the AF entity. With this method, the AF entity can cause the PCRF entity to actively report the user plane event to the AF entity by detecting the user plane event once, and suppress the sending of the empty user plane event, without having to have the user face every time. The event needs to establish a connection when reporting, and does not have to send an empty user plane event, thereby effectively reducing network signaling overhead.

3 is a flowchart of a third embodiment of a method for processing a user plane event according to the present invention. In this embodiment, a PCRF entity actively reports a user plane event to an AF entity on a long connection based on a long polling. The method specifically includes the following steps:

Step 301: The PCRF entity establishes a long connection based on long polling with the AF entity.

In this embodiment, the PCRF entity and the AF entity can directly establish a long connection. Alternatively, the PCRF entity establishes a long connection with the AF entity through the intermediate network element.

Specifically, after the AF entity determines that there is a PCRF entity or an intermediate network element of the connectable XML-based protocol, the AF entity establishes a TCP connection with the PCRF entity or the intermediate network element, and the TCP connection is a TCP long connection, which is established. After the TCP connection, the AF entity sends a first user plane event report request message and a second user plane event report request message to the PCRF entity, where the first user plane event report request message and the second user plane event report request message are HTTP messages. The first user plane event reporting request message is used to establish a long polling-based HTTP long connection, and after receiving the first user plane event reporting request message, the PCRF entity reports the request message according to the first user plane event. The carried identification information determines that the first user plane event report request message is used to establish a long polling-based HTTP long connection, and then maintains an HTTP connection, waiting for the first user event to occur, when detecting that the first user plane event occurs, The PCRF entity reports the first user plane event to the AF entity, or sends the user plane event to the intermediate network element, Between NE reports to the AF entity. Similarly, the second user plane event reporting request message is also used to establish a long long polling based HTTP connection, the PCRF entity maintains an HTTP connection, waits for a second user event to occur, and when a second user event is detected, the PCRF entity Reporting a second user plane event to the AF entity.

Step 302: The PCRF entity reports the first user to the AF entity on the long connection based on the long polling Face events and second user face events.

The PCRF entity reports the first user plane event and the second user plane event to the AF entity by using the long polling-based push mode on the long polling-based long connection. The PCRF entity receives the long round-based long connection. After the first user plane event report request message and the second user face report request message sent by the AF entity, the first user plane event report response message and the second user face event report are sent to the AF entity on the long polling based long connection. The first user plane event reporting response message is responsive to the first user plane event reporting request message, and the second user plane event reporting response message is responsive to the second user plane event reporting request message, the first user plane event reporting message. The response message includes a first user plane event, and the second user plane event report response message includes a second user plane event.

Or the PCRF entity sends the first user plane event and the second user plane event to the intermediate network element on the long connection based on the long polling, so that the intermediate network element receives the AF entity sending on the long connection based on the long polling. After the first user plane event reporting request message and the second user plane event reporting request message, the first user plane event reporting response message and the second user plane event reporting response message are sent to the AF entity on the long polling based long connection. The first user plane event reporting response message is responsive to the first user plane event reporting request message, and the second user plane event reporting response message is responsive to the second user plane event reporting request message, the first user plane event reporting response message The first user plane event is included, and the second user plane event report response message includes a second user plane event.

Specifically, the PCRF entity receives the user plane event report request message sent by the AF entity, and determines that the user plane event report request message is used to establish a long polling-based HTTP long connection, which is different from the HTTP short connection, not immediately to the AF The entity returns a response message, but waits for the occurrence of the user plane event. When the user plane event is detected, the user plane event is reported to the AF entity. Specifically, the PCRF entity includes the corresponding information of the user plane event in the user plane event report. The response message is sent to the AF entity, or the user plane event is sent to the intermediate network element, and the intermediate network element includes the corresponding information of the user plane event in the user plane event report response message, and sends the message to the AF entity, and sends the user plane event. Disconnect the long polling based HTTP long connection after reporting the response message.

It should be noted that, in this embodiment, after the TCP long connection is established, the PCRF entity can report not only two user plane events, that is, the first user plane event and the second user plane event, and the AF entity can send more to the PCRF entity. The user plane event reporting request message, the PCRF returns a user plane event reporting response message to each user plane event reporting message, and the user plane event reporting response message carries the user plane event. According to the above description, in the long polling-based push mode, when the PCRF entity reports a user plane event to the AF entity, the HTTP long connection is disconnected. After receiving the user plane event reported by the PCRF entity, the AF entity sends a user plane event report request message to the PCRF entity again, and re-establishes a long long polling-based HTTP long connection. Then, after receiving the request message, the PCRF entity receives the request message. , waiting for a user face event to occur. Different from the flow-based push mode, in the flow-based push mode, the PCRF entity does not need to disconnect the HTTP long connection after reporting the user plane event, and keeps the connection waiting for the user plane event to occur and reports the user plane event.

In the method provided in this embodiment, a long-based polling-based long connection is established between the PCRF entity and the AF entity, and the PCRF entity receives the first user plane event report request message and the second user plane event report request message sent by the AF entity. Waiting for a user plane event to occur, and transmitting a first user plane event report response message to the first user plane event request message to the AF entity on the long connection based on the long polling when the user plane event occurs, sending the first user plane event request message to the AF entity The user plane event response message is responsive to the second user plane event request message, and the PCRF entity actively reports the user plane event to the AF entity. On the other hand, the method provided in this embodiment can implement the sending and receiving of multiple HTTP packets by establishing a TCP connection. The AF entity needs to establish a TCP connection with the PCRF entity every time the packet is sent. Each time a TCP connection is established, a three-way handshake is required, and the release requires four handshakes. The establishment and release of the TCP connection also takes time and resources, and suppresses the sending of empty user plane events, and does not have to report every time there is a user plane event. When a connection is established, it is not necessary to send an empty user plane event, thereby effectively reducing network signaling overhead.

4 is a flowchart of Embodiment 4 of a method for processing a user plane event according to the present invention. The method provided in this embodiment may be performed by a user plane processing device, where the device is integrated on an AF entity, where the AF entity may be a World Wide Web (World Wide) Web, referred to as WEB) server, video server, File Transfer Protocol (FTP) server and mail server. The method provided by this embodiment includes the following steps:

Step 401: The AF entity establishes a long connection with the PCRF entity.

In this embodiment, the AF entity establishes a long connection with the PCRF entity after the session establishment is completed. Specifically, when the UE accesses the service to the AF entity, after the AF entity establishes a connection with the UE, the AF entity searches for a connectable PCRF entity according to the Internet Protocol (IP) address of the UE. Specifically, the AF entity is configured according to the The IP address of the UE acquires a Public Land Mobile Network (PLMN) of the UE, and the PLMN may be a home public land mobile The Home Public Land Mobile Network (HPLMN) may also be a visit to the Public Land Mobile Network (VPLMN) VPLMN, and then the AF entity determines whether the PCRF entity in the PLMN supports the XML-based protocol. Support, then establish a long connection with the PCRF entity.

The AF entity and the PCRF entity can directly establish a long connection; or the AF entity establishes a long connection with the PCRF entity through the intermediate network element. When the AF entity establishes a long connection with the PCRF entity through the intermediate entity, the AF entity needs to find the intermediate network element before establishing the long connection. Generally, the corresponding relationship between the AF entity and the PCRF entity is pre-configured on the AF entity. After the session is established, the AF entity can obtain the connectable intermediate network element and establish a long connection with the configuration information. The long connection established between the AF entity and the PCRF entity may be a long connection based on a flow or a long connection based on a long polling.

Step 402: The AF entity receives, on the established long connection, a first user plane event and a second user plane event reported by the PCRF entity, where the first user plane event and the second user plane event are non-empty user plane events. .

When the long connection established between the AF entity and the PCRF entity is a long connection based on the flow, the AF entity receives the first user plane event and the second user plane reported by the PCRF entity in the flow-based push manner on the long connection based on the flow. Event, and when the long connection established between the AF entity and the PCRF entity is a long connection based on long polling, the AF entity receives the PCRF entity on the established long poll-based long connection and reports it in a long polling manner. The first user plane event and the second user plane event.

In this embodiment, the AF entity establishes a long connection with the PCRF entity, and the PCRF entity reports the user plane event to the AF entity through the established long connection, and suppresses sending the empty user plane event, and does not need to report the user plane event every time. The connection is established and there is no need to send an empty user plane event, thereby reducing network signaling overhead.

On the basis of the fourth embodiment, in a feasible implementation manner, step 402 is specifically: the AF entity receives the first user plane event and the first reported by the PCRF entity by using the flow-based push manner on the long connection based on the flow. A user plane event, or the AF entity receives the first user plane event and the second user plane event reported by the PCRF entity in the long polling based push mode on the long polling based long connection.

The first user plane event and the second user plane event reported by the AF entity to receive the PCRF entity on the flow-based long connection are specifically: the AF entity sends the first use to the PCRF entity on the long connection based on the flow. After the user event report request message, the first user plane event report response message and the second user plane event report response message sent by the PCRF entity are received on the long connection based on the flow, in response to the first user plane event report request message, The first user plane event report response message includes a first user plane event, and the second user plane event report response message includes the second user plane event; or, the AF entity sends the first network element to the intermediate network element on the flow-based long connection. After the user plane event report request message, the first user plane event report response message and the second user face report response message sent by the intermediate network element are received on the long connection based on the flow, and the first user face report request message is sent, The user plane event report response message includes a first user plane event, and the second user face report response message includes a second user plane event, where the first user plane event and the second user plane event are sent by the PCRF entity to the intermediate network element. of.

When the PCRF entity reports the user plane event to the AF entity by using the flow-based push mode, after the AF entity establishes a TCP long connection with the PCRF entity, the AF entity only needs to send a user plane event report request message to establish a flow-based HTTP length. After the connection, the PCRF entity can report the user plane event to the AF entity through the HTTP long connection, and after reporting the user plane event, does not disconnect the HTTP long connection, but continues to wait for the user plane event to occur. Thus, multiple user plane events can be reported by one setup. The HTTP long connection is disconnected only when the connection is faulty or the connection is reestablished. Otherwise, the PCRF entity can always report the user plane event to the AF entity.

The first user plane event and the second user plane event reported by the AF entity to receive the PCRF entity on the long connection based on the long polling are specifically: the AF entity sends the first user plane event to the PCRF entity on the long connection based on the long polling After the report request message and the second user face report request message, the first user plane event report response message and the second user plane event report response message sent by the PCRF entity are received on the long connection based on the long poll, the first user plane The event reporting response message is responsive to the first two user plane event reporting request message, and the second user plane event reporting response message is responsive to the second user plane event reporting request message, where the first user plane event reporting response message includes the first message The user plane event, the second user plane event report response message includes a second user plane event, where the user plane event report response message is that the PCRF entity waits for the user face after receiving the user plane event report request message sent by the AF entity. The event occurs and is sent when a user plane event occurs.

Or the AF entity sends the first user plane event report request message and the second user plane event report request message to the intermediate network element after the long connection based on the long polling, and connects to the long connection based on the long polling And receiving, by the intermediate network element, the first user plane event report response message and the second user plane event report request message, the first user plane event report response message responding to the first user plane event report request message, and the second user plane event report request response The message responds to the second user plane event report request message, where the first user plane event report response message includes a first user plane event, and the second user plane event report response message includes a second user plane event. The user plane event report response message is that the intermediate network element waits for the PCRF entity to send the user plane event after receiving the user plane event report request message sent by the AF entity, and sends the user plane event after receiving the user plane event sent by the PCRF entity.

When the PCRF entity directly establishes a long connection based on the long polling with the AF entity, the PCRF entity reports the user plane event to the AF entity by using the long polling-based push mode. Specifically, after the AF entity establishes a TCP long connection with the PCRF entity, The AF entity sends a user plane event report request message to the PCRF entity to establish a long long polling-based HTTP long connection. After receiving the user plane event report request message, the PCRF entity waits for the user plane event to occur. When a user plane event occurs, The PCRF entity sends the user plane event to the AF entity in the user plane event report response message, and disconnects the HTTP long connection after sending the user plane event report response message. After the PCRF entity establishes a long polling-based long connection with the AF entity through the intermediate network element, the intermediate network element waits for the PCRF entity to send the user plane event after receiving the user plane event report request message, and receives the PCRF entity sending After the user plane event, the user plane event is included in the user plane event report response message and sent to the AF entity. According to the above description, in the long polling-based push mode, each time a user plane event is reported, an HTTP long connection based on long polling is established, and after the user plane event is reported, the HTTP long connection is disconnected.

FIG. 5 is a flowchart of a fifth embodiment of a user plane event processing method according to the present invention. In this embodiment, a direct flow-based long connection is established by using a PCRF entity and an AF entity as an example. As shown in FIG. 5, this embodiment provides The method includes the following steps:

Step 501: After the session establishment is completed, the AF entity determines an accessible PCRF entity.

The AF entity is aware of the establishment of the AF session, that is, the UE establishes a service connection with the AF entity. The UE carries an IP address, and the AF entity can be a WEB server, a video server, an FTP server, and a mail server. The AF entity obtains the PLMN of the UE according to the IP address of the UE, and the PLMN may be an HPLMN or a VPLMN. Then the AF entity determines whether the PCRF entity in the PLMN supports an XML-based protocol, and if so, establishes a long connection with the PCRF entity. . It can be understood that the PCRF entity information in the PLMN and the PCRF are pre-configured on the AF entity. The protocol supported by the entity. If there is an accessible PCRF entity, step 502 is performed. If there is no PCRF entity that can be accessed, the process ends.

The IP address of the UE may be an IP address translated by the private network/public network through the NAT. In this embodiment, the packet data network gateway (P-GW) and the IP address of the UE at the PCRF entity are used. The IP address of the private network before the conversion, and the UE carries the translated public IP address to the AF entity. In the subsequent process, the two IPs of the UE may be mismatched. Therefore, the private network can be NAT/ The public network mapping entry is sent to the PCRF entity or the P-GW to perform the conversion between the private network and the public network address at the PCRF entity or the P-GW, thereby preventing the gateway device from performing policy and charging control (Policy and Charging Control, Acronym for PCC) rules.

Step 502: The AF entity establishes a TCP connection with the accessible PCRF entity, and establishes a long flow-based connection on the TCP connection.

If the AF entity determines a PCRF entity with a connectable XML-based protocol, the AF entity establishes a TCP link with the IP of the UE and the accessible PCRF entity, and establishes a flow-based HTTP long connection on the TCP link.

Step 503: The AF entity sends a first user plane event report request message to the PCRF entity on the long connection based on the flow.

It should be noted that, after the AF entity establishes a long connection with the PCRF entity, when the AF entity needs to send a message to the PCRF entity, the AF entity can also establish a short connection with the PCRF entity, and send the information by using a traditional short connection form. .

Step 504: The PCRF entity sends an ACK response message to the AF entity on the long connection based on the flow.

After receiving the first user plane event report request message sent by the AF entity, the PCRF entity sends an acknowledgement ACK (Acknowledge) request response to the AF entity in order to notify the AF entity that the long connection is normal and indicates that the PCRF entity has correctly received the request. The ACK response message does not carry a user plane event.

Step 505: After sending the ACK response message to the AF entity on the long connection based on the flow, the PCRF entity does not disconnect the connection with the AF entity, and keeps the connection waiting for the user plane event to occur.

After the PCRF entity sends a user plane event report request response to the AF entity, the HTTP long connection is not disconnected, but the user plane event is awaited. Step 506: When the first user plane event occurs, the PCRF entity sends a first user plane event report response message to the AF entity on the long connection based on the flow.

When the first user plane event occurs, the PCRF entity carries the parameter information of the user plane event in the first user plane event report response and sends the parameter to the AF entity, where the user plane event is specifically IP-CAN session termination, SDF deactivation, and signaling. Let the path status notification, IP-CAN type change notification, access network billing information notification, sponsor data connection use report, access network information and other events. In the reported user plane event, the IP address of the UE is carried, and the IP address carried therein is the public IP address converted by the PCRF entity.

Step 507: The PCRF entity sends a first user plane event report response message, and then keeps the connection, and continues to wait for the second user plane event to occur. When the second user plane event occurs, the second entity reports the event to the AF entity. The user plane event reports a response message.

In the long connection based on the flow, after reporting the first user plane event report response message to the AF entity, the PCRF entity does not disconnect, but keeps the stream-based HTTP long connection and continues to wait for the second user plane event to occur. Repeat steps 505-507. The first user plane event and the second user plane event are non-empty user plane events.

In this embodiment, the PCRF may send the first user plane event report response message and the second user plane event report response message to the AF entity in response to the first user plane event report request message, and the PCRF may also send more to the AF entity. The user plane event reporting response message is in response to the first user plane event reporting request message, and each user plane event reporting response message includes a user plane event.

Step 508: When the AF entity session needs to be terminated, the AF entity sends a session termination message to the PCRF entity, to notify the PCRF entity that the user plane event does not need to be reported.

Step 509: The PCRF entity disconnects the long connection based on the flow.

After receiving the session termination message sent by the AF entity, the PCRF entity disconnects the long connection based on the flow.

In the method provided by the embodiment, the PCRF entity and the AF entity send a plurality of user plane event report response messages to the AF entity by using the flow-based push method by establishing a flow-based long connection, and implementing the PCRF. The entity actively reports the user plane event to the AF entity. The method can not only enable the PCRF entity to actively report the user plane event to the AF entity, but also suppress the sending of the empty user plane event, and does not need to establish a connection every time a user plane event needs to be reported, and does not have to Sending empty user plane events can effectively reduce network signaling overhead.

6 is a flowchart of a method for processing a user plane event according to a sixth embodiment of the present invention. In this embodiment, a long connection based on a long polling is directly established by a PCRF entity and an AF entity as an example. As shown in FIG. 6, the implementation is as shown in FIG. The method provided by the example includes the following steps:

Step 601: After the session establishment is completed, the AF entity determines the accessible PCRF entity.

Refer to the description of step 501 in the fifth embodiment, and details are not described herein again.

Step 602: The AF entity establishes a TCP long connection with the accessible PCRF entity.

If the AF entity determines a PCRF entity with a connectable XML-based protocol, the AF entity will carry a TCP connection with the accessible PCRF entity carrying the UE's IP address, which is a TCP long connection.

Step 603: The AF entity sends a user plane event report request message to the PCRF entity, to establish a long connection based on the long poll.

After establishing a TCP long connection with the PCRF entity, the AF entity establishes a long long polling-based HTTP long connection based on the TCP long connection, and adopts a long polling-based manner to the AF over the long polling-based HTTP long connection. The entity reports a user plane event. It should be noted that, when the AF entity needs to send a message to the PCRF entity, the AF entity may also establish a short connection with the PCRF entity, and send the information by using a traditional short connection and a long connection. The short connection and the long connection are parallel. .

Step 604: After receiving the first user plane event report request message sent by the AF entity, the PCRF entity keeps the connection waiting for the first user plane event to occur.

After receiving the request message by the first user plane event sent by the AF entity, the PCRF entity, and

The HTTP short connection is different. The PCRF entity does not immediately return a response message to the AF entity, but keeps the connection waiting for the first user plane event to occur. When the first user plane event occurs, the first user plane event report response is sent to the AF entity. The message is in response to the first user plane event escalation request message. The user plane events are specifically IP-CAN session termination, SDF deactivation, signaling path status notification, IP-CAN type change notification, access network charging information notification, sponsor data connection reporting, access network information, and the like. . In the reported user plane event, the IP address of the UE is carried, and the IP address carried in the IP address is the public IP address converted by the PCRF entity.

Step 605: After transmitting the first user plane event report response message to the AF entity on the long connection based on the long polling, the PCRF entity disconnects the connection.

When a user plane event occurs, the PCRF entity carries the parameter information of the user plane event on the user plane. The event reporting response message is sent to the AF entity. After the user plane event reporting response message is sent to the AF entity, the HTTP long connection is disconnected, but the TCP connection is not disconnected.

Step 606: After receiving the second user plane event report request message sent by the AF entity, the PCRF entity keeps the connection waiting for the second user plane event to occur.

The first user plane event and the second user plane event are non-empty user plane events.

Step 607: After the PCRF entity sends the second user plane event report response message to the AF entity, the connection is disconnected.

In this embodiment, after receiving the long message of the long polling, the PCRF entity returns a user plane event report response message in response to the user plane event report request message after receiving the user plane event report request message sent by the AF entity. It can be understood that, in this embodiment, after establishing a TCP long connection, the PCRF entity can not only report two user plane events, but the AF sends multiple user plane event report request messages, and accordingly, the PCRF is for each user plane. The event escalation request message returns a user plane event escalation response message.

Step 608: When the AF entity session needs to be terminated, the AF entity sends a session termination message to the PCRF entity, to notify the PCRF entity that the user plane event does not need to be reported.

Step 609: The PCRF entity disconnects the TCP long connection.

After receiving the session termination message sent by the AF entity, the PCRF entity disconnects the TCP long connection. It can be seen from the above description that the long connection based on long polling and the long connection based on flow are different, although in the above two methods, only one TCP long connection needs to be established, but the long connection based on the flow is connected in the TCP long connection. Only one HTTP connection needs to be established, and multiple response messages can be returned. In a long connection based on long polling, multiple HTTP connections need to be established on the TCP connection, and each time an HTTP connection is established, only one response message can be returned.

In the method provided by the embodiment, a long connection based on a long polling is established between the PCRF entity and the AF entity. After receiving the request message sent by the user plane event sent by the AF entity, the PCRF entity waits for the user plane event to occur, and the user occurs. When a face event occurs, the user plane event report response message is sent to the AF entity on the long connection based on the long polling, so that the PCRF entity actively reports the user plane event to the AF entity. On the other hand, the method provided in this embodiment can implement multiple TCP packets transmission and reception by establishing a TCP connection, and suppress sending empty user plane events, and does not need to be established every time a user plane event needs to be reported. Connect, and do not have to send empty user plane events, which reduces network signaling overhead. FIG. 7 is a flowchart of a signaling flow of a method for processing a user plane event according to a seventh embodiment of the present invention. In this embodiment, a direct connection based on a flow is established by using a PCRF entity and an AF entity as an example. As shown in FIG. The method provided by the embodiment includes the following steps:

Step 701: The AF entity senses session establishment, and determines an accessible PCRF entity.

For details, refer to the description of step 501 in the fifth embodiment, and details are not described herein again.

Step 702: The AF entity sends a user plane event report request message to the PCRF entity.

If the AF entity determines a PCRF entity with a connectable XML-based protocol, the AF entity establishes a TCP link with the IP of the UE and the accessible PCRF entity, and establishes a flow-based HTTP long connection on the TCP link. A user plane event report request message is sent to the PCRF entity.

Step 703: The PCRF entity returns an ACK response message to the AF entity.

After receiving the first user plane event report request sent by the AF entity, the PCRF entity returns an ACK response message to the AF entity to notify the AF that the HTTP long connection is successfully established. If the AF entity needs to send a message to the PCRF entity, it can use the traditional one-to-one short connection method for communication.

Step 704: The PCRF entity remains connected, waiting for a user plane event to occur.

After the PCRF entity sends an ACK response message to the AF entity, the HTTP long connection is not disconnected, but the connection is maintained, waiting for the user plane event to occur. In the process, the PCRF entity may receive corresponding information from the Policy and Charging Enforcement Function (PCEF) entity.

Step 705: The PCRF entity sends a user plane event report response message to the AF entity.

If the PCRF entity senses that the user plane event occurs, the corresponding parameter of the user plane event is carried in the user plane event report response message and sent to the AF entity.

Step 706, repeating steps 704 and 705.

After reporting the user plane event, the PCRF entity maintains the HTTP long connection and continues to wait for the user plane to occur. When the user plane event occurs, it reports to the AF entity, that is, steps 704 and 705 are repeated.

Step 707: The AF entity sends a message to the PC.

When the AF entity needs to terminate the session, the AF entity PCRF entity sends a session termination message, notifying that the PCRF does not need to report the user plane event.

For specific implementation manners and technical effects of this embodiment, refer to the description in Embodiment 5, where No longer.

FIG. 8 is a flowchart of a signaling procedure of a method for processing a user plane event according to the eighth embodiment of the present invention. In this embodiment, a long connection based on a long polling is directly established by a PCRF entity and an AF entity, as shown in FIG. The method provided in this embodiment includes the following steps:

Step 801: The AF entity senses session establishment, and determines an accessible PCRF entity.

Step 802: The AF entity sends a user plane event report request message to the PCRF entity.

If the AF entity determines a PCRF entity with a connectable XML-based protocol, the AF entity establishes a TCP link with the IP of the UE and the accessible PCRF entity, and establishes a long poll-based HTTP length on the TCP link. Connect, send a user plane event report request message to the PCRF entity.

Step 803: The PCRF entity maintains an HTTP long connection and waits for a user plane event to occur.

After receiving the first user plane event report request sent by the AF entity, the PCRF entity does not immediately reply to the AF entity, but keeps the connection and waits for the user plane event to occur. During this process, the PCRF entity may receive corresponding information from the PCEF. If the AF entity needs to send a message to the PCRF entity, it can communicate using the traditional one-shot short connection method.

Step 804: The PCRF entity sends a user plane event report response message to the AF entity, and disconnects

HTTP long connection.

If the PCRF entity senses that the user plane event occurs, the corresponding parameter of the user plane event is carried in the user plane event report response message, and is sent to the AF entity, and after reporting the user plane event, the PCRF entity disconnects the HTTP long connection.

Step 805: Repeat steps 802 to 804.

After the PCRF entity reports the user plane event, the HTTP long connection is disconnected, and the AF entity initiates a user plane event report request message to the PCRF entity to establish a long long polling HTTP long connection, that is, repeating steps 802 to 805. .

Step 806: The AF entity sends a session termination message to the PCRF entity.

For specific implementations and technical effects of the embodiment, reference may be made to the description in Embodiment 6, and details are not described herein again. FIG. 9 is a schematic structural diagram of a PCRF entity according to Embodiment 9 of the present invention. As shown in FIG. 9, the PCRF entity provided in this embodiment includes: a long connection establishing module 71 and a user plane event reporting module 72.

The long connection establishing module 71 is configured to establish a long connection with the application function AF entity, and the user plane event reporting module 72 is configured to report the first user plane event and the second user plane event to the AF entity on the established long connection. And suppressing sending an empty user plane event on the long connection, where the first user plane event and the second user plane event are non-empty user plane events.

The long connection establishing module 71 is specifically configured to: establish a long connection directly with the AF entity; or establish a long connection with the AF entity by using the intermediate network element. When the PCRF entity directly establishes a long connection with the AF entity, an XML-based protocol is used between the PCRF entity and the AF entity, which may be a SOAP protocol or a Rest protocol. When the PCRF entity establishes a long connection with the AF entity through the intermediate network element, an XML-based protocol is used between the intermediate network element and the AF entity, and the Diameter protocol is used between the PCRF entity and the intermediate network element, because the PCRF entity and the intermediate network element are used. The Diameter protocol is a peer-to-peer protocol. User plane events at the PCRF entity can be directly reported to the intermediate network element, and then reported to the AF entity by the intermediate network element through the established long connection. The intermediate network element can be a gateway or other functional entity such as a protocol conversion unit.

The long connection established between the PCRF entity and the AF entity may be a long connection based on a flow or a long connection based on a long poll.

The user plane event reporting module 72 is configured to: when the PCRF entity establishes a long connection with the AF entity, the PCRF entity actively reports the user plane event to the AF entity when the user plane event occurs. Specifically, the PCRF entity may send the user plane event to the AF entity in the user plane event report response message. When the PCRF entity establishes a long connection with the AF entity through the intermediate network element, when the user plane event occurs, the PCRF entity notifies the middle. The NE user plane event occurs, and then the intermediate network element carries the user plane event in the user plane event report response message and sends it to the AF entity. The user plane event may specifically be IP-CAN session termination, SDF deactivation, signaling path status notification, IP-CAN type change notification, access network charging information notification, sponsor data connection reporting, access network information reporting, etc. event.

The PCRF entity provided in this embodiment may be used to implement the technical solution provided by the method embodiment 1. The implementation principle and the technical effect are similar, and details are not described herein again.

In a feasible implementation manner of the present invention, the long connection is a long connection based on the flow, and the user plane The event reporting module 72 is specifically configured to: report the first user plane event second user plane event to the AF entity on the long connection based on the flow. The user plane event reporting module 72 reports the first user plane event and the second user plane event to the AF entity on the long connection based on the flow, which is specifically:

After receiving the first user plane event report request message sent by the AF entity on the long connection based on the flow, the user plane event reporting module 72 sends the first user plane event report response message and the second message to the AF entity on the long connection based on the flow. The user plane event report response message is in response to the first user plane event report request message, the first user plane event report response message includes a first user plane event, and the second user plane event report response message includes a second user plane event; Or,

The user plane event reporting module 72 sends the first user plane event and the second user event to the intermediate entity on the flow-based long connection to the AF entity, so that the intermediate network element receives the AF entity sent on the long connection based on the flow. After the first user plane event report request message, the first user plane event report response message and the second user plane event report response message are sent to the AF entity in response to the first user plane event report request message on the flow-based long connection. The first user plane event report response message includes a first user plane event, and the second user plane event report response message includes the second user plane event.

In another possible implementation manner of the present invention, the long connection is a long connection based on long polling; the user plane event reporting module 72 is specifically configured to use a long polling based push mode on a long polling based long connection. The first user plane event and the second user plane event are reported to the AF entity. The user plane event reporting module 72 reports the first user plane event and the first user plane event to the AF entity on the long connection based on the stream length polling push:

The user plane event reporting module 72 waits for the user plane event to occur after receiving the first user plane event reporting request message sent by the AF entity on the long polling based long connection, and occurs in the user plane. The first user plane event report response message and the second user plane event report response message are sent to the AF entity on the long connection based on the long polling, and the first user plane event report response message responds to the first two user planes. The event reporting request message, the second user plane event reporting response message is responsive to the second user plane event reporting request message, where the first user plane event reporting response message includes a first user plane event, and the second user plane event reporting response The message includes the second user plane event; or

The user plane event reporting module 72P sends the first user plane event and the second user plane event to the intermediate network element on the long connection based on the long polling, so that the intermediate network element receives the AF entity on the long connection based on the long polling. After sending a user plane event report request message and a second user face event report After the message is obtained, the first user plane event report response message and the second user plane event report response message are sent to the AF entity on the long connection based on the long polling, and the first user plane event report response message is sent to the first user plane event report. The request message, the second user plane event report response message is responsive to the second user plane event report request message, the first user plane event report response message includes the first user plane event, and the second user plane event report response message includes the second user Face event.

The PCRF provided in this embodiment may be used to perform the technical solution provided by any of the foregoing method embodiments, and the specific implementation manners and technical effects are similar, and therefore are not described again.

FIG. 10 is a schematic structural diagram of an AF entity according to Embodiment 10 of the present invention. As shown in FIG. 10, the AF entity provided in this embodiment includes: a long connection establishing module 81 and a user plane event receiving module 82.

The long connection establishing module 81 is configured to establish a long connection with the policy and charging rule function PCRF entity;

The user plane event receiving module 82 is configured to receive, by the established long connection, the first user plane event and the second user plane event reported by the PCRF entity, where the first user plane event and the second user plane event are non-empty users. Face event.

The AF entity in this embodiment may be used to implement the technical solution provided in the fourth embodiment, and the implementation principle and technical effects are similar, and details are not described herein again.

In this embodiment, the long connection establishing module 81 is specifically configured to: directly establish a long connection with the PCRF entity; or establish a long connection with the PCRF entity by using the intermediate network element.

The long connection may be a long connection based on a flow or a long connection based on a poll. When the long connection established by the long connection establishing module 81 is a long connection based on the flow, the user plane event receiving module 82 is specifically configured to: receive the first user plane event and the second user plane reported by the PCRF entity on the long connection based on the flow event. Specifically, the user plane event receiving module 82 is configured to:

After the first user plane event report request message is sent to the PCRF entity on the flow-based long connection, the first user plane event report response message and the second user plane event report response message sent by the PCRF entity are received on the flow-based long connection. In response to the first user plane event report request message, the first user plane event report response message includes a first user plane event, and the second user plane event report response message includes a second user plane event; or

After the first user plane event report request message is sent to the intermediate network element, the first user plane event report response message and the second user plane event report sent by the intermediate network element are received on the flow-based long connection. Responding to the first user plane event report request message in response to the message, the first user The face event report response message includes a first user plane event, and the second user plane event report response message includes a second user plane event.

When the long connection established by the long connection establishment module 81 is a long connection based on the long polling, the user plane event receiving module 82 is specifically configured to: receive the first reported by the PCRF entity or the intermediate network element on the long connection based on the long polling User plane events and second user plane events. Specifically, the user plane event receiving module 82 is used to:

After the first user plane event reporting request message and the second user plane event reporting request message are sent to the PCRF entity on the long connection based on the long polling, the first user sent by the PCRF entity is received on the long polling based long connection. The first user plane event reporting response message and the second user plane event reporting response message are responsive to the first two user plane event reporting request messages, and the second user plane event reporting response message is responsive to the second user plane event reporting. The request message, the first user plane event report response message includes a first user plane event, and the second user plane event report response message includes a second user plane event; or

After the first user plane event reporting request message and the second user plane event reporting request message are sent to the intermediate network element on the long connection based on the long polling, the first sending of the intermediate network element is received on the long connection based on the long polling The user plane event report response message and the second user plane event report request message, the first user plane event report response message responds to the first user plane event report request message, and the second user plane event report response message responds to the second user plane event report request message. The first user plane event report response message includes a first user plane event, and the second user plane event report response message includes a second user plane event.

In this embodiment, the long connection establishing module 81 is specifically configured to establish a long connection with the PCRF entity after the session establishment is completed, and then report the user plane event to the AF entity through the long connection.

The AF entity of this embodiment may be used to perform the technical solution provided by any of the foregoing method embodiments, and the implementation principle and technical effects are similar, and details are not described herein again.

FIG. 11 is a schematic structural diagram of a PCRF entity according to Embodiment 11 of the present invention. As shown in FIG. 11, the PCRF entity 900 provided in this embodiment includes: a processor 91 and a memory 92. The PCRF entity 900 may further include a transmitter 93. Receiver 94. Transmitter 93 and receiver 94 can be coupled to processor 91 via a bus. The memory 92 stores execution instructions. When the PCRF entity is running, the processor 91 communicates with the memory 92, and the processor 91 executes the execution instructions so that the PCRF entity executes the user plane event processing method provided by the present invention. In this embodiment, the processor 91 is configured to execute the following Operation:

Establishing a long connection with the application function AF entity through the receiver 94;

The first user plane event second user plane event is reported to the AF entity by the transmitter 93 on the established long connection, and the null user plane event is suppressed on the long connection, wherein the first user plane event and the second user plane The event is a non-empty user plane event.

The PCRF entity can establish a long connection directly with the AF entity. Alternatively, the PCRF entity establishes a long connection with the AF entity through the intermediate network element.

The PCRF entity establishes a long connection with the AF entity as a long flow-based connection, and the processor 91 is specifically configured to: report the first user plane event and the second user plane event to the AF entity on the long connection based on the flow.

Specifically, after the receiver 94 receives the first user plane event report request message sent by the AF entity on the long connection based on the flow, the processor 91 controls the transmitter 93 to send the first to the AF entity on the long connection based on the flow. The user plane event report response message and the second user plane event report response message are in response to the first user plane event report request message, where the first user plane event report response message includes a first user plane event, and the second user plane event report The response message includes a second user plane event; or,

The transmitter 93 sends the first user plane event and the second user plane event to the intermediate network element on the long connection based on the flow, so that the intermediate network element receives the first user plane event sent by the AF entity on the long connection based on the flow. After the request message is reported, the first user plane event report response message and the second user plane event report response message are sent to the AF entity in response to the first user plane event report request message, and the first user plane event report is sent on the flow-based long connection. In response to the first user plane event in the message, the second user plane event reporting response message includes a second user plane event.

The PCRF entity establishes a long connection with the AF entity as a long connection based on the long polling, and the processor 91 is specifically configured to: report the first user plane event and the second user plane event to the AF entity on the long connection based on the long polling.

Specifically, the receiver 94 receives the first user plane event report request message sent by the AF entity on the long connection based on the long poll, and the second user plane event report request message is sent on the long connection based on the long poll. Sending a first user plane event report response message and a second user plane event report response message to the AF entity, the first user plane event report response message responding to the first two user plane event report request messages, and the second user plane event report response message Responding to the second user plane event escalation request The first user plane event report response message includes a first user plane event, and the second user plane event report response message includes a second user plane event;

Or the PCRF entity sends the first user plane event and the second user plane event to the intermediate network element on the long connection based on the long polling, so that the intermediate network element receives the AF entity sending on the long polling based long connection. After the first user plane event reporting request message and the second user plane event reporting request message, the first user plane event reporting response message and the second user plane event reporting response message are sent to the AF entity on the long polling based long connection. The first user plane event reporting response message is responsive to the first user plane event reporting request message, the second user plane event reporting response message is responsive to the second user plane event reporting request message, and the first user plane event reporting response message includes the first user. The second user plane event report response message includes a second user plane event.

The PCRF provided in this embodiment may be used to implement the technical solution of the foregoing method embodiments. The principle and the technical effects are similar, and details are not described herein again.

FIG. 12 is a schematic structural diagram of an AF entity according to Embodiment 12 of the present invention. As shown in FIG. 12, the AF entity 100 provided in this embodiment includes: a processor 11 and a memory 12, and the AF entity 100 may further include a transmitter 13 and The receiver 14, the transmitter 13 and the receiver 14, and the memory 12 can all be connected to the processor 11 via a bus. The memory 11 stores execution instructions. When the AF entity is running, the processor 11 communicates with the memory 12, and the processor 11 executes the execution instructions so that the AF entity executes the user plane event processing method provided by the embodiment. The processor 11 is specifically configured to perform the following operations:

The processor 11 establishes a long connection with the charging rule function PCRF entity by controlling the transmitter 13; the processor 11 receives the first user plane event and the second user plane event reported by the PCRF entity on the established long connection by controlling the receiver 14. The first user plane event and the second user plane event are non-empty user plane events.

In this embodiment, the AF entity establishes a direct long connection with the PCRF entity; or the AF entity establishes a long connection with the PCRF entity through the intermediate network element. Specifically, the AF entity establishes a long connection with the PCRF entity after the session establishment is completed. Among them, long connections are long connections based on flows, or long connections based on polling.

If the long connection is a long stream-based connection, the receiver 14 receives the first user plane event and the second user plane event reported by the PCRF entity in the flow-based push mode on the flow-based long connection under the control of the processor 11. . Specifically, after the transmitter 13 sends the first user plane event report request message to the PCRF entity on the long connection based on the flow, the receiver 14 receives the first user plane event report response message sent by the PCRF entity on the long connection based on the flow. The second user plane event reporting response message is in response to the first user plane event reporting request message, the first user plane event reporting response message includes a user plane event, and the second user plane event reporting response message includes the second user plane event; or ,

After the transmitter 13 sends the first user plane event report request message to the intermediate network element on the long connection based on the flow, the receiver 14 receives the first user plane event report response message sent by the intermediate network element on the long connection based on the flow and The second user plane event report response message is sent to the first user plane event report request message, the first user plane event report response message includes the first user plane event, and the second user plane event report response message includes the second user plane event. .

If the long connection is a long connection based on long polling, the processor 11 controls the receiver 14 to receive the first user plane event and the second user plane event reported by the PCRF entity on the long connection based on the long poll.

Specifically, after the transmitter 13 sends the first user plane event report request message to the PCRF entity on the long poll-based long connection, the receiver 14 receives the first sent by the PCRF entity on the long poll-based long connection. The user plane event report response message and the second user plane event report response message, the first user plane event report response message is responsive to the first two user plane event report request messages, and the second user plane event report response message Responding to the second user plane event report request message, the first user plane event report response message includes the first user plane event, and the second user plane event report response message includes the second user plane event.

Alternatively, after the transmitter 13 sends the first user plane event report request message and the second user plane event report request message to the intermediate network element on the long connection based on the long poll, the receiver 14 is on the long connection based on the long poll. Receiving the first user plane event report response message and the second user plane event report request message sent by the intermediate network element, the first user plane event report response message responding to the first user plane event report request message, and the second user plane event report response message In response to the second user plane event report request message, the first user plane event report response message includes a first user plane event, and the second user plane event report response message includes a second user plane event.

It will be understood by those skilled in the art that all or part of the steps of implementing the foregoing method embodiments may be performed by hardware related to program instructions, and the foregoing program may be stored in a computer readable In the storage medium, when the program is executed, the steps including the foregoing method embodiments are performed; and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk or an optical disk.

Finally, it should be noted that the above embodiments are only for explaining the technical solutions of the present invention, and are not intended to be limiting thereof; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art will understand that The technical solutions described in the foregoing embodiments may be modified, or some or all of the technical features may be equivalently replaced; and the modifications or substitutions do not deviate from the technical solutions of the embodiments of the present invention. range.

Claims

claims

1. A user plane event processing method, characterized by including:

The policy and charging rule function PCRF entity establishes a persistent connection with the application function AF entity; the PCRF entity reports the first user plane event and the second user plane event to the AF entity on the established persistent connection, where, The first user plane event and the second user plane event are non-empty user plane events, and the PCRF entity suppresses sending empty user plane events on the long connection.

2. The method according to claim 1, characterized in that the long connection is a long connection based on streams;

The PCRF entity reports the first user plane event and the second user plane event to the AF entity on the long flow-based connection.

3. The method according to claim 2, characterized in that, the PCRF entity reports the first user plane event and the second user plane event to the AF entity on the long flow-based connection, include:

The PCRF entity receives the first user plane event reporting request message sent by the AF entity on the persistent flow-based connection, and sends the first user plane event report to the AF entity on the persistent flow-based connection. The response message and the second user plane event reporting response message are in response to the first user plane event reporting request message, the first user plane event reporting response message contains the first user plane event, the second user plane The event reporting response message contains the second user plane event; or,

The PCRF entity sends the first user plane event and the second user plane event to the intermediate network element on the long flow-based connection, so that the intermediate network element receives the first user plane event on the long flow-based connection. After the first user plane event reporting request message is sent by the AF entity, the first user plane event reporting response message and the second user plane event reporting response message are sent to the AF entity on the flow-based persistent connection in response. The first user plane event reporting request message, the first user plane event reporting response message includes the first user plane event, and the second user plane event reporting response message includes the second user plane event .

4. The method according to claim 1, characterized in that: the long connection is a long connection based on long polling; The PCRF entity reports the first user plane event and the second user plane event to the AF on the established long connection, including:

The PCRF entity reports the first user plane event and the second user plane event to the AF entity on the long polling-based long connection.

5. The method according to claim 4, characterized in that, the PCRF entity reports the first user plane event and the second user plane event to the AF entity on the long polling-based long connection. events, including:

The PCRF entity receives the first user plane event reporting request message and the second user plane event reporting request message sent by the AF entity on the long polling-based long connection. A first user plane event reporting response message and a second user plane event reporting response message are sent to the AF entity, and the first user plane event reporting response message responds to the first two user plane event reporting request messages, so The second user plane event reporting response message responds to the second user plane event reporting request message, the first user plane event reporting response message contains the first user plane event, and the second user plane event reporting response message The message contains the second user plane event; or,

The PCRF entity sends the first user plane event and the second user plane event to the intermediate network element on the long polling-based long connection, so that the intermediate network element can After receiving the first user plane event reporting request message and the second user plane event reporting request message sent by the AF entity, send the first user plane event reporting request message to the AF entity on the long polling-based long connection. response message and a second user plane event reporting response message, the first user plane event reporting response message responds to the first user plane event reporting request message, and the second user plane event reporting response message responds to the second user A plane event reporting request message, the first user plane event reporting response message includes the first user plane event, and the second user plane event reporting response message includes the second user plane event.

6. A user plane event processing method, characterized by including:

The application function AF entity establishes a persistent connection with the policy and charging rules function PCRF entity; the AF entity receives the first user plane event and the second user plane event reported by the PCRF entity on the established persistent connection, where, The first user plane event and the second user plane event are non-null user plane events.

7. The method according to claim 6, characterized in that the long connection is a stream-based long connection. connect;

The AF entity receives the first user plane event and the second user plane event reported by the PCRF entity on the established long connection, including:

The AF entity receives the first user plane event and the second user plane event reported by the PCRF entity on the long flow-based connection.

8. The method according to claim 7, characterized in that, the AF entity receives the first user plane event and the second user plane event reported by the PCRF entity on the long flow-based connection. , include:

After the AF entity sends a first user plane event reporting request message to the PCRF entity on the persistent flow-based connection, the AF entity receives the first user plane event sent by the PCRF entity on the persistent flow-based connection. The reporting response message and the second user plane event reporting response message are in response to the first user plane event reporting request message, the first user plane event reporting response message contains the first user plane event, and the second user The second user plane event is included in the plane event reporting response message; or,

After the AF entity sends the first user plane event reporting request message to the intermediate network element on the persistent flow-based connection, the AF entity receives the first user plane event sent by the intermediate network element on the persistent flow-based connection. The reporting response message and the second user plane event reporting response message are in response to the first user plane event reporting request message, the first user plane event reporting response message contains the first user plane event, and the second user The second user plane event is included in the plane event reporting response message.

9. The method according to claim 6, characterized in that the long connection is a long connection based on long polling;

10. The method according to claim 9, characterized in that, the AF entity receives the first user plane event and the second user plane event reported by the PCRF entity on the long polling-based long connection. Faced events include:

After the AF entity sends the first user plane event reporting request message and the second user plane event reporting request message to the PCRF entity on the long polling-based long connection, Receive the first user plane event reporting response message and the second user plane event reporting response message sent by the PCRF entity on the polling long connection, and the first user plane event reporting response message responds to the first two user planes an event reporting request message, the second user plane event reporting response message responds to the second user plane event reporting request message, the first user plane event reporting response message includes the first user plane event, and the The second user plane event reporting response message contains the second user plane event; or,

After the AF entity sends the first user plane event reporting request message and the second user plane event reporting request message to the intermediate network element on the long polling-based long connection, after the long polling-based long connection The connection receives the first user plane event reporting response message and the second user plane event reporting request message sent by the intermediate network element, and the first user plane event reporting response message responds to the first user plane event reporting request message, The second user plane event reporting response message responds to the second user plane event reporting request message, the first user plane event reporting response message contains the first user plane event, and the second user plane event reporting response message The response message contains the second user plane event.

11. The method according to any one of claims 6 to 10, wherein the AF entity establishes a long connection with the PCRF entity, including:

After the session establishment is completed, the AF entity establishes a long connection with the PCRF entity.

12. A policy and charging rule function PCRF entity, characterized in that it includes: a long connection establishment module, used to establish a long connection with the application function AF entity;

The user plane event reporting module is configured to report the first user plane event and the second user plane event to the AF entity on the established long connection, and suppress the sending of empty user plane events on the long connection, where , the first user plane event and the second user plane event are non-null user plane events.

13. The PCRF entity according to claim 12, characterized in that the long connection establishment module is specifically used for:

The long connection is established directly with the AF entity; or, the long connection is established with the AF entity through an intermediate network element.

14. The PCRF entity according to claim 13, wherein the long connection is a flow-based long connection;

The user plane event reporting module is specifically configured to report the first user plane event and the second user plane event to the AF entity on the flow-based persistent connection.

15. The PCRF entity according to claim 14, characterized in that the user plane event reporting module is specifically used to:

Receive the first user plane event reporting request message sent by the AF entity on the long flow-based connection, and send the first user plane event reporting response message and the first user plane event reporting response message to the AF entity on the long flow-based connection. The second user plane event reporting response message is in response to the first user plane event reporting request message, the first user plane event reporting response message contains the first user plane event, and the second user plane event reporting response message contains the second user plane event; or,

Send the first user plane event and the second user plane event to the intermediate network element on the long flow-based connection, so that the intermediate network element receives the first user plane event on the long flow-based connection. After the AF entity sends the first user plane event reporting request message, it sends the first user plane event reporting response message and the second user plane event reporting response message to the AF entity on the flow-based persistent connection in response to the A first user plane event reporting request message, the first user plane event reporting response message includes the first user plane event, and the second user plane event reporting response message includes the second user plane event.

16. The PCRF entity according to claim 13, characterized in that the long connection is a long connection based on long polling;

The user plane event reporting module is specifically configured to report the first user plane event and the second user plane event to the AF entity on the long polling-based long connection.

17. The PCRF entity according to claim 16, characterized in that the user plane event reporting module is specifically used to:

Receive the first user plane event reporting request message and the second user plane event reporting request message sent by the AF entity on the long polling-based long connection, and send the first user plane event reporting request message to the long polling-based long connection on the long polling-based long connection. The AF entity sends a first user plane event reporting response message and a second user plane event reporting response message. The first user plane event reporting response message responds to the first two user plane event reporting request messages. The second user The plane event reporting response message responds to the second user plane event reporting request message, the first user plane event reporting response message includes the first user plane event, and the second user plane event reporting response message includes the the second user plane event; or, send the first user plane event and the second user plane event to the intermediate network element on the long polling-based long connection, so that the intermediate network element can The first user plane event reporting request message and the second user plane event reporting request message sent by the AF entity are received on the long polling long connection. After receiving the message, the first user plane event reporting response message and the second user plane event reporting response message are sent to the AF entity on the long polling-based long connection, and the first user plane event reporting response message responds to the The first user plane event reporting request message, the second user plane event reporting response message responds to the second user plane event reporting request message, and the first user plane event reporting response message includes the first user plane event reporting request message. event, and the second user plane event reporting response message contains the second user plane event.

18. An application function AF entity, characterized by including:

A persistent connection establishment module, configured to establish a persistent connection with the Policy and Charging Rules Function PCRF entity; A user plane event receiving module, configured to receive the first user plane event and the third user plane event reported by the PCRF entity on the established persistent connection. Two user plane events, wherein the first user plane event and the second user plane event are non-null user plane events.

19. The AF entity according to claim 18, characterized in that the long connection establishment module is specifically used for:

The long connection is established directly with the PCRF entity; or, the long connection is established with the PCRF entity through an intermediate network element.

20. The AF entity according to claim 19, wherein the persistent connection is a stream-based persistent connection;

The user plane event receiving module is specifically configured to receive the first user plane event and the second user plane event reported by the PCRF entity on the long flow-based connection.

21. The AF entity according to claim 20, characterized in that the user plane event receiving module is specifically used for:

After sending the first user plane event reporting request message to the PCRF entity on the long flow-based connection, receiving the first user plane event reporting response message sent by the PCRF entity on the long flow-based connection and The second user plane event reporting response message is in response to the first user plane event reporting request message. The first user plane event reporting response message contains the first user plane event. The second user plane event reporting response message The message contains the second user plane event; or, after sending the first user plane event reporting request message to the intermediate network element on the long flow-based connection, receiving all the user plane events on the long flow-based connection. The first user plane event reporting response message and the second user plane event reporting response message sent by the intermediate network element are in response to the first user plane event reporting request message, and the first user plane event reporting response message contains the The first user interface event, The second user plane event reporting response message includes the second user plane event.

22. The AF entity according to claim 19, characterized in that the long connection is a long connection based on long polling;

The user plane event receiving module is specifically configured to: receive the first user plane event and the second user plane event reported by the PCRF entity on the long polling-based long connection.

23. The AF entity according to claim 22, characterized in that the user plane event receiving module is specifically used to:

After sending the first user plane event reporting request message and the second user plane event reporting request message to the PCRF entity on the long polling-based long connection, receive the The first user plane event reporting response message and the second user plane event reporting response message sent by the PCRF entity, the first user plane event reporting response message responds to the first two user plane event reporting request messages, and the second user plane event reporting response message responds to the first two user plane event reporting request messages. The user plane event reporting response message responds to the second user plane event reporting request message, the first user plane event reporting response message includes the first user plane event, and the second user plane event reporting response message includes The second user plane event; or,

After sending the first user plane event reporting request message and the second user plane event reporting request message to the intermediate network element on the long polling-based long connection, receive all the user plane event reporting requests on the long polling-based long connection. The first user plane event reporting response message and the second user plane event reporting request message sent by the intermediate network element, the first user plane event reporting response message responds to the first user plane event reporting request message, and the second user plane event reporting request message is The user plane event reporting response message responds to the second user plane event reporting request message, the first user plane event reporting response message contains the first user plane event, and the second user plane event reporting response message contains The second user plane event.

24. The AF entity according to any one of claims 18 to 23, characterized in that the long connection establishment module is specifically used for:

After the session establishment is completed, a long connection is established with the PCRF entity.

25. A policy and charging rule function PCRF entity, characterized in that it includes: a processor and a memory, the memory stores execution instructions, and when the PCRF entity is running, communication between the processor and the memory , the processor executes the execution instruction to cause the PCRF entity to execute the method according to any one of claims 1-5.

26. An application function AF entity, characterized by including: a processor and a memory, so The memory stores execution instructions. When the AF entity is running, there is communication between the processor and the memory. The processor executes the execution instructions to cause the AF entity to execute any one of claims 6-12. the method described.