Detailed Description
The technical scheme provided by the application is further described below by referring to the accompanying drawings and examples. It should be understood that the system structure and the service scenario provided in the embodiments of the present application are mainly for explaining some possible implementations of the technical solutions of the present application, and should not be construed as unique limitations of the technical solutions of the present application. Those skilled in the art can appreciate that, as the system evolves and updated service scenarios appear, the technical solution provided by the present application may still be applicable to the same or similar technical problems.
It should be understood that the technical solution provided by the embodiments of the present application includes a method for reconstructing a wireless link and related devices. In the following description of the specific embodiments, some repetition is not described in detail, but it should be understood that the specific embodiments have mutual references and can be combined with each other.
In a wireless communication system, devices may be classified into devices providing wireless network services and devices using wireless network services. Devices providing wireless network services are those devices that make up a wireless communication network, which may be referred to simply as network devices (network equipment), or network elements. Network devices are typically owned by and are responsible for operation or maintenance by operators (e.g., china mobile and Vodafone) or infrastructure providers (e.g., iron tower companies). The network devices may be further divided into radio access network (radio access network, RAN) devices and Core Network (CN) devices. A typical RAN apparatus includes a Base Station (BS).
It should be appreciated that a base station may also sometimes be referred to as a wireless Access Point (AP), or a transmitting receiving point (transmission reception point, TRP). Specifically, the base station may be a general node B (generation Node B, gNB) in a 5G New Radio (NR) system, an evolved node B (evolutional Node B, eNB) of a 4G long term evolution (long term evolution, LTE) system.
Devices that use wireless network services are typically located at the edge of the network and may be referred to simply as terminals (terminals). The terminal can establish connection with the network device and provide specific wireless communication service for the user based on the service of the network device. It should be appreciated that terminals are sometimes referred to as User Equipment (UE), or Subscriber Units (SU), due to their closer relationship to the user. In addition, terminals tend to move with users, sometimes referred to as Mobile Stations (MSs), relative to base stations that are typically placed at fixed locations. In addition, some network devices, such as a Relay Node (RN) or a wireless router, may be considered terminals because they have UE identities or belong to users.
Specifically, the terminal may be a mobile phone (mobile phone), a tablet computer (tablet computer), a laptop computer (laptop computer), a wearable device (such as a smart watch, a smart bracelet, a smart helmet, smart glasses), and other devices with wireless access capability, such as a smart car, various internet of things (internet of thing, IOT) devices, including various smart home devices (such as smart meters and smart appliances) and smart city devices (such as security or monitoring devices, intelligent road transportation facilities), and the like.
For convenience of description, the technical solution of the embodiment of the present application will be described in detail by taking a base station and a terminal as examples.
Fig. 1 is a schematic structural diagram of a wireless communication system according to an embodiment of the present application. As shown in fig. 1, the wireless communication system includes a terminal and a base station. The transmission link from terminal to base station is denoted as Uplink (UL) and the transmission link from base station to terminal is denoted as Downlink (DL) according to the transmission direction. Similarly, data transmission in the uplink may be abbreviated as uplink data transmission or uplink transmission, and data transmission in the downlink may be abbreviated as downlink data transmission or downlink transmission.
In the wireless communication system, the base station can provide communication coverage for a specific geographic area through an integrated or external antenna device. One or more terminals located within the communication coverage area of the base station may access the base station. One base station may manage one or more cells (cells). Each cell has an identification, also known as a cell identity (CELL IDENTITY, cell ID). From the radio resource point of view, one cell is a combination of downlink radio resources and (optionally) uplink radio resources paired therewith.
It should be appreciated that the wireless communication system may conform to the wireless communication standard of 3GPP, or may conform to other wireless communication standards, such as the 802 family (e.g., 802.11, 802.15, or 802.20) of Institute of Electrical and electronics Engineers (Institute of ELECTRICAL AND Electronics Engineers, IEEE). Although only one base station and one terminal are shown in fig. 1, the wireless communication system may include other numbers of terminals and base stations. The wireless communication system may further comprise other network devices, such as core network devices.
The terminals and base stations should be aware of the predefined configuration of the wireless communication system, including the radio access technologies (radio access technology, RATs) supported by the system, as well as the radio resources specified by the system, such as radio frequency bands and carriers. A carrier is a range of frequencies that meets system specifications. This range of frequencies may be determined by the center frequency of the carrier (denoted carrier frequency) and the bandwidth of the carrier. The predefined configuration of these systems may be determined as part of the standard protocols of the wireless communication system or by the interaction between the terminal and the base station. The content of the standard protocols of the wireless communication system may be pre-stored in memories of the terminal and the base station and/or embodied as hardware circuits or software codes of the terminal and the base station.
In the wireless communication system, the terminal and the base station support one or more same RATs, such as 5g nr,4g LTE, or RATs of future evolution systems. Specifically, the terminal and the base station adopt the same air interface parameters, coding scheme, modulation scheme, and the like, and communicate with each other based on radio resources specified by the system. Wherein the air interface parameter is a parameter for describing characteristics of the air interface. In English, the air interface parameter is sometimes also referred to as numerology. The air interface parameters may include subcarrier spacing (subcarrier spacing, SC) and may also include Cyclic Prefix (CP). The wireless communication system may support a variety of different air interface parameters that may be part of a standard protocol.
Transmissions between the terminal and the base station may follow a wireless protocol defined by the relevant standards organization. Fig. 2 is a schematic diagram of a control plane wireless protocol architecture according to an embodiment of the present application. The radio protocol architecture may correspond to a radio protocol architecture of 3 GPP. The NR radio protocol stack is divided into two planes: a user plane and a control plane. A User Plane (UP) protocol stack is a protocol cluster adopted by User data transmission, and a Control Plane (CP) protocol stack is a protocol cluster adopted by Control signaling transmission of a system. The user plane protocol is mainly responsible for functions related to user data transmission, and the control plane protocol is mainly responsible for functions such as connection establishment, mobility management, security management and the like.
As shown in fig. 2, the radio protocol architecture corresponds to a control plane protocol, and from a lower layer protocol to a higher layer protocol, a protocol stack is formed, and is divided into three layers, namely a first layer (layer 1), a second layer (layer 2) and a third layer (layer 3). The terminal and the base station are respectively provided with entities of each layer of protocol in the wireless protocol architecture, and each layer of protocol entity exchanges (including receiving and transmitting) service data units (SERVICE DATA units, SDUs) with higher layers and exchanges protocol data units (protocol data unit, PDU) with lower layers.
The Layer 1 is also called a physical Layer, and includes a Physical (PHY) Layer protocol, and the control plane protocol stack uses the PHY Layer protocol as a bottom Layer protocol. The PHY protocol may be used to perform encoding/decoding, modulation/demodulation, multi-antenna mapping, mapping of signals to time-frequency resources, and other typical physical layer functions. The PHY protocol provides services of transport channels to higher layer (i.e., layer 2) protocols and is responsible for handling mapping of transport channels to physical channels.
Layer 2 refers to the data link Layer, comprising in order: medium access control (MEDIA ACCESS control, MAC) protocol, radio link control (radio link control, RLC) protocol, packet data convergence protocol (PACKET DATA convergence protocol, PDCP).
The MAC protocol may be used to perform logical channel multiplexing, hybrid automatic repeat request (hybrid automatic repeat request, HARQ), scheduling and scheduling related functions. The MAC protocol provides services of logical channels to higher layer protocols, such as RLC protocol, and is responsible for mapping logical channels to transport channels.
The RLC protocol may be used to perform the packet (segementation) and retransmission processing of RLC data. The RLC protocol may provide services of an RLC channel to an upper layer protocol, such as PDCP protocol. In the terminal, each RLC channel (and each radio bearer) may correspond to one RLC entity. One RLC entity can be configured in three modes, respectively: transparent mode (TRANSPARENT MODE, TM), unacknowledged mode (unacknowledged mode, UM) and acknowledged mode (acknowledged mode, AM). The RLC entity can be classified into a TM RLC entity, a UM RLC entity, and an AM RLC entity according to the configured data transmission mode. In TM mode, only the data transmission function is provided, i.e. only the transmitted content is sent to the destination address, without any change to the data content. In UM mode, the protocol provides all RLC functions except retransmission and re-segmentation, which is an unreliable transport service. The AM mode provides all RLC functions, ensuring reliable transport services through error monitoring and retransmission. For data in AM mode, the RLC layer of the receiving end needs to send an acknowledgement message (acknowlegement, ACK) or a negative acknowledgement message (negative acknowlegement, NACK) to confirm whether the information is received successfully or not, where the messages are carried by status PDUs of the RLC layer entity.
The PDCP protocol may be used to perform internet protocol (internet protocol, IP) header compression, ciphering, and integrity protection functions. In addition, the PDPC protocol can be used for the functions of sequence number (sequence numbering) and sequential delivery (in-order delivery) of PDCP data. The PDCP protocol may provide service of Radio Bearers (RBs) to an upper layer protocol (i.e., layer 3). In the terminal, each RB may correspond to one PDCP entity. The RB is further divided into a signaling radio bearer (SIGNALLING RADIO BEARER, SRB) carrying control plane signaling data and a data radio bearer (data radio bearer, DRB) carrying user plane data.
Layer 3, the network Layer, includes in the control plane protocol: a radio resource control (radio resource control, RRC) protocol and a non-access stratum (NAS) protocol.
The NAS protocol may be used to perform functions such as authentication (authentiacation), mobility management (mobility management), security control (security control), etc.
The RRC protocol may be used to perform system message broadcasting, paging message transmission, RRC connection management, cell selection and reselection, measurement configuration and reporting, etc., through the transmission of control plane signaling. Which is encapsulated at the data link layer as a control plane message containing the corresponding control plane signaling. The control signaling messages of the RRC layer are transmitted using SRBs, of which a plurality are defined in the NR, mainly SRB0, SRB1, SRB2 and SRB3.SRB0 is a default established radio bearer without integrity protection and ciphering processing. SRB1 is used to send RRC messages to indicate the status and changes of the RRC connection, such as air interface node configuration, link switching, etc., and to send NAS messages before SRB2 is established. SRB2 is configured after AS security is activated to send RRC messages containing recorded measurement information, AS well AS NAS messages, which may offload the signaling load of SRB 1. SRB3 is used to carry specific RRC signaling.
Fig. 3 is an operation schematic diagram of protocol entities of each layer of a data link layer under a control plane protocol according to an embodiment of the present application. When the RRC layer delivers control signaling downward, the control signaling is one PDCP SDU with respect to the PDCP layer. The PDCP SDU is ciphered, etc., by the PDCP entity of the corresponding RB, delivered as PDCP PDUs down to the associated RLC entity. The PDCP PDU is an RLC SDU relative to the RLC layer, and the RLC entity performs operations such as segmentation and the like on the PDCP PDU, and finally outputs one or more RLC PDUs. The one or more RLC PDUs are one or more MAC SDUs with respect to the MAC layer. These MAC SDUs are multiplexed into one or more MAC PDUs awaiting transmission opportunities to the base station, according to the transmission limit indicated by the uplink resource. When each layer processes each SDU, an information head is added to indicate relevant parameter information of each layer.
Fig. 4 is a schematic diagram of mapping between different channels of a wireless communication system according to an embodiment of the present application. As shown in fig. 4, channels of the wireless communication system may include logical channels, transport channels, and physical channels. The logical channel is a channel between the RLC layer and the MAC layer, and the transport channel is a channel between the MAC layer and the PHY layer, wu Lixin to a channel on which the PHY layer actually transmits information. Logical channels are mapped to corresponding transport channels, which in turn are mapped to corresponding physical channels.
Logical channels are defined by the type of information carried by the channel and are generally divided into control channels and data channels. The control channel carries control and configuration information required by the operation of the wireless communication system, corresponds to a control plane protocol stack, and the data channel corresponds to a data plane protocol stack and carries user data. In particular, logical channels can include broadcast control channels (broadcast control channel, BCCH), paging control channels (paging control channel, PCCH), common control channels (common control channel, CCCH), dedicated control channels (DEDICATED CONTROL CHANNEL, DCCH), and dedicated data channels (DEDICATED TRAFFIC CHANNEL, DTCH). Wherein SRB0 uses CCCH for transmission and SRB1, SRB2 and SRB3 use DCCH.
The transport channels define the manner and nature of data transmission over the air interface. The data in the transport channel may be multiplexed into one Transport Block (TB) and transmitted within one transmission time interval (transmission TIME INTERVAL, TTI). Transport channels may include broadcast channels (broadcast channel, BCH), paging channels (PAGING CHANNEL, PCH), downlink shared channels (downlink SHARED CHANNEL, DL-SCH), and uplink shared channels (uplink SHARED CHANNEL, UL-SCH). In addition, a Random Access Channel (RACH) is also defined as a transport channel, although it does not carry transport blocks. Among them, SRBs are mostly transmitted through a shared channel (SHARED CHANNEL, SCH).
The physical channel corresponds to a set of time-frequency resources for carrying the control channel, which may refer to the time-frequency resource grid shown in fig. 4. The physical channels may include a physical downlink shared channel (physical downlink SHARED CHANNEL, PDSCH), a physical broadcast channel (physical broadcast channel, PBCH), a physical downlink control channel (physical downlink control channel, PDCCH), a physical uplink shared channel (PUSCH SHARED CHANNEL, PUSCH), a physical uplink control channel (physical uplink control channel, PUCCH). The PDCCH and the PUCCH have no corresponding control channel, and are used for carrying downlink control information (downlink control information, DCI) and uplink control information (uplink control information, UCI), respectively. DCI or UCI provides configuration information required for downlink data transmission and uplink data transmission.
Taking UCI as an example, UCI has a plurality of predefined formats that may contain some given information elements (information element, IE). An information element may be understood as a given field of UCI, the range of values of which, and the meaning of each value, may be predefined by the system. Among the information carried by UCI, there is a type of scheduling request (scheduling request, SR) for requesting access to a base station and uploading data. The precondition that UCI can carry SR is that the base station has configured the terminal side with SR configured PUCCH, which is periodic and dedicated to the terminal. Therefore, the flow of the scheduling request is as follows: the terminal receives SR configuration transmitted by the base station; the terminal sends an SR on the PUCCH to inform the base station that data are to be uploaded; the terminal receives a scheduling indication message, wherein the scheduling indication message carries out downlink transmission through a PDCCH and contains specific authorization information of an uplink resource PUSCH of the base station, and the specific authorization information is used for indicating the resource position, the transmission format, the multi-antenna configuration, the power control and the like of the uplink data transmission; the terminal transmits the message to be sent up; and the terminal receives a hybrid automatic repeat request (HARQ) feedback confirmation message which is used for confirming the successful transmission of the message to be sent. From the above flow, since the SR is configured as the terminal exclusive, the speed of the terminal accessing the base station is increased, so as to quickly obtain the uplink grant resource, and make the uplink transmission very efficient.
Random access is a process in which another terminal requests access to a base station, receives a base station response, and allocates an access channel, and uplink transmission of data is generally performed after the random access is successful. Random access is generally classified into a contention-based random access procedure and a non-contention-based random access procedure, the greatest difference of which is that the allocation of the access preamble of the former is generated by a terminal, thus having more processes of contention and collision resolution than the latter. In the reestablishment process of the wireless link, the random access is a random access flow based on competition.
Fig. 5 is a schematic diagram of a contention-based random access procedure according to an embodiment of the present application. The dashed boxes in the figure represent different operations that the terminal may take, and the dashed lines represent steps that may occur, but are not necessary for a complete random access procedure, as follows:
step 501, the terminal sends a random access preamble, where the random access preamble is used to obtain uplink resource authorization.
Since random access is based on contention access, a base station can receive random access preambles transmitted by a plurality of terminals at the same time, which do not respond to all the received random access preambles. Thus, the terminal starts a backoff window (backoff) and monitors the feedback of the base stations (i.e., the random access response corresponding to the aforementioned random access preamble) within this backoff window, by:
In step 502a, the base station does not feedback or send a random access response error, and the terminal makes a new random access preamble transmission attempt to the base station again until the number of attempts expires or receives a correct random access response.
Step 502b, the terminal receives a correct random access response from the base station, where the random access response carries configuration requirement information of uplink resources and size information of uplink TBs.
Step 503, the terminal transmits a TB, denoted as Msg 3; and the TB size accords with the size information of the uplink TB in the random access response.
Due to network instability, the transmission of Msg 3 may fail, so the terminal takes the following actions according to the base station feedback (i.e. the contention resolution message, which should correspond to Msg 3 described above):
step 504a, the base station does not feedback or the sent contention resolution message is wrong, and the terminal retransmits the Msg 3 based on the configuration mode until the maximum retransmission times; and if the contention resolution message is not received, restarting the random access flow.
Step 504b, the terminal receives a correct contention resolution message from the base station, where the contention resolution message is used to indicate that the Msg 3 is successfully sent, and the random access procedure ends.
In the embodiment of the present application, the Msg 3 refers to an RRC connection reestablishment request, an RRC connection reestablishment complete message, and an RLC response message; since the size of the Msg 3 is specified by the base station, the content of the Msg 3 is the complete content or partial content of the information which needs to be uploaded by the terminal; if the Msg 3 carries part of content, the terminal initiates a new random access flow again after the random access flow is finished, until the information to be transmitted is sent out.
It can be seen that the delay of random access has uncertainty, and if the size of the information content to be uploaded exceeds the limit in the random access response, the terminal needs to start the random access procedure for the second time. Thus, the uplink transmission achieved by random access has the characteristics of time extension, uncertainty and inefficiency.
Fig. 6 is a schematic diagram of an RRC state transition procedure according to an embodiment of the present application. As shown in fig. 6, the terminal and the base station may enter different NR RRC protocol states, including: IDLE state (rrc_idle), CONNECTED state (rrc_connected) and INACTIVE state (rrc_inactive), for reasons that may include mobility changes or service triggers, etc
Taking UE as an example, when the terminal is in NR rrc_idle state, the broadcast message of the located gNB is monitored. When the scene changes, such as registration or service triggering, the terminal establishes a link with the base station, and changes from the NR RRC_IDLE state to the NR RRC_CONNECTED state, and after the connection is released, the terminal can change back to the NR RRC_IDLE state. When the terminal is in the NR RRC_CONNECTED state, the connection is suspended to enter the NR RRC_INACTIVE state due to the fact that the terminal has no service and other scenes temporarily, and the connection is restored to enter the NR RRC_CONNECTED state after the service is triggered. When the terminal is in the NR RRC_INACTIVE state, the connection is released into the NR RRC_IDLE state.
As can be seen from the above description, when the terminal starts traffic communication, the rrc_connected state will be entered. This requires establishing a communication connection of RRC and guaranteeing integrity and confidentiality of communication by configuring Access Stratum (AS) security. AS security includes integrity protection of RRC SRBs, and encryption of SRBs with DRBs carrying data, implemented with security context. The security context is temporary state information established by the network for the terminal, and comprises key information and data bearing information, so that the resource consumption of mutual authentication between the terminal and the network when the terminal is switched between different states is reduced, the terminal can conveniently and quickly enter a connection state, and the terminal can safely communicate. If AS security is not activated, the original RRC connection and associated configuration are deleted and a new RRC connection is established.
In summary, establishing the RRC connection includes establishing SRB1, activation of AS security, and establishing SRB2 and DRB.
When the terminal is in the rrc_connected state, the RRC connection with the base station is not stable. Due to environmental instabilities, such as: the wireless link can fail due to failure of link switching, high probability error code of downlink channel, difficult transmission of uplink channel, inconsistent parameter configuration and security information understanding of terminal and network side, etc. Specific failure causes are: 1) Radio link reconfiguration failure including synchronization failure and configuration error; 2) Failure of cell handover; 3) Other reasons.
At this time, the terminal may search for a cell with a better selection signal to initiate connection recovery, and attempt to recover the radio link again, so that the user data or voice service is not interrupted. The communication process, i.e. the reestablishment of the radio link, restores the user traffic by reestablishing the RRC connection, comprising: restore and update RB configuration and reactivate and update AS security.
Fig. 7 is a schematic flow diagram of a radio link reestablishing method in the prior art, wherein a dashed box represents a random access flow, and the message content of Msg 3 is a message on an arrow in the dashed box. The link reestablishment flow includes the following steps:
Step 701, the terminal initiates a random access procedure for uplink transmission of an RRC connection reestablishment request (Re-establishment Request) message.
The terminal recovers the original RRC configuration and the security context from the stored security context, and recovers the SRB1 of the terminal side. And then sending an RRC connection reestablishment request message to the base station, wherein the RRC connection reestablishment request message is carried by SRB 0. The RRC connection reestablishment request message carries radio link failure reason information and terminal identity information. The radio link failure cause information is used for generating a corresponding RRC connection reestablishment message at the base station side, and the terminal identity information is used for carrying out security context retrieval at the base station side.
The base station recovers the RRC configuration and AS security accordingly, and reconstructs the SRB1 resource at the base station side, thereby providing integrity and encryption protection for the subsequent uplink and downlink messages. And then, the base station transmits an RRC connection reestablishment message to the terminal, recovers the DRB and SRB2 resources at the base station side, and sends an RRC connection reconfiguration message, and the sequence is as described.
Step 702, the terminal receives an RRC connection reestablishment (Re-establishment) message, where information carried by the RRC connection reestablishment message is used to indicate updating of an AS security key; wherein, the AS security key comprises an encryption and decryption key of the PDCP layer.
Since the RRC connection reestablishment message is AM data of the RLC layer, the data link layer of the terminal side needs to feed back an RLC acknowledgement message (ACK), otherwise the base station will retransmit the RRC connection reestablishment message.
In step 703, the terminal starts a complete random access procedure, and is configured to send an RLC acknowledgement message, where the RLC acknowledgement message is used to indicate successful reception of the RRC connection reestablishment message.
Step 704, the terminal starts a complete random access procedure for sending an RRC connection reestablishment complete (Re-establishment Complete) message, where the RRC connection reestablishment complete message is used to confirm successful completion of RRC connection reestablishment;
The RRC connection reestablishment completion message is transmitted on SRB1, integrity and encryption protection are carried out on the PDCP layer, segmentation processing is carried out on the AM RLC entity mapped on the RLC layer, and finally the RRC connection reestablishment completion message is enclosed in the TB after multiplexing of the MAC layer and is transmitted in the uplink direction by the physical layer.
Step 705, the terminal receives an RRC connection Reconfiguration (Reconfiguration) message, where the RRC connection Reconfiguration message carries information for modifying RRC connection configuration, recovering terminal side DRB and SRB2 resources, and SR configuration;
The PDCP layer may decrypt the RRC connection reconfiguration message according to the updated decryption key.
Step 706, the terminal sends a scheduling request to the base station according to the uplink resource information indicated by the SR configuration.
Step 707, the terminal receives a scheduling indication message from the base station, where the scheduling indication message is used to authorize uplink resources.
Step 708, the terminal sends an RRC connection reconfiguration complete (Reconfiguration Complete) message on the authorized uplink resource, where the RRC connection reconfiguration complete message is used to confirm successful completion of the RRC connection reconfiguration.
Thus, the terminal completes the process of reestablishing the RRC radio link. In this flow, after receiving the RRC connection reestablishment request message, the base station transmits an RRC connection reestablishment message to the terminal (step 702) and an RRC connection reconfiguration message sequentially (step 705). RRC connection re-establishment signaling is sent on SRB1 and RRC connection reconfiguration signaling may be sent on SRB1 or SRB 3. The RRC connection re-establishment signaling and RRC connection reconfiguration signaling may be generated in a short time, sequenced as described, and delivered to the lower layer with reference to the configuration and algorithms of the different base stations. Depending on the type of RB, both signaling needs integrity and ciphering protection, and therefore ciphering is performed in the PDCP layer, and is encapsulated by the AM RLC entity as RLC SDUs in the RLC layer, and then mapped to the next layer as one or more RLC PDUs(s) after segmentation. After receiving the MAC SDUs, the MAC layer may be multiplexed into the same MAC PDU, waiting to be transmitted by the PHY layer. Thus, the RRC connection reestablishment message and the RRC connection reconfiguration message may be sent in one TB, or may be sent in an adjacent or non-adjacent TB, the specific case being related to the base station configuration. Both of which will be discussed in the following embodiments.
According to the above flow, in the prior art, the terminal initiates 3 random access flows in total, which are respectively used for sending RRC Re-establishment Request, RLC ACK and RRC Re-establishment Complete messages. According to the description of the random access flow, the random access flow belongs to contention access, which increases the reestablishment delay of the wireless link of the terminal and is unfavorable for the rapid recovery of the data service. At the same time, this also aggravates the network side load and increases the power consumption of the terminal.
In order to solve the above problems, the general idea of the embodiment of the application is as follows:
in step 705, the terminal receives an RRC connection reconfiguration message, which carries the SR configuration. This SR configuration is periodic and dedicated to the terminal, so that acquisition of uplink resource grants by SR is a fast and efficient way of uplink resource request without contention access. Therefore, unnecessary random access flow is reduced, and uplink transmission messages (namely RLC response message, RRC connection reestablishment completion message and RRC connection reconfiguration completion message) are combined and sent through uplink resources acquired by the scheduling indication message, so that reestablishment of a wireless link and network recovery can be accelerated. The reducing unnecessary random access procedures includes, but is not limited to, not initiating random access procedures and interrupting initiated random access procedures.
Embodiments of the present application will be described below with reference to specific examples. Wherein, as before, the base station downlink transmits the RRC connection reestablishment message and the RRC connection reconfiguration message, which may be in one TB, or in an adjacent or non-adjacent TB, and the cases thereof are discussed in fig. 8 and 9, respectively.
As shown in fig. 8, a flow chart of reestablishing a radio link by a terminal according to an embodiment of the present application is shown, and a base station sends an RRC connection reestablishment message and an RRC connection reconfiguration message to the terminal in the same Transport Block (TB). The dashed box represents a random access procedure in which the message content of Msg 3 is the message on the arrow in the dashed box. The flow chart comprises the following steps:
Step 801, the terminal starts a complete random access procedure for transmitting an RRC connection reestablishment request message to the base station.
Step 802, the terminal receives a TB sent by the base station, where the TB includes an RRC connection reestablishment message and an RRC connection reconfiguration message, where the RRC connection reconfiguration message carries SR configuration information.
Step 803, the terminal sends a scheduling request to the base station according to the uplink resource information indicated by the SR configuration.
Step 804, the terminal receives a scheduling indication message from the base station, where the scheduling indication message is used for authorizing uplink resources.
Step 805, the terminal sends RLC response message, RRC connection reestablishment completion message and RRC connection reconfiguration completion message on the authorized uplink resource; the RLC acknowledgement message is configured to indicate successful reception of an RRC connection reestablishment message, where the RRC connection reestablishment completion message is configured to confirm successful completion of RRC connection reestablishment, and the RRC connection reconfiguration completion message is configured to confirm successful completion of RRC connection reconfiguration.
When the RRC connection reestablishment message and the RRC connection reconfiguration message are in the same TB, the data link layer of the terminal processes the TB, and delivers the two messages upward in the order as described. Since the RRC connection reestablishment message is an AM message, the terminal should send an RLC acknowledgement message to confirm successful reception of the RRC connection reestablishment message. But the terminal delays sending the RLC acknowledgement message, the implementation includes controlling at the data link layer, and the controlled actions include generating or sending the RLC acknowledgement message in a delayed manner.
In addition, since the base station generates signaling in sequence, the demultiplexed messages of the terminal should also follow the sequence: the RRC connection reestablishment message is preceded and the RRC connection reconfiguration message is followed. Therefore, the RRC layer will first get RRC connection reestablishment signaling. After the signaling is processed, the terminal delays sending the RRC connection reestablishment completion message, wherein the implementation mode comprises, but is not limited to, the control signaling of the RRC connection reestablishment completion is submitted after the RRC layer delays, and the RRC connection reestablishment completion message is sent after the data link layer delays; the deferred delivery behavior includes deferring generation of RRC connection reestablishment complete signaling.
The subsequent RRC connection reconfiguration message is decrypted by the PDCP layer and then submitted to the RRC layer for updating the SR configuration of the terminal, so that the terminal can efficiently apply for uplink resource grant to the base station. Meanwhile, the RRC layer respectively generates and transmits RRC connection reestablishment completion signaling and RRC connection reconfiguration completion signaling to the lower layer, and the sequence is as described. The RLC layer also generates an RLC acknowledgement message which waits for transmission together with the two aforementioned signaling. The MAC layer designates the total size of RLC PDUs to the RLC layer according to the new uplink resources that are granted. The RLC layer performs segmentation processing on two signaling to be sent according to the total RLC PDU size, that is, one signaling may correspond to a plurality of RLC PDUs. These RLC PDUs are each header-added and multiplexed into one or more TBs for uploading to the base station. In the case of multi-TB transmission, the terminal does not need to acquire a new uplink resource grant during this period.
From the above flow, the terminal controls the generation of the RLC response message and the RRC reestablishment completion message, so that the terminal uses one uplink resource grant together with the transmission of the RRC reconfiguration completion message, thereby reducing the total number of times of applying uplink grants to the base station, in particular, reducing the number of times that the terminal must acquire grants through random access flow when transmitting the RLC response message and the RRC reestablishment completion message, reducing time consumption, and efficiently recovering radio link connection. Compared with the prior art, the embodiment of the application transmits three messages to be uploaded through the same uplink resource grant, wherein the uplink resource grant is further acquired through the SR configuration carried by the conventional RRC reconfiguration message. Therefore, the embodiment of the application simplifies the reestablishment flow of the wireless link, greatly saves the time consumption of reestablishment of the link and reduces the occupation of uplink resources and a base station network side.
The embodiment shown in fig. 9 is a case where the RRC connection reestablishment message and the RRC connection reconfiguration message are transmitted in different TBs. For the foregoing reasons, the base station downlink RRC connection reestablishment message and the RRC connection reconfiguration message may be in different TBs. Here, the TB including the RRC connection reestablishment message is referred to as a first TB, and the TB including the RRC connection reconfiguration message is referred to as a second TB. Due to instability in the environment of wireless transmission and in the case of retransmission initiated by the base station, the sequence of TBs received by the terminal may be wrong, i.e. the second TB may arrive at the terminal before the first TB. It should be understood that the steps in the flow chart represent only one of the cases. The dashed box represents a random access procedure in which the message content of Msg 3 is the message on the arrow in the dashed box. The method comprises the following specific steps:
step 901, the terminal starts a complete random access procedure for sending an RRC connection reestablishment request message.
Step 902, the terminal receives an RRC connection reestablishment message.
In step 903, the terminal receives an RRC connection reconfiguration message, where the RRC connection reconfiguration message carries SR configuration information.
Step 904, the terminal sends a scheduling request to the base station according to the uplink resource information indicated by the SR configuration.
Step 905, a terminal receives a scheduling indication message from the base station, where the scheduling indication message is used for authorizing uplink resources.
Step 906, the terminal sends RLC response message, RRC connection reestablishment completion message and RRC connection reconfiguration completion message on the authorized uplink resource.
When the second TB is received earlier than the first TB by the terminal, the data link layer de-multiplexes to obtain an RLC SDU containing RRC connection reconfiguration signalling, but since the nature of the up-delivery by the PDCP layer is on-demand delivery, it can be discerned that the signalling arrives before the RRC connection reestablishment signalling. The PDCP layer caches the RRC connection reconfiguration signaling and waits for the RRC connection reestablishment signaling. In addition, since the RRC connection reconfiguration signaling carries indication information of the AS key update, the decryption key of the PDCP layer is not updated, and the RRC connection reconfiguration signaling cannot be decrypted and submitted. Therefore, on the terminal side, the control signaling sequence submitted to the network layer by the data link layer must be RRC connection reestablishment signaling and then RRC connection reconfiguration signaling.
As in the previous embodiment, after receiving the RRC connection reestablishment message, the terminal delays sending the RLC ACK and the RRC connection reestablishment complete message, so that the random access procedure is not started to apply for uplink resource grant. In the foregoing embodiment, the terminal waits for uplink resource grant carried by the RRC reconfiguration message, for integrated transmission of the following messages: RLC acknowledgement message, RRC connection reestablishment complete message, and RRC connection reconfiguration complete message. For the terminal side, after the first TB, the arrival time of the second TB is unknown, and considering the instability of the wireless network, such as network congestion or data loss, the waiting time T can be set to avoid the waste of network resources caused by the base station repeatedly downloading the RRC connection reestablishment message due to the lack of RLC ACK. The waiting time T is used to instruct the terminal to delay the time of initiating the random access procedure, that is, to suspend the time of sending the random access preamble to the base station, and T may be a fixed parameter or an adjustable parameter.
If T is a fixed parameter, which is stored in advance at the terminal side, the specific value may be set according to factors such as user service, and when the RRC connection reestablishment procedure starts, the RRC layer informs the data link layer downwards, so as to instruct the layer to generate or transmit the RLC response message in the maximum delay T time after receiving the RRC reestablishment message, and delay the data link layer to initiate the random access procedure to the base station. Meanwhile, the RRC layer also submits RRC connection reestablishment completion signaling to the data link layer with the maximum delay T time.
If T is an adjustable parameter, the calculation mode is based on various factors including, but not limited to, terminal requirements, service requirements, priorities, etc.
If the terminal does not receive the RRC reconfiguration message within the T time, initiating a random access procedure to the base station, wherein the random access procedure is used for applying for uplink resource authorization and is used for sending an RLC response message and an RRC connection reestablishment completion message.
Therefore, by reasonably setting the waiting time T, the terminal can wait for SR configuration in the RRC connection reconfiguration message by delaying the transmission of the RLC response message and the RRC connection reestablishment completion message and apply for uplink scheduling and acquire uplink authorized resources, thereby achieving the purpose of reducing the initiation times of the random access flow. The uplink resource obtained by the application can efficiently combine and send the RLC response message, the RRC reestablishment completion message and the RRC reconfiguration completion message, thereby reducing reestablishment delay of a wireless link.
Fig. 10 is a schematic flow chart of another method for reestablishing a radio link according to an embodiment of the present application, wherein a dashed box represents a random access procedure, and the message content of Msg 3 is a message on an arrow in the dashed box. The process comprises the following steps:
In step 1001, the terminal starts a complete random access procedure for sending an RRC connection reestablishment request message.
Step 1002, the terminal receives the RRC connection reestablishment message.
Step 1003, the terminal transmits a random access preamble.
Step 1004, the terminal receives an RRC connection reconfiguration message, where the RRC connection reconfiguration message carries SR configuration information.
Step 1005, the terminal sends a scheduling request to the base station according to the uplink resource information indicated by the SR configuration.
Step 1006, the terminal receives a scheduling indication message from the base station, where the scheduling indication message is used to authorize uplink resources.
Step 1007, the terminal sends RLC acknowledgement message, RRC connection reestablishment complete message, and RRC connection reconfiguration complete message on the authorized uplink resources.
After step 1002, the terminal intends to apply for uplink resource grant to the base station through a complete random access procedure for transmitting RLC response message. In step 1003, the terminal sends a random access preamble, which is the first step of starting a complete random access procedure, and the base station should send a random access response after receiving, which carries uplink resource grant, and is used to instruct the terminal to configure uplink resource information. Since this response behavior is only a response of the base station side to the received random access preamble, it is not informed of the corresponding uploaded content. The base station may have sent an RRC connection reconfiguration message to the terminal before sending the random access response.
In this case, the terminal receives the RRC connection reconfiguration message first and then receives the random access response, and the RRC layer updates the SR configuration carried in the RRC connection reconfiguration message to the lower layer. Accordingly, the terminal interrupts the random access procedure and transmits a scheduling request to the base station using the SR configuration. Meanwhile, the RRC layer firstly transmits an RRC connection reestablishment completion signaling downwards, and then transmits an RRC connection reconfiguration completion signaling. The data link layer finally uses the authorized uplink resources in the scheduling indication message to send the following messages: RLC acknowledgement message, RRC connection reestablishment complete message, and RRC connection reconfiguration complete message.
If the random access response arrives at the terminal earlier than the RRC connection reconfiguration message, the terminal uses the uplink resource of the random access application to send the RLC response message, and starts the random access process again, the authorized uplink resource is used for sending the RRC connection reconfiguration completion message, and finally the uplink authorization in the scheduling indication message is used for sending the RRC connection reconfiguration completion message.
In addition, since the time for the terminal to receive the RRC connection reconfiguration message is unknown, that is, while receiving the message, the terminal may have already transmitted the random access preamble, or may have initiated the random access procedure, but has not transmitted the random access preamble, it should be understood that step 1003 is not a necessary step, but one of possible situations. The terminal immediately interrupts the random access procedure including, but not limited to, suspending the generation of the random access preamble, stopping the transmission of the random access preamble, discarding the random access response, etc., after receiving the RRC connection reconfiguration message, the interrupting of the random access occurring at the data link layer and the physical layer. And then, the terminal validates the uplink resource authorization in the scheduling indication message, and sends an RLC response message, an RRC connection reestablishment completion message and an RRC connection reconfiguration completion message.
The above flow can be known that the terminal does not guarantee the integrity of the random access flow, so that the random access flow can be interrupted, and the three messages can be efficiently integrated and transmitted. Because the uplink resource authorization of the single TB is obtained through random access, the size of the portable content is determined by the base station, and the uplink resource authorization obtained by the scheduling request is not as efficient as the uplink resource authorization of the multi-TB is allowed, so that the uplink resource authorization of the single TB is more suitable for overall transmission of the three messages in the RRC reestablishment flow. The terminal responds to the RRC connection reconfiguration message in time to interrupt the random access flow in progress, so that SR configuration in the RRC connection reconfiguration message is effective, the three messages are sent more efficiently, and the time delay of radio link reestablishment is reduced.
The following describes a wireless communication device provided in an embodiment of the present application.
Referring to fig. 11, a schematic block diagram of a wireless communication apparatus 1100 according to an embodiment of the present application is provided, where the communication apparatus 1100 includes a processing unit 1110 and a transceiver unit 1120. The wireless communication device is used for realizing the steps of the corresponding terminal in the above embodiments:
The processing unit 1110 is configured to control the transceiver unit 1120. A transceiver unit 1120, configured to send an RRC connection reestablishment request message, where the RRC connection reestablishment request message is used to request reestablishment of an RRC connection; receiving an RRC connection reestablishment message of the base station, wherein the RRC connection reestablishment message is used for responding to the RRC connection reestablishment request message; receiving an RRC connection reconfiguration message from the base station, wherein the RRC connection reconfiguration message carries resource indication information of a scheduling request; receiving scheduling indication information from the base station, wherein the scheduling indication information is used for authorizing uplink resources; and sending the RLC response message, the RRC connection reestablishment completion message and the RRC connection reconfiguration completion message. The RLC acknowledgement message is configured to confirm receipt of the RRC connection reestablishment message, the RRC connection reestablishment completion message is configured to confirm completion of RRC connection reestablishment, and the RRC connection reconfiguration completion message is configured to confirm completion of RRC connection reconfiguration.
In a possible implementation method, the processing unit 1110 is further configured to suspend the transceiver unit 1120 from sending a random access preamble after receiving the RRC connection reestablishment message. Wherein the RRC connection reconfiguration message has been received during suspension of transmission of a random access preamble to the base station.
In a possible implementation method, the processing unit 1110 is configured to configure a duration for which the transceiver unit 1120 pauses sending the random access preamble.
In one possible implementation method, the duration of suspending sending the random access preamble configured by the processing unit 1110 includes any one of the following: one transmission time interval TTI, two TTIs, or three TTIs.
In a possible implementation, the transceiver unit 1120 is further configured to send a random access preamble after receiving the RRC connection reestablishment message. Wherein the RRC connection reconfiguration message has been received before the response message of the random access preamble is received.
In a possible implementation method, the processing unit 1110 is further configured to terminate the subsequent flow of the random access preamble in advance after the transceiver unit 1120 receives the RRC connection reconfiguration message.
In the above embodiments, the transceiver 1120 may be divided into a single receiver and a single transmitter, and each may have functions of receiving and transmitting, which are not limited herein.
Optionally, the communication device may further include a storage unit, where the storage unit is configured to store data or instructions (which may also be referred to as codes or programs), and the respective units may interact or be coupled with the storage unit to implement the corresponding methods or functions. The coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units, or modules, which may be in electrical, mechanical, or other forms for information interaction between the devices, units, or modules.
In the embodiment of the present application, the division of the units in the communication device is merely a division of a logic function, and may be fully or partially integrated into a physical entity or may be physically separated. And the units in the communication device may all be implemented in the form of software calls via the processing element; or can be realized in hardware; it is also possible that part of the units are implemented in the form of software, which is called by the processing element, and part of the units are implemented in the form of hardware. For example, each unit may be a processing element that is set up separately, may be implemented integrally in a certain chip of the communication device, or may be stored in a memory in the form of a program, and the function of the unit may be called and executed by a certain processing element of the communication device. Furthermore, all or part of these units may be integrated together or may be implemented independently. The processing element described herein, which may also be referred to as a processor, may be an integrated circuit with signal processing capabilities. In implementation, each step of the above method or each unit above may be implemented by an integrated logic circuit of hardware in a processor element or in the form of software called by a processing element.
In one example, the unit in any of the above communication devices may be one or more integrated circuits configured to implement the above methods, such as: one or more Application SPECIFIC INTEGRATED Circuits (ASIC), or one or more microprocessors (DIGITAL SINGNAL processors, DSP), or one or more field programmable gate arrays (field programmable GATE ARRAY, FPGA), or a combination of at least two of these integrated circuit forms. For another example, when the unit in the communication device is implemented in the form of a scheduler of processing elements, the processing elements may be general purpose processors, such as a central processing unit (central processing unit, CPU) or other processor that may invoke the program. For another example, the units may be integrated together and implemented in the form of a system-on-a-chip (SOC).
Referring to fig. 12, a schematic structural diagram of a wireless communication device according to an embodiment of the present application is provided, where the wireless communication device may be a wireless communication device or a network device, or may be a chip or a circuit, for example, may be disposed on the chip or the circuit of the wireless communication device, and further, for example, may be disposed on the chip or the circuit of the network device, so as to implement the method in the foregoing method embodiment. As shown in fig. 12, the communication apparatus 1200 includes: processor 1210 and transceiver 1230, optionally, the communication device 1200 further comprises a memory 1220, which memory 1220 is not necessary represented by a dashed box in the figure. The transceiver 1230 is used to enable communication with other devices.
Further, the communication device 1200 may further comprise a bus system, wherein the processor 1210, the memory 1220, and the transceiver 1230 may be connected by the bus system.
It should be appreciated that the processor 1210 may be a single chip. For example, the processor 1302 may be a field programmable gate array (field programmable GATE ARRAY, FPGA), an Application Specific Integrated Chip (ASIC), a system on chip (SoC), a central processing unit (central processor unit, CPU), a network processor (network processor, NP), a digital signal processing circuit (DIGITAL SIGNAL processor, DSP), a microcontroller (micro controller unit, MCU), a programmable controller (programmable logic device, PLD) or other integrated chip.
In implementation, the steps of the methods described above may be performed by integrated logic circuitry in hardware in processor 1210 or by instructions in software. The steps of a method disclosed in connection with an embodiment of the present application may be embodied directly in hardware processor execution or in a combination of hardware and software modules in processor 1210. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in the memory 1220, and the processor 1210 reads the information in the memory 1220 and performs the steps of the above method in combination with its hardware.
Specifically, the functions/implementation procedure of the transceiving unit 1120 in fig. 11 may be implemented by the processor 1210 in the communication apparatus 1200 shown in fig. 12 calling computer executable instructions stored in the memory 1220. Or the function/implementation of the transceiver unit 1120 in fig. 11 may be implemented by the transceiver 1230 in the communication apparatus 1200 shown in fig. 12.
It should be noted that the processor 1210 in the embodiment of the present application may be an integrated circuit chip with signal processing capability. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, or discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be embodied directly in the execution of a hardware decoding processor, or in the execution of a combination of hardware and software modules in a decoding processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.
In embodiments of the application, memory 1220 may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an erasable programmable ROM (erasable PROM), an electrically erasable programmable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM) which acts as external cache memory. By way of example, and not limitation, many forms of RAM are available, such as static random access memory (STATIC RAM, SRAM), dynamic random access memory (DYNAMIC RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate synchronous dynamic random access memory (double DATA RATE SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (ENHANCED SDRAM, ESDRAM), synchronous link dynamic random access memory (SYNCHLINK DRAM, SLDRAM), and direct memory bus random access memory (direct rambus RAM, DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.
In the case where the communication device 1200 corresponds to the wireless communication device in the above-described method, the communication device may include a processor 1210, a transceiver 1230, and a memory 1220. The memory 1220 is configured to store instructions and the processor 1210 is configured to execute the instructions stored by the memory 1220 to implement steps performed by the wireless communication device in any one or more of the corresponding methods shown in fig. 8-9. .
Those of ordinary skill in the art will appreciate that: the first, second, etc. numbers in the embodiments of the present application are merely for convenience of description and are not intended to limit the scope of the embodiments of the present application, and indicate the sequence. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship. "at least one" means one or more. At least two means two or more. "at least one," "any one," or the like, refers to any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one of a, b, or c (species ) may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or plural. "plurality" means two or more, and the like.
It should be understood that, in various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application.
The technical scheme provided by the embodiment of the application can be realized completely or partially by software, hardware, firmware or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, a terminal device, a network device, an artificial intelligence device, or other programmable apparatus. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, for example, by wired (e.g., coaxial cable, optical fiber, digital Subscriber Line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device including one or more servers, data centers, etc. that can be integrated with the available medium. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid State Drive (SSD)), etc.
In embodiments of the present application, the embodiments may be referred to each other, e.g., methods and/or terms between method embodiments may be referred to each other, e.g., functions and/or terms between apparatus embodiments and method embodiments may be referred to each other.
The foregoing is merely illustrative of the present invention, and the present invention is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.