WO2011099523A1 - Pcrf, procédé de reprise après anomalie, et système - Google Patents

Pcrf, procédé de reprise après anomalie, et système Download PDF

Info

Publication number
WO2011099523A1
WO2011099523A1 PCT/JP2011/052757 JP2011052757W WO2011099523A1 WO 2011099523 A1 WO2011099523 A1 WO 2011099523A1 JP 2011052757 W JP2011052757 W JP 2011052757W WO 2011099523 A1 WO2011099523 A1 WO 2011099523A1
Authority
WO
WIPO (PCT)
Prior art keywords
pcrf
node
session information
pcc
pgw
Prior art date
Application number
PCT/JP2011/052757
Other languages
English (en)
Japanese (ja)
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
Application filed by 日本電気株式会社, エヌイーシー ヨーロッパ リミテッド filed Critical 日本電気株式会社
Publication of WO2011099523A1 publication Critical patent/WO2011099523A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment

Definitions

  • the present invention is based on the priority claim of Japanese Patent Application No. 2010-028189 (filed on Feb. 10, 2010), the entire contents of which are incorporated herein by reference. Shall.
  • the present invention relates to a communication system, and more particularly to a PCRF and its failure recovery method and system.
  • SAE System Architecture Evolution
  • EPC Evolved Packet Core
  • 3G Third Generation
  • LTE Long Term Evolution
  • Network architecture Some of the abbreviations associated with the EPC network that are used herein are illustrated below.
  • eNodeB evolved NodeB
  • HSS Home Subscribe Server
  • MME Mobility Management Entity
  • UMTS Universal Mobile Telecommunications System
  • NodeB BTS (Base Transceiver Station)
  • PGW Packet Data Network Gateway
  • RNC Radio Network Controller
  • SGW Serving Gateway
  • SGSN Serving GPRS (General Packet Radio Service) Support Node;
  • Non-Patent Document 1 Some of the abbreviations related to the PCC (Policy and Charging Control) architecture are exemplified in this specification (see Non-Patent Document 1, etc.).
  • AF Application Function
  • BBERF Bearer Binding and Event Reporting Function
  • DRA Diameter Routing Agent
  • IP-CAN IP Connectivity Access Network
  • OCS Online Charging System
  • PCEF Policy and Charging Enforcement Function Function
  • PCRF Policy and Charging Rules Function
  • An EPC network that accommodates wireless access such as LTE and 3GPP (3rd Generation Partnership Project) includes SGW, PGW, PCRF, and LTE wireless access accommodation network that constitute a core network that does not depend on wireless access, as shown in FIG. It comprises an MME, an eNodeB, and the like. Each of these nodes is outlined below.
  • the PGW connects a UE (User Equipment) to a service network (an external packet network such as a Web browsing service or IMS (IP Multimedia Subsystem)).
  • a service network an external packet network such as a Web browsing service or IMS (IP Multimedia Subsystem)
  • the PGW performs application of policies whose rules are determined by the PCRF, charging, packet filtering, and the like.
  • the SGW accommodates LTE and 3GPP radio, transmits user data, switches user data transfer paths between LTE and 3GPP radio access accommodating networks, and performs routing.
  • the SGW functions as a mobility anchor for the user plane during handover between the UE's eNodeBs.
  • the SGW stores and manages UE context (IP bearer service parameters and routing information inside the network).
  • the MME is responsible for terminal mobility management and authentication in LTE wireless access, and setting of a user data transfer path between the SGW and the eNodeB. Involved in idle mode UE tracking, paging, bearer (eNodeB, logical packet transmission path between SGW / PGW, etc.) activation / deactivation process (authorization process), and selecting SGW during UE handover in LTE Do. In addition, the MME performs user authentication together with the HSS.
  • the UE, MME, SGW (BBERF), and PGW (PCEF) manage the path (bearer) that affects the communication of the UE (User Equipment) in the network configuration of the EPC.
  • the PCRF holds BBERF (SGW), PCEF (PGW), and session information.
  • SGW BBERF
  • PGW PCEF
  • session information The interface between the PCRF and the PCEF / BBERF (the session path between the PCRF / PGW and the session path between the PCRF / SGW in FIG. 1) is a DIAMETER protocol (IETF (The Internet Engineering Task Force) RFC (Request For Comments 35) RFC. ) Is used.
  • DIAMETER protocol IETF (The Internet Engineering Task Force) RFC (Request For Comments 35) RFC.
  • the PCRF performs policy and charging rule functions, and determines policy control and charging control rules such as QoS (control of communication quality such as packet priority transfer) applied in the PGW and SGW.
  • QoS control of communication quality such as packet priority transfer
  • the PCC session means an IP-CAN session, a gateway control session, an AF session, and related information.
  • a PCC session even when only a specific session (for example, a gateway control session) is indicated, it may be referred to as a PCC session.
  • Non-Patent Document 2 proposes several solutions. Based on the items described in Non-Patent Document 2, each solution is outlined below. It should be noted that none of these solutions are final and that a wide range of studies are currently underway regarding feasibility and the like.
  • Solution 1 For failure of PCRF, redirect to another PCRF by DRA.
  • a PCRF client such as PGW
  • a DIAMETER request message indicating a PCRF failure is sent to the DRA.
  • the DRA selects a new PCRF 2 and sends a redirect response to the client.
  • Solution 2 In a single PCRF, the PCRF client monitors the PCRF for faults by sending a watchdog request message. Handling of a session when detecting a PCRF failure is implementation specific. Since the PCC session information is unknown when the PCRF is restarted, the PCC session information is reconstructed. The reconstruction of the PCC session information is performed according to the following Solution 5 or 6, for example.
  • Solution 5 When the PCRF loses the session information due to the failure of the PCRF, the PCC rule is resynchronized for the bearer and the AF session between the PCRF and the PCRF client. In this case, the PCRF needs to store information of all clients having a session in the nonvolatile memory. The PCC session state is restored on the failed or alternate PCRF.
  • a PCRF client that has received a recovery request from a failed PCRF node or a manual setting or a triggering entity such as TMN (Telecommunication Manual network) schedules the signaling for recovery, and includes a request (CC ⁇ Session establishment request) is sent to the target PCRF node.
  • the PCRF node establishes a PCC session and sends data to the PCRF client.
  • the PCRF client sends a recovered session confirmation message to the triggering entity. After repeatedly sending a CC-session establishment request from the PCRF client to the target PCRF node and sending a confirmation message to the triggering entity by the PCRF client that has received a response from the target PCRF node, the PCRF client performs a final confirmation. To the triggering entity.
  • the PCRF notifies the client (PCRF client) related to the PCRF of the restart.
  • the client responds with a PCRF failure, the user ID of the DIAMETER session at the time of restart, and the like.
  • the PCRF notifies the client of the restart, and the client transmits basic information such as the PCRF failure and the user ID of the DIAMETER session that was active at the time of the restart to the PCRF.
  • the PCEF recognizes the necessity of transmitting the DIAMETER CC (Credit Control) -Request to the PCRF for the modification of the IP-CAN session, and transmits the CC-Request to the PCRF.
  • DIAMETER CC Clear Control
  • the PCEF transmits to the PCRF the DIAMETER session related information (user ID, IP address, PCC / QoS rule, etc.) necessary to reconstruct the session state and information in which the PCRF has been lost.
  • the PCRF reconstructs a Gx DIAMETER session based on information from the PCEF.
  • the PCRF sends a restoration request message along with user identification parameters (user ID, IP address) to the associated client (AF / P-CSCF) to reconstruct the associated lost Rx DIAMETER session Request information.
  • the client (AF / P-CSCF) that has received the recovery request sends the information related to the DIAMETER Rx session (user ID, IP address, session information) lost in the PCRF due to failure and restart to ACK (acknowledgement) to the recovery request.
  • the PCRF which reconstructs the lost Rx DIAMETER session based on the session related information from the client (AF / P-CSCF).
  • the PCRF makes an authorization response to the CC-Request from the PCEF using the CC-Answer and related parameters (for example, PCC rules).
  • 3GPP TS 23.203 V9.3.0 2009-12
  • 3rd Generation Partnership Project Technical Specification Group Services and System Aspects
  • Policy and charging control architecture (Release 9) (4.1 General requirements, 4.2 Charging related requirements , 6.2 Functional entities, 6.3 Policy and charging control rule) 3GPP TR 29.816 V0.3.0 (2009-11) 3rd Generation Partnership Project; Technical Specification Group Core and Renewal (StudyFrequency).
  • the temporary service stop of the PCRF does not affect the path (bearer), but the service related to QoS cannot be provided because the PCC session information is lost. For this reason, it is necessary to newly generate a PCC session by releasing the path (bearer) and re-establishing the path (bearer). As a result, there is a problem that a temporary service stop of the PCRF that does not originally affect the path (bearer) has an effect in the form of disconnection / connection of the path (bearer).
  • the bearer In the EPC, the bearer is always held from the principle of Always-On (always connected), and the disconnection of the bearer means detachment, which has a great influence on usability.
  • PCRF does not directly hold bearers. For this reason, the temporary service stop due to the failure of the PCRF does not actually affect the communication.
  • inconsistencies in the session information between the PCRF and SGW / PGW may cause problems such as the TA update (Tracking Area update), handover, and the dedicated bearer (dedicated bearer) establishment process based on requests from the AF. is there. For this reason, bearer re-stretching (disconnection / reconnection) is required.
  • the present invention provides a completely different approach from the solutions 1 to 6 proposed in Non-Patent Document 3 for the loss of PCC session information in the resumption of PCRF. It is.
  • An object of the present invention is to provide a system, a method, and an apparatus capable of recovering a PCC session without affecting a bearer when a temporary service stop due to a PCRF failure occurs.
  • the PCRF node includes a PCRF node that manages a QoS (Quality Of Service) and a charging policy, and one or a plurality of PCRF client nodes that form clients of the PCRF node, PCC (Policy and Charging Control) session information is transmitted to at least one of the PCRF client nodes, the PCRF client node receiving the PCC session information from the PCRF node holds the PCC session information, and after the PCRF restarts, The PCF session information is transmitted from the PCRF client node to the PCRF node, and the PCRF node receives the PF from the PCRF client node.
  • Network system is provided for performing a recovery PCC session receives C session information.
  • restart or “resume PCRF” means that the PCRF is initially set by a service stop due to a failure or an intentional service stop for maintenance or the like. This means that the operation is performed, and as a result of the restart, session information necessary for the operation as the PCRF is lost.
  • a Policy and Charging Rules Function (PCRF) device that manages QoS (Quality of Service) and charging policies, and PCC (Policy and Charging Control) session information to at least one PCRF client.
  • PCRF Policy and Charging Rules Function
  • Policy and Charging Control Policy and Charging Control
  • a Policy and Charging Rules Function (PCRF) node distributes PCRF-related information including PCC session information to one or more PCRF client nodes that are other nodes in a transparent format.
  • PCRF Policy and Charging Rules Function
  • a method is provided. According to the method of the present invention, the PCRF client node holds PCC session information, and after resuming the PCRF, the PCRF client node returns the PCC session information to the PCRF node, and the PCRF node returns the PCC session information. The receiving PCC session data is restored.
  • the PCC session can be recovered without affecting the bearer when a temporary service stop due to a PCRF failure occurs.
  • EPC network It is a figure which shows the structure of the 1st Embodiment of this invention. It is a figure explaining the operation
  • the PCRF distributes PCC session information to at least one of the PCRF clients.
  • the PCRF resumes PCC session information is lost
  • the PCC session information is transmitted from the PCRF client to the PCRF, and the PCC session is restored. That is, according to one of the concepts of the aspects of the present invention, in the PCC architecture (EPC network), the PCRF transmits PCRF related information transparently to other nodes, eg, one or more PCRF clients. Distribute in format.
  • PCC session information container (PCC session information container: abbreviated as “PCC container” or sometimes referred to as “PCRF container”) is defined as information as shown in FIG.
  • PCRF client that receives the PCC session information container from the PCRF and stores it therein does not need to understand the detailed contents and internal structure of the PCC session information container. That is, the PCRF client does not need to interpret (decode) the PCC session information container.
  • the PCC session information container consumes memory in the PCRF client, and the recovery process of the PCRF is prolonged. Therefore, the recovery function is limited only to high priority sessions. It is also beneficial to do.
  • priority handling is performed in the PCRF based on, for example, operator policy. For example, priority is given to an IMS (IP Multimedia Subsystem) related session, or the priority of the session is determined based on subscription (subscriber information).
  • the PCRF may be configured not to distribute the PCC session information container to the PCRF client of a session that is not explicitly a recovery process target.
  • the PCRF client may notify the PCRF of capability information through initial signaling.
  • the PCRF stores the PCC session information held by the PCRF in at least one of the PCF, BBERF, or AF that is the PCRF client, and when the PCRF is resumed, Alternatively, the PCC session information may be received from at least one of BBERF or AF, and the PCC session may be recovered. With this configuration, it is possible to improve the reliability of the network in the EPC without depending on whether the PCRF is a redundant configuration.
  • the PCRF when establishing / updating a session between PCRF-PCEF / PCRF-BBERF, the PCRF may notify the PCEF / BBERF of session information.
  • the PCF / BBERF pushes PCC session information to the PCRF. As a result, the PCRF session is recovered without releasing the established session.
  • the session information is recovered between PCRF-PCEF or PCRF-BBERF, so that the temporary path of the PCRF is established for the path (bearer) established between UE-PCEF (PGW). It is possible to avoid the effect of a service interruption.
  • PCC session information for a PCRF client (peripheral device) (PCEF, BBERF, AF, etc.), and PCRF restart.
  • PCEF peripheral device
  • BBERF basic bit error field
  • AF AF
  • PCRF restart As a result of adding the processing later, it may be considered that the recovery time of the PCRF is influenced as a result (negative factor).
  • the above-described advantages of the present invention can be provided to a service provider by enabling application in units of subscribers and further in units of APN (Access Point Name).
  • the system can be designed in consideration of the balance with the negative factor related to the recovery time of the PCRF.
  • the PCRF can improve the availability of the PCRF by cooperating with the PCRF client and multiplexing and managing only the minimum necessary information.
  • the present invention enables service providers to ensure and maintain high availability without imposing a large capital investment, and its cost merit is great.
  • the PCEF / BBERF when the PCRF recovers from a temporary service stop, notifies the PCRF of PCC session information without affecting the path (bearer). The state between PCRF-PCEF / BBERF is restored.
  • FIG. 2 is a schematic diagram for explaining the present invention.
  • FIG. 2 schematically shows on the time axis the PCRF, the event generated in the PGW / SGW that is PCEF / BBERF, and the exchange of signals between the PCRF and the PGW / SGW.
  • the arrows drawn horizontally from the PCRF and PGW / SGW to the right of the figure represent time, respectively.
  • ⁇ 8. Represents a step number.
  • a trigger related to the establishment of a bearer in the PGW / SGW occurs.
  • the SGW / PGW sends a CC (Credit Control) -session establishment request to the PCRF.
  • CC Cell Control
  • the PCRF Upon receiving the CC-session establishment request, the PCRF makes a CC-session establishment authorization decision and returns a CC-session establishment response. At this time, the PCRF gives PCC session information to the CC-session establishment response to the SGW / PGW and returns it as a CC-session establishment response.
  • the SGW / PGW that has received the CC-session establishment response in which the PCC session information is set holds the PCC session information.
  • the SGW / PGW detects the resumption of the corresponding PCRF.
  • the SGW / PGW transmits a message in which the PCC session information is added to the CC-session recovery request to the PCRF as a message newly introduced by the present invention (step 7).
  • the PCRF that has received the CC-session recovery request can reconstruct the session information from the PCC session information attached to the message, and can recover the session state before the restart occurred.
  • the PCRF saves and holds the PCC session information in the SGW / PGW, receives the PCC session information from the SGW / PGW when the PCRF restarts, and enters the session state before the restart. It is restored.
  • the SGW / PGW can recover the PCC session state without releasing the bearer related to the session.
  • the present invention will be described with reference to some embodiments.
  • FIG. 3 is a diagram showing a configuration of the first exemplary embodiment of the present invention.
  • the network configuration itself is the same as that of a normal EPC network.
  • UE (1, 2) indicates a mobile device such as a mobile phone.
  • ENodeB (11) is, for example, an LTE base station.
  • Node B (21) and RNC (31) indicate radio access devices employed in UMTS (Universal Mobile Telecommunications System).
  • the MME (41) is a device that manages mobility introduced by EPC.
  • SGSN (51) is a serving device used for UMTS.
  • the SGW is a device that handles the user plane in the area.
  • the PGW is a gateway device that connects an external packet network (service network (91)) and EPC.
  • the PCRF (81) is a device (server node) that manages QoS and charging policies, and is a unit for linking a session called “CC-session” with the SGW and PGW and the UE1, UE2, and the service network (91). Established for each IP-CAN session.
  • the PCRF does not handle the user plane.
  • the HSS (101) is a node (subscriber information management server) that holds subscriber profile information such as the subscriber number and location information in the IP telephone network.
  • the PCRF acquires profile information from the HSS (101) as necessary.
  • FIG. 4 is a diagram for explaining a comparative example of the present invention.
  • FIG. 4 illustrates an operation sequence of PGW activation and disconnection after the occurrence of a temporary service stop of the PCRF from “LTE attach”. Note that numbers 1 to 10 assigned to each operation represent a sequence operation number (step number).
  • An attach request (Attach Request) is transmitted from the UE to the MME.
  • the attach request from the UE is a request for registering the UE in the network, such as when the UE is powered on.
  • the MME that has received the attach request from the UE performs authentication and concealment processing between the UE / eNB (eNODEB).
  • the MME transmits a session creation request (Create Session Request) to the SGW via the S11 interface (GPRS Tunneling Protocol V2 (GTPv2)).
  • GPRS Tunneling Protocol V2 GTPv2
  • the SGW transmits a session creation request (Create Session Request) to the PGW via the S5 / S8 interface (GTPv2).
  • the PGW sends a credit control request (CC-Request (initial)) to the PCRF.
  • the initial of the CC-Request (initial) indicates that the request type (CC-Request Type) is initial.
  • the PCRF generates a CC-session, performs QoS and billing determination, and returns a credit control answer (CC-Answer) to the PGW.
  • CC-Answer reply timing session information for the session is generated in the PCRF.
  • the PCRF sets the bandwidth to, for example, 2 Mbits / Sec for the PGW related to the session by the 3G terminal, for example, 100 Mbits / Sec for the PGW related to the session by the LTE terminal, as bandwidth control.
  • the PGW that has received CC-Answer from the PCRF returns a session creation response (Create Session Response) to the SGW.
  • the SGW returns a session creation response (Create Session Response) to the MME.
  • the MME that has received the session creation response returns an attach acceptance (Attach Accept) to the UE.
  • a bearer establishment process is performed between the eNB-MME-SGW. As a result, bearer establishment from the UE to the service network is completed.
  • the details of steps 1 to 10 in FIG. 4 are referred to FIG. 5.3.2-1.1-1 of 5.3.2 Attach procedure of Non-Patent Document 3 and the related explanation).
  • the PGW detects the resumption of the PCRF.
  • the PGW activates the bearer release and makes a delete bearer request (Delete Bearer Request) to the SGW in order to match the session state.
  • the SGW that has received the bearer deletion request transmits a bearer deletion request (Delete Bearer Request) to the MME.
  • the MME since the MME becomes the last bearer for the UE, the MME activates the bearer deletion process and transmits a detach request (Detach Request) to the UE.
  • Detach Request a detach request
  • the UE informs the MME of the Detach Accept.
  • the MME that has received the detachment from the UE returns a delete bearer response (Delete Bearer Response) to the SGW.
  • Delete Bearer Response For the detach request from the MME to the UE, refer to FIG. 5.3.8.3-1 of the Mach-Initiated Detach Procedure and its related description in 5.3.8 of Non-Patent Document 3.
  • the SGW that has received this returns a delete bearer response (Delete Bearer Response) to the PGW.
  • the UE releases the bearer and transitions to the detach state once.
  • the UE activates the attach process again (reattach).
  • the bearer is re-established with the session information including the PCRF matching.
  • FIG. 5 is a diagram illustrating an operation sequence according to the first embodiment of this invention.
  • the attach process A from the UE in step 1 is the same as the process A in FIG. 4 (FIG. 5.2.1-1: Attach procedure of Non-Patent Document 3), and thus description thereof is omitted. .
  • the PGW sends a CC-Request (initial) message to the PCRF.
  • the PCRF that has received the CC-Request from the PGW generates a CC (Credit-Control) -session, and performs QoS and Charging determination.
  • the PCRF gives the CC-Answer a PCC session information (including QoS and billing information) container (PCC container).
  • the PCC session information container includes an AVP (Attribute Value Pair: attribute value pair) that stores PCC session information.
  • the PGW that has received the CC-Answer with the PCC container from the PCRF holds the PCC container (session) information (however, the PGW does not interpret the session information of the PCC container).
  • the bearer establishment process (process B) in step 5 of FIG. Step 7 of FIG. 4 (Reply of Create Session Response from PGW to SGW), Step 8 of FIG. 4 (Reply of Create Session Response from SGW to MME), Step 9 in FIG. 4 (reply of Attach Accept from MME to UE), Bearer establishment process (process B) in step 10 of FIG. Consists of.
  • the PGW detects the resumption of the PCRF.
  • the PGW that detected the resumption of the PCRF notifies the PCRC of the PCC session information container stored and held in the PGW, and in order to restore the PCC session information, the CC-Request (including the PCC session information container (PCC container)) update) to the PCRF.
  • Request-Type update of this CC-Request represents an update instruction (update indication) by the PCC container.
  • the PCRF receives a CC-Request (update) from the PGW. Since the PCC session information container is included in the CC-Request (update) from the PGW, the PCRF recognizes that the signal is intended to recover the PCC session information lost due to the PCRF restart, and the CC-Request and The session information (session data) is recovered from the PCC container (PCC session information).
  • the PCRF restores the PCC session information.
  • the PCRF returns a successful recovery of the PCC session to the PGW using CC-Answer.
  • the bearer is released (step 19 in FIG. 4)
  • the bearer is re-established by reattaching from the UE.
  • the PGW- It is possible to recover between PCRFs.
  • GTPv2 GTP Version 2 (GPRS (General Packet Radio Service) Tunneling Protocol)
  • PMIPv6 Proxy Mobile IPv6
  • the message to which the PCC container is added is not limited to the SGW / PGW at the time of Attach and the CC-Answer at the time of establishing the CC-session between the PCRFs.
  • PDNs Multiple PDNs
  • TA Track Area
  • CC-sessions established during handover are also detected by restarting the PCRF by adding a PCC container. Recovery of a later PCC session can be realized.
  • FIG. 6 is a diagram illustrating an example of information included in the PCC container in the present embodiment.
  • Information set in CC-Request transmitted from PGW / SGW to PCRF can be used as Diameter session ID and subscription ID (Subscription-Id). Missing information, -Mobile device IPv4 address / IPv6 prefix, APN (Access Point Name) name, ⁇ QoS rules, -Charging rules and -The PCRF sets related information in the PCC container.
  • APN Access Point Name
  • FIG. 7 is a diagram illustrating an example of PCRF restart detection in the present embodiment.
  • the PCRF can be restarted by using Origin-State-Id defined in IETF RFC 3588.
  • Origin-State-Id is counted up when session information is lost due to, for example, PCRF restart.
  • CER Capability Exchange Request
  • CEA Capability Exchange Answer
  • the peer device is re-established each time the Diameter connection is established (SCTP established). Can be recognized.
  • Diameter capability negotiation (CER / CEA) is performed to determine what applications are supported at each peer.
  • the PGW establishes a connection using PCRF and SCTP (Stream Control Transmission Protocol).
  • SCTP Stream Control Transmission Protocol
  • IET RFC 4960 is referred to.
  • the PGW transmits a CER (Origin-State-Id) message to the PCRF.
  • CER Oil-State-Id
  • the PGW receives a CEA (Origin-State-Id) message from the PCRF.
  • CEA Oil-State-Id
  • the PGW detects “SCTP disconnection” by increasing the value of Origin-State-Id.
  • the PCRF recovers from the failure and restarts (session information is lost in the PCRF).
  • the PGW establishes a connection using PCRF and SCTP (Stream Control Transmission Protocol).
  • the PGW transmits a CER (Origin-State-Id) message to the PCRF.
  • CER Oil-State-Id
  • the PCRF counts up Origin-State-Id.
  • the PGW receives a Diameter CEA (Origin-State-Id) message from the PCRF.
  • Diameter CEA Oil-State-Id
  • the PGW detects PCRF restart.
  • the PGW receives an Origin-State-Id that is larger than the Origin-State-Id of the Diameter CEA message previously received from the same issuer in the Diameter CEA (Origin-State-Id) message received from the PCRF Originally, it is assumed that the state has been lost since the previous message. In this case, in the PGW, it is estimated (detected) that the PCRF is resumed in a state where the PCC session is lost.
  • This embodiment has the following operational effects.
  • the PCC session information can be recovered by transferring the PCC session information from the SGW / PGW to the PCRF when the PCRF is resumed.
  • session information is lost due to a temporary service stop of the PCRF, it can be recovered between the SGW / PGW-PCRF, and the communication can be performed without affecting the bearer with which the UE is communicating. The impact on quality can be avoided.
  • FIG. 8 is a diagram for explaining the operation of the second embodiment of the present invention.
  • the network configuration of this embodiment is the same as FIG.
  • one PCC session is recovered in the PCRF, but in the present embodiment, a plurality of PCC sessions are recovered in the PCRF.
  • Step 1 (Attach process from the UE) is the same as the process A in FIG. Also, 2. CC-Request (initial) transmission from PGW to PCRF, 3. 3. Send CC-Answer (with PCC container) from PCRF to PGW PCC container (session information) retention in PGW, 5.
  • Process B (bearer establishment process) Both are the same as FIG.
  • the PGW detects the PCRF restart (according to the procedure described in FIG. 7).
  • the PGW sends a CC-Request (bulk update) to the PCRF. It is possible to register a plurality of PCC session information containers in this CC-Request (bulk update) message (one message).
  • Request Type bulk update in CC-Request represents an instruction to update a plurality of session information.
  • the PCRF receives the CC-Request from the PGW and restores a plurality of PCC session information.
  • the PCRF returns CC-Answer to the PGW.
  • the PGW is required to transmit a CC-Request (update) to the PCRF for each session, whereas in the present embodiment, the PGW corresponds to a plurality of bearers.
  • CC-Request CC-session message
  • the PGW can notify the PCRF of a plurality of PCC session information with one signal, the PCF session can be restored with the PCRF, compared with the case where CC-Request (update) is transmitted for each session.
  • the necessary amount of signal (the amount of signal transmitted (signaling load)) is reduced, and recovery is possible in a short time.
  • FIG. 9 is a diagram for explaining a third embodiment of the present invention.
  • the PCRF that has received the CC-Request from the PGW transmits a profile acquisition request to the HSS in order to acquire profile information of the corresponding subscriber (user of the UE that transmitted the attach request).
  • the HSS that has received the profile acquisition request from the PCRF returns a profile acquisition response in which the profile information of the subscriber is set to the PCRF.
  • the PCRF that has received the profile acquisition response from the HSS performs subscriber determination from the profile information (determines whether the subscriber is a priority user).
  • a PCC session information container is assigned to CC-Answer from PCRF to PGW.
  • the PGW holds a PCC session information container.
  • the PCRF If the subscriber is not a priority user, the PCRF returns a CC-Answer to which no PCC container is set (not including the PCC container) to the PGW.
  • the PGW does not hold PCC container information (PCC session information).
  • the PGW that has detected the resumption of the PCRF receives the PCC container (PCC session) from the CC-Request in order to restore the session information received by the PCC container to the PCRF when the bearer is established. Information) is set and transmitted to the PCRF.
  • the PCRF that has received the PCC container restores the PCC session of the priority user and returns a CC-Answer to the PGW.
  • the priority user refers to a user who wants to rescue with priority based on contract information or the like.
  • the priority setting may be such that the home subscriber is a priority user and the roaming-in subscriber is a non-priority user.
  • the home subscriber may be classified into a priority user and a non-priority user based on the contract information.
  • the number of PCC containers (information amount) that needs to be held on the PGW side is limited by limiting the sessions to be restored based on the priority (suppressing increase in the information amount) Is possible. For this reason, the influence on PGW can be suppressed.
  • FIG. 10 is a diagram showing a system configuration of the fourth exemplary embodiment of the present invention.
  • an AF (Application Function) 111 is added to the configuration of FIG.
  • AF is a node deployed in P-CSCF (Proxy-Call Session Control Function) in IMS (IP Multimedia System), and plays a role of notifying session information required for IMS to PCRF, and VoIP (Voice) in IMS.
  • P-CSCF Proxy-Call Session Control Function
  • IMS IP Multimedia System
  • VoIP Voice over IP
  • FIG. 11 is a diagram for explaining the operation of the present embodiment.
  • the first process A (Attach process from the UE) is the same as the process A of FIG.
  • a trigger such as VoIP call on the IMS side occurs.
  • the AF sends an AA-Request (Authentication / Authorization Request) to the PCRF.
  • the AA-Request is notified by setting a flag (restoration support) to true to indicate that the AF stores and holds PCC session information and has a PCC session information recovery support function when the PCRF is resumed. .
  • the PCRF that has received the AA-Request generates session information and returns AA-Answer to the AF.
  • the PCRF sets a PCC session information container in AA-Answer as in the first embodiment, and returns it to the AF.
  • the AF that has received the AA-Answer with the PCC container from the PCRF holds the PCC session information container (but the AF does not interpret the PCC session information container).
  • the PGW transmits a CC-Request in which the PCC container is set to the PCRF.
  • the PCRF that has received the CC-Request and AA-Request in which the PCC session information container is set restores the respective session information.
  • the PCRF sends CC-Answer to the PGW.
  • the PCRF sends AA-Answer to the AF.
  • the AF is notified of successful recovery of the PCC session information.
  • the PGW and AF may add a plurality of pieces of PCC session information to the CC-Request and AA-Request, and send “bulk update” in the same manner as in FIG. .
  • the PCRF when the PCRF is resumed, recovery from the AF cannot be expected, but the PCRF can be recovered by notifying the PGW of the session information of the AF session.
  • Step 1 (Attach process from the UE) is the same as the process A in FIG.
  • a trigger (establishment trigger) occurs for the VoIP call or the like on the IMS side.
  • the AF sends an AA-Request (Authentication / Authorization Request) to the PCRF.
  • the AF notifies the PCRF that the AF does not have the PCRF restart recovery function.
  • the PCRF returns AA-Answer without setting the PCC container to the AF.
  • the PCRF sets a PCC container to which session information for AF and PGW is added in order to hold information on the AF session in the PGW.
  • the PGW activates a dedicated bearer establishment process.
  • This dedicated bearer process is a bearer management function of the MME, and will not be described because it is a standard operation (see Non-Patent Document 3, TS23.401, 5.3.2, etc.).
  • the PGW returns RA (Re-Authentication) -Answer to the PCRF.
  • the PGW transmits a CC-Request with a PCC container to the PCRF.
  • the PCRF restores the PCC session and restores the session information between the PGW-PCRF and between the AF-PCRF.
  • the PCRF session can be restored from the AF to the PCRF when the PCRF is resumed.
  • a PCRF session that includes session information between AFs can be supported only by the PGW. It can be recovered.
  • a default bearer (default bearer) and a specific dedicated bearer (dedicated bearer) are relieved among a default bearer (default bearer) and a dedicated bearer managed by the same CC-session. (Restore session).
  • a new bearer (default bearer) is created.
  • a UE may have one (default bearer) or more bearers. Bearers other than the default bearer are called dedicated bearers.
  • FIG. 13 is a diagram for explaining the sequence operation in the present embodiment.
  • process A in Step 1 (Attach process from the UE) is the same as process A in FIG.
  • CC-Request (initial) is transmitted from the PGW to the PCRF.
  • the PCRF that received the CC-Request from the PGW sets the rescue flag (true) to the default bearer (default bearer) and the dedicated bearer to be rescued (dedicated bearer), and adds a PCC container. Returns the CC-Answer to the PGW.
  • Process B bearer establishment process It is the same as FIG. In the process B of step 5, for example, a default bearer is established by an initial attach request of the UE.
  • a trigger (establishment trigger) occurs for the VoIP call or the like on the IMS side.
  • the AF sends an AA-Request (Authentication / Authorization Request) to the PCRF.
  • AA-Request Authentication / Authorization Request
  • the PCRF that has received the AA-Request from the AF returns an AA-Answer to the AF.
  • PCC session information is set in the PCC container and returned to the AF.
  • the AF that has received the AA-Answer with the PCC container holds the PCC session information.
  • the PCRF sends an RA-Request with a rescue flag (false) set to false to the PGW.
  • the PGW that has received the RA-Request with a rescue flag (false flag) false recognizes that the corresponding dedicated bearer (dedicated bearer) of the same CC-session is a non-relief target.
  • the PGW In response to the restart of the PCRF, the PGW transmits a CC-Request in which the PCC container is set to the PCRF in order to recover the PCC session information.
  • the AF transmits an AA-Request in which the PCC container is set to the PCRF.
  • the PCRF that receives the CC-Request and AA-Request in which the PCC container is set restores the PCC session information.
  • the PCRF sends CC-Answer to the PGW.
  • the PCRF sends AA-Answer to the AF.
  • a bearer deletion request (Delete Bearer Request) is transmitted to the SGW.
  • the SGW sends a delete bearer request (Delete Bearer Request) to the MME.
  • the MME transmits a bearer deactivation request (Deactivate Bearer Request) to the eNB.
  • the eNB transmits an RRC (Radio Resource Connection) Connection Reconfiguration message to the UE.
  • RRC Radio Resource Connection
  • the UE returns an RRC Connection Reconfiguration Complete message to the eNB.
  • the eNB returns a bearer deactivation response (Deactivate Bearer Response) to the MME.
  • the MME sends a delete bearer response (Delete Bearer Response) to the SGW.
  • the SGW sends a delete bearer response (Delete Bearer Response) to the PGW.
  • the notification by the rescue flag of the above operation may be implicitly notified by the PCRF to the CC-Answer to the PGW depending on whether or not the PCC container is set.
  • This embodiment has the following effects in addition to the effects of the first embodiment.
  • FIG. 14 is a diagram showing the configuration of the sixth exemplary embodiment of the present invention.
  • a DRA 121 is added to the configuration of FIG.
  • the DRA 121 is a node having a function of receiving an access from the PCRF client and resolving the transfer destination PCRF, and is located between the PCRF client (SGW, PGW, AF) and the PCRF.
  • Diameter signaling messages pass transparently through the DRA.
  • FIG. 15 is a diagram for explaining the operation of the present embodiment. The operation of this embodiment will be described with reference to FIG.
  • the PGW that has received the event trigger transmits CC (Credit Control) -Request (initial) to the DRA.
  • the DRA that has received the CC-Request from the PGW determines the transfer destination PCRF and transfers the CC-Request (initial).
  • the PCRF that has received the CC-Request (initial) returns a CC-Answer (PCC container) in which the PCC session information container is set to the DRA.
  • PCC container CC-Answer
  • the DRA Upon receiving the CC-Answer (PCC container), the DRA transfers the CC-Answer (PCC container) to the PGW.
  • PCC container A PGW that has received CC-Answer (PCC container) holds a PCC session information container.
  • the DRA that has detected the restart of the PCRF transmits a PCRF restart notification to the PGW.
  • the PGW Upon receiving the PCRF restart notification, the PGW transmits CC-Request (PCC container) in which the PCC session information container is set to the DRA in order to recover the PCC session information.
  • CC-Request PCC container
  • the DRA that receives the CC-Request (PCC container) in which the PCC session information container is set transfers the CC-Request (PCC container) to the PCRF.
  • the PCRF that has received the CC-Request (PCC container) in which the PCC container is set restores the PCC session information and returns the CC-Answer to the DRA.
  • CC-Answer includes an instruction such as successful PCC session information recovery.
  • the DRA transfers the CC-Answer to the PGW.
  • the sequence in which the DRA transfers the CC-Request in which the PCC container is set to the PCRF in which the restart has occurred is illustrated.
  • a PCRF that includes a plurality of PCRFs and DRA uses a service whose service is not stopped when a single PCRF is restarted
  • the DRA may transfer the data.
  • the PGW that has transmitted the CC-Request PCC container
  • the PGW transmits the PCC session information held in the PGW to the new PCRF, and the session information is restored in the new PCRF.
  • session information can be recovered to a PCRF that is different from the PCRF that has restarted, so there is no need to wait for the recovery of the restarting PCRF, and the service stops Time can be shortened.
  • a part or all of the above-described embodiment can be described as follows, but is not limited thereto.
  • (Appendix 1) A Policy and Charging Rules Function (PCRF) node that manages Quality of Service (QoS) and Charging policies; One or more PCRF client nodes that are clients of the PCRF node; Including The PCRF node sends PCC (Policy and Charging Control) session information to at least one of the PCRF client nodes; The PCRF client node that has received the PCC session information from the PCRF node holds the PCC session information, After the PCRF restarts, the PCC session information is transmitted from the PCRF client node to the PCRF node, The recovery method (apparatus, system), wherein the PCRF node receives the PCC session information from the PCRF client node and recovers the PCC session.
  • PCC Policy and Charging Rules Function
  • the PCRF client node In response to the attach procedure from the terminal, the PCRF client node sets in the request message that the PCRF client node sends to the PCRF node that the PCRF client node has a session information recovery function.
  • the recovery method (apparatus, system) according to supplementary note 1, characterized by:
  • the PCRF node that has received the request message from the PCRF client node sends PCC session information including QoS (Quality Of Service) and charging rules to the PCRF client node in an answer message for the request message.
  • the recovery method (apparatus, system) according to appendix 2, characterized by being added and transmitted.
  • the PCRF node that has received the request message from the PCRF client node Obtain subscriber profile information of the terminal that has made the attach request from a server that manages subscriber information, determine whether the user is a priority user, and if the user is the priority user, The PCC session information is transmitted in addition to an answer message corresponding to the request message, and the PCC session information is not transmitted to the PCRF client node if the PCC session information is not the priority user.
  • Recovery method apparatus, system.
  • the PCRF client node that holds the PCC session information and transmits the PCC session information to the PCRF, A packet data network gateway (PGW), which is a node having PCEF (Policy and Charging Enforcement Function Function), A serving gateway (SGW), which is a node having BBERF (Bearer Binding and Event Reporting Function),
  • PGW packet data network gateway
  • SGW serving gateway
  • BBERF Bit Binding and Event Reporting Function
  • the PCRF client node includes a packet data network gateway (PGW) that is a node having PCEF (Policy and Charging Enforcement Function Function), In response to the attach request from the terminal (UE), the packet data network gateway (PGW) that has received the session creation request message from the mobility management entity (MME) via the serving gateway (SGW), In the credit control request message transmitted to the PCRF node, set that the packet data network gateway (PGW) has a session information recovery function, The PCRF node that has received the credit control request message from the packet data network gateway (PGW) performs QoS (Quality Of Service) and charging to the packet data network gateway (PGW). (6) The recovery method (apparatus, system) according to any one of appendices (1) to (5), wherein PCC session information including a (Charging) rule is added to an answer message for the control request message and transmitted.
  • PCEF Policy and Charging Enforcement Function Function
  • the PCRF client node Including application functions having AF (Application Function), When a predetermined trigger after bearer establishment occurs in the application function node, the application function node sends an authentication / authorization request message that the application function node sends to the PCRF node.
  • the PCRF node that has received the authentication / authorization request message from the application function node sends PCC session information including QoS (Quality Of Service) and Charging rules to the application function node.
  • the recovery method (apparatus, system) according to any one of appendices 1 to 5, wherein the recovery method (apparatus, system) is added to the authentication / authorization answer message for the / authorization request message and transmitted.
  • the application function node If the application function node does not have a session information recovery function, the application function node sends an authentication / authorization request message sent from the application function node to the PCRF node.
  • the PCRF node which has set that it does not have a session information recovery function and has received the authentication / authorization request message from the application function node, sends the session information of the application function to the packet data network After transmitting to the gateway (PGW) and restarting the PCRF, the PCRF node sends the packet data network
  • the session information transmitted from the gateway (PGW) is received to recover the PCC session, the session between the packet data network gateway (PGW) and the PCRF node, and / or the application function node and the
  • the recovery method (apparatus, system) according to appendix 7 or 8, characterized in that a session between PCRF nodes is recovered.
  • the PCRF node sets a repair flag that specifies true / false of the repair of the dedicated bearer in the request message transmitted to the PCRF client node, By resuming the PCRF, The PCRF node receives session information held in the PCRF client node, Among the sessions related to the resumed PCRF, the session information of the default bearer and the dedicated bearer for which the repair flag is set to true is restored, and the dedicated bearer for which the repair flag is set to false is disconnected.
  • the recovery method (apparatus, system) according to any one of appendices 1 to 5, characterized in that
  • the PCRF node sends the PCC session information to the PCRF client node via the routing unit,
  • the routing unit detects resumption of the PCRF node, it notifies the PCRF client node,
  • the PCRF client node transmits a message with the PCC session information added thereto to the PCRF node in which the restart has occurred via the routine unit.
  • a routing unit that performs routing management between the PCRF client node and the PCRF node and at least one other PCRF node;
  • the PCRF node sends the PCC session information to the PCRF client node via the routing unit,
  • the routing unit detects resumption of the PCRF node, it notifies the PCRF client node,
  • the PCRF client node transmits a message with the PCC session information added thereto in response to the notification of the restart of the PCRF node from the routing unit,
  • the routine unit forwards the message added with the PCC session information transmitted from the PCRF client node to the other PCRF node different from the PCRF node in which the restart has occurred, and the other PCRF node
  • the restoration method (apparatus, system) according to any one of appendices 1 to 6, wherein the session is restored.

