A random access fallback optimization method and device

Abstract

The present invention provides a random access fallback optimization method, comprising: when a random access failure is detected, obtaining a random access triggering reason, a RAR Backoff value, and a timer running state of a current RRC layer; determining a target Backoff duration based on the random access triggering reason, the RAR Backoff value, and the timer running state of the current RRC layer; and initiating random access again in different ways according to the target Backoff duration. When a UE detects a random access failure, a suitable Backoff mechanism is comprehensively formulated in combination with the service requirements of the application layer and the signaling process of the current RRC layer, thereby effectively reducing the UE power consumption while improving the success rate of random access.

Description

Technical Field

[0001] The present invention relates to the field of network technology, and in particular to a random access fallback optimization method and device. Background Art

[0002] Random access refers to the process of establishing an initial radio link between a UE and a cell, and its main purpose is to enable the UE to obtain uplink time synchronization and a unique user identity C-RNTI (Cell Radio Network Temporary Identifier). The types of random access are divided into contention-based random access and non-contention-based random access.

[0003] For 4 / 5G, low-power Internet of Things (Cat1, eMTC / NB-IOT), the random access process is roughly similar. The following is an example of 4G LTE network, which mainly includes the following steps: 1) UE sends a random access preamble (preamble) on the PRACH (Physical Random Access Channel) resource, i.e. MSG1; 2) UE monitors PDCCH (Physical Downlink Control Channel) within the RAR (Random Access Respond) time window to receive RAR, i.e. MSG2; 3) UE sends MSG3 on PUSCH (Physical Uplink Shared Channel) and starts the contention resolution timer; 4) Before the contention resolution timer expires, the UE will continue to monitor PDCCH to receive the contention resolution message, i.e. MSG4. It should be pointed out that non-contention-based random access does not require the above steps 3) and 4).

[0004] Based on the above process, if the UE receives a BI (Backoff Indicator) in the RAR, it will save a Backoff value specified by the BI. It specifies the backoff time (0 to a random value within the BI) before the UE resends the preamble. If the UE does not receive the RAR within the RAR time window, or there is no RAPID (Random Access Preamble IDentifier) ​​in the received RAR that matches the preamble in MSG1, it is considered that the RAR reception has failed. At this time, the UE needs to back off for a period of time before initiating random access. In addition, the same is true when MSG4 conflict resolution fails.

[0005] It can be seen that if the BI configured by the network is large, the access delay will increase and the power consumption will increase. In addition, the random access process may also be accompanied by RRC establishment / reconstruction / switching / recovery processes, so the RRC layer also needs to control the total access waiting time according to the T300 / T301 / T304 / T319 duration. If the Backoff value is longer than these timers of the RRC layer, the probability of access failure will increase. Especially for NB-IOT IoT terminals with extremely high requirements for low power consumption, this increase in power consumption requires a better solution.

[0006] The prior art does not have a comprehensive and systematic Backoff mechanism that takes into account the business scenario and power consumption. For example, for NB-IOT terminals with extremely high requirements for low power consumption, especially for smart meter reading services, the transmission of small data packets is often time-sensitive, and waiting for Backoff may miss the opportunity to send. In addition, the failure of a random access does not mean that the data packet must be sent. On the contrary, it is more important to cancel the transmission in time and quickly enter PSM to save power consumption. For example, for services with reliable transmission, when the current cell is congested, access is still initiated on the current cell, and the network will also configure BI, which will cause too much access delay and will also cause the access failure due to the timeout of the RRC layer timer. At this time, if the RRC is allowed to change to a different cell to reside, access can be quickly initiated and data transmission can be completed. Patents CN111757531A and CN114245477A do not combine actual business scenarios, but only optimize from the aspect of improving the success rate of random access, and do not consider the impact of power consumption, especially for IoT terminals with extremely high requirements for low power consumption. Summary of the invention

[0007] A technical problem to be solved by the present invention is that when the UE detects that random access fails, it is necessary to formulate an appropriate Backoff mechanism in combination with the service requirements of the application layer and the signaling process of the current RRC layer, so as to effectively reduce the power consumption of the UE while improving the success rate of random access. The present invention is achieved by the following technologies:

[0008] On the one hand, the present invention provides a fallback optimization method for random access, comprising:

[0009] When a random access failure is detected, the random access triggering cause, RAR Backoff value, and the current RRC layer timer running status are obtained;

