WO2019210502A1 - Procédé et appareil de transmission de données - Google Patents

Procédé et appareil de transmission de données Download PDF

Info

Publication number
WO2019210502A1
WO2019210502A1 PCT/CN2018/085566 CN2018085566W WO2019210502A1 WO 2019210502 A1 WO2019210502 A1 WO 2019210502A1 CN 2018085566 W CN2018085566 W CN 2018085566W WO 2019210502 A1 WO2019210502 A1 WO 2019210502A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
message
failure information
cscf
network
Prior art date
Application number
PCT/CN2018/085566
Other languages
English (en)
Inventor
Jinyin Zhu
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to PCT/CN2018/085566 priority Critical patent/WO2019210502A1/fr
Publication of WO2019210502A1 publication Critical patent/WO2019210502A1/fr

Links

Images

Classifications

    • 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/102—Gateways
    • H04L65/1033—Signalling gateways
    • H04L65/104—Signalling gateways in the network
    • 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/1046—Call controllers; Call servers
    • 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
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition

Definitions

  • Embodiments of the disclosure generally relate to communication, and, more particularly, to methods and apparatus for data transmission.
  • network elements in a network should have a very high availability, some maintenance downtime and occasional failures are unavoidable. Communication links although designed with robust protocols between the network elements are also subject to failures.
  • a Proxy Call Session Control Function may fail and a P-CSCF restoration procedure has been defined in 3GPP TS23.380, which is incorporated herein by reference in its entirety.
  • P-CSCF Proxy Call Session Control Function
  • HSS Home Subscriber Server
  • PCRF Policy and Charging Rules Function
  • S-CSCF serving-CSCF
  • PGW Packet Data Network Gateway detecting P-CSCF failure is defined in 3GPP TS29.061 which is incorporated herein by reference in its entirety, where a keep alive mechanism or other type mechanism may be used and then PGW only sends available P-CSCF addresses to a user equipment (UE) .
  • UE user equipment
  • the keep alive mechanism or other type mechanism requires additional cost, e.g. implementation cost, network resource cost, etc.
  • additional cost e.g. implementation cost, network resource cost, etc.
  • the failed P-CSCF may not respond to it and on the other hand, using a more advanced mechanism, e.g. a SIP based mechanism, will add a complexity in the PGW.
  • a method in a first network element may comprise: receiving a first message for a destination user equipment; determining failure information of a second network element, wherein the second network element is configured to process the first message; and sending a second message including at least the failure information to a third network element, wherein the failure information indicates that the second network element has failed or recovered.
  • the first network element may be a serving call session control function (S-CSCF)
  • the second network element may be a proxy CSCF (P-CSCF)
  • the third network element may be a home subscriber server (HSS) or an alternative P-CSCF.
  • S-CSCF serving call session control function
  • P-CSCF proxy CSCF
  • HSS home subscriber server
  • the third network element may be the HSS and the second message may be a Cx server assignment request (SAR) including the failure information.
  • SAR Cx server assignment request
  • the third network element may be the alternative P-CSCF and the second message may be the first message including the failure information.
  • the first message may be a session initiation protocol message.
  • determining failure information of a second network element comprises forwarding the first message to the second network element; and determining the failure information of a second network element based on a received error code or no response.
  • a method in a third network element may comprise: receiving from a first network element a second message including at least failure information of a second network element, wherein the second network element may be configured to process the first message; and sending a third message including at least the failure information to a fourth network element, wherein the failure information indicates that the second network element has failed or recovered.
  • the first network element may be a serving call session control function (S-CSCF)
  • the second network element may be a proxy CSCF (P-CSCF)
  • the third network element may be a home subscriber server (HSS) or an alternative P-CSCF.
  • S-CSCF serving call session control function
  • P-CSCF proxy CSCF
  • HSS home subscriber server
  • the third network element may be the HSS
  • the second message may be a Cx server assignment request (SAR) including the failure information
  • the fourth network element may be a mobility management entity (MME)
  • the third message may be a S6a Insert Subscriber Data Request (IDR) including at least the failure information.
  • the third network element may be the alternative P-CSCF
  • the second message may be the first message including the failure information
  • the fourth network element may be a policy and charging rules function (PCRF)
  • the third message may be an AA-Request (AAR) including at least the failure information.
  • PCRF policy and charging rules function
  • AAR AA-Request
  • the first message may be a session initiation protocol message.
  • a method in a fourth network element may comprise: receiving from a third network element a third message including at least failure information of a second network element, wherein the second network element may be configured to process the first message; and sending a fourth message including at least the failure information to a fifth network element, wherein the failure information indicates that the second network element has failed or recovered.
  • the second network element may be a proxy CSCF (P-CSCF)
  • the third network element may be a home subscriber server (HSS)
  • the fourth network element may be a mobility management entity (MME)
  • the fifth network element may be a serving gateway and packet data network gateway (SGW/PGW)
  • the third message may be a S6a Insert Subscriber Data Request (IDR) including at least the failure information
  • the fourth message may be a modify bearer request including at least the failure information.
  • the second network element may be a proxy CSCF (P-CSCF)
  • the third network element may be a home subscriber server (HSS)
  • the fourth network element may be a 3rd Generation Partnership Project (3GPP) authentication, authorization, accounting (AAA) server
  • the fifth network element may be a packet data network gateway (PGW)
  • the third message may be a SWx Push Profile Request (PPR) including at least the failure information
  • the fourth message may be a Re-authorization Request (RAR) including at least the failure information.
  • PPR SWx Push Profile Request
  • RAR Re-authorization Request
  • the second network element may be a proxy CSCF (P-CSCF)
  • the third network element may be an alternative P-CSCF
  • the fourth network element may be a policy and charging rules function (PCRF)
  • the fifth network element may be a packet data network gateway (PGW)
  • the third message may be a AA-Request (AAR) including at least the failure information
  • the fourth message may be a Re-authorization Request (RAR) including at least the failure information.
  • the first message may be a session initiation protocol message.
  • a method in a fifth network element may comprise: receiving from a fourth network element a fourth message including at least failure information of a second network element, wherein the second network element may be configured to process the first message; and performing at least one action based on the failure information, wherein the failure information indicates that the second network element has failed or recovered.
  • the second network element may be a proxy CSCF (P-CSCF)
  • the fourth network element may be a mobility management entity (MME)
  • the fifth network element may be a serving gateway and packet data network gateway (SGW/PGW)
  • the fourth message may be a modify bearer request including at least the failure information.
  • the second network element may be a proxy CSCF (P-CSCF)
  • the fourth network element may be a 3rd Generation Partnership Project (3GPP) authentication, authorization, accounting (AAA) server
  • the fifth network element may be a packet data network gateway (PGW)
  • the fourth message may be a Re-authorization Request (RAR) including at least the failure information.
  • P-CSCF proxy CSCF
  • 3GPP 3rd Generation Partnership Project
  • AAA authorization, accounting
  • PGW packet data network gateway
  • RAR Re-authorization Request
  • the second network element may be a proxy CSCF (P-CSCF)
  • the fourth network element may be a policy and charging rules function (PCRF)
  • the fifth network element may be a packet data network gateway (PGW)
  • the fourth message may be a Re-authorization Request (RAR) including at least the failure information.
  • P-CSCF proxy CSCF
  • PCRF policy and charging rules function
  • PGW packet data network gateway
  • RAR Re-authorization Request
  • performing at least one action based on the failure information comprises: when the failure information indicates that the second network element has failed, excluding the second network element from a list of available second network elements; when the failure information indicates that the second network element has recovered and been excluded from the list of available second network elements, putting the recovered second network element back to the list of available second network elements.
  • the first message may be a session initiation protocol message.
  • an apparatus in a first network element may comprise: a processor; and a memory, the memory containing instructions executable by the processor, whereby the apparatus may be operative to: receive a first message for a destination user equipment; determine failure information of a second network element wherein the second network element may be configured to process the first message; and send a second message including at least the failure information to a third network element, wherein the failure information indicates that the second network element has failed or recovered.
  • an apparatus in a third network element may comprise: a processor; and a memory, the memory containing instructions executable by the processor, whereby the apparatus may be operative to: receive from a first network element a second message including at least failure information of a second network element, wherein the second network element may be configured to process the first message; and send a third message including at least the failure information to a fourth network element, wherein the failure information indicates that the second network element has failed or recovered.
  • an apparatus in a fourth network element may comprise: a processor; and a memory, the memory containing instructions executable by the processor, whereby the apparatus may be operative to: receive from a third network element a third message including at least failure information of a second network element, wherein the second network element may be configured to process the first message; and send a fourth message including at least the failure information to a fifth network element, wherein the failure information indicates that the second network element has failed or recovered.
  • an apparatus in a fifth network element may comprise: a processor; and a memory, the memory containing instructions executable by the processor, whereby the apparatus may be operative to: receive from a fourth network element a fourth message including at least failure information of a second network element, wherein the second network element may be configured to process the first message; and perform at least one action based on the failure information, wherein the failure information indicates that the second network element has failed or recovered.
  • the computer program product comprises instructions which when executed by at least one processor, may cause the at least one processor to receive a first message for a destination user equipment; determine failure information of a second network element wherein the second network element may be configured to process the first message; and send a second message including at least the failure information to a third network element, wherein the failure information indicates that the second network element has failed or recovered.
  • the computer program product comprises instructions which when executed by at least one processor, may cause the at least one processor to receive from a first network element a second message including at least failure information of a second network element, wherein the second network element may be configured to process the first message; and send a third message including at least the failure information to a fourth network element, wherein the failure information indicates that the second network element has failed or recovered.
  • the computer program product comprises instructions which when executed by at least one processor, may cause the at least one processor to receive from a third network element a third message including at least failure information of a second network element, wherein the second network element may be configured to process the first message; and send a fourth message including at least the failure information to a fifth network element, wherein the failure information indicates that the second network element has failed or recovered.
  • the computer program product comprises instructions which when executed by at least one processor, may cause the at least one processor to receive from a fourth network element a fourth message including at least failure information of a second network element, wherein the second network element may be configured to process the first message; and perform at least one action based on the failure information, wherein the failure information indicates that the second network element has failed or recovered.
  • Fig. 1 is a flow chart depicting an existing HSS-based P-CSCF restoration procedure of 3GPP;
  • Fig. 2 is a flow chart depicting an existing PCRF-based P-CSCF restoration procedure of 3GPP;
  • Fig. 3 is a flow chart depicting an existing HSS-based P-CSCF restoration procedure for wireless local area network (WLAN) of 3GPP;
  • Fig. 4 is a flow chart depicting a HSS-based P-CSCF restoration procedure according to an embodiment of the present disclosure
  • Fig. 5 is a flow chart depicting a HSS-based P-CSCF restoration procedure for WLAN according to an embodiment of the present disclosure
  • Fig. 6 is a flow chart depicting a PCRF based P-CSCF restoration procedure according to an embodiment of the present disclosure
  • Fig. 7 is a flow chart depicting a method in a first network element according to an embodiment of the present disclosure
  • Fig. 8 is a flow chart depicting a method in a third network element according to an embodiment of the present disclosure.
  • Fig. 9 is a flow chart depicting a method in a fourth network element according to an embodiment of the present disclosure.
  • Fig. 10 is a flow chart depicting a method in a fifth network element according to an embodiment of the present disclosure.
  • Fig. 11 is a block diagram illustrating an apparatus in a first network element according to an embodiment of the present disclosure
  • Fig. 12 is a block diagram illustrating an apparatus in a third network element according to an embodiment of the present disclosure.
  • Fig. 13 is a block diagram illustrating an apparatus in a fourth network element according to an embodiment of the present disclosure.
  • Fig. 14 is a block diagram illustrating an apparatus in a fifth network element according to an embodiment of the present disclosure.
  • wireless network refers to a network following any suitable communication standards, such as LTE-Advanced (LTE-A) , LTE, Wideband Code Division Multiple Access (WCDMA) , High-Speed Packet Access (HSPA) , and so on.
  • LTE-A LTE-Advanced
  • WCDMA Wideband Code Division Multiple Access
  • HSPA High-Speed Packet Access
  • the communications between a terminal device and a network device in the wireless network may be performed according to any suitable generation communication protocols, including, but not limited to, Global System for Mobile Communications (GSM) , Universal Mobile Telecommunications System (UMTS) , Long Term Evolution (LTE) , and/or other suitable, and/or other suitable the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the future fifth generation (5G) communication protocols such as new radio (NR) , WLAN standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax) , Bluetooth, and/or ZigBee standards, and/or any other protocols either currently known or to be developed in the future.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • 5G fifth generation
  • NR new radio
  • WLAN standards such as
  • the term “network device/element” refers to a device/element in a communication network via which a terminal device/UE accesses the network and receives services therefrom.
  • the network device may refer to a base station (BS) , an access point (AP) , radio network controllers (RNCs) or base station controllers (BSCs) , Mobility Management Entity (MME) , SGW, PGW, PCRF, HSS, S-CSCF, P-CSCF, a serving general packet radio service (GPRS) support node (SGSN) , a interrogating CSCF, a 3GPP authentication, authorization, accounting (AAA) server, or any other suitable device in the wireless communication network.
  • BS base station
  • AP access point
  • RNCs radio network controllers
  • BSCs base station controllers
  • MME Mobility Management Entity
  • SGW Serving Packet Control Function
  • PGW Packet Control Function
  • PCRF Serving GPRS
  • HSS high-SS
  • the term “UE” refers to any end device that can access the network and receive services therefrom.
  • the UE refers to a mobile terminal, a terminal device, or other suitable devices.
  • the UE may be, for example, a Subscriber Station (SS) , a Portable Subscriber Station, a Mobile Station (MS) , or an Access Terminal (AT) .
  • SS Subscriber Station
  • MS Mobile Station
  • AT Access Terminal
  • the terminal device may include, but not limited to, portable computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable device, a personal digital assistant (PDA) , portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, wearable terminal devices, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , USB dongles, smart devices, wireless customer-premises equipment (CPE) and the like.
  • portable computers image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable device, a personal digital assistant (PDA) , portable
  • a terminal device may represent a UE configured for communication in accordance with one or more communication standards for example promulgated by 3GPP, such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards.
  • 3GPP 3GPP’s GSM, UMTS, LTE, and/or 5G standards.
  • a “user equipment” or “UE” may not necessarily have a “user” in the sense of a human user who owns and/or operates the relevant device.
  • a terminal device may be configured to transmit and/or receive information without direct human interaction.
  • a terminal device may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but that may not initially be associated with a specific human user.
  • the terminal device may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, and may in this case be referred to as a D2D communication device.
  • D2D device-to-device
  • a terminal device may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another terminal device and/or network equipment.
  • the terminal device may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as a machine-type communication (MTC) device.
  • M2M machine-to-machine
  • MTC machine-type communication
  • the terminal device may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard.
  • NB-IoT narrow band internet of things
  • NB-IoT narrow band internet of things
  • a terminal device may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • a downlink (DL) transmission refers to a transmission from the network device to a terminal device
  • an uplink (UL) transmission refers to a transmission in an opposite direction
  • references in the specification to “one embodiment, ” “an embodiment, ” “an example embodiment, ” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • first and second etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments.
  • the term “and/or” includes any and all combinations of one or more of the associated listed terms.
  • Fig. 1 is a flow chart depicting an existing HSS-based P-CSCF restoration procedure of 3GPP, which is a copy of Figure 5.4.2.1-1 of 3GPP TS23.380. More information about the HSS-based P-CSCF restoration procedure, please see section 5.4 of 3GPP TS23.380.
  • Fig. 2 is a flow chart depicting an existing PCRF-based P-CSCF restoration procedure of 3GPP, which is a copy of Figure 5.5.2-1 of 3GPP TS23.380. More information about the PCRF-based P-CSCF restoration procedure, please see section 5.5 of 3GPP TS23.380.
  • Fig. 3 is a flow chart depicting an existing HSS-based P-CSCF restoration procedure for WLAN of 3GPP, which is a copy of Figure 5.6.2.2-1 of 3GPP TS23.380. More information about the P-CSCF restoration procedure for WLAN, please see section 5.6 of 3GPP TS23.380.
  • PGW/SGW can implicitly know the failure of P-CSCF by the P-CSCF Restoration indication, PGW cannot know the real failure information of the P-CSCF. For example, PGW cannot know whether the P-CSCF is failed or has recovered and cannot process the SIP message (i.e. the UE registration data is not present in the recovered P-CSCF) . If PGW wants to know the real failure information of the P-CSCF, PGW/SGW may detect the P-CSCF failure by using the keep alive mechanism or other type mechanism, which requires additional cost, e.g. implementation cost, network resource cost, etc. Furthermore, if using a simple mechanism, e.g. a Ping message, the failed P-CSCF may not respond to it and on the other hand, using more advanced mechanism, e.g. a SIP based mechanism, will add a complexity in the PGW.
  • a simple mechanism e.g. a Ping message
  • more advanced mechanism e.g. a SIP based mechanism
  • the embodiments of the disclosure propose a solution for passing the failure information of the network element in the network.
  • the failure information of the P-CSCF is carried along with the messages during the HSS-based and PCRF-based P-CSCF restoration procedures, so that PGW can get known the real failure information of the P-CSCF.
  • PGW accordingly performs actions based on the real failure information of the P-CSCF.
  • PGW may exclude the failed P-CSCF from a list of available P-CSCFs and does not send an address of the failed P-CSCF to the UE during a subsequent IMS PDN connection setup procedure.
  • PGW may put the recovered P-CSCF back to the list of available P-CSCFs if the recovered P-CSCF is not included in the list.
  • Fig. 4 is a flow chart depicting a HSS-based P-CSCF restoration procedure according to an embodiment of the present disclosure.
  • S-CSCF receives a SIP message for a destination UE. If the called UE’s terminating P-CSCF is determined to be not reachable by the S-CSCF, S-CSCF may skip below steps 404 and 406. If the P-CSCF is not reachable, the S-CSCF does not receive any response when it sends a request to the non-reachable P-CSCF. In this case, the S-CSCF may consider the P-CSCF to be non-reachable. As long as the S-CSCF considers the P-CSCF to be non-reachable, the S-CSCF may not try to contact again this P-CSCF for subsequent terminating requests.
  • the S-CSCF shall consider the P-CSCF to be reachable as soon as a SIP request, including REGISTER, is received from that P-CSCF.
  • Various mechanisms can be used by the S-CSCF to detect the non-reachable P-CSCF, e.g. keep-alive mechanisms or expiry of timers. If the P-CSCF is reachable, but it is not able to process the request such as the SIP message (i.e. the UE registration data is not present in the recovered P-CSCF) , the P-CSCF may send an error code/indication to the S-CSCF.
  • the S-CSCF forwards the SIP message to this called UE’s terminating P-CSCF.
  • the S-CSCF receives a error code from the called UE’s terminating P-CSCF or does not receive any response.
  • the S-CSCF identifies whether the called UE’s terminating P-CSCF is not able to process this request, for example based on the received error code (i.e. the UE registration data is not present) or no response.
  • the S-CSCF may detect the recovery of P-CSCF. For example, the S-CSCF may receive some SIP signaling from P-CSCF. This can happen when the UE which is already served by this P-CSCF initiates originated service. As another example, the S-CSCF may receive SIP error response message from the P-CSCF. This can happen when there is a terminating service to the UE served by the P-CSCF, even if the recovered P-CSCF lost the UE context, but there will be a response message.
  • the S-CSCF sends a Cx Server Assignment Request (SAR) to the HSS, including a P-CSCF Restoration indication and the P-CSCF Failure information (i.e., failed or recovered) and the HSS answers with a Cx Server Assignment Answer (SAA) .
  • SAR Cx Server Assignment Request
  • the S-CSCF indicates that the P-CSCF has failed in the P-CSCF Failure information
  • the S-CSCF indicates that the P-CSCF has recovered in the P-CSCF Failure information.
  • the HSS sends a S6a Insert Subscriber Data Request (IDR) to MME, including a P-CSCF Restoration indication and the P-CSCF Failure information, and the MME answers with an Insert Subscriber Data Answer (IDA) .
  • IDR Insert Subscriber Data Request
  • IDA Insert Subscriber Data Answer
  • the MME sends a Modify Bearer Request to SGW/PGW, including a P-CSCF Restoration indication and the P-CSCF Failure information, and the PGW/SGW answers with a Modify Bearer Response.
  • PGW excludes it from the list of available P-CSCFs and does not send an address of the failed P-CSCF to UE during a subsequent IMS PDN connection setup procedure. If P-CSCF Failure information indicates that the P-CSCF has recovered, PGW puts the recovered P-CSCF back to the list of available P-CSCFs if the recovered P-CSCF has not been included in the list.
  • Fig. 5 is a flow chart depicting a HSS-based P-CSCF restoration procedure for WLAN according to an embodiment of the present disclosure.
  • the steps 502, 504a, 504b, 506 and 508 are same as the steps 402, 404a, 404b, 406 and 408 of Fig. 4, the description of these steps is omitted here for brevity.
  • the HSS sends a SWx Push Profile Request (PPR) to a 3GPP AAA server, including a P-CSCF Restoration indication and the P-CSCF Failure information, and the AAA answers with a Push Profile Answer (PPA) .
  • PPR SWx Push Profile Request
  • PPA Push Profile Answer
  • the 3GPP AAA server sends a Re-authorization Request (RAR) to PGW, including a P-CSCF Restoration indication and the P-CSCF Failure information, and the PGW answers with a Re-authorization Answer (RAA) .
  • RAR Re-authorization Request
  • RAA Re-authorization Answer
  • PGW excludes it from the list of available P-CSCFs and does not send an address of the failed P-CSCF to UE during a subsequent IMS PDN connection setup procedure. If P-CSCF Failure information indicates that the P-CSCF has recovered, PGW puts the recovered P-CSCF back to the list of available P-CSCFs if the recovered P-CSCF has not been included in the list before.
  • Fig. 6 is a flow chart depicting a PCRF based P-CSCF restoration procedure according to an embodiment of the present disclosure.
  • the steps 602, 604a, 604b and 606 are same as the steps 402, 404a, 404b and 406 of Fig. 4, the description of these steps is omitted here for brevity.
  • the S-CSCF forwards the SIP message to an alternative P-CSCF, including the P-CSCF Failure information.
  • the alternative P-CSCF may be chosen by using a local configuration or any other suitable approaches. If the P-CSCF is determined by S-CSCF to be not reachable, e.g. based on no response from the P-CSCF, S-CSCF indicates that the P-CSCF has failed in the P-CSCF Failure information; if an error code is received from the P-CSCF, S-CSCF indicates that the P-CSCF has recovered in the P-CSCF Failure information.
  • the alternative P-CSCF sends a SIP ERROR message to the S-CSCF.
  • the alternative P-CSCF sends a AA-Request (AAR) to PCRF, including a P-CSCF Restoration indication and the P-CSCF Failure information, and the PCRF answers with AA-Answer (AAA)
  • the PCRF sends a Re-authorization Request (RAR) to PGW, including a P-CSCF Restoration indication and the P-CSCF Failure information, and the PGW answers with a Re-authorization Answer (RAA)
  • RAR Re-authorization Request
  • RAA Re-authorization Answer
  • PGW excludes it from the list of available P-CSCFs and does not send an address of the failed P-CSCF to UE during a subsequent IMS PDN connection setup procedure. If P-CSCF Failure information indicates that the P-CSCF has recovered, PGW puts the recovered P-CSCF back to the list of available P-CSCFs if the recovered P-CSCF has not been included in the list before.
  • the P-CSCF Failure information may include the P-CSCF address, an indication of whether the P-CSCF is failed or recovered and the timestamp of when the P-CSCF is determined to be failed or recovered.
  • the failed P-CSCF is excluded from the list of the available P-CSCFs, there may be various ways to put it back to the list:
  • the network may comprise at least five network elements which may be referred to as a first, second, third, fourth and fifth network elements respectively.
  • the first network element may receive a first message for a destination UE. The first message is expected to be processed by the second network element. If the first network element determines the failure information of a second network element, the first network element may send a second message including at least the failure information to a third network element. The failure information may indicate that the second network element has failed or recovered. Then the third network element may send a third message including at least the failure information to a fourth network element. The fourth network element may send a fourth message including at least the failure information to a fifth network element which may perform at least one action based on the failure information.
  • Fig. 7 is a flow chart depicting a method in a first network element according to an embodiment of the present disclosure.
  • the method 700 may be performed at an apparatus such as the S-CSCF of Figs 1-6 or any other suitable apparatus.
  • the first network element may provide means for accomplishing various parts of the method 700 as well as means for accomplishing other processes in conjunction with other components.
  • the description of these parts is omitted here for brevity.
  • the first network element may receive a first message for a destination UE.
  • the first network element may be any suitable network element for example depending on the type of the network.
  • the first network element may be the S-CSCF.
  • the first message may be any suitable message terminated at the UE for example depending on the type of the network.
  • the first message may be a SIP message.
  • the first network element may determine failure information of a second network element, wherein the second network element is configured to process the first message.
  • the second network element may be any suitable network element for example depending the type of the network. For example, if the network is a 3GPP IMS core network, the second network element may be the P-CSCF.
  • the first network element may determine the failure information of the second network element by using any suitable approaches such as keep-alive mechanisms or expiry of timers. If the second network element such as P-CSCF is reachable, but it is not able to process the first message such as the SIP message (e.g. the UE registration data is not present in the recovered P-CSCF) , the second network element such as P-CSCF may send an error indication to the first network element such as S-CSCF.
  • the first network element may determine failure information of a second network element by forwarding the first message to the second network element and determining the failure information of a second network element based on a received error code or no response. For example, if the second network has recovered and does not have necessary information to process the first message, it will send the error code to indicate that it cannot process the first message and the first network element may determine that the second network has recovered. If the second network has failed due to such as outages, maintenance, communication link failure etc., the first network will not receive any response from the first network and then it may determine that the second network has failed.
  • the first network element may send a second message including at least the failure information to a third network element.
  • the second message may be any suitable message depending on the type of the network.
  • the first network element is the S-CSCF
  • the second network element is the P-CSCF
  • the third network element is the HSS as shown in Figs. 4-5.
  • the second message is a Cx SAR including the failure information.
  • the first network element is the S-CSCF
  • the second network element is the P-CSCF
  • the third network element is the alternative P-CSCF as shown in Fig. 6.
  • the second message is the first message including the failure information, for example, a SIP message including the failure information.
  • Fig. 8 is a flow chart depicting a method in a third network element according to an embodiment of the present disclosure.
  • the method 800 may be performed at an apparatus such as the HSS or alternative P-CSCF of Figs 1-6 or any other suitable apparatus.
  • the third network element may provide means for accomplishing various parts of the method 800 as well as means for accomplishing other processes in conjunction with other components. For some same or similar parts which have been described with respect to Figs. 1-7, the description of these parts is omitted here for brevity.
  • the third network element may receive from a first network element a second message including at least failure information of a second network element, wherein the second network element is configured to process the first message and the failure information indicates that the second network element has failed or recovered.
  • the first network element may send the second message to the third network element as described at block 706 of Fig. 7.
  • the first message is a session initiation protocol message or any other suitable message.
  • the third network element may send a third message including at least the failure information to a fourth network element.
  • the third message may be any suitable message for example depending on the type of the network.
  • the first network element is the S-CSCF
  • the second network element is the P-CSCF
  • the third network element is the HSS or an alternative P-CSCF as shown in Figs. 4-6.
  • the third network element is the HSS
  • the second message is a Cx SAR including the failure information
  • the fourth network element is the MME
  • the third message is a S6a IDR including at least the failure information as shown in Fig. 4.
  • the third network element is the HSS
  • the second message is a Cx SAR including the failure information
  • the fourth network element is the 3GPP AAA server
  • the third message is a SWx PPR including at least the failure information as shown in Fig. 5.
  • the third network element is the alternative P-CSCF
  • the second message is the first message including the failure information
  • the fourth network element is the PCRF
  • the third message is an AA-Request (AAR) including at least the failure information as shown in Fig. 6.
  • Fig. 9 is a flow chart depicting a method in a fourth network element according to an embodiment of the present disclosure.
  • the method 900 may be performed at an apparatus such as the MME, PCRF or 3GPP AAA of Figs 1-6 or any other suitable apparatus.
  • the fourth network element may provide means for accomplishing various parts of the method 900 as well as means for accomplishing other processes in conjunction with other components. For some same or similar parts which have been described with respect to Figs. 1-8, the description of these parts is omitted here for brevity.
  • the fourth network element may receive from a third network element a third message including at least failure information of a second network element, wherein the second network element is configured to process the first message and the failure information indicates that the second network element has failed or recovered.
  • the third network element may send the third message to the fourth network element as described at block 804 of Fig. 8.
  • the first message is a session initiation protocol message or any other suitable message in other embodiments.
  • the fourth network element may send a fourth message including at least the failure information to a fifth network element.
  • the fourth message may be any suitable message for example depending on the type of the network.
  • the second network element is the P-CSCF
  • the third network element is the HSS
  • the fourth network element is the MME
  • the fifth network element is the SGW/PGW
  • the third message is a S6a IDR including at least the failure information
  • the fourth message is a modify bearer request including at least the failure information as shown in Fig. 4.
  • the second network element is the P-CSCF
  • the third network element is the HSS
  • the fourth network element is the 3GPP AAA server
  • the fifth network element is a PGW
  • the third message is a SWx PPR including at least the failure information
  • the fourth message is a Re-authorization Request (RAR) including at least the failure information as shown in Fig. 5.
  • RAR Re-authorization Request
  • the second network element is the P-CSCF
  • the third network element is an alternative P-CSCF
  • the fourth network element is the PCRF
  • the fifth network element is the PGW
  • the third message is a AA-Request (AAR) including at least the failure information
  • the fourth message is a Re-authorization Request (RAR) including at least the failure information as shown in Fig. 6.
  • Fig. 10 is a flow chart depicting a method in a fifth network element according to an embodiment of the present disclosure.
  • the method 1000 may be performed at an apparatus such as the PGW of Figs 1-6 or any other suitable apparatus.
  • the fifth network element may provide means for accomplishing various parts of the method 1000 as well as means for accomplishing other processes in conjunction with other components.
  • the description of these parts is omitted here for brevity.
  • the fifth network element may receive from a fourth network element a fourth message including at least failure information of a second network element, wherein the second network element is configured to process the first message and the failure information indicates that the second network element has failed or recovered.
  • the fourth network element may send the fourth message to the fifth network element as described at block 904 of Fig. 9.
  • the first message is a session initiation protocol message or any other suitable message in other embodiments.
  • the fifth network element may perform at least one action based on the failure information.
  • the fifth network element may exclude the second network element from a list of available second network elements.
  • the fifth network element may put the recovered second network element back to the list of available second network elements.
  • the second, third and fourth may also include any other information such as the second network restoration indication, then the fifth network element may perform actions related to the second network restoration indication.
  • the second network element is the P-CSCF
  • the fourth network element is the MME
  • the fifth network element is the SGW/PGW
  • the fourth message is a modify bearer request including at least the failure information as shown in Fig. 4.
  • the second network element is the P-CSCF
  • the fourth network element is the 3GPP AAA server
  • the fifth network element is the PGW
  • the fourth message is a Re-authorization Request (RAR) including at least the failure information as shown in Fig. 5.
  • RAR Re-authorization Request
  • the second network element is the P-CSCF
  • the fourth network element is the PCRF
  • the fifth network element is the PGW
  • the fourth message is a Re-authorization Request (RAR) including at least the failure information as shown in Fig. 6.
  • Fig. 11 is a block diagram illustrating an apparatus in a first network element capable of implementing the methods as described above.
  • the apparatus 1100 comprises a processor 1104, a memory 1105, and a transceiver 1101 in operative communication with the processor 1104.
  • the transceiver 1101 comprises at least one transmitter 1102 and at least one receiver 1103. While only one processor is illustrated in Fig. 11, the processor 1104 may comprises a plurality of processors or multi-core processor (s) . Additionally, the processor 1104 may also comprise cache to facilitate processing operations.
  • Computer-executable instructions can be loaded in the memory 1105 and, when executed by the processor 1104, cause the apparatus 1100 to implement the above-described methods.
  • the computer-executable instructions can cause the apparatus 1100 to receive a first message for a destination user equipment; determine failure information of a second network element wherein the second network element is configured to process the first message; and send a second message including at least the failure information to a third network element, wherein the failure information indicates that the second network element has failed or recovered.
  • the first network element is a serving call session control function (S-CSCF)
  • the second network element is a proxy CSCF (P-CSCF)
  • the third network element is a home subscriber server (HSS) or an alternative P-CSCF.
  • S-CSCF serving call session control function
  • P-CSCF proxy CSCF
  • HSS home subscriber server
  • the third network element is the HSS and the second message is a Cx server assignment request (SAR) including the failure information.
  • SAR Cx server assignment request
  • the third network element is the alternative P-CSCF and the second message is the first message including the failure information.
  • the first message is a session initiation protocol message.
  • the computer-executable instructions can cause the apparatus 1100 to forward the first message to the second network element; and determine the failure information of a second network element based on a received error code or no response.
  • Fig. 12 is a block diagram illustrating an apparatus in a third network element capable of implementing the methods as described above.
  • the apparatus 1200 comprises a processor 1204, a memory 1205, and a transceiver 1201 in operative communication with the processor 1204.
  • the transceiver 1201 comprises at least one transmitter 1202 and at least one receiver 1203. While only one processor is illustrated in Fig. 12, the processor 1204 may comprises a plurality of processors or multi-core processor (s) . Additionally, the processor 1204 may also comprise cache to facilitate processing operations.
  • Computer-executable instructions can be loaded in the memory 1205 and, when executed by the processor 1204, cause the apparatus 1200 to implement the above-described methods.
  • the computer-executable instructions can cause the apparatus 1200 to receive from a first network element a second message including at least failure information of a second network element, wherein the second network element is configured to process the first message; and send a third message including at least the failure information to a fourth network element, wherein the failure information indicates that the second network element has failed or recovered.
  • the first network element is a serving call session control function (S-CSCF)
  • the second network element is a proxy CSCF (P-CSCF)
  • the third network element is a home subscriber server (HSS) or an alternative P-CSCF.
  • S-CSCF serving call session control function
  • P-CSCF proxy CSCF
  • HSS home subscriber server
  • the third network element is the HSS
  • the second message is a Cx server assignment request (SAR) including the failure information
  • the fourth network element is a mobility management entity (MME)
  • the third message is a S6a Insert Subscriber Data Request (IDR) including at least the failure information.
  • the third network element is the HSS
  • the second message is a Cx server assignment request (SAR) including the failure information
  • the fourth network element is a 3rd Generation Partnership Project (3GPP) authentication, authorization, accounting (AAA) server
  • the third message is a SWx Push Profile Request (PPR) including at least the failure information.
  • the third network element is the alternative P-CSCF
  • the second message is the first message including the failure information
  • the fourth network element is a policy and charging rules function (PCRF)
  • the third message is an AA-Request (AAR) including at least the failure information.
  • PCRF policy and charging rules function
  • AAR AA-Request
  • the first message is a session initiation protocol message.
  • Fig. 13 is a block diagram illustrating an apparatus in a fourth network element capable of implementing the methods as described above.
  • the apparatus 1300 comprises a processor 1304, a memory 1305, and a transceiver 1301 in operative communication with the processor 1304.
  • the transceiver 1301 comprises at least one transmitter 1302 and at least one receiver 1303.
  • the processor 1304 may comprises a plurality of processors or multi-core processor (s) . Additionally, the processor 1304 may also comprise cache to facilitate processing operations.
  • Computer-executable instructions can be loaded in the memory 1305 and, when executed by the processor 1304, cause the apparatus 1300 to implement the above-described methods.
  • the computer-executable instructions can cause the apparatus 1300 to receive from a third network element a third message including at least failure information of a second network element, wherein the second network element is configured to process the first message; and send a fourth message including at least the failure information to a fifth network element, wherein the failure information indicates that the second network element has failed or recovered.
  • the second network element is a proxy CSCF (P-CSCF)
  • the third network element is a home subscriber server (HSS)
  • the fourth network element is a mobility management entity (MME)
  • the fifth network element is a serving gateway and packet data network gateway (SGW/PGW)
  • the third message is a S6a Insert Subscriber Data Request (IDR) including at least the failure information
  • the fourth message is a modify bearer request including at least the failure information.
  • the second network element is a proxy CSCF (P-CSCF)
  • the third network element is a home subscriber server (HSS)
  • the fourth network element is a 3rd Generation Partnership Project (3GPP) authentication, authorization, accounting (AAA) server
  • the fifth network element is a packet data network gateway (PGW)
  • the third message is a SWx Push Profile Request (PPR) including at least the failure information
  • the fourth message is a Re-authorization Request (RAR) including at least the failure information.
  • the second network element is a proxy CSCF (P-CSCF)
  • the third network element is an alternative P-CSCF
  • the fourth network element is a policy and charging rules function (PCRF)
  • the fifth network element is a packet data network gateway (PGW)
  • the third message is a AA-Request (AAR) including at least the failure information
  • the fourth message is a Re-authorization Request (RAR) including at least the failure information.
  • the first message is a session initiation protocol message.
  • Fig. 14 is a block diagram illustrating an apparatus in a fifth network element capable of implementing the methods as described above.
  • the apparatus 1400 comprises a processor 1404, a memory 1405, and a transceiver 1401 in operative communication with the processor 1404.
  • the transceiver 1401 comprises at least one transmitter 1402 and at least one receiver 1403. While only one processor is illustrated in Fig. 14, the processor 1404 may comprises a plurality of processors or multi-core processor (s) . Additionally, the processor 1404 may also comprise cache to facilitate processing operations.
  • Computer-executable instructions can be loaded in the memory 1405 and, when executed by the processor 1404, cause the apparatus 1400 to implement the above-described methods.
  • the computer-executable instructions can cause the apparatus 1400 to receive from a fourth network element a fourth message including at least failure information of a second network element, wherein the second network element is configured to process the first message; and perform at least one action based on the failure information, wherein the failure information indicates that the second network element has failed or recovered.
  • the second network element is a proxy CSCF (P-CSCF)
  • the fourth network element is a mobility management entity (MME)
  • the fifth network element is a serving gateway and packet data network gateway (SGW/PGW)
  • the fourth message is a modify bearer request including at least the failure information.
  • the second network element is a proxy CSCF (P-CSCF)
  • the fourth network element is a 3rd Generation Partnership Project (3GPP) authentication, authorization, accounting (AAA) server
  • the fifth network element is a packet data network gateway (SGW/PGW)
  • the fourth message is a Re-authorization Request (RAR) including at least the failure information.
  • 3GPP 3rd Generation Partnership Project
  • AAA authorization, accounting
  • SGW/PGW packet data network gateway
  • RAR Re-authorization Request
  • the second network element is a proxy CSCF (P-CSCF)
  • the fourth network element is a policy and charging rules function (PCRF)
  • the fifth network element is a packet data network gateway (PGW)
  • the fourth message is a Re-authorization Request (RAR) including at least the failure information.
  • the computer-executable instructions can cause the apparatus 1400 to exclude the second network element from a list of available second network elements when the failure information indicates that the second network element has failed; and put the recovered second network element back to the list of available second network elements when the failure information indicates that the second network element has recovered and been excluded from the list of available second network elements.
  • the first message is a session initiation protocol message.
  • the embodiments of the disclosure may provide an efficient and timely way to pass the failure information of the second network element such as P-CSCF to the fifth network element such as PGW.
  • the cost of keep alive mechanism or other type mechanism to detect the failure information of the second network element will be saved.
  • a computer program product comprising at least one non-transitory computer-readable storage medium having computer-executable program instructions stored therein, the computer- executable instructions being configured to, when being executed, cause an apparatus in a first network element to operate as described above.
  • a computer program product comprising at least one non-transitory computer-readable storage medium having computer-executable program instructions stored therein, the computer-executable instructions being configured to, when being executed, cause an apparatus in a third network element to operate as described above.
  • a computer program product comprising at least one non-transitory computer-readable storage medium having computer-executable program instructions stored therein, the computer-executable instructions being configured to, when being executed, cause an apparatus a fourth network element to operate as described above.
  • a computer program product comprising at least one non-transitory computer-readable storage medium having computer-executable program instructions stored therein, the computer-executable instructions being configured to, when being executed, cause an apparatus a fifth network element to operate as described above.
  • any of the components of the apparatus in the first, third, fourth and fifth network element can be implemented as hardware or software modules.
  • software modules they can be embodied on a tangible computer-readable recordable storage medium. All of the software modules (or any subset thereof) can be on the same medium, or each can be on a different medium, for example.
  • the software modules can run, for example, on a hardware processor. The method steps can then be carried out using the distinct software modules, as described above, executing on a hardware processor.
  • program software
  • computer program code are meant to include any sequences or human or machine cognizable steps which perform a function.
  • Such program may be rendered in virtually any programming language or environment including, for example, C/C++, Fortran, COBOL, PASCAL, assembly language, markup languages (e.g., HTML, SGML, XML) , and the like, as well as object-oriented environments such as the Common Object Request Broker Architecture (CORBA) , JavaTM (including J2ME, Java Beans, etc. ) , Binary Runtime Environment (BREW) , and the like.
  • CORBA Common Object Request Broker Architecture
  • JavaTM including J2ME, Java Beans, etc.
  • BREW Binary Runtime Environment
  • memory and “storage device” are meant to include, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the memory or storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
  • RAM random access memory
  • ROM read-only memory
  • EPROM or Flash memory erasable programmable read-only memory
  • CD-ROM compact disc read-only memory
  • magnetic storage device or any suitable combination of the foregoing.

