WO2018171470A1

WO2018171470A1 - Method for maintaining air interface state synchronization, terminal, base station and storage medium

Info

Publication number: WO2018171470A1
Application number: PCT/CN2018/078861
Authority: WO
Inventors: 戴谦
Original assignee: 中兴通讯股份有限公司
Priority date: 2017-03-23
Filing date: 2018-03-13
Publication date: 2018-09-27
Also published as: CN108924963A; CN108924963B

Abstract

Disclosed is a method for maintaining air interface state synchronization. The method comprises: when a terminal is in an RRC connected state, if the terminal detects that same satisfies a first pre-set condition, the terminal converting the state thereof from the RRC connected state to an inactive state, and if a base station detects that same and the terminal satisfy a third pre-set condition, the base station converting the state of the terminal from the RRC connected state to the inactive state; and when the terminal is in the inactive state, if the terminal detects that same satisfies a second pre-set condition, the terminal converting the state thereof from the inactive state to an idle state, and if the base station detects that the terminal satisfies a fourth pre-set condition, the base station converting the state of the terminal from the inactive state to the idle state. Also disclosed are a terminal, a base station and a storage medium.

Description

Method, terminal, base station and storage medium for maintaining air interface state synchronization

Cross-reference to related applications

The present application is filed on the basis of the Chinese Patent Application No. PCT Application No. PCT Application Serial No.

Technical field

The present invention relates to the field of wireless communications, and in particular, to a method, a terminal, a base station, and a storage medium for maintaining air interface state synchronization.

Background technique

The Long Term Evolution (LTE) standard discussed in the current 3rd Generation Partnership Project (3GPP) and the new radio access technology of the fifth generation mobile communication (The new Radio Access Technology of The 5th In the Generation Mobile Communication Technology (5G New RAT) standard, a light connected state is introduced in LTE, and an inactive state is introduced in the 5G new RAT. The two states are similar in nature, and are connected to LTE wirelessly. In the case of the Radio Access Network (RAN) and the 5G RAN, both the light connected state and the inactive state belong to the sub-state of the Radio Resource Control (RRC) connection state. If the terminal is in the light connected state or the inactive state, Its RRC connection with the base station remains, and the signaling bearer and data bearer remain.

When the terminal is in the inactive state or the light connected state, in the process of establishing the RRC connection, or during the process of restoring the RRC connection, or during the process of transmitting the inactive uplink data transmission (inactive Up Data Transmit, inactive UL Data Tx) The eNB sends the RRC reject signaling, but the terminal does not receive the RRC reject. The terminal considers that the terminal is in the idle state; the terminal is actually in the inactive state or the light connected state. Or, when the terminal is in the inactive state or the light connected state, if the terminal sends the uplink data in the inactive state or the light connected state, the eNB sends the RRC release signaling, but the terminal fails to receive the terminal, and the base station considers that the terminal is in the terminal. Idle state; the terminal is actually in the inactive state or the light connected state. Alternatively, when the terminal is in the inactive state or the light connected state, if the base station detects a radio link failure (RLF) in the downlink data transmission, the base station deletes the terminal context (AS Context) autonomously, and sets the state of the terminal. The switch is in the idle state, but the terminal does not receive any RRC release signaling from the base station at this time, so the terminal considers that it is still in the inactive state or the light connected state.

It can be seen that the introduction of the above two new states can reduce the power consumption of the terminal and the number of times the terminal switches from the idle idle state to the connected state, and reduce signaling overhead; however, the state increase often results in a state between the terminal and the base station. Synchronization is more likely to happen.

Summary of the invention

In view of this, the embodiments of the present invention provide a method, a terminal, a base station, and a storage medium for maintaining air interface state synchronization, which implement state synchronization between a terminal and a base station in a specific case.

The technical solution of the embodiment of the present invention is implemented as follows:

An embodiment of the present invention provides a method for maintaining air interface state synchronization, including:

When the terminal is in the RRC connection state, if the terminal detects that it meets the first preset condition, the terminal converts its state from the RRC connection state to the inactive state; wherein the first preset condition is a condition that the terminal must satisfy when the terminal changes its state from the RRC connected state to the inactive state;

When the terminal is in the inactive state, if the terminal detects that the second preset condition is met, the terminal converts its own state from the inactive state to the idle state; wherein, the second The preset condition is a condition that the terminal must satisfy to convert its own state from the inactive state to the idle state.

In the above solution, the first preset condition includes:

The uplink of the terminal is out of synchronization, and the terminal does not generate RLF, and the terminal does not receive the resource scheduling signaling sent by the base station, and the terminal does not have to be transmitted to the base station to be transmitted. Data, and the terminal obtains an AS context ID sent by the base station; where the AS context ID is allocated by the base station, and is used to identify a terminal access layer context AS context stored in the base station.

In the above solution, the first preset condition further includes:

The terminal generates an RLF caused by an uplink out-of-synchronization, and the terminal does not receive the resource scheduling signaling sent by the base station, and the terminal does not have a data to be transmitted that needs to be sent to the base station, and the The terminal obtains the AS context ID sent by the base station, where the AS context ID is allocated by the base station, and is used to identify the terminal AS context stored in the base station.

In the above solution, the first preset condition further includes:

The first timer is started or restarted when the terminal sends and receives data, and the timing of the first timer exceeds a first timing value, and the terminal obtains an AS context ID sent by the base station; The AS context ID is allocated by the base station, and is used to identify a terminal AS context stored in the base station; the first timing value is a maximum timing duration of the first timer, and the first The timing value is configured by the base station in advance for the terminal; the data transmission and reception by the terminal includes the terminal receiving an uplink or downlink resource scheduling instruction allocated by the base station.

In the above solution, the second preset condition includes:

The terminal generates RLF, and the terminal fails to reselect other cells; wherein the other cells are cells other than the cell where the terminal is currently located.

In the above solution, the second preset condition further includes:

Starting or restarting the second timer timing when the terminal uplink transmission fails or the downlink transmission fails, and the timing duration of the second timer exceeds a second timing value; wherein the second timer is at the terminal The timing is stopped when the uplink transmission succeeds or the downlink transmission succeeds; the second timing value is the maximum timing duration of the second timer, and the second timing value is configured by the base station for the terminal in advance.

In the above solution, the second timer continues to be timed when the terminal reselects other cells; wherein the other cells are cells other than the cell where the terminal is currently located.

In the above solution, the second preset condition further includes:

Starting or restarting a third timer timing when data is transmitted and received by the terminal, and a timing duration of the third timer exceeds a third timing value; wherein the third timing value is a maximum timing of the third timer The time length, and the third timing value is configured by the base station in advance for the terminal; the data transmission and reception by the terminal includes the terminal receiving an uplink or downlink resource scheduling instruction allocated by the base station.

In the foregoing solution, when the terminal is in the inactive state, the method further includes:

The terminal stores its own AS context.

An embodiment of the present invention provides a method for maintaining air interface state synchronization, where the method includes:

When the terminal is in the RRC connection state, if the base station where the terminal is located detects that the terminal and the terminal meet the third preset condition, the base station converts the state of the terminal from the RRC connection state to the inactive state; The third preset condition is a condition that the base station must satisfy to convert the state of the terminal from the RRC connected state to the inactive state;

When the terminal is in the inactive state, if the base station detects that the terminal meets the fourth preset condition, the base station converts the state of the terminal from the inactive state to the idle state; The fourth preset condition is a condition that the base station must satisfy to convert the state of the terminal from the inactive state to the idle state.

In the above solution, the third preset condition includes:

The uplink of the terminal is out of synchronization, and the terminal does not generate RLF, and the base station does not send resource scheduling signaling to the terminal, and the terminal does not have data to be transmitted that needs to be sent to the base station, And the base station stores the AS context of the terminal, and the base station sends an AS context ID to the terminal, where the AS context ID is used to identify a terminal AS context stored in the base station.

In the above solution, the third preset condition further includes:

The terminal generates an RLF due to uplink out-of-synchronization, and the base station does not send resource scheduling signaling to the terminal, and the terminal does not have data to be transmitted that needs to be sent to the base station, and the base station An AS context is stored in the terminal, and the base station sends an AS context ID to the terminal. The AS context ID is used to identify a terminal AS context stored in the base station.

In the above solution, the third preset condition further includes:

Starting or restarting a fourth timer timing when data is transmitted and received by the terminal, and a timing duration of the fourth timer exceeds a fourth timing value, and the base station stores an AS context of the terminal, and the The base station sends an AS context ID to the terminal, where the AS context ID is used to identify the terminal AS context stored in the base station; the data transmission and reception of the terminal includes the base station allocating uplink or downlink resources to the terminal. Scheduling instructions.

In the above solution, the fourth preset condition includes: the terminal generates an RLF.

In the above solution, the fourth preset condition further includes:

Starting or restarting a fifth timer timing when the terminal uplink transmission fails or the downlink transmission fails, and the timing duration of the fifth timer exceeds a fifth timing value; wherein the fifth timer is at the base station The timing is stopped when the uplink transmission of the terminal is successful or the downlink transmission is successful.

In the above solution, the fourth preset condition further includes:

A sixth timer is started or restarted when data is transmitted and received by the terminal, and a timing of the sixth timer exceeds a sixth timing value; wherein the data transmission and reception of the terminal includes the base station being the terminal Allocate uplink or downlink resource scheduling instructions.

The base station stores an AS context of the terminal.

The embodiment of the invention provides a terminal, including:

a first processing unit, configured to: when the terminal is in an RRC connected state, if the terminal is configured to meet the first preset condition, the state of the terminal is changed from the RRC connected state to an inactive state; a preset condition is a condition that the first processing unit must satisfy to convert a state of the terminal from the RRC connected state to an inactive state;

a second processing unit, configured to: when the terminal is in the inactive state, if it is detected that the terminal meets the second preset condition, converting a state of the terminal from the inactive state to an idle state; The second preset condition is a condition that the second processing unit must satisfy to convert the state of the terminal from the inactive state to the idle state.

In the above solution, the first preset condition includes:

The uplink of the terminal is out of synchronization, and the terminal does not generate RLF, and the terminal does not receive the resource scheduling signaling sent by the base station, and the terminal does not have to be transmitted to the base station to be transmitted. Data, and the terminal obtains an access layer context identifier AS context ID sent by the base station; where the AS context ID is allocated by the base station, and is used to identify a terminal access layer stored in the base station Context AS context.

In the above solution, the first preset condition further includes:

In the above solution, the second preset condition includes:

In the above solution, the second preset condition further includes:

In the above solution, the terminal further includes:

The first storage unit is configured to store an AS context of the terminal.

An embodiment of the present invention provides a base station, including:

a third processing unit, configured to: when the terminal is in an RRC connected state, if the terminal and the base station are configured to meet a third preset condition, the state of the terminal is changed from the RRC connected state to an inactive state; The third preset condition is a condition that the third processing unit must satisfy to convert the state of the terminal from the RRC connected state to the inactive state;

a fourth processing unit, configured to: when the terminal is in the inactive state, if it is detected that the terminal meets the fourth preset condition, the state of the terminal is changed from the inactive state to the idle state; The fourth preset condition is a condition that the fourth processing unit must satisfy to convert the state of the terminal from the inactive state to the idle state.

In the above solution, the third preset condition includes:

In the above solution, the third preset condition further includes:

In the above solution, the fourth preset condition further includes:

In the foregoing solution, the terminal further includes: a second storage unit configured to store an AS context of the terminal.

The embodiment of the present invention further provides a terminal, including a processor and a memory storing the processor-executable instructions, and when the instruction is executed by the processor, performing the method of maintaining the air interface state synchronization implemented by the terminal side.

The embodiment of the present invention further provides a base station, including a processor and a memory storing the processor executable instructions, and when the instruction is executed by the processor, performing a method for maintaining an air interface state synchronization implemented by the base station side.

The embodiment of the present invention further provides a storage medium, where the computer-executable instructions are stored in the storage medium, and the computer-executable instructions are used to execute the foregoing method for maintaining air interface state synchronization.

The method, the terminal, the base station, and the storage medium for maintaining the air interface state synchronization provided by the embodiment of the present invention, when the terminal is in the RRC connection state, if the terminal detects that the terminal meets the first preset condition, the terminal converts its own state from the RRC connection state. If the base station detects that the terminal and the terminal meet the third preset condition, the base station changes the state of the terminal from the RRC connection state to the inactive state. When the terminal is in the inactive state, the terminal detects that the terminal meets the second preset condition. The terminal converts its state from the inactive state to the idle state. If the base station detects that the terminal meets the fourth preset condition, the base station converts the state of the terminal from the inactive state to the idle state, so that the terminal and the base station together state the state of the terminal. The RRC connection state is switched to the inactive state, or from the inactive state to the idle state, so that the state synchronization can still be maintained between the terminal and the base station in a specific case.

DRAWINGS

1 is a schematic flowchart 1 of a method for maintaining air interface state synchronization according to an embodiment of the present invention;

2 is a second schematic flowchart of a method for maintaining air interface state synchronization according to an embodiment of the present invention;

3 is a schematic flowchart 3 of a method for maintaining air interface state synchronization according to an embodiment of the present invention;

4 is a schematic flowchart 4 of a method for maintaining air interface state synchronization according to an embodiment of the present invention;

FIG. 5 is a schematic flowchart 5 of a method for maintaining air interface state synchronization according to an embodiment of the present invention;

6 is a schematic flowchart 6 of a method for maintaining air interface state synchronization according to an embodiment of the present invention;

FIG. 7 is a schematic flowchart diagram 7 of a method for maintaining air interface state synchronization according to an embodiment of the present disclosure;

FIG. 8 is a schematic structural diagram of a terminal according to an embodiment of the present disclosure;

FIG. 9 is a schematic structural diagram of another terminal according to an embodiment of the present disclosure;

FIG. 10 is a schematic structural diagram of a base station according to an embodiment of the present disclosure;

FIG. 11 is a schematic structural diagram of another base station according to an embodiment of the present disclosure;

FIG. 12 is a schematic structural diagram of hardware of an electronic device according to an embodiment of the present invention.

detailed description

First, some scenarios are described to illustrate the case where the RRC state is not synchronized at the terminal side and the base station side.

Scenario 1: When the terminal is in the RRC connected state, the terminal receives the suspend signaling sent by the eNodeB (e-Node B, eNB) of the LTE system, and the signaling is used to convert the terminal state to the light connected state. It is assumed that the terminal needs to feed back the acknowledgment of Radio Link Control (RLC ACK) to the eNB after receiving the signaling, so that the eNB confirms that the terminal has received the signaling, but in actuality, the ACK is changed due to the wireless channel. If the cause of the difference is not received by the eNB, the eNB will consider that the suspend signaling fails to be sent, and the terminal is still in the RRC connection state. In fact, the terminal successfully receives the suspend signaling and switches to the light connected state, so the terminal side appears. Not synchronized with the status of the base station side.

Scenario 2: When the terminal is in the RRC connected state, the eNB sends suspend signaling to the terminal, and prepares to convert the terminal to the light connected state, but in actuality, the signaling is not received by the terminal because the radio channel is degraded, then The eNB does not know that the terminal does not successfully receive the signaling, and the eNB converts the terminal state to the light connected state. In fact, the terminal does not receive the conversion signaling, and the state of the terminal is still in the RRC connection state, so the terminal side and the The base station side status is not synchronized.

Scenario 3: When the terminal is in the inactive state, if the terminal initiates an RRC connection establishment process, or an RRC connection recovery process, or uplink data transmission to the 5G base station (g-Node B, gNB), if the gNB is in the process due to the load If the terminal is too high and the terminal is rejected, the gNB sends an RRC reject message to the terminal, but the terminal does not successfully receive the message. Therefore, the base station considers that the terminal is in the idle state, and the terminal is still in the inactive state.

Scenario 4: When the terminal is in the inactive state, if the terminal initiates uplink data transmission to the 5G base station gNB, the gNB sends an RRC release to the terminal because the load is too high, but the terminal fails to receive the message. It is in the idle state, and the terminal is still in the inactive state.

Scenario 5: When the terminal is in the inactive state, if the base station is transmitting downlink data to the terminal, the continuous transmission fails due to the deterioration of the wireless channel in the process. When the number of failures is too large, the base station determines that the terminal has RLF. At this time, the gNB will automatically convert the terminal state to the idle state, and since there is no explicit signaling to notify the terminal, the terminal does not know that the base station has been converted, and the terminal is still in the inactive state.

Scenario 6: When the terminal is in the inactive state, if the terminal is sending uplink data to the gNB, the continuous transmission fails due to the deterioration of the radio channel in the process. When the number of failures is too high, the terminal determines that the terminal has RLF. At this time, the terminal will automatically convert the terminal state to the idle state, and the base station does not know that the terminal has been converted, and the base station is still in the inactive state.

Scenario 1 and Scenario 2 describe the case where the RRC state of the existing LTE system mechanism is not synchronized on the terminal side and the base station side; and scenarios 3 to 6 describe that the RRC state existing in the existing LTE system mechanism is on the terminal side. The situation is not synchronized with the state of the base station side.

The following describes how to implement state synchronization of the RRC state on the terminal side and the base station side in a specific embodiment.

An embodiment of the present invention provides a schematic flowchart 1 of a method for maintaining an air interface state synchronization. As shown in FIG. 1 , the method includes the following steps:

Step 101: When the terminal is in the RRC connected state, if the terminal detects that it meets the first preset condition, the terminal converts its own state from the RRC connected state to the inactive state.

The first preset condition is a condition that the terminal must satisfy when converting the state of the terminal from the RRC connected state to the inactive state.

Step 102: When the terminal is in the RRC connected state, if the base station where the terminal is located detects that the terminal and the terminal meet the third preset condition, the base station changes the state of the terminal from the RRC connected state to the inactive state.

The third preset condition is a condition that the base station must satisfy to convert the state of the terminal from the RRC connected state to the inactive state.

Step 103: When the terminal is in the inactive state, if the terminal detects that it meets the second preset condition, the terminal converts its own state from the inactive state to the idle state.

The second preset condition is a condition that the terminal must satisfy when converting the state of the state from the inactive state to the idle state.

Specifically, the step 103: converting the terminal from the inactive state to the idle state may be implemented by the terminal.

Step 104: When the terminal is in the inactive state, if the base station detects that the terminal meets the fourth preset condition, the base station converts the state of the terminal from the inactive state to the idle state.

The fourth preset condition is a condition that the base station must satisfy when converting the state of the terminal from the inactive state to the idle state.

It should be noted that there is no logical sequence between the step 101 implemented by the terminal and the step 102 implemented by the base station, that is, the terminal can implement step 101 while the terminal implements step 101; There is no logical sequence between the steps 104 implemented by the base station, that is, the terminal can implement step 104 while the terminal implements step 103.

The method for maintaining the state of the air interface state is provided in this embodiment. When the terminal is in the RRC connection state, if the terminal detects that the terminal meets the first preset condition, the terminal changes its state from the RRC connection state to the inactive state; if the base station detects The terminal and the terminal satisfy the third preset condition, and the base station changes the state of the terminal from the RRC connection state to the inactive state. When the terminal is in the inactive state, if the terminal detects that it meets the second preset condition, the terminal sets its own state from the inactive state. The state is converted to the idle state. If the base station detects that the terminal meets the fourth preset condition, the base station converts the state of the terminal from the inactive state to the idle state. In this way, the terminal and the base station convert the state of the terminal from the RRC connected state to the inactive state. Or from the inactive state to the idle state, so that the state and the base station can still maintain state synchronization in a specific case.

An embodiment of the present invention provides a schematic flowchart 2 of a method for maintaining an air interface state synchronization. The method is used to describe how a terminal and a base station maintain an air interface state synchronization when the terminal is in an RRC connected state. As shown in FIG. 2, the method includes the following steps:

Step 201: When the terminal is in the RRC connection state, if the terminal detects the uplink out-of-synchronization of the terminal, and the terminal does not generate RLF, and the terminal does not receive the resource scheduling signaling sent by the base station, and the terminal does not exist, it needs to be sent to the base station. The data to be transmitted, and the terminal obtains the access layer context identifier AS context ID sent by the base station, and the terminal converts its own state from the RRC connected state to the inactive state.

The AS context ID is allocated by the base station and is used to identify the terminal AS context stored in the base station.

Specifically, the step 201 is implemented by: the terminal first detecting whether the uplink of the terminal is out of synchronization, and whether the terminal generates RLF, and whether the terminal receives the resource scheduling signaling sent by the base station, and whether the terminal needs to be sent to The data to be transmitted by the base station, and whether the terminal receives the AS context ID sent by the base station; when the uplink desynchronization of the terminal is detected, and the terminal does not generate RLF, and the terminal does not receive the resource scheduling signaling sent by the base station, and the terminal There is no data to be transmitted to be sent to the base station, and the terminal obtains the AS context ID sent by the base station, and the terminal converts its own state to the inactive state.

Step 202: When the terminal is in the RRC connected state, if the base station detects the uplink out-of-synchronization of the terminal, and the RLF does not occur in the terminal, and the base station does not send the resource scheduling signaling to the terminal, and the terminal does not have to be sent to the base station. The data is transmitted, and the base station stores the AS context of the terminal, and the base station sends the AS context ID to the terminal, and the base station changes the state of the terminal from the RRC connection state to the inactive state.

The AS context ID is used to identify the terminal AS context stored in the base station.

Specifically, the step 202 is implemented by: the base station first detecting whether the uplink of the terminal is out of synchronization, and whether the terminal has a radio link failure RLF, and whether the base station sends resource scheduling signaling to the terminal, and whether the terminal exists. Whether the data to be transmitted is sent to the base station, and whether the base station stores the AS context of the terminal, and whether the base station sends the AS context ID to the terminal; when the uplink desynchronization of the terminal is detected, and the terminal does not generate RLF, and the base station does not have The resource scheduling signaling is sent to the terminal, and the terminal does not have the data to be transmitted to be sent to the base station, and the base station stores the AS context of the terminal, and the base station sends the AS context ID to the terminal, and the base station converts the state of the terminal to the inactive state.

It should be noted that there is no logical sequence between the step 201 implemented by the terminal and the step 202 implemented by the base station, that is, the terminal can implement step 202 while the terminal implements step 201.

It should be noted that the method for maintaining the air interface state synchronization provided in this embodiment is applicable to the problem described in the similar scenario 1 and scenario 2 that occurs in the 5G system mechanism, that is, the RRC state in the 5G system mechanism is on the terminal side and the base station side. The problem is that the status is out of sync.

The method for maintaining the air interface state synchronization provided by the embodiment of the present invention, when the terminal is in the RRC connection state, if the terminal detects the uplink out of synchronization of the terminal, and the terminal does not generate RLF, and the terminal does not receive the resource scheduling signaling sent by the base station. And the terminal does not have the data to be transmitted to be sent to the base station, and the terminal obtains the AS context ID sent by the base station, and the terminal converts its own state into an inactive state; if the base station detects the uplink out of synchronization of the terminal, and the terminal does not have The RLF is generated, and the base station does not send the resource scheduling signaling to the terminal, and the terminal does not have the data to be transmitted to be sent to the base station, and the base station stores the AS context of the terminal, and the base station sends the AS context ID to the terminal, and the base station will The state is converted to the inactive state. In this way, the terminal and the base station convert the state of the terminal from the RRC connection state to the inactive state, thereby achieving the purpose of maintaining state synchronization between the terminal and the base station in a specific case.

The embodiment of the present invention provides a schematic flowchart 3 of a method for maintaining the state of the air interface state. The method is used to describe how the terminal and the base station maintain the air interface state synchronization when the terminal is in the RRC connection state. As shown in FIG. 3, the method includes the following steps:

Step 301: When the terminal is in the RRC connected state, if the terminal detects that the terminal has an RLF caused by the uplink out-of-synchronization, and the terminal does not receive the resource scheduling signaling sent by the base station, and the terminal does not have to send to the base station. The data is transmitted, and the terminal obtains the AS context ID sent by the base station, and the terminal changes its state from the RRC connection state to the inactive state.

Specifically, the step 301 can be implemented in the following manner: the terminal first detects whether the terminal has an RLF caused by uplink out-of-synchronization, and whether the terminal receives the resource scheduling signaling sent by the base station, and whether the terminal needs to be sent to the base station. Data to be transmitted, and whether the terminal receives the AS context ID sent by the base station; detecting the RLF caused by the uplink out-of-synchronization of the terminal, and the terminal does not receive the resource scheduling signaling sent by the base station, and the terminal does not exist to be sent. The data to be transmitted to the base station, and the terminal obtains the AS context ID sent by the base station, and the terminal converts its own state into an inactive state.

Step 302: When the terminal is in the RRC connected state, if the base station detects that the terminal has an RLF caused by the uplink out-of-synchronization, and the base station does not send the resource scheduling signaling to the terminal, and the terminal does not have the data to be transmitted that needs to be sent to the base station. The base station stores the AS context of the terminal, and the base station sends the AS context ID to the terminal, and the base station changes the state of the terminal from the RRC connection state to the inactive state.

Specifically, the step 302 is implemented by: the base station first detecting whether the terminal has an RLF caused by uplink out-of-synchronization, whether the base station sends resource scheduling signaling to the terminal, and whether the terminal has data to be transmitted to be sent to the base station. Whether the base station stores the AS context of the terminal, and whether the base station sends the AS context ID to the terminal; the RLF is detected by the terminal due to the uplink out-of-synchronization, and the base station does not send the resource scheduling signaling to the terminal, and the terminal does not There is a data to be transmitted to be sent to the base station, and the base station stores the AS context of the terminal, and the base station sends an AS context ID to the terminal, and the base station converts the state of the terminal into an inactive state.

It should be noted that there is no logical sequence between the step 301 implemented by the terminal and the step 302 implemented by the base station, that is, the terminal may implement step 302 while the terminal implements step 301.

It should be noted that the method for maintaining the state of the air interface state provided by this embodiment can also be used to solve the problems described in the scenario 1 and scenario 2 that appear in the 5G system mechanism.

The method for maintaining the air interface state synchronization provided by the embodiment of the present invention, when the terminal is in the RRC connected state, if the terminal detects that the terminal has an RLF caused by the uplink out-of-synchronization, and the terminal does not receive the resource scheduling signaling sent by the base station, The terminal does not have the data to be transmitted to be sent to the base station, and the terminal obtains the AS context ID sent by the base station, and the terminal converts its own state to the inactive state; if the base station detects the uplink out of synchronization of the terminal, and the terminal does not generate RLF And the base station does not send the resource scheduling signaling to the terminal, and the terminal does not have the data to be transmitted to be sent to the base station, and the base station stores the AS context of the terminal, and the base station sends the AS context ID to the terminal, and the base station converts the state of the terminal. In the inactive state, the terminal and the base station simultaneously convert the state of the terminal from the RRC connection state to the inactive state, thereby achieving the purpose of maintaining state synchronization between the terminal and the base station in a specific case.

An embodiment of the present invention provides a schematic flowchart of a method for maintaining an air interface state synchronization. As shown in FIG. 4, the method is used to describe how a terminal and a base station maintain air interface state synchronization when the terminal is in an RRC connected state. The method includes the following steps:

Step 401: When the terminal is in the RRC connected state, if the terminal detects that the first timer is started or restarted when data is sent and received by the terminal, and the timing of the first timer exceeds the first timing, and the terminal obtains the base station The AS context ID is sent, and the terminal changes its state from the RRC connection state to the inactive state.

The AS context ID is allocated by the base station, and is used to identify the terminal AS context stored in the base station; the first timing value is the maximum timing duration of the first timer, and the first timing value is configured by the base station for the terminal in advance; The occurrence of data transmission and reception includes the terminal receiving an uplink or downlink resource scheduling instruction allocated by the base station.

Specifically, the detecting process of starting or restarting the first timer when the terminal sends and receives data, and the detecting process of the first timer exceeds the first timing value comprises: the terminal first detecting whether the terminal generates and receives data, and detecting that the terminal occurs When the data is sent or received, the first timer is started, and then the terminal is continuously detected whether the data is transmitted and received again. If the terminal does not detect that the data is transmitted and received again, and the timing of the first timer exceeds the first timing, the detection process ends. It is detected that the terminal re-transmits the data, restarts the first timer, and then continuously detects whether the terminal has another data transmission and reception, until no data transmission and reception of the terminal is detected and the timing of the first timer exceeds the first timing value. The detection process ends.

Step 402: When the terminal is in the RRC connection state, if the base station detects that the fourth timer is started or restarted when data is transmitted and received by the terminal, and the timing of the fourth timer exceeds the fourth timing value, and the base station stores the terminal. The AS context, and the base station sends an AS context ID to the terminal, and the base station changes the state of the terminal from the RRC connected state to the inactive state.

The AS context ID is used to identify the terminal AS context stored in the base station; the data transmission and reception by the terminal includes the base station assigning an uplink or downlink resource scheduling instruction to the terminal.

Specifically, when the terminal generates and receives data, the fourth timer is started or restarted, and the detecting process of the fourth timer exceeds the fourth timing value, the base station first detects whether the terminal generates data transmission and reception, and detects that the terminal occurs. When the data is transmitted and received, the fourth timer is started, and then the terminal is continuously detected whether the data is transmitted and received again. If the terminal does not detect that the data is transmitted and received again, and the timing of the fourth timer exceeds the fourth timing, the detection process ends. It is detected that the terminal re-transmits the data, restarts the fourth timer, and then continuously detects whether data transmission and reception occurs again, until no data transmission and reception of the terminal is detected and the timing of the fourth timer exceeds the fourth timing value, and the detection is performed. The process ends.

Further, the setting of the first timing value and the setting of the fourth timing value are equal or there is a certain error, so that the terminal and the base station can convert the state of the terminal from the RRC connected state to the inactive state simultaneously or within a certain time error.

It should be noted that there is no logical sequence between the step 401 implemented by the terminal and the step 402 implemented by the base station, that is, the terminal can implement step 402 while the terminal implements step 401. Even if the terminal and the base station may be out of synchronization between the RRC connection state and the inactive state, the party that does not enter the inactive state enters the inactive state over time (that is, after the preset value is exceeded), thereby realizing the state between the terminal and the base station. The purpose of synchronization.

It should be noted that the method for maintaining the state of the air interface state provided by this embodiment can also be used to solve the problems described in the scenario 1 and scenario 2 that appear in the 5G system mechanism. For the problem described in the scenario 1 and the scenario 2, the method for keeping the state of the terminal and the base station synchronized is basically the same as the method provided by the embodiment corresponding to FIG. 4, but in the embodiment corresponding to FIG. 4, the terminal and the base station are The state of the terminal is changed from the RRC connection state to the inactive state, and in the process of implementing the state synchronization between the terminal and the base station in scenario 1 and scenario 2, the terminal and the base station change the state of the terminal from the RRC connection state to the light connected state.

The method for maintaining the air interface state synchronization provided by the embodiment of the present invention, when the terminal is in the RRC connection state, if the terminal detects that the terminal generates data transmission and reception, the first timer is started or restarted, and the time duration of the first timer exceeds the a certain time value, and the terminal obtains the AS context ID sent by the base station, and the terminal converts its own state into an idle state; if the base station detects that the fourth timer is started or restarted when the terminal transmits and receives data, and the fourth timer The chronograph duration exceeds the fourth timing value, and the base station stores the AS context of the terminal, and the base station sends the AS context ID to the terminal, and the base station converts the state of the terminal into the idle state; thus, the terminal and the base station together state the state of the terminal from the RRC. The connection state is converted to the inactive state, so that the state synchronization can still be maintained between the terminal and the base station in a specific case.

The embodiment of the present invention provides a schematic flowchart of a method for maintaining the state of the air interface state. As shown in FIG. 5, the method is used to describe how the terminal and the base station maintain the air interface state synchronization when the terminal is in the inactive state. The method includes the following steps:

Step 501: When the terminal is in the inactive state, if the terminal detects that the terminal has RLF and the terminal fails to reselect other cells, the terminal changes its state from the inactive state to the idle state.

Specifically, the step 501 can be implemented in the following manner: the terminal first detects whether the terminal has an RLF; and the terminal reselects whether the other cell fails; when detecting that the terminal has RLF, and the terminal fails to reselect other cells, the terminal sets its own state. Convert to idle state.

It should be noted that other cells are cells other than the cell where the terminal is currently located.

Step 502: When the terminal is in the inactive state, if the base station detects that the terminal has RLF, the base station changes the state of the terminal from the inactive state to the idle state.

Specifically, the step 502 may include: the base station first detecting whether the terminal has an RLF; and detecting that the RLF occurs in the terminal, the base station converts the state of the terminal to an idle state.

It should be noted that there is no logical sequence between the step 501 implemented by the terminal and the step 502 implemented by the base station, that is, the terminal can implement step 502 while the terminal implements step 501.

Further, the method for maintaining the air interface state synchronization provided in this embodiment further includes: the terminal stores its own AS context, and the base station stores the AS context of the terminal. After the terminal converts its own state to the idle state, it saves its own AS context. This allows the terminal to support the RRC recovery process to reestablish the RRC connection. The base station saves the AS context of the terminal after converting the state of the terminal to the idle state. The base station is subsequently supported to use the RRC recovery procedure to reestablish the RRC connection.

It should be noted that the method for maintaining the air interface state synchronization provided in this embodiment may be used to solve the problem described in the type scenarios 4 to 6 in the 5G system mechanism, that is, the RRC state in the 5G system mechanism is on the terminal side and the base station side state. The problem is not synchronized.

The method for maintaining the air interface state synchronization provided by the embodiment of the present invention, when the terminal is in the inactive state, if the terminal detects that the RLF has occurred and the other cell fails to be reselected, the terminal converts its own state to the idle state; if the base station detects The RLF occurs on the terminal, and the base station converts the state of the terminal to the idle state. In this way, the terminal and the base station convert the state of the terminal from the inactive state to the idle state, thereby achieving the purpose of maintaining state synchronization between the terminal and the base station in a specific situation. .

An embodiment of the present invention provides a schematic flowchart of a method for maintaining an air interface state synchronization. As shown in FIG. 6 , the method is used to describe how a terminal and a base station maintain an air interface state synchronization when the terminal is in an inactive state. The method includes the following steps:

Step 601: When the terminal is in the inactive state, if the terminal detects that the second timer is started or restarted when the terminal uplink transmission fails or the downlink transmission fails, and the timing of the second timer exceeds the second timing value, the terminal will The state of the self transitions from the inactive state to the idle state; wherein the fifth timer stops timing when the terminal uplink transmission succeeds or the downlink transmission succeeds.

The second timing value is a maximum timing duration of the second timer, and the second timing value is configured by the base station for the terminal in advance.

Specifically, the step 601 can be implemented in the following manner: the terminal first detects the uplink transmission of the terminal, and the downlink transmission fails. If the terminal uplink transmission fails or the downlink transmission fails, the terminal starts to detect that the uplink transmission fails or the downlink transmission fails. The second timer is timed. When the timing of the second timer is within the second timing value and it is detected that the terminal uplink transmission is successful or the downlink transmission is successful, the second timer stops counting, and when the terminal detects the terminal uplink transmission failure or downlink again The transmission fails, and the fifth timer is restarted at the time when the terminal uplink transmission failure or the downlink transmission failure is detected again, until the timing of the fifth timer can exceed the fifth timing value, and the terminal converts its own state into the idle state.

Specifically, if the terminal detects that the terminal reselects other cells, the second timer continues to time.

Step 602: When the terminal is in the inactive state, if the base station detects that the fifth timer is started or restarted when the terminal uplink transmission fails or the downlink transmission fails, and the time duration of the fifth timer exceeds the fifth timing value, the base station will The state of the terminal is changed from the inactive state to the idle state. The fifth timer stops timing when the base station detects that the terminal uplink transmission succeeds or the downlink transmission succeeds.

Specifically, the step 602 can be implemented in the following manner: the base station first detects the uplink transmission of the terminal, and the downlink transmission fails. If the uplink transmission failure or the downlink transmission failure of the terminal is detected, the terminal starts to detect the uplink transmission failure or the downlink transmission fails. The fifth timer is timed. When the timing of the fifth timer is within the fifth timing value and the terminal uplink transmission is successful or the downlink transmission is successful, the fifth timer stops counting, and when the base station detects the terminal uplink transmission failure or downlink again. The transmission fails, and the fifth timer is restarted when the terminal uplink transmission failure or the downlink transmission fails is detected again, until the timing of the fifth timer can exceed the fifth timing value, and the base station converts the state of the terminal from the inactive state to Idle state.

It should be noted that there is no logical sequence between the step 601 implemented by the terminal and the step 602 implemented by the base station, that is, the terminal can implement step 602 while the terminal implements step 601.

It should be noted that, by using the method for maintaining air interface state synchronization provided by the embodiment of the present invention, when the terminal and the base station detect continuous uplink transmission failure or downlink transmission failure, the second timing value and the fifth timing value may be set earlier. The ground is converted to the idle state together without waiting for the RLF to occur.

Further, the setting of the second timing value and the setting of the fifth timing value are equal or there is a certain error, so that the terminal and the base station can convert the state of the terminal from the inactive state to the idle state simultaneously or within a certain time error.

Further, the method for maintaining the air interface state synchronization provided in this embodiment further includes, after step 601, the AS context of the terminal storage terminal, and further includes, after step 602, the AS context of the base station storage terminal.

It should be noted that the method for maintaining air interface state synchronization provided by this embodiment can be used to solve the problems described in type scenarios 4-6 occurring in the 5G system mechanism.

The method for maintaining the air interface state synchronization provided by the embodiment of the present invention, when the terminal is in the inactive state, if the terminal detects that the terminal uplink transmission fails or the downlink transmission fails, the second timer is started or restarted, and the second timer is If the timing exceeds the second timing, the terminal converts its own state to the idle state; if the base station detects that the uplink transmission fails or the downlink transmission fails, the base station starts or restarts the fifth timer, and the fifth timer is timed. When the fifth timing value is exceeded, the base station converts the state of the terminal to the idle state. In this way, the terminal and the base station convert the state of the terminal from the inactive state to the idle state, so that the state and the base station can still maintain state synchronization in a specific case. purpose.

The embodiment of the present invention provides a schematic flowchart of a method for maintaining the state of the air interface state synchronization. As shown in FIG. 7 , the method is used to describe how the terminal and the base station maintain the air interface state synchronization when the terminal is in the inactive state. The method includes the following steps:

Step 701: When the terminal is in the inactive state, if the terminal detects that the third timer is started or restarted when data is transmitted and received by the terminal, and the timing of the third timer exceeds the third timing value, the terminal sets its own state. The inactive state is converted to the idle state.

The third timing value is the maximum timing duration of the third timer, and the third timing value is configured by the base station for the terminal in advance; the data transmission and reception by the terminal includes the terminal receiving the uplink or downlink resource scheduling instruction allocated by the base station.

Specifically, the step 701 can be implemented in the following manner: the terminal first detects whether the terminal generates and receives data, and starts the third timer at the time when the terminal detects the data transmission and reception, and then continuously detects whether the terminal retransmits the data, if not detected. After the data is sent and received again to the terminal, and the timing of the third timer exceeds the third timing value, the terminal converts its own state into an idle state. If it detects that the terminal again receives data transmission and reception, restarts the third timer, and then restarts. The terminal continuously detects whether the data transmission and reception occurs again until the terminal does not detect that the data transmission and reception occurs, and the timing of the third timer exceeds the third timing value, and the terminal converts its own state into the idle state.

Step 702: When the terminal is in the inactive state, if the base station detects that the sixth timer is started or restarted when data is transmitted and received by the terminal, and the timing of the sixth timer exceeds the sixth timing value, the base station changes the state of the terminal from The inactive state is converted to the idle state.

The data transmission and reception by the terminal includes the base station allocating an uplink or downlink resource scheduling instruction to the terminal.

Specifically, the step 702 can be implemented by: the base station first detecting whether the terminal has data transmission and reception, and starting the sixth timer at the time when the terminal detects the data transmission and reception, and then continuously detecting whether the terminal retransmits the data, if not detected. After the data is sent and received again to the terminal, and the timing of the sixth timer exceeds the sixth timing value, the base station converts the state of the terminal to the idle state. If the terminal detects that the data is transmitted and received again, the sixth timer is restarted, and then Continuously detecting whether data transmission and reception occurs again, until the terminal does not detect data transmission and reception and the timing of the sixth timer exceeds the sixth timing value, the base station converts the state of the terminal into an idle state.

It should be noted that there is no logical sequence between the step 701 implemented by the terminal and the step 702 implemented by the base station, that is, the terminal may implement step 702 while the terminal implements step 701.

Further, the setting of the third timing value and the setting of the sixth timing value are equal or there is a certain error, so that the terminal and the base station can convert the state of the terminal from the inactive state to the idle state simultaneously or within a certain time error.

Further, the method for maintaining the air interface state synchronization provided by the embodiment further includes: the AS context of the terminal storage terminal, and the AS context of the base station storage terminal.

The method for maintaining the air interface state synchronization provided by the embodiment of the present invention, when the terminal is in the inactive state, if the terminal detects that the third timer is started or restarted when data is transmitted and received by the terminal, and the timing of the third timer exceeds the At the third timing, the terminal converts its own state into an idle state; if the base station detects that the sixth timer is started or restarted when data is transmitted and received by the terminal, and the timing of the sixth timer exceeds the sixth timing value, the base station will terminate the terminal. The state is converted to the idle state; thus, the terminal and the base station convert the state of the terminal from the inactive state to the idle state, thereby achieving the purpose of maintaining state synchronization between the terminal and the base station in a specific case.

The embodiment of the invention provides a terminal. As shown in FIG. 8, the terminal 8 includes:

The first processing unit 81 is configured to: when the terminal is in the RRC connection state, if it detects that the terminal meets the first preset condition, the state of the terminal is changed from the RRC connection state to the inactive state; wherein the first preset condition is the first The processing unit must satisfy the condition that the state of the terminal is changed from the RRC connected state to the inactive state.

The second processing unit 82 is configured to: when the terminal is in the inactive state, if the terminal is found to satisfy the second preset condition, the state of the terminal is changed from the inactive state to the idle state; wherein the second preset condition is the second processing unit The condition that must be met to convert the state of the terminal from the inactive state to the idle state.

Further, the first preset condition includes: an uplink out-of-synchronization of the terminal, and the terminal does not generate the RLF, and the terminal does not receive the resource scheduling signaling sent by the base station, and the terminal does not have the data to be transmitted that needs to be sent to the base station, The terminal obtains the access layer context identifier AS context ID sent by the base station, where the AS context ID is allocated by the base station, and is used to identify the terminal access layer context AS context stored in the base station.

The first preset condition further includes: the RLF caused by the uplink out-of-synchronization of the terminal, and the terminal does not receive the resource scheduling signaling sent by the base station, and the terminal does not have the data to be transmitted that needs to be sent to the base station, and the terminal obtains The AS context ID sent by the base station; where the AS context ID is allocated by the base station and used to identify the terminal AS context stored in the base station.

The first preset condition further includes: starting or restarting the first timer when the terminal sends and receives data, and the timing of the first timer exceeds the first timing value, and the terminal obtains the AS context ID sent by the base station; The AS context ID is allocated by the base station, and is used to identify the terminal AS context stored in the base station; the first timing value is the maximum timing duration of the first timer, and the first timing value is configured by the base station for the terminal in advance; the terminal occurs Data transceiving includes receiving, by the terminal, an uplink or downlink resource scheduling instruction allocated by the base station.

Further, the second preset condition includes: the terminal generates RLF, and the terminal fails to reselect other cells; wherein, the other cells are cells other than the cell where the terminal is currently located.

The second preset condition further includes: starting or restarting the second timer timing when the terminal uplink transmission fails or the downlink transmission fails, and the timing duration of the second timer exceeds the second timing value; wherein the second timer is at the terminal When the uplink transmission succeeds or the downlink transmission succeeds, the timing is stopped; the second timing value is the maximum timing duration of the second timer, and the second timing value is configured by the base station for the terminal in advance.

The second preset condition further includes: starting or restarting the third timer timing when the terminal transmits and receives data, and the timing duration of the third timer exceeds the third timing value; wherein the third timing value is the third timer The maximum timing is long, and the third timing value is configured by the base station in advance for the terminal; the data transmission and reception by the terminal includes the terminal receiving the uplink or downlink resource scheduling instruction allocated by the base station.

Further, on the basis of the corresponding embodiment of FIG. 8, as shown in FIG. 9, the terminal 8 provided by the embodiment of the present invention further includes:

The first storage unit 83 is configured to store the AS context of the terminal.

An embodiment of the present invention provides a base station. As shown in FIG. 10, the base station 9 includes:

The third processing unit 91 is configured to: when the terminal is in the RRC connected state, if it detects that the terminal and the base station meet the third preset condition, the state of the terminal is changed from the RRC connected state to the inactive state; wherein the third preset condition is The third processing unit is a condition that must be satisfied to convert the state of the terminal from the RRC connected state to the inactive state.

The fourth processing unit 92 is configured to: when the terminal is in the inactive state, if the terminal is found to satisfy the fourth preset condition, the state of the terminal is changed from the inactive state to the idle state; wherein the fourth preset condition is the fourth processing unit. The condition that must be met to convert the state of the terminal from the inactive state to the idle state.

Further, the third preset condition includes: the uplink desynchronization of the terminal, and the RLF does not occur in the terminal, and the base station does not send the resource scheduling signaling to the terminal, and the terminal does not have the data to be transmitted that needs to be sent to the base station, and the base station The AS context of the terminal is stored, and the base station sends an AS context ID to the terminal. The AS context ID is used to identify the terminal AS context stored in the base station.

The third preset condition further includes: the RLF generated by the terminal due to the uplink out-of-synchronization, and the base station does not send the resource scheduling signaling to the terminal, and the terminal does not have the data to be transmitted that needs to be sent to the base station, and the base station stores the terminal. The AS context, and the base station sends an AS context ID to the terminal. The AS context ID is used to identify the terminal AS context stored in the base station.

The third preset condition further includes: starting or restarting the fourth timer timing when the terminal performs data transmission and reception, and the timing duration of the fourth timer exceeds the fourth timing value, and the base station stores the AS context of the terminal, and the base station The AS sends the AS context ID. The AS context ID is used to identify the terminal AS context stored in the base station. The data transmission and reception of the terminal includes the base station assigning uplink or downlink resource scheduling commands to the terminal.

Further, the fourth preset condition includes: the terminal generates an RLF.

The fourth preset condition further includes: starting or restarting the fifth timer timing when the terminal uplink transmission fails or the downlink transmission fails, and the timing duration of the fifth timer exceeds a fifth timing value; wherein the fifth timer is at the base station The timing is stopped when the uplink transmission of the terminal is successful or the downlink transmission is successful.

The fourth preset condition further includes: starting or restarting the sixth timer when the terminal sends and receives data, and the timing of the sixth timer exceeds a sixth timing value; wherein the data transmission and reception by the terminal includes the base station allocating the uplink for the terminal Or downlink resource scheduling instructions.

Further, on the basis of the corresponding embodiment of FIG. 10, as shown in FIG. 11, the base station 9 provided by the embodiment of the present invention further includes:

The second storage unit 93 is configured to store the AS context of the terminal.

When the terminal is in the RRC connection state, if the terminal detects that the terminal meets the first preset condition, the terminal changes its state from the RRC connection state to the inactive state; if the base station detects itself and the terminal, The third preset condition is met, the base station changes the state of the terminal from the RRC connection state to the inactive state; when the terminal is in the inactive state, if the terminal detects that the terminal meets the second preset condition, the terminal converts its state from the inactive state to the inactive state. In the idle state, if the base station detects that the terminal meets the fourth preset condition, the base station converts the state of the terminal from the inactive state to the idle state; thus, the terminal and the base station convert the state of the terminal from the RRC connection state to the inactive state, or from the inactive state. The state is converted to the idle state, so that the state synchronization can still be maintained between the terminal and the base station in a specific case.

In practical applications, the first processing unit 81, the second processing unit 82, the first storage unit 83, the third processing unit 91, the fourth processing unit 92, and the second storage unit 93 may all be processed by the central processing located in the device. (Central Processing Unit (CPU), Micro Processor Unit (MPU), Digital Signal Processor (DSP) or Field Programmable Gate Array (FPGA).

Those skilled in the art will appreciate that embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention can take the form of a hardware embodiment, a software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) including computer usable program code.

The embodiment of the present invention further provides an electronic device, such as a terminal and a base station; and a hardware structure diagram of the electronic device. As shown in FIG. 12, the electronic device 110 includes: at least one processor 111, a memory 112, and at least one network interface. 114. The various components in electronic device 110 are coupled together by a bus system 115. It will be appreciated that the bus system 115 is used to implement connection communication between these components. The bus system 115 includes a power bus, a control bus, and a status signal bus in addition to the data bus. However, for clarity of description, various buses are labeled as bus system 115 in FIG.

It will be appreciated that the memory 112 can be either volatile memory or non-volatile memory, and can include both volatile and nonvolatile memory. The non-volatile memory may be a ROM, a Programmable Read-Only Memory (PROM), an Erasable Programmable Read-Only Memory (EPROM), or an electrically erasable device. EEPROM (Electrically Erasable Programmable Read-Only Memory), Ferromagnetic random access memory (FRAM), Flash Memory, Magnetic Surface Memory, Optical Disk, or Read Only Disc (CD) -ROM, Compact Disc Read-Only Memory); the magnetic surface memory may be a disk storage or a tape storage. The volatile memory can be a random access memory (RAM) that acts as an external cache. By way of example and not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access (SSRAM). DRAM (Dynamic Random Access Memory), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), enhancement Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), Synchronous Dynamic Random Access Memory (SLDRAM), Direct Memory Bus Random Access Memory (DRRAM) ). The memory 112 described in the embodiments of the present invention is intended to include, but is not limited to, these and any other suitable types of memory.

The memory 112 in the embodiment of the present invention is used to store various types of data to support the operation of the electronic device 110. Examples of such data include any computer program, such as application 1122, for operating on electronic device 110. A program implementing the method of the embodiment of the present invention may be included in the application 1122.

The method disclosed in the foregoing embodiments of the present invention may be applied to the processor 111 or implemented by the processor 111. The processor 111 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 111 or an instruction in a form of software. The processor 111 described above may be a general purpose processor, a digital signal processor (DSP), or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or the like. The processor 111 can implement or perform the various methods, steps, and logic blocks disclosed in the embodiments of the present invention. A general purpose processor can be a microprocessor or any conventional processor or the like. The steps of the method disclosed in the embodiment of the present invention may be directly implemented as a hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor. The software module can reside in a storage medium located in memory 112, and processor 111 reads the information in memory 112 and, in conjunction with its hardware, performs the steps of the foregoing method.

In an exemplary embodiment, the electronic device 110 may be configured by one or more Application Specific Integrated Circuits (ASICs), DSPs, Programmable Logic Devices (PLDs), and Complex Programmable Logic Devices (CPLDs). , Complex Programmable Logic Device), FPGA, general purpose processor, controller, MCU, MPU, or other electronic component implementation for performing the aforementioned methods.

The present invention has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (system), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG. These computer programs can be provided to signal to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for signaling by a processor of a computer or other programmable data processing device. Means are provided for implementing the functions specified in one or more of the flow or in one or more blocks of the flow chart.

The computer program signaling can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that signaling stored in the computer readable memory produces an article of manufacture including the signaling device. The signaling device implements the functions specified in one or more blocks of a flow or a flow and/or a block diagram of the flowchart.

These computer program signaling can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device The signaling provides steps for implementing the functions specified in one or more blocks of a flow or a flow and/or a block diagram of a block diagram.

The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention.

Industrial applicability

In the embodiment of the present invention, when the terminal is in the RRC connection state, if the terminal detects that the terminal meets the first preset condition, the terminal converts its state from the RRC connection state to the inactive state; The first preset condition is a condition that the terminal must satisfy when the terminal changes its state from the RRC connection state to the inactive state; when the terminal is in the inactive state, if the terminal detects that the user satisfies the a second preset condition, the terminal converts its own state from the inactive state to an idle state; wherein the second preset condition is that the terminal converts its state from the inactive state to the idle state The conditions that the state must satisfy. When the terminal is in the RRC connection state, if the base station where the terminal is located detects that the terminal and the terminal meet the third preset condition, the base station converts the state of the terminal from the RRC connection state to the inactive state; The third preset condition is a condition that the base station must satisfy when the state of the terminal is changed from the RRC connection state to the inactive state; when the terminal is in the inactive state, if the base station detects the The terminal satisfies the fourth preset condition, and the base station converts the state of the terminal from the inactive state to the idle state; wherein the fourth preset condition is that the base station changes the state of the terminal from the The condition that the inactive state must be converted to the idle state. In this way, state synchronization can still be maintained between the terminal and the base station in a specific case.

Claims

A method of maintaining air interface state synchronization, the method comprising:

When the terminal is in the radio resource control RRC connection state, if the terminal detects that it meets the first preset condition, the terminal converts its state from the RRC connection state to the inactive inactive state; A preset condition is a condition that the terminal must satisfy to convert its state from the RRC connected state to the inactive state;

When the terminal is in the inactive state, if the terminal detects that it meets the second preset condition, the terminal converts its own state from the inactive state to the idle idle state; The second preset condition is a condition that the terminal must satisfy when converting the state of the terminal from the inactive state to the idle state.
The method of claim 1 wherein said first predetermined condition comprises:

The uplink of the terminal is out of synchronization, and the terminal does not have a radio link failure RLF, and the terminal does not receive the resource scheduling signaling sent by the base station, and the terminal does not exist to be sent to the Data of the base station to be transmitted, and the terminal obtains an access layer context identifier AS context ID sent by the base station; where the AS context ID is allocated by the base station, and is used to identify the storage at the base station. Terminal access layer context AS context.
The method of claim 1 wherein said first predetermined condition comprises:

The terminal generates an RLF caused by an uplink out-of-synchronization, and the terminal does not receive the resource scheduling signaling sent by the base station, and the terminal does not have a data to be transmitted that needs to be sent to the base station, and the The terminal obtains the AS context ID sent by the base station, where the AS context ID is allocated by the base station, and is used to identify the terminal AS context stored in the base station.
The method of claim 1 wherein said at a first predetermined condition comprises:

The first timer is started or restarted when the terminal sends and receives data, and the timing of the first timer exceeds a first timing value, and the terminal obtains an AS context ID sent by the base station; The AS context ID is allocated by the base station, and is used to identify a terminal AS context stored in the base station; the first timing value is a maximum timing duration of the first timer, and the first The timing value is configured by the base station in advance for the terminal; the data transmission and reception by the terminal includes the terminal receiving an uplink or downlink resource scheduling instruction allocated by the base station.
The method of claim 1 wherein said second predetermined condition comprises:

The terminal generates RLF, and the terminal fails to reselect other cells; wherein the other cells are cells other than the cell where the terminal is currently located.
The method of claim 1 wherein said second predetermined condition comprises:

Starting or restarting the second timer timing when the terminal uplink transmission fails or the downlink transmission fails, and the timing duration of the second timer exceeds a second timing value; wherein the second timer is at the terminal The timing is stopped when the uplink transmission succeeds or the downlink transmission succeeds; the second timing value is the maximum timing duration of the second timer, and the second timing value is configured by the base station for the terminal in advance.
The method according to claim 6, wherein the second timer continues to count when the terminal reselects other cells; wherein the other cells are cells other than the cell in which the terminal is currently located.
The method of claim 1 wherein said second predetermined condition comprises:

Starting or restarting a third timer timing when data is transmitted and received by the terminal, and a timing duration of the third timer exceeds a third timing value; wherein the third timing value is a maximum timing of the third timer The time length, and the third timing value is configured by the base station in advance for the terminal; the data transmission and reception by the terminal includes the terminal receiving an uplink or downlink resource scheduling instruction allocated by the base station.
The method of claim 1, wherein when the terminal is in the inactive state, the method further comprises:

The terminal stores its own AS context.
A method of maintaining air interface state synchronization, the method comprising:

When the terminal is in the radio resource control RRC connection state, if the base station where the terminal is located detects that the terminal and the terminal meet the third preset condition, the base station converts the state of the terminal from the RRC connection state to the inactive inactive state. The third preset condition is a condition that the base station must satisfy to convert the state of the terminal from the RRC connected state to the inactive state;

When the terminal is in the inactive state, if the base station detects that the terminal meets the fourth preset condition, the base station converts the state of the terminal from the inactive state to the idle idle state; The fourth preset condition is a condition that the base station must satisfy to convert the state of the terminal from the inactive state to the idle state.
The method of claim 10, wherein the third predetermined condition comprises:

The uplink of the terminal is out of synchronization, and the terminal does not generate RLF, and the base station does not send resource scheduling signaling to the terminal, and the terminal does not have data to be transmitted that needs to be sent to the base station, And the base station stores an access layer context AS context of the terminal, and the base station sends an access layer context identifier AS context ID to the terminal, where the AS context ID is used to identify the base station. Stored terminal AS context.
The method of claim 10, wherein the third predetermined condition comprises:

The terminal generates an RLF due to uplink out-of-synchronization, and the base station does not send resource scheduling signaling to the terminal, and the terminal does not have data to be transmitted that needs to be sent to the base station, and the base station An AS context is stored in the terminal, and the base station sends an AS context ID to the terminal. The AS context ID is used to identify a terminal AS context stored in the base station.
The method of claim 10, wherein the third predetermined condition comprises:

Starting or restarting a fourth timer timing when data is transmitted and received by the terminal, and a timing duration of the fourth timer exceeds a fourth timing value, and the base station stores an AS context of the terminal, and the The base station sends an AS context ID to the terminal, where the AS context ID is used to identify the terminal AS context stored in the base station; the data transmission and reception of the terminal includes the base station allocating uplink or downlink resources to the terminal. Scheduling instructions.
The method of claim 10, wherein the fourth predetermined condition comprises:

The terminal generates a radio link failure RLF.
The method of claim 10, wherein the fourth predetermined condition comprises:

Starting or restarting a fifth timer timing when the terminal uplink transmission fails or the downlink transmission fails, and the timing duration of the fifth timer exceeds a fifth timing value; wherein the fifth timer is at the base station The timing is stopped when the uplink transmission of the terminal is successful or the downlink transmission is successful.
The method of claim 10, wherein the fourth predetermined condition comprises:

A sixth timer is started or restarted when data is transmitted and received by the terminal, and a timing of the sixth timer exceeds a sixth timing value; wherein the data transmission and reception of the terminal includes the base station being the terminal Allocate uplink or downlink resource scheduling instructions.
The method of claim 10, wherein when the terminal is in the inactive state, the method further comprises:

The base station stores an AS context of the terminal.
A terminal, the terminal comprising:

The first processing unit is configured to: when the terminal is in the RRC connection state, if the terminal is configured to meet the first preset condition, the state of the terminal is changed from the RRC connection state to the inactive inactive state; The first preset condition is a condition that the first processing unit must satisfy to convert the state of the terminal from the RRC connected state to the inactive state;

a second processing unit, configured to: when the terminal is in the inactive state, if it is detected that the terminal meets the second preset condition, the state of the terminal is changed from the inactive state to the idle idle state; The second preset condition is a condition that the second processing unit must satisfy to convert the state of the terminal from the inactive state to the idle state.
The terminal according to claim 18, wherein the first preset condition comprises:

The uplink of the terminal is out of synchronization, and the terminal does not have a radio link failure RLF, and the terminal does not receive the resource scheduling signaling sent by the base station, and the terminal does not exist to be sent to the Data of the base station to be transmitted, and the terminal obtains an access layer context identifier AS context ID sent by the base station; where the AS context ID is allocated by the base station, and is used to identify the storage at the base station. Terminal access layer context AS context.
The terminal according to claim 18, wherein the first preset condition further comprises:

The terminal generates an RLF caused by an uplink out-of-synchronization, and the terminal does not receive the resource scheduling signaling sent by the base station, and the terminal does not have a data to be transmitted that needs to be sent to the base station, and the The terminal obtains the AS context ID sent by the base station, where the AS context ID is allocated by the base station, and is used to identify the terminal AS context stored in the base station.
The terminal according to claim 18, wherein the first preset condition comprises:

The first timer is started or restarted when the terminal sends and receives data, and the timing of the first timer exceeds a first timing value, and the terminal obtains an AS context ID sent by the base station; The AS context ID is allocated by the base station, and is used to identify a terminal AS context stored in the base station; the first timing value is a maximum timing duration of the first timer, and the first The timing value is configured by the base station in advance for the terminal; the data transmission and reception by the terminal includes the terminal receiving an uplink or downlink resource scheduling instruction allocated by the base station.
The terminal according to claim 18, wherein the second preset condition comprises:

The terminal generates RLF, and the terminal fails to reselect other cells; wherein the other cells are cells other than the cell where the terminal is currently located.
The terminal according to claim 18, wherein the second preset condition comprises:

Starting or restarting the second timer timing when the terminal uplink transmission fails or the downlink transmission fails, and the timing duration of the second timer exceeds a second timing value; wherein the second timer is at the terminal The timing is stopped when the uplink transmission succeeds or the downlink transmission succeeds; the second timing value is the maximum timing duration of the second timer, and the second timing value is configured by the base station for the terminal in advance.
The terminal according to claim 18, wherein the second preset condition comprises:

Starting or restarting a third timer timing when data is transmitted and received by the terminal, and a timing duration of the third timer exceeds a third timing value; wherein the third timing value is a maximum timing of the third timer The time length, and the third timing value is configured by the base station in advance for the terminal; the data transmission and reception by the terminal includes the terminal receiving an uplink or downlink resource scheduling instruction allocated by the base station.
The terminal of claim 18, wherein the terminal comprises:

The first storage unit is configured to store an AS context of the terminal.
A base station, the base station comprising:

a third processing unit, configured to: when the terminal is in the RRC connection state, if the terminal and the base station are configured to meet the third preset condition, the state of the terminal is changed from the RRC connection state to the non- Activating an inactive state, where the third preset condition is a condition that the third processing unit must satisfy to convert a state of the terminal from the RRC connected state to an inactive state;

a fourth processing unit, configured to: when the terminal is in the inactive state, if it is detected that the terminal meets the fourth preset condition, the state of the terminal is changed from the inactive state to the idle idle state; The fourth preset condition is a condition that the fourth processing unit must satisfy to convert the state of the terminal from the inactive state to the idle state.
The base station according to claim 26, wherein said third preset condition comprises:

The uplink of the terminal is out of synchronization, and the terminal does not generate RLF, and the base station does not send resource scheduling signaling to the terminal, and the terminal does not have data to be transmitted that needs to be sent to the base station, And the base station stores an access layer context AS context of the terminal, and the base station sends an access layer context identifier AS context ID to the terminal, where the AS context ID is used to identify the base station. Stored terminal AS context.
The base station according to claim 26, wherein said third preset condition comprises:

The terminal generates an RLF due to uplink out-of-synchronization, and the base station does not send resource scheduling signaling to the terminal, and the terminal does not have data to be transmitted that needs to be sent to the base station, and the base station An AS context is stored in the terminal, and the base station sends an AS context ID to the terminal. The AS context ID is used to identify a terminal AS context stored in the base station.
The base station according to claim 26, wherein said third preset condition comprises:

Starting or restarting a fourth timer timing when data is transmitted and received by the terminal, and a timing duration of the fourth timer exceeds a fourth timing value, and the base station stores an AS context of the terminal, and the The base station sends an AS context ID to the terminal, where the AS context ID is used to identify the terminal AS context stored in the base station; the data transmission and reception of the terminal includes the base station allocating uplink or downlink resources to the terminal. Scheduling instructions.
The base station according to claim 26, wherein said fourth preset condition comprises:

The terminal generates a radio link failure RLF.
The base station according to claim 26, wherein said fourth preset condition comprises:

Starting or restarting a fifth timer timing when the terminal uplink transmission fails or the downlink transmission fails, and the timing duration of the fifth timer exceeds a fifth timing value; wherein the fifth timer is at the base station The timing is stopped when the uplink transmission of the terminal is successful or the downlink transmission is successful.
The base station according to claim 26, wherein the fourth preset condition further comprises:

A sixth timer is started or restarted when data is transmitted and received by the terminal, and a timing of the sixth timer exceeds a sixth timing value; wherein the data transmission and reception of the terminal includes the base station being the terminal Allocate uplink or downlink resource scheduling instructions.
The base station according to claim 26, wherein the base station further comprises:

The second storage unit is configured to store the AS context of the terminal.
A terminal comprising: a processor and a memory storing the processor executable instructions, when the instructions are executed by the processor, performing the method of maintaining air interface state synchronization according to any one of claims 1 to 9.
A terminal comprising: a processor and a memory storing the processor-executable instructions, when the instructions are executed by the processor, performing the method of maintaining air interface state synchronization according to any one of claims 10 to 17.
A storage medium storing computer executable instructions for performing the method of maintaining air interface state synchronization according to any one of claims 1 to 9.
A storage medium storing computer executable instructions for performing the method of maintaining air interface state synchronization according to any one of claims 10 to 17.