[0010] Determine a target Backoff duration based on the random access triggering cause, the RAR Backoff value, and the timer running state of the current RRC layer;

[0011] According to the target Backoff duration, random access is initiated again in different ways.

[0012] In some embodiments, when a random access failure is detected, obtaining a random access triggering cause, a RARBackoff value, and a running state of a timer at a current RRC layer, and determining a target Backoff duration includes:

[0013] If the random access is not triggered by application layer data and the T300 / T301 / T304 / T319 timer of the RRC layer is not running, the target Backoff duration is randomly selected between 0 and the RAR Backoff value;

[0014] Otherwise, the target Backoff duration is randomly selected from 0 to min (RAR Backoff value, remaining valid duration of data, remaining running duration of RRC timer);

[0015] Alternatively, the target Backoff duration is randomly selected from a value between 0 and the RAR Backoff value.

[0016] In some embodiments, the re-initiating random access in different ways according to the target Backoff duration includes:

[0017] After waiting for the target Backoff time, the MAC layer initiates random access again on the original cell.

[0018] In some embodiments, the re-initiating random access in different ways according to the target Backoff duration includes:

[0019] If the random access is triggered by application layer data, when the remaining valid duration of the application layer data is less than or equal to the target Backoff duration, the data transmission is canceled, otherwise the data transmission is not canceled;

[0020] If the sending is cancelled, notify RRC / MAC to execute the MAC RESET process;

[0021] If data transmission is not canceled, determine whether to search for available neighboring cells in combination with the running status of the T300 / T301 / T304 / T319 timer of the RRC layer;

[0022] If searching for the available neighboring cell, immediately initiating random access on the available neighboring cell;

[0023] If the available neighboring cell is not searched, random access is initiated again after the original cell waits for the target Backoff time.

[0024] In some embodiments, if the data transmission is not canceled, determining whether to search for an available neighboring area in combination with the running state of the T300 / T301 / T304 / T319 timer of the RRC layer includes:

[0025] If the RRC establishment process is in progress and the remaining duration of T300 is less than or equal to the target Backoff duration, the RRC establishment process is terminated and the available neighboring cell is searched;

[0026] If the RRC reestablishment process is in progress and the remaining duration of T301 is less than or equal to the target Backoff duration, the RRC reestablishment process is terminated and the available neighboring cell is searched;

[0027] If the RRC handover process is in progress and the remaining duration of T304 is less than or equal to the target Backoff duration, the RRC handover process is terminated and the available neighboring cell is searched;

[0028] If the RRC recovery process is in progress and the remaining duration of T319 is less than or equal to the target Backoff duration, the RRC recovery process is terminated and the available neighboring cell is searched;

[0029] Otherwise, the available neighboring area is not searched.

[0030] A random access fallback optimization device, comprising:

[0031] An acquisition module, used to acquire a random access triggering cause, an RAR Backoff value, and a timer running status of a current RRC layer when a random access failure is detected;

[0032] A determination module, configured to determine a target Backoff duration based on the random access triggering cause, the RAR Backoff value, and the running state of the timer of the current RRC layer;

[0033] The initiating module is used to initiate random access again in different ways according to the target Backoff duration.

[0034] In some embodiments, the determining module is further configured to:

[0035] If the random access is not triggered by application layer data and the T300 / T301 / T304 / T319 timer of the RRC layer is not running, the target Backoff duration is randomly selected between 0 and the RAR Backoff value;

[0036] Otherwise, the target Backoff duration is randomly selected from 0 to min (RAR Backoff value, remaining valid duration of data, remaining running duration of RRC timer);

[0037] Alternatively, the target Backoff duration is randomly selected from a value between 0 and the RAR Backoff value.

[0038] In some embodiments, the initiating module is used to:

[0039] After waiting for the target Backoff time, the MAC layer initiates random access again on the original cell.

[0040] In some embodiments, the initiating module is used to:

[0041] If the random access is triggered by application layer data, when the remaining valid duration of the application layer data is less than or equal to the target Backoff duration, the data transmission is canceled, otherwise the data transmission is not canceled;

[0042] If the sending is cancelled, notify RRC / MAC to execute the MAC RESET process;

[0043] If data transmission is not canceled, determine whether to search for available neighboring cells in combination with the running status of the T300 / T301 / T304 / T319 timer of the RRC layer;

[0044] If searching for the available neighboring cell, immediately initiating random access on the available neighboring cell;

