[go: up one dir, main page]

WO2012083739A1 - Procédé d'accès aléatoire et terminal - Google Patents

Procédé d'accès aléatoire et terminal Download PDF

Info

Publication number
WO2012083739A1
WO2012083739A1 PCT/CN2011/080006 CN2011080006W WO2012083739A1 WO 2012083739 A1 WO2012083739 A1 WO 2012083739A1 CN 2011080006 W CN2011080006 W CN 2011080006W WO 2012083739 A1 WO2012083739 A1 WO 2012083739A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
random access
waiting time
length
system message
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.)
Ceased
Application number
PCT/CN2011/080006
Other languages
English (en)
Chinese (zh)
Inventor
艾建勋
邓云
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.)
ZTE Corp
Original Assignee
ZTE 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 ZTE Corp filed Critical ZTE Corp
Publication of WO2012083739A1 publication Critical patent/WO2012083739A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H04W74/0841—Random access procedures, e.g. with 4-step access with collision treatment
    • H04W74/085—Random access procedures, e.g. with 4-step access with collision treatment collision avoidance

Definitions

  • the present invention relates to the field of mobile communications, and in particular, to a random access method and a terminal. Background technique
  • H2H Human to Human
  • ⁇ 2 ⁇ machine to machine
  • the definition is based on the intelligent interaction of the machine terminal, and the networked application and service. It is based on the intelligent machine terminal, and uses multiple communication methods as access means to provide customers with information solutions to meet customer requirements. Information needs for monitoring, command and dispatch, data collection and measurement.
  • ⁇ 2 ⁇ can be applied to industrial applications, home applications, personal applications, etc., in the field of industrial applications such as: traffic monitoring, warning systems, maritime rescue, vending machines, car payment, etc., in the field of home applications such as: Automatic meter reading, temperature control, etc., for personal use applications such as: life detection, remote diagnosis, etc.
  • ⁇ 2 ⁇ communication object is machine-to-machine or person-to-machine, data communication between one or more machines is defined as Machine Type Communication (MTC), in this case less human-computer interaction is required, and participation in MTC Machine, defined as MTC equipment (MTC Device, MD ).
  • MTC Machine Type Communication
  • MD MTC equipment
  • the MTC device is a terminal of the MTC user, and can communicate with the MTC device and the MTC server through a public Land Mobile Network (PLMN) network.
  • PLMN public Land Mobile Network
  • the existing system can be optimized according to its characteristics to meet the requirements of the M2M application, and it does not affect the ordinary H2H equipment in the existing system.
  • Some notable features of the M2M application include: The number of MTC devices is huge, and the number is much higher than the existing H2H devices; the data transmission is regular, the amount of data transmitted per time is small; the mobility of MTC devices is low, and a large part of MTC devices are Not moving.
  • FIG 1 is a flow chart of the contention-based random access procedure in the existing Long Term Evolution (LTE) system, as shown in Figure 1, in LTE.
  • the contention-based random access process mainly includes the following four steps:
  • Step 102 The user equipment (User Equipment, UE) randomly selects a preamble (Preamble) and transmits it on a Physical Random Access Channel (PRACH).
  • Preamble a preamble
  • PRACH Physical Random Access Channel
  • Step 104 After detecting the transmission of the Preamble code, the base station (eNB) sends a random access response (RAR) in the downlink, where the random access response generally includes the following information: The number of the received Preamble code The time adjustment amount corresponding to the received Preamble code, the uplink resource location indication information allocated to the terminal, and the temporary Temporary Cell Radio Network Temporary Identifier (Temporary C-RNTI) allocation.
  • RAR random access response
  • Step 106 After receiving the random access response, the UE sends an uplink message on the allocated uplink resource according to the indication.
  • the uplink message is also called Message 3 (Msg3), and at least should include: the terminal's unique identifier (TMSI) or random identifier (Random ID), and the establishment cause ( Establishment Cause ).
  • Step 108 The base station receives the uplink message of the UE, and returns a contention to the UE with successful access.
  • Contention Resolution also known as Msg4. If the UE receives the message before the collision resolution timer expires, and the packet is confirmed to be the Msg4 expected by the UE, it is determined that the random access procedure is successful; otherwise, the UE is re-initiated the random access. The UE re-initiating random access needs to restart from step 102.
  • the random access fails.
  • the random access of the LTE system is implemented in the medium access control (MAC). After the random access fails, the MAC layer needs to notify the upper layer of the user equipment of the failure. If the upper layer of the user equipment still needs to initiate a service, it will trigger the MAC layer to initiate random access again.
  • MAC medium access control
  • the MTC device Before the introduction of the MTC device, it is initiated and released by the person to control the service. When the user needs to initiate a service, the user equipment continuously initiates random access until the random access succeeds. If the random access fails multiple times, the user may terminate the connection request of the service. However, after the introduction of the MTC device, because there is no human participation, when the MTC device has data to transmit (when the service needs to be initiated), the MTC device continuously initiates random access until the data is successfully transmitted, so that when the number of MTCs is large, When the device needs to access the network to send data or update the location area, it is easy to make the wireless resource overloaded, causing the random access initiated by the MTC device to fail, and the network cannot be successfully implemented because the MTC device continuously initiates random access. restore. Summary of the invention
  • the main purpose of the present invention is to provide a random access method and a terminal, which can solve the problem that a large number of terminals continuously initiate random access, causing network overload and cannot be successfully recovered in a random access process, and improve random access. Success rate.
  • a random access method includes: after the terminal fails to access the random access, waiting for the set time to initiate random access.
  • the set time is obtained according to the length of the waiting time pre-agreed by the protocol, or is obtained according to the waiting time length carried in the system message.
  • the length of the waiting time pre-agreed by the protocol or the length of the waiting time of the system message is: according to the terminal type, and/or the terminal priority, and/or the priority of the service initiated by the terminal, and/or whether the terminal initiates the service to allow the delay, And/or the group to which the terminal belongs, and/or the terminal access level, and/or the terminal roaming situation, the corresponding waiting time length set,
  • the terminal acquires the set time as: the terminal according to its own terminal type, and/or the terminal priority, and/or the priority of the service initiated by the terminal, and/or whether the terminal initiates the service to allow the time delay, and/or the terminal belongs to Information such as group, and/or terminal access level, and/or terminal roaming status, query protocol agreement or length of waiting time carried by the system message, and the obtained waiting time length value is used as the set time.
  • the set time is obtained according to the waiting time length carried by the system message: According to the waiting time length of the new d and the area system message, the set time is obtained.
  • the terminal is a machine type communication MTC device and/or a person-to-person communication H2H device.
  • the waiting time length of the system message is the length of the waiting time set by the network side according to the random access load or the access restriction requirement set by the core network.
  • a terminal is configured to wait for a set time to initiate random access after a random access failure.
  • the set time is obtained by the terminal according to the length of the waiting time pre-agreed by the protocol, or is obtained by the terminal according to the waiting time length carried in the system message.
  • the length of the waiting time pre-agreed by the protocol on which the terminal obtains the set time or the length of the waiting time carried in the system message is: according to the terminal type, and/or the terminal priority, and/or the priority of the service initiated by the terminal, and / Or the terminal initiates the service whether the delay is allowed, and/or the group to which the terminal belongs, and/or the terminal access level, and/or the terminal roaming situation, and the corresponding waiting time length is set, and the terminal acquires the set time as: Its own terminal type, and / or terminal priority Level, and/or priority of the service initiated by the terminal, and/or whether the terminal initiates the service, whether the time delay is allowed, and/or the group to which the terminal belongs, and/or the terminal access level, and/or the terminal roaming situation, etc., the query protocol
  • the length of the waiting time carried by the appointment or system message, and the obtained waiting time length value is used as the set time.
  • the terminal After the random access fails and the cell is reselected, the terminal acquires the set time according to the waiting time length of the system message: According to the new d, the waiting time length carried by the area system message acquires the set time.
  • the terminal is an MTC device and/or an H2H device.
  • the present invention provides a random access method and a terminal. After detecting a random access failure, the terminal waits for a set time and then initiates random access. With the present invention, after the random access fails, the terminal waits for a period of time and then re-initiates the random access, so as to avoid the radio resource shortage caused by the frequent re-initiation of the random access by the terminal in the case of the wireless resource overload. Moreover, the invention can average the number of terminals accessing the network per unit time, thereby improving the success rate of random access.
  • 1 is a flow chart of a contention-based random access procedure in an existing LTE system
  • FIG. 2 is a schematic flowchart of a random access method according to the present invention.
  • FIG. 3 is a schematic flow chart of an MTC device (referred to as MD1) accessing a network according to Embodiment 1 of the present invention. detailed description
  • the basic idea of the present invention is: After detecting that the random access fails, the terminal waits for the set time to initiate random access.
  • Step 201 The terminal randomly fails to access.
  • Step 202 After the terminal waits for the set time, the random access is initiated again.
  • the set time may be obtained by the terminal according to the length of the waiting time pre-agreed by the protocol, or may be acquired by the terminal according to the waiting time length carried in the system message.
  • the protocol pre-agreed waiting time length may be: the protocol pre-agreed the waiting time length of a certain type of terminal; and/or, agreeing on the waiting time length of a certain priority terminal; and/or, arranging the terminal to initiate a certain priority service
  • the length of time; and/or, the length of the waiting time of the roaming terminal in other words, according to the terminal type, and/or the terminal priority, and/or the priority of the service initiated by the terminal, and/or whether the terminal initiates the service to allow the delay, And/or the group to which the terminal belongs, and/or the terminal access level, and/or the terminal roaming situation, and the corresponding waiting time length is set by means of a protocol.
  • the length of the system message carrying waiting time may be: a system message includes a waiting time length of a certain type of terminal; and/or a waiting time length including a certain priority terminal; and/or, including a terminal to initiate a certain priority
  • the length of the waiting time of the service and/or, including the length of the waiting time when the terminal initiates whether to allow the service to be delayed; and/or, the length of the waiting time including the terminal belonging to a group; and/or, including an access level
  • the length of the waiting time of the terminal; and/or, including the length of the waiting time of the roaming terminal in other words, the system side may initiate according to the terminal type, and/or the terminal priority, and/or the priority of the service initiated by the terminal, and/or the terminal.
  • the service allows delay, and/or the group to which the terminal belongs, and/or the terminal access level, and/or the terminal roaming situation, sets a corresponding waiting time length, and carries the set waiting time length through the system message.
  • the terminal according to its own terminal type, and/or terminal priority, and/or the priority of the service initiated by the terminal, and/or whether the terminal initiates the service to allow the delay, and/or the group to which the terminal belongs, and/or the terminal access level, And/or information about the terminal roaming situation, the length of the waiting time of the protocol agreement or the system message, and the obtained waiting time length value is used as the set time. If the terminal obtains the waiting time length through the system message, the network side sets the waiting time length included in the system message according to the random access load or the access restriction requirement set by the core network.
  • the set time of the waiting time length according to the system message is: According to the waiting time length of the new d and the area system message, set time.
  • the terminal may be an MTC device and/or an H2H device.
  • the present invention also correspondingly proposes a terminal, which is set to wait for a set time to initiate random access after a random access failure.
  • the set time is obtained by the terminal according to the length of the waiting time pre-agreed by the protocol, or is obtained by the terminal according to the waiting time length carried in the system message.
  • the length of the waiting time pre-agreed by the protocol on which the terminal obtains the set time or the length of the waiting time carried in the system message is: according to the terminal type, and/or the terminal priority, and/or the priority of the service initiated by the terminal, and / Or the terminal initiates the service whether the delay is allowed, and/or the group to which the terminal belongs, and/or the terminal access level, and/or the terminal roaming situation, and the corresponding waiting time length is set, and the terminal acquires the set time as: Its own terminal type, and/or terminal priority, and/or the priority of the terminal originating service, and/or whether the terminal initiated service allows delay, and/or the group to which the terminal belongs, and/or the terminal access level, and/or Or the information such as the terminal roaming situation, the length of the waiting time of the protocol agreement or the system message, and the obtained waiting time length value is used as the set time.
  • the terminal After the random access fails and the cell is reselected, the terminal acquires the set time according to the waiting time length of the system message: According to the new d, the waiting time length carried by the area system message acquires the set time.
  • the terminal is an MTC device and/or an H2H device.
  • Example 1 In this embodiment, a large number of MTC devices and H2H devices reside in a cell managed by any one of the LTE systems. Some of these devices are in a connected state, and some are in an idle state. At some point, some MTC devices need to initiate a service request because of data transmission.
  • 3 is a schematic flowchart of accessing a network by an MTC device (referred to as MD1) according to Embodiment 1 of the present invention. As shown in FIG. 3, the process includes:
  • Step 301 MD1 initializes related parameters, such as setting the preamble transmission times ( PREAMBLE_ TRANSMISSION_COUNTER) to 1.
  • Step 302 MD1 randomly selects a preamble (Preamble) and transmits it on a Physical Random Access Channel (PRACH).
  • Preamble a preamble
  • PRACH Physical Random Access Channel
  • Step 303 Whether the MD1 receives the random access response within the predetermined time window, if yes, step 304 is performed; otherwise, step 307 is performed.
  • the predetermined time window is a time window in which the protocol specified by the protocol receives the random access response.
  • Step 304 The MD1 sends the Msg3 on the indicated uplink resource (or the uplink grant) according to the received random access response, and starts a conflict resolution timer, where the Msg3 at least includes: the unique identifier of the terminal (TMSI) ) or random ID (Random ID), and Establishment Cause.
  • TMSI unique identifier of the terminal
  • RVID random ID
  • Step 305 The MD1 determines whether the expected contention resolution message Msg4 sent by the base station is received before the conflict resolution timer expires. If yes, go to step 306; otherwise, go to step 307.
  • Step 306 The random access is successful, and the process ends.
  • Step 307 The number of preamble transmissions is increased by one.
  • Step 308 MD1 determines whether the number of preamble transmissions is greater than the maximum number of transmissions. If yes, go to step 309; otherwise, go to step 302.
  • Step 309 The random access fails, and the upper layer reports that the random access fails, on the MD1.
  • the layer (the RRC layer or the non-access stratum) determines whether the service request needs to be initiated again. If necessary, wait for a period of time, and then trigger the MAC layer to initiate random access again, and MD1 restarts to perform step 301; if not, the MD1 access The flow of the network ends and MD1 remains idle.
  • step 309 if the MD1 needs to continue to initiate a service request, the timer needs to be started. After the timer expires, the MAC layer can be triggered to initiate random access again. This can avoid the shortage of random access resources and the conflicts caused by a large number of MTC devices accessing the network. By delaying the time period, the number of MTC devices accessing the network per unit time can be averaged, and the random access of the MTC devices is improved. Success rate. It can avoid that a large number of MTC devices access the network at the same time, causing overload of the wireless resources, and the random access initiated again will cause the network to fail to return to the normal state.
  • the waiting period adopts a pre-agreed manner in the protocol, and the protocol may pre-agreed the waiting time length of a certain type of terminal.
  • the MTC device needs to wait 600 seconds, and the H2H device needs to wait for 0. second;
  • the protocol may also pre-agreed the waiting time length of a certain priority terminal. For example, a terminal with a low priority needs to wait for 1000 seconds, and a terminal with a normal priority needs to wait for 100 seconds;
  • the protocol may also pre-arrange the length of waiting time for the terminal to initiate a certain priority service (or whether to allow the service to be delayed). For example, when the terminal is scheduled to initiate a low priority service (or allow the delayed service), it needs to wait for 500 seconds, and the terminal is required to initiate a high priority.
  • Level service (or no delay in service), waiting for 100 seconds; existing protocol supports terminal to initiate high priority service (highPriorityAccess), emergency service (Emergency, emergency service priority is the highest), due to paging Initiated services (mt-Access), user-initiated signaling services (mo-signaling), user-initiated data services (mo-data), introduced for MTC devices, can add other priority services, such as electronic meter reading Business (smart meter, smart meter, etc., etc.) is a time-tolerant service. This type of service can be called low-priority service or Delay Tolerant. For monitoring services, such as monitoring vehicle anti-theft.
  • the alarm service initiated by the MTC device belongs to a service with low time tolerance, and the service can be delineated. High priority The service can also introduce a new priority to indicate that the MTC device initiates a service that is not delayed (non Delay Tolerant).
  • the protocol can also pre-approve the waiting time of the terminals belonging to a group. Different terminals can belong to different groups. For example, the protocol pre-agreed for a group of terminals needs to wait 200 seconds, and other groups of terminals need to wait for 100 seconds. ;
  • the protocol may also pre-arrange the waiting time length of the terminal of an access class, and save the corresponding access level in the terminal, that is, the protocol may pre-agreed the waiting time length of the terminals of different access levels;
  • the protocol may also save the signed Local Public Land Mobile Network (HPLMN) in the terminal's User Identification Identity Card (USIM) according to whether the terminal roams in advance and waits for the length of the waiting time, or includes Equivalent Home PLMN (EHPLMN), if the terminal access network does not belong to HPLMN, or does not belong to HPLMN and EHPLMN, the terminal is a roaming terminal. If the protocol can stipulate that the waiting time of the roaming terminal is 1000. Seconds, the non-roaming terminal waits for a length of 0 seconds.
  • HPLMN Local Public Land Mobile Network
  • USIM User Identification Identity Card
  • a large number of MTC devices and H2H devices reside in a cell managed by any one of the LTE systems. Some of these devices are in a connected state, and some are in an idle state. At some point, some MTC devices need to initiate a service request because of data transmission.
  • the process of accessing the network by the MTC device (referred to as MD2) is similar to the process described in Embodiment 1, except that after determining that the number of retransmissions is greater than the maximum number of retransmissions, the upper layer of MD2 (RRC layer or non-access stratum) It is determined whether the service request needs to be initiated again. If necessary, wait for a period of time, and then trigger the MAC layer to initiate random access again.
  • the process of accessing the network by MD2 ends, and MD2 remains idle.
  • the waiting period is obtained from the system message, and when the MD2 accesses the current cell, the waiting time is obtained from the system message, but the MD2 is not immediately applied. This parameter is applied only after the random access fails.
  • the waiting time for the priority of the terminal such as setting the waiting time of the low priority terminal (or only the MTC device) to 1000 seconds, and the normal priority terminal waiting time to 100 seconds;
  • the waiting time for the priority of the service initiated by the terminal such as setting the waiting time for the terminal to initiate the low priority service (allowing the delayed service) to be 5 minutes, and setting the waiting time for the other priority services to be 0 minutes;
  • the waiting time for the access level of the terminal is 100 seconds, and the waiting time for other ACs is 0 seconds.
  • the waiting time for the group to which the terminal belongs is 500 seconds, and the waiting time for other groups is 100 seconds.
  • the waiting time for the roaming feature of the terminal is 600 seconds, and the non-roaming terminal waiting time is 0 seconds.
  • the terminal When the terminal enters the current cell, the terminal obtains the waiting time from the system message, and the terminal saves the parameter. If the terminal fails to access the random access because it needs to initiate a service request, the corresponding timer is started, and the timer duration is equal to the waiting time. The terminal can initiate random access again only when the timer expires.
  • the base station sets the waiting time by using the system message, and can dynamically set the waiting time according to the current radio resource load level, and can reasonably control the number of terminals that initiate random access in a unit time. If the current random access load is high (initiating a random connection) Into The number of terminals is large. The base station sets a long waiting time through system messages to reduce the current random access collision and improve the success rate of random access of the terminal.
  • the core network also imposes access restriction requirements on the base station according to its own load, such as The base station sends an access restriction requirement for limiting the access rate of a certain terminal, and the base station sets the waiting time length in the system message according to the requirements of the core network.
  • the terminal selects another cell after the random access failure occurs, and the terminal selects another cell, and the terminal initiates the random access again, the waiting time in the system message of the new resident cell needs to be applied. After the timer corresponding to the waiting time expires, the random access can be initiated again. After the terminal reselects the cell, the terminal still uses the waiting time in the original cell system message. After the timer corresponding to the waiting time expires, the random connection can be initiated again. In.
  • the base station can set the waiting time in the random access response. After the terminal obtains the waiting time through the random access response, after the random access fails, it needs to wait for the set time, and then can again Initiate random access. This requires adding a new cell in the random access response to indicate the latency.
  • the terminal obtains the waiting time by using the system message. After the terminal randomly fails to access the terminal, the terminal takes a random number between 0 and the waiting time as the actual waiting time, and only expires in the actual waiting time. After that, random access can be initiated again.
  • WCDMA Wideband Code Division Multiple Access
  • H2H devices reside in a cell under the jurisdiction of a Radio Network Control (RNC). Some of these devices are connected and some are idle. At some point, some MTC devices need to initiate a service request because of data transmission.
  • RNC Radio Network Control
  • One of the MTC devices (called MD1) initiates random access by:
  • the random access procedure of the physical layer in WCDMA is triggered by the MAC layer.
  • the physical layer first determines the random access resources according to the parameters obtained from the RRC layer and the MAC (signature and available).
  • the ACK identifier is received on the downlink time slot:
  • the physical layer sends an access message to the network side (RACH Message part). 0 After the data transmission is completed, the state "RACH message transmitted" is fed back to the MAC layer, and the physical random access procedure is exited. . This indicates that the random access is successful.
  • the NACK identifier is received on the downlink time slot: At this time, the physical layer feeds back the status "Nack on AICH received" to the MAC and exits the physical random access procedure.
  • the physical layer will reselect the random access resource, increase the transmission power, and perform random access again; If the number of transmissions of the Preamble reaches the upper limit, the physical layer feeds back the status "No ack on AICH" to the MAC layer and exits the physical random access procedure.
  • the upper layer of MD1 does not receive the "RACH message transmitted" of the physical layer feedback, it indicates that the random access fails. If MD1 still needs to initiate a service request, it will trigger the physical layer to implement the random access procedure again. At this time, it is necessary to wait for a period of time, which can be controlled by the RRC layer, or controlled by the MAC layer, or controlled by the physical layer.
  • the waiting time can be set in a pre-agreed manner in the protocol or set by system messages.
  • the protocol is agreed in the same manner as the method described in Embodiment 1, and the system message setting is the same as that described in Embodiment 2.
  • the number of terminals that initiate random access in a unit time can be controlled, and the success rate of random access of the terminal is improved. It can avoid overloading of wireless resources caused by a large number of terminals accessing the network at the same time.
  • the terminal deletes the configuration of the original cell waiting time, and immediately initiates random access in the new cell.
  • modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne un procédé d'accès aléatoire consistant à, lorsqu'un terminal détecte un échec d'accès aléatoire, relancer l'accès aléatoire après avoir attendu un temps déterminé. La présente invention concerne également, de manière correspondante, un terminal. Selon la présente invention, lorsque le terminal ne parvient pas à réaliser un accès aléatoire, l'accès aléatoire est relancé après avoir attendu un temps prédéfini, de manière à éviter le manque de ressources sans fil dû au fait que le terminal relance de façon continue l'accès aléatoire dans une situation de surcharge des ressources sans fil, et l'application de la présente invention permet ainsi de moyenner le nombre d'accès au réseau du terminal dans une unité de temps, ce qui permet d'améliorer le taux de réussite de l'accès aléatoire.