Landscapes

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

Abstract

Selon la présente invention, quand un service est momentanément interrompu en raison d'une anomalie, il est possible de reprendre une session PCRF sans que cela ait une incidence sur une porteuse. La PCRF transmet des informations relatives à une session PCC à un client PCRF (SGW/PGW) (3), et le client PCRF (SGW/PGW) conserve les informations relatives à la session PCC (4). Lorsque la PCRF redémarre (5), le client PCRF détecte le redémarrage (6) et transmet les informations relatives à la session PCC en envoyant un message de demande de récupération de session à la PCRF (7), et la PCRF récupère les informations relatives à la session PCC (8).
PCT/JP2011/052757 2010-02-10 2011-02-09 Pcrf, procédé de reprise après anomalie, et système WO2011099523A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2010028189 2010-02-10
JP2010-028189 2010-02-10

Publications (1)

Publication Number Publication Date
WO2011099523A1 true WO2011099523A1 (fr) 2011-08-18

Family

ID=44367794

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2011/052757 WO2011099523A1 (fr) 2010-02-10 2011-02-09 Pcrf, procédé de reprise après anomalie, et système

Country Status (1)

Country Link
WO (1) WO2011099523A1 (fr)

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2012120156A (ja) * 2011-10-06 2012-06-21 Ntt Docomo Inc 移動通信方法、ゲートウェイ装置、移動管理ノード及び呼セッション制御サーバ装置
JP2013535856A (ja) * 2010-06-29 2013-09-12 アルカテル−ルーセント Ｄｉａｍｅｔｅｒセッション監査
JP2014518022A (ja) * 2011-02-25 2014-07-24 アルカテル−ルーセント 一時サブスクリプションレコード
JP2014534705A (ja) * 2011-10-18 2014-12-18 アルカテル−ルーセント 訪問先ｐｃｒｆのｓ９セッションｉｄの生成
JP2015041906A (ja) * 2013-08-22 2015-03-02 株式会社日立製作所 ルーティングエージェント装置
KR20150027356A (ko) * 2013-08-30 2015-03-12 에스케이텔레콤 주식회사 데이터 세션 관리 방법 및 장치
JP2015115690A (ja) * 2013-12-10 2015-06-22 株式会社日立製作所 通信システム、輻輳回避方法、ゲートウェイ
WO2015182255A1 (fr) * 2014-05-28 2015-12-03 ソニー株式会社 Appareil et procédé
JP2016154389A (ja) * 2016-05-18 2016-08-25 ノキア ソリューションズ アンド ネットワークス オサケユキチュア 移動パケットコアネットワークにおけるセッション終了
US9830214B1 (en) 2015-04-22 2017-11-28 Sprint Communications Company L.P. Diameter routing agent detection of policy server communication failure
US10382360B2 (en) 2012-01-27 2019-08-13 Nokia Solutions And Networks Oy Session termination in a mobile packet core network
US10448268B1 (en) 2019-01-30 2019-10-15 Cisco Technology, Inc. Preservation of policy and charging for a subscriber following a user-plane element failover
CN113412665A (zh) * 2019-07-12 2021-09-17 Oppo广东移动通信有限公司 一种会话设置方法、网络设备、用户设备
US11483684B1 (en) 2021-05-07 2022-10-25 T-Mobile Usa, Inc. Session recovery from dedicated bearer failure

