WO2015010576A1 - Session management method, application function entity, policy server and protocol converter - Google Patents

Session management method, application function entity, policy server and protocol converter Download PDF

Info

Publication number
WO2015010576A1
WO2015010576A1 PCT/CN2014/082548 CN2014082548W WO2015010576A1 WO 2015010576 A1 WO2015010576 A1 WO 2015010576A1 CN 2014082548 W CN2014082548 W CN 2014082548W WO 2015010576 A1 WO2015010576 A1 WO 2015010576A1
Authority
WO
Grant status
Application
Patent type
Prior art keywords
af
entity
session
policy server
request message
Prior art date
Application number
PCT/CN2014/082548
Other languages
French (fr)
Chinese (zh)
Inventor
周晓云
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/02Arrangements for maintenance or administration or management of packet switching networks involving integration or standardization
    • H04L41/0246Arrangements for maintenance or administration or management of packet switching networks involving integration or standardization exchanging or transporting network management information using Internet, e.g. aspects relating to embedding network management web servers in network elements, web service for network management purposes, aspects related to Internet applications or services or web-based protocols, simple object access protocol [SOAP]
    • H04L41/0273Arrangements for maintenance or administration or management of packet switching networks involving integration or standardization exchanging or transporting network management information using Internet, e.g. aspects relating to embedding network management web servers in network elements, web service for network management purposes, aspects related to Internet applications or services or web-based protocols, simple object access protocol [SOAP] involving the use of web services for network management, e.g. SOAP
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATIONS NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/12Setup of transport tunnels

Abstract

Disclosed are a session management method, an application function entity, a policy server and a protocol converter, which relate to the field of communications. The method comprises: when an AF entity is establishing an AF session with a policy server, the AF entity sending a first HTTP request message to the policy server, wherein AF session identification information is sent to the policy server by the AF entity through the first HTTP request message, or the AF session identification information is allocated by the policy server and is sent to the AF entity through a response of the first HTTP request message; when the policy server notifies the AF entity of a bearing layer event of the above-mentioned AF session, the policy server sending a second HTTP request message which carries the AF session identification information to the AF entity; and the AF entity returning a response of the second HTTP request message to the policy server.

Description

Session management, application function entity, a policy server and protocol converter TECHNICAL FIELD

The present invention relates to communication field, in particular, to a session management method, an application function entity, a policy server and a protocol converter.

Background technique

Figure 1 is a Third Generation Partnership Project (3rd Generation Partnership Project, referred to as 3GPP) defined policy and charging control architecture (Policy and Charging Control, referred to as PCC).

Policy and Charging Rules Function (Policy and Charging Rules Function, referred to as PCRF) were formulated QoS and charging policy for the business use of network resources. PCRF needs to develop a control strategy in conjunction with information received from the AF service, from a user subscription database (Subscription Profile Repository, abbreviated as SPR) the received user subscription information, the policy configured by the operator, and the like. PCRF delivers the control strategy for the development of business policy and charging enforcement function (Policy and Charging Enforcement Function, referred to as PCEF) or a bearer binding and event reporting function (Bearer Binding and Event Report Function, referred to as BBERF) execution. PCRF to PCEF can simultaneously and / or carrier layer BBERF subscription-related events, to timely sense a carrier layer when the event occurs, and change the control strategy. Further, PCEF and traffic detection function (Traffic Detection Function, referred to as TDF) capable of executing application detection and control function delivered by the PCRF PCC rules (the PCEF) or ADC rules (TDF).

With the development of mobile Internet, operators need to exchange data with third-party application providers, carry out QoS guarantee for third-party application providers to offer data services. Since the Diameter protocol currently supported by PCC Rx interface preclude the use, and for most third-party application data providers, they are better at developing based on SOAP, REST protocol. The industry research PCC architecture supports Rx interface is based on SOAP / REST protocol. Two options are proposed, one is the supporting SOAP or REST protocol PCRF, the PCRF and the other is provided directly called AF protocol converter (Protocol Converter, referred to as PC), a network element, the protocol for the SOAP or REST converted to Diameter. Currently SOAP protocols support XML language, XML and JSON REST protocol support two languages. Rx interface needs to support two-way communication, i.e., AF provides service information to the PCRF, PCRF events necessary to provide the carrier layer (Traffic Plane Event) in real time to the AF. However, SOAP or REST protocols are based on Hypertext Transfer Protocol (Hypertext transfer protocol, referred to as HTTP).

HTTP is a stateless protocol, the client requests a URL, the server-side response, sends back a response content, ports, not two-way communication. In order to achieve the initiative Push server information to the client, the industry proposed the following three options:

1. Polling: browser kept requesting access to the latest data, the analog to push. This solution is determined large delay, a large signaling overhead.

2. Streaming: When the server receives the HTTP request from the client and returns an acknowledgment message, the server and the client connection is not, may continue to send data to the client terminal via the connection server. The disadvantage of this approach is the need to maintain the connection, taking up server resources and clients. Its proxy support is not good, because the proxy may cache data.

3. Long-Polling: requesting a browser, the server to suspend the connection until there is data to be sent to the client, disconnects the finished transactions; client receives the data, once again requests the server to get the data. The disadvantage of this approach is the need to maintain the connection, taking up server resources and clients.

Taking into account the particular application of the PCC, the third party data applications require users to provide services to a large number, so if the preclude the use of Long-Polling Streaming or programs between the application server and the third-party data PCRF or PC to maintain a large number of Transmission Control Protocol ( Transmission Control Protocol, referred to as TCP) connection.

In addition, the relevant agreement also stipulates that only last a maximum of two TCP connections before the HTTP server with a client and, if the extra two HTTP maintain TCP connections, inconsistent with the relevant agreements, leading to interoperability problems.

Related technology is also proposed that a plurality of HTTP requests may be encapsulated in a TCP connection (HTTP Pipelining becomes), and preclude the use of Long-Polling manner unsolicited data server to the client. However, this solution requires the client must be completed after Long-Polling can send a new request, this will cause a delay. SUMMARY

An embodiment provides a session management method, an application function entity, a policy server and a protocol converter according to the present invention, while the two-way communication, reducing the use of network resources, and can ensure real-time. One kind of session management method, comprising:

When an application function (AF) entity and the policy server to establish an AF session, the AF entity sends a first Hypertext Transfer Protocol (HTTP) request message to the policy server;

Wherein, the AF entity by the first HTTP request message transmits an AF session identification information to the policy server; alternatively, the AF entity first HTTP response returned from the policy server the request message acquires AF session identifier information assigned to the policy server AF session;

When the AF entity receives the policy server notifies the event the carrier layer to the AF AF entity session, transmitting to the second HTTP request message AF entity, the second HTTP request message carries the AF session identification information;

The AF entity returns the second HTTP request message to the policy server response. Preferably, the policy server for the policy and charging rules function (PCRF) entity or protocol converter (PC).

Preferably, when the AF entity to modify or terminate the AF session, the AF entity transmits the third HTTP request message to the policy server, the third HTTP request message carries the identification information of an AF session;

HTTP said third entity receives the AF policy server returns the request response message.

Preferably, the AF session identification information is a globally unique identifier.

Preferably, the AF session identification information represented by preclude any combination of the following:

Service session identifier and the IP address of the UE;

Service session identifier, UE IP address and IP domain identifier; service session identifier, UE IP address and a packet data network (PDN) identification; service session identifier and a user identifier. Preferably, the AF entity to support HTTP client and an HTTP server, and the policy server to support HTTP client and an HTTP server. Preferably, the AF entity sends the policy server to the first HTTP request message or the third HTTP request message, comprising:

When the AF entity and the policy server the first transmission control protocol (TCP) connection already exists, the AF entity preclude the first TCP connection to the policy server sending the first HTTP request message or the The third HTTP request message;

The AF entity and the policy server is not established when the first TCP connection, establishing the first AF first TCP connection to the policy server, then sending the first HTTP request message or the third HTTP request news.

Preferably, the AF entity receives the policy server transmits a first HTTP request message or the response message of the third HTTP request, reserving the AF between the entity and the policy server a first TCP connection; or

The AF entity receives the policy server transmits a first HTTP request message or the third HTTP request response message, and disconnecting the AF between the first entity and the policy server TCP connection. One kind of session management method, comprising:

Policy server receives an application function (AF) carrying the AF entity sends the session identifier information with a first Hypertext Transfer Protocol (HTTP) request message, returning a first HTTP response request message to the AF entity; or receive AF entity a first HTTP request message sent, session identification information is assigned AF AF session, the AF entity to return the AF carrying the session identification information is a first response to the HTTP request message;

When the event notification carrier layer to the AF AF entity session, transmits a second HTTP request message to the AF entity, the second HTTP request message carries the AF session identification information, and receiving the AF a second entity returns the HTTP response request message. Preferably, the policy server for the policy and charging rules function (PCRF) entity or protocol converter (PC). Preferably, the policy server sends the AF entity to the second HTTP request message comprises:

The AF entity to the policy server when the second TCP connection already exists, the policy server preclude the use of the second TCP connection sending the second HTTP request message to the AF entity; the policy server and the when the AF entity of the second TCP connection is not established, the policy server to establish a second TCP connection with the AF entity, and then sending the second HTTP request message. Preferably, the method further comprising:

After the policy server receives the AF entity sends the HTTP response to the second request message, the retention between the policy server and the second TCP connection AF entity; or

