Method to detect a user equipment stuck on a dedicated channel
Abstract
While engaged in a dedicated channel, a User Equipment (UE) may get stuck on it. A method and the computer program product detects whether the UE is stuck on the dedicated channel ( 202 ). When it is detected that the UE is stuck, the UE or the corresponding network in which the dedicated channel is located carries out a local release of the UE from the dedicated channel ( 204 ), and the UE is placed in idle mode ( 206 ). Locally releasing the UE from the dedicated channel curtails unnecessary battery consumption in the UE and limits wastage of network resources and bandwidth.

Term
Term ended
Expired 30 May 2026, 0.3 years ago.
- Priority
- Filed
- Granted
- Expired
- Today
16 claims: 1 independent, 15 dependent
- 1A method of resource utilization in a User Equipment, hereafter referred to as UE, engaged in a dedicated channel comprising:determining (202) that the UE is stuck on the dedicated channel by examining whether, for a pre-defined time period, the UE is (a) failing to send and receive higher layer signaling messages;(b) failing to send and receive user data over non-signaling Radio Bearers, hereafter referred to as RBs;(c) failing to send and receive signals over a voice RH;or (d) failing to determine that DCH Loopback Mode is active;performing (204) a local release of radio resources of the dedicated channel;and placing (206) the UE in an idle mode.
41 paragraphs in 4 sections, as filed
FIELD OF THE INVENTION
0001This invention relates in general to communication networks. More specifically, the invention relates to the release of a User Equipment (UE) stuck on a dedicated channel.
BACKGROUND OF THE INVENTION
0002Existing wireless communication systems include a User Equipment (UE), a Radio Access Network (RAN), and a Core Network (CN). The UE may be connected to the CN through a dedicated channel. The dedicated channel may be used for operations including circuit-switched voice transfer, packet-switched voice transfer or data transfer. In the Wideband Code Division Multiple Access (WCDMA) network, CELL-DCH state refers to the state in which the UE is engaged in the dedicated channel. In the Global System for Mobile Communications (GSM) network, the Traffic Channel (TCH) state refers to the state in which the UE is on a dedicated channel. The GSM network uses the TCH channel for the transfer of voice, circuit-switched data and circuit-switched related signaling.
0003While it is engaged in a dedicated channel, however, a UE may get stuck on the dedicated channel. This may happen due to an error or a fault in at least one UE, RAN and CN. When the UE is stuck on the dedicated channel, the UE and the RAN keep performing actions that are necessary to maintain the channel. For the WCDMA Radio Access Technology (RAT), the actions include UEs sending MEASUREMENT REPORT messages and RANs sending MEASUREMENT CONTROL messages and ACTIVE SET UPDATE messages on the relevant Radio Bearers (RBs). In spite of the UE and the RAN performing the necessary actions, no useful data is exchanged between the UE and the CN for a significant period of time. In other words, there is no higher layer signaling and no data transfer over non-signaling RBs carrying user data or voice.
0004When stuck on the dedicated channel, the UE can suffer from several problems. First, battery consumption is high in a UE stuck on the dedicated channel. The dedicated channel is the highest battery consumption mode for the UE. In the dedicated channel, the UE continually monitors the downlink and transmits on the uplink. Second, this situation also results in the wastage of network resources. Maintaining a dedicated channel for the UE requires a significant amount of RAN resources and bandwidth. When the UE is stuck on the dedicated channel, these RAN resources and bandwidth are wasted, without any useful data being exchanged.
0005<patcit id="pcit0001" dnum="US6088343A"><text>US patent no. 6,088,343</text></patcit> describes a GSM transceiver for use in a GSM network comprising a multilayer protocol stack for executing a plurality of asynchronous tasks and a mobility management entity for establishing and authenticating services provided by the GSM network to the transceiver. Only the mobility management entity makes decisions to establish channels between the transceiver and the GSM network. A function of the mobility management entity is to keep track of open connection management layer transactions of the third layer so that it can automatically disconnect the connection once all transactions are completed and also inform interested parties should the connection be interrupted.
0006<patcit id="pcit0002" dnum="US20050054298A"><text>US patent application no. 2005/0054298</text></patcit> describes a UE that can detect a Radio Link Control (RLC) unrecoverable error and a Radio Link (RL) failure, when the UE is in a DCH state. The RL failure leads to releasing the radio bearers and the RLC unrecoverable error is not permitted to release the radio bearers.
Summary of Invention
0007In accordance with the present invention there is provided a method of resource utilization in a UE as recited in the accompanying claims.
BRIEF DESCRIPTION OF THE DRAWINGS
0008The present invention is illustrated by way of example and not limitation in the accompanying figures, in which like references indicate similar elements, and in which:
0009<figref idref="f0001"><b>FIG. 1</b></figref> shows a block diagram illustrating an exemplary wireless communication system, in accordance with an embodiment
0010<figref idref="f0002"><b>FIG. 2</b></figref> shows a flowchart illustrating steps involved in utilizing the resources of a User Equipment (UE) stuck on a dedicated channel, and of the corresponding network, in accordance with an embodiment.
0011<figref idref="f0003"><b>FIG. 3</b></figref> shows a flowchart illustrating steps involved in determining whether the UE is stuck on a dedicated channel, in accordance with an embodiment.
0012Skilled artisans will appreciate that elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. For example, the dimensions of some of the elements in the figures may be exaggerated relative to other elements to help to improve understanding of embodiments of the present invention.
DETAILED DESCRIPTION OF THE EMBODIMENTS
0013Various embodiments of the present invention provide a method and a computer program product for resource utilization in a User Equipment (UE). When engaged in a dedicated channel, the UE may get stuck on it. The method and the computer program product detects whether the UE is stuck on the dedicated channel. When it is detected that the UE is stuck on the channel, either the UE or the corresponding network carries out a release of the UE from the dedicated channel. This is done by performing a local release of the dedicated channel's radio resources alone or through executing a fatal error routine.
0014Before describing in detail the method of detecting and releasing a User Equipment stuck on a dedicated channel, it should be observed that the method can be implemented using software and/or circuitry in combination with conventional UE software and hardware. Accordingly, the method steps have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.
0015<figref idref="f0001"><b>FIG. 1</b></figref> shows a block diagram illustrating an exemplary wireless communication system <b>100,</b> in accordance with an embodiment. The wireless communication system <b>100</b> includes a User Equipment (UE) <b>102,</b> a Radio Access Network (RAN) <b>104,</b> and a Core Network (CN) <b>106.</b> The UE <b>102</b> is sometimes also referred to as a Mobile Station (MS). Examples of the UE <b>102</b> include a cellular phone, a laptop computer, a Personal Digital Assistant (PDA), and so forth. The wireless communication system <b>100</b> may include a plurality of UEs. In this description, the wireless communication system <b>100</b> only shows a single UE <b>102.</b>
0016The UE <b>102</b> manages communications links with the CN <b>106</b> through the RAN <b>104.</b> The RAN <b>104</b> includes base stations <b>108</b> and <b>110.</b> The base stations <b>108</b> and <b>110</b> are wireless transmitting and receiving stations for the wireless communication system <b>100.</b> The CN <b>106</b> further manages communications links between the UE <b>102,</b> and fixed or mobile communication networks. Examples of fixed networks include a public-switched telephone network (PSTN), an Integrated Services Digital Network (ISDN), and the Internet. An example of a mobile network is a Public Land Mobile Network (PLMN).
0017<figref idref="f0002"><b>FIG. 2</b></figref> shows a flowchart <b>200</b> illustrating steps involved in utilizing the resources of a User Equipment (UE) stuck on a dedicated channel, and of the corresponding network, in accordance with an embodiment. Step <b>202</b> determines whether the UE <b>102</b> is stuck on the dedicated channel. In one embodiment, the dedicated channel is accessed in a Wideband Code Division Multiple Access (WCDMA) network while the UE is in a CELL_DCH state. In another embodiment, the UE <b>102</b> is engaged in a dedicated channel while in a Traffic Channel (TCH) state in the GSM network.
0018The UE <b>102</b> may get stuck on the dedicated channel while performing the General Packet Radio Service (GPRS) attach operation on WCDMA network. The UE <b>102</b> may set the 'follow on request flag' in the GPRS Attach message, which it sends to the CN <b>106</b> to indicate that it has additional data to send after the attach operation is complete. The UE <b>102</b> may then fail to send any additional data afterwards. If this occurs, the UE <b>102</b> may get stuck on the dedicated channel.
0019The UE <b>102</b> may also get stuck on the dedicated channel in WCDMA after failing to release a Circuit Switch (CS) signalling connection, once the transactions associated with the CS signalling connection are complete. Similarly in WCDMA, the UE <b>102</b> may get stuck on the dedicated channel after failing to release a Packet Switch (PS) signalling connection once the transactions associated with the PS signalling connection are complete.
0020Finally, the UE <b>102</b> may get stuck on the dedicated channel if the corresponding WCDMA network fails to release a Radio Resource Control (RRC) connection once all signalling connections have been successfully released. Similarly, the UE <b>102</b> may get stuck on the dedicated channel if the corresponding GSM network fails to release a Radio Resource (RR) connection once all signalling connections have been successfully released. In addition to these specific examples, there may be other situations that present a risk of the UE 102 getting stuck on the dedicated channel.
0021In an embodiment, the UE <b>102</b> performs the step <b>202.</b> In another embodiment, the RAN <b>104</b> triggers the UE to perform step <b>202.</b> The RAN <b>104</b> may trigger the UE <b>102</b> to perform step <b>202</b> by broadcasting a message (which indicates that the check described in step <b>202</b> should be performed while the UE <b>102</b> is on the dedicate channel) to all, or a select group of LTEs, in its coverage area. The trigger message may be sent as a system information message or as a device-specific message to individual UEs in its coverage area. In yet another embodiment, the RAN <b>104</b> performs the step <b>202</b> on its own, in which case no trigger needs to be sent to the UE.
0022Step <b>204</b> performs a local release of the radio resources when it is determined that the UE <b>102</b> is stuck on a dedicated channel. In one embodiment, the UE <b>102</b> performs the local release of the RRC connection. In another embodiment, a corresponding RAN <b>104</b> of the UE <b>102</b> performs the local release of the RRC connection. When the UE <b>102</b> performs a local release of the RRC connection, the release may be controlled by a Non Volatile Memory (NVM) field.
0023The NVM is a type of memory that retains its data even when the UE is switched off. Examples of NVM include Read-Only Memory (ROM), Programmable Read-Only Memory (PROM), and Erasable Programmable Read Only Memory (EPROM). The UE <b>102</b> performs the local release of the RRC connection based on a pre-defined value of a field in the NVM. If the field in the NVM contains a pre-defined first value is, for example, a 0 bit, then the local release of the RRC connection will be performed with little notice to the user of the UE. (Note that "first" is used solely to distinguish this value from another value introduced in the next paragraph).
0024If the field in the NVM contains a pre-defined second value, for example, a 1 bit, then the local release of the RRC connection will be performed according to a fatal error routine. A fatal error routine generally saves information regarding a failure of the UE (e.g., that the UE performed a local release due to a determination of being stuck on a dedicated channel, the time and date of the failure, etc.), forwards failure information to a remote server for analysis, and notifies the user of the UE (e.g., a tester) of the failure. The field of the NVM often contains a pre-defined second value when the UE is undergoing field testing, while the field of the NVM would often contain a pre-defined first value when the UE is a released product.
0025At step <b>206,</b> after the RRC is released, the UE <b>102</b> is placed in an idle mode.
0026<figref idref="f0003"><b>FIG. 3</b></figref> shows a flowchart <b>300</b> illustrating steps involved in determining whether the UE <b>102</b> is stuck on a dedicated channel, in accordance with an embodiment. This flowchart <b>300</b> provides details for implementing step <b>202</b> shown in <figref idref="f0002"><b>FIG. 2</b></figref><b>.</b>
0027At step <b>302,</b> a timer is started. Step <b>304,</b> determines whether the UE <b>102</b> is sending or receiving higher layer signaling messages. Examples of higher layer signaling messages for both the WCDMA and GSM networks include signaling performed by the Mobility Management (MM), General Packet Radio Service Mobility Management (GMM), Call Control (CC), Supplementary Services (SS), Short Message Service (SMS), and Session Management (SM) layers.
0028In a WCDMA implementation, WCDMA higher layer signaling messages are sent and received over a Signaling Radio Bearer 3 and a Signaling Radio Bearer 4. If the UE <b>102</b> is sending or receiving at least one of the higher layer signaling messages, then the flow returns to step <b>302.</b> If the UE <b>102</b> is not sending or receiving any higher layer signaling messages, then the flow continues to step <b>306.</b>
0029Step <b>306</b> determines whether the UE <b>102</b> is sending or receiving user data over non-signaling Radio Bearers (RBs). If the UE <b>102</b> is sending or receiving user data over non-signaling RBs, then the flow returns to step <b>302.</b> If the UE <b>102</b> is not sending or receiving user data over non-signaling Radio Bearers (RBs), then the flow continues to step <b>308.</b> Step <b>308</b> determines whether the UE <b>102</b> is sending or receiving signals over a voice RB. If the UE <b>102</b> is sending or receiving signals over a voice RB, then the flow returns to step <b>302.</b> If the UE <b>102</b> is not sending or receiving signals over the voice RB, then the flow continues to step <b>310.</b>
0030Step <b>310</b> determines whether a DCH Loopback Mode is active. The DCH Loopback Mode is a WCDMA test mode in UEs. A similar test mode is available for GSM networks and UEs. UEs with the test mode enabled on their Subscriber Identity Module (SIM) can be commanded to enter the DCH Loopback Mode by the corresponding network. The corresponding network commands the UE <b>102</b> to enter the DCH Loopback Mode through MM messages. The MM messages indicate when a test RB is to be activated, and also when the actual loopback of data sent on the test RB is to be enabled. When the DCH Loopback Mode is active, a downlink DCH data is looped back in the UE <b>102,</b> and the looped back downlink DCH data becomes an uplink DCH data. When the DCH Loopback Mode is active, there is no guarantee about how often the corresponding network will send the useful data in this mode. Therefore, to determine that the UE <b>102</b> is stuck on the dedicated channel, the DCH Loopback Mode should be inactive. If the DCH Loopback Mode is active, then the flow returns to step <b>302.</b> If the DCH Loopback Mode is not active, then the flow continues to step <b>312.</b>
0031At step <b>312,</b> a time period is determined from the timer that was started in step <b>302.</b> At step <b>314,</b> the determined time period is checked against a pre-defined time period. In an embodiment, the corresponding network controls the pre-defined time period by broadcasting information about the pre-defined time period to the UEs in its coverage area. The information about the pre-defined time period can be broadcast in a system information message. In another embodiment, the corresponding network controls the pre-defined time period by sending pre-defined time period information in a device-specific message to one or more UEs in its coverage area. The UE <b>102</b> receives this message if it lies within the coverage area of the RAN 104.
0032If the determined time period is more than the pre-defined time period, then it is ascertained that the UE <b>102</b> is stuck on the dedicated channel. If the determined time period is less than the pre-defined time period, then the flow goes to step <b>316.</b>
0033Step <b>316</b> determines whether the UE <b>102</b> is still engaged in the dedicated channel. If the UE <b>102</b> is still engaged in the dedicated channel, then the flow returns to step <b>304.</b> If the UE <b>102</b> is not engaged in the dedicated channel, it is determined that the UE <b>102</b> is not stuck on the dedicated channel.
0034In an embodiment, the UE <b>102</b> performs steps <b>302</b> through <b>316.</b> In another embodiment, the corresponding RAN 104 performs the steps <b>302</b> through <b>316.</b>
0035The method and computer program product for resource utilization in the UE <b>102</b> is applied in Radio Access Technologies (RATs) such as WCDMA and GSM, in accordance with various embodiments. It should be clear from the preceding disclosure that the method and a computer program product for resource utilization in a UE reduce unnecessary battery consumption in the UE. In addition, the method and computer program product limits wastage of network resources and bandwidth by releasing the UE stuck on the dedicated channel.
0036It will be appreciated the methods described herein may be comprised of one or more conventional processors and unique stored program instructions that control the one or more processors to implement, in conjunction with certain non-processor circuits, some, most, or all of the functions of the methods described herein. The non-processor circuits may include, but are not limited to, a radio receiver, a radio transmitter, signal drivers, clock circuits, power source circuits, and user input devices. As such, these functions may be interpreted as steps of a method to perform detection and release of a UE stuck on a dedicated channel. Alternatively, some or all functions could be implemented by a state machine that has no stored program instructions, or in one or more application specific integrated circuits (ASICs), in which each function or some combinations of certain of the functions are implemented as custom logic. Of course, a combination of the two approaches could be used. Thus, methods and means for these functions have been described herein.
0037It is expected that one of ordinary skill, notwithstanding possibly significant effort and many design choices motivated by, for example, available time, current technology, and economic considerations, when guided by the concepts and principles disclosed herein will be readily capable of generating such software instructions and programs and ICs with minimal experimentation.
0038In this document, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action, without necessarily requiring or implying any actual such relationship or order between such entities or actions. The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element preceded by "comprises ...a" does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that comprises the element.
0039The term "another", as used herein, is defined as at least a second or more. The terms "including" and/or "having", as used herein, are defined as comprising. The term "program", as used herein, is defined as a sequence of instructions designed for execution on a computer system. A "program", or "computer program", may include a subroutine, a function, a procedure, an object method, an object implementation, an executable application, an applet, a servlet, a source code, an object code, a shared library/dynamic load library and/or other sequence of instructions designed for execution on a computer system.
0040In the foregoing specification, the invention and its benefits and advantages have been described with reference to specific embodiments. However, one of ordinary skill in the art appreciates that various modifications and changes can be made without departing from the scope of the present invention as set forth in the claims below. Accordingly, the specification and figures are to be regarded in an illustrative rather than a restrictive sense, and all such modifications are intended to be included within the scope of present invention. The benefits, advantages, solutions to problems, and any element(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential features or elements of any or all the claims. The invention is defined solely by the appended claims including any amendments made during the pendency of this application and all equivalents of those claims as issued.
Contents4
3 sheets
Sheet 1 Sheet 2 Sheet 3
Every citation, both ways
| Document | Relation | Office |
|---|---|---|
| US6088343A | Cites | United States of America |
| US2005054298A1 | Cites | United States of America |
| ERIK DAHLMAN ET AL: "WCDMA-The Radio Interface for Future Mobile Multimedia Communications" IEEE TRANSACTIONS ON VEHICULAR TECHNOLOGY, IEEE SERVICE CENTER, PISCATAWAY, NJ, US, vol. 47, no. 4, November 1998 (1998-11), XP011063756 ISSN: 0018-9545 | Non-patent | – |
17 members in 9 offices
Priority claims3
| Document | Office | Kind | Date |
|---|---|---|---|
| 172313 | United States of America | – | |
| 17231305 | United States of America | A | |
| 2006020805 | United States of America | W |
Members17
| Document | Office | Kind | |
|---|---|---|---|
| US2007004417A1 | United States of America | A1 | |
| AU2006266373A1 | Australia | A1 | |
| WO2007005153A1 | World Intellectual Property Organization (WIPO) | A1 | |
| US7231213B2 | United States of America | B2 | |
| EP1908321A1 | European Patent Office (EPO) | A1 | |
| KR20080043745A | Republic of Korea | A | |
| CN101194530A | China | A | |
| AU2006266373B2 | Australia | B2 | |
| EP1908321B1This record | European Patent Office (EPO) | B1 | |
| AT445990T | Austria | T | |
| ATE445990T1 | Austria | T1 | |
| DE602006009815D1 | Germany | D1 | |
| BRPI0612540A2 | Brazil | A2 | |
| CN101194530B | China | B | |
| KR101236571B1 | Republic of Korea | B1 | |
| BRPI0612540A8 | Brazil | A8 | |
| BRPI0612540B1 | Brazil | B1 |
80 legal events, as 6 offices reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | Office | |
|---|---|---|---|
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Gb: european patent ceased through non-payment of renewal feeCeasedGBPC | GBPC | EP | |
| Application deemed withdrawn, or ip right lapsed, due to non-payment of renewal feeWithdrawnR119 | R119 | DE | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Opt-out of the competence of the unified patent court (upc) registeredP01 | P01 | EP | |
| Fee paymentPLFP | PLFP | FR | |
| Change of applicant/patenteeR081 | R081 | DE | |
| Change of representativeR082 | R082 | DE | |
| Change of name or company nameCD | CD | FR | |
| Transmission of propertyTP | TP | FR | |
| Amendment of ipc main classPREVIOUS MAIN CLASS: H04W0076060000R079 | R079 | DE | |
| Amendments to the register in respect of changes of name or changes affecting rights (sect. 32/1977)REGISTERED BETWEEN 20170831 AND 20170906732E | 732E | GB | |
| Fee paymentPLFP | PLFP | FR | |
| Fee paymentPLFP | PLFP | FR | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Change of applicant/patenteeR081 | R081 | DE | |
| Change of applicant/patenteeR081 | R081 | DE | |
| Change of applicant/patenteeR081 | R081 | DE | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Amendments to the register in respect of changes of name or changes affecting rights (sect. 32/1977)REGISTERED BETWEEN 20110127 AND 20110202732E | 732E | GB | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Patent ceasedCeasedPL | PL | CH | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| No opposition filedOpposition26N | 26N | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| No opposition filed within time limitOppositionORIGINAL CODE: 0009261PLBE | PLBE | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: NO OPPOSITION FILED WITHIN TIME LIMITSTAA | STAA | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Nl: lapsed or annulled due to failure to fulfill the requirements of art. 29p and 29m of the patents actLapsedNLV1 | NLV1 | EP | |
| Lt: invalidation of european patent or patent extensionLTIE | LTIE | EP | |
| Corresponds to:REF | REF | EP | |
| European patents granted designating irelandGrantedFG4D | FG4D | IE | |
| European patent takes effect as a national patent in ch/liEP | EP | CH | |
| Designated contracting statesAK | AK | EP | |
| European patent grantedGrantedFG4D | FG4D | GB | |
| (expected) grantORIGINAL CODE: 0009210GRAA | GRAA | EP | |
| Grant fee paidORIGINAL CODE: EPIDOSNIGR3GRAS | GRAS | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Despatch of communication of intention to grant a patentORIGINAL CODE: EPIDOSNIGR1GRAP | GRAP | EP | |
| Request for extension of the european patent (deleted)DAX | DAX | EP | |
| First examination report despatched17Q | 17Q | EP | |
| Information on inventor provided before grant (corrected)RIN1 | RIN1 | EP | |
| Information on inventor provided before grant (corrected)RIN1 | RIN1 | EP | |
| Information on inventor provided before grant (corrected)RIN1 | RIN1 | EP | |
| Information on inventor provided before grant (corrected)RIN1 | RIN1 | EP | |
| Information on inventor provided before grant (corrected)RIN1 | RIN1 | EP | |
| Information on inventor provided before grant (corrected)RIN1 | RIN1 | EP | |
| Information on inventor provided before grant (corrected)RIN1 | RIN1 | EP | |
| Information on inventor provided before grant (corrected)RIN1 | RIN1 | EP | |
| Information on inventor provided before grant (corrected)RIN1 | RIN1 | EP | |
| Information on inventor provided before grant (corrected)RIN1 | RIN1 | EP | |
| Request for examination filed17P | 17P | EP | |
| Designated contracting statesAK | AK | EP | |
| Public reference made under article 153(3) epc to a published international application that has entered the european phaseORIGINAL CODE: 0009012PUAI | PUAI | EP |
Numbers
- Publication
- 1908321
- Application
- 67715136
Titles3
- German
- VERFAHREN ZUM DETEKTIEREN EINES AUF EINEM FEST ZUGEORDNETEN KANAL FESTHÄNGENDEN BENUTZERGERÄTS
- English
- METHOD TO DETECT A USER EQUIPMENT STUCK ON A DEDICATED CHANNEL
- French
- PROCEDE DE DETECTION DE BLOCAGE D'UN EQUIPEMENT UTILISATEUR SUR UN CANAL RESERVE
Classification
- CPC, 4
- H04W76/38
- H04W52/0229
- Y02D30/70
- H04B7/2631
- IPC, 1
- H04W76 06
Designated states31
- Contracting states, 31
- Austria
- Belgium
- Bulgaria
- Switzerland
- Cyprus
- Czechia
- Germany
- Denmark
- Estonia
- Spain
- Finland
- France
- United Kingdom
- Greece
- Hungary
- Ireland
- Iceland
- Italy
- Liechtenstein
- Lithuania
- Luxembourg
- Latvia
- Monaco
- Netherlands (Kingdom of the)
and 7 moreShow fewer
- Poland
- Portugal
- Romania
- Sweden
- Slovenia
- Slovakia
- Türkiye