Landscapes

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

Abstract

L'invention concerne un procédé et un appareil de transmission de données. Un procédé peut consister : à recevoir un premier message destiné à un équipement utilisateur de destination ; à déterminer des informations de défaillance d'un deuxième élément de réseau, le deuxième élément de réseau étant conçu pour traiter le premier message ; et à envoyer un deuxième message comprenant au moins les informations de défaillance à un troisième élément de réseau, les informations de défaillance indiquant que le deuxième élément de réseau est défaillant ou a été réparé.
PCT/CN2018/085566 2018-05-04 2018-05-04 Procédé et appareil de transmission de données WO2019210502A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/085566 WO2019210502A1 (fr) 2018-05-04 2018-05-04 Procédé et appareil de transmission de données

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/085566 WO2019210502A1 (fr) 2018-05-04 2018-05-04 Procédé et appareil de transmission de données

Publications (1)

Publication Number Publication Date
WO2019210502A1 true WO2019210502A1 (fr) 2019-11-07

Family

ID=68386278

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/085566 WO2019210502A1 (fr) 2018-05-04 2018-05-04 Procédé et appareil de transmission de données

Country Status (1)

Country Link
WO (1) WO2019210502A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104284360A (zh) * 2014-10-21 2015-01-14 中国联合网络通信集团有限公司 P-cscf故障处理方法和系统
CN105764082A (zh) * 2014-12-18 2016-07-13 中国移动通信集团公司 网元容灾方法及装置
US20160380802A1 (en) * 2013-09-24 2016-12-29 Nec Corporation Methods and apparatuses for facilitating p-cscf restoration when a p-cscf failure has occurred
CN106470441A (zh) * 2015-08-20 2017-03-01 中国电信股份有限公司 一种容灾恢复方法和系统
CN106604318A (zh) * 2017-02-08 2017-04-26 中国联合网络通信集团有限公司 一种呼叫建立方法及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160380802A1 (en) * 2013-09-24 2016-12-29 Nec Corporation Methods and apparatuses for facilitating p-cscf restoration when a p-cscf failure has occurred
CN104284360A (zh) * 2014-10-21 2015-01-14 中国联合网络通信集团有限公司 P-cscf故障处理方法和系统
CN105764082A (zh) * 2014-12-18 2016-07-13 中国移动通信集团公司 网元容灾方法及装置
CN106470441A (zh) * 2015-08-20 2017-03-01 中国电信股份有限公司 一种容灾恢复方法和系统
CN106604318A (zh) * 2017-02-08 2017-04-26 中国联合网络通信集团有限公司 一种呼叫建立方法及系统