PCT/CN2011/080006 2010-12-22 2011-09-22 Procédé d'accès aléatoire et terminal Ceased WO2012083739A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010602025.0 2010-12-22
CN201010602025.0A CN102548012B (zh) 2010-12-22 2010-12-22 一种随机接入方法及终端

Publications (1)

Publication Number Publication Date
WO2012083739A1 true WO2012083739A1 (fr) 2012-06-28

Family

ID=46313117

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/080006 Ceased WO2012083739A1 (fr) 2010-12-22 2011-09-22 Procédé d'accès aléatoire et terminal

Country Status (2)

Country Link
CN (1) CN102548012B (fr)
WO (1) WO2012083739A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
RU2740512C1 (ru) * 2017-08-09 2021-01-15 Бейджин Сяоми Мобайл Софтвеа Ко., Лтд. Способ и устройство защиты от перегрева пользовательского оборудования, пользовательское оборудование и базовая станция
US20220015151A1 (en) * 2017-01-23 2022-01-13 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Method for random access, and terminal device and network device

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109547186B (zh) * 2013-08-14 2022-02-18 华为技术有限公司 一种随机接入网络的方法、终端和基站
CN106162923A (zh) * 2015-04-10 2016-11-23 中兴通讯股份有限公司 随机接入信令的重新发送方法及装置
CN106412091A (zh) * 2016-10-25 2017-02-15 广东欧珀移动通信有限公司 数据传输的控制方法、装置及系统
EP3531784B1 (fr) * 2016-12-26 2020-09-09 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Procédé et appareil d'accès aléatoire
CN113873556B (zh) * 2017-04-20 2024-06-04 北京小米移动软件有限公司 保护用户设备的方法、装置、用户设备及基站
US11184941B2 (en) 2017-05-18 2021-11-23 Beijing Xiaomi Mobile Software Co., Ltd. Method and apparatus for protecting user equipment, user equipment and base station
CN109429356B (zh) * 2017-08-23 2020-07-14 维沃移动通信有限公司 一种系统信息传输的处理方法和用户终端
CN107404746B (zh) * 2017-08-25 2020-12-29 深圳传音通讯有限公司 针对随机接入小区失败后的重选优化系统及方法
CN108769995B (zh) * 2018-05-29 2023-04-18 武汉虹信科技发展有限责任公司 一种业务调度处理方法及装置
CN113473571B (zh) * 2021-06-29 2022-10-21 中信科移动通信技术股份有限公司 小区接入控制方法、装置和基站
CN115379586B (zh) * 2022-08-22 2025-02-14 上海移芯通信科技股份有限公司 一种随机接入的回退优化方法及装置
CN119865923A (zh) * 2025-01-06 2025-04-22 中国联合网络通信集团有限公司 一种通信方法、程序产品、装置及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101247647A (zh) * 2007-02-15 2008-08-20 中兴通讯股份有限公司 一种增强上行链路实现快速切换的方法
CN101547513A (zh) * 2008-03-25 2009-09-30 华为技术有限公司 一种多频点系统中控制用户设备接入的方法及网络设备
CN101616488A (zh) * 2008-06-23 2009-12-30 华为技术有限公司 一种增强随机接入的控制方法、装置及系统
GB2461780A (en) * 2008-06-18 2010-01-20 Lg Electronics Inc Method for detecting failures of random access procedures

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1260917C (zh) * 2002-12-03 2006-06-21 华为技术有限公司 一种随机接入的控制方法
CN101132622B (zh) * 2006-08-20 2010-05-12 华为技术有限公司 一种随机接入时的服务质量控制方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101247647A (zh) * 2007-02-15 2008-08-20 中兴通讯股份有限公司 一种增强上行链路实现快速切换的方法
CN101547513A (zh) * 2008-03-25 2009-09-30 华为技术有限公司 一种多频点系统中控制用户设备接入的方法及网络设备
GB2461780A (en) * 2008-06-18 2010-01-20 Lg Electronics Inc Method for detecting failures of random access procedures
CN101616488A (zh) * 2008-06-23 2009-12-30 华为技术有限公司 一种增强随机接入的控制方法、装置及系统

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220015151A1 (en) * 2017-01-23 2022-01-13 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Method for random access, and terminal device and network device
US11617213B2 (en) * 2017-01-23 2023-03-28 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Method for random access, and terminal device and network device
RU2740512C1 (ru) * 2017-08-09 2021-01-15 Бейджин Сяоми Мобайл Софтвеа Ко., Лтд. Способ и устройство защиты от перегрева пользовательского оборудования, пользовательское оборудование и базовая станция