The policy server receives the AF entity sends the HTTP response after the second request message, the disconnection between the policy server and the second AF entity TCP connection. Preferably, the PC is a policy server, the policy server receives the first HTTP request message, the method further comprises: the PC sends diameter authentication authorization request (AAR) message to the PCRF, requesting to establish a session diameter the AAR message carries a session identifier diameter, and holding the corresponding relationship between the PC AF session identification information to the diameter of the session identifier. Preferably, the method further comprises: a policy server receives the HTTP carrying the third session identification information AF AF entity sends a request message to the PC, the PC transmits a diameter AAR message to the PCRF entity diameter or session termination request (STR) message, the STR or AAR message carries the session identifier diameter. Preferably, the policy server is a PC, you the policy server transmits a second HTTP request message to the AF entity, comprising:

PC PCRF entity sends the session identifier carried in the diameter of the re-authentication request diameter

When (the RAR), the session termination request (ASR) or the session termination response (STA) message, the PC transmits to the AF of the AF entity session carrying the second identification information of the HTTP request message. One kind of AF entity, comprising:

A first unit, configured to: when the session is established AF AF entity and the policy server sends a first Hypertext Transfer Protocol (HTTP) request message to the policy server and policy server receives the first HTTP request is returned reply message;

Wherein the first unit is configured to: in the first HTTP request message carries the identifier information of an AF session, or the first response request message from the HTTP server policy acquired AF returned session identifier information;

A second unit, configured to: upon receiving the policy server notifies the event the carrier layer to the AF AF entity session, sent by the HTTP carries the second AF session identification information request message, to the policy server returns the secondary HTTP request response message. Preferably, the AF entity further comprises:

A third unit, which is configured to: modify or terminate when the AF session, sending a third HTTP request message to the AF entity to the policy server, the third HTTP request message carries the identification information of an AF session, and receiving the policy server returns the HTTP response to the third request message.

Preferably, the first means is configured to: when the first transmission control protocol (TCP) of the AF entity and the policy server connection already exists, preclude the use of the first TCP connection to the policy server sending the first HTTP request message, when the first TCP connection with the present AF policy server is not established, establishing a first TCP connection to the policy server, then sending the first HTTP request message;

The third unit is configured to: AF already present in the first entity and the policy server TCP connection, preclude the use of the first TCP connection to the policy server transmits the third HTTP request message, when the first TCP connection with the present AF policy server is not established, establishing a first TCP connection to the policy server, and then transmits the third HTTP request message.

Preferably, the first unit, further configured to: after receiving the policy server sends the reply to the first HTTP request message, reserving the AF between the first entity and the policy server TCP connection or disconnection between the AF entity and the policy server of the first TCP connection; the third unit is further configured to: receiving the policy server to the HTTP request message sent by the third after the response, the AF retained between the entity and the policy server of the first TCP connection, or the disconnection of the TCP connection between the first AF entity and the policy server.

Preferably, the second means is configured to: preclude the use of a second TCP connection between the policy server and the AF entity is connected to receive the second HTTP request message, and preclude the use of the second TCP connection returning the second HTTP request message to the policy server response. A strategy server, including:

A first unit configured to: receive an application function (AF) carries a first hypertext transfer protocol AF session identification information (HTTP) request message sent by the entity, returning a first HTTP request message to the AF entity of response; or AF entity sends the received first HTTP request message, session identification information is assigned AF AF session, and returns carrying the AF session identifier information of the first HTTP request message in response to the AF entity;

A second unit, configured to: when the AF event notification carrier layer to the AF entity session, transmits a second HTTP request message to the AF entity, the second HTTP request message carries the session AF identification information, and the receiving the second AF entity returns a response message of HTTP request.

Preferably, the first means is configured to: AF preclude the use of the first TCP connection between the receipt of the first HTTP server entity and the policy of this request message, and preclude the use of the TCP connection to the first the AF entity returns the first request response message of HTTP.

Preferably, the second means is configured to: when the second TCP connection, preclude the use of the second TCP connection sends the AF already exist in the policy server and the second HTTP request message to the AF ;

When the policy server and the second AF TCP connection is not established, establishing the second TCP connection to the AF, and then sending the second HTTP request message.

Preferably, the second means is configured to: after receiving the AF entity sends the HTTP response to the second request message, according to reservation policy between the server and the TCP entity in the second AF connection or disconnection between the server and the policy of the present AF second TCP connection.

Preferably, the policy server for the policy and charging rules function (PCRF) entity or protocol converter (PC) a protocol converter, comprising:

A first unit, which is configured to: establish an application function (AF) during the session, the receiving entity sends AF carries a first hypertext transfer protocol has an AF session identification information (HTTP) request message, to the Policy and Charging Rules Function (PCRF) entity sending authentication authorization request diameter (AAR) message, a session request to establish the diameter, the diameter of the AAR message carries a session identifier, and the corresponding relationship holding AF session identification information to the diameter of the session identifier; or receive a first hypertext transfer protocol (the HTTP) request message to the AF entity sends, session identification information assigned to the AF AF session, the policy and charging rules function (PCRF) entity sending authentication authorization request diameter (AAR) message, requesting establishment diameter session, the diameter of the AAR message carries a session identifier, and the corresponding relationship holding AF session identification information to the diameter of the session identifier;

A second unit, which is configured to: modify or AF session termination process, the receiving entity carries a third AF AF session identification information of the HTTP request message, and transmits the Diameter session identifier carried to the PCRF entity AAR diameter or diameter session termination request (STR) message; and

A third unit configured to: in the event reporting procedure carrier layer, the diameter of the diameter of the re-authentication request carries the session identifier of the sending entity (RAR) receiving said the PCRF, the session termination request (ASR) or the session termination response (STA ) message, and sends the AF AF carries the session identifier information in the second HTTP request message.

Embodiments of the invention further provides a computer program comprising program instructions that, when executed by the program application function entity, so that the application function entity may perform the method described above.

Embodiments of the invention further provides a computer program comprising program instructions, the program instructions when executed policy server, the policy server that can perform the method described above.

Embodiments of the invention further provides a computer program containing any of the above carriers.

Technical solutions of the embodiments of the present application addresses and AF PCRF or HTTP-based PC can be problems in real time bidirectional information transfer. Brief Description

FIG 1 is a schematic diagram of the related art PCC;

Figure 2 is a prior art PC deployment architecture diagram of the PCC;

FIG 3 is a flowchart of an embodiment of an AF session establishment embodiment of the present invention;

FIG 4 is a flowchart of an embodiment of an AF session modification of the embodiment of the present invention;

5 is a flowchart of an AF session embodiment of the present invention, an embodiment is terminated;

6 is a flowchart of the event according to an embodiment of the present invention is reported;

7 is a flowchart diagram of a IP-CAN session embodiment of the present invention is terminated;

FIG 8 is a flowchart of an AF session according to a second embodiment of the present invention is established;

FIG 9 is a flowchart of an AF session according to a second embodiment of the present invention is modified;

10 is a flowchart of an AF session according to a second embodiment of the present invention, ending;

11 is a flowchart of two events reported Example embodiment of the present invention;

FIG 12 is a flowchart of the IP-CAN session termination of the two embodiments of the present invention.

Preferred embodiment of the present invention.

BRIEF detail below with description of embodiments of the present invention. Incidentally, in the case of no conflict, the embodiments of the present disclosure and embodiments of features may be arbitrarily combined with one another.

Example 1

The present embodiment provides a session management method, comprising:

When the AF entity to establish a session with the policy server AF, AF entity transmits a first HTTP request message to the policy server;

Wherein, the message carries the AF AF entity session identification information to the policy server to notify the first HTTP request, the HTTP request the policy server returns a first response message to the AF entity; or policy server receives the first HTTP request message, AF session identifier information assigned to an AF session, and sends the response to the AF AF entity session identifier information in a first HTTP request message;

When the policy server notifies the event the above-described carrier layer to the AF entity session AF, AF entity sends a policy server a second HTTP request message, the second HTTP request message carries a session identification information described above AF, AF entity returns to the second policy server HTTP request response message. Among them, the policy server can PCRF entity or PC.

AF session identifier information and the above-described method involved is a globally unique identifier, or a combination of service session identifier and other information. The composition service session identifier and other information, may preclude the composition represented by any one of the following: IP address of the UE and the service session identifier, wherein said session identifier is a service that can uniquely identify the IP address in the case where the same UE AF session identifier;

Service session identifier, an IP address and IP domain identifier of the UE, wherein the session identifier is a service identifier can be a unique identification of the AF session in the IP address and IP identification field where the same UE; service session identifier, the UE IP address and the PDN identifier, wherein said session identifier is a service identifier can be a unique identification of the AF session service session identifier, a user identifier, wherein said service session identifier in the IP address and PDN identifier where the same UE It is capable of uniquely identifying the AF session identifier in the case of user identity and the IP address the same UE.

Further, in the above methods, when the AF entity and the policy server to modify or terminate a session above AF, AF entity will send the policy server to a third HTTP request message, the third HTTP request message carries the identifier information of an AF session, the policy server will have to return the third HTTP request response message.

Below in conjunction with application scenario, a detailed description of the implementation process of the method described above.

First, the PCC architecture shown in Figure 1 to illustrate the Rx interface supporting SOAP or REST protocol flow between a session with the AF entity PCRF entity (i.e., policy server).

FIG. 3 flowchart session management process (i.e., AF session establishment procedure) is initially provided to the session information, including the steps 301 to 303:

Step 301. The user equipment UE attached to the network, initiating an attachment procedure or the UE initiates the additional PDN connection establishment procedure, UE interacts with AF entity, a media negotiation. AF entity determines business-related information.

Step 302.AF solid PCRF entity to initiate an AF session establishment procedure to establish a session AF, AF provides service information and the session identification information. The AF session identification information may be assigned by the AF to the PCRF entity by the AF in this case an interactive physical distribution or before the.

In this step, a first AF entity sends an HTTP request message to the PCRF, the first HTTP request message carries an AF session identification information and service information. In addition, the first HTTP request message may further carry an explicit AF session establishment indication. AF entity own uniform resource locator (Uniform Resource Locator, URL) (expressed as URL 1) may also be carried in the message. AF entity on the IP address, the user identity of the UE (if present), the PDN information, identification information of the domain structure of the URL for addressing PCRF PCRF.

Wherein, an AF session identification information may be a globally unique identifier information of the AF for the session, but also by a unique combination of AF session information identifying the service session ID information in combination with other compositions, the present embodiment, an AF session identification information to the service when a combination of the session identifier and other information, may preclude the combination of any of the following:

1) a service session identifier and the IP address of the UE, wherein the session identifier is a service capable of uniquely identifying the AF session identifier in the case where the same IP address of the UE;

2) a service session identifier, an IP address and IP domain identifier of the UE, wherein the session identifier is a service capable of uniquely identifying the AF session in the IP address and IP identification field where the same UE identifier;

3) a service session identifier, an IP address and a PDN identifier of the UE, wherein the session identifier is a service identifier can be a unique identification of the AF session in the IP address and PDN identifier where the same UE

4) The service session identifier, a user identifier, wherein the service identifier is a session identifier that can uniquely identify the IP addresses and AF in case where the same user identifier of the UE session.

Step 303. PCRF entity stores service information provided by the AF entity, PCRF entity a first HTTP request returns the response message to the AF entity.

In the above flow, the processing for AF between the PCRF entities and TCP connections, the following two schemes may preclude the use:

1) preclude the use of HTTP persistent connection mechanism. Performing step 302, if the PCRF entity AF TCP connection already exists (in this embodiment called a first TCP connection), the AF entity preclude the use of conventional TCP connection transmits a first HTTP request message to the PCRF a first, if there after the first TCP connection, establishing a first AF to the PCRF first TCP connection, and then send a first HTTP request message. After the step 303 is performed, a first TCP connection is not disconnected.

2) does not preclude the use of HTTP persistent connection mechanism. After 302, the AF entity to establish a first TCP connection and the PCRF entity performs the step of re-transmitting a first HTTP request message. After execution of step 303, the TCP connection is disconnected first.

AF session identifier information in the above-described process, the AF session is used to identify the physical distribution of AF (AF session if identification information is independent of a globally unique identifier, the session identifier information assigned by the AF AF; AF session identifier if the session information service and combinations of other identification information, the service session identifier is assigned AF). Of course, the relevant information may also be assigned by the PCRF entity. If AF session identification information is an independent globally unique identifier, it may be assigned by the PCRF entity. I.e., step 302, the AF to the PCRF entity transmits a first HTTP request message carries only service information (service information includes UE IP address, IP identification field (optional), a user identifier (optional), the PDN ID (optional)) in step 303, PCRF entity allocation information according to the service a global AF AF session session identifier, and a first HTTP request message sent in response to the AF entity. If the identification information is a combination of an AF session service session identifier and other information, the service session identifier may be assigned by the PCRF entity. I.e., step 302, the AF entity to send a first HTTP request message carries only service information (service information includes UE IP address, IP identification field (optional), a user identifier (optional) to the PCRF, the PDN ID (optional) ), in step 303, PCRF entity allocation information according to an AF session service a service session identifier, the first HTTP request message and the service additional information and AF session identifier the session identifier information in the combination is transmitted to the AF response entity ( i.e., an AF session identification information).

AF multiple requests can be polymerized in a HTTP request message to an AF session establishment information (such as traffic information carries identification information of a plurality of AF AF session corresponding to the session (if the session identifier information assigned by the AF AF)), PCRF entity in the HTTP response the response message may also be polymerized AF information request to establish a plurality of sessions (such as the PCRF AF AF session identification information for each session is allocated (if the session identifier information assigned by the AF entity P CRF)).

FIG 4 is a session information update process (i.e., an AF session modification procedure) is a flowchart of a session management, comprising the steps 401 to 403:

Step 401. UE interacts with the AF entity, a media renegotiation. Business-related information AF OK.

Step 402.AF entity initiates an AF session modification procedure (i.e., FIG. 3 modified AF session establishment) to the PCRF entity, providing updated service information.

In this step, the third AF entity sends a HTTP request message to the PCRF entity, the update carries media description information and an AF session identifier defined in FIG. 3. In addition, this third HTTP request message may further carry an explicit AF session modification.

According to step 403. PCRF entity stores the session identifier information determined before the AF service information, and updated accordingly. The third HTTP request PCRF entity returns a response message to the AF entity.

In the above flow, the processing for AF between the PCRF entities and TCP connections, the following two schemes may preclude the use:

1) preclude the use of HTTP persistent connection mechanism. I.e. step 402, AF preclude the use of conventional TCP connection (i.e., a first TCP connection) sending a third HTTP request message to the PCRF entity. After execution of step 403, a first TCP connection is not disconnected.

2) does not preclude the use of HTTP persistent connection mechanism. 402, AF entity PCRF entity to establish the third step send a first HTTP request message after the TCP connection. After execution of step 403, a first TCP connection is closed.

AF may aggregate a plurality of HTTP requests in a request message to the AF session modification information (such as traffic information carries identification information of a plurality of AF AF session corresponding to the session), PCRF entity plurality modified reply message may also be polymerized in the HTTP request AF response information session.

FIG 5 is a flowchart showing AF session manager session termination process, comprising the steps of 501-503: step 501. UE interacts with the AF entity session is terminated.

Step 502.AF AF entity initiating session termination process to the PCRF entity, the end of FIG 3 established

AF session.

Specific implementation of this step is: AF entity transmits the third HTTP request message to the PCRF, AF session carries the session termination indication and identification information defined in Figure 3. The third HTTP request message may further carry explicit AF session termination indication.

According to step 503. PCRF entity stores the session identifier information determined before the AF service information, and delete. The third HTTP request PCRF entity returns a response message to the AF entity.

In the above flow, the processing for AF between the PCRF entities and TCP connections, the following two schemes may preclude the use:

1) preclude the use of HTTP persistent connection mechanism. When performing step 502, AF entity preclude the use of conventional TCP connection (i.e., a first TCP connection) sending a third HTTP request message to the PCRF entity. After execution of step 503, a first TCP connection is not disconnected.

2) does not preclude the use of HTTP persistent connection mechanism. When 502, AF entity PCRF entity to establish the third step send a first HTTP request message after the TCP connection. After execution of step 503, a first TCP connection is closed.

AF entity may aggregate multiple requests termination of the message information (such as carrying a plurality of AF session and service information corresponding to an AF session identification information) in the AF session request to a HTTP, PCRF entity in the HTTP response message may also be multiple requests termination of the polymerization a response information AF session.

FIG 6 is a flowchart of a session management process event reporting carrier layer, comprising the steps of 601 to

603:

Step 601.PCRF carrier layer entity sensed event, such as the IP-CAN type change.

Step 602.PCRF carrier layer entity reporting an AF session-related events of FIG 3 established to the AF entity.

In this step, the PCRF entity AF entity sends the second HTTP request message, which carries the carrier layer and events defined in Example 1 AF session identification information. The URL address for the second HTTP message AF AF entity is an entity in FIG. 3 provided URL1.

Step 603.AF entity determines the application layer session corresponding to the UE according to an AF session identifier information, carrier layer known event session corresponding to the application layer. To perform related processing. AF second HTTP request entity returns a response message to the PCRF entity.

In the above flow, the PCRF entity for handling between the entity and the AF TCP connection may preclude the use of the following two scenarios:

1) preclude the use of HTTP persistent connection mechanism. Step 602, if a TCP connection already exists between the AF and the PCRF entity (i.e., a second TCP connection), the PCRF entity preclude existing TCP connection (i.e., a second TCP connection) transmits a second HTTP request to the AF entity message, does not exist between the AF entity PCRF entity, if the TCP connection, the AF entity PCRF entity after establishing the second TCP connection transmits a second HTTP request message. After execution of step 603, a second TCP connection is not disconnected.

2) does not preclude the use of HTTP persistent connection mechanism. 602, PCRF and the AF step to establish a second HTTP request message transmitted after the second TCP connection. After execution of step 603, a second TCP connection is closed.

PCRF entity may aggregate a plurality of AF session in the event information in the HTTP request message (carrying the event information such as an AF session identifier information corresponding to the plurality of AF session), the AF entity HTTP response message may be a plurality of polymeric AF session events reported response information.

FIG 7 is a session management IP-CAN session termination process flowchart (PCRF entity notifies the AF entity IP-CAN session termination may be considered a special event reporting carrier layer), comprising the steps 701 to 703:

Step 701. PCRF entity sensed IP-CAN session termination.

Step 702.PCRF related entity to entity notifies the AF AF session establishment FIG. 3 transmission resource is lost.

In this step, the PCRF entity transmits a second HTTP request message to the AF entity, the request carries the session termination indication and AF session identifier information defined in FIG. The URL for the second HTTP request message addressed AF AF entity is an entity in FIG. 3 provided URL1.

Step 703.AF AF entity session identifier determined application layer session information corresponding to the UE according to known transmission resource corresponding to the application layer session loss. To perform related processing. AF second HTTP request entity returns a response message to the PCRF entity.

In the above flow, the PCRF entity for handling between the entity and the AF TCP connection may preclude the use of the following two scenarios:

1) preclude the use of HTTP persistent connection mechanism. Step 702, if the AF entity PCRF entity with an existing TCP connection (i.e., a second TCP connection), the PCRF entity preclude the use of conventional TCP connection (i.e., a second TCP connection) transmits a second HTTP request message to the AF entity, If the entity does not exist between the PCRF and the AF entity TCP connection, the AF entity PCRF entity after establishing the second TCP connection transmits a second HTTP request message. After execution of step 703, a second TCP connection is not disconnected.

2) does not preclude the use of HTTP persistent connection mechanism. 702, PCRF entity AF entity to establish a second step the HTTP request message transmits the second TCP connection. After execution of step 703, a second TCP connection is closed.

PCRF may aggregate a plurality of transmission resource in an HTTP AF session request message event information is lost (for example, carries a plurality of AF session information corresponding to the event identification information and an AF session), the AF entity HTTP response message may aggregate multiple AF session events reported response information.

Next, the PCC architecture shown in FIG. 2 as an example, the process described session exists between PC with AF entity PCRF entity.

8 process (i.e., AF session establishment procedure) is a flowchart of the session management information initially provided to the session, including the steps 801 to 805:

Step 801. The user equipment UE attaches to the network, initiating an attachment procedure or the UE initiates the additional PDN connection establishment procedure, UE interacts with AF, performing media negotiation, AF entity determines the service related information.

Step 802.AF entity to initiate AF session establishment process request to the PC AF session establishment, provided

AF session identification information and business information. The AF session identification information may be assigned by a PC at this point by the AF interaction or physical distribution in before.

In this step, a first AF entity sends an HTTP request message to the PCRF entity, the first HTTP request message carries an AF session identification information and service information. PC to save one of the AF session identification information and business information. In addition, the first HTTP message may further carry an explicit AF session establishment indication. AF own uniform resource locator (Uniform Resource Locator, URL) (denoted as the URL2) may also be carried in the message. AF entity on the IP address, the user identity of the UE (if present), the PDN information, identification information of the domain structure of the URL for addressing PC PC. Wherein, an AF session identification information may be a globally unique identifier for identifying the separate AF session, it may be combined by the service session identifier other information that uniquely identifies the combination information of the AF session, in the present embodiment, an AF session identification information combination service session identifier and other information, may preclude the AF session identification information represents a combination of any of the following:

. 1) the IP address of the UE and service session identifier, wherein the service identifier is a session identifier that can uniquely identify the IP address of the AF in the case of the same UE session;

2) a service session identifier, an IP address and IP domain identifier of the UE, wherein the session identifier is a service capable of uniquely identifying the AF session in the IP address and IP identification field where the same UE identifier;

3) a service session identifier, an IP address and a PDN identifier of the UE, wherein the session identifier is a service identifier can be a unique identification of the AF session in the IP address and PDN identifier where the same UE

4) The service session identifier, a user identifier, wherein said session identifier is a service identifier can be a unique identification of the AF session in the case of user identity and the IP address the same UE.

Step 803.PC initiates an AF session establishment process request to the PCRF entity AF session establishment, providing service information.

In this step, the PCRF entity sends AF diameter (a Diameter) Authentication Authorization Request (Authentication and Authorization Request, abbreviated AAR) message, the AAR message carries the identifier information of an AF session, Diameter session identifier, and a media description. And, PC saves the mapping between an AF session identifier to the Diameter session identifier information in step 802. AF PC may not be directly stored session identifier information, and the stored corresponding relationship to an AF session identifier to the Diameter session identifier information in step 802. (For example, PC may be down according to a fixed algorithm according to an AF session identifier information Diameter session identifier, so that in the future when the PC is received Diameter session identifier can tear down the session identifier information corresponding to the AF according to an algorithm.). In addition, PC also save the correspondence between URL2 and Diameter session identifier.

Step 804. PCRF entity stored service information, PCRF entity returns a Diameter AAA message to the PC;

Step 805. PC returns to the first HTTP request response message to the AF entity to entity. The above process, for the process between the entities and the AF PC TCP connections, can preclude the use of the following two scenarios:

1) preclude the use of HTTP persistent connection mechanism. Step 802, if the AF entity is connected with the presence of PC is TCP (i.e. the first TCP connection), the AF entity preclude the use of conventional TCP connection to send a first HTTP request message to the PC, if TCP connection exists, the AF entity first establish a TCP connection with the PC (i.e., a first TCP connection) to send a first HTTP request message. After execution of step 805, a first TCP connection is not disconnected.

2) does not preclude the use of HTTP persistent connection mechanism. After 802, AF entity establishing a first TCP connection with the PC performs the step of sending a first HTTP request message. After execution of step 805, a first TCP connection is closed.

AF session identifier information in the above-described process, the AF session is used to identify the physical distribution of AF (AF session if identification information is a time-independent globally unique identifier, the session identifier assigned by the AF AF; AF session if identification information for business. when a combination of the session identifier and other information, the service session identifier is assigned AF). Of course, relevant information can also be assigned by the PC. (1) If the AF session identification information is an independent globally unique identifier, then this can also be globally unique identifier assigned by the PC. I.e., step 802, the AF entity sends PC carries only a first HTTP request message service information (service information includes UE IP address, IP identification field (optional), a user identifier (optional), the PDN ID (optional)) in step 803, a PC according to the service information distribution global AF AF session is the session identifier, and a correspondence relationship storage PC AF session identifier to the Diameter session identifier assigned to the PC. In step 805, PC in the first HTTP request response message returned to the AF AF session identifier. (2) If the identification information is a combination of the AF session service session identifier and other information, the service session identifier may be assigned by the PC. I.e., step 802, the AF entity to send a first HTTP request message carries only service information (service information includes UE IP address, IP identification field (optional), a user identifier (optional) to the PCRF, the PDN ID (optional) ), at step 803, a PC assigned service session identifier according to an AF session service information, and the PC save Diameter session identifier and other information in combination with (i.e., an AF session identification information) corresponding relationship between service session identifier. Response in step 805, PC in the first HTTP request message returns the service session ID information and the other identification information of an AF session combinations (i.e., an AF session identification information) to the AF entity.

AF entity may aggregate multiple messages AF session establishment information request in an HTTP request (for example, service information carries identification information and the plurality of AF AF session corresponding to the session (if the session identifier information assigned by the AF AF)), PC HTTP response in the response message may also be polymerized AF information request to establish a plurality of sessions (such as a PC AF AF session identification information for each session is allocated (if AF session identifier information assigned by the PC)).

FIG 9 is a session information update process (i.e., an AF session modification procedure) is a flowchart of a session management, comprising the steps 901 to 905:

Step 901. UE interaction with the AF entity, a media renegotiation, AF entity to determine the business-related information.

Step 902.AF entity to initiate AF session modification process modification Figure 8 AF session establishment, providing AF session identification information and service information to the PC.

In this step, the third AF entity sends an HTTP request message to the PC, the third HTTP request, and an AF session identifier information carried in the media description information defined in Figure 8 message. Bu this evening, the third HTTP request message may further carry an explicit AF session modification. PC according to previously saved AF session identification information to determine business information, and updates.

903.PC step determines that the corresponding Diameter session according to an AF session identification information. PC initiates AF session modification procedure to the PCRF, to provide business information.

In this step, AF transmits Diameter the AAR message to the PCRF entity, AAR message carries media Diameter session and entity identification information of the corresponding description.

According to step 904. PCRF entity stores previous Diameter session identifier and updates the service information confirmation, PCRF entity returns to the PC 4 Diameter authorized authentication response (Authentication and Authorization Answer, referred to as AAA) message;

A third step 905. PC returns the HTTP request response message to the AF entity.

The above process, for the process between the entities and the AF PC TCP connections, can preclude the use of the following two scenarios:

1) preclude the use of HTTP persistent connection mechanism. AF entity preclude the use of conventional TCP connection

(I.e., a first TCP connection) sending a third HTTP request message to the PC.

2) does not preclude the use of HTTP persistent connection mechanism. 902, AF entity to the PC to perform the step of sending a third HTTP request message after the first TCP connection. After execution of step 905, a first TCP connection is closed.

AF may aggregate a plurality of HTTP requests in a request message to the AF session modification information (such as traffic information carries identification information of a plurality of AF AF session corresponding to the session), PC in the HTTP response message may be a request to modify the polymerization of a plurality of AF answer session information.

FIG 10 is a flowchart showing AF session manager session termination process, comprising the steps 1001 to 1005:

Step 1001. UE and the AF entity to interact, the session terminated.

Step 1002.AF entity to initiate AF session termination process to establish PC AF session termination Figure 8. In this step, the third AF entity sends an HTTP request message to the PC, the third HTTP request message carries an AF session identifier and the session information as defined in FIG. 8 termination indication.

1003.PC step determines that the corresponding Diameter session according to an AF session identification information. PC initiates AF session termination process to the PCRF entity.

In this step, AF to the PCRF entity sends the Diameter session termination request (Session Termination Request, abbreviated STR) message, STR message carries corresponding Diameter session identifier.

The Diameter session identifier stored before step 1004. PCRF entity service information and determining to delete, PCRF entity returns a final response to the PC Diameter session (Session Termination Answer, referred to as STA) message;

Step 1005. PC for deleting the service information corresponding to, PC third HTTP request returns a response message to the AF entity.

The above process, for the process between the entities and the AF PC TCP connections, can preclude the use of the following two scenarios:

1) preclude the use of HTTP persistent connection mechanism. AF entity preclude existing TCP connection (i.e., a first TCP connection) sending a third HTTP request message to the PC.

2) does not preclude the use of HTTP persistent connection mechanism. 1002, AF entity to the PC to perform the step of sending a third HTTP request message after the first TCP connection. After step 1005, a first TCP connection is closed.

AF may aggregate a plurality of HTTP requests in a request message to AF session termination information (such as traffic information carries identification information of a plurality of AF AF session corresponding to the session), PC in the HTTP response message may request termination of the polymerization of a plurality of AF answer session information.

FIG 11 is a flowchart showing the session management events reported during the carrier layer, comprising the steps 1101 to 1105:

Step 1101.PCRF carrier layer entity sensed event, such as the IP-CAN type change.

FIG step 1102.PCRF entity reporting an AF session related events carrying layer 8 to build the PC. In this step, PCRF sends a Diameter entity re-authentication request to the AF entity

(Re-Authentication Request, referred to as RAR) message carrying the carrier layer and events defined in step 803 a Diameter session identifier.

Step 1103.PC AF session identification information is determined in accordance with Diameter session identifier. PC bearer layer event reporting to AF.

In this step, PC transmits a second HTTP request message to the AF entity, an AF session identifier information carried in an event and a corresponding bearer layer. The URL for the second HTTP request message addressed AF is provided in FIG. 8 AF URL2.

Step 1104.AF entity determines the application layer session corresponding to the UE according to an AF session identifier information, carrier layer known event session corresponding to the application layer. To perform related processing. AF returned to the second HTTP request response message to the PC.

Diameter return step 1105. PC re-authentication response to the PCRF entity (Re-Authentication Answer, referred RAA) message.

The above process, the processing between the PC and for the AF entity TCP connection may preclude the use of the following two scenarios:

1) preclude the use of HTTP persistent connection mechanism. When performing step 1103, if the PC and

AF entity TCP connection already exists (i.e., a second TCP connection), the PC preclude the use of conventional TCP connection transmits a second HTTP request message to the AF, if TCP connection exists, the PC first sends a second TCP connection is established after the AF The second HTTP request message. After step 1104, a second TCP connection is not disconnected.

2) does not preclude the use of HTTP persistent connection mechanism. After 1103, PC to establish a second TCP connection to the AF entity performing the step of sending a second HTTP request message. After step 1104, a second TCP connection is closed.

PC may aggregate a plurality of AF session in the event information in the HTTP request message (carrying the event information such as an AF session identifier information corresponding to the plurality of AF session), the AF HTTP response message may be reported by the polymerization of a plurality of AF session events response information.

FIG 12 is a managed IP-CAN session termination process flowchart (PCRF entity notifies the AF entity IP-CAN session termination may be considered a special event reporting carrier layer), comprising the steps 1201 to 1205:

Step 1201. PCRF entity sensed IP-CAN session termination.

Step 1202.PCRF entity sends a session request to terminate the PC Diameter (Abort Session Request, referred to as ASR) message, which carries the Diameter session identifier;

Diameter return step to terminate the session response 1203.PC (Abort Session to the PCRF

Answer, referred to as ASA) message.

Step 1204. PC transmits the STR Diameter message to the PCRF entity carries Diameter session identifier;

Diameter STA step 1205.PCRF entity returns a message to the PC.

Step 1206.PC AF session identification information corresponding to the message is determined in accordance with Diameter session. PC inform AF AF session related entity graph is lost in transmission resources 8 established. This step may have a step or steps 1202 1205 triggered.

In this step, PC transmits a second HTTP request message to the AF entity, wherein the request carries the session termination indication AF session identifier information and the corresponding. The URL address for the second HTTP message AF AF FIG. 8 is provided in URL1.

Step 1207.AF AF entity session identifier determined application layer session information corresponding to the UE according to the known loss of transmission resource corresponding to the application layer session. To perform related processing. AF entity returns the secondary HTTP response request message to the PC. The above process, the processing between the PC and for the AF entity TCP connection may preclude the use of the following two scenarios:

1) preclude the use of HTTP persistent connection mechanism. Step 1106, if the PC and the AF entity TCP connection already exists (i.e., a second TCP connection), the PC preclude the use of conventional TCP connection transmits a second HTTP request message to the AF entity, if TCP connection exists, first, the PC after establishing the second TCP connection transmits a second HTTP request message to AF. After step 1107, a second TCP connection is not disconnected.

2) does not preclude the use of HTTP persistent connection mechanism. After 1106, PC to establish a second TCP connection with a second transmission step of performing AF HTTP request message. After step 1107, a second TCP connection is closed.

PC transmission resources may aggregate a plurality of AF session in the HTTP request message is lost in the event information (such as an AF session carrying a plurality of event information corresponding to the identification information and an AF session), the AF HTTP response message may aggregate multiple AF sessions event reporting response information.

Alternatively, in the above-described step 302 and step 802, respectively, a first HTTP AF entity sends to the PCRF and the PC content request message in XML language described below (Example 1):

<AAR command>

<Framed-IP-Address Framed-IP-Address = "..."> <Framed-IP-Address>

<Framed-IPv6-Prefix Framed-IPv6-Prefix = "... ''> <Fr amed-ΙΡνό -Prefix>

<Subscriptions-Id Subscriptions-ID = "..."> </ Subscription-Id>

<Called-Station-Id Called-Station-ID = "..."> </ Called-Station-Id>

<Service-Session-Id Service-Session-ID = "..."> </ Service-Session-Id>

<IP-Domain-Id IP-Domain-ID = "..."> <IP-Domain-Id>

<AF-Application-Identifier AF-Application-Identifier = "..."> </ AF-Application-Identifier> <Media-Component-Description>

<Media-Component-Number

Media- Component-Number = '' ... ''> <Media- Component-Number>

<Media-Sub-Component>

<Flow-Number Flow-Number = '' ... ''> <Flow-Number>

<Flow-Description Flow-Description = "..."> <Flow-Description>

<Flow-Status Flow-Status = "..."> <Flow-Status>

<Flow-Usage Flow-Usage = "..."> <Flow-Usage>

<Max- equested-Bandwidth-UL

Max- equested-Bandwidth-UL = "..."> <Max- eqeusted-Bandwidth>

<Max- equested-Bandwidth-DL Max- equested-Bandwidth-DL = "..."> <Max- equested-Bandwidth-DL>

<AF- Signalling-Protocol AF-Signalling-Protocol = "..."> </ AF-Signalling-Protocol> <Media-Sub-Component>

<AF-Application-Identifier AF-Application-Identifier = "..."> </ AF-Application-Identifier> <Media-Type Media-Type = "..."> <Media-Type>

<Max- equested-Bandwidth-UL

Max- equested-Bandwidth-UL = "..."> <Max- eqeusted-Bandwidth-UL>

<Max- equested-Bandwidth-DL

Max- equested-Bandwidth-DL = "..."> <Max- equested-Bandwidth-DL>

<Min-Requested-Bandwidth-UL

Min-Requested-Bandwidth-UL = "..."> <Min-Reqeusted-Bandwidth-UL>

<Min-Requested-Bandwidth-DL

Min-Requested-Bandwidth-DL = "..."> <Min-Requested-Bandwidth-DL>

<Flow-Status Flow-Status = "..."> <Flow-Status>

<Reservation-Priority Reservation-Priority ^ "..."> <Reservation-Priority>

<RS-Bandwidth RS-Bandwidth = "..."> <RS-Bandwidth>

<RR-Bandwidth RR-Bandwidth = "..."> <RR-Bandwidth>

<Codec-Data Codec-Data = "..."> </ Codec-Data>

<Media-Component-Description>

<Service-Info-Status Service-Info-Status = "..."> </ Service-Info-Status>

<AF-Charging-Identifier AF-Charging-Identifier = "..."> </ AF-Charging-Identifier>

<SIP-Forking-Indication SIP-Forking-Indication = "..."> </ SIP-Forking-Indication>

<Specific-Action Specific-Action = M ... "> </ Specifici-Action>

</ AAR command>

In step 302 and step 802, respectively, a first HTTP AF entity sends to the PCRF and the PC content request message to JSON language is described as follows (Example 2):

{ "AAR":

{

"Framed-IP-Address": "Valuel",

, 'Framed-IPv6 -Prefix ":" Value2' ',

"Subscription-Id": "Value3",

"Called- Station-Id": "Value4",

"Service-Session-Id": "Value5",

"IP-Domain-Id": "Value6",

"AF-Application-Identifier": "Value7",

"Media-Component-Description":

{

"Optional": "YES"

"Media-Component-Number": "Value8",

"AF-Application-Identifier": "Value9", "Media-Type": "ValuelO",

"Max- equested-Bandwidth-UL": "Valuel l",

"Max- equested-Bandwidth-DL": "Valuel2",

"Min-Requested-Bandwidth-UL": "Valuel3",

"Min-Requested-Bandwidth-DL": "Valuel4"

"Flow-Status": "Value 15

"Reservation-Priority": "Valuel6",

"RS-Bandwidth": "Valuel7",

"RR-Bandwidth": "Valuel8",

"Codec-Data": "Valuel9",

"Media-Sub-Component":

{

"Flow-Number": "Value20",

"Flow-Status": "Value21",

"Flow-Usage": "Value22",

"Max-Requested-Bandwidth-UL": "Value23

"Max-Requested-Bandwidth-DL": "Value24",

"AF- Signalling-Protocol": "Value25",

"Flow-Description": "Value26",

}

"Service-Info- Status": "Value27"

"AF-Charging-Identifier": "Value28"

"SIP-Forking-Indication": "Value29"

"Specific- Action": "Value30"

}

}

Where Framed-IP- Address, Framed-IPv6-Prefix were used to carry IPv4 addresses and IPv6 address of the UE (UE will preclude access to the same time with a business address, so it does not carry the same time two AVP). Service-Session-Id is used to carry the service session identifier. IP-Domain-Id used to carry the IP domain identifier, Called-Station-Id used to carry the PDN identifier. Subscription-Id used to carry the user identifier.

In step 402 and step 902, respectively, the third HTTP AF entity sends to the PCRF and the PC content request message described in XML language as similar to Example 1, described below in JSON language similar to Example 2. If step 302 or step 802 Service-Session-Id is a globally unique identifier (i.e., session identification AF), the Framed-IP-Address, Framed-IPv6-Prefix, Called-Station-Id, Subscription-Id, IP-Domain- Id does not carry other parameters; if step 302 or step 802 Service-session-Id is not globally unique identifier, or carry and the steps 302 and 802 the same parameters in order to uniquely identify AF session.

In step 502 and step 1002, respectively, the third HTTP AF entity sends to the PCRF and the PC content request message in XML language described below (Example 3):

<ST command>

<Framed-IP-Address Framed-IP-Address = "..."> <F ramed-IP-Address>

<Framed-IPv6-Prefix Framed-IPv6-Prefix = "..."> <F ramed-IPv6-Prefix>

<Subscriptions-Id Subscriptions-ID = "..."> </ Subscription-Id>

<Called-Station-Id Called-Station-ID = "..."> </ Called-Station-Id>

<Service-Session-Id Service-Session-ID = "..."> </ Service-Session-Id>

<IP-Domain-Id IP-Domain-ID = "■■■"> <IP-Domain-Id>

<Termination-Cause Termination-Cause = "■■."> </ Termination-Cause>

</ STA command>

In step 502 and in step 1002, the third HTTP AF entity are transmitted to the PC and the PCRF to request the content of the message described in language as JSON (Example 4)

{ "STR":

{

"Framed-IP-Address": "Valuel",

, 'Framed-IPv6 -Prefix ":" Value2' ',

"Subscription-Id": "Value3",

"Called- Station-Id": "Value4",

"Service-Session-Id": "Value5",

"IP-Domain-Id": "Value6",

"Termination-Cause": "Value7",

}

}

If step 302 or step 802 Service-Session-Id is a globally unique identifier (i.e., session identification AF), the Framed-IP-Address, Framed-IPv6-Prefix, Called- Station-Id, Subscription-Id, IP-Domain- Id does not carry other parameters; if step 302 or step 802 Service-session-Id is not globally unique identifier, or carry and the steps 302 and 802 the same parameters in order to uniquely identify AF session.

In step 602 and in step 1103, the second entity transmits to the HTTP PCRF entity AF AF entity to request content and the PC message in XML language described below (Example 5): <RAR command> <Framed-IP-Address Framed -IP-Address = "..."> <Framed-IP-Address>

<Framed-IPv6-Prefix Framed-IPv6-Prefix = "... ''> <Fr amed-ΙΡνό -Prefix>

<Subscriptions-Id Subscriptions-ID = "..."> </ Subscription-Id>

<Called-Station-Id Called-Station-ID = "..."> </ Called-Station-Id>

<Service-Session-Id Service-Session-ID = "..."> </ Service-Session-Id>

<IP-Domain-Id IP-Domain-ID = "..."> <IP-Domain-Id>

<Specific-Action Specific-Action = M ... "> </ Specific-Action>

<Abort-Cause Abort-Cause: "..."> </ Abort-Cause>

<Access-Network-Charging-Identifier Access-Network-Charging-Identifier "> </ Access-Network-Charging-Identifier>

<Access-Network-Charging-Address Access-Network-Charging-Address = "..."> </

Access-Network-Charging-Address>

<Flows>

<Media-Component-Number

Media- Component-Number = '' ... ''> <Media- Component-Number>

<Flow-Number Flow-Number = '' ... ''> <Flow-Number>

<Final-Unit- Action Final-Unit- Action ^ "..."> <Final-Unit-Action>

<Flows>

<IP-CAN-Type IP-CAN-Type = "..."> <IP-CAN-Type>

<RAT-Type RAT-Type> = "..."> <RAT-Type>

<RAR command>

In step 602 and in step 1103, the second entity transmits to the HTTP PCRF entity AF AF entity to request content and the PC JSON language message to be described below (Example 6):

{ "RAR":

{

"Framed-IP-Address": "Valuel",

, 'Framed-IPv6 -Prefix ":" Value2' ',

"Subscription-Id": "Value3",

"Called- Station-Id": "Value4",

"Service-Session-Id": "Value5",

"IP-Domain-Id": "Value6",

"Specific-Action": "Value7",

"Abort-Cause": "Value8",

"Access-Network-Charging-Identifier": "Value9",

"Access-Network-Charging-Address": "ValuelO",

"Flows":

{

"Media-Component-Number": "Valuel 1",

"Flow-Number": "Valuel2",

"Final-Unit- Action": "Valuel3",}

"IP-CAN-Type": "Valuel4",

"RAT-Type": "Valuel5",

}

}

If step 302 or step 802 Service-Session-Id is a globally unique identifier (i.e., session identification AF), the Framed-IP-Address, Framed-IPv6-Prefix, Called- Station-Id, Subscription-Id, IP-Domain- Id does not carry other parameters; if step 302 or step 802 Service-session-Id is not globally unique identifier, or carry and the steps 302 and 802 the same parameters in order to uniquely identify AF session.

In step 702 and in step 1103, the second entity transmits to the HTTP PCRF entity AF AF entity to request content and the PC message in XML language described below (Example 7):

<ST command>

<Framed-IP-Address Framed-IP-Address = "..."> <Framed-IP-Address>

<Framed-IPv6-Prefix Framed-IPv6-Prefix = "... ''> <Fr amed-ΙΡνό -Prefix>

<Subscriptions-Id Subscriptions-ID = "..."> </ Subscription-Id>

<Called-Station-Id Called-Station-ID = "..."> </ Called-Station-Id>

<Service-Session-Id Service-Session-ID = "..."> </ Service-Session-Id>

<IP-Domain-Id IP-Domain-ID = "..."> <IP-Domain-Id>

<Abort-Cause Abort-Cause: "..."> </ Abort-Cause>

</ ST command>

In step 702 and in step 1103, the second entity transmits to the HTTP PCRF entity AF AF entity to request content and the PC JSON language message to be described below (Example 8):

{ "RAR":

{

"Framed-IP-Address": "Valuel",

, 'Framed-IPv6 -Prefix ":" Value2' ',

"Subscription-Id": "Value3",

"Called- Station-Id": "Value4",

"Service-Session-Id": "Value5",

"IP-Domain-Id": "Value6",

"Abort-Cause": "Value7",

}

}

If step 302 or step 802 Service-Session-Id is a globally unique identifier (i.e., session identification AF), the Framed-IP-Address, Framed-IPv6-Prefix, Called- Station-Id, Subscription-Id, IP-Domain- Id does not carry other parameters; if step 302 or step 802 Service-session-Id is not globally unique identifier, or carry and the steps 302 and 802 the same parameters in order to uniquely identify AF session.

Example 2

The present embodiment provides an application function (AF) entity, which support both HTTP client and an HTTP server, and realizes various functions of the above-described embodiment of Example 1 AF. The AF entity comprises at least the following units.

A first unit configured to: when the session is established AF AF entity and the policy of this server, transmits a first HTTP request message to the policy server and receiving the policy server returns a reply to the first HTTP request message;

Wherein the first message carries the AF unit session identification information of the first HTTP request; Alternatively, a first response request message from the HTTP server policy acquired AF returned session identifier information;

A second unit, configured to: upon receiving the bearer layer event notification policy server session to the present AF AF entity sends the HTTP that carries the second AF session identification information request message to the policy server returning the response to the second HTTP request message.

On the basis of the above-described architecture, AF entity may further include a third unit that when the AF with the policy server to modify or terminate the AF session, sending a third HTTP request message to the policy server, the said third HTTP request message carries the identification information of an AF session, and the policy server receives the HTTP request returns a response to the third message.

Incidentally, in the embodiment between the AF processing entity policy server TCP connection with the present embodiment, it may preclude the use or not use HTTP persistent connection mechanism Bian. For example, the first unit, the TCP connection (i.e., a first TCP connection) already exist in the AF entity and the policy server, preclude the use of the first TCP connection transmits a first HTTP request message, and present between the AF and the policy server when establishing a TCP connection, the first unit to establishing a first TCP connection with the policy server, and then send a first HTTP request message. Likewise, the third cell, the TCP connection (i.e., a first TCP connection) already exist in the AF entity and the policy server, preclude a first TCP connection with the request message sends a third HTTP, and in the present AF policy server to establish a TCP when connected to the third unit establishing a first TCP connection with the policy server, and then transmits the third HTTP request message.

And the first unit, configured to: receiving a first HTTP request message sent by the policy server of the response may be to retain a first disconnect the TCP connection between the present AF policy server. Similarly, a third unit, after receiving the third response HTTP request message sent by the Policy Server, and may be retained on or off according to a first TCP connection between the AF and the policy server. It is also noted that the second unit, configured to: when receiving the second HTTP request message sent by the policy server, receiving is performed preclude the second TCP connection between the server and the policy of the present AF entity, a corresponding first two units are also preclude the use of a second TCP connection to the policy server returns to the second HTTP request message response.

In the specific application scenario, the session management process between AF entity and the policy server may refer to the corresponding content in the above Example 1, are not repeated here.

It provided a policy server Example 3 This example embodiment, which supports HTTP client and an HTTP server and can implement various functions described above in Example 1 policy server, comprising at least first and second units. A first unit, configured to: receiving a first transmission AF entity an AF session identifier information with a HTTP request message, the first HTTP request returns a response message to the AF entity; AF or the receiving entity a first HTTP request message sent by , an AF session identifier information assigned to an AF session, the AF return a first HTTP session identification information carried in the request response message to the AF entity.

Preferably, the first unit, configured to: receive a first HTTP request message, preclude the use of a TCP connection between a first entity and AF present receiving policy server is connected, and accordingly, the first TCP connection also preclude return to the first HTTP request message to the AF entity response.

A second unit, configured to: when the event notification carrier layer to the AF of the AF entity session, the AF entity transmits a second HTTP request message, the second HTTP request message carries an AF session identification information, and the receiving entity returns AF the second HTTP request response message. Preferably, the second unit transmits a second HTTP request message, the policy server is present when the AF second TCP connection already exists, preclude the use of a second TCP connection transmits a second HTTP request message to the AF, and in this strategy when the second TCP connection is not established between the server and the AF, to establish a second TCP connection with the AF, and then transmits a second HTTP request message.

It is noted that the other, the second cell, after receiving the second response AF entity sends the HTTP request message may be retained or disconnect the second TCP connection between the server and the policy of the present AF entity.

The practical application of the policy server can be PCRF entity, or a PC. Session management process between the PC and the AF PCRF entity or entities may see Example 1 the corresponding content, which is not repeated herein.

Example 4

The present embodiment provides a protocol converter, which can be used as the session management in Example 1 policy server, the protocol converter comprises at least the following units:

A first unit, configured to: AF session establishment procedure, the receiving entity sends AF carries

The first identification information of the HTTP AF session request message, the authentication message carrying Diameter diameter 4 authorized request (Diameter) session identifier (AAR) message to the PCRF, requesting to establish a session diameter, and holding the AF session identification information Diameter session identifier corresponding relationship; or, in the AF session establishment procedure, receiving a first HTTP request message sent by the entity AF, AF session identification information assigned to an AF session, sending carries diameter (diameter) diameter session identifier authentication authorization request to the PCRF entity (AAR) message to request establishment of a session in diameter, and maintain a correspondence relationship AF diameter session identifier information with a session identifier.

A second unit, configured to: AF session modification or termination process, the receiving entity carries a third AF AF session identifier information with a HTTP request message, and transmits the AAR carrying Diameter message or above the STR Diameter Diameter session identifier to the PCRF entity ;

A third unit configured to: in the event reporting procedure in a carrier layer, carrying the above-described received Diameter session identifier sent by the PCRF entity Diameter RAR, ASR or STA message, and sending the second HTTP request carries the above-described AF AF session identification information news. Embodiments of the invention further provides a computer program comprising program instructions that, when executed by the program application function entity, so that the application function entity may perform the method described above.

Embodiments of the invention further provides a computer program comprising program instructions, the program instructions when executed policy server, the policy server that can perform the method described above.

Embodiments of the invention further provides a computer program containing any of the above carriers.

In summary, the above-described embodiments address AF and the PCRF entity or HTTP-based PC can be two-way information transmission problems in real time.

Those of ordinary skill in the art will be appreciated that the above method may be all or part of the steps by a program instructing relevant hardware, the program may be stored in a computer-readable storage medium, such as a read-only memory, magnetic or optical disk. Alternatively, all or part of the steps of the above-described embodiments may be implemented using one or more integrated circuits. Accordingly, each module / unit in the above-described embodiments may be implemented preclude the form of hardware, and also can be implemented in the form of software function module. This application is not limited to any specific combination of hardware and software form.

The above are merely preferred examples of the present invention, but not intended to limit the scope of the present invention. Within the spirit and principle of the present invention, any modifications, equivalent replacements, improvements, etc., should be included within the scope of the present invention.

Industrial Applicability

Embodiment of the present invention solves the AF and the PCRF entity or HTTP-based PC can be two-way information transmission problems in real time.

Claims

Claims
A session management method comprising:
When an application function (AF) entity and the policy server to establish an AF session, the AF entity sends a first Hypertext Transfer Protocol (HTTP) request message to the policy server;
Wherein, the AF entity by the first HTTP request message transmits an AF session identification information to the policy server; alternatively, the AF entity first HTTP response returned from the policy server the request message acquires AF session identifier information assigned to the policy server AF session;
When the AF entity receives the policy server notifies the event the carrier layer to the AF AF entity session, transmitting to the second HTTP request message AF entity, the second HTTP request message carries the AF session identification information;
The AF entity returns the second HTTP request message to the policy server response.
2. The method as claimed in claim 1, wherein,
The policy server a policy and charging rules function (PCRF) entity or protocol converter (PC). 3. The method of claim 1 or claim 2, wherein,
When the AF entity to modify or terminate the AF session, the AF entity transmits the third HTTP request message to the policy server, the third HTTP request message carries the identification information of an AF session;
HTTP said third entity receives the AF policy server returns the request response message.
4. The method of claim 1 or claim 2, wherein the AF session identification information is a globally unique identifier.
5. The method of claim 1 or claim 2, wherein the AF session identification information represented by preclude any combination of the following:
Service session identifier and the IP address of the UE;
Service session identifier, UE IP address and IP domain identifier; service session identifier, UE IP address and a packet data network (PDN) identification; service session identifier and a user identifier.
6. A method as claimed in claim 1 or claim 2, wherein the AF entity to support HTTP client and an HTTP server, and the policy server to support HTTP client and an HTTP server.
7. The method according to claim 3, wherein, the AF entity sends the policy server of the first HTTP request message or the third HTTP request message, comprising:
When the AF entity and the policy server the first transmission control protocol (TCP) connection already exists, the AF entity preclude the first TCP connection to the policy server sending the first HTTP request message or the The third HTTP request message;
The AF entity and the policy server is not established when the first TCP connection, establishing the first AF first TCP connection to the policy server, then sending the first HTTP request message or the third HTTP request news.
8. A method as claimed in claim 7, wherein,
The AF entity receives the policy server transmits a first HTTP request message or the response message of the third HTTP request, reserving the AF between the first entity and the policy server TCP connection ; or
The AF entity receives the policy server transmits a first HTTP request message or the third HTTP request response message, and disconnecting the AF between the first entity and the policy server TCP connection.
9. A method for session management, the method comprising:
Policy server receives an application function (AF) carrying the AF entity sends the session identifier information with a first Hypertext Transfer Protocol (HTTP) request message, returning a first HTTP response request message to the AF entity; or receive AF entity a first HTTP request message sent, session identification information is assigned AF AF session, the AF entity to return the AF session carrying the identification information in the first HTTP request response message; in the AF entity to notify when the carrier layer AF event session, the AF entity sends the second HTTP request message, the second HTTP request message carries the identification information of an AF session, the AF entity and receiving the second return HTTP request response message.
10. The method of claim 9, wherein the policy server for the policy and charging rules function (PCRF) entity or protocol converter (PC) requirements.
11. The method of claim 9 or claim 10, wherein the policy server sends the AF entity to the second HTTP request message comprises:
The AF entity to the policy server when the second TCP connection already exists, the policy server preclude the use of the second TCP connection sending the second HTTP request message to the AF entity; the policy server and the when the AF entity of the second TCP connection is not established, the policy server to establish a second TCP connection with the AF entity, and then sending the second HTTP request message.
12. The method of claim 11, further comprising:
After the policy server receives the AF entity sends the HTTP response to the second request message, the retention between the policy server and the second TCP connection AF entity; or
The policy server receives the AF entity sends the HTTP response after the second request message, the disconnection between the policy server and the second AF entity TCP connection.
13. The method according to claim 10, wherein the policy server is a PC, the policy server receives the first HTTP request message, the method further comprises: the PC sends an authorization request to the diameter of the authentication entity PCRF (AAR) message, a session request to establish the diameter, the diameter of the AAR message carries a session identifier, and the corresponding relationship between the PC holding the AF session identification information and the diameter of the session identifier.
14. The method as claimed in claim 13, further comprising: a policy server receives the HTTP session carries the identification information of the third AF AF entity sends a request message to the PC, the PC to the PCRF diameter AAR message entity sends a session termination request or diameter (STR) message, the STR or AAR message carries the session identifier diameter. 15. The method according to claim 10, wherein the policy server is a PC, you the policy server transmits a second HTTP request message to the AF entity, comprising:
When the PC is transmitted to the PCRF re-authentication request carries the diameter of the diameter of the session identifier (the RAR), the session termination request (ASR) or the session termination response (STA) message, the PC transmits to the AF entity has carried the AF session identifier information of said second HTTP request message.
16, an application function (AF) entity, comprising:
A first unit, configured to: when the session is established AF AF entity and the policy server sends a first Hypertext Transfer Protocol (HTTP) request message to the policy server and policy server receives the first HTTP request is returned reply message;
Wherein the first unit is configured to: in the first HTTP request message carries the identifier information of an AF session, or the first response request message from the HTTP server policy acquired AF returned session identifier information;
A second unit, configured to: upon receiving the policy server notifies the event the carrier layer to the AF AF entity session, sent by the HTTP carries the second AF session identification information request message, to the policy server returns the secondary HTTP request response message.
17, as the AF entity as claimed in claim 16, further comprising:
A third unit, which is configured to: modify or terminate when the AF session, sending a third HTTP request message to the AF entity to the policy server, the third HTTP request message carries the identification information of an AF session, and receiving the policy server returns the HTTP response to the third request message.
18, AF entity as claimed in claim 17, wherein,
The first unit is configured to: when the first transmission control protocol (TCP) of the AF entity and the policy server connection already exists, preclude the first TCP connection with the policy server sends the first a HTTP request message is not established in the AF with the policy server of the first TCP connection, establishing a first TCP connection to the policy server, then sending the first HTTP request message;
The third unit is configured to: AF already present in the first entity and the policy server TCP connection, preclude the use of the first TCP connection to the policy server transmits the third HTTP request message, when the first TCP connection with the present AF policy server is not established, establishing a first TCP connection to the policy server, and then transmits the third HTTP request message.
19, as the AF entity as claimed in claim 18, wherein,
The first unit is further configured to: after receiving a response to the policy server transmits a first HTTP request message, the AF retained between the entity and the policy server of the first TCP connection, or disconnecting the AF between a first entity and the policy server TCP connection; the third unit is further configured to: after receiving a response message to the policy server transmits the third HTTP request, reserving the AF between the entity and the policy server of the first TCP connection, or the disconnection of the TCP connection between the first AF entity and the policy server.
20. The AF entity according to any one of claims 16 to 19, wherein,
The second unit is configured to: preclude the use of a second TCP connection between the policy server and the AF entity is connected to receive the second HTTP request message, and to preclude the connection with the second policy to TCP the server returns the secondary HTTP request response message. 21. A policy server, including:
A first unit configured to: receive an application function (AF) carries a first hypertext transfer protocol AF session identification information (HTTP) request message sent by the entity, returning a first HTTP request message to the AF entity of response; or AF entity sends the received first HTTP request message, session identification information is assigned AF AF session, and returns carrying the AF session identifier information of the first HTTP request message in response to the AF entity;
A second unit, configured to: when the AF event notification carrier layer to the AF entity session, transmits a second HTTP request message to the AF entity, the second HTTP request message carries the session AF identification information, and the receiving the second AF entity returns a response message of HTTP request. 22, the policy server as claimed in claim 21, wherein,
The first unit is configured to: AF preclude the use of the first TCP connection between the receipt of the first HTTP server entity and the policy of this request message, and preclude the first TCP connection to the AF entity returning the first HTTP request response message.
23, the policy server as claimed in claim 21, wherein,
The second unit is configured to: when the second TCP connection, preclude the use of the second TCP connection sending the second HTTP request message to the AF already exist in the policy server and the AF; the policy when the server and the second AF TCP connection is not established, establishing the second TCP connection to the AF, and then sending the second HTTP request message.
24, the policy server as claimed in claim 23, wherein,
The second unit is configured to: the AF entity receiving the HTTP response sent by the second request message, according to reservation policy between the server and the second TCP connection AF entity, or broken Folio policy server connected with the AF between the second TCP.
25. The policy server 21-1 according to any one of claim 24, wherein,
The policy server a policy and charging rules function (PCRF) entity or protocol converter (PC).
26, a protocol converter, comprising:
A first unit, which is configured to: establish an application function (AF) during the session, the receiving entity sends AF carries a first hypertext transfer protocol has an AF session identification information (HTTP) request message, to the Policy and Charging Rules Function (PCRF) entity sending authentication authorization request diameter (AAR) message, a session request to establish the diameter, the diameter of the AAR message carries a session identifier, and the corresponding relationship holding AF session identification information to the diameter of the session identifier; or receive a first hypertext transfer protocol (the HTTP) request message to the AF entity sends, session identification information assigned to the AF AF session, the policy and charging rules function (PCRF) entity sending authentication authorization request diameter (AAR) message, requesting establishment diameter session, the diameter of the AAR message carries a session identifier, and the corresponding relationship holding AF session identification information to the diameter of the session identifier;
A second unit, which is configured to: modify or AF session termination process, the receiving entity carries a third AF AF session identification information of the HTTP request message, and transmits the Diameter session identifier carried to the PCRF entity AAR diameter or diameter session termination request (STR) message; and
A third unit configured to: in the event reporting procedure carrier layer, the diameter of the diameter of the re-authentication request carries the session identifier of the sending entity (RAR) receiving said the PCRF, the session termination request (ASR) or the session termination response (STA ) message, and sends the AF AF carries the session identifier information in the second HTTP request message.
27. A computer program comprising program instructions that, when executed by the program application function entity, so that the application function entity may perform the method of any claim of claims 1-8.
28. A computer program comprising program instructions, the program instructions when executed policy server, the policy server such method of any of claims 9-15 executable.
29. A carrier carrying the computer program of claim 27 or claim 28.
PCT/CN2014/082548 2013-07-26 2014-07-18 Session management method, application function entity, policy server and protocol converter WO2015010576A1 (en)

Priority Applications (6)

Application Number Priority Date Filing Date Title
CN201310319571 2013-07-26
CN201310319571.7 2013-07-26
CNPCT/CN2014/075677 2014-04-18
PCT/CN2014/075677 WO2014173252A1 (en) 2013-07-26 2014-04-18 Session management method, application function entity, policy server and protocol converter
CN201410301186.4 2014-06-27
CN 201410301186 CN104348826A (en) 2013-07-26 2014-06-27 Session management method, AF (application function) entity, policy server and PC (protocol converter)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US15506945 US20170331691A1 (en) 2013-07-26 2014-07-18 Session Management Method, Application Function Entity, Policy Server and Protocol Converter
EP20140828651 EP3171542B1 (en) 2013-07-26 2014-07-18 Session management method, application function entity, policy server and protocol converter

Publications (1)

Publication Number Publication Date
WO2015010576A1 true true WO2015010576A1 (en) 2015-01-29

Family

ID=52392715

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/082548 WO2015010576A1 (en) 2013-07-26 2014-07-18 Session management method, application function entity, policy server and protocol converter

Country Status (1)

Country Link
WO (1) WO2015010576A1 (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101217789A (en) * 2008-01-10 2008-07-09 中兴通讯股份有限公司 A selecting method of strategies under non-roaming scenery and the functional server of charging rules
CN101583112A (en) * 2008-08-12 2009-11-18 中兴通讯股份有限公司 Method and device for marking session information
WO2012058643A2 (en) * 2010-10-29 2012-05-03 F5 Networks, Inc. System and method for on the fly protocol conversion in obtaining policy enforcement information

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101217789A (en) * 2008-01-10 2008-07-09 中兴通讯股份有限公司 A selecting method of strategies under non-roaming scenery and the functional server of charging rules
CN101583112A (en) * 2008-08-12 2009-11-18 中兴通讯股份有限公司 Method and device for marking session information
WO2012058643A2 (en) * 2010-10-29 2012-05-03 F5 Networks, Inc. System and method for on the fly protocol conversion in obtaining policy enforcement information

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
3GPP: "Study on XML based access of AF to the PCRF", TR 29.817 V 12.0.0, 31 March 2014 (2014-03-31), pages 60 - 62, XP055360632 *
3GPP: "STUDY ON XML-BASED ACCESS OF THE APPLICATION FUNCTION (AF) TO THE POLICY AND CHARGING RULES FUNCTION (PCRF)", TR 29.817 V 0.1.0, 30 June 2013 (2013-06-30), pages 7 - 13, XP055360635 *
None
See also references of EP3171542A4 *

Similar Documents

Publication Publication Date Title
US20100017846A1 (en) Service processing method and system, and policy control and charging rules function
US20110225306A1 (en) Methods, systems, and computer readable media for triggering a service node to initiate a session with a policy charging and rules function
US20100040047A1 (en) Loss of Signalling Bearer Transport
US20100290392A1 (en) Session and Media Binding to Common Control
US20150149656A1 (en) Methods, systems, and computer readable media for diameter routing using software defined network (sdn) functionality
US7136635B1 (en) Proxy SIP server interface for session initiation communications
US20120023246A1 (en) Group session management for policy control
US20110307790A1 (en) Extending revalidation-time of diameter sessions
WO2010066295A1 (en) Token-based correlation of control sessions for policy and charging control of a data session through a nat
CN101483826A (en) Method and apparatus for selecting policy and fee charging rule functional entity
US20100115071A1 (en) Devices and method for guaranteeing service requirements per user equipment basis into a bearer
US20110201303A1 (en) Method of handling a change to bearer control mode
US20120036257A1 (en) Diameter session audits
CN101296517A (en) Switch method, system and device for guaranteeing service quality management in isomer network
US20120177028A1 (en) Radius gateway on policy charging and rules function (pcrf) for wireline/wireless converged solution
CN101442428A (en) Application method, system and equipment for end-to-end QoS
CN102186162A (en) Method and equipment for acquiring accessible state of terminal
US20080062985A1 (en) System and method for collapsed subscriber management and call control
US8875274B2 (en) Methods and apparatus for providing indirect alternative paths to obtain session policy
US20130084826A1 (en) Usage sharing across fixed line and mobile subscribers
CN101540980A (en) Business priority updating indicating method, business priority updating method and device thereof
CN101052201A (en) Evolution mobile communication system and its strategy consulting method
US20130273876A1 (en) Method and apparatuses for multimedia priority service
US20110320584A1 (en) Method for determining a pcc rule waiting for pcef action
US20130003566A1 (en) Method and Node for Controlling Bearer Related Resources as well as a Corresponding System and Computer Program

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14828651

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase in:

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14828651

Country of ref document: EP

Kind code of ref document: A1

REEP

Ref document number: 2014828651

Country of ref document: EP