Similar Documents

Publication Publication Date Title
US11102351B2 (en) IMS emergency call routing techniques
US11910287B2 (en) Method and apparatus for event monitoring
US20240121591A1 (en) Methods and apparatuses for event monitoring
US20220232051A1 (en) Method and apparatus for restoration of proxy call session control function
EP4189933B1 (fr) Procédés et appareils de commande de politique
WO2021136651A1 (fr) Procédé et appareil de gestion de disponibilité d'un dispositif terminal
WO2019210502A1 (fr) Procédé et appareil de transmission de données
EP3954100B1 (fr) Procédés et appareils de mise en oeuvre d'appel de mobile entrant
US11522962B2 (en) Methods and apparatuses for IP and non-IP data communication using a unified interface
US20220007278A1 (en) Method and apparatus for notifying application function node about rds configuration of network
WO2020215486A1 (fr) Procédé et appareil pour une session nidd gérée par fonction de réseau
US11647379B2 (en) Methods and apparatuses for exposure of monitoring event
US8983505B1 (en) Providing a message notification in a wireless communication system
WO2023130999A1 (fr) Procédé et appareil de restauration de p-cscf
WO2023131166A1 (fr) Procédé et appareil de restauration de p-cscf et d'enregistrement d'informations de p-cscf
WO2022156676A1 (fr) Procédé et appareil de gestion de services
WO2022042606A1 (fr) Procédé et appareil de gestion de services
CN113796123A (zh) 用于plmn速率控制的方法和装置

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

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

Country of ref document: EP

Kind code of ref document: A1