Also Published As

Publication number Publication date
CN102548012A (zh) 2012-07-04
CN102548012B (zh) 2019-03-15

Similar Documents

Publication Publication Date Title
WO2012083739A1 (fr) Procédé d'accès aléatoire et terminal
CN102740493B (zh) 终端接入控制调整方法及系统
CN103957603B (zh) 机器类型通信的增强型随机接入信道设计
CN102404865B (zh) 优先化随机接入方法
Cheng et al. Overload control for machine-type-communications in LTE-advanced system
EP3200543B1 (fr) Procédé pour configurer une fenêtre de réponse d'accès aléatoire, station de base et équipement d'utilisateur
CN107277741B (zh) 基站及其方法
CN107864499B (zh) 用户设备的接入控制方法和装置
CN103929826B (zh) 一种机器类通信终端自适应随机接入方法及系统
CN102740492B (zh) 随机接入控制方法及系统
WO2012083741A1 (fr) Procédé d'accès aléatoire et terminal
US20130121303A1 (en) Method for distributing random access, method for distributing and performing random access, and device therefor
TW201306530A (zh) 加強型傳呼的方法及其機器類型通訊裝置
WO2012024996A1 (fr) Procédé d'accès aléatoire et système apparenté
WO2012129905A1 (fr) Procédé et système permettant de commander et de déterminer la puissance d'émission d'un préambule au cours d'un processus d'accès aléatoire
WO2012041112A1 (fr) Procédé de régulation de puissance, appareil côté réseau et terminal associé
WO2012058985A1 (fr) Procédé et système d'accès réseau par terminal
CN102740374A (zh) 接入控制方法及系统
Cheng et al. Performance evaluation of radio access network overloading from machine type communications in LTE-A networks
CN115553052A (zh) 用于无线通信系统中的无线电链路失败报告的方法和装置
CN102469554B (zh) 终端接入网络的方法及终端
WO2011160565A1 (fr) Procédé et système de configuration d'informations publiques de cellule
CN102638880A (zh) 一种终端发送数据的方法及装置
CN102238689B (zh) 一种机器类型通信终端的接入控制方法及系统
KR101845558B1 (ko) 무선 통신 시스템에서의 그룹 페이징 방법 및 장치와 이를 이용한 랜덤 액세스 수행 방법 및 장치

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11850996

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11850996

Country of ref document: EP

Kind code of ref document: A1