Method and apparatus for controlling network access of ue in wireless communication system
13 claims: 4 independent, 9 dependent
- 1A network access method in a wireless communication system including a terminal and a base station, the network access method comprising:transmitting (219), by the terminal to the base station, a radio resource control, RRC, connection request message including a machine type communication, MTC, terminal indicator;receiving (221), by the terminal from the base station, an RRC reject message including a hold time if the MTC terminal indicator is included in the first access request message and an overload start message is transmitted from a mobility management entity, MME to the base station;and transmitting (223), by the terminal to the base station, a second access request message after the hold time included in the RRC reject message elapses.
- 4A wireless communication system including a terminal and a base station, the terminal comprising:a transceiver configured to transmit and receive a signal;and a controller configured to: transmit (219), to the base station, a radio resource control, RRC, connection request message including a machine type communication, MTC, terminal indicator, receive (221), from the base station, an RRC reject message including a hold time if the MTC terminal indicator is included in the first access request message and an overload start message is transmitted from a mobility management entity, MME to the base station, and transmit (223), to the base station, a second access request message after the hold time included in the RRC reject message elapses.
- 7A network access control method executed by a base station in a wireless communication system, the network access control method comprising:receiving (217), by the base station, an overload start message from a mobility management entity, MME;receiving (219), by the base station, a radio resource control, RRC, connection request message including a machine type communication, MTC, terminal indicator from a terminal;transmitting (221), by the base station, if the first access request message includes the MTC terminal indicator, an RRC reject message including a hold time to the terminal;and receiving (223), by the base station from the terminal, a second access request message after the hold time in the RRC reject message elapses.
- 11A base station in a wireless communication system, the base station comprising:a transceiver configured to transmit and receive a signal;and a controller configured to: receive (217) an overload start message from a mobility management entity, MME, receive (219) a radio resource control, RRC, connection request message including a machine type communication, MTC, terminal indicator from a terminal, transmit (221), if the RRC connection request message includes the MTC terminal indicator, an RRC reject message including a hold time to the terminal, and receive (223), from the terminal, a second access request message after the hold time in the RRC reject message elapses.
Independent claims4
67 paragraphs, as filed
[Technical Field]
0001The present invention relates to wireless communications. More particularly, the present invention relates to a method and an apparatus for controlling network access of a User Equipment (UE) based on the network's load and time tolerance (delay tolerance).
[Background Art]
0002When a Machine Type Communication (MTC) or a Machine To Machine (M2M) device, or a User Equipment (UE) and a normal UE attempt to access a network simultaneously, there is a need to restrict the device's access to the network based on the network load in a wireless communication system. That is, if the MTC device has the time tolerant feature, the wireless communication system should restrict the MTC device's access to the network and/or the sending of data towards the MTC device and should limit the amount of data that the MTC device can transfer.
0003When restricting the service to the MTC device, the network load configuration values are used as thresholds to start the service restriction according to the subscriptions of the MTC device. For example, in a case of the MTC device (e.g., metering device) which reports measurement results periodically, the network load configuration value for the service restriction to the subscription having the time tolerance level which requires reporting of the entire utilization of a day, should differ from the network load configuration value for the service restriction to the subscription having the time tolerance level which requires reporting at a time interval set under contract of the dynamic billing policy.
0004In the related art, however, it is impossible to set the network load configuration values for the network use restrictions of the MTC device to different values individually according to the time tolerant levels of the subscriptions. Accordingly, it is difficult to expect good efficiency of the access barring which is performed, in the wireless communication system of the related art, to restrict the network access of the MTC device when the network congestion reaches a predefined level. That is, the network access control method of the related art has a drawback in that it is impossible to set the time tolerant level per MTC device or per subscription of the MTC device.
0005LTE; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification (3GPP TS 36.331 version 9.1.0 Release 9) specifies the Radio Resource Control protocol for the UE-E-UTRAN radio interface relating to eNB.
0006Universal Mobile Telecommunications System (UMTS); Radio Resource Control (RRC); Protocol specification (3GPP TS 25.331 version 9.1.0 Release 9) specifies the Radio Resource Control protocol for the UE-UTRAN radio interface relating to RNC.
0007<nplcit id="ncit0001" npl-type="s"><text>ZTE: "Time Tolerant optimization", 3GPP DRAFT; S2-101044</text></nplcit>, discloses that for MTC devices support Time Tolerant feature, it shall be possible for those MTC devices to get the load information from the network and decides to delay its access to the network or data transfer, according to the statically configured profile.
00083rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Improvements for Machine-Type Communications; (Release 10), 3GPP TR 23.888, discloses architectural aspects of the System Improvements for Machine Type Communications requirements specified in TS22.368.
0009<patcit id="pcit0001" dnum="EP0994604A2"><text>EP 0 994 604 A2</text></patcit> discloses methods and apparatus for providing access priority in a MAC protocol of a communications system such as, for example, with respect to UMTS RACH.
0010<patcit id="pcit0002" dnum="WO2009096833A1"><text>WO 2009/096833 A1</text></patcit> discloses that each of the RAN nodes receives the overload message and determines whether an access class restriction should be implemented to reduce the number of mobile radio terminals permitted to access the cellular radio communications network. If so, the RAN node determines one or more access classes of mobile radio terminals to be restricted based on the information in the overload message. Information relating to the one or more restricted access classes is transmitted in an area associated with the RAN node so that the mobile terminals of a restricted access class are prohibited from accessing the cellular radio communications network.
0011<patcit id="pcit0003" dnum="US2007248060A1"><text>US 2007/248060 A1</text></patcit> discloses methods involving at least one access terminal and at least one access network. The methods may include providing or receiving information indicative of future accessibility of at least one access network.
0012<nplcit id="ncit0002" npl-type="s"><text>CATT: "Access control of MTC devices", 3GPP DRAFT; R2-100182</text></nplcit>, discloses the access control of MTC devices with some alternatives, where access control only takes account of the access of UE from idle state to connection state.
0013<patcit id="pcit0004" dnum="CN101610494A"><text>CN 101 610 494 A</text></patcit> discloses a method, a device, a system and user equipment for realizing overload control or differentiated services.
[Disclosure of Invention]
[Technical Problem]
0014Therefore, a need exists for a method and an apparatus for controlling network access of MTC devices with time tolerant feature in a wireless communication system that is capable of restricting the MTC devices' network access, for sending of data towards MTC devices, and for limiting the amount data that the MTC device can transfer.
[Solution to Problem]
0015The solution to the problem is according to the independent claims.
[Advantageous Effects of Invention]
0016The network access control method of an exemplary embodiment of the present invention configures the load threshold for restricting network access with different values according to time tolerant level of subscription, thereby efficiently controlling access barring to UEs when the network load reaches to the load threshold. That is, the network access control method of an exemplary embodiment of the present invention is advantageous to control the network access of the UEs efficiently according to the time tolerant level per MTC device or per MTC device's subscription.
[Brief Description of Drawings]
0017The above and other aspects, features, and advantages of certain exemplary embodiments of the present invention will be more apparent from the following description taken in conjunction with the accompanying drawings, in which: <ul id="ul0001" list-style="none" compact="compact"><li><figref idref="f0001">FIG. 1</figref> is a diagram illustrating a principle of a User Equipment (UE)-decisive network access control method according to an exemplary embodiment of the present invention;</li><li><figref idref="f0001">FIG. 2</figref> is a diagram illustrating a principle of a network-decisive network access control method in an Access Stratum (AS) level according to an exemplary embodiment of the present invention;</li><li><figref idref="f0001">FIG. 3</figref> is a diagram illustrating a principle of a network-decisive network access control method in a Non-Access Stratum (NAS) level according to an exemplary embodiment of the present invention;</li><li><figref idref="f0002">FIG. 4</figref> is a signaling diagram illustrating a UE-decisive network access control method according to an exemplary embodiment of the present invention;</li><li><figref idref="f0003">FIG. 5</figref> is a signaling diagram illustrating an evolved Node B (eNB)-decisive network access control method in an AS level according to an exemplary embodiment of the present invention; and</li><li><figref idref="f0004">FIG. 6</figref> is a signaling diagram illustrating a network-decisive network access control method in a NAS level according to an exemplary embodiment of the present invention.</li></ul>
0018Throughout the drawings, it should be noted that like reference numbers are used to depict the same or similar elements, features, and structures.
[Mode for the Invention]
0019The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of exemplary embodiments of the invention as defined by the claims. It includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope of the invention, as defined by the appended claims. In addition, description of well-known functions and constructions may be omitted for clarity and conciseness.
0020The terms and words used in the following description and claims are not limited to the bibliographical meanings, but, are merely used by the inventor to enable a clear and consistent understanding of the invention. Accordingly, it should be apparent to those skilled in the art that the following description of exemplary embodiments of the present invention is provided for illustration purpose only and not for the purpose of limiting the invention as defined by the appended claims.
0021It is to be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces.
0022By the term "substantially" it is meant that the recited characteristic, parameter, or value need not be achieved exactly, but that deviations or variations, including for example, tolerances, measurement error, measurement accuracy limitations and other factors known to skill in the art, may occur in amounts that do not preclude the effect the characteristic was intended to provide.
0023<figref idref="f0001 f0002 f0003 f0004">FIGs. 1 through 6</figref>, discussed below, and the various exemplary embodiments used to describe the principles of the present disclosure in this patent document are by way of illustration only and should not be construed in any way that would limit the scope of the disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged communications system. The terms used to describe various embodiments are exemplary. It should be understood that these are provided to merely aid the understanding of the description, and that their use and definitions in no way limit the scope of the invention. Terms first, second, and the like are used to differentiate between objects having the same terminology and are in no way intended to represent a chronological order, unless where explicitly state otherwise. A set is defined as a non-empty set including at least one element.
0024<figref idref="f0001">FIG. 1</figref> is a diagram illustrating a principle of a User Equipment (UE)-decisive network access control method according to an exemplary embodiment of the present invention.
0025Referring to <figref idref="f0001">FIG. 1</figref>, a UE 10, if it supports a time tolerant (or delay tolerant) feature, sends the access request message to the evolved Node B (eNB) 20 along with its time tolerant capability. If it is transmitted in an Access Stratum (AS) signaling, the access request message can be a Radio Resource Control (RRC) connection request message. In contrast, if it is transmitted in a Non-Access Stratum (NAS) signaling, the access request message can be an Attach Request Message or a Service Request message. In a case where the network load reaches the load threshold, the eNB 20 transmits a reject (connection release) message to the UE 10, and the reject message (hereinafter, the term "connection release" is used interchangeably) can contain a cause value indicating the rejected reason and a hold time. The cause value can be the information on the Mobility Management Entity (MME) overload, Serving Gateway/Packet Data Network Gateway (S-GW/P-GW) overload, or eNB overload. The UE 10 determines the reason of the network load by analyzing the cause value contained in the reject message and waits for the hold time to re-request the access. At this time, the UE 10 can reselect a cell (an eNB, or a Radio Access Network (RAN)) or a Public Land Mobile Network (PLMN) rather than requesting retrial of the network access.
0026The UE 10 configures a time tolerant level (or a delay tolerant level), a weight factor penalty, and a hold time penalty. If the network load within the eNB reaches the load threshold, the eNB 20 broadcasts barring information containing the Identifications (IDs) of classes and services to be barred, the weight factor indicating the current load status, and the hold time for which the barred UE waits before retrial.
0027If the barring information is received, the UE 10 compares its tolerant level and weight factor with those contained in the barring information. That is, the UE 10 compares its UE-specific load threshold with the current network load of the eNB 20 to decide whether to access the network or not. According to the relationship between the weight vector of the UE 10 and the tolerant level, the UE 10 can operate as follows:
0028If the weight factor is greater than (>) the tolerant level, the UE waits for the hold time before retrial of the network access. Here, the hold time can be the value obtained by adding a UE-specific hold time penalty to the received hold time. If the weight factor is less than (<) the tolerant level, the Machine Type Communication (MTC) UE generates random access numbers as much as random factor penalty. At this time, if all the random access numbers are greater than the weight factor, the MTC UE tries to access the network. In contrast, if any one of the random access numbers is less than the weight factor, the MTC UE waits for the hold time before retrial of the network access.
0029Thereafter, the UE 10 sends the access request message to the eNB 20 at a predefined time. If the access request message is received, the eNB 20 determines whether the eNB-specific network load has reached the network load threshold (network load configuration value) and, if the eNB-specific network load has reached the network load threshold, sends the reject message to the UE 10. Here, the reject message can include a cause value and a hold time. When the reject message is received, the UE 10 can retry access to the network after waiting for the hold time.
0030<figref idref="f0001">FIG. 2</figref> is a diagram illustrating a principle of a network-decisive network access control method in an AS level according to an exemplary embodiment of the present invention.
0031Referring to <figref idref="f0001">FIG. 2</figref>, an eNB 20 receives overload start messages of MME, SGW, and P-GW that are sent by the MME 30. If the overload start messages are received, the eNB sends a reject message to the UE 10. At this time, the reject message can contain the cause value and hold time information. Here, the cause value can be the information on the MME overload, SGW/P-GW overload, and/or eNB overload. In this case, the hold time carried by the reject message can be the hold time corresponding to the cause value. For example, the hold time can be the eNB-specific hold time for the eNB overload or the MME-specific hold time for the MME overload.
0032The MME 30 configures the load threshold of the MME 30 and the P-GW/SGW. Next, the MME 30 receives the current load status piggybacked in the messages from the SGW/P-GW. The MME 30 then determines whether the current load of the MME or the SGW/P-GW is greater than the network load threshold and, if the current load of the MME or the SGW/P-GW is greater than the network load threshold, sends an overload start message (including MTC UE, hold time, and weight factor information) to the eNB 20.
0033In this state, if the UE 10 generates an RRC connection request message including an MTC UE indicator and time-tolerant indication, the eNB 20 sends an RRC connection release message to the UE 10. That is, if the overload start message is received from the MME 30 or the eNB 20 is in the overload state, the eNB rejects the RRC connection request as the service request of the UE 10. If the RRC release request message is received, the UE retries to access the network after waiting for the hold time.
0034<figref idref="f0001">FIG. 3</figref> is a diagram illustrating a principle of a network-decisive network access control method in an NAS level according to an exemplary embodiment of the present invention.
0035Referring to <figref idref="f0001">FIG. 3</figref>, if overload is detected at the MME, SGW, or P-GW, an MME 30 sends an overload start message to the eNB 20. In this state, if the UE 10 sends a NAS attach request message, the MME 30 sends a reject message containing the cause value and the hold time to the UE 10. At this time, the overload can be a network entity-specific hold time configured by the MME, SGW, or P-GW. If the reject message is received, the UE 10 retries to access the network to send the NAS message after waiting for the hold time. As mentioned above, the NAS request message can be the attach request message, the service request message, or tracking area update message.
0036The MME 30 receives the current load status of the S-GW/P-GW 40 piggybacked in the messages from the S-GW/P-GW 40. Meanwhile, the UE 10 sends an attach request or service request message to the MME 30 via the eNB 20. At this time, if the UE 10 is an MTC UE and supports time-tolerant function, the attach request or service request message can contain an MTC UE indicator and a time-tolerant indicator. If the attach request or service request message is received, the MME 30 delivers the request message to the S-GW/P-GW 40 and receives the load status information of the S-GW/P-GW 40 in response to the request message.
0037The MME 30 also acquires the subscription information to determine the load levels of the MME 30 and S-GW/P-GW 40 as the threshold for MTC UE's barring is included in the subscription of the UE.
0038Thereafter, the MME 30 determines whether the current load level of the MME or S-GW/P-GW is greater than the threshold value set in the UE's subscription and, if it is, generates a reject message (attach reject or service reject message) and sends the reject message to the UE 10.
0039If the reject message is received, the UE 10 retries to access the network after waiting for the hold time.
0040<figref idref="f0002">FIG. 4</figref> is a signaling diagram illustrating a UE-decisive network access control method according to an exemplary embodiment of the present invention.
0041Referring to <figref idref="f0002">FIG. 4</figref>, an MTC UE first configures UE-specific time tolerant level, weight factor penalty, and hold time penalty in step 111. Meanwhile, the eNB configures the eNB-specific load level to start barring for the class or service corresponding to the MTC UE in step 113.
0042Thereafter, if the network load of the eNB reaches the eNB-specific load level, the eNB detects this status in step 115 and configures the class or service ID indicating the MTC UE, the weight factor indicating the current load status, and the holding time for which the UE waits for before retrial. If the load of the MME, S-GW, or P-GW reaches the load level, the eNB receives the overload start message from the MME 30. In step 117, the eNB broadcasts the configured barring information including class or service and hold time.
0043If the barring information is received, the UE compares the weight factor with the tolerant level configured in the UE in step 119. That is, the UE compares the current load of the eNB with the UE-specific load level and controls network access based on the comparison result. The UE can operate as follows according to the relationship of the weight factor and the tolerant level: If the current load of the eNB is greater than the load level configured in the UE, i.e., if the weight factor > the tolerant level, the MTC UE waits for the time calculated by multiplying the hold time with the hold time penalty.
0044Secondly, if the current load of the eNB is less than the load level configured in the UE, i.e., if the weight factor < the tolerant level, the MTC UE generates random access numbers as much as random factor penalty, compares the random access numbers with weight factor, and controls network access based on the comparison result. If all random access numbers (k) are larger than the weight factor, the MTC UE tries to access the network. In contrast, if any number (k) is smaller than the weight factor, the MTC UE waits for the time duration calculated by multiplying the hold time with the hold time penalty (hold time <sup>∗</sup> hold time penalty).
0045If it is determined in step 119 to access the network, the UE sends the eNB a request message for establishing the connection to the network in step 121. The request message can be an AS message or an NAS message and include the time-tolerant indication. The AS message can be the RRC connection request message, and the NAS message can be the attach request message, the service request message, or tracking area update message.
0046If it is determined that the UE has the time controlled feature which allows accessing the network at a predefined time and if the predefined time expires, the UE may not apply the hold time penalty, both the hold time nor the hold time penalty, or the weight factor.
0047After sending the network connection request, the UE may receive the reject message (or connection release message) from the eNB. This can be the case where the overload is detected in the eNB, MME, S-GW, or P-GW. As mentioned above, the reject message can include only the cause value and the hold time. If the reject message is received, the UE waits for the hold time before retrying to access the network.
0048<figref idref="f0003">FIG. 5</figref> is a signaling diagram illustrating an eNB-decisive network access control method in an AS level according to an exemplary embodiment of the present invention.
0049Referring to <figref idref="f0003">FIG. 5</figref>, in step 211, an MME configures the MME load level and P-GW/S-GW load level to send the barring information to the class or service corresponding to the MTC UE. In step 213, the MME receives the current load status of the S-GW and P-GW which is piggybacked in the messages from the S-GW and/or P-GW while serving other UE.
0050Thereafter, the MME monitors the network and, if it is determined in step 215 that the current MME or S-GW/P-GW load reaches the configured load level for the MTC UE, sends the overload start message to the eNB in step 217. That is, when the current load status of the MME or the S-GW/P-GW is greater than the configured load level, the MME permits only the network access of the normal UEs and thus sends the overload start message to the eNB for barring the MTC UE. Here, the overload start message can include the MTC UE indicator to indicate the MTC UE to be barred, the cause value to indicate the reason of the overload, and the hold time configured based on the time for the overload to be addressed which is estimated with a probability calculation. The overload start message can further include the weight factor indicating the current load status.
0051Thereafter, in step 219, if an RRC connection request message containing the MTC UE indicator is received from the MTC UE, the eNB sends an RRC connection release message to the UE in response to the RRC connection request message in step 221. That is, when the overload start message is received from the MME or the eNB is in the overload status, the eNB rejects the RRC connection request as the service request from the MTC UE. The RRC connection release message sent by the eNB can include the cause value indicating the MTC UE barring due to the Core Network overload and the hold time indicating the time for the overload to be solved during which the MTC UE waits for retrial of the network access.
0052Upon receipt of the RRC release message, the UE waits for the hold time before retrial in step 223. Here, the UE can apply a penalty to the hold time according to the time tolerance level of the UE service as in the UE-decisive access control method described with reference to <figref idref="f0002">FIG. 4</figref>. As mentioned above, the UE can attempt to access another reselected cell (i.e., another eNB). <figref idref="f0004">FIG. 6</figref> is a signaling diagram illustrating a network-decisive network access control method in an NAS level according to an exemplary embodiment of the present invention.
0053Referring to <figref idref="f0004">FIG. 6</figref>, in step 311, an MME receives the information on the current load status of the S-GW/P-GW which is piggybacked in the messages from the S-GW/P-GW while serving other UEs.
0054Thereafter, the MME receives an attach request message or a service request message transmitted by an MTC UE in step 313. In a case where the S-GW/P-GW load status information stored in the MME is older than a predefined age, the MME sends a load status request message to the S-GW/P-GW and receives the S-GW/P-GW load status information in step 315.
0055In addition, the MME acquires the information of the MME and S-GW/P-GW load levels for barring the MTC UE included in the UE's subscription by exchanging updater location request (UE id) and update location Acknowledgment ACK (subscription) messages with the HSS in step 317. In a case where the UE has sent the service request, the MME skips step 317 since it has the information on the UE's subscription.
0056Thereafter, the MME determines whether the current load level of the MME or S-GW/P-GW is greater than the configured value for the UE's subscription and, if it is, sends a reject message (attach reject or service reject message) to the MTC UE in step 321. That is, the MME gets the configured load level of the MME or S-GW/P-GW in the subscription and, if the load level reaches the configured load level in step 319, the MME rejects the attach request from the MTC UE in step 321. At this time, the reject message can include the cause value indicating the MTC UE barring due to the Core Network overload and the hold time indicating the time for the overload to be solved during which the MTC UE waits for retrial of the network access.
0057Upon receipt of the reject message, the UE waits for the hold time before retrial. When retrying to access the network, the UE can apply a penalty to the hold time according to the time tolerance level of the UE service as in UE-decisive access control method described with reference to <figref idref="f0002">FIG. 4</figref>.
0058As described above, the network access control method of an exemplary embodiment of the present invention configures the load threshold for restricting network access with different values according to time tolerant level of subscription, thereby efficiently controlling access barring to UEs when the network load reaches to the load threshold. That is, the network access control method of an exemplary embodiment of the present invention is advantageous to control the network access of the UEs efficiently according to the time tolerant level per MTC device or per MTC device's subscription.
0059While the invention has been shown and described with reference to certain exemplary embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the scope of the invention as defined by their appended claims.
4 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| CN107969015A | Cited by | China | Search report |
| CN101610494A | Cites | China | Examiner |
| EP0994604A2 | Cites | European Patent Office (EPO) | – |
| WO2009096833A1 | Cites | World Intellectual Property Organization (WIPO) | – |
| CN101610494A | Cites | China | – |
| KR20090046035A | Cites | Republic of Korea | – |
| US2002041568A1 | Cites | United States of America | – |
| US2007248060A1 | Cites | United States of America | – |
| US2009028060A1 | Cites | United States of America | – |
| US2009190518A1 | Cites | United States of America | – |
| "LTE; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification (3GPP TS 36.331 version 9.1.0 Release 9)", TECHNICAL SPECIFICATION, EUROPEAN TELECOMMUNICATIONS STANDARDS INSTITUTE (ETSI), 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS ; FRANCE, vol. 3GPP RAN 2, no. V9.1.0, 1 February 2010 (2010-02-01), XP014046913, | Non-patent | – | – |
| SAMSUNG: "MTC Time Tolerant Feature", 3GPP DRAFT; S2-101137-MTCTIMETOLERANT, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. San Francisco, USA; 20100222, 16 February 2010 (2010-02-16), XP050433713, [retrieved on 2010-02-16] | Non-patent | – | – |
| "Universal Mobile Telecommunications System (UMTS); Radio Resource Control (RRC); Protocol specification (3GPP TS 25.331 version 9.1.0 Release 9)", TECHNICAL SPECIFICATION, EUROPEAN TELECOMMUNICATIONS STANDARDS INSTITUTE (ETSI), 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS ; FRANCE, vol. 3GPP RAN 2, no. V9.1.0, 1 February 2010 (2010-02-01), XP014046584, | Non-patent | – | – |
| ZTE: "Time Tolerant optimization", 3GPP DRAFT; S2-101044 TIME TOLERANT OPTIMIZATION, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. San Francisco, USA; 20100222, 12 February 2010 (2010-02-12), XP050433599, [retrieved on 2010-02-12] | Non-patent | – | – |
| "3 rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Improvements for Machine-Type Communications; (Release 10)", 3GPP STANDARD; 3GPP TR 23.888, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V0.2.1, 1 February 2010 (2010-02-01), pages 1-19, XP050401847, [retrieved on 2010-02-01] | Non-patent | – | – |
| CATT: "Access control of MTC devices", 3GPP DRAFT; R2-100182, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Valencia, Spain; 20100118, 12 January 2010 (2010-01-12), XP050420962, [retrieved on 2010-01-12] | Non-patent | – | – |
12 members in 5 offices
Priority claims3
| Document | Office | Kind | Date |
|---|---|---|---|
| 20100013749 | Republic of Korea | – | |
| 20100013749 | Republic of Korea | A | |
| 2011000966 | Republic of Korea | W |
Members12
| Document | Office | Kind | |
|---|---|---|---|
| US2011199898A1 | United States of America | A1 | |
| KR20110094408A | Republic of Korea | A | |
| WO2011102624A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2011102624A3 | World Intellectual Property Organization (WIPO) | A3 | |
| EP2537372A2 | European Patent Office (EPO) | A2 | |
| US9066277B2 | United States of America | B2 | |
| US2015289139A1 | United States of America | A1 | |
| KR101670253B1 | Republic of Korea | B1 | |
| US9648498B2 | United States of America | B2 | |
| EP2537372A4 | European Patent Office (EPO) | A4 | |
| EP2537372B1This record | European Patent Office (EPO) | B1 | |
| ES2800982T3 | Spain | T3 |
68 legal events, as 9 offices reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | Office | |
|---|---|---|---|
| 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 | |
| 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 | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | 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 because of non-payment of the annual feeLapsedMM | MM | BE | |
| 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 filedOpposition26N | 26N | 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 | |
| No opposition filed against granted patent, or epo opposition proceedings concluded without decisionGrantedR097 | R097 | 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 | |
| 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 | |
| Definitive protectionFG2A | FG2A | ES | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Deletion acc. to par. 5 (withdrawal of the translation of the ep patent)MK05 | MK05 | AT | |
| 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 | |
| Invalidated european patentMG4D | MG4D | LT | |
| Translation for ep filed (entry of ep into country)FP | FP | NL | |
| Dpma publication of mentioned ep patent grantGrantedR096 | R096 | DE | |
| European patent takes effect as a national patent in ch/liEP | EP | CH | |
| Reference to at number (ep patent validated in austria)REF | REF | AT | |
| Designated contracting statesAK | AK | EP | |
| European patent grantedGrantedFG4D | FG4D | GB | |
| (expected) grantORIGINAL CODE: 0009210GRAA | GRAA | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: THE PATENT HAS BEEN GRANTEDSTAA | STAA | EP | |
| Grant fee paidORIGINAL CODE: EPIDOSNIGR3GRAS | GRAS | EP | |
| Intention to grant announcedINTG | INTG | EP | |
| Despatch of communication of intention to grant a patentORIGINAL CODE: EPIDOSNIGR1GRAP | GRAP | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: GRANT OF PATENT IS INTENDEDSTAA | STAA | EP | |
| First examination report despatched17Q | 17Q | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: EXAMINATION IS IN PROGRESSSTAA | STAA | EP | |
| Supplementary search report drawn up and despatchedA4 | A4 | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Request for extension of the european patent (deleted)DAX | DAX | 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
- 2537372
- Application
- 117448662
Titles3
- German
- VERFAHREN UND VORRICHTUNG ZUR STEUERUNG EINES NETZWERKZUGRIFFS EINER BENUTZEREINRICHTUNG IN EINEM DRAHTLOSEN KOMMUNIKATIONSSYSTEM
- English
- METHOD AND APPARATUS FOR CONTROLLING NETWORK ACCESS OF UE IN WIRELESS COMMUNICATION SYSTEM
- French
- PROCÉDÉ ET APPAREIL DE CONTRÔLE D'ACCÈS AU RÉSEAU D'UN ÉQUIPEMENT UTILISATEUR DANS UN SYSTÈME DE COMMUNICATION SANS FIL
Classification
- CPC, 5
- H04W4/70
- H04W48/02
- H04W76/18
- H04W48/06
- H04W12/08
- IPC, 3
- H04W48 06
- H04W4 70
- H04W76 18
Designated states1
- Contracting states, 1
- Türkiye