Non-Patent Citations (1)

* 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", 3GPP TR 29.816, V0.3.0, 3GPP, November 2009 (2009-11-01) *

Cited By (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2013535856A (ja) * 2010-06-29 2013-09-12 アルカテル−ルーセント Ｄｉａｍｅｔｅｒセッション監査
JP2014518022A (ja) * 2011-02-25 2014-07-24 アルカテル−ルーセント 一時サブスクリプションレコード
JP2012120156A (ja) * 2011-10-06 2012-06-21 Ntt Docomo Inc 移動通信方法、ゲートウェイ装置、移動管理ノード及び呼セッション制御サーバ装置
JP2014534705A (ja) * 2011-10-18 2014-12-18 アルカテル−ルーセント 訪問先ｐｃｒｆのｓ９セッションｉｄの生成
US10382360B2 (en) 2012-01-27 2019-08-13 Nokia Solutions And Networks Oy Session termination in a mobile packet core network
JP2015041906A (ja) * 2013-08-22 2015-03-02 株式会社日立製作所 ルーティングエージェント装置
KR20150027356A (ko) * 2013-08-30 2015-03-12 에스케이텔레콤 주식회사 데이터 세션 관리 방법 및 장치
KR102072702B1 (ko) 2013-08-30 2020-03-03 에스케이텔레콤 주식회사 데이터 세션 관리 방법 및 장치
JP2015115690A (ja) * 2013-12-10 2015-06-22 株式会社日立製作所 通信システム、輻輳回避方法、ゲートウェイ
WO2015182255A1 (fr) * 2014-05-28 2015-12-03 ソニー株式会社 Appareil et procédé
US10425932B2 (en) 2014-05-28 2019-09-24 Sony Corporation Apparatus and method
US10813087B2 (en) 2014-05-28 2020-10-20 Sony Corporation Apparatus and method
US9830214B1 (en) 2015-04-22 2017-11-28 Sprint Communications Company L.P. Diameter routing agent detection of policy server communication failure
JP2016154389A (ja) * 2016-05-18 2016-08-25 ノキア ソリューションズ アンド ネットワークス オサケユキチュア 移動パケットコアネットワークにおけるセッション終了
US10448268B1 (en) 2019-01-30 2019-10-15 Cisco Technology, Inc. Preservation of policy and charging for a subscriber following a user-plane element failover
US11356869B2 (en) 2019-01-30 2022-06-07 Cisco Technology, Inc. Preservation of policy and charging for a subscriber following a user-plane element failover
CN113412665A (zh) * 2019-07-12 2021-09-17 Oppo广东移动通信有限公司 一种会话设置方法、网络设备、用户设备
CN113412665B (zh) * 2019-07-12 2023-09-22 Oppo广东移动通信有限公司 一种会话设置方法、网络设备、用户设备
US11483684B1 (en) 2021-05-07 2022-10-25 T-Mobile Usa, Inc. Session recovery from dedicated bearer failure
US11930425B2 (en) 2021-05-07 2024-03-12 T-Mobile Usa, Inc. Session recovery from dedicated bearer failure

Similar Documents

Publication Publication Date Title
WO2011099523A1 (fr) Pcrf, procédé de reprise après anomalie, et système
CN109391979B (zh) P-cscf故障恢复方法、装置及***
CN109905469B (zh) 归属地订户服务器、移动管理实体及其执行的方法、***和用户设备
DK2702793T3 (en) Improvements to completed mobile calls
KR101802005B1 (ko) 장애가 생긴 서빙 게이트웨이를 통한 접속의 재배치 및 복구 및 트래픽 오프로딩을 위한 방법 및 장치
US10567216B2 (en) Fault detection method, gateway, user equipment, and communications system
EP2543159B1 (fr) Contrôle de politique et facturation à haute disponibilité dans des configurations pcrf à redondance geographique
EP3051787B1 (fr) Sous-système multimédia ip, appareil de commande de session mandataire et procédé de commande de communications
US8675567B2 (en) Reactivation of dedicated bearers
US20150138952A1 (en) Communication system and method for path control
US9172776B2 (en) PCC control at PCRF failure
WO2012142884A1 (fr) Procédé et appareil pour le traitement d'informations de charge du réseau, de données de position d'utilisateur et de politique
US20140348071A1 (en) Bearer processing method and mobile management device
US20130142120A1 (en) Mobile communication method and call session control server device
WO2017036227A1 (fr) Procédé et dispositif réalisant une restauration de service appelé par un terminal
WO2010124551A1 (fr) Procédé et système pour préserver un identifiant de passerelle de réseau par paquets dans un scénario d'accès multiples
US8737202B2 (en) Automatic connection recovery
CN107404715B (zh) 位置信息提供方法及装置
US8913505B2 (en) PMIPv6 MAG restoration
WO2012013103A1 (fr) Procédé et système de rapport d'identité de passerelle
WO2013037271A1 (fr) Procédé et système d'accès multiple
JP7510957B2 (ja) 緊急コールのための強化されたシグナリングゲートウェイ（ｓｇｗ）ステータス検出および選択のための方法、システム、およびコンピュータ読取可能媒体
JP6450280B2 (ja) 通信制御装置及び通信システム
WO2011082524A1 (fr) Procédé et système pour la transmission de données de machine à machine, et dispositif formant entité de gestion de la mobilité
JP2015115690A (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: 11742266

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

NENP Non-entry into the national phase

Ref country code: JP

122 Ep: pct application non-entry in european phase

Ref document number: 11742266

Country of ref document: EP

Kind code of ref document: A1