[0045] If the available neighboring cell is not searched, random access is initiated again after the original cell waits for the target Backoff time.

[0046] In some embodiments, a search module is included to:

[0047] If the RRC establishment process is in progress and the remaining duration of T300 is less than or equal to the target Backoff duration, the RRC establishment process is terminated and the available neighboring cell is searched;

[0048] If the RRC reestablishment process is in progress and the remaining duration of T301 is less than or equal to the target Backoff duration, the RRC reestablishment process is terminated and the available neighboring cell is searched;

[0049] If the RRC handover process is in progress and the remaining duration of T304 is less than or equal to the target Backoff duration, the RRC handover process is terminated and the available neighboring cell is searched;

[0050] If the RRC recovery process is in progress and the remaining duration of T319 is less than or equal to the target Backoff duration, the RRC recovery process is terminated and the available neighboring cell is searched.

[0051] The random access fallback optimization method and system provided by the present invention have at least the following beneficial effects: when the UE detects that the random access fails, an appropriate Backoff mechanism is comprehensively formulated in combination with the service requirements of the application layer and the signaling process of the current RRC layer, thereby effectively reducing the UE power consumption while improving the random access success rate. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] The preferred implementation scheme will be described below in a clear and understandable manner with reference to the accompanying drawings to further illustrate the above-mentioned characteristics, technical features, advantages and implementation methods of a random access fallback optimization system.

[0053] Figure 1 is a schematic diagram of an embodiment of a random access fallback optimization method in the present invention;

[0054] Figure 2 This is a schematic diagram of a Backoff mechanism when random access fails in the present invention;

[0055] Figure 3 It is a schematic diagram of another Backoff mechanism when random access fails in the present invention. DETAILED DESCRIPTION

[0056] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.

[0057] It should be understood that when used in this specification and the appended claims, the term "comprising" indicates the presence of the described features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or collections.

[0058] In order to simplify the drawings, only the parts related to the present invention are schematically shown in each figure, and they do not represent the actual structure of the product. In addition, in order to simplify the drawings and facilitate understanding, in some figures, only one of the parts with the same structure or function is schematically drawn or marked. In this article, "one" not only means "only one", but also means "more than one".

[0059] It should be further understood that the term “and / or” used in the specification and appended claims refers to any combination and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0060] In addition, in the description of the present application, the terms "first", "second", etc. are only used to distinguish the description and cannot be understood as indicating or implying relative importance.

[0061] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the specific implementation methods of the present invention will be described below with reference to the accompanying drawings. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings and other implementation methods can be obtained based on these drawings without creative work.

[0062] In one embodiment, Figure 1 As shown, the present invention provides a fallback optimization method for random access, comprising:

[0063] When random access failure is detected in S101, the random access triggering reason, RAR Backoff value, and the timer running status of the current RRC layer are obtained.

[0064] S102 determines a target Backoff duration based on the random access triggering cause, the RAR Backoff value, and the running state of the timer of the current RRC layer.

[0065] S103 initiates random access again in a different manner according to the target Backoff duration.

[0066] In this embodiment, when the UE detects that random access fails, an appropriate Backoff mechanism is comprehensively formulated in combination with the service requirements of the application layer and the signaling process of the current RRC layer, thereby effectively reducing the power consumption of the UE while improving the success rate of random access.

[0067] In one embodiment, the present invention provides a random access fallback optimization method, wherein when a random access failure is detected, a random access triggering cause, an RAR Backoff value, and a timer running state of a current RRC layer are obtained, and a target Backoff duration is determined, including:

[0068] If the random access is not triggered by application layer data and the T300 / T301 / T304 / T319 timer of the RRC layer is not running, the target Backoff duration is randomly selected between 0 and the RAR Backoff value;

[0069] Otherwise, the target Backoff duration is randomly selected from 0 to min (RAR Backoff value, remaining valid duration of data, remaining running duration of RRC timer);

[0070] Alternatively, the target Backoff duration is randomly selected from a value between 0 and the RAR Backoff value.

[0071] Exemplarily, when it is determined that the random access is not triggered by application layer data and the RRC layer timer is not running, the target Backoff duration is randomly taken between 0 and the RAR Backoff value; otherwise, the target Backoff duration is randomly taken between 0 and min (RAR Backoff value, remaining valid time of the data, remaining running time of the RRC timer).

[0072] In this embodiment, if the current random access is not triggered by application layer data, and the T300 / T301 / T304 / T319 timer of the RRC layer is not running, then T_Target_BI_Delay is randomly selected between 0 and T_RAR_BI_Delay. Otherwise, it is randomly selected between 0 and min(T_RAR_BI_Delay, T_Data_Left_BI_Delay, T_RRC_Left_BI_Delay). Finally, MAC will wait for T_Target_BI_Delay to time out before initiating random access again.

[0073] Specifically, Figure 2 As shown, option 1:

[0074] 1. The UE detects a random access failure and determines that the network has configured a BI in the RAR and that it is not 0. If so, the RARBackoff value (T_RAR_BI_Delay) is specified by the BI, otherwise it is set to 0. If T_RAR_BI_Delay is not 0, jump to step 2, otherwise T_Target_BI_Delay is also set to 0 and jump to step 5.

[0075] 2. Determine whether the current random access is triggered by application layer data. If so, use the remaining valid duration of the application layer data as the data Backoff value (T_Data_Left_BI_Delay).

[0076] Among them, the application layer will indicate the validity period of the data packet in the signal of sending data, and pass it through layer by layer until it is finally given to the MAC layer.

[0077] 3. According to the current RRC layer signaling process, determine whether the corresponding T300 / T301 / T304 / T319 timer is running. If so, use the remaining duration of these timers as the RRC Backoff value (T_RRC_Left_BI_Delay).

[0078] Specifically, according to the internal state of RRC, it can be determined whether the current process is connection establishment process (T300) / reestablishment process (T301) / handover process (T304) / reconnection recovery process (T319), and these processes must have corresponding timers running. In addition, the OS timer mechanism of the UE itself also knows whether these timers are running and the remaining time.

[0079] The remaining time is the time interval from the current time to the timeout time of the timer.

[0080] T300: RRC connection establishment timer. It starts from when the UE sends MSG1 and ends when it receives RRCConnectionSetup or RRCConnectionReject. If it is not received within the period defined by the timer, it is recorded as T300 timeout.

[0081] T301: RRC re-establishment timer.

[0082] The timing starts from when the UE sends MSG1 and ends when it receives RRCConnectionReestablishment or RRCConnectionReestablishmentReject. If it is not received within the period defined by the timer, it is recorded as T301 timeout.

[0083] T304: Switch timer.

[0084] The process starts from when the UE receives RRCConnectionReconfiguration (including MobilityControlINfo) and ends when the UE completes the handover and sends RRCConnectionReconfigurationComplete. If the message is not received within the period defined by the timer, it is recorded as T304 timeout.

[0085] T319: Reconnection timer (38.331).

[0086] T319 is started when RRCResumeRequest / RRCResumeRequest1 is sent.

[0087] If you receive the following message, stop running T319:

[0088] RRCResume / RRCSetup / RRCRelease / RRCRelease with suspend / RRCReject. If the above message is not received, wait for T319 to time out.

[0089] 4. Take a minimum value among T_RAR_BI_Delay, T_Data_Left_BI_Delay (if it exists) and T_RRC_Left_BI_Delay (if it exists), and randomly select a value between 0 and this minimum value as the target Backoff duration (T_Target_BI_Delay).

[0090] 5. The MAC layer waits for T_Target_BI_Delay to time out and then initiates random access again.

[0091] The logic for determining the target backoff duration includes two solutions:

[0092] Solution 1:

[0093] If the random access is not triggered by application layer data and the T300 / T301 / T304 / T319 timer of the RRC layer is not running, the target Backoff duration is randomly selected between 0 and the RAR Backoff value;

[0094] Otherwise, the target Backoff duration is randomly selected between 0 and min (RAR Backoff value, remaining valid duration of data, remaining running duration of RRC timer).

[0095] Option 2:

[0096] The target Backoff duration is randomly selected between 0 and the RAR Backoff value.

[0097] In one embodiment, the present invention provides a random access backoff optimization method, wherein the random access is initiated again in different ways according to the target Backoff duration, including:

[0098] After waiting for the target Backoff time, the MAC layer initiates random access again on the original cell.

[0099] In one embodiment, the present invention provides a random access backoff optimization method, wherein the random access is initiated again in different ways according to the target Backoff duration, including:

[0100] If the random access is triggered by application layer data, when the remaining valid duration of the application layer data is less than or equal to the target Backoff duration, the data transmission is canceled, otherwise the data transmission is not canceled;

[0101] If the sending is cancelled, notify RRC / MAC to execute the MAC RESET process;

[0102] If data transmission is not canceled, determine whether to search for available neighboring cells in combination with the running status of the T300 / T301 / T304 / T319 timer of the RRC layer;

[0103] If searching for the available neighboring cell, immediately initiating random access on the available neighboring cell;

[0104] If the available neighboring cell is not searched, random access is initiated again after the original cell waits for the target Backoff time.

[0105] When the remaining valid duration of the application layer data is greater than the target Backoff duration, the RRC is notified to determine whether to search for an available neighboring cell according to the target Backoff duration;

[0106] After searching for the available neighboring cells, random access is initiated on the available neighboring cells. In one embodiment, if data transmission is not canceled, determining whether to search for available neighboring cells in combination with the running state of the T300 / T301 / T304 / T319 timer of the RRC layer includes:

[0107] If the RRC establishment process is in progress and the remaining duration of T300 is less than or equal to the target Backoff duration, the RRC establishment process is terminated and the available neighboring cell is searched;

[0108] If the RRC reestablishment process is in progress and the remaining duration of T301 is less than or equal to the target Backoff duration, the RRC reestablishment process is terminated and the available neighboring cell is searched;

[0109] If the RRC handover process is in progress and the remaining duration of T304 is less than or equal to the target Backoff duration, the RRC handover process is terminated and the available neighboring cell is searched;

[0110] If the RRC recovery process is in progress and the remaining duration of T319 is less than or equal to the target Backoff duration, the RRC recovery process is terminated and the available neighboring cell is searched;

[0111] Otherwise, the available neighboring area is not searched.

[0112] In this embodiment, if Figure 3The Backoff mechanism diagram when random access fails is shown in the figure. MAC determines the T_Target_BI_Delay duration, and the application layer determines whether to cancel data transmission based on T_Target_BI_Delay (if it is a random access triggered by application layer data). Finally, RRC determines whether to search for available neighboring cells based on T_Target_BI_Delay and its own business process, and immediately initiates random access on the neighboring cells.

[0113] Specifically, Figure 3 As shown, option 2:

[0114] 1. The UE detects that the random access fails and determines that the network has configured BI in the RAR and that it is not 0. If so, T_Target_BI_Delay is randomly set between 0 and the value specified by the BI, otherwise it is set to 0. If T_Target_BI_Delay is not 0, it is notified to the application layer (if the random access is triggered by application layer data) and the RRC layer, and jumps to step 2, otherwise T_Target_BI_Delay is also set to 0, and jumps to step 9;

[0115] 2. If the remaining valid time of the application layer data is less than or equal to T_Target_BI_Delay, the data transmission is canceled and the RRC / MAC is notified to execute the MAC RESET process to achieve the purpose of power saving;

[0116] 3. If the remaining valid time of the application layer data is greater than T_Target_BI_Delay, notify RRC to continue to initiate access;

[0117] 4. RRC further considers the following optimizations based on T_Target_BI_Delay and the current signaling process;

[0118] 5. If the RRC establishment process is currently in progress and the remaining duration of T300 is less than or equal to T_Target_BI_Delay, the establishment process ends in advance, and an available neighboring cell is immediately searched before the establishment process is executed again;

[0119] 6. If the RRC reestablishment process is in progress and the remaining duration of T301 is less than or equal to T_Target_BI_Delay, the reestablishment process ends in advance, and an available neighboring cell is immediately searched before the establishment process is executed;

[0120] 7. If the RRC handover process is in progress and the remaining time of T304 is less than or equal to T_Target_BI_Delay, the handover process ends in advance, and an available neighboring cell is immediately searched before the reestablishment process is performed;

[0121] 8. In addition, for 5G communications, the RRC recovery process must also be considered. If the RRC recovery process is currently in progress and the remaining time of T319 is less than or equal to T_Target_BI_Delay, the recovery process ends early, and the available neighboring cells are immediately searched before the establishment process is executed;

[0122] 9. RRC does not do anything and remains in the original cell. MAC waits for T_Target_BI_Delay to time out and then initiates random access again.

[0123] The common point of Solution 1 and Solution 2 is to shorten the waiting time for BackOff as much as possible, initiate random access or send data as early as possible, so as to reduce power consumption.

[0124] The difference between Solution 1 and Solution 2 is that Solution 1 shortens the BackOff time and initiates random access again on the current cell, while Solution 2 considers terminating the current process in advance and immediately initiates random access on an available neighboring cell.

[0125] The present invention also provides a random access fallback optimization device, comprising:

[0126] An acquisition module, used to acquire a random access triggering cause, an RAR Backoff value, and a timer running status of a current RRC layer when a random access failure is detected;

[0127] A determination module, configured to determine a target Backoff duration based on the random access triggering cause, the RAR Backoff value, and the timer running state of the current RRC layer;

[0128] The initiating module is used to initiate random access again in different ways according to the target Backoff duration. Based on the above embodiments, the parts of the present device that are the same as the above method will not be discussed one by one.

[0129] In one embodiment, the determining module is further used to:

[0130] If the random access is not triggered by application layer data and the T300 / T301 / T304 / T319 timer of the RRC layer is not running, the target Backoff duration is randomly selected between 0 and the RAR Backoff value;

[0131] Otherwise, the target Backoff duration is randomly selected from 0 to min (RAR Backoff value, remaining valid duration of data, remaining running duration of RRC timer);

[0132] Alternatively, the target Backoff duration is randomly selected from a value between 0 and the RAR Backoff value.

[0133] In one embodiment, the initiating module is used to:

[0134] After waiting for the target Backoff time, the MAC layer initiates random access again on the original cell.

[0135] In one embodiment, the initiating module is used to:

[0136] If the random access is triggered by application layer data, when the remaining valid duration of the application layer data is less than or equal to the target Backoff duration, the data transmission is canceled, otherwise the data transmission is not canceled;

[0137] If the sending is cancelled, notify RRC / MAC to execute the MAC RESET process;

[0138] If data transmission is not canceled, determine whether to search for available neighboring cells in combination with the running status of the T300 / T301 / T304 / T319 timer of the RRC layer;

[0139] If searching for the available neighboring cell, immediately initiating random access on the available neighboring cell;

[0140] If the available neighboring cell is not searched, random access is initiated again after the original cell waits for the target Backoff time.

[0141] In one embodiment, the search module is used to:

[0142] If the RRC establishment process is in progress and the remaining duration of T300 is less than or equal to the target Backoff duration, the RRC establishment process is terminated and the available neighboring cell is searched;

[0143] If the RRC reestablishment process is in progress and the remaining duration of T301 is less than or equal to the target Backoff duration, the RRC reestablishment process is terminated and the available neighboring cell is searched;

[0144] If the RRC handover process is in progress and the remaining duration of T304 is less than or equal to the target Backoff duration, the RRC handover process is terminated and the available neighboring cell is searched;

[0145] If the RRC recovery process is in progress and the remaining duration of T319 is less than or equal to the target Backoff duration, the RRC recovery process is terminated and the available neighboring cell is searched.

[0146] Those skilled in the art can clearly understand that, for the convenience and simplicity of description, only the division of the above-mentioned program modules is used for example. In practical applications, the above-mentioned function distribution can be completed by different program modules as needed, that is, the internal structure of the device is divided into different program units or modules to complete all or part of the functions described above. Each program module in the embodiment can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in a processing unit, and the above-mentioned integrated unit can be implemented in the form of hardware or in the form of software program units. In addition, the specific names of each program module are only for the convenience of distinguishing from each other, and are not used to limit the scope of protection of the present application.

[0147] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0148] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented with electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed with hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0149] In the embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. Exemplarily, the device embodiments described above are merely schematic. Exemplarily, the division of the modules or units is merely a logical function division, and there may be other division methods in actual implementation. Exemplarily, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the device or unit may be electrical, mechanical or other forms.

[0150] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0151] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0152] It should be noted that the above embodiments can be freely combined as needed. The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered as the protection scope of the present invention.

Claims

1. A fallback optimization method for random access, characterized in that: include: When a random access failure is detected, the random access triggering cause, RAR Backoff value, and the current RRC layer timer running status are obtained; Determine a target Backoff duration based on the random access triggering cause, the RAR Backoff value, and the timer running state of the current RRC layer; Among them, when the random access failure is detected, the random access triggering reason, the RAR Backoff value, and the current RRC layer timer running state are obtained, and the target Backoff duration is determined: if the random access is not triggered by application layer data, and the T300 / T301 / T304 / T319 timer of the RRC layer is not running, then the target Backoff duration is randomly selected between 0 and the RARBackoff value; otherwise, the target Backoff duration is randomly selected between 0 and min (RAR Backoff value, remaining valid duration of data, remaining running duration of RRC timer); According to the target Backoff duration, random access is initiated again in different ways.

2. The random access fallback optimization method according to claim 1, characterized in that: The re-initiating random access in different ways according to the target Backoff duration includes: After waiting for the target Backoff time, the MAC layer initiates random access again on the original cell.

3. The random access fallback optimization method according to claim 1, characterized in that: The re-initiating random access in different ways according to the target Backoff duration includes: If the random access is triggered by application layer data, when the remaining valid duration of the application layer data is less than or equal to the target Backoff duration, the data transmission is canceled, otherwise the data transmission is not canceled; If the sending is cancelled, notify RRC / MAC to execute the MAC RESET process; If data transmission is not canceled, determine whether to search for available neighboring cells in combination with the running status of the T300 / T301 / T304 / T319 timer of the RRC layer; If searching for the available neighboring cell, immediately initiating random access on the available neighboring cell; If the available neighboring cell is not searched, random access is initiated again after the original cell waits for the target Backoff time.

4. The random access fallback optimization method according to claim 3, characterized in that: If the data transmission is not canceled, determining whether to search for an available neighboring area in combination with the running status of the T300 / T301 / T304 / T319 timer of the RRC layer includes: If the RRC establishment process is in progress and the remaining duration of T300 is less than or equal to the target Backoff duration, the RRC establishment process is terminated and the available neighboring cell is searched; If the RRC reestablishment process is in progress and the remaining duration of T301 is less than or equal to the target Backoff duration, the RRC reestablishment process is terminated and the available neighboring cell is searched; If the RRC handover process is in progress and the remaining duration of T304 is less than or equal to the target Backoff duration, the RRC handover process is terminated and the available neighboring cell is searched; If the RRC recovery process is in progress and the remaining duration of T319 is less than or equal to the target Backoff duration, the RRC recovery process is terminated and the available neighboring cell is searched; Otherwise, the available neighboring area is not searched.

5. A random access fallback optimization device, characterized in that: include: An acquisition module, used to acquire a random access triggering cause, an RAR Backoff value, and a timer running status of a current RRC layer when a random access failure is detected; A determination module, configured to determine a target Backoff duration based on the random access triggering cause, the RAR Backoff value, and the timer running state of the current RRC layer; Wherein, the determining module is further used for: If the random access is not triggered by application layer data and the T300 / T301 / T304 / T319 timer of the RRC layer is not running, the target Backoff duration is randomly selected between 0 and the RAR Backoff value; Otherwise, the target Backoff duration is randomly selected from 0 to min (RAR Backoff value, data remaining valid duration, RRC timer remaining running duration); The initiating module is used to initiate random access again in different ways according to the target Backoff duration.

6. The random access fallback optimization device according to claim 5, characterized in that: The initiating module is used to: After waiting for the target Backoff time, the MAC layer initiates random access again on the original cell.

7. The random access fallback optimization device according to claim 5, characterized in that: The initiating module is used to: If the random access is triggered by application layer data, when the remaining valid duration of the application layer data is less than or equal to the target Backoff duration, the data transmission is canceled, otherwise the data transmission is not canceled; If the sending is cancelled, notify RRC / MAC to execute the MAC RESET process; If data transmission is not canceled, determine whether to search for available neighboring cells in combination with the running status of the T300 / T301 / T304 / T319 timer of the RRC layer; If searching for the available neighboring cell, immediately initiating random access on the available neighboring cell; If the available neighboring cell is not searched, random access is initiated again after the original cell waits for the target Backoff time.

8. The random access fallback optimization device according to claim 7, characterized in that: Includes search modules for: If the RRC establishment process is in progress and the remaining duration of T300 is less than or equal to the target Backoff duration, the RRC establishment process is terminated and the available neighboring cell is searched; If the RRC reestablishment process is in progress and the remaining duration of T301 is less than or equal to the target Backoff duration, the RRC reestablishment process is terminated and the available neighboring cell is searched; If the RRC handover process is in progress and the remaining duration of T304 is less than or equal to the target Backoff duration, the RRC handover process is terminated and the available neighboring cell is searched; If the RRC recovery process is in progress and the remaining duration of T319 is less than or equal to the target Backoff duration, the RRC recovery process is terminated and the available neighboring cell is searched.

Images