[go: up one dir, main page]

EP2416597B1 - Procédé de gestion de sessions d'urgence et dispositif de communication associé - Google Patents

Procédé de gestion de sessions d'urgence et dispositif de communication associé Download PDF

Info

Publication number
EP2416597B1
EP2416597B1 EP11006396.3A EP11006396A EP2416597B1 EP 2416597 B1 EP2416597 B1 EP 2416597B1 EP 11006396 A EP11006396 A EP 11006396A EP 2416597 B1 EP2416597 B1 EP 2416597B1
Authority
EP
European Patent Office
Prior art keywords
network
emergency
procedure
detach
context
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP11006396.3A
Other languages
German (de)
English (en)
Other versions
EP2416597A3 (fr
EP2416597A2 (fr
Inventor
Kundan Tiwari
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
HTC Corp
Original Assignee
HTC Corp
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 HTC Corp filed Critical HTC Corp
Priority to EP12007735.9A priority Critical patent/EP2560418B1/fr
Publication of EP2416597A2 publication Critical patent/EP2416597A2/fr
Publication of EP2416597A3 publication Critical patent/EP2416597A3/fr
Application granted granted Critical
Publication of EP2416597B1 publication Critical patent/EP2416597B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/06—De-registration or detaching
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/90—Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signalling for the administration of the divided path, e.g. signalling of configuration information
    • H04L5/0096—Indication of changes in allocation
    • H04L5/0098—Signalling of the activation or deactivation of component carriers, subcarriers or frequency bands
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/50—Connection management for emergency connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/34—Selective release of ongoing connections

Definitions

  • the present invention relates to a method of handling emergency sessions in a wireless communication system and a communication device thereof, and more particularly, to a method of handling emergency sessions in abnormal scenarios and a related communication device.
  • an emergency session is often provided by a network to a mobile device that is in a limited service state.
  • UMTS Universal Mobile Telecommunications System
  • LTE long-term evolution
  • an emergency session is often provided by a network to a mobile device that is in a limited service state.
  • Receiving emergency services in the limited service state does not require a subscription, yet the mobile device must first establish a session with the network to access emergency services provided by the system.
  • UMTS provides both circuit switching (CS) and packet switching (PS) services, while the LTE system has been designed to support only packet switched (PS) services.
  • the network is referred to as a universal terrestrial radio access network (UTRAN), comprising a plurality of base stations (Node-Bs) and Radio Network Controllers (RNCs), whereas the mobile devices are referred to as user equipments (UEs).
  • UTRAN universal terrestrial radio access network
  • RNCs Radio Network Controllers
  • UEs user equipments
  • an evolved universal terrestrial radio access network includes a plurality of evolved Node-Bs (eNodeBs) and communicates with a plurality of mobile stations, also referred to as user equipments (UEs).
  • eNodeBs evolved Node-Bs
  • UEs user equipments
  • the UE before accessing a service in an external network (e.g. the Internet), the UE needs to perform a packet data protocol (PDP) context activation procedure to activate a PDP context (containing routing information for tunneling packets) to a belonging serving general packet radio service (GPRS) support node (SGSN) and a specific gateway GPRS support node (GGSN), which can support the service.
  • PDP packet data protocol
  • GPRS general packet radio service
  • GGSN gateway GPRS support node
  • IP Internet Protocol
  • PDN packet data network
  • EPS evolved packet system
  • the GGSN may be referred to a packet data network gateway (P-GW), the SGSN to a serving gateway (S-GW).
  • P-GW packet data network gateway
  • S-GW serving gateway
  • the 3GPP Technical Specification TS 24.301 Release 9 specifies that a UE and a Mobility Management Entity (MME) in the network would locally deactivate an EPS or PDP context when corresponding user plane radio bearers are not established during a service request procedure.
  • MME Mobility Management Entity
  • the emergency session may also be interrupted by a collision between a service request procedure for the emergency session and a network-initiated detach procedure during abnormal scenarios.
  • the 3GPP Technical Specification TS 24.008 Release 9 specifies that when the UE has initiated the service request procedure for the emergency service session (i.e. in a GMM-SERVICE-REQUEST-INITIATED state, or an EMM-SERVICE-REQUEST-INITIATED state), a UE will abort the service request procedure and proceed with the detach procedure after receiving a detach request message from the network.
  • the UE After receiving a detach request message with a detach type "IMSI detach" to detach the UE from CS services, the UE needs to perform a combined tracking area update procedure to attach for CS services again. This procedure will abort the emergency call activation procedure, hence a user will not be able to initiate another emergency service before the detach procedure and a subsequent attachment procedure finishes.
  • a UE receives a detach request message with a detach type "re-attach not requited" to detach the UE from PS services, then the UE will abort the service request procedure and proceed with the detach procedure.
  • the network will abort the service request procedure and proceed with the detach procedure.
  • the emergency session can only be established after the detach procedure and a subsequent emergency attach procedure is finished. Thus, the emergency call will be delayed. In some time-critical cases this delay will be significant.
  • the network can send a detach request message with a detach type "Re-attach not required” and a GPRS mobility management (GMM) cause "IMSI unknown in HLR" to detach the UE from CS services.
  • a detach request message with a detach type "Re-attach not required” and a GPRS mobility management (GMM) cause "IMSI unknown in HLR" to detach the UE from CS services.
  • RAU Routing Area Update
  • the UE and the network will abort the RAU procedure and the network initiated detach procedure will proceed.
  • the next RAU procedure will be started when a periodic RAU timer expires or the UE changes a Routing Area. During this period the UE will miss paging from the network and hence an emergency call-back will fail.
  • a method of handling emergency sessions for a wireless communication system and related communication device are provided.
  • a method of handling an emergency session for a network in a wireless communication system comprises having an emergency context for a mobile device corresponding to the emergency session; not deactivating the emergency context for the mobile device when the network does not allocate radio resources to the emergency context; and preserving the emergency context.
  • a method of handling an emergency session for a mobile device in a wireless communication system comprises having an emergency context from a network corresponding to the emergency session; and not deactivating the emergency context when the network does not allocate radio resources to the emergency context.
  • a method of handling an emergency session for a mobile device in a wireless communication system comprises initiating a service request procedure corresponding to the emergency session in a network; receiving a detach request message from the network when initiating the service request procedure or after having initiated the service request procedure; and continuing the service request procedure when the detach request message is received.
  • a method of handling an emergency session for a network in a wireless communication system comprises receiving a service request message from a mobile device when the network is initiating a detach procedure; and neither aborting nor ignoring the service request message and proceeding with a service request procedure corresponding to the service request message.
  • a method of handling an emergency session for a mobile device in a wireless communication system comprises receiving a detach request message from a network when a Routing Area Update procedure is ongoing; not aborting the RAU procedure when the detach request message is received; and concurrently proceeding with the RAU procedure and a detach procedure corresponding to the detach request message.
  • a method of handling an emergency session for a network in a wireless communication system comprises receiving a Routing Area Update request message corresponding to an RAU procedure from a mobile device when the network is sending a detach request message to the mobile device; and processing the RAU request message and responding the mobile device with an RAU accept message or an RAU reject message when the RAU request message is received.
  • a method of handling an emergency session for a mobile device in a wireless communication system comprises receiving a detach request message from a network when a Routing Area Update procedure is ongoing; aborting the RAU procedure and proceeding with a detach procedure corresponding to the detach request message when the detach request message is received; and restarting the RAU procedure immediately upon completion of the detach procedure.
  • a communication device for handling an emergency session in a wireless communication system comprises means for providing an emergency context for a mobile device corresponding to the emergency session; means for not deactivating the emergency context for the mobile device when the communication device does not allocate radio resources to the emergency context; and means for preserving the emergency context.
  • a communication device for handling an emergency session in a wireless communication system comprises means for receiving an emergency context from a network corresponding to the emergency session; means for not deactivating the emergency context when the network does not allocate radio resources to the emergency context.
  • a communication device for handling an emergency session in a wireless communication system comprises means for initiating a service request procedure corresponding to the emergency session in a network; means for receiving a detach request message from the network when initiating the service request procedure or after having initiated the service request procedure; and means for not aborting the service request procedure when the detach request message is received.
  • a communication device of handling an emergency session in a wireless communication system comprises means for receiving a service request message from a mobile device when the communication device is initiating a detach procedure; and means for neither aborting nor ignoring the service request message and proceeding with a service request procedure corresponding to the service request message.
  • a communication device of handling an emergency session in a wireless communication system comprises means for receiving a detach request message from a network when a Routing Area Update (RAU) procedure is ongoing; means for not aborting the RAU procedure when the detach request message is received; and means for continuing the RAU procedure.
  • RAU Routing Area Update
  • a communication device of handling an emergency session in a wireless communication system comprises means for receiving a detach request message from a network when a Routing Area Update procedure is ongoing; means for not aborting the RAU procedure when the detach request message is received; and means for concurrently proceeding with the RAU procedure and a detach procedure corresponding to the detach request message.
  • a communication device for handling an emergency session in a wireless communication system comprises means for receiving a Routing Area Update request message corresponding to an RAU procedure from a mobile device when the communication device is sending a detach request message to the mobile device; and means for processing the RAU request message and responding the mobile device with an RAU accept message or an RAU reject message when the RAU request message is received.
  • Fig. 1 illustrates a schematic diagram of a wireless communication system 10.
  • the wireless communication system 10 is composed of a network and a plurality of mobile devices.
  • the network and the mobile devices are simply utilized for illustrating the structure of the wireless communication system 10.
  • the wireless communication system 10 can be a Global System for Mobile communications (GSM), universal mobile telecommunications system (UMTS), long-term evolution (LTE) system or LTE-Advanced system.
  • GSM Global System for Mobile communications
  • UMTS universal mobile telecommunications system
  • LTE long-term evolution
  • LTE-Advanced system LTE-Advanced
  • the network can be referred to as an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) comprising a plurality of base stations (eNodeBs), whereas the mobile devices are referred to as user equipments (UEs).
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • UEs user equipments
  • the UEs can be devices such as mobile phones, computer systems, etc.
  • the network and the UE can be seen as a transmitter or a receiver according to a transmission direction, e.g., for uplink (UL), the UE is the transmitter and the network is the receiver, and for downlink (DL), the network is the transmitter and the UE is the receiver.
  • UL uplink
  • DL downlink
  • Fig. 2 illustrates a schematic diagram of an exemplary communication device 20.
  • the communication device 20 may be the mobile device shown in Fig. 1 , but is not limited herein.
  • the communication device 20 may include a processing means 200 such as a microprocessor or Application Specific Integrated Circuit (ASIC), a storage unit 210 and a communication interfacing unit 220.
  • the storage unit 210 may be any data storage device that can store program code 214, for access by the processing means 200. Examples of the storage unit 210 include but are not limited to a subscriber identity module (SIM), read-only memory (ROM), flash memory, random-access memory (RAM), CD-ROMs, magnetic tape, hard disk, and optical data storage device.
  • SIM subscriber identity module
  • ROM read-only memory
  • flash memory random-access memory
  • CD-ROMs magnetic tape
  • hard disk hard disk
  • optical data storage device optical data storage device.
  • the communication interfacing unit 220 is preferably a radio transceiver and can exchange wireless signals with the network according to processing
  • Fig. 3 is a flowchart of an exemplary process 30.
  • the process 30 is utilized for a network NT1 (such as the network of Fig. 1 ) for handling an emergency session in the wireless communication system 10, including the network NT1 and a UE UE1.
  • the process 30 can be compiled into the program code 214 and includes the following steps:
  • the network NT1 has an emergency context EC1 for the UE UE1.
  • the emergency context EC1 may be an emergency EPS bearer context for LTE, or an emergency PDP context for UMTS.
  • the network NT1 may be E-UTRAN for LTE.
  • the emergency context EC1 is an emergency Evolved Packet System (EPS) context.
  • EPS Evolved Packet System
  • Fig. 4 is a flowchart of an exemplary process 40.
  • the process 40 is utilized in the UE UE1 in the wireless communication system 10 for handling the emergency session.
  • the process 40 can be compiled into the program code 214 and includes the following steps:
  • the UE UE1 if the network NT1 has the emergency context EC1 for the UE UE1 but does not assign radio resources to the emergency context EC1, the UE UE1 is forbidden to deactivate the emergency context EC1 locally. Therefore, the UE UE1 does not need to initiate an EPS context procedure again when the UE UE1 makes an emergency call. Therefore, the redundant deactivation and activation steps could be skipped. Further, unnecessary additional signaling and delays in establishment of the emergency session are avoided.
  • the network NT1 and the UE UE1 preserve the emergency context EC1 (e.g. an emergency EPS bearer context) when the network NT1 does not assign user plane radio resources to the UE UE1, such that unnecessary additional signaling and delays in establishment of the emergency session are avoided.
  • the emergency context EC1 e.g. an emergency EPS bearer context
  • Fig. 5 is a flowchart of an exemplary process 50.
  • the process 50 is utilized for a UE UE2 which is attached for both PS and CS services in a network NT2, for handling an emergency session in a wireless communication system including the network NT2 and the UE UE2.
  • the process 50 can be compiled into the program code 214 and includes the following steps:
  • the UE UE2 is attached for both PS and CS services in the network NT2.
  • the network NT2 may be E-UTRAN for LTE or U-TRAN for UMTS.
  • the service request procedure SRQ_p is for PS services in the network NT2 corresponding to the emergency session, e.g. for establishing an emergency EPS context, an emergency PDP context, or user plane radio bearers in the network NT2.
  • the UE UE2 receives the detach request message DRQ_m from the network NT2 when initiating the service request procedure SRQ_p or after having initiated the service request procedure SRQ_p, i.e.
  • the UE UE2 is in a mobility management (MM) state of GMM-SERVICE-REQUEST-INITIATED (for UMTS) or EMM-SERVICE-REQUEST-INITIATED (for LTE).
  • MM mobility management
  • the service e.g. emergency bearer service
  • the service can keep going without being aborted. Redundant delay may be avoided.
  • the detach request message DRQ_m may correspond to a detach procedure DRQ1_p to detach the UE UE2 from CS services in the network NT2.
  • the UE UE2 receives the detach request message DRQ_m from the network NT2 while initiating or having initiated the service request procedure SRQ_p for PS services, the UE UE2 is forbidden to abort the service request procedure SRQ_p for PS domain.
  • the UE UE2 continues with the service request procedure SRQ_p.
  • the UE UE2 may be IMSI attached for both PS and CS services to a network in Network Operation Mode I (NMO I) and receives the detach request message DRQ_m with a detach type "IMSI detach” or with a detach type "Re-attach not required” with a GMM cause "IMSI unknown in HLR" while the UE UE2 is initiating the PS service request procedure SRQ_p to establish the PDP context or establish the user plane bearers, then the UE UE2 does not abort the PS service procedure SRQ_p and proceeds with the PS services request procedure SRQ_p. Therefore, the network NT2 will not ignore the service request for the PS services from the UE UE2, and unnecessary additional signaling and delays in establishment of the emergency session is avoided.
  • NMO I Network Operation Mode I
  • the detach request message DRQ_m may correspond to a detach procedure DRQ2_p to detach the UE UE2 from PS services in the network NT2. If the detach request message DRQ_m received has a detach type "Re-attach not required" to detach the UE UE2 from the PS services while the UE UE2 is initiating the service request procedure SRQ_p or has initiated a service request procedure SRQ_p, the UE UE2 is forbidden to abort the service request procedure SRQ_p and continues the service request procedure SRQ_p.
  • the service request procedure SRQ_p may be for establishing a PDP context for emergency bearer services.
  • the UE UE2 deactivates all non-emergency PDP contexts if any.
  • the UE UE2 sends a detach accept message to the network and considers itself attached for emergency bearer services only.
  • the UE UE2 initiates a PDP or EPS context activation procedure for emergency PDP or EPS context.
  • Fig. 6 is a flowchart of an exemplary process 60.
  • the process 60 is utilized for the network NT2, for handling an emergency session in the wireless communication system including the network NT2 and the UE UE2.
  • the process 60 can be compiled into the program code 214 and includes the following steps:
  • the service request message SRQ_m corresponds to the service request procedure SRQ_p, for PS services in the network NT2 corresponding to the emergency session, e.g. for establishing an emergency EPS/PDP context, or user plane radio bearers.
  • the detach procedure DRQ_p may be the detach procedure DRQ1_p or the detach procedure DRQ1_p, to detach the UE UE2 from CS and PS services, respectively.
  • the network NT2 is forbidden to ignore or abort the service request message SRQ_m for PS services and proceeds with the corresponding service request procedure SRQ_p.
  • the network NT2 if the network NT2 is operating in a network mode of operation I(NMO I) and receives PS service request message SRQ_m from the UE UE2 attached for both PS and CS services, while it has sent the detach request message DRQ_m with a detach type "IMSI detach” or "Re-attach not required” with a GMM cause "IMSI unknown in HLR", the network NT2 shall not ignore the PS Service Request message SRQ_m from the UE UE2 and proceeds with the PS Service Request procedure SRQ_p, i.e. the network NT2 may establish the PDP context or assign resources for user plane bearer services. Therefore, delays caused by the detach procedure DRQ_p and subsequent redundant re-attach steps could be skipped, and unnecessary delays in establishment of the emergency session are avoided.
  • the network NT2 does not abort or ignore the service request message SRQ_m from the UE UE2 when initiating the detach procedure DRQ_p, such that establishment of the emergency session is not delayed by the detach procedure DRQ_p.
  • Fig. 7 is a flowchart of an exemplary process 70.
  • the process 70 is utilized for a UE UE3 for handling an emergency session in a wireless communication system including a network NT3 and the UE UE3.
  • the process 70 can be compiled into the program code 214 and includes the following steps:
  • the UE UE3 when the UE UE3 receives a detach request message DRQ'_m corresponding to a detach request procedure DRQ'_p from the network NT3 while the RAU procedure RAU_p is ongoing, the UE UE3 does not abort the RAU procedure RAU_p.
  • the detach request message DRQ'_m may have a detach type "Re-attach not required” and GMM cause "IMSI unknown in HLR" to detach the UE UE3 from CS services in the network NT3.
  • the UE UE3 proceeds with the RAU procedure RAU_p and the detach procedure DRQ'_p to detach from CS services in the network NT3, and then starts the timer T1 and changes to the state S1 indicating the UE UE3 is attempting the RAU procedure RAU_p.
  • the timer T1 may be a timer T3302, and the state S1 may be a GMM-REGISTERED-ATTEMMPING-TO-UPDATE state according to the 3GPP Technical Specification TS 24.008, but not limited thereto. Therefore, the RAU procedure RAU_p is not aborted and will be successful when collided with the detach procedure DRQ'_p. Further, the RAU procedure RAU_p is not delayed until the timer T1 expires or the UE UE3 changes a routing area.
  • Fig. 8 is a flowchart of an exemplary process 80.
  • the process 80 is utilized for the network NT3 for handling the emergency session in the wireless communication system including the network NT3 and the UE UE3.
  • the process 80 can be compiled into the program code 214 and includes the following steps:
  • the network NT3 when the network NT3 receives the RAU request message RAU_m from the UE UE3 while sending the detach request message DRQ'_m to detach the UE UE3 from CS services, the network NT3 proceeds with the RAU procedure RAU_p and the detach procedure DRQ'_p to detach the UE UE3 from CS services concurrently and responds the UE UE3 with the RAU accept message RAU_AC_m or the RAU reject message RAU_RJ_m.
  • Fig. 9 is a flowchart of an exemplary process 90.
  • the process 90 is utilized in the UE UE3.
  • the process 90 can be compiled into the program code 214 and includes the following steps:
  • the RAU procedure and the detach procedure DRQ'_p to detach the UE UE3 from CS services of the network NT3 are not proceeded concurrently. Instead, the RAU procedure will be aborted and restarted after the detach procedure DRQ'_p is finished.
  • the RAU procedure RAU_p is processed concurrently with the detach procedure DRQ'_p, or restarted immediately after the detach procedure DRQ'_p is finished.
  • the RAU procedure RAU_p is not delayed until the time T1 expires or until the UE UE3 changes a routing area, and thus the UE UE3 will not miss paging from the network NT3, and emergency call-back procedures will not fail.
  • the abovementioned steps of the processes 30 to 90 including suggested steps can be realized by means that could be hardware, firmware known as a combination of a hardware device and computer instructions and data that reside as read-only software on the hardware device, or an electronic system.
  • hardware can include analog, digital and mixed circuits known as microcircuit, microchip, or silicon chip.
  • the electronic system can include system on chip (SOC), system in package (SiP), computer on module (COM), and the communication device 20.
  • the exemplary examples and means are provided for handling emergency sessions and keeping the emergency context active during abnormal scenarios, so as to minimize unnecessary additional signaling and delays in the establishment of the emergency sessions.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Business, Economics & Management (AREA)
  • Health & Medical Sciences (AREA)
  • Emergency Management (AREA)
  • Environmental & Geological Engineering (AREA)
  • Public Health (AREA)
  • Mobile Radio Communication Systems (AREA)

Claims (7)

  1. Procédé pour gérer une session d'urgence pour un dispositif mobile (20) dans un système de communication sans fil (10), le procédé comprenant :
    lancer (510) une procédure de demande de service correspondant à la session d'urgence dans un réseau ;
    recevoir (520) un message de demande de détachement provenant du réseau lors du lancement de la procédure de demande de service ou après avoir lancé la procédure de demande de service ; et
    continuer (530) la procédure de demande de service lorsque le message de demande de détachement est reçu ;
    dans lequel le dispositif mobile (20) est attaché à la fois à des services à commutation de paquets, PS, et à commutation de circuits, CS, dans le réseau, le réseau est un Réseau d'Accès Radio Terrestre UMTS Évolué, E-UTRAN, ou un Réseau d'Accès Radio Terrestre UMTS, UTRAN, et la procédure de demande de service concerne des services PS dans le réseau, et le message de demande de détachement correspond à une procédure de détachement pour détacher le dispositif mobile de services CS dans le réseau.
  2. Procédé pour gérer une session d'urgence pour un dispositif mobile (20) dans un système de communication sans fil (10), le procédé comprenant :
    lancer (510) une procédure de demande de service correspondant à une session d'urgence dans un réseau ;
    recevoir (520) un message de demande de détachement provenant du réseau lors du lancement de la procédure de demande de service ou après avoir lancé la procédure de demande de service ; et
    continuer (530) la procédure de demande de service lorsque le message de demande de détachement est reçu ;
    dans lequel le réseau est un Réseau d'Accès Radio Terrestre UMTS Évolué, E-UTRAN, ou un Réseau d'Accès Radio Terrestre UMTS, UTRAN, la procédure de demande de service est utilisée pour établir un contexte de Système de Paquets Évolué, EPS, d'urgence ou un contexte de Protocole de Paquets de Données, PDP, d'urgence dans le réseau, ou pour établir un support radio pour le contexte PDP ou le contexte EPS d'urgence, et le message de demande de détachement correspond à une procédure de détachement pour détacher le dispositif mobile de services à commutation de paquets, PS, dans le réseau.
  3. Procédé selon la revendication 2 comprenant en outre :
    désactiver tout contexte non d'urgence et envoyer un message d'acceptation de détachement au réseau.
  4. Procédé selon la revendication 2, comprenant en outre :
    lancer une procédure d'activation de contexte PDP ou EPS pour le contexte PDP ou EPS d'urgence, ou pour établir un support radio pour le contexte PDP d'urgence ou le contexte EPS d'urgence.
  5. Procédé pour gérer une session d'urgence pour un réseau dans un système de communication sans fil (10), le procédé comprenant :
    recevoir (610) un message de demande de service provenant d'un dispositif mobile (20) lorsque le réseau est en train de lancer une procédure de détachement ; et
    procéder à une procédure de demande de service correspondant au message de demande de service ;
    dans lequel le réseau est un Réseau d'Accès Radio Terrestre UMTS Évolué, E-UTRAN, ou un Réseau d'Accès Radio Terrestre UMTS, UTRAN, et la procédure de demande de service concerne des services à commutation de paquets, PS, dans le réseau, et la procédure de détachement est utilisée pour détacher le dispositif mobile de services à commutation de circuits, CS, dans le réseau.
  6. Procédé pour gérer une session d'urgence pour un réseau dans un système de communication sans fil (10), le procédé comprenant :
    recevoir (610) un message de demande de service provenant d'un dispositif mobile (20) lorsque le réseau est en train de lancer une procédure de détachement ; et
    procéder à une procédure de demande de service correspondant au message de demande de service ;
    dans lequel le réseau est un Réseau d'Accès Radio Terrestre UMTS Évolué, E-UTRAN, ou un Réseau d'Accès Radio Terrestre UMTS, UTRAN, et la procédure de demande de service est destinée à établir un contexte de Système de Paquets Évolué, EPS, d'urgence ou un contexte de Protocole de Paquets de Données, PDP, d'urgence, ou à établir un support radio pour le contexte PDP ou le contexte EPS d'urgence dans le réseau, et la procédure de demande détachement est utilisée pour détacher le dispositif mobile de services à commutation de paquets, PS, dans le réseau.
  7. Procédé selon la revendication 6, comprenant en outre le fait de procéder à la procédure de détachement lorsque le réseau reçoit un message d'acceptation de détachement provenant du dispositif mobile et correspondant à la procédure de détachement ; ou d'activer une procédure d'activation de contexte urgence correspondant au contexte EPS d'urgence ou au contexte PDP d'urgence, ou d'établir un support radio pour le contexte PDP d'urgence ou le contexte EPS d'urgence.
EP11006396.3A 2010-08-05 2011-08-03 Procédé de gestion de sessions d'urgence et dispositif de communication associé Active EP2416597B1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP12007735.9A EP2560418B1 (fr) 2010-08-05 2011-08-03 Procédé de gestion de sessions d'urgence et dispositif de communication associé

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US37081310P 2010-08-05 2010-08-05

Related Child Applications (2)

Application Number Title Priority Date Filing Date
EP12007735.9A Division-Into EP2560418B1 (fr) 2010-08-05 2011-08-03 Procédé de gestion de sessions d'urgence et dispositif de communication associé
EP12007735.9A Division EP2560418B1 (fr) 2010-08-05 2011-08-03 Procédé de gestion de sessions d'urgence et dispositif de communication associé

Publications (3)

Publication Number Publication Date
EP2416597A2 EP2416597A2 (fr) 2012-02-08
EP2416597A3 EP2416597A3 (fr) 2012-04-04
EP2416597B1 true EP2416597B1 (fr) 2016-03-16

Family

ID=44673943

Family Applications (2)

Application Number Title Priority Date Filing Date
EP11006396.3A Active EP2416597B1 (fr) 2010-08-05 2011-08-03 Procédé de gestion de sessions d'urgence et dispositif de communication associé
EP12007735.9A Active EP2560418B1 (fr) 2010-08-05 2011-08-03 Procédé de gestion de sessions d'urgence et dispositif de communication associé

Family Applications After (1)

Application Number Title Priority Date Filing Date
EP12007735.9A Active EP2560418B1 (fr) 2010-08-05 2011-08-03 Procédé de gestion de sessions d'urgence et dispositif de communication associé

Country Status (6)

Country Link
US (2) US20120034898A1 (fr)
EP (2) EP2416597B1 (fr)
JP (3) JP5291769B2 (fr)
KR (1) KR101258192B1 (fr)
CN (1) CN102378142A (fr)
TW (2) TWI481272B (fr)

Families Citing this family (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2416597B1 (fr) * 2010-08-05 2016-03-16 HTC Corporation Procédé de gestion de sessions d'urgence et dispositif de communication associé
US8619654B2 (en) 2010-08-13 2013-12-31 Intel Corporation Base station selection method for heterogeneous overlay networks
US8787337B2 (en) * 2010-08-13 2014-07-22 Intel Corporation Techniques for managing mobility management signaling in a wireless network
ES2918456T3 (es) 2010-08-18 2022-07-15 Blackberry Ltd Métodos para mantener la continuidad de las llamadas
US20130016608A1 (en) * 2011-07-12 2013-01-17 Kundan Tiwari Method of Reducing Signaling in Congested Network and Related Communication Device
CN110062479A (zh) * 2012-03-08 2019-07-26 三星电子株式会社 用于控制无线通信系统中的服务的方法
US9143914B2 (en) 2012-04-27 2015-09-22 Qualcomm Incorporated Emergency call optimization during tracking area update
WO2014113074A1 (fr) 2013-01-17 2014-07-24 Intel IP Corporation Techniques et systèmes de réception discontinue étendue
WO2014143776A2 (fr) 2013-03-15 2014-09-18 Bodhi Technology Ventures Llc Fourniture d'interactions à distance avec un dispositif hôte à l'aide d'un dispositif sans fil
CN104604269B (zh) * 2013-06-19 2019-04-19 华为技术有限公司 一种联合位置更新处理方法、装置和系统
US10270898B2 (en) 2014-05-30 2019-04-23 Apple Inc. Wellness aggregator
US12080421B2 (en) 2013-12-04 2024-09-03 Apple Inc. Wellness aggregator
US20160019360A1 (en) 2013-12-04 2016-01-21 Apple Inc. Wellness aggregator
CN117038008A (zh) 2014-09-02 2023-11-10 苹果公司 身体活动和健身监视器
US10776739B2 (en) 2014-09-30 2020-09-15 Apple Inc. Fitness challenge E-awards
CN107209655B (zh) 2015-02-02 2020-08-11 苹果公司 建立两个设备之间的关系和连接
WO2016144385A1 (fr) 2015-03-08 2016-09-15 Apple Inc. Partage de constructions graphiques configurables par l'utilisateur
US10275116B2 (en) 2015-06-07 2019-04-30 Apple Inc. Browser with docked tabs
WO2017030646A1 (fr) 2015-08-20 2017-02-23 Apple Inc. Cadran de montre d'exercice et applications
US11033708B2 (en) 2016-06-10 2021-06-15 Apple Inc. Breathing sequence user interface
DK201770423A1 (en) 2016-06-11 2018-01-15 Apple Inc Activity and workout updates
US11216119B2 (en) 2016-06-12 2022-01-04 Apple Inc. Displaying a predetermined view of an application
US10873786B2 (en) 2016-06-12 2020-12-22 Apple Inc. Recording and broadcasting application visual output
US11696250B2 (en) * 2016-11-09 2023-07-04 Intel Corporation UE and devices for detach handling
DK180171B1 (en) 2018-05-07 2020-07-14 Apple Inc USER INTERFACES FOR SHARING CONTEXTUALLY RELEVANT MEDIA CONTENT
WO2022245669A1 (fr) 2021-05-15 2022-11-24 Apple Inc. Interfaces utilisateur pour des entraînements de groupe

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FI104679B (fi) * 1997-04-18 2000-04-14 Nokia Networks Oy Menetelmä hätäpuhelun muodostamiseksi langattomassa tilaajaverkossa
JP2000324534A (ja) * 2000-01-01 2000-11-24 Nec Corp 移動体通信システムにおける移動局および位置登録方法
US7787855B2 (en) * 2003-03-31 2010-08-31 Motorola, Inc. Establishing emergency sessions in packet data networks for wireless devices having invalid subscriber identities
US7904094B2 (en) * 2004-10-27 2011-03-08 Motorola Mobility, Inc. Method for reducing wireless communication procedure failure
KR100716890B1 (ko) * 2005-07-05 2007-05-09 주식회사 현대오토넷 다중 서비스 제공 서버 선택 기능을 가지는 텔레매틱스시스템 및 다양한 컨텐츠 서비스 제공 방법
KR101273131B1 (ko) * 2006-03-09 2013-06-13 삼성전자주식회사 이동 단말에서 시스템 선택 방법
GB0608612D0 (en) * 2006-05-02 2006-06-14 Vodafone Plc Telecommunications networks
CN100493039C (zh) * 2006-05-19 2009-05-27 华为技术有限公司 减少分组域业务中断的方法
US8144650B2 (en) * 2006-12-22 2012-03-27 Telefonaktiebolaget L M Ericsson (Publ) Method and arrangement relating to communications network services request activation
CN101335993A (zh) * 2007-06-25 2008-12-31 华为技术有限公司 接入处理方法、装置及用户设备
CN101365230B (zh) * 2007-08-07 2010-08-11 华为技术有限公司 异构网络切换/改变时的用户分离方法、系统及装置
JP5224036B2 (ja) * 2008-02-19 2013-07-03 日本電気株式会社 緊急呼処理装置、方法、プログラム、並びにサーバ装置及びこれを用いた緊急呼処理システム
CN101610576B (zh) * 2008-06-18 2013-01-30 上海华为技术有限公司 限制信令下的信息处理方法及相关设备
US8300772B2 (en) 2008-12-31 2012-10-30 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus for emergency call processing
US20110275342A1 (en) * 2008-12-31 2011-11-10 Peter Ramle Emergency call handling while roaming
US20110310731A1 (en) * 2010-06-18 2011-12-22 Sharp Laboratories Of America, Inc. Controlling network resource usage of machine type communication (mtc) devices
EP2416597B1 (fr) * 2010-08-05 2016-03-16 HTC Corporation Procédé de gestion de sessions d'urgence et dispositif de communication associé

Also Published As

Publication number Publication date
US20140335860A1 (en) 2014-11-13
JP5469757B2 (ja) 2014-04-16
TW201408099A (zh) 2014-02-16
KR20120013911A (ko) 2012-02-15
EP2416597A3 (fr) 2012-04-04
JP2013128317A (ja) 2013-06-27
EP2560418A1 (fr) 2013-02-20
JP5291769B2 (ja) 2013-09-18
TWI481272B (zh) 2015-04-11
TW201210368A (en) 2012-03-01
CN102378142A (zh) 2012-03-14
JP5562457B2 (ja) 2014-07-30
JP2012039617A (ja) 2012-02-23
EP2560418B1 (fr) 2014-10-08
US20120034898A1 (en) 2012-02-09
TWI423701B (zh) 2014-01-11
KR101258192B1 (ko) 2013-04-25
EP2416597A2 (fr) 2012-02-08
JP2013128318A (ja) 2013-06-27

Similar Documents

Publication Publication Date Title
EP2416597B1 (fr) Procédé de gestion de sessions d'urgence et dispositif de communication associé
CN106686565B (zh) 在无线网络中在用户设备处理ims呼叫和csfb呼叫
US8755766B2 (en) Handling reachability of mobile device when serving core network node changes
EP2487954B1 (fr) Procédés et dispositif de traitement des temporisateurs dans un système de communications sans fil
US8331304B2 (en) Mobile communication method, mobile station and mobile switching center
US8977227B2 (en) Method of handling signaling in congested core network
JP5928478B2 (ja) 移動無線通信ネットワークデバイス、移動無線通信デバイス、方法、コンピュータプログラム、コンピュータ可読媒体及び移動通信システム
US9560516B2 (en) Method to use existing NAS signaling connection for pending uplink signaling/data after TAU accept
US9420443B2 (en) Cleanup of LAU-less circuit switched fallback emergency call
EP2437555B1 (fr) Séparation initié de réseau avec reconnexion
EP2587883B1 (fr) Méthode de traitement de rejet de service pour service à circuit communité
US10383169B2 (en) Base station and terminal connection management method of base station
US20250184834A1 (en) Sip timer modification to support ims call fallback

Legal Events

Date Code Title Description
17P Request for examination filed

Effective date: 20110803

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

PUAL Search report despatched

Free format text: ORIGINAL CODE: 0009013

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 4/22 20090101AFI20120131BHEP

AK Designated contracting states

Kind code of ref document: A3

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

17Q First examination report despatched

Effective date: 20120503

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: HTC CORPORATION

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 4/22 20090101AFI20150804BHEP

Ipc: H04W 76/00 20090101ALI20150804BHEP

Ipc: H04W 60/06 20090101ALI20150804BHEP

INTG Intention to grant announced

Effective date: 20150909

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 782104

Country of ref document: AT

Kind code of ref document: T

Effective date: 20160415

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602011023959

Country of ref document: DE

REG Reference to a national code

Ref country code: NL

Ref legal event code: FP

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160616

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160316

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160617

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160316

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 782104

Country of ref document: AT

Kind code of ref document: T

Effective date: 20160316

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 6

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160316

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160316

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160316

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160316

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160316

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160716

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160316

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160316

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160316

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160316

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160316

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160718

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160316

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160316

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602011023959

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160316

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160316

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160316

26N No opposition filed

Effective date: 20161219

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160616

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160316

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20160831

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20160831

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160316

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 7

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20160803

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20160803

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602011023959

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04W0004220000

Ipc: H04W0004900000

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160316

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20110803

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 8

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20160831

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160316

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160316

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160316

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230602

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20250612

Year of fee payment: 15

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: NL

Payment date: 20250613

Year of fee payment: 15

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20250610

Year of fee payment: 15

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20250611

Year of fee payment: 15