CN116636299A - Method and device for processing radio link failure and communication equipment - Google Patents
Method and device for processing radio link failure and communication equipment Download PDFInfo
- Publication number
- CN116636299A CN116636299A CN202180082863.6A CN202180082863A CN116636299A CN 116636299 A CN116636299 A CN 116636299A CN 202180082863 A CN202180082863 A CN 202180082863A CN 116636299 A CN116636299 A CN 116636299A
- Authority
- CN
- China
- Prior art keywords
- scg
- mcg
- message
- activation
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 167
- 238000004891 communication Methods 0.000 title claims abstract description 79
- 238000012545 processing Methods 0.000 title abstract description 23
- 238000011084 recovery Methods 0.000 claims abstract description 66
- 230000008569 process Effects 0.000 claims abstract description 32
- 230000004913 activation Effects 0.000 claims description 146
- 238000004590 computer program Methods 0.000 claims description 34
- 238000012790 confirmation Methods 0.000 claims description 23
- 230000009849 deactivation Effects 0.000 claims description 17
- 230000001360 synchronised effect Effects 0.000 claims description 13
- 238000010586 diagram Methods 0.000 description 14
- 101100150275 Caenorhabditis elegans srb-3 gene Proteins 0.000 description 12
- 108091005487 SCARB1 Proteins 0.000 description 12
- 102100037118 Scavenger receptor class B member 1 Human genes 0.000 description 12
- 230000006870 function Effects 0.000 description 10
- 238000005259 measurement Methods 0.000 description 9
- 230000009977 dual effect Effects 0.000 description 6
- 230000004044 response Effects 0.000 description 5
- 230000001960 triggered effect Effects 0.000 description 5
- 230000001413 cellular effect Effects 0.000 description 4
- 230000011664 signaling Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 101100150273 Caenorhabditis elegans srb-1 gene Proteins 0.000 description 1
- 101001055444 Homo sapiens Mediator of RNA polymerase II transcription subunit 20 Proteins 0.000 description 1
- 102100026165 Mediator of RNA polymerase II transcription subunit 20 Human genes 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000005562 fading Methods 0.000 description 1
- GVVPGTZRZFNKDS-JXMROGBWSA-N geranyl diphosphate Chemical compound CC(C)=CCC\C(C)=C\CO[P@](O)(=O)OP(O)(O)=O GVVPGTZRZFNKDS-JXMROGBWSA-N 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000003595 spectral effect Effects 0.000 description 1
- 238000001228 spectrum Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000001356 surgical procedure Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 238000011144 upstream manufacturing Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/15—Setup of multiple wireless link connections
Abstract
The embodiment of the application provides a method and a device for processing radio link failure and communication equipment, wherein the method comprises the following steps: the terminal equipment determines that the MCG radio link failure occurs under the condition that the SCG is in a deactivated state; the terminal device triggers an RRC connection reestablishment process of the MCG or a quick recovery process of the MCG.
Description
The embodiment of the application relates to the technical field of mobile communication, in particular to a method and a device for processing radio link failure and communication equipment.
In case of radio link failure of the primary cell group (Master Cell Group, MCG), the quick recovery of MCG can be performed through the link on the secondary cell group (Secondary Cell Group, SCG) side. However, the SCG may be in an activated state or a deactivated state, and if the SCG is in the deactivated state, in the case that the MCG fails in radio link, the terminal device cannot perform quick recovery of the MCG through the link on the SCG side, and how to perform MCG recovery is a problem to be solved.
Disclosure of Invention
The embodiment of the application provides a method and a device for processing radio link failure and communication equipment.
The method for processing the radio link failure provided by the embodiment of the application comprises the following steps:
the terminal equipment determines that the MCG radio link failure occurs under the condition that the SCG is in a deactivated state;
the terminal device triggers a radio resource control (Radio Resource Control, RRC) connection re-establishment procedure of the MCG or a fast recovery procedure of the MCG.
The method for processing the radio link failure provided by the embodiment of the application comprises the following steps:
the terminal equipment determines that MCG radio link failure occurs;
the terminal equipment sends a first message to the SCG and starts a first timer, wherein the first message is used for triggering the quick recovery process of the MCG;
and if the terminal equipment receives the SCG deactivation command before the first timer is overtime, the terminal equipment triggers an RRC connection reestablishment process.
The device for processing the radio link failure provided by the embodiment of the application is applied to the terminal equipment, and comprises the following components:
a determining unit, configured to determine that an MCG radio link failure occurs when the SCG is in a deactivated state;
and the communication unit is used for triggering the RRC connection reestablishment process of the MCG or the quick recovery process of the MCG.
The device for processing the radio link failure provided by the embodiment of the application is applied to the terminal equipment, and comprises the following components:
a determining unit, configured to determine that an MCG radio link failure occurs;
a communication unit, configured to send a first message to an SCG, where the first message is used to trigger a fast recovery procedure of the MCG;
a control unit, configured to start a first timer after the communication unit sends a first message to the SCG;
the communication unit is further configured to trigger an RRC connection reestablishment procedure if an SCG deactivation command is received before the first timer expires.
The communication device provided by the embodiment of the application comprises a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory to execute the method for processing the radio link failure.
The chip provided by the embodiment of the application is used for realizing the method for processing the radio link failure.
Specifically, the chip includes: and a processor for calling and running the computer program from the memory, so that the device provided with the chip executes the method for processing the radio link failure.
The computer readable storage medium provided by the embodiment of the application is used for storing a computer program, and the computer program enables a computer to execute the method for processing the radio link failure.
The computer program product provided by the embodiment of the application comprises computer program instructions, wherein the computer program instructions enable a computer to execute the method for processing radio link failure.
The computer program provided by the embodiment of the application, when running on a computer, causes the computer to execute the method for processing the radio link failure.
Through the technical scheme, on one hand, under the condition that the MCG radio link fails, if the SCG is in a deactivated state, the terminal equipment directly initiates an RRC connection reestablishment process or initiates a random access process to the SCG and then carries out quick recovery of the MCG based on the SCG, so that the RRC connection reestablishment of the MCG or the quick MCG recovery is realized. On the other hand, if the terminal device receives the SCG deactivation command during the operation of the first timer corresponding to the MCG fast recovery under the condition that the MCG radio link failure occurs, the terminal device initiates the RRC connection reestablishment process, thereby realizing the RRC connection reestablishment of the MCG.
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute a limitation on the application. In the drawings:
Fig. 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application;
fig. 2 is a flowchart illustrating an RRC connection reestablishment procedure according to an embodiment of the present application;
fig. 3 is a schematic diagram of triggering a fast MCG recovery procedure using Split SRB1 on the SCG side according to an embodiment of the present application;
fig. 4 is a schematic diagram of an SRB3 triggered fast MCG recovery procedure using the SCG side provided in an embodiment of the present application;
fig. 5 is a flowchart illustrating a method for handling radio link failure according to an embodiment of the present application;
fig. 6 is a second flowchart of a method for handling radio link failure according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of an apparatus for handling radio link failure according to an embodiment of the present application;
fig. 8 is a schematic diagram ii of a structural composition of an apparatus for handling radio link failure according to an embodiment of the present application;
fig. 9 is a schematic structural diagram of a communication device according to an embodiment of the present application;
FIG. 10 is a schematic block diagram of a chip of an embodiment of the application;
fig. 11 is a schematic block diagram of a communication system provided in an embodiment of the present application.
The following description of the technical solutions according to the embodiments of the present application will be given with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
The technical scheme of the embodiment of the application can be applied to various communication systems, such as: long term evolution (Long Term Evolution, LTE) systems, LTE frequency division duplex (Frequency Division Duplex, FDD) systems, LTE time division duplex (Time Division Duplex, TDD), systems, 5G communication systems, future communication systems, or the like.
An exemplary communication system 100 to which embodiments of the present application may be applied is shown in fig. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal 120 (or referred to as a communication terminal, terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminals located within the coverage area. Alternatively, the network device 110 may be an evolved base station (Evolutional Node B, eNB or eNodeB) in the LTE system, or a radio controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the network device may be a mobile switching center, a relay station, an access point, a vehicle device, a wearable device, a hub, a switch, a bridge, a router, a network-side device in a 5G network, or a network device in a future communication system, etc.
The communication system 100 further includes at least one terminal 120 located within the coverage area of the network device 110. "terminal" as used herein includes, but is not limited to, connection via wireline, such as via public-switched telephone network (Public Switched Telephone Networks, PSTN), digital subscriber line (Digital Subscriber Line, DSL), digital cable, direct cable connection; and/or another data connection/network; and/or via a wireless interface, e.g., for a cellular network, a wireless local area network (Wireless Local Area Network, WLAN), a digital television network such as a DVB-H network, a satellite network, an AM-FM broadcast transmitter; and/or means of the other terminal arranged to receive/transmit communication signals; and/or internet of things (Internet of Things, ioT) devices. Terminals arranged to communicate over a wireless interface may be referred to as "wireless communication terminals", "wireless terminals" or "mobile terminals". Examples of mobile terminals include, but are not limited to, satellites or cellular telephones; a personal communications system (Personal Communications System, PCS) terminal that may combine a cellular radiotelephone with data processing, facsimile and data communications capabilities; a PDA that can include a radiotelephone, pager, internet/intranet access, web browser, organizer, calendar, and/or a global positioning system (Global Positioning System, GPS) receiver; and conventional laptop and/or palmtop receivers or other electronic devices that include a radiotelephone transceiver. A terminal may refer to an access terminal, user Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal in a 5G network or a terminal in a future evolved PLMN, etc.
Alternatively, direct to Device (D2D) communication may be performed between the terminals 120.
Alternatively, the 5G communication system or 5G network may also be referred to as a New Radio (NR) system or NR network.
Fig. 1 illustrates one network device and two terminals, alternatively, the communication system 100 may include multiple network devices and each network device may include other numbers of terminals within its coverage area, which is not limited by the embodiment of the present application.
Optionally, the communication system 100 may further include a network controller, a mobility management entity, and other network entities, which are not limited by the embodiment of the present application.
It should be understood that a device having a communication function in a network/system according to an embodiment of the present application may be referred to as a communication device. Taking the communication system 100 shown in fig. 1 as an example, the communication device may include a network device 110 and a terminal 120 with communication functions, where the network device 110 and the terminal 120 may be specific devices described above, and are not described herein again; the communication device may also include other devices in the communication system 100, such as a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.
It should be understood that the terms "system" and "network" are used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.
In order to facilitate understanding of the technical solutions of the embodiments of the present application, the following describes the technical solutions related to the embodiments of the present application.
With the pursuit of speed, delay, high speed mobility, energy efficiency and diversity and complexity of future life business, the third generation partnership project (3 rd Generation Partnership Project,3 GPP) international standards organization began developing 5G. The main application scenario of 5G is: enhanced mobile Ultra-wideband (enhanced Mobile Broadband, emmbb), low latency high reliability communication (URLLC), large-scale Machine-based communication (mctc).
On the one hand, embbs still target users to obtain multimedia content, services and data, and their demand is growing very rapidly. On the other hand, since an eMBB may be deployed in different scenarios, such as indoors, urban, rural, etc., its capabilities and requirements are also quite different, so that detailed analysis must be performed in connection with a specific deployment scenario, not in general. Typical applications of URLLC include: industrial automation, electric power automation, remote medical operation (surgery), traffic safety guarantee and the like. Typical characteristics of mctc include: high connection density, small data volume, delay insensitive traffic, low cost and long service life of the module, etc.
At early deployment of NRs, full NR coverage is difficult to acquire, so typical network coverage is wide area LTE coverage and island coverage mode of NRs. And a large amount of LTE is deployed below 6GHz, and the frequency spectrum below 6GHz which can be used for 5G is few. NR must study spectral applications above 6GHz while high-band coverage is limited and signal fading is fast. Meanwhile, in order to protect the mobile operators from early investment in LTE, a working mode of close cooperation (tight interworking) between LTE and NR is proposed.
To enable 5G network deployment and commercial applications as soon as possible, 3GPP first completed the first 5G release, E-UTRA and NR dual connectivity (E-UTRA-NR Dual Connectivity, EN-DC), before 2017, 12. In EN-DC, an LTE base station (eNB) serves as a Master Node (MN), and an NR base station (gNB or EN-gNB) serves as a Secondary Node (SN). Wherein the MN is mainly responsible for RRC control functions and control plane towards the core network; the SN may configure secondary signaling, such as SRB3, primarily to provide data transfer functionality.
In the later stages of R15, other dual connectivity (Dual Connectivity, DC) modes will be supported, namely NR and E-UTRA dual connectivity (NR-E-UTRA Dual Connectivity, NE-DC), 5GC-EN-DC, NR DC. For EN-DC, the core network of the access network connection is an evolved packet core network (Evolved Packet Core network, EPC), while the core network of the other DC mode connection is a 5G core network (5G Core Network,5GC).
In R15, when a radio link failure (also referred to as MCG failure) occurs in the MCG, an RRC connection reestablishment procedure is triggered, and referring to fig. 2, fig. 2 shows a flow chart of the RRC connection reestablishment procedure, which includes the following steps:
step 201: the terminal device sends an RRC connection reestablishment request message to the network.
Step 202: the network sends an RRC connection reestablishment message to the terminal device.
Step 203: the terminal device sends an RRC connection reestablishment complete message to the network.
The "RRC connection reestablishment request message" may also be referred to as "RRC reestablishment request message (RRCReestablishmentRequest)".
The "RRC connection reestablishment message" may also be referred to as "RRC reestablishment message (rrcreestabliment)".
The "RRC connection reestablishment complete message" may also be referred to as "RRC reestablishment complete message (rrcreestablischentcomplete)".
Table 1 below gives the content carried in the RRC connection reestablishment request message. Wherein the RRC connection reestablishment request message carries a reestablishment cause (resestishmentcause). In addition, the RRC connection reestablishment request message also carries the following: cell radio network temporary identity (Cell-Radio Network Temporary Identifier, C-RNTI), physical Cell identity (Physical Cell Identity, PCI), and short complete message authentication code (short Message Authentication Code-Integrity, shortMAC-I). In addition, in the case of the optical fiber,
TABLE 1
Considering the scenario that the MCG fails and the SCG side signal is better, in order to avoid RRC connection reestablishment in the scenario, service interruption is reduced, and a fast MCG recovery (fast MCG recovery) function is introduced into R16. Namely, under the condition that the MCG fails in radio link, the terminal equipment sends MCG failure information (MCGFailurenformation) through a link of the SCG side, and triggers the network side to quickly recover the link of the MCG side.
It is noted that MCG fast recovery is triggered if and only if AS is securely activated and at least one of SRB2 and split SRB1 is established. MCG failure information may be sent through Split SRB1 or SRB3 on the SCG side. Only if Split SRB1 is not configured and SRB3 is configured, MCGFailureInformation is reported using SRB 3.
After the terminal equipment sends the MCGFailueinformation, a timer Guard timer (namely T316) is started, and the network side response is waited. The message responded by the network side can be: a synchronization reconfiguration (reconfiguration with sync) or RRC Release (RRC Release) message. If the terminal equipment receives the response message, the terminal equipment stops the Guard timer. If the timer Guard timer is overtime, the terminal device triggers an RRC connection reestablishment process, and at this time, the reestablishment reason value in the RRC connection reestablishment request fills in 'other failure'.
The terminal device can trigger the rapid MCG recovery process, which is triggered by the configuration displayed on the network side, that is, the configuration of the timer Guard timer (the network side configures the timer Guard timer through RRC dedicated signaling) implies that the terminal device can perform the rapid MCG recovery process.
When the fast MCG recovery procedure is triggered, the terminal device sends mcgfailurenformation, and the terminal device has the following actions: 1. suspending transmissions on MCG side SRBs, DRBs, except SRB 0; 2. resetting the MCG MAC; 3. the measurement configurations from the MCG and SCG sides are saved and, if possible, measurements continue to be made in accordance with the measurement configurations of the MCG and SCG sides. If the terminal device receives the response from the network side, the terminal device resumes transmission from the MCG side.
Referring to fig. 3, fig. 3 shows a schematic diagram of triggering a fast MCG recovery procedure by using Split SRB1 on the SCG side. The path of Split SRB1 in the upstream direction is: terminal device→mac layer on SCG side→rlc layer on SCG side→pdcp layer on MCG side→rrc layer on MCG side. The path of Split SRB1 in the downstream direction is: RRC layer on MCG side→pdcp layer on MCG side→rlc layer on SCG side→mac layer on SCG side→terminal device. The terminal device transmits MCG failure information (MCGFailureInformation) message to the network using Split SRB1, and receives a synchronization reconfiguration (reconfiguration with sync) or RRC Release (RRC Release) message of the network response using Split SRB 1.
It should be noted that if the PDCP copy (PDCP duplication) function of the split SRB1 is activated, when the terminal device detects an MCG failure, it is not necessary to switch a primary path (primary path). If the PDCP multiplexing function of split SRB1 is not activated, the primary Path is implicitly configured as the SCG side. In the MCG recovery process or the RRC connection reestablishment process, the terminal device expects the network side to display the configuration primary path to the MCG.
Referring to fig. 4, fig. 4 shows a schematic diagram of a terminal device triggering a fast MCG recovery procedure using SRB3 on the SCG side. The path of SRB3 in the uplink direction is: terminal device→mac layer on SCG side→rlc layer on SCG side→pdcp layer on SCG side→rrc layer on SCG side→mcg. The path of SRB3 in the downstream direction is: mcg→rrc layer on scg→pdcp layer on scg→rlc layer on scg→mac layer on scg→terminal device. The terminal device transmits MCG failure information (MCGFailureInformation) message to the network using SRB3, and causes SRB3 to receive a synchronization reconfiguration (reconfiguration with sync) or RRC Release (RRC Release) message of the network response.
As an example, the content of the MCG failure information (MCGFailureInformation) message includes at least one of: the MCG side can obtain measurement results; MCG link failure cause; the SCG side can obtain the measurement result; available measurements of Non-serving cells.
The above fast MCG recovery procedure is performed with the default SCG in the active state. However, the SCG may be in an activated state or a deactivated state, and if the SCG is in the deactivated state, in the case that the MCG fails in radio link, the terminal device cannot perform quick recovery of the MCG through the link on the SCG side, and how to perform MCG recovery is a problem to be solved. For this reason, the following technical solutions of the embodiments of the present application are provided.
It should be noted that, in the embodiment of the present application, the meaning of "fast MCG recovery" and "MCG fast reply" are equivalent and may be replaced with each other.
It should be noted that, in the embodiment of the present application, the description of the "MCG side" may also be referred to as "MN side", and the description of the "SCG side" may also be referred to as "SN side".
The technical scheme of the embodiment of the application can be applied to a DC architecture, wherein a main node in DC is MN, an auxiliary node in DC is SN, a cell group at the MN side is called MCG, and a cell group at the SN side is called SCG. The embodiment of the application does not limit the type of DC, and for example, MR-DC, EN-DC, NE-DC, NR-DC and the like can be used. Of course, the technical solution of the embodiment of the present application can also be applied to a multi-connection architecture.
Fig. 5 is a flowchart of a method for handling radio link failure according to an embodiment of the present application, as shown in fig. 5, the method for handling radio link failure includes the following steps:
step 501: the terminal device determines that an MCG radio link failure occurred with the SCG in a deactivated state.
Step 502: the terminal device triggers the radio resource control RRC connection reestablishment process of the MCG or the quick recovery process of the MCG.
In an embodiment of the application, the terminal device is configured with a DC mode, e.g. an MR-DC mode.
In some alternative embodiments, if the SCG is in a deactivated state, the terminal device triggers an RRC connection reestablishment procedure in case of a radio link failure of the MCG. Here, the terminal device may or may not be configured to trigger the fast MCG recovery procedure. Specifically, the terminal device is configured to trigger the fast MCG recovery procedure implicitly configured by a timer Guard timer (i.e., T316), that is, if the network side configures the timer T316, the terminal device is considered to trigger the fast MCG recovery procedure; if the network device is not configured with the timer T316, the terminal device is considered to be unable to trigger the fast MCG recovery procedure. Whether or not the network device is configured with a timer T316, if the SCG is in a deactivated state, the terminal device triggers an RRC connection reestablishment procedure in case of a radio link failure of the MCG.
In some optional embodiments, if the SCG is in a deactivated state, in case that the MCG fails in radio link, the terminal device triggers a fast recovery procedure of the MCG, specifically, the terminal device initiates a random access procedure to the SCG, and performs fast recovery of the MCG based on the SCG, thereby ensuring fast recovery of the MCG.
Here, the terminal device initiates a random access procedure to the SCG, and performs rapid recovery of the MCG based on the SCG, including: the terminal equipment sends a first message to the SCG, wherein the first message is borne in MSG3 in a random access process; the terminal device receives an RRC reconfiguration message or an RRC release message sent by the SCG, wherein the RRC reconfiguration message carries synchronous reconfiguration (reconfiguration with sync), and the RRC reconfiguration message or the RRC release message is sent to the SCG by the MCG.
In some alternative embodiments, the terminal device is configured with a first timer; after the terminal equipment sends the first message to the SCG, starting the first timer; and if the terminal equipment receives the RRC reconfiguration message or the RRC release message before the first timer is overtime, stopping the first timer by the terminal equipment.
Here, the first timer is configured for the network device, and optionally, the first timer is configured for the network device through RRC signaling. The first timer may also be referred to as a timer Guard timer or a timer T316, where the timer Guard timer or the timer T316 may refer to the description of the related schemes described above.
Here, as an example, the contents of the RRC reconfiguration message may be shown with reference to table 2 below.
TABLE 2
The following scenario illustrates how the terminal device touches the fast recovery procedure of the MCG.
Case one: the first message is an RRC connection reestablishment request message.
The terminal equipment sends an RRC connection reestablishment request message to an SCG, wherein the RRC connection reestablishment request message is borne in an MSG3 in a random access process; the terminal device receives an RRC reconfiguration message or an RRC release message sent by the SCG, wherein the RRC reconfiguration message carries synchronous reconfiguration (reconfiguration with sync), and the RRC reconfiguration message or the RRC release message is sent to the SCG by the MCG.
In some optional embodiments, the RRC connection reestablishment request message carries at least one of:
the first C-RNTI is C-RNTI allocated by the MCG to the terminal equipment;
A first PCI, which is a PCI of a primary cell PCell in an MCG;
the first shortMAC-I is generated by an MCG-based key and an integrity protection algorithm.
In some optional embodiments, the RRC connection reestablishment request message carries a reestablishment reason, where the reestablishment reason is used to indicate at least one of:
the reason for the reestablishment is that the MCG fails the radio link;
the purpose of the rebuild is to activate SCG;
the purpose of the reconstruction is to perform a fast recovery of the MCG based on the SCG.
In some optional embodiments, after the terminal device sends an RRC connection reestablishment request message to an SCG, the terminal device receives an SCG activation confirmation message or an RRC connection reestablishment message sent by the SCG; wherein the SCG activation confirmation message is prepared and issued by the SCG; alternatively, the SCG activation confirmation message is prepared by the MCG and forwarded to the SCG for delivery by the SCG.
Here, in the case where the SCG activation confirmation message is prepared by an MCG, after an MCG failure message or an RRC connection reestablishment message is transmitted to the MCG by the SCG, the SCG activation confirmation message is prepared by the MCG.
And a second case: the first message is an MCG failure information (mcgfailurenformation) message.
The terminal equipment sends an MCG failure information message to the SCG, wherein the MCG failure information message is borne in MSG3 in a random access process; the terminal device receives an RRC reconfiguration message or an RRC release message sent by the SCG, wherein the RRC reconfiguration message carries synchronous reconfiguration (reconfiguration with sync), and the RRC reconfiguration message or the RRC release message is sent to the SCG by the MCG.
In some alternative embodiments, the MCG failure information message carries first information on the MCG side or second information on the SCG side.
And under the condition that the MCG failure information message carries first information on the MCG side, forwarding the first information to the MCG by the SCG and verifying the identity of the terminal equipment by the MCG based on the first information. Or if the MCG failure information message carries second information on the SCG side, the second information verifies the identity of the terminal device by the SCG based on the second information.
In some alternative embodiments, the first information on the MCG side includes at least one of:
the first C-RNTI is C-RNTI allocated by the MCG to the terminal equipment;
a first PCI that is a PCI of a PCell in an MCG;
The first shortMAC-I is generated by an MCG-based key and an integrity protection algorithm.
In some alternative embodiments, the second information on the SCG side includes at least one of:
a second C-RNTI, wherein the second C-RNTI is C-RNTI allocated by SCG for the terminal equipment;
a second PCI, which is a PCI of a PSCell in an SCG;
and the second shortMAC-I is generated by a key and an integrity protection algorithm based on SCG.
In some optional embodiments, after the terminal device sends an MCG failure information message to the SCG, the terminal device receives an SCG activation message sent by the SCG; wherein the SCG activation message is prepared and issued by the SCG; alternatively, the SCG activation message is prepared by the MCG and forwarded to the SCG for delivery by the SCG.
In some alternative embodiments, in a case where the SCG activation message is prepared by an MCG, the SCG activation message is prepared by the MCG after the SCG sends the MCG to the MCG, or the content in the MCG failure information message.
Here, the content of the MCG failure information message includes at least one of: the MCG side can obtain measurement results; MCG link failure cause; the SCG side can obtain the measurement result; available measurements of Non-serving cells.
In some alternative embodiments, the SCG activation message carries an activated SCG reason for indicating at least one of:
the reason for activation is that MCG fails in radio link;
the purpose of activation is to activate SCG;
the purpose of activation is to perform a fast recovery of the MCG based on the SCG.
And a third case: the first message is an SCG activation request message.
The terminal equipment sends an SCG activation request message to an SCG, wherein the SCG activation request message is borne in MSG3 in the random access process; the terminal device receives an RRC reconfiguration message or an RRC release message sent by the SCG, wherein the RRC reconfiguration message carries synchronous reconfiguration (reconfiguration with sync), and the RRC reconfiguration message or the RRC release message is sent to the SCG by the MCG.
In some alternative embodiments, the SCG activation request message carries first information on the MCG side or second information on the SCG side.
And under the condition that the SCG activation request message carries first information on the MCG side, forwarding the first information to the MCG by the SCG and verifying the identity of the terminal equipment by the MCG based on the first information. Or if the SCG activation request message carries second information on the SCG side, the second information verifies the identity of the terminal device by the SCG based on the second information.
In some alternative embodiments, the first information on the MCG side includes at least one of:
the first C-RNTI is C-RNTI allocated by the MCG to the terminal equipment;
a first PCI that is a PCI of a PCell in an MCG;
the first shortMAC-I is generated by an MCG-based key and an integrity protection algorithm.
In some alternative embodiments, the second information on the SCG side includes at least one of:
a second C-RNTI, wherein the second C-RNTI is C-RNTI allocated by SCG for the terminal equipment;
a second PCI, which is a PCI of a PSCell in an SCG;
and the second shortMAC-I is generated by a key and an integrity protection algorithm based on SCG.
In some alternative embodiments, the SCG activation request message carries an activation reason for indicating at least one of:
the reason for activation is that MCG fails in radio link;
the purpose of activation is to activate SCG;
the purpose of activation is to perform a fast recovery of the MCG based on the SCG.
In some optional embodiments, after the terminal device sends an SCG activation request message to an SCG, the terminal device receives the SCG activation message sent by the SCG; wherein the SCG activation message is prepared and issued by the SCG; alternatively, the SCG activation message is prepared by the MCG and forwarded to the SCG for delivery by the SCG.
In some alternative embodiments, in a case where the SCG activation message is prepared by an MCG, the SCG activation message is prepared by the MCG after the SCG activation request message is sent to the MCG by the SCG.
In some alternative embodiments, the SCG activation message carries an activated SCG reason for indicating at least one of:
the reason for activation is that MCG fails in radio link;
the purpose of activation is to activate SCG;
the purpose of activation is to perform a fast recovery of the MCG based on the SCG.
By the technical scheme provided by the embodiment of the application, how to realize rapid MCG recovery under the condition that the MCG fails in a radio link is clear, so that normal communication of the MCG side is ensured.
The following describes the technical scheme of the embodiment of the present application with reference to specific application examples.
Application example 1
The terminal device is configured with a DC mode, e.g. an MR-DC mode.
1. If the SCG is in a deactivated state, the terminal equipment initiates a random access procedure to the SCG when the MCG fails in radio link.
2. In the random access process, the terminal device sends an RRC connection reestablishment request message to the SCG through a message 3 (MSG 3).
Here, optionally, after the terminal device has sent the RRC connection reestablishment request message, a timer T316 is started.
The RRC connection reestablishment request message carries at least one of the following information: C-RNTI, PCI, shortMAC-I. The C-RNTI is C-RNTI allocated by the MCG as the terminal equipment, the PCI is PCI of the PCell at the MCG side, and the shortMAC-I is shortMAC-I generated by utilizing a KgNB or KeNB, namely a secret key at the MCG side and an integrity protection algorithm.
The RRC connection reestablishment request message also carries a reestablishment cause (reestablishment cause), here the reestablishment cause "MCGfailure" for indicating at least one of: the reason for the reestablishment is that the MCG fails the radio link; the purpose of the rebuild is to activate SCG; the purpose of the reconstruction is to perform a fast recovery of the MCG based on the SCG. Table 3 below gives the content of the reconstruction reasons.
TABLE 3 Table 3
3. After the SCG receives the RRC connection reestablishment request message,
option 1: the SCG sends an SCG activation confirmation message or an RRC connection reestablishment message to the terminal device. Or,
option 2: the SCG sends an MCG failure message or an RRC connection reestablishment request message to the MCG, prepares an SCG activation confirmation message, and sends the SCG activation confirmation message to the terminal equipment through a link on the SCG side.
4. After receiving the MCG failure notification message or the RRC connection reestablishment request message sent by the SCG, the MCG sends an RRC reconfiguration message carrying the synchronization reconfiguration (reconfiguration with sync) to the terminal device through a link on the SCG side or sends an RRC Release (RRC Release) message to the SCG.
Application instance two
The terminal device is configured with a DC mode, e.g. an MR-DC mode.
1. If the SCG is in a deactivated state, when the MCG fails in radio link, the terminal equipment initiates a random access procedure to the SCG side.
2. In the random access process, the terminal device sends an MCG failure information (MCGFailureInformation) message to the SCG through a message 3 (MSG 3).
Here, optionally, after the terminal device has sent the MCGFailureInformation message, a timer T316 is started.
The MCGFailureInformation message carries at least one of the following information on the MCG side or the SCG side: C-RNTI, PCI, shortMAC-I. Wherein,
if the information on the MCG side is carried in the MCGFailureinformation message, the C-RNTI is the C-RNTI allocated by the MCG for the terminal equipment, the PCI is the PCI of the PCell on the MCG side, and the shortMAC-I is the shortMAC-I generated by utilizing the KgNB or KeNB, namely the key on the MCG side and the integrity protection algorithm.
If the information on the SCG side is carried in the MCGFailureinformation message, the C-RNTI is the C-RNTI allocated by the SCG for the terminal equipment, the PCI is the PCI of the PScell on the SCG side, and the shortMAC-I is the shortMAC-I generated by using the S-KgNB or the S-KeNB, namely the key on the SCG side and the integrity protection algorithm.
3. After receiving the MCGFailureInformation message, if the message carries the information on the SCG side, the SCG needs to verify the identity validity of the terminal equipment according to the information, and if the message carries the information on the MCG side, the SCG forwards the information to the MCG, and the MCG verifies the identity validity of the terminal equipment. Further, the method comprises the steps of,
option 1: the SCG sends an SCG activation message to the terminal device. Or,
option 2: the SCG sends the MCGFailureinformation message or the content in the MCGFailureinformation message to the MCG, prepares an SCG activation message, and sends the SCG activation message to the terminal equipment through a link on the SCG side.
4. After receiving the MCGFailureInformation message or the MCG failure notification message sent by the SCG, the MCG sends an RRC reconfiguration message carrying synchronous reconfiguration (reconfiguration with sync) to the terminal equipment or sends an RRC Release (RRC Release) message to the SCG through a link on the SCG side.
Application example three
The terminal device is configured with a DC mode, e.g. an MR-DC mode.
1. If the SCG is in a deactivated state, the terminal equipment initiates a random access procedure to the SCG when the MCG fails in radio link.
2. In the random access process, the terminal device sends an SCG activation request message to the SCG through a message 3 (MSG 3).
Here, optionally, after the terminal device has sent the SCG activation request message, a timer T316 is started.
The SCG activation request message carries at least one of the following information on the MCG side or the SCG side: C-RNTI, PCI, shortMAC-I. Wherein,
if the SCG activation request message carries information on the MCG side, the C-RNTI is C-RNTI allocated by the MCG for the terminal equipment, the PCI is PCI of a PCell on the MCG side, and the shortMAC-I is shortMAC-I generated by utilizing a KgNB or KeNB, namely a key on the MCG side and an integrity protection algorithm.
If the SCG activation request message carries information of the SCG side, the C-RNTI is C-RNTI allocated by the SCG for the terminal equipment, the PCI is PCI of the PScell of the SCG side, and the shortMAC-I is shortMAC-I generated by using the S-KgNB or the S-KeNB, namely a secret key of the SCG side and an integrity protection algorithm.
Further, the SCG activation request message may also carry a reason (simply referred to as an activation reason) for requesting SCG activation, where the activation reason is, for example, "MCG failure" for indicating at least one of the following: the reason for activation is that MCG fails in radio link; the purpose of activation is to activate SCG; the purpose of activation is to perform a fast recovery of the MCG based on the SCG.
3. After receiving the SCG activation request message, if the SCG carries the information of the SCG side, the SCG needs to verify the identity validity of the terminal equipment according to the information, and if the SCG carries the information of the MCG side, the SCG forwards the information to the MCG, and the MCG verifies the identity validity of the terminal equipment. Further, the method comprises the steps of,
Option 1: the SCG sends an SCG activation message to the terminal device, optionally carrying an activation reason such as "MCG failure". Or,
option 2: the SCG sends an SCG activation request message to the MCG, the MCG prepares an SCG activation message, and the SCG activation message is sent to the terminal equipment through a link on the SCG side.
4. After receiving the SCG activation request message sent by the SCG, the MCG sends an RRC reconfiguration message carrying synchronous reconfiguration (reconfiguration with sync) to the terminal device through a link on the SCG side or sends an RRC Release (RRC Release) message to the SCG.
Fig. 6 is a second flowchart of a method for handling radio link failure according to an embodiment of the present application, as shown in fig. 6, where the method for handling radio link failure includes the following steps:
step 601: the terminal device determines that an MCG radio link failure has occurred.
Step 602: the terminal equipment sends a first message to the SCG and starts a first timer, wherein the first message is used for triggering the quick recovery process of the MCG; and if the terminal equipment receives the SCG deactivation command before the first timer is overtime, the terminal equipment triggers an RRC connection reestablishment process.
In an embodiment of the application, the terminal device is configured with a DC mode, e.g. an MR-DC mode.
In the embodiment of the application, if the terminal equipment detects that the MCG has radio link failure and the first timer is configured, the terminal equipment carries out quick SCG recovery through a link on the SCG side.
Here, the first timer is configured for the network device, and optionally, the first timer is configured for the network device through RRC signaling. The first timer may also be referred to as a timer Guard timer or a timer T316, where the timer Guard timer or the timer T316 may refer to the description of the related schemes described above.
In the embodiment of the application, in the process that the terminal equipment carries out rapid SCG recovery through the link of the SCG side, the terminal equipment sends a first message to the MCG through the link of the SCG side, and starts a first timer after the first message is sent. Here, optionally, the first message is an RRC connection reestablishment request message or an MCG failure information message or an SCG activation request message.
Here, the SCG-side link is, for example, split SRB1 (see fig. 3) or SRB3 (see fig. 4). It should be noted that, when the terminal device sends the first message, the SCG is still in an active state, so the terminal device may send the first message by using split SRB1 or SRB3 on the SCG side.
In the embodiment of the present application, if the terminal device receives the SCG deactivation command before the first timer expires (or during the operation of the first timer), the terminal device triggers an RRC connection reestablishment procedure. Here, the point in time when the terminal device triggers the RRC connection reestablishment procedure may have the following two options:
option 1: after receiving the SCG deactivation command, the terminal equipment stops the first timer and triggers an RRC connection reestablishment process; or,
option 2: and after receiving the SCG deactivation command, the terminal equipment maintains the operation of the first timer and triggers an RRC connection reestablishment process after the first timer is overtime.
In the above scheme, during the running of the first timer, the SCG is maintained in an activated state; after the first timer expires or expires, the SCG enters a deactivated state.
For example: during the operation of the timer T316, if an SCG deactivation command is received, the terminal device: the terminal equipment stops the timer T316 and triggers the RRC connection reestablishment process; alternatively, the terminal device maintains the operation of the timer T316 and triggers the RRC connection reestablishment procedure after the timer T316 expires. Here, during the running of the timer T316, the SCG is in an active state, and the terminal device stores PDCCH monitoring on the SCG side. After the timer T316 expires or expires, the SCG is in a deactivated state, and the terminal device does not transmit and/or receive on the SCG side.
Fig. 7 is a schematic structural diagram of an apparatus for processing radio link failure according to an embodiment of the present application, as shown in fig. 7, where the apparatus for processing radio link failure includes:
a determining unit 701, configured to determine that an MCG radio link failure occurs when the SCG is in a deactivated state;
a communication unit 702, configured to trigger an RRC connection reestablishment procedure of the MCG or a fast recovery procedure of the MCG.
In some alternative embodiments, the communication unit 702 is configured to initiate a random access procedure to an SCG, and perform quick recovery of the MCG based on the SCG.
In some alternative embodiments, the communication unit 702 is configured to send a first message to the SCG, where the first message is carried in MSG3 in a random access procedure; and receiving an RRC reconfiguration message or an RRC release message sent by the SCG, wherein the RRC reconfiguration message carries synchronous reconfiguration, and the RRC reconfiguration message or the RRC release message is sent to the SCG by the MCG.
In some alternative embodiments, the terminal device is configured with a first timer; the apparatus further comprises:
a control unit, configured to start the first timer after sending the first message to the SCG; and stopping the first timer if the RRC reconfiguration message or the RRC release message is received before the first timer times out.
In some alternative embodiments, the first message is an RRC connection reestablishment request message.
In some optional embodiments, the RRC connection reestablishment request message carries at least one of:
the first C-RNTI is C-RNTI allocated by the MCG to the terminal equipment;
a first PCI that is a PCI of a PCell in an MCG;
the first shortMAC-I is generated by an MCG-based key and an integrity protection algorithm.
In some optional embodiments, the RRC connection reestablishment request message carries a reestablishment reason, where the reestablishment reason is used to indicate at least one of:
the reason for the reestablishment is that the MCG fails the radio link;
the purpose of the rebuild is to activate SCG;
the purpose of the reconstruction is to perform a fast recovery of the MCG based on the SCG.
In some optional embodiments, the communication unit 702 is further configured to receive, after sending the first message to the SCG, an SCG activation confirmation message or an RRC connection reestablishment message sent by the SCG;
wherein the SCG activation confirmation message is prepared and issued by the SCG; alternatively, the SCG activation confirmation message is prepared by the MCG and forwarded to the SCG for delivery by the SCG.
In some alternative embodiments, in the case where the SCG activation confirmation message is prepared by an MCG,
after the MCG failure message or the RRC connection reestablishment message is sent to the MCG by the SCG, the SCG activation confirmation message is prepared by the MCG.
In some alternative embodiments, the first message is an MCG failure information message or an SCG activation request message.
In some optional embodiments, the MCG failure information message or the SCG activation request message carries first information on the MCG side or second information on the SCG side.
In some alternative embodiments, the first information on the MCG side includes at least one of:
the first C-RNTI is C-RNTI allocated by the MCG to the terminal equipment;
a first PCI that is a PCI of a PCell in an MCG;
the first shortMAC-I is generated by an MCG-based key and an integrity protection algorithm.
In some alternative embodiments, the second information on the SCG side includes at least one of:
a second C-RNTI, wherein the second C-RNTI is C-RNTI allocated by SCG for the terminal equipment;
a second PCI, which is a PCI of a PSCell in an SCG;
and the second shortMAC-I is generated by a key and an integrity protection algorithm based on SCG.
In some optional embodiments, in a case that the MCG failure information message or the SCG activation request message carries first information on the MCG side, the first information is forwarded to the MCG by the SCG and the identity of the terminal device is verified by the MCG based on the first information.
In some optional embodiments, in a case that the MCG failure information message or the SCG activation request message carries second information on the SCG side, the second information verifies, by the SCG, the identity of the terminal device based on the second information.
In some optional embodiments, in a case that the first message is an SCG activation request message, the SCG activation request message carries an activation reason, where the activation reason is used to indicate at least one of the following:
the reason for activation is that MCG fails in radio link;
the purpose of activation is to activate SCG;
the purpose of activation is to perform a fast recovery of the MCG based on the SCG.
In some optional embodiments, the communication unit 702 is further configured to receive, after sending the first message to the SCG, an SCG activation message sent by the SCG;
wherein the SCG activation message is prepared and issued by the SCG; alternatively, the SCG activation message is prepared by the MCG and forwarded to the SCG for delivery by the SCG.
In some alternative embodiments, where the first message is an SCG activation request message,
after the SCG activation request message is sent to the MCG by the SCG, the SCG activation message is prepared by the MCG.
In some alternative embodiments, where the first message is an MCG failure information message,
after the MCG failure information message or the content in the MCG failure information message is sent to the MCG by the SCG, the SCG activation message is prepared by the MCG.
In some alternative embodiments, the SCG activation message carries an activated SCG reason for indicating at least one of:
the reason for activation is that MCG fails in radio link;
the purpose of activation is to activate SCG;
the purpose of activation is to perform a fast recovery of the MCG based on the SCG.
It should be understood by those skilled in the art that the above description of the apparatus for handling radio link failure according to the embodiments of the present application may be understood with reference to the description of the method for handling radio link failure according to the embodiments of the present application.
Fig. 8 is a schematic diagram ii of a structural composition of an apparatus for processing radio link failure according to an embodiment of the present application, where, as shown in fig. 8, the apparatus for processing radio link failure includes:
A determining unit 801, configured to determine that an MCG radio link failure occurs;
a communication unit 802, configured to send a first message to the SCG, where the first message is used to trigger a fast recovery procedure of the MCG;
a control unit 803, configured to start a first timer after the communication unit sends a first message to the SCG;
the communication unit 802 is further configured to trigger an RRC connection reestablishment procedure if an SCG deactivation command is received before the first timer expires.
In some alternative embodiments, the control unit 803 is configured to stop the first timer after the communication unit 802 receives an SCG deactivation command; alternatively, after the communication unit 802 receives the SCG deactivation command, the operation of the first timer is maintained until timeout;
the communication unit 802 is configured to trigger an RRC connection reestablishment procedure after the first timer is stopped or expires.
In some alternative embodiments, the SCG is maintained in an active state during operation of the first timer;
after the first timer expires or expires, the SCG enters a deactivated state.
In some alternative embodiments, the first message is an RRC connection reestablishment request message or an MCG failure information message or an SCG activation request message.
It should be understood by those skilled in the art that the above description of the apparatus for handling radio link failure according to the embodiments of the present application may be understood with reference to the description of the method for handling radio link failure according to the embodiments of the present application.
Fig. 9 is a schematic block diagram of a communication device 900 according to an embodiment of the present application. The communication device may be a terminal device or a network device, and the communication device 900 shown in fig. 9 includes a processor 910, where the processor 910 may call and execute a computer program from a memory to implement a method according to an embodiment of the present application.
Optionally, as shown in fig. 9, the communication device 900 may also include a memory 920. Wherein the processor 910 may invoke and run a computer program from the memory 920 to implement the method in the embodiments of the present application.
Wherein the memory 920 may be a separate device from the processor 910 or may be integrated in the processor 910.
Optionally, as shown in fig. 9, the communication device 900 may further include a transceiver 930, and the processor 910 may control the transceiver 930 to communicate with other devices, and in particular, may send information or data to other devices, or receive information or data sent by other devices.
Wherein transceiver 930 may include a transmitter and a receiver. Transceiver 930 may further include antennas, the number of which may be one or more.
Optionally, the communication device 900 may be specifically a network device in the embodiment of the present application, and the communication device 900 may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.
Optionally, the communication device 900 may be specifically a mobile terminal/terminal device according to an embodiment of the present application, and the communication device 900 may implement corresponding processes implemented by the mobile terminal/terminal device in each method according to the embodiment of the present application, which are not described herein for brevity.
Fig. 10 is a schematic structural view of a chip of an embodiment of the present application. The chip 1000 shown in fig. 10 includes a processor 1010, and the processor 1010 may call and run a computer program from a memory to implement the method in the embodiment of the present application.
Optionally, as shown in fig. 10, the chip 1000 may further include a memory 1020. Wherein the processor 1010 may call and run a computer program from the memory 1020 to implement the methods in embodiments of the present application.
The memory 1020 may be a separate device from the processor 1010 or may be integrated into the processor 1010.
Optionally, the chip 1000 may also include an input interface 1030. The processor 1010 may control the input interface 1030 to communicate with other devices or chips, and in particular, may obtain information or data sent by the other devices or chips.
Optionally, the chip 1000 may further include an output interface 1040. Wherein the processor 1010 may control the output interface 1040 to communicate with other devices or chips, and in particular, may output information or data to other devices or chips.
Optionally, the chip may be applied to the network device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.
Optionally, the chip may be applied to a mobile terminal/terminal device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein for brevity.
It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.
Fig. 11 is a schematic block diagram of a communication system 1100 provided by an embodiment of the present application. As shown in fig. 11, the communication system 1100 includes a terminal device 1110 and a network device 1120.
The terminal device 1110 may be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 1120 may be used to implement the corresponding functions implemented by the network device in the above method, which are not described herein for brevity.
It should be appreciated that the processor of an embodiment of the present application may be an integrated circuit chip having signal processing capabilities. 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 (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, 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.
It will be appreciated that the memory in embodiments of the application may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and Direct 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.
It should be understood that the above memory is illustrative but not restrictive, and for example, the memory in the embodiments of the present application may be Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), direct RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.
The embodiment of the application also provides a computer readable storage medium for storing a computer program.
Optionally, the computer readable storage medium may be applied to a network device in the embodiment of the present application, and the computer program causes a computer to execute a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.
Optionally, the computer readable storage medium may be applied to a mobile terminal/terminal device in the embodiment of the present application, and the computer program causes a computer to execute a corresponding procedure implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, which is not described herein for brevity.
The embodiment of the application also provides a computer program product comprising computer program instructions.
Optionally, the computer program product may be applied to a network device in the embodiment of the present application, and the computer program instructions cause a computer to execute corresponding processes implemented by the network device in each method in the embodiment of the present application, which are not described herein for brevity.
Optionally, the computer program product may be applied to a mobile terminal/terminal device in the embodiment of the present application, and the computer program instructions cause a computer to execute corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, which are not described herein for brevity.
The embodiment of the application also provides a computer program.
Optionally, the computer program may be applied to a network device in the embodiment of the present application, and when the computer program runs on a computer, the computer is caused to execute a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.
Optionally, the computer program may be applied to a mobile terminal/terminal device in the embodiment of the present application, and when the computer program runs on a computer, the computer is caused to execute corresponding processes implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein for brevity.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.
In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The foregoing is merely illustrative of the present application, and the present application 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 application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (53)
- A method of handling radio link failure, the method comprising:the terminal equipment determines that the primary cell group MCG radio link failure occurs under the condition that the secondary cell group SCG is in a deactivated state;the terminal device triggers the radio resource control RRC connection reestablishment process of the MCG or the quick recovery process of the MCG.
- The method of claim 1, wherein the terminal device triggers a fast recovery procedure of the MCG, comprising:and the terminal equipment initiates a random access process to the SCG and carries out quick recovery of the MCG based on the SCG.
- The method of claim 2, wherein the terminal device initiates a random access procedure to an SCG and performs rapid recovery of the MCG based on the SCG, comprising:the terminal equipment sends a first message to the SCG, wherein the first message is borne in MSG3 in a random access process;The terminal equipment receives RRC reconfiguration information or RRC release information sent by SCG, the RRC reconfiguration information carries synchronous reconfiguration, and the RRC reconfiguration information or the RRC release information is sent to the SCG by MCG.
- A method according to claim 3, wherein the terminal device is configured with a first timer; the method further comprises the steps of:after the terminal equipment sends the first message to the SCG, starting the first timer;and if the terminal equipment receives the RRC reconfiguration message or the RRC release message before the first timer is overtime, stopping the first timer by the terminal equipment.
- The method of claim 3 or 4, wherein the first message is an RRC connection reestablishment request message.
- The method of claim 5, wherein the RRC connection reestablishment request message carries at least one of:a first cell radio network temporary identifier C-RNTI, wherein the first C-RNTI is C-RNTI allocated by MCG to the terminal equipment;a first Physical Cell Identifier (PCI), wherein the first PCI is the PCI of a master cell (PCell) in an MCG;the method comprises the steps of authenticating a first short complete message authentication code shortMAC-I, wherein the first shortMAC-I is shortMAC-I generated based on a key of an MCG and an integrity protection algorithm.
- The method according to claim 5 or 6, wherein the RRC connection reestablishment request message carries a reestablishment reason for indicating at least one of:the reason for the reestablishment is that the MCG fails the radio link;the purpose of the rebuild is to activate SCG;the purpose of the reconstruction is to perform a fast recovery of the MCG based on the SCG.
- The method according to any of claims 5 to 7, wherein after the terminal device sends the first message to the SCG, the method further comprises:the terminal equipment receives an SCG activation confirmation message or an RRC connection reestablishment message sent by the SCG;wherein the SCG activation confirmation message is prepared and issued by the SCG; alternatively, the SCG activation confirmation message is prepared by the MCG and forwarded to the SCG for delivery by the SCG.
- The method of claim 8, wherein, in the case where the SCG activation confirmation message is prepared by an MCG,after the MCG failure message or the RRC connection reestablishment message is sent to the MCG by the SCG, the SCG activation confirmation message is prepared by the MCG.
- The method of claim 3 or 4, wherein the first message is an MCG failure information message or an SCG activation request message.
- The method of claim 10, wherein the MCG failure information message or SCG activation request message carries first information on an MCG side or second information on an SCG side.
- The method of claim 11, wherein the first information of the MCG side includes at least one of:the first C-RNTI is C-RNTI allocated by the MCG to the terminal equipment;a first PCI that is a PCI of a PCell in an MCG;the first shortMAC-I is generated by an MCG-based key and an integrity protection algorithm.
- The method of claim 11, wherein the second information of the SCG side comprises at least one of:a second C-RNTI, wherein the second C-RNTI is C-RNTI allocated by SCG for the terminal equipment;a second PCI, which is a PCI of a PSCell in an SCG;and the second shortMAC-I is generated by a key and an integrity protection algorithm based on SCG.
- The method according to claim 11 or 12, wherein in case the MCG failure information message or SCG activation request message carries first information on the MCG side, the first information is forwarded by the SCG to the MCG and the identity of the terminal device is verified by the MCG based on the first information.
- The method according to claim 11 or 13, wherein in case the MCG failure information message or SCG activation request message carries second information on the SCG side, the second information verifies the identity of the terminal device by the SCG based on the second information.
- The method according to any one of claims 10 to 15, wherein, in case the first message is an SCG activation request message, the SCG activation request message carries an activation cause for indicating at least one of:the reason for activation is that MCG fails in radio link;the purpose of activation is to activate SCG;the purpose of activation is to perform a fast recovery of the MCG based on the SCG.
- The method according to any of claims 10 to 16, wherein after the terminal device sends the first message to the SCG, the method further comprises:the terminal equipment receives an SCG activation message sent by the SCG;wherein the SCG activation message is prepared and issued by the SCG; alternatively, the SCG activation message is prepared by the MCG and forwarded to the SCG for delivery by the SCG.
- The method of claim 17, wherein, in the case where the first message is an SCG activation request message,After the SCG activation request message is sent to the MCG by the SCG, the SCG activation message is prepared by the MCG.
- The method of claim 17, wherein, in the case where the first message is an MCG failure information message,after the MCG failure information message or the content in the MCG failure information message is sent to the MCG by the SCG, the SCG activation message is prepared by the MCG.
- The method of any of claims 17 to 19, wherein the SCG activation message carries an activation SCG reason for indicating at least one of:the reason for activation is that MCG fails in radio link;the purpose of activation is to activate SCG;the purpose of activation is to perform a fast recovery of the MCG based on the SCG.
- A method of handling radio link failure, the method comprising:the terminal equipment determines that MCG radio link failure occurs;the terminal equipment sends a first message to the SCG and starts a first timer, wherein the first message is used for triggering the quick recovery process of the MCG;and if the terminal equipment receives the SCG deactivation command before the first timer is overtime, the terminal equipment triggers an RRC connection reestablishment process.
- The method of claim 21, wherein the terminal device triggers an RRC connection reestablishment procedure comprising:After receiving the SCG deactivation command, the terminal equipment stops the first timer and triggers an RRC connection reestablishment process; or,and after receiving the SCG deactivation command, the terminal equipment maintains the operation of the first timer and triggers an RRC connection reestablishment process after the first timer is overtime.
- The method of claim 22, wherein,during operation of the first timer, the SCG is maintained in an active state;after the first timer expires or expires, the SCG enters a deactivated state.
- The method according to any of claims 21 to 23, wherein the first message is an RRC connection reestablishment request message or an MCG failure information message or an SCG activation request message.
- An apparatus for handling radio link failure, applied to a terminal device, the apparatus comprising:a determining unit, configured to determine that an MCG radio link failure occurs when the SCG is in a deactivated state;and the communication unit is used for triggering the RRC connection reestablishment process of the MCG or the quick recovery process of the MCG.
- The apparatus of claim 25, wherein the communication unit is configured to initiate a random access procedure to an SCG and to perform fast recovery of an MCG based on the SCG.
- The apparatus of claim 26, wherein the communication unit is configured to send a first message to an SCG, the first message being carried in MSG3 in a random access procedure; and receiving an RRC reconfiguration message or an RRC release message sent by the SCG, wherein the RRC reconfiguration message carries synchronous reconfiguration, and the RRC reconfiguration message or the RRC release message is sent to the SCG by the MCG.
- The apparatus of claim 27, wherein the terminal device is configured with a first timer; the apparatus further comprises:a control unit, configured to start the first timer after sending the first message to the SCG; and stopping the first timer if the RRC reconfiguration message or the RRC release message is received before the first timer times out.
- The apparatus of claim 27 or 28, wherein the first message is an RRC connection reestablishment request message.
- The apparatus of claim 29, wherein the RRC connection reestablishment request message carries at least one of:the first C-RNTI is C-RNTI allocated by the MCG to the terminal equipment;a first PCI that is a PCI of a PCell in an MCG;The first shortMAC-I is generated by an MCG-based key and an integrity protection algorithm.
- The apparatus of claim 29 or 30, wherein the RRC connection reestablishment request message carries a reestablishment reason for indicating at least one of:the reason for the reestablishment is that the MCG fails the radio link;the purpose of the rebuild is to activate SCG;the purpose of the reconstruction is to perform a fast recovery of the MCG based on the SCG.
- The apparatus of any one of claims 29 to 31, wherein the communication unit is further configured to receive an SCG activation confirmation message or an RRC connection reestablishment message sent by the SCG after sending the first message to the SCG;wherein the SCG activation confirmation message is prepared and issued by the SCG; alternatively, the SCG activation confirmation message is prepared by the MCG and forwarded to the SCG for delivery by the SCG.
- The apparatus of claim 32, wherein, in the case where the SCG activation confirmation message is prepared by an MCG,after the MCG failure message or the RRC connection reestablishment message is sent to the MCG by the SCG, the SCG activation confirmation message is prepared by the MCG.
- The apparatus of claim 27 or 28, wherein the first message is an MCG failure information message or an SCG activation request message.
- The apparatus of claim 34, wherein the MCG failure information message or SCG activation request message carries first information on an MCG side or second information on an SCG side.
- The apparatus of claim 35, wherein the first information of the MCG side comprises at least one of:the first C-RNTI is C-RNTI allocated by the MCG to the terminal equipment;a first PCI that is a PCI of a PCell in an MCG;the first shortMAC-I is generated by an MCG-based key and an integrity protection algorithm.
- The apparatus of claim 35, wherein the second information of the SCG side comprises at least one of:a second C-RNTI, wherein the second C-RNTI is C-RNTI allocated by SCG for the terminal equipment;a second PCI, which is a PCI of a PSCell in an SCG;and the second shortMAC-I is generated by a key and an integrity protection algorithm based on SCG.
- The apparatus of claim 35 or 36, wherein, in case the MCG failure information message or SCG activation request message carries first information on the MCG side, the first information is forwarded by the SCG to the MCG and the identity of the terminal device is verified by the MCG based on the first information.
- The apparatus of claim 35 or 37, wherein the second information verifies, by the SCG, the identity of the terminal device based on the second information if the MCG failure information message or SCG activation request message carries second information on the SCG side.
- The apparatus of any of claims 34 to 39, wherein, in the case where the first message is an SCG activation request message, the SCG activation request message carries an activation cause indicating at least one of:the reason for activation is that MCG fails in radio link;the purpose of activation is to activate SCG;the purpose of activation is to perform a fast recovery of the MCG based on the SCG.
- The apparatus of any one of claims 34 to 40, wherein the communication unit is further configured to receive an SCG activation message sent by the SCG after sending the first message to the SCG;wherein the SCG activation message is prepared and issued by the SCG; alternatively, the SCG activation message is prepared by the MCG and forwarded to the SCG for delivery by the SCG.
- The apparatus of claim 41, wherein in the case where the first message is an SCG activation request message,after the SCG activation request message is sent to the MCG by the SCG, the SCG activation message is prepared by the MCG.
- The apparatus of claim 41, wherein in the case where the first message is an MCG failure information message,after the MCG failure information message or the content in the MCG failure information message is sent to the MCG by the SCG, the SCG activation message is prepared by the MCG.
- The apparatus of any one of claims 41 to 43, wherein the SCG activation message carries an activation SCG reason for indicating at least one of:the reason for activation is that MCG fails in radio link;the purpose of activation is to activate SCG;the purpose of activation is to perform a fast recovery of the MCG based on the SCG.
- An apparatus for handling radio link failure, applied to a terminal device, the apparatus comprising:a determining unit, configured to determine that an MCG radio link failure occurs;a communication unit, configured to send a first message to an SCG, where the first message is used to trigger a fast recovery procedure of the MCG;a control unit, configured to start a first timer after the communication unit sends a first message to the SCG;the communication unit is further configured to trigger an RRC connection reestablishment procedure if an SCG deactivation command is received before the first timer expires.
- The apparatus of claim 45, wherein,The control unit is used for stopping the first timer after the communication unit receives the SCG deactivation command; or after the communication unit receives the SCG deactivation command, maintaining the operation of the first timer until the time-out;the communication unit is configured to trigger an RRC connection reestablishment procedure after the first timer is stopped or overtime.
- The apparatus of claim 46, wherein,during operation of the first timer, the SCG is maintained in an active state;after the first timer expires or expires, the SCG enters a deactivated state.
- The apparatus of any one of claims 45 to 47, wherein the first message is an RRC connection reestablishment request message or an MCG failure information message or an SCG activation request message.
- A communication device, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and run the computer program stored in the memory, to perform the method of any of claims 1 to 20, or the method of any of claims 21 to 24.
- A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any one of claims 1 to 20 or the method of any one of claims 21 to 24.
- A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 20 or the method of any one of claims 21 to 24.
- A computer program product comprising computer program instructions which cause a computer to perform the method of any one of claims 1 to 20 or the method of any one of claims 21 to 24.
- A computer program which causes a computer to perform the method of any one of claims 1 to 20 or the method of any one of claims 21 to 24.
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2021/085103 WO2022205374A1 (en) | 2021-04-01 | 2021-04-01 | Radio link failure processing method and apparatus, and communication device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116636299A true CN116636299A (en) | 2023-08-22 |
Family
ID=83457564
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202180082863.6A Pending CN116636299A (en) | 2021-04-01 | 2021-04-01 | Method and device for processing radio link failure and communication equipment |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN116636299A (en) |
| WO (1) | WO2022205374A1 (en) |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110839301B (en) * | 2018-08-16 | 2021-09-10 | 维沃移动通信有限公司 | Information processing method, terminal and network equipment for radio link failure |
| EP3925399A1 (en) * | 2019-02-11 | 2021-12-22 | Telefonaktiebolaget LM Ericsson (publ) | Master cell group failure handling by a master node |
| US20220159483A1 (en) * | 2019-03-28 | 2022-05-19 | Lg Electronics Inc. | Activation of secondary cell group configuration upon master cell group failure detection |
| CN114303439A (en) * | 2019-08-28 | 2022-04-08 | 瑞典爱立信有限公司 | Method, apparatus, computer program and computer program product for indicating use of a master cell group fast recovery procedure |
-
2021
- 2021-04-01 WO PCT/CN2021/085103 patent/WO2022205374A1/en active Application Filing
- 2021-04-01 CN CN202180082863.6A patent/CN116636299A/en active Pending
Also Published As
| Publication number | Publication date |
|---|---|
| WO2022205374A1 (en) | 2022-10-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20200351977A1 (en) | Information transmission method and apparatus, and communication device | |
| US20240080699A1 (en) | Sdt failure reporting method, terminal device, and network device | |
| US20230328807A1 (en) | Methods and apparatuses for designing an adaptation layer and handling a failure in a sidelink relay system | |
| CN113796118B (en) | Switching method and device and communication equipment | |
| CN113068276B (en) | Information configuration method and device, terminal and network equipment | |
| CN114125969B (en) | Connection reestablishing method, terminal equipment and storage medium | |
| CN112703802B (en) | Method and device for processing uplink coverage weakening, terminal and network equipment | |
| CN116491216A (en) | Method and apparatus for fast MCG link recovery procedure and MRO mechanism for unbalanced UL and DL coverage scenarios | |
| WO2020206643A1 (en) | Random access method, device, and storage medium | |
| US11553344B2 (en) | Information transmission method, network device and terminal device | |
| CN112789891A (en) | Wireless communication method, device and terminal equipment | |
| US11265951B2 (en) | Method and apparatus for recovering RRC connection, and terminal | |
| CN116636299A (en) | Method and device for processing radio link failure and communication equipment | |
| CN117295182A (en) | Method and device for determining terminal equipment behaviors, terminal equipment and network equipment | |
| CN116097801A (en) | Communication method and device, terminal equipment and network equipment | |
| CN112703770A (en) | RRC connection reestablishment method and device, and network equipment | |
| CN113348699B (en) | Data transmission method, device and communication equipment | |
| US20230199712A1 (en) | Wireless communication method and terminal | |
| WO2022110048A1 (en) | Information indication method and apparatus, terminal device, and network device | |
| WO2022151239A1 (en) | Method and apparatus for data transmission processing | |
| CN116210336A (en) | Key generation method and device, terminal equipment and network equipment | |
| CN116134912A (en) | Communication method and device, network equipment and terminal equipment | |
| CN117480849A (en) | Method and device for controlling random access and terminal equipment | |
| CN116097744A (en) | Method and device for negotiating communication and terminal equipment | |
| CN116648980A (en) | Method and device for updating position and terminal equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |