WO2015010576A1 - Procédé de gestion de session, entité à fonction d'application, serveur de règles et convertisseur de protocole - Google Patents

Procédé de gestion de session, entité à fonction d'application, serveur de règles et convertisseur de protocole 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
WIPO (PCT)
Prior art keywords
entity
request message
session
policy server
http request
Prior art date
Application number
PCT/CN2014/082548
Other languages
English (en)
Chinese (zh)
Inventor
周晓云
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from PCT/CN2014/075677 external-priority patent/WO2014173252A1/fr
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP14828651.1A priority Critical patent/EP3171542B1/fr
Priority to US15/506,945 priority patent/US10225151B2/en
Publication of WO2015010576A1 publication Critical patent/WO2015010576A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
    • H04L41/0273—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols using web services for network management, e.g. simple object access protocol [SOAP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels

Definitions

  • Session management method application functional entity, policy server and protocol converter
  • the present invention relates to the field of communications, and in particular, to a session management method, an application function entity, a policy server, and a protocol converter.
  • FIG 1 is the Policy and Charging Control (PCC) defined by the 3rd Generation Partnership Project (3GPP).
  • PCC Policy and Charging Control
  • the Policy and Charging Rules Function is used to formulate QoS and charging policies for network resources.
  • the PCRF formulates the control policy, and needs to combine the service information received from the AF, the user subscription information received from the User Profile Repository (SPR), the policy configured by the operator, and the like.
  • the PCRF sends the control policy for the service to the Policy and Charging Enforcement Function (PCEF) or the Bearer Binding and Event Report Function (BBERF).
  • PCEF Policy and Charging Enforcement Function
  • BBERF Bearer Binding and Event Report Function
  • the PCRF can subscribe to the bearer layer related events to the PCEF and/or BBERF to be aware of the event when the bearer layer occurs, and to change the control strategy.
  • the PCEF and the Traffic Detection Function can perform application detection and control functions based on the PCC rules (PCEF) or ADC rules (TDF) issued by the PCRF.
  • PCC Protocol Converter
  • the Rx interface needs to support two-way communication, that is, the AF provides service information to the PCRF, and the PCRF needs to provide a Traffic Plane Event to the AF in real time.
  • the SOAP or REST protocols are based on the Hypertext Transfer Protocol (HTTP).
  • HTTP is a stateless protocol.
  • the client requests a URL
  • the server responds, sends back the response content, and connects to the port. It cannot implement two-way communication.
  • the following three solutions are proposed in the industry:
  • the browser sends a request. After the server receives the connection, it suspends the connection until it has data to send to the client. After the data is sent, the connection is disconnected. When the client receives the data, it requests the server to take the data again.
  • the downside of this approach is that the connection needs to be maintained, taking up resources from the server and client.
  • the related protocol stipulates that the same client and server can only maintain a maximum of 2 HTTP TCP connections. If more than 2 HTTP TCP connections are maintained, the protocol is inconsistent with the related protocols, resulting in interoperability problems.
  • the related art also proposes that multiple HTTP requests can be encapsulated into one TCP connection (becoming HTTP Pipelining), and Long-Polling is used to implement the server to actively provide data to the client.
  • This scheme requires the client to send a new request after Long-Polling is completed, which will cause a delay.
  • Embodiments of the present invention provide a session management method, an application function entity, a policy server, and a protocol converter, which reduce the use of network resources while realizing two-way communication, and can ensure real-time performance.
  • a session management method including:
  • the AF entity When the application function (AF) entity establishes an AF session with the policy server, the AF entity sends a first hypertext transfer protocol (HTTP) request message to the policy server;
  • HTTP hypertext transfer protocol
  • the AF entity sends the AF session identification information to the policy server by using the first HTTP request message; or the AF entity obtains the response from the response of the first HTTP request message returned by the policy server.
  • the AF entity returns a response to the second HTTP request message to the policy server.
  • the policy server is a Policy and Charging Rules Function (PCRF) entity or a Protocol Translator (PC).
  • the AF entity when the AF entity modifies or terminates the AF session, the AF entity sends a third HTTP request message to the policy server, where the third HTTP request message carries the AF session identifier information;
  • the AF entity receives an answer to the third HTTP request message returned by the policy server.
  • the AF session identification information is a globally unique identifier.
  • the AF session identification information is represented by any combination of the following:
  • the service session identifier and the IP address of the UE are mapped to the service session identifier and the IP address of the UE.
  • Service session identifier IP address of the UE, and IP domain identifier
  • Service session identifier Service session identifier, UE's IP address, and packet data network (PDN) identity
  • service session identity service session identity and user identity.
  • the AF entity supports both an HTTP client and an HTTP server
  • the policy server supports both an HTTP client and an HTTP server.
  • the sending, by the AF entity, the first HTTP request message or the third HTTP request message to the policy server includes:
  • the AF entity When the AF entity and the policy server already have a first Transmission Control Protocol (TCP) connection, the AF entity sends the first HTTP request message to the policy server by using the first TCP connection or Third HTTP request message;
  • TCP Transmission Control Protocol
  • the AF When the AF entity and the policy server do not establish the first TCP connection, the AF first establishes a first TCP connection with the policy server, and then sends the first HTTP request message or the third HTTP request. Message.
  • the AF entity reserves the relationship between the AF entity and the policy server.
  • a session management method including:
  • the policy server receives a first hypertext transfer protocol (HTTP) request message that is sent by the application function (AF) entity and carries the AF session identifier information, and returns a response of the first HTTP request message to the AF entity; or, receives the AF
  • HTTP hypertext transfer protocol
  • the first HTTP request message sent by the entity, the AF session identifier information is allocated to the AF session, and the response of the first HTTP request message carrying the AF session identifier information is returned to the AF entity;
  • the policy server is a Policy and Charging Rules Function (PCRF) entity or a protocol converter (PC).
  • PC Policy and Charging Rules Function
  • the sending, by the policy server, the second HTTP request message to the AF entity includes:
  • the policy server sends the second HTTP request message to the AF entity by using the second TCP connection; the policy server and the When the AF entity does not establish a second TCP connection, the policy server first establishes a second TCP connection with the AF entity, and then sends the second HTTP request message.
  • the method further includes:
  • the policy server After receiving the response of the second HTTP request message sent by the AF entity, the policy server retains the second TCP connection between the policy server and the AF entity; or
  • the policy server After receiving the response of the second HTTP request message sent by the AF entity, the policy server disconnects the second TCP connection between the policy server and the AF entity.
  • the policy server is a PC
  • the method further includes: the PC sending a Diameter Authentication Authorization Request (AAR) message to the PCRF entity, requesting to establish a diameter session.
  • AAR Diameter Authentication Authorization Request
  • the AAR message carries a diameter session identifier, and the PC maintains a correspondence between the AF session identifier information and the diameter session identifier.
  • the method further includes: the policy server receiving a third HTTP request message that is sent by the AF entity to the PC and carrying the AF session identifier information, where the PC sends a Diameter AAR message to the PCRF entity. Or a Diameter Session Termination Request (STR) message, the AAR or STR message carrying the diameter session identifier.
  • the policy server when the policy server is a PC, the policy server sends a second HTTP request message to the AF entity, including:
  • the PCRF entity sends a diameter re-authentication request carrying the diameter session identifier to the PC
  • RAR when terminating a session request (ASR) or a session termination response (STA) message, the PC sends the second HTTP request message carrying the AF session identification information to the AF entity.
  • An AF entity including:
  • a first unit configured to: when the AF entity establishes an AF session with the policy server, send a first hypertext transfer protocol (HTTP) request message to the policy server, and receive a first HTTP request returned by the policy server Response to the message;
  • HTTP hypertext transfer protocol
  • the first unit is configured to: carry the AF session identifier information in the first HTTP request message, or obtain the AF session identifier information from the response of the first HTTP request message returned by the policy server;
  • a second unit configured to: receive a second HTTP request message carrying the AF session identification information, when the policy server notifies the AF entity of the bearer layer event of the AF session, and send the The policy server returns a response to the second HTTP request message.
  • the AF entity further includes:
  • a third unit configured to: when the AF entity modifies or terminates the AF session, sending a third HTTP request message to the policy server, where the third HTTP request message carries the AF session identifier information, And receiving a response of the third HTTP request message returned by the policy server.
  • the first unit is configured to: when the AF entity and the policy server already have a first Transmission Control Protocol (TCP) connection, use the first TCP connection to the policy server Sending the first HTTP request message, when the first TCP connection is not established between the AF and the policy server, first establishing a first TCP connection with the policy server, and then sending the first HTTP request message;
  • TCP Transmission Control Protocol
  • the third unit is configured to: when the AF entity and the policy server already have a first TCP connection, send the third HTTP request message to the policy server by using the first TCP connection, When the first TCP connection is not established between the AF and the policy server, first establishing a first TCP connection with the policy server, and then sending the third HTTP request message.
  • the first unit is further configured to: after receiving the response of the first HTTP request message sent by the policy server, retain the first between the AF entity and the policy server a TCP connection, or disconnecting the first TCP connection between the AF entity and the policy server;
  • the third unit is further configured to: after receiving the response of the third HTTP request message sent by the policy server, retain the first TCP connection between the AF entity and the policy server, or Disconnecting the first TCP connection between the AF entity and the policy server.
  • the second unit is configured to: receive the second HTTP request message by using a second TCP connection between the policy server and the AF entity, and use the second TCP connection Returning a response to the second HTTP request message to the policy server.
  • a policy server including:
  • a first unit configured to: receive, by the application function (AF) entity, a first hypertext transfer protocol (HTTP) request message carrying AF session identification information, and return the first HTTP request message to the AF entity Receiving; or receiving a first HTTP request message sent by the AF entity, assigning AF session identification information to the AF session, and returning, to the AF entity, a response of the first HTTP request message carrying the AF session identification information;
  • AF application function
  • HTTP hypertext transfer protocol
  • a second unit configured to: when notifying the AF entity of the bearer layer event of the AF session, sending a second HTTP request message to the AF entity, where the second HTTP request message carries the AF session Identification information, and receiving a response of the second HTTP request message returned by the AF entity.
  • the first unit is configured to: receive the first HTTP request message by using a first TCP connection between the AF entity and the policy server, and use the first TCP connection to The AF entity returns a response to the first HTTP request message.
  • the second unit is configured to: when the policy server and the AF have a second TCP connection, send the second HTTP request message to the AF by using the second TCP connection. ;
  • the policy server When the policy server does not establish a second TCP connection with the AF, first establish a second TCP connection with the AF, and then send the second HTTP request message.
  • the second unit is configured to: after receiving the response of the second HTTP request message sent by the AF entity, retain the second TCP between the policy server and the AF entity Connecting, or disconnecting the second TCP connection between the policy server and the AF.
  • the policy server is a policy and charging rule function (PCRF) entity or protocol transfer.
  • PC policy and charging rule function
  • PC PC
  • the first unit is configured to: receive, in an application function (AF) session establishment process, a first hypertext transfer protocol (HTTP) request message that carries the AF session identifier information sent by the AF entity, to the policy and charging rule function a (PCRF) entity sends a Diameter Authentication Authorization Request (AAR) message, requesting to establish a diameter session, the AAR message carrying a diameter session identifier, and maintaining a correspondence between the AF session identifier information and the diameter session identifier; or, receiving a first hypertext transfer protocol (HTTP) request message sent by the AF entity, assigning AF session identification information to the AF session, and sending a Diameter Authentication Authorization Request (AAR) message to the Policy and Charging Rules Function (PCRF) entity, requesting to establish a diameter session, the AAR message carrying a diameter session identifier, and maintaining a correspondence between the AF session identifier information and the diameter session identifier;
  • HTTP application function
  • PCRF Policy and Charging Rules Function
  • a second unit configured to: receive, in an AF session modification or termination process, a third HTTP request message that is sent by the AF entity and that carries the AF session identification information, and send, to the PCRF entity, the path session identifier that carries the diameter Diameter AAR or Diameter Session End Request (STR) message;
  • a third unit configured to: receive a diameter re-authentication request (RAR), a termination session request (ASR), or a session termination response (STA) that is sent by the PCRF entity and that carries the diameter session identifier in a bearer layer event reporting process. a message, and sending the second HTTP request message carrying the AF session identification information to the AF.
  • RAR diameter re-authentication request
  • ASR termination session request
  • STA session termination response
  • the embodiment of the present invention further provides a computer program, including program instructions, when the program instruction is executed by an application function entity, so that the application function entity can execute the above method.
  • the embodiment of the invention further provides a computer program, comprising program instructions, when the program instruction is executed by the policy server, so that the policy server can execute the above method.
  • Embodiments of the present invention also provide a carrier carrying any of the above computer programs.
  • FIG. 3 is a flowchart of establishing an AF session according to Embodiment 1 of the present invention.
  • FIG. 5 is a flowchart of an AF session termination according to Embodiment 1 of the present invention.
  • FIG. 7 is a flowchart of an IP-CAN session termination according to Embodiment 1 of the present invention.
  • FIG. 8 is a flowchart of establishing an AF session according to Embodiment 2 of the present invention.
  • FIG. 9 is a flowchart of an AF session modification according to Embodiment 2 of the present invention.
  • FIG. 10 is a flowchart of an AF session termination according to Embodiment 2 of the present invention.
  • FIG. 11 is a flowchart of event reporting according to Embodiment 2 of the present invention.
  • FIG. 12 is a flowchart of IP-CAN session termination according to Embodiment 2 of the present invention.
  • This embodiment provides a session management method, including:
  • the AF entity When the AF entity establishes an AF session with the policy server, the AF entity sends a first HTTP request message to the policy server;
  • the AF entity carries the AF session identification information in the first HTTP request message to notify the policy server, and the policy server returns a response of the first HTTP request message to the AF entity; or, after the policy server receives the first HTTP request message, Assigning AF session identification information to the AF session, and transmitting the AF session identification information to the AF entity in response to the first HTTP request message;
  • the policy server when the policy server notifies the AF entity of the bearer layer event of the above AF session Sending a second HTTP request message to the AF entity, where the second HTTP request message carries the AF session identifier information, and the AF entity returns a response of the second HTTP request message to the policy server.
  • the policy server can be a PCRF entity or a PC.
  • the AF session identification information involved in the above method is a globally unique identifier, or a combination of a service session identifier and other information.
  • the combination of the service session identifier and other information may be represented by any combination of the following: a service session identifier and an IP address of the UE, where the service session identifier is capable of uniquely identifying the IP address of the same UE.
  • a service session identifier an IP address of the UE, and an IP domain identifier
  • the service session identifier is an identifier that can uniquely identify the AF session in the case of an IP address and an IP domain identifier of the same UE
  • An address and a packet data network PDN identifier where the service session identifier is an identifier service session identifier and a user identifier that can uniquely identify the AF session in the case of an IP address and a PDN identifier of the same UE, where the service session identifier
  • the identifier of the AF session is uniquely identified in the case of the same UE's IP address and user identity.
  • the AF entity when the AF entity and the policy server modify or terminate the AF session, the AF entity sends a third HTTP request message to the policy server, where the third HTTP request message carries the AF session identifier information.
  • the Policy Server will return a response to the third HTTP request message.
  • FIG. 3 is a flow chart of session management during the initial provision of session information (ie, during the establishment of the AF session), including the following steps 301 to 303:
  • Step 301 The user equipment UE is attached to the network, initiates an attach procedure, or the UE initiates another PDN connection establishment process, and the UE interacts with the AF entity to perform media negotiation.
  • the AF entity determines business related information.
  • Step 302. The AF entity initiates an AF session establishment process to the PCRF entity to establish an AF session.
  • AF session identification information For AF session identification information and business information.
  • the AF session identification information may be assigned to the AF entity by the PCRF entity at this time by the AF entity or in an interaction before this.
  • the AF entity sends a first HTTP request message to the PCRF, where the first HTTP request message carries the AF session identification information and the service information.
  • the first HTTP request message can also carry an explicit AF session establishment indication.
  • the AF entity's own Uniform Resource Locator (URL) (denoted as URL 1) can also be carried in the message.
  • the AF entity may construct a PCRF URL for addressing the PCRF according to the UE's IP address, user identification (if any), PDN information, and domain identification information.
  • the AF session identifier information may be a globally unique identifier for the AF session, or may be a combination of the service session identifier and other information that uniquely identifies the AF session.
  • the AF session identifier information is a service.
  • service session identifier is an identifier that can uniquely identify the AF session in the case of an IP address and an IP domain identifier of the same UE;
  • the service session identifier is an identifier that can uniquely identify the AF session in the case of an IP address and a PDN identifier of the same UE.
  • a service session identifier is an identifier that can uniquely identify the session of the AF in the case of an IP address and a user identifier of the same UE.
  • Step 303 The PCRF entity saves the service information provided by the AF entity, and the PCRF entity returns a response of the first HTTP request message to the AF entity.
  • the AF entity uses The existing first TCP connection sends a first HTTP request message to the PCRF. If the first TCP connection does not exist, the AF and the PCRF first establish a first TCP connection, and then send the first HTTP request message. After the step 303 is performed, the first TCP connection is not disconnected.
  • step 302 the AF entity establishes a first TCP connection with the PCRF entity, and then sends a first HTTP request message. After performing step 303, the first TCP connection is disconnected.
  • the AF session identification information used to identify the AF session is assigned by the AF entity (if the AF session identification information is an independent global unique identifier, the AF session identification information is allocated by the AF; if the AF session identification information is a service session A combination of identification and other information, then the business session identifier is assigned to the AF).
  • the AF session identification information is an independent globally unique identifier, it can also be assigned by the PCRF entity.
  • the AF sends the first HTTP request message to the PCRF entity to carry only the service information (the service information includes the UE IP address, the IP domain identifier (optional), the user identifier (optional), and the PDN identifier (optional))
  • the PCRF entity allocates a global AF session identifier to the AF session according to the service information, and sends the AF session identifier to the AF entity in the response of the first HTTP request message. If the AF session identification information is a combination of the service session identifier and other information, the service session identifier may also be assigned by the PCRF entity.
  • the AF entity sends the first HTTP request message to the PCRF entity to carry only the service information (the service information includes the UE IP address, the IP domain identifier (optional), the user identifier (optional), and the PDN identifier (optional).
  • the PCRF entity allocates a service session identifier to the AF session according to the service information, and sends other information in the combination of the service session identifier and the AF session identifier information to the AF entity in the response of the first HTTP request message ( That is, AF session identification information).
  • the AF may aggregate multiple pieces of information requesting to establish an AF session in an HTTP request message (for example, carrying service information corresponding to multiple AF sessions and AF session identification information (if AF session identification information is assigned by AF)), and the PCRF entity responds in HTTP
  • the message may also aggregate the response information of the multiple AF sessions that are requested to be established (for example, the AF session identification information allocated by the PCRF entity for each AF session (if the AF session identification information is allocated by the P entity CRF)).
  • Figure 4 shows the session management process during the session information update process (that is, during the AF session modification process).
  • the figure includes the following steps 401 to 403:
  • Step 401 The UE interacts with the AF entity to perform media renegotiation.
  • AF determines business related information.
  • Step 402 The AF entity initiates an AF session modification process to the PCRF entity (ie, modifies the AF session established in FIG. 3) to provide updated service information.
  • the AF entity sends a third HTTP request message to the PCRF entity, carrying the updated media description information and the AF session identification information defined in FIG.
  • the third HTTP request message can also carry an explicit AF session modification indication.
  • Step 403. The PCRF entity determines the previously saved service information according to the AF session identification information, and performs corresponding update.
  • the PCRF entity returns a response to the third HTTP request message to the AF entity.
  • step 402 uses the existing TCP connection (i.e., the first TCP connection) to send a third HTTP request message to the PCRF entity. After performing step 403, the first TCP connection is also not broken.
  • step 402 the AF entity sends a third HTTP request message after establishing a first TCP connection with the PCRF entity. After performing step 403, the first TCP connection is broken.
  • the AF may aggregate multiple information for modifying the AF session in an HTTP request message (for example, carrying service information corresponding to multiple AF sessions and AF session identification information), and the PCRF entity may aggregate multiple requests for modification in the HTTP response message.
  • the response information of the AF session for example, carrying service information corresponding to multiple AF sessions and AF session identification information.
  • Figure 5 is a flow chart of session management during the termination of the AF session, including the following steps 501 to 503: Step 501.
  • the UE interacts with the AF entity to terminate the session.
  • Step 502. The AF entity initiates an AF session termination process to the PCRF entity, and terminates the establishment of FIG.
  • the AF entity sends a third HTTP request message to the PCRF entity, Carrying the session termination indication and the AF session identification information defined in FIG.
  • the third HTTP request message may also carry an explicit AF session termination indication.
  • Step 503. The PCRF entity determines the previously saved service information according to the AF session identification information, and deletes it.
  • the PCRF entity returns a response to the third HTTP request message to the AF entity.
  • step 502 the AF entity sends a third HTTP request message to the PCRF entity using the existing TCP connection (ie, the first TCP connection). After performing step 503, the first TCP connection is also not broken.
  • step 502 the AF entity sends a third HTTP request message after establishing a first TCP connection with the PCRF entity. After performing step 503, the first TCP connection is broken.
  • the AF entity may aggregate information of multiple request termination AF sessions in an HTTP request message (for example, carrying service information corresponding to multiple AF sessions and AF session identification information), and the PCRF entity may also aggregate the request termination in the HTTP response message. Response information for AF sessions.
  • FIG. 6 is a flowchart of session management in a bearer layer event reporting process, including the following steps 601 to
  • Step 601. The PCRF entity perceives a bearer layer event, such as an IP-CAN type change.
  • Step 602 The PCRF entity reports the bearer layer event related to the AF session established in Figure 3 to the AF entity.
  • the PCRF entity sends a second HTTP request message to the AF entity, where the bearer layer event and the AF session identification information defined in Embodiment 1 are carried.
  • the URL used to locate the AF entity in the second HTTP message is the URL1 provided by the AF entity in FIG.
  • Step 603. The AF entity determines an application layer session corresponding to the UE according to the AF session identification information, and learns a bearer layer event corresponding to the application layer session. Thereby performing related processing.
  • the AF entity returns a response to the second HTTP request message to the PCRF entity.
  • step 602 if a TCP connection (ie, a second TCP connection) already exists between the PCRF entity and the AF entity, the PCRF entity sends the second HTTP request to the AF entity by using the existing TCP connection (ie, the second TCP connection).
  • the existing TCP connection ie, the second TCP connection.
  • the PCRF entity sends a second TCP request message after establishing a second TCP connection with the AF entity.
  • the second TCP connection is also not broken.
  • step 602 the PCRF establishes a second TCP connection with the AF and sends a second HTTP request message. After performing step 603, the second TCP connection is broken.
  • the PCRF entity may aggregate event information of multiple AF sessions in an HTTP request message (for example, carrying event information corresponding to multiple AF sessions and AF session identification information), and the AF entity may also aggregate multiple AF session events in the HTTP response message. Evaluated response information.
  • Figure 7 is a flow chart of session management during the IP-CAN session termination process (the PCRF entity notifies the AF entity that the IP-CAN session termination can be considered as a special bearer layer event report), and includes the following steps 701 to 703:
  • Step 701. The PCRF entity perceives the termination of the IP-CAN session.
  • Step 702. The PCRF entity notifies the AF entity of the loss of the transmission resource associated with the AF session established in FIG.
  • the PCRF entity sends a second HTTP request message to the AF entity, carrying the request session termination indication and the AF session identification information defined in FIG.
  • the URL used to address the AF entity in the second HTTP request message is URL1 provided by the AF entity in FIG.
  • Step 703. The AF entity determines an application layer session corresponding to the UE according to the AF session identifier information, and learns that the transmission resource corresponding to the application layer session is lost. Thereby performing related processing.
  • the AF entity returns a response to the second HTTP request message to the PCRF entity.
  • step 702 if the PCRF is real The physical connection with the AF entity already exists (ie, the second TCP connection), and the PCRF entity sends the second HTTP request message to the AF entity by using the existing TCP connection (ie, the second TCP connection), if the PCRF entity and the AF entity If there is no TCP connection, the PCRF entity sends a second HTTP request message after establishing a second TCP connection with the AF entity. After performing step 703, the second TCP connection is also not broken.
  • step 702 the PCRF entity sends a second TCP request message after establishing a second TCP connection with the AF entity. After performing step 703, the second TCP connection is broken.
  • the PCRF can aggregate the transmission resource loss event information of multiple AF sessions in an HTTP request message (for example, carrying event information corresponding to multiple AF sessions and AF session identification information), and the AF entity can also aggregate multiple AFs in the HTTP response message.
  • the response information reported by the session event for example, carrying event information corresponding to multiple AF sessions and AF session identification information.
  • FIG. 8 is a flow chart of session management during the initial provision of session information (ie, during the establishment of the AF session), including the following steps 801 to 805:
  • Step 801. The user equipment UE attaches to the network, initiates an attach procedure, or after the UE initiates another PDN connection establishment process, the UE interacts with the AF to perform media negotiation, and the AF entity determines service related information.
  • Step 802. The AF entity initiates an AF session establishment process to the PC, requesting to establish an AF session, providing
  • the AF session identification information may be assigned by the AF entity at this time or by a PC in an earlier interaction.
  • the AF entity sends a first HTTP request message to the PCRF entity, where the first HTTP request message carries the AF session identification information and the service information.
  • the PC saves the AF session identification information and service information therein.
  • the first HTTP message may also carry an explicit AF session establishment indication.
  • AF's own Uniform Resource Locator (URL) (denoted as URL2) can also be carried in the message.
  • the AF entity may construct a URL of the PC for addressing the PC based on the IP address of the UE, the user identification (if present), the PDN information, and the domain identification information.
  • the AF session identifier information may be a globally unique identifier for separately identifying the AF session, or may be a combination of the service session identifier and other information to uniquely identify the AF session.
  • the AF session identifier information is When a combination of a service session identifier and other information, the AF session identification information may be represented by any combination of the following:
  • service session identifier is an identifier that can uniquely identify the session of the AF in the case of an IP address of the same UE;
  • service session identifier is an identifier that can uniquely identify the AF session in the case of an IP address and an IP domain identifier of the same UE;
  • the service session identifier is an identifier that can uniquely identify the AF session in the case of an IP address and a PDN identifier of the same UE.
  • a service session identifier is an identifier that can uniquely identify the AF session in the case of an IP address and a user identifier of the same UE.
  • Step 803. The PC initiates an AF session establishment procedure to the PCRF entity to request an AF session to provide service information.
  • the AF entity sends a Diameter Authentication and Authorization Request (AAR) message to the PCRF entity, and the AAR message carries the AF session identification information, the Diameter session identifier, and the media information description.
  • the PC saves the correspondence between the Diameter session identifier and the AF session identification information in step 802.
  • the PC may not directly save the AF session identification information, but may save the correspondence between the Diameter session identifier and the AF session identification information in step 802. (For example, the PC can push out the Diameter session identifier according to the AF session identification information according to a fixed algorithm, so that when the PC receives the Diameter session identifier in the future, the corresponding AF session identification information can be pushed out according to the algorithm.).
  • the PC also stores the correspondence between URL2 and the Diameter session ID.
  • Step 804. The PCRF entity saves the service information, and the PCRF entity returns a Diameter AAA message to the PC.
  • Step 805. The PC returns a response of the first HTTP request message to the AF entity entity.
  • the following two schemes can be used:
  • step 802 if the AF entity has a TCP connection with the PC (that is, the first TCP connection), the AF entity sends the first HTTP request message to the PC by using the existing TCP connection, and if there is no TCP connection, the AF entity The first HTTP request message is sent after establishing a TCP connection (ie, the first TCP connection) with the PC. After performing step 805, the first TCP connection is also not broken.
  • step 802 the AF entity sends a first HTTP request message after establishing a first TCP connection with the PC. After performing step 805, the first TCP connection is broken.
  • the AF session identification information used to identify the AF session is assigned by the AF entity.
  • the AF session identification information is an independent global unique identifier
  • the AF session identifier is assigned by the AF; if the AF session identification information is a service When the session identifier and other information are combined, then the service session identifier is assigned to the AF).
  • relevant information can also be assigned by the PC.
  • the AF session identification information is an independent globally unique identifier, then the globally unique identifier can also be assigned by the PC.
  • the AF entity sends the first HTTP request message to the PC to carry only the service information (the service information includes the UE IP address, the IP domain identifier (optional), the user identifier (optional), and the PDN identifier (optional))
  • the PC allocates a global AF session identifier to the AF session according to the service information, and the PC saves the correspondence between the Diameter session identifier and the AF session identifier assigned by the PC.
  • the PC returns an AF session identifier to the AF in response to the first HTTP request message.
  • the AF session identification information is a combination of the service session identifier and other information, the service session identifier can also be assigned by the PC.
  • the AF entity sends the first HTTP request message to the PCRF entity to carry only the service information.
  • the service information includes the UE IP address, the IP domain identifier (optional), the user identifier (optional), and the PDN identifier (optional).
  • the PC allocates a service session identifier to the AF session according to the service information, and the PC saves the correspondence between the Diameter session identifier and the service session identifier and other information combination (ie, AF session identifier information).
  • the PC returns other information (i.e., AF session identification information) in the combination of the service session identifier and the AF session identifier information to the AF entity in response to the first HTTP request message.
  • the AF entity can aggregate multiple requests to establish an AF session information in an HTTP request message.
  • the PC may also aggregate response information of multiple AF sessions requested in the HTTP response message (such as PC).
  • AF session identification information assigned to each AF session if the AF session identification information is assigned by the PC.
  • FIG. 9 is a flow chart of the session management process during the session information update process, that is, during the AF session modification process, and includes the following steps 901 to 905:
  • Step 901. The UE interacts with the AF entity to perform media renegotiation, and the AF entity determines service related information.
  • Step 902. The AF entity initiates an AF session modification process to the PC to modify the AF session established in FIG. 8 to provide AF session identification information and service information.
  • the AF entity sends a third HTTP request message to the PC, where the third HTTP request message carries the AF session identification information and the media information description defined in FIG. Furthermore, the third HTTP request message may also carry an explicit AF session modification indication.
  • the PC determines the previously saved service information based on the AF session identification information and updates it.
  • Step 903. The PC determines a corresponding Diameter session according to the AF session identification information.
  • the PC initiates an AF session modification process to the PCRF to provide service information.
  • the AF sends a Diameter AAR message to the PCRF entity, where the AAR message carries the corresponding Diameter session entity identifier and media information description.
  • Step 904. The PCRF entity saves the service information and updates according to the Diameter session identifier, and the PCRF entity returns a Diameter Authentication 4 (Authentication and Authorization Answer, AAA for short message) message to the PC;
  • Diameter Authentication 4 Authentication and Authorization Answer, AAA for short message
  • Step 905. The PC returns a response of the third HTTP request message to the AF entity.
  • step 902 the AF entity first sends a third HTTP request message after establishing a first TCP connection with the PC. After performing step 905, The first TCP connection is broken.
  • the AF may aggregate multiple information for modifying the AF session in an HTTP request message (for example, carrying service information corresponding to multiple AF sessions and AF session identification information), and the PC may aggregate the multiple AFs requested to be modified in the HTTP response message.
  • the response information of the session for example, carrying service information corresponding to multiple AF sessions and AF session identification information
  • Figure 10 is a flowchart of session management during the termination of the AF session, including the following steps 1001 to 1005:
  • Step 1001. The UE interacts with the AF entity to terminate the session.
  • Step 1002 The AF entity initiates an AF session termination process to the PC to terminate the AF session established in FIG.
  • the AF entity sends a third HTTP request message to the PC, where the third HTTP request message carries the AF session identification information and the session termination indication defined in FIG.
  • Step 1003 The PC determines a corresponding Diameter session according to the AF session identification information.
  • the PC initiates an AF session termination process to the PCRF entity.
  • the AF entity sends a Diameter Session Termination Request (STR) message to the PCRF, and the STR message carries the corresponding Diameter session identifier.
  • STR Diameter Session Termination Request
  • Step 1004. The PCRF entity determines that the service information is saved and deletes according to the Diameter session identifier, and the PCRF entity returns a Session Termination Answer (STA) message to the PC.
  • STA Session Termination Answer
  • Step 1005. The PC deletes the corresponding service information, and the PC returns a response of the third HTTP request message to the AF entity.
  • the AF entity sends a third HTTP request message to the PC using the existing TCP connection (ie, the first TCP connection).
  • step 1002 the AF entity first sends a third HTTP connection message after establishing a first TCP connection with the PC. After performing step 1005, The first TCP connection is broken.
  • the AF may aggregate information of multiple request termination AF sessions in an HTTP request message (for example, carrying service information corresponding to multiple AF sessions and AF session identification information), and the PC may aggregate multiple AFs that are requested to be terminated in the HTTP response message.
  • the response information of the session for example, carrying service information corresponding to multiple AF sessions and AF session identification information
  • Figure 11 is a flow chart of session management during the bearer layer event reporting process, including the following steps 1101 to 1105:
  • Step 1101. The PCRF entity perceives a bearer layer event, such as an IP-CAN type change.
  • Step 1102 The PCRF entity reports the AF session-related bearer layer event established in Figure 8 to the PC. In this step, the PCRF entity sends a Diameter re-authentication request to the AF entity.
  • Step 1103 The PC determines the AF session identification information according to the Diameter session identifier.
  • the PC reports the bearer layer event to the AF.
  • the PC sends a second HTTP request message to the AF entity, where the bearer layer event and the corresponding AF session identifier information are carried.
  • the URL used to address the AF in the second HTTP request message is URL2 provided by AF in FIG.
  • Step 1104 The AF entity determines an application layer session corresponding to the UE according to the AF session identifier information, and learns the bearer layer event corresponding to the application layer session. Thereby performing related processing.
  • the AF returns a response to the second HTTP request message to the PC.
  • Step 1105. The PC returns a Diameter Re-Authentication Answer (RAA) message to the PCRF entity.
  • RAA Diameter Re-Authentication Answer
  • the PC sends an second HTTP request message to the AF by using the existing TCP connection. If there is no TCP connection, the PC first sends a second TCP connection with the AF and then sends the second HTTP connection message. The second HTTP request message. After performing step 1104, the second TCP connection It does not disconnect.
  • step 1103 the PC first sends a second TCP request message after establishing a second TCP connection with the AF entity. After performing step 1104, the second TCP connection is broken.
  • the PC may aggregate event information of multiple AF sessions in an HTTP request message (for example, carrying event information corresponding to multiple AF sessions and AF session identification information), and the AF may also aggregate multiple AF session events in the HTTP response message. Answer the message.
  • Figure 12 is a flowchart of the session management in the IP-CAN termination process (the PCRF entity notifies the AF entity that the IP-CAN session termination can be considered as a special bearer layer event report), and includes the following steps 1201 to 1205:
  • Step 1201. The PCRF entity perceives the termination of the IP-CAN session.
  • Step 1202 The PCRF entity sends a Diameter Termination Session Request (ASR) message to the PC, where the Diameter session identifier is carried;
  • ASR Diameter Termination Session Request
  • Step 1203. The PC returns a Diameter termination session response to the PCRF entity (Abort Session
  • ASA Answer, referred to as ASA
  • Step 1204. The PC sends a Diameter STR message to the PCRF entity, carrying the Diameter session identifier.
  • Step 1205. The PCRF entity returns a Diameter STA message to the PC.
  • Step 1206 The PC determines corresponding AF session identification information according to the Diameter session message.
  • the PC notifies the AF entity that the transmission resources associated with the AF session established in Figure 8 are lost. This step can be triggered by step 1202 or step 1205.
  • the PC sends a second HTTP request message to the AF entity, where the request carries the session termination indication and the corresponding AF session identification information.
  • the URL for addressing AF in the second HTTP message is URL1 provided by AF in FIG.
  • Step 1207 The AF entity determines an application layer session corresponding to the UE according to the AF session identifier information, and learns that the transmission resource corresponding to the application layer session is lost. Thereby performing related processing.
  • the AF entity returns a response to the second HTTP request message to the PC.
  • the following two schemes can be used:
  • step 1106 if the PC and the AF entity already have a TCP connection (ie, a second TCP connection), the PC sends an second HTTP request message to the AF entity by using the existing TCP connection. If there is no TCP connection, the PC first Sending a second HTTP request message after establishing a second TCP connection with the AF. After performing step 1107, the second TCP connection is also not broken.
  • a TCP connection ie, a second TCP connection
  • step 1106 the PC first sends a second TCP connection message after establishing a second TCP connection with the AF. After performing step 1107, the second TCP connection is broken.
  • the PC may aggregate the transmission resource loss event information of multiple AF sessions in an HTTP request message (for example, carrying event information corresponding to multiple AF sessions and AF session identification information), and the AF may also aggregate multiple AF sessions in the HTTP response message. The response information reported by the event.
  • step 302 the content of the first HTTP request message sent by the AF entity to the PCRF entity and the PC respectively is described in the XML language as follows (Example 1):
  • IP-Domain-ID ... "> ⁇ IP-Domain-Id>
  • Max-equested-Bandwidth-UL ... "> ⁇ Max- eqeusted-Bandwidth>
  • Max-equested-Bandwidth-DL ... "> ⁇ Max- equested-Bandwidth-DL>
  • AF-Application-Identifier ... "> ⁇ /AF-Application-Identifier>
  • Media-Type ... "> ⁇ Media-Type>
  • Max-equested-Bandwidth-UL ... "> ⁇ Max- eqeusted-Bandwidth-UL>
  • Max-equested-Bandwidth-DL ... "> ⁇ Max- equested-Bandwidth-DL>
  • Min-Requested-Bandwidth-UL ... "> ⁇ Min-Reqeusted-Bandwidth-UL>
  • Min-Requested-Bandwidth-DL ... "> ⁇ Min-Requested-Bandwidth-DL>
  • step 302 and in step 802 the contents of the first HTTP request message sent by the AF entity to the PCRF entity and the PC, respectively, are described in the JSON language as follows (Example 2):
  • the Framed-IP-Address and the Framed-IPv6-Prefix are respectively used to carry the IPv4 address and IPv6 address of the UE. (The UE only uses one address to access the service at the same time, so the two AVPs are not carried at the same time).
  • Service-Session-Id is used to carry the service session identifier.
  • the IP-Domain-Id is used to carry the IP domain identifier, and the Called-Station-Id is used to carry the PDN identifier.
  • the Subscription-Id is used to carry the user ID.
  • step 402 and in step 902 the contents of the third HTTP request message sent by the AF entity to the PCRF entity and the PC respectively are described in XML language as follows, similar to Example 1, and the JSON language description is similar to Example 2 as follows. If the Service-Session-Id of step 302 or step 802 is a globally unique identifier (ie, an AF session identifier), then Framed-IP-Address, Framed-IPv6-Prefix, Called-Station-Id, Subscription-Id, IP-Domain- Parameters such as Id are not carried; if step 302 or If the Service-Session-Id of step 802 is not a globally unique identifier, the same parameters as in step 302 and step 802 are carried to uniquely identify the AF session.
  • a globally unique identifier ie, an AF session identifier
  • step 502 and in step 1002 the contents of the third HTTP request message sent by the AF entity to the PCRF entity and the PC, respectively, are described in XML language as follows (Example 3):
  • Service-Session-ID " ... "> ⁇ /Service-Session-Id>
  • IP-Domain-ID " ⁇ "> ⁇ IP-Domain-Id>
  • step 502 and in step 1002 the contents of the third HTTP request message sent by the AF entity to the PCRF entity and the PC respectively are described in the JSON language as follows (Example 4)
  • Service-Session-Id of step 302 or step 802 is a globally unique identifier (ie, an AF session identifier), then Framed-IP-Address, Framed-IPv6-Prefix, Called-Station-Id, Subscription-Id, IP-Domain- The parameters such as Id are not carried; if the Service-Session-Id of step 302 or step 802 is not a globally unique identifier, the same parameters as in step 302 and step 802 are carried to uniquely identify the AF session.
  • a globally unique identifier ie, an AF session identifier
  • IP-Domain-ID ... "> ⁇ IP-Domain-Id>
  • Access-Network-Charging-Identifier "> ⁇ / Access-Network-Charging-Identifier >
  • IP-CAN-Type ... "> ⁇ IP-CAN-Type>
  • step 602 and in step 1103, the contents of the second HTTP request message sent by the PCRF entity to the AF entity and the PC to the AF entity are described in the JSON language as follows (Example 6):
  • IP-CAN-Type "Valuel4"
  • Service-Session-Id of step 302 or step 802 is a globally unique identifier (ie, an AF session identifier), then Framed-IP-Address, Framed-IPv6-Prefix, Called-Station-Id, Subscription-Id, IP-Domain- The parameters such as Id are not carried; if the Service-Session-Id of step 302 or step 802 is not a globally unique identifier, the same parameters as in step 302 and step 802 are carried to uniquely identify the AF session.
  • a globally unique identifier ie, an AF session identifier
  • step 702 and in step 1103, the contents of the second HTTP request message sent by the PCRF entity to the AF entity and the PC to the AF entity are described in the XML language as follows (Example 7):
  • IP-Domain-ID ... "> ⁇ IP-Domain-Id>
  • step 702 and in step 1103, the contents of the second HTTP request message sent by the PCRF entity to the AF entity and the PC to the AF entity are described in the JSON language as follows (Example 8):
  • Service-Session-Id of step 302 or step 802 is a globally unique identifier (ie, an AF session) ID), Framed-IP-Address, Framed-IPv6-Prefix, Called-Station-Id, Subscription-Id, IP-Domain-Id, etc. are not carried; if the Service-Session-Id of step 302 or step 802 is not global The unique identifier then carries the same parameters as in steps 302 and 802 to uniquely identify the AF session.
  • a globally unique identifier ie, an AF session ID
  • the embodiment provides an application function (AF) entity, which supports both an HTTP client and an HTTP server, and can implement various functions of the AF in the above embodiment 1.
  • the AF entity includes at least the following units.
  • the first unit is configured to: when the AF entity establishes an AF session with the policy server, send a first HTTP request message to the policy server, and receive a response of the first HTTP request message returned by the policy server;
  • the first unit carries the AF session identifier information in the first HTTP request message; or obtains the AF session identifier information from the response of the first HTTP request message returned by the policy server;
  • the second unit is configured to: when receiving the bearer layer event of the AF session, the policy server sends the second HTTP request message carrying the AF session identifier information to the policy server Returning a response to the second HTTP request message.
  • the AF entity may further include: a third unit, where the unit sends a third HTTP request message to the policy server when the AF and the policy server modify or terminate the AF session, where The third HTTP request message carries the AF session identification information, and receives a response of the third HTTP request message returned by the policy server.
  • the HTTP persistent connection mechanism may or may not be used.
  • the first unit when the AF entity and the policy server already have a TCP connection (ie, the first TCP connection), the first HTTP request message is sent by using the first TCP connection, and the first AF request message is not between the AF and the policy server.
  • the first unit When a TCP connection is established, the first unit first establishes a first TCP connection with the policy server, and then sends a first HTTP request message.
  • the first TCP connection message is sent by using the first TCP connection, and when the AF connection is not established between the AF and the policy server, the third unit first establishes a first TCP connection with the policy server, and then sends The third HTTP request message.
  • the first unit is configured to: after receiving the response of the first HTTP request message sent by the policy server, the first TCP connection between the AF and the policy server may be disconnected. Similarly, after receiving the response of the third HTTP request message sent by the policy server, the third unit may also reserve or disconnect the first TCP connection between the AF and the policy server. It should be noted that the foregoing second unit is configured to: when receiving the second HTTP request message sent by the policy server, receive the second TCP connection between the policy server and the AF entity, correspondingly, The second unit also responds with a second TCP connection returning a second HTTP request message to the policy server.
  • Embodiment 3 provides a policy server that supports both an HTTP client and an HTTP server, and implements various functions of the policy server in Embodiment 1 above, and includes at least a first unit and a second unit.
  • the first unit is configured to: receive a first HTTP request message that is sent by the AF entity and that carries the AF session identification information, and return a response of the first HTTP request message to the AF entity; or receive the first HTTP request message sent by the AF entity. And assigning AF session identification information to the AF session, and returning, to the AF entity, a response of the first HTTP request message carrying the AF session identification information.
  • the first unit is configured to: when receiving the first HTTP request message, receive the first TCP connection between the AF entity and the policy server, and correspondingly, use the first TCP connection. Returning the response of the first HTTP request message to the AF entity.
  • the second unit is configured to: when notifying the AF entity of the bearer layer event of the AF session, send a second HTTP request message to the AF entity, where the second HTTP request message carries the AF session identifier information, and receives the AF entity return The response of the second HTTP request message.
  • the second unit sends the second HTTP request message when the second TCP connection exists between the policy server and the AF, the second HTTP connection message is sent to the AF by using the second TCP connection, and the policy is When the second TCP connection is not established between the server and the AF, the second TCP connection is established with the AF, and the second HTTP request message is sent.
  • the foregoing second unit may reserve or disconnect the second TCP connection between the policy server and the AF entity.
  • the foregoing policy server may be a PCRF entity or a PC.
  • the session management process between the PCRF entity or the PC and the AF entity refer to the corresponding content in the foregoing Embodiment 1, and details are not described herein again.
  • the embodiment provides a protocol converter, which can be used as the policy server in the foregoing embodiment 1 for session management.
  • the protocol converter includes at least the following units:
  • the first unit is configured to: during the establishment of the AF session, the receiving AF entity sends the carried
  • the first HTTP request message of the AF session identification information is sent to the PCRF entity to send a Diameter Authentication 4 Authorization Request (AAR) message carrying a Diameter session identifier to request to establish a diameter session, and maintain the AF session identification information and the Diameter session identifier.
  • AAR Diameter Authentication 4 Authorization Request
  • the first HTTP request message sent by the AF entity the AF session identification information is allocated to the AF session, and the Diameter authentication authorization request carrying the Diameter session identifier is sent to the PCRF entity.
  • AAR Diameter Authentication 4 Authorization Request
  • the second unit is configured to: receive a third HTTP request message that is sent by the AF entity and that carries the AF session identifier information, and send a Diameter AAR or Diameter STR message carrying the Diameter session identifier to the PCRF entity during the AF session modification or termination process. ;
  • the third unit is configured to: receive a Diameter RAR, ASR or STA message that is sent by the PCRF entity and carry the Diameter session identifier, and send a second HTTP request carrying the AF session identifier information to the AF, in the bearer layer event reporting process. Message.
  • the embodiment of the present invention further provides a computer program, including program instructions, when the program instruction is executed by an application function entity, so that the application function entity can execute the above method.
  • the embodiment of the invention further provides a computer program, comprising program instructions, when the program instruction is executed by the policy server, so that the policy server can execute the above method.
  • Embodiments of the present invention also provide a carrier carrying any of the above computer programs.
  • the above embodiment solves the problem that the AF entity and the PCRF entity or the PC can perform bidirectional information transmission based on HTTP real time.
  • the embodiment of the invention solves the problem that the AF entity and the PCRF entity or the PC can perform two-way information transmission based on HTTP real-time.

Abstract

L'invention concerne un procédé de gestion de session, une entité à fonction d'application (AF), un serveur de règles et un convertisseur de protocole, qui s'appliquent au domaine des communications. Ledit procédé se déroule de la manière suivante : lorsqu'une entité AF établit une session AF avec un serveur de règles, elle envoie audit serveur un premier message d'appel au protocole HTTP, l'entité AF envoyant des informations d'identification de session AF au serveur de règles par le biais du premier message d'appel au protocole HTTP, ou les informations d'identification de session AF étant attribuées par le serveur de règles et envoyées à l'entité AF par le biais d'une réponse au premier message d'appel au protocole HTTP ; lorsque le serveur de règles communique à l'entité AF un événement de la couche support de ladite session AF, il envoie à ladite entité un second message d'appel au protocole HTTP qui contient les informations d'identification de session AF ; et l'entité AF renvoie au serveur de règles une réponse au second message d'appel au protocole HTTP.
PCT/CN2014/082548 2013-07-26 2014-07-18 Procédé de gestion de session, entité à fonction d'application, serveur de règles et convertisseur de protocole WO2015010576A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP14828651.1A EP3171542B1 (fr) 2013-07-26 2014-07-18 Procédé de gestion de session, entité à fonction d'application, serveur de règles et convertisseur de protocole
US15/506,945 US10225151B2 (en) 2013-07-26 2014-07-18 Session management method, application function entity, policy server and protocol converter

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
CN201310319571.7 2013-07-26
CN201310319571 2013-07-26
PCT/CN2014/075677 WO2014173252A1 (fr) 2013-07-26 2014-04-18 Procédé de gestion de sessions, entité fonctionnelle d'application, serveur de politiques et convertisseur de protocole
CNPCT/CN2014/075677 2014-04-18
CN201410301186.4A CN104348826A (zh) 2013-07-26 2014-06-27 会话管理方法、应用功能实体、策略服务器和协议转换器
CN201410301186.4 2014-06-27

Publications (1)

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

Family

ID=52392715

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/082548 WO2015010576A1 (fr) 2013-07-26 2014-07-18 Procédé de gestion de session, entité à fonction d'application, serveur de règles et convertisseur de protocole

Country Status (1)

Country Link
WO (1) WO2015010576A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111698290A (zh) * 2020-05-19 2020-09-22 展讯通信(天津)有限公司 Pdu会话复用方法、装置、用户设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101217789A (zh) * 2008-01-10 2008-07-09 中兴通讯股份有限公司 一种非漫游场景下策略和计费规则功能服务器的选择方法
CN101583112A (zh) * 2008-08-12 2009-11-18 中兴通讯股份有限公司 会话信息的标识方法及装置
WO2012058643A2 (fr) * 2010-10-29 2012-05-03 F5 Networks, Inc. Système et procédé de conversion de protocole à la volée dans l'obtention d'informations de mise en application de politique

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101217789A (zh) * 2008-01-10 2008-07-09 中兴通讯股份有限公司 一种非漫游场景下策略和计费规则功能服务器的选择方法
CN101583112A (zh) * 2008-08-12 2009-11-18 中兴通讯股份有限公司 会话信息的标识方法及装置
WO2012058643A2 (fr) * 2010-10-29 2012-05-03 F5 Networks, Inc. Système et procédé de conversion de protocole à la volée dans l'obtention d'informations de mise en application de politique

Non-Patent Citations (2)

* 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 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111698290A (zh) * 2020-05-19 2020-09-22 展讯通信(天津)有限公司 Pdu会话复用方法、装置、用户设备及存储介质
CN111698290B (zh) * 2020-05-19 2021-06-15 展讯通信(天津)有限公司 Pdu会话复用方法、装置、用户设备及存储介质

Similar Documents

Publication Publication Date Title
EP3171542B1 (fr) Procédé de gestion de session, entité à fonction d'application, serveur de règles et convertisseur de protocole
KR102546956B1 (ko) 3gpp 네트워크들에서의 소량 데이터 사용 가능
JP7190031B2 (ja) 通信システムにおいてアプリケーションごとにポリシルールを実行するための方法およびデバイス
US8799440B2 (en) Policy and charging control method and system for multi-PDN connections of single APN
US9351325B2 (en) Policy control method and system for converged network
US9215145B2 (en) Policy decision function addressing method, network element and network system
WO2011097911A1 (fr) Procédé, dispositif et système pour sélectionner une entité de fonction de politique et de règles de facturation
WO2008055541A1 (fr) Dispositifs et procédé destinés à garantir des exigences de service sur une base par équipement utilisateur dans un support
WO2015103875A1 (fr) Procédé de gestion de session, serveur de règles, et entité de fonction d'application
WO2009033382A1 (fr) Procédé et dispositif d'élément de réseau destinés à acquérir l'information de contrôle des règles d'une session d'accès ip
WO2011147074A1 (fr) Procédé, système et dispositif associé pour la mise en œuvre d'un contrôle de politique et de tarification
WO2011134327A1 (fr) Procédé et système permettant de déterminer une fonction de règles de politique et de facturation
WO2011144083A2 (fr) Procédé et dispositif de contrôle de règles
WO2014101731A1 (fr) Système et procédé pour l'ouverture de capacités réseau, et éléments de réseau associés
WO2017124807A1 (fr) Procédé de commande de facturation de politique, convertisseur de protocole, appareil et système de règle de facturation de politique
WO2011018020A1 (fr) Procede et systeme de commande d'equilibre de charge de pcrf et dra de redirection
US10205659B2 (en) Information transmission using direct HPCRF communications
WO2014179992A1 (fr) Procédé de traitement d'événement de plan utilisateur, entité pcrf et entité af
WO2015010576A1 (fr) Procédé de gestion de session, entité à fonction d'application, serveur de règles et convertisseur de protocole
WO2013071860A1 (fr) Procédé de décision de règles et dispositif de réseau
WO2011134321A1 (fr) Procédé et système d'envoi de politique pour communication de type machine
WO2011134315A1 (fr) Procédé, dispositif et système pour une autorisation de service
WO2015192620A1 (fr) Procédé et dispositif de transmission d'informations de réseau d'accès
WO2015135124A1 (fr) Procédé et appareil de transfert d'informations
JP5872705B2 (ja) ローミング協定／パートナの抹消を契機とするローミングセッションの終了

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

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 Request for entry into the european phase

Ref document number: 2014828651

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 15506945

Country of ref document: US

Ref document number: 2014828651

Country of ref document: EP