[go: up one dir, main page]

WO2012119656A1 - Association d'une session af à une session ip-can après redémarrage d'un pcrf - Google Patents

Association d'une session af à une session ip-can après redémarrage d'un pcrf Download PDF

Info

Publication number
WO2012119656A1
WO2012119656A1 PCT/EP2011/053593 EP2011053593W WO2012119656A1 WO 2012119656 A1 WO2012119656 A1 WO 2012119656A1 EP 2011053593 W EP2011053593 W EP 2011053593W WO 2012119656 A1 WO2012119656 A1 WO 2012119656A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
pcrf
identification information
user equipment
gateway
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/EP2011/053593
Other languages
English (en)
Inventor
Juha Antero Rasanen
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Solutions and Networks Oy
Original Assignee
Nokia Siemens Networks Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Siemens Networks Oy filed Critical Nokia Siemens Networks Oy
Priority to PCT/EP2011/053593 priority Critical patent/WO2012119656A1/fr
Publication of WO2012119656A1 publication Critical patent/WO2012119656A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0659—Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities
    • H04L41/0661—Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities by reconfiguring faulty entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1045—Proxies, e.g. for session initiation protocol [SIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications

Definitions

  • the present invention relates to the handling of an
  • PCRF Policy and Charging Function
  • the counterpart entity may be e.g. a signalling entity, charging entity, access control entity, authentication and/or authorization and/or accounting entity, gateway or server.
  • PCRF Policy and Charging Rules Function
  • PCEF Policy and Charging Enforcement Function
  • BBERF Bearer binding and Event Reporting Function
  • the PCEF knowing that the PCRF has restarted, establishes a new (Diameter Gx) control session towards the PCRF for the IP-CAN session.
  • Figs. 1 and 2 illustrate the 3GPP EPS architecture examples applicable to the currently specified Rel-10 recovery procedure from a PCRF failure (cf. 3GPP TS 23.401 V10.2.1 and TS 23.402 V10.2.1).
  • Fig. 3 describes the Policy and Charging Control (PCC) architecture in more detail and shows e.g. that the PCRF has an interface to the user data repository (UDR/HSS (home subscriber server) /SPR
  • UDR/HSS home subscriber server
  • Fig. 3 shows a communication system that may comprise a user equipment (UE) (not shown) and a network (not shown) .
  • the network may comprise a policy and charging enforcement function (PCEF) , a PCRF, an
  • AF application function
  • SPR bearer binding and event reporting function
  • OCS online charging system
  • OFCS offline charging system
  • the user may have an IP-CAN session without any PCRF control and no PCRF being
  • Diameter Gx control session towards the PCRF for the IP- CAN session.
  • the AF/P-CSCF Provides a (Rx Diameter) session with the PCRF for the AF session (as described for example in 3GPP TS 29.214 VIO.1.0 / section 4.4.1 "Initial Provisioning of Session Information") and the PCRF is supposed to bind the AF session to an existing IP-CAN session (refer to 3GPP TS 29.213 VIO.0.0 / section 5.2 "Session binding") .
  • the PCRF fails to bind the AF session to any IP-CAN session, because the IP-CAN session related information has not been refreshed at the PCRF after the restart, and consequently, the PCRF rejects the AF session (according to 3GPP TS 29.213 VIO.0.0 / section 5.2 "Session binding" and TS 29.214 VIO.1.0).
  • the AF contacts the PCRF before a possibly related IP-CAN session modification by the UE would cause the PCEF to contact the PCRF (and thus re-establish the missing Gx session) .
  • the AF pushes the negotiated new session
  • the PCRF fails to bind the AF session to any IP-CAN session, because the IP-CAN session related
  • the problem applies also to an IP multimedia subsystem (IMS) registration.
  • IMS IP multimedia subsystem
  • a UE attached to the network before the PCRF restart, tries to register to IMS and the AF/P- CSCF establishes a (Rx Diameter) session with the PCRF (refer to 3GPP TS 29.214 VIO.1.0), the PCRF fails to bind the Rx control session to any IP-CAN session, because the IP-CAN session related information has not been refreshed at the PCRF after the restart.
  • a consequence of the above described problem is that, if a UE is attached to the network but does not have any AF sessions, i.e. has only a default bearer, no AF sessions can be activated to or from the UE and the UE cannot register to IMS, because the PCRF rejects any such attempts due to missing Gx session information at the restarted PCRF. This condition is hard to escape, i.e. this might lead to a kind of a deadlock.
  • the method further comprises:
  • control session is re-established or newly established
  • control session information relates to a Gxx Diameter control session
  • the network session information relates to a Gx Diameter control session
  • controller is a home policy and charging rules function, H-PCRF, the method further comprises
  • an apparatus comprising:
  • transceiver configured to receive a request message requesting an application session
  • the transceiver being further configured to send a request message for requesting identification information of a gateway allocated to a user equipment to a
  • the transceiver being further configured to receive a response message including identification information of the gateway from the subscription register,
  • the transceiver being further configured to send an enquiry to the gateway based on the received identification information of the gateway including identification
  • the transceiver being further configured to receive a request message including network session information corresponding to the identification information of the user equipment, and
  • a binding unit configured to bind the requested application session to the network session.
  • the transceiver is further configured to send an enquiry including identification information of the user equipment to the gateway allocated to the user equipment, and
  • the transceiver is further configured to receive a request message including control session information corresponding to the identification information of the user equipment ;
  • the transceiver is further configured to receive the address of a serving gateway from the gateway allocated to the user equipment, and
  • the transceiver is further configured to use the address of the serving gateway to send to the serving gateway an enquiry including identification information of the user equipment;
  • control session information relates to a Gxx
  • the network session information relates to a Gx
  • the apparatus is a home policy and charging rules function, H-PCRF, and the transceiver is further configured to
  • the apparatus is configured to establish a S9 session; the apparatus being configured to re-establish the S9 session or to newly establish the S9 session.
  • a computer program product comprising code means adapted to produce steps of any of the methods as described above when loaded into the memory of a computer.
  • a computer program product as defined above, wherein the computer program product comprises a computer- readable medium on which the software code portions are stored .
  • Fig. 1 is a diagram illustrating a non-roaming architecture for 3GPP accesses.
  • Fig. 2 is a diagram illustrating another non-roaming architecture for 3GPP accesses.
  • Fig. 3 is a diagram illustrating an example of the Policy and Charging Control (PCC) architecture.
  • PCC Policy and Charging Control
  • Fig. 4 shows a signaling diagram according to another embodiment of the present invention.
  • Fig. 5 shows a signaling diagram according to another embodiment of the present invention.
  • Fig. 6 shows a signaling diagram according to another embodiment of the present invention.
  • Fig. 7 shows a signaling diagram according to another embodiment of the present invention.
  • Fig. 8 shows a signaling diagram according to another embodiment of the present invention.
  • Fig. 9 shows a signaling diagram according to another embodiment of the present invention.
  • Fig. 10 shows a signaling diagram according to another embodiment of the present invention.
  • Fig. 11 shows a signaling diagram according to another embodiment of the present invention.
  • Fig. 12 is a block diagram showing a PCRF according to an embodiment of the present invention.
  • Figs. 4 and 5 show signaling diagrams according to
  • FIG. 4 illustrates an example of application session handling after PCRF restart in non-roaming
  • FIG. 5 illustrates an example of application session handling after PCRF restart in non-roaming architecture for 3GPP Accesses within evolved packet system (EPS) wherein the PCRF controls a policy and charging enforcement function
  • EPS evolved packet system
  • PCEF bearer binding and event reporting
  • the PCRF acquires the identity and/or address of the P-GW allocated to the UE .
  • the PCRF may acquire the identity and/or address through an enquiry to a subscription register (such as e.g. UDR, HSS, SPR) (step S46) .
  • the PCRF sends an enquiry to the PCEF corresponding to the P-GW address (step S48) .
  • the enquiry includes relevant parameters needed for session binding (the minimum being an IP address of the UE, and possibly in addition a user ID) .
  • the message exchange realizing the enquiry may rely on a general purpose control session, or on transactional / non-session based message exchange, instead of a per-user control session, because the per-user (Gx Diameter) control session does not exist due to the PCRF restart, and setting up a new (Diameter) control session is usually initiated by the client (the client in this case being the PCEF) .
  • the message exchange realizing the enquiry may also use a different protocol than the per-user control session that is being requested to be set up.
  • a further condition (in addition to the session binding failure) for the PCRF to acquire the P-GW address and to send an enquiry to the PCEF may be that the PCRF knows that it has restarted and this may be the reason for the binding failure .
  • the PCEF can then verify that a corresponding IP-CAN session exists (step S410) and can re-establish/refresh the (Gx Diameter) control session for the IP-CAN session by sending a request message with relevant parameters to the PCRF (step S411), or alternatively, can establish a new (Gx Diameter) control session for the IP-CAN session by sending a request message with relevant parameters to the PCRF.
  • the PCRF acquires the identity and/or address of the P-GW allocated to the UE .
  • the PCRF may acquire the identity and/or address through an enquiry to a subscription register (such as e.g. UDR, HSS, SPR) (step S56) .
  • the PCRF sends an enquiry to the PCEF corresponding to the P-GW address (step S58) .
  • the enquiry includes relevant parameters needed for session binding (the minimum being an IP address of the UE, and possibly in addition a user ID) .
  • a further condition (in addition to the session binding failure) for the PCRF to acquire the P-GW address and to send an enquiry to the PCEF may be that the PCRF knows that it has restarted and this may be the reason for the binding failure .
  • the PCEF can then verify that a corresponding IP-CAN session exists (step S510) and can re-establish/refresh the (Gx Diameter) control session for the IP-CAN session by sending a request message with relevant parameters to the PCRF (step S511), or alternatively, can establish a new (Gx Diameter) control session for the IP-CAN session by sending a request message with relevant parameters to the PCRF.
  • the P-GW may provide the PCRF with the address and/or identity of the S-GW.
  • the PCRF may then send a
  • the BBERF can then re-establish/refresh the (Gxx Diameter) control session by sending a request message with relevant parameters to the PCRF (step S517), or
  • the PCRF can bind the AF session to the IP-CAN session and the AF session with possibly related IP-CAN session and/or bearer level operations can proceed normally.
  • a similar procedure as described above can also be applied at a home PCRF (H-PCRF) towards the visited PCRF (V-PCRF) , when the home PCRF restarts in a home routed case (i.e. in a case where the UE is roaming in a visited network but the AF/P- CSCF and the P-GW are in the home network of the
  • Fig. 6 shows a signaling diagram according to another embodiment of the present invention.
  • the UE is roaming in a visited network, but the connection is home-routed, i.e. the P-GW and AF/P-CSCF are in the home network of the user.
  • step S62 the H-PCRF restarts, for example, due to a failure, and the session data is lost.
  • the H-PCRF receives application / AF session information including the UE IP address and User ID from the AF (step S64) .
  • the H-PCRF fails to bind the application / AF session to an IP-CAN session or to an S9 BBERF/Gxx related session due to loss of session data at the restart (step S65) .
  • the H-PCRF may request user information or a subscription profile related to the identified user from the UDR/HSS/SPR (steps S66 and S67) .
  • the information may comprise the P-GW address / identity of the P-GW allocated to the user/UE.
  • the H-PCRF may use the P-GW address / address domain or the UE IP address / address domain to resolve or deduce the V-PCRF address for sending a request to the V-PCRF to (re-) establish (the) a relevant BBERF/Gxx related S9 control session (steps S68 and S69) .
  • the V-PCRF is able to bind the IP address of the UE to an existing session (step S612) and consequently completes the S9 session (re-) establishment (e.g. as with steps S614 to S616) .
  • the H-PCRF may send a request to the PCEF to get a relevant Gx control session (re-) established (steps S610 and S611) .
  • the PCEF is able to bind the IP address of the UE to an existing IP-CAN session (step S613) and consequently completes the Gx session (re-) establishment (e.g. as with steps S617 to S619) .
  • the message exchange realizing the enquiry may rely on a general purpose control session, or on transactional / non-session based message exchange, instead of a per-user control session, because the per-user (Gx Diameter) control session does not exist due to the PCRF restart, and setting up a new (Diameter) control session is usually initiated by the client (the client in this case being the PCEF) .
  • the message exchange realizing the enquiry may also use a different protocol than the per ⁇ user control session that is being requested to be set up.
  • the following procedure can be applied when the V-PCRF restarts in a home routed case (i.e. in a case where the UE is roaming in a visited network but the AF/P-CSCF and the P-GW are in the home network of the subscriber) .
  • the H-PCRF knows (through a
  • the H-PCRF receives application / AF session information including the UE IP address and User ID from the AF (step S74) .
  • the H-PCRF fails to bind the application / AF session to an S9 BBERF/Gxx related session due to loss/removal of session data at the restart of the V-PCRF (step S75) , i.e. the H-PCRF, knowing that the V-PCRF has restarted, may have deleted the session data.
  • the H-PCRF pushes PCC rules to PCEF and gets S-GW address from PCEF (steps S76 and S77) .
  • the H-PCRF requests (re-) establishment of a relevant
  • BBERF/Gxx related S9 control session (steps S78 to S711), and may send the S-GW address and QoS rules to the V-PCRF in this context.
  • the V-PCRF may send a request to the BBERF corresponding to the S-GW address / identity to get a relevant Gxx control session (re-) established (steps S714 to S718) .
  • the following procedure, as illustrated in Fig. 8, can be applied when the H-PCRF restarts in a case where the UE is roaming in a visited network and the AF/P-CSCF and P-GW are in the visited network.
  • the H-PCRF restarts and session data is lost (step S82) .
  • the H- PCRF receives application / AF session information
  • step S84 the restarted H-PCRF cannot bind the AF session to any S9 BBERF/Gxx related session (step S86).
  • the H-PCRF may use the response message
  • step S87 to the application / AF session information message (step S85) for triggering the V-PCRF to (re-) establish a relevant BBERF/Gxx related S9 control session with the H-PCRF.
  • the H-PCRF may resolve or deduce the V-PCRF address from the application / AF session related message received from the V-PCRF and for send a separate request to the V-PCRF to (re-) establish a relevant BBERF/Gxx related S9 control session (steps S88 and S89) .
  • the V-PCRF is able to bind the IP address of the UE to existing Gx and/or Gxx sessions and consequently completes the S9 session (re-) establishment (e.g. as with steps S810 and S811) .
  • the V-PCRF may push the relevant PCC and QoS rules to the PCEF and BBERF, respectively, as per steps S813 to S816.
  • the following procedure as illustrated in Fig. 9, can be applied when the V-PCRF restarts in a case where the UE is roaming in a visited network and the AF/P-CSCF and P-GW are in the visited network.
  • the V-PCRF restarts and session data is lost (step S92) .
  • the AF establishes an application / AF related Rx control session to the V-PCRF
  • the V-PCRF establishes an application / AF related S9 control session to the H-PCRF
  • the H-PCRF receives application / AF session information including the UE IP address and User ID from the V-PCRF (steps S94 and S95) .
  • the H-PCRF cannot bind the new AF session to any S9 BBERF/Gxx related session (step S96) , because the H-PCRF has deleted the obsolete V-PCRF related S9 session data when noticing the V-PCRF restart.
  • the H-PCRF may request user information or a subscription profile related to the identified user from the UDR/HSS/SPR (steps S97 and S98) .
  • the information may comprise the P-GW address / identity of the P-GW allocated to the user/UE.
  • the H-PCRF may send the P-GW address / identity to the V-PCRF in the response message (step S99) .
  • the V-PCRF may send a request to the PCEF corresponding to the P-GW address / identity to get a relevant Gx control session (re-) established (steps S912 to S915) .
  • the V-PCRF may get the S-GW address and/or identity from the PCEF/P-GW. Then the V-PCRF may send a request to the BBERF
  • the following procedure can be applied at a H-PCRF towards the V-PCRF, when the H-PCRF restarts in a case where the UE is roaming in a visited network, the P-GW is in the visited network and the AF/P- CSCF is in the home network.
  • the H-PCRF restarts and session data is lost (step S102) .
  • the H- PCRF receives application / AF session information
  • the H-PCRF fails to bind the application / AF session to a S9 session towards the V-PCRF due to loss of session data at the restart (step S105) .
  • the H-PCRF may request user information or a subscription profile related to the identified user from the UDR/HSS/SPR (steps S106 and S107) .
  • the information may comprise the P-GW address / identity of the P-GW allocated to the user/UE.
  • the H-PCRF may use the P-GW address / address domain or the UE IP address / address domain to resolve or deduce the V-PCRF address for sending a request to the V-PCRF to (re-) establish (the) a relevant S9 control session (steps S108 to S1010) .
  • the V- PCRF is able to bind the IP address of the UE to an
  • the V-PCRF may push the relevant PCC and QoS rules to the PCEF and BBERF, respectively, as per steps S1014 to S1017.
  • the following procedure, as illustrated in Fig. 11 can be applied, when the V-PCRF restarts in a case where the UE is roaming in a visited network, the P-GW is in the visited network and the AF/P-CSCF is in the home network.
  • the V-PCRF restarts and session data is lost (step S112) .
  • the H- PCRF receives application / AF session information
  • the H-PCRF fails to bind the application / AF session to an S9 session towards the V-PCRF (step S115) , because the H-PCRF has deleted the obsolete V-PCRF related S9 session data when noticing the V-PCRF restart.
  • the H- PCRF may request user information or a subscription profile related to the identified user from the UDR/HSS/SPR (steps S116 and S117) .
  • the information may comprise the P-GW address / identity of the P-GW allocated to the user/UE.
  • the H-PCRF may use the P-GW address / address domain or the UE IP address / address domain to resolve or deduce the V-PCRF address for sending a request to the V-PCRF to (re-) establish a relevant S9 control session with the H-PCRF (steps S118 to S1112) .
  • the request message may contain the P-GW address / identity.
  • the V-PCRF may send a request to the PCEF corresponding to the P-GW address / identity to get a relevant Gx control session (re-) established (steps S1115 to S1118) .
  • the V-PCRF may get the S-GW address and/or identity from the PCEF/P- GW. Then the V-PCRF may send a request to the BBERF
  • the transport of the P-GW address/ identity shall be supported in the Ud interface protocol between the UDR and the PCRF.
  • the PCRF needs internal logic to utilize the P-GW address/ identity for contacting the PCEF, possibly with a user/UE independent and/or an IP-CAN independent / general purpose session related or
  • PCEF/BBERF needs to understand the request (to (re-) establish (the) a control session) sent by PCRF and perform the requested (re-) establishment operation.
  • the PCEF/P-GW shall send the BBERF/S-GW address to the PCRF.
  • the BBERF needs to understand the request (to (re-) establish (the) a Gxx control session) sent by PCRF and perform the requested (re-) establishment operation.
  • the present invention provides a light weight recovery from a PCRF restart not requiring heavy redundancy schemes nor heavy message exchange
  • FIG. 12 is a block diagram showing a PCRF according to an embodiment of the present invention.
  • the PCRF 120 comprises a transceiver 121 for sending and receiving various messages to and from various entities, like e.g. the AF, the PCEF, the BBERF etc. Further, the PCRF comprises a binding unit 121 for performing session binding, as described above. Further, the PCRF comprises a resolving unit 123 for resolving the address of the counterpart entity, as described above.
  • the PCRF may comprise further units that are necessary for its respective operation. However, a description of these units is omitted in this specification.
  • PCRF is used only as an example of a control entity and the related counterpart network entities are used as examples of possible related network entities.
  • control entity like e.g. a signalling entity, charging entity, access control entity, authentication and/or authorization and/or accounting entity, where the control entity controls operations (like e.g. user or user session related or network operations and/or management related operations) in another network entity or other network entities applying a control protocol between the entities.
  • the counterpart entity may be e.g. a signalling entity, charging entity, access control entity,
  • the entity where an address / identity of a counterpart entity is fetched from, may be any kind of network entity, like e.g. gateway, server, signalling entity, control entity, having access to the address / identity.
  • the entities may operate in any kind of a communication network, like e.g. mobile network and/or fixed network.
  • any method step is suitable to be implemented as software or by hardware without changing the idea of the embodiments and its modification in terms of the
  • MOS Metal Oxide Semiconductor
  • CMOS complementary metal oxide semiconductor
  • apparatuses and user equipments can be implemented as individual devices, units or means, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device, unit or means is preserved;
  • an apparatus may be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of an apparatus or module, instead of being hardware implemented, be implemented as software in a (software) module such as a computer program or a computer program product comprising executable software code
  • a device may be regarded as an apparatus or as an
  • respective functional blocks or elements according to above-described aspects can be implemented by any known means, either in hardware and/or software, respectively, if it is only adapted to perform the described functions of the respective parts.
  • the mentioned method steps can be realized in individual functional blocks or by individual devices, or one or more of the method steps can be realized in a single functional block or by a single device.
  • any method step is suitable to be implemented as software or by hardware without changing the idea of the present invention.
  • Devices and means can be implemented as individual devices, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device is preserved. Such and similar principles are to be considered as known to a skilled person.
  • Software in the sense of the present description comprises software code as such comprising code means or portions or a computer program or a computer program product for performing the respective functions, as well as software

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne un procédé, un appareil et un produit de programme informatique destinés à gérer une session d'application après le redémarrage d'une unité de commande. Selon la présente invention, une unité de commande reçoit un message de demande demandant une session d'application, l'unité de commande envoie un message de demande demandant des informations d'identification d'une passerelle allouée à un équipement utilisateur à un registre d'abonnement, l'unité de commande reçoit un message de réponse contenant des informations d'identification de la passerelle en provenance du registre d'abonnement, l'unité de commande envoie une requête à la passerelle ayant pour base les informations d'identification reçues de la passerelle et contenant des informations d'identification de l'équipement utilisateur, l'unité de commande reçoit un message de demande contenant des informations de session de réseau correspondant aux informations d'identification de l'équipement utilisateur, et l'unité de commande associe la session d'application demandée à la session de réseau.
PCT/EP2011/053593 2011-03-10 2011-03-10 Association d'une session af à une session ip-can après redémarrage d'un pcrf Ceased WO2012119656A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2011/053593 WO2012119656A1 (fr) 2011-03-10 2011-03-10 Association d'une session af à une session ip-can après redémarrage d'un pcrf

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2011/053593 WO2012119656A1 (fr) 2011-03-10 2011-03-10 Association d'une session af à une session ip-can après redémarrage d'un pcrf

Publications (1)

Publication Number Publication Date
WO2012119656A1 true WO2012119656A1 (fr) 2012-09-13

Family

ID=44625346

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2011/053593 Ceased WO2012119656A1 (fr) 2011-03-10 2011-03-10 Association d'une session af à une session ip-can après redémarrage d'un pcrf

Country Status (1)

Country Link
WO (1) WO2012119656A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2016503610A (ja) * 2012-11-13 2016-02-04 ホアウェイ・テクノロジーズ・カンパニー・リミテッド パケットに関する情報を取得するための方法およびネットワーク要素
US10284420B2 (en) 2017-02-19 2019-05-07 Cisco Technology, Inc. System and method to facilitate network element failure detection and session restoration in a network environment
CN120434640A (zh) * 2025-07-09 2025-08-05 武汉博易讯信息科技有限公司 一种Diameter信令信息的会话关联方法及相关设备

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Study on PCRF failure and restoration (Release 10)", 3GPP STANDARD; 3GPP TR 29.816, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V10.0.0, 1 October 2010 (2010-10-01), pages 1 - 63, XP050442432 *
"Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Policy and charging control signalling flows and Quality of Service (QoS) parameter mapping (3GPP TS 29.213 version 9.5.0 Release 9)", TECHNICAL SPECIFICATION, EUROPEAN TELECOMMUNICATIONS STANDARDS INSTITUTE (ETSI), 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS ; FRANCE, vol. 3GPP CT 3, no. V9.5.0, 1 January 2011 (2011-01-01), XP014062002 *
"Universal Mobile Telecommunications System (UMTS); LTE; Policy and charging control over Rx reference point (3GPP TS 29.214 version 9.5.0 Release 9)", TECHNICAL SPECIFICATION, EUROPEAN TELECOMMUNICATIONS STANDARDS INSTITUTE (ETSI), 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS ; FRANCE, vol. 3GPP CT 3, no. V9.5.0, 1 January 2011 (2011-01-01), XP014062005 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2016503610A (ja) * 2012-11-13 2016-02-04 ホアウェイ・テクノロジーズ・カンパニー・リミテッド パケットに関する情報を取得するための方法およびネットワーク要素
US10080156B2 (en) 2012-11-13 2018-09-18 Huawei Technologies Co., Ltd. Method and network element for acquiring information about packet
US10284420B2 (en) 2017-02-19 2019-05-07 Cisco Technology, Inc. System and method to facilitate network element failure detection and session restoration in a network environment
US11121911B2 (en) 2017-02-19 2021-09-14 Cisco Technology, Inc. System and method to facilitate network element failure detection and session restoration in a network environment
CN120434640A (zh) * 2025-07-09 2025-08-05 武汉博易讯信息科技有限公司 一种Diameter信令信息的会话关联方法及相关设备

Similar Documents

Publication Publication Date Title
US9258368B2 (en) Methods, apparatuses, and related computer program product for network element recovery
US8837500B2 (en) Service data flow direction/redirection
DK3007406T3 (en) PROCEDURE, DEVICES AND COMPUTER PROGRAM FOR DYNAMIC CONFIGURATION OF A PROXY CALL SESSION CONTROL FUNCTION OF THE IP MULTIMEDIA SUBSYSTEM FROM A POLICY CONTROL RULES SERVER
US8839382B2 (en) Mobile network operator and data service provider interoperation
US9641624B2 (en) Service provisioning in a communications system
US8799440B2 (en) Policy and charging control method and system for multi-PDN connections of single APN
US20120042059A1 (en) Method for indicating a service priority update, service priority update method and apparatus
KR20160064885A (ko) 단말간 스폰서링 서비스를 제공하기 위한 방법 및 장치
CN101588326B (zh) 网关控制会话和Gx会话关联的方法、设备和系统
CN102131172B (zh) 业务处理方法及系统
US10326604B2 (en) Policy and charging rules function (PCRF) selection
US11470512B2 (en) Network-based policy control for simultaneous accesses
WO2012119656A1 (fr) Association d'une session af à une session ip-can après redémarrage d'un pcrf
US9467852B2 (en) Detection of non-entitlement of a subscriber to a service in communication networks
CN101998515B (zh) 控制pcrf负载均衡的实现方法和实现系统
WO2013178183A1 (fr) Procédé et dispositif de traitement de mise à jour de la qualité de service
US11438879B2 (en) Method of enabling a standalone Traffic Detection Function, TDF, node in a telecommunication network to act on unsuccessful resource allocation for an over-the-top, OTT application
EP3086593A1 (fr) Entité de réseau et procédé permettant de surveiller un service ims
EP2866414A1 (fr) Découverte de noeud proxy
EP2915286B1 (fr) Gestion d'un groupe géré par politique

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

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

Country of ref document: EP

Kind code of ref document: A1